From daemon@ns.ietf.org  Mon Apr  1 10:52:36 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02383
	for <sipping-archive@odin.ietf.org>; Mon, 1 Apr 2002 10:52:36 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA17133
	for sipping-archive@odin.ietf.org; Mon, 1 Apr 2002 10:52:37 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA16589;
	Mon, 1 Apr 2002 10:41:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA16556
	for <sipping@ns.ietf.org>; Mon, 1 Apr 2002 10:41:24 -0500 (EST)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02098
	for <sipping@ietf.org>; Mon, 1 Apr 2002 10:41:22 -0500 (EST)
Received: from cia.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id g31Ff8X02989;
	Mon, 1 Apr 2002 10:41:09 -0500 (EST)
Received: from MHAMMER-W2K.cisco.com (hrn2-dhcp-161-44-87-145.cisco.com [161.44.87.145])
	by cia.cisco.com (Mirapoint)
	with ESMTP id AAS97440;
	Mon, 1 Apr 2002 10:35:41 -0500 (EST)
Message-Id: <4.3.2.7.2.20020401103720.00b0a650@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 01 Apr 2002 10:40:42 -0500
To: Romel Khan <rkhan@net2phone.com>
From: Michael Hammer <mhammer@cisco.com>
Subject: Re: [Sipping] Question on ISUP to SIP mapping draft
Cc: sipping@ietf.org, "'jon.peterson@neustar.biz'" <jon.peterson@neustar.biz>
In-Reply-To: <6F46FABB90ABD411BD690002B3152FB97BAA17@lkwmail01>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Romel,

That is not the only case where such non-bi-directional mapping occurs.

I would recommend using only the encapsulated ISUP for transit 
situations.  The response codes should only be used to ISUP cause codes 
when the SIP message source is a SIP node.

Mike



At 03:05 PM 3/31/2002 -0500, Romel Khan wrote:
>1. Mapping ISDN cause to SIP status in section 6.2.4.1 states that cause 18
>"no user responding" to SIP 408 Request Timeout. This is reasonable.
>However, in section 7.2.6.1, for SIP to ISUP, it shows 408 to ISDN cause 102
>Recovery on timer expiry. This is unreasonable. This interworking should be
>bidirectional:
>SIP 408 <==> ISDN cause 18 "No User Responding"
>
>An example of why it is unreasonable: With a SIP B2BUA where there is an
>inbound leg and an outbound leg for a call going to a Softswitch which
>terminates SS7. Callee starts ringing and does not pick up the phone within
>a period which causes the ring timer in the Softswitch to expire. The
>Softswitch then sends 408 to the B2BUA, which will send back the 408 on the
>inbound leg. If the PSTN connectivity to the Inbound is SS7 or ISDN, don't
>want the corresponding REL/DISC msg to interwork with cause 102 but rather
>the cause should be 18 "No User Responding". Why should SIP 480 map to ISDN
>cause 18 in this case? Why not please keep some of these interworking same
>both ways (bidirectional) ==> simplifies many implementer's life, minimizes
>departure from the spec.,enhances interoperability.
>
>
>2. Need a SIP status code that interworks to ISDN cause 31 "Normal
>Unspecified".
>
>
>Thanks,
>Romel
>
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the 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 daemon@optimus.ietf.org  Mon Apr  1 17:11:56 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16786
	for <sipping-archive@odin.ietf.org>; Mon, 1 Apr 2002 17:11:56 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA16123
	for sipping-archive@odin.ietf.org; Mon, 1 Apr 2002 17:11:59 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA14471;
	Mon, 1 Apr 2002 16:57:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA14442
	for <sipping@optimus.ietf.org>; Mon, 1 Apr 2002 16:57:26 -0500 (EST)
Received: from mail.net2phone.com (mail.net2phone.com [216.53.3.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16512
	for <sipping@ietf.org>; Mon, 1 Apr 2002 16:57:23 -0500 (EST)
Received: from mailsvr.net2phone.com (exchange.net2phone.com [216.53.60.1])
	by mail.net2phone.com (8.11.5/8.11.5) with ESMTP id g31LuvM20945;
	Mon, 1 Apr 2002 16:56:57 -0500 (EST)
Received: by mailsvr with Internet Mail Service (5.5.2653.19)
	id <HSM24WYL>; Mon, 1 Apr 2002 16:56:40 -0500
Message-ID: <6F46FABB90ABD411BD690002B3152FB97BAA1B@lkwmail01>
From: Romel Khan <rkhan@net2phone.com>
To: "'Michael Hammer'" <mhammer@cisco.com>
Cc: sipping@ietf.org,
        "'jon.peterson@neustar.biz'"
	 <jon.peterson@neustar.biz>
Subject: RE: [Sipping] Question on ISUP to SIP mapping draft
Date: Mon, 1 Apr 2002 16:54:04 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Some SIP node are not designed to look at the encapsulated
ISUP.....(complicates some things pointlessly). Some SIP nodes will get rid
of the ISUP body. So by the time the terminating SIP endpoint gateway (that
interworks to SS7) receives the SIP message there is no ISUP body. Moreover,
looks like most switches today will not look at the ISUP body in SIP msg to
interwork to ISUP.

Is there any particular hindrance towards making a relevant bunch of these
SIP Status code to/from ISUP cause code bidirectional interworking (using
sec 6.2.4.1 as starting base)? If I were to be able to vote I would request
bidirectional whereever possible. Of course, majority of the cases looks
like multiple ISDN cause maps to a single SIP status code, e.g. cause
34,41,etc to SIP 503; SIP 503 to one of those, such as, cause 41 is
reasonable. But if it is one to one mapping in sec 6.2.4.1, it is reasonable
to have it map the other way round. Examples are: 
Already defined:
SIP 486 <==> ISDN cause 17 
SIP 484 <==> ISDN cause 28

Requesting:
-- SIP 408 <==> ISDN cause 18

-- Sec. 6.2.4.1 defines ISDN cause 19,20,31 ==> SIP 480, then SIP 480 to
ISDN cause 18 as in sec. 7.2.6.1 is unreasonable. Mapping to ISDN cause 19
or 20 or 31 is the reasonable choice.


Thanks,
Romel 
Net2Phone




-----Original Message-----
From: Michael Hammer [mailto:mhammer@cisco.com]
Sent: Monday, April 01, 2002 10:41 AM
To: Romel Khan
Cc: sipping@ietf.org; 'jon.peterson@neustar.biz'
Subject: Re: [Sipping] Question on ISUP to SIP mapping draft


Romel,

That is not the only case where such non-bi-directional mapping occurs.

I would recommend using only the encapsulated ISUP for transit 
situations.  The response codes should only be used to ISUP cause codes 
when the SIP message source is a SIP node.

Mike



At 03:05 PM 3/31/2002 -0500, Romel Khan wrote:
>1. Mapping ISDN cause to SIP status in section 6.2.4.1 states that cause 18
>"no user responding" to SIP 408 Request Timeout. This is reasonable.
>However, in section 7.2.6.1, for SIP to ISUP, it shows 408 to ISDN cause
102
>Recovery on timer expiry. This is unreasonable. This interworking should be
>bidirectional:
>SIP 408 <==> ISDN cause 18 "No User Responding"
>
>An example of why it is unreasonable: With a SIP B2BUA where there is an
>inbound leg and an outbound leg for a call going to a Softswitch which
>terminates SS7. Callee starts ringing and does not pick up the phone within
>a period which causes the ring timer in the Softswitch to expire. The
>Softswitch then sends 408 to the B2BUA, which will send back the 408 on the
>inbound leg. If the PSTN connectivity to the Inbound is SS7 or ISDN, don't
>want the corresponding REL/DISC msg to interwork with cause 102 but rather
>the cause should be 18 "No User Responding". Why should SIP 480 map to ISDN
>cause 18 in this case? Why not please keep some of these interworking same
>both ways (bidirectional) ==> simplifies many implementer's life, minimizes
>departure from the spec.,enhances interoperability.
>
>
>2. Need a SIP status code that interworks to ISDN cause 31 "Normal
>Unspecified".
>
>
>Thanks,
>Romel
>
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the 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 daemon@optimus.ietf.org  Mon Apr  1 17:28:53 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17322
	for <sipping-archive@odin.ietf.org>; Mon, 1 Apr 2002 17:28:51 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA16671
	for sipping-archive@odin.ietf.org; Mon, 1 Apr 2002 17:28:54 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA16375;
	Mon, 1 Apr 2002 17:19:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA16343
	for <sipping@optimus.ietf.org>; Mon, 1 Apr 2002 17:19:49 -0500 (EST)
Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16998
	for <sipping@ietf.org>; Mon, 1 Apr 2002 17:19:45 -0500 (EST)
Received: from DYN-VA-EXCH-001.dynamicsoft.com (dyn-va-exch-001 [63.114.208.70])
	by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id g31MGie8008636;
	Mon, 1 Apr 2002 17:16:44 -0500 (EST)
Received: by DYN-VA-EXCH-001.dynamicsoft.com with Internet Mail Service (5.5.2650.21)
	id <GNFB6WK0>; Mon, 1 Apr 2002 17:19:02 -0500
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F36301AE@DYN-TX-EXCH-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'Romel Khan'" <rkhan@net2phone.com>, sipping@ietf.org
Cc: "'jon.peterson@neustar.biz'" <jon.peterson@neustar.biz>
Subject: RE: [Sipping] Question on ISUP to SIP mapping draft
Date: Mon, 1 Apr 2002 17:19:01 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

> 2. Need a SIP status code that interworks to ISDN cause 31 "Normal
> Unspecified".


No, you don't.


For normal call clearing, you'll have a flow something
like:

SIP            MGC            PSTN
 |----INVITE--->|              |
 |              |-----IAM----->|
 |              |<----ACM------|
 |----CANCEL--->|              |
 |<----200------|              |
 |<----487------|              |
 |              |-----REL----->| with cause=31
 |              |<----RLC------|

Or:

SIP            MGC            PSTN
 |----INVITE--->|              |
 |              |-----IAM----->|
 |              |<----ACM------|
 |<----180------|              |
 |              |<----ANM------|
 |<----200------|              |
 |-----ACK----->|              |
 |              |<----REL------| with cause=31
 |              |-----RLC----->|
 |<----BYE------|              |
 |-----200----->|              |

So far, no response code mapping is needed.

The only call flow that would possibly use what
you ask for would start something like this:

SIP            MGC            PSTN
 |----INVITE--->|              |
 |              |-----IAM----->|
 |              |<----REL------| with cause=31

To which anyone who knows ISUP will respond: "WHAT?!?!?
I sent an IAM and got **NORMAL CLEARING** back as a
response? What sort of crack were they smoking when
the wrote *that* code?"

For some reason, we decided not define behavior for
impossible situations. I suspect any reasonably implemented
MGC will clean this up in some appropriate fashion
(probably a reset towards the PSTN and a 500 class
message towards the SIP network), raise an O&M alarm,
and possibly take the trunk in question out of service...
but that's completely up to the implementor.

/a

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



From daemon@optimus.ietf.org  Mon Apr  1 17:40:34 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17775
	for <sipping-archive@odin.ietf.org>; Mon, 1 Apr 2002 17:40:29 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA17593
	for sipping-archive@odin.ietf.org; Mon, 1 Apr 2002 17:40:32 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA17277;
	Mon, 1 Apr 2002 17:31:30 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA17239
	for <sipping@optimus.ietf.org>; Mon, 1 Apr 2002 17:31:27 -0500 (EST)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17418
	for <sipping@ietf.org>; Mon, 1 Apr 2002 17:31:23 -0500 (EST)
Received: from cia.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id g31MVBK23787;
	Mon, 1 Apr 2002 17:31:12 -0500 (EST)
Received: from MHAMMER-W2K.cisco.com (hrn2-dhcp-161-44-87-145.cisco.com [161.44.87.145])
	by cia.cisco.com (Mirapoint)
	with ESMTP id AAT02109;
	Mon, 1 Apr 2002 17:25:45 -0500 (EST)
Message-Id: <4.3.2.7.2.20020401171058.03994768@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 01 Apr 2002 17:30:47 -0500
To: Romel Khan <rkhan@net2phone.com>
From: Michael Hammer <mhammer@cisco.com>
Subject: RE: [Sipping] Question on ISUP to SIP mapping draft
Cc: sipping@ietf.org, "'jon.peterson@neustar.biz'" <jon.peterson@neustar.biz>
In-Reply-To: <6F46FABB90ABD411BD690002B3152FB97BAA1B@lkwmail01>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Romel,

There is no control over the received ISUP message's choice of cause 
value.  Because of the many-to-one mapping problem, trying to force it to 
be bi-directional, can only mean that there must be a unique response code 
for every ISUP cause code.  I'm not sure that is necessary.

It is not good for the SIP nodes to discard what it cannot understand.  I 
believe proper behavior is to ignore and transmit on.

In any case, if a transit situation requires the ISUP, then the Requires 
header should probably be used to avoid arbitrary dropping of the ISUP 
body.  Otherwise, you will get the less-than-transparent experience you cite.

The interesting question is how do you know at the ingress that you are 
going to an egress gateway versus a smart end-point.  Presumably, ENUM is 
point you to a smart endpoint, but responses from the SIP network may 
divert you to a PSTN number not local to your gateway that then requires 
TRIP or local configuration to select the egress gateway.  Or you are only 
a transit network to begin with.

Thoughts?

Mike


At 04:54 PM 4/1/2002 -0500, Romel Khan wrote:
>Some SIP node are not designed to look at the encapsulated
>ISUP.....(complicates some things pointlessly). Some SIP nodes will get rid
>of the ISUP body. So by the time the terminating SIP endpoint gateway (that
>interworks to SS7) receives the SIP message there is no ISUP body. Moreover,
>looks like most switches today will not look at the ISUP body in SIP msg to
>interwork to ISUP.
>
>Is there any particular hindrance towards making a relevant bunch of these
>SIP Status code to/from ISUP cause code bidirectional interworking (using
>sec 6.2.4.1 as starting base)? If I were to be able to vote I would request
>bidirectional whereever possible. Of course, majority of the cases looks
>like multiple ISDN cause maps to a single SIP status code, e.g. cause
>34,41,etc to SIP 503; SIP 503 to one of those, such as, cause 41 is
>reasonable. But if it is one to one mapping in sec 6.2.4.1, it is reasonable
>to have it map the other way round. Examples are:
>Already defined:
>SIP 486 <==> ISDN cause 17
>SIP 484 <==> ISDN cause 28
>
>Requesting:
>-- SIP 408 <==> ISDN cause 18
>
>-- Sec. 6.2.4.1 defines ISDN cause 19,20,31 ==> SIP 480, then SIP 480 to
>ISDN cause 18 as in sec. 7.2.6.1 is unreasonable. Mapping to ISDN cause 19
>or 20 or 31 is the reasonable choice.
>
>
>Thanks,
>Romel
>Net2Phone
>
>
>
>
>-----Original Message-----
>From: Michael Hammer [mailto:mhammer@cisco.com]
>Sent: Monday, April 01, 2002 10:41 AM
>To: Romel Khan
>Cc: sipping@ietf.org; 'jon.peterson@neustar.biz'
>Subject: Re: [Sipping] Question on ISUP to SIP mapping draft
>
>
>Romel,
>
>That is not the only case where such non-bi-directional mapping occurs.
>
>I would recommend using only the encapsulated ISUP for transit
>situations.  The response codes should only be used to ISUP cause codes
>when the SIP message source is a SIP node.
>
>Mike
>
>
>
>At 03:05 PM 3/31/2002 -0500, Romel Khan wrote:
> >1. Mapping ISDN cause to SIP status in section 6.2.4.1 states that cause 18
> >"no user responding" to SIP 408 Request Timeout. This is reasonable.
> >However, in section 7.2.6.1, for SIP to ISUP, it shows 408 to ISDN cause
>102
> >Recovery on timer expiry. This is unreasonable. This interworking should be
> >bidirectional:
> >SIP 408 <==> ISDN cause 18 "No User Responding"
> >
> >An example of why it is unreasonable: With a SIP B2BUA where there is an
> >inbound leg and an outbound leg for a call going to a Softswitch which
> >terminates SS7. Callee starts ringing and does not pick up the phone within
> >a period which causes the ring timer in the Softswitch to expire. The
> >Softswitch then sends 408 to the B2BUA, which will send back the 408 on the
> >inbound leg. If the PSTN connectivity to the Inbound is SS7 or ISDN, don't
> >want the corresponding REL/DISC msg to interwork with cause 102 but rather
> >the cause should be 18 "No User Responding". Why should SIP 480 map to ISDN
> >cause 18 in this case? Why not please keep some of these interworking same
> >both ways (bidirectional) ==> simplifies many implementer's life, minimizes
> >departure from the spec.,enhances interoperability.
> >
> >
> >2. Need a SIP status code that interworks to ISDN cause 31 "Normal
> >Unspecified".
> >
> >
> >Thanks,
> >Romel
> >
> >_______________________________________________
> >Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> >This list is for NEW development of the 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 daemon@optimus.ietf.org  Mon Apr  1 17:42:30 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17850
	for <sipping-archive@odin.ietf.org>; Mon, 1 Apr 2002 17:42:30 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA17687
	for sipping-archive@odin.ietf.org; Mon, 1 Apr 2002 17:42:33 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA17355;
	Mon, 1 Apr 2002 17:34:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA17328
	for <sipping@optimus.ietf.org>; Mon, 1 Apr 2002 17:34:22 -0500 (EST)
Received: from mail1.dynamicsoft.com (mail1.dynamicsoft.com [63.113.40.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17508
	for <sipping@ietf.org>; Mon, 1 Apr 2002 17:34:18 -0500 (EST)
Received: from DYN-EXCH-001.dynamicsoft.com (dyn-exch-001 [63.113.44.7])
	by mail1.dynamicsoft.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id g31MVVe8008758;
	Mon, 1 Apr 2002 17:31:32 -0500 (EST)
Received: by DYN-EXCH-001.dynamicsoft.com with Internet Mail Service (5.5.2653.19)
	id <H8SJ2YFM>; Mon, 1 Apr 2002 17:33:50 -0500
Message-ID: <9BF66EBF6BEFD942915B4D4D45C051F36301AF@DYN-TX-EXCH-001.dynamicsoft.com>
From: Adam Roach <adam@dynamicsoft.com>
To: "'Romel Khan'" <rkhan@net2phone.com>,
        "'Michael Hammer'"
	 <mhammer@cisco.com>
Cc: sipping@ietf.org,
        "'jon.peterson@neustar.biz'"
	 <jon.peterson@neustar.biz>
Subject: RE: [Sipping] Question on ISUP to SIP mapping draft
Date: Mon, 1 Apr 2002 17:33:42 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

> Some SIP nodes will get rid of the ISUP body.

Has anyone around here mentioned that B2BUAs aren't usually a good
idea lately?

> Moreover,
> looks like most switches today will not look at the ISUP body 
> in SIP msg to
> interwork to ISUP.

...but any node that isn't using our draft for ISUP mapping
won't magically start using the tables in our document after
we fix them. They chose their own mapping.

> Is there any particular hindrance towards making a relevant 
> bunch of these
> SIP Status code to/from ISUP cause code bidirectional 
> interworking (using
> sec 6.2.4.1 as starting base)? If I were to be able to vote I 
> would request
> bidirectional whereever possible.

Your request isn't unreasonable, although it is of limited benefit
(it only makes sense when you'll be transiting from PSTN through a SIP
network, going through B2BUAs, and terminating in another PSTN network;
even then won't preserve cause codes except in certain isolated cases).

In general, the cause code mapping has been the most controversial
section of the document to date, with most codes provoking multiple,
conflicting suggestions about what mapping makes the most sense. By
doing a wholesale remapping of the codes to meet your criteria, we
will probably open up a whole slew of arguments about which mappings
are most appropriate. If that's something Jon has the bandwidth to
deal with, great -- but I suspect it's a bit too much work for
a very minor improvement.

/a

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



From daemon@ns.ietf.org  Tue Apr  2 17:42:29 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06513
	for <sipping-archive@odin.ietf.org>; Tue, 2 Apr 2002 17:42:28 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA19550
	for sipping-archive@odin.ietf.org; Tue, 2 Apr 2002 17:42:31 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA18385;
	Tue, 2 Apr 2002 17:29:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA18354
	for <sipping@ns.ietf.org>; Tue, 2 Apr 2002 17:29:50 -0500 (EST)
Received: from chiron.nge.isi.edu (chiron.nge.isi.edu [65.114.169.204])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06011
	for <sipping@ietf.org>; Tue, 2 Apr 2002 17:29:47 -0500 (EST)
Received: from chiron (csp@localhost)
	by chiron.nge.isi.edu (8.11.6/8.11.6) with ESMTP id g32MTmn09590;
	Tue, 2 Apr 2002 17:29:48 -0500
Message-Id: <200204022229.g32MTmn09590@chiron.nge.isi.edu>
To: Xiaotao Wu <xiaotaow@cs.columbia.edu>
cc: Prashant Gupta <pgupta@unity.ncsu.edu>, sipping@ietf.org
Subject: Re: [Sipping] Re: Queries/Suggestions on draft-wu-sipping-floor-control-00.txt 
In-Reply-To: Your message of "Sat, 30 Mar 2002 10:55:44 EST."
             <Pine.SOL.4.33.0203301016060.12696-100000@ind.cs.columbia.edu> 
Date: Tue, 02 Apr 2002 17:29:48 -0500
From: Colin Perkins <csp@isi.edu>
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

--> Xiaotao Wu writes:
>On Fri, 29 Mar 2002, Prashant Gupta wrote:
>
>> Hi,
>>
>> Thank you for your detailed reply.
>>
>> Does the proposed usage of a=type:moderated for each m line, go against
>> the definition of the "a=type:" semantic, which, as per
>> draft-ietf-mmusic-sdp-new-06.txt (page 26) says that this is a conference
>> level attribute ?
>
>You are right. The type attribute is defined as session-level attribute in
>SDP. I think it is a bug in SDP.

I disagree. See my response to your message on the mmusic mailing list for
details.

Colin

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



From daemon@ns.ietf.org  Wed Apr  3 07:34:43 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00837
	for <sipping-archive@odin.ietf.org>; Wed, 3 Apr 2002 07:34:41 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA19423
	for sipping-archive@odin.ietf.org; Wed, 3 Apr 2002 07:34:44 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18072;
	Wed, 3 Apr 2002 07:26:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA18041
	for <sipping@ns.ietf.org>; Wed, 3 Apr 2002 07:26:31 -0500 (EST)
Received: from hindon.hss.co.in ([202.54.26.202])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00612
	for <sipping@ietf.org>; Wed, 3 Apr 2002 07:26:26 -0500 (EST)
From: nagrawala@hss.hns.com
Received: from sandesh.hss.hns.com (sandesh [139.85.242.35])
	by hindon.hss.co.in (8.10.0/8.10.0) with SMTP id g33CR5316707
	for <sipping@ietf.org>; Wed, 3 Apr 2002 17:57:05 +0530 (IST)
Received: by sandesh.hss.hns.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 65256B90.00441F08 ; Wed, 3 Apr 2002 17:54:03 +0530
X-Lotus-FromDomain: HSS
To: sipping@ietf.org
Message-ID: <65256B90.00441D4F.00@sandesh.hss.hns.com>
Date: Wed, 3 Apr 2002 17:56:07 +0530
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: [Sipping] Re: BYE from server side
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org








Naresh K Agrawala
04/03/2002 06:52 PM

To:   sipping@ietf.org
cc:

Subject:  BYE from server side

Hi,
 the scenario is like this.
Suppose an UAC sends an Cseq with 1 INVITE & call is established.
Now from another side  BYE is received with Cseq  1 BYE. what should be the
behaiour of UAC?

Another case is:
Gateway( MGC) receives an INVITE with Cseq as 5 INVITE and call is established.
Now when the callee releases the call, what should be the Cseq in the BYE sent
from the gateway?

Thanks & Regards,
 naresh





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



From daemon@ns.ietf.org  Wed Apr  3 11:23:42 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08047
	for <sipping-archive@odin.ietf.org>; Wed, 3 Apr 2002 11:23:37 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA06611
	for sipping-archive@odin.ietf.org; Wed, 3 Apr 2002 11:23:40 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04554;
	Wed, 3 Apr 2002 10:56:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04523
	for <sipping@ns.ietf.org>; Wed, 3 Apr 2002 10:56:00 -0500 (EST)
Received: from wiprom2mx1.wipro.com (wiprom2mx1.wipro.com [203.197.164.41])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07256
	for <Sipping@ietf.org>; Wed, 3 Apr 2002 10:55:43 -0500 (EST)
Received: from m2vwall2.wipro.com (m2vwall2.wipro.com [164.164.29.236])
	by wiprom2mx1.wipro.com (8.11.3/8.11.3) with SMTP id g33FtGG15216
	for <Sipping@ietf.org>; Wed, 3 Apr 2002 21:25:16 +0530 (IST)
Received: from Shom ([10.117.2.114]) by kmglmail.mail.wipro.com
          (Netscape Messaging Server 4.15) with ESMTP id GU01JX00.2OU for
          <Sipping@ietf.org>; Wed, 3 Apr 2002 21:25:09 +0530 
Reply-To: <soumendu.ghara@wipro.com>
From: "SOUMENDU GHARA" <soumendu.ghara@wipro.com>
To: <Sipping@ietf.org>
Date: Wed, 3 Apr 2002 21:25:09 +0530
Organization: wipro
Message-ID: <01d001c1db27$ef165430$7202750a@wipro.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-647cd860-4715-11d6-af80-0080c8048dde"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
Subject: [Sipping] Isup to sip mapping
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

This is a multi-part message in MIME format.

------=_NextPartTM-000-647cd860-4715-11d6-af80-0080c8048dde
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_01D1_01C1DB56.08CE9030"

------=_NextPart_000_01D1_01C1DB56.08CE9030
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,
Do we have a doc which talks about how to map a ISUP APM message to
SIP-T. How should be the handling of the segmented APM.
Regards,

Soumendu Ghara
Next Generation Networks
JSLEE Development Team
Office: 91+80+5538301 extn: 2210/2753
~ I am ready to meet my Maker. Whether my Maker is prepared for the
great ordeal of meeting me is another matter - Winston Churchill


------=_NextPart_000_01D1_01C1DB56.08CE9030
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4630.0">
<TITLE>Isup to sip mapping</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT COLOR=3D"#008080" SIZE=3D2 FACE=3D"Century Gothic">Hi,</FONT>

<BR><FONT COLOR=3D"#008080" SIZE=3D2 FACE=3D"Century Gothic">Do we have =
a doc which talks about how to map a ISUP APM message to SIP-T. How =
should be the handling of the segmented APM.</FONT></P>

<P><FONT COLOR=3D"#008080" SIZE=3D2 FACE=3D"Century =
Gothic">Regards,</FONT>
</P>

<P><FONT COLOR=3D"#008080" SIZE=3D4 FACE=3D"Comic Sans MS">Soumendu =
Ghara</FONT>

<BR><FONT COLOR=3D"#808000" SIZE=3D2 FACE=3D"Comic Sans MS">Next =
Generation Networks</FONT>

<BR><FONT COLOR=3D"#800080" SIZE=3D2 FACE=3D"Comic Sans MS">JSLEE =
Development Team</FONT><BR>
<FONT COLOR=3D"#800080" SIZE=3D2 FACE=3D"Comic Sans =
MS">Office:</FONT><FONT COLOR=3D"#008080" SIZE=3D2 FACE=3D"Comic Sans =
MS"> 91+80+5538301</FONT> <FONT COLOR=3D"#800080" SIZE=3D2 FACE=3D"Comic =
Sans MS">extn:</FONT><FONT COLOR=3D"#008080" SIZE=3D2 FACE=3D"Comic Sans =
MS"> 2210/2753</FONT>

<BR><FONT COLOR=3D"#808080" SIZE=3D2 FACE=3D"Comic Sans MS">~ I am ready =
to meet my Maker. Whether my Maker is prepared for the great ordeal of =
meeting me is another matter - Winston Churchill</FONT></P>

</BODY>
</HTML>
------=_NextPart_000_01D1_01C1DB56.08CE9030--



------=_NextPartTM-000-647cd860-4715-11d6-af80-0080c8048dde
Content-Type: text/plain;
	name="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

**************************Disclaimer************************************
Information contained in this E-MAIL being proprietary to Wipro Limited
is 'privileged' and 'confidential' and intended for use only by the
individual or entity to which it is addressed. You are notified that any
use, copying or dissemination of the information contained in the E-MAIL
in any manner whatsoever is strictly prohibited.
********************************************************************

------=_NextPartTM-000-647cd860-4715-11d6-af80-0080c8048dde--


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



From daemon@ns.ietf.org  Wed Apr  3 14:06:33 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12469
	for <sipping-archive@odin.ietf.org>; Wed, 3 Apr 2002 14:06:33 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA19548
	for sipping-archive@odin.ietf.org; Wed, 3 Apr 2002 14:06:35 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA18061;
	Wed, 3 Apr 2002 13:52:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA18034
	for <sipping@ns.ietf.org>; Wed, 3 Apr 2002 13:52:04 -0500 (EST)
Received: from zrc2s0jx.nortelnetworks.com (zrc2s0jx.nortelnetworks.com [47.103.122.112])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12029
	for <sipping@ietf.org>; Wed, 3 Apr 2002 13:52:01 -0500 (EST)
Received: from zrc2c011.us.nortel.com (zrc2c011.us.nortel.com [47.103.120.51])
	by zrc2s0jx.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g33IpUe12871
	for <sipping@ietf.org>; Wed, 3 Apr 2002 12:51:30 -0600 (CST)
Received: by zrc2c011.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <G6V0GDGM>; Wed, 3 Apr 2002 12:51:32 -0600
Message-ID: <933FADF5E673D411B8A30002A5608A0E01187A2C@zrc2c012.us.nortel.com>
From: "Sanjoy Sen"<sanjoy@nortelnetworks.com>
To: sipping@ietf.org
Date: Wed, 3 Apr 2002 12:51:32 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1DB40.92544270"
Subject: [Sipping] SIP & T.120
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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


Is there any ongoing work or planned work in the WG to integrate SIP and
T.120/whiteboarding ?  Is this the right place for this work or should this
be handled at MMUSIC?

The fundamental issues that come to mind : 
1) T.120 family does everything from capability negotiation (T.121), session
set-up (T.122), to conference control (T.124). Should we, for simplicity's
sake, use SIP just to set-up transport for T.120 and leave everything else
for T.120 to handle? This makes some sense given the wide deployment of
complete T.120 stacks. However, there're lot of overlap between the Generic
Conferencing Model (T.124) and SIP conferencing models and framework, and
their interactions need to be sorted out (e.g., Join). What're some of the
new SDP attributes that need to be defined?

2) The alternative is, of course, to recreate "whiteboarding" using SDP &
SIP conferencing models. Is anybody aware of any ongoing work in other
bodies (e.g., W3C)?

What is the general opinion of the WG on starting some work on this?

Thanks,

Sanjoy
sanjoy@nortelnetworks.com


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>SIP &amp; T.120</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Is there any ongoing work or planned =
work in the WG to integrate SIP and T.120/whiteboarding ?&nbsp; Is this =
the right place for this work or should this be handled at =
MMUSIC?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The fundamental issues that come to =
mind : </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">1) T.120 family does everything from =
capability negotiation (T.121), session set-up (T.122), to conference =
control (T.124). Should we, for simplicity's sake, use SIP just to =
set-up transport for T.120 and leave everything else for T.120 to =
handle? This makes some sense given the wide deployment of complete =
T.120 stacks. However, there're lot of overlap between the Generic =
Conferencing Model (T.124) and SIP conferencing models and framework, =
and their interactions need to be sorted out (e.g., Join). What're some =
of the new SDP attributes that need to be defined?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">2) The alternative is, of course, to =
recreate &quot;whiteboarding&quot; using SDP &amp; SIP conferencing =
models. Is anybody aware of any ongoing work in other bodies (e.g., =
W3C)?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">What is the general opinion of the WG =
on starting some work on this?</FONT>
</P>

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

<P><FONT SIZE=3D2 FACE=3D"Arial">Sanjoy</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">sanjoy@nortelnetworks.com</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1DB40.92544270--

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



From daemon@ns.ietf.org  Wed Apr  3 14:17:50 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12772
	for <sipping-archive@odin.ietf.org>; Wed, 3 Apr 2002 14:17:49 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA20171
	for sipping-archive@odin.ietf.org; Wed, 3 Apr 2002 14:17:52 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA19193;
	Wed, 3 Apr 2002 14:02:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA19163
	for <sipping@ns.ietf.org>; Wed, 3 Apr 2002 14:02:54 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12318
	for <Sipping@ietf.org>; Wed, 3 Apr 2002 14:02:51 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g33J2Li25381
	for <Sipping@ietf.org>; Wed, 3 Apr 2002 14:02:21 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <H63LAA64>; Wed, 3 Apr 2002 14:02:23 -0500
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A245@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'soumendu.ghara@wipro.com'" <soumendu.ghara@wipro.com>, Sipping@ietf.org
Subject: RE: [Sipping] Isup to sip mapping
Date: Wed, 3 Apr 2002 14:02:20 -0500 
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


That will be covered in current work on SIP-BICC interworking in ITU-T SG
11.

-----Original Message-----
From: SOUMENDU GHARA [mailto:soumendu.ghara@wipro.com]
Sent: Wednesday, April 03, 2002 10:55 AM
To: Sipping@ietf.org
Subject: [Sipping] Isup to sip mapping


Hi, 
Do we have a doc which talks about how to map a ISUP APM message to SIP-T.
How should be the handling of the segmented APM.
Regards, 
Soumendu Ghara 
Next Generation Networks 
JSLEE Development Team
Office: 91+80+5538301 extn: 2210/2753 
~ I am ready to meet my Maker. Whether my Maker is prepared for the great
ordeal of meeting me is another matter - Winston Churchill

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



From daemon@optimus.ietf.org  Thu Apr  4 06:29:46 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09904
	for <sipping-archive@odin.ietf.org>; Thu, 4 Apr 2002 06:29:45 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA22598
	for sipping-archive@odin.ietf.org; Thu, 4 Apr 2002 06:29:47 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA21854;
	Thu, 4 Apr 2002 06:12:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA21826
	for <sipping@optimus.ietf.org>; Thu, 4 Apr 2002 06:12:51 -0500 (EST)
Received: from accord-ntsrv3.accord-domain ([212.199.61.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09648
	for <sipping@ietf.org>; Thu, 4 Apr 2002 06:12:46 -0500 (EST)
Received: by ACCORD-NTSRV3 with Internet Mail Service (5.5.2653.19)
	id <FSC8PRGV>; Thu, 4 Apr 2002 14:12:31 +0300
Message-ID: <B2518D608282D511BEA400508BBB9148EA9E48@ACCORD-NTSRV3>
From: "Even, Roni" <roni.even@polycom.co.il>
To: "'Sanjoy Sen'" <sanjoy@nortelnetworks.com>, sipping@ietf.org
Subject: RE: [Sipping] SIP & T.120
Date: Thu, 4 Apr 2002 14:12:30 +0300 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1DBC9.9CB631E0"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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_01C1DBC9.9CB631E0
Content-Type: text/plain;
	charset="ISO-8859-1"

Sanjoy,
 
The issue of integrating SIP and T.120 was mentioned in draft-levin-sip-for
-video. the work is continued after the Minneapolis meeting by a group that
tries to define the requirements and framework for multimedia conferencing.
Using T.120 for control was discussed in the initial phases of H.323 and was
not accepted due to the complexity of T.120 as well as the low availability
of a stack. I would argue your point of wide deployment. It is true that
Netmeeting is a T.120 client but if you want a stack for an embedded
platform you have a problem. Databeam who used to be the major vendor of
such stack does not do it this days.
As for data collaboration there is no other protocol and I think that the
industry would welcome such a protocol. Today you can see web collaboration
applications but they do not have full application sharing capabilities.
Roni Even
Polycom

-----Original Message-----
From: Sanjoy Sen [mailto:sanjoy@nortelnetworks.com]
Sent: Wednesday, April 03, 2002 9:52 PM
To: sipping@ietf.org
Subject: [Sipping] SIP & T.120




Is there any ongoing work or planned work in the WG to integrate SIP and
T.120/whiteboarding ?  Is this the right place for this work or should this
be handled at MMUSIC?

The fundamental issues that come to mind : 
1) T.120 family does everything from capability negotiation (T.121), session
set-up (T.122), to conference control (T.124). Should we, for simplicity's
sake, use SIP just to set-up transport for T.120 and leave everything else
for T.120 to handle? This makes some sense given the wide deployment of
complete T.120 stacks. However, there're lot of overlap between the Generic
Conferencing Model (T.124) and SIP conferencing models and framework, and
their interactions need to be sorted out (e.g., Join). What're some of the
new SDP attributes that need to be defined?

2) The alternative is, of course, to recreate "whiteboarding" using SDP &
SIP conferencing models. Is anybody aware of any ongoing work in other
bodies (e.g., W3C)?

What is the general opinion of the WG on starting some work on this? 

Thanks, 

Sanjoy 
sanjoy@nortelnetworks.com 


------_=_NextPart_001_01C1DBC9.9CB631E0
Content-Type: text/html;
	charset="ISO-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<TITLE>SIP & T.120</TITLE>

<META content="MSHTML 6.00.2600.0" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=928080311-04042002><FONT face=Arial color=#0000ff 
size=2>Sanjoy,</FONT></SPAN></DIV>
<DIV><SPAN class=928080311-04042002><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=928080311-04042002><FONT face=Arial color=#0000ff size=2>The 
issue of integrating SIP and T.120 was mentioned in draft-levin-sip-for -video. 
the work is continued after the Minneapolis meeting by a group that tries to 
define the requirements and framework for multimedia 
conferencing.</FONT></SPAN></DIV>
<DIV><SPAN class=928080311-04042002><FONT face=Arial color=#0000ff size=2>Using 
T.120 for control was discussed in the initial phases of H.323 and was not 
accepted due to the complexity of T.120 as well as the low availability of a 
stack. I would argue your point of wide deployment. It is true that Netmeeting 
is a T.120 client but if you want a stack for an embedded platform you have a 
problem. Databeam who used to be the major vendor of such stack does not do it 
this days.</FONT></SPAN></DIV>
<DIV><SPAN class=928080311-04042002><FONT face=Arial color=#0000ff size=2>As for 
data collaboration there is no other protocol and I think that the industry 
would welcome such a protocol. Today you can see web collaboration applications 
but they do not have full application sharing capabilities.</FONT></SPAN></DIV>
<DIV><SPAN class=928080311-04042002><FONT face=Arial color=#0000ff size=2>Roni 
Even</FONT></SPAN></DIV>
<DIV><SPAN class=928080311-04042002><FONT face=Arial color=#0000ff 
size=2>Polycom</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Sanjoy Sen 
  [mailto:sanjoy@nortelnetworks.com]<BR><B>Sent:</B> Wednesday, April 03, 2002 
  9:52 PM<BR><B>To:</B> sipping@ietf.org<BR><B>Subject:</B> [Sipping] SIP &amp; 
  T.120<BR><BR></FONT></DIV><BR>
  <P><FONT face=Arial size=2>Is there any ongoing work or planned work in the WG 
  to integrate SIP and T.120/whiteboarding ?&nbsp; Is this the right place for 
  this work or should this be handled at MMUSIC?</FONT></P>
  <P><FONT face=Arial size=2>The fundamental issues that come to mind : 
  </FONT><BR><FONT face=Arial size=2>1) T.120 family does everything from 
  capability negotiation (T.121), session set-up (T.122), to conference control 
  (T.124). Should we, for simplicity's sake, use SIP just to set-up transport 
  for T.120 and leave everything else for T.120 to handle? This makes some sense 
  given the wide deployment of complete T.120 stacks. However, there're lot of 
  overlap between the Generic Conferencing Model (T.124) and SIP conferencing 
  models and framework, and their interactions need to be sorted out (e.g., 
  Join). What're some of the new SDP attributes that need to be 
  defined?</FONT></P>
  <P><FONT face=Arial size=2>2) The alternative is, of course, to recreate 
  "whiteboarding" using SDP &amp; SIP conferencing models. Is anybody aware of 
  any ongoing work in other bodies (e.g., W3C)?</FONT></P>
  <P><FONT face=Arial size=2>What is the general opinion of the WG on starting 
  some work on this?</FONT> </P>
  <P><FONT face=Arial size=2>Thanks,</FONT> </P>
  <P><FONT face=Arial size=2>Sanjoy</FONT> <BR><FONT face=Arial 
  size=2>sanjoy@nortelnetworks.com</FONT> </P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1DBC9.9CB631E0--

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



From daemon@optimus.ietf.org  Thu Apr  4 12:18:12 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23912
	for <sipping-archive@odin.ietf.org>; Thu, 4 Apr 2002 12:18:12 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA17542
	for sipping-archive@odin.ietf.org; Thu, 4 Apr 2002 12:18:15 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA16584;
	Thu, 4 Apr 2002 12:04:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA16546
	for <sipping@optimus.ietf.org>; Thu, 4 Apr 2002 12:04:50 -0500 (EST)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23132;
	Thu, 4 Apr 2002 12:04:46 -0500 (EST)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-2.cisco.com (8.12.2/8.12.2) with ESMTP id g34H4JON027477;
	Thu, 4 Apr 2002 09:04:19 -0800 (PST)
Received: from localhost (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint)
	with ESMTP id ACT91521;
	Thu, 4 Apr 2002 09:04:18 -0800 (PST)
Date: Thu, 4 Apr 2002 09:01:41 -0800 (Pacific Standard Time)
From: Rohan Mahy <rohan@cisco.com>
To: sipping@ietf.org, <sip@ietf.org>
Message-ID: <Pine.WNT.4.44.0204040850400.-394077@chorizo.rapidconvergence.com>
X-X-Sender: rmahy@imop.cisco.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Sipping] Poll for interest in an interim SIP/SIPPING meeting
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Hi,

I've heard from some folks that they would like to have another interim
SIP/SIPPING meeting like we did in Dallas between IETF 49 and 50.  I'd
like to here from folks *privately* please if they are interested in such
an interim meeting, probably during the month of May.  Also if you are
strongly opposed to such a meeting, I would like to hear from you
*privately* as well.

As for the possible locations, I am currently entertaining both Flagstaff,
Arizona, and Boston.  I can get a very good room rate for one, and the
other is easier for most folks to get to.  If you send me *private* mail
in support of an interim meeting, your location suggestion is also appreciated.

As always, any interim meeting has to be announced on ietf-announce at
least 30 days before the meeting, so please get me your comments early.
For your convenience, you can just click on the apropriate link.

Yes Reply:  mailto:rohan@cisco.com?Subject=[sip-interim-yes]

No  Reply:  mailto:rohan@cisco.com?Subject=[sip-interim-no]

thanks,
-rohan


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



From daemon@optimus.ietf.org  Thu Apr  4 16:10:00 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08885
	for <sipping-archive@odin.ietf.org>; Thu, 4 Apr 2002 16:10:00 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA02413
	for sipping-archive@odin.ietf.org; Thu, 4 Apr 2002 16:10:03 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA01250;
	Thu, 4 Apr 2002 15:51:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA01222
	for <sipping@optimus.ietf.org>; Thu, 4 Apr 2002 15:51:29 -0500 (EST)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08303
	for <sipping@ietf.org>; Thu, 4 Apr 2002 15:51:25 -0500 (EST)
Received: from cia.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id g34KpJ400323;
	Thu, 4 Apr 2002 15:51:19 -0500 (EST)
Received: from MHAMMER-W2K.cisco.com (hrn2-dhcp-161-44-87-145.cisco.com [161.44.87.145])
	by cia.cisco.com (Mirapoint)
	with ESMTP id AAT28181;
	Thu, 4 Apr 2002 15:45:52 -0500 (EST)
Message-Id: <4.3.2.7.2.20020404154313.00b1dc20@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 04 Apr 2002 15:50:55 -0500
To: james.yu@neustar.biz
From: Michael Hammer <mhammer@cisco.com>
Subject: [Sipping] draft-yu-tel-url-04.txt comment
Cc: sipping@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

James,

Section 6: npdi-ident = "yes" | "no"
Yet, section 7.3, example 1: "npdi=yes@sip.abc,com"

Would that be rejected or truncated?

Also, cic-ident = *phonedigit
Section 7.3, example 2: "cic=+1-6789@sip.xyz.com"

Does phonedigit include all alphanumeric?

Mike


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



From daemon@optimus.ietf.org  Thu Apr  4 18:46:24 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12936
	for <sipping-archive@odin.ietf.org>; Thu, 4 Apr 2002 18:46:24 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA11530
	for sipping-archive@odin.ietf.org; Thu, 4 Apr 2002 18:46:29 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA11064;
	Thu, 4 Apr 2002 18:37:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA11009
	for <sipping@optimus.ietf.org>; Thu, 4 Apr 2002 18:36:56 -0500 (EST)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12755;
	Thu, 4 Apr 2002 18:36:50 -0500 (EST)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g34NaOq6002737;
	Thu, 4 Apr 2002 15:36:24 -0800 (PST)
Received: from dhcp-128-107-142-216.cisco.com (dhcp-128-107-142-216.cisco.com [128.107.142.216])
	by imop.cisco.com (Mirapoint)
	with ESMTP id ACU02659;
	Thu, 4 Apr 2002 15:36:23 -0800 (PST)
Date: Thu, 4 Apr 2002 15:33:47 -0800 (Pacific Standard Time)
From: Rohan Mahy <rohan@cisco.com>
To: sip@ietf.org, <sipping@ietf.org>
Message-ID: <Pine.WNT.4.44.0204041523430.-517107@chorizo.rapidconvergence.com>
X-X-Sender: rmahy@imop.cisco.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Sipping] possible agenda/motivation for interim meeting
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Hi,

A couple folks have asked for my motivation for suggesting an interim.
Basically we've got a lot of stuff on our plate in both WGs, and much of
it is in that midway done phase were face time is most valuable.
An interim would give us time to resolve several sticky technical issues
and then get drafts out before the cutoff date for IETF54.  I think
we could have a much more productive meeting in Japan as a result.

Topics in serious need of face time:

- the longer term privacy solution
- a whole raft of security issues
- REFER, replaces, and cc-transfer
- call info and conf info packages
- multiparty and conferencing requirements/frameworks
- possibly more ISUP interworking issues
- possibly a working session to revise the AAA requirements draft

The last two would depend on critical mass of folks willing to work on
these.

thanks,
-rohan



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



From daemon@optimus.ietf.org  Thu Apr  4 19:59:26 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14335
	for <sipping-archive@odin.ietf.org>; Thu, 4 Apr 2002 19:59:26 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA15263
	for sipping-archive@odin.ietf.org; Thu, 4 Apr 2002 19:59:29 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA15046;
	Thu, 4 Apr 2002 19:51:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA15016
	for <sipping@optimus.ietf.org>; Thu, 4 Apr 2002 19:51:46 -0500 (EST)
Received: from broadsoft.com (broadsoft.com [198.104.184.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14261
	for <sipping@ietf.org>; Thu, 4 Apr 2002 19:51:43 -0500 (EST)
Received: from tate (host4.brodsoft.com [66.160.10.4] (may be forged)) by broadsoft.com (8.11.6) id g350pgk73541; Thu, 4 Apr 2002 19:51:42 -0500 (EST)
Reply-To: <brett@broadsoft.com>
From: "Brett Tate" <brett@broadsoft.com>
To: "'Michael Hammer'" <mhammer@cisco.com>
Cc: <sipping@ietf.org>
Subject: RE: [Sipping] draft-yu-tel-url-04.txt comment
Date: Thu, 4 Apr 2002 19:55:40 -0500
Message-ID: <002201c1dc3c$9bfef390$2b01a8c0@broadsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <4.3.2.7.2.20020404154313.00b1dc20@cia.cisco.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

> Section 6: npdi-ident = "yes" | "no"
> Yet, section 7.3, example 1: "npdi=yes@sip.abc,com"
> 
> Would that be rejected or truncated?

The '@' represents the end of the 
telephone-subscriber part of the sip-url.

Thus the npdi has a value of yes.

> Also, cic-ident = *phonedigit
> Section 7.3, example 2: "cic=+1-6789@sip.xyz.com"
> 
> Does phonedigit include all alphanumeric?

The '@' represents the end of the 
telephone-subscriber part of the sip-url.

Thus the cic-ident has a value of +1-6789.


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



From daemon@optimus.ietf.org  Fri Apr  5 10:05:19 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06720
	for <sipping-archive@odin.ietf.org>; Fri, 5 Apr 2002 10:05:19 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA05216
	for sipping-archive@odin.ietf.org; Fri, 5 Apr 2002 10:05:24 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA04265;
	Fri, 5 Apr 2002 09:53:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA28769
	for <sipping@optimus.ietf.org>; Fri, 5 Apr 2002 08:04:40 -0500 (EST)
Received: from mail1.telekom.de (mail1.telekom.de [62.225.183.235])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03521
	for <sipping@ietf.org>; Fri, 5 Apr 2002 08:04:35 -0500 (EST)
Received: from g9jbr.mgb01.telekom.de by G8SBV.dmz.telekom.de with ESMTP for sipping@ietf.org; Fri, 5 Apr 2002 15:02:46 +0200
Received: by G9JBR.mgb01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <1Z4M7P93>; Fri, 5 Apr 2002 15:04:06 +0200
Message-Id: <C3F9C806AEC6D5119643000347055E322088B7@G9JNW.mgb01.telekom.de>
From: "Beck01, Wolfgang" <BeckW@t-systems.com>
To: sipping@ietf.org
Date: Fri, 5 Apr 2002 15:04:05 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Subject: [Sipping] SIP billing service, new draft-beck-sipping-billing-scen-00.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


During the Minneapolis meeting an idea came up to use SIP
to invoke billable services ("SIP = Service Invoice Protocol").
The draft
http://www.ietf.org/internet-drafts/draft-beck-sippping-billing-scen-00.txt
outlines some scenarios, security considerations and mechanisms.

What is a billable service?

-  a PSTN gateway?
-  a non-free support hotline?
-  accepting SIP calls from obtrusive salespeople?
-  accepting RTP traffic that will show up on the bill of my volume-based
IP access?

Extra header(s) are needed to convey pricing information and to protect callers.

CPL could be extended in a way that enables users to individually charge
callers. 

Non-repudiation is an issue here. 

Comments?




--
Wolfgang Beck
T-Systems Nova GmbH 


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



From daemon@optimus.ietf.org  Fri Apr  5 10:30:19 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07456
	for <sipping-archive@odin.ietf.org>; Fri, 5 Apr 2002 10:30:19 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA07199
	for sipping-archive@odin.ietf.org; Fri, 5 Apr 2002 10:30:24 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA05823;
	Fri, 5 Apr 2002 10:13:52 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA05790
	for <sipping@optimus.ietf.org>; Fri, 5 Apr 2002 10:13:48 -0500 (EST)
Received: from gbnewp0915s1.eu.ubiquity.net (news.ubiquity.net [194.202.146.92])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA06975
	for <sipping@ietf.org>; Fri, 5 Apr 2002 10:13:41 -0500 (EST)
Received: from mailhost.eu.ubiquity.net by gbnewp0915s1.eu.ubiquity.net
          via smtpd (for odin.ietf.org [132.151.1.176]) with SMTP; 5 Apr 2002 15:14:06 UT
content-class: urn:content-classes:message
Subject: RE: [Sipping] SIP billing service, new draft-beck-sipping-billing-scen-00.txt
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Date: Fri, 5 Apr 2002 16:13:16 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
Message-ID: <45730E094814E44488F789C1CDED27AEC552D9@GBNEWP0758M.eu.ubiquity.net>
Thread-Topic: [Sipping] SIP billing service, new draft-beck-sipping-billing-scen-00.txt
Thread-Index: AcHcsc8+qFggP7T3TZeuvvrtIp5e1AAAJnqA
From: "James Undery" <jundery@ubiquity.net>
To: "Beck01, Wolfgang" <BeckW@t-systems.com>, <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id KAA05791
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 8bit

Hi,

I've a large number of problems with this draft, mainly it isn't a set
of requirements ;-). The scenarios miss a large number of obvious
attacks, using route to generate 200s to BYEs, both parties colluding to
defraud (by creating asymetry in timings of two BSPs; assuming a global
BSP is logistically infeasible), callee taking caller to his cost limit
every time and a host of others things no doubt.

However, it should be noted as I am biased and don't believe you can
bill for any resource you don't directly control. A corollary of this
belief is, in order to bill on the call duration you must be call
stateful.

James

> -----Original Message-----
> From: Beck01, Wolfgang [mailto:BeckW@t-systems.com]

 
> During the Minneapolis meeting an idea came up to use SIP
> to invoke billable services ("SIP = Service Invoice Protocol").
> The draft
> http://www.ietf.org/internet-drafts/draft-beck-sippping-billin
> g-scen-00.txt
> outlines some scenarios, security considerations and mechanisms.
> 
> What is a billable service?
> 
> -  a PSTN gateway?
> -  a non-free support hotline?
> -  accepting SIP calls from obtrusive salespeople?
> -  accepting RTP traffic that will show up on the bill of my 
> volume-based
> IP access?
> 
> Extra header(s) are needed to convey pricing information and 
> to protect callers.
> 
> CPL could be extended in a way that enables users to 
> individually charge
> callers. 
> 
> Non-repudiation is an issue here. 
> 
> Comments?
> 
> 
> 
> 
> --
> Wolfgang Beck
> T-Systems Nova GmbH 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 daemon@optimus.ietf.org  Fri Apr  5 20:41:49 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17042
	for <sipping-archive@odin.ietf.org>; Fri, 5 Apr 2002 20:41:49 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA11678
	for sipping-archive@odin.ietf.org; Fri, 5 Apr 2002 20:41:42 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA11369;
	Fri, 5 Apr 2002 20:34:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA11338
	for <sipping@optimus.ietf.org>; Fri, 5 Apr 2002 20:34:12 -0500 (EST)
Received: from web11608.mail.yahoo.com (web11608.mail.yahoo.com [216.136.172.60])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA16808
	for <sipping@ietf.org>; Fri, 5 Apr 2002 20:34:06 -0500 (EST)
Message-ID: <20020406013410.1461.qmail@web11608.mail.yahoo.com>
Received: from [131.107.3.70] by web11608.mail.yahoo.com via HTTP; Fri, 05 Apr 2002 17:34:10 PST
Date: Fri, 5 Apr 2002 17:34:10 -0800 (PST)
From: Sean Olson <seancolson@yahoo.com>
To: sipping@ietf.org, simple@mailman.dynamicsoft.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Sipping] draft-olson-sipping-content-indirect-00.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

FYI. I've put together a draft of requirements
for a mechanism to allow content indirection
(an indirect reference to content that would normally
be carried directly in the SIP payload)

http://www.ietf.org/internet-drafts/draft-olson-sipping-content-indirect-00.txt

/sean


=====
Sean Olson <seancolson@yahoo.com>

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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



From daemon@ns.ietf.org  Mon Apr  8 10:37:57 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25368
	for <sipping-archive@odin.ietf.org>; Mon, 8 Apr 2002 10:37:57 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA10413
	for sipping-archive@odin.ietf.org; Mon, 8 Apr 2002 10:37:59 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA08019;
	Mon, 8 Apr 2002 10:11:34 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA16409
	for <sipping@optimus.ietf.org>; Mon, 8 Apr 2002 03:48:13 -0400 (EDT)
Received: from mail1.telekom.de (mail1.telekom.de [62.225.183.235])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17225
	for <sipping@ietf.org>; Mon, 8 Apr 2002 03:48:09 -0400 (EDT)
Received: from g9jbr.mgb01.telekom.de by G8SBV.dmz.telekom.de with ESMTP; Mon, 8 Apr 2002 09:46:20 +0200
Received: by G9JBR.mgb01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <1Z4M8N3A>; Mon, 8 Apr 2002 09:47:39 +0200
Message-Id: <C3F9C806AEC6D5119643000347055E322088B8@G9JNW.mgb01.telekom.de>
From: "Beck01, Wolfgang" <BeckW@t-systems.com>
To: jundery@ubiquity.net, sipping@ietf.org
Subject: RE: [Sipping] SIP billing service, new draft-beck-sipping-billing
	-scen-00.txt
Date: Mon, 8 Apr 2002 09:47:37 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

James,
> -----Original Message-----
> From: James Undery [mailto:jundery@ubiquity.net]
>
> [justified criticism about lacking requirements omitted]
> 
> The scenarios miss a large number of obvious
> attacks, using route to generate 200s to BYEs, both parties 
> colluding to
> defraud (by creating asymetry in timings of two BSPs; 
> assuming a global
> BSP is logistically infeasible)
The purpose of the billing service is not to generate call detail records
on behalf of the ITSP or ISP, but on behalf of the callee. If the two parties
don't want to use a billing service, they just call each other directly.

The draft assumes that the parties have an interest to use the BSP's proxies:
- the callee needs a proof that somebody has called
- the caller needs a proof that he didn't call.
The BSP is just a neutral third party.

> 
> However, it should be noted as I am biased and don't believe you can
> bill for any resource you don't directly control. A corollary of this
> belief is, in order to bill on the call duration you must be call
> stateful.
The SIP billing service is stateful in a back-end system that gathers
information (offline?) from its stateless proxies. Do you think call
stateful proxies would be better suited to provide a certain level of
non-repudiation?


--
Wolfgang Beck
T-Systems Nova GmbH 


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



From daemon@ns.ietf.org  Mon Apr  8 10:44:20 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25632
	for <sipping-archive@odin.ietf.org>; Mon, 8 Apr 2002 10:44:19 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA10826
	for sipping-archive@odin.ietf.org; Mon, 8 Apr 2002 10:44:22 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA07860;
	Mon, 8 Apr 2002 10:10:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA07804
	for <sipping@ns.ietf.org>; Mon, 8 Apr 2002 10:10:36 -0400 (EDT)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24325
	for <sipping@ietf.org>; Mon, 8 Apr 2002 10:10:34 -0400 (EDT)
Received: from cannon.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g38EARDX019488;
	Mon, 8 Apr 2002 10:10:28 -0400 (EDT)
Received: from cisco.com (dhcp-161-44-241-140.cisco.com [161.44.241.140])
	by cannon.cisco.com (Mirapoint)
	with ESMTP id AAI02609;
	Mon, 8 Apr 2002 10:13:22 -0400 (EDT)
Message-ID: <3CB1A4BC.8DB70998@cisco.com>
Date: Mon, 08 Apr 2002 10:10:04 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD   (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Sean Olson <seancolson@yahoo.com>
CC: sipping@ietf.org, simple@mailman.dynamicsoft.com
Subject: Re: [Sipping] draft-olson-sipping-content-indirect-00.txt
References: <20020406013410.1461.qmail@web11608.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Sean - comment below.

	Paul

Sean Olson wrote:
> 
> FYI. I've put together a draft of requirements
> for a mechanism to allow content indirection
> (an indirect reference to content that would normally
> be carried directly in the SIP payload)
> 
> http://www.ietf.org/internet-drafts/draft-olson-sipping-content-indirect-00.txt

What is the purpose of REQ-2? 

Since this proposal is about content indirection, it seems like the purpose of the content should be unchanged whether it is indirected or not. Whatever mechanism there is
out to apply equally whether the content is direct or indirect. The Content-Disposition header already serves this purpose.

Perhaps you are trying to say that it should be possible to use several URLs as an alternative to several parts in a multipart-MIME body, and that you want an ability
equivalent to specifying a separate Content-Disposition header for each. That seems reasonable.

But if you are suggesting a need for more forms of disposition than are currently covered by Content-Disposition, then I think that should be handled in a way independent
of content indirection.

	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 daemon@ns.ietf.org  Mon Apr  8 11:05:11 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26310
	for <sipping-archive@odin.ietf.org>; Mon, 8 Apr 2002 11:05:11 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA12673
	for sipping-archive@odin.ietf.org; Mon, 8 Apr 2002 11:05:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA11573;
	Mon, 8 Apr 2002 10:54:04 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA11534
	for <sipping@ns.ietf.org>; Mon, 8 Apr 2002 10:54:00 -0400 (EDT)
Received: from zrc2s0jx.nortelnetworks.com (zrc2s0jx.nortelnetworks.com [47.103.122.112])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25962
	for <sipping@ietf.org>; Mon, 8 Apr 2002 10:53:56 -0400 (EDT)
Received: from zrc2c011.us.nortel.com (zrc2c011.us.nortel.com [47.103.120.51])
	by zrc2s0jx.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g38ErID25199;
	Mon, 8 Apr 2002 09:53:18 -0500 (CDT)
Received: by zrc2c011.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <2JXVK3GP>; Mon, 8 Apr 2002 09:50:42 -0500
Message-ID: <EF1056F8EB4ED511B8FB0002A56079D401E5AFE8@zrc2c014.us.nortel.com>
From: "Sriram Parameswar"<sriramp@nortelnetworks.com>
To: "'Paul Kyzivat'" <pkyzivat@cisco.com>, Sean Olson <seancolson@yahoo.com>
Cc: sipping@ietf.org, simple@mailman.dynamicsoft.com
Subject: RE: [Simple] Re: [Sipping] draft-olson-sipping-content-indirect-0
	0.txt
Date: Mon, 8 Apr 2002 09:50:39 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1DF0C.C00A0BD0"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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

Sean:

Couple of additional comments/requirements:

** Access-Control - control over access to the content either by
authorization mechanisms or others. 
** Access-Control mechanism - this is probably extreme but we could probably
add an access-control mechanism. This should allow for a method of
access-control modification i.e. I gave you permission to see a particular
content - then want to revoke this privilege.

Thanks,

Sriram

__________________________________________
Sriram Parameswar              Phone: 972-685-8540
Interactive Multimedia Server (IMS) Fax: 972-684-3986
Nortel Networks, Richardson USA  Email: sriramp@nortelnetworks.com


-----Original Message-----
From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
Sent: Monday, April 08, 2002 9:10 AM
To: Sean Olson
Cc: sipping@ietf.org; simple@mailman.dynamicsoft.com
Subject: [Simple] Re: [Sipping]
draft-olson-sipping-content-indirect-00.txt


Sean - comment below.

	Paul

Sean Olson wrote:
> 
> FYI. I've put together a draft of requirements
> for a mechanism to allow content indirection
> (an indirect reference to content that would normally
> be carried directly in the SIP payload)
> 
>
http://www.ietf.org/internet-drafts/draft-olson-sipping-content-indirect-00.
txt

What is the purpose of REQ-2? 

Since this proposal is about content indirection, it seems like the purpose
of the content should be unchanged whether it is indirected or not. Whatever
mechanism there is
out to apply equally whether the content is direct or indirect. The
Content-Disposition header already serves this purpose.

Perhaps you are trying to say that it should be possible to use several URLs
as an alternative to several parts in a multipart-MIME body, and that you
want an ability
equivalent to specifying a separate Content-Disposition header for each.
That seems reasonable.

But if you are suggesting a need for more forms of disposition than are
currently covered by Content-Disposition, then I think that should be
handled in a way independent
of content indirection.

	Paul
_______________________________________________
simple mailing list
simple@mailman.dynamicsoft.com
http://mailman.dynamicsoft.com/mailman/listinfo/simple

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Simple] Re: [Sipping] =
draft-olson-sipping-content-indirect-00.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Sean:</FONT>
</P>

<P><FONT SIZE=3D2>Couple of additional comments/requirements:</FONT>
</P>

<P><FONT SIZE=3D2>** Access-Control - control over access to the =
content either by authorization mechanisms or others. </FONT>
<BR><FONT SIZE=3D2>** Access-Control mechanism - this is probably =
extreme but we could probably add an access-control mechanism. This =
should allow for a method of access-control modification i.e. I gave =
you permission to see a particular content - then want to revoke this =
privilege.</FONT></P>

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

<P><FONT SIZE=3D2>Sriram</FONT>
</P>

<P><FONT SIZE=3D2>__________________________________________</FONT>
<BR><FONT SIZE=3D2>Sriram =
Parameswar&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; Phone: 972-685-8540</FONT>
<BR><FONT SIZE=3D2>Interactive Multimedia Server (IMS) Fax: =
972-684-3986</FONT>
<BR><FONT SIZE=3D2>Nortel Networks, Richardson USA&nbsp; Email: =
sriramp@nortelnetworks.com</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Paul Kyzivat [<A =
HREF=3D"mailto:pkyzivat@cisco.com">mailto:pkyzivat@cisco.com</A>]</FONT>=

<BR><FONT SIZE=3D2>Sent: Monday, April 08, 2002 9:10 AM</FONT>
<BR><FONT SIZE=3D2>To: Sean Olson</FONT>
<BR><FONT SIZE=3D2>Cc: sipping@ietf.org; =
simple@mailman.dynamicsoft.com</FONT>
<BR><FONT SIZE=3D2>Subject: [Simple] Re: [Sipping]</FONT>
<BR><FONT SIZE=3D2>draft-olson-sipping-content-indirect-00.txt</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Sean - comment below.</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>Paul</FONT>
</P>

<P><FONT SIZE=3D2>Sean Olson wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; FYI. I've put together a draft of =
requirements</FONT>
<BR><FONT SIZE=3D2>&gt; for a mechanism to allow content =
indirection</FONT>
<BR><FONT SIZE=3D2>&gt; (an indirect reference to content that would =
normally</FONT>
<BR><FONT SIZE=3D2>&gt; be carried directly in the SIP payload)</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-olson-sipping-content-=
indirect-00.txt" =
TARGET=3D"_blank">http://www.ietf.org/internet-drafts/draft-olson-sippin=
g-content-indirect-00.txt</A></FONT>
</P>

<P><FONT SIZE=3D2>What is the purpose of REQ-2? </FONT>
</P>

<P><FONT SIZE=3D2>Since this proposal is about content indirection, it =
seems like the purpose of the content should be unchanged whether it is =
indirected or not. Whatever mechanism there is</FONT></P>

<P><FONT SIZE=3D2>out to apply equally whether the content is direct or =
indirect. The Content-Disposition header already serves this =
purpose.</FONT></P>

<P><FONT SIZE=3D2>Perhaps you are trying to say that it should be =
possible to use several URLs as an alternative to several parts in a =
multipart-MIME body, and that you want an ability</FONT></P>

<P><FONT SIZE=3D2>equivalent to specifying a separate =
Content-Disposition header for each. That seems reasonable.</FONT>
</P>

<P><FONT SIZE=3D2>But if you are suggesting a need for more forms of =
disposition than are currently covered by Content-Disposition, then I =
think that should be handled in a way independent</FONT></P>

<P><FONT SIZE=3D2>of content indirection.</FONT>
</P>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>Paul</FONT>
<BR><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>simple mailing list</FONT>
<BR><FONT SIZE=3D2>simple@mailman.dynamicsoft.com</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.dynamicsoft.com/mailman/listinfo/simple" =
TARGET=3D"_blank">http://mailman.dynamicsoft.com/mailman/listinfo/simple=
</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1DF0C.C00A0BD0--

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



From daemon@ns.ietf.org  Mon Apr  8 13:00:07 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29813
	for <sipping-archive@odin.ietf.org>; Mon, 8 Apr 2002 13:00:07 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA21733
	for sipping-archive@odin.ietf.org; Mon, 8 Apr 2002 13:00:09 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA20908;
	Mon, 8 Apr 2002 12:42:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA20877
	for <sipping@ns.ietf.org>; Mon, 8 Apr 2002 12:42:06 -0400 (EDT)
Received: from web11602.mail.yahoo.com (web11602.mail.yahoo.com [216.136.172.54])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA29457
	for <sipping@ietf.org>; Mon, 8 Apr 2002 12:42:04 -0400 (EDT)
Message-ID: <20020408164205.88765.qmail@web11602.mail.yahoo.com>
Received: from [207.46.137.8] by web11602.mail.yahoo.com via HTTP; Mon, 08 Apr 2002 09:42:05 PDT
Date: Mon, 8 Apr 2002 09:42:05 -0700 (PDT)
From: Sean Olson <seancolson@yahoo.com>
Subject: Re: [Sipping] draft-olson-sipping-content-indirect-00.txt
To: Paul Kyzivat <pkyzivat@cisco.com>
Cc: sipping@ietf.org, simple@mailman.dynamicsoft.com
In-Reply-To: <3CB1A4BC.8DB70998@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


> 
> Perhaps you are trying to say that it should be
> possible to use several URLs as an alternative to
> several parts in a multipart-MIME body, and that you
> want an ability
> equivalent to specifying a separate
> Content-Disposition header for each. That seems
> reasonable.

Exactly. I will make this explicit.

> 
> But if you are suggesting a need for more forms of
> disposition than are currently covered by
> Content-Disposition, then I think that should be
> handled in a way independent
> of content indirection.

I think Content-Disposition could be easily
extended to accommodate what I have in mind.
I will leave those details to a draft that 
proposes an implementation of these requirements.

> 
> 	Paul

Thanks for the comments.
/sean



__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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



From daemon@ns.ietf.org  Mon Apr  8 13:24:26 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00401
	for <sipping-archive@odin.ietf.org>; Mon, 8 Apr 2002 13:24:26 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA23198
	for sipping-archive@odin.ietf.org; Mon, 8 Apr 2002 13:24:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA22371;
	Mon, 8 Apr 2002 13:04:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA22345
	for <sipping@ns.ietf.org>; Mon, 8 Apr 2002 13:04:49 -0400 (EDT)
Received: from web11607.mail.yahoo.com (web11607.mail.yahoo.com [216.136.172.59])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA29970
	for <sipping@ietf.org>; Mon, 8 Apr 2002 13:04:45 -0400 (EDT)
Message-ID: <20020408170447.29119.qmail@web11607.mail.yahoo.com>
Received: from [207.46.137.9] by web11607.mail.yahoo.com via HTTP; Mon, 08 Apr 2002 10:04:47 PDT
Date: Mon, 8 Apr 2002 10:04:47 -0700 (PDT)
From: Sean Olson <seancolson@yahoo.com>
Subject: RE: [Simple] Re: [Sipping] draft-olson-sipping-content-indirect-0 0.txt
To: Sriram Parameswar <sriramp@nortelnetworks.com>,
        "'Paul Kyzivat'" <pkyzivat@cisco.com>
Cc: sipping@ietf.org, simple@mailman.dynamicsoft.com
In-Reply-To: <EF1056F8EB4ED511B8FB0002A56079D401E5AFE8@zrc2c014.us.nortel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

This starts to spill over into the content vault
area. I'm preparing a separate draft for this.
There is obviously a lot of overlap here. I 
should be able to post the new draft in about a
week. Let me know if this doesn't cover your 
concerns.

Thanks,
Sean

--- Sriram Parameswar <sriramp@nortelnetworks.com>
wrote:
> Sean:
> 
> Couple of additional comments/requirements:
> 
> ** Access-Control - control over access to the
> content either by
> authorization mechanisms or others. 
> ** Access-Control mechanism - this is probably
> extreme but we could probably
> add an access-control mechanism. This should allow
> for a method of
> access-control modification i.e. I gave you
> permission to see a particular
> content - then want to revoke this privilege.
> 
> Thanks,
> 
> Sriram
> 
> __________________________________________
> Sriram Parameswar              Phone: 972-685-8540
> Interactive Multimedia Server (IMS) Fax:
> 972-684-3986
> Nortel Networks, Richardson USA  Email:
> sriramp@nortelnetworks.com
> 
> 
> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> Sent: Monday, April 08, 2002 9:10 AM
> To: Sean Olson
> Cc: sipping@ietf.org; simple@mailman.dynamicsoft.com
> Subject: [Simple] Re: [Sipping]
> draft-olson-sipping-content-indirect-00.txt
> 
> 
> Sean - comment below.
> 
> 	Paul
> 
> Sean Olson wrote:
> > 
> > FYI. I've put together a draft of requirements
> > for a mechanism to allow content indirection
> > (an indirect reference to content that would
> normally
> > be carried directly in the SIP payload)
> > 
> >
>
http://www.ietf.org/internet-drafts/draft-olson-sipping-content-indirect-00.
> txt
> 
> What is the purpose of REQ-2? 
> 
> Since this proposal is about content indirection, it
> seems like the purpose
> of the content should be unchanged whether it is
> indirected or not. Whatever
> mechanism there is
> out to apply equally whether the content is direct
> or indirect. The
> Content-Disposition header already serves this
> purpose.
> 
> Perhaps you are trying to say that it should be
> possible to use several URLs
> as an alternative to several parts in a
> multipart-MIME body, and that you
> want an ability
> equivalent to specifying a separate
> Content-Disposition header for each.
> That seems reasonable.
> 
> But if you are suggesting a need for more forms of
> disposition than are
> currently covered by Content-Disposition, then I
> think that should be
> handled in a way independent
> of content indirection.
> 
> 	Paul
> _______________________________________________
> simple mailing list
> simple@mailman.dynamicsoft.com
>
http://mailman.dynamicsoft.com/mailman/listinfo/simple
> 


=====
Sean Olson <seancolson@yahoo.com>

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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



From daemon@ns.ietf.org  Mon Apr  8 14:45:43 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02374
	for <sipping-archive@odin.ietf.org>; Mon, 8 Apr 2002 14:45:43 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA29272
	for sipping-archive@odin.ietf.org; Mon, 8 Apr 2002 14:45:45 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA27357;
	Mon, 8 Apr 2002 14:23:42 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA27326
	for <sipping@ns.ietf.org>; Mon, 8 Apr 2002 14:23:39 -0400 (EDT)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01883
	for <sipping@ietf.org>; Mon, 8 Apr 2002 14:23:36 -0400 (EDT)
Received: from cia.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g38INUFQ014041;
	Mon, 8 Apr 2002 14:23:30 -0400 (EDT)
Received: from MHAMMER-W2K.cisco.com (hrn2-dhcp-161-44-87-145.cisco.com [161.44.87.145])
	by cia.cisco.com (Mirapoint)
	with ESMTP id AAT46702;
	Mon, 8 Apr 2002 14:18:03 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020408141509.00b26cb8@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 08 Apr 2002 14:23:05 -0400
To: "Yu, James" <james.yu@neustar.biz>
From: Michael Hammer <mhammer@cisco.com>
Subject: RE: [Sipping] draft-yu-tel-url-04.txt comment
Cc: sipping@ietf.org
In-Reply-To: <A83B38C38B3ED6119D3600306E0722D038BF0B@dc02.npac.com>
Mime-Version: 1.0
Content-Type: text/html; charset="us-ascii"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

<html>
<font size=3>James,<br>
<br>
I missed the intent of the first two lines of Section 6.&nbsp; What you
are saying is that the npdi=, rn=, cic= are embedded in the URL, and not
appended to the end like the tag=xxx, user=phone, branch=xxx,
received=xxx and any other parameter I recall seeing in SIP.<br>
<br>
Will the &quot;;&quot; in the middle of the URI present any
problems?<br>
<br>
Sorry for being obtuse and being perhaps the only one who didn't
appreciate this detail.<br>
<br>
Mike<br>
<br>
<br>
<br>
At 11:27 AM 4/8/2002 -0500, Yu, James wrote:<br>
<blockquote type=cite cite>Mike,<br>
<br>
Everything after &quot;@&quot; in a SIP URL belongs to the SIP host
part.&nbsp; tel URL<br>
appears in the user part of the SIP URL.<br>
<br>
James<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: Michael Hammer
[<a href="mailto:mhammer@cisco.com" eudora="autourl">mailto:mhammer@cisco.com</a>]<br>
&gt; Sent: Thursday, April 04, 2002 3:51 PM<br>
&gt; To: james.yu@neustar.biz<br>
&gt; Cc: sipping@ietf.org<br>
&gt; Subject: [Sipping] draft-yu-tel-url-04.txt comment<br>
&gt; <br>
&gt; <br>
&gt; James,<br>
&gt; <br>
&gt; Section 6: npdi-ident = &quot;yes&quot; | &quot;no&quot;<br>
&gt; Yet, section 7.3, example 1: &quot;npdi=yes@sip.abc,com&quot;<br>
&gt; <br>
&gt; Would that be rejected or truncated?<br>
&gt; <br>
&gt; Also, cic-ident = *phonedigit<br>
&gt; Section 7.3, example 2: &quot;cic=+1-6789@sip.xyz.com&quot;<br>
&gt; <br>
&gt; Does phonedigit include all alphanumeric?<br>
&gt; <br>
&gt; Mike<br>
&gt; </font></blockquote></html>


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



From daemon@ns.ietf.org  Mon Apr  8 14:48:17 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02441
	for <sipping-archive@odin.ietf.org>; Mon, 8 Apr 2002 14:48:17 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA29358
	for sipping-archive@odin.ietf.org; Mon, 8 Apr 2002 14:48:20 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA27684;
	Mon, 8 Apr 2002 14:29:07 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA27656
	for <sipping@ns.ietf.org>; Mon, 8 Apr 2002 14:29:04 -0400 (EDT)
Received: from cundall.co.uk (dorfl.roke.co.uk [193.118.205.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA01966
	for <sipping@ietf.org>; Mon, 8 Apr 2002 14:29:00 -0400 (EDT)
Received: from [193.118.192.41] ([193.118.192.41] verified) by cundall.co.uk (Stalker SMTP Server 1.7) with ESMTP id S.0000089514; Mon, 08 Apr 2002 19:28:58 +0000
Mime-Version: 1.0
X-Sender: lwc@193.118.192.24 (Unverified)
Message-Id: <p05100300b8d78b4f4bf6@[193.118.192.41]>
Date: Mon, 8 Apr 2002 19:29:02 +0100
To: seancolson@yahoo.com
From: Lawrence Conroy <lwc@roke.co.uk>
Cc: sipping@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Subject: [Sipping] Re: draft-olson-sipping-content-indirection
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Hi Sean, Folks,
    IMHO, the content-indirection draft is is fine, but needs a little 
expansion.

I am unsure whether you're suggesting that it's required to provide a 
header (or
headers) holding URI/URLs WITHIN a SIP message, or that it's required 
to put URL
lists in MIME sub-parts associated with the SIP message, or to include such
references within an SDP part.

 From your covering note it SEEMs that you mean the first option. Perhaps it
would be useful to spell out why you need references in a SIP header rather
than elsewhere.

[The SDP approach was the one we took with PINT, where we needed 
external/static
data as part of the PINT session (for example, a file to be faxed), 
so I'm biased :].


Also, I'm not clear on REQ-10 - this reads as suggesting that a SIP message can
be fragmented, with some of the message being held indirectly (I guess with the
rump of the SIP message carrying a reference to the "rest" of the headers)?
That can't be right, so please explain.

all the best,
    Lawrence
-- 
lwc@roke.co.uk: +44 1794 833666::<my opinions>:

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



From daemon@ns.ietf.org  Mon Apr  8 14:48:39 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02460
	for <sipping-archive@odin.ietf.org>; Mon, 8 Apr 2002 14:48:39 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA29376
	for sipping-archive@odin.ietf.org; Mon, 8 Apr 2002 14:48:29 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA28661;
	Mon, 8 Apr 2002 14:36:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA19862
	for <sipping@ns.ietf.org>; Mon, 8 Apr 2002 12:27:58 -0400 (EDT)
Received: from pine.neustar.com (pine.neustar.com [209.173.57.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28996
	for <sipping@ietf.org>; Mon, 8 Apr 2002 12:27:53 -0400 (EDT)
Received: from chiimc01.il.neustar.com (chih650b-s3p2.il.neustar.com [209.173.57.65])
	by pine.neustar.com (8.11.0/8.11.0) with ESMTP id g38GRHZ30772;
	Mon, 8 Apr 2002 11:27:17 -0500
Received: by chiimc01.il.neustar.com with Internet Mail Service (5.5.2653.19)
	id <HGJXZJ82>; Mon, 8 Apr 2002 11:27:12 -0500
Message-ID: <A83B38C38B3ED6119D3600306E0722D038BF0B@dc02.npac.com>
From: "Yu, James" <james.yu@neustar.biz>
To: "'Michael Hammer'" <mhammer@cisco.com>
Cc: sipping@ietf.org
Subject: RE: [Sipping] draft-yu-tel-url-04.txt comment
Date: Mon, 8 Apr 2002 11:27:10 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Mike,

Everything after "@" in a SIP URL belongs to the SIP host part.  tel URL
appears in the user part of the SIP URL.

James

> -----Original Message-----
> From: Michael Hammer [mailto:mhammer@cisco.com]
> Sent: Thursday, April 04, 2002 3:51 PM
> To: james.yu@neustar.biz
> Cc: sipping@ietf.org
> Subject: [Sipping] draft-yu-tel-url-04.txt comment
> 
> 
> James,
> 
> Section 6: npdi-ident = "yes" | "no"
> Yet, section 7.3, example 1: "npdi=yes@sip.abc,com"
> 
> Would that be rejected or truncated?
> 
> Also, cic-ident = *phonedigit
> Section 7.3, example 2: "cic=+1-6789@sip.xyz.com"
> 
> Does phonedigit include all alphanumeric?
> 
> Mike
> 


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



From daemon@ns.ietf.org  Mon Apr  8 14:52:17 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02610
	for <sipping-archive@odin.ietf.org>; Mon, 8 Apr 2002 14:52:16 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA29620
	for sipping-archive@odin.ietf.org; Mon, 8 Apr 2002 14:52:19 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA28763;
	Mon, 8 Apr 2002 14:37:45 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA28734
	for <sipping@ns.ietf.org>; Mon, 8 Apr 2002 14:37:42 -0400 (EDT)
Received: from web11603.mail.yahoo.com (web11603.mail.yahoo.com [216.136.172.55])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA02191
	for <sipping@ietf.org>; Mon, 8 Apr 2002 14:37:39 -0400 (EDT)
Message-ID: <20020408183741.35924.qmail@web11603.mail.yahoo.com>
Received: from [131.107.3.85] by web11603.mail.yahoo.com via HTTP; Mon, 08 Apr 2002 11:37:41 PDT
Date: Mon, 8 Apr 2002 11:37:41 -0700 (PDT)
From: Sean Olson <seancolson@yahoo.com>
Subject: Re: [Sipping] Re: draft-olson-sipping-content-indirection
To: Lawrence Conroy <lwc@roke.co.uk>
Cc: sipping@ietf.org
In-Reply-To: <p05100300b8d78b4f4bf6@[193.118.192.41]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


--- Lawrence Conroy <lwc@roke.co.uk> wrote:
> Hi Sean, Folks,
>     IMHO, the content-indirection draft is is fine,
> but needs a little 
> expansion.
> 
> I am unsure whether you're suggesting that it's
> required to provide a 
> header (or
> headers) holding URI/URLs WITHIN a SIP message, or
> that it's required 
> to put URL
> lists in MIME sub-parts associated with the SIP
> message, or to include such
> references within an SDP part.

I am suggesting requirements. I am intentionally
avoiding defining implementation like whether
this should be done in a header or a MIME part, etc.
I realize this can be a source of confusion. To
clarify, I am leaning towards something that would
be a MIME part, but I will leave the protocol 
mechanics to the SIP working group.

> 
>  From your covering note it SEEMs that you mean the
> first option. Perhaps it
> would be useful to spell out why you need references
> in a SIP header rather
> than elsewhere.

Sorry for the confusion. As per a previous
suggestion, I will expand the section on the
intended uses of this mechanism in the hope that
the requirements will become clearer with more
context.

> 
> [The SDP approach was the one we took with PINT,
> where we needed 
> external/static
> data as part of the PINT session (for example, a
> file to be faxed), 
> so I'm biased :].

This is not something I had considered, but 
it is certainly one option. I will revisit the
requirements from this perspective to see if
any new requirements fall out.

> Also, I'm not clear on REQ-10 - this reads as
> suggesting that a SIP message can
> be fragmented, with some of the message being held
> indirectly (I guess with the
> rump of the SIP message carrying a reference to the
> "rest" of the headers)?
> That can't be right, so please explain.

That is right. This requirement is a bit on the
fringe so I would welcome any feedback on whether
people think this is a good idea or not.

> all the best,
>     Lawrence
> -- 

Thanks for the comments,
Sean


=====
Sean Olson <seancolson@yahoo.com>

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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



From daemon@ns.ietf.org  Mon Apr  8 15:10:15 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03190
	for <sipping-archive@odin.ietf.org>; Mon, 8 Apr 2002 15:10:15 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA01036
	for sipping-archive@odin.ietf.org; Mon, 8 Apr 2002 15:10:18 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA29692;
	Mon, 8 Apr 2002 14:54:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA29661
	for <sipping@ns.ietf.org>; Mon, 8 Apr 2002 14:54:12 -0400 (EDT)
Received: from Mitel.COM ([216.191.234.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02683
	for <sipping@ietf.org>; Mon, 8 Apr 2002 14:54:08 -0400 (EDT)
From: Tom_Gray@Mitel.COM
Received: from kanmta01.mitel.com (kanmta01.kanata.mitel.com [134.199.37.58]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with ESMTP id OAA20507;
	Mon, 8 Apr 2002 14:51:50 -0400 (EDT)
Subject: Re: [Sipping] Re: draft-olson-sipping-content-indirection
To: Sean Olson <seancolson@yahoo.com>
Cc: Lawrence Conroy <lwc@roke.co.uk>, sipping@ietf.org
Date: Mon, 8 Apr 2002 14:51:48 -0400
Message-ID: <OF81F6A26D.FA15AD36-ON85256B95.0067594D@mitel.com>
X-MIMETrack: Serialize by Router on kanmta01/Mitel(Release 5.0.7 |March 21, 2001) at 04/08/2002
 02:51:50 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org







>> Also, I'm not clear on REQ-10 - this reads as
>> suggesting that a SIP message can
>> be fragmented, with some of the message being held
>> indirectly (I guess with the
>> rump of the SIP message carrying a reference to the
>> "rest" of the headers)?
>> That can't be right, so please explain.

>That is right. This requirement is a bit on the
>fringe so I would welcome any feedback on whether
>people think this is a good idea or not.

If this is to be used for stereotyped behavior, why bother with the
indirection at all. Why not just a header which indicates which stereotyped
complement of headers is to be assumed?





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



From daemon@ns.ietf.org  Mon Apr  8 15:14:20 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03367
	for <sipping-archive@odin.ietf.org>; Mon, 8 Apr 2002 15:14:20 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA01171
	for sipping-archive@odin.ietf.org; Mon, 8 Apr 2002 15:14:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA29899;
	Mon, 8 Apr 2002 14:57:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA29867
	for <sipping@ns.ietf.org>; Mon, 8 Apr 2002 14:57:53 -0400 (EDT)
Received: from howler.tri.sbc.com (howler.tri.sbc.com [205.173.58.4] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02787
	for <sipping@ietf.org>; Mon, 8 Apr 2002 14:57:50 -0400 (EDT)
Received: from sbctri.tri.sbc.com (sbctri [144.60.1.10])
	by howler.tri.sbc.com (8.11.6+Sun/8.11.0) with ESMTP id g38J0cN22048
	for <sipping@ietf.org>; Mon, 8 Apr 2002 14:00:38 -0500 (CDT)
Received: from tripacific.nttl.ad.tri.sbc.com (localhost [127.0.0.1])
	by sbctri.tri.sbc.com (8.11.6+Sun/8.9.3) with ESMTP id g38Iv8J27668
	for <sipping@ietf.org>; Mon, 8 Apr 2002 13:57:08 -0500 (CDT)
Received: by tripacific.nttl.ad.tri.sbc.com with Internet Mail Service (5.5.2653.19)
	id <2HF6K0CA>; Mon, 8 Apr 2002 11:57:50 -0700
Message-ID: <CC16687B8C7AA1419B47057C36B1E98D0F67F7@tripacific.nttl.ad.tri.sbc.com>
From: "Hu, Cheng-Hong" <cxhu@tri.sbc.com>
To: sipping@ietf.org
Date: Mon, 8 Apr 2002 11:57:49 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sipping] Instant Messaging
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Hi,

Is any good technical whitepapers or documents on Instant Messaging?

Thanks!
Cheng-hong 

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



From daemon@ns.ietf.org  Mon Apr  8 15:50:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04240
	for <sipping-archive@odin.ietf.org>; Mon, 8 Apr 2002 15:50:24 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA04198
	for sipping-archive@odin.ietf.org; Mon, 8 Apr 2002 15:50:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA01926;
	Mon, 8 Apr 2002 15:29:16 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA01895
	for <sipping@ns.ietf.org>; Mon, 8 Apr 2002 15:29:13 -0400 (EDT)
Received: from web11603.mail.yahoo.com (web11603.mail.yahoo.com [216.136.172.55])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA03702
	for <sipping@ietf.org>; Mon, 8 Apr 2002 15:29:09 -0400 (EDT)
Message-ID: <20020408192912.43290.qmail@web11603.mail.yahoo.com>
Received: from [131.107.3.86] by web11603.mail.yahoo.com via HTTP; Mon, 08 Apr 2002 12:29:12 PDT
Date: Mon, 8 Apr 2002 12:29:12 -0700 (PDT)
From: Sean Olson <seancolson@yahoo.com>
Subject: Re: [Sipping] Re: draft-olson-sipping-content-indirection
To: Tom_Gray@Mitel.COM
Cc: Lawrence Conroy <lwc@roke.co.uk>, sipping@ietf.org
In-Reply-To: <OF81F6A26D.FA15AD36-ON85256B95.0067594D@mitel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

> >> Also, I'm not clear on REQ-10 - this reads as
> >> suggesting that a SIP message can
> >> be fragmented, with some of the message being
> held
> >> indirectly (I guess with the
> >> rump of the SIP message carrying a reference to
> the
> >> "rest" of the headers)?
> >> That can't be right, so please explain.
> 
> >That is right. This requirement is a bit on the
> >fringe so I would welcome any feedback on whether
> >people think this is a good idea or not.
> 
> If this is to be used for stereotyped behavior, why
> bother with the
> indirection at all. Why not just a header which
> indicates which stereotyped
> complement of headers is to be assumed?

Stereotyping is not the intended application 
of this indirection. Rather, it is intended
to "offload" large headers or sets of large headers.

Stereotyping is interesting but probably a rathole
and eventually an interop problem.


=====
Sean Olson <seancolson@yahoo.com>

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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



From daemon@ns.ietf.org  Mon Apr  8 16:35:07 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05581
	for <sipping-archive@odin.ietf.org>; Mon, 8 Apr 2002 16:35:07 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA09172
	for sipping-archive@odin.ietf.org; Mon, 8 Apr 2002 16:35:11 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA07202;
	Mon, 8 Apr 2002 16:16:32 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA07173
	for <sipping@ns.ietf.org>; Mon, 8 Apr 2002 16:16:29 -0400 (EDT)
Received: from Mitel.COM ([216.191.234.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05062
	for <sipping@ietf.org>; Mon, 8 Apr 2002 16:16:20 -0400 (EDT)
From: Tom_Gray@Mitel.COM
Received: from kanmta01.mitel.com (kanmta01.kanata.mitel.com [134.199.37.58]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with ESMTP id QAA03024;
	Mon, 8 Apr 2002 16:14:41 -0400 (EDT)
Subject: Re: [Sipping] Re: draft-olson-sipping-content-indirection
To: Sean Olson <seancolson@yahoo.com>
Cc: Tom_Gray@Mitel.COM, Lawrence Conroy <lwc@roke.co.uk>, sipping@ietf.org
Date: Mon, 8 Apr 2002 16:14:40 -0400
Message-ID: <OFD6BC248C.3207DCFB-ON85256B95.006EBCC9@mitel.com>
X-MIMETrack: Serialize by Router on kanmta01/Mitel(Release 5.0.7 |March 21, 2001) at 04/08/2002
 04:14:41 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org



I'm not really advocating any position on stereotyping here. It may be a
good or bad idea depending on the circumstances, However I don't see how
tit is anymore prone to interoperability problems than any other type of
header. It could possibly lead to some amount of compression in some
circumstances if some 'boilerplate' headers could be assumed.






Sean Olson <seancolson@yahoo.com> on 04/08/2002 03:29:12 PM

To:   Tom_Gray@Mitel.COM
cc:   Lawrence Conroy <lwc@roke.co.uk>, sipping@ietf.org

Subject:  Re: [Sipping] Re: draft-olson-sipping-content-indirection


> >> Also, I'm not clear on REQ-10 - this reads as
> >> suggesting that a SIP message can
> >> be fragmented, with some of the message being
> held
> >> indirectly (I guess with the
> >> rump of the SIP message carrying a reference to
> the
> >> "rest" of the headers)?
> >> That can't be right, so please explain.
>
> >That is right. This requirement is a bit on the
> >fringe so I would welcome any feedback on whether
> >people think this is a good idea or not.
>
> If this is to be used for stereotyped behavior, why
> bother with the
> indirection at all. Why not just a header which
> indicates which stereotyped
> complement of headers is to be assumed?

Stereotyping is not the intended application
of this indirection. Rather, it is intended
to "offload" large headers or sets of large headers.

Stereotyping is interesting but probably a rathole
and eventually an interop problem.


=====
Sean Olson <seancolson@yahoo.com>

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/





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



From daemon@optimus.ietf.org  Tue Apr  9 08:28:05 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03000
	for <sipping-archive@odin.ietf.org>; Tue, 9 Apr 2002 08:28:05 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA14449
	for sipping-archive@odin.ietf.org; Tue, 9 Apr 2002 08:28:07 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA12868;
	Tue, 9 Apr 2002 08:00:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA04879
	for <sipping@optimus.ietf.org>; Mon, 8 Apr 2002 23:28:57 -0400 (EDT)
Received: from oak.neustar.com (oak.neustar.com [209.173.53.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16384
	for <sipping@ietf.org>; Mon, 8 Apr 2002 23:28:53 -0400 (EDT)
Received: from chiimc01.il.neustar.com (stih650b-s1p2.va.neustar.com [209.173.53.65])
	by oak.neustar.com (8.11.0/8.11.0) with ESMTP id g393SI813849;
	Mon, 8 Apr 2002 23:28:18 -0400
Received: by chiimc01.il.neustar.com with Internet Mail Service (5.5.2653.19)
	id <HGJXZR2H>; Mon, 8 Apr 2002 22:28:13 -0500
Message-ID: <A83B38C38B3ED6119D3600306E0722D038BF13@dc02.npac.com>
From: "Yu, James" <james.yu@neustar.biz>
To: "'Michael Hammer'" <mhammer@cisco.com>
Cc: sipping@ietf.org
Subject: RE: [Sipping] draft-yu-tel-url-04.txt comment
Date: Mon, 8 Apr 2002 22:28:11 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1DF76.9354AEA0"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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

Mike,
 
Yes, user=phone or branch=xxx is the url-parameter (after the hostport).
npdi, rn and cic are part of the tel URL and can appear in the user part of
the sip url when user=phone is present.
 
The user part of the sip url is usually treated as a string.  but when
user=phone is present, the user part will contain a telephone number and
with or without some tel URL parameters.  ";' in the user part does not
present any problem.
 
James

-----Original Message-----
From: Michael Hammer [mailto:mhammer@cisco.com]
Sent: Monday, April 08, 2002 2:23 PM
To: Yu, James
Cc: sipping@ietf.org
Subject: RE: [Sipping] draft-yu-tel-url-04.txt comment


James,

I missed the intent of the first two lines of Section 6.  What you are
saying is that the npdi=, rn=, cic= are embedded in the URL, and not
appended to the end like the tag=xxx, user=phone, branch=xxx, received=xxx
and any other parameter I recall seeing in SIP.

Will the ";" in the middle of the URI present any problems?

Sorry for being obtuse and being perhaps the only one who didn't appreciate
this detail.

Mike



At 11:27 AM 4/8/2002 -0500, Yu, James wrote:


Mike,

Everything after "@" in a SIP URL belongs to the SIP host part.  tel URL
appears in the user part of the SIP URL.

James

> -----Original Message-----
> From: Michael Hammer [ mailto:mhammer@cisco.com <mailto:mhammer@cisco.com>
]
> Sent: Thursday, April 04, 2002 3:51 PM
> To: james.yu@neustar.biz
> Cc: sipping@ietf.org
> Subject: [Sipping] draft-yu-tel-url-04.txt comment
> 
> 
> James,
> 
> Section 6: npdi-ident = "yes" | "no"
> Yet, section 7.3, example 1: "npdi=yes@sip.abc,com"
> 
> Would that be rejected or truncated?
> 
> Also, cic-ident = *phonedigit
> Section 7.3, example 2: "cic=+1-6789@sip.xyz.com"
> 
> Does phonedigit include all alphanumeric?
> 
> Mike
> 


------_=_NextPart_001_01C1DF76.9354AEA0
Content-Type: text/html;
	charset="iso-8859-1"

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


<META content="MSHTML 5.50.4807.2300" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=431582103-09042002>Mike,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=431582103-09042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=431582103-09042002>Yes, 
user=phone or branch=xxx is the url-parameter (after the hostport).&nbsp; npdi, 
rn and cic are part of the tel URL and can appear in the user part of the sip 
url when user=phone is present.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=431582103-09042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=431582103-09042002>The 
user part of the sip url is usually treated as a string.&nbsp; but when 
user=phone is present, the user part will contain a telephone number&nbsp;and 
with or without&nbsp;some tel URL parameters.&nbsp; ";' in the user part does 
not present any problem.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=431582103-09042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=431582103-09042002>James</SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Michael Hammer 
  [mailto:mhammer@cisco.com]<BR><B>Sent:</B> Monday, April 08, 2002 2:23 
  PM<BR><B>To:</B> Yu, James<BR><B>Cc:</B> sipping@ietf.org<BR><B>Subject:</B> 
  RE: [Sipping] draft-yu-tel-url-04.txt comment<BR><BR></FONT></DIV><FONT 
  size=3>James,<BR><BR>I missed the intent of the first two lines of Section 
  6.&nbsp; What you are saying is that the npdi=, rn=, cic= are embedded in the 
  URL, and not appended to the end like the tag=xxx, user=phone, branch=xxx, 
  received=xxx and any other parameter I recall seeing in SIP.<BR><BR>Will the 
  ";" in the middle of the URI present any problems?<BR><BR>Sorry for being 
  obtuse and being perhaps the only one who didn't appreciate this 
  detail.<BR><BR>Mike<BR><BR><BR><BR>At 11:27 AM 4/8/2002 -0500, Yu, James 
  wrote:<BR>
  <BLOCKQUOTE cite type="cite">Mike,<BR><BR>Everything after "@" in a SIP URL 
    belongs to the SIP host part.&nbsp; tel URL<BR>appears in the user part of 
    the SIP URL.<BR><BR>James<BR><BR>&gt; -----Original Message-----<BR>&gt; 
    From: Michael Hammer [<A href="mailto:mhammer@cisco.com" 
    eudora="autourl">mailto:mhammer@cisco.com</A>]<BR>&gt; Sent: Thursday, April 
    04, 2002 3:51 PM<BR>&gt; To: james.yu@neustar.biz<BR>&gt; Cc: 
    sipping@ietf.org<BR>&gt; Subject: [Sipping] draft-yu-tel-url-04.txt 
    comment<BR>&gt; <BR>&gt; <BR>&gt; James,<BR>&gt; <BR>&gt; Section 6: 
    npdi-ident = "yes" | "no"<BR>&gt; Yet, section 7.3, example 1: 
    "npdi=yes@sip.abc,com"<BR>&gt; <BR>&gt; Would that be rejected or 
    truncated?<BR>&gt; <BR>&gt; Also, cic-ident = *phonedigit<BR>&gt; Section 
    7.3, example 2: "cic=+1-6789@sip.xyz.com"<BR>&gt; <BR>&gt; Does phonedigit 
    include all alphanumeric?<BR>&gt; <BR>&gt; Mike<BR>&gt; 
</FONT></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1DF76.9354AEA0--


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



From daemon@optimus.ietf.org  Tue Apr  9 10:48:09 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07490
	for <sipping-archive@odin.ietf.org>; Tue, 9 Apr 2002 10:48:08 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA24663
	for sipping-archive@odin.ietf.org; Tue, 9 Apr 2002 10:48:10 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA24150;
	Tue, 9 Apr 2002 10:37:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA17787
	for <sipping@optimus.ietf.org>; Tue, 9 Apr 2002 09:21:20 -0400 (EDT)
Received: from mail1.telekom.de (mail1.telekom.de [62.225.183.235])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04347
	for <sipping@ietf.org>; Tue, 9 Apr 2002 09:21:18 -0400 (EDT)
Received: from g9jbr.mgb01.telekom.de by G8SBV.dmz.telekom.de with ESMTP; Tue, 9 Apr 2002 15:19:23 +0200
Received: by G9JBR.mgb01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <2Q8W76AN>; Tue, 9 Apr 2002 15:20:30 +0200
Message-Id: <C3F9C806AEC6D5119643000347055E322088B9@G9JNW.mgb01.telekom.de>
From: "Beck01, Wolfgang" <BeckW@t-systems.com>
To: seancolson@yahoo.com, sipping@ietf.org, simple@mailman.dynamicsoft.com
Subject: RE: [Sipping] draft-olson-sipping-content-indirect-00.txt
Date: Tue, 9 Apr 2002 15:20:29 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Sean,

disposition "execute" in REQ-2 is very dangerous. A popular E-mail program
used to have a similar function enabled by default, which resulted
in a worldwide breakdown of many mail servers. Even "render" might be dangerous, if
the document uses some language like PostScript or Word macros.


--
Wolfgang Beck
T-Systems Nova GmbH 




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



From daemon@optimus.ietf.org  Tue Apr  9 10:52:16 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07589
	for <sipping-archive@odin.ietf.org>; Tue, 9 Apr 2002 10:52:16 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA24822
	for sipping-archive@odin.ietf.org; Tue, 9 Apr 2002 10:52:17 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA24096;
	Tue, 9 Apr 2002 10:36:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA15437
	for <sipping@optimus.ietf.org>; Tue, 9 Apr 2002 08:41:07 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03423;
	Tue, 9 Apr 2002 08:41:03 -0400 (EDT)
Message-Id: <200204091241.IAA03423@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 09 Apr 2002 08:41:03 -0400
Subject: [Sipping] I-D ACTION:draft-camarillo-sipping-reason-00.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

--NextPart

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


	Title		: Session Initiation Protocol: Requirements on Reason 
                          Information beyond the Status Code
	Author(s)	: G. Camarillo
	Filename	: draft-camarillo-sipping-reason-00.txt
	Pages		: 5
	Date		: 08-Apr-02
	
Some applications need to know why a particular SIP message was
issued. This document describes those applications and provides a
set of requirements that a mechanism used to transport this type of
information has to fulfill.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-camarillo-sipping-reason-00.txt

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-camarillo-sipping-reason-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-camarillo-sipping-reason-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:	<20020408122729.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-camarillo-sipping-reason-00.txt

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

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

--OtherAccess--

--NextPart--




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



From daemon@optimus.ietf.org  Tue Apr  9 13:00:12 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12113
	for <sipping-archive@odin.ietf.org>; Tue, 9 Apr 2002 13:00:12 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA04320
	for sipping-archive@odin.ietf.org; Tue, 9 Apr 2002 13:00:13 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA02267;
	Tue, 9 Apr 2002 12:25:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA02236
	for <sipping@optimus.ietf.org>; Tue, 9 Apr 2002 12:25:38 -0400 (EDT)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11256
	for <sipping@ietf.org>; Tue, 9 Apr 2002 12:25:35 -0400 (EDT)
Received: from cia.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g39GPUu0026228;
	Tue, 9 Apr 2002 12:25:30 -0400 (EDT)
Received: from MHAMMER-W2K.cisco.com (hrn2-dhcp-161-44-87-145.cisco.com [161.44.87.145])
	by cia.cisco.com (Mirapoint)
	with ESMTP id AAT54408;
	Tue, 9 Apr 2002 12:20:03 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020409121103.00b1b0f8@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 09 Apr 2002 12:25:02 -0400
To: "Yu, James" <james.yu@neustar.biz>
From: Michael Hammer <mhammer@cisco.com>
Subject: RE: [Sipping] draft-yu-tel-url-04.txt comment
Cc: sipping@ietf.org
In-Reply-To: <A83B38C38B3ED6119D3600306E0722D038BF13@dc02.npac.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

James,

Thanks.  I found that the ABNF on bis9 p.228 allowed the ";" in the user 
part.  I still feel that the use of parameters that are intended to be 
globally used, within the user part of a sip: URI (which I've heard many 
times can only be interpreted correctly by the domain after the "@" sign) 
may be an unintended contradiction.  I don't see a problem with the tel: 
URI as that does not have the domain construct.

Would an address such as:
sip:+1-202-533-1234@sip.abc.com;user=phone;npdi=yes;rn=+1-202-544-000;cic=+1-6789
also be valid or is that prohibited by your draft?

Thanks again.
Mike


At 10:28 PM 4/8/2002 -0500, Yu, James wrote:
>Mike,
>
>Yes, user=phone or branch=xxx is the url-parameter (after the 
>hostport).  npdi, rn and cic are part of the tel URL and can appear in the 
>user part of the sip url when user=phone is present.
>
>The user part of the sip url is usually treated as a string.  but when 
>user=phone is present, the user part will contain a telephone number and 
>with or without some tel URL parameters.  ";' in the user part does not 
>present any problem.
>
>James
>-----Original Message-----
>From: Michael Hammer [mailto:mhammer@cisco.com]
>Sent: Monday, April 08, 2002 2:23 PM
>To: Yu, James
>Cc: sipping@ietf.org
>Subject: RE: [Sipping] draft-yu-tel-url-04.txt comment
>
>James,
>
>I missed the intent of the first two lines of Section 6.  What you are 
>saying is that the npdi=, rn=, cic= are embedded in the URL, and not 
>appended to the end like the tag=xxx, user=phone, branch=xxx, received=xxx 
>and any other parameter I recall seeing in SIP.
>
>Will the ";" in the middle of the URI present any problems?
>
>Sorry for being obtuse and being perhaps the only one who didn't 
>appreciate this detail.
>
>Mike
>
>
>
>
>
>At 11:27 AM 4/8/2002 -0500, Yu, James wrote:
>>Mike,
>>
>>Everything after "@" in a SIP URL belongs to the SIP host part.  tel URL
>>appears in the user part of the SIP URL.
>>
>>James
>>
>> > -----Original Message-----
>> > From: Michael Hammer [mailto:mhammer@cisco.com]
>> > Sent: Thursday, April 04, 2002 3:51 PM
>> > To: james.yu@neustar.biz
>> > Cc: sipping@ietf.org
>> > Subject: [Sipping] draft-yu-tel-url-04.txt comment
>> >
>> >
>> > James,
>> >
>> > Section 6: npdi-ident = "yes" | "no"
>> > Yet, section 7.3, example 1: "npdi=yes@sip.abc,com"
>> >
>> > Would that be rejected or truncated?
>> >
>> > Also, cic-ident = *phonedigit
>> > Section 7.3, example 2: "cic=+1-6789@sip.xyz.com"
>> >
>> > Does phonedigit include all alphanumeric?
>> >
>> > Mike
>> >


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



From daemon@optimus.ietf.org  Tue Apr  9 13:25:13 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12974
	for <sipping-archive@odin.ietf.org>; Tue, 9 Apr 2002 13:25:13 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA06121
	for sipping-archive@odin.ietf.org; Tue, 9 Apr 2002 13:25:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA05049;
	Tue, 9 Apr 2002 13:07:19 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA05018
	for <sipping@optimus.ietf.org>; Tue, 9 Apr 2002 13:07:16 -0400 (EDT)
Received: from web11608.mail.yahoo.com (web11608.mail.yahoo.com [216.136.172.60])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA12269
	for <sipping@ietf.org>; Tue, 9 Apr 2002 13:07:14 -0400 (EDT)
Message-ID: <20020409170715.94629.qmail@web11608.mail.yahoo.com>
Received: from [207.46.137.9] by web11608.mail.yahoo.com via HTTP; Tue, 09 Apr 2002 10:07:15 PDT
Date: Tue, 9 Apr 2002 10:07:15 -0700 (PDT)
From: Sean Olson <seancolson@yahoo.com>
Subject: RE: [Sipping] draft-olson-sipping-content-indirect-00.txt
To: "Beck01, Wolfgang" <BeckW@t-systems.com>, sipping@ietf.org,
        simple@mailman.dynamicsoft.com
In-Reply-To: <C3F9C806AEC6D5119643000347055E322088B9@G9JNW.mgb01.telekom.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

I absolutely appreciate your concern. Simply
put, any system must have an appropriately defined
security mechanism in place for any packets it
receives. Ignoring Content-Disposition: for now,
what dangers do you perceive for handling an INVITE,
or a SUBSCRIBE, or a REFER, or ... ? This is
roughly equivalent to the problem of handling CPL 
upload. How do you trust the CPL you receive to
know it is safe to execute? Assuming there is
an answer to that question, can you apply that
answer to an "execute" disposition?

I would like to solicit other people's comments
on this topic. If there is sufficient pushback,
I'll remove this item.

Thanks!
/sean

--- "Beck01, Wolfgang" <BeckW@t-systems.com> wrote:
> Sean,
> 
> disposition "execute" in REQ-2 is very dangerous. A
> popular E-mail program
> used to have a similar function enabled by default,
> which resulted
> in a worldwide breakdown of many mail servers. Even
> "render" might be dangerous, if
> the document uses some language like PostScript or
> Word macros.
> 
> 
> --
> Wolfgang Beck
> T-Systems Nova GmbH 
> 
> 


=====
Sean Olson <seancolson@yahoo.com>

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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



From daemon@optimus.ietf.org  Tue Apr  9 14:59:05 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17077
	for <sipping-archive@odin.ietf.org>; Tue, 9 Apr 2002 14:59:04 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA12970
	for sipping-archive@odin.ietf.org; Tue, 9 Apr 2002 14:59:06 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA12481;
	Tue, 9 Apr 2002 14:44:18 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA12450
	for <sipping@optimus.ietf.org>; Tue, 9 Apr 2002 14:44:15 -0400 (EDT)
Received: from chuckie.dgms.com (angelica.ulticom.com [208.255.120.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16446
	for <sipping@ietf.org>; Tue, 9 Apr 2002 14:44:08 -0400 (EDT)
Received: from ulticom.com (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with ESMTP id OAA14012
	for <sipping@ietf.org>; Tue, 9 Apr 2002 14:43:34 -0400 (EDT)
Message-ID: <3CB3373D.8D5B502F@ulticom.com>
Date: Tue, 09 Apr 2002 14:47:25 -0400
From: Vijaya Venkatachalam <vijaya@ulticom.com>
Organization: Ulticom, Inc.
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: sipping@ietf.org
Content-Type: multipart/mixed;
 boundary="------------68215B7A07021B61ECA742C9"
Subject: [Sipping] Path Header
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


This is a multi-part message in MIME format.
--------------68215B7A07021B61ECA742C9
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,

Can somebody tell me where I can find some information
regarding path header?

Thanks,
Vijaya

--------------68215B7A07021B61ECA742C9
Content-Type: text/x-vcard; charset=us-ascii;
 name="vijaya.vcf"
Content-Description: Card for Vijaya Venkatachalam
Content-Disposition: attachment;
 filename="vijaya.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Venkatachalam;Vijaya
tel;fax:+1-856-866-2033
tel;work:+1-856-787-2853
x-mozilla-html:FALSE
url:www.ulticom.com
org:Ulticom, Inc.;Advanced Research 
adr:;;1020 Briggs Rd;Mt. Laurel;NJ;08054;USA
version:2.1
email;internet:vijaya@ulticom.com
fn:Vijaya Venkatachalam
end:vcard

--------------68215B7A07021B61ECA742C9--


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



From daemon@optimus.ietf.org  Wed Apr 10 00:55:09 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02748
	for <sipping-archive@odin.ietf.org>; Wed, 10 Apr 2002 00:55:09 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA14638
	for sipping-archive@odin.ietf.org; Wed, 10 Apr 2002 00:55:11 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA13027;
	Wed, 10 Apr 2002 00:19:40 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA12996
	for <sipping@optimus.ietf.org>; Wed, 10 Apr 2002 00:19:36 -0400 (EDT)
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01887
	for <sipping@ietf.org>; Wed, 10 Apr 2002 00:19:34 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.23])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g3A4K7o6003934;
	Wed, 10 Apr 2002 00:20:09 -0400 (EDT)
Message-ID: <3CB3BD2E.45C6EB3A@dynamicsoft.com>
Date: Wed, 10 Apr 2002 00:18:54 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Bobby Sardana <sardana@obsoft.com>
CC: "Beck01, Wolfgang" <BeckW@t-systems.com>, seancolson@yahoo.com,
        sipping@ietf.org
Subject: Re: [Simple] RE: [Sipping] draft-olson-sipping-content-indirect-00.txt
References: <3CB39BF0.4A4435C8@obsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

[trimmed SIMPLE]

Bobby Sardana wrote:
> 
> I am sure that the appropriate UAC will implement a "security sandbox"
> for both the
> "execute" and "render" feature set. A properly designed UAC will also
> allow such
> features to be manually disabled.
> 
> Personally, I like the "execute" feature as it allows new services to be
> deployed on
> the UAC.

I agree with those who think this is far too dangerous.

I think a lot more thinking needs to go into disposition types. In any
case, I think they are totally ortogonal to the problem at hand. Rather,
the appropriate requirement for this draft is to simply state that it
must be possible to associate a registered disposition with each URI.

If someone wants to write a separate draft on new disposition
requirements, they should feel free to do so...

-Jonathan R.


-- 
Jonathan D. Rosenberg, Ph.D.            72 Eagle Rock Avenue
Chief Scientist                         First Floor
dynamicsoft                             East Hanover, NJ 07936
jdrosen@dynamicsoft.com                 FAX: (973) 952-5050
http://www.jdrosen.net                  PH:  (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 daemon@optimus.ietf.org  Wed Apr 10 00:55:12 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02763
	for <sipping-archive@odin.ietf.org>; Wed, 10 Apr 2002 00:55:12 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA14632
	for sipping-archive@odin.ietf.org; Wed, 10 Apr 2002 00:55:11 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA14232;
	Wed, 10 Apr 2002 00:42:50 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA14201
	for <sipping@optimus.ietf.org>; Wed, 10 Apr 2002 00:42:47 -0400 (EDT)
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02599
	for <sipping@ietf.org>; Wed, 10 Apr 2002 00:42:44 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.23])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g3A4hNo6003944
	for <sipping@ietf.org>; Wed, 10 Apr 2002 00:43:25 -0400 (EDT)
Message-ID: <3CB3C2A0.49766A2@dynamicsoft.com>
Date: Wed, 10 Apr 2002 00:42:08 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: sipping@ietf.org
Subject: Re: [Sipping] I-D 
 ACTION:draft-culpepper-sipping-app-interact-reqs-00.txt
References: <200203281208.HAA22393@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

This is an excellent start at requirements. Some comments on the
requirements there, and some suggestions for additional requirements:

R1 reads:

> The mechanism must support collecting device/user input which 
>         is associated with an established SIP session but must also 
>         support collecting device/user input that is outside of any 
>         established sessions. 

I am concerned about the security and scope issues about listening for
device/user input outside of a session. This seems like a
standards-based approach for implementing the government key input
snooper.... I know what you had in mind for this (things like service
activation for call forwarding), but I think that there are better ways
to do it (web page, anyone?).

> R5:  A network entity desiring user indications must be able to 
>         request user indications from another network entity.  The 
>         entity receiving a request must be able to respond with its 
>         capability/intent to transmit user indications. 

We should be more specific here. We have a caller and a callee. I think
that by "entity" you mean one of those two.

>  R6:  The mechanism must support filtering so that only user 
>         indications of interest are transmitted. 

I don't know what this means.

> R15: The receiving application must be able to detect user activity 
>         indication loss due to packet loss from received user activity 
>         indications. 

I don't know what this means.

> D4:  The mechanism should support routing and identification that is 
>         compatible with use in a SIP-based network. 

This is too vague to be useful.


Some additional requirements:

* The mechanism should support devices that possess a UI, and those
which do not possess a UI

* The mechanism should be capable of handling UIs from simple screens
with buttons, to voice input

* The mechanism should be capable of handling future user interfaces
that may be defined down the road

* The mechanism should allow a device to indicate support for multiple
user interfaces, and allow the application to select which one is to be
used

* The mechanism should allow a device to indicate relative preferences
amongst the various user interfaces

* The mechanism should support user interfaces which require a new
content to be presented to the user upon input from the user (i.e.,
change the screen when a user presses a button)

* The mechanism should support user interfaces where user input can be
sent to the application without waiting for a response from the previous
input

* The mechanism should allow the user to interface with multiple user
interfaces for different applications within the same call (for example,
a single call may involve a call recording application and a prepaid
calling application, both of which might support a UI)

* The mechanism should allow the user to know which application is
associated with which user interface/input

* The mechanism must allow a user to have assurances that the user input
it is providing is only to applications/servers on the call path between
caller and callee.

* The mechanism must work with applications that are both proxy and
b2bua.

* The mechanism must not require excessive bandwidth on the access link
to the device, in order to support mobiles



Thats it for now.

THanks,
Jonathan R.

Internet-Drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> 
>         Title           : Network Application Interaction Requirements
>         Author(s)       : B. Culpepper, R. Fairlie-Cuninghame
>         Filename        :
> draft-culpepper-sipping-app-interact-reqs-00.txt
>         Pages           : 6
>         Date            : 27-Mar-02
> 
> This document defines the requirements for a mechanism based on SIP
> that allows network entities to request and report user indications
> that can be used to interact with applications associated with SIP-
> based services.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-culpepper-sipping-app-interact
> -reqs-00.txt
> 
> To remove yourself from the IETF Announcement list, send a message to
> ietf-announce-request with the word unsubscribe in the body of the
> message.
> 
> Internet-Drafts are also available by anonymous FTP. Login with the
> username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
>         "get draft-culpepper-sipping-app-interact-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-culpepper-sipping-app-interact-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.
> 
>   ------------------------------------------------------------------------
> 
> Subject:
> Date: Thu, 28 Mar 2002 16:41:59 -0500
> 
>   ------------------------------------------------------------------------
> 
>    ATT36315.txtName: ATT36315.txt
>                Type: Plain Text (text/plain)
> 
>                 Access-Type: anon-ftp
>  Document Info:        Site: internet-drafts
>                        Mode: ftp.ietf.org

-- 
Jonathan D. Rosenberg, Ph.D.            72 Eagle Rock Avenue
Chief Scientist                         First Floor
dynamicsoft                             East Hanover, NJ 07936
jdrosen@dynamicsoft.com                 FAX: (973) 952-5050
http://www.jdrosen.net                  PH:  (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 daemon@optimus.ietf.org  Wed Apr 10 01:33:11 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA03251
	for <sipping-archive@odin.ietf.org>; Wed, 10 Apr 2002 01:33:11 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA27325
	for sipping-archive@odin.ietf.org; Wed, 10 Apr 2002 01:33:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA26317;
	Wed, 10 Apr 2002 01:22:25 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA26286
	for <sipping@optimus.ietf.org>; Wed, 10 Apr 2002 01:22:22 -0400 (EDT)
Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA03087
	for <sipping@ietf.org>; Wed, 10 Apr 2002 01:22:18 -0400 (EDT)
Received: from BOB ([12.230.191.92]) by rwcrmhc53.attbi.com
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20020410052145.FSJW21252.rwcrmhc53.attbi.com@BOB>;
          Wed, 10 Apr 2002 05:21:45 +0000
Reply-To: <seancolson@yahoo.com>
From: "Sean Olson" <seancolson@yahoo.com>
To: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>,
        "'Bobby Sardana'" <sardana@obsoft.com>
Cc: "'Beck01, Wolfgang'" <BeckW@t-systems.com>, <sipping@ietf.org>
Subject: RE: [Simple] RE: [Sipping] draft-olson-sipping-content-indirect-00.txt
Date: Tue, 9 Apr 2002 22:21:52 -0700
Message-ID: <000001c1e04f$9f995970$6401a8c0@BOB>
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.3416
Importance: Normal
In-Reply-To: <3CB3BD2E.45C6EB3A@dynamicsoft.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Fair enough. This does spill over into implementation a bit.
I'll remove the specifics from the text. What I will add is
that these content dispositions should be extensible.

/sean

-----Original Message-----
From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com] 
Sent: Tuesday, April 09, 2002 9:19 PM
To: Bobby Sardana
Cc: Beck01, Wolfgang; seancolson@yahoo.com; sipping@ietf.org
Subject: Re: [Simple] RE: [Sipping]
draft-olson-sipping-content-indirect-00.txt


[trimmed SIMPLE]

Bobby Sardana wrote:
> 
> I am sure that the appropriate UAC will implement a "security sandbox"

> for both the "execute" and "render" feature set. A properly designed 
> UAC will also allow such
> features to be manually disabled.
> 
> Personally, I like the "execute" feature as it allows new services to 
> be deployed on the UAC.

I agree with those who think this is far too dangerous.

I think a lot more thinking needs to go into disposition types. In any
case, I think they are totally ortogonal to the problem at hand. Rather,
the appropriate requirement for this draft is to simply state that it
must be possible to associate a registered disposition with each URI.

If someone wants to write a separate draft on new disposition
requirements, they should feel free to do so...

-Jonathan R.


-- 
Jonathan D. Rosenberg, Ph.D.            72 Eagle Rock Avenue
Chief Scientist                         First Floor
dynamicsoft                             East Hanover, NJ 07936
jdrosen@dynamicsoft.com                 FAX: (973) 952-5050
http://www.jdrosen.net                  PH:  (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 daemon@optimus.ietf.org  Wed Apr 10 10:08:14 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19961
	for <sipping-archive@odin.ietf.org>; Wed, 10 Apr 2002 10:08:14 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA24289
	for sipping-archive@odin.ietf.org; Wed, 10 Apr 2002 10:08:18 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA23334;
	Wed, 10 Apr 2002 09:57:43 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA23307
	for <sipping@optimus.ietf.org>; Wed, 10 Apr 2002 09:57:40 -0400 (EDT)
Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19515
	for <sipping@ietf.org>; Wed, 10 Apr 2002 09:57:35 -0400 (EDT)
Received: from BOB ([12.230.191.92]) by rwcrmhc53.attbi.com
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20020410135707.MHWR21252.rwcrmhc53.attbi.com@BOB>;
          Wed, 10 Apr 2002 13:57:07 +0000
Reply-To: <seancolson@yahoo.com>
From: "Sean Olson" <seancolson@yahoo.com>
To: "'Beck01, Wolfgang'" <BeckW@t-systems.com>, <sipping@ietf.org>
Subject: RE: [Sipping] draft-olson-sipping-content-indirect-00.txt
Date: Wed, 10 Apr 2002 06:57:16 -0700
Message-ID: <003301c1e097$9fa579b0$6401a8c0@BOB>
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.3416
Importance: Normal
In-Reply-To: <C3F9C806AEC6D5119643000347055E322088BB@G9JNW.mgb01.telekom.de>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

I see where this is going. I will remove the "execute"
disposition. What the text below says, in different terms,
is that it is possible to verify that a CPL script does 
nothing "wrong" and you don't have to worry about a CPL
script taking an infinite amount of resources. There are
several types of executable sources that fit that description.
If you allow CPL, why not allow these? It is really academic
because what we are saying is that we are not going to 
allow a requirement that opens up the door for bad implementations.

/sean

-----Original Message-----
From: Beck01, Wolfgang [mailto:BeckW@t-systems.com] 
Sent: Wednesday, April 10, 2002 1:06 AM
To: seancolson@yahoo.com; sipping@ietf.org
Subject: RE: [Sipping] draft-olson-sipping-content-indirect-00.txt


Sean,
> for now,
> what dangers do you perceive for handling an INVITE,
> or a SUBSCRIBE, or a REFER, or ... ? This is
> roughly equivalent to the problem of handling CPL
> upload. How do you trust the CPL you receive to
> know it is safe to execute? Assuming there is
> an answer to that question, can you apply that
> answer to an "execute" disposition?
Quoting from the CPL draft:
"The CPL is powerful enough to describe a large number of services and
features, but it is limited in power so that it can run safely in
Internet telephony servers. The intention is to make it impossible for
users to do anything more complex (and dangerous) than describing
Internet telephony services. The language is not Turing-complete, and
provides no way to write loops or recursion."


--
Wolfgang Beck
T-Systems Nova GmbH 


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



From daemon@optimus.ietf.org  Wed Apr 10 12:56:52 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25145
	for <sipping-archive@odin.ietf.org>; Wed, 10 Apr 2002 12:56:52 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA05061
	for sipping-archive@odin.ietf.org; Wed, 10 Apr 2002 12:56:54 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA04811;
	Wed, 10 Apr 2002 12:48:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA05410
	for <sipping@optimus.ietf.org>; Wed, 10 Apr 2002 04:06:45 -0400 (EDT)
Received: from mail1.telekom.de (mail1.telekom.de [62.225.183.235])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13483
	for <sipping@ietf.org>; Wed, 10 Apr 2002 04:06:35 -0400 (EDT)
Received: from g9jbr.mgb01.telekom.de by G8SBV.dmz.telekom.de with ESMTP; Wed, 10 Apr 2002 10:04:46 +0200
Received: by G9JBR.mgb01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <2Q8W8N9R>; Wed, 10 Apr 2002 10:06:05 +0200
Message-Id: <C3F9C806AEC6D5119643000347055E322088BB@G9JNW.mgb01.telekom.de>
From: "Beck01, Wolfgang" <BeckW@t-systems.com>
To: seancolson@yahoo.com, sipping@ietf.org
Subject: RE: [Sipping] draft-olson-sipping-content-indirect-00.txt
Date: Wed, 10 Apr 2002 10:06:04 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Sean,
> for now,
> what dangers do you perceive for handling an INVITE,
> or a SUBSCRIBE, or a REFER, or ... ? This is
> roughly equivalent to the problem of handling CPL 
> upload. How do you trust the CPL you receive to
> know it is safe to execute? Assuming there is
> an answer to that question, can you apply that
> answer to an "execute" disposition?
Quoting from the CPL draft:
"The CPL is powerful enough to describe a large number of services and
 features, but it is limited in power so that it can run safely in
Internet telephony servers. The intention is to make it impossible
for users to do anything more complex (and dangerous) than describing
Internet telephony services. The language is not Turing-complete, and
provides no way to write loops or recursion."


--
Wolfgang Beck
T-Systems Nova GmbH 


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



From daemon@optimus.ietf.org  Wed Apr 10 12:57:01 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25162
	for <sipping-archive@odin.ietf.org>; Wed, 10 Apr 2002 12:57:00 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA05075
	for sipping-archive@odin.ietf.org; Wed, 10 Apr 2002 12:57:02 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA04647;
	Wed, 10 Apr 2002 12:44:45 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA05128
	for <sipping@optimus.ietf.org>; Tue, 9 Apr 2002 21:52:21 -0400 (EDT)
Received: from obsoft.com (sdsl-64-139-4-113.dsl.sca.megapath.net [64.139.4.113])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28469
	for <sipping@ietf.org>; Tue, 9 Apr 2002 21:52:18 -0400 (EDT)
Received: from obsoft.com (localhost.localdomain [127.0.0.1])
	by obsoft.com (8.11.6/8.11.6) with ESMTP id g3A1v4t14429;
	Tue, 9 Apr 2002 18:57:04 -0700
Message-ID: <3CB39BF0.4A4435C8@obsoft.com>
Date: Tue, 09 Apr 2002 18:57:04 -0700
From: Bobby Sardana <sardana@obsoft.com>
Organization: ObjectSoftware, Inc
X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: "Beck01, Wolfgang" <BeckW@t-systems.com>
CC: seancolson@yahoo.com, sipping@ietf.org, simple@mailman.dynamicsoft.com
Subject: Re: [Simple] RE: [Sipping] draft-olson-sipping-content-indirect-00.txt
References: <C3F9C806AEC6D5119643000347055E322088B9@G9JNW.mgb01.telekom.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

I am sure that the appropriate UAC will implement a "security sandbox" for both the
"execute" and "render" feature set. A properly designed UAC will also allow such
features to be manually disabled.

Personally, I like the "execute" feature as it allows new services to be deployed on
the UAC.

regards,

Bobby Sardana.
sardana@obsoft.com

"Beck01, Wolfgang" wrote:

> Sean,
>
> disposition "execute" in REQ-2 is very dangerous. A popular E-mail program
> used to have a similar function enabled by default, which resulted
> in a worldwide breakdown of many mail servers. Even "render" might be dangerous, if
> the document uses some language like PostScript or Word macros.
>
> --
> Wolfgang Beck
> T-Systems Nova GmbH
>
> _______________________________________________
> simple mailing list
> simple@mailman.dynamicsoft.com
> http://mailman.dynamicsoft.com/mailman/listinfo/simple



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



From daemon@optimus.ietf.org  Wed Apr 10 14:05:54 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27522
	for <sipping-archive@odin.ietf.org>; Wed, 10 Apr 2002 14:05:54 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA09732
	for sipping-archive@odin.ietf.org; Wed, 10 Apr 2002 14:05:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA08436;
	Wed, 10 Apr 2002 13:54:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA08388
	for <sipping@optimus.ietf.org>; Wed, 10 Apr 2002 13:54:31 -0400 (EDT)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26990
	for <sipping@ietf.org>; Wed, 10 Apr 2002 13:54:26 -0400 (EDT)
Received: from cia.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g3AHsGKP014167;
	Wed, 10 Apr 2002 13:54:16 -0400 (EDT)
Received: from MHAMMER-W2K.cisco.com (hrn2-dhcp-161-44-87-145.cisco.com [161.44.87.145])
	by cia.cisco.com (Mirapoint)
	with ESMTP id AAT65016;
	Wed, 10 Apr 2002 13:48:49 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020410134637.00b97fd8@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 10 Apr 2002 13:53:49 -0400
To: "Yu, James" <james.yu@neustar.biz>
From: Michael Hammer <mhammer@cisco.com>
Subject: RE: [Sipping] draft-yu-tel-url-04.txt comment
Cc: sipping@ietf.org
In-Reply-To: <A83B38C38B3ED6119D3600306E0722D038BF20@dc02.npac.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

James,

That begs the question on whether those parameters should be defined for 
sip URI as well?

Could I then infer that the answer to that question was NO?

Further, unless it knows the local policy on subsequent nodes, a gateway 
should use the tel: URI rather than the sip: URI to assure the least amount 
of opaqueness for those parameters.

Mike


At 12:39 PM 4/10/2002 -0500, Yu, James wrote:
> > I still feel that the use of parameters that are
> > intended to be
> > globally used, within the user part of a sip: URI (which I've
> > heard many
> > times can only be interpreted correctly by the domain after
> > the "@" sign)
> > may be an unintended contradiction.  I don't see a problem
> > with the tel:
> > URI as that does not have the domain construct.
>
>The routing is based on the host info. after "@" first.  The user part is
>then checked when that host receives the message.
>
> >
> > Would an address such as:
> > sip:+1-202-533-1234@sip.abc.com;user=phone;npdi=yes;rn=+1-202-
> > 544-000;cic=+1-6789
> > also be valid or is that prohibited by your draft?
> >
>
>No, it is not allowed because they are not valid url parameters in sip url.


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



From daemon@optimus.ietf.org  Wed Apr 10 19:02:56 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04863
	for <sipping-archive@odin.ietf.org>; Wed, 10 Apr 2002 19:02:55 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA26491
	for sipping-archive@odin.ietf.org; Wed, 10 Apr 2002 19:02:59 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA25785;
	Wed, 10 Apr 2002 18:55:07 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA25754
	for <sipping@optimus.ietf.org>; Wed, 10 Apr 2002 18:55:04 -0400 (EDT)
Received: from bdsl.66.12.12.130.gte.net (bdsl.66.12.12.130.gte.net [66.12.12.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04781
	for <sipping@ietf.org>; Wed, 10 Apr 2002 18:55:00 -0400 (EDT)
Received: from TXDWILLIS2 (bdsl.greycouncil.com [127.0.0.1])
	by bdsl.66.12.12.130.gte.net (8.11.6/8.11.6) with ESMTP id g3AMsWd03902
	for <sipping@ietf.org>; Wed, 10 Apr 2002 17:54:32 -0500
From: "Dean Willis" <dean.willis@softarmor.com>
To: <sipping@ietf.org>
Date: Wed, 10 Apr 2002 17:53:59 -0500
Message-ID: <04b201c1e0e2$9a544810$1c036e3f@TXDWILLIS2>
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.3416
Importance: Normal
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Slides for SIPPING at IETF 53
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit


I think I have posted all the slides I have received at:

http://www.softarmor.com/sipping/meets/ietf53/slides/


Please check -- the final is due into the proceedings people by April
12.

--
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 daemon@optimus.ietf.org  Thu Apr 11 08:25:38 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25317
	for <sipping-archive@odin.ietf.org>; Thu, 11 Apr 2002 08:24:22 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA12853
	for sipping-archive@odin.ietf.org; Thu, 11 Apr 2002 08:18:38 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA08662;
	Thu, 11 Apr 2002 06:32:29 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA08054
	for <sipping@optimus.ietf.org>; Thu, 11 Apr 2002 06:29:51 -0400 (EDT)
Received: from exchange1.nuera.com ([12.105.228.79])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA23566
	for <sipping@ietf.org>; Thu, 11 Apr 2002 06:29:49 -0400 (EDT)
Received: by exchange1.nuera.com with Internet Mail Service (5.5.2653.19)
	id <2HAD2HGP>; Thu, 11 Apr 2002 03:30:29 -0700
Message-ID: <E79883AEA37FD411A58C00508BAC5F4B01D38C5F@exchange1.nuera.com>
From: "Fairlie-Cuninghame, Robert" <rfairlie@nuera.com>
To: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>, sipping@ietf.org
Cc: "'Bert Culpepper'" <bert.culpepper@intervoice-brite.com>
Subject: RE: [Sipping] I-D  ACTION:draft-culpepper-sipping-app-interact-re
	qs-00.txt
Date: Thu, 11 Apr 2002 03:30:25 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Thanks for the comments, very helpful.  Bert Culpepper and myself have
discussed them. Here are our combined responses. Bert please speak up if
I've misrepresented your position or missed anything.

> From: Jonathan Rosenberg
> 
> This is an excellent start at requirements. Some comments on the
> requirements there, and some suggestions for additional requirements:
> 
> R1 reads:
> 
> > The mechanism must support collecting device/user input which 
> >         is associated with an established SIP session but must also 
> >         support collecting device/user input that is outside of any 
> >         established sessions. 
> 
> I am concerned about the security and scope issues about listening for
> device/user input outside of a session. This seems like a
> standards-based approach for implementing the government key input
> snooper.... I know what you had in mind for this (things like service
> activation for call forwarding), but I think that there are 
> better ways
> to do it (web page, anyone?).

I would agree there are better mechanisms for user service interaction
outside of a session.  A web interface is certainly viable and "richer" for
control of CLASS 5-like or PBX-like services. I myself am happy with
dropping this part of the requirement.  On the other hand, many SIP devices
may have no more of a UI than today's common cell phones so is a web-based
mechanism appropriate for these devices?  

> 
> > R5:  A network entity desiring user indications must be able to 
> >         request user indications from another network entity.  The 
> >         entity receiving a request must be able to respond with its 
> >         capability/intent to transmit user indications. 
> 
> We should be more specific here. We have a caller and a 
> callee. I think
> that by "entity" you mean one of those two.

No, we are purposefully not restricting the mechanism to only caller and
callee (or even proxy). So, yes, I agree we need to re-word to explicitly
define. Further discussion later.

> 
> >  R6:  The mechanism must support filtering so that only user 
> >         indications of interest are transmitted. 
> 
> I don't know what this means.

Well, an application that wants only digits should be able to apply a
generate a request so that only it gets digits.  This may help the problem
of "application interaction" and bandwidth.  Agree that filtering is not a
good word - will re-write.

> 
> > R15: The receiving application must be able to detect user activity 
> >         indication loss due to packet loss from received 
> user activity 
> >         indications. 
> 
> I don't know what this means.

Detecting missing indications.  For example, a PIN is transmitted one digit
at a time.  If one message (network packet) gets lost, we want to be able to
determine this at the receiver. Will re-word.

> 
> > D4:  The mechanism should support routing and 
> identification that is 
> >         compatible with use in a SIP-based network. 
> 
> This is too vague to be useful.
> 

Are you suggesting we reword or simply drop ? Can you suggest anything more
useful/specific? 

> 
> Some additional requirements:
> 
> * The mechanism should support devices that possess a UI, and those
> which do not possess a UI

Jonathan can you please explain exactly what you mean by this. My feeling is
that this is the crux of your new requirements, yet I don't have a clear
idea of what you mean by "The mechanism should support devices ... which do
not possess a UI."

By this requirement, do you mean
1) The mechanism should allow an application to present a virtual user
interface and/or the transport of user indications on the virtual interface
(when a device has no physical interface aside from a display and possibly a
touch-screen or pointing device); or
2) the mechanism should allow an application to determine that a device has
no physical interface aside from a display (and possibly a touch-screen or
pointing device) and how that resource is accessed?

These are two very different requirements. Or do you have something entirely
different in mind?

Perhaps it would be best to respond to this point in a separate thread. 

> 
> * The mechanism should be capable of handling UIs from simple screens
> with buttons, to voice input

I'm not sure what the functional requirement you are asking for here (apart
from the fact that the mechanism should be extensible that is mentioned in
the next point): "The mechanism should be capable of handling UI's ... with
voice input?" Are you meaning local recognition software that allows a user
to "say a command" or something similar? [I presume you aren't talking about
voice recog on the application server here.] Surely, this is just another
permutation of mapping some local interface to application specific stimuli?


> 
> * The mechanism should be capable of handling future user interfaces
> that may be defined down the road

R10 was supposed to cover that ...

R10:	The mechanism must be extensible so that some non key-based user
indications can be supported in the future, for instance, sliders, dials or
wheels.

Perhaps it could be broadened. Any suggestions?

> 
> * The mechanism should allow a device to indicate support for multiple
> user interfaces, and allow the application to select which 
> one is to be
> used

Good point.

> 
> * The mechanism should allow a device to indicate relative preferences
> amongst the various user interfaces

OK.

> 
> * The mechanism should support user interfaces which require a new
> content to be presented to the user upon input from the user (i.e.,
> change the screen when a user presses a button)
> 

Hmm, this goes beyond "getting indications a device supports" and is more to
do with "application action in response to input". I'm not sure it is in
scope.

> * The mechanism should support user interfaces where user input can be
> sent to the application without waiting for a response from 
> the previous
> input

Agreed.  A requirement that the mechanism is not limited to stop and wait.
This was what we were aiming at in D3:

D3:	The mechanism should attempt to reduce recovery delays under packet
loss scenarios.

Agree that more specific rewording and strength upgrading is needed.

> 
> * The mechanism should allow the user to interface with multiple user
> interfaces for different applications within the same call 
> (for example,
> a single call may involve a call recording application and a prepaid
> calling application, both of which might support a UI)

Good one, although I'm not sure how this is a requirement on the mechanism
rather than simply how the user locally selects their user interface (which
would be a requirement on how to design a user device, i.e., not in scope).
Each relationship between an application and a user interface would be a
separate subscription. 

> 
> * The mechanism should allow the user to know which application is
> associated with which user interface/input

OK.  (satisfied through authentication/authorization of the SUBSCRIBE?)

> 
> * The mechanism must allow a user to have assurances that the 
> user input
> it is providing is only to applications/servers on the call 
> path between
> caller and callee.

I think this is covered by R16 & R17:

R16:	The mechanism must allow for end-to-end security/privacy between
source and destination.

R17:	Both entities must be able to authenticate each other.

but we will try to re-word it to include this explicitly.

> 
> * The mechanism must work with applications that are both proxy and
> b2bua.

As mentioned in the discussion of R5, the use of the term "network entity"
is purposefully designed to NOT limit the interaction to just proxies or
b2bua's. SIP Event's has no such constraints and I don't see that this
mechanism should either. Will re-word to make clearer our intent. Do you
have a problem with this generalization?

> 
> * The mechanism must not require excessive bandwidth on the 
> access link
> to the device, in order to support mobiles
> 

R3 was meant to cover this ...

R3:	The transport mechanism must be sensitive to the limited bandwidth
constraints of some signaling planes, for instance, reliability through
blind retransmission is not acceptable.

From SIP, we learned that for mobile deployment (ie low bandwidth) it is
better to concentrate on ROHC compression [or other binary encoding schemes
(e.g. XML->ASN.1)] rather than constraining the size/syntax of the actual
message format to the achieve the desired bandwidth constraints. The number
of messages required is much more of a consideration as a design criteria in
this area!

[Aside: we are actually in the process of rewriting our
draft-culpepper-sip-key-events-xx draft to use XML. We originally wrote the
key-events draft to use a much more compact SDP-like syntax but after much
thought, we believe that in the long run an easier to implement XML scheme
is better even at the cost of larger (uncompressed) messages. When bandwidth
is really an issue compression or binary encoding will be used in any case
(and the message body is only one part of the message in any case). ]

We look forward to continuing this discussion.

Regards,

Robert & 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 daemon@optimus.ietf.org  Thu Apr 11 12:03:42 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04436
	for <sipping-archive@odin.ietf.org>; Thu, 11 Apr 2002 12:03:42 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA26969
	for sipping-archive@odin.ietf.org; Thu, 11 Apr 2002 12:03:46 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA21424;
	Thu, 11 Apr 2002 10:58:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA29913
	for <sipping@optimus.ietf.org>; Thu, 11 Apr 2002 03:32:26 -0400 (EDT)
Received: from obsoft.com (sdsl-64-139-4-113.dsl.sca.megapath.net [64.139.4.113])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21426
	for <sipping@ietf.org>; Thu, 11 Apr 2002 03:32:22 -0400 (EDT)
Received: from obsoft.com (localhost.localdomain [127.0.0.1])
	by obsoft.com (8.11.6/8.11.6) with ESMTP id g3B7b8t15790;
	Thu, 11 Apr 2002 00:37:08 -0700
Message-ID: <3CB53D23.554249B4@obsoft.com>
Date: Thu, 11 Apr 2002 00:37:07 -0700
From: Bobby Sardana <sardana@obsoft.com>
Organization: ObjectSoftware, Inc
X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: "Beck01, Wolfgang" <BeckW@t-systems.com>
CC: seancolson@yahoo.com, sipping@ietf.org
Subject: Re: [Simple] RE: [Sipping] draft-olson-sipping-content-indirect-00.txt
References: <C3F9C806AEC6D5119643000347055E322088BC@G9JNW.mgb01.telekom.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

"Beck01, Wolfgang" wrote:

> Bobby Sardana wrote:
> > I am sure that the appropriate UAC will implement a "security sandbox"
> > for both the "execute" and "render" feature set.
>
> Like MS Outlook and mIRC did? One global "I love you.vbs" desaster is enough in
> my opinion. Can you imagine what happens if administrators have to block
> all SIP traffic because of some broken, but widespread implementation?

Initial implementations require a period of time till they are stable and secure.
Primarily a UNIX user, I am aware of many robust functionalities being deployed, via
"execute" feature, to MS Explorer. The key here is deployment aka a mechanism to
deploy features. Provided the "security sandbox" is stable and the underlying
platform does not allow misuse, new services can be downloaded onto the UAC and
executed safely.  Is the underlying platform 100% secure to not allow misuse? This
requires time to mature.

>
> We can scan E-mails for worms and viruses as the receiver won't notice the delay.
> If we have to scan SIP messages, we are in trouble.

Almost all mobile manufacturers have published plans to support J2ME which will
follow similar constraints. Currently in infancy, but the promise still holds and
provides a framework to deploy executable services.

>
>
> > A properly designed UAC
> > will also allow such
> > features to be manually disabled.
>
> After the first major security incident many people will have to
> disable the feature by their organization's rules.
>
> > Personally, I like the "execute" feature as it allows new
> > services to be deployed on
> > the UAC.
>
> As long as a script can't access local data -- like address books --,
> can't access the net and can be limited in it's memory and CPU usage,
> it might be safe. But can such a script still be useful? (This is not a
> rhetorical question).

A simple script could be:

1. On render at UAC, present click to connect. On click, send an INVITE.

To conclude, yes there are constaints as what disposition types that can be
supported with regards to security. But restricting them, because of their past
misuse, should not be a limiting factor in their future adoption.

regards,

Bobby Sardana.
sardana@obsoft.com

>
>
> RfC 2046 spends no less than 2 pages on describing the dangers of PostScript
> files being sent as MIME attachment..
>
> --
> Wolfgang Beck
> T-Systems Nova GmbH



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



From daemon@optimus.ietf.org  Thu Apr 11 14:28:46 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08780
	for <sipping-archive@odin.ietf.org>; Thu, 11 Apr 2002 14:28:46 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA04525
	for sipping-archive@odin.ietf.org; Thu, 11 Apr 2002 14:28:48 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA00881;
	Thu, 11 Apr 2002 13:24:45 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA07866
	for <sipping@optimus.ietf.org>; Wed, 10 Apr 2002 13:40:02 -0400 (EDT)
Received: from pine.neustar.com (pine.neustar.com [209.173.57.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26319
	for <sipping@ietf.org>; Wed, 10 Apr 2002 13:39:52 -0400 (EDT)
Received: from chiimc01.il.neustar.com (chih650b-s3p2.il.neustar.com [209.173.57.65])
	by pine.neustar.com (8.11.0/8.11.0) with ESMTP id g3AHdGZ27136;
	Wed, 10 Apr 2002 12:39:16 -0500
Received: by chiimc01.il.neustar.com with Internet Mail Service (5.5.2653.19)
	id <HGJX5CS1>; Wed, 10 Apr 2002 12:39:11 -0500
Message-ID: <A83B38C38B3ED6119D3600306E0722D038BF20@dc02.npac.com>
From: "Yu, James" <james.yu@neustar.biz>
To: "'Michael Hammer'" <mhammer@cisco.com>
Cc: sipping@ietf.org
Subject: RE: [Sipping] draft-yu-tel-url-04.txt comment
Date: Wed, 10 Apr 2002 12:39:10 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

> I still feel that the use of parameters that are 
> intended to be 
> globally used, within the user part of a sip: URI (which I've 
> heard many 
> times can only be interpreted correctly by the domain after 
> the "@" sign) 
> may be an unintended contradiction.  I don't see a problem 
> with the tel: 
> URI as that does not have the domain construct.

The routing is based on the host info. after "@" first.  The user part is
then checked when that host receives the message.

> 
> Would an address such as:
> sip:+1-202-533-1234@sip.abc.com;user=phone;npdi=yes;rn=+1-202-
> 544-000;cic=+1-6789
> also be valid or is that prohibited by your draft?
> 

No, it is not allowed because they are not valid url parameters in sip url.


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



From daemon@optimus.ietf.org  Thu Apr 11 14:37:57 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09024
	for <sipping-archive@odin.ietf.org>; Thu, 11 Apr 2002 14:37:57 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA05300
	for sipping-archive@odin.ietf.org; Thu, 11 Apr 2002 14:35:36 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA00565;
	Thu, 11 Apr 2002 13:14:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA26885
	for <sipping@optimus.ietf.org>; Thu, 11 Apr 2002 02:35:28 -0400 (EDT)
Received: from mail1.telekom.de (mail1.telekom.de [62.225.183.235])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20805
	for <sipping@ietf.org>; Thu, 11 Apr 2002 02:35:25 -0400 (EDT)
Received: from g9jbr.mgb01.telekom.de by G8SBV.dmz.telekom.de with ESMTP; Thu, 11 Apr 2002 08:33:34 +0200
Received: by G9JBR.mgb01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <2Q8W9KBW>; Thu, 11 Apr 2002 08:34:52 +0200
Message-Id: <C3F9C806AEC6D5119643000347055E322088BC@G9JNW.mgb01.telekom.de>
From: "Beck01, Wolfgang" <BeckW@t-systems.com>
To: sardana@obsoft.com
Cc: seancolson@yahoo.com, sipping@ietf.org
Subject: RE: [Simple] RE: [Sipping] draft-olson-sipping-content-indirect-0
	0.txt
Date: Thu, 11 Apr 2002 08:34:51 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Bobby Sardana wrote:
> I am sure that the appropriate UAC will implement a "security sandbox"
> for both the "execute" and "render" feature set.

Like MS Outlook and mIRC did? One global "I love you.vbs" desaster is enough in
my opinion. Can you imagine what happens if administrators have to block
all SIP traffic because of some broken, but widespread implementation?
We can scan E-mails for worms and viruses as the receiver won't notice the delay.
If we have to scan SIP messages, we are in trouble.

> A properly designed UAC 
> will also allow such
> features to be manually disabled.

After the first major security incident many people will have to
disable the feature by their organization's rules. 

> Personally, I like the "execute" feature as it allows new 
> services to be deployed on
> the UAC.

As long as a script can't access local data -- like address books --,
can't access the net and can be limited in it's memory and CPU usage,
it might be safe. But can such a script still be useful? (This is not a
rhetorical question).

RfC 2046 spends no less than 2 pages on describing the dangers of PostScript
files being sent as MIME attachment..

--
Wolfgang Beck
T-Systems Nova GmbH 




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



From daemon@optimus.ietf.org  Thu Apr 11 15:21:29 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10403
	for <sipping-archive@odin.ietf.org>; Thu, 11 Apr 2002 15:21:29 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA07577
	for sipping-archive@odin.ietf.org; Thu, 11 Apr 2002 15:21:31 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA05425;
	Thu, 11 Apr 2002 14:38:11 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA05394
	for <sipping@optimus.ietf.org>; Thu, 11 Apr 2002 14:38:04 -0400 (EDT)
Received: from crash.dfw.dynamicsoft.com ([63.110.3.64])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09037
	for <sipping@ietf.org>; Thu, 11 Apr 2002 14:38:01 -0400 (EDT)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by crash.dfw.dynamicsoft.com (8.11.6/8.11.6) with ESMTP id g3BIfAh13781;
	Thu, 11 Apr 2002 13:41:11 -0500
Subject: RE: [Sipping] draft-yu-tel-url-04.txt comment
From: Robert Sparks <rsparks@dynamicsoft.com>
To: "Yu, James" <james.yu@neustar.biz>
Cc: "'Michael Hammer'" <mhammer@cisco.com>, sipping@ietf.org
In-Reply-To: <A83B38C38B3ED6119D3600306E0722D038BF20@dc02.npac.com>
References: <A83B38C38B3ED6119D3600306E0722D038BF20@dc02.npac.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.3 
Date: 11 Apr 2002 13:36:51 -0500
Message-Id: <1018550213.1325.21.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

On Wed, 2002-04-10 at 12:39, Yu, James wrote:
> > I still feel that the use of parameters that are 
> > intended to be 
> > globally used, within the user part of a sip: URI (which I've 
> > heard many 
> > times can only be interpreted correctly by the domain after 
> > the "@" sign) 
> > may be an unintended contradiction.  I don't see a problem 
> > with the tel: 
> > URI as that does not have the domain construct.
> 
> The routing is based on the host info. after "@" first.  The user part is
> then checked when that host receives the message.
> 
> > 
> > Would an address such as:
> > sip:+1-202-533-1234@sip.abc.com;user=phone;npdi=yes;rn=+1-202-
> > 544-000;cic=+1-6789
> > also be valid or is that prohibited by your draft?
> > 
> 
> No, it is not allowed because they are not valid url parameters in sip url.

That's not quite right. They are very much allowed. They just don't mean
anything - everything will treat them as unknown SIP URI parameters and
ignore them for anything but URI comparision.

> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 daemon@optimus.ietf.org  Thu Apr 11 17:10:55 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15099
	for <sipping-archive@odin.ietf.org>; Thu, 11 Apr 2002 17:10:55 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA13629
	for sipping-archive@odin.ietf.org; Thu, 11 Apr 2002 17:10:58 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA10511;
	Thu, 11 Apr 2002 16:16:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA10480
	for <sipping@optimus.ietf.org>; Thu, 11 Apr 2002 16:16:48 -0400 (EDT)
Received: from bdsl.66.12.12.130.gte.net (bdsl.66.12.12.130.gte.net [66.12.12.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12634;
	Thu, 11 Apr 2002 16:16:43 -0400 (EDT)
Received: from TXDWILLIS2 (bdsl.greycouncil.com [127.0.0.1])
	by bdsl.66.12.12.130.gte.net (8.11.6/8.11.6) with ESMTP id g3BKFwd11875;
	Thu, 11 Apr 2002 15:15:58 -0500
From: "Dean Willis" <dwillis@dynamicsoft.com>
To: <sipping@ietf.org>, <minutes@ietf.org>
Date: Thu, 11 Apr 2002 15:15:23 -0500
Message-ID: <007801c1e195$9c7cdd10$1c036e3f@TXDWILLIS2>
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.3416
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Minutes, SIPPING Working Group, IETF53
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit


Also on web site at:
http://www.softarmor.com/sipping/meets/ietf53/notes/minutes.html


Minutes, SIPPING Working Group, IETF 53

Session 1
------------

Chairs announce "Note Well" 2026 provisions. 

Agenda Bash: 
     No Comments 

Status: 
     * SIP-T and ISUP-SIP -- ready to resubmit after blackout 

     * SIP Overlap Dialing -- should be ready for WGLC next month. 

     * Requirements for Deaf -- Hum on objections, none noted, will
     move to last call.

     * E164 and ENUM to discuss in ENUM WG

     * cc-transfer -- depends on refer, replaces, has security concerns 

     * Fax -- new comments from ITU from group review, informal
     liaison reported, formal channels expected to be exercised
     soon. ITU has essentially combined and cleaned up T.38. They want
     to reference this doc, and are happy with it being a a BCP
     instead of informational. They wish to further request
     collaboration and notification of changes. They also suggest
     splitting fax and modem into two separate documents.

     * Call Flows BCP -- needs updates to torture tests, do we need
     some bis-specific torture tests? We also need volunteers for
     formal review on a section-by-section basis, target WGLC for last
     of May.

Service Examples Draft, Alan Johnston: 

     * Updated for bis in this release. 

     * Open issues with getting setup info for transfers, etc. Suggest
     doing the development of the SIP events package proposed in
     draft-rosenberg-sip-call-package.

     * Several issues with Replaces resolved, especially around
     transfer of call. Main one is use of Require: replaces to verify
     capability of foreign node.

     * Join: Some primitive with a function like the
     draft-mahy-join-and-fork "Join" header required to complete
     single-line-extension.

     * Caller Prefs: How should we demonstrate this stuff in call
     flows?

Multiparty Apps Framework Discussion, Rohan Mahy: 

     * The "new" cc-framework is an attempt to bring together
     categories and descriptions and working groups status of various
     drafts across SIP, SIPPING, and individual contributions.

     * Question to group: Is this approach "what we are looking
     for". General response seems favorable, and the document editor
     will proceed.

Conferencing Requirements, Orit Levin and Henning Schulzrinne: 

     draft-levin-sip-for-video: Objectives are a BCP guide for
     building "multimedia" conferencing apps, with similar user
     interface and clear migration path from voice-only connections
     using basic non-extended SIP UAs.

     Stuff in many WGs: * Call control in SIPPING * Capabilities
     exchange/declaration in MMUSIC * T.120 and other app integration
     in MMUSIC * Media control in AVT * Conferencing and Floor Control
     models in SIPPING/SIP

     Media Control is viewed as critical open issue. Where should work
     be done?

     Comment from audience: Sounds like exactly the original charter
     of the MMUSIC working group. Only difference is requirement that
     simple SIP client be able to participate in session. Also
     suggestion that "control channel" is just another media in the
     session, and should be treated as such by the system.

     Comment from audience: The control channel is sort of like but
     not completely like media.

     Suggested approach: do a framework draft, maps requirements to
     solutions using existing drafts andapproaches as possible,
     closely related to multi-party application framework.

     Question from audience: presumes certain boundary around "what a
     conferencing application is", presumably from classic
     conferencing model. What about other approaches, such as
     collaborative editing models?

     Requirements for Conference Control, Henning Schulzrinne: Suggest
     focus on media-independent control for range of conference models
     with core property of single "media choke point". Functional
     taxonomy presented in slides. List of floor control primitives in
     slides.

     Comment from audience: Group membership management is very
     similar to authorization policy for subscription in Events
     structure.

     This problem space seems to have commonalities with SIP:
     asynchronous event functions and synchronous command functions to
     "the conference" (as opposed to commands to participants).

     Work division model proposed in slides. 

     Comments from audience: 

     * Shouldn't split asynchronous events from synchronous commands. 

     * This work spans a lot of groups but isn't in any specific one. 

     * Must make efforts to mesh well across many groups 

     * Missing something in the problem statement: We have not
     addressed of graph building, leaving us with star and mesh,
     neither of which scales. Media transmission along a graph is
     something we're not treating well. Once we can do that, if can
     think about controlling and eventing along the graph. Suggestion
     we decide the problem along these lines.


     -- Response: This is a big effort. With the scoping suggested, we
     have a constituency. Don't want to repeat the last 10 years of
     MMUSIC.

     * Request to get decision on work plan made soon.  Chair
     position: There is clearly interest. We have to work out issues
     of scope and jurisdiction.


Request History Requirements, Mary Barnes: 

     Several examples presented of SIP call diagrams in which there
     may not be enough information in current SIP to make appropriate
     state analyses in various nodes.

     Issues from mailing list discussed in slides. 

     Comments: 

     * the general problem is not one of information loss. Propagating
     information upstream is oen of the problems. The second piece is
     "telling someone why they got a request". this is much more like
     caller pref sand identity issues.

     * need to decide when to throw information away. 

     * may be important problem here, but where? we're getting into
     the identity issue again. We should work on this and try to find
     general problem. there is a profound slippery slope problem.

     * discussion that there is a big difference between the lack of
     information at a random proxy, and the failure of a specific one.

     * It's the systems that manage identities, not the endpoints,
     that need to have knowledge.

     * Need to clearly delineate between "what happened to the
     request" and "what you want the next hop to do".

     Hum for continue working: loud. Open issue with splitting it into
     two pieces.


SIP Telephony Device Requirements, Dan Petrie: 

    tries to formulate requirements for phone-like devices on fixed
    and wireless (not 3G) networks. Includes requirements for device
    configuration.

    Splits issues: 

    1) Configuration discovery -- maybe inside of SIP? 

    2) UA enrollment -- inside of SIP 

    3) Configuration retrieval -- outside of SIP 

    4) Configuration change notification -- may be SIP? 5)
    configuration change upload (phone to server0 -- outside of sip

     Discussion: Use of SIP for configuration discovery and change
     notification. Comment from audience: seems to be a lack of
     understanding and analysis of other protocols for doing
     this. Plea for simplifying the administrator role by reducing
     number of configuration mechanisms. Comment: Didn't we decide not
     to do this two years ago? What has changed? Ans. We have now
     clarified between data transfer (not SIP) and SIP
     identity-related discovery and notification issues. Comment:
     there has been some analysis of SNMP as not adequate. Comment
     from AD: there ARE other conifguration protocols. This would be a
     very hard sell. chair action: defer to list. Hum for in/out of
     scope slightly weighted towards in scope.

Tel: URL enhancement work, Jon Peterson 

     Work is probably moving to iptel group. Please read rfc2806 bis
     and comment ASAP.


Emergency Services discussion, Henning Schulzrinne, Mike Pierce: 

SIP Resource Priority, Henning Schulzrinne: 

     Establish priority when competing for terminating UA
     resources. This is not "network priority", more like an SMTP
     priority flag. Open issue: Do we need an Accept tag?

     Comment: IEPREP group is working on requirements. We should hold
     up priority header until IEPREP has considered more
     requirements. At least we should let IEPREP look at it and see if
     it applies.

     Comment: There are probably privacy and security requirements for
     use of this header needed to prevent SPAM. Security requirements
     in draft are probably not adequate.

     Comment: Needs to be discussion of WHO will be looking at this
     header.

SOS, Henning Schulzrinne: 

     Issue on IANA considerations for reserving names such as
     "SOS@domain".

     Comment: happy to have a BCP saying "SOS is a reserved word" but
     this is not a solution for e911 and we have to be careful that
     this is understood.  Comment: We should use MAYDAY or PANPAN
     instead of SOS.  User Application Control: Bert Culpepper:
     Assumptions and requirements given in slides.

     Open issues: 

     1) What should the mechanism be: Is it SIP? 

     2) IS SIP Events framework appropriate? 

     3) If so, what should payload format be? 

     Comment: If we require people to subscribe, we need to tell them
     WHERE to subscribe Comment: Would like to express higher-level
     semantics than just key scan-codes. For example "jump left three
     feet and shoot" instead of "4,4,4,5" Comment: This is much more
     like a markup problem. Maybe we could provide a standard DTD for
     keys, or perhaps dynamically loaded for custom mappings.
     Comment: Is a stop-and-wait protocol adequate?  Comment:
     Mechanism should be more extensible than just keys, but this is a
     good starting point.  Comment: We don't want to reinvent X or
     VNC.  Comment: Two sets of requirements: delivery, and
     content. These should be dealt with seperately.  Comment:
     Previous questioner asserted difficulty with knowing semantics,
     but a markup approach could solve this.  Comment: There may not
     be a human at the UA, so if you don't have semantic awareness at
     the UA, you prevent useful interaction.  Comment: Current model
     of markup does not solve two-directional question of "what the
     device possesses" as well as the "what are the semantics".
     Chairs: hum for interest? High level of general interested
     indicated. Feed changes in requirements into Bert.


PUBLISH Requirements, Robert Sparks: 

     Covers Donovan's requirements draft. Slides review requirements
     from Donovan draft. Review Stucker draft proposing solution to
     those requirements. Presents discussion of requirements
     abstracted from protocol proposals 1) Binding to SIP identities,
     and 2) Getting the information to the node responsible for the
     application associated with the SIP identity.

     Question: Do we agree we need to meet these requirements?
     Comment: Calling it a "publish" mechanism is semantically leading
     and should be avoided.  Comment: What are the kind of issues that
     would help us decide whether this needs/not to be SIP. Is it a
     single server or a server farm? Does it need to be reliably
     available to more than one place? Comment" this is same as
     REGISTER problem.  Comment: Skeptical if there is such a thing as
     a "generic upload requirement". Generally, this is more like an
     operation against a network object. This is consistent with SOAP
     or RPC.  Comment: We should look at what we know, determine the
     specific requirements, and go from there.  Comment: Whether stuff
     uploaded is merged with an application or used en-bloc is up to
     the application, but a generic mechanism should be doable.


Session 2
-----------

Agenda Bash:
    * No Issues

Accounting/AAA Systems, Bernard Aboba:

    Slides describe requirements of real-world accounting
    requirements, including reliability, security, current issues with
    RADIUS.

    Current issues with RADIUS include:
	- backoff unspecified
	- failover unspecified
	- application layer acknowledgement missing
	- undefined proxy behavior
	- no error messages prevent intelligent failure response
	- transport security has no confidentiality, known attacks
	- replay protection only in post-processing
	- no object security, MITM open

    Alternatives discussed including SNMP, DIAMETER
    
    Question: Why couldn't we use Web Services model and XML over
    secure transport? Answer: accounting semantics are undefined. It
    could be done, but hasn't yet.
    Chair: We had this conversation in order to help us understand
    AAA requirements.
    Question: There are existing systems usually in place
    (RADIUS). Why are we being blocked from working with them?
    Proposal from chairs: Should we be able to do capacity planning
    and non-usage sensitive billing? Consensus yes. Is time sensitive
    billing in scope? Chair's
    Question: We have real requirements -- why are we arguing about
    which grid-box from RFC 2975 we're going to try and fill?
     
    Question: Time-sensitive billing is a requirement from 3G. Whether
    it is interdomain is option. Are we talking about the other two
    A's?
    
    Comment: We should at least consider what has been accomplished with
    a non-IETF protocol in real-world billing systems.
    Question: DIAMETER seems to be the implicit assumption. RADIUS may
    be obsolete, but should we, instead of arguing requirements, just
    do a standards-track spec for using DIAMETER and an informational
    track for using one or more of the existing protocols like RADIUS?
    Allison: There will be resistance to any RADIUS solution on an RFC
    track. Why not just use SNMPv3? Chair comment that that doesn't
    appear to be a good fit for people are doing.
    Question: When will DIAMETER exist? Spec editor reports that major
    issues are done, a few editorial and security considerations
    remain for documentation, otherwise ready to go.
    Observation: RADIUS is widely deployed in accounting for dialup
    internet access. Many providers combine dial=up with VoIP and have
    incentive to use same accounting infrastructure. It would be
    useful for us to document any vulnerabilities of RADIUS that apply
    to SIP that did not apply to dialup. Response: If you're doing
    dialup, you're probably not in usage sensitive billing or at least
    don't have the same requirements as VoIP.
    Comment: It is clear that we are driving while looking in
    rear-view mirror, trying to retrofit VoIP billing on RADIUS. It is
    clear that we have to look at record format (XML), secure
    transport (TLS), and look forward instead of backward.
    Comment: We should keep in mind that we have a lot of work to do
    with things like record transfer and post-processing stuff
    independent of record formats and the like.

Other DCS Drafts:

  draft-scsgroup-sip-proxy-proxy-06.txt:
    Slides report status and background. Need to update for sipchange
    process as ind. informational (P-header, no options tag)

  DCS architecture draft:
    Slides report status. Similar sipchange issues.
    Chairs poll for reading of drafts, and for concerns on informational
    publishing. Comment that we need to know if there are any
intellectual
    property claims, answer "probably".
    Question? Will we apply sipchange? yes.
    Poll for consensus to proceed -- no objections raised.


Report on 3GPP Ad-Hoc from 20Mar02 (Miguel Garcia):
    Path header: current two drafts seem reasonable.
    Privacy: Several problems, no clear resolution yet.
    Dialed URL: (Target Address-of-Record): P-header approach seems
    feasible in the short term, may be able to use history or other
    mechanism in the future. EdNote: This could also be considered
    as something like a "display name" for the request-URI.
    3GPP XML Body: Moving most content to P-headers. 
    Security items as resolved in SIP.

Event Packages Procedure (Rohan Mahy):
    Chairs: Do we need a separate guidelines document for the authors
    of SIP Events?
    Question: Do we have a template that somebody to use to pre-screen
    their work for completeness? ENUM put together a template for
    service field definition. Is the stuff in the sip-events RFC
    adequate? Chairs poll for sufficiency: strong consensus, current
    guidance is adequate.



Call and Conference Package (Jonathan Rosenberg):

    Slides review proposal from drafts and changes including examples,
    bis-alignment, addition of direction attribute, removal of To-
    headers in favor of explicit coding, removal of floor control.
    Next steps: at least one implementation known. Need to make sure
    scope is right and data formats have all information we need. Will
    split document into two packages (dialog and conference). Propose
    adding this effort as SIPPING WG item. 

    Comment: AS we start defining XML event packages, it looks like the
    world has moved on beyond DTD definitions into schema-based
    definitions. We should make a similar evolution in schema
    definition. Chairs: This is reasonable. 
    Comment: This framework is needed for distributed call control and
    the work is supported by the speaker. Several confirming comments
    made. 

    Comment from chair (Rosen): Do we want to do this definition in
    SIPPING or is this something that should be done in SIP? This is a
    "piece" of the problem. It would be really nice to have a bigger
    view. Have we finished the requirements? Response: It's nice to
    understand big picture, but also nice to make incremental
    progress. Chair (Mahy) we need to follow procedure, but we have
    some requirements, can we proceed? Author: It would be nice to
    have some discussion of requirements on data format. This should
    be reflected one-to-one in the result document, so can be done in
    conjunction instead of as a separate effort. This is really a
    "piece of framework". General discussion follows. Poll for
    call-info package, none opposed. Poll for conference info package:
    none opposed.

Future Work (chairs):

    Proposals in slides.

    3PCC BCP: Never an extension because it was doable in straight
    SIP, mostly. This has been greatly improved in bis with o/a and
    update. So the proposed work is to discuss questionable alternatives
and
    recommend best practices from the known alternatives. This is not
    intended to say that 3PCC itself is a better practice than
    distributed. Poll for adoption: no objections.

    Message waiting: Poll for adoption as WG item: no
    objections. Question: package seems to want to do more than voice
    message waiting. Author response: will adjust to workgroup
    consensus. Question: Where do we document interworking this with
    ISDN?

    Content indirection and reason codes: Will continue requirements
    development.

    Opaque URI usage: Proposal to do informational draft on guidelines
    for use of opaque URIs.

    MSURI draft: Propose to either roll into Opaque URI or publish as
    individual informational or do as WG effort. Comment: We haven't
    really as a group figured out how to do this osrt of thing. Would
    like to see something that steps back, looks at broad
    requirements, before delving into solutions. The usage of URIs as
    service indicators is one of the biggest architectural problems
    we face. Counter: This is too large an approach, and we need a
    solution today. Comment: It is important to define a framework for
    discovery. Comment: Unless there is someone pushing to do this
    analysis, the result is likely useless. It is better to proceed by
    just allowing people to document different approaches and label
    them with applicability statements. We don't know how big the
    problem space is, and it is likely to be very large. Comment: we
    need to define a schema. Comment: we need to do requirements, not
    jump into solutions. Comment: we need services, concern that if we
    stall on URI conventions that we'll have problems. Eric Burger
    volunteers to do framework. Comment: Suggest researching
    requirements and publishing msuri as an individual in the
    meantime. Chair comment: would like to see framework or
    requirements first. Poll: SIPPING WG to develop guideline document
    on use of URIs. Result - one opposed.

    SIP VXML: 

    NAT Scenarios Draft: Should we do it as WG efforts? Comment:
    Dealing with NATS is an enormous tar pit. There are many options
    that apply to different scenarios. Discussion on scope
    follows. Comments: it would be good to bidirectionally align this
    with the "unsafe" framework document. Poll: Adopt this as wg item
    leading to informational rfc: None opposed.
    

Emergency Services Discussion (Mike Pierce):

    Slides review status of emergency services draft and relation to
    IEPREP work.  Proposal from chair: Can authors work with authors
    of resource priority header on SIP requirements and move other
    work to ieprep? Answer: That is how the authors are currently
    proceeding.


Open Mic:

    How do we deal with the approval policy for 3PCC stuff like
    accepting REFERs, etc. Ans: should be in usage drafts, if not send
    text.

    Device Requirements: We didn't get to this the other day. Where do
    we stand on it? Comment: There has been some discussion that there
    may be other venues for operational discussions, such as SIP
    forums. Comment: Ideal world would be: IETF realized long ago that
    device configuration is a problem that will be universally faced
    and have developed a "plug-in" framework (like MIBs) for doing
    so. This didn't happen. Comment: discussed taking current config
    document and adding discussion and applicability of things like
    SNMP, ACAP, etc. Comment: The OAM area has committed to reading
    the document and working with the author and other interested
    parties. Comment: This is "right now" problem. We have all the
    tools we need. We need to write down an interop doc. Comment: We
    have a split between framework and content. Can we go forward with
    the definition of the data independent of the delivery mechanism?
    Request from chair: Can we continue this as individual work,
    discussed on SIPPING list, until more clarity?. No
    opposition. Comment: SIP end devices are a whole industry,
    managed by housewives to sysadmins with massive systems. Please
    think about it.

    Settlement: Idea to generate discussion. There might be an
    opportunity to define a generic challenge-response settlement
    architecture framework. Comment: How about a response code that
    says "Payment required -- here's an invoice" something like a
    401/407 challenge, with the re-INVITE to contain payment
    information. Comment: This screams for requirements development in
    the SIPPING process, need to scope the problem, describe some
    scenarios, and send text.

    AAA: Earlier presentation did not explore large solution space now
    available. What we can we do if we bring in web services and
    similar technologies? Consider reviving interdomain settlement/osp
    drafts earlier "out of scoped" in SIP. Chair request: List
    discussion on proposal and approach -- "how can we get something
    done within IETF?" Question: Do you see this work diverging into
    user-service/provider and provider/provider channels? Response:
    Mostly between providers. The important thing is the trust
    function or clearinghouse that enables any-any business
    relationships.


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



From daemon@optimus.ietf.org  Fri Apr 12 04:40:46 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21789
	for <sipping-archive@odin.ietf.org>; Fri, 12 Apr 2002 04:40:46 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA01573
	for sipping-archive@odin.ietf.org; Fri, 12 Apr 2002 04:40:48 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA28694;
	Fri, 12 Apr 2002 03:45:47 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA28664
	for <sipping@optimus.ietf.org>; Fri, 12 Apr 2002 03:45:41 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17190
	for <sipping@ietf.org>; Fri, 12 Apr 2002 03:45:37 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g3C7jas7001663;
	Fri, 12 Apr 2002 09:45:36 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.12])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g3C7jYUD024555;
	Fri, 12 Apr 2002 10:45:34 +0300 (EET DST)
Message-ID: <3CB690A4.586ABDB1@lmf.ericsson.se>
Date: Fri, 12 Apr 2002 10:45:40 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Robert Sparks <rsparks@dynamicsoft.com>
CC: "Yu, James" <james.yu@neustar.biz>, "'Michael Hammer'" <mhammer@cisco.com>,
        sipping@ietf.org
Subject: Re: [Sipping] draft-yu-tel-url-04.txt comment
References: <A83B38C38B3ED6119D3600306E0722D038BF20@dc02.npac.com> <1018550213.1325.21.camel@localhost.localdomain>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit


Hi,

> >>I still feel that the use of parameters that are  intended to be
> >>globally used, within the user part of a sip: URI (which I've
> >>heard many times can only be interpreted correctly by the domain after
> >>the "@" sign) may be an unintended contradiction.  I don't see a problem
> >>with the tel: URI as that does not have the domain construct.
> >
> >The routing is based on the host info. after "@" first.  The user part is
> >then checked when that host receives the message.
> >
> >>
> >>Would an address such as:
> >>sip:+1-202-533-1234@sip.abc.com;user=phone;npdi=yes;rn=+1-202-
> >>544-000;cic=+1-6789 also be valid or is that prohibited by your draft?
> >
> >No, it is not allowed because they are not valid url parameters in sip url.
>
> That's not quite right. They are very much allowed. They just don't mean
> anything - everything will treat them as unknown SIP URI parameters and
> ignore them for anything but URI comparision.

This issue has been discussed before, and the following is what I also said back
then.

Yes, the ABNF does allow the ";" character in the user-part. However, the SIP-URI
does not specify specific user-part  parameters, so if you send
"sip:+1-202-533-1234;npdi=yes@sip.abc.com" to a server which doesn't understand
the extension it's going to treat the whole "+1-202-533-1234;npdi=yes" eg as a
phone number, and in case of a PSTN GW try to route that "number" to the PSTN
network (which, of course, won't work, since the ";npdi=yes" part can't be routed
as a phone number).

So, I very much support to use the parameters in the host-part instead. Then, if
a server doesn't understand them it will simply ignore them, as specified in the
standard.

Regards,

Christer Holmberg
Ericsson Finland







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


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



From daemon@optimus.ietf.org  Fri Apr 12 09:33:25 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21323
	for <sipping-archive@odin.ietf.org>; Fri, 12 Apr 2002 09:33:25 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA16073
	for sipping-archive@odin.ietf.org; Fri, 12 Apr 2002 09:33:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA11475;
	Fri, 12 Apr 2002 08:06:29 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA11434
	for <sipping@optimus.ietf.org>; Fri, 12 Apr 2002 08:06:21 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13220
	for <sipping@ietf.org>; Fri, 12 Apr 2002 08:06:18 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g3CC6Fs7027340;
	Fri, 12 Apr 2002 14:06:15 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.12])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g3CC6EUD010030;
	Fri, 12 Apr 2002 15:06:14 +0300 (EET DST)
Message-ID: <3CB6CDBD.BC3FB2E5@lmf.ericsson.se>
Date: Fri, 12 Apr 2002 15:06:21 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Yu, James" <james.yu@neustar.biz>
CC: "'Robert Sparks'" <rsparks@dynamicsoft.com>,
        "'Michael Hammer'" <mhammer@cisco.com>, sipping@ietf.org
Subject: Re: [Sipping] draft-yu-tel-url-04.txt comment
References: <A83B38C38B3ED6119D3600306E0722D038BF2D@dc02.npac.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit


Hi,

What do you mean by "invalid url parameters" and "they don't mean anything"?
The spec allows one to specify any kind of uri parameter (other-param in the
ABNF syntax). Any implementation supporting the draft-yu-tel-url-04.txt will
treat them exactly the same way they would support them if they were in the
user-part, wouldn't it? They would only "mean nothing" to implementations
not supporting the draft...

Regards,

Christer Holmberg
Ericsson Finland


> Thanks.  I mean that they are "invalid url parameters."
>
> James
>
> > -----Original Message-----
> > From: Robert Sparks [mailto:rsparks@dynamicsoft.com]
> > Sent: Thursday, April 11, 2002 2:37 PM
> > To: Yu, James
> > Cc: 'Michael Hammer'; sipping@ietf.org
> > Subject: RE: [Sipping] draft-yu-tel-url-04.txt comment
> >
> >
> > On Wed, 2002-04-10 at 12:39, Yu, James wrote:
> > > > I still feel that the use of parameters that are
> > > > intended to be
> > > > globally used, within the user part of a sip: URI (which I've
> > > > heard many
> > > > times can only be interpreted correctly by the domain after
> > > > the "@" sign)
> > > > may be an unintended contradiction.  I don't see a problem
> > > > with the tel:
> > > > URI as that does not have the domain construct.
> > >
> > > The routing is based on the host info. after "@" first.
> > The user part is
> > > then checked when that host receives the message.
> > >
> > > >
> > > > Would an address such as:
> > > > sip:+1-202-533-1234@sip.abc.com;user=phone;npdi=yes;rn=+1-202-
> > > > 544-000;cic=+1-6789
> > > > also be valid or is that prohibited by your draft?
> > > >
> > >
> > > No, it is not allowed because they are not valid url
> > parameters in sip url.
> >
> > That's not quite right. They are very much allowed. They just
> > don't mean
> > anything - everything will treat them as unknown SIP URI
> > parameters and
> > ignore them for anything but URI comparision.
> >
> > >
> > >
> > > _______________________________________________
> > > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > > This list is for NEW development of the 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 daemon@optimus.ietf.org  Fri Apr 12 09:33:32 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21339
	for <sipping-archive@odin.ietf.org>; Fri, 12 Apr 2002 09:33:27 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA16075
	for sipping-archive@odin.ietf.org; Fri, 12 Apr 2002 09:33:28 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA10571;
	Fri, 12 Apr 2002 07:56:39 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA06282
	for <sipping@optimus.ietf.org>; Thu, 11 Apr 2002 15:00:50 -0400 (EDT)
Received: from oak.neustar.com (oak.neustar.com [209.173.53.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09647
	for <sipping@ietf.org>; Thu, 11 Apr 2002 15:00:47 -0400 (EDT)
Received: from chiimc01.il.neustar.com (stih650b-s1p2.va.neustar.com [209.173.53.65])
	by oak.neustar.com (8.11.0/8.11.0) with ESMTP id g3BIxx801897;
	Thu, 11 Apr 2002 14:59:59 -0400
Received: by chiimc01.il.neustar.com with Internet Mail Service (5.5.2653.19)
	id <HGJX5QHV>; Thu, 11 Apr 2002 13:59:54 -0500
Message-ID: <A83B38C38B3ED6119D3600306E0722D038BF2D@dc02.npac.com>
From: "Yu, James" <james.yu@neustar.biz>
To: "'Robert Sparks'" <rsparks@dynamicsoft.com>
Cc: "'Michael Hammer'" <mhammer@cisco.com>, sipping@ietf.org
Subject: RE: [Sipping] draft-yu-tel-url-04.txt comment
Date: Thu, 11 Apr 2002 13:59:52 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Robert,

Thanks.  I mean that they are "invalid url parameters."

James

> -----Original Message-----
> From: Robert Sparks [mailto:rsparks@dynamicsoft.com]
> Sent: Thursday, April 11, 2002 2:37 PM
> To: Yu, James
> Cc: 'Michael Hammer'; sipping@ietf.org
> Subject: RE: [Sipping] draft-yu-tel-url-04.txt comment
> 
> 
> On Wed, 2002-04-10 at 12:39, Yu, James wrote:
> > > I still feel that the use of parameters that are 
> > > intended to be 
> > > globally used, within the user part of a sip: URI (which I've 
> > > heard many 
> > > times can only be interpreted correctly by the domain after 
> > > the "@" sign) 
> > > may be an unintended contradiction.  I don't see a problem 
> > > with the tel: 
> > > URI as that does not have the domain construct.
> > 
> > The routing is based on the host info. after "@" first.  
> The user part is
> > then checked when that host receives the message.
> > 
> > > 
> > > Would an address such as:
> > > sip:+1-202-533-1234@sip.abc.com;user=phone;npdi=yes;rn=+1-202-
> > > 544-000;cic=+1-6789
> > > also be valid or is that prohibited by your draft?
> > > 
> > 
> > No, it is not allowed because they are not valid url 
> parameters in sip url.
> 
> That's not quite right. They are very much allowed. They just 
> don't mean
> anything - everything will treat them as unknown SIP URI 
> parameters and
> ignore them for anything but URI comparision.
> 
> > 
> > 
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the 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 daemon@ns.ietf.org  Fri Apr 12 15:47:43 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02064
	for <sipping-archive@odin.ietf.org>; Fri, 12 Apr 2002 15:47:42 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA08318
	for sipping-archive@odin.ietf.org; Fri, 12 Apr 2002 15:40:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA04969;
	Fri, 12 Apr 2002 14:52:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA04933
	for <sipping@ns.ietf.org>; Fri, 12 Apr 2002 14:52:32 -0400 (EDT)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00352
	for <sipping@ietf.org>; Fri, 12 Apr 2002 14:52:29 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g3CIpjiL020152
	for <sipping@ietf.org>; Fri, 12 Apr 2002 11:51:45 -0700 (PDT)
Received: from localhost (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint)
	with ESMTP id ACV60096;
	Fri, 12 Apr 2002 11:52:00 -0700 (PDT)
Date: Fri, 12 Apr 2002 11:49:11 -0700 (Pacific Daylight Time)
From: Rohan Mahy <rohan@cisco.com>
To: sipping@ietf.org
Message-ID: <Pine.WNT.4.44.0204121147410.-360391@chorizo.rapidconvergence.com>
X-X-Sender: rmahy@imop.cisco.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Sipping] reminder to review call flows
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Hi Folks,

As a reminder, WGLC for call flows is scheduled to end April 19th.  Please
contact Alan Johnston (alan.johnston@wcom.com) to volunteer to review a
section.

thanks,
-rohan



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



From daemon@ns.ietf.org  Fri Apr 12 16:23:54 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03011
	for <sipping-archive@odin.ietf.org>; Fri, 12 Apr 2002 16:23:54 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA10804
	for sipping-archive@odin.ietf.org; Fri, 12 Apr 2002 16:23:56 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA08587;
	Fri, 12 Apr 2002 15:46:40 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA08556
	for <sipping@ns.ietf.org>; Fri, 12 Apr 2002 15:46:37 -0400 (EDT)
Received: from magus.nostrum.com (root@magus.nostrum.com [66.119.225.66])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02008
	for <sipping@ietf.org>; Fri, 12 Apr 2002 15:46:34 -0400 (EDT)
Received: from txbcampbell (root@magus.nostrum.com [66.119.225.66])
	by magus.nostrum.com (8.11.0/8.11.0) with SMTP id g3CJkaX70663
	for <sipping@ietf.org>; Fri, 12 Apr 2002 14:46:36 -0500 (CDT)
From: "Ben Campbell" <bcampbell@dynamicsoft.com>
To: "Sipping" <sipping@ietf.org>
Date: Fri, 12 Apr 2002 14:46:21 -0500
Message-ID: <HNEOJECGFHIABDLENMMCOEJNCFAA.bcampbell@dynamicsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Binding published data to services
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

In Minneapolis, we talked (yet again) about how to publish service data to
SIP network elements (such as presence documents, CPL, etc.). We decided to
look first into the question of how we would bind such publications to the
SIP services in question. I volunteered to try to spearhead the solution
effort in that area. So here goes:

First, the problem itself seems rather nebulous. It would be useful to more
clearly define the problem. It seems to me that it is really an issue of
name binding--that is, how do we map the name of a SIP based service to the
name of a data element.

Of course, before we can generically map service names to data names, we
must understand how to refer to SIP services in the first place. This issue
keeps coming up, and it is always controversial--so I am not sure if it
makes sense to go futher here than say we use a URI to refer to a service.
(Even that can be problematic, as a service may be distinguished by more
than just the URI. For example, a presence subscription is distinguished by
URI, method, and event. Of course you can still create a URI for that, but
it wouldn't be one you would enjoy typing.

So, does a generic binding of data to services even make sense? We have so
far been unable to agree on a way to generically refer to services. Is there
a way to narrow this problem to avoid that particular rat hole?

Thoughts?

Thanks!

Ben Campbell.



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



From daemon@ns.ietf.org  Fri Apr 12 16:29:21 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03239
	for <sipping-archive@odin.ietf.org>; Fri, 12 Apr 2002 16:29:21 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA11074
	for sipping-archive@odin.ietf.org; Fri, 12 Apr 2002 16:29:24 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA10097;
	Fri, 12 Apr 2002 16:12:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA10056
	for <sipping@ns.ietf.org>; Fri, 12 Apr 2002 16:12:31 -0400 (EDT)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02731
	for <sipping@ietf.org>; Fri, 12 Apr 2002 16:12:28 -0400 (EDT)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id QAA15520;
	Fri, 12 Apr 2002 16:12:29 -0400 (EDT)
Received: from cs.columbia.edu (cta.cs.columbia.edu [128.59.19.46])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g3CKCSPm023609
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Fri, 12 Apr 2002 16:12:29 -0400 (EDT)
Message-ID: <3CB73F82.AF4EAE33@cs.columbia.edu>
Date: Fri, 12 Apr 2002 16:11:46 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Ben Campbell <bcampbell@dynamicsoft.com>
CC: Sipping <sipping@ietf.org>
Subject: Re: [Sipping] Binding published data to services
References: <HNEOJECGFHIABDLENMMCOEJNCFAA.bcampbell@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

A useful and easibly describable sub-problem is the binding of a non-SIP
URI to a SIP URI, so that properties of the SIP URI can be described.
This is sufficient, for example, to describe CPL and other configuration
information, two of the motivating examples for this discussion. It may
also be sufficient for some subset of the presence issue, as long as all
events are handled by the same entity and thus event discrimination can
be handled by the entity receiving the published data. Given practical
realities, that doesn't seem unrealistic.

Ben Campbell wrote:
> 
> In Minneapolis, we talked (yet again) about how to publish service data to
> SIP network elements (such as presence documents, CPL, etc.). We decided to
> look first into the question of how we would bind such publications to the
> SIP services in question. I volunteered to try to spearhead the solution
> effort in that area. So here goes:
> 
> First, the problem itself seems rather nebulous. It would be useful to more
> clearly define the problem. It seems to me that it is really an issue of
> name binding--that is, how do we map the name of a SIP based service to the
> name of a data element.
> 
> Of course, before we can generically map service names to data names, we
> must understand how to refer to SIP services in the first place. This issue
> keeps coming up, and it is always controversial--so I am not sure if it
> makes sense to go futher here than say we use a URI to refer to a service.
> (Even that can be problematic, as a service may be distinguished by more
> than just the URI. For example, a presence subscription is distinguished by
> URI, method, and event. Of course you can still create a URI for that, but
> it wouldn't be one you would enjoy typing.
> 
> So, does a generic binding of data to services even make sense? We have so
> far been unable to agree on a way to generically refer to services. Is there
> a way to narrow this problem to avoid that particular rat hole?
> 
> Thoughts?
> 
> Thanks!
> 
> Ben Campbell.
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 daemon@ns.ietf.org  Fri Apr 12 16:43:44 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03714
	for <sipping-archive@odin.ietf.org>; Fri, 12 Apr 2002 16:43:44 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA12221
	for sipping-archive@odin.ietf.org; Fri, 12 Apr 2002 16:43:47 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA11707;
	Fri, 12 Apr 2002 16:33:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA11677
	for <sipping@ns.ietf.org>; Fri, 12 Apr 2002 16:33:32 -0400 (EDT)
Received: from magus.nostrum.com (root@magus.nostrum.com [66.119.225.66])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03341
	for <sipping@ietf.org>; Fri, 12 Apr 2002 16:33:27 -0400 (EDT)
Received: from txbcampbell (root@magus.nostrum.com [66.119.225.66])
	by magus.nostrum.com (8.11.0/8.11.0) with SMTP id g3CKXRX74316;
	Fri, 12 Apr 2002 15:33:27 -0500 (CDT)
From: "Ben Campbell" <bcampbell@dynamicsoft.com>
To: "Henning Schulzrinne" <hgs@cs.columbia.edu>
Cc: "Sipping" <sipping@ietf.org>
Subject: RE: [Sipping] Binding published data to services
Date: Fri, 12 Apr 2002 15:33:12 -0500
Message-ID: <HNEOJECGFHIABDLENMMCEEKACFAA.bcampbell@dynamicsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <3CB73F82.AF4EAE33@cs.columbia.edu>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Are you thinking of an algorithmic binding, or some discovery mechanism?

An algorithmic binding would be nice, but I am afraid it may imply some
limitations on architecture that we might not should make. For example,
would an algoritmic binding force the publication point to have the same
domain name as the SIP service element?

> -----Original Message-----
> From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]
> Sent: Friday, April 12, 2002 3:12 PM
> To: Ben Campbell
> Cc: Sipping
> Subject: Re: [Sipping] Binding published data to services
>
>
> A useful and easibly describable sub-problem is the binding of a non-SIP
> URI to a SIP URI, so that properties of the SIP URI can be described.
> This is sufficient, for example, to describe CPL and other configuration
> information, two of the motivating examples for this discussion. It may
> also be sufficient for some subset of the presence issue, as long as all
> events are handled by the same entity and thus event discrimination can
> be handled by the entity receiving the published data. Given practical
> realities, that doesn't seem unrealistic.
>
> Ben Campbell wrote:
> >
> > In Minneapolis, we talked (yet again) about how to publish
> service data to
> > SIP network elements (such as presence documents, CPL, etc.).
> We decided to
> > look first into the question of how we would bind such
> publications to the
> > SIP services in question. I volunteered to try to spearhead the solution
> > effort in that area. So here goes:
> >
> > First, the problem itself seems rather nebulous. It would be
> useful to more
> > clearly define the problem. It seems to me that it is really an issue of
> > name binding--that is, how do we map the name of a SIP based
> service to the
> > name of a data element.
> >
> > Of course, before we can generically map service names to data names, we
> > must understand how to refer to SIP services in the first
> place. This issue
> > keeps coming up, and it is always controversial--so I am not sure if it
> > makes sense to go futher here than say we use a URI to refer to
> a service.
> > (Even that can be problematic, as a service may be distinguished by more
> > than just the URI. For example, a presence subscription is
> distinguished by
> > URI, method, and event. Of course you can still create a URI
> for that, but
> > it wouldn't be one you would enjoy typing.
> >
> > So, does a generic binding of data to services even make sense?
> We have so
> > far been unable to agree on a way to generically refer to
> services. Is there
> > a way to narrow this problem to avoid that particular rat hole?
> >
> > Thoughts?
> >
> > Thanks!
> >
> > Ben Campbell.
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the 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 daemon@ns.ietf.org  Fri Apr 12 16:44:12 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03805
	for <sipping-archive@odin.ietf.org>; Fri, 12 Apr 2002 16:44:12 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA12238
	for sipping-archive@odin.ietf.org; Fri, 12 Apr 2002 16:44:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA11603;
	Fri, 12 Apr 2002 16:32:11 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA11561
	for <sipping@ns.ietf.org>; Fri, 12 Apr 2002 16:32:07 -0400 (EDT)
Received: from mail2.intervoice-brite.com (mail2.intervoice-brite.com [204.62.8.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03321
	for <sipping@ietf.org>; Fri, 12 Apr 2002 16:32:02 -0400 (EDT)
Received: from DALNTMS02.ivbi.com (dalntms02.ivbi.com [151.214.90.44])
	by mail2.intervoice-brite.com (Build 101 8.9.3/NT-8.9.3) with ESMTP id QAA00020
	for <sipping@ietf.org>; Thu, 11 Apr 2002 16:00:15 -0500
Received: from 172.16.16.64 (unverified) by DALNTMS02.ivbi.com
 (Content Technologies SMTPRS 4.2.5) with SMTP id <T5a3216e86e97d65a2c3b0@DALNTMS02.ivbi.com> for <sipping@ietf.org>;
 Thu, 11 Apr 2002 15:36:58 -0500
Received: from bculpepperpc
	([151.214.151.115])
	by 172.16.16.64; Thu, 11 Apr 2002 15:54:51 -0500
From: "Bert Culpepper" <bert.culpepper@intervoice-brite.com>
To: "'Fairlie-Cuninghame, Robert'" <rfairlie@nuera.com>,
        "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>, <sipping@ietf.org>
Subject: RE: [Sipping] I-D  ACTION:draft-culpepper-sipping-app-interact-reqs-00.txt
Date: Thu, 11 Apr 2002 16:54:23 -0400
Message-ID: <001f01c1e19b$0f994d10$7397d697@bculpepperpc>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
In-Reply-To: <E79883AEA37FD411A58C00508BAC5F4B01D38C5F@exchange1.nuera.com>
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit


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



From daemon@ns.ietf.org  Fri Apr 12 18:51:51 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06220
	for <sipping-archive@odin.ietf.org>; Fri, 12 Apr 2002 18:51:51 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA19082
	for sipping-archive@odin.ietf.org; Fri, 12 Apr 2002 18:51:53 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA18761;
	Fri, 12 Apr 2002 18:42:30 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA18732
	for <sipping@ns.ietf.org>; Fri, 12 Apr 2002 18:42:27 -0400 (EDT)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05861
	for <sipping@ietf.org>; Fri, 12 Apr 2002 18:42:24 -0400 (EDT)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id SAA03222;
	Fri, 12 Apr 2002 18:42:24 -0400 (EDT)
Received: from cs.columbia.edu (cta.cs.columbia.edu [128.59.19.46])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g3CMgNPm000187
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Fri, 12 Apr 2002 18:42:24 -0400 (EDT)
Message-ID: <3CB762A5.26E44BFF@cs.columbia.edu>
Date: Fri, 12 Apr 2002 18:41:41 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Ben Campbell <bcampbell@dynamicsoft.com>
CC: Sipping <sipping@ietf.org>
Subject: Re: [Sipping] Binding published data to services
References: <HNEOJECGFHIABDLENMMCEEKACFAA.bcampbell@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Ben Campbell wrote:
> 
> Are you thinking of an algorithmic binding, or some discovery mechanism?
> 
> An algorithmic binding would be nice, but I am afraid it may imply some
> limitations on architecture that we might not should make. For example,
> would an algoritmic binding force the publication point to have the same
> domain name as the SIP service element?

Not sure I understand algorithmic vs. discovery.

No, I certainly wouldn't want to restrict the publication point in any
way, by domain or otherwise.

As a crude thought-experiment, imagine that the REGISTER response for
bcampbell@dynamicsoft.com would return something like

SIP/2.0 200 OK
From: bcampbell@dynamicsoft.com
...
Publish: <http://www.yahoo.com/campbell> ;use=cpl ,
 <http://www.att.com> ;use=config

This would tie the publish information to your SIP URI, but not in any
way restrict the publishing URL.

You could presumably configure this information via REGISTER, too.

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



From daemon@ns.ietf.org  Fri Apr 12 20:52:26 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07632
	for <sipping-archive@odin.ietf.org>; Fri, 12 Apr 2002 20:52:25 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA23969
	for sipping-archive@odin.ietf.org; Fri, 12 Apr 2002 20:52:28 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA23472;
	Fri, 12 Apr 2002 20:40:54 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA23441
	for <sipping@ns.ietf.org>; Fri, 12 Apr 2002 20:40:50 -0400 (EDT)
Received: from bdsl.66.12.12.130.gte.net (bdsl.66.12.12.130.gte.net [66.12.12.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07428
	for <sipping@ietf.org>; Fri, 12 Apr 2002 20:40:46 -0400 (EDT)
Received: from TXDWILLIS2 (bdsl.greycouncil.com [127.0.0.1])
	by bdsl.66.12.12.130.gte.net (8.11.6/8.11.6) with ESMTP id g3D0e7d21792;
	Fri, 12 Apr 2002 19:40:07 -0500
From: "Dean Willis" <dwillis@dynamicsoft.com>
To: <sipping@ietf.org>
Cc: <rohan@cisco.com>, <brian.rosen@cisco.com>, <vesa.torvinen@ericsson.fi>,
        <jari.arkko@ericsson.com>, <aki.niemi@nokia.com>
Date: Fri, 12 Apr 2002 19:39:29 -0500
Message-ID: <000001c1e283$ac6a5f10$0100a8c0@TXDWILLIS2>
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.3416
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [Sipping] WGLC AKA-Digest
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit


Ok, Assuming I have the right version of the file, I believe we're ready
to semiformally WGLC the informational-track draft:

http://search.ietf.org/internet-drafts/draft-niemi-sipping-digest-aka-00
.txt

Which explains how to use AKA to set up keys to do HTTP digest
authentication, which just happens to work with SIP, and since
GSM-derived cell phones have SIM cards with AKA and also use SIP, may
turn ut to be very useful for mobile SIP and is therefore in the
province of this group.

Please discuss on list, and copy the authors with anything juicy.

We'd like to get this stuff into IETF last call fairly soon, so move
quick . . .

One nit that I'd like to go ahead and note is that the references need
to be divided into Normative and Non-Normative sections. This makes the
RFC editors job MUCH easier.

--
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 daemon@ns.ietf.org  Fri Apr 12 20:58:40 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07718
	for <sipping-archive@odin.ietf.org>; Fri, 12 Apr 2002 20:58:40 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA24171
	for sipping-archive@odin.ietf.org; Fri, 12 Apr 2002 20:58:40 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA23863;
	Fri, 12 Apr 2002 20:47:13 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA23832
	for <sipping@ns.ietf.org>; Fri, 12 Apr 2002 20:47:09 -0400 (EDT)
Received: from magus.nostrum.com (root@magus.nostrum.com [66.119.225.66])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07585
	for <sipping@ietf.org>; Fri, 12 Apr 2002 20:47:05 -0400 (EDT)
Received: from txbcampbell (root@magus.nostrum.com [66.119.225.66])
	by magus.nostrum.com (8.11.0/8.11.0) with SMTP id g3D0l1X92938;
	Fri, 12 Apr 2002 19:47:01 -0500 (CDT)
From: "Ben Campbell" <bcampbell@dynamicsoft.com>
To: "Henning Schulzrinne" <hgs@cs.columbia.edu>
Cc: "Sipping" <sipping@ietf.org>
Subject: RE: [Sipping] Binding published data to services
Date: Fri, 12 Apr 2002 19:46:46 -0500
Message-ID: <HNEOJECGFHIABDLENMMCMEKECFAA.bcampbell@dynamicsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-reply-to: <3CB762A5.26E44BFF@cs.columbia.edu>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

That is what I meant by discovery--the service tells you where to publish,
as opposed to being able to perform some transformation on a SIP URI to get
an http: (or foo: for that matter) URI.

> -----Original Message-----
> From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]
> Sent: Friday, April 12, 2002 5:42 PM
> To: Ben Campbell
> Cc: Sipping
> Subject: Re: [Sipping] Binding published data to services
>
>
> Ben Campbell wrote:
> >
> > Are you thinking of an algorithmic binding, or some discovery mechanism?
> >
> > An algorithmic binding would be nice, but I am afraid it may imply some
> > limitations on architecture that we might not should make. For example,
> > would an algoritmic binding force the publication point to have the same
> > domain name as the SIP service element?
>
> Not sure I understand algorithmic vs. discovery.
>
> No, I certainly wouldn't want to restrict the publication point in any
> way, by domain or otherwise.
>
> As a crude thought-experiment, imagine that the REGISTER response for
> bcampbell@dynamicsoft.com would return something like
>
> SIP/2.0 200 OK
> From: bcampbell@dynamicsoft.com
> ...
> Publish: <http://www.yahoo.com/campbell> ;use=cpl ,
>  <http://www.att.com> ;use=config
>
> This would tie the publish information to your SIP URI, but not in any
> way restrict the publishing URL.
>
> You could presumably configure this information via REGISTER, too.


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



From daemon@ns.ietf.org  Fri Apr 12 21:07:09 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07843
	for <sipping-archive@odin.ietf.org>; Fri, 12 Apr 2002 21:07:09 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA24915
	for sipping-archive@odin.ietf.org; Fri, 12 Apr 2002 21:07:12 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA24087;
	Fri, 12 Apr 2002 20:54:47 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA24056
	for <sipping@ns.ietf.org>; Fri, 12 Apr 2002 20:54:43 -0400 (EDT)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07689
	for <sipping@ietf.org>; Fri, 12 Apr 2002 20:54:39 -0400 (EDT)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id UAA14568;
	Fri, 12 Apr 2002 20:54:37 -0400 (EDT)
Received: from cs.columbia.edu (cta.cs.columbia.edu [128.59.19.46])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g3D0sbPm004834
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Fri, 12 Apr 2002 20:54:37 -0400 (EDT)
Message-ID: <3CB781A2.21283F75@cs.columbia.edu>
Date: Fri, 12 Apr 2002 20:53:54 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Ben Campbell <bcampbell@dynamicsoft.com>
CC: Sipping <sipping@ietf.org>
Subject: Re: [Sipping] Binding published data to services
References: <HNEOJECGFHIABDLENMMCMEKECFAA.bcampbell@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

The only way I could see something like an algorithmic transformation
working would be to use NAPTR records, using the regexp transformations.
However, I'm not convinced that DNS is the right location for this, as
it would pretty much mean that everybody in the same domain has to use
the same transformation. This may still be useful as a default
mechanism, however, subject to some discovery override.

Ben Campbell wrote:
> 
> That is what I meant by discovery--the service tells you where to publish,
> as opposed to being able to perform some transformation on a SIP URI to get
> an http: (or foo: for that matter) URI.
>

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



From daemon@ns.ietf.org  Fri Apr 12 21:14:24 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07955
	for <sipping-archive@odin.ietf.org>; Fri, 12 Apr 2002 21:14:24 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA25048
	for sipping-archive@odin.ietf.org; Fri, 12 Apr 2002 21:14:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA24807;
	Fri, 12 Apr 2002 21:03:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA24768
	for <sipping@ns.ietf.org>; Fri, 12 Apr 2002 21:02:58 -0400 (EDT)
Received: from web11605.mail.yahoo.com (web11605.mail.yahoo.com [216.136.172.57])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA07767
	for <sipping@ietf.org>; Fri, 12 Apr 2002 21:02:54 -0400 (EDT)
Message-ID: <20020413010256.87521.qmail@web11605.mail.yahoo.com>
Received: from [131.107.3.86] by web11605.mail.yahoo.com via HTTP; Fri, 12 Apr 2002 18:02:56 PDT
Date: Fri, 12 Apr 2002 18:02:56 -0700 (PDT)
From: Sean Olson <seancolson@yahoo.com>
Subject: RE: [Sipping] Binding published data to services
To: Ben Campbell <bcampbell@dynamicsoft.com>,
        Henning Schulzrinne <hgs@cs.columbia.edu>
Cc: Sipping <sipping@ietf.org>
In-Reply-To: <HNEOJECGFHIABDLENMMCMEKECFAA.bcampbell@dynamicsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

A few comments on this topic:

1) We should consider both SIP-based mechanisms
   for discovery (like the example shown) as well
   as other mechanisms: DHCP, DDDS, etc.

2) We should support both client-supplied bindings
   as well as server-supplied bindings. A 
   client supplied binding might be publishing a
   CPL script. A server supplied binding might be
   an administrator creating a binding between an
   LDAP URL and a SIP URL.

3) We should allow (as one option) an automated
   way for binding one URL scheme to another.
   An example might be an automated way to 
   bind a pres: URL to a sip: URL. You don't
   necessarily want to have to provision these
   bindings.

4) It might be nice to be able to identify the
   party which created the binding.

5) It would be nice to support an ephemeral 
   binding.

6) It would be nice to support bindings 
   in some situations that are not easily 
   guessable.

/sean



__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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



From daemon@ns.ietf.org  Fri Apr 12 22:25:13 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09385
	for <sipping-archive@odin.ietf.org>; Fri, 12 Apr 2002 22:25:12 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA27020
	for sipping-archive@odin.ietf.org; Fri, 12 Apr 2002 22:25:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA26787;
	Fri, 12 Apr 2002 22:12:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA26754
	for <sipping@ns.ietf.org>; Fri, 12 Apr 2002 22:12:54 -0400 (EDT)
Received: from magus.nostrum.com (root@magus.nostrum.com [66.119.225.66])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09269
	for <sipping@ietf.org>; Fri, 12 Apr 2002 22:12:51 -0400 (EDT)
Received: from txbcampbell (root@magus.nostrum.com [66.119.225.66])
	by magus.nostrum.com (8.11.0/8.11.0) with SMTP id g3D2CqX98839;
	Fri, 12 Apr 2002 21:12:52 -0500 (CDT)
From: "Ben Campbell" <bcampbell@dynamicsoft.com>
To: "Henning Schulzrinne" <hgs@cs.columbia.edu>
Cc: "Sipping" <sipping@ietf.org>
Subject: RE: [Sipping] Binding published data to services
Date: Fri, 12 Apr 2002 21:12:36 -0500
Message-ID: <HNEOJECGFHIABDLENMMCOEKFCFAA.bcampbell@dynamicsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-reply-to: <3CB781A2.21283F75@cs.columbia.edu>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

My concern about algorithmic tranformations (DNS or otherwise) is that it
would imply fairly static bindings. I can imagine an application that would
allocate a publication URI on the fly, and not necesarrily give the same
result for multiple queries against a given SIP URI.

> -----Original Message-----
> From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]
> Sent: Friday, April 12, 2002 7:54 PM
> To: Ben Campbell
> Cc: Sipping
> Subject: Re: [Sipping] Binding published data to services
>
>
> The only way I could see something like an algorithmic transformation
> working would be to use NAPTR records, using the regexp transformations.
> However, I'm not convinced that DNS is the right location for this, as
> it would pretty much mean that everybody in the same domain has to use
> the same transformation. This may still be useful as a default
> mechanism, however, subject to some discovery override.
>
> Ben Campbell wrote:
> >
> > That is what I meant by discovery--the service tells you where
> to publish,
> > as opposed to being able to perform some transformation on a
> SIP URI to get
> > an http: (or foo: for that matter) URI.
> >


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



From daemon@ns.ietf.org  Fri Apr 12 22:32:47 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10392
	for <sipping-archive@odin.ietf.org>; Fri, 12 Apr 2002 22:32:47 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA27592
	for sipping-archive@odin.ietf.org; Fri, 12 Apr 2002 22:32:49 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA26908;
	Fri, 12 Apr 2002 22:20:16 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA26876
	for <sipping@ns.ietf.org>; Fri, 12 Apr 2002 22:20:13 -0400 (EDT)
Received: from magus.nostrum.com (root@magus.nostrum.com [66.119.225.66])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09337
	for <sipping@ietf.org>; Fri, 12 Apr 2002 22:20:09 -0400 (EDT)
Received: from txbcampbell (root@magus.nostrum.com [66.119.225.66])
	by magus.nostrum.com (8.11.0/8.11.0) with SMTP id g3D2K9X99236;
	Fri, 12 Apr 2002 21:20:09 -0500 (CDT)
From: "Ben Campbell" <bcampbell@dynamicsoft.com>
To: "Sean Olson" <seancolson@yahoo.com>,
        "Henning Schulzrinne" <hgs@cs.columbia.edu>
Cc: "Sipping" <sipping@ietf.org>
Subject: RE: [Sipping] Binding published data to services
Date: Fri, 12 Apr 2002 21:19:53 -0500
Message-ID: <HNEOJECGFHIABDLENMMCMEKGCFAA.bcampbell@dynamicsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-reply-to: <20020413010256.87521.qmail@web11605.mail.yahoo.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

It sounds like we are starting to generate requirements--I guess that is
progress. More comments inline.

> -----Original Message-----
> From: Sean Olson [mailto:seancolson@yahoo.com]
> Sent: Friday, April 12, 2002 8:03 PM
> To: Ben Campbell; Henning Schulzrinne
> Cc: Sipping
> Subject: RE: [Sipping] Binding published data to services
>
>
> A few comments on this topic:
>
> 1) We should consider both SIP-based mechanisms
>    for discovery (like the example shown) as well
>    as other mechanisms: DHCP, DDDS, etc.
>
> 2) We should support both client-supplied bindings
>    as well as server-supplied bindings. A
>    client supplied binding might be publishing a
>    CPL script. A server supplied binding might be
>    an administrator creating a binding between an
>    LDAP URL and a SIP URL.

Can you elaborate further on what you mean by client-side bindings?

>
> 3) We should allow (as one option) an automated
>    way for binding one URL scheme to another.
>    An example might be an automated way to
>    bind a pres: URL to a sip: URL. You don't
>    necessarily want to have to provision these
>    bindings.

By automated, I assume you mean a way for a client to infer the publication
URI from a SIP URI without asking the SIP service? Henning suggested a NAPTR
approach as a possible last-resort alternative. Is this the sort of thing
you had in mind? It does seem like this might conflict with your items 4 and
6.

>
> 4) It might be nice to be able to identify the
>    party which created the binding.

Agreed.

>
> 5) It would be nice to support an ephemeral
>    binding.

Agreed, which points more to a discovery mechanism.

>
> 6) It would be nice to support bindings
>    in some situations that are not easily
>    guessable.

Agreed. I suspect 5 and 6 are aspects of the same thing.

I would also  propose 7) It would be nice to control who can discover a
binding, and 8) who can use the bound URI it is discovered.

>
> /sean
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Tax Center - online filing with TurboTax
> http://taxes.yahoo.com/


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



From daemon@ns.ietf.org  Fri Apr 12 22:35:46 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10419
	for <sipping-archive@odin.ietf.org>; Fri, 12 Apr 2002 22:35:46 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA27623
	for sipping-archive@odin.ietf.org; Fri, 12 Apr 2002 22:35:48 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA27002;
	Fri, 12 Apr 2002 22:24:25 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA26971
	for <sipping@ns.ietf.org>; Fri, 12 Apr 2002 22:24:21 -0400 (EDT)
Received: from magus.nostrum.com (root@magus.nostrum.com [66.119.225.66])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09353
	for <sipping@ietf.org>; Fri, 12 Apr 2002 22:24:17 -0400 (EDT)
Received: from txbcampbell (root@magus.nostrum.com [66.119.225.66])
	by magus.nostrum.com (8.11.0/8.11.0) with SMTP id g3D2OFX99524;
	Fri, 12 Apr 2002 21:24:15 -0500 (CDT)
From: "Ben Campbell" <bcampbell@dynamicsoft.com>
To: "Ben Campbell" <bcampbell@dynamicsoft.com>,
        "Sean Olson" <seancolson@yahoo.com>,
        "Henning Schulzrinne" <hgs@cs.columbia.edu>
Cc: "Sipping" <sipping@ietf.org>
Subject: RE: [Sipping] Binding published data to services
Date: Fri, 12 Apr 2002 21:23:59 -0500
Message-ID: <HNEOJECGFHIABDLENMMCEEKHCFAA.bcampbell@dynamicsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-reply-to: <HNEOJECGFHIABDLENMMCMEKGCFAA.bcampbell@dynamicsoft.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

(replies to self)

Actually, let me retract my number 8 item--authentication/authorization for
the use bound URI after discovery is probably an aspect of the associated
publication protocol itself, not the binding mechanism.

> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]On Behalf Of
> Ben Campbell
> Sent: Friday, April 12, 2002 9:20 PM
> To: Sean Olson; Henning Schulzrinne
> Cc: Sipping
> Subject: RE: [Sipping] Binding published data to services
>
>
> It sounds like we are starting to generate requirements--I guess that is
> progress. More comments inline.
>
> > -----Original Message-----
> > From: Sean Olson [mailto:seancolson@yahoo.com]
> > Sent: Friday, April 12, 2002 8:03 PM
> > To: Ben Campbell; Henning Schulzrinne
> > Cc: Sipping
> > Subject: RE: [Sipping] Binding published data to services
> >
> >
> > A few comments on this topic:
> >
> > 1) We should consider both SIP-based mechanisms
> >    for discovery (like the example shown) as well
> >    as other mechanisms: DHCP, DDDS, etc.
> >
> > 2) We should support both client-supplied bindings
> >    as well as server-supplied bindings. A
> >    client supplied binding might be publishing a
> >    CPL script. A server supplied binding might be
> >    an administrator creating a binding between an
> >    LDAP URL and a SIP URL.
>
> Can you elaborate further on what you mean by client-side bindings?
>
> >
> > 3) We should allow (as one option) an automated
> >    way for binding one URL scheme to another.
> >    An example might be an automated way to
> >    bind a pres: URL to a sip: URL. You don't
> >    necessarily want to have to provision these
> >    bindings.
>
> By automated, I assume you mean a way for a client to infer the
> publication
> URI from a SIP URI without asking the SIP service? Henning
> suggested a NAPTR
> approach as a possible last-resort alternative. Is this the sort of thing
> you had in mind? It does seem like this might conflict with your
> items 4 and
> 6.
>
> >
> > 4) It might be nice to be able to identify the
> >    party which created the binding.
>
> Agreed.
>
> >
> > 5) It would be nice to support an ephemeral
> >    binding.
>
> Agreed, which points more to a discovery mechanism.
>
> >
> > 6) It would be nice to support bindings
> >    in some situations that are not easily
> >    guessable.
>
> Agreed. I suspect 5 and 6 are aspects of the same thing.
>
> I would also  propose 7) It would be nice to control who can discover a
> binding, and 8) who can use the bound URI it is discovered.
>
> >
> > /sean
> >
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! Tax Center - online filing with TurboTax
> > http://taxes.yahoo.com/
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP


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



From daemon@ns.ietf.org  Fri Apr 12 23:12:20 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10730
	for <sipping-archive@odin.ietf.org>; Fri, 12 Apr 2002 23:12:19 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA28766
	for sipping-archive@odin.ietf.org; Fri, 12 Apr 2002 23:12:22 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA27977;
	Fri, 12 Apr 2002 22:59:16 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA27945
	for <sipping@ns.ietf.org>; Fri, 12 Apr 2002 22:59:13 -0400 (EDT)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10636
	for <sipping@ietf.org>; Fri, 12 Apr 2002 22:59:10 -0400 (EDT)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id WAA23534;
	Fri, 12 Apr 2002 22:59:12 -0400 (EDT)
Received: from cs.columbia.edu (pool-138-89-41-200.mad.east.verizon.net [138.89.41.200])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g3D2xBPm008042
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Fri, 12 Apr 2002 22:59:11 -0400 (EDT)
Message-ID: <3CB79EBF.4C203EB@cs.columbia.edu>
Date: Fri, 12 Apr 2002 22:58:07 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Ben Campbell <bcampbell@dynamicsoft.com>
CC: Sipping <sipping@ietf.org>
Subject: Re: [Sipping] Binding published data to services
References: <HNEOJECGFHIABDLENMMCOEKFCFAA.bcampbell@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Ben Campbell wrote:
> 
> My concern about algorithmic tranformations (DNS or otherwise) is that it
> would imply fairly static bindings. I can imagine an application that would
> allocate a publication URI on the fly, and not necesarrily give the same
> result for multiple queries against a given SIP URI.
> 

As long as such static bindings can be overridden, they may have a
useful role to play, particularly for provisioned bindings.

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



From daemon@optimus.ietf.org  Sat Apr 13 02:58:58 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21878
	for <sipping-archive@odin.ietf.org>; Sat, 13 Apr 2002 02:58:58 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA16640
	for sipping-archive@odin.ietf.org; Sat, 13 Apr 2002 02:59:00 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA16410;
	Sat, 13 Apr 2002 02:46:20 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA16379
	for <sipping@optimus.ietf.org>; Sat, 13 Apr 2002 02:46:17 -0400 (EDT)
Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21823
	for <sipping@ietf.org>; Sat, 13 Apr 2002 02:46:14 -0400 (EDT)
Received: from BOB ([12.230.191.92]) by rwcrmhc51.attbi.com
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20020413064545.HCIN1143.rwcrmhc51.attbi.com@BOB>;
          Sat, 13 Apr 2002 06:45:45 +0000
Reply-To: <seancolson@yahoo.com>
From: "Sean Olson" <seancolson@yahoo.com>
To: "'Ben Campbell'" <bcampbell@dynamicsoft.com>,
        "'Henning Schulzrinne'" <hgs@cs.columbia.edu>
Cc: "'Sipping'" <sipping@ietf.org>
Subject: RE: [Sipping] Binding published data to services
Date: Fri, 12 Apr 2002 23:45:45 -0700
Message-ID: <000a01c1e2b6$d7327ce0$6401a8c0@BOB>
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.3416
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <HNEOJECGFHIABDLENMMCMEKGCFAA.bcampbell@dynamicsoft.com>
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit


> 2) We should support both client-supplied bindings
>    as well as server-supplied bindings. A
>    client supplied binding might be publishing a
>    CPL script. A server supplied binding might be
>    an administrator creating a binding between an
>    LDAP URL and a SIP URL.

Can you elaborate further on what you mean by client-side bindings?

Sean> The distinction I am trying to make is who owns/defines the
binding, assuming that the binding is dynamic and not simple
string manipulation. A client-side binding, would be made by a
UserAgent/user-centric device. A server-side binding would be
made by a registrar/proxy/network-centric device. This may be a
bit blurry, but I wanted to ensure that the mechanism worked 
"both ways".

>
> 3) We should allow (as one option) an automated
>    way for binding one URL scheme to another.
>    An example might be an automated way to
>    bind a pres: URL to a sip: URL. You don't
>    necessarily want to have to provision these
>    bindings.

By automated, I assume you mean a way for a client to infer the
publication URI from a SIP URI without asking the SIP service? Henning
suggested a NAPTR approach as a possible last-resort alternative. Is
this the sort of thing you had in mind? It does seem like this might
conflict with your items 4 and 6.

Sean> I had two possibilities in mind:
      1) Use something like NAPTR/DDDS
      2) Use something even simpler like a well-known regex.
         This would be much more static and useful in only a 
         handful of cases. Nonetheless, I think it will serve
         a purpose. An example that comes to mind is the 
         construction of a UUID binding from a SIP URL.
 
      It conflicts with items 4,6 in the sense that you would
      likely not apply such an obvious static binding in the case where
      you want an ephemeral or private binding. Both types of 
      bindings are useful under different circumstances.

/sean



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



From daemon@optimus.ietf.org  Sat Apr 13 04:48:17 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22817
	for <sipping-archive@odin.ietf.org>; Sat, 13 Apr 2002 04:48:17 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA22638
	for sipping-archive@odin.ietf.org; Sat, 13 Apr 2002 04:48:18 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA21066;
	Sat, 13 Apr 2002 04:33:30 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA20962
	for <sipping@optimus.ietf.org>; Sat, 13 Apr 2002 04:33:24 -0400 (EDT)
Received: from hongkong.com ([202.84.12.154])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA22620
	for <sipping@ietf.org>; Sat, 13 Apr 2002 04:33:21 -0400 (EDT)
Received: from hongkong.com([10.1.0.100]) by hongkong.com(JetMail 2.5.3.0)
	with SMTP id jmd3cb8326c; Sat, 13 Apr 2002 08:27:26 -0000
Received: from loki.ietf.org([132.151.1.177]) by hongkong.com(JetMail 2.5.3.0)
	with SMTP id jm3a3cb35c0c; Tue,  9 Apr 2002 13:59:45 -0000
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id JAA20951
	for ietf-123-outbound.03@ietf.org; Tue, 9 Apr 2002 09:55:00 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id IAA20292
	for <all-ietf@loki.ietf.org>; Tue, 9 Apr 2002 08:41:05 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03423;
	Tue, 9 Apr 2002 08:41:03 -0400 (EDT)
Message-Id: <200204091241.IAA03423@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 09 Apr 2002 08:41:03 -0400
X-Auto-Forward: nicklau@hongkong.com
 nicklau@speednet.net
Subject: [Sipping] I-D ACTION:draft-camarillo-sipping-reason-00.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

--NextPart

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


	Title		: Session Initiation Protocol: Requirements on Reason 
                          Information beyond the Status Code
	Author(s)	: G. Camarillo
	Filename	: draft-camarillo-sipping-reason-00.txt
	Pages		: 5
	Date		: 08-Apr-02
	
Some applications need to know why a particular SIP message was
issued. This document describes those applications and provides a
set of requirements that a mechanism used to transport this type of
information has to fulfill.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-camarillo-sipping-reason-00.txt

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-camarillo-sipping-reason-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-camarillo-sipping-reason-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:	<20020408122729.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-camarillo-sipping-reason-00.txt

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

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

--OtherAccess--

--NextPart--



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



From daemon@optimus.ietf.org  Sat Apr 13 07:08:58 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23708
	for <sipping-archive@odin.ietf.org>; Sat, 13 Apr 2002 07:08:53 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA27618
	for sipping-archive@odin.ietf.org; Sat, 13 Apr 2002 07:08:54 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA26909;
	Sat, 13 Apr 2002 06:53:22 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA26881
	for <sipping@optimus.ietf.org>; Sat, 13 Apr 2002 06:53:18 -0400 (EDT)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA23605
	for <sipping@ietf.org>; Sat, 13 Apr 2002 06:53:10 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g3DAqu3G004437;
	Sat, 13 Apr 2002 12:53:02 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.106.10])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g3DAqpUD001457;
	Sat, 13 Apr 2002 13:52:55 +0300 (EET DST)
Message-ID: <3CB80E03.5849AD36@lmf.ericsson.se>
Date: Sat, 13 Apr 2002 13:52:51 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Yu, James" <james.yu@neustar.biz>
CC: "'Robert Sparks'" <rsparks@dynamicsoft.com>,
        "'Michael Hammer'" <mhammer@cisco.com>, sipping@ietf.org
Subject: Re: [Sipping] draft-yu-tel-url-04.txt comment
References: <A83B38C38B3ED6119D3600306E0722D038BF3A@dc02.npac.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit


Hi,

> I mean that they (rn, cic, npdi) are not specified in rfc2543bis.

Exactly, because a bis-only compliant implementation would not care about
those parameters.

However, bis DOES allow extensions (in this case your draft) define new
uri-parameters, by using the "other-parms" defined in bis. Then,
implementations supporting your extension would support the parameters, while
implementations not supporting them would simply ignore them - according to
the rules in bis.

If you, however, put your parameters in the user-part, you may mess up
implementations not supporting your extension, since bis doesn't specify
parameters for the user-part (even if it does allow the ";" character).

Regards,

Christer Holmberg
Ericsson Finland




> Sorry
> that if I used the wrong term.
>
> James
>
> > -----Original Message-----
> > From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> > Sent: Friday, April 12, 2002 8:06 AM
> > To: Yu, James
> > Cc: 'Robert Sparks'; 'Michael Hammer'; sipping@ietf.org
> > Subject: Re: [Sipping] draft-yu-tel-url-04.txt comment
> >
> >
> >
> > Hi,
> >
> > What do you mean by "invalid url parameters" and "they don't
> > mean anything"?
> > The spec allows one to specify any kind of uri parameter
> > (other-param in the
> > ABNF syntax). Any implementation supporting the
> > draft-yu-tel-url-04.txt will
> > treat them exactly the same way they would support them if
> > they were in the
> > user-part, wouldn't it? They would only "mean nothing" to
> > implementations
> > not supporting the draft...
> >
> > Regards,
> >
> > Christer Holmberg
> > Ericsson Finland
> >
> >
> > > Thanks.  I mean that they are "invalid url parameters."
> > >
> > > James
> > >
> > > > -----Original Message-----
> > > > From: Robert Sparks [mailto:rsparks@dynamicsoft.com]
> > > > Sent: Thursday, April 11, 2002 2:37 PM
> > > > To: Yu, James
> > > > Cc: 'Michael Hammer'; sipping@ietf.org
> > > > Subject: RE: [Sipping] draft-yu-tel-url-04.txt comment
> > > >
> > > >
> > > > On Wed, 2002-04-10 at 12:39, Yu, James wrote:
> > > > > > I still feel that the use of parameters that are
> > > > > > intended to be
> > > > > > globally used, within the user part of a sip: URI (which I've
> > > > > > heard many
> > > > > > times can only be interpreted correctly by the domain after
> > > > > > the "@" sign)
> > > > > > may be an unintended contradiction.  I don't see a problem
> > > > > > with the tel:
> > > > > > URI as that does not have the domain construct.
> > > > >
> > > > > The routing is based on the host info. after "@" first.
> > > > The user part is
> > > > > then checked when that host receives the message.
> > > > >
> > > > > >
> > > > > > Would an address such as:
> > > > > > sip:+1-202-533-1234@sip.abc.com;user=phone;npdi=yes;rn=+1-202-
> > > > > > 544-000;cic=+1-6789
> > > > > > also be valid or is that prohibited by your draft?
> > > > > >
> > > > >
> > > > > No, it is not allowed because they are not valid url
> > > > parameters in sip url.
> > > >
> > > > That's not quite right. They are very much allowed. They just
> > > > don't mean
> > > > anything - everything will treat them as unknown SIP URI
> > > > parameters and
> > > > ignore them for anything but URI comparision.
> > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Sipping mailing list
> > https://www1.ietf.org/mailman/listinfo/sipping
> > > > > This list is for NEW development of the 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 daemon@optimus.ietf.org  Sat Apr 13 14:50:06 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28121
	for <sipping-archive@odin.ietf.org>; Sat, 13 Apr 2002 14:50:06 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA13599
	for sipping-archive@odin.ietf.org; Sat, 13 Apr 2002 14:50:07 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA13316;
	Sat, 13 Apr 2002 14:32:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA10583
	for <sipping@ns.ietf.org>; Fri, 12 Apr 2002 16:20:35 -0400 (EDT)
Received: from pine.neustar.com (pine.neustar.com [209.173.57.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02909
	for <sipping@ietf.org>; Fri, 12 Apr 2002 16:20:32 -0400 (EDT)
Received: from chiimc01.il.neustar.com (chih650b-s3p2.il.neustar.com [209.173.57.65])
	by pine.neustar.com (8.11.0/8.11.0) with ESMTP id g3CEUqZ12110;
	Fri, 12 Apr 2002 09:30:52 -0500
Received: by chiimc01.il.neustar.com with Internet Mail Service (5.5.2653.19)
	id <HGJX5XTH>; Fri, 12 Apr 2002 09:30:47 -0500
Message-ID: <A83B38C38B3ED6119D3600306E0722D038BF3A@dc02.npac.com>
From: "Yu, James" <james.yu@neustar.biz>
To: "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>
Cc: "'Robert Sparks'" <rsparks@dynamicsoft.com>,
        "'Michael Hammer'"
	 <mhammer@cisco.com>, sipping@ietf.org
Subject: RE: [Sipping] draft-yu-tel-url-04.txt comment
Date: Fri, 12 Apr 2002 09:30:43 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Christer,

I mean that they (rn, cic, npdi) are not specified in rfc2543bis.   Sorry
that if I used the wrong term.

James

> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@lmf.ericsson.se]
> Sent: Friday, April 12, 2002 8:06 AM
> To: Yu, James
> Cc: 'Robert Sparks'; 'Michael Hammer'; sipping@ietf.org
> Subject: Re: [Sipping] draft-yu-tel-url-04.txt comment
> 
> 
> 
> Hi,
> 
> What do you mean by "invalid url parameters" and "they don't 
> mean anything"?
> The spec allows one to specify any kind of uri parameter 
> (other-param in the
> ABNF syntax). Any implementation supporting the 
> draft-yu-tel-url-04.txt will
> treat them exactly the same way they would support them if 
> they were in the
> user-part, wouldn't it? They would only "mean nothing" to 
> implementations
> not supporting the draft...
> 
> Regards,
> 
> Christer Holmberg
> Ericsson Finland
> 
> 
> > Thanks.  I mean that they are "invalid url parameters."
> >
> > James
> >
> > > -----Original Message-----
> > > From: Robert Sparks [mailto:rsparks@dynamicsoft.com]
> > > Sent: Thursday, April 11, 2002 2:37 PM
> > > To: Yu, James
> > > Cc: 'Michael Hammer'; sipping@ietf.org
> > > Subject: RE: [Sipping] draft-yu-tel-url-04.txt comment
> > >
> > >
> > > On Wed, 2002-04-10 at 12:39, Yu, James wrote:
> > > > > I still feel that the use of parameters that are
> > > > > intended to be
> > > > > globally used, within the user part of a sip: URI (which I've
> > > > > heard many
> > > > > times can only be interpreted correctly by the domain after
> > > > > the "@" sign)
> > > > > may be an unintended contradiction.  I don't see a problem
> > > > > with the tel:
> > > > > URI as that does not have the domain construct.
> > > >
> > > > The routing is based on the host info. after "@" first.
> > > The user part is
> > > > then checked when that host receives the message.
> > > >
> > > > >
> > > > > Would an address such as:
> > > > > sip:+1-202-533-1234@sip.abc.com;user=phone;npdi=yes;rn=+1-202-
> > > > > 544-000;cic=+1-6789
> > > > > also be valid or is that prohibited by your draft?
> > > > >
> > > >
> > > > No, it is not allowed because they are not valid url
> > > parameters in sip url.
> > >
> > > That's not quite right. They are very much allowed. They just
> > > don't mean
> > > anything - everything will treat them as unknown SIP URI
> > > parameters and
> > > ignore them for anything but URI comparision.
> > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Sipping mailing list  
> https://www1.ietf.org/mailman/listinfo/sipping
> > > > This list is for NEW development of the 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 daemon@optimus.ietf.org  Sat Apr 13 16:52:54 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28989
	for <sipping-archive@odin.ietf.org>; Sat, 13 Apr 2002 16:52:54 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA17239
	for sipping-archive@odin.ietf.org; Sat, 13 Apr 2002 16:52:56 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA17069;
	Sat, 13 Apr 2002 16:42:50 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA17031
	for <sipping@optimus.ietf.org>; Sat, 13 Apr 2002 16:42:46 -0400 (EDT)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28858;
	Sat, 13 Apr 2002 16:42:39 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-2.cisco.com (8.12.2/8.12.2) with ESMTP id g3DKfx83010553;
	Sat, 13 Apr 2002 13:41:59 -0700 (PDT)
Received: from localhost (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint)
	with ESMTP id ACV68528;
	Sat, 13 Apr 2002 13:41:57 -0700 (PDT)
Date: Sat, 13 Apr 2002 13:39:07 -0700 (Pacific Daylight Time)
From: Rohan Mahy <rohan@cisco.com>
To: ietf@ietf.org, <sip@ietf.org>, <sipping@ietf.org>
cc: rohan@cisco.com, <dwillis@dynamicsoft.com>, <brian.rosen@marconi.com>,
        <jo@ipdialog.com>, <mankin@isi.edu>, <sob@harvard.edu>
Message-ID: <Pine.WNT.4.44.0204131324400.-17957-100000@chorizo.rapidconvergence.com>
X-X-Sender: rmahy@imop.cisco.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Sipping] SIP/SIPPING Interim Meeting
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Hi,

I'd like to announce a joint SIP/SIPPING interim meeting May 6-7 in Las
Vegas, Nevada.  This date and location were changed (with AD approval)
as a fallback due to conflicts with the previously proposed time and place
(Boston, the following week).

The meeting will occur at the Las Vegas Convention Center or the adjacent
Las Vegas Hilton Hotel (not to be confused with the Flamingo Hilton).
Inexpensive rooms and flights are still available.

Proposed Agenda:

Monday May 6
08:00  Agenda bashing, logistics
08:30  Open issues for REFER, Replaces, and cc-transfer
11:00  Multiparty and conferencing requirements
12:30  lunch
14:00  call-info and conference-info packages
16:00  Content-indirection
16:30  Binding published data to SIP
17:30  Wrap

Tuesday May 7
08:00   The long-term privacy solution
12:00   lunch
13:30   outstanding security issues/requirements
15:00   AAA requirements
17:30   Wrap

As always, drafts must be submitted by two weeks before the meeting,
(April 22).  Detailed minutes and blue sheets will be taken and posted to
the list.  All decisions based on a proto-consensus at the interim will go
back to the list.

If you are planning to attend, please send mail to me (rohan@cisco.com)
privately so I can get a room of an appropriate size.

thanks,
-rohan

p.s. A couple folks have asked for my motivation for suggesting an interim.
Basically we've got a lot of stuff on our plate in both WGs, and much of
it is in that midway done phase were face time is most valuable.
An interim would give us time to resolve several sticky technical issues
and then get drafts out before the cutoff date for IETF54.  I think
we could have a much more productive meeting in Japan as a result.


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



From daemon@optimus.ietf.org  Sat Apr 13 18:11:26 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29627
	for <sipping-archive@odin.ietf.org>; Sat, 13 Apr 2002 18:11:26 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA20198
	for sipping-archive@odin.ietf.org; Sat, 13 Apr 2002 18:11:29 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA20050;
	Sat, 13 Apr 2002 18:01:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA20020
	for <sipping@optimus.ietf.org>; Sat, 13 Apr 2002 18:01:33 -0400 (EDT)
Received: from mail2.intervoice-brite.com (mail2.intervoice-brite.com [204.62.8.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29586
	for <sipping@ietf.org>; Sat, 13 Apr 2002 18:01:29 -0400 (EDT)
Received: from DALNTMS02.ivbi.com (dalntms02.ivbi.com [151.214.90.44])
	by mail2.intervoice-brite.com (Build 101 8.9.3/NT-8.9.3) with ESMTP id RAA01153
	for <sipping@ietf.org>; Sat, 13 Apr 2002 17:06:27 -0500
Received: from 172.16.16.64 (unverified) by DALNTMS02.ivbi.com
 (Content Technologies SMTPRS 4.2.10) with SMTP id <T5a3cadc4e697d65a2c398@DALNTMS02.ivbi.com> for <sipping@ietf.org>;
 Sat, 13 Apr 2002 16:57:57 -0500
Received: from bculpepperpc
	([151.214.91.232])
	by 172.16.16.64; Sat, 13 Apr 2002 17:00:55 -0500
From: "Bert Culpepper" <bert.culpepper@intervoice-brite.com>
To: <sipping@ietf.org>
Cc: "'Fairlie-Cuninghame, Robert'" <rfairlie@nuera.com>,
        "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>
Subject: RE: [Sipping] I-D  ACTION:draft-culpepper-sipping-app-interact-reqs-00.txt
Date: Sat, 13 Apr 2002 18:00:29 -0400
Message-ID: <000001c1e336$a09da670$6500a8c0@bculpepperpc>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

(It seems my post didn't make it to the list intact.  And another comment to
add to one of the "two added points".)

-----Original Message-----
From: Bert Culpepper [mailto:bert.culpepper@intervoice-brite.com]
Sent: Thursday, April 11, 2002 4:54 PM

Two added points below...

> From: Fairlie-Cuninghame, Robert
>
> Thanks for the comments, very helpful.  Bert Culpepper and myself have
> discussed them. Here are our combined responses. Bert please
> speak up if
> I've misrepresented your position or missed anything.
>
> > From: Jonathan Rosenberg
> >
> > This is an excellent start at requirements. Some comments on the
> > requirements there, and some suggestions for additional
> requirements:
> >
> > R1 reads:
> >
> > > The mechanism must support collecting device/user input which
> > >         is associated with an established SIP session but
> must also
> > >         support collecting device/user input that is
> outside of any
> > >         established sessions.
> >
> > I am concerned about the security and scope issues about
> listening for
> > device/user input outside of a session. This seems like a
> > standards-based approach for implementing the government key input
> > snooper.... I know what you had in mind for this (things
> like service
> > activation for call forwarding), but I think that there are
> > better ways
> > to do it (web page, anyone?).
>
> I would agree there are better mechanisms for user service interaction
> outside of a session.  A web interface is certainly viable
> and "richer" for
> control of CLASS 5-like or PBX-like services. I myself am happy with
> dropping this part of the requirement.  On the other hand,
> many SIP devices
> may have no more of a UI than today's common cell phones so
> is a web-based
> mechanism appropriate for these devices?
>

The "outside of a session" part was added to support being able to receive
indications before a SIP session was fully established, (aka "early
sessions").  So do we want to limit the mechanism to established sessions?

[additional comments] First, "early dialog" was meant above, and the
requirement should be re-worded I think so this is clear.  Second, related
to service activation Jonathan mentions above, I can see using SIP for these
things where no SIP session is in progress or established may be (in fact is
most likely) a misuse of the protocol.  For the kinds of service activation
mentioned above, a user could "call" the service and interact with it using
the resulting mechanism we're going for here if the user device was protocol
limited.  I can see other means for doing this (service activation/control)
too so the second part of the requirement is not needed IMHO.

[snip]

>
> >
> > >  R6:  The mechanism must support filtering so that only user
> > >         indications of interest are transmitted.
> >
> > I don't know what this means.
>
> Well, an application that wants only digits should be able to apply a
> generate a request so that only it gets digits.  This may
> help the problem
> of "application interaction" and bandwidth.  Agree that
> filtering is not a
> good word - will re-write.
>

The comment above got garbled...the requestor should be able to apply a
"mask" so that it is possible to request a subset of supported UI
indications.  This "mask" (or whatever) should of course be able to do other
things as indicated above.

[snip]

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 daemon@optimus.ietf.org  Sun Apr 14 06:31:54 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16495
	for <sipping-archive@odin.ietf.org>; Sun, 14 Apr 2002 06:31:54 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA23847
	for sipping-archive@odin.ietf.org; Sun, 14 Apr 2002 06:31:55 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA22421;
	Sun, 14 Apr 2002 05:59:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA22390
	for <sipping@optimus.ietf.org>; Sun, 14 Apr 2002 05:59:06 -0400 (EDT)
Received: from exchange1.nuera.com ([12.105.228.79])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16217
	for <sipping@ietf.org>; Sun, 14 Apr 2002 05:59:02 -0400 (EDT)
Received: by exchange1.nuera.com with Internet Mail Service (5.5.2653.19)
	id <2HAD2ST6>; Sun, 14 Apr 2002 02:59:41 -0700
Message-ID: <E79883AEA37FD411A58C00508BAC5F4B01D38C6C@exchange1.nuera.com>
From: "Fairlie-Cuninghame, Robert" <rfairlie@nuera.com>
To: "'Bert Culpepper'" <bert.culpepper@intervoice-brite.com>, sipping@ietf.org
Cc: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>
Subject: RE: [Sipping] I-D  ACTION:draft-culpepper-sipping-app-interact-re
	qs-00.txt
Date: Sun, 14 Apr 2002 02:59:36 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

> 
> The "outside of a session" part was added to support being 
> able to receive
> indications before a SIP session was fully established, (aka "early
> sessions").  So do we want to limit the mechanism to 
> established sessions?

I believe that "outside of a session" and "early dialog" dialog subscription
are two entirely different beasts and should be considered differently.
"Outside a session" subscriptions relate to NO other dialogs; "early
"subscriptions relate to a session that is in the progress of being
established - but they still relate to a dialog. . 

I guess there are two types of "early" subscription. The first is a
subscription established before the session dialog has become established
but only becomes active when the session becomes established. This is needed
to ensure an appln doesn't miss any user indications when the session
becomes active. The second is where the subscription becomes active while
the sessions is still only an early dialog. This allows a number of services
such as pre-ring PIN identification. We allowed this type of subscription in
our key-events draft but now I'm having second thoughts. Allowing this
mechanism could encourage people to do things in early dialogs that should
only be done in established sessions. For instance, the pre-ring PIN
identification should perhaps really be done in an established session to
the "SIP answering machine"  rather than an early session. 

Can anybody think of any legitimate reasons where user indications are
needed before a (possibly forked) subscription becomes active?

Robert.

> [additional comments] First, "early dialog" was meant above, and the
> requirement should be re-worded I think so this is clear.  
> Second, related
> to service activation Jonathan mentions above, I can see 
> using SIP for these
> things where no SIP session is in progress or established may 
> be (in fact is
> most likely) a misuse of the protocol.  For the kinds of 
> service activation
> mentioned above, a user could "call" the service and interact 
> with it using
> the resulting mechanism we're going for here if the user 
> device was protocol
> limited.  I can see other means for doing this (service 
> activation/control)
> too so the second part of the requirement is not needed IMHO.
> 
> [snip]
> 
> >
> > >
> > > >  R6:  The mechanism must support filtering so that only user
> > > >         indications of interest are transmitted.
> > >
> > > I don't know what this means.
> >
> > Well, an application that wants only digits should be able 
> to apply a
> > generate a request so that only it gets digits.  This may
> > help the problem
> > of "application interaction" and bandwidth.  Agree that
> > filtering is not a
> > good word - will re-write.
> >
> 
> The comment above got garbled...the requestor should be able 
> to apply a
> "mask" so that it is possible to request a subset of supported UI
> indications.  This "mask" (or whatever) should of course be 
> able to do other
> things as indicated above.
> 
> [snip]
> 
> 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 daemon@optimus.ietf.org  Sun Apr 14 17:12:47 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22535
	for <sipping-archive@odin.ietf.org>; Sun, 14 Apr 2002 17:12:47 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA15678
	for sipping-archive@odin.ietf.org; Sun, 14 Apr 2002 17:12:50 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA14386;
	Sun, 14 Apr 2002 16:59:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA14333
	for <sipping@optimus.ietf.org>; Sun, 14 Apr 2002 16:59:54 -0400 (EDT)
Received: from imo-m07.mx.aol.com (imo-m07.mx.aol.com [64.12.136.162])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22381;
	Sun, 14 Apr 2002 16:59:50 -0400 (EDT)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m07.mx.aol.com (mail_out_v32.5.) id c.c.2669c2fb (30972);
	Sun, 14 Apr 2002 16:59:14 -0400 (EDT)
Message-ID: <c.2669c2fb.29eb47a2@aol.com>
Date: Sun, 14 Apr 2002 16:59:14 EDT
Subject: Re: [Sipping] SIP/SIPPING Interim Meeting
To: rohan@cisco.com, ietf@ietf.org, sip@ietf.org, sipping@ietf.org
CC: dwillis@dynamicsoft.com, brian.rosen@marconi.com, jo@ipdialog.com,
        mankin@isi.edu, sob@harvard.edu
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_c.2669c2fb.29eb47a2_boundary"
X-Mailer: AOL 6.0 for Windows US sub 10524
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


--part1_c.2669c2fb.29eb47a2_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 4/13/02 4:43:51 PM Eastern Daylight Time, rohan@cisco.com 
writes:


> I'd like to announce a joint SIP/SIPPING interim meeting May 6-7 in Las
> Vegas, Nevada.  This date and location were changed (with AD approval)
> as a fallback due to conflicts with the previously proposed time and place
> (Boston, the following week).
> 
> 
What happened to the 30 day advance notice (as your 4 April e-mail said was 
required)? I'm sure that other besides myself have already planned other 
things for May 6-7, since no interim meeting was announced on time.

Mike


--part1_c.2669c2fb.29eb47a2_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 4/13/02 4:43:51 PM Eastern Daylight Time, rohan@cisco.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">I'd like to announce a joint SIP/SIPPING interim meeting May 6-7 in Las
<BR>Vegas, Nevada. &nbsp;This date and location were changed (with AD approval)
<BR>as a fallback due to conflicts with the previously proposed time and place
<BR>(Boston, the following week).
<BR>
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">What happened to the 30 day advance notice (as your 4 April e-mail said was required)? I'm sure that other besides myself have already planned other things for May 6-7, since no interim meeting was announced on time.
<BR>
<BR>Mike
<BR></FONT></HTML>

--part1_c.2669c2fb.29eb47a2_boundary--

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



From daemon@optimus.ietf.org  Sun Apr 14 23:30:59 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27712
	for <sipping-archive@odin.ietf.org>; Sun, 14 Apr 2002 23:30:59 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA29514
	for sipping-archive@odin.ietf.org; Sun, 14 Apr 2002 23:31:02 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA29027;
	Sun, 14 Apr 2002 23:20:48 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA28973
	for <sipping@optimus.ietf.org>; Sun, 14 Apr 2002 23:20:44 -0400 (EDT)
Received: from ierw.net.avaya.com (ierw.net.avaya.com [198.152.13.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27325;
	Sun, 14 Apr 2002 23:20:35 -0400 (EDT)
Received: from ierw.net.avaya.com (localhost [127.0.0.1])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id XAA09647;
	Sun, 14 Apr 2002 23:18:57 -0400 (EDT)
Received: from cof110avexu1.global.avaya.com (h135-9-6-16.avaya.com [135.9.6.16])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id XAA09634;
	Sun, 14 Apr 2002 23:18:57 -0400 (EDT)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E42C.9979843A"
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Subject: RE: [Sipping] SIP/SIPPING Interim Meeting
Date: Sun, 14 Apr 2002 21:21:14 -0600
Message-ID: <EF4C65F18BE6464B8E9DF3C212B6B29301637F70@cof110avexu1.global.avaya.com>
Thread-Topic: [Sipping] SIP/SIPPING Interim Meeting
Thread-Index: AcHj+AqSZns5TevyR+ufe3TBYtVP5AANCXfg
From: "Zmolek, Andrew (Andrew)" <zmolek@avaya.com>
To: <Mpierce1@aol.com>, <rohan@cisco.com>, <ietf@ietf.org>, <sip@ietf.org>,
        <sipping@ietf.org>
Cc: <dwillis@dynamicsoft.com>, <brian.rosen@marconi.com>, <jo@ipdialog.com>,
        <mankin@isi.edu>, <sob@harvard.edu>
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

This is a multi-part message in MIME format.

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

This date also conflicts with upcoming W3C meetings. What was the =
conflict with the following week?
=20
--Andy

-----Original Message-----
From: Mpierce1@aol.com [mailto:Mpierce1@aol.com]
Sent: Sunday, April 14, 2002 2:59 PM
To: rohan@cisco.com; ietf@ietf.org; sip@ietf.org; sipping@ietf.org
Cc: dwillis@dynamicsoft.com; brian.rosen@marconi.com; jo@ipdialog.com; =
mankin@isi.edu; sob@harvard.edu
Subject: Re: [Sipping] SIP/SIPPING Interim Meeting


In a message dated 4/13/02 4:43:51 PM Eastern Daylight Time, =
rohan@cisco.com writes:=20




I'd like to announce a joint SIP/SIPPING interim meeting May 6-7 in Las=20
Vegas, Nevada.  This date and location were changed (with AD approval)=20
as a fallback due to conflicts with the previously proposed time and =
place=20
(Boston, the following week).=20




What happened to the 30 day advance notice (as your 4 April e-mail said =
was required)? I'm sure that other besides myself have already planned =
other things for May 6-7, since no interim meeting was announced on =
time.=20

Mike=20



------_=_NextPart_001_01C1E42C.9979843A
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.2715.400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D555181803-15042002><FONT face=3DArial color=3D#0000ff =
size=3D2>This=20
date also conflicts with upcoming W3C meetings. What was the conflict =
with the=20
following week?</FONT></SPAN></DIV>
<DIV><SPAN class=3D555181803-15042002><FONT face=3DArial color=3D#0000ff =

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

size=3D2>--Andy</FONT></SPAN></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Mpierce1@aol.com=20
  [mailto:Mpierce1@aol.com]<BR><B>Sent:</B> Sunday, April 14, 2002 2:59=20
  PM<BR><B>To:</B> rohan@cisco.com; ietf@ietf.org; sip@ietf.org;=20
  sipping@ietf.org<BR><B>Cc:</B> dwillis@dynamicsoft.com;=20
  brian.rosen@marconi.com; jo@ipdialog.com; mankin@isi.edu;=20
  sob@harvard.edu<BR><B>Subject:</B> Re: [Sipping] SIP/SIPPING Interim=20
  Meeting<BR><BR></FONT></DIV><FONT face=3Darial,helvetica><FONT =
size=3D2>In a=20
  message dated 4/13/02 4:43:51 PM Eastern Daylight Time, =
rohan@cisco.com=20
  writes: <BR><BR><BR>
  <BLOCKQUOTE=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px"=20
  TYPE=3D"CITE">I'd like to announce a joint SIP/SIPPING interim meeting =
May 6-7=20
    in Las <BR>Vegas, Nevada. &nbsp;This date and location were changed =
(with AD=20
    approval) <BR>as a fallback due to conflicts with the previously =
proposed=20
    time and place <BR>(Boston, the following week). =
<BR><BR></FONT><FONT lang=3D0=20
    face=3DArial color=3D#000000 size=3D3=20
  FAMILY=3D"SANSSERIF"></BLOCKQUOTE><BR></FONT><FONT lang=3D0 =
face=3DArial=20
  color=3D#000000 size=3D2 FAMILY=3D"SANSSERIF">What happened to the 30 =
day advance=20
  notice (as your 4 April e-mail said was required)? I'm sure that other =
besides=20
  myself have already planned other things for May 6-7, since no interim =
meeting=20
  was announced on time. <BR><BR>Mike=20
<BR></BLOCKQUOTE></FONT></FONT></BODY></HTML>

------_=_NextPart_001_01C1E42C.9979843A--

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



From daemon@optimus.ietf.org  Mon Apr 15 12:39:53 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25679
	for <sipping-archive@odin.ietf.org>; Mon, 15 Apr 2002 12:39:53 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA26853
	for sipping-archive@odin.ietf.org; Mon, 15 Apr 2002 12:39:54 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA24393;
	Mon, 15 Apr 2002 12:10:45 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA24340
	for <sipping@ns.ietf.org>; Mon, 15 Apr 2002 12:10:41 -0400 (EDT)
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22085;
	Mon, 15 Apr 2002 12:10:37 -0400 (EDT)
Received: from JMPOLK-W2K (ssh-sjc-1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id JAA06475; Mon, 15 Apr 2002 09:10:08 -0700 (PDT)
Message-Id: <4.1.20020415103657.016784e0@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Mon, 15 Apr 2002 11:10:06 -0500
To: Rohan Mahy <rohan@cisco.com>, <sip@ietf.org>, <sipping@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [Sipping] SIP/SIPPING Interim Meeting
In-Reply-To: <Pine.WNT.4.44.0204131324400.-17957-100000@chorizo.rapidcon
 vergence.com>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_5317165==_.ALT"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

--=====================_5317165==_.ALT
Content-Type: text/plain; charset="us-ascii"

At 01:39 PM 4/13/2002 -0700, Rohan Mahy wrote:
>Hi,
>
>I'd like to announce a joint SIP/SIPPING interim meeting May 6-7 in Las
>Vegas, Nevada.  

You chose the week of InterOp Las Vegas, plan on having the meeting *at* the
same location as that convention, and have really confirmed that there are
rooms available at the hotel attached to the convention center?!

Seems even if you've picked a location that does have the room, that you
couldn't have picked a more hectic week or place to have it in (except maybe
CES week in Januarys)...

Or was this a plan to have during InterOp?

>this date and location were changed (with AD approval)
>as a fallback due to conflicts with the previously proposed time and place
>(Boston, the following week).
*************************************
"People generally demand more respect for their own rights than they are
willing to allow for others"

James M. Polk
Consulting Engineer
Office of the CTO

Cisco Systems
2200 East President George Bush Turnpike 
Richardson, TX  75082 USA
w) 972.813.5208
f)  972.813.5280
www.cisco.com
--=====================_5317165==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
At 01:39 PM 4/13/2002 -0700, Rohan Mahy wrote:<br>
&gt;Hi,<br>
&gt;<br>
&gt;I'd like to announce a joint SIP/SIPPING interim meeting May 6-7 in
Las<br>
&gt;Vegas, Nevada.&nbsp; <br>
<br>
You chose the week of<u> InterOp Las Vegas</u>, plan on having the
meeting *at* the same location as that convention, and have really
confirmed that there are rooms available at the hotel attached to the
convention center?!<br>
<br>
Seems even if you've picked a location that does have the room, that you
couldn't have picked a more hectic week or place to have it in (except
maybe CES week in Januarys)...<br>
<br>
Or was this a plan to have during InterOp?<br>
<br>
&gt;this date and location were changed (with AD approval)<br>
&gt;as a fallback due to conflicts with the previously proposed time and
place<br>
&gt;(Boston, the following week).<br>

<div align="center">
*************************************<br>
&quot;People generally demand more respect for their own rights than they
are willing to allow for others&quot;<br>
<br>
</div>
James M. Polk<br>
Consulting Engineer<br>
Office of the CTO<br>
<br>
Cisco Systems<br>
2200 East President George Bush Turnpike <br>
Richardson, TX&nbsp; 75082 USA<br>
w) 972.813.5208<br>
f)&nbsp; 972.813.5280<br>
<a href="http://www.cisco.com/" eudora="autourl">www.cisco.com</a></html>

--=====================_5317165==_.ALT--


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



From daemon@optimus.ietf.org  Mon Apr 15 12:57:41 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27680
	for <sipping-archive@odin.ietf.org>; Mon, 15 Apr 2002 12:57:41 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA28370
	for sipping-archive@odin.ietf.org; Mon, 15 Apr 2002 12:57:43 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA27098;
	Mon, 15 Apr 2002 12:43:40 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA27068
	for <sipping@optimus.ietf.org>; Mon, 15 Apr 2002 12:43:37 -0400 (EDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26494
	for <sipping@ietf.org>; Mon, 15 Apr 2002 12:43:35 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g3FGh687024873
	for <sipping@ietf.org>; Mon, 15 Apr 2002 09:43:06 -0700 (PDT)
Received: from localhost (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint)
	with ESMTP id ACV76219;
	Mon, 15 Apr 2002 09:43:05 -0700 (PDT)
Date: Mon, 15 Apr 2002 09:40:13 -0700 (Pacific Daylight Time)
From: Rohan Mahy <rohan@cisco.com>
To: sipping@ietf.org
Message-ID: <Pine.WNT.4.44.0204150939580.-430659@chorizo.rapidconvergence.com>
X-X-Sender: rmahy@imop.cisco.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Sipping] rooms for interim
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


Hi,

Rooms during the Interim can be reserved here:

http://www.pkghlrss.com/liveres/res.asp?EventCode=nilvgen0501&action=new

thanks,
-rohan




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



From daemon@optimus.ietf.org  Mon Apr 15 13:57:25 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00179
	for <sipping-archive@odin.ietf.org>; Mon, 15 Apr 2002 13:57:25 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA02317
	for sipping-archive@odin.ietf.org; Mon, 15 Apr 2002 13:57:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA00238;
	Mon, 15 Apr 2002 13:24:24 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA00119
	for <sipping@optimus.ietf.org>; Mon, 15 Apr 2002 13:24:13 -0400 (EDT)
Received: from zctfs063.nortelnetworks.com (zctfs063.nortelnetworks.com [47.164.128.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28747;
	Mon, 15 Apr 2002 13:24:10 -0400 (EDT)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by zctfs063.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3FHNUg15284;
	Mon, 15 Apr 2002 19:23:30 +0200 (MEST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <HLDBRQ9C>; Mon, 15 Apr 2002 18:23:30 +0100
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7137@zwcwd00r.europe.nortel.com>
From: "Mark Watson"<mwatson@nortelnetworks.com>
To: "'David R. Oran'" <oran@cisco.com>,
        "'Rosen, Brian'"
	 <Brian.Rosen@marconi.com>, Mpierce1@aol.com,
        sip@ietf.org, "'sipping@ietf.org'" <sipping@ietf.org>
Date: Mon, 15 Apr 2002 18:23:26 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E4A2.40D159C2"
Subject: [Sipping] Network Asserted Identity (was: RE: Summary of RE: [Sip] Comment,
 SIP Privacy draft)
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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_01C1E4A2.40D159C2
Content-Type: text/plain

OK, so lets see if we can conclude on _short-term_ Network Asserted identity
requirements in a separate thread. Follow-ups to SIPPING ONLY please.

First, assume a trust domain model as per privacy draft applicability
statement. Entities within a domain trust each other, entities in different
domains are mutually untrusted.

I'll try to build up the requirements, least contraversial first:
NAI1) The ability for network entities to insert a network asserted identity
and pass to other network entities within the same trust domain.
NAI2) The ability for a network entity to pass a (non-private) network
asserted identity directly to a UA
NAI3) Secure transport of network asserted identity across 'untrusted'
networks back to the same trust domain (including between trust 'islands' -
disconnected parts of a single trust domain)
NAI4) Transport of network asserted identity between trust domains (i.e.
transport in one domain of a network asserted identity received from another
domain)

For clarity, 
(a) the requirement for a user to choose one of a number of identities,
whilst retaining privacy, is a 3GPP requirement, but is *out of scope* of
this thread.
(b) Call Trace implemented by encrypting the identity and passing this to
the called user, who can then pass the encrypted identity to the generating
service provider/authorities, is considered a sub-case of NAI3 - the
identity is passed to the 'untrusted' user and back to the original Trust
Domain (the Service Provider) before being passed to the authorities.

I expect the From/To debate will continue, probably to the end of time, but
I don't see a strong relationship with this issue.

If people agree with my statement of the potential requirements, perhaps we
could open discussion on which of these should be considered for immediate
standardisation. The others can be put into the pot for discussion of the
generic privacy requirements.

For my part, I am most concerned about NAI1 and NAI2.

Regards...Mark

> -----Original Message-----
> From: David R. Oran [mailto:oran@cisco.com]
> Sent: 15 April 2002 17:39
> To: 'Rosen, Brian'; Mpierce1@aol.com; sip@ietf.org
> Subject: RE: Summary of RE: [Sip] Comment, SIP Privacy draft
> 
> 
> Brian Rosen wrote:
> >If we could get consensus that trace-with-anonymity is the problem,
> then > we can
> > work on solutions.  Until we get to something as straightforward as 
> > that,
> > we are going to spin a lot of wheels.
> 
> That's always been the prime motivator for me, plus the 
> secondary use of
> NAI for call return to an anonymous caller.
> 
> Dave
> 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 

------_=_NextPart_001_01C1E4A2.40D159C2
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.2655.35">
<TITLE>Network Asserted Identity (was: RE: Summary of RE: [Sip] =
Comment, SIP Privacy draft)</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>OK, so lets see if we can conclude on _short-term_ =
Network Asserted identity requirements in a separate thread. Follow-ups =
to SIPPING ONLY please.</FONT></P>

<P><FONT SIZE=3D2>First, assume a trust domain model as per privacy =
draft applicability statement. Entities within a domain trust each =
other, entities in different domains are mutually untrusted.</FONT></P>

<P><FONT SIZE=3D2>I'll try to build up the requirements, least =
contraversial first:</FONT>
<BR><FONT SIZE=3D2>NAI1) The ability for network entities to insert a =
network asserted identity and pass to other network entities within the =
same trust domain.</FONT></P>

<P><FONT SIZE=3D2>NAI2) The ability for a network entity to pass a =
(non-private) network asserted identity directly to a UA</FONT>
<BR><FONT SIZE=3D2>NAI3) Secure transport of network asserted identity =
across 'untrusted' networks back to the same trust domain (including =
between trust 'islands' - disconnected parts of a single trust =
domain)</FONT></P>

<P><FONT SIZE=3D2>NAI4) Transport of network asserted identity between =
trust domains (i.e. transport in one domain of a network asserted =
identity received from another domain)</FONT></P>

<P><FONT SIZE=3D2>For clarity, </FONT>
<BR><FONT SIZE=3D2>(a) the requirement for a user to choose one of a =
number of identities, whilst retaining privacy, is a 3GPP requirement, =
but is *out of scope* of this thread.</FONT></P>

<P><FONT SIZE=3D2>(b) Call Trace implemented by encrypting the identity =
and passing this to the called user, who can then pass the encrypted =
identity to the generating service provider/authorities, is considered =
a sub-case of NAI3 - the identity is passed to the 'untrusted' user and =
back to the original Trust Domain (the Service Provider) before being =
passed to the authorities.</FONT></P>

<P><FONT SIZE=3D2>I expect the From/To debate will continue, probably =
to the end of time, but I don't see a strong relationship with this =
issue.</FONT></P>

<P><FONT SIZE=3D2>If people agree with my statement of the potential =
requirements, perhaps we could open discussion on which of these should =
be considered for immediate standardisation. The others can be put into =
the pot for discussion of the generic privacy requirements.</FONT></P>

<P><FONT SIZE=3D2>For my part, I am most concerned about NAI1 and =
NAI2.</FONT>
</P>

<P><FONT SIZE=3D2>Regards...Mark</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: David R. Oran [<A =
HREF=3D"mailto:oran@cisco.com">mailto:oran@cisco.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: 15 April 2002 17:39</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'Rosen, Brian'; Mpierce1@aol.com; =
sip@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: Summary of RE: [Sip] Comment, SIP =
Privacy draft</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Brian Rosen wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;If we could get consensus that =
trace-with-anonymity is the problem,</FONT>
<BR><FONT SIZE=3D2>&gt; then &gt; we can</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; work on solutions.&nbsp; Until we get to =
something as straightforward as </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; that,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; we are going to spin a lot of =
wheels.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; That's always been the prime motivator for me, =
plus the </FONT>
<BR><FONT SIZE=3D2>&gt; secondary use of</FONT>
<BR><FONT SIZE=3D2>&gt; NAI for call return to an anonymous =
caller.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Dave</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Sip mailing list&nbsp; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sip" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/sip</A></FONT>
<BR><FONT SIZE=3D2>&gt; This list is for NEW development of the core =
SIP Protocol</FONT>
<BR><FONT SIZE=3D2>&gt; Use sip-implementors@cs.columbia.edu for =
questions on current sip</FONT>
<BR><FONT SIZE=3D2>&gt; Use sipping@ietf.org for new developments on =
the application of sip</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E4A2.40D159C2--

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



From daemon@optimus.ietf.org  Mon Apr 15 14:58:03 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02873
	for <sipping-archive@odin.ietf.org>; Mon, 15 Apr 2002 14:58:03 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA05935
	for sipping-archive@odin.ietf.org; Mon, 15 Apr 2002 14:58:05 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA04985;
	Mon, 15 Apr 2002 14:38:09 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA04954
	for <sipping@optimus.ietf.org>; Mon, 15 Apr 2002 14:38:02 -0400 (EDT)
Received: from magus.nostrum.com (root@magus.nostrum.com [66.119.225.66])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02137
	for <sipping@ietf.org>; Mon, 15 Apr 2002 14:37:58 -0400 (EDT)
Received: from txbcampbell (root@magus.nostrum.com [66.119.225.66])
	by magus.nostrum.com (8.11.0/8.11.0) with SMTP id g3FIbxX65025
	for <sipping@ietf.org>; Mon, 15 Apr 2002 13:37:59 -0500 (CDT)
From: "Ben Campbell" <bcampbell@dynamicsoft.com>
To: <sipping@ietf.org>
Subject: RE: [Sipping] Network Asserted Identity (was: RE: Summary of RE: [Sip] Comment, SIP Privacy draft)
Date: Mon, 15 Apr 2002 13:37:37 -0500
Message-ID: <HNEOJECGFHIABDLENMMCCENOCFAA.bcampbell@dynamicsoft.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_007D_01C1E482.B52E5B00"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <A3C2399B2FACD411A54200508BE39C74054F7137@zwcwd00r.europe.nortel.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_007D_01C1E482.B52E5B00
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Network Asserted Identity (was: RE: Summary of RE: [Sip] Comment, SIP
Privacy draft)
  -----Original Message-----
  From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]On Behalf Of
Mark Watson
  Sent: Monday, April 15, 2002 12:23 PM
  To: 'David R. Oran'; 'Rosen, Brian'; Mpierce1@aol.com; sip@ietf.org;
'sipping@ietf.org'
  Subject: [Sipping] Network Asserted Identity (was: RE: Summary of RE:
[Sip] Comment, SIP Privacy draft)


  OK, so lets see if we can conclude on _short-term_ Network Asserted
identity requirements in a separate thread. Follow-ups to SIPPING ONLY
please.

  First, assume a trust domain model as per privacy draft applicability
statement. Entities within a domain trust each other, entities in different
domains are mutually untrusted.

  I'll try to build up the requirements, least contraversial first:
  NAI1) The ability for network entities to insert a network asserted
identity and pass to other network entities within the same trust domain.

  NAI2) The ability for a network entity to pass a (non-private) network
asserted identity directly to a UA
  NAI3) Secure transport of network asserted identity across 'untrusted'
networks back to the same trust domain (including between trust 'islands' -
disconnected parts of a single trust domain)

  What do we mean by secure? Does this mean non-disclosure of a _private_
NAI to the untrusted domain? Preventing the untrusted domain from tampering
with the NAI (private or otherwise)? I realize we may have discussed that
elsewhere, but we should capture it in the requirement nonetheless. (Note
that I am _not_ disagreeing for a change :-) )

   NAI4) Transport of network asserted identity between trust domains (i.e.
transport in one domain of a network asserted identity received from another
domain)

  Should there be a "Secure" in this requirement as well?

  For clarity,
  (a) the requirement for a user to choose one of a number of identities,
whilst retaining privacy, is a 3GPP requirement, but is *out of scope* of
this thread.

  (b) Call Trace implemented by encrypting the identity and passing this to
the called user, who can then pass the encrypted identity to the generating
service provider/authorities, is considered a sub-case of NAI3 - the
identity is passed to the 'untrusted' user and back to the original Trust
Domain (the Service Provider) before being passed to the authorities.

  I expect the From/To debate will continue, probably to the end of time,
but I don't see a strong relationship with this issue.

  If people agree with my statement of the potential requirements, perhaps
we could open discussion on which of these should be considered for
immediate standardisation. The others can be put into the pot for discussion
of the generic privacy requirements.

  For my part, I am most concerned about NAI1 and NAI2.

  Regards...Mark

  > -----Original Message-----
  > From: David R. Oran [mailto:oran@cisco.com]
  > Sent: 15 April 2002 17:39
  > To: 'Rosen, Brian'; Mpierce1@aol.com; sip@ietf.org
  > Subject: RE: Summary of RE: [Sip] Comment, SIP Privacy draft
  >
  >
  > Brian Rosen wrote:
  > >If we could get consensus that trace-with-anonymity is the problem,
  > then > we can
  > > work on solutions.  Until we get to something as straightforward as
  > > that,
  > > we are going to spin a lot of wheels.
  >
  > That's always been the prime motivator for me, plus the
  > secondary use of
  > NAI for call return to an anonymous caller.
  >
  > Dave
  >
  >
  > _______________________________________________
  > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
  > This list is for NEW development of the core SIP Protocol
  > Use sip-implementors@cs.columbia.edu for questions on current sip
  > Use sipping@ietf.org for new developments on the application of sip
  >


------=_NextPart_000_007D_01C1E482.B52E5B00
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><TITLE>Network Asserted Identity (was: RE: Summary of RE: =
[Sip] Comment, SIP Privacy draft)</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2715.400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> =
sipping-admin@ietf.org=20
  [mailto:sipping-admin@ietf.org]<B>On Behalf Of </B>Mark =
Watson<BR><B>Sent:</B>=20
  Monday, April 15, 2002 12:23 PM<BR><B>To:</B> 'David R. Oran'; 'Rosen, =
Brian';=20
  Mpierce1@aol.com; sip@ietf.org; 'sipping@ietf.org'<BR><B>Subject:</B>=20
  [Sipping] Network Asserted Identity (was: RE: Summary of RE: [Sip] =
Comment,=20
  SIP Privacy draft)<BR><BR></FONT></DIV>
  <P><FONT size=3D2>OK, so lets see if we can conclude on _short-term_ =
Network=20
  Asserted identity requirements in a separate thread. Follow-ups to =
SIPPING=20
  ONLY please.</FONT></P>
  <P><FONT size=3D2>First, assume a trust domain model as per privacy =
draft=20
  applicability statement. Entities within a domain trust each other, =
entities=20
  in different domains are mutually untrusted.</FONT></P>
  <P><FONT size=3D2>I'll try to build up the requirements, least =
contraversial=20
  first:</FONT> <BR><FONT size=3D2>NAI1) The ability for network =
entities to=20
  insert a network asserted identity and pass to other network entities =
within=20
  the same trust domain.</FONT></P>
  <P><FONT size=3D2>NAI2) The ability for a network entity to pass a =
(non-private)=20
  network asserted identity directly to a UA</FONT> <BR><FONT =
size=3D2>NAI3)=20
  Secure transport of network asserted identity across 'untrusted' =
networks back=20
  to the same trust domain (including between trust 'islands' - =
disconnected=20
  parts of a single trust domain)</FONT></P>
  <P><FONT size=3D2><SPAN class=3D853283218-15042002><FONT face=3DArial=20
  color=3D#0000ff>What do we mean by secure? Does this&nbsp;mean =
non-disclosure=20
  of&nbsp;a _private_ NAI to the untrusted domain? Preventing the =
untrusted=20
  domain from tampering with the NAI (private or otherwise)?&nbsp;I =
realize we=20
  may have discussed that elsewhere, but we should capture it in the =
requirement=20
  nonetheless. (Note that I am _not_ disagreeing for a change :-) )=20
  </FONT></SPAN></FONT></P>
  <P><FONT size=3D2><SPAN class=3D853283218-15042002>&nbsp;</SPAN>NAI4) =
Transport of=20
  network asserted identity between trust domains (i.e. transport in one =
domain=20
  of a network asserted identity received from another domain)<SPAN=20
  class=3D853283218-15042002><FONT face=3DArial=20
  color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></P>
  <P><FONT size=3D2><SPAN class=3D853283218-15042002><FONT face=3DArial=20
  color=3D#0000ff>Should there be a&nbsp;"Secure" in this requirement as =

  well?</FONT>&nbsp;</SPAN></FONT></P>
  <P><FONT size=3D2>For clarity, </FONT><BR><FONT size=3D2>(a) the =
requirement for a=20
  user to choose one of a number of identities, whilst retaining =
privacy, is a=20
  3GPP requirement, but is *out of scope* of this thread.</FONT></P>
  <P><FONT size=3D2>(b) Call Trace implemented by encrypting the =
identity and=20
  passing this to the called user, who can then pass the encrypted =
identity to=20
  the generating service provider/authorities, is considered a sub-case =
of NAI3=20
  - the identity is passed to the 'untrusted' user and back to the =
original=20
  Trust Domain (the Service Provider) before being passed to the=20
  authorities.</FONT></P>
  <P><FONT size=3D2>I expect the From/To debate will continue, probably =
to the end=20
  of time, but I don't see a strong relationship with this =
issue.</FONT></P>
  <P><FONT size=3D2>If people agree with my statement of the potential=20
  requirements, perhaps we could open discussion on which of these =
should be=20
  considered for immediate standardisation. The others can be put into =
the pot=20
  for discussion of the generic privacy requirements.</FONT></P>
  <P><FONT size=3D2>For my part, I am most concerned about NAI1 and =
NAI2.</FONT>=20
  </P>
  <P><FONT size=3D2>Regards...Mark</FONT> </P>
  <P><FONT size=3D2>&gt; -----Original Message-----</FONT> <BR><FONT =
size=3D2>&gt;=20
  From: David R. Oran [<A=20
  href=3D"mailto:oran@cisco.com">mailto:oran@cisco.com</A>]</FONT> =
<BR><FONT=20
  size=3D2>&gt; Sent: 15 April 2002 17:39</FONT> <BR><FONT size=3D2>&gt; =
To: 'Rosen,=20
  Brian'; Mpierce1@aol.com; sip@ietf.org</FONT> <BR><FONT size=3D2>&gt; =
Subject:=20
  RE: Summary of RE: [Sip] Comment, SIP Privacy draft</FONT> <BR><FONT=20
  size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; </FONT><BR><FONT =
size=3D2>&gt; Brian=20
  Rosen wrote:</FONT> <BR><FONT size=3D2>&gt; &gt;If we could get =
consensus that=20
  trace-with-anonymity is the problem,</FONT> <BR><FONT size=3D2>&gt; =
then &gt; we=20
  can</FONT> <BR><FONT size=3D2>&gt; &gt; work on solutions.&nbsp; Until =
we get to=20
  something as straightforward as </FONT><BR><FONT size=3D2>&gt; &gt; =
that,</FONT>=20
  <BR><FONT size=3D2>&gt; &gt; we are going to spin a lot of =
wheels.</FONT>=20
  <BR><FONT size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; That's always =
been the=20
  prime motivator for me, plus the </FONT><BR><FONT size=3D2>&gt; =
secondary use=20
  of</FONT> <BR><FONT size=3D2>&gt; NAI for call return to an anonymous=20
  caller.</FONT> <BR><FONT size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; =
Dave</FONT>=20
  <BR><FONT size=3D2>&gt; </FONT><BR><FONT size=3D2>&gt; =
</FONT><BR><FONT=20
  size=3D2>&gt; _______________________________________________</FONT> =
<BR><FONT=20
  size=3D2>&gt; Sip mailing list&nbsp; <A=20
  href=3D"https://www1.ietf.org/mailman/listinfo/sip"=20
  target=3D_blank>https://www1.ietf.org/mailman/listinfo/sip</A></FONT> =
<BR><FONT=20
  size=3D2>&gt; This list is for NEW development of the core SIP =
Protocol</FONT>=20
  <BR><FONT size=3D2>&gt; Use sip-implementors@cs.columbia.edu for =
questions on=20
  current sip</FONT> <BR><FONT size=3D2>&gt; Use sipping@ietf.org for =
new=20
  developments on the application of sip</FONT> <BR><FONT size=3D2>&gt;=20
</FONT></P></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_007D_01C1E482.B52E5B00--


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



From daemon@optimus.ietf.org  Mon Apr 15 15:08:45 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03343
	for <sipping-archive@odin.ietf.org>; Mon, 15 Apr 2002 15:08:45 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA06916
	for sipping-archive@odin.ietf.org; Mon, 15 Apr 2002 15:08:47 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA05518;
	Mon, 15 Apr 2002 14:50:01 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA05486
	for <sipping@optimus.ietf.org>; Mon, 15 Apr 2002 14:49:57 -0400 (EDT)
Received: from zctfs063.nortelnetworks.com (zctfs063.nortelnetworks.com [47.164.128.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02653
	for <sipping@ietf.org>; Mon, 15 Apr 2002 14:49:54 -0400 (EDT)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zctfs063.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3FInOg21986;
	Mon, 15 Apr 2002 20:49:24 +0200 (MEST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3FImjE11702;
	Mon, 15 Apr 2002 19:48:45 +0100 (BST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <HLDBRSAM>; Mon, 15 Apr 2002 19:49:23 +0100
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F713E@zwcwd00r.europe.nortel.com>
From: "Mark Watson"<mwatson@nortelnetworks.com>
To: "'Ben Campbell'" <bcampbell@dynamicsoft.com>, sipping@ietf.org
Subject: RE: [Sipping] Network Asserted Identity (was: RE: Summary of RE: 
	[Sip] Comment, SIP Privacy draft)
Date: Mon, 15 Apr 2002 19:49:22 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E4AD.CAE864EC"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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


NAI3) Secure transport of network asserted identity across 'untrusted'
networks back to the same trust domain (including between trust 'islands' -
disconnected parts of a single trust domain)

What do we mean by secure? Does this mean non-disclosure of a _private_ NAI
to the untrusted domain? Preventing the untrusted domain from tampering with
the NAI (private or otherwise)? I realize we may have discussed that
elsewhere, but we should capture it in the requirement nonetheless. (Note
that I am _not_ disagreeing for a change :-) )  

Good point. I meant preventing the untrusted domain from tampering with or
seeing the NAI (private or otherwise). i.e. it gets passed securely back to
the original trust domain, although I don't suppose we can prevent the
untrusted domain from removing it altogether!

 NAI4) Transport of network asserted identity between trust domains (i.e.
transport in one domain of a network asserted identity received from another
domain) 

Should there be a "Secure" in this requirement as well?  

No, this was the case where the untrusted domain can see, and I guess tamper
with, the NAI.

...Mark

 


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Network Asserted Identity (was: RE: Summary of RE: [Sip] Comment, SIP Privacy draft)</TITLE>

<META content="MSHTML 5.00.3315.2870" name=GENERATOR></HEAD>
<BODY>
<BLOCKQUOTE dir=ltr 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <BLOCKQUOTE dir=ltr 
  style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
    <P><BR><FONT size=2>NAI3) Secure transport of network asserted identity 
    across 'untrusted' networks back to the same trust domain (including between 
    trust 'islands' - disconnected parts of a single trust domain)</FONT></P>
    <P><FONT color=#0000ff><FONT size=2><SPAN class=853283218-15042002><FONT 
    face=Arial>What do we mean by secure? Does this&nbsp;mean non-disclosure 
    of&nbsp;a _private_ NAI to the untrusted domain? Preventing the untrusted 
    domain from tampering with the NAI (private or otherwise)?&nbsp;I realize we 
    may have discussed that elsewhere, but we should capture it in the 
    requirement nonetheless. (Note that I am _not_ disagreeing for a change :-) 
    )&nbsp;<FONT face=Verdana size=1><SPAN 
    class=855065018-15042002>&nbsp;</SPAN></FONT></FONT></SPAN></FONT></FONT></P></BLOCKQUOTE></BLOCKQUOTE>
<P><FONT color=#0000ff><FONT size=2><SPAN class=853283218-15042002><FONT 
face=Arial><FONT face=Verdana size=1><SPAN class=855065018-15042002>Good point. 
I meant preventing the untrusted domain from tampering with or seeing the NAI 
(private or otherwise). i.e. it gets passed securely back to the original trust 
domain, although I don't suppose we can prevent the untrusted domain from 
removing it altogether!</SPAN></FONT></FONT></SPAN></FONT></FONT></P>
<BLOCKQUOTE dir=ltr 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <BLOCKQUOTE dir=ltr 
  style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
    <P><FONT size=2><SPAN class=853283218-15042002>&nbsp;</SPAN>NAI4) Transport 
    of network asserted identity between trust domains (i.e. transport in one 
    domain of a network asserted identity received from another domain)<SPAN 
    class=853283218-15042002><FONT color=#0000ff 
    face=Arial>&nbsp;</FONT></SPAN></FONT></P>
    <P><FONT size=2><SPAN class=853283218-15042002><FONT color=#0000ff 
    face=Arial>Should there be a&nbsp;"Secure" in this requirement as 
    well?</FONT>&nbsp;<FONT color=#0000ff face=Verdana size=1><SPAN 
    class=855065018-15042002>&nbsp;</SPAN></FONT></SPAN></FONT></P></BLOCKQUOTE></BLOCKQUOTE>
<P><FONT size=2><SPAN class=853283218-15042002><FONT color=#0000ff face=Verdana 
size=1><SPAN class=855065018-15042002>No, this was the case where the untrusted 
domain&nbsp;can see, and I guess tamper with, the 
NAI.</SPAN></FONT></SPAN></FONT></P>
<P><FONT color=#0000ff face=Verdana size=1><SPAN 
class=855065018-15042002>...Mark</SPAN></FONT></P>
<P dir=ltr 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">&nbsp;</P></BODY></HTML>

------_=_NextPart_001_01C1E4AD.CAE864EC--

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



From daemon@ns.ietf.org  Tue Apr 16 00:30:07 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15280
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 00:30:06 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA04998
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 00:30:08 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA04269;
	Tue, 16 Apr 2002 00:12:02 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA04236
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 00:11:59 -0400 (EDT)
Received: from oak.neustar.com (oak.neustar.com [209.173.53.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14760
	for <sipping@ietf.org>; Tue, 16 Apr 2002 00:11:55 -0400 (EDT)
Received: from chiimc01.il.neustar.com (stih650b-s1p2.va.neustar.com [209.173.53.65])
	by oak.neustar.com (8.11.0/8.11.0) with ESMTP id g3G4BK820537;
	Tue, 16 Apr 2002 00:11:20 -0400
Received: by chiimc01.il.neustar.com with Internet Mail Service (5.5.2653.19)
	id <204FPJ17>; Mon, 15 Apr 2002 23:11:14 -0500
Message-ID: <A83B38C38B3ED6119D3600306E0722D038BF4F@dc02.npac.com>
From: "Yu, James" <james.yu@neustar.biz>
To: "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>
Cc: sipping@ietf.org
Subject: RE: [Sipping] draft-yu-tel-url-04.txt comment
Date: Mon, 15 Apr 2002 23:11:13 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

> Exactly, because a bis-only compliant implementation would 
> not care about
> those parameters.
> 
> However, bis DOES allow extensions (in this case your draft) 
> define new
> uri-parameters, by using the "other-parms" defined in bis. Then,
> implementations supporting your extension would support the 
> parameters, while
> implementations not supporting them would simply ignore them 
> - according to
> the rules in bis.
> 
> If you, however, put your parameters in the user-part, you may mess up
> implementations not supporting your extension, since bis 
> doesn't specify
> parameters for the user-part (even if it does allow the ";" 
> character).
>

Those parameters (rn, npdi and cic) are defined as the extensions to the tel
URL.  There were discussions on supporting tel URL a while back.  I believe
that bis has included texts that clarifies how parameters in the tel URL
(plus its extensions) are supported in the sip URL.  We are not discussing
how those tel URL extensions can be carried as the url-parameters, that is
implementation issue, as you have indicated.  We are discussing how tel URL
parameters (including extensions) are carried in the sip URL in a "standard"
way.  The consensus is that they'll appear in the user part of the sip URL
when user=phone is present.

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



From daemon@ns.ietf.org  Tue Apr 16 04:55:52 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26660
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 04:55:52 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA29048
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 04:55:55 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA28431;
	Tue, 16 Apr 2002 04:37:45 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA28321
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 04:37:38 -0400 (EDT)
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26480
	for <sipping@ietf.org>; Tue, 16 Apr 2002 04:37:34 -0400 (EDT)
Received: from esvir02nok.ntc.nokia.com (esvir02nokt.ntc.nokia.com [172.21.143.34])
	by mgw-x2.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g3G8br500912
	for <sipping@ietf.org>; Tue, 16 Apr 2002 11:37:53 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir02nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5a4afb8be9ac158f22076@esvir02nok.ntc.nokia.com> for <sipping@ietf.org>;
 Tue, 16 Apr 2002 11:37:35 +0300
Received: from mgw.research.nokia.com ([172.21.33.76]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.3779);
	 Tue, 16 Apr 2002 11:37:35 +0300
Received: from agni.research.nokia.com (agni.research.nokia.com [172.21.40.24])
	by mgw.research.nokia.com (8.9.3/8.9.3) with ESMTP id LAA09361
	for <sipping@ietf.org>; Tue, 16 Apr 2002 11:37:35 +0300 (EETDST)
Received: (from ppessi@localhost)
	by agni.research.nokia.com (8.11.6/8.11.2) id g3G814O09419;
	Tue, 16 Apr 2002 11:01:04 +0300
To: sipping@ietf.org
References: <Pine.WNT.4.44.0204121147410.-360391@chorizo.rapidconvergence.com>
X-face: #V(jdpv[lI!TNUU=2*oh:="#suS*ponXW"yr6G;~L}<xZn_2^0)V{jqdc4y}@2b]ffd}SY#
 :9||1pew85O,WjiYA"6C7bW^zt^+.{b#B{lEE+4$9lrXL(55g}dU>uZ\JfD\"IG#G{j`hZI;=DmT\H
 pfDMyJ`i=:M;BM3R.`[>P^ER8+]i
From: Pekka Pessi <Pekka.Pessi@nokia.com>
In-Reply-To: <Pine.WNT.4.44.0204121147410.-360391@chorizo.rapidconvergence.com>
Date: 16 Apr 2002 11:01:03 +0300
Message-ID: <pvvgasysw0.fsf@agni.research.nokia.com>
Lines: 63
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-OriginalArrivalTime: 16 Apr 2002 08:37:35.0543 (UTC) FILETIME=[F5500C70:01C1E521]
Subject: [Sipping] IPv6 messages for callflows?
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

	Hello,

	I think that a couple of torture messages with IPv6 addresses in
	them would be nice addition. 

	I have attached an INVITE request and a 488 response to it, feel
	free to include them.

						Pekka

-----8<-------------8<-------------8<-------------8<-------------8<-----
7.42 INVITE Request with IPv6 Addresses

   This is a valid INVITE message containing IPv6 addresses. An IPv4-only
   SIP element should be able to parse and respond this request.

   INVITE sip:bob@[3ffe:1200:3012:c006:206:5bff:fe55:462f] SIP/2.0
   Via: SIP/2.0/UDP [3ffe:1200:3012:c006:206:5bff:fe55:462f]
        ;branch=z9hG4bKoHjruVnj9aW
   Via: SIP/2.0/UDP [3ffe:1200:3012:c000:210:a4ff:fe8d:6a46]:5062
        ;branch=z9hG4bKuNCTHs8Lumv
        ;received=[3ffe:1200:3012:c006:210:a4ff:fe8d:6a46]
   From: <sip:alice@[3ffe:1200:3012:c000:210:a4ff:fe8d:6a46]>
        ;tag=ud6a29947
   Record-Route: <sip:bob@example.com;maddr=[fe80::206:5bff:fe55:462f]>
   To: <sip:bob@example.com;maddr=[3ffe:1200:3012:c006:206:5bff:fe55:462f]>
   Call-ID: f89fa68e-5109-11d6-0581-0010A48D6A46
   CSeq: 2 INVITE
   Contact: <sip:[3ffe:1200:3012:c000:210:a4ff:fe8d:6a46]:5062>
   Call-Info: <http://[3ffe:1200:3012:c000:210:a4ff:fe8d:6a46]/alice.gif>
        ;purpose=icon;g-param=[3ffe:1200:3012:c000:210:a4ff:fe8d:6a46]
   Content-Type: application/sdp
   Content-Length: 352

   v=0
   o=alice 1804289383 2 IN IP6 3ffe:1200:3012:c000:210:a4ff:fe8d:6a46
   s=-
   c=IN IP6 3ffe:1200:3012:c000:210:a4ff:fe8d:6a46
   t=0 0
   m=audio 5004 RTP/AVP 96 97 
   a=rtpmap:96 AMR/8000
   a=rtpmap:97 GSM-EFR/8000

7.43 Response message with IPv6 Addresses

   This is a response from IPv4-only host to the INVITE above.

   SIP/2.0 488 Not Acceptable Here
   Via: SIP/2.0/UDP [3ffe:1200:3012:c006:206:5bff:fe55:462f]
        ;branch=z9hG4bKoHjruVnj9aW;received=172.21.40.44
   Via: SIP/2.0/UDP [3ffe:1200:3012:c000:210:a4ff:fe8d:6a46]:5062
        ;branch=z9hG4bKuNCTHs8Lumv
        ;received=[3ffe:1200:3012:c006:210:a4ff:fe8d:6a46]
   From: <sip:alice@[3ffe:1200:3012:c000:210:a4ff:fe8d:6a46]>
        ;tag=ud6a29947
   To: <sip:bob@example.com;maddr=[3ffe:1200:3012:c006:206:5bff:fe55:462f]>
        ;tag=f4ef9d6a
   Call-ID: f89fa68e-5109-11d6-0581-0010A48D6A46
   CSeq: 2 INVITE
   Warning: 301 172.21.40.24 "IN network address type 'IP6' not supported"
   Content-Length: 0

-----8<-------------8<-------------8<-------------8<-------------8<-----

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



From daemon@ns.ietf.org  Tue Apr 16 09:28:02 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02633
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 09:28:02 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA14182
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 09:28:05 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA13059;
	Tue, 16 Apr 2002 09:15:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA13025
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 09:14:59 -0400 (EDT)
Received: from bdsl.66.12.12.130.gte.net (bdsl.66.12.12.130.gte.net [66.12.12.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01562
	for <sipping@ietf.org>; Tue, 16 Apr 2002 09:14:55 -0400 (EDT)
Received: from C1893415A (bdsl.greycouncil.com [127.0.0.1])
	by bdsl.66.12.12.130.gte.net (8.11.6/8.11.6) with SMTP id g3GDERd23114
	for <sipping@ietf.org>; Tue, 16 Apr 2002 08:14:27 -0500
Message-ID: <005d01c1e548$a2c54d90$133fed0c@C1893415A>
From: "Dean Willis" <dean.willis@softarmor.com>
To: "Sipping \(E-mail\)" <sipping@ietf.org>
References: <CD110021698980419241042CF576B8F2012BAB7B@EXCALIBUR.santera.com><009401c1e4bc$699dd320$1c036e3f@TXDWILLIS2> <15547.46611.373594.803557@harjus.eng.song.fi>
Date: Tue, 16 Apr 2002 08:14:27 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Screened From: and Privacy
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit


Some have suggested that we have everything needed to handle caller ID
using the From: field, and that we can reasonably screen callas based on
the "From:" field to assure the veracity of this field value.

We COULD.

But there's a very common usage suggesting otherwise.

Generally, there's some sort of authentication token associated with the
phone, not the user of the phone. For example, in 3PPP it's in the SIM
card. For the Cisco 7960 on my desk, it's in the boot file on the TFTP
server, and for the Pingtel phone on my desk it is stored into the phone
using a web interface.

So really, the service platform is authenticating the phone, not the
user.

So let's say my kid (I don't have one, but we're pretending here) is
using the home phone to call her friend. She doesn't want the call to be
from Dad, she wants it to be "from" her.

Logically:

    From: littlekid
    Authenticated-RPID: Account of Dean Willis 9724735455

Ok, so we could add "littlekid" to the list of "Approved From Fields".
Or we could revamp things so that she gets a "login" and Her Very Own
RPID (which is contractually iffy in many countries)

Now her friend comes over and wants to use the phone to call his mother
. . .

As you can see, this rapidly becomes a provisionng nightmare, and I'd
argue that the From screening provides no useful value anyhow. Much more
useful to leave it as a user provided string with the semantic of "How
the user wants to be though of at the far end".

--
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 daemon@ns.ietf.org  Tue Apr 16 09:39:26 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03528
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 09:39:26 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA15759
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 09:39:29 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA13849;
	Tue, 16 Apr 2002 09:24:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA13805
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 09:24:33 -0400 (EDT)
Received: from bdsl.66.12.12.130.gte.net (bdsl.66.12.12.130.gte.net [66.12.12.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02426;
	Tue, 16 Apr 2002 09:24:28 -0400 (EDT)
Received: from C1893415A (bdsl.greycouncil.com [127.0.0.1])
	by bdsl.66.12.12.130.gte.net (8.11.6/8.11.6) with SMTP id g3GDNrd23221;
	Tue, 16 Apr 2002 08:23:53 -0500
Message-ID: <00af01c1e549$f453caf0$133fed0c@C1893415A>
From: "Dean Willis" <dean.willis@softarmor.com>
To: "Rohan Mahy" <rohan@cisco.com>, <sip@ietf.org>, <sipping@ietf.org>,
        "James M. Polk" <jmpolk@cisco.com>
References: <4.1.20020415103657.016784e0@localhost>
Subject: Re: [Sip] Re: [Sipping] SIP/SIPPING Interim Meeting
Date: Tue, 16 Apr 2002 08:23:53 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00AC_01C1E520.0B345DE0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_00AC_01C1E520.0B345DE0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I don't recall whether this has been explicitly mentioned, but the =
Pulver SIP Summit occurs in conjunction with Interop. So many of the SIP =
people of the world are already in Vegas this week for SIP Summit.  We =
might as well get together formally.

And yes, I was able to book a room at the Riviera, 0.6 miles from the =
convention center, for $90 a night, on the web yesterday afternoon.

--
Dean

  ----- Original Message -----=20
  From: James M. Polk=20
  To: Rohan Mahy ; sip@ietf.org ; sipping@ietf.org=20
  Sent: Monday, April 15, 2002 11:10 AM
  Subject: [Sip] Re: [Sipping] SIP/SIPPING Interim Meeting


  At 01:39 PM 4/13/2002 -0700, Rohan Mahy wrote:
  >Hi,
  >
  >I'd like to announce a joint SIP/SIPPING interim meeting May 6-7 in =
Las
  >Vegas, Nevada. =20

  You chose the week of InterOp Las Vegas, plan on having the meeting =
*at* the same location as that convention, and have really confirmed =
that there are rooms available at the hotel attached to the convention =
center?!

  Seems even if you've picked a location that does have the room, that =
you couldn't have picked a more hectic week or place to have it in =
(except maybe CES week in Januarys)...

  Or was this a plan to have during InterOp?

  >this date and location were changed (with AD approval)
  >as a fallback due to conflicts with the previously proposed time and =
place
  >(Boston, the following week).

  *************************************
  "People generally demand more respect for their own rights than they =
are willing to allow for others"


  James M. Polk
  Consulting Engineer
  Office of the CTO

  Cisco Systems
  2200 East President George Bush Turnpike=20
  Richardson, TX  75082 USA
  w) 972.813.5208
  f)  972.813.5280
  www.cisco.com=20

------=_NextPart_000_00AC_01C1E520.0B345DE0
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=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2715.400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I don't recall whether this has been =
explicitly=20
mentioned, but the Pulver SIP Summit occurs in conjunction with Interop. =
So many=20
of the SIP people of the world are already in Vegas this week for SIP=20
Summit.&nbsp; We might as well get together formally.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>And yes, I was able to book a room at =
the Riviera,=20
0.6 miles from the convention center, for $90 a night, on the web =
yesterday=20
afternoon.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>--<BR>Dean</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Djmpolk@cisco.com href=3D"mailto:jmpolk@cisco.com">James M. =
Polk</A>=20
  </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3Drohan@cisco.com=20
  href=3D"mailto:rohan@cisco.com">Rohan Mahy</A> ; <A =
title=3Dsip@ietf.org=20
  href=3D"mailto:sip@ietf.org">sip@ietf.org</A> ; <A =
title=3Dsipping@ietf.org=20
  href=3D"mailto:sipping@ietf.org">sipping@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Monday, April 15, 2002 =
11:10=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [Sip] Re: [Sipping] =
SIP/SIPPING=20
  Interim Meeting</DIV>
  <DIV><FONT face=3DArial size=3D2></FONT><BR></DIV>At 01:39 PM =
4/13/2002 -0700,=20
  Rohan Mahy wrote:<BR>&gt;Hi,<BR>&gt;<BR>&gt;I'd like to announce a =
joint=20
  SIP/SIPPING interim meeting May 6-7 in Las<BR>&gt;Vegas, Nevada.&nbsp; =

  <BR><BR>You chose the week of<U> InterOp Las Vegas</U>, plan on having =
the=20
  meeting *at* the same location as that convention, and have really =
confirmed=20
  that there are rooms available at the hotel attached to the convention =

  center?!<BR><BR>Seems even if you've picked a location that does have =
the=20
  room, that you couldn't have picked a more hectic week or place to =
have it in=20
  (except maybe CES week in Januarys)...<BR><BR>Or was this a plan to =
have=20
  during InterOp?<BR><BR>&gt;this date and location were changed (with =
AD=20
  approval)<BR>&gt;as a fallback due to conflicts with the previously =
proposed=20
  time and place<BR>&gt;(Boston, the following week).<BR>
  <DIV align=3Dcenter>*************************************<BR>"People =
generally=20
  demand more respect for their own rights than they are willing to =
allow for=20
  others"<BR><BR></DIV>James M. Polk<BR>Consulting Engineer<BR>Office of =
the=20
  CTO<BR><BR>Cisco Systems<BR>2200 East President George Bush Turnpike=20
  <BR>Richardson, TX&nbsp; 75082 USA<BR>w) 972.813.5208<BR>f)&nbsp;=20
  972.813.5280<BR><A href=3D"http://www.cisco.com/"=20
  eudora=3D"autourl">www.cisco.com</A> </BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_00AC_01C1E520.0B345DE0--


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



From daemon@ns.ietf.org  Tue Apr 16 09:42:34 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03774
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 09:42:34 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA16015
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 09:42:37 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA14361;
	Tue, 16 Apr 2002 09:30:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA14318
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 09:30:11 -0400 (EDT)
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02722
	for <sipping@ietf.org>; Tue, 16 Apr 2002 09:30:07 -0400 (EDT)
Received: from mira-sjc5-9.cisco.com (IDENT:mirapoint@mira-sjc5-9.cisco.com [171.71.163.32])
	by sj-msg-core-4.cisco.com (8.12.2/8.12.2) with ESMTP id g3GDTdXf019712;
	Tue, 16 Apr 2002 06:29:39 -0700 (PDT)
Received: from OranLT ([161.44.238.53])
	by mira-sjc5-9.cisco.com (Mirapoint)
	with ESMTP id ACQ54232;
	Tue, 16 Apr 2002 06:29:49 -0700 (PDT)
From: "David R. Oran" <oran@cisco.com>
To: "'Dean Willis'" <dean.willis@softarmor.com>,
        "'Sipping \(E-mail\)'" <sipping@ietf.org>
Subject: RE: [Sipping] Screened From: and Privacy
Date: Tue, 16 Apr 2002 09:22:02 -0400
Organization: Cisco Systems
Message-ID: <005301c1e549$b2dc4d40$35ee2ca1@OranLT>
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.3416
In-Reply-To: <005d01c1e548$a2c54d90$133fed0c@C1893415A>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Viewing things this way, where the "principal" sending and receiving SIP
messages is some amalgam of a "user" and "the phone" is just asking for
trouble, IMHO. It gets into all sorts of issues about who is doing what,
what the "phone" part is trusted with as opposed to the "user", which
identity various identifiers are bound to, etc., etc., etc.

I believe a much cleaner and simpler model is where there is just a
"user". If there are multiple "users" of a single device, then there
are, logically speaking, multiple UAs in the device, as there would be
for a multi-line phone.

To handle the binding between user and device where needed you do two
things:
A) have the user "login" to the device, using whatever local (or at
least non-SIP, machinery you like)
A) have the UA support a "default" user who is logged in automagically
at boot time to handle the lobby phone, auto-login, etc.

This way there is no confusion about who is doing what and who should be
trusted for what. Trust between the device and user is established
outside SIP. Trust between the user and the rest of the SIP elements is
established via SIP security mechanisms. The device is no more or less
privileged than the user using it.

Dave.

> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] 
> On Behalf Of Dean Willis
> Sent: Tuesday, April 16, 2002 9:14 AM
> To: Sipping (E-mail)
> Subject: [Sipping] Screened From: and Privacy
> 
> 
> 
> Some have suggested that we have everything needed to handle 
> caller ID using the From: field, and that we can reasonably 
> screen callas based on the "From:" field to assure the 
> veracity of this field value.
> 
> We COULD.
> 
> But there's a very common usage suggesting otherwise.
> 
> Generally, there's some sort of authentication token 
> associated with the phone, not the user of the phone. For 
> example, in 3PPP it's in the SIM card. For the Cisco 7960 on 
> my desk, it's in the boot file on the TFTP server, and for 
> the Pingtel phone on my desk it is stored into the phone 
> using a web interface.
> 
> So really, the service platform is authenticating the phone, 
> not the user.
> 
> So let's say my kid (I don't have one, but we're pretending 
> here) is using the home phone to call her friend. She doesn't 
> want the call to be from Dad, she wants it to be "from" her.
> 
> Logically:
> 
>     From: littlekid
>     Authenticated-RPID: Account of Dean Willis 9724735455
> 
> Ok, so we could add "littlekid" to the list of "Approved From 
> Fields". Or we could revamp things so that she gets a "login" 
> and Her Very Own RPID (which is contractually iffy in many countries)
> 
> Now her friend comes over and wants to use the phone to call 
> his mother . . .
> 
> As you can see, this rapidly becomes a provisionng nightmare, 
> and I'd argue that the From screening provides no useful 
> value anyhow. Much more useful to leave it as a user provided 
> string with the semantic of "How the user wants to be though 
> of at the far end".
> 
> --
> Dean
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sip@ietf.org for new developments of core SIP
> 


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



From daemon@ns.ietf.org  Tue Apr 16 09:45:27 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03936
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 09:45:27 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA16235
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 09:45:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA14612;
	Tue, 16 Apr 2002 09:30:50 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA14563
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 09:30:45 -0400 (EDT)
Received: from bdsl.66.12.12.130.gte.net (bdsl.66.12.12.130.gte.net [66.12.12.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02732;
	Tue, 16 Apr 2002 09:30:40 -0400 (EDT)
Received: from C1893415A (bdsl.greycouncil.com [127.0.0.1])
	by bdsl.66.12.12.130.gte.net (8.11.6/8.11.6) with SMTP id g3GDUDd23269;
	Tue, 16 Apr 2002 08:30:13 -0500
Message-ID: <00b901c1e54a$d6ba51c0$133fed0c@C1893415A>
From: "Dean Willis" <dean.willis@softarmor.com>
To: <sip@ietf.org>, "Sipping \(E-mail\)" <sipping@ietf.org>
Date: Tue, 16 Apr 2002 08:30:13 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Request: Posting Formats -- Use Plain Text
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

I've noticed a lot of people posting messages in Microsoft Rich Text or
MHTML formats.

This is painful and hard to reply to, and makes it hard to follow the
thread of conversation. And it makes the messages nearly IMPOSSIBLE to
read on smaller-format devices.

Please:

1) Set your email program up to use plain text if at all possible. There
were guidelines for this on IETF Announce last year.

2) Don't just copy in the whole body of a message when you're responding
to a small section of it. Just include the relevant text and an
attribution to the original author -- like "Dean wrote:".

Thanks.

--
Dean

We could probably dig up the USENET etiquette FAQ if anyone would find
that useful.


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



From daemon@ns.ietf.org  Tue Apr 16 09:48:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04050
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 09:48:28 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA16437
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 09:48:31 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA15203;
	Tue, 16 Apr 2002 09:33:45 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA15172
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 09:33:41 -0400 (EDT)
Received: from bdsl.66.12.12.130.gte.net (bdsl.66.12.12.130.gte.net [66.12.12.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03074
	for <sipping@ietf.org>; Tue, 16 Apr 2002 09:33:37 -0400 (EDT)
Received: from C1893415A (bdsl.greycouncil.com [127.0.0.1])
	by bdsl.66.12.12.130.gte.net (8.11.6/8.11.6) with SMTP id g3GDX2d23314;
	Tue, 16 Apr 2002 08:33:02 -0500
Message-ID: <00c501c1e54b$3bb28e30$133fed0c@C1893415A>
From: "Dean Willis" <dean.willis@softarmor.com>
To: "David R. Oran" <oran@cisco.com>,
        "'Sipping \(E-mail\)'" <sipping@ietf.org>
References: <005301c1e549$b2dc4d40$35ee2ca1@OranLT>
Subject: Re: [Sipping] Screened From: and Privacy
Date: Tue, 16 Apr 2002 08:33:02 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit


As I said: Provisioning nightmare.

And when you're using the lobby phone, don't you want to set a display
name? You want to set your own Subject: too, right?

--
Dean



----- Original Message -----
From: "David R. Oran" <oran@cisco.com>
To: "'Dean Willis'" <dean.willis@softarmor.com>; "'Sipping (E-mail)'"
<sipping@ietf.org>
Sent: Tuesday, April 16, 2002 8:22 AM
Subject: RE: [Sipping] Screened From: and Privacy


> Viewing things this way, where the "principal" sending and receiving
SIP
> messages is some amalgam of a "user" and "the phone" is just asking
for
> trouble, IMHO. It gets into all sorts of issues about who is doing
what,
> what the "phone" part is trusted with as opposed to the "user", which
> identity various identifiers are bound to, etc., etc., etc.
>
> I believe a much cleaner and simpler model is where there is just a
> "user". If there are multiple "users" of a single device, then there
> are, logically speaking, multiple UAs in the device, as there would be
> for a multi-line phone.
>
> To handle the binding between user and device where needed you do two
> things:
> A) have the user "login" to the device, using whatever local (or at
> least non-SIP, machinery you like)
> A) have the UA support a "default" user who is logged in automagically
> at boot time to handle the lobby phone, auto-login, etc.
>
> This way there is no confusion about who is doing what and who should
be
> trusted for what. Trust between the device and user is established
> outside SIP. Trust between the user and the rest of the SIP elements
is
> established via SIP security mechanisms. The device is no more or less
> privileged than the user using it.
>
> Dave.
>
> > -----Original Message-----
> > From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]
> > On Behalf Of Dean Willis
> > Sent: Tuesday, April 16, 2002 9:14 AM
> > To: Sipping (E-mail)
> > Subject: [Sipping] Screened From: and Privacy
> >
> >
> >
> > Some have suggested that we have everything needed to handle
> > caller ID using the From: field, and that we can reasonably
> > screen callas based on the "From:" field to assure the
> > veracity of this field value.
> >
> > We COULD.
> >
> > But there's a very common usage suggesting otherwise.
> >
> > Generally, there's some sort of authentication token
> > associated with the phone, not the user of the phone. For
> > example, in 3PPP it's in the SIM card. For the Cisco 7960 on
> > my desk, it's in the boot file on the TFTP server, and for
> > the Pingtel phone on my desk it is stored into the phone
> > using a web interface.
> >
> > So really, the service platform is authenticating the phone,
> > not the user.
> >
> > So let's say my kid (I don't have one, but we're pretending
> > here) is using the home phone to call her friend. She doesn't
> > want the call to be from Dad, she wants it to be "from" her.
> >
> > Logically:
> >
> >     From: littlekid
> >     Authenticated-RPID: Account of Dean Willis 9724735455
> >
> > Ok, so we could add "littlekid" to the list of "Approved From
> > Fields". Or we could revamp things so that she gets a "login"
> > and Her Very Own RPID (which is contractually iffy in many
countries)
> >
> > Now her friend comes over and wants to use the phone to call
> > his mother . . .
> >
> > As you can see, this rapidly becomes a provisionng nightmare,
> > and I'd argue that the From screening provides no useful
> > value anyhow. Much more useful to leave it as a user provided
> > string with the semantic of "How the user wants to be though
> > of at the far end".
> >
> > --
> > Dean
> >
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current
> > sip Use sip@ietf.org for new developments of core SIP
> >
>
>


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



From daemon@ns.ietf.org  Tue Apr 16 10:02:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05040
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 10:02:27 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA17932
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 10:02:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA15816;
	Tue, 16 Apr 2002 09:39:54 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA15788
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 09:39:51 -0400 (EDT)
Received: from lohi.eng.song.fi (lohi.eng.song.fi [195.10.149.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03569
	for <sipping@ietf.org>; Tue, 16 Apr 2002 09:39:46 -0400 (EDT)
From: jh@lohi.eng.song.fi
Received: from harjus.eng.song.fi ([195.10.149.20])
	by lohi.eng.song.fi with esmtp (Exim 3.34 #1 (Debian))
	id 16xTBU-0004hu-00; Tue, 16 Apr 2002 16:39:48 +0300
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15548.10660.370894.332955@harjus.eng.song.fi>
Date: Tue, 16 Apr 2002 16:39:48 +0300
To: "Dean Willis" <dean.willis@softarmor.com>
Cc: "Sipping \(E-mail\)" <sipping@ietf.org>
Subject: [Sipping] Screened From: and Privacy
In-Reply-To: <005d01c1e548$a2c54d90$133fed0c@C1893415A>
References: <CD110021698980419241042CF576B8F2012BAB7B@EXCALIBUR.santera.com>
	<009401c1e4bc$699dd320$1c036e3f@TXDWILLIS2>
	<15547.46611.373594.803557@harjus.eng.song.fi>
	<005d01c1e548$a2c54d90$133fed0c@C1893415A>
X-Mailer: VM 7.01 under Emacs 21.1.1
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Dean Willis writes:

 > So let's say my kid (I don't have one, but we're pretending here) is
 > using the home phone to call her friend. She doesn't want the call to be
 > from Dad, she wants it to be "from" her.

then you simply define a new "line" to your 7960 phone for your kid and
things work as he/she wants.  the username/password can be either the
same as yours or the kid's own.

 > Now her friend comes over and wants to use the phone to call his mother
 > . . .

in this case, the friend most likely would use your kid's "line" rather
than defining his/her own to the phone.  it is the same as using
someone's cell phone.  most likely the friend would not open it and
replace his/her own sim to the phone in order to make the call, because
that would be too complicated.

i again fail to see what this has to do with the privacy discussion.
when you use someone else's phone, you will also use his/her privacy
setup.

-- juha


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



From daemon@ns.ietf.org  Tue Apr 16 10:04:41 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05116
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 10:04:40 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA18196
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 10:04:43 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA16617;
	Tue, 16 Apr 2002 09:50:11 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA16585
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 09:50:08 -0400 (EDT)
Received: from bdsl.66.12.12.130.gte.net (bdsl.66.12.12.130.gte.net [66.12.12.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04139
	for <sipping@ietf.org>; Tue, 16 Apr 2002 09:50:03 -0400 (EDT)
Received: from C1893415A (bdsl.greycouncil.com [127.0.0.1])
	by bdsl.66.12.12.130.gte.net (8.11.6/8.11.6) with SMTP id g3GDn0d23501;
	Tue, 16 Apr 2002 08:49:00 -0500
Message-ID: <00f301c1e54d$76f5fe80$133fed0c@C1893415A>
From: "Dean Willis" <dean.willis@softarmor.com>
To: <jh@lohi.eng.song.fi>
Cc: "Sipping \(E-mail\)" <sipping@ietf.org>
References: <CD110021698980419241042CF576B8F2012BAB7B@EXCALIBUR.santera.com><009401c1e4bc$699dd320$1c036e3f@TXDWILLIS2><15547.46611.373594.803557@harjus.eng.song.fi><005d01c1e548$a2c54d90$133fed0c@C1893415A> <15548.10660.370894.332955@harjus.eng.song.fi>
Subject: Re: [Sipping] Screened From: and Privacy
Date: Tue, 16 Apr 2002 08:49:01 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit


> in this case, the friend most likely would use your kid's "line"
rather
> than defining his/her own to the phone.  it is the same as using
> someone's cell phone.  most likely the friend would not open it and
> replace his/her own sim to the phone in order to make the call,
because
> that would be too complicated.

Exactly. But they're going to defin their own Subject field and other
user (not SUBSCRIBER) data. I'm arguing that the display name field
(From:) falls into this category.

> i again fail to see what this has to do with the privacy discussion.
> when you use someone else's phone, you will also use his/her privacy
> setup.

Because if the display name field (From:) is part of the SUBSCRIBER
data, as you are arguing, then it falls into network-controlled privacy
management regulation and we end up with "MUST B2BUA everything." If it
is a USER field, then regulation affects it much more lightly.

What would be the implication if we added a "New" header for
"UserDisplayName" intended for just what I've proposed above? Simple:
The phone people would inist that that be rewritten by the network,
because this MIGHT conflict with Subscriber privacy requirements. Since
the protocol allows extension with arbitrary new headers, the logical
requirement is for "the network" to be required to block arbitrary new
headers, thereby destroying service transparency.

Life is much better if we consider "From:", along with "Subject:" and
other such fields, as  per-call user-provided data intended for display
to the other end of the dialog. Filtering the From, as you are doing,
forces it into the regulatory realm in a way that you're not going to
like.

--
Dean


--
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 daemon@ns.ietf.org  Tue Apr 16 10:07:50 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05309
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 10:07:45 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA18335
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 10:07:48 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA16983;
	Tue, 16 Apr 2002 09:54:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA16950
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 09:54:00 -0400 (EDT)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04332
	for <sipping@ietf.org>; Tue, 16 Apr 2002 09:53:56 -0400 (EDT)
Received: from mira-sjc5-9.cisco.com (IDENT:mirapoint@mira-sjc5-9.cisco.com [171.71.163.32])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g3GDrBNo001186;
	Tue, 16 Apr 2002 06:53:11 -0700 (PDT)
Received: from OranLT ([161.44.238.53])
	by mira-sjc5-9.cisco.com (Mirapoint)
	with ESMTP id ACQ54614;
	Tue, 16 Apr 2002 06:53:38 -0700 (PDT)
From: "David R. Oran" <oran@cisco.com>
To: "'Dean Willis'" <dean.willis@softarmor.com>,
        "'Sipping \(E-mail\)'" <sipping@ietf.org>
Subject: RE: [Sipping] Screened From: and Privacy
Date: Tue, 16 Apr 2002 09:45:51 -0400
Organization: Cisco Systems
Message-ID: <006101c1e54d$06630640$35ee2ca1@OranLT>
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.3416
In-Reply-To: <00c501c1e54b$3bb28e30$133fed0c@C1893415A>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: Dean Willis [mailto:dean.willis@softarmor.com] 
> Sent: Tuesday, April 16, 2002 9:33 AM
> To: David R. Oran; 'Sipping (E-mail)'
> Subject: Re: [Sipping] Screened From: and Privacy
> 
> 
> 
> As I said: Provisioning nightmare.
> 
Why?

> And when you're using the lobby phone, don't you want to set 
> a display name? You want to set your own Subject: too, right?
>
If you care enough, then log into the phone (or authenticate to it for a
single call). Then it's yours, has your secret(s), can authenticate as
you, etc. etc. etc.

If you don't care enough, just use the phone. Then the From: will be 
	From: Unsecured Public Lobby phone <lobby@dynamicsoft.com>

And the subject will be 
	Subject: WTF, over?

or whatever the phone vendor stuck into his default config, since nobody
will bother to change it (like the contents of the pad in ISIS hellos,
in which I've seen:
	"this space intentionally left blank"
	"this space for rent"
	"if you're looking at this, you probably are using a sniffer"

Dave.
 
> --
> Dean
> 
> 
> 
> ----- Original Message -----
> From: "David R. Oran" <oran@cisco.com>
> To: "'Dean Willis'" <dean.willis@softarmor.com>; "'Sipping 
> (E-mail)'" <sipping@ietf.org>
> Sent: Tuesday, April 16, 2002 8:22 AM
> Subject: RE: [Sipping] Screened From: and Privacy
> 
> 
> > Viewing things this way, where the "principal" sending and receiving
> SIP
> > messages is some amalgam of a "user" and "the phone" is just asking
> for
> > trouble, IMHO. It gets into all sorts of issues about who is doing
> what,
> > what the "phone" part is trusted with as opposed to the 
> "user", which 
> > identity various identifiers are bound to, etc., etc., etc.
> >
> > I believe a much cleaner and simpler model is where there is just a 
> > "user". If there are multiple "users" of a single device, 
> then there 
> > are, logically speaking, multiple UAs in the device, as 
> there would be 
> > for a multi-line phone.
> >
> > To handle the binding between user and device where needed 
> you do two
> > things:
> > A) have the user "login" to the device, using whatever local (or at 
> > least non-SIP, machinery you like)
> > A) have the UA support a "default" user who is logged in 
> automagically 
> > at boot time to handle the lobby phone, auto-login, etc.
> >
> > This way there is no confusion about who is doing what and 
> who should
> be
> > trusted for what. Trust between the device and user is established 
> > outside SIP. Trust between the user and the rest of the SIP elements
> is
> > established via SIP security mechanisms. The device is no 
> more or less 
> > privileged than the user using it.
> >
> > Dave.
> >
> > > -----Original Message-----
> > > From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] On 
> > > Behalf Of Dean Willis
> > > Sent: Tuesday, April 16, 2002 9:14 AM
> > > To: Sipping (E-mail)
> > > Subject: [Sipping] Screened From: and Privacy
> > >
> > >
> > >
> > > Some have suggested that we have everything needed to 
> handle caller 
> > > ID using the From: field, and that we can reasonably 
> screen callas 
> > > based on the "From:" field to assure the veracity of this field 
> > > value.
> > >
> > > We COULD.
> > >
> > > But there's a very common usage suggesting otherwise.
> > >
> > > Generally, there's some sort of authentication token 
> associated with 
> > > the phone, not the user of the phone. For example, in 
> 3PPP it's in 
> > > the SIM card. For the Cisco 7960 on my desk, it's in the 
> boot file 
> > > on the TFTP server, and for the Pingtel phone on my desk it is 
> > > stored into the phone using a web interface.
> > >
> > > So really, the service platform is authenticating the 
> phone, not the 
> > > user.
> > >
> > > So let's say my kid (I don't have one, but we're pretending
> > > here) is using the home phone to call her friend. She 
> doesn't want 
> > > the call to be from Dad, she wants it to be "from" her.
> > >
> > > Logically:
> > >
> > >     From: littlekid
> > >     Authenticated-RPID: Account of Dean Willis 9724735455
> > >
> > > Ok, so we could add "littlekid" to the list of "Approved From 
> > > Fields". Or we could revamp things so that she gets a "login" and 
> > > Her Very Own RPID (which is contractually iffy in many
> countries)
> > >
> > > Now her friend comes over and wants to use the phone to call his 
> > > mother . . .
> > >
> > > As you can see, this rapidly becomes a provisionng nightmare, and 
> > > I'd argue that the From screening provides no useful 
> value anyhow. 
> > > Much more useful to leave it as a user provided string with the 
> > > semantic of "How the user wants to be though of at the far end".
> > >
> > > --
> > > Dean
> > >
> > >
> > > _______________________________________________
> > > Sipping mailing list  
> https://www1.ietf.org/mailman/listinfo/sipping
> > > This list 
> is for NEW development of the application of SIP Use 
> > > sip-implementors@cs.columbia.edu for questions on current sip Use 
> > > sip@ietf.org for new developments of core SIP
> > >
> >
> >
> 
> 


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



From daemon@ns.ietf.org  Tue Apr 16 10:08:53 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05392
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 10:08:48 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA18433
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 10:08:52 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA17154;
	Tue, 16 Apr 2002 09:55:47 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA17037
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 09:55:39 -0400 (EDT)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04384;
	Tue, 16 Apr 2002 09:55:32 -0400 (EDT)
Received: from cannon.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g3GDtHSk016496;
	Tue, 16 Apr 2002 09:55:17 -0400 (EDT)
Received: from cisco.com (dhcp-161-44-241-140.cisco.com [161.44.241.140])
	by cannon.cisco.com (Mirapoint)
	with ESMTP id AAI47380;
	Tue, 16 Apr 2002 09:58:11 -0400 (EDT)
Message-ID: <3CBC2D2C.411D97E5@cisco.com>
Date: Tue, 16 Apr 2002 09:54:52 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD   (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Internet-Drafts@ietf.org
CC: IETF-Announce:@cisco.com, ";"@cisco.com, sipping@ietf.org
Subject: Re: [Sipping] I-D ACTION:draft-camarillo-sipping-reason-00.txt
References: <200204091241.IAA03423@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Gonzalo,

I have another possible reason for Reason:

7. Identifying purpose of dialog refresh

   There are multiple reasons for sending a dialog refresh
   message (e.g. reINVITE). It may be sent simply to update
   a session timer, or it may be sent to test the signalling
   path. In these cases the server need not do anything special.

   But another reason may be that the sender believes there is
   some problem that might be resolved by changing something 
   at the other endpoint. For instance the sender may be
   receiving errors attempting to send media to the receiver.
   A change in media port at the receiving endpoint might fix
   this problem. However there is currently no way to distinguish
   this case from a simple refresh.

(I numbered this 7 because you have two 5s in your draft.)

There is another case I don't see mentioned, but I am not sure
where to put it. This is the case of CANCEL or BYE used to
drop extra call legs of a forked invite. Would like to indicate
the difference between dropping because answered elsewhere and
dropping because changed mind or got tired of waiting.
This could be important to avoid later callbacks. This is similar
to stuff in your Service Creation section, but the name seems
wrong.

	Paul

Internet-Drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
>         Title           : Session Initiation Protocol: Requirements on Reason
>                           Information beyond the Status Code
>         Author(s)       : G. Camarillo
>         Filename        : draft-camarillo-sipping-reason-00.txt
>         Pages           : 5
>         Date            : 08-Apr-02
> 
> Some applications need to know why a particular SIP message was
> issued. This document describes those applications and provides a
> set of requirements that a mechanism used to transport this type of
> information has to fulfill.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-camarillo-sipping-reason-00.txt
> 
> To remove yourself from the IETF Announcement list, send a message to
> ietf-announce-request with the word unsubscribe in the body of the message.
> 
> Internet-Drafts are also available by anonymous FTP. Login with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
>         "get draft-camarillo-sipping-reason-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-camarillo-sipping-reason-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.
> 
>   ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> Content-Type: text/plain
> Content-ID:     <20020408122729.I-D@ietf.org>

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



From daemon@ns.ietf.org  Tue Apr 16 10:12:42 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05535
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 10:12:42 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA18622
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 10:12:42 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA16872;
	Tue, 16 Apr 2002 09:52:11 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA16839
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 09:52:05 -0400 (EDT)
Received: from lohi.eng.song.fi (lohi.eng.song.fi [195.10.149.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04281
	for <sipping@ietf.org>; Tue, 16 Apr 2002 09:52:01 -0400 (EDT)
From: jh@lohi.eng.song.fi
Received: from harjus.eng.song.fi ([195.10.149.20])
	by lohi.eng.song.fi with esmtp (Exim 3.34 #1 (Debian))
	id 16xTNL-0004in-00; Tue, 16 Apr 2002 16:52:03 +0300
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15548.11395.594227.273091@harjus.eng.song.fi>
Date: Tue, 16 Apr 2002 16:52:03 +0300
To: "Dean Willis" <dean.willis@softarmor.com>
Cc: "David R. Oran" <oran@cisco.com>,
        "'Sipping \(E-mail\)'" <sipping@ietf.org>
Subject: Re: [Sipping] Screened From: and Privacy
In-Reply-To: <00c501c1e54b$3bb28e30$133fed0c@C1893415A>
References: <005301c1e549$b2dc4d40$35ee2ca1@OranLT>
	<00c501c1e54b$3bb28e30$133fed0c@C1893415A>
X-Mailer: VM 7.01 under Emacs 21.1.1
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Dean Willis writes:

 > And when you're using the lobby phone, don't you want to set a display
 > name? You want to set your own Subject: too, right?

when i use a lobby phone, i don't want to set anything.  i just use the
phone as it is configured.

how is this relevant to the subject line?

-- juha


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



From daemon@ns.ietf.org  Tue Apr 16 10:44:45 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06737
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 10:44:44 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA20764
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 10:44:49 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA19222;
	Tue, 16 Apr 2002 10:22:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA19191
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 10:22:54 -0400 (EDT)
Received: from lohi.eng.song.fi (lohi.eng.song.fi [195.10.149.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05946
	for <sipping@ietf.org>; Tue, 16 Apr 2002 10:22:49 -0400 (EDT)
From: jh@lohi.eng.song.fi
Received: from harjus.eng.song.fi ([195.10.149.20])
	by lohi.eng.song.fi with esmtp (Exim 3.34 #1 (Debian))
	id 16xTr9-0004k8-00; Tue, 16 Apr 2002 17:22:51 +0300
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15548.13243.542688.817409@harjus.eng.song.fi>
Date: Tue, 16 Apr 2002 17:22:51 +0300
To: "Dean Willis" <dean.willis@softarmor.com>
Cc: "Sipping \(E-mail\)" <sipping@ietf.org>
Subject: Re: [Sipping] Screened From: and Privacy
In-Reply-To: <00f301c1e54d$76f5fe80$133fed0c@C1893415A>
References: <CD110021698980419241042CF576B8F2012BAB7B@EXCALIBUR.santera.com>
	<009401c1e4bc$699dd320$1c036e3f@TXDWILLIS2>
	<15547.46611.373594.803557@harjus.eng.song.fi>
	<005d01c1e548$a2c54d90$133fed0c@C1893415A>
	<15548.10660.370894.332955@harjus.eng.song.fi>
	<00f301c1e54d$76f5fe80$133fed0c@C1893415A>
X-Mailer: VM 7.01 under Emacs 21.1.1
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Dean Willis writes:

 > Exactly. But they're going to defin their own Subject field and other
 > user (not SUBSCRIBER) data. I'm arguing that the display name field
 > (From:) falls into this category.

yes they could if there is an easy way to enter a subject field, which
none of the phones i have seen has.  this is analogous to using someone
else's email account.  you can set the subject line, but not from whom
the message came from, i.e., the from field.

 > Because if the display name field (From:) is part of the SUBSCRIBER
 > data, as you are arguing, then it falls into network-controlled privacy
 > management regulation and we end up with "MUST B2BUA everything." If it
 > is a USER field, then regulation affects it much more lightly.

i'm arguing that the whole from field belongs to the user whose phone
i'm borrowing and there is no problem whatsoever with privacy
regulation.  the privacy what i get is the privacy of the person whose
phone (or "line") i'm using.  if i borrow someone else's cell phone, i
don't get my own privacy, but the privacy of the phone owner. if i want
my own privacy, i need to change the sim.

 > Life is much better if we consider "From:", along with "Subject:" and
 > other such fields, as  per-call user-provided data intended for display
 > to the other end of the dialog. Filtering the From, as you are doing,
 > forces it into the regulatory realm in a way that you're not going to
 > like.

so far we haven't had any other field than the from field to identify
the calling party:

20.20 From The From header field indicates the initiator of the
   request. This may be different from the initiator of the
   dialog. Requests sent by the callee to the caller use the callee s
   address in the From header field. The optional  display-name  is
   meant to be rendered by a human user interface. A system SHOULD use
   4280 the display name  Anonymous  if the identity of the client is to
   remain hidden.

all sip phones on the market include the calling user's address in the
from field.  they do not have any other field for that purpose and thus
i have not had any other way to make sure that the callee address as
seen by the pstn has not been faked.  if i had not used the from field
for that purpose, there could not (for regulatory reasons) have been any
sip to pstn service in finland.

since there is already lots of sip phones on the market owners of which
do want to make pstn calls, i have to keep on screening calls based on
the from field for a very long time to come.  also, many of the proxies
on the marker can today do this from field screening.  changing it so
something else would do nothing else but make things more complicated.

of course operational complexity and backwards compatibility is not a
problem for vendors like dynamicsoft and nortel, who do not need to run
sip services.

-- juha


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



From daemon@ns.ietf.org  Tue Apr 16 10:46:49 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06818
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 10:46:49 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA20811
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 10:46:53 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA19532;
	Tue, 16 Apr 2002 10:28:29 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA19501
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 10:28:26 -0400 (EDT)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06155
	for <sipping@ietf.org>; Tue, 16 Apr 2002 10:28:21 -0400 (EDT)
Received: from cannon.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g3GESFdo019850;
	Tue, 16 Apr 2002 10:28:16 -0400 (EDT)
Received: from cisco.com (dhcp-161-44-241-140.cisco.com [161.44.241.140])
	by cannon.cisco.com (Mirapoint)
	with ESMTP id AAI47703;
	Tue, 16 Apr 2002 10:31:11 -0400 (EDT)
Message-ID: <3CBC34E8.134513F6@cisco.com>
Date: Tue, 16 Apr 2002 10:27:52 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD   (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
CC: jh@lohi.eng.song.fi, "Sipping (E-mail)" <sipping@ietf.org>
Subject: Re: [Sipping] Screened From: and Privacy
References: <CD110021698980419241042CF576B8F2012BAB7B@EXCALIBUR.santera.com><009401c1e4bc$699dd320$1c036e3f@TXDWILLIS2><15547.46611.373594.803557@harjus.eng.song.fi><005d01c1e548$a2c54d90$133fed0c@C1893415A> <15548.10660.370894.332955@harjus.eng.song.fi> <00f301c1e54d$76f5fe80$133fed0c@C1893415A>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Bis-09, section 8.1.1.3 says:

  The From header field indicates the logical identity of the initiator
  of the request, possibly the user's address-of-record. Like the To
  header field, it contains a URI and optionally a display name. It is
  used by SIP elements to determine which processing rules to apply to
  a request (for example, automatic call rejection).

For it to be useful for this purpose, there must be some belief
that it is accurate. Otherwise I am going to start claiming I
am Bill Gates every time I call MicroSoft.

Practically speaking it doesn't make sense to consider the display-name portion of the From address when determining processing rules to apply, so that portion should be
open for arbitrary use.

So, in your example, without separate authentication, your kid could set
 
   From: "littlekid" <sip:dean.willis@softarmor.com>

Then the callee would execute call screening rules assuming call was you, but could still see the name "littlekid" displayed.

	Paul

Dean Willis wrote:
> 
> > in this case, the friend most likely would use your kid's "line"
> rather
> > than defining his/her own to the phone.  it is the same as using
> > someone's cell phone.  most likely the friend would not open it and
> > replace his/her own sim to the phone in order to make the call,
> because
> > that would be too complicated.
> 
> Exactly. But they're going to defin their own Subject field and other
> user (not SUBSCRIBER) data. I'm arguing that the display name field
> (From:) falls into this category.
> 
> > i again fail to see what this has to do with the privacy discussion.
> > when you use someone else's phone, you will also use his/her privacy
> > setup.
> 
> Because if the display name field (From:) is part of the SUBSCRIBER
> data, as you are arguing, then it falls into network-controlled privacy
> management regulation and we end up with "MUST B2BUA everything." If it
> is a USER field, then regulation affects it much more lightly.
> 
> What would be the implication if we added a "New" header for
> "UserDisplayName" intended for just what I've proposed above? Simple:
> The phone people would inist that that be rewritten by the network,
> because this MIGHT conflict with Subscriber privacy requirements. Since
> the protocol allows extension with arbitrary new headers, the logical
> requirement is for "the network" to be required to block arbitrary new
> headers, thereby destroying service transparency.
> 
> Life is much better if we consider "From:", along with "Subject:" and
> other such fields, as  per-call user-provided data intended for display
> to the other end of the dialog. Filtering the From, as you are doing,
> forces it into the regulatory realm in a way that you're not going to
> like.
> 
> --
> Dean
> 
> --
> Dean
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP

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



From daemon@ns.ietf.org  Tue Apr 16 10:54:44 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07121
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 10:54:44 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA21190
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 10:54:48 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA20497;
	Tue, 16 Apr 2002 10:40:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA20465
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 10:40:11 -0400 (EDT)
Received: from lohi.eng.song.fi (lohi.eng.song.fi [195.10.149.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06489
	for <sipping@ietf.org>; Tue, 16 Apr 2002 10:40:06 -0400 (EDT)
From: jh@lohi.eng.song.fi
Received: from harjus.eng.song.fi ([195.10.149.20])
	by lohi.eng.song.fi with esmtp (Exim 3.34 #1 (Debian))
	id 16xU7t-0004ka-00; Tue, 16 Apr 2002 17:40:09 +0300
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15548.14281.136088.416072@harjus.eng.song.fi>
Date: Tue, 16 Apr 2002 17:40:09 +0300
To: Paul Kyzivat <pkyzivat@cisco.com>
Cc: Dean Willis <dean.willis@softarmor.com>,
        "Sipping (E-mail)" <sipping@ietf.org>
Subject: Re: [Sipping] Screened From: and Privacy
In-Reply-To: <3CBC34E8.134513F6@cisco.com>
References: <CD110021698980419241042CF576B8F2012BAB7B@EXCALIBUR.santera.com>
	<009401c1e4bc$699dd320$1c036e3f@TXDWILLIS2>
	<15547.46611.373594.803557@harjus.eng.song.fi>
	<005d01c1e548$a2c54d90$133fed0c@C1893415A>
	<15548.10660.370894.332955@harjus.eng.song.fi>
	<00f301c1e54d$76f5fe80$133fed0c@C1893415A>
	<3CBC34E8.134513F6@cisco.com>
X-Mailer: VM 7.01 under Emacs 21.1.1
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Paul Kyzivat writes:

 > Practically speaking it doesn't make sense to consider the
 > display-name portion of the From address when determining processing
 > rules to apply, so that portion should be open for arbitrary use.

i don't check the display name portion except for the value
"Anonymous".
 > 
 > So, in your example, without separate authentication, your kid could set
 >  
 >    From: "littlekid" <sip:dean.willis@softarmor.com>
 > 
 > Then the callee would execute call screening rules assuming call was you, but could still see the name "littlekid" displayed.

that would be possible to do also in my service, but i agree with david
that is highly unlikely that the friend or lobby phone user would
reconfigure the display name or add a subject line or do anything else, but
would just make the call with the existing settings.

-- juha


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



From daemon@ns.ietf.org  Tue Apr 16 11:11:24 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07599
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 11:11:24 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA22460
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 11:11:28 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA21119;
	Tue, 16 Apr 2002 10:51:59 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA21088
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 10:51:55 -0400 (EDT)
Received: from imo-m10.mx.aol.com (imo-m10.mx.aol.com [64.12.136.165])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07064
	for <sipping@ietf.org>; Tue, 16 Apr 2002 10:51:47 -0400 (EDT)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m10.mx.aol.com (mail_out_v32.5.) id d.16f.c273dec (4207);
	Tue, 16 Apr 2002 10:50:45 -0400 (EDT)
Message-ID: <16f.c273dec.29ed9444@aol.com>
Date: Tue, 16 Apr 2002 10:50:44 EDT
Subject: Re: [Sipping] Screened From: and Privacy
To: dean.willis@softarmor.com, jh@lohi.eng.song.fi
CC: sipping@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_16f.c273dec.29ed9444_boundary"
X-Mailer: AOL 6.0 for Windows US sub 10524
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


--part1_16f.c273dec.29ed9444_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 4/16/02 9:50:43 AM Eastern Daylight Time, 
dean.willis@softarmor.com writes:


> > in this case, the friend most likely would use your kid's "line"
> rather
> > than defining his/her own to the phone.  it is the same as using
> > someone's cell phone.  most likely the friend would not open it and
> > replace his/her own sim to the phone in order to make the call,
> because
> > that would be too complicated.
> 
> Exactly. But they're going to define their own Subject field and other
> user (not SUBSCRIBER) data. I'm arguing that the display name field
> (From:) falls into this category.
> 
> 

No, they are going to simply pick up the phone and dial a number. They are 
not going to log on to a device and create a new profile and whatever else 
just to call home and say "am at Susie's house".

Reminds me of a quote I heard one time. Many years ago when IBM came out with 
the first PC, one of their top execs said "Our goal is to make the computer 
as easy to use as the telephone". Unfortunately, the opposite has happened!

Mike


--part1_16f.c273dec.29ed9444_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 4/16/02 9:50:43 AM Eastern Daylight Time, dean.willis@softarmor.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">&gt; in this case, the friend most likely would use your kid's "line"
<BR>rather
<BR>&gt; than defining his/her own to the phone. &nbsp;it is the same as using
<BR>&gt; someone's cell phone. &nbsp;most likely the friend would not open it and
<BR>&gt; replace his/her own sim to the phone in order to make the call,
<BR>because
<BR>&gt; that would be too complicated.
<BR>
<BR>Exactly. But they're going to define their own Subject field and other
<BR>user (not SUBSCRIBER) data. I'm arguing that the display name field
<BR>(From:) falls into this category.
<BR>
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>No, they are going to simply pick up the phone and dial a number. They are not going to log on to a device and create a new profile and whatever else just to call home and say "am at Susie's house".
<BR>
<BR>Reminds me of a quote I heard one time. Many years ago when IBM came out with the first PC, one of their top execs said "Our goal is to make the computer as easy to use as the telephone". Unfortunately, the opposite has happened!
<BR>
<BR>Mike
<BR></FONT></HTML>

--part1_16f.c273dec.29ed9444_boundary--

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



From daemon@ns.ietf.org  Tue Apr 16 13:36:18 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23957
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 13:36:17 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA01828
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 13:36:19 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA00652;
	Tue, 16 Apr 2002 13:22:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA00623
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 13:22:02 -0400 (EDT)
Received: from bdsl.66.12.12.130.gte.net (bdsl.66.12.12.130.gte.net [66.12.12.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22224
	for <sipping@ietf.org>; Tue, 16 Apr 2002 13:21:56 -0400 (EDT)
Received: from TXDWILLIS2 (bdsl.greycouncil.com [127.0.0.1])
	by bdsl.66.12.12.130.gte.net (8.11.6/8.11.6) with ESMTP id g3GHLKd25011;
	Tue, 16 Apr 2002 12:21:21 -0500
From: "Dean Willis" <dean.willis@softarmor.com>
To: "'David R. Oran'" <oran@cisco.com>,
        "'Sipping \(E-mail\)'" <sipping@ietf.org>
Subject: RE: [Sipping] Screened From: and Privacy
Date: Tue, 16 Apr 2002 12:21:10 -0500
Message-ID: <002e01c1e56b$1a639600$bb036e3f@TXDWILLIS2>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <006101c1e54d$06630640$35ee2ca1@OranLT>
Importance: Normal
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id NAA00624
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 8bit


Dave asked:
>Dean sad:
> > As I said: Provisioning nightmare.
> > 
> Why?

We'd have to actually have a provisoined account and establish key
management techniques for each " user" (example, member of the
household) associated with each "subscriber" (example: houselhold).
Operationally speaking, it ain't happenning (there's an RFC for that
term somewhere).

> > And when you're using the lobby phone, don't you want to set
> > a display name? You want to set your own Subject: too, right?
> >
> If you care enough, then log into the phone (or authenticate 
> to it for a single call). Then it's yours, has your 
> secret(s), can authenticate as you, etc. etc. etc.
> 
> If you don't care enough, just use the phone. Then the From: will be 
> 	From: Unsecured Public Lobby phone <lobby@dynamicsoft.com>
> 
> And the subject will be 
> 	Subject: WTF, over?

Well, when I sit down at the lobby PC, or the i-café PC, or whatever, I
manually enter From: and Subject lines on my email. Given a SIP phone
that isn't crippled by a ten-key pad (get over this "it has todays
interface and must therefore be crippled" willya?) why shouldn't I use
the same capability in SIP?

--
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 daemon@ns.ietf.org  Tue Apr 16 13:39:56 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24455
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 13:39:55 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA01999
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 13:39:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA00720;
	Tue, 16 Apr 2002 13:22:25 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA00689
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 13:22:22 -0400 (EDT)
Received: from bdsl.66.12.12.130.gte.net (bdsl.66.12.12.130.gte.net [66.12.12.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22253
	for <sipping@ietf.org>; Tue, 16 Apr 2002 13:22:20 -0400 (EDT)
Received: from TXDWILLIS2 (bdsl.greycouncil.com [127.0.0.1])
	by bdsl.66.12.12.130.gte.net (8.11.6/8.11.6) with ESMTP id g3GHLKd25006;
	Tue, 16 Apr 2002 12:21:20 -0500
From: "Dean Willis" <dean.willis@softarmor.com>
To: <jh@lohi.eng.song.fi>
Cc: "'Sipping \(E-mail\)'" <sipping@ietf.org>
Subject: RE: [Sipping] Screened From: and Privacy
Date: Tue, 16 Apr 2002 12:21:10 -0500
Message-ID: <002d01c1e56b$1a18aa50$bb036e3f@TXDWILLIS2>
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.3416
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <15548.13243.542688.817409@harjus.eng.song.fi>
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit


Juha writes:
> Dean Willis writes:
> 
>  > Exactly. But they're going to defin their own Subject 
> field and other  > user (not SUBSCRIBER) data. I'm arguing 
> that the display name field  > (From:) falls into this category.
> 
> yes they could if there is an easy way to enter a subject 
> field, which none of the phones i have seen has.  this is 
> analogous to using someone else's email account.  you can set 
> the subject line, but not from whom the message came from, 
> i.e., the from field.

Look, I realize today's SIP phone's user interfaces are not ideal. I
have however supreme confidence that they'll get better. I just bought a
nifty PDA with a full keyboard under a slide-down cover -- this would
make a nice portable SIP phone.

Remainder of message snipped due to inclusion of name-calling . . . 

--
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 daemon@ns.ietf.org  Tue Apr 16 14:08:07 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27648
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 14:08:06 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA04314
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 14:08:08 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA02682;
	Tue, 16 Apr 2002 13:52:00 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA02641
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 13:51:54 -0400 (EDT)
Received: from zctfs063.nortelnetworks.com (zctfs063.nortelnetworks.com [47.164.128.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25952
	for <sipping@ietf.org>; Tue, 16 Apr 2002 13:51:51 -0400 (EDT)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zctfs063.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3GHpLD08808;
	Tue, 16 Apr 2002 19:51:21 +0200 (MEST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3GHohH24188;
	Tue, 16 Apr 2002 18:50:43 +0100 (BST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <HLDBS9YX>; Tue, 16 Apr 2002 18:51:19 +0100
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7152@zwcwd00r.europe.nortel.com>
From: "Mark Watson"<mwatson@nortelnetworks.com>
To: "'Dean Willis'" <dean.willis@softarmor.com>,
        "Sipping (E-mail)"
	 <sipping@ietf.org>
Subject: RE: [Sipping] Screened From: and Privacy
Date: Tue, 16 Apr 2002 18:51:14 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E56F.4D9BB94A"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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

Assuming that you only need one 'identity' is always a bad thing in any
application. In these examples there are at least two:
1) An identity the user wishes to be known by
2) An identity the service recognises for the user

Dean is arguing that (1) is what From: is for, and (2) is confined to the
authentication process.

It seems people have assumed that in a Service Provider environment From: is
sometimes used for (2). Certainly the SIP spec points you in this direction
('possibly the address-of-record' ...). Particularly the fact that
*services*, with no qualification, might key off this field imply that it
should be accurate.

There is a requirement from Service Providers to deliver something based on
(2) to the terminator (absent privacy), especially if the terminator is in
the PSTN.

These last two points have led Service Providers to verify the From: field.
They've been encouraged in this by the lack of any other field to
communicate (2) passed the device which does authentication.

As Dean correctly points out, using From: for information like (2) leads to
the need to B2BUA everything for subscriber privacy (if you care about
RFC2543 clients).

I would still argue that a subscriber privacy service may need to remove (1)
as well, so if the idea is to avoid the requirement to modify/control the
From: field, it still might not work.

I can't see a clean way out of this. I don't think it's realistic to assume
that From: is ALWAYS and ONLY of type (1) - purely end-to-end. Sure, some
systems may treat it this way, and there is no harm in that, but it seems to
me too late to make this statement now. Service Providers exist which put it
into class (2). They may need to modify it. As long as we are aware of this
there should be no problem.

I also think it will be common to check the URI portion of the From: field
but not the Display Name.

We can't *assume* From: is ALWAYS of type (2) either. So let's just get on
and define a field for this - Network Asserted Identity.

...Mark



> -----Original Message-----
> From: Dean Willis [mailto:dean.willis@softarmor.com]
> Sent: 16 April 2002 14:14
> To: Sipping (E-mail)
> Subject: [Sipping] Screened From: and Privacy
> 
> 
> 
> Some have suggested that we have everything needed to handle caller ID
> using the From: field, and that we can reasonably screen 
> callas based on
> the "From:" field to assure the veracity of this field value.
> 
> We COULD.
> 
> But there's a very common usage suggesting otherwise.
> 
> Generally, there's some sort of authentication token 
> associated with the
> phone, not the user of the phone. For example, in 3PPP it's in the SIM
> card. For the Cisco 7960 on my desk, it's in the boot file on the TFTP
> server, and for the Pingtel phone on my desk it is stored 
> into the phone
> using a web interface.
> 
> So really, the service platform is authenticating the phone, not the
> user.
> 
> So let's say my kid (I don't have one, but we're pretending here) is
> using the home phone to call her friend. She doesn't want the 
> call to be
> from Dad, she wants it to be "from" her.
> 
> Logically:
> 
>     From: littlekid
>     Authenticated-RPID: Account of Dean Willis 9724735455
> 
> Ok, so we could add "littlekid" to the list of "Approved From Fields".
> Or we could revamp things so that she gets a "login" and Her Very Own
> RPID (which is contractually iffy in many countries)
> 
> Now her friend comes over and wants to use the phone to call 
> his mother
> . . .
> 
> As you can see, this rapidly becomes a provisionng nightmare, and I'd
> argue that the From screening provides no useful value 
> anyhow. Much more
> useful to leave it as a user provided string with the semantic of "How
> the user wants to be though of at the far end".
> 
> --
> 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
> 

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Sipping] Screened From: and Privacy</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Assuming that you only need one 'identity' is always =
a bad thing in any application. In these examples there are at least =
two:</FONT></P>

<P><FONT SIZE=3D2>1) An identity the user wishes to be known by</FONT>
<BR><FONT SIZE=3D2>2) An identity the service recognises for the =
user</FONT>
</P>

<P><FONT SIZE=3D2>Dean is arguing that (1) is what From: is for, and =
(2) is confined to the authentication process.</FONT>
</P>

<P><FONT SIZE=3D2>It seems people have assumed that in a Service =
Provider environment From: is sometimes used for (2). Certainly the SIP =
spec points you in this direction ('possibly the address-of-record' =
...). Particularly the fact that *services*, with no qualification, =
might key off this field imply that it should be accurate.</FONT></P>

<P><FONT SIZE=3D2>There is a requirement from Service Providers to =
deliver something based on (2) to the terminator (absent privacy), =
especially if the terminator is in the PSTN.</FONT></P>

<P><FONT SIZE=3D2>These last two points have led Service Providers to =
verify the From: field. They've been encouraged in this by the lack of =
any other field to communicate (2) passed the device which does =
authentication.</FONT></P>

<P><FONT SIZE=3D2>As Dean correctly points out, using From: for =
information like (2) leads to the need to B2BUA everything for =
subscriber privacy (if you care about RFC2543 clients).</FONT></P>

<P><FONT SIZE=3D2>I would still argue that a subscriber privacy service =
may need to remove (1) as well, so if the idea is to avoid the =
requirement to modify/control the From: field, it still might not =
work.</FONT></P>

<P><FONT SIZE=3D2>I can't see a clean way out of this. I don't think =
it's realistic to assume that From: is ALWAYS and ONLY of type (1) - =
purely end-to-end. Sure, some systems may treat it this way, and there =
is no harm in that, but it seems to me too late to make this statement =
now. Service Providers exist which put it into class (2). They may need =
to modify it. As long as we are aware of this there should be no =
problem.</FONT></P>

<P><FONT SIZE=3D2>I also think it will be common to check the URI =
portion of the From: field but not the Display Name.</FONT>
</P>

<P><FONT SIZE=3D2>We can't *assume* From: is ALWAYS of type (2) either. =
So let's just get on and define a field for this - Network Asserted =
Identity.</FONT></P>

<P><FONT SIZE=3D2>...Mark</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Dean Willis [<A =
HREF=3D"mailto:dean.willis@softarmor.com">mailto:dean.willis@softarmor.c=
om</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: 16 April 2002 14:14</FONT>
<BR><FONT SIZE=3D2>&gt; To: Sipping (E-mail)</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: [Sipping] Screened From: and =
Privacy</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Some have suggested that we have everything =
needed to handle caller ID</FONT>
<BR><FONT SIZE=3D2>&gt; using the From: field, and that we can =
reasonably screen </FONT>
<BR><FONT SIZE=3D2>&gt; callas based on</FONT>
<BR><FONT SIZE=3D2>&gt; the &quot;From:&quot; field to assure the =
veracity of this field value.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; We COULD.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; But there's a very common usage suggesting =
otherwise.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Generally, there's some sort of authentication =
token </FONT>
<BR><FONT SIZE=3D2>&gt; associated with the</FONT>
<BR><FONT SIZE=3D2>&gt; phone, not the user of the phone. For example, =
in 3PPP it's in the SIM</FONT>
<BR><FONT SIZE=3D2>&gt; card. For the Cisco 7960 on my desk, it's in =
the boot file on the TFTP</FONT>
<BR><FONT SIZE=3D2>&gt; server, and for the Pingtel phone on my desk it =
is stored </FONT>
<BR><FONT SIZE=3D2>&gt; into the phone</FONT>
<BR><FONT SIZE=3D2>&gt; using a web interface.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; So really, the service platform is =
authenticating the phone, not the</FONT>
<BR><FONT SIZE=3D2>&gt; user.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; So let's say my kid (I don't have one, but =
we're pretending here) is</FONT>
<BR><FONT SIZE=3D2>&gt; using the home phone to call her friend. She =
doesn't want the </FONT>
<BR><FONT SIZE=3D2>&gt; call to be</FONT>
<BR><FONT SIZE=3D2>&gt; from Dad, she wants it to be &quot;from&quot; =
her.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Logically:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; From: littlekid</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Authenticated-RPID: =
Account of Dean Willis 9724735455</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Ok, so we could add &quot;littlekid&quot; to =
the list of &quot;Approved From Fields&quot;.</FONT>
<BR><FONT SIZE=3D2>&gt; Or we could revamp things so that she gets a =
&quot;login&quot; and Her Very Own</FONT>
<BR><FONT SIZE=3D2>&gt; RPID (which is contractually iffy in many =
countries)</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Now her friend comes over and wants to use the =
phone to call </FONT>
<BR><FONT SIZE=3D2>&gt; his mother</FONT>
<BR><FONT SIZE=3D2>&gt; . . .</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; As you can see, this rapidly becomes a =
provisionng nightmare, and I'd</FONT>
<BR><FONT SIZE=3D2>&gt; argue that the From screening provides no =
useful value </FONT>
<BR><FONT SIZE=3D2>&gt; anyhow. Much more</FONT>
<BR><FONT SIZE=3D2>&gt; useful to leave it as a user provided string =
with the semantic of &quot;How</FONT>
<BR><FONT SIZE=3D2>&gt; the user wants to be though of at the far =
end&quot;.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; --</FONT>
<BR><FONT SIZE=3D2>&gt; Dean</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 sip</FONT>
<BR><FONT SIZE=3D2>&gt; Use sip@ietf.org for new developments of core =
SIP</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E56F.4D9BB94A--

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



From daemon@ns.ietf.org  Tue Apr 16 14:52:08 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02814
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 14:52:07 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA06785
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 14:52:08 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA05893;
	Tue, 16 Apr 2002 14:35:18 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA05857
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 14:35:14 -0400 (EDT)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00573
	for <sipping@ietf.org>; Tue, 16 Apr 2002 14:35:06 -0400 (EDT)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id OAA09573;
	Tue, 16 Apr 2002 14:35:05 -0400 (EDT)
Received: from cs.columbia.edu (slip-32-102-22-19.md.us.prserv.net [32.102.22.19])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g3GIYxPm029356
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Tue, 16 Apr 2002 14:35:02 -0400 (EDT)
Message-ID: <3CBC6EA5.7BBB30F2@cs.columbia.edu>
Date: Tue, 16 Apr 2002 14:34:13 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: jh@lohi.eng.song.fi
CC: Dean Willis <dean.willis@softarmor.com>,
        "Sipping (E-mail)" <sipping@ietf.org>
Subject: Re: [Sipping] Screened From: and Privacy
References: <CD110021698980419241042CF576B8F2012BAB7B@EXCALIBUR.santera.com>
		<009401c1e4bc$699dd320$1c036e3f@TXDWILLIS2>
		<15547.46611.373594.803557@harjus.eng.song.fi>
		<005d01c1e548$a2c54d90$133fed0c@C1893415A>
		<15548.10660.370894.332955@harjus.eng.song.fi>
		<00f301c1e54d$76f5fe80$133fed0c@C1893415A> <15548.13243.542688.817409@harjus.eng.song.fi>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

> yes they could if there is an easy way to enter a subject field, which
> none of the phones i have seen has.  this is analogous to using someone
> else's email account.  you can set the subject line, but not from whom
> the message came from, i.e., the from field.

Editing the From field is just one more click away on many systems
(Netscape mail). The bad part about the user interfaces is that it is
hard to "escape" temporarily and then reset the old value. More
pernicious are certain email providers (such as a large NY/NJ DSL
provider) that enforce that the From field has to have a certain value,
in a pointless attempt at spam prevention.

> 
>  > Because if the display name field (From:) is part of the SUBSCRIBER
>  > data, as you are arguing, then it falls into network-controlled privacy
>  > management regulation and we end up with "MUST B2BUA everything." If it
>  > is a USER field, then regulation affects it much more lightly.
> 
> i'm arguing that the whole from field belongs to the user whose phone
> i'm borrowing and there is no problem whatsoever with privacy
> regulation.  the privacy what i get is the privacy of the person whose
> phone (or "line") i'm using.  if i borrow someone else's cell phone, i
> don't get my own privacy, but the privacy of the phone owner. if i want
> my own privacy, i need to change the sim.

In many cases, just knowing the local policy would be helpful.

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



From daemon@ns.ietf.org  Tue Apr 16 16:10:56 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13011
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 16:10:55 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA11719
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 16:10:58 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA10437;
	Tue, 16 Apr 2002 15:50:36 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA22031
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 11:05:53 -0400 (EDT)
Received: from porfidio.atstake.com (porfidio.atstake.com [63.168.6.70])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA07435
	for <sipping@ietf.org>; Tue, 16 Apr 2002 11:05:48 -0400 (EDT)
Message-ID: <3CBC3D18.8020102@atstake.com>
Date: Tue, 16 Apr 2002 16:02:48 +0100
From: Ofir Arkin <ofir@atstake.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4.1) Gecko/20020314 Netscape6/6.2.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
Cc: Dean Willis <dean.willis@softarmor.com>, jh@lohi.eng.song.fi,
        "Sipping (E-mail)" <sipping@ietf.org>
Subject: Re: [Sipping] Screened From: and Privacy
References: <CD110021698980419241042CF576B8F2012BAB7B@EXCALIBUR.santera.com><009401c1e4bc$699dd320$1c036e3f@TXDWILLIS2><15547.46611.373594.803557@harjus.eng.song.fi><005d01c1e548$a2c54d90$133fed0c@C1893415A> <15548.10660.370894.332955@harjus.eng.song.fi> <00f301c1e54d$76f5fe80$133fed0c@C1893415A> <3CBC34E8.134513F6@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Or it would relate to

<sip:dean.willis@softarmor.com>

the way we apply incoming mail rules and will discard "littlekid"?


Ofir



Paul Kyzivat wrote:

>Bis-09, section 8.1.1.3 says:
>
>  The From header field indicates the logical identity of the initiator
>  of the request, possibly the user's address-of-record. Like the To
>  header field, it contains a URI and optionally a display name. It is
>  used by SIP elements to determine which processing rules to apply to
>  a request (for example, automatic call rejection).
>
>For it to be useful for this purpose, there must be some belief
>that it is accurate. Otherwise I am going to start claiming I
>am Bill Gates every time I call MicroSoft.
>
>Practically speaking it doesn't make sense to consider the display-name portion of the From address when determining processing rules to apply, so that portion should be
>open for arbitrary use.
>
>So, in your example, without separate authentication, your kid could set
> 
>   From: "littlekid" <sip:dean.willis@softarmor.com>
>
>Then the callee would execute call screening rules assuming call was you, but could still see the name "littlekid" displayed.
>
>	Paul
>
>Dean Willis wrote:
>
>>>in this case, the friend most likely would use your kid's "line"
>>>
>>rather
>>
>>>than defining his/her own to the phone.  it is the same as using
>>>someone's cell phone.  most likely the friend would not open it and
>>>replace his/her own sim to the phone in order to make the call,
>>>
>>because
>>
>>>that would be too complicated.
>>>
>>Exactly. But they're going to defin their own Subject field and other
>>user (not SUBSCRIBER) data. I'm arguing that the display name field
>>(From:) falls into this category.
>>
>>>i again fail to see what this has to do with the privacy discussion.
>>>when you use someone else's phone, you will also use his/her privacy
>>>setup.
>>>
>>Because if the display name field (From:) is part of the SUBSCRIBER
>>data, as you are arguing, then it falls into network-controlled privacy
>>management regulation and we end up with "MUST B2BUA everything." If it
>>is a USER field, then regulation affects it much more lightly.
>>
>>What would be the implication if we added a "New" header for
>>"UserDisplayName" intended for just what I've proposed above? Simple:
>>The phone people would inist that that be rewritten by the network,
>>because this MIGHT conflict with Subscriber privacy requirements. Since
>>the protocol allows extension with arbitrary new headers, the logical
>>requirement is for "the network" to be required to block arbitrary new
>>headers, thereby destroying service transparency.
>>
>>Life is much better if we consider "From:", along with "Subject:" and
>>other such fields, as  per-call user-provided data intended for display
>>to the other end of the dialog. Filtering the From, as you are doing,
>>forces it into the regulatory realm in a way that you're not going to
>>like.
>>
>>--
>>Dean
>>
>>--
>>Dean
>>
>>_______________________________________________
>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>This list is for NEW development of the application of SIP
>>Use sip-implementors@cs.columbia.edu for questions on current sip
>>Use sip@ietf.org for new developments of core SIP
>>
>
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the application of SIP
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sip@ietf.org for new developments of core SIP
>

-- 
Ofir Arkin
Managing Security Architect
@stake, Limited.
http://www.atstake.com
email: ofir@stake.com
Tel: +44 (0) 207 495 7002
Fax: +44 (0) 207 495 7062
Mobile: +44 (0) 779 630 8632

-----------------------------
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material.  Any review, re transmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited.  If you received this in error, please contact the sender and delete the material from any computer.






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



From daemon@ns.ietf.org  Tue Apr 16 16:10:57 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13027
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 16:10:57 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA11733
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 16:11:00 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA10455;
	Tue, 16 Apr 2002 15:50:38 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA17792
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 10:01:34 -0400 (EDT)
Received: from porfidio.atstake.com (porfidio.atstake.com [63.168.6.70])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA04958
	for <sipping@ietf.org>; Tue, 16 Apr 2002 10:01:30 -0400 (EDT)
Message-ID: <3CBC2E8F.3060601@atstake.com>
Date: Tue, 16 Apr 2002 15:00:47 +0100
From: Ofir Arkin <ofir@atstake.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4.1) Gecko/20020314 Netscape6/6.2.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Cc: "David R. Oran" <oran@cisco.com>, "'Sipping (E-mail)'" <sipping@ietf.org>
Subject: Re: [Sipping] Screened From: and Privacy
References: <005301c1e549$b2dc4d40$35ee2ca1@OranLT> <00c501c1e54b$3bb28e30$133fed0c@C1893415A>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

So you are going to require people to authenticate... or login to the 
device as you put it

Enjoy...
I guess they will appreciate the user experience

Ofir

Dean Willis wrote:

>As I said: Provisioning nightmare.
>
>And when you're using the lobby phone, don't you want to set a display
>name? You want to set your own Subject: too, right?
>
>--
>Dean
>
>
>
>----- Original Message -----
>From: "David R. Oran" <oran@cisco.com>
>To: "'Dean Willis'" <dean.willis@softarmor.com>; "'Sipping (E-mail)'"
><sipping@ietf.org>
>Sent: Tuesday, April 16, 2002 8:22 AM
>Subject: RE: [Sipping] Screened From: and Privacy
>
>
>>Viewing things this way, where the "principal" sending and receiving
>>
>SIP
>
>>messages is some amalgam of a "user" and "the phone" is just asking
>>
>for
>
>>trouble, IMHO. It gets into all sorts of issues about who is doing
>>
>what,
>
>>what the "phone" part is trusted with as opposed to the "user", which
>>identity various identifiers are bound to, etc., etc., etc.
>>
>>I believe a much cleaner and simpler model is where there is just a
>>"user". If there are multiple "users" of a single device, then there
>>are, logically speaking, multiple UAs in the device, as there would be
>>for a multi-line phone.
>>
>>To handle the binding between user and device where needed you do two
>>things:
>>A) have the user "login" to the device, using whatever local (or at
>>least non-SIP, machinery you like)
>>A) have the UA support a "default" user who is logged in automagically
>>at boot time to handle the lobby phone, auto-login, etc.
>>
>>This way there is no confusion about who is doing what and who should
>>
>be
>
>>trusted for what. Trust between the device and user is established
>>outside SIP. Trust between the user and the rest of the SIP elements
>>
>is
>
>>established via SIP security mechanisms. The device is no more or less
>>privileged than the user using it.
>>
>>Dave.
>>
>>>-----Original Message-----
>>>From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]
>>>On Behalf Of Dean Willis
>>>Sent: Tuesday, April 16, 2002 9:14 AM
>>>To: Sipping (E-mail)
>>>Subject: [Sipping] Screened From: and Privacy
>>>
>>>
>>>
>>>Some have suggested that we have everything needed to handle
>>>caller ID using the From: field, and that we can reasonably
>>>screen callas based on the "From:" field to assure the
>>>veracity of this field value.
>>>
>>>We COULD.
>>>
>>>But there's a very common usage suggesting otherwise.
>>>
>>>Generally, there's some sort of authentication token
>>>associated with the phone, not the user of the phone. For
>>>example, in 3PPP it's in the SIM card. For the Cisco 7960 on
>>>my desk, it's in the boot file on the TFTP server, and for
>>>the Pingtel phone on my desk it is stored into the phone
>>>using a web interface.
>>>
>>>So really, the service platform is authenticating the phone,
>>>not the user.
>>>
>>>So let's say my kid (I don't have one, but we're pretending
>>>here) is using the home phone to call her friend. She doesn't
>>>want the call to be from Dad, she wants it to be "from" her.
>>>
>>>Logically:
>>>
>>>    From: littlekid
>>>    Authenticated-RPID: Account of Dean Willis 9724735455
>>>
>>>Ok, so we could add "littlekid" to the list of "Approved From
>>>Fields". Or we could revamp things so that she gets a "login"
>>>and Her Very Own RPID (which is contractually iffy in many
>>>
>countries)
>
>>>Now her friend comes over and wants to use the phone to call
>>>his mother . . .
>>>
>>>As you can see, this rapidly becomes a provisionng nightmare,
>>>and I'd argue that the From screening provides no useful
>>>value anyhow. Much more useful to leave it as a user provided
>>>string with the semantic of "How the user wants to be though
>>>of at the far end".
>>>
>>>--
>>>Dean
>>>
>>>
>>>_______________________________________________
>>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>>This list is for NEW development of the application of SIP
>>>Use sip-implementors@cs.columbia.edu for questions on current
>>>sip Use sip@ietf.org for new developments of core SIP
>>>
>>
>
>
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the application of SIP
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sip@ietf.org for new developments of core SIP
>






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



From daemon@ns.ietf.org  Tue Apr 16 16:18:44 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13982
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 16:18:43 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA11983
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 16:18:46 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA11442;
	Tue, 16 Apr 2002 16:03:00 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA11411
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 16:02:55 -0400 (EDT)
Received: from mage.qualcomm.com (mage.qualcomm.com [129.46.65.64])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11932
	for <sipping@ietf.org>; Tue, 16 Apr 2002 16:02:51 -0400 (EDT)
Received: from [199.106.106.137] (vpn-5k-client-10141231.qualcomm.com [10.14.12.31])
	by mage.qualcomm.com (8.12.1/8.12.1/1.0) with ESMTP id g3GK2dkg019183;
	Tue, 16 Apr 2002 13:02:40 -0700 (PDT)
Mime-Version: 1.0
X-Sender: jwn2@mage.qualcomm.com
Message-Id: <a05101509b8e232566189@[199.106.106.137]>
In-Reply-To: <15548.10660.370894.332955@harjus.eng.song.fi>
References: 
 <CD110021698980419241042CF576B8F2012BAB7B@EXCALIBUR.santera.com>
 <009401c1e4bc$699dd320$1c036e3f@TXDWILLIS2>
 <15547.46611.373594.803557@harjus.eng.song.fi>
 <005d01c1e548$a2c54d90$133fed0c@C1893415A>
 <15548.10660.370894.332955@harjus.eng.song.fi>
X-Mailer: eudora51carbon-0415021019
X-PGP-RSA-Fingerprint: EA53 01A6 C076 F9C2  09E8 9480 645A 8857
X-PGP-DH-Fingerprint: 4F5E 56C9 BD4D 0227 331F 6AEE 9590 24F9 6FD7 04F8
Date: Tue, 16 Apr 2002 12:58:15 -0700
To: jh@lohi.eng.song.fi
From: John  W Noerenberg II <jwn2@qualcomm.com>
Subject: Re: [Sipping] Screened From: and Privacy
Cc: "Dean Willis" <dean.willis@softarmor.com>,
        "Sipping \(E-mail\)" <sipping@ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

At 4:39 PM +0300 4/16/02, jh@lohi.eng.song.fi wrote:
>
>i again fail to see what this has to do with the privacy discussion.
>when you use someone else's phone, you will also use his/her privacy
>setup.

That simplifies things.  It also denies the possibility that one user 
would have different privacy/authentication requirement than another. 
Consequently, it oversimplifies things.

best,

jwn2

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



From daemon@ns.ietf.org  Tue Apr 16 17:09:08 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19810
	for <sipping-archive@odin.ietf.org>; Tue, 16 Apr 2002 17:09:08 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA14878
	for sipping-archive@odin.ietf.org; Tue, 16 Apr 2002 17:09:11 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA13003;
	Tue, 16 Apr 2002 16:34:50 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA12972
	for <sipping@ns.ietf.org>; Tue, 16 Apr 2002 16:34:47 -0400 (EDT)
Received: from lohi.eng.song.fi (lohi.eng.song.fi [195.10.149.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15588
	for <sipping@ietf.org>; Tue, 16 Apr 2002 16:34:43 -0400 (EDT)
From: jh@lohi.eng.song.fi
Received: from harjus.eng.song.fi ([195.10.149.20])
	by lohi.eng.song.fi with esmtp (Exim 3.34 #1 (Debian))
	id 16xZf2-0004tU-00; Tue, 16 Apr 2002 23:34:44 +0300
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15548.35556.298075.40268@harjus.eng.song.fi>
Date: Tue, 16 Apr 2002 23:34:44 +0300
To: John  W Noerenberg II <jwn2@qualcomm.com>
Cc: "Dean Willis" <dean.willis@softarmor.com>,
        "Sipping \(E-mail\)" <sipping@ietf.org>
Subject: Re: [Sipping] Screened From: and Privacy
In-Reply-To: <a05101509b8e232566189@[199.106.106.137]>
References: <CD110021698980419241042CF576B8F2012BAB7B@EXCALIBUR.santera.com>
	<009401c1e4bc$699dd320$1c036e3f@TXDWILLIS2>
	<15547.46611.373594.803557@harjus.eng.song.fi>
	<005d01c1e548$a2c54d90$133fed0c@C1893415A>
	<15548.10660.370894.332955@harjus.eng.song.fi>
	<a05101509b8e232566189@[199.106.106.137]>
X-Mailer: VM 7.01 under Emacs 21.1.1
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

John  W Noerenberg II writes:

 > That simplifies things.  It also denies the possibility that one user 
 > would have different privacy/authentication requirement than another. 
 > Consequently, it oversimplifies things.

no it doesn't.  you can always depending on the situation buy your own
phone or sim or login as yourself to the other person's phone.  the
trade off is between simplicity (use the other person's setting) and
configuration complexity.

-- juha


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



From daemon@optimus.ietf.org  Wed Apr 17 02:05:58 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10518
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 02:05:58 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA17748
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 02:06:00 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA16627;
	Wed, 17 Apr 2002 01:44:01 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA16520
	for <sipping@optimus.ietf.org>; Wed, 17 Apr 2002 01:43:54 -0400 (EDT)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02555
	for <sipping@ietf.org>; Wed, 17 Apr 2002 01:43:51 -0400 (EDT)
Received: from mira-sjc5-9.cisco.com (IDENT:mirapoint@mira-sjc5-9.cisco.com [171.71.163.32])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g3H5h6No008187;
	Tue, 16 Apr 2002 22:43:06 -0700 (PDT)
Received: from OranLT (sjc-vpn3-425.cisco.com [10.21.65.169])
	by mira-sjc5-9.cisco.com (Mirapoint)
	with ESMTP id ACQ78152;
	Tue, 16 Apr 2002 22:43:30 -0700 (PDT)
From: "David R. Oran" <oran@cisco.com>
To: "'Mark Watson'" <mwatson@nortelnetworks.com>,
        "'Dean Willis'" <dean.willis@softarmor.com>,
        "'Sipping \(E-mail\)'" <sipping@ietf.org>
Subject: RE: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 01:35:40 -0400
Organization: Cisco Systems
Message-ID: <000501c1e5d1$b99a3060$35ee2ca1@OranLT>
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.3416
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <A3C2399B2FACD411A54200508BE39C74054F7152@zwcwd00r.europe.nortel.com>
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] 
> On Behalf Of Mark Watson
> Sent: Tuesday, April 16, 2002 1:51 PM
> To: 'Dean Willis'; Sipping (E-mail)
> Subject: RE: [Sipping] Screened From: and Privacy
> 
> 
> Assuming that you only need one 'identity' is always a bad 
> thing in any application. In these examples there are at least two:
> 1) An identity the user wishes to be known by 
> 2) An identity the service recognises for the user 
> Dean is arguing that (1) is what From: is for, and (2) is 
> confined to the authentication process. 

That is my contention as well.

> It seems people have assumed that in a Service Provider 
> environment From: is sometimes used for (2). 
My preference would be to clarify that such an assumption is unwarranted
and that is not the purpose of the From: field.

> Certainly the 
> SIP spec points you in this direction ('possibly the 
> address-of-record' ...). Particularly the fact that 
> *services*, with no qualification, might key off this field 
> imply that it should be accurate.
Define "accurate". For me "accurate" simply means that it reflects who
the user wishes to be known by to recipients for this request. 


> There is a requirement from 
> Service Providers to deliver something based on (2) to the 
> terminator (absent privacy), especially if the terminator is 
> in the PSTN. 
Ah, YES YES. Hence RPID. We come full circle yet again (maybe this
discussion needs a loop detect feature :-) )

> These last two points have led Service Providers 
> to verify the From: field. They've been encouraged in this by 
> the lack of any other field to communicate (2) passed the 
> device which does authentication. As Dean correctly points 
> out, using From: for information like (2) leads to the need 
> to B2BUA everything for subscriber privacy (if you care about 
> RFC2543 clients). 
How does this follow as long as you define From: as only
user-controlled?

> I would still argue that a subscriber 
> privacy service may need to remove (1) as well, so if the 
> idea is to avoid the requirement to modify/control the From: 
> field, it still might not work. 
I'm afraid we're destined to disagree here. Anything in the From field
is something the user by definition wants to reveal.

> I can't see a clean way out 
> of this. 
Well, RPID may not be perfect, but it does get us out of this.

> I don't think it's realistic to assume that From: is 
> ALWAYS and ONLY of type (1) - purely end-to-end. 
I think the consequences of any other interpretation are much worse, but
that's of course just my considered technical opinion.

> Sure, some 
> systems may treat it this way, and there is no harm in that, 
> but it seems to me too late to make this statement now. 
Why? What have we done in any SIP spec which causes a problem? (as
opposed to what some implementers and other standards groups have done).
What is irreversible here?


> Service Providers exist which put it into class (2). They may 
> need to modify it. 
Existence proof, please, aside from the obvious case of a B2BUA which
can munge ANYTHING and still comply with the SIP spec.

> As long as we are aware of this there 
> should be no problem. I also think it will be common to check 
> the URI portion of the From: field but not the Display Name. 
> We can't *assume* From: is ALWAYS of type (2) either. So 
> let's just get on and define a field for this - Network 
> Asserted Identity. ...Mark 
> 
Ah, so we wind up in the same place at the end. Hope everybody bothered
to read this far :-)

Dave.
> 
> 
> > -----Original Message-----
> > From: Dean Willis [mailto:dean.willis@softarmor.com] 
> > Sent: 16 April 2002 14:14 
> > To: Sipping (E-mail) 
> > Subject: [Sipping] Screened From: and Privacy 
> > 
> > 
> > 
> > Some have suggested that we have everything needed to 
> handle caller ID
> > using the From: field, and that we can reasonably screen 
> > callas based on 
> > the "From:" field to assure the veracity of this field value. 
> > 
> > We COULD.
> > 
> > But there's a very common usage suggesting otherwise.
> > 
> > Generally, there's some sort of authentication token
> > associated with the 
> > phone, not the user of the phone. For example, in 3PPP it's 
> in the SIM 
> > card. For the Cisco 7960 on my desk, it's in the boot file 
> on the TFTP 
> > server, and for the Pingtel phone on my desk it is stored 
> > into the phone 
> > using a web interface. 
> > 
> > So really, the service platform is authenticating the phone, not the
> > user. 
> > 
> > So let's say my kid (I don't have one, but we're pretending here) is
> > using the home phone to call her friend. She doesn't want the 
> > call to be 
> > from Dad, she wants it to be "from" her. 
> > 
> > Logically:
> > 
> >     From: littlekid 
> >     Authenticated-RPID: Account of Dean Willis 9724735455
> > 
> > Ok, so we could add "littlekid" to the list of "Approved 
> From Fields".
> > Or we could revamp things so that she gets a "login" and 
> Her Very Own 
> > RPID (which is contractually iffy in many countries) 
> > 
> > Now her friend comes over and wants to use the phone to call
> > his mother 
> > . . . 
> > 
> > As you can see, this rapidly becomes a provisionng 
> nightmare, and I'd
> > argue that the From screening provides no useful value 
> > anyhow. Much more 
> > useful to leave it as a user provided string with the 
> semantic of "How 
> > the user wants to be though of at the far end". 
> > 
> > --
> > Dean 
> > 
> > 
> > _______________________________________________
> > Sipping mailing list  
> https://www1.ietf.org/mailman/listinfo/sipping 
> > This list 
> is for NEW development of the application of SIP 
> > Use sip-implementors@cs.columbia.edu for questions on current sip 
> > Use sip@ietf.org for new developments of core SIP 
> > 
> 


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



From daemon@optimus.ietf.org  Wed Apr 17 03:15:00 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11709
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 03:14:59 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA20891
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 03:15:02 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA19328;
	Wed, 17 Apr 2002 02:48:42 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA19301
	for <sipping@optimus.ietf.org>; Wed, 17 Apr 2002 02:48:39 -0400 (EDT)
Received: from lohi.eng.song.fi (lohi.eng.song.fi [195.10.149.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11437
	for <sipping@ietf.org>; Wed, 17 Apr 2002 02:48:36 -0400 (EDT)
From: jh@lohi.eng.song.fi
Received: from harjus.eng.song.fi ([195.10.149.20])
	by lohi.eng.song.fi with esmtp (Exim 3.34 #1 (Debian))
	id 16xjEa-00051q-00; Wed, 17 Apr 2002 09:48:04 +0300
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15549.6820.464752.477488@harjus.eng.song.fi>
Date: Wed, 17 Apr 2002 09:48:04 +0300
To: "David R. Oran" <oran@cisco.com>
Cc: "'Mark Watson'" <mwatson@nortelnetworks.com>,
        "'Dean Willis'" <dean.willis@softarmor.com>,
        "'Sipping \(E-mail\)'" <sipping@ietf.org>
Subject: RE: [Sipping] Screened From: and Privacy
In-Reply-To: <000501c1e5d1$b99a3060$35ee2ca1@OranLT>
References: <A3C2399B2FACD411A54200508BE39C74054F7152@zwcwd00r.europe.nortel.com>
	<000501c1e5d1$b99a3060$35ee2ca1@OranLT>
X-Mailer: VM 7.01 under Emacs 21.1.1
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

David R. Oran writes:

 > Ah, YES YES. Hence RPID. We come full circle yet again (maybe this
 > discussion needs a loop detect feature :-) )

today the FROM field is the ONLY CHOICE that a service provider like me
has to figure out what number the user wants to use as the calling party
number and if the user wants to reveal that number to the called party.
former information is carried in the uri of the from field and the
latter in the display string.

in order to prevent the user from spoofing the calling party number, i
MUST check that the number in the uri of the from field indeed has been
allocated for that user.

if the call gets routed (instead of pstn) to another sip user and if the
user doesn't want to reveal the calling party number, i have no other
choice than to implement a b2bua and rewrite the from field, because
most UAs on the market today don't allow me to modify the from field.
if the situation later changes because of the new sip spec, i can get
rid of the b2bua, which, of course, is a good thing.

could someone clarify me once more what value would rpid give over the
above process?  once i understand what it is, i can weight if i makes
sense for me to start using it or save time and money and just stick to
my current working procedure.

-- juha


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



From daemon@optimus.ietf.org  Wed Apr 17 03:20:00 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11744
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 03:20:00 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA21072
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 03:20:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA19819;
	Wed, 17 Apr 2002 02:58:13 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA19792
	for <sipping@optimus.ietf.org>; Wed, 17 Apr 2002 02:58:09 -0400 (EDT)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11576
	for <sipping@ietf.org>; Wed, 17 Apr 2002 02:58:06 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g3H6w73G003641;
	Wed, 17 Apr 2002 08:58:07 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.12])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g3H6w6o5012499;
	Wed, 17 Apr 2002 09:58:06 +0300 (EET DST)
Message-ID: <3CBD1D01.CC0A9D1F@lmf.ericsson.se>
Date: Wed, 17 Apr 2002 09:58:09 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Yu, James" <james.yu@neustar.biz>
CC: sipping@ietf.org
Subject: Re: [Sipping] draft-yu-tel-url-04.txt comment
References: <A83B38C38B3ED6119D3600306E0722D038BF4F@dc02.npac.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit


Hi,

> Those parameters (rn, npdi and cic) are defined as the extensions to the tel
> URL.  There were discussions on supporting tel URL a while back.  I believe
> that bis has included texts that clarifies how parameters in the tel URL
> (plus its extensions) are supported in the sip URL.  We are not discussing
> how those tel URL extensions can be carried as the url-parameters, that is
> implementation issue, as you have indicated.  We are discussing how tel URL
> parameters (including extensions) are carried in the sip URL in a "standard"
> way.  The consensus is that they'll appear in the user part of the sip URL
> when user=phone is present.

So, what you say is: if user=phone, an implementation must always be able to
handle parameters in the SIP-URL???

If this is the case, I think it must be specified in bis, since user=phone is
also specified there.

OR, we can say that an implementation not supporting the parameters will simply
treat the whole user part as a single string, but again - that would probably be
rejected by PSTN routing handlers etc.


Regards,

Christer Holmberg
Ericsson Finland




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



From daemon@optimus.ietf.org  Wed Apr 17 04:41:49 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12648
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 04:41:48 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA25261
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 04:41:51 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA22955;
	Wed, 17 Apr 2002 03:55:30 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA22926
	for <sipping@optimus.ietf.org>; Wed, 17 Apr 2002 03:55:26 -0400 (EDT)
Received: from mail1.telekom.de (mail1.telekom.de [62.225.183.235])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12169
	for <sipping@ietf.org>; Wed, 17 Apr 2002 03:55:23 -0400 (EDT)
Received: from g8pbr.blf01.telekom.de by G8SBV.dmz.telekom.de with ESMTP; Wed, 17 Apr 2002 09:53:35 +0200
Received: by G8PBR.blf01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <2W57FCTL>; Wed, 17 Apr 2002 09:54:51 +0200
Message-Id: <C835D57E3730D6119F5000A0C9F019A94A9A49@U8P13.blf01.telekom.de>
From: "Jesske, R" <R.Jesske@telekom.de>
To: jh@lohi.eng.song.fi, dean.willis@softarmor.com
Cc: sipping@ietf.org
Subject: AW: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 09:54:45 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id DAA22927
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 8bit



> -----Ursprüngliche Nachricht-----
> Von: jh@lohi.eng.song.fi [mailto:jh@lohi.eng.song.fi]
> Gesendet am: Dienstag, 16. April 2002 16:23
> An: Dean Willis
> Cc: Sipping (E-mail)
> Betreff: Re: [Sipping] Screened From: and Privacy
> 
> Dean Willis writes:
> 
>  > Exactly. But they're going to defin their own Subject 
> field and other
>  > user (not SUBSCRIBER) data. I'm arguing that the display name field
>  > (From:) falls into this category.
> 
> yes they could if there is an easy way to enter a subject field, which
> none of the phones i have seen has.  this is analogous to 
> using someone
> else's email account.  you can set the subject line, but not from whom
> the message came from, i.e., the from field.
> 
>  > Because if the display name field (From:) is part of the SUBSCRIBER
>  > data, as you are arguing, then it falls into 
> network-controlled privacy
>  > management regulation and we end up with "MUST B2BUA 
> everything." If it
>  > is a USER field, then regulation affects it much more lightly.
> 
> i'm arguing that the whole from field belongs to the user whose phone
> i'm borrowing and there is no problem whatsoever with privacy
> regulation.  the privacy what i get is the privacy of the person whose
> phone (or "line") i'm using.  if i borrow someone else's cell phone, i
> don't get my own privacy, but the privacy of the phone owner. 
> if i want
> my own privacy, i need to change the sim.
> 
>  > Life is much better if we consider "From:", along with 
> "Subject:" and
>  > other such fields, as  per-call user-provided data 
> intended for display
>  > to the other end of the dialog. Filtering the From, as you 
> are doing,
>  > forces it into the regulatory realm in a way that you're 
> not going to
>  > like.
> 
> so far we haven't had any other field than the from field to identify
> the calling party:
> 
> 20.20 From The From header field indicates the initiator of the
>    request. This may be different from the initiator of the
>    dialog. Requests sent by the callee to the caller use the callee s
>    address in the From header field. The optional  display-name  is
>    meant to be rendered by a human user interface. A system SHOULD use
>    4280 the display name  Anonymous  if the identity of the 
> client is to
>    remain hidden.
> 
> all sip phones on the market include the calling user's address in the
> from field.  they do not have any other field for that 
> purpose and thus
> i have not had any other way to make sure that the callee address as
> seen by the pstn has not been faked.  if i had not used the from field
> for that purpose, there could not (for regulatory reasons) 
> have been any
> sip to pstn service in finland.

That is the problem for the interworking with PSTN, that the phone include the From header. For the interworking case with the PSTN the From header is a not trusted information (because it is direct from the user and not verified from the network). But if there is a network provided indication (from a trusted network)that verifies that the From is the true user address (like the RPID do this with the screen = yes), than the Interworking entity can map the information in a proper way to the PSTN (including the regulatory aspects are fulfilled).    
There will be no PSTN Operator that take an untrusted From Header to a calling party number --> instead the PSTN operator will set up a new calling party number that is network provided and trusted!
> 
> since there is already lots of sip phones on the market 
> owners of which
> do want to make pstn calls, i have to keep on screening calls based on
> the from field for a very long time to come.  also, many of 
> the proxies
> on the marker can today do this from field screening.  changing it so
> something else would do nothing else but make things more complicated.
> 
> of course operational complexity and backwards compatibility is not a
> problem for vendors like dynamicsoft and nortel, who do not 
> need to run
> sip services.
> 
> -- juha
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

Best Regards 

Roland Jesske

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



From daemon@optimus.ietf.org  Wed Apr 17 05:04:47 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12865
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 05:04:47 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA26336
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 05:04:50 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA25133;
	Wed, 17 Apr 2002 04:38:19 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA25103
	for <sipping@optimus.ietf.org>; Wed, 17 Apr 2002 04:38:17 -0400 (EDT)
Received: from harjus.eng.song.fi (harjus.eng.song.fi [195.10.149.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12621
	for <sipping@ietf.org>; Wed, 17 Apr 2002 04:38:11 -0400 (EDT)
From: jh@lohi.eng.song.fi
Received: from harjus.eng.song.fi ([195.10.149.20])
	by lohi.eng.song.fi with esmtp (Exim 3.34 #1 (Debian))
	id 16xkb9-00053c-00; Wed, 17 Apr 2002 11:15:27 +0300
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15549.12063.298605.10950@harjus.eng.song.fi>
Date: Wed, 17 Apr 2002 11:15:27 +0300
To: "Jesske, R" <R.Jesske@telekom.de>
Cc: dean.willis@softarmor.com, sipping@ietf.org
Subject: AW: [Sipping] Screened From: and Privacy
In-Reply-To: <C835D57E3730D6119F5000A0C9F019A94A9A49@U8P13.blf01.telekom.de>
References: <C835D57E3730D6119F5000A0C9F019A94A9A49@U8P13.blf01.telekom.de>
X-Mailer: VM 7.01 under Emacs 21.1.1
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Jesske, R writes:

 > That is the problem for the interworking with PSTN, that the phone
 > include the From header. For the interworking case with the PSTN the
 > >From header is a not trusted information (because it is direct from
 > the user and not verified from the network). 

in my case it IS verified.

 > But if there is a
 > network provided indication (from a trusted network)that verifies
 > that the From is the true user address (like the RPID do this with
 > the screen = yes), than the Interworking entity can map the
 > information in a proper way to the PSTN (including the regulatory
 > aspects are fulfilled). 

i don't see how rpid would make things any more trusted than the from
field. if two providers don't trust each other, they would not trust
the rpid any more than the from field.

 > There will be no PSTN Operator that take an untrusted From Header to
 > a calling party number --> instead the PSTN operator will set up a
 > new calling party number that is network provided and trusted!

to which number the network would set the calling party number?  my sip
users can have any number of calling party numbers belonging to any
number of calling areas and soon even to any number of countries.  

thus the user thus MUST have some means to indicate to me which of those
numbers that i have allocated to the user, the user wants to use as the
calling party number in a particular call.  today this information is
carried in the uri of the from field, which becomes a trusted entity
after i have checked its validity.  

it is ok for me to add "screen=yes" parameter to the from field although
i don't need that information for anything. and if you want to copy the
from field to another rpid field and have "screen=yes" there, it is ok
with me too as long as i'm not forced to do that myself.

-- juha


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



From daemon@optimus.ietf.org  Wed Apr 17 05:19:13 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13062
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 05:19:13 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA26793
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 05:19:16 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA26245;
	Wed, 17 Apr 2002 05:01:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA26216
	for <sipping@optimus.ietf.org>; Wed, 17 Apr 2002 05:01:32 -0400 (EDT)
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12836
	for <sipping@ietf.org>; Wed, 17 Apr 2002 05:01:26 -0400 (EDT)
From: hisham.khartabil@nokia.com
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x2.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g3H91iF29866
	for <sipping@ietf.org>; Wed, 17 Apr 2002 12:01:44 +0300 (EET DST)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5a5037bfc6ac158f24077@esvir04nok.ntc.nokia.com>;
 Wed, 17 Apr 2002 12:01:27 +0300
Received: from esebe010.NOE.Nokia.com ([172.21.138.49]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.3779);
	 Wed, 17 Apr 2002 12:01:27 +0300
Received: from esebe019.NOE.Nokia.com ([172.21.138.58]) by esebe010.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Wed, 17 Apr 2002 12:01:26 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 12:01:26 +0300
Message-ID: <2038BCC78B1AD641891A0D1AE133DBB777913A@esebe019.NOE.Nokia.com>
Thread-Topic: [Sipping] Screened From: and Privacy
Thread-Index: AcHlTcmmPVLgjgc2QRSocMOZ527iDAAoDsAw
To: <dean.willis@softarmor.com>, <jh@lohi.eng.song.fi>
Cc: <sipping@ietf.org>
X-OriginalArrivalTime: 17 Apr 2002 09:01:26.0807 (UTC) FILETIME=[74D35A70:01C1E5EE]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id FAA26217
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 8bit



> -----Original Message-----
> From: ext Dean Willis [mailto:dean.willis@softarmor.com]
> Sent: Tuesday, April 16, 2002 4:49 PM
> To: jh@lohi.eng.song.fi
> Cc: Sipping (E-mail)
> Subject: Re: [Sipping] Screened From: and Privacy
> 
> 
> 
> > in this case, the friend most likely would use your kid's "line"
> rather
> > than defining his/her own to the phone.  it is the same as using
> > someone's cell phone.  most likely the friend would not open it and
> > replace his/her own sim to the phone in order to make the call,
> because
> > that would be too complicated.
> 
> Exactly. But they're going to defin their own Subject field and other
> user (not SUBSCRIBER) data. I'm arguing that the display name field
> (From:) falls into this category.


Does that include Home Proxy? If you want to use my SIP phone and you don't have an account with my service provider, you have to reconfigure my phone with your service provider home proxy. I prefer for you to just use my phone and not change the configuration.



regards,
Hisham

> 
> > i again fail to see what this has to do with the privacy discussion.
> > when you use someone else's phone, you will also use his/her privacy
> > setup.
> 
> Because if the display name field (From:) is part of the SUBSCRIBER
> data, as you are arguing, then it falls into 
> network-controlled privacy
> management regulation and we end up with "MUST B2BUA 
> everything." If it
> is a USER field, then regulation affects it much more lightly.
> 
> What would be the implication if we added a "New" header for
> "UserDisplayName" intended for just what I've proposed above? Simple:
> The phone people would inist that that be rewritten by the network,
> because this MIGHT conflict with Subscriber privacy 
> requirements. Since
> the protocol allows extension with arbitrary new headers, the logical
> requirement is for "the network" to be required to block arbitrary new
> headers, thereby destroying service transparency.
> 
> Life is much better if we consider "From:", along with "Subject:" and
> other such fields, as  per-call user-provided data intended 
> for display
> to the other end of the dialog. Filtering the From, as you are doing,
> forces it into the regulatory realm in a way that you're not going to
> like.
> 
> --
> Dean
> 
> 
> --
> Dean
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

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



From daemon@optimus.ietf.org  Wed Apr 17 05:54:40 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13453
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 05:54:38 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA28616
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 05:54:42 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA27650;
	Wed, 17 Apr 2002 05:32:02 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA27620
	for <sipping@optimus.ietf.org>; Wed, 17 Apr 2002 05:31:57 -0400 (EDT)
Received: from zctfs063.nortelnetworks.com (zctfs063.nortelnetworks.com [47.164.128.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13196
	for <sipping@ietf.org>; Wed, 17 Apr 2002 05:31:53 -0400 (EDT)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zctfs063.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3H9VLe04716;
	Wed, 17 Apr 2002 11:31:21 +0200 (MEST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3H9Uft10203;
	Wed, 17 Apr 2002 10:30:41 +0100 (BST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <HLDBTP0S>; Wed, 17 Apr 2002 10:31:22 +0100
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7158@zwcwd00r.europe.nortel.com>
From: "Mark Watson"<mwatson@nortelnetworks.com>
To: "'David R. Oran'" <oran@cisco.com>,
        "'Dean Willis'"
	 <dean.willis@softarmor.com>,
        "'Sipping (E-mail)'" <sipping@ietf.org>
Subject: RE: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 10:31:21 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E5F2.A2B04292"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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_01C1E5F2.A2B04292
Content-Type: text/plain

Starting at the end of Dave's response to my comments..

> > So, let's just get on and define a field for this - Network 
> > Asserted Identity. ...Mark 
> > 
> Ah, so we wind up in the same place at the end. Hope 
> everybody bothered
> to read this far :-)

Comments, please, to the requirements I suggested in the Network Asserted
Identity thread - perhaps we can make some rapid progress on this thereby
decide what to do with the current privacy draft.

If you're more interested in the 'philosophy of the From field', read on...

> > Certainly the 
> > SIP spec points you in this direction ('possibly the 
> > address-of-record' ...). Particularly the fact that 
> > *services*, with no qualification, might key off this field 
> > imply that it should be accurate.
> Define "accurate". For me "accurate" simply means that it reflects who
> the user wishes to be known by to recipients for this request. 

An incoming call barring service, or other filtering service based on the
origin of the call, is no use whatsoever if it's based on how the calling
user 'wishes to be known', as it give the caller an easy way to override my
service.

Service of this kind can only work if you have some confidence in the field
they are based on. The fact that the SIP specification implies such services
might be based on From: has quite reasonably led service providers to
believe they should verify this field.

You argue that this is a mistake - mayby so - but that doesn't change the
words in the spec.

<snip>
> > These last two points have led Service Providers 
> > to verify the From: field. They've been encouraged in this by 
> > the lack of any other field to communicate (2) passed the 
> > device which does authentication. As Dean correctly points 
> > out, using From: for information like (2) leads to the need 
> > to B2BUA everything for subscriber privacy (if you care about 
> > RFC2543 clients). 
> How does this follow as long as you define From: as only
> user-controlled?
> 

The field is NOT 'user-controlled' if the user is forced to insert a
specific piece of information.

> > I would still argue that a subscriber 
> > privacy service may need to remove (1) as well, so if the 
> > idea is to avoid the requirement to modify/control the From: 
> > field, it still might not work. 
> I'm afraid we're destined to disagree here. Anything in the From field
> is something the user by definition wants to reveal.
> 

But the subscriber may not want it revealed, and the subscriber's wishes may
override the users.


> > I can't see a clean way out 
> > of this. 
> Well, RPID may not be perfect, but it does get us out of this.
> 

Indeed.

> > I don't think it's realistic to assume that From: is 
> > ALWAYS and ONLY of type (1) - purely end-to-end. 
> I think the consequences of any other interpretation are much 
> worse, but
> that's of course just my considered technical opinion.
> 

I think the consequences of the purely end-to-end interpretation, are that
for Service Provider environments, we essentially invent an 'alternative
From' field, and the From field itself does not get used. I don't have a big
problem with this, but I thought others did.

> > Sure, some 
> > systems may treat it this way, and there is no harm in that, 
> > but it seems to me too late to make this statement now. 
> Why? What have we done in any SIP spec which causes a problem? (as
> opposed to what some implementers and other standards groups 
> have done).
> What is irreversible here?
>

As noted above, the SIP specification does seem to imply that there is some
advantage to be gained by checking the From field is valid, as it is used
for terminating end services other than display.

> 
> > Service Providers exist which put it into class (2). They may 
> > need to modify it. 
> Existence proof, please, aside from the obvious case of a B2BUA which
> can munge ANYTHING and still comply with the SIP spec.
>

Juha described how his service verified the From field. It is unlikely that
3GPP would be pursuaded to do otherwise if they are pursuaded to use the
From field at all. I described in some detail on the SIP list thread why
this may imply a Data Protetcion requirement to modift the field. I don't
dispute that this may require a B2BUA.
 
>

...Mark 

------_=_NextPart_001_01C1E5F2.A2B04292
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.2655.35">
<TITLE>RE: [Sipping] Screened From: and Privacy</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Starting at the end of Dave's response to my =
comments..</FONT>
</P>

<P><FONT SIZE=3D2>&gt; &gt; So, let's just get on and define a field =
for this - Network </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Asserted Identity. ...Mark </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Ah, so we wind up in the same place at the end. =
Hope </FONT>
<BR><FONT SIZE=3D2>&gt; everybody bothered</FONT>
<BR><FONT SIZE=3D2>&gt; to read this far :-)</FONT>
</P>

<P><FONT SIZE=3D2>Comments, please, to the requirements I suggested in =
the Network Asserted Identity thread - perhaps we can make some rapid =
progress on this thereby decide what to do with the current privacy =
draft.</FONT></P>

<P><FONT SIZE=3D2>If you're more interested in the 'philosophy of the =
From field', read on...</FONT>
</P>

<P><FONT SIZE=3D2>&gt; &gt; Certainly the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; SIP spec points you in this direction =
('possibly the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; address-of-record' ...). Particularly the =
fact that </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; *services*, with no qualification, might =
key off this field </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; imply that it should be accurate.</FONT>
<BR><FONT SIZE=3D2>&gt; Define &quot;accurate&quot;. For me =
&quot;accurate&quot; simply means that it reflects who</FONT>
<BR><FONT SIZE=3D2>&gt; the user wishes to be known by to recipients =
for this request. </FONT>
</P>

<P><FONT SIZE=3D2>An incoming call barring service, or other filtering =
service based on the origin of the call, is no use whatsoever if it's =
based on how the calling user 'wishes to be known', as it give the =
caller an easy way to override my service.</FONT></P>

<P><FONT SIZE=3D2>Service of this kind can only work if you have some =
confidence in the field they are based on. The fact that the SIP =
specification implies such services might be based on From: has quite =
reasonably led service providers to believe they should verify this =
field.</FONT></P>

<P><FONT SIZE=3D2>You argue that this is a mistake - mayby so - but =
that doesn't change the words in the spec.</FONT>
</P>

<P><FONT SIZE=3D2>&lt;snip&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; These last two points have led Service =
Providers </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; to verify the From: field. They've been =
encouraged in this by </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the lack of any other field to communicate =
(2) passed the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; device which does authentication. As Dean =
correctly points </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; out, using From: for information like (2) =
leads to the need </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; to B2BUA everything for subscriber privacy =
(if you care about </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; RFC2543 clients). </FONT>
<BR><FONT SIZE=3D2>&gt; How does this follow as long as you define =
From: as only</FONT>
<BR><FONT SIZE=3D2>&gt; user-controlled?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>The field is NOT 'user-controlled' if the user is =
forced to insert a specific piece of information.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; &gt; I would still argue that a subscriber =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; privacy service may need to remove (1) as =
well, so if the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; idea is to avoid the requirement to =
modify/control the From: </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; field, it still might not work. </FONT>
<BR><FONT SIZE=3D2>&gt; I'm afraid we're destined to disagree here. =
Anything in the From field</FONT>
<BR><FONT SIZE=3D2>&gt; is something the user by definition wants to =
reveal.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>But the subscriber may not want it revealed, and the =
subscriber's wishes may override the users.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&gt; &gt; I can't see a clean way out </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; of this. </FONT>
<BR><FONT SIZE=3D2>&gt; Well, RPID may not be perfect, but it does get =
us out of this.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>Indeed.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; &gt; I don't think it's realistic to assume that =
From: is </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ALWAYS and ONLY of type (1) - purely =
end-to-end. </FONT>
<BR><FONT SIZE=3D2>&gt; I think the consequences of any other =
interpretation are much </FONT>
<BR><FONT SIZE=3D2>&gt; worse, but</FONT>
<BR><FONT SIZE=3D2>&gt; that's of course just my considered technical =
opinion.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>I think the consequences of the purely end-to-end =
interpretation, are that for Service Provider environments, we =
essentially invent an 'alternative From' field, and the From field =
itself does not get used. I don't have a big problem with this, but I =
thought others did.</FONT></P>

<P><FONT SIZE=3D2>&gt; &gt; Sure, some </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; systems may treat it this way, and there =
is no harm in that, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; but it seems to me too late to make this =
statement now. </FONT>
<BR><FONT SIZE=3D2>&gt; Why? What have we done in any SIP spec which =
causes a problem? (as</FONT>
<BR><FONT SIZE=3D2>&gt; opposed to what some implementers and other =
standards groups </FONT>
<BR><FONT SIZE=3D2>&gt; have done).</FONT>
<BR><FONT SIZE=3D2>&gt; What is irreversible here?</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
</P>

<P><FONT SIZE=3D2>As noted above, the SIP specification does seem to =
imply that there is some advantage to be gained by checking the From =
field is valid, as it is used for terminating end services other than =
display.</FONT></P>

<P><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Service Providers exist which put it into =
class (2). They may </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; need to modify it. </FONT>
<BR><FONT SIZE=3D2>&gt; Existence proof, please, aside from the obvious =
case of a B2BUA which</FONT>
<BR><FONT SIZE=3D2>&gt; can munge ANYTHING and still comply with the =
SIP spec.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
</P>

<P><FONT SIZE=3D2>Juha described how his service verified the From =
field. It is unlikely that 3GPP would be pursuaded to do otherwise if =
they are pursuaded to use the From field at all. I described in some =
detail on the SIP list thread why this may imply a Data Protetcion =
requirement to modift the field. I don't dispute that this may require =
a B2BUA.</FONT></P>

<P><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
</P>

<P><FONT SIZE=3D2>...Mark </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E5F2.A2B04292--

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



From daemon@optimus.ietf.org  Wed Apr 17 05:55:36 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13488
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 05:55:31 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA28657
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 05:55:34 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA28069;
	Wed, 17 Apr 2002 05:43:23 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA28037
	for <sipping@optimus.ietf.org>; Wed, 17 Apr 2002 05:43:19 -0400 (EDT)
Received: from zctfs063.nortelnetworks.com (zctfs063.nortelnetworks.com [47.164.128.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13316
	for <sipping@ietf.org>; Wed, 17 Apr 2002 05:43:13 -0400 (EDT)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by zctfs063.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3H9g2e07324;
	Wed, 17 Apr 2002 11:42:02 +0200 (MEST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <HLDBTQX6>; Wed, 17 Apr 2002 10:42:05 +0100
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7159@zwcwd00r.europe.nortel.com>
From: "Mark Watson"<mwatson@nortelnetworks.com>
To: "'jh@lohi.eng.song.fi'" <jh@lohi.eng.song.fi>,
        Dean Willis
	 <dean.willis@softarmor.com>
Cc: "Sipping (E-mail)" <sipping@ietf.org>
Subject: RE: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 10:41:55 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E5F4.1C8B722A"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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_01C1E5F4.1C8B722A
Content-Type: text/plain


Juha wrote:

> i'm arguing that the whole from field belongs to the user whose phone
> i'm borrowing and there is no problem whatsoever with privacy
> regulation.  the privacy what i get is the privacy of the person whose
> phone (or "line") i'm using.  if i borrow someone else's cell phone, i
> don't get my own privacy, but the privacy of the phone owner. 
> if i want
> my own privacy, i need to change the sim.
>

Minor point, but when you borrow someone elses phone, you become the 'user'
and you have a right to restrict the delivery of the identity (be it yours,
the phones, the phone owner, the 'line' etc.).

If the subscriber (who may or may not be the person who you have borrowed
the phone from) has requested that this information not be delivered, you do
not have the right to override this.

[At least this is my understanding of the legislation in Europe]

...Mark 

------_=_NextPart_001_01C1E5F4.1C8B722A
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.2655.35">
<TITLE>RE: [Sipping] Screened From: and Privacy</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2>Juha wrote:</FONT>
</P>

<P><FONT SIZE=3D2>&gt; i'm arguing that the whole from field belongs to =
the user whose phone</FONT>
<BR><FONT SIZE=3D2>&gt; i'm borrowing and there is no problem =
whatsoever with privacy</FONT>
<BR><FONT SIZE=3D2>&gt; regulation.&nbsp; the privacy what i get is the =
privacy of the person whose</FONT>
<BR><FONT SIZE=3D2>&gt; phone (or &quot;line&quot;) i'm using.&nbsp; if =
i borrow someone else's cell phone, i</FONT>
<BR><FONT SIZE=3D2>&gt; don't get my own privacy, but the privacy of =
the phone owner. </FONT>
<BR><FONT SIZE=3D2>&gt; if i want</FONT>
<BR><FONT SIZE=3D2>&gt; my own privacy, i need to change the =
sim.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
</P>

<P><FONT SIZE=3D2>Minor point, but when you borrow someone elses phone, =
you become the 'user' and you have a right to restrict the delivery of =
the identity (be it yours, the phones, the phone owner, the 'line' =
etc.).</FONT></P>

<P><FONT SIZE=3D2>If the subscriber (who may or may not be the person =
who you have borrowed the phone from) has requested that this =
information not be delivered, you do not have the right to override =
this.</FONT></P>

<P><FONT SIZE=3D2>[At least this is my understanding of the legislation =
in Europe]</FONT>
</P>

<P><FONT SIZE=3D2>...Mark </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E5F4.1C8B722A--

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



From daemon@optimus.ietf.org  Wed Apr 17 07:07:27 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14316
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 07:07:27 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA01872
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 07:07:29 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA01042;
	Wed, 17 Apr 2002 06:52:39 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA00939
	for <sipping@optimus.ietf.org>; Wed, 17 Apr 2002 06:52:32 -0400 (EDT)
Received: from fox.iptel.org (fox.iptel.org [195.37.77.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14120
	for <sipping@ietf.org>; Wed, 17 Apr 2002 06:52:29 -0400 (EDT)
Received: from jku2.fokus.gmd.de (datela-1-3-63.dialup.vol.cz [212.20.97.209])
	by fox.iptel.org (8.11.6/8.11.6) with ESMTP id g3HArpZ19056;
	Wed, 17 Apr 2002 12:53:52 +0200
Message-Id: <5.1.0.14.0.20020417125022.02dc7e50@mailhost.fokus.gmd.de>
X-Sender: jku@mailhost.fokus.gmd.de
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 17 Apr 2002 12:51:48 +0200
To: Pekka Pessi <Pekka.Pessi@nokia.com>, sipping@ietf.org
From: Jiri Kuthan <kuthan@fokus.gmd.de>
Subject: Re: [Sipping] IPv6 messages for callflows?
In-Reply-To: <pvvgasysw0.fsf@agni.research.nokia.com>
References: <Pine.WNT.4.44.0204121147410.-360391@chorizo.rapidconvergence.com>
 <Pine.WNT.4.44.0204121147410.-360391@chorizo.rapidconvergence.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Hi Pekka,

one of our developpers meant there was a bug in your example. Can you
verify that?

Thanks,

-Jiri

> >7.42 INVITE Request with IPv6 Addresses 
> > 
> > This is a valid INVITE message containing IPv6 addresses. An IPv4-only 
> > SIP element should be able to parse and respond this request. 
> > 
> > INVITE sip:bob@[3ffe:1200:3012:c006:206:5bff:fe55:462f] SIP/2.0 
> > Via: SIP/2.0/UDP [3ffe:1200:3012:c006:206:5bff:fe55:462f] 
> > ;branch=z9hG4bKoHjruVnj9aW 
> > Via: SIP/2.0/UDP [3ffe:1200:3012:c000:210:a4ff:fe8d:6a46]:5062 
> > ;branch=z9hG4bKuNCTHs8Lumv 
> > ;received=[3ffe:1200:3012:c006:210:a4ff:fe8d:6a46] 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
this is an IPv6reference. the "received" param is defined as 
via-received = "received" EQUAL ( IPv4address / IPv6address ) 
(see page 241 of draft-ietf-sip-rfc2543bis-09) ^^^^^^^^^^^ 
So this is illegal, because an IPv6address is basically not the same as an 
IPv6reference: 
IPv6reference = "[" IPv6address "]"
The same is in 7.43
Did I miss something ? Or do I have an old draft ?


At 10:01 AM 4/16/2002, Pekka Pessi wrote:
>        Hello,
>
>        I think that a couple of torture messages with IPv6 addresses in
>        them would be nice addition. 
>
>        I have attached an INVITE request and a 488 response to it, feel
>        free to include them.
>
>                                                Pekka
>
>-----8<-------------8<-------------8<-------------8<-------------8<-----
>7.42 INVITE Request with IPv6 Addresses
>
>   This is a valid INVITE message containing IPv6 addresses. An IPv4-only
>   SIP element should be able to parse and respond this request.
>
>   INVITE sip:bob@[3ffe:1200:3012:c006:206:5bff:fe55:462f] SIP/2.0
>   Via: SIP/2.0/UDP [3ffe:1200:3012:c006:206:5bff:fe55:462f]
>        ;branch=z9hG4bKoHjruVnj9aW
>   Via: SIP/2.0/UDP [3ffe:1200:3012:c000:210:a4ff:fe8d:6a46]:5062
>        ;branch=z9hG4bKuNCTHs8Lumv
>        ;received=[3ffe:1200:3012:c006:210:a4ff:fe8d:6a46]
>   From: <sip:alice@[3ffe:1200:3012:c000:210:a4ff:fe8d:6a46]>
>        ;tag=ud6a29947
>   Record-Route: <sip:bob@example.com;maddr=[fe80::206:5bff:fe55:462f]>
>   To: <sip:bob@example.com;maddr=[3ffe:1200:3012:c006:206:5bff:fe55:462f]>
>   Call-ID: f89fa68e-5109-11d6-0581-0010A48D6A46
>   CSeq: 2 INVITE
>   Contact: <sip:[3ffe:1200:3012:c000:210:a4ff:fe8d:6a46]:5062>
>   Call-Info: <http://[3ffe:1200:3012:c000:210:a4ff:fe8d:6a46]/alice.gif>
>        ;purpose=icon;g-param=[3ffe:1200:3012:c000:210:a4ff:fe8d:6a46]
>   Content-Type: application/sdp
>   Content-Length: 352
>
>   v=0
>   o=alice 1804289383 2 IN IP6 3ffe:1200:3012:c000:210:a4ff:fe8d:6a46
>   s=-
>   c=IN IP6 3ffe:1200:3012:c000:210:a4ff:fe8d:6a46
>   t=0 0
>   m=audio 5004 RTP/AVP 96 97 
>   a=rtpmap:96 AMR/8000
>   a=rtpmap:97 GSM-EFR/8000
>
>7.43 Response message with IPv6 Addresses
>
>   This is a response from IPv4-only host to the INVITE above.
>
>   SIP/2.0 488 Not Acceptable Here
>   Via: SIP/2.0/UDP [3ffe:1200:3012:c006:206:5bff:fe55:462f]
>        ;branch=z9hG4bKoHjruVnj9aW;received=172.21.40.44
>   Via: SIP/2.0/UDP [3ffe:1200:3012:c000:210:a4ff:fe8d:6a46]:5062
>        ;branch=z9hG4bKuNCTHs8Lumv
>        ;received=[3ffe:1200:3012:c006:210:a4ff:fe8d:6a46]
>   From: <sip:alice@[3ffe:1200:3012:c000:210:a4ff:fe8d:6a46]>
>        ;tag=ud6a29947
>   To: <sip:bob@example.com;maddr=[3ffe:1200:3012:c006:206:5bff:fe55:462f]>
>        ;tag=f4ef9d6a
>   Call-ID: f89fa68e-5109-11d6-0581-0010A48D6A46
>   CSeq: 2 INVITE
>   Warning: 301 172.21.40.24 "IN network address type 'IP6' not supported"
>   Content-Length: 0
>
>-----8<-------------8<-------------8<-------------8<-------------8<-----
>
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the 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 daemon@optimus.ietf.org  Wed Apr 17 08:26:14 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15572
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 08:26:14 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA05557
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 08:26:16 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA04614;
	Wed, 17 Apr 2002 08:07:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA04583
	for <sipping@optimus.ietf.org>; Wed, 17 Apr 2002 08:07:01 -0400 (EDT)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15218
	for <sipping@ietf.org>; Wed, 17 Apr 2002 08:06:57 -0400 (EDT)
Received: from mira-sjc5-9.cisco.com (IDENT:mirapoint@mira-sjc5-9.cisco.com [171.71.163.32])
	by sj-msg-core-2.cisco.com (8.12.2/8.12.2) with ESMTP id g3HC6S9C020438;
	Wed, 17 Apr 2002 05:06:28 -0700 (PDT)
Received: from OranLT (sjc-vpn3-425.cisco.com [10.21.65.169])
	by mira-sjc5-9.cisco.com (Mirapoint)
	with ESMTP id ACQ81308;
	Wed, 17 Apr 2002 05:06:38 -0700 (PDT)
From: "David R. Oran" <oran@cisco.com>
To: "'Mark Watson'" <mwatson@nortelnetworks.com>,
        "'Dean Willis'" <dean.willis@softarmor.com>,
        "'Sipping \(E-mail\)'" <sipping@ietf.org>
Subject: RE: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 07:58:35 -0400
Organization: Cisco Systems
Message-ID: <007c01c1e607$34ab5dd0$35ee2ca1@OranLT>
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.3416
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <A3C2399B2FACD411A54200508BE39C74054F7158@zwcwd00r.europe.nortel.com>
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] 
> On Behalf Of Mark Watson
> Sent: Wednesday, April 17, 2002 5:31 AM
> To: 'David R. Oran'; 'Dean Willis'; 'Sipping (E-mail)'
> Subject: RE: [Sipping] Screened From: and Privacy
> 
> 
> > > Certainly the
> > > SIP spec points you in this direction ('possibly the 
> > > address-of-record' ...). Particularly the fact that 
> > > *services*, with no qualification, might key off this field 
> > > imply that it should be accurate. 
> > Define "accurate". For me "accurate" simply means that it 
> reflects who
> > the user wishes to be known by to recipients for this request. 

Mark responded:
> An incoming call barring service, or other filtering service 
> based on the origin of the call, is no use whatsoever if it's 
> based on how the calling user 'wishes to be known', as it 
> give the caller an easy way to override my service. 
How did you get there? The screening service can always challege the
calling user to authenticate. Anything in a callee's call screening list
is something he put there, and hence can include authentication as well
as authorization parameters.

> Service 
> of this kind can only work if you have some confidence in the 
> field they are based on. 
Yup. That's what cryptographic authenication/integrity/authorizationb
are for. Waving your hands and saying that something (anything!) can be
relied on because you think it was stuffed in the message by a service
provider you trust is hoodoo. The need for RPID asises not for these
mundane reasons, but for the need to cover the very few very tricky
cases of call trace and anonymous call return and possibly a couple of
others I can't recall at the moment.

> The fact that the SIP specification 
> implies such services might be based on From: has quite 
> reasonably led service providers to believe they should 
> verify this field. You argue that this is a mistake - mayby 
> so - but that doesn't change the words in the spec. 
> 
It's perfectly OK to verify anything in any field if you want. I'm not
sure this is in fact relevant to the discussion. 

<snip> 
> > > These last two points have led Service Providers
> > > to verify the From: field. They've been encouraged in this by 
> > > the lack of any other field to communicate (2) passed the 
> > > device which does authentication. As Dean correctly points 
> > > out, using From: for information like (2) leads to the need 
> > > to B2BUA everything for subscriber privacy (if you care about 
> > > RFC2543 clients). 
> > How does this follow as long as you define From: as only
> > user-controlled? 
> > 
> The field is NOT 'user-controlled' if the user is forced to 
> insert a specific piece of information. 
Sure it is. I can still put anything I want in there. If I don't like
the fact that the service provider rejects the call I go use somebody
else. This is like saying the RequestURI: field isn't user controlled,
because I may have subscribed to a free-phone service that only lets me
call certain destinations that don't go through a PSTN gateway.

> > > I would still argue that a subscriber
> > > privacy service may need to remove (1) as well, so if the 
> > > idea is to avoid the requirement to modify/control the From: 
> > > field, it still might not work. 
> > I'm afraid we're destined to disagree here. Anything in the 
> From field
> > is something the user by definition wants to reveal. 
> > 
> But the subscriber may not want it revealed, and the 
> subscriber's wishes may override the users. 
> 
Then the "subscriber" can, in a proxy of B2BUA controlled by him (like
the proxy in his basement if a residence, or the border proxy of a
corporate site) do any scrubbing or call rejection he likes. This
reliance on the PSTN definitions of user and subscriber are really,
really getting in the way here. I'm not saying that we ignore the
distinction. Rather, I am saying that, unlike the PSTN world, it is easy
to trivial to insert an intermediary, controlled by you that you trust
to verify and screen outgoing calls, incoming calls, or both.

> 
> > > I can't see a clean way out
> > > of this. 
> > Well, RPID may not be perfect, but it does get us out of this.
> > 
> Indeed. 
> > > I don't think it's realistic to assume that From: is
> > > ALWAYS and ONLY of type (1) - purely end-to-end. 
> > I think the consequences of any other interpretation are much
> > worse, but 
> > that's of course just my considered technical opinion. 
> > 
> I think the consequences of the purely end-to-end 
> interpretation, are that for Service Provider environments, 
> we essentially invent an 'alternative From' field, and the 
> From field itself does not get used. I don't have a big 
> problem with this, but I thought others did.
I think the problems arise from trying to make this into some
general-purpose alternate identity scheme where we just re-create all
the authentication ad authorization problems of the existing end-to-end
fields except now the problem is middle-to-middle or middle-to-end over
multiple hops. Something restricted of this sort is needed for malicious
call trace and aonoymous call return, but my suspicion is that trying to
over-generalizew is what sends this into la-la-land.

> > > Sure, some
> > > systems may treat it this way, and there is no harm in that, 
> > > but it seems to me too late to make this statement now. 
> > Why? What have we done in any SIP spec which causes a problem? (as
> > opposed to what some implementers and other standards groups 
> > have done). 
> > What is irreversible here? 
> > 
> As noted above, the SIP specification does seem to imply that 
> there is some advantage to be gained by checking the From 
> field is valid, as it is used for terminating end services 
> other than display.
I would agree with you if you reworded to say "that the From field in a
SIP message that you have authenticated and integrity checked contains a
value which leads you to believe you want to accept the call".

> > 
> > > Service Providers exist which put it into class (2). They may
> > > need to modify it. 
> > Existence proof, please, aside from the obvious case of a 
> B2BUA which
> > can munge ANYTHING and still comply with the SIP spec. 
> > 
> Juha described how his service verified the From field. 
There's nothing wrong with what Juha is doing. If I don't like it I go
get my service from somebody else. He isn't rewiting or asserting random
alternate identifies for me without my knowledge. He's only deciding
what calls to process based on who he believes the call is from. If we
wanted to reject all calls that didn't have the IP address of one of his
customers in the first VIA header that would be OK too!

> It is 
> unlikely that 3GPP would be pursuaded to do otherwise if they 
> are pursuaded to use the From field at all. I described in 
> some detail on the SIP list thread why this may imply a Data 
> Protetcion requirement to modift the field. I don't dispute 
> that this may require a B2BUA.
> 
Look, the basic connundrum is how to process calls for which the user
has declared anonymity while allowing call trace and a few other special
cases. Can we agree at least one that?
 
> > 
> ...Mark 
>
Dave. 


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



From daemon@optimus.ietf.org  Wed Apr 17 09:21:10 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16787
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 09:21:10 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA08455
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 09:21:13 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA07794;
	Wed, 17 Apr 2002 09:05:14 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA07767
	for <sipping@optimus.ietf.org>; Wed, 17 Apr 2002 09:05:11 -0400 (EDT)
Received: from mail1.telekom.de (mail1.telekom.de [62.225.183.235])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16325
	for <sipping@ietf.org>; Wed, 17 Apr 2002 09:05:06 -0400 (EDT)
Received: from g8pbr.blf01.telekom.de by G8SBV.dmz.telekom.de with ESMTP; Wed, 17 Apr 2002 15:03:20 +0200
Received: by G8PBR.blf01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <2W57F0AJ>; Wed, 17 Apr 2002 15:04:36 +0200
Message-Id: <C835D57E3730D6119F5000A0C9F019A94A9A4A@U8P13.blf01.telekom.de>
From: "Jesske, R" <R.Jesske@telekom.de>
To: jh@lohi.eng.song.fi
Cc: dean.willis@softarmor.com, sipping@ietf.org
Subject: AW: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 15:04:33 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id JAA07768
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 8bit



> -----Ursprüngliche Nachricht-----
> Von: jh@lohi.eng.song.fi [mailto:jh@lohi.eng.song.fi]
> Gesendet am: Mittwoch, 17. April 2002 10:15
> An: Jesske, Roland
> Cc: dean.willis@softarmor.com; sipping@ietf.org
> Betreff: AW: [Sipping] Screened From: and Privacy
> 
> Jesske, R writes:
> 
>  > That is the problem for the interworking with PSTN, that the phone
>  > include the From header. For the interworking case with 
> the PSTN the
>  > >From header is a not trusted information (because it is 
> direct from
>  > the user and not verified from the network). 
> 
> in my case it IS verified.

How should it be verified when I'm anonymous. Then I need some Information for the regulatory aspect!

> 
>  > But if there is a
>  > network provided indication (from a trusted network)that verifies
>  > that the From is the true user address (like the RPID do this with
>  > the screen = yes), than the Interworking entity can map the
>  > information in a proper way to the PSTN (including the regulatory
>  > aspects are fulfilled). 
> 
> i don't see how rpid would make things any more trusted than the from
> field. if two providers don't trust each other, they would not trust
> the rpid any more than the from field.
> 
>  > There will be no PSTN Operator that take an untrusted From 
> Header to
>  > a calling party number --> instead the PSTN operator will set up a
>  > new calling party number that is network provided and trusted!
> 
> to which number the network would set the calling party 
> number?  my sip
> users can have any number of calling party numbers belonging to any
> number of calling areas and soon even to any number of countries.  

Here I have two possibilities:
1. The user is only SIP user and insert some XYZ@user URL and want to reach the PSTN. The interworking function of the PSTN Gateway will set a network provided E.164 number (003333 for a special SIP Provider where the call come from) into the Calling Party Number. But if the PSTN Provider don't like calls without a E.164@user URL, the provider reject the call.

2. The SIP user has a E.164@user URL then the Gateway maps the URL direct to the Calling Party Number. (e.G. +496151835940@telekom.de to CgPN=6151835940 with the indication national or international). 

> 
> thus the user thus MUST have some means to indicate to me 
> which of those
> numbers that i have allocated to the user, the user wants to 
> use as the
> calling party number in a particular call.  today this information is
> carried in the uri of the from field, which becomes a trusted entity
> after i have checked its validity.  
> 
> it is ok for me to add "screen=yes" parameter to the from 
> field although
> i don't need that information for anything. and if you want 
> to copy the
> from field to another rpid field and have "screen=yes" there, it is ok
> with me too as long as i'm not forced to do that myself.

I see, from the user aspect I don't want to add RPID within the user entity that have to do a trusted entity of the network provider.
If I'm anonymous I need the real identity within an other Header (RPID).The network will inset the real identity into the RPID with screen=yes. The RPID will be mapped to the PSTN as an restricted number, the restricted number is needed for some regulatory aspect (e.g. legal interception). But the normal user sees only the contend of the From header.
> 
> -- juha
> 

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



From daemon@optimus.ietf.org  Wed Apr 17 09:48:34 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17365
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 09:48:33 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA09994
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 09:48:37 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA09585;
	Wed, 17 Apr 2002 09:35:33 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA09557
	for <sipping@optimus.ietf.org>; Wed, 17 Apr 2002 09:35:30 -0400 (EDT)
Received: from btclick.com (mta03.btfusion.com [62.172.195.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17132
	for <sipping@ietf.org>; Wed, 17 Apr 2002 09:35:24 -0400 (EDT)
Received: from ictgateway.ictrnid.org.uk ([217.34.231.189]) by
          btclick.com (Netscape Messaging Server 4.15) with SMTP id
          GUPSE802.V5N for <sipping@ietf.org>; Wed, 17 Apr 2002 14:34:56 +0100 
Received: from 192.168.1.35 ([192.168.1.35]) by ictgateway.ictrnid.org.uk (WinRoute Pro 4.1.29) with SMTP; Wed, 17 Apr 2002 14:45:05 +0100
Message-ID: <002401c1e614$d4db70d0$2301a8c0@LTGUIDO>
From: "Guido Gybels" <guido.gybels@rnid.org.uk>
To: <sipping@ietf.org>
Date: Wed, 17 Apr 2002 14:36:08 +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 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 7bit
Subject: [Sipping] draft-ietf-sipping-deaf-req-01.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Hi all,

The draft on "User requirements for SIP in support of deaf, hard of hearing
and speech-impaired individuals" has been updated and submitted to IETF as
well as to the chair of the SIPPING WG. You can find the new draft on the
Design Team Home Page at www.ictrnid.org.uk/sipping/
It would be helpful if people would have a loo at this updated draft, since
the ambition is to submit it to IESG as soon as possible. Following up on
recent discussion on the mailing list, there have been some minor edits and
correction of spelling mistakes as well as some more substantial changes:
- Added a reference for V18
- Added a new real-world scenario under 7.6 Conference call
- Added suggestions for Service Providers and User Agent Manufacturers about
time synchronisation and conference calls
The Design Team looks, as usual, forward to your comments.

Guido

Guido Gybels, Head of ICT
guido.gybels@rnid.org.uk
Tel. 020-7294 3713
--
The Royal National Institute for Deaf People
Technology Directorate
19-23 Featherstone Street
London EC1Y 8SL - UK





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



From daemon@optimus.ietf.org  Wed Apr 17 10:01:08 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18090
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 10:01:08 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA11351
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 10:01:12 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA10202;
	Wed, 17 Apr 2002 09:50:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA10103
	for <sipping@optimus.ietf.org>; Wed, 17 Apr 2002 09:50:29 -0400 (EDT)
Received: from zctfs063.nortelnetworks.com (zctfs063.nortelnetworks.com [47.164.128.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17362
	for <sipping@ietf.org>; Wed, 17 Apr 2002 09:48:26 -0400 (EDT)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zctfs063.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3HDluB25875;
	Wed, 17 Apr 2002 15:47:57 +0200 (MEST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3HDlHt20641;
	Wed, 17 Apr 2002 14:47:17 +0100 (BST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <HLDBT64L>; Wed, 17 Apr 2002 13:55:35 +0100
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7161@zwcwd00r.europe.nortel.com>
From: "Mark Watson"<mwatson@nortelnetworks.com>
To: "'David R. Oran'" <oran@cisco.com>,
        "'Dean Willis'"
	 <dean.willis@softarmor.com>,
        "'Sipping (E-mail)'" <sipping@ietf.org>
Subject: RE: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 13:53:37 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E60E.E3DC75B2"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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_01C1E60E.E3DC75B2
Content-Type: text/plain

Dave wrote:

> Mark wrote:
> > An incoming call barring service, or other filtering service 
> > based on the origin of the call, is no use whatsoever if it's 
> > based on how the calling user 'wishes to be known', as it 
> > give the caller an easy way to override my service. 
> How did you get there? The screening service can always challege the
> calling user to authenticate. Anything in a callee's call 
> screening list
> is something he put there, and hence can include 
> authentication as well
> as authorization parameters.
> 

Suppose I have a list of people I do NOT want to accept calls from. I'm not
likely to have authentication data for *everyone else in the world*.

> > Service 
> > of this kind can only work if you have some confidence in the 
> > field they are based on. 
> Yup. That's what cryptographic authenication/integrity/authorizationb
> are for. Waving your hands and saying that something 
> (anything!) can be
> relied on because you think it was stuffed in the message by a service
> provider you trust is hoodoo. The need for RPID asises not for these
> mundane reasons, but for the need to cover the very few very tricky
> cases of call trace and anonymous call return and possibly a couple of
> others I can't recall at the moment.
> 

Perhaps I'm missing something, but in the absence of some global PKI I can't
see how authentication helps me as a called party, except for calls from a
limited set of people that I know and have a relationship with.

In the interim (whilst this PKI is set up), we have a 'trusted service
provider' arrangement (as in 3GPP), where the originating service provider
does authentication and verifies that the use is who they say they are in
the From: field.

I was trying to explain why the text in the SIP specification may have led
Service Providers to believe that they ought to verify the From: field. You
are arguing this is a wrong interpretation, but independent of that, I don't
think people who have interpreted the text that way are being unreasonable.

I'm happy to try this agument at 3GPP and see how many people agree with
you. My feeling is that with the specification as it is, and only 2 months
to work with, that the view will remain that these fields need to be
verified if they are used at all.

> > The fact that the SIP specification 
> > implies such services might be based on From: has quite 
> > reasonably led service providers to believe they should 
> > verify this field. You argue that this is a mistake - mayby 
> > so - but that doesn't change the words in the spec. 
> > 
> It's perfectly OK to verify anything in any field if you want. I'm not
> sure this is in fact relevant to the discussion. 
>

It is, because if you 'verify' the field (and refuse service if it is not
'right') you take on responsibility for its value and this has Data
Protection implications.
 
> <snip> 
> > > > These last two points have led Service Providers
> > > > to verify the From: field. They've been encouraged in this by 
> > > > the lack of any other field to communicate (2) passed the 
> > > > device which does authentication. As Dean correctly points 
> > > > out, using From: for information like (2) leads to the need 
> > > > to B2BUA everything for subscriber privacy (if you care about 
> > > > RFC2543 clients). 
> > > How does this follow as long as you define From: as only
> > > user-controlled? 
> > > 
> > The field is NOT 'user-controlled' if the user is forced to 
> > insert a specific piece of information. 
> Sure it is. I can still put anything I want in there. If I don't like
> the fact that the service provider rejects the call I go use somebody
> else. This is like saying the RequestURI: field isn't user controlled,
> because I may have subscribed to a free-phone service that 
> only lets me
> call certain destinations that don't go through a PSTN gateway.
> 

I don't think the discussion makes sense at all if we don't assume that the
user wishes to use the service. (*) With this assumption, if the user is
required by the service to put a particular value in the From: field, then
the service provider absolutely has responsibility for that value being
there with the associated Data Protection responsibility if that value is
Personal Data.

In your free-phone example, the service provider has responsibility for the
fact that the Request-URI is one of a certain set of destinations (and the
user has control of which one). But this is not Personal Data, so there is
nothing complex about this.

If the user can choose one of ten possibilities for the From field, but all
of them identify the user in some way, then although the user has the choice
of which value, they have no choice about whether to include Personal Data.


> > > > I would still argue that a subscriber
> > > > privacy service may need to remove (1) as well, so if the 
> > > > idea is to avoid the requirement to modify/control the From: 
> > > > field, it still might not work. 
> > > I'm afraid we're destined to disagree here. Anything in the 
> > From field
> > > is something the user by definition wants to reveal. 
> > > 
> > But the subscriber may not want it revealed, and the 
> > subscriber's wishes may override the users. 
> > 
> Then the "subscriber" can, in a proxy of B2BUA controlled by him (like
> the proxy in his basement if a residence, or the border proxy of a
> corporate site) do any scrubbing or call rejection he likes. This
> reliance on the PSTN definitions of user and subscriber are really,
> really getting in the way here. I'm not saying that we ignore the
> distinction. Rather, I am saying that, unlike the PSTN world, 
> it is easy
> to trivial to insert an intermediary, controlled by you that you trust
> to verify and screen outgoing calls, incoming calls, or both.
> 

The definitions of subscriber and user are certainly not PSTN ones. It's
common-sense concept applying to any time any business sells a service in
which the person contracting for the service may not be the same as the
person who actually uses it.

If you're not happy with that, the European legislation on electronic
communication defines these concepts, and you'd better believe it's scope is
wider than the PSTN.

Sure the subscriber can deploy a proxy of their own. But the legislation
requires the subscriber to have a 'simple means, free of charge' to request
the privacy service, and the responsibility to provide this is placed on the
Service provider. And where would the subscribe put the proxy for a wireless
terminal using a Wireless WAN ?

> > 
> > > > I can't see a clean way out
> > > > of this. 
> > > Well, RPID may not be perfect, but it does get us out of this.
> > > 
> > Indeed. 
> > > > I don't think it's realistic to assume that From: is
> > > > ALWAYS and ONLY of type (1) - purely end-to-end. 
> > > I think the consequences of any other interpretation are much
> > > worse, but 
> > > that's of course just my considered technical opinion. 
> > > 
> > I think the consequences of the purely end-to-end 
> > interpretation, are that for Service Provider environments, 
> > we essentially invent an 'alternative From' field, and the 
> > From field itself does not get used. I don't have a big 
> > problem with this, but I thought others did.
> I think the problems arise from trying to make this into some
> general-purpose alternate identity scheme where we just re-create all
> the authentication ad authorization problems of the existing 
> end-to-end
> fields except now the problem is middle-to-middle or 
> middle-to-end over
> multiple hops. Something restricted of this sort is needed 
> for malicious
> call trace and aonoymous call return, but my suspicion is 
> that trying to
> over-generalizew is what sends this into la-la-land.
> 

My feeling is that not generalising enough is what is causing half this
problem in the first place. It would be good to have a generic mechanism for
carrying informationm subject to potential Data Protection requirments -
somewhere to 'quarantine' such information - so that future services could
use this container in the knowledge that its Data Protection status will be
recognised even by devices which do not support the new service.

<snip>

> Look, the basic connundrum is how to process calls for which the user
> has declared anonymity while allowing call trace and a few 
> other special
> cases. Can we agree at least one that?
>  

Yes. I think the need for the Network Asserted Identity is a slightly
different debate where we do agree. Do you have any comments on the
requirements I sent out yesterday ?

...Mark

------_=_NextPart_001_01C1E60E.E3DC75B2
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.2655.35">
<TITLE>RE: [Sipping] Screened From: and Privacy</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Dave wrote:</FONT>
</P>

<P><FONT SIZE=3D2>&gt; Mark wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; An incoming call barring service, or other =
filtering service </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; based on the origin of the call, is no use =
whatsoever if it's </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; based on how the calling user 'wishes to =
be known', as it </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; give the caller an easy way to override my =
service. </FONT>
<BR><FONT SIZE=3D2>&gt; How did you get there? The screening service =
can always challege the</FONT>
<BR><FONT SIZE=3D2>&gt; calling user to authenticate. Anything in a =
callee's call </FONT>
<BR><FONT SIZE=3D2>&gt; screening list</FONT>
<BR><FONT SIZE=3D2>&gt; is something he put there, and hence can =
include </FONT>
<BR><FONT SIZE=3D2>&gt; authentication as well</FONT>
<BR><FONT SIZE=3D2>&gt; as authorization parameters.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>Suppose I have a list of people I do NOT want to =
accept calls from. I'm not likely to have authentication data for =
*everyone else in the world*.</FONT></P>

<P><FONT SIZE=3D2>&gt; &gt; Service </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; of this kind can only work if you have =
some confidence in the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; field they are based on. </FONT>
<BR><FONT SIZE=3D2>&gt; Yup. That's what cryptographic =
authenication/integrity/authorizationb</FONT>
<BR><FONT SIZE=3D2>&gt; are for. Waving your hands and saying that =
something </FONT>
<BR><FONT SIZE=3D2>&gt; (anything!) can be</FONT>
<BR><FONT SIZE=3D2>&gt; relied on because you think it was stuffed in =
the message by a service</FONT>
<BR><FONT SIZE=3D2>&gt; provider you trust is hoodoo. The need for RPID =
asises not for these</FONT>
<BR><FONT SIZE=3D2>&gt; mundane reasons, but for the need to cover the =
very few very tricky</FONT>
<BR><FONT SIZE=3D2>&gt; cases of call trace and anonymous call return =
and possibly a couple of</FONT>
<BR><FONT SIZE=3D2>&gt; others I can't recall at the moment.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>Perhaps I'm missing something, but in the absence of =
some global PKI I can't see how authentication helps me as a called =
party, except for calls from a limited set of people that I know and =
have a relationship with.</FONT></P>

<P><FONT SIZE=3D2>In the interim (whilst this PKI is set up), we have a =
'trusted service provider' arrangement (as in 3GPP), where the =
originating service provider does authentication and verifies that the =
use is who they say they are in the From: field.</FONT></P>

<P><FONT SIZE=3D2>I was trying to explain why the text in the SIP =
specification may have led Service Providers to believe that they ought =
to verify the From: field. You are arguing this is a wrong =
interpretation, but independent of that, I don't think people who have =
interpreted the text that way are being unreasonable.</FONT></P>

<P><FONT SIZE=3D2>I'm happy to try this agument at 3GPP and see how =
many people agree with you. My feeling is that with the specification =
as it is, and only 2 months to work with, that the view will remain =
that these fields need to be verified if they are used at =
all.</FONT></P>

<P><FONT SIZE=3D2>&gt; &gt; The fact that the SIP specification </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; implies such services might be based on =
From: has quite </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; reasonably led service providers to =
believe they should </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; verify this field. You argue that this is =
a mistake - mayby </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; so - but that doesn't change the words in =
the spec. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; It's perfectly OK to verify anything in any =
field if you want. I'm not</FONT>
<BR><FONT SIZE=3D2>&gt; sure this is in fact relevant to the =
discussion. </FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
</P>

<P><FONT SIZE=3D2>It is, because if you 'verify' the field (and refuse =
service if it is not 'right') you take on responsibility for its value =
and this has Data Protection implications.</FONT></P>

<P><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>&gt; &lt;snip&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; These last two points have led =
Service Providers</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; to verify the From: field. =
They've been encouraged in this by </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; the lack of any other field to =
communicate (2) passed the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; device which does =
authentication. As Dean correctly points </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; out, using From: for information =
like (2) leads to the need </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; to B2BUA everything for =
subscriber privacy (if you care about </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; RFC2543 clients). </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; How does this follow as long as you =
define From: as only</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; user-controlled? </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; The field is NOT 'user-controlled' if the =
user is forced to </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; insert a specific piece of information. =
</FONT>
<BR><FONT SIZE=3D2>&gt; Sure it is. I can still put anything I want in =
there. If I don't like</FONT>
<BR><FONT SIZE=3D2>&gt; the fact that the service provider rejects the =
call I go use somebody</FONT>
<BR><FONT SIZE=3D2>&gt; else. This is like saying the RequestURI: field =
isn't user controlled,</FONT>
<BR><FONT SIZE=3D2>&gt; because I may have subscribed to a free-phone =
service that </FONT>
<BR><FONT SIZE=3D2>&gt; only lets me</FONT>
<BR><FONT SIZE=3D2>&gt; call certain destinations that don't go through =
a PSTN gateway.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>I don't think the discussion makes sense at all if we =
don't assume that the user wishes to use the service. (*) With this =
assumption, if the user is required by the service to put a particular =
value in the From: field, then the service provider absolutely has =
responsibility for that value being there with the associated Data =
Protection responsibility if that value is Personal Data.</FONT></P>

<P><FONT SIZE=3D2>In your free-phone example, the service provider has =
responsibility for the fact that the Request-URI is one of a certain =
set of destinations (and the user has control of which one). But this =
is not Personal Data, so there is nothing complex about =
this.</FONT></P>

<P><FONT SIZE=3D2>If the user can choose one of ten possibilities for =
the From field, but all of them identify the user in some way, then =
although the user has the choice of which value, they have no choice =
about whether to include Personal Data.</FONT></P>
<BR>

<P><FONT SIZE=3D2>&gt; &gt; &gt; &gt; I would still argue that a =
subscriber</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; privacy service may need to =
remove (1) as well, so if the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; idea is to avoid the requirement =
to modify/control the From: </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; field, it still might not work. =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; I'm afraid we're destined to disagree =
here. Anything in the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; From field</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; is something the user by definition =
wants to reveal. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; But the subscriber may not want it =
revealed, and the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; subscriber's wishes may override the =
users. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Then the &quot;subscriber&quot; can, in a proxy =
of B2BUA controlled by him (like</FONT>
<BR><FONT SIZE=3D2>&gt; the proxy in his basement if a residence, or =
the border proxy of a</FONT>
<BR><FONT SIZE=3D2>&gt; corporate site) do any scrubbing or call =
rejection he likes. This</FONT>
<BR><FONT SIZE=3D2>&gt; reliance on the PSTN definitions of user and =
subscriber are really,</FONT>
<BR><FONT SIZE=3D2>&gt; really getting in the way here. I'm not saying =
that we ignore the</FONT>
<BR><FONT SIZE=3D2>&gt; distinction. Rather, I am saying that, unlike =
the PSTN world, </FONT>
<BR><FONT SIZE=3D2>&gt; it is easy</FONT>
<BR><FONT SIZE=3D2>&gt; to trivial to insert an intermediary, =
controlled by you that you trust</FONT>
<BR><FONT SIZE=3D2>&gt; to verify and screen outgoing calls, incoming =
calls, or both.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>The definitions of subscriber and user are certainly =
not PSTN ones. It's common-sense concept applying to any time any =
business sells a service in which the person contracting for the =
service may not be the same as the person who actually uses =
it.</FONT></P>

<P><FONT SIZE=3D2>If you're not happy with that, the European =
legislation on electronic communication defines these concepts, and =
you'd better believe it's scope is wider than the PSTN.</FONT></P>

<P><FONT SIZE=3D2>Sure the subscriber can deploy a proxy of their own. =
But the legislation requires the subscriber to have a 'simple means, =
free of charge' to request the privacy service, and the responsibility =
to provide this is placed on the Service provider. And where would the =
subscribe put the proxy for a wireless terminal using a Wireless WAN =
?</FONT></P>

<P><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; I can't see a clean way =
out</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; of this. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Well, RPID may not be perfect, but it =
does get us out of this.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Indeed. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; I don't think it's realistic to =
assume that From: is</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; ALWAYS and ONLY of type (1) - =
purely end-to-end. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; I think the consequences of any other =
interpretation are much</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; worse, but </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; that's of course just my considered =
technical opinion. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I think the consequences of the purely =
end-to-end </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; interpretation, are that for Service =
Provider environments, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; we essentially invent an 'alternative =
From' field, and the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; From field itself does not get used. I =
don't have a big </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; problem with this, but I thought others =
did.</FONT>
<BR><FONT SIZE=3D2>&gt; I think the problems arise from trying to make =
this into some</FONT>
<BR><FONT SIZE=3D2>&gt; general-purpose alternate identity scheme where =
we just re-create all</FONT>
<BR><FONT SIZE=3D2>&gt; the authentication ad authorization problems of =
the existing </FONT>
<BR><FONT SIZE=3D2>&gt; end-to-end</FONT>
<BR><FONT SIZE=3D2>&gt; fields except now the problem is =
middle-to-middle or </FONT>
<BR><FONT SIZE=3D2>&gt; middle-to-end over</FONT>
<BR><FONT SIZE=3D2>&gt; multiple hops. Something restricted of this =
sort is needed </FONT>
<BR><FONT SIZE=3D2>&gt; for malicious</FONT>
<BR><FONT SIZE=3D2>&gt; call trace and aonoymous call return, but my =
suspicion is </FONT>
<BR><FONT SIZE=3D2>&gt; that trying to</FONT>
<BR><FONT SIZE=3D2>&gt; over-generalizew is what sends this into =
la-la-land.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>My feeling is that not generalising enough is what is =
causing half this problem in the first place. It would be good to have =
a generic mechanism for carrying informationm subject to potential Data =
Protection requirments - somewhere to 'quarantine' such information - =
so that future services could use this container in the knowledge that =
its Data Protection status will be recognised even by devices which do =
not support the new service.</FONT></P>

<P><FONT SIZE=3D2>&lt;snip&gt;</FONT>
</P>

<P><FONT SIZE=3D2>&gt; Look, the basic connundrum is how to process =
calls for which the user</FONT>
<BR><FONT SIZE=3D2>&gt; has declared anonymity while allowing call =
trace and a few </FONT>
<BR><FONT SIZE=3D2>&gt; other special</FONT>
<BR><FONT SIZE=3D2>&gt; cases. Can we agree at least one that?</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; </FONT>
</P>

<P><FONT SIZE=3D2>Yes. I think the need for the Network Asserted =
Identity is a slightly different debate where we do agree. Do you have =
any comments on the requirements I sent out yesterday ?</FONT></P>

<P><FONT SIZE=3D2>...Mark</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E60E.E3DC75B2--

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



From daemon@optimus.ietf.org  Wed Apr 17 10:35:30 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20649
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 10:35:30 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA14260
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 10:35:34 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA13246;
	Wed, 17 Apr 2002 10:25:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA13214
	for <sipping@optimus.ietf.org>; Wed, 17 Apr 2002 10:25:26 -0400 (EDT)
Received: from mail1.telekom.de (mail1.telekom.de [62.225.183.235])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19968
	for <sipping@ietf.org>; Wed, 17 Apr 2002 10:25:21 -0400 (EDT)
Received: from g9jbr.mgb01.telekom.de by G8SBV.dmz.telekom.de with ESMTP; Wed, 17 Apr 2002 16:23:37 +0200
Received: by G9JBR.mgb01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <2Q8XDHM5>; Wed, 17 Apr 2002 16:24:53 +0200
Message-Id: <A89A213731F7D51196A0000347055C83E391D4@G9JNT.mgb01.telekom.de>
From: "Alexeitsev, D" <D.Alexeitsev@telekom.de>
To: james.yu@neustar.biz
Cc: sipping@ietf.org
Subject: AW: [Sipping] draft-yu-tel-url-04.txt comment
Date: Wed, 17 Apr 2002 16:24:53 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Hello,

Some comments inline:

> Those parameters (rn, npdi and cic) are defined as the extensions to the tel
> URL.  There were discussions on supporting tel URL a while back.  I believe
> that bis has included texts that clarifies how parameters in the tel URL
> (plus its extensions) are supported in the sip URL.

Christer has pointed out, that the use of any parameters in the user-part may mess up the implementation.
Is there something in the bis doc, that says its not a problem? 

>  We are not discussing how those tel URL extensions can be carried as the url-parameters, that is
> implementation issue, as you have indicated.

Would not you want to describe this possibility in the draft?

> We are discussing how tel URL parameters (including extensions) are carried in the sip URL in a "standard"
> way.  The consensus is that they'll appear in the user part of the sip URL when user=phone is present.

What are the main concerns about transferring this extensions as SIP url-parameters?



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



From daemon@optimus.ietf.org  Wed Apr 17 11:22:59 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22803
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 11:22:54 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA27581
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 11:22:58 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA19058;
	Wed, 17 Apr 2002 11:05:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA19015
	for <sipping@optimus.ietf.org>; Wed, 17 Apr 2002 11:05:01 -0400 (EDT)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22028
	for <sipping@ietf.org>; Wed, 17 Apr 2002 11:04:53 -0400 (EDT)
Received: from mira-sjc5-9.cisco.com (IDENT:mirapoint@mira-sjc5-9.cisco.com [171.71.163.32])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g3HF41No007772;
	Wed, 17 Apr 2002 08:04:01 -0700 (PDT)
Received: from OranLT ([64.101.157.153])
	by mira-sjc5-9.cisco.com (Mirapoint)
	with ESMTP id ACQ83545;
	Wed, 17 Apr 2002 08:04:29 -0700 (PDT)
From: "David R. Oran" <oran@cisco.com>
To: "'Mark Watson'" <mwatson@nortelnetworks.com>,
        "'Dean Willis'" <dean.willis@softarmor.com>,
        "'Sipping \(E-mail\)'" <sipping@ietf.org>
Subject: RE: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 10:56:21 -0400
Organization: Cisco Systems
Message-ID: <003001c1e620$09ad7870$999d6540@OranLT>
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.3416
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <A3C2399B2FACD411A54200508BE39C74054F7161@zwcwd00r.europe.nortel.com>
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: Mark Watson [mailto:mwatson@nortelnetworks.com] 
> Sent: Wednesday, April 17, 2002 8:54 AM
> To: 'David R. Oran'; 'Dean Willis'; 'Sipping (E-mail)'
> Subject: RE: [Sipping] Screened From: and Privacy
> 
> 
> Dave wrote: 
> > Mark wrote:
> > > An incoming call barring service, or other filtering service
> > > based on the origin of the call, is no use whatsoever if it's 
> > > based on how the calling user 'wishes to be known', as it 
> > > give the caller an easy way to override my service. 
> > How did you get there? The screening service can always challenge
the
> > calling user to authenticate. Anything in a callee's call 
> > screening list 
> > is something he put there, and hence can include 
> > authentication as well 
> > as authorization parameters. 
> > 
> Suppose I have a list of people I do NOT want to accept calls 
> from. I'm not likely to have authentication data for 
> *everyone else in the world*.

That one's even easier since you don't need to authenticate a blocking
list. Anybody who masquerades as someone you block will get blocked.
They just screwed themselves.

> > > Service
> > > of this kind can only work if you have some confidence in the 
> > > field they are based on. 
> > Yup. That's what cryptographic 
> authenication/integrity/authorization
> > are for. Waving your hands and saying that something 
> > (anything!) can be 
> > relied on because you think it was stuffed in the message 
> by a service 
> > provider you trust is hoodoo. The need for RPID arises not 
> for these 
> > mundane reasons, but for the need to cover the very few very tricky 
> > cases of call trace and anonymous call return and possibly 
> a couple of 
> > others I can't recall at the moment. 
> > 
> Perhaps I'm missing something, but in the absence of some 
> global PKI I can't see how authentication helps me as a 
> called party, except for calls from a limited set of people 
> that I know and have a relationship with. 
Right. Is it any different to accept a call from "Bugs Bunny" when it's
actually Bugs or Osama Bin Laden?

> In the interim 
> (whilst this PKI is set up), we have a 'trusted service 
> provider' arrangement (as in 3GPP), where the originating 
> service provider does authentication and verifies that the 
> use is who they say they are in the From: field. 
That doesn't help at all unless I trust the calling user's service
provider. What good does it do me that "George Bush" using the Chaos
Computer Club service provider? In the PSTN doing this requires global
transitive trust, which is unrealistic for the Internet and SIP in
general. 

> I was trying 
> to explain why the text in the SIP specification may have led 
> Service Providers to believe that they ought to verify the 
> From: field. You are arguing this is a wrong interpretation, 
> but independent of that, I don't think people who have 
> interpreted the text that way are being unreasonable. I'm 
> happy to try this argument at 3GPP and see how many people 
> agree with you. My feeling is that with the specification as 
> it is, and only 2 months to work with, that the view will 
> remain that these fields need to be verified if they are used at all.
And I have no problem with somebody wanting to verify them if that's
what they want to do. It just doesn't have anything to do with SIP the
protocol.

> > > The fact that the SIP specification
> > > implies such services might be based on From: has quite 
> > > reasonably led service providers to believe they should 
> > > verify this field. You argue that this is a mistake - maybe 
> > > so - but that doesn't change the words in the spec. 
> > > 
> > It's perfectly OK to verify anything in any field if you 
> want. I'm not
> > sure this is in fact relevant to the discussion. 
> > 
> It is, because if you 'verify' the field (and refuse service 
> if it is not 'right') you take on responsibility for its 
> value and this has Data Protection implications.
>  
This logical leap does not seem to be justified. It is much better IMHO
to not depend on this implication. What in the regs leads you to believe
this is required? If I do RPF verification on the source IP address of a
packet, does that mean I take responsibility to not reveal the address
or the subscriber who is using that address? This is a very slippery
slope!

> > <snip>
> > > > > These last two points have led Service Providers
> > > > > to verify the From: field. They've been encouraged in this by 
> > > > > the lack of any other field to communicate (2) passed the 
> > > > > device which does authentication. As Dean correctly points 
> > > > > out, using From: for information like (2) leads to the need 
> > > > > to B2BUA everything for subscriber privacy (if you care about 
> > > > > RFC2543 clients). 
> > > > How does this follow as long as you define From: as only
> > > > user-controlled? 
> > > > 
> > > The field is NOT 'user-controlled' if the user is forced to
> > > insert a specific piece of information. 
> > Sure it is. I can still put anything I want in there. If I 
> don't like
> > the fact that the service provider rejects the call I go 
> use somebody 
> > else. This is like saying the RequestURI: field isn't user 
> controlled, 
> > because I may have subscribed to a free-phone service that 
> > only lets me 
> > call certain destinations that don't go through a PSTN gateway. 
> > 
> I don't think the discussion makes sense at all if we don't 
> assume that the user wishes to use the service. (*) With this 
> assumption, if the user is required by the service to put a 
> particular value in the From: field, then the service 
> provider absolutely has responsibility for that value being 
> there with the associated Data Protection responsibility if 
> that value is Personal Data. 
Sort of, but I'll grant the point. In this case the service provider
chose this technique and has to live with it. That means doing B2BUA
stuff to anonymize. 

> In your free-phone example, the 
> service provider has responsibility for the fact that the 
> Request-URI is one of a certain set of destinations (and the 
> user has control of which one). But this is not Personal 
> Data, so there is nothing complex about this. If the user can 
> choose one of ten possibilities for the From field, but all 
> of them identify the user in some way, 
> then although the user 
> has the choice of which value, they have no choice about 
> whether to include Personal Data.
> 
Why is this of necessity true? I could, for example, do a subscription
with a service provider which consists of the generator for a one time
pad with full forward security, and the From field is generated based on
running the one-time pad. Then every call has a different From: field,
the From: is completely verifiable based on the one-time pad, and it
reveals absolutely nothing about the user to any third party.

> 
> > > > > I would still argue that a subscriber
> > > > > privacy service may need to remove (1) as well, so if the 
> > > > > idea is to avoid the requirement to modify/control the From: 
> > > > > field, it still might not work. 
> > > > I'm afraid we're destined to disagree here. Anything in the
> > > From field
> > > > is something the user by definition wants to reveal.
> > > > 
> > > But the subscriber may not want it revealed, and the
> > > subscriber's wishes may override the users. 
> > > 
> > Then the "subscriber" can, in a proxy of B2BUA controlled 
> by him (like
> > the proxy in his basement if a residence, or the border proxy of a 
> > corporate site) do any scrubbing or call rejection he likes. This 
> > reliance on the PSTN definitions of user and subscriber are really, 
> > really getting in the way here. I'm not saying that we ignore the 
> > distinction. Rather, I am saying that, unlike the PSTN world, 
> > it is easy 
> > to trivial to insert an intermediary, controlled by you 
> that you trust 
> > to verify and screen outgoing calls, incoming calls, or both. 
> > 
> The definitions of subscriber and user are certainly not PSTN 
> ones. It's common-sense concept applying to any time any 
> business sells a service in which the person contracting for 
> the service may not be the same as the person who actually 
> uses it. If you're not happy with that, the European 
> legislation on electronic communication defines these 
> concepts, and you'd better believe it's scope is wider than 
> the PSTN. 
Sure, but how does this change my argument? Either all calls are treated
as though they come from the "subscriber" (i.e. the service provider
cannot distinguish or otherwise vouch for the various users) or the
subscriber provides the discrimination themselves. This is an
unavoidable consequence of the endpoints being on one side of a trust
boundary and the serves being on the other.

Sure the subscriber can deploy a proxy of their 
> own. But the legislation requires the subscriber to have a 
> 'simple means, free of charge' to request the privacy 
> service, and the responsibility to provide this is placed on 
> the Service provider. And where would the subscribe put the 
> proxy for a wireless terminal using a Wireless WAN ?
Anywhere they want. This is IP.

> > > 
> > > > > I can't see a clean way out
> > > > > of this. 
> > > > Well, RPID may not be perfect, but it does get us out of this.
> > > > 
> > > Indeed.
> > > > > I don't think it's realistic to assume that From: is
> > > > > ALWAYS and ONLY of type (1) - purely end-to-end. 
> > > > I think the consequences of any other interpretation are much
> > > > worse, but 
> > > > that's of course just my considered technical opinion. 
> > > > 
> > > I think the consequences of the purely end-to-end
> > > interpretation, are that for Service Provider environments, 
> > > we essentially invent an 'alternative From' field, and the 
> > > From field itself does not get used. I don't have a big 
> > > problem with this, but I thought others did. 
> > I think the problems arise from trying to make this into some
> > general-purpose alternate identity scheme where we just 
> re-create all 
> > the authentication ad authorization problems of the existing 
> > end-to-end 
> > fields except now the problem is middle-to-middle or 
> > middle-to-end over 
> > multiple hops. Something restricted of this sort is needed 
> > for malicious 
> > call trace and anonymous call return, but my suspicion is 
> > that trying to 
> > over-generalize is what sends this into la-la-land. 
> > 
> My feeling is that not generalizing enough is what is causing 
> half this problem in the first place. It would be good to 
> have a generic mechanism for carrying information subject to 
> potential Data Protection requirements - somewhere to 
> 'quarantine' such information - so that future services could 
> use this container in the knowledge that its Data Protection 
> status will be recognised even by devices which do not 
> support the new service. <snip> 
I respectfully disagree. I think this approach is an infinite sinkhole.
The cases that need separate identities asserted by the provider are few
and highly specific, tricky, and not IMHO of general utility beyond
their specific functions.

> > Look, the basic conundrum is how to process calls for 
> which the user
> > has declared anonymity while allowing call trace and a few 
> > other special 
> > cases. Can we agree at least one that? 
> >  
> Yes. I think the need for the Network Asserted Identity is a 
> slightly different debate where we do agree. Do you have any 
> comments on the requirements I sent out yesterday ? ...Mark 
> 
I think I sent something out already, but I'll check.


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



From daemon@optimus.ietf.org  Wed Apr 17 12:12:10 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24873
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 12:12:10 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA23580
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 12:12:10 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA09436;
	Wed, 17 Apr 2002 11:55:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA09374
	for <sipping@optimus.ietf.org>; Wed, 17 Apr 2002 11:55:49 -0400 (EDT)
Received: from bdsl.66.12.12.130.gte.net (bdsl.66.12.12.130.gte.net [66.12.12.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24175
	for <sipping@ietf.org>; Wed, 17 Apr 2002 11:55:45 -0400 (EDT)
Received: from C1893415A (bdsl.greycouncil.com [127.0.0.1])
	by bdsl.66.12.12.130.gte.net (8.11.6/8.11.6) with SMTP id g3HFsid01183;
	Wed, 17 Apr 2002 10:54:44 -0500
Message-ID: <014a01c1e628$31c551e0$133fed0c@C1893415A>
From: "Dean Willis" <dean.willis@softarmor.com>
To: <hisham.khartabil@nokia.com>, <jh@lohi.eng.song.fi>
Cc: <sipping@ietf.org>
References: <2038BCC78B1AD641891A0D1AE133DBB777913A@esebe019.NOE.Nokia.com>
Subject: Re: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 10:54:44 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Hisham said:
> Dean said:
> > Exactly. But they're going to defin their own Subject field and
other
> > user (not SUBSCRIBER) data. I'm arguing that the display name field
> > (From:) falls into this category.
>
>
> Does that include Home Proxy? If you want to use my SIP phone and you
don't have an account with my service provider, you have to reconfigure
my phone with your service provider home proxy. I prefer for you to just
use my phone and not change the configuration.

Think of this as like using a browser-based email client. Users key in
their subject and from fields, but they aren't likely to  (and generally
can't)  change the SMTP gateway used.

I wish people would top expecting phones to have a 10-key pad and a bad
user interface. This will change, and we should not cripple our designs
based on the assumption that it will never change.

--
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 daemon@optimus.ietf.org  Wed Apr 17 12:31:45 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25741
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 12:31:44 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA27662
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 12:31:46 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA22291;
	Wed, 17 Apr 2002 12:09:48 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA22239
	for <sipping@optimus.ietf.org>; Wed, 17 Apr 2002 12:09:43 -0400 (EDT)
Received: from bdsl.66.12.12.130.gte.net (bdsl.66.12.12.130.gte.net [66.12.12.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24792
	for <sipping@ietf.org>; Wed, 17 Apr 2002 12:09:39 -0400 (EDT)
Received: from C1893415A (bdsl.greycouncil.com [127.0.0.1])
	by bdsl.66.12.12.130.gte.net (8.11.6/8.11.6) with SMTP id g3HG9Cd01283
	for <sipping@ietf.org>; Wed, 17 Apr 2002 11:09:12 -0500
Message-ID: <015101c1e62a$3770d180$133fed0c@C1893415A>
From: "Dean Willis" <dean.willis@softarmor.com>
To: "'Sipping \(E-mail\)'" <sipping@ietf.org>
References: <A3C2399B2FACD411A54200508BE39C74054F7158@zwcwd00r.europe.nortel.com>
Subject: Re: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 11:09:13 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

RE: [Sipping] Screened From: and Privacy
Mark says:
---------------
An incoming call barring service, or other filtering service based on
the origin of the call, is no use whatsoever if it's based on how the
calling user 'wishes to be known', as it give the caller an easy way to
override my service.
Service of this kind can only work if you have some confidence in the
field they are based on. The fact that the SIP specification implies
such services might be based on From: has quite reasonably led service
providers to believe they should verify this field.
You argue that this is a mistake - mayby so - but that doesn't change
the words in the spec.
---------------

Funny, the From and To fields on your email were "user provided" and my
procmail filter managed to put them in the right place.

There's a fundamental dualism that everybody seems to be missing:

There are user-asserted and network-asserted aspects of alomst
everything, including privacy and identity. Although similar, the
network-asserted thing is NOT exactly the same as the user-asserted
thing. Therefore, I can quite reasonably define services which treat
them differently.

For example, I might have a call filtering service that accepts calls
from phones identified by the network as pay-phones where the
user-provided identity is "George W. Bush", just in case the President
calls me from a pay phone. There's no assurance it will REALLY be him,
but it MIGHT be, so I'm willing to take the call . . .


-----------
Somebody wrote:
> > These last two points have led Service Providers
> > to verify the From: field. They've been encouraged in this by
> > the lack of any other field to communicate (2) passed the
> > device which does authentication. As Dean correctly points
> > out, using From: for information like (2) leads to the need
> > to B2BUA everything for subscriber privacy (if you care about
> > RFC2543 clients).
> How does this follow as long as you define From: as only
> user-controlled?
>
Mark wrote:
The field is NOT 'user-controlled' if the user is forced to insert a
specific piece of information.
-----------

SO STOP REQUIRING THEM TO ENTER SOMETHING SPECIFIC!


----------
Somebody wrote:
> > I would still argue that a subscriber
> > privacy service may need to remove (1) as well, so if the
> > idea is to avoid the requirement to modify/control the From:
> > field, it still might not work.
> I'm afraid we're destined to disagree here. Anything in the From field
> is something the user by definition wants to reveal.
>
Mark wrote:
But the subscriber may not want it revealed, and the subscriber's wishes
may override the users.
-----------

Fine! The subscriber controls the service routing. This may route the
call through an anonymizer service, which terminates the dialog and
creates a new "safe" dialog. This still leaves the From: field  as "end
to end" as far as SIP is concerned -- the network delivers the
user-entered From: to the far end of the dialog, exactly as required by
the specification.


---------------------
somebody wrote:
> > I can't see a clean way out
> > of this.
> Well, RPID may not be perfect, but it does get us out of this.
>
Indeed.
> > I don't think it's realistic to assume that From: is
> > ALWAYS and ONLY of type (1) - purely end-to-end.
> I think the consequences of any other interpretation are much
> worse, but
> that's of course just my considered technical opinion.
>
Mark wrote:
I think the consequences of the purely end-to-end interpretation, are
that for Service Provider environments, we essentially invent an
'alternative From' field, and the From field itself does not get used. I
don't have a big problem with this, but I thought others did.
---------------------
In the absence of subscriber or regulatory policy forcing the use of an
anoynizer service, the user's From field gets delivered to the
terminating user. No problem. I have a BIG problem if you want to try to
sell me a service that NEVER delivers my From fields . . .


------------------
somebody wrote
> > Sure, some
> > systems may treat it this way, and there is no harm in that,
> > but it seems to me too late to make this statement now.
> Why? What have we done in any SIP spec which causes a problem? (as
> opposed to what some implementers and other standards groups
> have done).
> What is irreversible here?
>
Mark wrote:
As noted above, the SIP specification does seem to imply that there is
some advantage to be gained by checking the From field is valid, as it
is used for terminating end services other than display.
------------------

Yes! It is useful BECAUSE it is user-provided information, not
controlled by the caprice of  the network, and MAY contain additional
useful infromation. But by no means is it the ONLY pirce of useful
information, and, in the absence of an authentication mechanism, can be
treated only as a hint as to how the message should be processed.


---------------------
Somebody wrote:
>
> > Service Providers exist which put it into class (2). They may
> > need to modify it.
> Existence proof, please, aside from the obvious case of a B2BUA which
> can munge ANYTHING and still comply with the SIP spec.
>
Mark wrote:
Juha described how his service verified the From field. It is unlikely
that 3GPP would be pursuaded to do otherwise if they are pursuaded to
use the From field at all. I described in some detail on the SIP list
thread why this may imply a Data Protetcion requirement to modift the
field. I don't dispute that this may require a B2BUA.
-----------------------

Juha's service works the way it does because nobody gave him a better
alternative. Like many early implementations, it's a hack. A necessary
hack, but a hack. I suggest not perpetuating it.


--
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 daemon@optimus.ietf.org  Wed Apr 17 12:36:42 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25928
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 12:36:42 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA28277
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 12:36:44 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA25130;
	Wed, 17 Apr 2002 12:15:22 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA25082
	for <sipping@optimus.ietf.org>; Wed, 17 Apr 2002 12:15:18 -0400 (EDT)
Received: from dgesmtp01.wcom.com (dgesmtp01.wcom.com [199.249.16.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25057
	for <sipping@ietf.org>; Wed, 17 Apr 2002 12:15:14 -0400 (EDT)
Received: from CONVERSION-DAEMON by firewall.wcom.com (PMDF V5.2-33 #42260)
 id <0GUP00601ZSD97@firewall.wcom.com> for sipping@ietf.org; Wed,
 17 Apr 2002 16:14:37 +0000 (GMT)
Received: from pmismtp05.wcomnet.com ([166.38.62.53])
 by firewall.wcom.com (PMDF V5.2-33 #42260)
 with ESMTP id <0GUP0053TZSDUL@firewall.wcom.com>; Wed,
 17 Apr 2002 16:14:37 +0000 (GMT)
Received: from pmismtp05.wcomnet.com by pmismtp05.wcomnet.com
 (iPlanet Messaging Server 5.1 (built May  7 2001))
 with SMTP id <0GUP00K01ZS68E@pmismtp05.wcomnet.com>; Wed,
 17 Apr 2002 16:14:30 +0000 (GMT)
Received: from ajohnston ([166.42.33.143])
 by pmismtp05.wcomnet.com (iPlanet Messaging Server 5.1 (built May  7 2001))
 with ESMTP id <0GUP009VMZS4I7@pmismtp05.wcomnet.com>; Wed,
 17 Apr 2002 16:14:30 +0000 (GMT)
Date: Wed, 17 Apr 2002 11:14:10 -0500
From: Alan Johnston <alan.johnston@wcom.com>
Subject: RE: [Sipping] Screened From: and Privacy
In-reply-to: 
 <A3C2399B2FACD411A54200508BE39C74054F7161@zwcwd00r.europe.nortel.com>
To: "'Mark Watson'" <mwatson@nortelnetworks.com>,
        "'David R. Oran'" <oran@cisco.com>,
        "'Dean Willis'" <dean.willis@softarmor.com>,
        "'Sipping (E-mail)'" <sipping@ietf.org>
Message-id: <008a01c1e62a$e97972b0$23202aa6@ajohnston>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit


Mark wrote:

>I was trying to explain why the text in the SIP specification may have
led Service
>Providers to believe that they ought to verify the From: field. You are
arguing this is
>a wrong interpretation, but independent of that, I don't think people
who have
>interpreted the text that way are being unreasonable.

I must have missed the 4xx From Header Incorrect response code which
must be somewhere in bis for this verification of From identity to work
:-)

I think this interpretation is totally unreasonable and should be
dispelled right now for what it is - a mistake.

Service providers must read Internet specifications very carefully - the
Internet and its protocols were not designed for them (fortunately).

Thanks,
Alan Johnston
WorldCom
sip:alan@siptest.wcom.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 daemon@optimus.ietf.org  Wed Apr 17 12:52:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26685
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 12:52:28 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA29280
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 12:52:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA28637;
	Wed, 17 Apr 2002 12:40:40 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA28420
	for <sipping@optimus.ietf.org>; Wed, 17 Apr 2002 12:40:28 -0400 (EDT)
Received: from zctfs063.nortelnetworks.com (zctfs063.nortelnetworks.com [47.164.128.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23709
	for <sipping@ietf.org>; Wed, 17 Apr 2002 11:42:06 -0400 (EDT)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by zctfs063.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3HFetB22454;
	Wed, 17 Apr 2002 17:40:55 +0200 (MEST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JDW4M8ZZ>; Wed, 17 Apr 2002 16:40:54 +0100
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F716C@zwcwd00r.europe.nortel.com>
From: "Mark Watson"<mwatson@nortelnetworks.com>
To: "'David R. Oran'" <oran@cisco.com>,
        "'Dean Willis'"
	 <dean.willis@softarmor.com>,
        "'Sipping (E-mail)'" <sipping@ietf.org>
Subject: RE: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 16:40:41 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E626.3AA8921A"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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_01C1E626.3AA8921A
Content-Type: text/plain

Anyone still left apart from me & Dave :-)

> 
> That one's even easier since you don't need to authenticate a blocking
> list. Anybody who masquerades as someone you block will get blocked.
> They just screwed themselves.
> 

I'm worried about the person I have blocked masquerading as someone else,
and so circumventing the blocking.

> > Perhaps I'm missing something, but in the absence of some 
> > global PKI I can't see how authentication helps me as a 
> > called party, except for calls from a limited set of people 
> > that I know and have a relationship with. 
> Right. Is it any different to accept a call from "Bugs Bunny" 
> when it's
> actually Bugs or Osama Bin Laden?
> 

No, but after he has called twenty times, I want to add him to my blocking
list. But then he just calls as "Donald Duck" and I am no better off. I
agree there's nothing I can do about this if the calls are coming from the
an untrusted source and I am stupid enough to accept them at all.

But if the calls were made through a service provider who could authenticate
the caller, I would thank them for not allowing their subscribers to
masquerade as cartoon characters.

> > In the interim 
> > (whilst this PKI is set up), we have a 'trusted service 
> > provider' arrangement (as in 3GPP), where the originating 
> > service provider does authentication and verifies that the 
> > use is who they say they are in the From: field. 
> That doesn't help at all unless I trust the calling user's service
> provider. What good does it do me that "George Bush" using the Chaos
> Computer Club service provider? In the PSTN doing this requires global
> transitive trust, which is unrealistic for the Internet and SIP in
> general. 
>

But this is what we will have in 3GPP. There are other reasons why
inter-operator agreements are needed which are much more important than this
discussion.
 
<snip>
> And I have no problem with somebody wanting to verify them if that's
> what they want to do. It just doesn't have anything to do with SIP the
> protocol.
> 

It does when people are arguing that there is never a requirement to modify
the information in these fields.

<snip>
> > > It's perfectly OK to verify anything in any field if you 
> > want. I'm not
> > > sure this is in fact relevant to the discussion. 
> > > 
> > It is, because if you 'verify' the field (and refuse service 
> > if it is not 'right') you take on responsibility for its 
> > value and this has Data Protection implications.
> >  
> This logical leap does not seem to be justified. It is much 
> better IMHO
> to not depend on this implication. What in the regs leads you 
> to believe
> this is required? If I do RPF verification on the source IP 
> address of a
> packet, does that mean I take responsibility to not reveal the address
> or the subscriber who is using that address? This is a very slippery
> slope!
> 

There is no legislation that I know of which requires Internet Service
Providers to provide an anoymous packet delivery service - i.e. delivering a
packet without revealing the source address.

There is legislation which requires providers of Publically Available
Telecommunications Services to allow their users to make anonymous calls,
and to allow subscriber to require that all calls from that subscription be
anonymous.

I could speculate about why there is this difference between services, but
that is not the point.

If the slope is slippery, it's not me what put oil on it. I am just trying
to explain the situation and ensure that we do not ignore potentially
important requirements. The price for ignoring this stuff is that *more*
regulation gets thrust down your throat - this slope is more slippery still.

> > > <snip>
> > > > > > These last two points have led Service Providers
> > > > > > to verify the From: field. They've been encouraged 
> in this by 
> > > > > > the lack of any other field to communicate (2) passed the 
> > > > > > device which does authentication. As Dean correctly points 
> > > > > > out, using From: for information like (2) leads to the need 
> > > > > > to B2BUA everything for subscriber privacy (if you 
> care about 
> > > > > > RFC2543 clients). 
> > > > > How does this follow as long as you define From: as only
> > > > > user-controlled? 
> > > > > 
> > > > The field is NOT 'user-controlled' if the user is forced to
> > > > insert a specific piece of information. 
> > > Sure it is. I can still put anything I want in there. If I 
> > don't like
> > > the fact that the service provider rejects the call I go 
> > use somebody 
> > > else. This is like saying the RequestURI: field isn't user 
> > controlled, 
> > > because I may have subscribed to a free-phone service that 
> > > only lets me 
> > > call certain destinations that don't go through a PSTN gateway. 
> > > 
> > I don't think the discussion makes sense at all if we don't 
> > assume that the user wishes to use the service. (*) With this 
> > assumption, if the user is required by the service to put a 
> > particular value in the From: field, then the service 
> > provider absolutely has responsibility for that value being 
> > there with the associated Data Protection responsibility if 
> > that value is Personal Data. 
> Sort of, but I'll grant the point. In this case the service provider
> chose this technique and has to live with it. That means doing B2BUA
> stuff to anonymize. 
> 

Sure.

> > In your free-phone example, the 
> > service provider has responsibility for the fact that the 
> > Request-URI is one of a certain set of destinations (and the 
> > user has control of which one). But this is not Personal 
> > Data, so there is nothing complex about this. If the user can 
> > choose one of ten possibilities for the From field, but all 
> > of them identify the user in some way, 
> > then although the user 
> > has the choice of which value, they have no choice about 
> > whether to include Personal Data.
> > 
> Why is this of necessity true? I could, for example, do a subscription
> with a service provider which consists of the generator for a one time
> pad with full forward security, and the From field is 
> generated based on
> running the one-time pad. Then every call has a different From: field,
> the From: is completely verifiable based on the one-time pad, and it
> reveals absolutely nothing about the user to any third party.
> 

My argument only applies if the possible values of the From field *do*
contain information which would be meaningful to a third party.

The purpose of any verification is to ensure that the user is not
mis-leading the called party, not to authenticate the user, so if the
information is meaningless to the called user, there is no point in
verifying it at all.

> > 
> > > > > > I would still argue that a subscriber
> > > > > > privacy service may need to remove (1) as well, so if the 
> > > > > > idea is to avoid the requirement to modify/control 
> the From: 
> > > > > > field, it still might not work. 
> > > > > I'm afraid we're destined to disagree here. Anything in the
> > > > From field
> > > > > is something the user by definition wants to reveal.
> > > > > 
> > > > But the subscriber may not want it revealed, and the
> > > > subscriber's wishes may override the users. 
> > > > 
> > > Then the "subscriber" can, in a proxy of B2BUA controlled 
> > by him (like
> > > the proxy in his basement if a residence, or the border 
> proxy of a 
> > > corporate site) do any scrubbing or call rejection he likes. This 
> > > reliance on the PSTN definitions of user and subscriber 
> are really, 
> > > really getting in the way here. I'm not saying that we ignore the 
> > > distinction. Rather, I am saying that, unlike the PSTN world, 
> > > it is easy 
> > > to trivial to insert an intermediary, controlled by you 
> > that you trust 
> > > to verify and screen outgoing calls, incoming calls, or both. 
> > > 
> > The definitions of subscriber and user are certainly not PSTN 
> > ones. It's common-sense concept applying to any time any 
> > business sells a service in which the person contracting for 
> > the service may not be the same as the person who actually 
> > uses it. If you're not happy with that, the European 
> > legislation on electronic communication defines these 
> > concepts, and you'd better believe it's scope is wider than 
> > the PSTN. 
> Sure, but how does this change my argument? Either all calls 
> are treated
> as though they come from the "subscriber" (i.e. the service provider
> cannot distinguish or otherwise vouch for the various users) or the
> subscriber provides the discrimination themselves. This is an
> unavoidable consequence of the endpoints being on one side of a trust
> boundary and the serves being on the other.
> 

I don't follow this. The subscriber *could* provide their own proxy, but if
the Service Provider accepts that multiple users might make calls under the
same subscription (in the legal sense), they cannot later require the
subscriber to install their own proxy when the subscriber decides to ask for
anonymity services.

The Service Provider could fulfil their obligations by *requiring* that all
subscribers first install such a proxy, before accepting them for service,
but this does not sound like a good business proposition.

> Sure the subscriber can deploy a proxy of their 
> > own. But the legislation requires the subscriber to have a 
> > 'simple means, free of charge' to request the privacy 
> > service, and the responsibility to provide this is placed on 
> > the Service provider. And where would the subscribe put the 
> > proxy for a wireless terminal using a Wireless WAN ?
> Anywhere they want. This is IP.
>
OK, I'm thinking 3GPP. 

<snip>

> > My feeling is that not generalizing enough is what is causing 
> > half this problem in the first place. It would be good to 
> > have a generic mechanism for carrying information subject to 
> > potential Data Protection requirements - somewhere to 
> > 'quarantine' such information - so that future services could 
> > use this container in the knowledge that its Data Protection 
> > status will be recognised even by devices which do not 
> > support the new service. <snip> 
> I respectfully disagree. I think this approach is an infinite 
> sinkhole.
> The cases that need separate identities asserted by the 
> provider are few
> and highly specific, tricky, and not IMHO of general utility beyond
> their specific functions.
> 

I guess my experience from PSTN/ISDN CLI discussions is that there were
vastly more applications for Calling Line Identity than anyone ever
envisaged when they defined the single Calling Party Number field, or even
the Additional Calling Party Number field.

Trying to key services with different requirements off a single field often
resulted in mutually incompatible requirements on which identity should be
in the field, resulting in poorer service to the user.

...Mark 

------_=_NextPart_001_01C1E626.3AA8921A
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.2655.35">
<TITLE>RE: [Sipping] Screened From: and Privacy</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Anyone still left apart from me &amp; Dave :-)</FONT>
</P>

<P><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; That one's even easier since you don't need to =
authenticate a blocking</FONT>
<BR><FONT SIZE=3D2>&gt; list. Anybody who masquerades as someone you =
block will get blocked.</FONT>
<BR><FONT SIZE=3D2>&gt; They just screwed themselves.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>I'm worried about the person I have blocked =
masquerading as someone else, and so circumventing the blocking.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; &gt; Perhaps I'm missing something, but in the =
absence of some </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; global PKI I can't see how authentication =
helps me as a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; called party, except for calls from a =
limited set of people </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; that I know and have a relationship with. =
</FONT>
<BR><FONT SIZE=3D2>&gt; Right. Is it any different to accept a call =
from &quot;Bugs Bunny&quot; </FONT>
<BR><FONT SIZE=3D2>&gt; when it's</FONT>
<BR><FONT SIZE=3D2>&gt; actually Bugs or Osama Bin Laden?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>No, but after he has called twenty times, I want to =
add him to my blocking list. But then he just calls as &quot;Donald =
Duck&quot; and I am no better off. I agree there's nothing I can do =
about this if the calls are coming from the an untrusted source and I =
am stupid enough to accept them at all.</FONT></P>

<P><FONT SIZE=3D2>But if the calls were made through a service provider =
who could authenticate the caller, I would thank them for not allowing =
their subscribers to masquerade as cartoon characters.</FONT></P>

<P><FONT SIZE=3D2>&gt; &gt; In the interim </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; (whilst this PKI is set up), we have a =
'trusted service </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; provider' arrangement (as in 3GPP), where =
the originating </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; service provider does authentication and =
verifies that the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; use is who they say they are in the From: =
field. </FONT>
<BR><FONT SIZE=3D2>&gt; That doesn't help at all unless I trust the =
calling user's service</FONT>
<BR><FONT SIZE=3D2>&gt; provider. What good does it do me that =
&quot;George Bush&quot; using the Chaos</FONT>
<BR><FONT SIZE=3D2>&gt; Computer Club service provider? In the PSTN =
doing this requires global</FONT>
<BR><FONT SIZE=3D2>&gt; transitive trust, which is unrealistic for the =
Internet and SIP in</FONT>
<BR><FONT SIZE=3D2>&gt; general. </FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
</P>

<P><FONT SIZE=3D2>But this is what we will have in 3GPP. There are =
other reasons why inter-operator agreements are needed which are much =
more important than this discussion.</FONT></P>

<P><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>&lt;snip&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; And I have no problem with somebody wanting to =
verify them if that's</FONT>
<BR><FONT SIZE=3D2>&gt; what they want to do. It just doesn't have =
anything to do with SIP the</FONT>
<BR><FONT SIZE=3D2>&gt; protocol.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>It does when people are arguing that there is never a =
requirement to modify the information in these fields.</FONT>
</P>

<P><FONT SIZE=3D2>&lt;snip&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; It's perfectly OK to verify anything =
in any field if you </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; want. I'm not</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; sure this is in fact relevant to the =
discussion. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; It is, because if you 'verify' the field =
(and refuse service </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; if it is not 'right') you take on =
responsibility for its </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; value and this has Data Protection =
implications.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; This logical leap does not seem to be =
justified. It is much </FONT>
<BR><FONT SIZE=3D2>&gt; better IMHO</FONT>
<BR><FONT SIZE=3D2>&gt; to not depend on this implication. What in the =
regs leads you </FONT>
<BR><FONT SIZE=3D2>&gt; to believe</FONT>
<BR><FONT SIZE=3D2>&gt; this is required? If I do RPF verification on =
the source IP </FONT>
<BR><FONT SIZE=3D2>&gt; address of a</FONT>
<BR><FONT SIZE=3D2>&gt; packet, does that mean I take responsibility to =
not reveal the address</FONT>
<BR><FONT SIZE=3D2>&gt; or the subscriber who is using that address? =
This is a very slippery</FONT>
<BR><FONT SIZE=3D2>&gt; slope!</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>There is no legislation that I know of which requires =
Internet Service Providers to provide an anoymous packet delivery =
service - i.e. delivering a packet without revealing the source =
address.</FONT></P>

<P><FONT SIZE=3D2>There is legislation which requires providers of =
Publically Available Telecommunications Services to allow their users =
to make anonymous calls, and to allow subscriber to require that all =
calls from that subscription be anonymous.</FONT></P>

<P><FONT SIZE=3D2>I could speculate about why there is this difference =
between services, but that is not the point.</FONT>
</P>

<P><FONT SIZE=3D2>If the slope is slippery, it's not me what put oil on =
it. I am just trying to explain the situation and ensure that we do not =
ignore potentially important requirements. The price for ignoring this =
stuff is that *more* regulation gets thrust down your throat - this =
slope is more slippery still.</FONT></P>

<P><FONT SIZE=3D2>&gt; &gt; &gt; &lt;snip&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; These last two points =
have led Service Providers</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; to verify the From: =
field. They've been encouraged </FONT>
<BR><FONT SIZE=3D2>&gt; in this by </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; the lack of any other =
field to communicate (2) passed the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; device which does =
authentication. As Dean correctly points </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; out, using From: for =
information like (2) leads to the need </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; to B2BUA everything =
for subscriber privacy (if you </FONT>
<BR><FONT SIZE=3D2>&gt; care about </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; RFC2543 clients). =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; How does this follow as =
long as you define From: as only</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; user-controlled? </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; The field is NOT =
'user-controlled' if the user is forced to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; insert a specific piece of =
information. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Sure it is. I can still put anything =
I want in there. If I </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; don't like</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; the fact that the service provider =
rejects the call I go </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; use somebody </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; else. This is like saying the =
RequestURI: field isn't user </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; controlled, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; because I may have subscribed to a =
free-phone service that </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; only lets me </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; call certain destinations that don't =
go through a PSTN gateway. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I don't think the discussion makes sense =
at all if we don't </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; assume that the user wishes to use the =
service. (*) With this </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; assumption, if the user is required by the =
service to put a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; particular value in the From: field, then =
the service </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; provider absolutely has responsibility for =
that value being </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; there with the associated Data Protection =
responsibility if </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; that value is Personal Data. </FONT>
<BR><FONT SIZE=3D2>&gt; Sort of, but I'll grant the point. In this case =
the service provider</FONT>
<BR><FONT SIZE=3D2>&gt; chose this technique and has to live with it. =
That means doing B2BUA</FONT>
<BR><FONT SIZE=3D2>&gt; stuff to anonymize. </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>Sure.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; &gt; In your free-phone example, the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; service provider has responsibility for =
the fact that the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Request-URI is one of a certain set of =
destinations (and the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; user has control of which one). But this =
is not Personal </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Data, so there is nothing complex about =
this. If the user can </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; choose one of ten possibilities for the =
From field, but all </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; of them identify the user in some way, =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; then although the user </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; has the choice of which value, they have =
no choice about </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; whether to include Personal Data.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Why is this of necessity true? I could, for =
example, do a subscription</FONT>
<BR><FONT SIZE=3D2>&gt; with a service provider which consists of the =
generator for a one time</FONT>
<BR><FONT SIZE=3D2>&gt; pad with full forward security, and the From =
field is </FONT>
<BR><FONT SIZE=3D2>&gt; generated based on</FONT>
<BR><FONT SIZE=3D2>&gt; running the one-time pad. Then every call has a =
different From: field,</FONT>
<BR><FONT SIZE=3D2>&gt; the From: is completely verifiable based on the =
one-time pad, and it</FONT>
<BR><FONT SIZE=3D2>&gt; reveals absolutely nothing about the user to =
any third party.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>My argument only applies if the possible values of =
the From field *do* contain information which would be meaningful to a =
third party.</FONT></P>

<P><FONT SIZE=3D2>The purpose of any verification is to ensure that the =
user is not mis-leading the called party, not to authenticate the user, =
so if the information is meaningless to the called user, there is no =
point in verifying it at all.</FONT></P>

<P><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; I would still argue =
that a subscriber</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; privacy service may =
need to remove (1) as well, so if the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; idea is to avoid the =
requirement to modify/control </FONT>
<BR><FONT SIZE=3D2>&gt; the From: </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; &gt; field, it still might =
not work. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; I'm afraid we're destined =
to disagree here. Anything in the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; From field</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; is something the user by =
definition wants to reveal.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; But the subscriber may not want =
it revealed, and the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; subscriber's wishes may override =
the users. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Then the &quot;subscriber&quot; can, =
in a proxy of B2BUA controlled </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; by him (like</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; the proxy in his basement if a =
residence, or the border </FONT>
<BR><FONT SIZE=3D2>&gt; proxy of a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; corporate site) do any scrubbing or =
call rejection he likes. This </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; reliance on the PSTN definitions of =
user and subscriber </FONT>
<BR><FONT SIZE=3D2>&gt; are really, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; really getting in the way here. I'm =
not saying that we ignore the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; distinction. Rather, I am saying =
that, unlike the PSTN world, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; it is easy </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; to trivial to insert an intermediary, =
controlled by you </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; that you trust </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; to verify and screen outgoing calls, =
incoming calls, or both. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; The definitions of subscriber and user are =
certainly not PSTN </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; ones. It's common-sense concept applying =
to any time any </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; business sells a service in which the =
person contracting for </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the service may not be the same as the =
person who actually </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; uses it. If you're not happy with that, =
the European </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; legislation on electronic communication =
defines these </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; concepts, and you'd better believe it's =
scope is wider than </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the PSTN. </FONT>
<BR><FONT SIZE=3D2>&gt; Sure, but how does this change my argument? =
Either all calls </FONT>
<BR><FONT SIZE=3D2>&gt; are treated</FONT>
<BR><FONT SIZE=3D2>&gt; as though they come from the =
&quot;subscriber&quot; (i.e. the service provider</FONT>
<BR><FONT SIZE=3D2>&gt; cannot distinguish or otherwise vouch for the =
various users) or the</FONT>
<BR><FONT SIZE=3D2>&gt; subscriber provides the discrimination =
themselves. This is an</FONT>
<BR><FONT SIZE=3D2>&gt; unavoidable consequence of the endpoints being =
on one side of a trust</FONT>
<BR><FONT SIZE=3D2>&gt; boundary and the serves being on the =
other.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>I don't follow this. The subscriber *could* provide =
their own proxy, but if the Service Provider accepts that multiple =
users might make calls under the same subscription (in the legal =
sense), they cannot later require the subscriber to install their own =
proxy when the subscriber decides to ask for anonymity =
services.</FONT></P>

<P><FONT SIZE=3D2>The Service Provider could fulfil their obligations =
by *requiring* that all subscribers first install such a proxy, before =
accepting them for service, but this does not sound like a good =
business proposition.</FONT></P>

<P><FONT SIZE=3D2>&gt; Sure the subscriber can deploy a proxy of their =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; own. But the legislation requires the =
subscriber to have a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; 'simple means, free of charge' to request =
the privacy </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; service, and the responsibility to provide =
this is placed on </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the Service provider. And where would the =
subscribe put the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; proxy for a wireless terminal using a =
Wireless WAN ?</FONT>
<BR><FONT SIZE=3D2>&gt; Anywhere they want. This is IP.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>OK, I'm thinking 3GPP. </FONT>
</P>

<P><FONT SIZE=3D2>&lt;snip&gt;</FONT>
</P>

<P><FONT SIZE=3D2>&gt; &gt; My feeling is that not generalizing enough =
is what is causing </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; half this problem in the first place. It =
would be good to </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; have a generic mechanism for carrying =
information subject to </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; potential Data Protection requirements - =
somewhere to </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; 'quarantine' such information - so that fut=
ure services could </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; use this container in the knowledge that =
its Data Protection </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; status will be recognised even by devices =
which do not </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; support the new service. &lt;snip&gt; =
</FONT>
<BR><FONT SIZE=3D2>&gt; I respectfully disagree. I think this approach =
is an infinite </FONT>
<BR><FONT SIZE=3D2>&gt; sinkhole.</FONT>
<BR><FONT SIZE=3D2>&gt; The cases that need separate identities =
asserted by the </FONT>
<BR><FONT SIZE=3D2>&gt; provider are few</FONT>
<BR><FONT SIZE=3D2>&gt; and highly specific, tricky, and not IMHO of =
general utility beyond</FONT>
<BR><FONT SIZE=3D2>&gt; their specific functions.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>I guess my experience from PSTN/ISDN CLI discussions =
is that there were vastly more applications for Calling Line Identity =
than anyone ever envisaged when they defined the single Calling Party =
Number field, or even the Additional Calling Party Number =
field.</FONT></P>

<P><FONT SIZE=3D2>Trying to key services with different requirements =
off a single field often resulted in mutually incompatible requirements =
on which identity should be in the field, resulting in poorer service =
to the user.</FONT></P>

<P><FONT SIZE=3D2>...Mark </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E626.3AA8921A--

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



From daemon@optimus.ietf.org  Wed Apr 17 12:56:26 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26899
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 12:56:21 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA29577
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 12:56:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA28910;
	Wed, 17 Apr 2002 12:43:43 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA28878
	for <sipping@optimus.ietf.org>; Wed, 17 Apr 2002 12:43:40 -0400 (EDT)
Received: from zctfs063.nortelnetworks.com (zctfs063.nortelnetworks.com [47.164.128.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26301
	for <sipping@ietf.org>; Wed, 17 Apr 2002 12:43:32 -0400 (EDT)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zctfs063.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3HGh2B12250;
	Wed, 17 Apr 2002 18:43:02 +0200 (MEST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3HGgNt29056;
	Wed, 17 Apr 2002 17:42:24 +0100 (BST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JDW4NAS8>; Wed, 17 Apr 2002 17:38:36 +0100
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7170@zwcwd00r.europe.nortel.com>
From: "Mark Watson"<mwatson@nortelnetworks.com>
To: "'Alan Johnston'" <alan.johnston@wcom.com>,
        "'David R. Oran'"
	 <oran@cisco.com>,
        "'Dean Willis'" <dean.willis@softarmor.com>,
        "'Sipping (E-mail)'" <sipping@ietf.org>
Subject: RE: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 17:37:31 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E62E.2B4C45AC"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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_01C1E62E.2B4C45AC
Content-Type: text/plain

So, there is clearly disagreement on whether screened From: is a BAD THING
or a GOOD THING.

I really feel that trying to argue that one side is RIGHT and the other
WRONG will not get us anywhere, and we should just work with the situation
as it is. I've just been trying to point out why some people have taken the
screening route.

Two things are independent of this, though:
1) The need for Network Asserted Identity
2) The need for anonymity services

For the example service Juha gave, (1) is the only thing which would allow
him to turn off his From screening, so it is a little churlish to argue that
From screening is WRONG when there is presently no alternative.

Regards,

Mark

> -----Original Message-----
> From: Alan Johnston [mailto:alan.johnston@wcom.com]
> Sent: 17 April 2002 17:14
> To: Watson, Mark [MDN05:EP10:EXCH]; 'David R. Oran'; 'Dean Willis';
> 'Sipping (E-mail)'
> Subject: RE: [Sipping] Screened From: and Privacy
> 
> 
> 
> Mark wrote:
> 
> >I was trying to explain why the text in the SIP 
> specification may have
> led Service
> >Providers to believe that they ought to verify the From: 
> field. You are
> arguing this is
> >a wrong interpretation, but independent of that, I don't think people
> who have
> >interpreted the text that way are being unreasonable.
> 
> I must have missed the 4xx From Header Incorrect response code which
> must be somewhere in bis for this verification of From 
> identity to work
> :-)
> 
> I think this interpretation is totally unreasonable and should be
> dispelled right now for what it is - a mistake.
> 
> Service providers must read Internet specifications very 
> carefully - the
> Internet and its protocols were not designed for them (fortunately).
> 
> Thanks,
> Alan Johnston
> WorldCom
> sip:alan@siptest.wcom.com
> 
> 

------_=_NextPart_001_01C1E62E.2B4C45AC
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.2655.35">
<TITLE>RE: [Sipping] Screened From: and Privacy</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>So, there is clearly disagreement on whether screened =
From: is a BAD THING or a GOOD THING.</FONT>
</P>

<P><FONT SIZE=3D2>I really feel that trying to argue that one side is =
RIGHT and the other WRONG will not get us anywhere, and we should just =
work with the situation as it is. I've just been trying to point out =
why some people have taken the screening route.</FONT></P>

<P><FONT SIZE=3D2>Two things are independent of this, though:</FONT>
<BR><FONT SIZE=3D2>1) The need for Network Asserted Identity</FONT>
<BR><FONT SIZE=3D2>2) The need for anonymity services</FONT>
</P>

<P><FONT SIZE=3D2>For the example service Juha gave, (1) is the only =
thing which would allow him to turn off his From screening, so it is a =
little churlish to argue that From screening is WRONG when there is =
presently no alternative.</FONT></P>

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

<P><FONT SIZE=3D2>Mark</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Alan Johnston [<A =
HREF=3D"mailto:alan.johnston@wcom.com">mailto:alan.johnston@wcom.com</A>=
]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: 17 April 2002 17:14</FONT>
<BR><FONT SIZE=3D2>&gt; To: Watson, Mark [MDN05:EP10:EXCH]; 'David R. =
Oran'; 'Dean Willis';</FONT>
<BR><FONT SIZE=3D2>&gt; 'Sipping (E-mail)'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [Sipping] Screened From: and =
Privacy</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Mark wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;I was trying to explain why the text in the =
SIP </FONT>
<BR><FONT SIZE=3D2>&gt; specification may have</FONT>
<BR><FONT SIZE=3D2>&gt; led Service</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;Providers to believe that they ought to =
verify the From: </FONT>
<BR><FONT SIZE=3D2>&gt; field. You are</FONT>
<BR><FONT SIZE=3D2>&gt; arguing this is</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;a wrong interpretation, but independent of =
that, I don't think people</FONT>
<BR><FONT SIZE=3D2>&gt; who have</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;interpreted the text that way are being =
unreasonable.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I must have missed the 4xx From Header =
Incorrect response code which</FONT>
<BR><FONT SIZE=3D2>&gt; must be somewhere in bis for this verification =
of From </FONT>
<BR><FONT SIZE=3D2>&gt; identity to work</FONT>
<BR><FONT SIZE=3D2>&gt; :-)</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I think this interpretation is totally =
unreasonable and should be</FONT>
<BR><FONT SIZE=3D2>&gt; dispelled right now for what it is - a =
mistake.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Service providers must read Internet =
specifications very </FONT>
<BR><FONT SIZE=3D2>&gt; carefully - the</FONT>
<BR><FONT SIZE=3D2>&gt; Internet and its protocols were not designed =
for them (fortunately).</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Thanks,</FONT>
<BR><FONT SIZE=3D2>&gt; Alan Johnston</FONT>
<BR><FONT SIZE=3D2>&gt; WorldCom</FONT>
<BR><FONT SIZE=3D2>&gt; sip:alan@siptest.wcom.com</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E62E.2B4C45AC--

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



From daemon@ns.ietf.org  Wed Apr 17 14:58:20 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01783
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 14:58:19 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA08368
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 14:58:22 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA07073;
	Wed, 17 Apr 2002 14:35:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA07041
	for <sipping@ns.ietf.org>; Wed, 17 Apr 2002 14:35:33 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00879
	for <sipping@ietf.org>; Wed, 17 Apr 2002 14:35:30 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA29801;
	Wed, 17 Apr 2002 14:34:59 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA29469;
	Wed, 17 Apr 2002 14:35:00 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <H8GSKFGK>; Wed, 17 Apr 2002 14:34:51 -0400
Message-ID: <313680C9A886D511A06000204840E1CF57CE6D@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Mark Watson'" <mwatson@nortelnetworks.com>,
        "'Alan Johnston'"
	 <alan.johnston@wcom.com>,
        "'David R. Oran'" <oran@cisco.com>,
        "'Dean Willis'" <dean.willis@softarmor.com>,
        "'Sipping (E-mail)'"
	 <sipping@ietf.org>
Subject: RE: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 14:34:59 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

I  keep wishing we could slice and dice this down to some things we
agree on and a short list of things we don't, but it doesn't seem to be
happening.

I'll try again.

Can we assume that Mark is correct about SUBSCRIBER (he who pays) as
opposed to USER rights?   I don't like it, but I conclude we
are stuck with it.

Can we assume a Network Asserted Identity is a requirement?  I actually
don't agree with all of Mark's proposed requirements yet, but I think
we HAVE to have it.

Can we possibly agree that an anonymizing B2BUA, provided by a service
provider, would be the only way to achieve real privacy?  I don't think any
of the short cuts like messing with this header or that header will do.

The only practical problems I am aware of with an anonymizing
B2BUA are crypto and DOS. In general, you can't use any kind of crypto
unless 
the B2BUA has the right secrets.  I vaguely remember some research on
anonymous crypto, but in general, it isn't interesting to be secure and 
anonymous completely. You could arrange security against outside 
snooping as long as the service	provider was part of the trust domain 
(which means the B2BUA could be trusted) and still be anonymous. 

If we had a reasonable network asserted identity, I think that is
sufficient to avoid the kinds of problems Christian pointed out
with anonymizers.  It's not truly anonymous - the SP knows who
called.

Brian

 


-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Wednesday, April 17, 2002 12:38 PM
To: 'Alan Johnston'; 'David R. Oran'; 'Dean Willis'; 'Sipping (E-mail)'
Subject: RE: [Sipping] Screened From: and Privacy


So, there is clearly disagreement on whether screened From: is a BAD THING
or a GOOD THING. 
I really feel that trying to argue that one side is RIGHT and the other
WRONG will not get us anywhere, and we should just work with the situation
as it is. I've just been trying to point out why some people have taken the
screening route.
Two things are independent of this, though: 
1) The need for Network Asserted Identity 
2) The need for anonymity services 
For the example service Juha gave, (1) is the only thing which would allow
him to turn off his From screening, so it is a little churlish to argue that
From screening is WRONG when there is presently no alternative.
Regards, 
Mark 
> -----Original Message----- 
> From: Alan Johnston [mailto:alan.johnston@wcom.com] 
> Sent: 17 April 2002 17:14 
> To: Watson, Mark [MDN05:EP10:EXCH]; 'David R. Oran'; 'Dean Willis'; 
> 'Sipping (E-mail)' 
> Subject: RE: [Sipping] Screened From: and Privacy 
> 
> 
> 
> Mark wrote: 
> 
> >I was trying to explain why the text in the SIP 
> specification may have 
> led Service 
> >Providers to believe that they ought to verify the From: 
> field. You are 
> arguing this is 
> >a wrong interpretation, but independent of that, I don't think people 
> who have 
> >interpreted the text that way are being unreasonable. 
> 
> I must have missed the 4xx From Header Incorrect response code which 
> must be somewhere in bis for this verification of From 
> identity to work 
> :-) 
> 
> I think this interpretation is totally unreasonable and should be 
> dispelled right now for what it is - a mistake. 
> 
> Service providers must read Internet specifications very 
> carefully - the 
> Internet and its protocols were not designed for them (fortunately). 
> 
> Thanks, 
> Alan Johnston 
> WorldCom 
> sip:alan@siptest.wcom.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 daemon@ns.ietf.org  Wed Apr 17 15:01:13 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01953
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 15:01:13 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA08806
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 15:01:16 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA07989;
	Wed, 17 Apr 2002 14:48:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA07954
	for <sipping@ns.ietf.org>; Wed, 17 Apr 2002 14:48:03 -0400 (EDT)
Received: from bdsl.66.12.12.130.gte.net (bdsl.66.12.12.130.gte.net [66.12.12.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01336
	for <sipping@ietf.org>; Wed, 17 Apr 2002 14:47:56 -0400 (EDT)
Received: from C1893415A (bdsl.greycouncil.com [127.0.0.1])
	by bdsl.66.12.12.130.gte.net (8.11.6/8.11.6) with SMTP id g3HIkOd02570;
	Wed, 17 Apr 2002 13:46:24 -0500
Message-ID: <029801c1e640$2e8c8120$133fed0c@C1893415A>
From: "Dean Willis" <dean.willis@softarmor.com>
To: "Rosen, Brian" <Brian.Rosen@marconi.com>,
        "'Mark Watson'" <mwatson@nortelnetworks.com>,
        "'Alan Johnston'" <alan.johnston@wcom.com>,
        "'David R. Oran'" <oran@cisco.com>,
        "'Sipping \(E-mail\)'" <sipping@ietf.org>
References: <313680C9A886D511A06000204840E1CF57CE6D@whq-msgusr-02.pit.comms.marconi.com>
Subject: Re: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 13:46:26 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Brian mumbled:
> I  keep wishing we could slice and dice this down to some things we
> agree on and a short list of things we don't, but it doesn't seem to
be
> happening.
>
> I'll try again.
>
> Can we assume that Mark is correct about SUBSCRIBER (he who pays) as
> opposed to USER rights?   I don't like it, but I conclude we
> are stuck with it.

yes


> Can we assume a Network Asserted Identity is a requirement?  I
actually
> don't agree with all of Mark's proposed requirements yet, but I think
> we HAVE to have it.

yes


> Can we possibly agree that an anonymizing B2BUA, provided by a service
> provider, would be the only way to achieve real privacy?  I don't
think any
> of the short cuts like messing with this header or that header will
do.

yes

> The only practical problems I am aware of with an anonymizing
> B2BUA are crypto and DOS. In general, you can't use any kind of crypto
> unless
> the B2BUA has the right secrets.  I vaguely remember some research on
> anonymous crypto, but in general, it isn't interesting to be secure
and
> anonymous completely. You could arrange security against outside
> snooping as long as the service provider was part of the trust domain
> (which means the B2BUA could be trusted) and still be anonymous.

one might argue that user-specific keys are themselves privacy
violations. One needs session re-keying at the B2BUA.

> If we had a reasonable network asserted identity, I think that is
> sufficient to avoid the kinds of problems Christian pointed out
> with anonymizers.  It's not truly anonymous - the SP knows who
> called.
>

yes


Of course, there are OTHER requirements, but I think we're moving well
now . . .

--
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 daemon@ns.ietf.org  Wed Apr 17 15:40:22 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03618
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 15:40:20 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA11767
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 15:40:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA10308;
	Wed, 17 Apr 2002 15:29:32 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA10278
	for <sipping@ns.ietf.org>; Wed, 17 Apr 2002 15:29:29 -0400 (EDT)
Received: from mail6.microsoft.com (mail6.microsoft.com [131.107.3.126])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03151
	for <sipping@ietf.org>; Wed, 17 Apr 2002 15:29:25 -0400 (EDT)
Received: from inet-vrs-06.redmond.corp.microsoft.com ([157.54.6.201]) by mail6.microsoft.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 17 Apr 2002 12:28:50 -0700
Received: from 157.54.8.109 by inet-vrs-06.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 17 Apr 2002 12:28:50 -0700
Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by inet-hub-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 17 Apr 2002 12:28:50 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by red-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 17 Apr 2002 12:28:32 -0700
Received: from win-msg-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.134]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3604.0);
	 Wed, 17 Apr 2002 12:25:05 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6177.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 12:25:05 -0700
Message-ID: <F66A04C29AD9034A8205949AD0C90104032702EB@win-msg-02.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: [Sipping] Screened From: and Privacy
Thread-Index: AcHmPky9cmi30OBlR0Cnb1Ti535+ZwABlrAQ
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Rosen, Brian" <Brian.Rosen@marconi.com>,
        "Mark Watson" <mwatson@nortelnetworks.com>,
        "Alan Johnston" <alan.johnston@wcom.com>,
        "David R. Oran" <oran@cisco.com>,
        "Dean Willis" <dean.willis@softarmor.com>,
        "Sipping (E-mail)" <sipping@ietf.org>
X-OriginalArrivalTime: 17 Apr 2002 19:25:05.0968 (UTC) FILETIME=[94623300:01C1E645]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id PAA10279
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 8bit

> Can we assume that Mark is correct about SUBSCRIBER (he who pays) as
> opposed to USER rights?   I don't like it, but I conclude we
> are stuck with it.

Well, let's put it this way: the only think that a network service can
possibly disclose is the identity of the subscriber. I do not agree
however that the From field should necessarily contain the name of the
subscriber.

> Can we assume a Network Asserted Identity is a requirement?  I
actually
> don't agree with all of Mark's proposed requirements yet, but I think
> we HAVE to have it.

No, I do not agree.

> Can we possibly agree that an anonymizing B2BUA, provided by a service
> provider, would be the only way to achieve real privacy?  I don't
think
> any
> of the short cuts like messing with this header or that header will
do.

I believe that "B2BUA provided by a service provider" do not actually
provide any more privacy than any service in which the provider agrees
to let you place random values in the "from" field. In practice, privacy
and third parties don't mix. I also believe that it is in practice
impossible to provide a useful anonymizing service in the network.

> If we had a reasonable network asserted identity, I think that is
> sufficient to avoid the kinds of problems Christian pointed out
> with anonymizers.  It's not truly anonymous - the SP knows who
> called.

I think trusting a network asserted identity would be a big mistake --
much like trusting a source IP address. Real end-to-end assessment of
the third party's identity can only result from end-to-end
authentication, as in S-MIME. Trying to push the trust in the network
requires a chain of trust between all relays, which is bound to fail in
a system the size of the Internet.

-- Christian Huitema

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



From daemon@ns.ietf.org  Wed Apr 17 16:31:31 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06382
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 16:31:31 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA15427
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 16:31:34 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA14268;
	Wed, 17 Apr 2002 16:19:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA14221
	for <sipping@ns.ietf.org>; Wed, 17 Apr 2002 16:19:01 -0400 (EDT)
Received: from mail6.microsoft.com (mail6.microsoft.com [131.107.3.126])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05821
	for <sipping@ietf.org>; Wed, 17 Apr 2002 16:18:57 -0400 (EDT)
Received: from inet-vrs-06.redmond.corp.microsoft.com ([157.54.6.201]) by mail6.microsoft.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 17 Apr 2002 13:18:30 -0700
Received: from 157.54.6.150 by inet-vrs-06.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 17 Apr 2002 13:18:30 -0700
Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by inet-hub-05.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 17 Apr 2002 13:18:29 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by red-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 17 Apr 2002 13:18:29 -0700
Received: from win-msg-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.134]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3604.0);
	 Wed, 17 Apr 2002 13:14:39 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6177.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 13:14:38 -0700
Message-ID: <F66A04C29AD9034A8205949AD0C90104032702EC@win-msg-02.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: [Sipping] Screened From: and Privacy
Thread-Index: AcHmShle0iG014L7RCKO/E4N/q4M/AAAchHQ
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Dean Willis" <dean.willis@softarmor.com>,
        "Rosen, Brian" <Brian.Rosen@marconi.com>,
        "Mark Watson" <mwatson@nortelnetworks.com>,
        "Alan Johnston" <alan.johnston@wcom.com>,
        "David R. Oran" <oran@cisco.com>,
        "Sipping (E-mail)" <sipping@ietf.org>
X-OriginalArrivalTime: 17 Apr 2002 20:14:39.0227 (UTC) FILETIME=[809584B0:01C1E64C]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id QAA14222
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 8bit

> Do you trust your browser to know that the web server you're banking
> with is actually your bank's server, and not somebody else? Probably
--
> but in doing so you trusted Microsoft (really?) to give you good root
CA
> certs. You then trusted the CA to validate the cert of the bank.
> Reasonably solid crypto. It's not impossible to do something similar
for
> SIP identity assertion. How much do we really need?

You are correct in pointing out the elements in the trust chain: in the
case of HTTPS, the software you run, and the list of root-CA that the
software trusts. Am I entirely satisfied that all root-CA are doing a
good job? Well, not entirely, I tend to find that there are too many of
them, about 100; but it is relatively easy to yank a compromised CA from
the list -- I can do that locally, on my PC. OTOH, there are many more
ISP than root-CA, several 10,000, so it is quite obvious that I cannot
trust them all; besides, each enterprise is going to run its own server,
so I would have to trust a few 1,000,000 domains in addition to the ISP.
And I have no way to yank an ISP from the list. So I believe that, if we
want real screening, we need S-MIME.

-- Christian Huitema

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



From daemon@ns.ietf.org  Wed Apr 17 16:31:35 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06376
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 16:31:30 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA15419
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 16:31:34 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA13643;
	Wed, 17 Apr 2002 16:01:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA13612
	for <sipping@ns.ietf.org>; Wed, 17 Apr 2002 16:01:46 -0400 (EDT)
Received: from bdsl.66.12.12.130.gte.net (bdsl.66.12.12.130.gte.net [66.12.12.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05008
	for <sipping@ietf.org>; Wed, 17 Apr 2002 16:01:42 -0400 (EDT)
Received: from C1893415A (bdsl.greycouncil.com [127.0.0.1])
	by bdsl.66.12.12.130.gte.net (8.11.6/8.11.6) with SMTP id g3HK0nd03138;
	Wed, 17 Apr 2002 15:00:50 -0500
Message-ID: <02eb01c1e64a$94ac1b00$133fed0c@C1893415A>
From: "Dean Willis" <dean.willis@softarmor.com>
To: "Christian Huitema" <huitema@windows.microsoft.com>,
        "Rosen, Brian" <Brian.Rosen@marconi.com>,
        "Mark Watson" <mwatson@nortelnetworks.com>,
        "Alan Johnston" <alan.johnston@wcom.com>,
        "David R. Oran" <oran@cisco.com>,
        "Sipping \(E-mail\)" <sipping@ietf.org>
References: <F66A04C29AD9034A8205949AD0C90104032702EB@win-msg-02.wingroup.windeploy.ntdev.microsoft.com>
Subject: Re: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 15:00:52 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit


> > Can we assume that Mark is correct about SUBSCRIBER (he who pays) as
> > opposed to USER rights?   I don't like it, but I conclude we
> > are stuck with it.
>
> Well, let's put it this way: the only think that a network service can
> possibly disclose is the identity of the subscriber. I do not agree
> however that the From field should necessarily contain the name of the
> subscriber.

No argument here.

> > Can we assume a Network Asserted Identity is a requirement?  I
> actually
> > don't agree with all of Mark's proposed requirements yet, but I
think
> > we HAVE to have it.
>
> No, I do not agree.

I think it is a requirement only for PSTN interworking where a "name"
has to be mapped to a PSTN phone number for caller-ID purposes.

> > Can we possibly agree that an anonymizing B2BUA, provided by a
service
> > provider, would be the only way to achieve real privacy?  I don't
> think
> > any
> > of the short cuts like messing with this header or that header will
> do.
>
> I believe that "B2BUA provided by a service provider" do not actually
> provide any more privacy than any service in which the provider agrees
> to let you place random values in the "from" field. In practice,
privacy
> and third parties don't mix. I also believe that it is in practice
> impossible to provide a useful anonymizing service in the network.

Well, they do have the advantage of being able to suppress Via and Route
information that would tend to give away your location, and of being
able to provide a media-intermediary that prevents traceroutes back
along the RTP path from giving up much useful information.

Actually, I use useful anonymizing services every day. Can you tell if
this email is being sent from a PC at my house or from my office? I hope
not, because as far as I know I'm ssh tunnelling to my mail relay, which
is then sending the mail onward. So the SMTP relay is anonymizing my
physical location, insofar as it might be readily determined from the
actual IP address I'm using at the moment.

 > > If we had a reasonable network asserted identity, I think that is
> > sufficient to avoid the kinds of problems Christian pointed out
> > with anonymizers.  It's not truly anonymous - the SP knows who
> > called.
>
> I think trusting a network asserted identity would be a big mistake --
> much like trusting a source IP address. Real end-to-end assessment of
> the third party's identity can only result from end-to-end
> authentication, as in S-MIME. Trying to push the trust in the network
> requires a chain of trust between all relays, which is bound to fail
in
> a system the size of the Internet.

If absolute truth is an absolute lie, then perhaps absolute trust is an
absolute betrayal.

Does the network-asserted identity work well enough to do caller ID
interworking? What is calling-party-ID except for network-asserted
identity, anyhow?

Do you trust your browser to know that the web server you're banking
with is actually your bank's server, and not somebody else? Probably --
but in doing so you trusted Microsoft (really?) to give you good root CA
certs. You then trusted the CA to validate the cert of the bank.
Reasonably solid crypto. It's not impossible to do something similar for
SIP identity assertion. How much do we really need?

--
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 daemon@ns.ietf.org  Wed Apr 17 16:43:44 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06963
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 16:43:43 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA16312
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 16:43:47 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA15683;
	Wed, 17 Apr 2002 16:33:44 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA15652
	for <sipping@ns.ietf.org>; Wed, 17 Apr 2002 16:33:40 -0400 (EDT)
Received: from ierw.net.avaya.com (ierw.net.avaya.com [198.152.13.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06457
	for <sipping@ietf.org>; Wed, 17 Apr 2002 16:33:36 -0400 (EDT)
Received: from ierw.net.avaya.com (localhost [127.0.0.1])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id QAA23400
	for <sipping@ietf.org>; Wed, 17 Apr 2002 16:32:03 -0400 (EDT)
Received: from cof110avexu1.global.avaya.com (h135-9-6-16.avaya.com [135.9.6.16])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id QAA23383
	for <sipping@ietf.org>; Wed, 17 Apr 2002 16:32:03 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 14:34:21 -0600
Message-ID: <EF4C65F18BE6464B8E9DF3C212B6B2930168E108@cof110avexu1.global.avaya.com>
Thread-Topic: [Sipping] Screened From: and Privacy
Thread-Index: AcHmPky9cmi30OBlR0Cnb1Ti535+ZwABlrAQAAJnmrA=
From: "Zmolek, Andrew (Andrew)" <zmolek@avaya.com>
To: "Christian Huitema" <huitema@windows.microsoft.com>,
        "Rosen, Brian" <Brian.Rosen@marconi.com>,
        "Mark Watson" <mwatson@nortelnetworks.com>,
        "Alan Johnston" <alan.johnston@wcom.com>,
        "David R. Oran" <oran@cisco.com>,
        "Dean Willis" <dean.willis@softarmor.com>,
        "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id QAA15653
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 8bit

> > Can we assume a Network Asserted Identity is a requirement?  
> > I actually don't agree with all of Mark's proposed requirements 
> > yet, but I think we HAVE to have it.
> 
> No, I do not agree.

Could you elaborate, Christian? What is the alternative?

--Andy Zmolek 
    Technology & Standards Engineer 
      CTO Standards 
        Avaya Inc. 

            zmolek@avaya.com 
              +1 720 444 4001 


 

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



From daemon@ns.ietf.org  Wed Apr 17 16:57:35 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07448
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 16:57:35 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA17166
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 16:57:39 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA16554;
	Wed, 17 Apr 2002 16:47:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA16488
	for <sipping@ns.ietf.org>; Wed, 17 Apr 2002 16:47:03 -0400 (EDT)
Received: from lohi.eng.song.fi (lohi.eng.song.fi [195.10.149.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07038
	for <sipping@ietf.org>; Wed, 17 Apr 2002 16:46:46 -0400 (EDT)
From: jh@lohi.eng.song.fi
Received: from harjus.eng.song.fi ([195.10.149.20])
	by lohi.eng.song.fi with esmtp (Exim 3.34 #1 (Debian))
	id 16xwKD-0005DI-00; Wed, 17 Apr 2002 23:46:45 +0300
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15549.57141.223169.437546@harjus.eng.song.fi>
Date: Wed, 17 Apr 2002 23:46:45 +0300
To: "Jesske, R" <R.Jesske@telekom.de>
Cc: dean.willis@softarmor.com, sipping@ietf.org
Subject: AW: [Sipping] Screened From: and Privacy
In-Reply-To: <C835D57E3730D6119F5000A0C9F019A94A9A4A@U8P13.blf01.telekom.de>
References: <C835D57E3730D6119F5000A0C9F019A94A9A4A@U8P13.blf01.telekom.de>
X-Mailer: VM 7.01 under Emacs 21.1.1
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Jesske, R writes:

 > How should it be verified when I'm anonymous. Then I need some Information for the regulatory aspect!

your display string is "Anonymous", but the uri contains the your from
address (see below).

 > 2. The SIP user has a E.164@user URL then the Gateway maps the URL direct to the Calling Party Number. (e.G. +496151835940@telekom.de to CgPN=6151835940 with the indication national or international). 

this is what we are using and once it is used, the provider needs to
verify the number and after the verification is becomes trusted.

so i don't understand what additional value the rpid would bring.

 > If I'm anonymous I need the real identity within an other Header
 > (RPID).The network will inset the real identity into the RPID with
 > screen=yes. The RPID will be mapped to the PSTN as an restricted
 > number, the restricted number is needed for some regulatory aspect
 > (e.g. legal interception). But the normal user sees only the contend
 > of the From header.

you clearly didn't get my point.  the uri of the from field MUST contain
the calling number, whereas the display string controls the anonymity or
that number.

-- juha



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



From daemon@ns.ietf.org  Wed Apr 17 16:57:37 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07462
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 16:57:37 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA17180
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 16:57:40 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA16519;
	Wed, 17 Apr 2002 16:47:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA16480
	for <sipping@ns.ietf.org>; Wed, 17 Apr 2002 16:47:02 -0400 (EDT)
Received: from iere.net.avaya.com (iere.net.avaya.com [198.152.12.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07054
	for <sipping@ietf.org>; Wed, 17 Apr 2002 16:46:58 -0400 (EDT)
Received: from iere.net.avaya.com (localhost [127.0.0.1])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g3HKjO101457
	for <sipping@ietf.org>; Wed, 17 Apr 2002 16:45:24 -0400 (EDT)
Received: from cof110avexu1.global.avaya.com (h135-9-6-16.avaya.com [135.9.6.16])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g3HKjOu01428
	for <sipping@ietf.org>; Wed, 17 Apr 2002 16:45:24 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 14:47:42 -0600
Message-ID: <EF4C65F18BE6464B8E9DF3C212B6B2930168E10E@cof110avexu1.global.avaya.com>
Thread-Topic: [Sipping] Screened From: and Privacy
Thread-Index: AcHmShle0iG014L7RCKO/E4N/q4M/AAAchHQAADYNIA=
From: "Zmolek, Andrew (Andrew)" <zmolek@avaya.com>
To: "Christian Huitema" <huitema@windows.microsoft.com>,
        "Dean Willis" <dean.willis@softarmor.com>,
        "Rosen, Brian" <Brian.Rosen@marconi.com>,
        "Mark Watson" <mwatson@nortelnetworks.com>,
        "Alan Johnston" <alan.johnston@wcom.com>,
        "David R. Oran" <oran@cisco.com>,
        "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id QAA16481
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 8bit

> So I believe that, if we want real screening, 
> we need S-MIME.
> 
> -- Christian Huitema

Are you suggesting that screening is an all-or-nothing proposition? Imagine what would happen in the web or email systems were held to these standards. 

At some point, it becomes more important to indicate a level of trust and allow the end-user to decide. Reasonable identity assertions are far preferable to toothless guarantees.

--Andy Zmolek 
    Technology & Standards Engineer 
      CTO Standards 
        Avaya Inc. 

            zmolek@avaya.com 
              +1 720 444 4001 



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



From daemon@ns.ietf.org  Wed Apr 17 17:15:52 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08223
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 17:15:51 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA19096
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 17:15:55 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA18354;
	Wed, 17 Apr 2002 17:02:04 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA18294
	for <sipping@ns.ietf.org>; Wed, 17 Apr 2002 17:01:59 -0400 (EDT)
Received: from mail5.microsoft.com (mail5.microsoft.com [131.107.3.121])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07705
	for <sipping@ietf.org>; Wed, 17 Apr 2002 17:01:55 -0400 (EDT)
Received: from inet-vrs-05.redmond.corp.microsoft.com ([157.54.6.148]) by mail5.microsoft.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 17 Apr 2002 14:01:26 -0700
Received: from 157.54.8.109 by inet-vrs-05.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 17 Apr 2002 14:01:26 -0700
Received: from red-imc-04.redmond.corp.microsoft.com ([157.54.2.168]) by inet-hub-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Wed, 17 Apr 2002 14:01:26 -0700
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.84]) by red-imc-04.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Wed, 17 Apr 2002 14:01:26 -0700
Received: from win-msg-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.134]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3590.0);
	 Wed, 17 Apr 2002 13:57:50 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6177.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 13:57:49 -0700
Message-ID: <F66A04C29AD9034A8205949AD0C90104032702ED@win-msg-02.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: [Sipping] Screened From: and Privacy
Thread-Index: AcHmPky9cmi30OBlR0Cnb1Ti535+ZwABlrAQAAJnmrAAASfSQA==
From: "Christian Huitema" <huitema@windows.microsoft.com>
To: "Zmolek, Andrew (Andrew)" <zmolek@avaya.com>,
        "Rosen, Brian" <Brian.Rosen@marconi.com>,
        "Mark Watson" <mwatson@nortelnetworks.com>,
        "Alan Johnston" <alan.johnston@wcom.com>,
        "David R. Oran" <oran@cisco.com>,
        "Dean Willis" <dean.willis@softarmor.com>,
        "Sipping (E-mail)" <sipping@ietf.org>
X-OriginalArrivalTime: 17 Apr 2002 20:57:50.0271 (UTC) FILETIME=[88F774F0:01C1E652]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id RAA18295
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 8bit

> > > Can we assume a Network Asserted Identity is a requirement?
> > > I actually don't agree with all of Mark's proposed requirements
> > > yet, but I think we HAVE to have it.
> >
> > No, I do not agree.
> 
> Could you elaborate, Christian? What is the alternative?

User asserted identity backed by S-MIME or other similar technology.

-- Christian Huitema
 

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



From daemon@ns.ietf.org  Wed Apr 17 17:40:27 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08712
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 17:40:27 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA20643
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 17:40:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA19363;
	Wed, 17 Apr 2002 17:23:04 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA19331
	for <sipping@ns.ietf.org>; Wed, 17 Apr 2002 17:23:01 -0400 (EDT)
Received: from ierw.net.avaya.com (ierw.net.avaya.com [198.152.13.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08412
	for <sipping@ietf.org>; Wed, 17 Apr 2002 17:22:57 -0400 (EDT)
Received: from ierw.net.avaya.com (localhost [127.0.0.1])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id RAA17618
	for <sipping@ietf.org>; Wed, 17 Apr 2002 17:21:23 -0400 (EDT)
Received: from cof110avexu1.global.avaya.com (h135-9-6-16.avaya.com [135.9.6.16])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id RAA17603
	for <sipping@ietf.org>; Wed, 17 Apr 2002 17:21:23 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 15:23:41 -0600
Message-ID: <EF4C65F18BE6464B8E9DF3C212B6B2930168E12A@cof110avexu1.global.avaya.com>
Thread-Topic: [Sipping] Screened From: and Privacy
Thread-Index: AcHmPky9cmi30OBlR0Cnb1Ti535+ZwABlrAQAAJnmrAAASfSQAAAlPGA
From: "Zmolek, Andrew (Andrew)" <zmolek@avaya.com>
To: "Christian Huitema" <huitema@windows.microsoft.com>,
        "Rosen, Brian" <Brian.Rosen@marconi.com>,
        "Mark Watson" <mwatson@nortelnetworks.com>,
        "Alan Johnston" <alan.johnston@wcom.com>,
        "David R. Oran" <oran@cisco.com>,
        "Dean Willis" <dean.willis@softarmor.com>,
        "Sipping (E-mail)" <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id RAA19332
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 8bit

> > > > Can we assume a Network Asserted Identity is a requirement?
> > > > I actually don't agree with all of Mark's proposed requirements
> > > > yet, but I think we HAVE to have it.
> > >
> > > No, I do not agree.
> > 
> > Could you elaborate, Christian? What is the alternative?
> 
> User asserted identity backed by S-MIME or other similar technology.
> 
> -- Christian Huitema

So we're back to the UAI vs. NAI debate. 

I don't see any compelling reason to pick a winner, but I do agree with earlier assertions that each has unique requirements. What is the benefit gained by precluding NAI? 

--Andy

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



From daemon@ns.ietf.org  Wed Apr 17 17:55:25 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09092
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 17:55:25 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA21397
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 17:55:29 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA20892;
	Wed, 17 Apr 2002 17:43:34 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA20864
	for <sipping@ns.ietf.org>; Wed, 17 Apr 2002 17:43:31 -0400 (EDT)
Received: from ierw.net.avaya.com (ierw.net.avaya.com [198.152.13.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08793
	for <sipping@ietf.org>; Wed, 17 Apr 2002 17:43:27 -0400 (EDT)
Received: from ierw.net.avaya.com (localhost [127.0.0.1])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id RAA06264
	for <sipping@ietf.org>; Wed, 17 Apr 2002 17:41:54 -0400 (EDT)
Received: from cof110avexu1.global.avaya.com (h135-9-6-16.avaya.com [135.9.6.16])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id RAA06249
	for <sipping@ietf.org>; Wed, 17 Apr 2002 17:41:53 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] Screened From: and Privacy
Date: Wed, 17 Apr 2002 15:44:11 -0600
Message-ID: <EF4C65F18BE6464B8E9DF3C212B6B2930168E147@cof110avexu1.global.avaya.com>
Thread-Topic: [Sipping] Screened From: and Privacy
Thread-Index: AcHmUUbWy40wKn6VR+W27HbFDnuKZgABkLdg
From: "Zmolek, Andrew (Andrew)" <zmolek@avaya.com>
To: <jh@lohi.eng.song.fi>, "Jesske, R" <R.Jesske@telekom.de>
Cc: <dean.willis@softarmor.com>, <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id RAA20865
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 8bit

> the uri of the from field MUST contain the calling 
> number, whereas the display string controls the 
> anonymity or that number.
> 
> -- juha

Just because a display string might exist doesn't mean it's necessarily the only thing presented to the end user at the far end. Frankly, an implementer can choose to display as much or as little as desired, use local policy, etc. And while the display string may meet UAI requirements, it doesn't meet NAI without forcing a choice. 

Again, what is the benefit gained by forcing a choice between UAI and NAI? I don't see it.

--Andy

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



From daemon@ns.ietf.org  Wed Apr 17 19:28:59 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10871
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 19:28:59 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA26559
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 19:29:01 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA25858;
	Wed, 17 Apr 2002 19:11:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA25750
	for <sipping@ns.ietf.org>; Wed, 17 Apr 2002 19:11:29 -0400 (EDT)
Received: from exchange1.nuera.com ([12.105.228.79])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10587
	for <sipping@ietf.org>; Wed, 17 Apr 2002 19:11:25 -0400 (EDT)
Received: by exchange1.nuera.com with Internet Mail Service (5.5.2653.19)
	id <2HADJBQP>; Wed, 17 Apr 2002 16:11:59 -0700
Message-ID: <E79883AEA37FD411A58C00508BAC5F4B01D38C7E@exchange1.nuera.com>
From: "Fairlie-Cuninghame, Robert" <rfairlie@nuera.com>
To: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>, sipping@ietf.org
Subject: RE: [Sipping] I-D  ACTION:draft-culpepper-sipping-app-interact-re
	qs-00.txt
Date: Wed, 17 Apr 2002 16:11:54 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Just to provide a break in the monotony of Subject fields ...

Jonathan,

 I've given some more thought to a couple of your requirements:

> * The mechanism should allow a device to indicate support for multiple
> user interfaces, and allow the application to select which 
> one is to be
> used
>
> * The mechanism should allow a device to indicate relative preferences
> amongst the various user interfaces
> 

I don't think your requirement adequately answers the questions: what is a
"user interface" and what does it mean to have "multiple user interfaces"?
Assumedly a device normally has only one *physical* interface (be it keys or
display or whatever). Now we all agree that the mechanism must not force the
device's interface to be "taken over" by an application. 

One logical way to define multiple user interfaces or rather "virtual user
interfaces" is to create a virtual instance of the physical instance that is
active when the application/session is in focus to the user (much in the way
a multiline SIP phone may work). There are other approaches but most of the
ones I can think of are diminuitive cases of this general approach. In any
case, how this interface is selected or created will largely depend on the
user device and not this mechanism. 

It is my contention therefore, that it should not be a requirement on the
network application interaction mechanism to present multiple (prioritized)
permutations or instances of user interfaces to an application. Rather, the
relevant requirement should be:

* The mechanism should support the identification of a requesting
application identity [e.g. application name+version @ creator's domain] and
application instance [e.g. instance@ service perovider's domain]. 
* The mechanism should the ability for a user interface instance to be
shared between subscriptions (and probably applications when multiple
applications are co-operating). 

This allows a device to create and offer virtual user interfaces as it sees
fit. The application always operates on the "virtual" user interface
instance. This is also a MUCH, MUCH simpler problem - merely one of
identification - not presentation or negotiation (this is a highly
complicated area already). [This approach also allows the device to store
customized application-specific interfaces that can be recalled as required
whenever interacting with the same application.]

Just some thoughts.

Robert.

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



From daemon@ns.ietf.org  Wed Apr 17 19:30:18 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10908
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 19:30:18 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA26691
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 19:30:20 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA26111;
	Wed, 17 Apr 2002 19:21:45 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA26082
	for <sipping@ns.ietf.org>; Wed, 17 Apr 2002 19:21:43 -0400 (EDT)
Received: from imo-d08.mx.aol.com (imo-d08.mx.aol.com [205.188.157.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10693
	for <sipping@ietf.org>; Wed, 17 Apr 2002 19:21:40 -0400 (EDT)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-d08.mx.aol.com (mail_out_v32.5.) id 6.9a.242c9b0e (25511);
	Wed, 17 Apr 2002 19:21:09 -0400 (EDT)
Message-ID: <9a.242c9b0e.29ef5d64@aol.com>
Date: Wed, 17 Apr 2002 19:21:08 EDT
Subject: Re: [Sipping] Screened From: and Privacy
To: huitema@windows.microsoft.com, sipping@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_9a.242c9b0e.29ef5d64_boundary"
X-Mailer: AOL 6.0 for Windows US sub 10524
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


--part1_9a.242c9b0e.29ef5d64_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 4/17/02 3:31:39 PM Eastern Daylight Time, 
huitema@windows.microsoft.com writes:


> I think trusting a network asserted identity would be a big mistake --
> much like trusting a source IP address. Real end-to-end assessment of
> the third party's identity can only result from end-to-end
> authentication, as in S-MIME. Trying to push the trust in the network
> requires a chain of trust between all relays, which is bound to fail in
> a system the size of the Internet.
> 
> 

This all depends on your "network" model. If a telephone call is set up 
through a sucession of "networks" and each one trusts the previous to pass 
valid data because they have interworking agreements, then if the first 
network aserts an identity and labels it as "verified", then every succesive 
network must believe it, just as each network must believe that the sucessive 
network will honor any request to keep the identity private. Yes, there is a 
chain of trust which can not fail in this model. (Yes, I know people will 
jump on that final sentence!)

If, on the other hand, your "network" model is one of a collection of routers 
and entities and network segments in which none can trust anyone else, then 
you are correct. End-to-end authentication becomes necessary if you want to 
believe the identity. However, because of the lack of trust, the identity 
will never be there to check if the originator wanted privacy.

Mike


--part1_9a.242c9b0e.29ef5d64_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 4/17/02 3:31:39 PM Eastern Daylight Time, huitema@windows.microsoft.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">I think trusting a network asserted identity would be a big mistake --
<BR>much like trusting a source IP address. Real end-to-end assessment of
<BR>the third party's identity can only result from end-to-end
<BR>authentication, as in S-MIME. Trying to push the trust in the network
<BR>requires a chain of trust between all relays, which is bound to fail in
<BR>a system the size of the Internet.
<BR>
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>This all depends on your "network" model. If a telephone call is set up through a sucession of "networks" and each one trusts the previous to pass valid data because they have interworking agreements, then if the first network aserts an identity and labels it as "verified", then every succesive network must believe it, just as each network must believe that the sucessive network will honor any request to keep the identity private. Yes, there is a chain of trust which can not fail in this model. (Yes, I know people will jump on that final sentence!)
<BR>
<BR>If, on the other hand, your "network" model is one of a collection of routers and entities and network segments in which none can trust anyone else, then you are correct. End-to-end authentication becomes necessary if you want to believe the identity. However, because of the lack of trust, the identity will never be there to check if the originator wanted privacy.
<BR>
<BR>Mike
<BR></FONT></HTML>

--part1_9a.242c9b0e.29ef5d64_boundary--

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



From daemon@ns.ietf.org  Wed Apr 17 19:31:21 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10958
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 19:31:21 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA26966
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 19:31:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA26366;
	Wed, 17 Apr 2002 19:23:01 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA26335
	for <sipping@ns.ietf.org>; Wed, 17 Apr 2002 19:22:56 -0400 (EDT)
Received: from imo-r02.mx.aol.com (imo-r02.mx.aol.com [152.163.225.98])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10756
	for <sipping@ietf.org>; Wed, 17 Apr 2002 19:22:53 -0400 (EDT)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r02.mx.aol.com (mail_out_v32.5.) id t.117.101ff569 (25511);
	Wed, 17 Apr 2002 19:21:18 -0400 (EDT)
Message-ID: <117.101ff569.29ef5d6d@aol.com>
Date: Wed, 17 Apr 2002 19:21:17 EDT
Subject: Re: AW: [Sipping] Screened From: and Privacy
To: jh@lohi.eng.song.fi, R.Jesske@telekom.de
CC: dean.willis@softarmor.com, sipping@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_117.101ff569.29ef5d6d_boundary"
X-Mailer: AOL 6.0 for Windows US sub 10524
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


--part1_117.101ff569.29ef5d6d_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 4/17/02 4:39:02 AM Eastern Daylight Time, 
jh@lohi.eng.song.fi writes:


> > There will be no PSTN Operator that take an untrusted From Header to
> > a calling party number --> instead the PSTN operator will set up a
> > new calling party number that is network provided and trusted!
> 
> to which number the network would set the calling party number?  my sip
> users can have any number of calling party numbers belonging to any
> number of calling areas and soon even to any number of countries.  
> 

I believe the point was that the gateway (or whatever you want to call the 
thing that goes between the SIP and the PSTN signaling) would replace the 
untrusted identity in the "From" with a new calling party number, and that 
this new number would be one that designates the operator of the gateway 
itself, not one belonging to the originator of the call. It's like the 
gateway is originating a new call.

But then, I think it more likely that the operator of the gateway would 
simply reject the call attempt as not having all the necessary information.

Mike


--part1_117.101ff569.29ef5d6d_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 4/17/02 4:39:02 AM Eastern Daylight Time, jh@lohi.eng.song.fi writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">&gt; There will be no PSTN Operator that take an untrusted From Header to
<BR>&gt; a calling party number --&gt; instead the PSTN operator will set up a
<BR>&gt; new calling party number that is network provided and trusted!
<BR>
<BR>to which number the network would set the calling party number? &nbsp;my sip
<BR>users can have any number of calling party numbers belonging to any
<BR>number of calling areas and soon even to any number of countries. &nbsp;
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>I believe the point was that the gateway (or whatever you want to call the thing that goes between the SIP and the PSTN signaling) would replace the untrusted identity in the "From" with a new calling party number, and that this new number would be one that designates the operator of the gateway itself, not one belonging to the originator of the call. It's like the gateway is originating a new call.
<BR>
<BR>But then, I think it more likely that the operator of the gateway would simply reject the call attempt as not having all the necessary information.
<BR>
<BR>Mike
<BR></FONT></HTML>

--part1_117.101ff569.29ef5d6d_boundary--

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



From daemon@ns.ietf.org  Wed Apr 17 19:48:26 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11213
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 19:48:26 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA27765
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 19:48:29 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA27487;
	Wed, 17 Apr 2002 19:40:08 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA27450
	for <sipping@ns.ietf.org>; Wed, 17 Apr 2002 19:40:04 -0400 (EDT)
Received: from pine.neustar.com (pine.neustar.com [209.173.57.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11071;
	Wed, 17 Apr 2002 19:40:01 -0400 (EDT)
Received: from chiimc01.il.neustar.com (chih650b-s3p2.il.neustar.com [209.173.57.65])
	by pine.neustar.com (8.11.0/8.11.0) with ESMTP id g3HNdYZ18819;
	Wed, 17 Apr 2002 18:39:34 -0500
Received: by chiimc01.il.neustar.com with Internet Mail Service (5.5.2653.19)
	id <JB0ZVK15>; Wed, 17 Apr 2002 18:39:29 -0500
Message-ID: <70565611B164D511957A001083FCDD5601870224@va02.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'sip@ietf.org'" <sip@ietf.org>, "'sipping@ietf.org'"
	 <sipping@ietf.org>
Date: Wed, 17 Apr 2002 18:39:28 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sipping] new I-Ds on privacy and identity
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


Sorry for the cross-post.

I've submitted some new Internet-Drafts on SIP privacy and identity. I hope
that these drafts can serve as a good starting point for discussion about
long-term cryptographic approaches to privacy and identity that will be
generally serviceable for the SIP protocol. As Dean's note to the SIP WG
list suggested, they are now available on softarmor.

Any comments on the drafts would be appreciated, and I hope we'll have a
chance to discuss them at the interim meeting.

The abstracts of the two drafts follow:

Privacy: This document defines new mechanisms for the Session Initiation
Protocol (SIP) in support of privacy. Specifically, guidelines are provided
for the creation of messages that do not divulge personal identity
information. A new "privacy service" logical role for intermediaries is
defined to answer some privacy requirements that user agents cannot satisfy
themselves. Finally, means are presented by which a user can request
particular functions from a privacy service. 

Identity: The existing mechanisms for expressing identity in the Session
Initiation Protocol do not currently permit an administrative domain to
securely verify the identity of the originator of a request. This document
recommends practices and conventions for authenticating end users, and
proposes a way to distribute secure authenticated identities within SIP
messages. 

Jon Peterson
NeuStar, Inc.

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



From daemon@ns.ietf.org  Wed Apr 17 20:25:27 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10907
	for <sipping-archive@odin.ietf.org>; Wed, 17 Apr 2002 19:30:18 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA26690
	for sipping-archive@odin.ietf.org; Wed, 17 Apr 2002 19:30:19 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA26229;
	Wed, 17 Apr 2002 19:22:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA26198
	for <sipping@ns.ietf.org>; Wed, 17 Apr 2002 19:22:02 -0400 (EDT)
Received: from imo-r01.mx.aol.com (imo-r01.mx.aol.com [152.163.225.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10701
	for <sipping@ietf.org>; Wed, 17 Apr 2002 19:22:00 -0400 (EDT)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r01.mx.aol.com (mail_out_v32.5.) id c.4b.1bd86b6b (25511);
	Wed, 17 Apr 2002 19:21:16 -0400 (EDT)
Message-ID: <4b.1bd86b6b.29ef5d6c@aol.com>
Date: Wed, 17 Apr 2002 19:21:16 EDT
Subject: Re: [Sipping] Screened From: and Privacy
To: oran@cisco.com, sipping@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_4b.1bd86b6b.29ef5d6c_boundary"
X-Mailer: AOL 6.0 for Windows US sub 10524
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


--part1_4b.1bd86b6b.29ef5d6c_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 4/17/02 8:13:25 AM Eastern Daylight Time, oran@cisco.com 
writes:


> <snip> 
> > > > These last two points have led Service Providers
> > > > to verify the From: field. They've been encouraged in this by 
> > > > the lack of any other field to communicate (2) passed the 
> > > > device which does authentication. As Dean correctly points 
> > > > out, using From: for information like (2) leads to the need 
> > > > to B2BUA everything for subscriber privacy (if you care about 
> > > > RFC2543 clients). 
> > > How does this follow as long as you define From: as only
> > > user-controlled? 
> > > 
> > The field is NOT 'user-controlled' if the user is forced to 
> > insert a specific piece of information. 
> Sure it is. I can still put anything I want in there. If I don't like
> the fact that the service provider rejects the call I go use somebody
> else. This is like saying the RequestURI: field isn't user controlled,
> because I may have subscribed to a free-phone service that only lets me
> call certain destinations that don't go through a PSTN gateway.
> 

I'm having a hard time understanding why the discussion keeps going around in 
circles. (Except that we're obviously talking about two completely different 
network models.)

Part of the clear requirement expressed before was that the service provider 
would be required to verify the identity of the originator to support 
government mandated tracing capability, etc. If you believe "From" is used 
for this, as some obviously did, then this field is mandatory, it must 
contain a valid identity, and the service provider verifies it. If a service 
provider rejects a call attempt when there is false information in this 
field, it is because they are required to reject it. Every other legitimate 
service provider will do the same.

I believe that this comment and discussion show the vast difference between 
your network model and others and difference of opinion on the requirements.

Mike


--part1_4b.1bd86b6b.29ef5d6c_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 4/17/02 8:13:25 AM Eastern Daylight Time, oran@cisco.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">&lt;snip&gt; 
<BR>&gt; &gt; &gt; These last two points have led Service Providers
<BR>&gt; &gt; &gt; to verify the From: field. They've been encouraged in this by 
<BR>&gt; &gt; &gt; the lack of any other field to communicate (2) passed the 
<BR>&gt; &gt; &gt; device which does authentication. As Dean correctly points 
<BR>&gt; &gt; &gt; out, using From: for information like (2) leads to the need 
<BR>&gt; &gt; &gt; to B2BUA everything for subscriber privacy (if you care about 
<BR>&gt; &gt; &gt; RFC2543 clients). 
<BR>&gt; &gt; How does this follow as long as you define From: as only
<BR>&gt; &gt; user-controlled? 
<BR>&gt; &gt; 
<BR>&gt; The field is NOT 'user-controlled' if the user is forced to 
<BR>&gt; insert a specific piece of information. 
<BR>Sure it is. I can still put anything I want in there. If I don't like
<BR>the fact that the service provider rejects the call I go use somebody
<BR>else. This is like saying the RequestURI: field isn't user controlled,
<BR>because I may have subscribed to a free-phone service that only lets me
<BR>call certain destinations that don't go through a PSTN gateway.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>I'm having a hard time understanding why the discussion keeps going around in circles. (Except that we're obviously talking about two completely different network models.)
<BR>
<BR>Part of the clear requirement expressed before was that the service provider would be required to verify the identity of the originator to support government mandated tracing capability, etc. If you believe "From" is used for this, as some obviously did, then this field is mandatory, it must contain a valid identity, and the service provider verifies it. If a service provider rejects a call attempt when there is false information in this field, it is because they are required to reject it. Every other legitimate service provider will do the same.
<BR>
<BR>I believe that this comment and discussion show the vast difference between your network model and others and difference of opinion on the requirements.
<BR>
<BR>Mike
<BR></FONT></HTML>

--part1_4b.1bd86b6b.29ef5d6c_boundary--

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



From daemon@ns.ietf.org  Thu Apr 18 01:30:53 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18069
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 01:30:53 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA24739
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 01:30:55 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA23156;
	Thu, 18 Apr 2002 01:19:43 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA23116
	for <sipping@ns.ietf.org>; Thu, 18 Apr 2002 01:19:40 -0400 (EDT)
Received: from lohi.eng.song.fi (lohi.eng.song.fi [195.10.149.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17998
	for <sipping@ietf.org>; Thu, 18 Apr 2002 01:19:36 -0400 (EDT)
From: jh@lohi.eng.song.fi
Received: from harjus.eng.song.fi ([195.10.149.20])
	by lohi.eng.song.fi with esmtp (Exim 3.34 #1 (Debian))
	id 16y4KX-0005Li-00; Thu, 18 Apr 2002 08:19:37 +0300
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15550.22376.949138.491783@harjus.eng.song.fi>
Date: Thu, 18 Apr 2002 08:19:36 +0300
To: "Zmolek, Andrew (Andrew)" <zmolek@avaya.com>
Cc: "Jesske, R" <R.Jesske@telekom.de>, <dean.willis@softarmor.com>,
        <sipping@ietf.org>
Subject: RE: [Sipping] Screened From: and Privacy
In-Reply-To: <EF4C65F18BE6464B8E9DF3C212B6B2930168E147@cof110avexu1.global.avaya.com>
References: <EF4C65F18BE6464B8E9DF3C212B6B2930168E147@cof110avexu1.global.avaya.com>
X-Mailer: VM 7.01 under Emacs 21.1.1
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Zmolek, Andrew (Andrew) writes:

 > > the uri of the from field MUST contain the calling 
 > > number, whereas the display string controls the 
 > > anonymity or that number.

 > Just because a display string might exist doesn't mean it's
 > necessarily the only thing presented to the end user at the far
 > end. Frankly, an implementer can choose to display as much or as
 > little as desired, use local policy, etc. And while the display
 > string may meet UAI requirements, it doesn't meet NAI without forcing
 > a choice.

seems that you didn't understand how things happen (which i have
explained already at least twice before).

if the user has given display string "Anonymous" and the call gets
routed to sip destination, i must implement b2bua and make also the from
uri anonymous.  if the call gets routed to pstn, i set the calling party
number blocking parameter.

 > Again, what is the benefit gained by forcing a choice between UAI and
 > NAI? I don't see it.

i don't understand how this relates to what i have said.  i simply want
to check that if someone uses my service, that someone is not spoofing
its calling party identity.  today the from field happens to be the only
way for the caller to tell what its identity is and if the caller wants
to reveal or not.

i still don't understand what this whole thread is all about and i still
haven't got a reply to my question what advantage rpid or some other new
header field would bring as compared to the current situation.

-- juha


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



From daemon@ns.ietf.org  Thu Apr 18 01:39:35 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18128
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 01:39:35 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA25420
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 01:39:37 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA24478;
	Thu, 18 Apr 2002 01:28:02 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA24447
	for <sipping@ns.ietf.org>; Thu, 18 Apr 2002 01:27:58 -0400 (EDT)
Received: from lohi.eng.song.fi (lohi.eng.song.fi [195.10.149.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18059
	for <sipping@ietf.org>; Thu, 18 Apr 2002 01:27:54 -0400 (EDT)
From: jh@lohi.eng.song.fi
Received: from harjus.eng.song.fi ([195.10.149.20])
	by lohi.eng.song.fi with esmtp (Exim 3.34 #1 (Debian))
	id 16y4Sa-0005Lr-00; Thu, 18 Apr 2002 08:27:56 +0300
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15550.22876.306576.896741@harjus.eng.song.fi>
Date: Thu, 18 Apr 2002 08:27:56 +0300
To: Mpierce1@aol.com
Cc: R.Jesske@telekom.de, dean.willis@softarmor.com, sipping@ietf.org
Subject: Re: AW: [Sipping] Screened From: and Privacy
In-Reply-To: <117.101ff569.29ef5d6d@aol.com>
References: <117.101ff569.29ef5d6d@aol.com>
X-Mailer: VM 7.01 under Emacs 21.1.1
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Mpierce1@aol.com writes:
 > 
 > I believe the point was that the gateway (or whatever you want to call the 
 > thing that goes between the SIP and the PSTN signaling) would replace the 
 > untrusted identity in the "From" with a new calling party number, and that 
 > this new number would be one that designates the operator of the gateway 
 > itself, not one belonging to the originator of the call. It's like the 
 > gateway is originating a new call.

this makes no sense, because as i have said many times before, the
caller is today using the from field to tell, what calling party number
it wants to use.  so the only thing that i can do is to verify that the
number indeed is one that the caller is entitled to use.  i cant replace
it with any "new calling party number".  if the number in the from uri
doesn't belong to the caller, the only thing i can do is to reject the
call.

and if the calling party doesn't have a telephone number in the from
uri, but a sip url like sip:jh@song.fi, then my sip/ss7 gw will replace
it with a number of the gateway itself when it forwards the call to the
pstn.  again, there is no need for any new header field that would be
more "trusted" than the from header.

-- juha


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



From daemon@optimus.ietf.org  Thu Apr 18 02:45:59 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27302
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 02:45:59 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA29079
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 02:46:02 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA28609;
	Thu, 18 Apr 2002 02:36:27 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA28581
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 02:36:24 -0400 (EDT)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27116
	for <sipping@ietf.org>; Thu, 18 Apr 2002 02:36:20 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g3I6ZYNo011453;
	Wed, 17 Apr 2002 23:35:34 -0700 (PDT)
Received: from localhost (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint)
	with ESMTP id ACX04026;
	Wed, 17 Apr 2002 23:35:51 -0700 (PDT)
Date: Wed, 17 Apr 2002 23:32:55 -0700 (Pacific Daylight Time)
From: Rohan Mahy <rohan@cisco.com>
To: sipping@ietf.org
cc: Brian Rosen <brian.rosen@marconi.com>, <mpierce1@aol.com>
Message-ID: <Pine.WNT.4.44.0204172323570.-394465@chorizo.rapidconvergence.com>
X-X-Sender: rmahy@imop.cisco.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Sipping] Cookies vs. State
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

two comments inline with ##

thanks,
-rohan

To: Brian.Rosen@marconi.com, sip@ietf.org
Subject: Re: [Sip] Cookies or State
From: Mpierce1@aol.com
Date: Wed, 17 Apr 2002 19:21:12 EDT
--------------------------------------------------------------------------------
Brian.Rosen@marconi.com writes:

There are two drafts that define how to save state in a UA for subsequent
use by a Proxy Server - State and Cookies.

State is part of the DCS work.  Cookies arose when IP assertions were
made against State.  Cookies attempted to get around the IP issues
by defining it as exactly like HTTP cookies.  To our consternation,
the same IP claims were then made against Cookies!

We need to get this capability.  The question is, should we
base it on State or Cookies?

In my personal (biased) opinion we are better off with Cookies.
If anyone did want to fight the IP claim, you would clearly
be better off with 75% same language as HTTP cookies.

## i vote for cookies because it is more generic than state.

I presume the reference for "Cookies" is still draft-willis-sip-cookies-00
of July 2001. I haven't seen any further discussion on this draft or
responses to the comments I submitted Nov 19. From that draft, it appears
there are significant security concerns with the use of "Cookies" in a
fashion similar to HTTP as proposed in this draft.

State would appear to have fewer security concerns if it is simply a value
stored in the UA for the beniefit of the proxy to fetch and use later. It
is presumed that the lack of a standard definition of this state value
would preclude its use by a different proxy than the one which stored it
(at least by a proxy of a different design).

It continues to escape me why it would not be better for the proxy to
simply stored this "state" in its own storage, rather than using every UA
as a distributed storage device. This concept seems to go back to the days
when memory was limited (the first telephone switch I was involved in
designing had 64k bytes of memory!) When one can buy 512M bytes of memory
for less than $100, this should no longer be an issue. The "state" draft
seems to indicate that the only reason for doing this is so that "proxy
servers can remain stateless for the duration of the call", but I have
never heard a reason why this is desirable. (Note that bis-09 defines the
term "call-stateful proxy".) Why don't we just admit that it is required
in some cases to keep the call state in the proxy and stop trying to
invent ways around this, all of which have security and performance
problems?

## the reason to allow a server to remain stateless allows servers to fail
## in the middle of a call without interruption of service.  this is
## arguably much easier/better/faster than requiring SIP servers to fully
## mirror call state across a cluster of servers.
## thx, -r

Mike



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



From daemon@optimus.ietf.org  Thu Apr 18 07:25:49 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01355
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 07:25:48 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA17648
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 07:25:51 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA16757;
	Thu, 18 Apr 2002 07:10:16 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA16727
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 07:10:12 -0400 (EDT)
Received: from zctfs063.europe.nortel.com (zctfs063.nortelnetworks.com [47.164.128.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01082
	for <sipping@ietf.org>; Thu, 18 Apr 2002 07:10:06 -0400 (EDT)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by zctfs063.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3IB7U029970;
	Thu, 18 Apr 2002 13:07:30 +0200 (MEST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JDW4N74P>; Thu, 18 Apr 2002 12:07:34 +0100
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7173@zwcwd00r.europe.nortel.com>
From: "Mark Watson"<mwatson@nortelnetworks.com>
To: "'jh@lohi.eng.song.fi'" <jh@lohi.eng.song.fi>,
        "Jesske, R"
	 <R.Jesske@telekom.de>
Cc: dean.willis@softarmor.com, sipping@ietf.org
Subject: RE: [Sipping] Screened From: and Privacy
Date: Thu, 18 Apr 2002 12:07:24 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E6C9.3803BD8E"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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_01C1E6C9.3803BD8E
Content-Type: text/plain


> Jesske, R writes:
> 
>  > How should it be verified when I'm anonymous. Then I need 
> some Information for the regulatory aspect!
> 
> your display string is "Anonymous", but the uri contains the your from
> address (see below).
> 

I had not understood this aspect of your service. This allows me to answer
your question about the advantage of RPID or some other Network Asserted
Identity.

If your client if SIP-compliant, then it will insert "Anonymous" in the
display string, and _something meaningless_ in the uri.

Your proxy can determine the client identity during the Authentication
process. The Network Asserted Identity field then allows the identity to be
communicated to the Gateway.

You would not need to verify the From: field, though I would understand why
if you still did. You would not require that it contained the user uri when
the user wanted privacy. 

Also, if the user has requested anonymity, and the session leaves your
network, towards a SIP endpoint, then rather than needing to insert a B2BUA
to remove the user's URI from the From: field, you just remove the Network
Asserted Identity field.

[If the *subscriber* requires anonymity, and the user has NOT requested it,
then you still need the B2BUA, IMO]

...Mark


>  > 2. The SIP user has a E.164@user URL then the Gateway maps 
> the URL direct to the Calling Party Number. (e.G. 
> +496151835940@telekom.de to CgPN=6151835940 with the 
> indication national or international). 
> 
> this is what we are using and once it is used, the provider needs to
> verify the number and after the verification is becomes trusted.
> 
> so i don't understand what additional value the rpid would bring.
> 
>  > If I'm anonymous I need the real identity within an other Header
>  > (RPID).The network will inset the real identity into the RPID with
>  > screen=yes. The RPID will be mapped to the PSTN as an restricted
>  > number, the restricted number is needed for some regulatory aspect
>  > (e.g. legal interception). But the normal user sees only 
> the contend
>  > of the From header.
> 
> you clearly didn't get my point.  the uri of the from field 
> MUST contain
> the calling number, whereas the display string controls the 
> anonymity or
> that number.
> 
> -- juha
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

------_=_NextPart_001_01C1E6C9.3803BD8E
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.2655.35">
<TITLE>RE: [Sipping] Screened From: and Privacy</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2>&gt; Jesske, R writes:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; How should it be verified when I'm =
anonymous. Then I need </FONT>
<BR><FONT SIZE=3D2>&gt; some Information for the regulatory =
aspect!</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; your display string is &quot;Anonymous&quot;, =
but the uri contains the your from</FONT>
<BR><FONT SIZE=3D2>&gt; address (see below).</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>I had not understood this aspect of your service. =
This allows me to answer your question about the advantage of RPID or =
some other Network Asserted Identity.</FONT></P>

<P><FONT SIZE=3D2>If your client if SIP-compliant, then it will insert =
&quot;Anonymous&quot; in the display string, and _something =
meaningless_ in the uri.</FONT></P>

<P><FONT SIZE=3D2>Your proxy can determine the client identity during =
the Authentication process. The Network Asserted Identity field then =
allows the identity to be communicated to the Gateway.</FONT></P>

<P><FONT SIZE=3D2>You would not need to verify the From: field, though =
I would understand why if you still did. You would not require that it =
contained the user uri when the user wanted privacy. </FONT></P>

<P><FONT SIZE=3D2>Also, if the user has requested anonymity, and the =
session leaves your network, towards a SIP endpoint, then rather than =
needing to insert a B2BUA to remove the user's URI from the From: =
field, you just remove the Network Asserted Identity field.</FONT></P>

<P><FONT SIZE=3D2>[If the *subscriber* requires anonymity, and the user =
has NOT requested it, then you still need the B2BUA, IMO]</FONT>
</P>

<P><FONT SIZE=3D2>...Mark</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&gt;&nbsp; &gt; 2. The SIP user has a E.164@user URL =
then the Gateway maps </FONT>
<BR><FONT SIZE=3D2>&gt; the URL direct to the Calling Party Number. =
(e.G. </FONT>
<BR><FONT SIZE=3D2>&gt; +496151835940@telekom.de to CgPN=3D6151835940 =
with the </FONT>
<BR><FONT SIZE=3D2>&gt; indication national or international). </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; this is what we are using and once it is used, =
the provider needs to</FONT>
<BR><FONT SIZE=3D2>&gt; verify the number and after the verification is =
becomes trusted.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; so i don't understand what additional value the =
rpid would bring.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; If I'm anonymous I need the real =
identity within an other Header</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; (RPID).The network will inset the =
real identity into the RPID with</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; screen=3Dyes. The RPID will be =
mapped to the PSTN as an restricted</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; number, the restricted number is =
needed for some regulatory aspect</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; (e.g. legal interception). But the =
normal user sees only </FONT>
<BR><FONT SIZE=3D2>&gt; the contend</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; of the From header.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; you clearly didn't get my point.&nbsp; the uri =
of the from field </FONT>
<BR><FONT SIZE=3D2>&gt; MUST contain</FONT>
<BR><FONT SIZE=3D2>&gt; the calling number, whereas the display string =
controls the </FONT>
<BR><FONT SIZE=3D2>&gt; anonymity or</FONT>
<BR><FONT SIZE=3D2>&gt; that number.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -- juha</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 sip</FONT>
<BR><FONT SIZE=3D2>&gt; Use sip@ietf.org for new developments of core =
SIP</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E6C9.3803BD8E--

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



From daemon@optimus.ietf.org  Thu Apr 18 07:38:46 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01588
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 07:38:45 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA18728
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 07:38:48 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA17529;
	Thu, 18 Apr 2002 07:24:34 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA17421
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 07:24:27 -0400 (EDT)
Received: from lohi.eng.song.fi (lohi.eng.song.fi [195.10.149.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01330
	for <sipping@ietf.org>; Thu, 18 Apr 2002 07:24:24 -0400 (EDT)
From: jh@lohi.eng.song.fi
Received: from harjus.eng.song.fi ([195.10.149.20])
	by lohi.eng.song.fi with esmtp (Exim 3.34 #1 (Debian))
	id 16yA1V-0005Xh-00; Thu, 18 Apr 2002 14:24:21 +0300
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15550.44261.129134.991771@harjus.eng.song.fi>
Date: Thu, 18 Apr 2002 14:24:21 +0300
To: "Mark Watson"<mwatson@nortelnetworks.com>
Cc: "Jesske, R"
	 <R.Jesske@telekom.de>, dean.willis@softarmor.com,
        sipping@ietf.org
Subject: RE: [Sipping] Screened From: and Privacy
In-Reply-To: <A3C2399B2FACD411A54200508BE39C74054F7173@zwcwd00r.europe.nortel.com>
References: <A3C2399B2FACD411A54200508BE39C74054F7173@zwcwd00r.europe.nortel.com>
X-Mailer: VM 7.01 under Emacs 21.1.1
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Mark Watson writes:

 > If your client if SIP-compliant, then it will insert "Anonymous" in the
 > display string, and _something meaningless_ in the uri.

none of the UAs that i have seen inserts something meaningless in
the from uri if the user sets the display string is anonymous.  it is
"should" in the spec and looks like every UA implementer allows the
user to determine what to do, which is a good thing.

 > Your proxy can determine the client identity during the Authentication
 > process. The Network Asserted Identity field then allows the identity to be
 > communicated to the Gateway.

if you mean that the proxy can verify who the user is, sure, it does
that via digest authentication.  however, that doesn't mean that the
proxy would know what from uri the user would like to use, because as i
have again said far too many times already, a single user can have any
number of valid from uris.

 > You would not need to verify the From: field, though I would understand why
 > if you still did. You would not require that it contained the user uri when
 > the user wanted privacy. 

see above.

-- juha


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



From daemon@optimus.ietf.org  Thu Apr 18 08:00:20 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01925
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 08:00:20 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA19819
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 08:00:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA19033;
	Thu, 18 Apr 2002 07:45:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA19002
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 07:45:00 -0400 (EDT)
Received: from zctfs063.europe.nortel.com (zctfs063.nortelnetworks.com [47.164.128.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01633
	for <sipping@ietf.org>; Thu, 18 Apr 2002 07:44:56 -0400 (EDT)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by zctfs063.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3IBgI006178;
	Thu, 18 Apr 2002 13:42:18 +0200 (MEST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JDW4N9V8>; Thu, 18 Apr 2002 12:42:22 +0100
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7175@zwcwd00r.europe.nortel.com>
From: "Mark Watson"<mwatson@nortelnetworks.com>
To: "'jh@lohi.eng.song.fi'" <jh@lohi.eng.song.fi>
Cc: "Jesske, R" <R.Jesske@telekom.de>, dean.willis@softarmor.com,
        sipping@ietf.org
Subject: RE: [Sipping] Screened From: and Privacy
Date: Thu, 18 Apr 2002 12:42:20 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E6CD.3D9C3F7E"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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_01C1E6CD.3D9C3F7E
Content-Type: text/plain


> 
>  > If your client if SIP-compliant, then it will insert 
> "Anonymous" in the
>  > display string, and _something meaningless_ in the uri.
> 
> none of the UAs that i have seen inserts something meaningless in
> the from uri if the user sets the display string is anonymous.  it is
> "should" in the spec and looks like every UA implementer allows the
> user to determine what to do, which is a good thing.
>

OK, you know more about the clients out there than I do. But I would expect
clients to have a simple means for a user to indicate that a given session
should be anonymous - a special key, check-box, whatever, depending on the
form-factor/UI. I would be surprised if the UA still included the real uri
if the User checked this box.

It does not surprise me that UAs _allow_ you to send Anonymous along with
your URI.

>  > Your proxy can determine the client identity during the 
> Authentication
>  > process. The Network Asserted Identity field then allows 
> the identity to be
>  > communicated to the Gateway.
> 
> if you mean that the proxy can verify who the user is, sure, it does
> that via digest authentication.  however, that doesn't mean that the
> proxy would know what from uri the user would like to use, 
> because as i
> have again said far too many times already, a single user can have any
> number of valid from uris.
> 

Yes, 3GPP has this requirement too. But it is a slightly separate question
from the NAI itself. If we follow the SHOULD in the SIP specification about
the From uri being meaningless when the user requests privacy, then another
field is needed to allow the user to choose which identity will be used for
the Network Asserted Identity out of a particular set.

...Mark 

------_=_NextPart_001_01C1E6CD.3D9C3F7E
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.2655.35">
<TITLE>RE: [Sipping] Screened From: and Privacy</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; If your client if SIP-compliant, =
then it will insert </FONT>
<BR><FONT SIZE=3D2>&gt; &quot;Anonymous&quot; in the</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; display string, and _something =
meaningless_ in the uri.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; none of the UAs that i have seen inserts =
something meaningless in</FONT>
<BR><FONT SIZE=3D2>&gt; the from uri if the user sets the display =
string is anonymous.&nbsp; it is</FONT>
<BR><FONT SIZE=3D2>&gt; &quot;should&quot; in the spec and looks like =
every UA implementer allows the</FONT>
<BR><FONT SIZE=3D2>&gt; user to determine what to do, which is a good =
thing.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
</P>

<P><FONT SIZE=3D2>OK, you know more about the clients out there than I =
do. But I would expect clients to have a simple means for a user to =
indicate that a given session should be anonymous - a special key, =
check-box, whatever, depending on the form-factor/UI. I would be =
surprised if the UA still included the real uri if the User checked =
this box.</FONT></P>

<P><FONT SIZE=3D2>It does not surprise me that UAs _allow_ you to send =
Anonymous along with your URI.</FONT>
</P>

<P><FONT SIZE=3D2>&gt;&nbsp; &gt; Your proxy can determine the client =
identity during the </FONT>
<BR><FONT SIZE=3D2>&gt; Authentication</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; process. The Network Asserted =
Identity field then allows </FONT>
<BR><FONT SIZE=3D2>&gt; the identity to be</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; communicated to the Gateway.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; if you mean that the proxy can verify who the =
user is, sure, it does</FONT>
<BR><FONT SIZE=3D2>&gt; that via digest authentication.&nbsp; however, =
that doesn't mean that the</FONT>
<BR><FONT SIZE=3D2>&gt; proxy would know what from uri the user would =
like to use, </FONT>
<BR><FONT SIZE=3D2>&gt; because as i</FONT>
<BR><FONT SIZE=3D2>&gt; have again said far too many times already, a =
single user can have any</FONT>
<BR><FONT SIZE=3D2>&gt; number of valid from uris.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>Yes, 3GPP has this requirement too. But it is a =
slightly separate question from the NAI itself. If we follow the SHOULD =
in the SIP specification about the From uri being meaningless when the =
user requests privacy, then another field is needed to allow the user =
to choose which identity will be used for the Network Asserted Identity =
out of a particular set.</FONT></P>

<P><FONT SIZE=3D2>...Mark </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E6CD.3D9C3F7E--

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



From daemon@optimus.ietf.org  Thu Apr 18 08:15:46 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02363
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 08:15:45 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA20947
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 08:15:48 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA20226;
	Thu, 18 Apr 2002 08:01:47 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA20186
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 08:01:42 -0400 (EDT)
Received: from lohi.eng.song.fi (lohi.eng.song.fi [195.10.149.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02094
	for <sipping@ietf.org>; Thu, 18 Apr 2002 08:01:38 -0400 (EDT)
From: jh@lohi.eng.song.fi
Received: from harjus.eng.song.fi ([195.10.149.20])
	by lohi.eng.song.fi with esmtp (Exim 3.34 #1 (Debian))
	id 16yAbS-0005YQ-00; Thu, 18 Apr 2002 15:01:30 +0300
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15550.46490.819181.812793@harjus.eng.song.fi>
Date: Thu, 18 Apr 2002 15:01:30 +0300
To: "Mark Watson"<mwatson@nortelnetworks.com>
Cc: "Jesske, R" <R.Jesske@telekom.de>, dean.willis@softarmor.com,
        sipping@ietf.org
Subject: RE: [Sipping] Screened From: and Privacy
In-Reply-To: <A3C2399B2FACD411A54200508BE39C74054F7175@zwcwd00r.europe.nortel.com>
References: <A3C2399B2FACD411A54200508BE39C74054F7175@zwcwd00r.europe.nortel.com>
X-Mailer: VM 7.01 under Emacs 21.1.1
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Mark Watson writes:

 > Yes, 3GPP has this requirement too. But it is a slightly separate question
 > from the NAI itself. If we follow the SHOULD in the SIP specification about
 > the From uri being meaningless when the user requests privacy, then another
 > field is needed to allow the user to choose which identity will be used for
 > the Network Asserted Identity out of a particular set.

you could define another header field for that purpose, but in the
meanwhile, i need to be able to run my sip service with CURRENT UAs,
proxies, and sip/ss7 gws all of which today support the from uri +
display string trick as i have described.  since my basic rule is "if it
not broken, don't fix it", i'm not interested to change the current
working practice just for the sake of it.

-- juha


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



From daemon@optimus.ietf.org  Thu Apr 18 08:17:19 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02528
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 08:17:19 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA21058
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 08:17:22 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA20079;
	Thu, 18 Apr 2002 08:01:08 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA20036
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 08:01:04 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02059;
	Thu, 18 Apr 2002 08:01:00 -0400 (EDT)
Message-Id: <200204181201.IAA02059@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Thu, 18 Apr 2002 08:01:00 -0400
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-deaf-req-01.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

--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		: User Requirements for SIP in support of deaf, hard of 
                          hearing and speech-impaired individuals
	Author(s)	: N. Charlton et al.
	Filename	: draft-ietf-sipping-deaf-req-01.txt
	Pages		: 13
	Date		: 17-Apr-02
	
This document aims to present a set of SIP user requirements that
support communications for deaf, hard of hearing and speech-impaired
individuals. These user requirements address the current difficulties
of deaf, hard of hearing and speech-impaired individuals in using
communications facilities, while acknowledging the multi-functional
potential of SIP-based communications.
A number of issues related to these user requirements are further
raised in this document.
Also included are some real world scenarios and some technical
requirements to show the robustness of these requirements on a
concept-level.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-deaf-req-01.txt

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-sipping-deaf-req-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-deaf-req-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:	<20020417151748.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-deaf-req-01.txt

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

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

--OtherAccess--

--NextPart--



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



From daemon@optimus.ietf.org  Thu Apr 18 08:34:22 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02959
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 08:34:21 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA22213
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 08:34:24 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA21204;
	Thu, 18 Apr 2002 08:19:42 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA21174
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 08:19:38 -0400 (EDT)
Received: from zctfs063.europe.nortel.com (zctfs063.nortelnetworks.com [47.164.128.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02586
	for <sipping@ietf.org>; Thu, 18 Apr 2002 08:19:30 -0400 (EDT)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zctfs063.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3ICIq023505;
	Thu, 18 Apr 2002 14:18:52 +0200 (MEST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3ICICG24180;
	Thu, 18 Apr 2002 13:18:12 +0100 (BST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JDW43AZL>; Thu, 18 Apr 2002 13:18:54 +0100
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7178@zwcwd00r.europe.nortel.com>
From: "Mark Watson"<mwatson@nortelnetworks.com>
To: "'Rosen, Brian'" <Brian.Rosen@marconi.com>,
        "'Alan Johnston'"
	 <alan.johnston@wcom.com>,
        "'David R. Oran'" <oran@cisco.com>,
        "'Dean Willis'" <dean.willis@softarmor.com>,
        "'Sipping (E-mail)'"
	 <sipping@ietf.org>
Subject: RE: [Sipping] Screened From: and Privacy
Date: Thu, 18 Apr 2002 13:18:52 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E6D3.340787E2"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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

Answers to Brians questions: yes, yes and yes.

Brian wrote:
> I  keep wishing we could slice and dice this down to some things we
> agree on and a short list of things we don't, but it doesn't 
> seem to be
> happening.
> 
> I'll try again.
> 
> Can we assume that Mark is correct about SUBSCRIBER (he who pays) as
> opposed to USER rights?   I don't like it, but I conclude we
> are stuck with it.
> 

The subscriber legally contracts for the service - probably best to leave
payment out of it.

> Can we assume a Network Asserted Identity is a requirement?  
> I actually
> don't agree with all of Mark's proposed requirements yet, but I think
> we HAVE to have it.
> 

My requirements were a straw man - I only have a strong view on the first
two anyway.

> Can we possibly agree that an anonymizing B2BUA, provided by a service
> provider, would be the only way to achieve real privacy?  I 
> don't think any
> of the short cuts like messing with this header or that 
> header will do.
> 

The level of privacy needed to meet regulations, user requirements, service
requirements, common sense etc. is in my view tbd. Different services will
be applicable in different circumstances & we don't have to standardise one
single privacy service now (or ever).

I wasn't arguing for a 'short cut' of header modification, just that From/To
modification was *one aspect* that any privacy service would need to
provide.

> The only practical problems I am aware of with an anonymizing
> B2BUA are crypto and DOS. In general, you can't use any kind of crypto
> unless 
> the B2BUA has the right secrets.  I vaguely remember some research on
> anonymous crypto, but in general, it isn't interesting to be 
> secure and 
> anonymous completely. You could arrange security against outside 
> snooping as long as the service	provider was part of 
> the trust domain 
> (which means the B2BUA could be trusted) and still be anonymous. 
> 
> If we had a reasonable network asserted identity, I think that is
> sufficient to avoid the kinds of problems Christian pointed out
> with anonymizers.  It's not truly anonymous - the SP knows who
> called.
> 
> Brian
> 
>  
> 
> 
> -----Original Message-----
> From: Mark Watson [mailto:mwatson@nortelnetworks.com]
> Sent: Wednesday, April 17, 2002 12:38 PM
> To: 'Alan Johnston'; 'David R. Oran'; 'Dean Willis'; 'Sipping 
> (E-mail)'
> Subject: RE: [Sipping] Screened From: and Privacy
> 
> 
> So, there is clearly disagreement on whether screened From: 
> is a BAD THING
> or a GOOD THING. 
> I really feel that trying to argue that one side is RIGHT and 
> the other
> WRONG will not get us anywhere, and we should just work with 
> the situation
> as it is. I've just been trying to point out why some people 
> have taken the
> screening route.
> Two things are independent of this, though: 
> 1) The need for Network Asserted Identity 
> 2) The need for anonymity services 
> For the example service Juha gave, (1) is the only thing 
> which would allow
> him to turn off his From screening, so it is a little 
> churlish to argue that
> From screening is WRONG when there is presently no alternative.
> Regards, 
> Mark 
> > -----Original Message----- 
> > From: Alan Johnston [mailto:alan.johnston@wcom.com] 
> > Sent: 17 April 2002 17:14 
> > To: Watson, Mark [MDN05:EP10:EXCH]; 'David R. Oran'; 'Dean Willis'; 
> > 'Sipping (E-mail)' 
> > Subject: RE: [Sipping] Screened From: and Privacy 
> > 
> > 
> > 
> > Mark wrote: 
> > 
> > >I was trying to explain why the text in the SIP 
> > specification may have 
> > led Service 
> > >Providers to believe that they ought to verify the From: 
> > field. You are 
> > arguing this is 
> > >a wrong interpretation, but independent of that, I don't 
> think people 
> > who have 
> > >interpreted the text that way are being unreasonable. 
> > 
> > I must have missed the 4xx From Header Incorrect response 
> code which 
> > must be somewhere in bis for this verification of From 
> > identity to work 
> > :-) 
> > 
> > I think this interpretation is totally unreasonable and should be 
> > dispelled right now for what it is - a mistake. 
> > 
> > Service providers must read Internet specifications very 
> > carefully - the 
> > Internet and its protocols were not designed for them 
> (fortunately). 
> > 
> > Thanks, 
> > Alan Johnston 
> > WorldCom 
> > sip:alan@siptest.wcom.com 
> > 
> > 
> 

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Sipping] Screened From: and Privacy</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Answers to Brians questions: yes, yes and yes.</FONT>
</P>

<P><FONT SIZE=3D2>Brian wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; I&nbsp; keep wishing we could slice and dice =
this down to some things we</FONT>
<BR><FONT SIZE=3D2>&gt; agree on and a short list of things we don't, =
but it doesn't </FONT>
<BR><FONT SIZE=3D2>&gt; seem to be</FONT>
<BR><FONT SIZE=3D2>&gt; happening.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I'll try again.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Can we assume that Mark is correct about =
SUBSCRIBER (he who pays) as</FONT>
<BR><FONT SIZE=3D2>&gt; opposed to USER rights?&nbsp;&nbsp; I don't =
like it, but I conclude we</FONT>
<BR><FONT SIZE=3D2>&gt; are stuck with it.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>The subscriber legally contracts for the service - =
probably best to leave payment out of it.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; Can we assume a Network Asserted Identity is a =
requirement?&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; I actually</FONT>
<BR><FONT SIZE=3D2>&gt; don't agree with all of Mark's proposed =
requirements yet, but I think</FONT>
<BR><FONT SIZE=3D2>&gt; we HAVE to have it.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>My requirements were a straw man - I only have a =
strong view on the first two anyway.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; Can we possibly agree that an anonymizing B2BUA, =
provided by a service</FONT>
<BR><FONT SIZE=3D2>&gt; provider, would be the only way to achieve real =
privacy?&nbsp; I </FONT>
<BR><FONT SIZE=3D2>&gt; don't think any</FONT>
<BR><FONT SIZE=3D2>&gt; of the short cuts like messing with this header =
or that </FONT>
<BR><FONT SIZE=3D2>&gt; header will do.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

<P><FONT SIZE=3D2>The level of privacy needed to meet regulations, user =
requirements, service requirements, common sense etc. is in my view =
tbd. Different services will be applicable in different circumstances =
&amp; we don't have to standardise one single privacy service now (or =
ever).</FONT></P>

<P><FONT SIZE=3D2>I wasn't arguing for a 'short cut' of header =
modification, just that From/To modification was *one aspect* that any =
privacy service would need to provide.</FONT></P>

<P><FONT SIZE=3D2>&gt; The only practical problems I am aware of with =
an anonymizing</FONT>
<BR><FONT SIZE=3D2>&gt; B2BUA are crypto and DOS. In general, you can't =
use any kind of crypto</FONT>
<BR><FONT SIZE=3D2>&gt; unless </FONT>
<BR><FONT SIZE=3D2>&gt; the B2BUA has the right secrets.&nbsp; I =
vaguely remember some research on</FONT>
<BR><FONT SIZE=3D2>&gt; anonymous crypto, but in general, it isn't =
interesting to be </FONT>
<BR><FONT SIZE=3D2>&gt; secure and </FONT>
<BR><FONT SIZE=3D2>&gt; anonymous completely. You could arrange =
security against outside </FONT>
<BR><FONT SIZE=3D2>&gt; snooping as long as the =
service&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; provider was part of =
</FONT>
<BR><FONT SIZE=3D2>&gt; the trust domain </FONT>
<BR><FONT SIZE=3D2>&gt; (which means the B2BUA could be trusted) and =
still be anonymous. </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; If we had a reasonable network asserted =
identity, I think that is</FONT>
<BR><FONT SIZE=3D2>&gt; sufficient to avoid the kinds of problems =
Christian pointed out</FONT>
<BR><FONT SIZE=3D2>&gt; with anonymizers.&nbsp; It's not truly =
anonymous - the SP knows who</FONT>
<BR><FONT SIZE=3D2>&gt; called.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Brian</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Mark Watson [<A =
HREF=3D"mailto:mwatson@nortelnetworks.com">mailto:mwatson@nortelnetworks=
.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Wednesday, April 17, 2002 12:38 PM</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'Alan Johnston'; 'David R. Oran'; 'Dean =
Willis'; 'Sipping </FONT>
<BR><FONT SIZE=3D2>&gt; (E-mail)'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [Sipping] Screened From: and =
Privacy</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; So, there is clearly disagreement on whether =
screened From: </FONT>
<BR><FONT SIZE=3D2>&gt; is a BAD THING</FONT>
<BR><FONT SIZE=3D2>&gt; or a GOOD THING. </FONT>
<BR><FONT SIZE=3D2>&gt; I really feel that trying to argue that one =
side is RIGHT and </FONT>
<BR><FONT SIZE=3D2>&gt; the other</FONT>
<BR><FONT SIZE=3D2>&gt; WRONG will not get us anywhere, and we should =
just work with </FONT>
<BR><FONT SIZE=3D2>&gt; the situation</FONT>
<BR><FONT SIZE=3D2>&gt; as it is. I've just been trying to point out =
why some people </FONT>
<BR><FONT SIZE=3D2>&gt; have taken the</FONT>
<BR><FONT SIZE=3D2>&gt; screening route.</FONT>
<BR><FONT SIZE=3D2>&gt; Two things are independent of this, though: =
</FONT>
<BR><FONT SIZE=3D2>&gt; 1) The need for Network Asserted Identity =
</FONT>
<BR><FONT SIZE=3D2>&gt; 2) The need for anonymity services </FONT>
<BR><FONT SIZE=3D2>&gt; For the example service Juha gave, (1) is the =
only thing </FONT>
<BR><FONT SIZE=3D2>&gt; which would allow</FONT>
<BR><FONT SIZE=3D2>&gt; him to turn off his From screening, so it is a =
little </FONT>
<BR><FONT SIZE=3D2>&gt; churlish to argue that</FONT>
<BR><FONT SIZE=3D2>&gt; From screening is WRONG when there is presently =
no alternative.</FONT>
<BR><FONT SIZE=3D2>&gt; Regards, </FONT>
<BR><FONT SIZE=3D2>&gt; Mark </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; -----Original Message----- </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; From: Alan Johnston [<A =
HREF=3D"mailto:alan.johnston@wcom.com">mailto:alan.johnston@wcom.com</A>=
] </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sent: 17 April 2002 17:14 </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; To: Watson, Mark [MDN05:EP10:EXCH]; 'David =
R. Oran'; 'Dean Willis'; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; 'Sipping (E-mail)' </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Subject: RE: [Sipping] Screened From: and =
Privacy </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Mark wrote: </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;I was trying to explain why the text =
in the SIP </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; specification may have </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; led Service </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;Providers to believe that they ought =
to verify the From: </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; field. You are </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; arguing this is </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;a wrong interpretation, but =
independent of that, I don't </FONT>
<BR><FONT SIZE=3D2>&gt; think people </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; who have </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;interpreted the text that way are =
being unreasonable. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I must have missed the 4xx From Header =
Incorrect response </FONT>
<BR><FONT SIZE=3D2>&gt; code which </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; must be somewhere in bis for this =
verification of From </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; identity to work </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; :-) </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I think this interpretation is totally =
unreasonable and should be </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; dispelled right now for what it is - a =
mistake. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Service providers must read Internet =
specifications very </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; carefully - the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Internet and its protocols were not =
designed for them </FONT>
<BR><FONT SIZE=3D2>&gt; (fortunately). </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Thanks, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Alan Johnston </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; WorldCom </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; sip:alan@siptest.wcom.com </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E6D3.340787E2--

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



From daemon@optimus.ietf.org  Thu Apr 18 10:08:33 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06851
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 10:08:33 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA28693
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 10:08:36 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA27057;
	Thu, 18 Apr 2002 09:43:46 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA26953
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 09:43:39 -0400 (EDT)
Received: from imo-r06.mx.aol.com (imo-r06.mx.aol.com [152.163.225.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05801
	for <sipping@ietf.org>; Thu, 18 Apr 2002 09:43:35 -0400 (EDT)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r06.mx.aol.com (mail_out_v32.5.) id c.b2.a239876 (3702);
	Thu, 18 Apr 2002 09:42:52 -0400 (EDT)
Message-ID: <b2.a239876.29f0275c@aol.com>
Date: Thu, 18 Apr 2002 09:42:52 EDT
To: rohan@cisco.com, sipping@ietf.org
CC: brian.rosen@marconi.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_b2.a239876.29f0275c_boundary"
X-Mailer: AOL 6.0 for Windows US sub 10524
Subject: [Sipping] Re: Cookies vs. State
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


--part1_b2.a239876.29f0275c_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 4/18/02 2:35:58 AM Eastern Daylight Time, rohan@cisco.com 
writes:


> ## the reason to allow a server to remain stateless allows servers to fail
> ## in the middle of a call without interruption of service.  this is
> ## arguably much easier/better/faster than requiring SIP servers to fully
> ## mirror call state across a cluster of servers.
> ## thx, -r
> 

In a message dated 4/17/02 9:06:48 PM Eastern Daylight Time, 
ssaha@longboard.com writes:


> The concern for being stateless is not memory but HA. What happens when a 
> Call statefull proxy dies? How do you reconstruct states after recovery? 
> Distributing state to edge lowers the risk in failure conditions. If a US 
> fails, it only affect that very UA none else [when UA is dead - the call is 
> anyway lost]. Providing HA a statefull proxy is not easy job either. 
> 

Yes, I presumed that someone would use the above as the reason for storing 
state (whether as "Cookie" or "State") in the UA. That's why my original 
e-mail stated that "It is presumed that the lack of a standard definition of 
this state value would preclude its use by a different proxy than the one 
which stored it (at least by a proxy of a different design)." Another proxy 
could take over for a failed one only if they had a common understanding of 
the contents of the "State" or "Cookie". I don't see this ever happening 
between proxies of a different design, therefore, I think it is wrong to use 
it. If you can standardize the contents of either, that is a different story.

Further, as Dean wrote: 'Both approaches leave the format of the "hunk" open 
-- it could be cryptographically protected, just a hash value matching a 
table stored on the proxy, or almost anything else.' It seems to me that any 
of these security measures would prevent another proxy from being able to 
understand the State or Cookie anyway, unless they share keys. Wouldn't that 
be as hard as sharing states?

State is clearly less of a security problem than Cookie. As noted in the 
"State" draft, 'Cookies typically persist across sessions'. "State", on the 
other hand, clearly only exists until the next state change, i.e., when a 
call ends, the state disappears (or goes to idle). Cookies, on the other hand 
may persist longer and the indication in previous discussions was that they 
may contain more than just "state" information and may do other things like 
cause new calls to be initiated. 

As Dean noted: "I also believe the security concern is SLIGHTLY less urgent 
than in HTTP. As I understand it, both state and cookie drafts indicate a 
substantially shorter lifetime for the token. In the case of state, the 
lifetime is the duration of the current dialog. In the case of cookie, it's 
the current dialog plus any dialog resulting from redirection or referral of 
the original dialog. 
HTTP cookies, on the other hand, persist relatively indefiitely and may be 
extracted by any server in the domain of the cookie during any HTTP 
interaction with said server for the duraction of the cookie."

I addressed this issue of Cookie persistance in my November 19 comments which 
I will repeat below. The only way that "Cookie" can be allowed is if it must 
be erased at the end of a call and if it can not be read by any proxy other 
than the one setting up the call (or by a limited set which may take over for 
another proxy in the case of proxy failure and which the UA can verify is 
allowed to handle the call further). Any other use would be a serious 
security problem and probably illegal in some places. A device must be 
considered non-compliant if it does not erase the "Cookie".

------------------------------------------------------------------------------

-----------------------------------------------------------
Comments on draft-willis-sip-cookies-00:

This draft provides a good base-line for definition of a SIP-cookie 
functionality, derived from RFC 2109.

Some comments/observations:

1. The proposed SIP-cookie borrows heavily from the definition/procedures of 
cookies for HTTP (RFC 2109). Given the known possibility of abuse of cookies 
in HTTP, it is very important that the avoidance of such abuse be considered 
for SIP.

2. Currently, if one disables all cookies in their browser, certain web-based 
applications such as on-line shopping are not usable, but this does not 
affect access to most web-browsing. If the support of SIP cookies is 
essential to the provision of regular telephone type service (e.g., Call 
Transfer), a user would not be able to disable cookies, thereby exposing 
themselves to possible abuse. The draft is written as if a User Agent is 
required to store cookies, that is, can not disable them as a web-browser can 
today.

3. Section 8, Security Considerations states: "Cookies in SIP, unlike cookies 
in HTTP, are discarded at the conclusion of a session." It is not clear why 
this is stated, since RFC 2109 allows the User Agent to discard cookies. It 
states that "When a user agent terminates execution, it should let the user 
discard all state information." It seems that the common browsers do not 
choose to provide the user with this option to discard cookies upon exit, 
probably since the companies that produce them want to use these persistent 
cookies as much as any other companies. If these same companies implement SIP 
functionality, it can be expected that they will choose to not discard 
SIP-cookies at the conclusion of a telephone call either.

4. As I understand the draft, it requires a user agent to store cookies, and 
seems to make a strong objective that it must store at least 10 cookies of at 
least 4096 bytes each, and that it must include all stored cookies in every 
subsequent message it sends associated with a call. Since other draft 
proposals result in sending a very large number of messages for some 
capabilities, especially those associated with providing security, it would 
appear that this results in huge amounts of data being sent. It is obvious 
this can not lead to an efficient telephone service.

5. One could easily envision services that would benefit from retaining 
SIP-cookies after completion of a call in order to support a new call.

6. This draft appears to be one more admission that processing of many (maybe 
all) telephone type applications requires that the entity controlling the 
service have knowledge of the "state" of the call. In an increasing number of 
defined applications, it is a proxy that controls the service (not the user 
agent as perhaps originally envisioned) and that proxy needs to "remember" 
the state of the call and service. RFC 2543 included the concept of a 
"stateful proxy", which maintains the state of a transaction (until a 
definitive response is received). The proposed revision of SIP further 
refines this definition of "stateful proxy" and then introduces the notion of 
a "call stateful (proxy)" which maintains the state "from the initiating 
INVITE to the terminating BYE", but it does not describe in detail the 
operation of a "call stateful proxy".

For the control of telephone services using SIP beyond the simple, basic 
call, it appears that the time has come to admit that these services require 
a "call stateful proxy" and not to depend on storing of "cookies" in user 
agents as a substitute.

7. For some yet to be defined SIP-provided services, this cookie mechanism 
will probably be essential. In line with the recent draft for "SIP Change 
Process", draft-tsvarea-sipchange-00.txt, a definition of the requirements 
needs to be submitted to SIPPING. This would identify the specific class of 
services/capabilities that require the addition of a SIP-cookie. It should be 
intended for special cases (equivalent to the shopping cart example in RFC 
2109), not support for everyday telephone services.

Mike Pierce
Artel



--part1_b2.a239876.29f0275c_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 4/18/02 2:35:58 AM Eastern Daylight Time, rohan@cisco.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">## the reason to allow a server to remain stateless allows servers to fail
<BR>## in the middle of a call without interruption of service. &nbsp;this is
<BR>## arguably much easier/better/faster than requiring SIP servers to fully
<BR>## mirror call state across a cluster of servers.
<BR>## thx, -r
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>In a message dated 4/17/02 9:06:48 PM Eastern Daylight Time, ssaha@longboard.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">The concern for being stateless is not memory but HA. What happens when a Call statefull proxy dies? How do you reconstruct states after recovery? Distributing state to edge lowers the risk in failure conditions. If a US fails, it only affect that very UA none else [when UA is dead - the call is anyway lost]. Providing HA a statefull proxy is not easy job either. 
<BR></BLOCKQUOTE>
<BR>
<BR>Yes, I presumed that someone would use the above as the reason for storing state (whether as "Cookie" or "State") in the UA. That's why my original e-mail stated that "It is presumed that the lack of a standard definition of this state value would preclude its use by a different proxy than the one which stored it (at least by a proxy of a different design)." Another proxy could take over for a failed one only if they had a common understanding of the contents of the "State" or "Cookie". I don't see this ever happening between proxies of a different design, therefore, I think it is wrong to use it. If you can standardize the contents of either, that is a different story.
<BR>
<BR>Further, as Dean wrote: 'Both approaches leave the format of the "hunk" open -- it could be cryptographically protected, just a hash value matching a table stored on the proxy, or almost anything else.' It seems to me that any of these security measures would prevent another proxy from being able to understand the State or Cookie anyway, unless they share keys. Wouldn't that be as hard as sharing states?
<BR>
<BR>State is clearly less of a security problem than Cookie. As noted in the "State" draft, 'Cookies typically persist across sessions'. "State", on the other hand, clearly only exists until the next state change, i.e., when a call ends, the state disappears (or goes to idle). Cookies, on the other hand may persist longer and the indication in previous discussions was that they may contain more than just "state" information and may do other things like cause new calls to be initiated. 
<BR>
<BR>As Dean noted: "I also believe the security concern is SLIGHTLY less urgent than in HTTP. As I understand it, both state and cookie drafts indicate a substantially shorter lifetime for the token. In the case of state, the lifetime is the duration of the current dialog. In the case of cookie, it's the current dialog plus any dialog resulting from redirection or referral of the original dialog. 
<BR>HTTP cookies, on the other hand, persist relatively indefiitely and may be extracted by any server in the domain of the cookie during any HTTP interaction with said server for the duraction of the cookie."
<BR>
<BR>I addressed this issue of Cookie persistance in my November 19 comments which I will repeat below. The only way that "Cookie" can be allowed is if it must be erased at the end of a call and if it can not be read by any proxy other than the one setting up the call (or by a limited set which may take over for another proxy in the case of proxy failure and which the UA can verify is allowed to handle the call further). Any other use would be a serious security problem and probably illegal in some places. A device must be considered non-compliant if it does not erase the "Cookie".
<BR>
<BR>-----------------------------------------------------------------------------------------------------------------------------------------
<BR>Comments on draft-willis-sip-cookies-00:
<BR>
<BR>This draft provides a good base-line for definition of a SIP-cookie functionality, derived from RFC 2109.
<BR>
<BR>Some comments/observations:
<BR>
<BR>1. The proposed SIP-cookie borrows heavily from the definition/procedures of cookies for HTTP (RFC 2109). Given the known possibility of abuse of cookies in HTTP, it is very important that the avoidance of such abuse be considered for SIP.
<BR>
<BR>2. Currently, if one disables all cookies in their browser, certain web-based applications such as on-line shopping are not usable, but this does not affect access to most web-browsing. If the support of SIP cookies is essential to the provision of regular telephone type service (e.g., Call Transfer), a user would not be able to disable cookies, thereby exposing themselves to possible abuse. The draft is written as if a User Agent is required to store cookies, that is, can not disable them as a web-browser can today.
<BR>
<BR>3. Section 8, Security Considerations states: "Cookies in SIP, unlike cookies in HTTP, are discarded at the conclusion of a session." It is not clear why this is stated, since RFC 2109 allows the User Agent to discard cookies. It states that "When a user agent terminates execution, it should let the user discard all state information." It seems that the common browsers do not choose to provide the user with this option to discard cookies upon exit, probably since the companies that produce them want to use these persistent cookies as much as any other companies. If these same companies implement SIP functionality, it can be expected that they will choose to not discard SIP-cookies at the conclusion of a telephone call either.
<BR>
<BR>4. As I understand the draft, it requires a user agent to store cookies, and seems to make a strong objective that it must store at least 10 cookies of at least 4096 bytes each, and that it must include all stored cookies in every subsequent message it sends associated with a call. Since other draft proposals result in sending a very large number of messages for some capabilities, especially those associated with providing security, it would appear that this results in huge amounts of data being sent. It is obvious this can not lead to an efficient telephone service.
<BR>
<BR>5. One could easily envision services that would benefit from retaining SIP-cookies after completion of a call in order to support a new call.
<BR>
<BR>6. This draft appears to be one more admission that processing of many (maybe all) telephone type applications requires that the entity controlling the service have knowledge of the "state" of the call. In an increasing number of defined applications, it is a proxy that controls the service (not the user agent as perhaps originally envisioned) and that proxy needs to "remember" the state of the call and service. RFC 2543 included the concept of a "stateful proxy", which maintains the state of a transaction (until a definitive response is received). The proposed revision of SIP further refines this definition of "stateful proxy" and then introduces the notion of a "call stateful (proxy)" which maintains the state "from the initiating INVITE to the terminating BYE", but it does not describe in detail the operation of a "call stateful proxy".
<BR>
<BR>For the control of telephone services using SIP beyond the simple, basic call, it appears that the time has come to admit that these services require a "call stateful proxy" and not to depend on storing of "cookies" in user agents as a substitute.
<BR>
<BR>7. For some yet to be defined SIP-provided services, this cookie mechanism will probably be essential. In line with the recent draft for "SIP Change Process", draft-tsvarea-sipchange-00.txt, a definition of the requirements needs to be submitted to SIPPING. This would identify the specific class of services/capabilities that require the addition of a SIP-cookie. It should be intended for special cases (equivalent to the shopping cart example in RFC 2109), not support for everyday telephone services.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR>
<BR></FONT></HTML>

--part1_b2.a239876.29f0275c_boundary--

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



From daemon@optimus.ietf.org  Thu Apr 18 10:22:59 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07608
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 10:22:59 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA29801
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 10:23:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA28932;
	Thu, 18 Apr 2002 10:13:04 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA28902
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 10:12:59 -0400 (EDT)
Received: from zctfs063.europe.nortel.com (zctfs063.nortelnetworks.com [47.164.128.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07022
	for <sipping@ietf.org>; Thu, 18 Apr 2002 10:12:54 -0400 (EDT)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by zctfs063.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3IECQ016149
	for <sipping@ietf.org>; Thu, 18 Apr 2002 16:12:26 +0200 (MEST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JDW432X0>; Thu, 18 Apr 2002 15:12:26 +0100
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F717A@zwcwd00r.europe.nortel.com>
From: "Mark Watson"<mwatson@nortelnetworks.com>
To: "'sipping@ietf.org'" <sipping@ietf.org>
Date: Thu, 18 Apr 2002 15:12:19 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E6E2.CBB4F61A"
Subject: [Sipping] RE: Network Asserted Identity
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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

So, no comments on the proposed requirements below. I take it everyone
agrees then ?

...Mark

> -----Original Message-----

> OK, so lets see if we can conclude on _short-term_ Network 
> Asserted identity requirements in a separate thread. 
> Follow-ups to SIPPING ONLY please.
> 
> First, assume a trust domain model as per privacy draft 
> applicability statement. Entities within a domain trust each 
> other, entities in different domains are mutually untrusted.
> 
> I'll try to build up the requirements, least contraversial first: 
> NAI1) The ability for network entities to insert a network 
> asserted identity and pass to other network entities within 
> the same trust domain.
> 
> NAI2) The ability for a network entity to pass a 
> (non-private) network asserted identity directly to a UA
>
> NAI3) Secure transport of network asserted identity across 
> 'untrusted' networks back to the same trust domain (including 
> between trust 'islands' - disconnected parts of a single trust domain)
> 
> NAI4) Transport of network asserted identity between trust 
> domains (i.e. transport in one domain of a network asserted 
> identity received from another domain)
> 
> For clarity, 
> (a) the requirement for a user to choose one of a number of 
> identities, whilst retaining privacy, is a 3GPP requirement, 
> but is *out of scope* of this thread.
> 
> (b) Call Trace implemented by encrypting the identity and 
> passing this to the called user, who can then pass the 
> encrypted identity to the generating service 
> provider/authorities, is considered a sub-case of NAI3 - the 
> identity is passed to the 'untrusted' user and back to the 
> original Trust Domain (the Service Provider) before being 
> passed to the authorities.
> 
> I expect the From/To debate will continue, probably to the 
> end of time, but I don't see a strong relationship with this issue.
> 
> If people agree with my statement of the potential 
> requirements, perhaps we could open discussion on which of 
> these should be considered for immediate standardisation. The 
> others can be put into the pot for discussion of the generic 
> privacy requirements.
> 
> For my part, I am most concerned about NAI1 and NAI2. 
> 
> Regards...Mark 
> 
> > -----Original Message----- 
> > From: David R. Oran [mailto:oran@cisco.com] 
> > Sent: 15 April 2002 17:39 
> > To: 'Rosen, Brian'; Mpierce1@aol.com; sip@ietf.org 
> > Subject: RE: Summary of RE: [Sip] Comment, SIP Privacy draft 
> > 
> > 
> > Brian Rosen wrote: 
> > >If we could get consensus that trace-with-anonymity is the 
> problem, 
> > then > we can 
> > > work on solutions.  Until we get to something as 
> straightforward as 
> > > that, 
> > > we are going to spin a lot of wheels. 
> > 
> > That's always been the prime motivator for me, plus the 
> > secondary use of 
> > NAI for call return to an anonymous caller. 
> > 
> > Dave 
> > 
> > 
> > _______________________________________________ 
> > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip 
> > This list is for NEW development of the core SIP Protocol 
> > Use sip-implementors@cs.columbia.edu for questions on current sip 
> > Use sipping@ietf.org for new developments on the application of sip 
> > 
> 
> ---
> Mark Watson
> UMTS Strategic Product Planning
> Nortel Networks, Maidenhead, UK
> Tel: +44 1628 434456 email: mwatson@nortelnetworks.com
> 

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2655.35">
<TITLE>RE: Network Asserted Identity</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>So, no comments on the proposed requirements below. I take it everyone agrees then ?</FONT>
</P>

<P><FONT SIZE=2>...Mark</FONT>
</P>

<P><FONT SIZE=2>&gt; -----Original Message-----</FONT>
</P>

<P><FONT SIZE=2>&gt; OK, so lets see if we can conclude on _short-term_ Network </FONT>
<BR><FONT SIZE=2>&gt; Asserted identity requirements in a separate thread. </FONT>
<BR><FONT SIZE=2>&gt; Follow-ups to SIPPING ONLY please.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; First, assume a trust domain model as per privacy draft </FONT>
<BR><FONT SIZE=2>&gt; applicability statement. Entities within a domain trust each </FONT>
<BR><FONT SIZE=2>&gt; other, entities in different domains are mutually untrusted.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; I'll try to build up the requirements, least contraversial first: </FONT>
<BR><FONT SIZE=2>&gt; NAI1) The ability for network entities to insert a network </FONT>
<BR><FONT SIZE=2>&gt; asserted identity and pass to other network entities within </FONT>
<BR><FONT SIZE=2>&gt; the same trust domain.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; NAI2) The ability for a network entity to pass a </FONT>
<BR><FONT SIZE=2>&gt; (non-private) network asserted identity directly to a UA</FONT>
<BR><FONT SIZE=2>&gt;</FONT>
<BR><FONT SIZE=2>&gt; NAI3) Secure transport of network asserted identity across </FONT>
<BR><FONT SIZE=2>&gt; 'untrusted' networks back to the same trust domain (including </FONT>
<BR><FONT SIZE=2>&gt; between trust 'islands' - disconnected parts of a single trust domain)</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; NAI4) Transport of network asserted identity between trust </FONT>
<BR><FONT SIZE=2>&gt; domains (i.e. transport in one domain of a network asserted </FONT>
<BR><FONT SIZE=2>&gt; identity received from another domain)</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; For clarity, </FONT>
<BR><FONT SIZE=2>&gt; (a) the requirement for a user to choose one of a number of </FONT>
<BR><FONT SIZE=2>&gt; identities, whilst retaining privacy, is a 3GPP requirement, </FONT>
<BR><FONT SIZE=2>&gt; but is *out of scope* of this thread.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; (b) Call Trace implemented by encrypting the identity and </FONT>
<BR><FONT SIZE=2>&gt; passing this to the called user, who can then pass the </FONT>
<BR><FONT SIZE=2>&gt; encrypted identity to the generating service </FONT>
<BR><FONT SIZE=2>&gt; provider/authorities, is considered a sub-case of NAI3 - the </FONT>
<BR><FONT SIZE=2>&gt; identity is passed to the 'untrusted' user and back to the </FONT>
<BR><FONT SIZE=2>&gt; original Trust Domain (the Service Provider) before being </FONT>
<BR><FONT SIZE=2>&gt; passed to the authorities.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; I expect the From/To debate will continue, probably to the </FONT>
<BR><FONT SIZE=2>&gt; end of time, but I don't see a strong relationship with this issue.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; If people agree with my statement of the potential </FONT>
<BR><FONT SIZE=2>&gt; requirements, perhaps we could open discussion on which of </FONT>
<BR><FONT SIZE=2>&gt; these should be considered for immediate standardisation. The </FONT>
<BR><FONT SIZE=2>&gt; others can be put into the pot for discussion of the generic </FONT>
<BR><FONT SIZE=2>&gt; privacy requirements.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; For my part, I am most concerned about NAI1 and NAI2. </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; Regards...Mark </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; -----Original Message----- </FONT>
<BR><FONT SIZE=2>&gt; &gt; From: David R. Oran [<A HREF="mailto:oran@cisco.com">mailto:oran@cisco.com</A>] </FONT>
<BR><FONT SIZE=2>&gt; &gt; Sent: 15 April 2002 17:39 </FONT>
<BR><FONT SIZE=2>&gt; &gt; To: 'Rosen, Brian'; Mpierce1@aol.com; sip@ietf.org </FONT>
<BR><FONT SIZE=2>&gt; &gt; Subject: RE: Summary of RE: [Sip] Comment, SIP Privacy draft </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; Brian Rosen wrote: </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;If we could get consensus that trace-with-anonymity is the </FONT>
<BR><FONT SIZE=2>&gt; problem, </FONT>
<BR><FONT SIZE=2>&gt; &gt; then &gt; we can </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; work on solutions.&nbsp; Until we get to something as </FONT>
<BR><FONT SIZE=2>&gt; straightforward as </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; that, </FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; we are going to spin a lot of wheels. </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; That's always been the prime motivator for me, plus the </FONT>
<BR><FONT SIZE=2>&gt; &gt; secondary use of </FONT>
<BR><FONT SIZE=2>&gt; &gt; NAI for call return to an anonymous caller. </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; Dave </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; &gt; _______________________________________________ </FONT>
<BR><FONT SIZE=2>&gt; &gt; Sip mailing list&nbsp; <A HREF="https://www1.ietf.org/mailman/listinfo/sip" TARGET="_blank">https://www1.ietf.org/mailman/listinfo/sip</A> </FONT>
<BR><FONT SIZE=2>&gt; &gt; This list is for NEW development of the core SIP Protocol </FONT>
<BR><FONT SIZE=2>&gt; &gt; Use sip-implementors@cs.columbia.edu for questions on current sip </FONT>
<BR><FONT SIZE=2>&gt; &gt; Use sipping@ietf.org for new developments on the application of sip </FONT>
<BR><FONT SIZE=2>&gt; &gt; </FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; ---</FONT>
<BR><FONT SIZE=2>&gt; Mark Watson</FONT>
<BR><FONT SIZE=2>&gt; UMTS Strategic Product Planning</FONT>
<BR><FONT SIZE=2>&gt; Nortel Networks, Maidenhead, UK</FONT>
<BR><FONT SIZE=2>&gt; Tel: +44 1628 434456 email: mwatson@nortelnetworks.com</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E6E2.CBB4F61A--

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



From daemon@optimus.ietf.org  Thu Apr 18 11:01:01 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09384
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 11:01:01 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA02956
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 11:01:05 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA01589;
	Thu, 18 Apr 2002 10:42:26 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA01785
	for <sipping@ns.ietf.org>; Wed, 17 Apr 2002 21:04:00 -0400 (EDT)
Received: from services.dasecurenetworks.com (adsl-64-218-133-75.dsl.rcsntx.swbell.net [64.218.133.75])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12304
	for <sipping@ietf.org>; Wed, 17 Apr 2002 21:03:56 -0400 (EDT)
Received: from dasecurenetworks.com (main1.localdomain [192.168.0.151])
	by services.dasecurenetworks.com (8.11.6/8.9.3) with ESMTP id g3I0YVf30721;
	Wed, 17 Apr 2002 19:34:32 -0500
Message-ID: <3CBE2053.2984C73E@dasecurenetworks.com>
Date: Wed, 17 Apr 2002 20:24:35 -0500
From: Chris Martin <cmartin@dasecurenetworks.com>
X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10enterprise i686)
X-Accept-Language: en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>, cmartin@dasecurenetworks.com
References: <A3C2399B2FACD411A54200508BE39C74054F7137@zwcwd00r.europe.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Re: Network Asserted Identity (was: RE: Summary of RE: [Sip] Comment,SIP
 Privacy draft)
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

> Mark Watson wrote:
> 
> OK, so lets see if we can conclude on _short-term_ Network Asserted
> identity requirements in a separate thread. Follow-ups to SIPPING ONLY
> please.
> 
> First, assume a trust domain model as per privacy draft applicability
> statement. Entities within a domain trust each other, entities in
> different domains are mutually untrusted.

Is this different than a "realm", as in wcom.com is a domain, but "wcom"
is a realm in the sip sense?

> 
> I'll try to build up the requirements, least contraversial first:
> NAI1) The ability for network entities to insert a network asserted
> identity and pass to other network entities within the same trust
> domain.

insert a new header (like RPID)? or as in modification of existing
headers, I think you mean the first just want to be clear for own
edification? Agreee.

> 
> NAI2) The ability for a network entity to pass a (non-private) network
> asserted identity directly to a UA

non-private, as in an inbound identity contained in a request from an
untrusted entity to an internal (in relation to the SP domain) UA? If
so, I agree.

> NAI3) Secure transport of network asserted identity across 'untrusted'
> networks back to the same trust domain (including between trust
> 'islands' - disconnected parts of a single trust domain)

Such as IPsec encryption, TLS, as an example, over untrusted networks?

> 
> NAI4) Transport of network asserted identity between trust domains
> (i.e. transport in one domain of a network asserted identity received
> from another domain)
> For clarity,
> (a) the requirement for a user to choose one of a number of
> identities, whilst retaining privacy, is a 3GPP requirement, but is
> *out of scope* of this thread.

What draft would be good to catch up on these requirements?

> 
> (b) Call Trace implemented by encrypting the identity and passing this
> to the called user, who can then pass the encrypted identity to the
> generating service provider/authorities, is considered a sub-case of
> NAI3 - the identity is passed to the 'untrusted' user and back to the
> original Trust Domain (the Service Provider) before being passed to
> the authorities.

This is interesting.


> 
> I expect the From/To debate will continue, probably to the end of
> time, but I don't see a strong relationship with this issue.


I kind of responded to this in a response to Christian, to the fact that
with the exception of the content/message body..the other fields may be
relevant. Think more discussion should be done in this respect to this
topic, (after the requirements are submitted  :^) )

> 
> If people agree with my statement of the potential requirements,
> perhaps we could open discussion on which of these should be
> considered for immediate standardisation. The others can be put into
> the pot for discussion of the generic privacy requirements.

agree with the requirements


> 
> For my part, I am most concerned about NAI1 and NAI2.
> 
> Regards...Mark
> 
> > -----Original Message-----
> > From: David R. Oran [mailto:oran@cisco.com]
> > Sent: 15 April 2002 17:39
> > To: 'Rosen, Brian'; Mpierce1@aol.com; sip@ietf.org
> > Subject: RE: Summary of RE: [Sip] Comment, SIP Privacy draft
> >
> >
> > Brian Rosen wrote:
> > >If we could get consensus that trace-with-anonymity is the problem,
> 
> > then > we can
> > > work on solutions.  Until we get to something as straightforward
> as
> > > that,
> > > we are going to spin a lot of wheels.
> >
> > That's always been the prime motivator for me, plus the
> > secondary use of
> > NAI for call return to an anonymous caller.
> >
> > Dave
> >
> >
> > _______________________________________________
> > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sipping@ietf.org for new developments on the application of sip
> >


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



From daemon@optimus.ietf.org  Thu Apr 18 11:03:27 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09474
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 11:03:27 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA03328
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 11:03:31 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA01595;
	Thu, 18 Apr 2002 10:42:26 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA16043
	for <sipping@ns.ietf.org>; Wed, 17 Apr 2002 16:40:45 -0400 (EDT)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06730
	for <sipping@ietf.org>; Wed, 17 Apr 2002 16:40:41 -0400 (EDT)
Received: from mr6.exu.ericsson.se (mr6att.ericy.com [138.85.224.157])
	by imr2.ericy.com (8.11.3/8.11.3) with ESMTP id g3HKeEi22317
	for <sipping@ietf.org>; Wed, 17 Apr 2002 15:40:14 -0500 (CDT)
Received: from eamrcnt747.exu.ericsson.se (eamrcnt747.exu.ericsson.se [138.85.133.37])
	by mr6.exu.ericsson.se (8.11.3/8.11.3) with SMTP id g3HKeEd27413
	for <sipping@ietf.org>; Wed, 17 Apr 2002 15:40:14 -0500 (CDT)
Received: FROM eamrcnt761.exu.ericsson.se BY eamrcnt747.exu.ericsson.se ; Wed Apr 17 15:40:13 2002 -0500
Received: by eamrcnt761.exu.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <2Z5W12YT>; Wed, 17 Apr 2002 15:40:13 -0500
Message-ID: <F9211EC7A7FED4119FD9005004A6C87007E242C8@eamrcnt723.exu.ericsson.se>
From: "Stephen Hayes (EUS)" <Stephen.Hayes@am1.ericsson.se>
To: sipping@ietf.org
Date: Wed, 17 Apr 2002 15:40:11 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E650.122E9760"
Subject: [Sipping] Caller ID requirements from 3GPP
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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

At the risk of adding fuel to an already huge fire, please find below the requirements on caller-id from the 3GPP.  I call them caller-id requirements as opposed to privacy requirements, because privacy is something bigger.  These have been presented on the CN1 list and there have been no objections to their content.  The 3 requirements are what 3GPP needs for Release 5.  The 3 non-requirements are NOT needed for Release 5.

In general, this is not the way we like to clarify requirements from the 3GPP, however this issue needs resolution quickly to meet our timeframes.  I encourage anyone from the 3GPP to set me right if they think I have mistated the requirements.

Requirement 1: 3GPP DOES need a way of indicating network asserted identity  Given that the To/From headers cannot be trusted, a way of indicating the subscriber identity is needed.  So far 3GPP has assumed the use of RPID for this purpose.

Requirement 2: 3GPP DOES need a way of restricting presentation of network asserted identity.  For purposes of authorization, the network will need to be able to identify a subscriber.  However, the user may not wish this information to be presented to the remote party or passed to an untrusted network.  This is analogus to the GSM CLIR capability.  Note that if the user has not requested that it's identity be suppressed, then the network should have the option of presenting the network asserted identity.

Requirement 3: 3GPP DOES need a way for the UE to pass the network an indication of what public identity it should use.  This identity might be for purposes of being displayed by the called UE or perhaps for processing within the network (e.g., charged to a particular account).  Having the UE populate the RPID has been proposed for this role although other mechanisms could probably also be used. Note that the network cannot rely on this identity information to be valid.

Non-requirement 1: 3GPP does NOT need to address inter-network trust boundaries (at least in this context).  In general, the UEs are considered to not be trusted. This means that the network must not send the network asserted identity to the UE or any other proxy that is not trusted (if the originator requested that it be restricted).  In general roaming relations imply a level of trust (you are after all trusting them to faithfully provide the SIP proxy function).  If all roaming partners are "trusted" then the issue of inter-network trust boundaries is irrelevant for the 3GPP.

Non-requirement 2: 3GPP does NOT need to address call trace across trust boundaries.  Given non-requirement 1, then the trace problem is an internal issue within the trusted boundary.  Trace functionality in 3GPP has also been moved to Release 6.

Non-requirement 3: 3GPP does NOT need to address total privacy in Rel 5.  3GPP needs a draft dealing with the restriction of RPID delivery.  It does not require addressing the general issue of obfuscating other SIP headers (including those supplied by the UE) and other information that could be correlated with a subscriber (such as an IP address).  This might be something that 3GPP would consider in a longer timeframe.

3GPP also assumes that there is integrity protection across all hops (including across trust boundaries), so that tampering with privacy related information is not an issue.  Also, the requirements apply to service platforms which may or may not be inside the trust boundary.

Regards, 
Stephen Hayes
3GPP TSG-CN Chair
Ericsson Inc.
Tel: +1 972 583 5773
Fax: +1 801 409 6319
Mobile: +1 469 360 8500
mailto:stephen.hayes@ericsson.com

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.45">
<TITLE>Caller ID requirements from 3GPP</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>At the risk of adding fuel to an already huge fire, =
please find below the requirements on caller-id from the 3GPP.&nbsp; I =
call them caller-id requirements as opposed to privacy requirements, =
because privacy is something bigger.&nbsp; These have been presented on =
the CN1 list and there have been no objections to their content.&nbsp; =
The 3 requirements are what 3GPP needs for Release 5.&nbsp; The 3 =
non-requirements are NOT needed for Release 5.</FONT></P>

<P><FONT SIZE=3D2>In general, this is not the way we like to clarify =
requirements from the 3GPP, however this issue needs resolution quickly =
to meet our timeframes.&nbsp; I encourage anyone from the 3GPP to set =
me right if they think I have mistated the requirements.</FONT></P>

<P><FONT SIZE=3D2>Requirement 1: 3GPP DOES need a way of indicating =
network asserted identity&nbsp; Given that the To/From headers cannot =
be trusted, a way of indicating the subscriber identity is =
needed.&nbsp; So far 3GPP has assumed the use of RPID for this =
purpose.</FONT></P>

<P><FONT SIZE=3D2>Requirement 2: 3GPP DOES need a way of restricting =
presentation of network asserted identity.&nbsp; For purposes of =
authorization, the network will need to be able to identify a =
subscriber.&nbsp; However, the user may not wish this information to be =
presented to the remote party or passed to an untrusted network.&nbsp; =
This is analogus to the GSM CLIR capability.&nbsp; Note that if the =
user has not requested that it's identity be suppressed, then the =
network should have the option of presenting the network asserted =
identity.</FONT></P>

<P><FONT SIZE=3D2>Requirement 3: 3GPP DOES need a way for the UE to =
pass the network an indication of what public identity it should =
use.&nbsp; This identity might be for purposes of being displayed by =
the called UE or perhaps for processing within the network (e.g., =
charged to a particular account).&nbsp; Having the UE populate the RPID =
has been proposed for this role although other mechanisms could =
probably also be used. Note that the network cannot rely on this =
identity information to be valid.</FONT></P>

<P><FONT SIZE=3D2>Non-requirement 1: 3GPP does NOT need to address =
inter-network trust boundaries (at least in this context).&nbsp; In =
general, the UEs are considered to not be trusted. This means that the =
network must not send the network asserted identity to the UE or any =
other proxy that is not trusted (if the originator requested that it be =
restricted).&nbsp; In general roaming relations imply a level of trust =
(you are after all trusting them to faithfully provide the SIP proxy =
function).&nbsp; If all roaming partners are &quot;trusted&quot; then =
the issue of inter-network trust boundaries is irrelevant for the =
3GPP.</FONT></P>

<P><FONT SIZE=3D2>Non-requirement 2: 3GPP does NOT need to address call =
trace across trust boundaries.&nbsp; Given non-requirement 1, then the =
trace problem is an internal issue within the trusted boundary.&nbsp; =
Trace functionality in 3GPP has also been moved to Release =
6.</FONT></P>

<P><FONT SIZE=3D2>Non-requirement 3: 3GPP does NOT need to address =
total privacy in Rel 5.&nbsp; 3GPP needs a draft dealing with the =
restriction of RPID delivery.&nbsp; It does not require addressing the =
general issue of obfuscating other SIP headers (including those =
supplied by the UE) and other information that could be correlated with =
a subscriber (such as an IP address).&nbsp; This might be something =
that 3GPP would consider in a longer timeframe.</FONT></P>

<P><FONT SIZE=3D2>3GPP also assumes that there is integrity protection =
across all hops (including across trust boundaries), so that tampering =
with privacy related information is not an issue.&nbsp; Also, the =
requirements apply to service platforms which may or may not be inside =
the trust boundary.</FONT></P>

<P><FONT SIZE=3D2>Regards, </FONT>
<BR><FONT SIZE=3D2>Stephen Hayes</FONT>
<BR><FONT SIZE=3D2>3GPP TSG-CN Chair</FONT>
<BR><FONT SIZE=3D2>Ericsson Inc.</FONT>
<BR><FONT SIZE=3D2>Tel: +1 972 583 5773</FONT>
<BR><FONT SIZE=3D2>Fax: +1 801 409 6319</FONT>
<BR><FONT SIZE=3D2>Mobile: +1 469 360 8500</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"mailto:stephen.hayes@ericsson.com">mailto:stephen.hayes@ericsson=
.com</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E650.122E9760--


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



From daemon@optimus.ietf.org  Thu Apr 18 11:17:14 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09978
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 11:17:10 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA04102
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 11:17:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA03309;
	Thu, 18 Apr 2002 11:03:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA03206
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 11:02:59 -0400 (EDT)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09442
	for <sipping@ietf.org>; Thu, 18 Apr 2002 11:02:41 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g3IF1uNo000560;
	Thu, 18 Apr 2002 08:01:56 -0700 (PDT)
Received: from localhost (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint)
	with ESMTP id ACX06446;
	Thu, 18 Apr 2002 08:02:12 -0700 (PDT)
Date: Thu, 18 Apr 2002 07:59:16 -0700 (Pacific Daylight Time)
From: Rohan Mahy <rohan@cisco.com>
To: Mpierce1@aol.com
cc: sipping@ietf.org, <brian.rosen@marconi.com>
In-Reply-To: <b2.a239876.29f0275c@aol.com>
Message-ID: <Pine.WNT.4.44.0204180747240.-441563@chorizo.rapidconvergence.com>
X-X-Sender: rmahy@imop.cisco.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Sipping] Re: Cookies vs. State
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org



On Thu, 18 Apr 2002 Mpierce1@aol.com wrote:
> In a message dated 4/18/02 2:35:58 AM Eastern Daylight Time, rohan@cisco.com
> writes:
> > ## the reason to allow a server to remain stateless allows servers to fail
> > ## in the middle of a call without interruption of service.  this is
> > ## arguably much easier/better/faster than requiring SIP servers to fully
> > ## mirror call state across a cluster of servers.
> > ## thx, -r
>
> In a message dated 4/17/02 9:06:48 PM Eastern Daylight Time,
> ssaha@longboard.com writes:
> > The concern for being stateless is not memory but HA. What happens when a
> > Call statefull proxy dies? How do you reconstruct states after recovery?
> > Distributing state to edge lowers the risk in failure conditions. If a US
> > fails, it only affect that very UA none else [when UA is dead - the call is
> > anyway lost]. Providing HA a statefull proxy is not easy job either.
>
> Yes, I presumed that someone would use the above as the reason for storing
> state (whether as "Cookie" or "State") in the UA. That's why my original
> e-mail stated that "It is presumed that the lack of a standard definition of
> this state value would preclude its use by a different proxy than the one
> which stored it (at least by a proxy of a different design)." Another proxy
> could take over for a failed one only if they had a common understanding of
> the contents of the "State" or "Cookie". I don't see this ever happening
> between proxies of a different design, therefore, I think it is wrong to use
> it. If you can standardize the contents of either, that is a different story.

typically only one or two enitities in the path of the call are
likely to set/check cookies.  the cookies set by one server just need to
be understood by other members of the same high-availability cluster.
this is really MUCH less of a big deal than you are making it out to be.

> Further, as Dean wrote: 'Both approaches leave the format of the "hunk" open
> -- it could be cryptographically protected, just a hash value matching a
> table stored on the proxy, or almost anything else.' It seems to me that any
> of these security measures would prevent another proxy from being able to
> understand the State or Cookie anyway, unless they share keys. Wouldn't that
> be as hard as sharing states?

no.  have you ever implemented a robust, real-time, high-availability
state sharing mechanism in software?

> State is clearly less of a security problem than Cookie. As noted in the
> "State" draft, 'Cookies typically persist across sessions'. "State", on the
> other hand, clearly only exists until the next state change, i.e., when a
> call ends, the state disappears (or goes to idle). Cookies, on the other hand
> may persist longer and the indication in previous discussions was that they
> may contain more than just "state" information and may do other things like
> cause new calls to be initiated.

The state draft was written before the SIP cookies draft, and so refers to
an assumed use of HTTP cookies.  This last sentence clearly does not
apply SIP cookies.

> As Dean noted: "I also believe the security concern is SLIGHTLY less urgent
> than in HTTP. As I understand it, both state and cookie drafts indicate a
> substantially shorter lifetime for the token. In the case of state, the
> lifetime is the duration of the current dialog. In the case of cookie, it's
> the current dialog plus any dialog resulting from redirection or referral of
> the original dialog.
> HTTP cookies, on the other hand, persist relatively indefiitely and may be
> extracted by any server in the domain of the cookie during any HTTP
> interaction with said server for the duraction of the cookie."
>
> I addressed this issue of Cookie persistance in my November 19 comments which
> I will repeat below. The only way that "Cookie" can be allowed is if it must
> be erased at the end of a call and if it can not be read by any proxy other
> than the one setting up the call (or by a limited set which may take over for
> another proxy in the case of proxy failure and which the UA can verify is
> allowed to handle the call further). Any other use would be a serious
> security problem and probably illegal in some places. A device must be
> considered non-compliant if it does not erase the "Cookie".

Perhaps this should be more obvious, but Section 5.1 of the SIP cookies
draft states:

   Cookies are discarded when the call instantiating the cookie and all
   calls derived from that call have terminated.

The purpose of this sentence was clearly to prevent the kind of abuses
permitted by the current HTTP mechanism.  Would you be satisfied if this
sentence said "Cookies MUST be discarded..." ?

thanks,
-rohan

> ------------------------------------------------------------------------------
>
> -----------------------------------------------------------
> Comments on draft-willis-sip-cookies-00:
>
> This draft provides a good base-line for definition of a SIP-cookie
> functionality, derived from RFC 2109.
>
> Some comments/observations:
>
> 1. The proposed SIP-cookie borrows heavily from the definition/procedures of
> cookies for HTTP (RFC 2109). Given the known possibility of abuse of cookies
> in HTTP, it is very important that the avoidance of such abuse be considered
> for SIP.
>
> 2. Currently, if one disables all cookies in their browser, certain web-based
> applications such as on-line shopping are not usable, but this does not
> affect access to most web-browsing. If the support of SIP cookies is
> essential to the provision of regular telephone type service (e.g., Call
> Transfer), a user would not be able to disable cookies, thereby exposing
> themselves to possible abuse. The draft is written as if a User Agent is
> required to store cookies, that is, can not disable them as a web-browser can
> today.
>
> 3. Section 8, Security Considerations states: "Cookies in SIP, unlike cookies
> in HTTP, are discarded at the conclusion of a session." It is not clear why
> this is stated, since RFC 2109 allows the User Agent to discard cookies. It
> states that "When a user agent terminates execution, it should let the user
> discard all state information." It seems that the common browsers do not
> choose to provide the user with this option to discard cookies upon exit,
> probably since the companies that produce them want to use these persistent
> cookies as much as any other companies. If these same companies implement SIP
> functionality, it can be expected that they will choose to not discard
> SIP-cookies at the conclusion of a telephone call either.
>
> 4. As I understand the draft, it requires a user agent to store cookies, and
> seems to make a strong objective that it must store at least 10 cookies of at
> least 4096 bytes each, and that it must include all stored cookies in every
> subsequent message it sends associated with a call. Since other draft
> proposals result in sending a very large number of messages for some
> capabilities, especially those associated with providing security, it would
> appear that this results in huge amounts of data being sent. It is obvious
> this can not lead to an efficient telephone service.
>
> 5. One could easily envision services that would benefit from retaining
> SIP-cookies after completion of a call in order to support a new call.
>
> 6. This draft appears to be one more admission that processing of many (maybe
> all) telephone type applications requires that the entity controlling the
> service have knowledge of the "state" of the call. In an increasing number of
> defined applications, it is a proxy that controls the service (not the user
> agent as perhaps originally envisioned) and that proxy needs to "remember"
> the state of the call and service. RFC 2543 included the concept of a
> "stateful proxy", which maintains the state of a transaction (until a
> definitive response is received). The proposed revision of SIP further
> refines this definition of "stateful proxy" and then introduces the notion of
> a "call stateful (proxy)" which maintains the state "from the initiating
> INVITE to the terminating BYE", but it does not describe in detail the
> operation of a "call stateful proxy".
>
> For the control of telephone services using SIP beyond the simple, basic
> call, it appears that the time has come to admit that these services require
> a "call stateful proxy" and not to depend on storing of "cookies" in user
> agents as a substitute.
>
> 7. For some yet to be defined SIP-provided services, this cookie mechanism
> will probably be essential. In line with the recent draft for "SIP Change
> Process", draft-tsvarea-sipchange-00.txt, a definition of the requirements
> needs to be submitted to SIPPING. This would identify the specific class of
> services/capabilities that require the addition of a SIP-cookie. It should be
> intended for special cases (equivalent to the shopping cart example in RFC
> 2109), not support for everyday telephone services.
>
> Mike Pierce
> Artel
>
>
>


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



From daemon@optimus.ietf.org  Thu Apr 18 11:36:00 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11008
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 11:35:59 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA06576
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 11:36:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA04324;
	Thu, 18 Apr 2002 11:19:39 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA04295
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 11:19:35 -0400 (EDT)
Received: from iere.net.avaya.com (iere.net.avaya.com [198.152.12.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10127
	for <sipping@ietf.org>; Thu, 18 Apr 2002 11:19:30 -0400 (EDT)
Received: from iere.net.avaya.com (localhost [127.0.0.1])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g3IFHvG13845
	for <sipping@ietf.org>; Thu, 18 Apr 2002 11:17:57 -0400 (EDT)
Received: from cof110avexu1.global.avaya.com (h135-9-6-16.avaya.com [135.9.6.16])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g3IFHrM13778
	for <sipping@ietf.org>; Thu, 18 Apr 2002 11:17:53 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] Screened From: and Privacy
Date: Thu, 18 Apr 2002 09:20:11 -0600
Message-ID: <EF4C65F18BE6464B8E9DF3C212B6B2930168E292@cof110avexu1.global.avaya.com>
Thread-Topic: [Sipping] Screened From: and Privacy
Thread-Index: AcHm0WYqDb6kmtAnTdO91jlm9KtbnAAGOXDA
From: "Zmolek, Andrew (Andrew)" <zmolek@avaya.com>
To: <jh@lohi.eng.song.fi>, "Mark Watson" <mwatson@nortelnetworks.com>
Cc: "Jesske, R" <R.Jesske@telekom.de>, <dean.willis@softarmor.com>,
        <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA04296
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 8bit

> you could define another header field for that purpose, but in the
> meanwhile, i need to be able to run my sip service with CURRENT UAs,
> proxies, and sip/ss7 gws all of which today support the from uri +
> display string trick as i have described.  since my basic 
> rule is "if it not broken, don't fix it", i'm not interested to 
> change the current working practice just for the sake of it.
> 
> -- juha

Sure, it's possible to hack current SIP to do just about anything, particularly if the right simplifying assumptions are made, but there is always a trade-off and this thread alone has highlighted many. But your argument basically boils down to:

"I don't have a problem with using my hack to solve my problem, so why don't the rest of you go away and leave things the way they are so I don't have to deal with any change"

Given that more than a one good requirements statement has been made for REAL problems with the current approach (and I think Jon's drafts make this abundantly clear), taking a Luddite stance isn't helpful. 

sip-change happens.

--Andy

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



From daemon@optimus.ietf.org  Thu Apr 18 11:38:09 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11134
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 11:38:09 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA06800
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 11:38:13 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA04027;
	Thu, 18 Apr 2002 11:16:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA03996
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 11:16:14 -0400 (EDT)
Received: from oak.neustar.com (oak.neustar.com [209.173.53.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09912
	for <sipping@ietf.org>; Thu, 18 Apr 2002 11:16:09 -0400 (EDT)
Received: from chiimc01.il.neustar.com (stih650b-s1p2.va.neustar.com [209.173.53.65])
	by oak.neustar.com (8.11.0/8.11.0) with ESMTP id g3IFFc832011;
	Thu, 18 Apr 2002 11:15:38 -0400
Received: by chiimc01.il.neustar.com with Internet Mail Service (5.5.2653.19)
	id <JB0ZV3HJ>; Thu, 18 Apr 2002 10:15:33 -0500
Message-ID: <A83B38C38B3ED6119D3600306E0722D038BF59@dc02.npac.com>
From: "Yu, James" <james.yu@neustar.biz>
To: "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>
Cc: sipping@ietf.org
Subject: RE: [Sipping] draft-yu-tel-url-04.txt comment
Date: Thu, 18 Apr 2002 10:15:29 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

> 
> So, what you say is: if user=phone, an implementation must 
> always be able to
> handle parameters in the SIP-URL???
> 
> If this is the case, I think it must be specified in bis, 
> since user=phone is
> also specified there.
> 
> OR, we can say that an implementation not supporting the 
> parameters will simply
> treat the whole user part as a single string, but again - 
> that would probably be
> rejected by PSTN routing handlers etc.
> 

The user part can be treated as a single string first.  There is no need to
understand or process the user part if the received sip URL in the
Request-URI contains a host that is not the node itself.  Based on the
routing precedence, this node is supposed to route based on the host
information.  Only when this node is that host, it needs to process the user
part.  In that situation, when "user=phone" is present, it knows that a
telephone number is in the user part and other tel URL parameters may be
present.  If this node does not understand some of the parameters in the
user part, it can ignore them.  The actual message parsing and processing is
certainly much more complicated.

James

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



From daemon@optimus.ietf.org  Thu Apr 18 11:59:21 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12087
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 11:59:09 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA08872
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 11:59:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA06255;
	Thu, 18 Apr 2002 11:33:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA06211
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 11:33:02 -0400 (EDT)
Received: from commserver.iperia.com ([204.57.52.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10842
	for <sipping@ietf.org>; Thu, 18 Apr 2002 11:32:56 -0400 (EDT)
Received: by commserver.erictest.com with Internet Mail Service (5.5.2653.19)
	id <2287PRG0>; Thu, 18 Apr 2002 11:31:54 -0400
Message-ID: <1A69639B9B6AD511812B00B0D0DE19F60A353C@commserver.erictest.com>
From: Gordon Ledgard <gledgard@iperia.com>
To: "'Rohan Mahy'" <rohan@cisco.com>, Mpierce1@aol.com
Cc: sipping@ietf.org, brian.rosen@marconi.com
Subject: RE: [Sipping] Re: Cookies vs. State
Date: Thu, 18 Apr 2002 11:31:54 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


Inline....


> -----Original Message-----
> From: Rohan Mahy [mailto:rohan@cisco.com]
> Sent: Thursday, April 18, 2002 10:59 AM
> To: Mpierce1@aol.com
> Cc: sipping@ietf.org; brian.rosen@marconi.com
> Subject: [Sipping] Re: Cookies vs. State
> 
> 
> 
> 
> On Thu, 18 Apr 2002 Mpierce1@aol.com wrote:
> > In a message dated 4/18/02 2:35:58 AM Eastern Daylight 
> Time, rohan@cisco.com
> > writes:
> > > ## the reason to allow a server to remain stateless 
> allows servers to fail
> > > ## in the middle of a call without interruption of 
> service.  this is
> > > ## arguably much easier/better/faster than requiring SIP 
> servers to fully
> > > ## mirror call state across a cluster of servers.
> > > ## thx, -r
> >
> > In a message dated 4/17/02 9:06:48 PM Eastern Daylight Time,
> > ssaha@longboard.com writes:
> > > The concern for being stateless is not memory but HA. 
> What happens when a
> > > Call statefull proxy dies? How do you reconstruct states 
> after recovery?
> > > Distributing state to edge lowers the risk in failure 
> conditions. If a US
> > > fails, it only affect that very UA none else [when UA is 
> dead - the call is
> > > anyway lost]. Providing HA a statefull proxy is not easy 
> job either.
> >
> > Yes, I presumed that someone would use the above as the 
> reason for storing
> > state (whether as "Cookie" or "State") in the UA. That's 
> why my original
> > e-mail stated that "It is presumed that the lack of a 
> standard definition of
> > this state value would preclude its use by a different 
> proxy than the one
> > which stored it (at least by a proxy of a different 
> design)." Another proxy
> > could take over for a failed one only if they had a common 
> understanding of
> > the contents of the "State" or "Cookie". I don't see this 
> ever happening
> > between proxies of a different design, therefore, I think 
> it is wrong to use
> > it. If you can standardize the contents of either, that is 
> a different story.
> 
> typically only one or two enitities in the path of the call are
> likely to set/check cookies.  the cookies set by one server 
> just need to
> be understood by other members of the same high-availability cluster.
> this is really MUCH less of a big deal than you are making it 
> out to be.
> 
> > Further, as Dean wrote: 'Both approaches leave the format 
> of the "hunk" open
> > -- it could be cryptographically protected, just a hash 
> value matching a
> > table stored on the proxy, or almost anything else.' It 
> seems to me that any
> > of these security measures would prevent another proxy from 
> being able to
> > understand the State or Cookie anyway, unless they share 
> keys. Wouldn't that
> > be as hard as sharing states?
> 
> no.  have you ever implemented a robust, real-time, high-availability
> state sharing mechanism in software?
> 

To expand on "NO" for a moment, all the members of the cluster have to
do is exchange keys or markers when they boot up or come into the cluster.
Easy as cake. If they share the actual state, they need to constantly
update each other or some other repository each time the state changes.



> > State is clearly less of a security problem than Cookie. As 
> noted in the
> > "State" draft, 'Cookies typically persist across sessions'. 
> "State", on the
> > other hand, clearly only exists until the next state 
> change, i.e., when a
> > call ends, the state disappears (or goes to idle). Cookies, 
> on the other hand
> > may persist longer and the indication in previous 
> discussions was that they
> > may contain more than just "state" information and may do 
> other things like
> > cause new calls to be initiated.
> 
> The state draft was written before the SIP cookies draft, and 
> so refers to
> an assumed use of HTTP cookies.  This last sentence clearly does not
> apply SIP cookies.
> 
> > As Dean noted: "I also believe the security concern is 
> SLIGHTLY less urgent
> > than in HTTP. As I understand it, both state and cookie 
> drafts indicate a
> > substantially shorter lifetime for the token. In the case 
> of state, the
> > lifetime is the duration of the current dialog. In the case 
> of cookie, it's
> > the current dialog plus any dialog resulting from 
> redirection or referral of
> > the original dialog.
> > HTTP cookies, on the other hand, persist relatively 
> indefiitely and may be
> > extracted by any server in the domain of the cookie during any HTTP
> > interaction with said server for the duraction of the cookie."
> >
> > I addressed this issue of Cookie persistance in my November 
> 19 comments which
> > I will repeat below. The only way that "Cookie" can be 
> allowed is if it must
> > be erased at the end of a call and if it can not be read by 
> any proxy other
> > than the one setting up the call (or by a limited set which 
> may take over for
> > another proxy in the case of proxy failure and which the UA 
> can verify is
> > allowed to handle the call further). Any other use would be 
> a serious
> > security problem and probably illegal in some places. A 
> device must be
> > considered non-compliant if it does not erase the "Cookie".
> 
> Perhaps this should be more obvious, but Section 5.1 of the 
> SIP cookies
> draft states:
> 
>    Cookies are discarded when the call instantiating the 
> cookie and all
>    calls derived from that call have terminated.
> 
> The purpose of this sentence was clearly to prevent the kind of abuses
> permitted by the current HTTP mechanism.  Would you be 
> satisfied if this
> sentence said "Cookies MUST be discarded..." ?
> 
> thanks,
> -rohan
> 
> > 
> --------------------------------------------------------------
> ----------------
> >
> > -----------------------------------------------------------
> > Comments on draft-willis-sip-cookies-00:
> >
> > This draft provides a good base-line for definition of a SIP-cookie
> > functionality, derived from RFC 2109.
> >
> > Some comments/observations:
> >
> > 1. The proposed SIP-cookie borrows heavily from the 
> definition/procedures of
> > cookies for HTTP (RFC 2109). Given the known possibility of 
> abuse of cookies
> > in HTTP, it is very important that the avoidance of such 
> abuse be considered
> > for SIP.
> >
> > 2. Currently, if one disables all cookies in their browser, 
> certain web-based
> > applications such as on-line shopping are not usable, but 
> this does not
> > affect access to most web-browsing. If the support of SIP cookies is
> > essential to the provision of regular telephone type 
> service (e.g., Call
> > Transfer), a user would not be able to disable cookies, 
> thereby exposing
> > themselves to possible abuse. The draft is written as if a 
> User Agent is
> > required to store cookies, that is, can not disable them as 
> a web-browser can
> > today.
> >
> > 3. Section 8, Security Considerations states: "Cookies in 
> SIP, unlike cookies
> > in HTTP, are discarded at the conclusion of a session." It 
> is not clear why
> > this is stated, since RFC 2109 allows the User Agent to 
> discard cookies. It
> > states that "When a user agent terminates execution, it 
> should let the user
> > discard all state information." It seems that the common 
> browsers do not
> > choose to provide the user with this option to discard 
> cookies upon exit,
> > probably since the companies that produce them want to use 
> these persistent
> > cookies as much as any other companies. If these same 
> companies implement SIP
> > functionality, it can be expected that they will choose to 
> not discard
> > SIP-cookies at the conclusion of a telephone call either.
> >
> > 4. As I understand the draft, it requires a user agent to 
> store cookies, and
> > seems to make a strong objective that it must store at 
> least 10 cookies of at
> > least 4096 bytes each, and that it must include all stored 
> cookies in every
> > subsequent message it sends associated with a call. Since 
> other draft
> > proposals result in sending a very large number of messages for some
> > capabilities, especially those associated with providing 
> security, it would
> > appear that this results in huge amounts of data being 
> sent. It is obvious
> > this can not lead to an efficient telephone service.
> >
> > 5. One could easily envision services that would benefit 
> from retaining
> > SIP-cookies after completion of a call in order to support 
> a new call.
> >
> > 6. This draft appears to be one more admission that 
> processing of many (maybe
> > all) telephone type applications requires that the entity 
> controlling the
> > service have knowledge of the "state" of the call. In an 
> increasing number of
> > defined applications, it is a proxy that controls the 
> service (not the user
> > agent as perhaps originally envisioned) and that proxy 
> needs to "remember"
> > the state of the call and service. RFC 2543 included the 
> concept of a
> > "stateful proxy", which maintains the state of a 
> transaction (until a
> > definitive response is received). The proposed revision of 
> SIP further
> > refines this definition of "stateful proxy" and then 
> introduces the notion of
> > a "call stateful (proxy)" which maintains the state "from 
> the initiating
> > INVITE to the terminating BYE", but it does not describe in 
> detail the
> > operation of a "call stateful proxy".
> >
> > For the control of telephone services using SIP beyond the 
> simple, basic
> > call, it appears that the time has come to admit that these 
> services require
> > a "call stateful proxy" and not to depend on storing of 
> "cookies" in user
> > agents as a substitute.
> >
> > 7. For some yet to be defined SIP-provided services, this 
> cookie mechanism
> > will probably be essential. In line with the recent draft 
> for "SIP Change
> > Process", draft-tsvarea-sipchange-00.txt, a definition of 
> the requirements
> > needs to be submitted to SIPPING. This would identify the 
> specific class of
> > services/capabilities that require the addition of a 
> SIP-cookie. It should be
> > intended for special cases (equivalent to the shopping cart 
> example in RFC
> > 2109), not support for everyday telephone services.
> >
> > Mike Pierce
> > Artel
> >
> >
> >
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

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



From daemon@optimus.ietf.org  Thu Apr 18 12:25:09 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13440
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 12:25:04 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA12733
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 12:25:08 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA11589;
	Thu, 18 Apr 2002 12:10:12 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA11558
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 12:10:09 -0400 (EDT)
Received: from iere.net.avaya.com (iere.net.avaya.com [198.152.12.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12808
	for <sipping@ietf.org>; Thu, 18 Apr 2002 12:10:04 -0400 (EDT)
Received: from iere.net.avaya.com (localhost [127.0.0.1])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g3IG8Vc14049
	for <sipping@ietf.org>; Thu, 18 Apr 2002 12:08:31 -0400 (EDT)
Received: from cof110avexu1.global.avaya.com (h135-9-6-16.avaya.com [135.9.6.16])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g3IG8VI14042
	for <sipping@ietf.org>; Thu, 18 Apr 2002 12:08:31 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] Screened From: and Privacy
Date: Thu, 18 Apr 2002 10:10:50 -0600
Message-ID: <EF4C65F18BE6464B8E9DF3C212B6B2930168E2BF@cof110avexu1.global.avaya.com>
Thread-Topic: [Sipping] Screened From: and Privacy
Thread-Index: AcHmmMMQUdzqkmm9TXuuuiXYKSYlRwAWShuQ
From: "Zmolek, Andrew (Andrew)" <zmolek@avaya.com>
To: <jh@lohi.eng.song.fi>
Cc: "Jesske, R" <R.Jesske@telekom.de>, <dean.willis@softarmor.com>,
        <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id MAA11559
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 8bit

Juha writes:

> seems that you didn't understand how things happen (which i have
> explained already at least twice before).

Existing practice is only one factor to be considered for standards requirements. Your point has been made and understood, but that doesn't make it normative or binding on the standards process or implementers.

> > Again, what is the benefit gained by forcing a choice 
> > between UAI and NAI? I don't see it.
> 
> i don't understand how this relates to what i have said.  

Your approach, from what I can tell, precludes the possibility of having both UAI and NAI associated with a dialog. Either could be hacked into current headers, but a choice would have to be made by someone along the way. Why force that choice? Backwards compatibility and header reduction appear to be your sole arguments for this, but it's not clear that separable a NAI mechanism would break anything. 

--Andy

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



From daemon@optimus.ietf.org  Thu Apr 18 13:42:10 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16599
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 13:42:10 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA19269
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 13:42:13 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA17644;
	Thu, 18 Apr 2002 13:27:56 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA17606
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 13:27:52 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15767
	for <sipping@ietf.org>; Thu, 18 Apr 2002 13:27:48 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA15351;
	Thu, 18 Apr 2002 13:27:17 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA13439;
	Thu, 18 Apr 2002 13:27:17 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <H8GSL714>; Thu, 18 Apr 2002 13:27:07 -0400
Message-ID: <313680C9A886D511A06000204840E1CF57CE85@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Mpierce1@aol.com'" <Mpierce1@aol.com>, rohan@cisco.com, sipping@ietf.org
Cc: "Rosen, Brian" <Brian.Rosen@marconi.com>
Subject: RE: [Sipping] Re: Cookies vs. State
Date: Thu, 18 Apr 2002 13:27:16 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

>----------------------------------------------------- 
>Comments on draft-willis-sip-cookies-00: 
>
>This draft provides a good base-line for definition of a SIP-cookie
functionality, >derived from RFC 2109. 
>
>Some comments/observations: 
>
>1. The proposed SIP-cookie borrows heavily from the definition/procedures
of 
>cookies for HTTP (RFC 2109). Given the known possibility of abuse of
cookies in 
>HTTP, it is very important that the avoidance of such abuse be considered
for SIP.
Agreed.  We do so primarily by limiting Cookies to the duration of a call 

>2. Currently, if one disables all cookies in their browser, certain
web-based 
>applications such as on-line shopping are not usable, but this does not
affect 
>access to most web-browsing. If the support of SIP cookies is essential to
the 
>provision of regular telephone type service (e.g., Call Transfer), a user 
>would not be able to disable cookies, thereby exposing themselves to
possible 
>abuse. The draft is written as if a User Agent is required to store
cookies, 
>that is, can not disable them as a web-browser can today. 
Of course we don't know exactly what cookies will be used for, but since
almost all of the "regular telephone-type services", including all forms
of Call Transfer, don't need cookies, I think we are pretty safe.


>3. Section 8, Security Considerations states: "Cookies in SIP, unlike
cookies 
>in HTTP, are discarded at the conclusion of a session." It is not clear why

>this is stated, since RFC 2109 allows the User Agent to discard cookies. 
>It states that "When a user agent terminates execution, it should let the 
>user discard all state information." It seems that the common browsers do 
>not choose to provide the user with this option to discard cookies upon
exit, 
>probably since the companies that produce them want to use these persistent

>cookies as much as any other companies. If these same companies implement 
>SIP functionality, it can be expected that they will choose to not discard 
>SIP-cookies at the conclusion of a telephone call either. 
In HTTP, cookies are often "permanent".  Most of the abuse of cookies 
comes from this use.  Of course you can discard HTTP cookies at any time.
You may lose some "services" if you do.  Same with SIP cookies, but we
specify that cookies ARE NOT saved across sessions, primarily to avoid
the abuse that we have seen with HTTP cookies.


>4. As I understand the draft, it requires a user agent to store cookies, 
>and seems to make a strong objective that it must store at least 10 
>cookies of at least 4096 bytes each, and that it must include all stored
>cookies in every subsequent message it sends associated with a call. 
>Since other draft proposals result in sending a very large number of 
>messages for some capabilities, especially those associated with providing 
>security, it would appear that this results in huge amounts of data 
>being sent. It is obvious this can not lead to an efficient telephone
service.
Woah, you don't send ALL stored cookies, you send those associated with
a particular call.  Message size can be a problem, in wireless networks,
and when message size exceeds MTU size with UDP.  That is a consideration
which the draft should note.


>5. One could easily envision services that would benefit from retaining 
>SIP-cookies after completion of a call in order to support a new call. 
Yes, but that would get us back to security issues wouldn't it.
I think we should not allow cookies to be held across calls until
we have better mechanisms to control abuse.


>6. This draft appears to be one more admission that processing of many 
>(maybe all) telephone type applications requires that the entity 
>controlling the service have knowledge of the "state" of the call. 
>In an increasing number of defined applications, it is a proxy that 
>controls the service (not the user agent as perhaps originally envisioned) 
>and that proxy needs to "remember" the state of the call and service. 
>RFC 2543 included the concept of a "stateful proxy", which maintains 
>the state of a transaction (until a definitive response is received). 
>The proposed revision of SIP further refines this definition of 
>"stateful proxy" and then introduces the notion of a "call stateful 
>(proxy)" which maintains the state "from the initiating INVITE to the 
>terminating BYE", but it does not describe in detail the operation of 
>a "call stateful proxy". 
>
>For the control of telephone services using SIP beyond the simple, 
>basic call, it appears that the time has come to admit that these 
>services require a "call stateful proxy" and not to depend on storing 
>of "cookies" in user agents as a substitute. 
Several others have noted that it is much easier to support high
availability
when state is stored in the endpoints rather than to have replication
mechanisms and all sorts of other gunk required when state is maintained
in the proxy server.  Some would say that while call-statefull proxies
may be needed for some services, they are mostly undesirable, and
SIP is designed for statefull UAs and stateless proxies.  Cookies
continues that design philosophy.

>7. For some yet to be defined SIP-provided services, this cookie 
>mechanism will probably be essential. In line with the recent draft 
>for "SIP Change Process", draft-tsvarea-sipchange-00.txt, a definition 
>of the requirements needs to be submitted to SIPPING. This would identify 
>the specific class of services/capabilities that require the addition 
>of a SIP-cookie. It should be intended for special cases (equivalent 
>to the shopping cart example in RFC 2109), not support for everyday 
>telephone services. 
State and Cookies predate SIP Change Process and have been grandfathered
in.


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



From daemon@optimus.ietf.org  Thu Apr 18 13:47:03 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16741
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 13:47:03 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA19491
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 13:47:06 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA18768;
	Thu, 18 Apr 2002 13:36:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA18714
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 13:36:48 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16219
	for <sipping@ietf.org>; Thu, 18 Apr 2002 13:36:35 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA16842;
	Thu, 18 Apr 2002 13:35:50 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA15851;
	Thu, 18 Apr 2002 13:35:51 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <H8GSL74Z>; Thu, 18 Apr 2002 13:35:40 -0400
Message-ID: <313680C9A886D511A06000204840E1CF57CE86@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Mark Watson'" <mwatson@nortelnetworks.com>,
        "'sipping@ietf.org'"
	 <sipping@ietf.org>
Subject: RE: [Sipping] RE: Network Asserted Identity
Date: Thu, 18 Apr 2002 13:35:50 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

> NAI2) The ability for a network entity to pass a 
> (non-private) network asserted identity directly to a UA  
I'd like to explore this one.  In my zeal to cut down the discussion to 
manageable hunks, I don't get why we need this now.  I think NAI is 
strictly for SP elements to assert an identity to one another, 
and there is no requirement for any UA to see it.  If we can always 
define NAI as inserted by the network, and stripped prior to sending to 
a UA, then I think many things may get simpler.

It may also make other people happier with this work - UAs send 
things they want the other UA to see.  Proxy Servers send things 
they want other Proxy Servers to see.  I'm still assuming a B2BUA 
is needed for really anonymous calls, and to deal with Subscriber 
vs User issues. 

Brian

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



From daemon@optimus.ietf.org  Thu Apr 18 14:35:42 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18698
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 14:35:42 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA23647
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 14:35:46 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA22743;
	Thu, 18 Apr 2002 14:25:18 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA22697
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 14:25:13 -0400 (EDT)
Received: from ierw.net.avaya.com (ierw.net.avaya.com [198.152.13.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18280
	for <sipping@ietf.org>; Thu, 18 Apr 2002 14:25:09 -0400 (EDT)
Received: from ierw.net.avaya.com (localhost [127.0.0.1])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id OAA20823
	for <sipping@ietf.org>; Thu, 18 Apr 2002 14:23:35 -0400 (EDT)
Received: from cof110avexu1.global.avaya.com (h135-9-6-16.avaya.com [135.9.6.16])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id OAA20810
	for <sipping@ietf.org>; Thu, 18 Apr 2002 14:23:35 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] RE: Network Asserted Identity
Date: Thu, 18 Apr 2002 12:25:53 -0600
Message-ID: <EF4C65F18BE6464B8E9DF3C212B6B2930168E331@cof110avexu1.global.avaya.com>
Thread-Topic: [Sipping] RE: Network Asserted Identity
Thread-Index: AcHnARxnb91tVNsNRUalLZZz1+eIIAABA64w
From: "Zmolek, Andrew (Andrew)" <zmolek@avaya.com>
To: "Rosen, Brian" <Brian.Rosen@marconi.com>,
        "Mark Watson" <mwatson@nortelnetworks.com>, <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id OAA22700
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 8bit

While enterprise customers in general probably don't care so much if NAI is passed directly to the UA or handled by an intermediary they own/manage, I would like to encourage the SIP community to recognize that either: (1) Enterprises can be their own "service providers" in every sense (with or without others) or alternatively: (2) another term is needed to represent the broader notion of all regulated and unregulated, private or public providers of SIP services. 

Many enterprise call centers today make use of this information. I can imagine scenarios where an authorized UA might receive NAI information but if the answer is that it doesn't go beyond some class of proxy or other intermediary I suppose that's a fine answer provided that the notion of "service provider" is properly defined.

If somehow our NAI standard required the kind of formalism that today is reserved for carrier-to-carrier interchange, then that would be a bad thing.

--Andy


> -----Original Message-----
> From: Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> Sent: Thursday, April 18, 2002 11:36 AM
> To: 'Mark Watson'; 'sipping@ietf.org'
> Subject: RE: [Sipping] RE: Network Asserted Identity
> 
> 
> > NAI2) The ability for a network entity to pass a 
> > (non-private) network asserted identity directly to a UA  
> I'd like to explore this one.  In my zeal to cut down the 
> discussion to 
> manageable hunks, I don't get why we need this now.  I think NAI is 
> strictly for SP elements to assert an identity to one another, 
> and there is no requirement for any UA to see it.  If we can always 
> define NAI as inserted by the network, and stripped prior to 
> sending to 
> a UA, then I think many things may get simpler.
> 
> It may also make other people happier with this work - UAs send 
> things they want the other UA to see.  Proxy Servers send things 
> they want other Proxy Servers to see.  I'm still assuming a B2BUA 
> is needed for really anonymous calls, and to deal with Subscriber 
> vs User issues. 
> 
> Brian
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

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



From daemon@optimus.ietf.org  Thu Apr 18 14:59:27 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19440
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 14:59:27 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA25082
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 14:59:31 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA23850;
	Thu, 18 Apr 2002 14:38:32 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA23749
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 14:38:26 -0400 (EDT)
Received: from pine.neustar.com (pine.neustar.com [209.173.57.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18800
	for <sipping@ietf.org>; Thu, 18 Apr 2002 14:38:22 -0400 (EDT)
Received: from chiimc01.il.neustar.com (chih650b-s3p2.il.neustar.com [209.173.57.65])
	by pine.neustar.com (8.11.0/8.11.0) with ESMTP id g3IITrZ15966;
	Thu, 18 Apr 2002 13:29:53 -0500
Received: by chiimc01.il.neustar.com with Internet Mail Service (5.5.2653.19)
	id <JB0ZVQS8>; Thu, 18 Apr 2002 13:29:48 -0500
Message-ID: <70565611B164D511957A001083FCDD560187022B@va02.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Mark Watson'" <mwatson@nortelnetworks.com>,
        "'sipping@ietf.org'"
	 <sipping@ietf.org>
Subject: RE: [Sipping] RE: Network Asserted Identity
Date: Thu, 18 Apr 2002 13:29:41 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E707.013C4940"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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

Well, a few comments on this, actually. First, we might quibble over some of
the terminology here: 'network entity', what these 'identities' represent,
etc.
 
Next, I think most of the problems with sip-privacy-04 seem to fall out from
the fact that the concepts of 'trusted' and 'untrusted' are not well
understood. I'm not sure that we can use these words and think that we're
actually putting forward a hard requirement. The Iraqi example, 'screen' and
so forth exposed some of the problems with these terms. Therefore I'm a
little wary of NAI1, NAI3 and NAI4. NAI3 and NAI4 especially seem to make
assumptions about how trust operates that are a little silly. For NAI3, why
would a SIP 'trusted' domain send something through an untrusted domain to
get back to itself, to the same trusted domain? Sure, in the PSTN that might
make sense, but that would be a harder sell to claim that SIP networks will
need to do this. The whole concept of a trusted domain would require
significant explication before any of this made sense. In sip-privacy-04,
perhaps the biggest problem is that 'trustedness' is assumed to be something
intrinsic about an entity, rather than something about which every other SIP
element in the world is entitled to its own opinion.
 
I would rather phrase NAI1 and NAI2 a little differently. Ideally, these
should only be one requirement - that a 'network entity' can insert the
identity of a user into a message, and that this identity can be viewed by
the recipients of the message. It is a separate matter, a privacy
requirement (which I surmise you don't want to group with NAI requirements),
that in some instances the user can request that their identity not be
shared with others, and it is a problem for that requirement that some
administrative domains might obstinantly be inclined to circulate the user's
identity anyway. Without this privacy requirement, NAI1 and NAI2 would be
identical, right? NAI4, I suspect, is also this same requirement, in any
definition of 'trust' that will turn out to be usable.
 
On clarifying remark (a), I've never been sure what the big deal is about
this 'hinted' identity. I consider 'hinting' to be part of the
authentication process by which the NAI is generated. If someone would like
to propose some new authentication scheme for SIP that contains a plaintext
'hinted' identity in a header that is sent in a request to the entity that
generates the NAI (assuming that some other part of the authentication
process involving security has already occurred, or is occurring out of band
but cannot accomodate the 'hint'), I welcome them to do so - whether or not
any IETF working group would look favorably on that is a different matter.
In any event, I maintain that this is a question about how authentication
works, and it is orthogonal to the NAI problem - it just ended up being
conflated with the privacy and identity problems in the initial
considerations of this space. We can all think of authentication systems
that intrinsically support such a hint (like Digest, which is mandatory for
all SIP entitites).
 
Clarifying remark (b) makes NAI3 a little more practical, but I think I read
NAI3 very differently (in that it didn't involve some sort of administrative
process, but was just a protocol concept). I believe (b) is different enough
to be a requirement in its own merit, though it also is probably not
uncontroversial.
 
So even with a short-term view, I'm afraid I can't immediately go along with
these.
 
Jon Peterson
NeuStar, Inc.

-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Thursday, April 18, 2002 7:12 AM
To: 'sipping@ietf.org'
Subject: [Sipping] RE: Network Asserted Identity



So, no comments on the proposed requirements below. I take it everyone
agrees then ? 

...Mark 

> -----Original Message----- 

> OK, so lets see if we can conclude on _short-term_ Network 
> Asserted identity requirements in a separate thread. 
> Follow-ups to SIPPING ONLY please. 
> 
> First, assume a trust domain model as per privacy draft 
> applicability statement. Entities within a domain trust each 
> other, entities in different domains are mutually untrusted. 
> 
> I'll try to build up the requirements, least contraversial first: 
> NAI1) The ability for network entities to insert a network 
> asserted identity and pass to other network entities within 
> the same trust domain. 
> 
> NAI2) The ability for a network entity to pass a 
> (non-private) network asserted identity directly to a UA 
> 
> NAI3) Secure transport of network asserted identity across 
> 'untrusted' networks back to the same trust domain (including 
> between trust 'islands' - disconnected parts of a single trust domain) 
> 
> NAI4) Transport of network asserted identity between trust 
> domains (i.e. transport in one domain of a network asserted 
> identity received from another domain) 
> 
> For clarity, 
> (a) the requirement for a user to choose one of a number of 
> identities, whilst retaining privacy, is a 3GPP requirement, 
> but is *out of scope* of this thread. 
> 
> (b) Call Trace implemented by encrypting the identity and 
> passing this to the called user, who can then pass the 
> encrypted identity to the generating service 
> provider/authorities, is considered a sub-case of NAI3 - the 
> identity is passed to the 'untrusted' user and back to the 
> original Trust Domain (the Service Provider) before being 
> passed to the authorities. 
> 
> I expect the From/To debate will continue, probably to the 
> end of time, but I don't see a strong relationship with this issue. 
> 
> If people agree with my statement of the potential 
> requirements, perhaps we could open discussion on which of 
> these should be considered for immediate standardisation. The 
> others can be put into the pot for discussion of the generic 
> privacy requirements. 
> 
> For my part, I am most concerned about NAI1 and NAI2. 
> 
> Regards...Mark 
> 
> > -----Original Message----- 
> > From: David R. Oran [ mailto:oran@cisco.com <mailto:oran@cisco.com> ] 
> > Sent: 15 April 2002 17:39 
> > To: 'Rosen, Brian'; Mpierce1@aol.com; sip@ietf.org 
> > Subject: RE: Summary of RE: [Sip] Comment, SIP Privacy draft 
> > 
> > 
> > Brian Rosen wrote: 
> > >If we could get consensus that trace-with-anonymity is the 
> problem, 
> > then > we can 
> > > work on solutions.  Until we get to something as 
> straightforward as 
> > > that, 
> > > we are going to spin a lot of wheels. 
> > 
> > That's always been the prime motivator for me, plus the 
> > secondary use of 
> > NAI for call return to an anonymous caller. 
> > 
> > Dave 
> > 
> > 
> > _______________________________________________ 
> > Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
<https://www1.ietf.org/mailman/listinfo/sip>  
> > This list is for NEW development of the core SIP Protocol 
> > Use sip-implementors@cs.columbia.edu for questions on current sip 
> > Use sipping@ietf.org for new developments on the application of sip 
> > 
> 
> --- 
> Mark Watson 
> UMTS Strategic Product Planning 
> Nortel Networks, Maidenhead, UK 
> Tel: +44 1628 434456 email: mwatson@nortelnetworks.com 
> 


------_=_NextPart_001_01C1E707.013C4940
Content-Type: text/html;
	charset="iso-8859-1"

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

<META content="MSHTML 5.00.3315.2870" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=860003417-18042002>Well, 
a few comments on this, actually. First, we might quibble over some of the 
terminology here: 'network entity', what these 'identities' represent, 
etc.</SPAN></FONT></DIV>
<DIV><SPAN class=860003417-18042002>
<DIV><SPAN class=860003417-18042002></SPAN><FONT color=#0000ff face=Arial 
size=2>&nbsp;</FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=860003417-18042002>Next, 
I think most of the problems with sip-privacy-04 seem to fall out&nbsp;from the 
fact that the concepts of 'trusted' and 'untrusted' are not well understood. I'm 
not sure that we can use these words and think that we're actually putting 
forward a hard requirement. The Iraqi example, 'screen' and so forth exposed 
some of the problems with these terms. Therefore I'm a little wary of NAI1, NAI3 
and NAI4. NAI3 and NAI4 especially seem to make assumptions about how trust 
operates that are a little silly. For NAI3, why would a SIP 'trusted' domain 
send something through an untrusted domain to get back to itself, to the same 
trusted domain? Sure, in the PSTN that might make sense, but that would be a 
harder sell to claim that SIP networks will need to do this. The whole concept 
of a trusted domain would require significant explication before any of this 
made sense. In sip-privacy-04, perhaps the biggest problem is that 'trustedness' 
is assumed to be something intrinsic about an entity, rather than something 
about which every other SIP element in the world is entitled to its own 
opinion.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=860003417-18042002></SPAN></FONT><SPAN 
class=860003417-18042002></SPAN>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=860003417-18042002>I 
would rather phrase NAI1 and NAI2 a little differently. Ideally, these should 
only be one requirement - that a 'network entity' can insert the identity of a 
user into a message, and that this identity can be viewed by the recipients of 
the message. It is a separate matter, a privacy requirement (which I surmise you 
don't want to group with NAI requirements), that in some instances the user can 
request that their identity not be shared with others, and it is a problem for 
that requirement that some administrative domains might obstinantly be inclined 
to circulate the user's identity anyway. Without this privacy requirement, NAI1 
and NAI2 would be identical,&nbsp;right? NAI4, I suspect, is also this same 
requirement, in any definition of 'trust' that will turn out to be 
usable.</SPAN></FONT></SPAN></DIV></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=860003417-18042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=860003417-18042002>On 
clarifying remark (a), I've never been sure what the big deal is about this 
'hinted' identity. I consider 'hinting' to be part of the authentication process 
by which the NAI is generated. If someone would like to propose some new 
authentication scheme for SIP that contains a plaintext 'hinted' identity in a 
header that is sent in a request to the entity that generates the NAI (assuming 
that some other part of the authentication process involving security has 
already occurred, or is occurring out of band but cannot accomodate the 'hint'), 
I welcome them to do so - whether or not any IETF working group would look 
favorably on that is a different matter. In any event, I maintain that this is a 
question about how authentication works, and it is orthogonal to the NAI 
problem&nbsp;- it just ended up being conflated with the privacy and identity 
problems in the initial considerations of this space. We can all think of 
authentication systems that intrinsically support such a hint (like Digest, 
which is mandatory for all SIP entitites).</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=860003417-18042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=860003417-18042002>Clarifying remark (b) makes NAI3 a little more 
practical, but I think I read NAI3 very differently (in that it didn't involve 
some sort of administrative process, but was just a protocol concept). I believe 
(b) is different enough to be a requirement in its own merit, though it also is 
probably not uncontroversial.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=860003417-18042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=860003417-18042002>So 
even with a short-term view, I'm afraid I can't immediately go along with 
these.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=860003417-18042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=860003417-18042002>Jon 
Peterson</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=860003417-18042002>NeuStar, Inc.</SPAN></FONT></DIV>
<BLOCKQUOTE 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Mark Watson 
  [mailto:mwatson@nortelnetworks.com]<BR><B>Sent:</B> Thursday, April 18, 2002 
  7:12 AM<BR><B>To:</B> 'sipping@ietf.org'<BR><B>Subject:</B> [Sipping] RE: 
  Network Asserted Identity<BR><BR></DIV></FONT>
  <P><FONT size=2>So, no comments on the proposed requirements below. I take it 
  everyone agrees then ?</FONT> </P>
  <P><FONT size=2>...Mark</FONT> </P>
  <P><FONT size=2>&gt; -----Original Message-----</FONT> </P>
  <P><FONT size=2>&gt; OK, so lets see if we can conclude on _short-term_ 
  Network </FONT><BR><FONT size=2>&gt; Asserted identity requirements in a 
  separate thread. </FONT><BR><FONT size=2>&gt; Follow-ups to SIPPING ONLY 
  please.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; First, 
  assume a trust domain model as per privacy draft </FONT><BR><FONT size=2>&gt; 
  applicability statement. Entities within a domain trust each </FONT><BR><FONT 
  size=2>&gt; other, entities in different domains are mutually 
  untrusted.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; I'll try 
  to build up the requirements, least contraversial first: </FONT><BR><FONT 
  size=2>&gt; NAI1) The ability for network entities to insert a network 
  </FONT><BR><FONT size=2>&gt; asserted identity and pass to other network 
  entities within </FONT><BR><FONT size=2>&gt; the same trust domain.</FONT> 
  <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; NAI2) The ability for a 
  network entity to pass a </FONT><BR><FONT size=2>&gt; (non-private) network 
  asserted identity directly to a UA</FONT> <BR><FONT size=2>&gt;</FONT> 
  <BR><FONT size=2>&gt; NAI3) Secure transport of network asserted identity 
  across </FONT><BR><FONT size=2>&gt; 'untrusted' networks back to the same 
  trust domain (including </FONT><BR><FONT size=2>&gt; between trust 'islands' - 
  disconnected parts of a single trust domain)</FONT> <BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; NAI4) Transport of network asserted identity 
  between trust </FONT><BR><FONT size=2>&gt; domains (i.e. transport in one 
  domain of a network asserted </FONT><BR><FONT size=2>&gt; identity received 
  from another domain)</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  For clarity, </FONT><BR><FONT size=2>&gt; (a) the requirement for a user to 
  choose one of a number of </FONT><BR><FONT size=2>&gt; identities, whilst 
  retaining privacy, is a 3GPP requirement, </FONT><BR><FONT size=2>&gt; but is 
  *out of scope* of this thread.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; (b) Call Trace implemented by encrypting the identity and 
  </FONT><BR><FONT size=2>&gt; passing this to the called user, who can then 
  pass the </FONT><BR><FONT size=2>&gt; encrypted identity to the generating 
  service </FONT><BR><FONT size=2>&gt; provider/authorities, is considered a 
  sub-case of NAI3 - the </FONT><BR><FONT size=2>&gt; identity is passed to the 
  'untrusted' user and back to the </FONT><BR><FONT size=2>&gt; original Trust 
  Domain (the Service Provider) before being </FONT><BR><FONT size=2>&gt; passed 
  to the authorities.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; 
  I expect the From/To debate will continue, probably to the </FONT><BR><FONT 
  size=2>&gt; end of time, but I don't see a strong relationship with this 
  issue.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; If people 
  agree with my statement of the potential </FONT><BR><FONT size=2>&gt; 
  requirements, perhaps we could open discussion on which of </FONT><BR><FONT 
  size=2>&gt; these should be considered for immediate standardisation. The 
  </FONT><BR><FONT size=2>&gt; others can be put into the pot for discussion of 
  the generic </FONT><BR><FONT size=2>&gt; privacy requirements.</FONT> 
  <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; For my part, I am most 
  concerned about NAI1 and NAI2. </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; Regards...Mark </FONT><BR><FONT size=2>&gt; </FONT><BR><FONT 
  size=2>&gt; &gt; -----Original Message----- </FONT><BR><FONT size=2>&gt; &gt; 
  From: David R. Oran [<A 
  href="mailto:oran@cisco.com">mailto:oran@cisco.com</A>] </FONT><BR><FONT 
  size=2>&gt; &gt; Sent: 15 April 2002 17:39 </FONT><BR><FONT size=2>&gt; &gt; 
  To: 'Rosen, Brian'; Mpierce1@aol.com; sip@ietf.org </FONT><BR><FONT 
  size=2>&gt; &gt; Subject: RE: Summary of RE: [Sip] Comment, SIP Privacy draft 
  </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
  </FONT><BR><FONT size=2>&gt; &gt; Brian Rosen wrote: </FONT><BR><FONT 
  size=2>&gt; &gt; &gt;If we could get consensus that trace-with-anonymity is 
  the </FONT><BR><FONT size=2>&gt; problem, </FONT><BR><FONT size=2>&gt; &gt; 
  then &gt; we can </FONT><BR><FONT size=2>&gt; &gt; &gt; work on 
  solutions.&nbsp; Until we get to something as </FONT><BR><FONT size=2>&gt; 
  straightforward as </FONT><BR><FONT size=2>&gt; &gt; &gt; that, 
  </FONT><BR><FONT size=2>&gt; &gt; &gt; we are going to spin a lot of wheels. 
  </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; That's 
  always been the prime motivator for me, plus the </FONT><BR><FONT size=2>&gt; 
  &gt; secondary use of </FONT><BR><FONT size=2>&gt; &gt; NAI for call return to 
  an anonymous caller. </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
  size=2>&gt; &gt; Dave </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT 
  size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; &gt; 
  _______________________________________________ </FONT><BR><FONT size=2>&gt; 
  &gt; Sip mailing list&nbsp; <A 
  href="https://www1.ietf.org/mailman/listinfo/sip" 
  target=_blank>https://www1.ietf.org/mailman/listinfo/sip</A> </FONT><BR><FONT 
  size=2>&gt; &gt; This list is for NEW development of the core SIP Protocol 
  </FONT><BR><FONT size=2>&gt; &gt; Use sip-implementors@cs.columbia.edu for 
  questions on current sip </FONT><BR><FONT size=2>&gt; &gt; Use 
  sipping@ietf.org for new developments on the application of sip 
  </FONT><BR><FONT size=2>&gt; &gt; </FONT><BR><FONT size=2>&gt; 
  </FONT><BR><FONT size=2>&gt; ---</FONT> <BR><FONT size=2>&gt; Mark 
  Watson</FONT> <BR><FONT size=2>&gt; UMTS Strategic Product Planning</FONT> 
  <BR><FONT size=2>&gt; Nortel Networks, Maidenhead, UK</FONT> <BR><FONT 
  size=2>&gt; Tel: +44 1628 434456 email: mwatson@nortelnetworks.com</FONT> 
  <BR><FONT size=2>&gt; </FONT></P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1E707.013C4940--

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



From daemon@optimus.ietf.org  Thu Apr 18 15:35:12 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20423
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 15:35:12 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA27469
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 15:35:16 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA26575;
	Thu, 18 Apr 2002 15:25:18 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA26544
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 15:25:15 -0400 (EDT)
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20040
	for <sipping@ietf.org>; Thu, 18 Apr 2002 15:25:10 -0400 (EDT)
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x2.nokia.com (Switch-2.2.1/Switch-2.2.0) with ESMTP id g3IJPVF10658
	for <sipping@ietf.org>; Thu, 18 Apr 2002 22:25:31 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5a57992c3eac158f24077@esvir04nok.ntc.nokia.com>;
 Thu, 18 Apr 2002 22:25:12 +0300
Received: from mgw.research.nokia.com ([172.21.33.76]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.3779);
	 Thu, 18 Apr 2002 22:25:12 +0300
Received: from agni.research.nokia.com (agni.research.nokia.com [172.21.40.24])
	by mgw.research.nokia.com (8.9.3/8.9.3) with ESMTP id WAA24658;
	Thu, 18 Apr 2002 22:25:12 +0300 (EETDST)
Received: (from ppessi@localhost)
	by agni.research.nokia.com (8.11.6/8.11.2) id g3HGHH002880;
	Wed, 17 Apr 2002 19:17:17 +0300
To: Jiri Kuthan <kuthan@fokus.gmd.de>
Cc: Pekka Pessi <Pekka.Pessi@nokia.com>, sipping@ietf.org
Subject: Re: [Sipping] IPv6 messages for callflows?
References: <Pine.WNT.4.44.0204121147410.-360391@chorizo.rapidconvergence.com>
 <Pine.WNT.4.44.0204121147410.-360391@chorizo.rapidconvergence.com> <5.1.0.14.0.20020417125022.02dc7e50@mailhost.fokus.gmd.de>
	<Pine.WNT.4.44.0204121147410.-360391@chorizo.rapidconvergence.com>
	<5.1.0.14.0.20020417125022.02dc7e50@mailhost.fokus.gmd.de>
X-face: #V(jdpv[lI!TNUU=2*oh:="#suS*ponXW"yr6G;~L}<xZn_2^0)V{jqdc4y}@2b]ffd}SY#
 :9||1pew85O,WjiYA"6C7bW^zt^+.{b#B{lEE+4$9lrXL(55g}dU>uZ\JfD\"IG#G{j`hZI;=DmT\H
 pfDMyJ`i=:M;BM3R.`[>P^ER8+]i
From: Pekka Pessi <Pekka.Pessi@nokia.com>
In-Reply-To: <5.1.0.14.0.20020417125022.02dc7e50@mailhost.fokus.gmd.de>
Date: 17 Apr 2002 19:17:16 +0300
Message-ID: <pv4riafgfn.fsf@agni.research.nokia.com>
Lines: 32
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-OriginalArrivalTime: 18 Apr 2002 19:25:12.0680 (UTC) FILETIME=[C2CC1E80:01C1E70E]
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

In message <5.1.0.14.0.20020417125022.02dc7e50@mailhost.fokus.gmd.de> Jiri Kuthan <kuthan@fokus.gmd.de> writes:
>one of our developpers meant there was a bug in your example. Can you
>verify that?

	The request is a valid SIP message and it should be accepted.
	The "received=[3ffe:1200:3012:c006:210:a4ff:fe8d:6a46]"
	parameter in question actually matches the generic-param rule in
	the bis-09 ABNF.

>> > Via: SIP/2.0/UDP [3ffe:1200:3012:c000:210:a4ff:fe8d:6a46]:5062 
>> > ;branch=z9hG4bKuNCTHs8Lumv 
>> > ;received=[3ffe:1200:3012:c006:210:a4ff:fe8d:6a46] 
>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
>this is an IPv6reference. the "received" param is defined as
>via-received = "received" EQUAL ( IPv4address / IPv6address ) 
>(see page 241 of draft-ietf-sip-rfc2543bis-09) ^^^^^^^^^^^ 
>So this is illegal, because an IPv6address is basically not the same as an 
>IPv6reference: IPv6reference = "[" IPv6address "]" >The same is in 7.43
>Did I miss something ? Or do I have an old draft ?

	I'd say the bug is in the spec (bis-09), the 

via-received = "received" EQUAL ( IPv4address / IPv6address ) 

	should be replaced with 

via-received = "received" EQUAL ( IPv4address / IPv6reference ) 

	Did they managed to publish 3261? 

					Pekka


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



From daemon@optimus.ietf.org  Thu Apr 18 15:50:06 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20979
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 15:50:06 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA28293
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 15:50:10 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA27878;
	Thu, 18 Apr 2002 15:41:16 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA27842
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 15:41:11 -0400 (EDT)
Received: from imo-d03.mx.aol.com (imo-d03.mx.aol.com [205.188.157.35])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20650
	for <sipping@ietf.org>; Thu, 18 Apr 2002 15:41:06 -0400 (EDT)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-d03.mx.aol.com (mail_out_v32.5.) id t.118.102f7bd1 (4397);
	Thu, 18 Apr 2002 15:39:44 -0400 (EDT)
Message-ID: <118.102f7bd1.29f07aff@aol.com>
Date: Thu, 18 Apr 2002 15:39:43 EDT
Subject: Re: [Sipping] Screened From: and Privacy
To: jh@lohi.eng.song.fi, zmolek@avaya.com
CC: R.Jesske@telekom.de, dean.willis@softarmor.com, sipping@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_118.102f7bd1.29f07aff_boundary"
X-Mailer: AOL 6.0 for Windows US sub 10524
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


--part1_118.102f7bd1.29f07aff_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 4/18/02 1:20:14 AM Eastern Daylight Time, 
jh@lohi.eng.song.fi writes:


> 
> if the user has given display string "Anonymous" and the call gets
> routed to sip destination, i must implement b2bua and make also the from
> uri anonymous.  if the call gets routed to pstn, i set the calling party
> number blocking parameter.
> 
> <snip>
> 
> i still don't understand what this whole thread is all about and i still
> haven't got a reply to my question what advantage rpid or some other new
> header field would bring as compared to the current situation.
> 
> -- juha
> 

It's obvious to me that there is not a consistent opinion of what the 
"current situation" is. I believe I've heard several different 
interpretations of what bis-09 says regarding the From and the use of 
"anonymous" in the Display name. For example, your comment above is that, if 
the user puts in "Anonymous", you (as the servie provider) must do something 
to the uri. I don't read that in bis-09. It says that if the user wants to 
remain hidden "a UAC SHOULD use ... "Anonymous", along with ... a meaningless 
URI." So what really is the "current situation"?

In a message dated 4/18/02 8:02:13 AM Eastern Daylight Time, 
jh@lohi.eng.song.fi writes:


> you could define another header field for that purpose, but in the
> meanwhile, i need to be able to run my sip service with CURRENT UAs,
> proxies, and sip/ss7 gws all of which today support the from uri +
> display string trick as i have described.  since my basic rule is "if it
> not broken, don't fix it", i'm not interested to change the current
> working practice just for the sake of it.
> 
> -- juha
> 
Again, I think the comments and different opinions expressed clearly indicate 
that it is "broke", even if it may just be the description of the use of From 
and "Anonymous". But it seems that any attempt to redefine (or better 
define?) these fields results in a claim that it "breaks" some current 
implementation.

In a message dated 4/18/02 7:46:00 AM Eastern Daylight Time, 
mwatson@nortelnetworks.com writes:


> Yes, 3GPP has this requirement too. But it is a slightly separate question 
> from the NAI itself. If we follow the SHOULD in the SIP specification about 
> the From uri being meaningless when the user requests privacy, then another 
> field is needed to allow the user to choose which identity will be used for 
> 

Yes, I believe Mark is correct, another field is required which is only 
intended for the UA to tell the "network" their identity and the network is 
expected to verify it and may reject calls that don't have a valid identity. 
The UA can not fill it with "meaningless" information. In some cases it may 
be omitted. What the "network" might do with it is another issue.

Mike


--part1_118.102f7bd1.29f07aff_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 4/18/02 1:20:14 AM Eastern Daylight Time, jh@lohi.eng.song.fi writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
<BR>if the user has given display string "Anonymous" and the call gets
<BR>routed to sip destination, i must implement b2bua and make also the from
<BR>uri anonymous. &nbsp;if the call gets routed to pstn, i set the calling party
<BR>number blocking parameter.
<BR>
<BR>&lt;snip&gt;
<BR>
<BR>i still don't understand what this whole thread is all about and i still
<BR>haven't got a reply to my question what advantage rpid or some other new
<BR>header field would bring as compared to the current situation.
<BR>
<BR>-- juha
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>It's obvious to me that there is not a consistent opinion of what the "current situation" is. I believe I've heard several different interpretations of what bis-09 says regarding the From and the use of "anonymous" in the Display name. For example, your comment above is that, if the user puts in "Anonymous", you (as the servie provider) must do something to the uri. I don't read that in bis-09. It says that if the user wants to remain hidden "a UAC SHOULD use ... "Anonymous", along with ... a meaningless URI." So what really is the "current situation"?
<BR>
<BR>In a message dated 4/18/02 8:02:13 AM Eastern Daylight Time, jh@lohi.eng.song.fi writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">you could define another header field for that purpose, but in the
<BR>meanwhile, i need to be able to run my sip service with CURRENT UAs,
<BR>proxies, and sip/ss7 gws all of which today support the from uri +
<BR>display string trick as i have described. &nbsp;since my basic rule is "if it
<BR>not broken, don't fix it", i'm not interested to change the current
<BR>working practice just for the sake of it.
<BR>
<BR>-- juha
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">Again, I think the comments and different opinions expressed clearly indicate that it is "broke", even if it may just be the description of the use of From and "Anonymous". But it seems that any attempt to redefine (or better define?) these fields results in a claim that it "breaks" some current implementation.
<BR>
<BR>In a message dated 4/18/02 7:46:00 AM Eastern Daylight Time, mwatson@nortelnetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Yes, 3GPP has this requirement too. But it is a slightly separate question from the NAI itself. If we follow the SHOULD in the SIP specification about the From uri being meaningless when the user requests privacy, then another field is needed to allow the user to choose which identity will be used for the Network Asserted Identity out of a particular set.</BLOCKQUOTE>
<BR>
<BR>Yes, I believe Mark is correct, another field is required which is only intended for the UA to tell the "network" their identity and the network is expected to verify it and may reject calls that don't have a valid identity. The UA can not fill it with "meaningless" information. In some cases it may be omitted. What the "network" might do with it is another issue.
<BR>
<BR>Mike
<BR></FONT></HTML>

--part1_118.102f7bd1.29f07aff_boundary--

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



From daemon@optimus.ietf.org  Thu Apr 18 15:50:10 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20995
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 15:50:10 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA28307
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 15:50:10 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA27785;
	Thu, 18 Apr 2002 15:40:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA27742
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 15:40:35 -0400 (EDT)
Received: from imo-d04.mx.aol.com (imo-d04.mx.aol.com [205.188.157.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20612
	for <sipping@ietf.org>; Thu, 18 Apr 2002 15:40:29 -0400 (EDT)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-d04.mx.aol.com (mail_out_v32.5.) id d.b2.a2e2d9c (4397);
	Thu, 18 Apr 2002 15:39:46 -0400 (EDT)
Message-ID: <b2.a2e2d9c.29f07b01@aol.com>
Date: Thu, 18 Apr 2002 15:39:45 EDT
Subject: Re: [Sipping] RE: Network Asserted Identity
To: mwatson@nortelnetworks.com, sipping@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_b2.a2e2d9c.29f07b01_boundary"
X-Mailer: AOL 6.0 for Windows US sub 10524
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


--part1_b2.a2e2d9c.29f07b01_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 4/18/02 10:13:57 AM Eastern Daylight Time, 
mwatson@nortelnetworks.com writes:


> > For clarity, 
> > (a) the requirement for a user to choose one of a number of 
> > identities, whilst retaining privacy, is a 3GPP requirement, 
> > but is *out of scope* of this thread. 
> 

The question still remains - what is "user" in the above statement. When I 
log into AOL (yea, I know, bad idea) I can specify one of several identities 
(screen name). If I had a SIP phone, it would likely be capable of multiple 
identities that I personally might use or someone else would use. So there is 
clearly a requirement for the "User Agent" (the device) to choose one of a 
number of identities. I believe there is also a clear need for the "user" 
(person) to choose one of a number of identies. So why is this not a 
requirement, other than for 3GPP? Note that my above statements are not 
directly addressing "privacy", but just the "identity" part of the issue. The 
requirements for choosing privacy should be the same.

Mike


--part1_b2.a2e2d9c.29f07b01_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 4/18/02 10:13:57 AM Eastern Daylight Time, mwatson@nortelnetworks.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">&gt; For clarity, 
<BR>&gt; (a) the requirement for a user to choose one of a number of 
<BR>&gt; identities, whilst retaining privacy, is a 3GPP requirement, 
<BR>&gt; but is *out of scope* of this thread. 
<BR></BLOCKQUOTE>
<BR>
<BR>The question still remains - what is "user" in the above statement. When I log into AOL (yea, I know, bad idea) I can specify one of several identities (screen name). If I had a SIP phone, it would likely be capable of multiple identities that I personally might use or someone else would use. So there is clearly a requirement for the "User Agent" (the device) to choose one of a number of identities. I believe there is also a clear need for the "user" (person) to choose one of a number of identies. So why is this not a requirement, other than for 3GPP? Note that my above statements are not directly addressing "privacy", but just the "identity" part of the issue. The requirements for choosing privacy should be the same.
<BR>
<BR>Mike
<BR></FONT></HTML>

--part1_b2.a2e2d9c.29f07b01_boundary--

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



From daemon@optimus.ietf.org  Thu Apr 18 15:51:35 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21041
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 15:51:35 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA28417
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 15:51:39 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA27972;
	Thu, 18 Apr 2002 15:42:32 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA27937
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 15:42:28 -0400 (EDT)
Received: from web11604.mail.yahoo.com (web11604.mail.yahoo.com [216.136.172.56])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA20708
	for <sipping@ietf.org>; Thu, 18 Apr 2002 15:42:24 -0400 (EDT)
Message-ID: <20020418194226.20540.qmail@web11604.mail.yahoo.com>
Received: from [131.107.3.72] by web11604.mail.yahoo.com via HTTP; Thu, 18 Apr 2002 12:42:26 PDT
Date: Thu, 18 Apr 2002 12:42:26 -0700 (PDT)
From: Sean Olson <seancolson@yahoo.com>
Subject: Re: [Sipping] IPv6 messages for callflows?
To: Pekka Pessi <Pekka.Pessi@nokia.com>, Jiri Kuthan <kuthan@fokus.gmd.de>
Cc: Pekka Pessi <Pekka.Pessi@nokia.com>, sipping@ietf.org
In-Reply-To: <pv4riafgfn.fsf@agni.research.nokia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

I agree. IPv6reference should be used almost
exclusively. This uniformity makes it much easier
to build.

/sean

--- Pekka Pessi <Pekka.Pessi@nokia.com> wrote:
> In message
>
<5.1.0.14.0.20020417125022.02dc7e50@mailhost.fokus.gmd.de>
> Jiri Kuthan <kuthan@fokus.gmd.de> writes:
> >one of our developpers meant there was a bug in
> your example. Can you
> >verify that?
> 
> 	The request is a valid SIP message and it should be
> accepted.
> 	The
> "received=[3ffe:1200:3012:c006:210:a4ff:fe8d:6a46]"
> 	parameter in question actually matches the
> generic-param rule in
> 	the bis-09 ABNF.
> 
> >> > Via: SIP/2.0/UDP
> [3ffe:1200:3012:c000:210:a4ff:fe8d:6a46]:5062 
> >> > ;branch=z9hG4bKuNCTHs8Lumv 
> >> >
> ;received=[3ffe:1200:3012:c006:210:a4ff:fe8d:6a46] 
> >^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
> >this is an IPv6reference. the "received" param is
> defined as
> >via-received = "received" EQUAL ( IPv4address /
> IPv6address ) 
> >(see page 241 of draft-ietf-sip-rfc2543bis-09)
> ^^^^^^^^^^^ 
> >So this is illegal, because an IPv6address is
> basically not the same as an 
> >IPv6reference: IPv6reference = "[" IPv6address "]"
> >The same is in 7.43
> >Did I miss something ? Or do I have an old draft ?
> 
> 	I'd say the bug is in the spec (bis-09), the 
> 
> via-received = "received" EQUAL ( IPv4address /
> IPv6address ) 
> 
> 	should be replaced with 
> 
> via-received = "received" EQUAL ( IPv4address /
> IPv6reference ) 
> 
> 	Did they managed to publish 3261? 
> 
> 					Pekka
> 
> 
> _______________________________________________
> Sipping mailing list 
> https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application
> of SIP
> Use sip-implementors@cs.columbia.edu for questions
> on current sip
> Use sip@ietf.org for new developments of core SIP


=====
Sean Olson <seancolson@yahoo.com>

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

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



From daemon@optimus.ietf.org  Thu Apr 18 16:08:47 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21438
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 16:08:47 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA29528
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 16:08:51 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA27735;
	Thu, 18 Apr 2002 15:40:32 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA27668
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 15:40:28 -0400 (EDT)
Received: from imo-d02.mx.aol.com (imo-d02.mx.aol.com [205.188.157.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20595
	for <sipping@ietf.org>; Thu, 18 Apr 2002 15:40:23 -0400 (EDT)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-d02.mx.aol.com (mail_out_v32.5.) id c.197.596ed06 (4397);
	Thu, 18 Apr 2002 15:39:40 -0400 (EDT)
Message-ID: <197.596ed06.29f07afc@aol.com>
Date: Thu, 18 Apr 2002 15:39:40 EDT
To: rohan@cisco.com
CC: sipping@ietf.org, brian.rosen@marconi.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_197.596ed06.29f07afc_boundary"
X-Mailer: AOL 6.0 for Windows US sub 10524
Subject: [Sipping] Re: Cookies vs. State
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


--part1_197.596ed06.29f07afc_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 4/18/02 11:02:35 AM Eastern Daylight Time, rohan@cisco.com 
writes:


> > Further, as Dean wrote: 'Both approaches leave the format of the "hunk" 
> open
> > -- it could be cryptographically protected, just a hash value matching a
> > table stored on the proxy, or almost anything else.' It seems to me that 
> any
> > of these security measures would prevent another proxy from being able to
> > understand the State or Cookie anyway, unless they share keys. Wouldn't 
> that
> > be as hard as sharing states?
> 
> no.  have you ever implemented a robust, real-time, high-availability
> 

Yes, I've been involved in the design and implementation of 3 telephony 
switching systems, where the presumed requirement was for high 
reliability/almost no down time. They operated on the principle of 
active/standby processors and critical peripherals and performed "state" 
sharing between the two sides in order to support switch-over when the active 
side failed. I guess coming from this design background, I continue to wonder 
why so much effort is being put into complex protocols and procedures between 
devices which have a high failure rate and down time rather than tackling the 
real problem. Telephone and data switching equipment in the past was designed 
for low failure and down time and I continue to wonder why I keep getting 
e-mails from our system administrator that "The LAN or e-mail server will be 
down for several hours for maintenance".

> 
> > As Dean noted: "I also believe the security concern is SLIGHTLY less 
> urgent
> > than in HTTP. As I understand it, both state and cookie drafts indicate a
> > substantially shorter lifetime for the token. In the case of state, the
> > lifetime is the duration of the current dialog. In the case of cookie, 
> it's
> > the current dialog plus any dialog resulting from redirection or referral 
> of
> > the original dialog.
> > HTTP cookies, on the other hand, persist relatively indefiitely and may be
> > extracted by any server in the domain of the cookie during any HTTP
> > interaction with said server for the duraction of the cookie."
> >
> > I addressed this issue of Cookie persistance in my November 19 comments 
> which
> > I will repeat below. The only way that "Cookie" can be allowed is if it 
> must
> > be erased at the end of a call and if it can not be read by any proxy 
> other
> > than the one setting up the call (or by a limited set which may take over 
> for
> > another proxy in the case of proxy failure and which the UA can verify is
> > allowed to handle the call further). Any other use would be a serious
> > security problem and probably illegal in some places. A device must be
> > considered non-compliant if it does not erase the "Cookie".
> 
> Perhaps this should be more obvious, but Section 5.1 of the SIP cookies
> draft states:
> 
>    Cookies are discarded when the call instantiating the cookie and all
>    

> The purpose of this sentence was clearly to prevent the kind of abuses
> permitted by the current HTTP mechanism.  Would you be satisfied if this
> sentence said "Cookies MUST be discarded..." ?
> 
> 
That was my comment. Any device which does not guarantee that the Cookie is 
thrown away when I "hang up" is non-compliant.

Mike


--part1_197.596ed06.29f07afc_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 4/18/02 11:02:35 AM Eastern Daylight Time, rohan@cisco.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">&gt; Further, as Dean wrote: 'Both approaches leave the format of the "hunk" open
<BR>&gt; -- it could be cryptographically protected, just a hash value matching a
<BR>&gt; table stored on the proxy, or almost anything else.' It seems to me that any
<BR>&gt; of these security measures would prevent another proxy from being able to
<BR>&gt; understand the State or Cookie anyway, unless they share keys. Wouldn't that
<BR>&gt; be as hard as sharing states?
<BR>
<BR>no. &nbsp;have you ever implemented a robust, real-time, high-availability
<BR>state sharing mechanism in software?</BLOCKQUOTE>
<BR>
<BR>Yes, I've been involved in the design and implementation of 3 telephony switching systems, where the presumed requirement was for high reliability/almost no down time. They operated on the principle of active/standby processors and critical peripherals and performed "state" sharing between the two sides in order to support switch-over when the active side failed. I guess coming from this design background, I continue to wonder why so much effort is being put into complex protocols and procedures between devices which have a high failure rate and down time rather than tackling the real problem. Telephone and data switching equipment in the past was designed for low failure and down time and I continue to wonder why I keep getting e-mails from our system administrator that "The LAN or e-mail server will be down for several hours for maintenance".
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
<BR>&gt; As Dean noted: "I also believe the security concern is SLIGHTLY less urgent
<BR>&gt; than in HTTP. As I understand it, both state and cookie drafts indicate a
<BR>&gt; substantially shorter lifetime for the token. In the case of state, the
<BR>&gt; lifetime is the duration of the current dialog. In the case of cookie, it's
<BR>&gt; the current dialog plus any dialog resulting from redirection or referral of
<BR>&gt; the original dialog.
<BR>&gt; HTTP cookies, on the other hand, persist relatively indefiitely and may be
<BR>&gt; extracted by any server in the domain of the cookie during any HTTP
<BR>&gt; interaction with said server for the duraction of the cookie."
<BR>&gt;
<BR>&gt; I addressed this issue of Cookie persistance in my November 19 comments which
<BR>&gt; I will repeat below. The only way that "Cookie" can be allowed is if it must
<BR>&gt; be erased at the end of a call and if it can not be read by any proxy other
<BR>&gt; than the one setting up the call (or by a limited set which may take over for
<BR>&gt; another proxy in the case of proxy failure and which the UA can verify is
<BR>&gt; allowed to handle the call further). Any other use would be a serious
<BR>&gt; security problem and probably illegal in some places. A device must be
<BR>&gt; considered non-compliant if it does not erase the "Cookie".
<BR>
<BR>Perhaps this should be more obvious, but Section 5.1 of the SIP cookies
<BR>draft states:
<BR>
<BR> &nbsp;&nbsp;Cookies are discarded when the call instantiating the cookie and all
<BR> &nbsp;&nbsp;calls derived from that call have terminated.</BLOCKQUOTE>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">The purpose of this sentence was clearly to prevent the kind of abuses
<BR>permitted by the current HTTP mechanism. &nbsp;Would you be satisfied if this
<BR>sentence said "Cookies MUST be discarded..." ?
<BR>
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">That was my comment. Any device which does not guarantee that the Cookie is thrown away when I "hang up" is non-compliant.
<BR>
<BR>Mike
<BR></FONT></HTML>

--part1_197.596ed06.29f07afc_boundary--

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



From daemon@optimus.ietf.org  Thu Apr 18 16:16:34 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21599
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 16:16:34 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA29720
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 16:16:34 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA29493;
	Thu, 18 Apr 2002 16:07:07 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA29458
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 16:07:03 -0400 (EDT)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21418
	for <sipping@ietf.org>; Thu, 18 Apr 2002 16:06:55 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g3IK68No002784;
	Thu, 18 Apr 2002 13:06:09 -0700 (PDT)
Received: from localhost (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint)
	with ESMTP id ACX10663;
	Thu, 18 Apr 2002 13:06:21 -0700 (PDT)
Date: Thu, 18 Apr 2002 13:03:25 -0700 (Pacific Daylight Time)
From: Rohan Mahy <rohan@cisco.com>
To: Mpierce1@aol.com
cc: sipping@ietf.org, <brian.rosen@marconi.com>
In-Reply-To: <197.596ed06.29f07afc@aol.com>
Message-ID: <Pine.WNT.4.44.0204181259380.-438321@chorizo.rapidconvergence.com>
X-X-Sender: rmahy@imop.cisco.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Sipping] Re: Cookies vs. State
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org



On Thu, 18 Apr 2002 Mpierce1@aol.com wrote:

> In a message dated 4/18/02 11:02:35 AM Eastern Daylight Time, rohan@cisco.com
> writes:
>
>
> > > Further, as Dean wrote: 'Both approaches leave the format of the "hunk"
> > open
> > > -- it could be cryptographically protected, just a hash value matching a
> > > table stored on the proxy, or almost anything else.' It seems to me that
> > any
> > > of these security measures would prevent another proxy from being able to
> > > understand the State or Cookie anyway, unless they share keys. Wouldn't
> > that
> > > be as hard as sharing states?
> >
> > no.  have you ever implemented a robust, real-time, high-availability
> >
>
> Yes, I've been involved in the design and implementation of 3 telephony
> switching systems, where the presumed requirement was for high
> reliability/almost no down time. They operated on the principle of
> active/standby processors and critical peripherals and performed "state"
> sharing between the two sides in order to support switch-over when the active
> side failed. I guess coming from this design background, I continue to wonder
> why so much effort is being put into complex protocols and procedures between
> devices which have a high failure rate and down time rather than tackling the
> real problem. Telephone and data switching equipment in the past was designed
> for low failure and down time and I continue to wonder why I keep getting
> e-mails from our system administrator that "The LAN or e-mail server will be
> down for several hours for maintenance".

Based on your description, you did not implement such a system in software
(as I queried), but in hardware instead.  It is fundamental to the
Internet model to use lots of cheap distributed components.  Despite the
phone systems better reliability during oridinary usage, the Internet
continues to adapt better to unforseen massive failures.  Your Mileage May
Vary.

> > > As Dean noted: "I also believe the security concern is SLIGHTLY less
> > urgent
> > > than in HTTP. As I understand it, both state and cookie drafts indicate a
> > > substantially shorter lifetime for the token. In the case of state, the
> > > lifetime is the duration of the current dialog. In the case of cookie,
> > it's
> > > the current dialog plus any dialog resulting from redirection or referral
> > of
> > > the original dialog.
> > > HTTP cookies, on the other hand, persist relatively indefiitely and may be
> > > extracted by any server in the domain of the cookie during any HTTP
> > > interaction with said server for the duraction of the cookie."
> > >
> > > I addressed this issue of Cookie persistance in my November 19 comments
> > which
> > > I will repeat below. The only way that "Cookie" can be allowed is if it
> > must
> > > be erased at the end of a call and if it can not be read by any proxy
> > other
> > > than the one setting up the call (or by a limited set which may take over
> > for
> > > another proxy in the case of proxy failure and which the UA can verify is
> > > allowed to handle the call further). Any other use would be a serious
> > > security problem and probably illegal in some places. A device must be
> > > considered non-compliant if it does not erase the "Cookie".
> >
> > Perhaps this should be more obvious, but Section 5.1 of the SIP cookies
> > draft states:
> >
> >    Cookies are discarded when the call instantiating the cookie and all
> >
>
> > The purpose of this sentence was clearly to prevent the kind of abuses
> > permitted by the current HTTP mechanism.  Would you be satisfied if this
> > sentence said "Cookies MUST be discarded..." ?
> >
> >
> That was my comment. Any device which does not guarantee that the Cookie is
> thrown away when I "hang up" is non-compliant.

Agreed.

thanks,
-rohan


> Mike
>
>


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



From daemon@optimus.ietf.org  Thu Apr 18 17:18:31 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23281
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 17:18:31 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA04146
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 17:18:35 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA03048;
	Thu, 18 Apr 2002 17:03:56 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA02889
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 17:03:46 -0400 (EDT)
Received: from pmesmtp02.wcom.com (pmesmtp02.wcom.com [199.249.20.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22863
	for <sipping@ietf.org>; Thu, 18 Apr 2002 17:03:41 -0400 (EDT)
Received: from CONVERSION-DAEMON by firewall.wcom.com (PMDF V5.2-32 #42257)
 id <0GUS00I017QHEC@firewall.wcom.com> for sipping@ietf.org; Thu,
 18 Apr 2002 21:01:29 +0000 (GMT)
Received: from dgismtp05.wcomnet.com ([166.38.58.88])
 by firewall.wcom.com (PMDF V5.2-32 #42257)
 with ESMTP id <0GUS00GEM7PZFJ@firewall.wcom.com>; Thu,
 18 Apr 2002 21:01:29 +0000 (GMT)
Received: from dgismtp05.wcomnet.com by dgismtp05.wcomnet.com
 (iPlanet Messaging Server 5.1 (built May  7 2001))
 with SMTP id <0GUS005017MDU7@dgismtp05.wcomnet.com>; Thu,
 18 Apr 2002 21:00:14 +0000 (GMT)
Received: from hsinnreich2 ([166.35.224.250])
 by dgismtp05.wcomnet.com (iPlanet Messaging Server 5.1 (built May  7 2001))
 with ESMTP id <0GUS004F87O6V6@dgismtp05.wcomnet.com>; Thu,
 18 Apr 2002 21:00:07 +0000 (GMT)
Date: Thu, 18 Apr 2002 16:00:25 -0500
From: Henry Sinnreich <Henry.Sinnreich@wcom.com>
Subject: RE: [Sipping] Re: Cookies vs. State
In-reply-to: <197.596ed06.29f07afc@aol.com>
To: Mpierce1@aol.com, rohan@cisco.com
Cc: sipping@ietf.org, brian.rosen@marconi.com
Message-id: <008601c1e71c$1094eae0$fae023a6@hsinnreich2>
Organization: WorldCom, Inc.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

>"The LAN or e-mail server will be down for several hours for
maintenance". 

Sorry, but this does not happen in environments that have a distributed
server architecture, with DNS based or other load sharing approach. I
don't like to say it, but I am just fortunate to live in such a
resilient network, so I know it can be done with non-telephony, non-
"carrier strength" approach. The "carrier strength" boxes were and still
are designed for the single mode of failure architecture in the ITU-T
central control models. Or in the softswitch and many IP PBX models.

Henry


-----Original Message-----
From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] On Behalf
Of Mpierce1@aol.com
Sent: Thursday, April 18, 2002 2:40 PM
To: rohan@cisco.com
Cc: sipping@ietf.org; brian.rosen@marconi.com
Subject: [Sipping] Re: Cookies vs. State


In a message dated 4/18/02 11:02:35 AM Eastern Daylight Time,
rohan@cisco.com writes: 



> Further, as Dean wrote: 'Both approaches leave the format of the
"hunk" open 
> -- it could be cryptographically protected, just a hash value matching
a 
> table stored on the proxy, or almost anything else.' It seems to me
that any 
> of these security measures would prevent another proxy from being able
to 
> understand the State or Cookie anyway, unless they share keys.
Wouldn't that 
> be as hard as sharing states? 

no.  have you ever implemented a robust, real-time, high-availability 
state sharing mechanism in software?


Yes, I've been involved in the design and implementation of 3 telephony
switching systems, where the presumed requirement was for high
reliability/almost no down time. They operated on the principle of
active/standby processors and critical peripherals and performed "state"
sharing between the two sides in order to support switch-over when the
active side failed. I guess coming from this design background, I
continue to wonder why so much effort is being put into complex
protocols and procedures between devices which have a high failure rate
and down time rather than tackling the real problem. Telephone and data
switching equipment in the past was designed for low failure and down
time and I continue to wonder why I keep getting e-mails from our system
administrator that "The LAN or e-mail server will be down for several
hours for maintenance". 



> As Dean noted: "I also believe the security concern is SLIGHTLY less
urgent 
> than in HTTP. As I understand it, both state and cookie drafts
indicate a 
> substantially shorter lifetime for the token. In the case of state,
the 
> lifetime is the duration of the current dialog. In the case of cookie,
it's 
> the current dialog plus any dialog resulting from redirection or
referral of 
> the original dialog. 
> HTTP cookies, on the other hand, persist relatively indefiitely and
may be 
> extracted by any server in the domain of the cookie during any HTTP 
> interaction with said server for the duraction of the cookie." 
> 
> I addressed this issue of Cookie persistance in my November 19
comments which 
> I will repeat below. The only way that "Cookie" can be allowed is if
it must 
> be erased at the end of a call and if it can not be read by any proxy
other 
> than the one setting up the call (or by a limited set which may take
over for 
> another proxy in the case of proxy failure and which the UA can verify
is 
> allowed to handle the call further). Any other use would be a serious 
> security problem and probably illegal in some places. A device must be

> considered non-compliant if it does not erase the "Cookie". 

Perhaps this should be more obvious, but Section 5.1 of the SIP cookies 
draft states: 

  Cookies are discarded when the call instantiating the cookie and all 
  calls derived from that call have terminated.



The purpose of this sentence was clearly to prevent the kind of abuses 
permitted by the current HTTP mechanism.  Would you be satisfied if this

sentence said "Cookies MUST be discarded..." ? 



That was my comment. Any device which does not guarantee that the Cookie
is thrown away when I "hang up" is non-compliant. 

Mike 


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



From daemon@optimus.ietf.org  Thu Apr 18 17:58:16 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24085
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 17:58:16 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA06856
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 17:58:21 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA06169;
	Thu, 18 Apr 2002 17:45:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA06140
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 17:45:53 -0400 (EDT)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23880
	for <sipping@ietf.org>; Thu, 18 Apr 2002 17:45:48 -0400 (EDT)
Received: from cia.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g3ILjdnQ005096;
	Thu, 18 Apr 2002 17:45:39 -0400 (EDT)
Received: from MHAMMER-W2K.cisco.com (hrn2-dhcp-161-44-87-145.cisco.com [161.44.87.145])
	by cia.cisco.com (Mirapoint)
	with ESMTP id AAU27324;
	Thu, 18 Apr 2002 17:40:12 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020418171051.00b92de8@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 18 Apr 2002 17:45:13 -0400
To: Mpierce1@aol.com
From: Michael Hammer <mhammer@cisco.com>
Subject: Re: [Sipping] Screened From: and Privacy
Cc: jh@lohi.eng.song.fi, zmolek@avaya.com, R.Jesske@telekom.de,
        dean.willis@softarmor.com, sipping@ietf.org
In-Reply-To: <118.102f7bd1.29f07aff@aol.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

I finally got to the end of this thread!
My observation of what this boils down to:

The user may wish to project a public identity end-to-end (UAI).
The UAI may not be valid for authentication.
The network has a need to identify the user to authorized third parties (NAI).
There are legal requirements for "public" service providers to restrict the 
NAI.

Question:  Can UAI and NAI be one and the same?
Answer: Not unless:
a) it is possible to modify that parameter along the way,
b) it is OK to block the end-to-end UAI.

If you want From: field that means it must be modifiable or use B2BUA.

To meet legal requirements:
The network entity must be able to authenticate the subscriber.
The network entity must be able to set/reset the NAI value.
The network entity must be able to restrict passing the NAI value to any 
next hop not authorized to see it.

The question of hop-by-hop versus end-to-end trust chains determines 
whether a crypto-based solution or service agreement arrangement may be used.

One added wrinkle:  Given that a public service provider may not have 
sufficient information to authenticate the data in the From: field, will 
the legal requirements drive all intermediate hops to be public service 
providers if the From: field falls under the Privacy Rules?  (Falls out of 
the assumption that a public carrier refuses all calls unless from a 
trusted carrier, or from an authenticatable user.)

Mike

At 03:39 PM 4/18/2002 -0400, Mpierce1@aol.com wrote:
>In a message dated 4/18/02 1:20:14 AM Eastern Daylight Time, 
>jh@lohi.eng.song.fi writes:
>
>
>>
>>if the user has given display string "Anonymous" and the call gets
>>routed to sip destination, i must implement b2bua and make also the from
>>uri anonymous.  if the call gets routed to pstn, i set the calling party
>>number blocking parameter.
>>
>><snip>
>>
>>i still don't understand what this whole thread is all about and i still
>>haven't got a reply to my question what advantage rpid or some other new
>>header field would bring as compared to the current situation.
>>
>>-- juha
>
>
>It's obvious to me that there is not a consistent opinion of what the 
>"current situation" is. I believe I've heard several different 
>interpretations of what bis-09 says regarding the From and the use of 
>"anonymous" in the Display name. For example, your comment above is that, 
>if the user puts in "Anonymous", you (as the servie provider) must do 
>something to the uri. I don't read that in bis-09. It says that if the 
>user wants to remain hidden "a UAC SHOULD use ... "Anonymous", along with 
>... a meaningless URI." So what really is the "current situation"?
>
>In a message dated 4/18/02 8:02:13 AM Eastern Daylight Time, 
>jh@lohi.eng.song.fi writes:
>
>
>>you could define another header field for that purpose, but in the
>>meanwhile, i need to be able to run my sip service with CURRENT UAs,
>>proxies, and sip/ss7 gws all of which today support the from uri +
>>display string trick as i have described.  since my basic rule is "if it
>>not broken, don't fix it", i'm not interested to change the current
>>working practice just for the sake of it.
>>
>>-- juha
>
>Again, I think the comments and different opinions expressed clearly 
>indicate that it is "broke", even if it may just be the description of the 
>use of From and "Anonymous". But it seems that any attempt to redefine (or 
>better define?) these fields results in a claim that it "breaks" some 
>current implementation.
>
>In a message dated 4/18/02 7:46:00 AM Eastern Daylight Time, 
>mwatson@nortelnetworks.com writes:
>
>
>>Yes, 3GPP has this requirement too. But it is a slightly separate 
>>question from the NAI itself. If we follow the SHOULD in the SIP 
>>specification about the From uri being meaningless when the user requests 
>>privacy, then another field is needed to allow the user to choose which 
>>identity will be used for the Network Asserted Identity out of a 
>>particular set.
>
>
>Yes, I believe Mark is correct, another field is required which is only 
>intended for the UA to tell the "network" their identity and the network 
>is expected to verify it and may reject calls that don't have a valid 
>identity. The UA can not fill it with "meaningless" information. In some 
>cases it may be omitted. What the "network" might do with it is another issue.
>
>Mike


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



From daemon@optimus.ietf.org  Thu Apr 18 19:21:30 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25366
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 19:21:30 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA11719
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 19:21:33 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA11456;
	Thu, 18 Apr 2002 19:12:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA11423
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 19:12:12 -0400 (EDT)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25276
	for <sipping@ietf.org>; Thu, 18 Apr 2002 19:12:08 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g3INBN2q013319
	for <sipping@ietf.org>; Thu, 18 Apr 2002 16:11:23 -0700 (PDT)
Received: from localhost (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint)
	with ESMTP id ACX12911;
	Thu, 18 Apr 2002 16:11:40 -0700 (PDT)
Date: Thu, 18 Apr 2002 16:08:44 -0700 (Pacific Daylight Time)
From: Rohan Mahy <rohan@cisco.com>
To: sipping@ietf.org
Message-ID: <Pine.WNT.4.44.0204181606420.-438321@chorizo.rapidconvergence.com>
X-X-Sender: rmahy@imop.cisco.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Sipping] Proposed plan for Network Identity/Privacy
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

FYI:

I just posted a proposal to the sip list, in an attempt to break the
current privacy/network identity log jamb.  Please provide comments there.

thanks,
-rohan




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



From daemon@optimus.ietf.org  Thu Apr 18 19:26:22 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25427
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 19:26:22 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA11847
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 19:26:25 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA11581;
	Thu, 18 Apr 2002 19:14:50 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA11552
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 19:14:47 -0400 (EDT)
Received: from mail1.microsoft.com (mail1.microsoft.com [131.107.3.125])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25296
	for <sipping@ietf.org>; Thu, 18 Apr 2002 19:14:43 -0400 (EDT)
Received: from inet-vrs-01.redmond.corp.microsoft.com ([157.54.8.27]) by mail1.microsoft.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Thu, 18 Apr 2002 16:13:21 -0700
Received: from 157.54.8.23 by inet-vrs-01.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 18 Apr 2002 16:14:14 -0700
Received: from red-msg-12.redmond.corp.microsoft.com ([157.54.2.26]) by inet-hub-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.4905);
	 Thu, 18 Apr 2002 16:13:23 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6177.0
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="------------InterScan_NT_MIME_Boundary"
Date: Thu, 18 Apr 2002 16:13:23 -0700
Message-ID: <E5B814702B65CB4DA51644580E4853FB02845789@red-msg-12.redmond.corp.microsoft.com>
Thread-Topic: REFER usage in multiparty application and call control
Thread-Index: AcHnLsCg8vEFFJ5+Qt+lMErB/mzFJA==
From: "Aaron Lo" <aaronlo@microsoft.com>
To: <sipping@ietf.org>
X-OriginalArrivalTime: 18 Apr 2002 23:13:23.0751 (UTC) FILETIME=[A34FC370:01C1E72E]
Subject: [Sipping] REFER usage in multiparty application and call control
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E72E.A34023BB"

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

Hi all,

=20

I have a question regarding the use of REFER in peer to peer multiparty
applications and call control.

=20

Say a UAS receives a REFER, how would it distinguish a REFER used for
multiparty application from a REFER used in call control?=20

Or, to put it differently, do we really care if the REFER is different?

Thanks.

=20

Aaron


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

<html>

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


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

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

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi all,</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'>I have a question regarding the use of REFER in peer =
to peer
multiparty applications and call control.</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'>Say a UAS receives a REFER, how would it distinguish =
a REFER
used for multiparty application from a REFER used in call control? =
</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Or, to put it differently, do we really care if the =
REFER is
different?</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thanks.</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'>Aaron</span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C1E72E.A34023BB--

--------------InterScan_NT_MIME_Boundary--


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



From daemon@ns.ietf.org  Thu Apr 18 20:12:26 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26246
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 20:12:22 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA14210
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 20:12:25 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA12658;
	Thu, 18 Apr 2002 19:43:14 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA12633
	for <sipping@optimus.ietf.org>; Thu, 18 Apr 2002 19:43:12 -0400 (EDT)
Received: from imo-r04.mx.aol.com (imo-r04.mx.aol.com [152.163.225.100])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25666
	for <sipping@ietf.org>; Thu, 18 Apr 2002 19:43:08 -0400 (EDT)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r04.mx.aol.com (mail_out_v32.5.) id e.2b.25d26488 (3935);
	Thu, 18 Apr 2002 19:42:22 -0400 (EDT)
Message-ID: <2b.25d26488.29f0b3de@aol.com>
Date: Thu, 18 Apr 2002 19:42:22 EDT
Subject: Re: [Sipping] Re: Cookies vs. State
To: Brian.Rosen@marconi.com, rohan@cisco.com, sipping@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_2b.25d26488.29f0b3de_boundary"
X-Mailer: AOL 6.0 for Windows US sub 10524
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


--part1_2b.25d26488.29f0b3de_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 4/18/02 1:28:15 PM Eastern Daylight Time, 
Brian.Rosen@marconi.com writes:


> >----------------------------------------------------- 
> >Comments on draft-willis-sip-cookies-00: 
> >
> >This draft provides a good base-line for definition of a SIP-cookie
> functionality, >derived from RFC 2109. 
> >
> >Some comments/observations: 
> >
> <Mike's original comments snipped>


> In HTTP, cookies are often "permanent".  Most of the abuse of cookies 
> comes from this use.  Of course you can discard HTTP cookies at any time.
> You may lose some "services" if you do.  Same with SIP cookies, but we
> specify that cookies ARE NOT saved across sessions, primarily to avoid
> the abuse that we have seen with HTTP cookies.
> 

Then an explicit statement needs to be added that cookies MUST be discarded 
at the end of a call.

> 
> Woah, you don't send ALL stored cookies, you send those associated with
> a particular call.  Message size can be a problem, in wireless networks,
> and when message size exceeds MTU size with UDP.  That is a consideration
> which the draft should note.
> 

Yes, I hope that you don't send all, but the draft didn't seem to say that. 
It indicated that all cookies recieved for a call must be kept and that every 
cookie stored for a call must be sent in every message. Since there could not 
be any cookies for any previous call, all stored cookies must be sent in 
every message.

If the point is to store "state" in the UA by this method, then it's obvious 
to me that the requirement is to store exactly one Cookie per call. (One 
could argue whether a multipoint call like three way calling is modeled as 
one call or two.)

> 
> 
> Several others have noted that it is much easier to support high 
> availability
> when state is stored in the endpoints rather than to have replication
> mechanisms and all sorts of other gunk required when state is maintained
> in the proxy server.  Some would say that while call-statefull proxies
> may be needed for some services, they are mostly undesirable, and
> SIP is designed for statefull UAs and stateless proxies.  Cookies
> continues that design philosophy.

High availability with everything stored in one place is certainly easier 
than storing the data in end devices and working out all the protocol and 
security issues to fetch it whenever feature processing needs to know it. 
Design technique for highly reliable systems, often based on redundant pairs 
with sharing of state information, has been around for decades.

And I continue to puzzle over why a call stateful, highly reliable proxy to 
control some service is considered to be "undesirable". And it's not 
sufficient to say "because that's not the way http did it".

Mike




--part1_2b.25d26488.29f0b3de_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 4/18/02 1:28:15 PM Eastern Daylight Time, Brian.Rosen@marconi.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">&gt;----------------------------------------------------- 
<BR>&gt;Comments on draft-willis-sip-cookies-00: 
<BR>&gt;
<BR>&gt;This draft provides a good base-line for definition of a SIP-cookie
<BR>functionality, &gt;derived from RFC 2109. 
<BR>&gt;
<BR>&gt;Some comments/observations: 
<BR>&gt;
<BR>&lt;Mike's original comments snipped&gt;</FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR>
<BR>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0"><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">In HTTP, cookies are often "permanent". &nbsp;Most of the abuse of cookies 
<BR>comes from this use. &nbsp;Of course you can discard HTTP cookies at any time.
<BR>You may lose some "services" if you do. &nbsp;Same with SIP cookies, but we
<BR>specify that cookies ARE NOT saved across sessions, primarily to avoid
<BR>the abuse that we have seen with HTTP cookies.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">Then an explicit statement needs to be added that cookies MUST be discarded at the end of a call.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0"><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
<BR>Woah, you don't send ALL stored cookies, you send those associated with
<BR>a particular call. &nbsp;Message size can be a problem, in wireless networks,
<BR>and when message size exceeds MTU size with UDP. &nbsp;That is a consideration
<BR>which the draft should note.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">Yes, I hope that you don't send all, but the draft didn't seem to say that. It indicated that all cookies recieved for a call must be kept and that every cookie stored for a call must be sent in every message. Since there could not be any cookies for any previous call, all stored cookies must be sent in every message.
<BR>
<BR>If the point is to store "state" in the UA by this method, then it's obvious to me that the requirement is to store exactly one Cookie per call. (One could argue whether a multipoint call like three way calling is modeled as one call or two.)
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0"><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
<BR>
<BR>Several others have noted that it is much easier to support high availability
<BR>when state is stored in the endpoints rather than to have replication
<BR>mechanisms and all sorts of other gunk required when state is maintained
<BR>in the proxy server. &nbsp;Some would say that while call-statefull proxies
<BR>may be needed for some services, they are mostly undesirable, and
<BR>SIP is designed for statefull UAs and stateless proxies. &nbsp;Cookies
<BR>continues that design philosophy.</FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">High availability with everything stored in one place is certainly easier than storing the data in end devices and working out all the protocol and security issues to fetch it whenever feature processing needs to know it. Design technique for highly reliable systems, often based on redundant pairs with sharing of state information, has been around for decades.
<BR>
<BR>And I continue to puzzle over why a call stateful, highly reliable proxy to control some service is considered to be "undesirable". And it's not sufficient to say "because that's not the way http did it".
<BR>
<BR>Mike
<BR>
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></FONT></HTML>

--part1_2b.25d26488.29f0b3de_boundary--

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



From daemon@ns.ietf.org  Thu Apr 18 21:59:44 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28669
	for <sipping-archive@odin.ietf.org>; Thu, 18 Apr 2002 21:59:44 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA19295
	for sipping-archive@odin.ietf.org; Thu, 18 Apr 2002 21:59:48 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA19053;
	Thu, 18 Apr 2002 21:49:48 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA19022
	for <sipping@ns.ietf.org>; Thu, 18 Apr 2002 21:49:45 -0400 (EDT)
Received: from bdsl.66.12.12.130.gte.net (bdsl.66.12.12.130.gte.net [66.12.12.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28524
	for <sipping@ietf.org>; Thu, 18 Apr 2002 21:49:39 -0400 (EDT)
Received: from TXDWILLIS2 (bdsl.greycouncil.com [127.0.0.1])
	by bdsl.66.12.12.130.gte.net (8.11.6/8.11.6) with ESMTP id g3J1n2d14685;
	Thu, 18 Apr 2002 20:49:02 -0500
From: "Dean Willis" <dean.willis@softarmor.com>
To: <Mpierce1@aol.com>, <Brian.Rosen@marconi.com>, <rohan@cisco.com>,
        <sipping@ietf.org>
Subject: RE: [Sipping] Re: Cookies vs. State
Date: Thu, 18 Apr 2002 20:48:58 -0500
Message-ID: <005701c1e744$5f8e2cb0$bb036e3f@TXDWILLIS2>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0058_01C1E71A.76B824B0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <2b.25d26488.29f0b3de@aol.com>
Importance: Normal
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0058_01C1E71A.76B824B0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

 
Mike said:
-------------- 
Yes, I hope that you don't send all, but the draft didn't seem to say
that. It indicated that all cookies recieved for a call must be kept and
that every cookie stored for a call must be sent in every message. Since
there could not be any cookies for any previous call, all stored cookies
must be sent in every message. 

If the point is to store "state" in the UA by this method, then it's
obvious to me that the requirement is to store exactly one Cookie per
call. (One could argue whether a multipoint call like three way calling
is modeled as one call or two.) 
 -------------
 
1) One could envision a call passing through multiple service provider
proxies, with each service provider adding a cookie. 

2) If one serves excessively large cookies, one can expect to have one's
service shunned. Survival is not mandatory.
 
 
Mike said:
------------------ 
 High availability with everything stored in one place is certainly
easier than storing the data in end devices and working out all the
protocol and security issues to fetch it whenever feature processing
needs to know it. Design technique for highly reliable systems, often
based on redundant pairs with sharing of state information, has been
around for decades. 

And I continue to puzzle over why a call stateful, highly reliable proxy
to control some service is considered to be "undesirable". And it's not
sufficient to say "because that's not the way http did it".  
------------------ 

Works fine until someone shoves an airplane into your "one place". Of
course, one could geographically distribute matched pairs. Or quartets.
Then we're back to building wide-area state replication, which is hard.
 
But a system builder is free to use centralized redundancy. I do it all
the time. We sell lots of highly redundant state-shared proxyclusters,
primarily as firewall controllers. 
 
It's just not the perfect solution for all situations. What it doesn't
work well for in my experience is things like "Kansas just went off line
due to an MBOSI , so some of the users are being served out of Chicago
now, some from California, and some from Virginia, and some seem to have
rehomed off the orbital platform that just came into view". In the PSTN
world you're used to, since their circuits were cut, their calls
dropped, and they can restablish on a new circuit. In the Internet
model, it means their packets are briefly delayed while the router
network finds a new shortest path, and they're still talking, and
eventually, they're going to want to send a BYE or do somethine else
useful.
 
An MBOSI, if you're curious,  is a "Multiple Backhoe Operator Stupidity
Incident", and it happens with alarming frequency whenever backhoes and
fiber optics share space. It doesn't matter HOW much fiber redundancy
you put into a building, they'll find a way to cut all of it at the same
time. I once serviced a data center that we built straddling GTE and
SWBell property lines, with fully redundant provisioning from each
carrier, with entry points on opposite sides of the five million square
foot building. The first MBOSI occurred before we had the center fully
operational, less than a month after the fibers were lit. As I recall,
the operator realized he'd hit something, so he went around to the
opposite side of the buiilding looking for a safer place to dig. Voila.
Murphy was an optimist.

- -
Dean 



------=_NextPart_000_0058_01C1E71A.76B824B0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

<META content=3D"MSHTML 6.00.2715.400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT lang=3D0 color=3D#000000 size=3D3 FAMILY=3D"SANSSERIF"><FONT =
face=3DArial><SPAN=20
class=3D019022701-19042002><FONT color=3D#0000ff=20
size=3D2>&nbsp;</FONT></SPAN></FONT></FONT></DIV>
<DIV><FONT lang=3D0 color=3D#000000 size=3D3 FAMILY=3D"SANSSERIF"><FONT =
face=3DArial><SPAN=20
class=3D019022701-19042002><FONT color=3D#0000ff size=3D2>Mike=20
said:</FONT></SPAN></FONT></FONT></DIV>
<DIV><FONT lang=3D0 color=3D#000000 size=3D3 FAMILY=3D"SANSSERIF"><FONT =
face=3DArial><SPAN=20
class=3D019022701-19042002><FONT color=3D#0000ff=20
size=3D2>--------------</FONT>&nbsp;</SPAN><BR></FONT></FONT><FONT =
lang=3D0=20
face=3DArial color=3D#000000 size=3D2 FAMILY=3D"SANSSERIF">Yes, I hope =
that you don't=20
send all, but the draft didn't seem to say that. It indicated that all =
cookies=20
recieved for a call must be kept and that every cookie stored for a call =
must be=20
sent in every message. Since there could not be any cookies for any =
previous=20
call, all stored cookies must be sent in every message. <BR><BR>If the =
point is=20
to store "state" in the UA by this method, then it's obvious to me that =
the=20
requirement is to store exactly one Cookie per call. (One could argue =
whether a=20
multipoint call like three way calling is modeled as one call or=20
two.)&nbsp;<BR></FONT><FONT lang=3D0 color=3D#000000 size=3D3 =
FAMILY=3D"SANSSERIF"><SPAN=20
class=3D019022701-19042002><FONT face=3DArial color=3D#0000ff=20
size=3D2>&nbsp;-------------</FONT></SPAN></FONT></DIV>
<DIV><FONT lang=3D0 face=3DArial color=3D#0000ff size=3D2 =
FAMILY=3D"SANSSERIF"><SPAN=20
class=3D019022701-19042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT lang=3D0 color=3D#000000 size=3D3 FAMILY=3D"SANSSERIF"><SPAN=20
class=3D019022701-19042002><FONT face=3DArial color=3D#0000ff =
size=3D2>1) One could=20
envision&nbsp;a call passing through multiple service provider proxies, =
with=20
each service provider adding a cookie.</FONT>&nbsp;</SPAN><BR><SPAN=20
class=3D019022701-19042002><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN></FONT></DIV>
<DIV><FONT lang=3D0 color=3D#000000 size=3D3 FAMILY=3D"SANSSERIF"><SPAN=20
class=3D019022701-19042002><FONT face=3DArial color=3D#0000ff =
size=3D2>2) If one serves=20
excessively large cookies, one can expect to have one's service=20
shunned.</FONT>&nbsp;<FONT face=3DArial color=3D#0000ff =
size=3D2>Survival is not=20
mandatory.</FONT></SPAN></FONT></DIV>
<DIV><FONT lang=3D0 color=3D#000000 FAMILY=3D"SANSSERIF"><FONT =
face=3DArial><FONT=20
size=3D2><SPAN class=3D019022701-19042002><FONT=20
color=3D#0000ff></FONT></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT lang=3D0 color=3D#000000 FAMILY=3D"SANSSERIF"><FONT =
face=3DArial><FONT=20
color=3D#0000ff size=3D2><SPAN=20
class=3D019022701-19042002></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT lang=3D0 FAMILY=3D"SANSSERIF"><FONT face=3DArial><FONT =
color=3D#0000ff=20
size=3D2><SPAN class=3D019022701-19042002>Mike=20
said:</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT lang=3D0 color=3D#000000 FAMILY=3D"SANSSERIF"><FONT =
face=3DArial><FONT=20
size=3D2><SPAN class=3D019022701-19042002><FONT=20
color=3D#0000ff>------------------</FONT>&nbsp;</SPAN></FONT></FONT></FON=
T></DIV>
<DIV><FONT lang=3D0 color=3D#000000 FAMILY=3D"SANSSERIF"><FONT><FONT =
face=3DArial><FONT=20
size=3D2><SPAN class=3D019022701-19042002>&nbsp;</SPAN>High availability =
with=20
everything stored in one place is certainly easier than storing the data =
in end=20
devices and working out all the protocol and security issues to fetch it =

whenever feature processing needs to know it. Design technique for =
highly=20
reliable systems, often based on redundant pairs with sharing of state=20
information, has been around for decades. <BR><BR>And I continue to =
puzzle over=20
why a call stateful, highly reliable proxy to control some service is =
considered=20
to be "undesirable". And it's not sufficient to say "because that's not =
the way=20
http did it".&nbsp;<SPAN class=3D019022701-19042002><FONT=20
color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></FONT></FONT></FONT></DIV>
<DIV><FONT lang=3D0 color=3D#000000 =
FAMILY=3D"SANSSERIF"><FONT><FONT><FONT=20
face=3DArial><FONT size=3D2><SPAN class=3D019022701-19042002><FONT=20
color=3D#0000ff>------------------</FONT>&nbsp;</SPAN><BR><BR><SPAN=20
class=3D019022701-19042002><FONT color=3D#0000ff>Works fine until =
someone shoves an=20
airplane into your "one place". Of course, one could geographically =
distribute=20
matched pairs. Or quartets. Then we're back to building wide-area state=20
replication, which is=20
hard.</FONT></SPAN></FONT></FONT></FONT></FONT></FONT></DIV>
<DIV><FONT lang=3D0 color=3D#000000 =
FAMILY=3D"SANSSERIF"><FONT><FONT><FONT=20
face=3DArial><FONT size=3D2><SPAN class=3D019022701-19042002><FONT=20
color=3D#0000ff></FONT></SPAN></FONT></FONT></FONT></FONT></FONT>&nbsp;</=
DIV>
<DIV><FONT lang=3D0 color=3D#000000 =
FAMILY=3D"SANSSERIF"><FONT><FONT><FONT><SPAN=20
class=3D019022701-19042002><FONT face=3DArial color=3D#0000ff =
size=3D2>But a system=20
builder is free to use centralized redundancy. I do it all the time. We =
sell=20
lots of highly redundant state-shared proxyclusters, primarily as =
firewall=20
controllers. </FONT></SPAN></FONT></FONT></FONT></FONT></DIV>
<DIV><FONT lang=3D0 color=3D#000000 =
FAMILY=3D"SANSSERIF"><FONT><FONT><FONT><SPAN=20
class=3D019022701-19042002><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN></FONT></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT lang=3D0 color=3D#000000 =
FAMILY=3D"SANSSERIF"><FONT><FONT><FONT><SPAN=20
class=3D019022701-19042002><FONT face=3DArial color=3D#0000ff =
size=3D2>It's just not the=20
perfect solution for all situations. What it doesn't work well for in my =

experience is things like "Kansas just went off line due to an MBOSI ,=20
so&nbsp;some of&nbsp;the users are being served out of Chicago now, some =
from=20
California, and some from Virginia, and some&nbsp;seem to have rehomed =
off the=20
orbital platform that just came into view". In the PSTN world you're =
used to,=20
since their circuits were cut, their calls dropped, and they can =
restablish on a=20
new circuit. In the Internet model, it means their packets are briefly =
delayed=20
while the router network finds a new shortest path, and they're still =
talking,=20
and eventually, they're going to want to send a BYE or do somethine else =

useful.</FONT></SPAN></DIV><FONT color=3D#0000ff></FONT>
<DIV><SPAN class=3D019022701-19042002><FONT face=3DArial color=3D#0000ff =

size=3D2>&nbsp;</FONT></SPAN></DIV>
<DIV><SPAN class=3D019022701-19042002><FONT face=3DArial color=3D#0000ff =
size=3D2>An=20
MBOSI, if you're curious, &nbsp;is a "Multiple Backhoe Operator =
Stupidity=20
Incident", and it happens with alarming frequency whenever backhoes and =
fiber=20
optics share space. I</FONT><FONT face=3DArial color=3D#0000ff =
size=3D2>t doesn't=20
matter HOW much fiber redundancy you put into a building, they'll find a =
way to=20
cut all of it at the same time. I once&nbsp;serviced a data center that =
we built=20
straddling GTE and SWBell property lines, with fully redundant =
provisioning from=20
each carrier, with entry points on opposite sides of the five million =
square=20
foot building. The first MBOSI occurred before we had the center fully=20
operational, less than a month after the fibers were lit. As I recall, =
the=20
operator realized he'd hit something, so he went around to the opposite =
side of=20
the buiilding looking for a safer place to dig. Voila. Murphy was an=20
optimist.</FONT></SPAN></DIV>
<DIV><SPAN class=3D019022701-19042002><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT><FONT=20
face=3DArial color=3D#0000ff size=3D2></FONT><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT><FONT face=3DArial color=3D#0000ff size=3D2></FONT><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT><FONT=20
face=3DArial color=3D#0000ff size=3D2></FONT><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT><FONT face=3DArial color=3D#0000ff size=3D2></FONT><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT><BR><SPAN class=3D019022701-19042002></SPAN><FONT =
face=3DArial=20
size=3D2>-<SPAN class=3D019022701-19042002><FONT=20
color=3D#0000ff>&nbsp;-</FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D019022701-19042002><FONT=20
color=3D#0000ff>Dean</FONT>&nbsp;</SPAN><BR></FONT></FONT></FONT></FONT><=
/FONT><FONT=20
lang=3D0 size=3D3 FAMILY=3D"SANSSERIF"><BR></DIV></FONT><FONT lang=3D0 =
size=3D2=20
FAMILY=3D"SANSSERIF"></FONT></BODY></HTML>

------=_NextPart_000_0058_01C1E71A.76B824B0--


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



From daemon@ns.ietf.org  Fri Apr 19 01:15:25 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02424
	for <sipping-archive@odin.ietf.org>; Fri, 19 Apr 2002 01:15:25 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA07146
	for sipping-archive@odin.ietf.org; Fri, 19 Apr 2002 01:15:25 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA28851;
	Fri, 19 Apr 2002 00:57:24 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA28733
	for <sipping@ns.ietf.org>; Fri, 19 Apr 2002 00:57:01 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.47])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02239
	for <sipping@ietf.org>; Fri, 19 Apr 2002 00:56:59 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g3J4uws7026829;
	Fri, 19 Apr 2002 06:56:59 +0200 (MEST)
Received: from lmf.ericsson.se (3OQK900K04BAB3K.lmf.ericsson.se [131.160.30.12])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g3J4uwo5003760;
	Fri, 19 Apr 2002 07:56:58 +0300 (EET DST)
Message-ID: <3CBFA3A0.DF9A0DC9@lmf.ericsson.se>
Date: Fri, 19 Apr 2002 07:57:04 +0300
From: Christer Holmberg <christer.holmberg@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Yu, James" <james.yu@neustar.biz>
CC: sipping@ietf.org
Subject: Re: [Sipping] draft-yu-tel-url-04.txt comment
References: <A83B38C38B3ED6119D3600306E0722D038BF59@dc02.npac.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit


Hi,

> >So, what you say is: if user=phone, an implementation must
> >always be able to
> >handle parameters in the SIP-URL???
> >
> >If this is the case, I think it must be specified in bis,
> >since user=phone is
> >also specified there.
> >
> >OR, we can say that an implementation not supporting the
> >parameters will simply
> >treat the whole user part as a single string, but again -
> >that would probably be
> >rejected by PSTN routing handlers etc.
>
> The user part can be treated as a single string first.  There is no need to
> understand or process the user part if the received sip URL in the
> Request-URI contains a host that is not the node itself.  Based on the
> routing precedence, this node is supposed to route based on the host
> information.  Only when this node is that host, it needs to process the user
> part.

That is true, but the intermediate node may still change the Request-URI. In
that case it could remote the old user part - INCLUDING your parameters - and
add a new user part without them. I guess you don't want that to happend, do
you?

> In that situation, when "user=phone" is present, it knows that a
> telephone number is in the user part and other tel URL parameters may be
> present.

Again, that's NOT how it's said in bis. Since "user=phone" is defined in bis, if
it requires some special treatment of the URL user part I think it also must be
defined in bis.

> If this node does not understand some of the parameters in the user part, it
> can ignore them.

Yes, yes, yes. But, again, my bis compliant implementation doesn't even know
there are any parameters to ignore in the first place, since bis doesn't specify
any parameter for the user part - no matter if "user=phone". It will assume the
WHOLE user part represents the user, eg a phone number, or whatever.

Others have asked, and I also still would like to know, why you can't define the
parameters as uri-parameters instead??? Maybe there is a good reason, and maybe
there is something I've missed, so please tell me.

Regards,

Christer Holmberg
Ericsson Finland



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



From daemon@ns.ietf.org  Fri Apr 19 03:29:52 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12458
	for <sipping-archive@odin.ietf.org>; Fri, 19 Apr 2002 03:29:52 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA19039
	for sipping-archive@odin.ietf.org; Fri, 19 Apr 2002 03:29:53 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA18596;
	Fri, 19 Apr 2002 03:19:18 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA18528
	for <sipping@ns.ietf.org>; Fri, 19 Apr 2002 03:19:04 -0400 (EDT)
Received: from ns.unisa.it (ns.unisa.it [193.205.160.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12353
	for <sipping@ietf.org>; Fri, 19 Apr 2002 03:19:02 -0400 (EDT)
From: loretosa@vizzavi.it
Received: from eeu1itc02904 (alina.diiie.unisa.it [193.205.164.67])
	by ns.unisa.it (8.12.0/8.12.0) with SMTP id g3J7IH1c001492;
	Fri, 19 Apr 2002 09:18:33 +0200 (MET DST)
Message-ID: <003901c1e772$983961f0$43a4cdc1@eeu1itc02904>
To: <sipping@ietf.org>
Cc: <schulzrinne@cs.columbia.edu>, <nobuyasu@tari.research.telcordia.com>,
        <sbaba@tari.thosiba.com>, <miriam@research.telcordia.com>,
        <adutta@research.telcordia.com>, <farm@research.telcordia.com>
Date: Fri, 19 Apr 2002 09:19:48 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0035_01C1E783.5A7CB9A0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Subject: [Sipping] mobility in SIP
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0035_01C1E783.5A7CB9A0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

HI....


someon tells me whe the draft about the ITSUMO group haven't been =
renewed?

what is the status of the issues about the mobility in sip???
and the sip mobility in 3GPP...

tanks in advance
Sal

------=_NextPart_000_0035_01C1E783.5A7CB9A0
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=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>HI....</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>someon tells me whe the draft about the =
ITSUMO=20
group haven't been renewed?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>what is the status of the issues about =
the=20
mobility&nbsp;in sip???</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and the sip mobility in =
3GPP...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>tanks in advance</FONT></DIV>
<DIV><FONT face=3DArial =
size=3D2>Sal</FONT></DIV></FONT></DIV></BODY></HTML>

------=_NextPart_000_0035_01C1E783.5A7CB9A0--



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



From daemon@ns.ietf.org  Fri Apr 19 03:29:54 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12474
	for <sipping-archive@odin.ietf.org>; Fri, 19 Apr 2002 03:29:54 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA19053
	for sipping-archive@odin.ietf.org; Fri, 19 Apr 2002 03:29:55 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA18581;
	Fri, 19 Apr 2002 03:19:16 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA18531
	for <sipping@ns.ietf.org>; Fri, 19 Apr 2002 03:19:08 -0400 (EDT)
Received: from ns.unisa.it (ns.unisa.it [193.205.160.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12352
	for <sipping@ietf.org>; Fri, 19 Apr 2002 03:19:02 -0400 (EDT)
From: loretosa@vizzavi.it
Received: from eeu1itc02904 (alina.diiie.unisa.it [193.205.164.67])
	by ns.unisa.it (8.12.0/8.12.0) with SMTP id g3J7IH1a001492;
	Fri, 19 Apr 2002 09:18:33 +0200 (MET DST)
Message-ID: <003801c1e772$97883a60$43a4cdc1@eeu1itc02904>
To: <sipping@ietf.org>
Cc: <schulzrinne@cs.columbia.edu>, <nobuyasu@tari.research.telcordia.com>,
        <sbaba@tari.thosiba.com>, <miriam@research.telcordia.com>,
        <adutta@research.telcordia.com>, <farm@research.telcordia.com>
Date: Fri, 19 Apr 2002 09:17:35 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0025_01C1E783.0AD30C60"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Subject: [Sipping] mobility in SIP
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0025_01C1E783.0AD30C60
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

HI....


someon tells me whe the draft about the ITSUMO group haven't been =
renewed?

what is the status of the issues about the mobility in sip???
and the sip mobility in 3GPP...

tanks in advance
Sal



------=_NextPart_000_0025_01C1E783.0AD30C60
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=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>HI....</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>someon tells me whe the draft about the =
ITSUMO=20
group haven't been renewed?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>what is the status of the issues about =
the=20
mobility&nbsp;in sip???</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and the sip mobility in =
3GPP...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>tanks in advance</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Sal</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0025_01C1E783.0AD30C60--



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



From daemon@ns.ietf.org  Fri Apr 19 04:43:37 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13590
	for <sipping-archive@odin.ietf.org>; Fri, 19 Apr 2002 04:43:37 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA23588
	for sipping-archive@odin.ietf.org; Fri, 19 Apr 2002 04:43:39 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA22366;
	Fri, 19 Apr 2002 04:28:55 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA22331
	for <sipping@ns.ietf.org>; Fri, 19 Apr 2002 04:28:52 -0400 (EDT)
Received: from ns.unisa.it (ns.unisa.it [193.205.160.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13394;
	Fri, 19 Apr 2002 04:28:49 -0400 (EDT)
From: loretosa@vizzavi.it
Received: from eeu1itc02904 (alina.diiie.unisa.it [193.205.164.67])
	by ns.unisa.it (8.12.0/8.12.0) with SMTP id g3J8DH1Y003379;
	Fri, 19 Apr 2002 10:13:25 +0200 (MET DST)
Message-ID: <00c801c1e77a$468ac350$43a4cdc1@eeu1itc02904>
To: <sipping@ietf.org>, <sip@ietf.org>
Date: Fri, 19 Apr 2002 10:14:48 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00C5_01C1E78B.09591CF0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Subject: [Sipping] status
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_00C5_01C1E78B.09591CF0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

hi all,

where it's possible find the status of not renewed  and the cause...
of the inclusion in other draft as draft-sip-rfc2543


thanks

sal

------=_NextPart_000_00C5_01C1E78B.09591CF0
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=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>hi all,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>where it's possible find the status of =
not=20
renewed&nbsp;&nbsp;and the cause...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>of&nbsp;the inclusion in other draft as =

draft-sip-rfc2543</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>thanks</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>sal</FONT></DIV></BODY></HTML>

------=_NextPart_000_00C5_01C1E78B.09591CF0--



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



From daemon@ns.ietf.org  Fri Apr 19 05:58:36 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14739
	for <sipping-archive@odin.ietf.org>; Fri, 19 Apr 2002 05:58:35 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA27725
	for sipping-archive@odin.ietf.org; Fri, 19 Apr 2002 05:58:38 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA27098;
	Fri, 19 Apr 2002 05:46:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA27069
	for <sipping@ns.ietf.org>; Fri, 19 Apr 2002 05:46:28 -0400 (EDT)
Received: from zctfs063.europe.nortel.com (zctfs063.nortelnetworks.com [47.164.128.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14552
	for <sipping@ietf.org>; Fri, 19 Apr 2002 05:46:25 -0400 (EDT)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zctfs063.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3J9juU15127;
	Fri, 19 Apr 2002 11:45:56 +0200 (MEST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3J9jGv09270;
	Fri, 19 Apr 2002 10:45:16 +0100 (BST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JDW4P22Z>; Fri, 19 Apr 2002 10:45:58 +0100
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7180@zwcwd00r.europe.nortel.com>
From: "Mark Watson"<mwatson@nortelnetworks.com>
To: "'Rosen, Brian'" <Brian.Rosen@marconi.com>,
        "'sipping@ietf.org'"
	 <sipping@ietf.org>
Subject: RE: [Sipping] RE: Network Asserted Identity
Date: Fri, 19 Apr 2002 10:45:46 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E786.F95D0482"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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

If there is a network asserted identity, and there is no privacy
requirement, I don't understand the grounds for hiding this information from
the UA.

Many services based on the identity of the caller will operate much more
sucessfully based on the network asserted identity that just based on the
caller's claimed identity.

I thought Jon's identity draft explained very well why an identity signed by
a recognised 'authentication service' might be useful to the UA - this is
the general solution. In the short term, if your Service Provider has
obtained a trusted network asserted identity - by virtue of the trust
relationships with the other Service Providers - then all the same reasoning
applies.

...Mark 

> -----Original Message-----
> From: Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> Sent: 18 April 2002 18:36
> To: Watson, Mark [MDN05:EP10:EXCH]; 'sipping@ietf.org'
> Subject: RE: [Sipping] RE: Network Asserted Identity
> 
> 
> > NAI2) The ability for a network entity to pass a 
> > (non-private) network asserted identity directly to a UA  
> I'd like to explore this one.  In my zeal to cut down the 
> discussion to 
> manageable hunks, I don't get why we need this now.  I think NAI is 
> strictly for SP elements to assert an identity to one another, 
> and there is no requirement for any UA to see it.  If we can always 
> define NAI as inserted by the network, and stripped prior to 
> sending to 
> a UA, then I think many things may get simpler.
> 
> It may also make other people happier with this work - UAs send 
> things they want the other UA to see.  Proxy Servers send things 
> they want other Proxy Servers to see.  I'm still assuming a B2BUA 
> is needed for really anonymous calls, and to deal with Subscriber 
> vs User issues. 
> 
> Brian
> 

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Sipping] RE: Network Asserted Identity</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>If there is a network asserted identity, and there is =
no privacy requirement, I don't understand the grounds for hiding this =
information from the UA.</FONT></P>

<P><FONT SIZE=3D2>Many services based on the identity of the caller =
will operate much more sucessfully based on the network asserted =
identity that just based on the caller's claimed identity.</FONT></P>

<P><FONT SIZE=3D2>I thought Jon's identity draft explained very well =
why an identity signed by a recognised 'authentication service' might =
be useful to the UA - this is the general solution. In the short term, =
if your Service Provider has obtained a trusted network asserted =
identity - by virtue of the trust relationships with the other Service =
Providers - then all the same reasoning applies.</FONT></P>

<P><FONT SIZE=3D2>...Mark </FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Rosen, Brian [<A =
HREF=3D"mailto:Brian.Rosen@marconi.com">mailto:Brian.Rosen@marconi.com</=
A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: 18 April 2002 18:36</FONT>
<BR><FONT SIZE=3D2>&gt; To: Watson, Mark [MDN05:EP10:EXCH]; =
'sipping@ietf.org'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [Sipping] RE: Network Asserted =
Identity</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; NAI2) The ability for a network entity to =
pass a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; (non-private) network asserted identity =
directly to a UA&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; I'd like to explore this one.&nbsp; In my zeal =
to cut down the </FONT>
<BR><FONT SIZE=3D2>&gt; discussion to </FONT>
<BR><FONT SIZE=3D2>&gt; manageable hunks, I don't get why we need this =
now.&nbsp; I think NAI is </FONT>
<BR><FONT SIZE=3D2>&gt; strictly for SP elements to assert an identity =
to one another, </FONT>
<BR><FONT SIZE=3D2>&gt; and there is no requirement for any UA to see =
it.&nbsp; If we can always </FONT>
<BR><FONT SIZE=3D2>&gt; define NAI as inserted by the network, and =
stripped prior to </FONT>
<BR><FONT SIZE=3D2>&gt; sending to </FONT>
<BR><FONT SIZE=3D2>&gt; a UA, then I think many things may get =
simpler.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; It may also make other people happier with this =
work - UAs send </FONT>
<BR><FONT SIZE=3D2>&gt; things they want the other UA to see.&nbsp; =
Proxy Servers send things </FONT>
<BR><FONT SIZE=3D2>&gt; they want other Proxy Servers to see.&nbsp; I'm =
still assuming a B2BUA </FONT>
<BR><FONT SIZE=3D2>&gt; is needed for really anonymous calls, and to =
deal with Subscriber </FONT>
<BR><FONT SIZE=3D2>&gt; vs User issues. </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Brian</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E786.F95D0482--

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



From daemon@ns.ietf.org  Fri Apr 19 07:36:44 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16438
	for <sipping-archive@odin.ietf.org>; Fri, 19 Apr 2002 07:36:44 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA03682
	for sipping-archive@odin.ietf.org; Fri, 19 Apr 2002 07:36:44 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA02608;
	Fri, 19 Apr 2002 07:22:43 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA02544
	for <sipping@ns.ietf.org>; Fri, 19 Apr 2002 07:22:36 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15918;
	Fri, 19 Apr 2002 07:22:34 -0400 (EDT)
Message-Id: <200204191122.HAA15918@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 19 Apr 2002 07:22:34 -0400
Subject: [Sipping] I-D ACTION:draft-watson-sipping-req-history-01.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

--NextPart

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


	Title		: Generic Request History Capability - Requirements
	Author(s)	: M. Watson, M. Barnes, C. Jennings, J. Peterson
	Filename	: draft-watson-sipping-req-history-01.txt
	Pages		: 10
	Date		: 18-Apr-02
	
Many services that SIP is anticipated to support require the 
ability to determine why and how the call arrived at a specific 
application.  Examples of such services include (but are not 
limited to) sessions initiated to call centers via 'click to talk' 
SIP URLs on a web page, 'call history/logging' style services 
within intelligent 'call management' software for SIP UAs and calls 
to voicemail servers and call centers.  While SIP implicitly 
provides the redirect/retarget capabilities that enable calls to be 
routed to chosen applications, there is currently no standard 
mechanism within SIP for communicating the history of such a 
request. This 'request history' information allows the receiving 
application to determine hints about how and why the call arrived 
at the application/user.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-watson-sipping-req-history-01.txt

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-watson-sipping-req-history-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-watson-sipping-req-history-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:	<20020418140916.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-watson-sipping-req-history-01.txt

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

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

--OtherAccess--

--NextPart--



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



From daemon@ns.ietf.org  Fri Apr 19 09:21:58 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19098
	for <sipping-archive@odin.ietf.org>; Fri, 19 Apr 2002 09:21:58 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA08487
	for sipping-archive@odin.ietf.org; Fri, 19 Apr 2002 09:21:59 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA07926;
	Fri, 19 Apr 2002 09:06:01 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA07894
	for <sipping@optimus.ietf.org>; Fri, 19 Apr 2002 09:05:56 -0400 (EDT)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18644
	for <sipping@ietf.org>; Fri, 19 Apr 2002 09:05:53 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA04999;
	Fri, 19 Apr 2002 09:05:17 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA20523;
	Fri, 19 Apr 2002 09:05:18 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <H8GSNCHS>; Fri, 19 Apr 2002 09:05:06 -0400
Message-ID: <313680C9A886D511A06000204840E1CF030B51C5@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Mpierce1@aol.com'" <Mpierce1@aol.com>, sipping@ietf.org
Subject: RE: [Sipping] Re: Cookies vs. State
Date: Fri, 19 Apr 2002 09:05:10 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

>If the point is to store "state" in the UA by this method, then it's 
>obvious to me that the requirement is to store exactly one Cookie 
>per call. (One could argue whether a multipoint call like three way 
>calling is modeled as one call or two.) 
No, there could be multiple intermediaries in a call that need state
to be saved.  Each would add a cookie if it needed to.  Therefore
you could have multiple cookies per call.


>High availability with everything stored in one place is certainly 
>easier than storing the data in end devices and working out all 
>the protocol and security issues to fetch it whenever feature 
>processing needs to know it. Design technique for highly reliable 
>systems, often based on redundant pairs with sharing of state 
>information, has been around for decades. 
Yes, and the experience of building these systems is that it is
very hard to get them right.  It is possible, but hard.

>And I continue to puzzle over why a call stateful, highly reliable 
>proxy to control some service is considered to be "undesirable". 
>And it's not sufficient to say "because that's not the way http did it". 
Because many find that it's a whole lot easier to get stateless systems
reliable and scaleable then a stateful system.  If you want to build
systems that use replicated state by all means, do it.  To enable
people who want to build systems where state is kept in the UA, we
offer cookies. 

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



From daemon@ns.ietf.org  Fri Apr 19 09:43:15 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19679
	for <sipping-archive@odin.ietf.org>; Fri, 19 Apr 2002 09:43:15 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA10034
	for sipping-archive@odin.ietf.org; Fri, 19 Apr 2002 09:43:05 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA08602;
	Fri, 19 Apr 2002 09:23:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA08564
	for <sipping@ns.ietf.org>; Fri, 19 Apr 2002 09:23:06 -0400 (EDT)
Received: from harjus.eng.song.fi (harjus.eng.song.fi [195.10.149.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19134
	for <sipping@ietf.org>; Fri, 19 Apr 2002 09:23:03 -0400 (EDT)
Received: from jh by lohi.eng.song.fi with local (Exim 3.34 #1 (Debian))
	id 16yXpC-0006A4-00; Fri, 19 Apr 2002 15:49:14 +0300
From: Juha Heinanen <jh@lohi.eng.song.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15552.4682.63061.41179@lohi.eng.song.fi>
Date: Fri, 19 Apr 2002 15:49:14 +0300
To: "Mark Watson"<mwatson@nortelnetworks.com>
Cc: "'Rosen, Brian'" <Brian.Rosen@marconi.com>,
        "'sipping@ietf.org'"
	 <sipping@ietf.org>
Subject: RE: [Sipping] RE: Network Asserted Identity
In-Reply-To: <A3C2399B2FACD411A54200508BE39C74054F7180@zwcwd00r.europe.nortel.com>
References: <A3C2399B2FACD411A54200508BE39C74054F7180@zwcwd00r.europe.nortel.com>
X-Mailer: VM 6.97 under Emacs 20.7.2
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Mark Watson writes:

 > Many services based on the identity of the caller will operate much more
 > sucessfully based on the network asserted identity that just based on the
 > caller's claimed identity.

i'm a bit confused by what "identity" means here: the identify of the
user, e.g., jh@song.fi, or the from uri, e.g., tel:+35844123456, the
user wants to use in the call.

-- juha


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



From daemon@ns.ietf.org  Fri Apr 19 09:45:45 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19749
	for <sipping-archive@odin.ietf.org>; Fri, 19 Apr 2002 09:45:45 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA10188
	for sipping-archive@odin.ietf.org; Fri, 19 Apr 2002 09:45:47 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA09290;
	Fri, 19 Apr 2002 09:31:49 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA04505
	for <sipping@optimus.ietf.org>; Fri, 19 Apr 2002 07:58:27 -0400 (EDT)
Received: from breeze.research.telcordia.com (breeze-fddi.research.telcordia.com [192.4.5.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16864
	for <sipping@ietf.org>; Fri, 19 Apr 2002 07:58:25 -0400 (EDT)
Received: from research.telcordia.com (localhost [127.0.0.1])
	by breeze.research.telcordia.com (8.12.1/8.12.1) with ESMTP id g3JBvNRQ014842;
	Fri, 19 Apr 2002 07:57:23 -0400 (EDT)
Message-Id: <200204191157.g3JBvNRQ014842@breeze.research.telcordia.com>
To: loretosa@vizzavi.it
cc: sipping@ietf.org, schulzrinne@cs.columbia.edu,
        nobuyasu@tari.research.telcordia.com, sbaba@tari.thosiba.com,
        miriam@research.telcordia.com, farm@research.telcordia.com,
        adutta@research.telcordia.com
In-reply-to: Your message of "Fri, 19 Apr 2002 09:19:48 +0200."
             <003901c1e772$983961f0$43a4cdc1@eeu1itc02904> 
Date: Fri, 19 Apr 2002 07:57:23 -0400
From: Ashutosh Dutta <adutta@research.telcordia.com>
Subject: [Sipping] Re: mobility in SIP
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


Hi Loretosa,
	     Thank you for your interest in ITSUMO drafts.

We  are  still continuing  our  work  on  SIP based  mobility,  mostly
mid-session  terminal mobility  and inter-domain  mobility  using AAA,
PANA etc  besides the standard  forms of mobility  (personal, service)
supported  by SIP.  You  can find  any  drafts and  related papers  in
www.research.telcordia.com/sip-mobile. I have to update it a bit also.
At some  point these  drafts will be  updated depending upon  any new
results and issues.


You can find 3GPP related issues at
http://www.3gpp.org/TB/Other/IETF.htm.

Thanks
Ashutosh

> HI....
> 
> 
> someon tells me whe the draft about the ITSUMO group haven't been =
> renewed?
> 
> what is the status of the issues about the mobility in sip???
> and the sip mobility in 3GPP...
> 
> tanks in advance
> Sal
> 


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



From daemon@ns.ietf.org  Fri Apr 19 11:45:53 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24363
	for <sipping-archive@odin.ietf.org>; Fri, 19 Apr 2002 11:45:52 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA20183
	for sipping-archive@odin.ietf.org; Fri, 19 Apr 2002 11:45:55 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA18650;
	Fri, 19 Apr 2002 11:25:02 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA18597
	for <sipping@ns.ietf.org>; Fri, 19 Apr 2002 11:24:58 -0400 (EDT)
Received: from auemail1.firewall.lucent.com (auemail1.lucent.com [192.11.223.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23533;
	Fri, 19 Apr 2002 11:24:54 -0400 (EDT)
Received: from ih2mail.ih.lucent.com (h135-1-241-39.lucent.com [135.1.241.39])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3JFOPL02911;
	Fri, 19 Apr 2002 11:24:26 -0400 (EDT)
Received: from lucent.com by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id KAA07438; Fri, 19 Apr 2002 10:24:24 -0500 (CDT)
Message-ID: <3CC03681.2060701@lucent.com>
Date: Fri, 19 Apr 2002 10:23:45 -0500
From: "Vijay K. Gurbani" <vkg@lucent.com>
Organization: Lucent Technologies, Inc./Bell Laboratories
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1
X-Accept-Language: en-us
MIME-Version: 1.0
To: SIP LIST <sip@ietf.org>, SIPPING LIST <sipping@ietf.org>,
        SPIRITS list <spirits@lists.bell-labs.com>, pint@lists.bell-labs.com
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] SIP support for IN services
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Folks:

Enclosed is an I-D for review that describes SIP support for IN
services.  The I-D represents agreement of the IETF SIN (SIP/IN) design
team and is intended for publication as an informational RFC.  It has
been through Last Call in the IETF SIN DT and the comments of the WGs
identified in the To list of this email are now being solicited.

http://search.ietf.org/internet-drafts/draft-gurbani-sin-00.txt

Thanks,

- vijay
-- 
Vijay K. Gurbani  vkg@{lucent.com,research.bell-labs.com,acm.org}
Wireless Networks Group/Internet Software and eServices
Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440
Naperville, Illinois 60566     Voice: +1 630 224 0216


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



From daemon@ns.ietf.org  Fri Apr 19 11:59:35 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25111
	for <sipping-archive@odin.ietf.org>; Fri, 19 Apr 2002 11:59:34 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA21133
	for sipping-archive@odin.ietf.org; Fri, 19 Apr 2002 11:59:37 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA20313;
	Fri, 19 Apr 2002 11:46:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA20283
	for <sipping@ns.ietf.org>; Fri, 19 Apr 2002 11:46:54 -0400 (EDT)
Received: from zctfs063.europe.nortel.com (zctfs063.nortelnetworks.com [47.164.128.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24446
	for <sipping@ietf.org>; Fri, 19 Apr 2002 11:46:50 -0400 (EDT)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by zctfs063.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3JFjFm10947;
	Fri, 19 Apr 2002 17:45:15 +0200 (MEST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JDW4P9FQ>; Fri, 19 Apr 2002 16:45:15 +0100
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7190@zwcwd00r.europe.nortel.com>
From: "Mark Watson"<mwatson@nortelnetworks.com>
To: "'Juha Heinanen'" <jh@lohi.eng.song.fi>
Cc: "'Rosen, Brian'" <Brian.Rosen@marconi.com>,
        "'sipping@ietf.org'"
	 <sipping@ietf.org>
Subject: RE: [Sipping] RE: Network Asserted Identity
Date: Fri, 19 Apr 2002 16:45:11 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E7B9.206D6BD4"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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_01C1E7B9.206D6BD4
Content-Type: text/plain

Either - I'm just saying terminating services will work more reliably if the
information they work on is more reliable.

...Mark

> -----Original Message-----
> From: Juha Heinanen [mailto:jh@lohi.eng.song.fi]
> Sent: 19 April 2002 13:49
> To: Watson, Mark [MDN05:EP10:EXCH]
> Cc: 'Rosen, Brian'; 'sipping@ietf.org'
> Subject: RE: [Sipping] RE: Network Asserted Identity
> 
> 
> Mark Watson writes:
> 
>  > Many services based on the identity of the caller will 
> operate much more
>  > sucessfully based on the network asserted identity that 
> just based on the
>  > caller's claimed identity.
> 
> i'm a bit confused by what "identity" means here: the identify of the
> user, e.g., jh@song.fi, or the from uri, e.g., tel:+35844123456, the
> user wants to use in the call.
> 
> -- juha
> 
> 

------_=_NextPart_001_01C1E7B9.206D6BD4
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.2655.35">
<TITLE>RE: [Sipping] RE: Network Asserted Identity</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Either - I'm just saying terminating services will =
work more reliably if the information they work on is more =
reliable.</FONT>
</P>

<P><FONT SIZE=3D2>...Mark</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Juha Heinanen [<A =
HREF=3D"mailto:jh@lohi.eng.song.fi">mailto:jh@lohi.eng.song.fi</A>]</FON=
T>
<BR><FONT SIZE=3D2>&gt; Sent: 19 April 2002 13:49</FONT>
<BR><FONT SIZE=3D2>&gt; To: Watson, Mark [MDN05:EP10:EXCH]</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: 'Rosen, Brian'; 'sipping@ietf.org'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [Sipping] RE: Network Asserted =
Identity</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Mark Watson writes:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; Many services based on the identity =
of the caller will </FONT>
<BR><FONT SIZE=3D2>&gt; operate much more</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; sucessfully based on the network =
asserted identity that </FONT>
<BR><FONT SIZE=3D2>&gt; just based on the</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; &gt; caller's claimed identity.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; i'm a bit confused by what &quot;identity&quot; =
means here: the identify of the</FONT>
<BR><FONT SIZE=3D2>&gt; user, e.g., jh@song.fi, or the from uri, e.g., =
tel:+35844123456, the</FONT>
<BR><FONT SIZE=3D2>&gt; user wants to use in the call.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -- juha</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E7B9.206D6BD4--

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



From daemon@ns.ietf.org  Fri Apr 19 11:59:41 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25135
	for <sipping-archive@odin.ietf.org>; Fri, 19 Apr 2002 11:59:41 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA21147
	for sipping-archive@odin.ietf.org; Fri, 19 Apr 2002 11:59:44 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA20500;
	Fri, 19 Apr 2002 11:47:59 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA20388
	for <sipping@ns.ietf.org>; Fri, 19 Apr 2002 11:47:52 -0400 (EDT)
Received: from imo-r09.mx.aol.com (imo-r09.mx.aol.com [152.163.225.105])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24489
	for <sipping@ietf.org>; Fri, 19 Apr 2002 11:47:49 -0400 (EDT)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r09.mx.aol.com (mail_out_v32.5.) id c.ca.a37334b (3703);
	Fri, 19 Apr 2002 11:46:57 -0400 (EDT)
Message-ID: <ca.a37334b.29f195f1@aol.com>
Date: Fri, 19 Apr 2002 11:46:57 EDT
To: rohan@cisco.com
CC: sipping@ietf.org, brian.rosen@marconi.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_ca.a37334b.29f195f1_boundary"
X-Mailer: AOL 6.0 for Windows US sub 10524
Subject: [Sipping] Re: Cookies vs. State
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


--part1_ca.a37334b.29f195f1_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 4/18/02 4:06:56 PM Eastern Daylight Time, rohan@cisco.com 
writes:


> > [Mike] Yes, I've been involved in the design and implementation of 3 
> telephony
> > switching systems, where the presumed requirement was for high
> > reliability/almost no down time. They operated on the principle of
> > active/standby processors and critical peripherals and performed "state"
> > sharing between the two sides in order to support switch-over when the 
> active
> > side failed. I guess coming from this design background, I continue to 
> wonder
> > why so much effort is being put into complex protocols and procedures 
> between
> > devices which have a high failure rate and down time rather than tackling 
> the
> > real problem. Telephone and data switching equipment in the past was 
> designed
> > for low failure and down time and I continue to wonder why I keep getting
> > e-mails from our system administrator that "The LAN or e-mail server will 
> be
> > down for several hours for maintenance".
> 
> Based on your description, you did not implement such a system in software
> (as I queried), but in hardware instead.  It is fundamental to the
> Internet model to use lots of cheap distributed components.  Despite the
> phone systems better reliability during oridinary usage, the Internet
> continues to adapt better to unforseen massive failures.  Your Mileage May
> Vary.
> 

Sorry, I wasn't clear. What I was referring to was completely software. Of 
course it ran on a piece of hardware, which was specially designed for the 
telephony system, since there never was an off-the-shelf computer system that 
could provide the reliablity and functionality required by every telephony 
service provider around the world.

I believe if you query those service providers who you hope will replace 
their existing large telephone switches with internet (SIP) based equipment, 
they will universally tell you that reliability is the primary requirement. 
"Cheap" is nice but is secondary. As for "distributed components", as one of 
the ADs insisted, don't tell me that your favorite solution is the 
requirement. And I firmly believe that past experience in telephone switching 
has shown that distributed systems by themselves are not always the answer.

Mike


--part1_ca.a37334b.29f195f1_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 4/18/02 4:06:56 PM Eastern Daylight Time, rohan@cisco.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">&gt; [Mike] Yes, I've been involved in the design and implementation of 3 telephony
<BR>&gt; switching systems, where the presumed requirement was for high
<BR>&gt; reliability/almost no down time. They operated on the principle of
<BR>&gt; active/standby processors and critical peripherals and performed "state"
<BR>&gt; sharing between the two sides in order to support switch-over when the active
<BR>&gt; side failed. I guess coming from this design background, I continue to wonder
<BR>&gt; why so much effort is being put into complex protocols and procedures between
<BR>&gt; devices which have a high failure rate and down time rather than tackling the
<BR>&gt; real problem. Telephone and data switching equipment in the past was designed
<BR>&gt; for low failure and down time and I continue to wonder why I keep getting
<BR>&gt; e-mails from our system administrator that "The LAN or e-mail server will be
<BR>&gt; down for several hours for maintenance".
<BR>
<BR>Based on your description, you did not implement such a system in software
<BR>(as I queried), but in hardware instead. &nbsp;It is fundamental to the
<BR>Internet model to use lots of cheap distributed components. &nbsp;Despite the
<BR>phone systems better reliability during oridinary usage, the Internet
<BR>continues to adapt better to unforseen massive failures. &nbsp;Your Mileage May
<BR>Vary.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>Sorry, I wasn't clear. What I was referring to was completely software. Of course it ran on a piece of hardware, which was specially designed for the telephony system, since there never was an off-the-shelf computer system that could provide the reliablity and functionality required by every telephony service provider around the world.
<BR>
<BR>I believe if you query those service providers who you hope will replace their existing large telephone switches with internet (SIP) based equipment, they will universally tell you that reliability is the primary requirement. "Cheap" is nice but is secondary. As for "distributed components", as one of the ADs insisted, don't tell me that your favorite solution is the requirement. And I firmly believe that past experience in telephone switching has shown that distributed systems by themselves are not always the answer.
<BR>
<BR>Mike
<BR></FONT></HTML>

--part1_ca.a37334b.29f195f1_boundary--

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



From daemon@ns.ietf.org  Fri Apr 19 12:06:20 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25501
	for <sipping-archive@odin.ietf.org>; Fri, 19 Apr 2002 12:06:20 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA22818
	for sipping-archive@odin.ietf.org; Fri, 19 Apr 2002 12:06:19 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA20378;
	Fri, 19 Apr 2002 11:47:43 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA20347
	for <sipping@ns.ietf.org>; Fri, 19 Apr 2002 11:47:39 -0400 (EDT)
Received: from imo-r10.mx.aol.com (imo-r10.mx.aol.com [152.163.225.106])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24481
	for <sipping@ietf.org>; Fri, 19 Apr 2002 11:47:36 -0400 (EDT)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r10.mx.aol.com (mail_out_v32.5.) id l.33.25d435b6 (3703);
	Fri, 19 Apr 2002 11:47:00 -0400 (EDT)
Message-ID: <33.25d435b6.29f195f4@aol.com>
Date: Fri, 19 Apr 2002 11:47:00 EDT
Subject: Re: [Sipping] Re: Cookies vs. State
To: sipping@ietf.org
CC: dean.willis@softarmor.com, Brian.Rosen@marconi.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_33.25d435b6.29f195f4_boundary"
X-Mailer: AOL 6.0 for Windows US sub 10524
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


--part1_33.25d435b6.29f195f4_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 4/18/02 7:44:05 PM Eastern Daylight Time, Mpierce1@aol.com 
writes:


> High availability with everything stored in one place is certainly easier 
> than storing the data in end devices and working out all the protocol and 
> security issues to fetch it whenever feature processing needs to know it. 
> Design technique for highly reliable systems, often based on redundant 
> pairs with sharing of state information, has been around for decades. 
> 
> And I continue to puzzle over why a call stateful, highly reliable proxy to 
> control some service is considered to be "undesirable". And it's not 
> sufficient to say "because that's not the way http did it". 
> 

In a message dated 4/19/02 9:06:16 AM Eastern Daylight Time, 
Brian.Rosen@marconi.com writes:


> Because many find that it's a whole lot easier to get stateless systems
> reliable and scaleable then a stateful system.  If you want to build
> systems that use replicated state by all means, do it.  To enable
> people who want to build systems where state is kept in the UA, we
> offer cookies. 
> 

In a message dated 4/18/02 9:49:29 PM Eastern Daylight Time, 
dean.willis@softarmor.com writes:


> But a system builder is free to use centralized redundancy. I do it all the 
> time. We sell lots of highly redundant state-shared proxyclusters, 
> primarily as firewall controllers. 
> 

Exactly. What I've been trying to say it that there are multiple ways to 
achieve reliability, and one of them is with redundant, highly reliable 
systems that do not need to resort to stored their important data in someone 
elses device for backup. So admit that this may be the better solution in 
some cases or for some implementors and stop referring to this method as 
"undesirable".

Mike

--part1_33.25d435b6.29f195f4_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 4/18/02 7:44:05 PM Eastern Daylight Time, Mpierce1@aol.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">High availability with everything stored in one place is certainly easier than storing the data in end devices and working out all the protocol and security issues to fetch it whenever feature processing needs to know it. Design technique for highly reliable systems, often based on redundant pairs with sharing of state information, has been around for decades. 
<BR>
<BR>And I continue to puzzle over why a call stateful, highly reliable proxy to control some service is considered to be "undesirable". And it's not sufficient to say "because that's not the way http did it". 
<BR></BLOCKQUOTE>
<BR>
<BR>In a message dated 4/19/02 9:06:16 AM Eastern Daylight Time, Brian.Rosen@marconi.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Because many find that it's a whole lot easier to get stateless systems
<BR>reliable and scaleable then a stateful system. &nbsp;If you want to build
<BR>systems that use replicated state by all means, do it. &nbsp;To enable
<BR>people who want to build systems where state is kept in the UA, we
<BR>offer cookies. 
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>In a message dated 4/18/02 9:49:29 PM Eastern Daylight Time, dean.willis@softarmor.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">But a system builder is free to use centralized redundancy. I do it all the time. We sell lots of highly redundant state-shared proxyclusters, primarily as firewall controllers. </FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>Exactly. What I've been trying to say it that there are multiple ways to achieve reliability, and one of them is with redundant, highly reliable systems that do not need to resort to stored their important data in someone elses device for backup. So admit that this may be the better solution in some cases or for some implementors and stop referring to this method as "undesirable".
<BR>
<BR>Mike</FONT></HTML>

--part1_33.25d435b6.29f195f4_boundary--

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



From daemon@ns.ietf.org  Fri Apr 19 12:15:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27005
	for <sipping-archive@odin.ietf.org>; Fri, 19 Apr 2002 12:15:28 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA23227
	for sipping-archive@odin.ietf.org; Fri, 19 Apr 2002 12:15:31 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA22205;
	Fri, 19 Apr 2002 12:00:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA22167
	for <sipping@ns.ietf.org>; Fri, 19 Apr 2002 12:00:54 -0400 (EDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25257
	for <sipping@ietf.org>; Fri, 19 Apr 2002 12:00:51 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g3JG0MpG021192;
	Fri, 19 Apr 2002 09:00:22 -0700 (PDT)
Received: from localhost (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint)
	with ESMTP id ACX19180;
	Fri, 19 Apr 2002 09:00:21 -0700 (PDT)
Date: Fri, 19 Apr 2002 08:57:24 -0700 (Pacific Daylight Time)
From: Rohan Mahy <rohan@cisco.com>
To: Mpierce1@aol.com
cc: sipping@ietf.org, <brian.rosen@marconi.com>
In-Reply-To: <ca.a37334b.29f195f1@aol.com>
Message-ID: <Pine.WNT.4.44.0204190851440.-453743@chorizo.rapidconvergence.com>
X-X-Sender: rmahy@imop.cisco.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Sipping] Re: Cookies vs. State
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org



On Fri, 19 Apr 2002 Mpierce1@aol.com wrote:

> In a message dated 4/18/02 4:06:56 PM Eastern Daylight Time, rohan@cisco.com
> writes:
>
>
> > > [Mike] Yes, I've been involved in the design and implementation of 3
> > telephony
> > > switching systems, where the presumed requirement was for high
> > > reliability/almost no down time. They operated on the principle of
> > > active/standby processors and critical peripherals and performed "state"
> > > sharing between the two sides in order to support switch-over when the
> > active
> > > side failed. I guess coming from this design background, I continue to
> > wonder
> > > why so much effort is being put into complex protocols and procedures
> > between
> > > devices which have a high failure rate and down time rather than tackling
> > the
> > > real problem. Telephone and data switching equipment in the past was
> > designed
> > > for low failure and down time and I continue to wonder why I keep getting
> > > e-mails from our system administrator that "The LAN or e-mail server will
> > be
> > > down for several hours for maintenance".
> >
> > Based on your description, you did not implement such a system in software
> > (as I queried), but in hardware instead.  It is fundamental to the
> > Internet model to use lots of cheap distributed components.  Despite the
> > phone systems better reliability during oridinary usage, the Internet
> > continues to adapt better to unforseen massive failures.  Your Mileage May
> > Vary.
>
> Sorry, I wasn't clear. What I was referring to was completely software. Of
> course it ran on a piece of hardware, which was specially designed for the
> telephony system, since there never was an off-the-shelf computer system that
> could provide the reliablity and functionality required by every telephony
> service provider around the world.

My apologies for mispeaking.  I think others have made my point for me
however about the need for out-of-box redundancy and the complexity of
passing state over the wire.

> I believe if you query those service providers who you hope will replace
> their existing large telephone switches with internet (SIP) based equipment,
> they will universally tell you that reliability is the primary requirement.
> "Cheap" is nice but is secondary. As for "distributed components", as one of
> the ADs insisted, don't tell me that your favorite solution is the
> requirement. And I firmly believe that past experience in telephone switching
> has shown that distributed systems by themselves are not always the answer.

We are now significantly off-topic.  If you object to requirements to
build a distributed system, may I suggest the MEGACO Working Group.  If
you don't object, then we can agree to disagree on this philosophical
point and move on with tightening the language on the cookies draft.

thanks,
-rohan





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



From daemon@ns.ietf.org  Fri Apr 19 13:19:31 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06053
	for <sipping-archive@odin.ietf.org>; Fri, 19 Apr 2002 13:19:31 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA27403
	for sipping-archive@odin.ietf.org; Fri, 19 Apr 2002 13:19:32 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA26421;
	Fri, 19 Apr 2002 13:05:54 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA26390
	for <sipping@ns.ietf.org>; Fri, 19 Apr 2002 13:05:50 -0400 (EDT)
Received: from pine.neustar.com (pine.neustar.com [209.173.57.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04477
	for <sipping@ietf.org>; Fri, 19 Apr 2002 13:05:48 -0400 (EDT)
Received: from chiimc01.il.neustar.com (chih650b-s3p2.il.neustar.com [209.173.57.65])
	by pine.neustar.com (8.11.0/8.11.0) with ESMTP id g3JH5EZ24296;
	Fri, 19 Apr 2002 12:05:14 -0500
Received: by chiimc01.il.neustar.com with Internet Mail Service (5.5.2653.19)
	id <JB0ZV5DM>; Fri, 19 Apr 2002 12:05:09 -0500
Message-ID: <A83B38C38B3ED6119D3600306E0722D038BF71@dc02.npac.com>
From: "Yu, James" <james.yu@neustar.biz>
To: "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>
Cc: sipping@ietf.org
Subject: RE: [Sipping] draft-yu-tel-url-04.txt comment
Date: Fri, 19 Apr 2002 12:05:04 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

> 
> That is true, but the intermediate node may still change the 
> Request-URI. In
> that case it could remote the old user part - INCLUDING your 
> parameters - and
> add a new user part without them. I guess you don't want that 
> to happend, do
> you?

An intermediate node may not just replace the Request-URI by another URL.
For example, if a telephone number (TN) appears in the user part, I cannot
imagine that an intermediate node will totally ignore the TN in the user
part when replacing the Request-URI with another URL.  If the node is
examining the user part, especially the TN and if it understands those
extensions, it will know how to make use of the info.  If it does not
understand the extensions, it can just ignore them.

> 
> Others have asked, and I also still would like to know, why 
> you can't define the
> parameters as uri-parameters instead??? Maybe there is a good 
> reason, and maybe
> there is something I've missed, so please tell me.
> 

Initially I was looking for url-parameters to put rn, npdi and cic.  After
consulting with Jonathan and Henning, they suggested me to put in tel URL.
It made sense because those parameters were closely tied to the TN.  Your
issue is really how to convert a tel URL (with those extensions) to a sip
URL.  The present scheme is to leave them with the TN so they all appear in
the user part.  You are suggesting to put them in the url-parameters.  My
perception is that most people do not have a problem with the current
arrangement.  Please feel free to push for using the url-parameters for
those parameters.  You'll need to defend why you need them.

James

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



From daemon@ns.ietf.org  Fri Apr 19 13:23:05 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06617
	for <sipping-archive@odin.ietf.org>; Fri, 19 Apr 2002 13:23:04 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA27733
	for sipping-archive@odin.ietf.org; Fri, 19 Apr 2002 13:23:05 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA26591;
	Fri, 19 Apr 2002 13:07:09 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA26485
	for <sipping@ns.ietf.org>; Fri, 19 Apr 2002 13:07:01 -0400 (EDT)
Received: from zctfs063.europe.nortel.com (zctfs063.nortelnetworks.com [47.164.128.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04620
	for <sipping@ietf.org>; Fri, 19 Apr 2002 13:06:58 -0400 (EDT)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zctfs063.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3JH6Km00734;
	Fri, 19 Apr 2002 19:06:20 +0200 (MEST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3JH5fv03536;
	Fri, 19 Apr 2002 18:05:41 +0100 (BST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JDW4QAX4>; Fri, 19 Apr 2002 18:06:18 +0100
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F7194@zwcwd00r.europe.nortel.com>
From: "Mark Watson"<mwatson@nortelnetworks.com>
To: "'sipping@ietf.org'" <sipping@ietf.org>,
        "'Peterson, Jon'"
	 <jon.peterson@neustar.biz>
Subject: RE: [Sipping] RE: Network Asserted Identity
Date: Fri, 19 Apr 2002 18:05:32 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E7C4.69F08542"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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

Jon,

I was trying to keep things simply stated, assuming that everyone understood
the applicability statement in the privacy draft - well, at least everyone
that was involved in writing it.

Just for you, in terms of 'significant explication', there is a mathematical
definition of a 'Trust Domain' at the end of this mail along with the
proposed requirements. I think the previous statement of requirements was
clearer, but at least the one below is well-defined.

For everyone else, a 'Trust Domain' is just a group of SIP devices which are
known to follow a particular set of specifications with respect to identity.
One device in the domain 'trusts' another if it has a secure connection to
it AND has been *configured* with the information that the other device is
in the same Trust Domain.

I am proposing that we adopt NAI1 and NAI2 only, which I believe aligns with
Rohan's plan and the 3GPP requirements.

Pls see comments below.

...Mark


Jon wrote:
> Next, I think most of the problems with sip-privacy-04 seem 
> to fall out from the fact that the concepts of 'trusted' and 
> 'untrusted' are not well understood. 

Please see above.

> I'm not sure that we can 
> use these words and think that we're actually putting forward 
> a hard requirement. The Iraqi example, 'screen' and so forth 
> exposed some of the problems with these terms. Therefore I'm 
> a little wary of NAI1, NAI3 and NAI4. 

The Iraqi example concerned NAI4 only. I am not proposing we adopt this
requirement. I'm not sure how that example has relevant to NAI1 and NAI2.

> NAI3 and NAI4 
> especially seem to make assumptions about how trust operates 
> that are a little silly. For NAI3, why would a SIP 'trusted' 
> domain send something through an untrusted domain to get back 
> to itself, to the same trusted domain? 

Because the Trust Domain is not a fully connected network. There are
elements which are not interconnected by any path through trusted elements,
and so the only way of passing information between them is via untrusted
parts of the network. One solution would be to encrypt the information using
a key known to all elements in the Trust Domain. It also encompasses the
Call Trace solution where the user is given the encrypted NAI and passes it
back to (the owner of) the Trust Domain.

If we don't have this requirement, then we don't need encryption.

I am not proposing we adopt this requirement.

> Sure, in the PSTN that 
> might make sense, but that would be a harder sell to claim 
> that SIP networks will need to do this. The whole concept of 
> a trusted domain would require significant explication before 
> any of this made sense. In sip-privacy-04, perhaps the 
> biggest problem is that 'trustedness' is assumed to be 
> something intrinsic about an entity, rather than something 
> about which every other SIP element in the world is entitled 
> to its own opinion.

I don't think the assumption you claim is made by the draft. 'Trustedness'
is indeed an 'opinion' that one node has about another, based on
configuration by human beings who know the properties of the devices (i.e.
that they are indeed compliant to the relevant specifications and so can be
trusted to act in a particular way).

>  
> I would rather phrase NAI1 and NAI2 a little differently. 
> Ideally, these should only be one requirement - that a 
> 'network entity' can insert the identity of a user into a 
> message, and that this identity can be viewed by the 
> recipients of the message. It is a separate matter, a privacy 
> requirement (which I surmise you don't want to group with NAI 
> requirements), that in some instances the user can request 
> that their identity not be shared with others, and it is a 
> problem for that requirement that some administrative domains 
> might obstinantly be inclined to circulate the user's 
> identity anyway. Without this privacy requirement, NAI1 and 
> NAI2 would be identical, right?

No. The requirements do not mention privacy.

NAI1 and NAI2 do ask for different things. There is certainly a way of
stating a single requirement which covers both, but I separated them in case
we don't *want* both.

> NAI4, I suspect, is also this 
> same requirement, in any definition of 'trust' that will turn 
> out to be usable.
>

No. NAI4 implies the need for 'screen' or something equivalent. Without NAI4
then it can be assumed that Network Asserted Identities passed between
entities of a Trust Domain were asserted by an entity in the same Trust
Domain. NAI4 allows identities that were asserted by another Trust Domain to
be passed around. This includes those asserted by a Trust Domain containing
a single User Agent which is exactly what causes the problem of
distinguishing between the identity asserted by the Iraqi network and an
identity asserted by some mischevious user.
 
> On clarifying remark (a), I've never been sure what the big 
> deal is about this 'hinted' identity. I consider 'hinting' to 
> be part of the authentication process by which the NAI is 
> generated. If someone would like to propose some new 
> authentication scheme for SIP that contains a plaintext 
> 'hinted' identity in a header that is sent in a request to 
> the entity that generates the NAI (assuming that some other 
> part of the authentication process involving security has 
> already occurred, or is occurring out of band but cannot 
> accomodate the 'hint'), I welcome them to do so - whether or 
> not any IETF working group would look favorably on that is a 
> different matter. In any event, I maintain that this is a 
> question about how authentication works, and it is orthogonal 
> to the NAI problem - it just ended up being conflated with 
> the privacy and identity problems in the initial 
> considerations of this space. We can all think of 
> authentication systems that intrinsically support such a hint 
> (like Digest, which is mandatory for all SIP entitites).

Agreed. That is why I left it out of scope of this thread.

The requirement is specific to scenarios where a single user (from an
authentication point of view) can be identified by several URIs. This is
certainly the case in 3GPP, and I would expect in other networks.

3GPP have the additional restriction that, except at registration,
authentication is achieved by non-SIP means. So, some means other than SIP
authentication is needed for this hint.

>  
> Clarifying remark (b) makes NAI3 a little more practical, but 
> I think I read NAI3 very differently (in that it didn't 
> involve some sort of administrative process, but was just a 
> protocol concept). I believe (b) is different enough to be a 
> requirement in its own merit, though it also is probably not 
> uncontroversial.

NAI3 was intended to cover protocol means of passing the identity across
untrusted nodes. It was easier to extend it to out-of-band passing as well,
to avoid the need for a further requirement.

I am not proposing we address this requirement.

>  
> So even with a short-term view, I'm afraid I can't 
> immediately go along with these.

With the above clarifications, are you still opposed to NAI1 & NAI2 ?

...Mark

---------Mathematical definition of 'Trust Domain', for those so
inclined--->

Using the symbol 'e' for the usual set membership symbol ('is a member of')

Defn: A 'Trust Domain' is defined to be a set T of SIP elements (UAs,
Proxies etc.) and a set RT of unordered pairs of elements from T such that
for all x e T, {x,x} e RT. (RT is a subset of the set of ALL unordered pairs
from T)

Defn: A is 'T-trusted by' B iff { a, b } e RT.

Defn: An Identity I is said to be 'T-asserted' if it has been asserted by a
network element which is a member of T

Defn: An Identity I is said to be a 'Network Asserted Identity' if there
exist a Trust Domain T with more than one element such that I is T-asserted.

And now two interpretations:
i) a e T implies that a is known to operate strictly according to a set of
specifications Spec(T)
ii) { a, b } e R iff there exists a secure connection between a and b for
transmission of SIP messages (e.g. IPSEC, TLS, dedicated link etc.)

Real SIP elements are arranged into Trust Domains by human beings in some
unspecified (out of band) manner. This would require the definition of
Spec(T) for the trust domain T.

Note that every (untrusted) UA is a member of a trust domain all of it's
own.

Now the proposed requirements are to define a specification S such that if S
e Spec(T) then the following can be achieved (where T and U are Trust
Domains):
NAI1) The ability for an element A e T to securely pass a T-asserted
Identity to an element B e T, where A is T-trusted by B.
NAI2) The ability for an element A e T to securely pass a T-asserted
Identity to an element C, where NOT c e T.
NAI3) The ability for an element A e T to securely pass a T-asserted
Identity to an element B e T via another element C, where NOT C e T
NAI4a) The ability for an element A e T to pass a T-asserted Identity to an
element B, where NOT B e T
NAI4b) The ability for an element B e U to pass a Network Asserted Identity
to an element C e U, where  B is U-trusted by C.
NAI4c) The ability for an element B e U to pass a Network Asserted Identity
to an element C, where NOT C e U.


----------------------------------------------------------------------------
---
>  
> Jon Peterson
> NeuStar, Inc.
> -----Original Message-----
> From: Mark Watson [mailto:mwatson@nortelnetworks.com]
> Sent: Thursday, April 18, 2002 7:12 AM
> To: 'sipping@ietf.org'
> Subject: [Sipping] RE: Network Asserted Identity
> 
> 
> So, no comments on the proposed requirements below. I take it 
> everyone agrees then ? 
> 
> ...Mark 
> 
> > -----Original Message----- 
> 
> > OK, so lets see if we can conclude on _short-term_ Network 
> > Asserted identity requirements in a separate thread. 
> > Follow-ups to SIPPING ONLY please. 
> > 
> > First, assume a trust domain model as per privacy draft 
> > applicability statement. Entities within a domain trust each 
> > other, entities in different domains are mutually untrusted. 
> > 
> > I'll try to build up the requirements, least contraversial first: 
> > NAI1) The ability for network entities to insert a network 
> > asserted identity and pass to other network entities within 
> > the same trust domain. 
> > 
> > NAI2) The ability for a network entity to pass a 
> > (non-private) network asserted identity directly to a UA 
> > 
> > NAI3) Secure transport of network asserted identity across 
> > 'untrusted' networks back to the same trust domain (including 
> > between trust 'islands' - disconnected parts of a single 
> trust domain) 
> > 
> > NAI4) Transport of network asserted identity between trust 
> > domains (i.e. transport in one domain of a network asserted 
> > identity received from another domain) 
> > 
> > For clarity, 
> > (a) the requirement for a user to choose one of a number of 
> > identities, whilst retaining privacy, is a 3GPP requirement, 
> > but is *out of scope* of this thread. 
> > 
> > (b) Call Trace implemented by encrypting the identity and 
> > passing this to the called user, who can then pass the 
> > encrypted identity to the generating service 
> > provider/authorities, is considered a sub-case of NAI3 - the 
> > identity is passed to the 'untrusted' user and back to the 
> > original Trust Domain (the Service Provider) before being 
> > passed to the authorities. 
> > 
> > I expect the From/To debate will continue, probably to the 
> > end of time, but I don't see a strong relationship with this issue. 
> > 
> > If people agree with my statement of the potential 
> > requirements, perhaps we could open discussion on which of 
> > these should be considered for immediate standardisation. The 
> > others can be put into the pot for discussion of the generic 
> > privacy requirements. 
> > 
> > For my part, I am most concerned about NAI1 and NAI2. 
> > 
> > Regards...Mark 
---------Mathematical definition of 'Trust Domain', for those so
inclined--->

Using the symbol 'e' for the usual set membership symbol ('is a member of')

Defn: A 'Trust Domain' is defined to be a set T of SIP elements (UAs,
Proxies etc.) and a set RT of unordered pairs of elements from T such that
for all x e T, {x,x} e RT. (RT is a subset of the set of ALL unordered pairs
from T)

Defn: A is 'T-trusted by' B iff { a, b } e RT.

Defn: An Identity I is said to be 'T-asserted' if it has been asserted by a
network element which is a member of T

Defn: An Identity I is said to be a 'Network Asserted Identity' if there
exist a Trust Domain T with more than one element such that I is T-asserted.

And now two interpretations:
i) a e T implies that a is known to operate strictly according to a set of
specifications Spec(T)
ii) { a, b } e R iff there exists a secure connection between a and b for
transmission of SIP messages (e.g. IPSEC, TLS, dedicated link etc.)

Real SIP elements are arranged into Trust Domains by human beings in some
unspecified (out of band) manner. This would require the definition of
Spec(T) for the trust domain T.

Note that every (untrusted) UA is a member of a trust domain all of it's
own.

Now the proposed requirements are to define a specification S such that if S
e Spec(T) then the following can be achieved (where T and U are Trust
Domains):
NAI1) The ability for an element A e T to securely pass a T-asserted
Identity to an element B e T, where A is T-trusted by B.
NAI2) The ability for an element A e T to securely pass a T-asserted
Identity to an element C, where NOT c e T.
NAI3) The ability for an element A e T to securely pass a T-asserted
Identity to an element B e T via another element C, where NOT C e T
NAI4a) The ability for an element A e T to pass a T-asserted Identity to an
element B, where NOT B e T
NAI4b) The ability for an element B e U to pass a Network Asserted Identity
to an element C e U, where  B is U-trusted by C.
NAI4c) The ability for an element B e U to pass a Network Asserted Identity
to an element C, where NOT C e U.


----------------------------------------------------------------------------
---

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Sipping] RE: Network Asserted Identity</TITLE>
</HEAD>
<BODY>

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

<P><FONT SIZE=3D2>I was trying to keep things simply stated, assuming =
that everyone understood the applicability statement in the privacy =
draft - well, at least everyone that was involved in writing =
it.</FONT></P>

<P><FONT SIZE=3D2>Just for you, in terms of 'significant explication', =
there is a mathematical definition of a 'Trust Domain' at the end of =
this mail along with the proposed requirements. I think the previous =
statement of requirements was clearer, but at least the one below is =
well-defined.</FONT></P>

<P><FONT SIZE=3D2>For everyone else, a 'Trust Domain' is just a group =
of SIP devices which are known to follow a particular set of =
specifications with respect to identity. One device in the domain =
'trusts' another if it has a secure connection to it AND has been =
*configured* with the information that the other device is in the same =
Trust Domain.</FONT></P>

<P><FONT SIZE=3D2>I am proposing that we adopt NAI1 and NAI2 only, =
which I believe aligns with Rohan's plan and the 3GPP =
requirements.</FONT>
</P>

<P><FONT SIZE=3D2>Pls see comments below.</FONT>
</P>

<P><FONT SIZE=3D2>...Mark</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Jon wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; Next, I think most of the problems with =
sip-privacy-04 seem </FONT>
<BR><FONT SIZE=3D2>&gt; to fall out from the fact that the concepts of =
'trusted' and </FONT>
<BR><FONT SIZE=3D2>&gt; 'untrusted' are not well understood. </FONT>
</P>

<P><FONT SIZE=3D2>Please see above.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; I'm not sure that we can </FONT>
<BR><FONT SIZE=3D2>&gt; use these words and think that we're actually =
putting forward </FONT>
<BR><FONT SIZE=3D2>&gt; a hard requirement. The Iraqi example, 'screen' =
and so forth </FONT>
<BR><FONT SIZE=3D2>&gt; exposed some of the problems with these terms. =
Therefore I'm </FONT>
<BR><FONT SIZE=3D2>&gt; a little wary of NAI1, NAI3 and NAI4. </FONT>
</P>

<P><FONT SIZE=3D2>The Iraqi example concerned NAI4 only. I am not =
proposing we adopt this requirement. I'm not sure how that example has =
relevant to NAI1 and NAI2.</FONT></P>

<P><FONT SIZE=3D2>&gt; NAI3 and NAI4 </FONT>
<BR><FONT SIZE=3D2>&gt; especially seem to make assumptions about how =
trust operates </FONT>
<BR><FONT SIZE=3D2>&gt; that are a little silly. For NAI3, why would a =
SIP 'trusted' </FONT>
<BR><FONT SIZE=3D2>&gt; domain send something through an untrusted =
domain to get back </FONT>
<BR><FONT SIZE=3D2>&gt; to itself, to the same trusted domain? </FONT>
</P>

<P><FONT SIZE=3D2>Because the Trust Domain is not a fully connected =
network. There are elements which are not interconnected by any path =
through trusted elements, and so the only way of passing information =
between them is via untrusted parts of the network. One solution would =
be to encrypt the information using a key known to all elements in the =
Trust Domain. It also encompasses the Call Trace solution where the =
user is given the encrypted NAI and passes it back to (the owner of) =
the Trust Domain.</FONT></P>

<P><FONT SIZE=3D2>If we don't have this requirement, then we don't need =
encryption.</FONT>
</P>

<P><FONT SIZE=3D2>I am not proposing we adopt this requirement.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; Sure, in the PSTN that </FONT>
<BR><FONT SIZE=3D2>&gt; might make sense, but that would be a harder =
sell to claim </FONT>
<BR><FONT SIZE=3D2>&gt; that SIP networks will need to do this. The =
whole concept of </FONT>
<BR><FONT SIZE=3D2>&gt; a trusted domain would require significant =
explication before </FONT>
<BR><FONT SIZE=3D2>&gt; any of this made sense. In sip-privacy-04, =
perhaps the </FONT>
<BR><FONT SIZE=3D2>&gt; biggest problem is that 'trustedness' is =
assumed to be </FONT>
<BR><FONT SIZE=3D2>&gt; something intrinsic about an entity, rather =
than something </FONT>
<BR><FONT SIZE=3D2>&gt; about which every other SIP element in the =
world is entitled </FONT>
<BR><FONT SIZE=3D2>&gt; to its own opinion.</FONT>
</P>

<P><FONT SIZE=3D2>I don't think the assumption you claim is made by the =
draft. 'Trustedness' is indeed an 'opinion' that one node has about =
another, based on configuration by human beings who know the properties =
of the devices (i.e. that they are indeed compliant to the relevant =
specifications and so can be trusted to act in a particular =
way).</FONT></P>

<P><FONT SIZE=3D2>&gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; I would rather phrase NAI1 and NAI2 a little =
differently. </FONT>
<BR><FONT SIZE=3D2>&gt; Ideally, these should only be one requirement - =
that a </FONT>
<BR><FONT SIZE=3D2>&gt; 'network entity' can insert the identity of a =
user into a </FONT>
<BR><FONT SIZE=3D2>&gt; message, and that this identity can be viewed =
by the </FONT>
<BR><FONT SIZE=3D2>&gt; recipients of the message. It is a separate =
matter, a privacy </FONT>
<BR><FONT SIZE=3D2>&gt; requirement (which I surmise you don't want to =
group with NAI </FONT>
<BR><FONT SIZE=3D2>&gt; requirements), that in some instances the user =
can request </FONT>
<BR><FONT SIZE=3D2>&gt; that their identity not be shared with others, =
and it is a </FONT>
<BR><FONT SIZE=3D2>&gt; problem for that requirement that some =
administrative domains </FONT>
<BR><FONT SIZE=3D2>&gt; might obstinantly be inclined to circulate the =
user's </FONT>
<BR><FONT SIZE=3D2>&gt; identity anyway. Without this privacy =
requirement, NAI1 and </FONT>
<BR><FONT SIZE=3D2>&gt; NAI2 would be identical, right?</FONT>
</P>

<P><FONT SIZE=3D2>No. The requirements do not mention privacy.</FONT>
</P>

<P><FONT SIZE=3D2>NAI1 and NAI2 do ask for different things. There is =
certainly a way of stating a single requirement which covers both, but =
I separated them in case we don't *want* both.</FONT></P>

<P><FONT SIZE=3D2>&gt; NAI4, I suspect, is also this </FONT>
<BR><FONT SIZE=3D2>&gt; same requirement, in any definition of 'trust' =
that will turn </FONT>
<BR><FONT SIZE=3D2>&gt; out to be usable.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
</P>

<P><FONT SIZE=3D2>No. NAI4 implies the need for 'screen' or something =
equivalent. Without NAI4 then it can be assumed that Network Asserted =
Identities passed between entities of a Trust Domain were asserted by =
an entity in the same Trust Domain. NAI4 allows identities that were =
asserted by another Trust Domain to be passed around. This includes =
those asserted by a Trust Domain containing a single User Agent which =
is exactly what causes the problem of distinguishing between the =
identity asserted by the Iraqi network and an identity asserted by some =
mischevious user.</FONT></P>

<P><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>&gt; On clarifying remark (a), I've never been sure =
what the big </FONT>
<BR><FONT SIZE=3D2>&gt; deal is about this 'hinted' identity. I =
consider 'hinting' to </FONT>
<BR><FONT SIZE=3D2>&gt; be part of the authentication process by which =
the NAI is </FONT>
<BR><FONT SIZE=3D2>&gt; generated. If someone would like to propose =
some new </FONT>
<BR><FONT SIZE=3D2>&gt; authentication scheme for SIP that contains a =
plaintext </FONT>
<BR><FONT SIZE=3D2>&gt; 'hinted' identity in a header that is sent in a =
request to </FONT>
<BR><FONT SIZE=3D2>&gt; the entity that generates the NAI (assuming =
that some other </FONT>
<BR><FONT SIZE=3D2>&gt; part of the authentication process involving =
security has </FONT>
<BR><FONT SIZE=3D2>&gt; already occurred, or is occurring out of band =
but cannot </FONT>
<BR><FONT SIZE=3D2>&gt; accomodate the 'hint'), I welcome them to do so =
- whether or </FONT>
<BR><FONT SIZE=3D2>&gt; not any IETF working group would look favorably =
on that is a </FONT>
<BR><FONT SIZE=3D2>&gt; different matter. In any event, I maintain that =
this is a </FONT>
<BR><FONT SIZE=3D2>&gt; question about how authentication works, and it =
is orthogonal </FONT>
<BR><FONT SIZE=3D2>&gt; to the NAI problem - it just ended up being =
conflated with </FONT>
<BR><FONT SIZE=3D2>&gt; the privacy and identity problems in the =
initial </FONT>
<BR><FONT SIZE=3D2>&gt; considerations of this space. We can all think =
of </FONT>
<BR><FONT SIZE=3D2>&gt; authentication systems that intrinsically =
support such a hint </FONT>
<BR><FONT SIZE=3D2>&gt; (like Digest, which is mandatory for all SIP =
entitites).</FONT>
</P>

<P><FONT SIZE=3D2>Agreed. That is why I left it out of scope of this =
thread.</FONT>
</P>

<P><FONT SIZE=3D2>The requirement is specific to scenarios where a =
single user (from an authentication point of view) can be identified by =
several URIs. This is certainly the case in 3GPP, and I would expect in =
other networks.</FONT></P>

<P><FONT SIZE=3D2>3GPP have the additional restriction that, except at =
registration, authentication is achieved by non-SIP means. So, some =
means other than SIP authentication is needed for this hint.</FONT></P>

<P><FONT SIZE=3D2>&gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; Clarifying remark (b) makes NAI3 a little more =
practical, but </FONT>
<BR><FONT SIZE=3D2>&gt; I think I read NAI3 very differently (in that =
it didn't </FONT>
<BR><FONT SIZE=3D2>&gt; involve some sort of administrative process, =
but was just a </FONT>
<BR><FONT SIZE=3D2>&gt; protocol concept). I believe (b) is different =
enough to be a </FONT>
<BR><FONT SIZE=3D2>&gt; requirement in its own merit, though it also is =
probably not </FONT>
<BR><FONT SIZE=3D2>&gt; uncontroversial.</FONT>
</P>

<P><FONT SIZE=3D2>NAI3 was intended to cover protocol means of passing =
the identity across untrusted nodes. It was easier to extend it to =
out-of-band passing as well, to avoid the need for a further =
requirement.</FONT></P>

<P><FONT SIZE=3D2>I am not proposing we address this =
requirement.</FONT>
</P>

<P><FONT SIZE=3D2>&gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; So even with a short-term view, I'm afraid I =
can't </FONT>
<BR><FONT SIZE=3D2>&gt; immediately go along with these.</FONT>
</P>

<P><FONT SIZE=3D2>With the above clarifications, are you still opposed =
to NAI1 &amp; NAI2 ?</FONT>
</P>

<P><FONT SIZE=3D2>...Mark</FONT>
</P>

<P><FONT SIZE=3D2>---------Mathematical definition of 'Trust Domain', =
for those so inclined---&gt;</FONT>
</P>

<P><FONT SIZE=3D2>Using the symbol 'e' for the usual set membership =
symbol ('is a member of')</FONT>
</P>

<P><FONT SIZE=3D2>Defn: A 'Trust Domain' is defined to be a set T of =
SIP elements (UAs, Proxies etc.) and a set RT of unordered pairs of =
elements from T such that for all x e T, {x,x} e RT. (RT is a subset of =
the set of ALL unordered pairs from T)</FONT></P>

<P><FONT SIZE=3D2>Defn: A is 'T-trusted by' B iff { a, b } e RT.</FONT>
</P>

<P><FONT SIZE=3D2>Defn: An Identity I is said to be 'T-asserted' if it =
has been asserted by a network element which is a member of T</FONT>
</P>

<P><FONT SIZE=3D2>Defn: An Identity I is said to be a 'Network Asserted =
Identity' if there exist a Trust Domain T with more than one element =
such that I is T-asserted.</FONT></P>

<P><FONT SIZE=3D2>And now two interpretations:</FONT>
<BR><FONT SIZE=3D2>i) a e T implies that a is known to operate strictly =
according to a set of specifications Spec(T)</FONT>
<BR><FONT SIZE=3D2>ii) { a, b } e R iff there exists a secure =
connection between a and b for transmission of SIP messages (e.g. =
IPSEC, TLS, dedicated link etc.)</FONT></P>

<P><FONT SIZE=3D2>Real SIP elements are arranged into Trust Domains by =
human beings in some unspecified (out of band) manner. This would =
require the definition of Spec(T) for the trust domain T.</FONT></P>

<P><FONT SIZE=3D2>Note that every (untrusted) UA is a member of a trust =
domain all of it's own.</FONT>
</P>

<P><FONT SIZE=3D2>Now the proposed requirements are to define a =
specification S such that if S e Spec(T) then the following can be =
achieved (where T and U are Trust Domains):</FONT></P>

<P><FONT SIZE=3D2>NAI1) The ability for an element A e T to securely =
pass a T-asserted Identity to an element B e T, where A is T-trusted by =
B.</FONT></P>

<P><FONT SIZE=3D2>NAI2) The ability for an element A e T to securely =
pass a T-asserted Identity to an element C, where NOT c e T.</FONT>
<BR><FONT SIZE=3D2>NAI3) The ability for an element A e T to securely =
pass a T-asserted Identity to an element B e T via another element C, =
where NOT C e T</FONT></P>

<P><FONT SIZE=3D2>NAI4a) The ability for an element A e T to pass a =
T-asserted Identity to an element B, where NOT B e T</FONT>
<BR><FONT SIZE=3D2>NAI4b) The ability for an element B e U to pass a =
Network Asserted Identity to an element C e U, where&nbsp; B is =
U-trusted by C.</FONT></P>

<P><FONT SIZE=3D2>NAI4c) The ability for an element B e U to pass a =
Network Asserted Identity to an element C, where NOT C e U.</FONT>
</P>
<BR>

<P><FONT =
SIZE=3D2>---------------------------------------------------------------=
----------------</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&gt; Jon Peterson</FONT>
<BR><FONT SIZE=3D2>&gt; NeuStar, Inc.</FONT>
<BR><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Mark Watson [<A =
HREF=3D"mailto:mwatson@nortelnetworks.com">mailto:mwatson@nortelnetworks=
.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Thursday, April 18, 2002 7:12 AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'sipping@ietf.org'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: [Sipping] RE: Network Asserted =
Identity</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; So, no comments on the proposed requirements =
below. I take it </FONT>
<BR><FONT SIZE=3D2>&gt; everyone agrees then ? </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; ...Mark </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; -----Original Message----- </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; OK, so lets see if we can conclude on =
_short-term_ Network </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Asserted identity requirements in a =
separate thread. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Follow-ups to SIPPING ONLY please. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; First, assume a trust domain model as per =
privacy draft </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; applicability statement. Entities within a =
domain trust each </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; other, entities in different domains are =
mutually untrusted. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I'll try to build up the requirements, =
least contraversial first: </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; NAI1) The ability for network entities to =
insert a network </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; asserted identity and pass to other =
network entities within </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the same trust domain. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; NAI2) The ability for a network entity to =
pass a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; (non-private) network asserted identity =
directly to a UA </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; NAI3) Secure transport of network asserted =
identity across </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; 'untrusted' networks back to the same =
trust domain (including </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; between trust 'islands' - disconnected =
parts of a single </FONT>
<BR><FONT SIZE=3D2>&gt; trust domain) </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; NAI4) Transport of network asserted =
identity between trust </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; domains (i.e. transport in one domain of a =
network asserted </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; identity received from another domain) =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; For clarity, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; (a) the requirement for a user to choose =
one of a number of </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; identities, whilst retaining privacy, is a =
3GPP requirement, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; but is *out of scope* of this thread. =
</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; (b) Call Trace implemented by encrypting =
the identity and </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; passing this to the called user, who can =
then pass the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; encrypted identity to the generating =
service </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; provider/authorities, is considered a =
sub-case of NAI3 - the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; identity is passed to the 'untrusted' user =
and back to the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; original Trust Domain (the Service =
Provider) before being </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; passed to the authorities. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I expect the From/To debate will continue, =
probably to the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; end of time, but I don't see a strong =
relationship with this issue. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; If people agree with my statement of the =
potential </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; requirements, perhaps we could open =
discussion on which of </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; these should be considered for immediate =
standardisation. The </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; others can be put into the pot for =
discussion of the generic </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; privacy requirements. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; For my part, I am most concerned about =
NAI1 and NAI2. </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Regards...Mark </FONT>
<BR><FONT SIZE=3D2>---------Mathematical definition of 'Trust Domain', =
for those so inclined---&gt;</FONT>
</P>

<P><FONT SIZE=3D2>Using the symbol 'e' for the usual set membership =
symbol ('is a member of')</FONT>
</P>

<P><FONT SIZE=3D2>Defn: A 'Trust Domain' is defined to be a set T of =
SIP elements (UAs, Proxies etc.) and a set RT of unordered pairs of =
elements from T such that for all x e T, {x,x} e RT. (RT is a subset of =
the set of ALL unordered pairs from T)</FONT></P>

<P><FONT SIZE=3D2>Defn: A is 'T-trusted by' B iff { a, b } e RT.</FONT>
</P>

<P><FONT SIZE=3D2>Defn: An Identity I is said to be 'T-asserted' if it =
has been asserted by a network element which is a member of T</FONT>
</P>

<P><FONT SIZE=3D2>Defn: An Identity I is said to be a 'Network Asserted =
Identity' if there exist a Trust Domain T with more than one element =
such that I is T-asserted.</FONT></P>

<P><FONT SIZE=3D2>And now two interpretations:</FONT>
<BR><FONT SIZE=3D2>i) a e T implies that a is known to operate strictly =
according to a set of specifications Spec(T)</FONT>
<BR><FONT SIZE=3D2>ii) { a, b } e R iff there exists a secure =
connection between a and b for transmission of SIP messages (e.g. =
IPSEC, TLS, dedicated link etc.)</FONT></P>

<P><FONT SIZE=3D2>Real SIP elements are arranged into Trust Domains by =
human beings in some unspecified (out of band) manner. This would =
require the definition of Spec(T) for the trust domain T.</FONT></P>

<P><FONT SIZE=3D2>Note that every (untrusted) UA is a member of a trust =
domain all of it's own.</FONT>
</P>

<P><FONT SIZE=3D2>Now the proposed requirements are to define a =
specification S such that if S e Spec(T) then the following can be =
achieved (where T and U are Trust Domains):</FONT></P>

<P><FONT SIZE=3D2>NAI1) The ability for an element A e T to securely =
pass a T-asserted Identity to an element B e T, where A is T-trusted by =
B.</FONT></P>

<P><FONT SIZE=3D2>NAI2) The ability for an element A e T to securely =
pass a T-asserted Identity to an element C, where NOT c e T.</FONT>
<BR><FONT SIZE=3D2>NAI3) The ability for an element A e T to securely =
pass a T-asserted Identity to an element B e T via another element C, =
where NOT C e T</FONT></P>

<P><FONT SIZE=3D2>NAI4a) The ability for an element A e T to pass a =
T-asserted Identity to an element B, where NOT B e T</FONT>
<BR><FONT SIZE=3D2>NAI4b) The ability for an element B e U to pass a =
Network Asserted Identity to an element C e U, where&nbsp; B is =
U-trusted by C.</FONT></P>

<P><FONT SIZE=3D2>NAI4c) The ability for an element B e U to pass a =
Network Asserted Identity to an element C, where NOT C e U.</FONT>
</P>
<BR>

<P><FONT =
SIZE=3D2>---------------------------------------------------------------=
----------------</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1E7C4.69F08542--

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



From daemon@ns.ietf.org  Fri Apr 19 15:16:40 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21173
	for <sipping-archive@odin.ietf.org>; Fri, 19 Apr 2002 15:16:40 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA04637
	for sipping-archive@odin.ietf.org; Fri, 19 Apr 2002 15:16:42 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA04222;
	Fri, 19 Apr 2002 15:05:46 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA04191
	for <sipping@ns.ietf.org>; Fri, 19 Apr 2002 15:05:43 -0400 (EDT)
Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19581
	for <sipping@ietf.org>; Fri, 19 Apr 2002 15:05:40 -0400 (EDT)
Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26])
	by mail-green.research.att.com (Postfix) with ESMTP
	id D31531E004; Fri, 19 Apr 2002 14:28:50 -0400 (EDT)
Received: from fish.research.att.com (fish.research.att.com [135.207.27.137])
	by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id OAA23208;
	Fri, 19 Apr 2002 14:28:45 -0400 (EDT)
From: William Marshall <wtm@research.att.com>
Received: (from wtm@localhost)
	by fish.research.att.com (SGI-8.9.3/8.8.5) id OAA11550;
	Fri, 19 Apr 2002 14:28:18 -0400 (EDT)
Date: Fri, 19 Apr 2002 14:28:18 -0400 (EDT)
Message-Id: <200204191828.OAA11550@fish.research.att.com>
To: Brian.Rosen@marconi.com
Cc: sipping@ietf.org
Subject: Re: [Sipping] RE: Network Asserted Identity
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Brian Rosen wrote:
> > NAI2) The ability for a network entity to pass a 
> > (non-private) network asserted identity directly to a UA  
> I'd like to explore this one.  In my zeal to cut down the discussion to 
> manageable hunks, I don't get why we need this now.  I think NAI is 
> strictly for SP elements to assert an identity to one another, 
> and there is no requirement for any UA to see it.  If we can always 
> define NAI as inserted by the network, and stripped prior to sending to 
> a UA, then I think many things may get simpler.
> 
> It may also make other people happier with this work - UAs send 
> things they want the other UA to see.  Proxy Servers send things 
> they want other Proxy Servers to see.  I'm still assuming a B2BUA 
> is needed for really anonymous calls, and to deal with Subscriber 
> vs User issues. 

The symmetry is certainly nice.

However, we also need to account for informational items that an inbound
proxy will insert in the request for its clients.  In the same way that
an originating UA will insert informational items for its outbound proxy
(like authentication headers).  So there are really three pairwise
assiciations at work here:

   UAC <----> Proxy <----> Proxy <----> UAC
    <------------------------------------>	user<->user items
    <----------->            <----------->	user<->proxy items
                <------------>			proxy<->proxy items

The proxies in the above diagram will certainly use the user-to-proxy
items to generate the proxy-to-proxy items, and use the proxy-to-proxy
items to generate the proxy-to-user items.  Would it really "make other 
people happier with this work" if the header names were different, but 
the processing rules the same?

Leaving the philosophy, and on a more practical level, the whole
reason caller-id is a useful service is that it is NOT user-provided.

Bill Marshall
wtm@research.att.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 daemon@ns.ietf.org  Fri Apr 19 15:23:58 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21993
	for <sipping-archive@odin.ietf.org>; Fri, 19 Apr 2002 15:23:58 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA04862
	for sipping-archive@odin.ietf.org; Fri, 19 Apr 2002 15:24:00 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA04502;
	Fri, 19 Apr 2002 15:13:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA04472
	for <sipping@ns.ietf.org>; Fri, 19 Apr 2002 15:13:18 -0400 (EDT)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20752
	for <sipping@ietf.org>; Fri, 19 Apr 2002 15:13:15 -0400 (EDT)
Received: from cia.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g3JJDAqL011609;
	Fri, 19 Apr 2002 15:13:10 -0400 (EDT)
Received: from MHAMMER-W2K.cisco.com (hrn2-dhcp-161-44-87-145.cisco.com [161.44.87.145])
	by cia.cisco.com (Mirapoint)
	with ESMTP id AAU34789;
	Fri, 19 Apr 2002 15:07:43 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020419150935.03bef008@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 19 Apr 2002 15:12:44 -0400
To: "Yu, James" <james.yu@neustar.biz>
From: Michael Hammer <mhammer@cisco.com>
Subject: RE: [Sipping] draft-yu-tel-url-04.txt comment
Cc: "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>,
        sipping@ietf.org
In-Reply-To: <A83B38C38B3ED6119D3600306E0722D038BF71@dc02.npac.com>
Mime-Version: 1.0
Content-Type: text/html; charset="us-ascii"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

<html>
<font size=3>James,<br>
<br>
Another thought:&nbsp; How do anonymizers handle these parameters?&nbsp;
Would they preserve the parameters somehow, even though they are not
privacy related?<br>
<br>
Mike<br>
<br>
<br>
At 12:05 PM 4/19/2002 -0500, Yu, James wrote:<br>
<blockquote type=cite cite>&gt; <br>
&gt; That is true, but the intermediate node may still change the <br>
&gt; Request-URI. In<br>
&gt; that case it could remote the old user part - INCLUDING your <br>
&gt; parameters - and<br>
&gt; add a new user part without them. I guess you don't want that <br>
&gt; to happend, do<br>
&gt; you?<br>
<br>
An intermediate node may not just replace the Request-URI by another
URL.<br>
For example, if a telephone number (TN) appears in the user part, I
cannot<br>
imagine that an intermediate node will totally ignore the TN in the
user<br>
part when replacing the Request-URI with another URL.&nbsp; If the node
is<br>
examining the user part, especially the TN and if it understands
those<br>
extensions, it will know how to make use of the info.&nbsp; If it does
not<br>
understand the extensions, it can just ignore them.<br>
<br>
&gt; <br>
&gt; Others have asked, and I also still would like to know, why <br>
&gt; you can't define the<br>
&gt; parameters as uri-parameters instead??? Maybe there is a good <br>
&gt; reason, and maybe<br>
&gt; there is something I've missed, so please tell me.<br>
&gt; <br>
<br>
Initially I was looking for url-parameters to put rn, npdi and cic.&nbsp;
After<br>
consulting with Jonathan and Henning, they suggested me to put in tel
URL.<br>
It made sense because those parameters were closely tied to the TN.&nbsp;
Your<br>
issue is really how to convert a tel URL (with those extensions) to a
sip<br>
URL.&nbsp; The present scheme is to leave them with the TN so they all
appear in<br>
the user part.&nbsp; You are suggesting to put them in the
url-parameters.&nbsp; My<br>
perception is that most people do not have a problem with the
current<br>
arrangement.&nbsp; Please feel free to push for using the url-parameters
for<br>
those parameters.&nbsp; You'll need to defend why you need them.<br>
<br>
James<br>
<br>
_______________________________________________<br>
Sipping mailing list&nbsp;
<a href="https://www1.ietf.org/mailman/listinfo/sipping" eudora="autourl">https://www1.ietf.org/mailman/listinfo/sipping</a><br>
This list is for NEW development of the application of SIP<br>
Use sip-implementors@cs.columbia.edu for questions on current sip<br>
Use sip@ietf.org for new developments of core SIP
</font></blockquote></html>


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



From daemon@ns.ietf.org  Fri Apr 19 15:48:06 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25062
	for <sipping-archive@odin.ietf.org>; Fri, 19 Apr 2002 15:48:06 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA06327
	for sipping-archive@odin.ietf.org; Fri, 19 Apr 2002 15:48:08 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA05981;
	Fri, 19 Apr 2002 15:38:38 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA05946
	for <sipping@ns.ietf.org>; Fri, 19 Apr 2002 15:38:35 -0400 (EDT)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23952
	for <sipping@ietf.org>; Fri, 19 Apr 2002 15:38:32 -0400 (EDT)
Received: from cia.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g3JJcRgf013949;
	Fri, 19 Apr 2002 15:38:27 -0400 (EDT)
Received: from MHAMMER-W2K.cisco.com (hrn2-dhcp-161-44-87-145.cisco.com [161.44.87.145])
	by cia.cisco.com (Mirapoint)
	with ESMTP id AAU35036;
	Fri, 19 Apr 2002 15:33:00 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020419153720.00b74448@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 19 Apr 2002 15:38:01 -0400
To: "Yu, James" <james.yu@neustar.biz>
From: Michael Hammer <mhammer@cisco.com>
Subject: RE: [Sipping] draft-yu-tel-url-04.txt comment
Cc: "'Christer Holmberg'" <christer.holmberg@lmf.ericsson.se>,
        sipping@ietf.org
In-Reply-To: <A83B38C38B3ED6119D3600306E0722D038BF71@dc02.npac.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

All,

Scratch that last question.  I think I am getting my wires crossed between 
reading two threads.

Mike


At 12:05 PM 4/19/2002 -0500, Yu, James wrote:
> >
> > That is true, but the intermediate node may still change the
> > Request-URI. In
> > that case it could remote the old user part - INCLUDING your
> > parameters - and
> > add a new user part without them. I guess you don't want that
> > to happend, do
> > you?
>
>An intermediate node may not just replace the Request-URI by another URL.
>For example, if a telephone number (TN) appears in the user part, I cannot
>imagine that an intermediate node will totally ignore the TN in the user
>part when replacing the Request-URI with another URL.  If the node is
>examining the user part, especially the TN and if it understands those
>extensions, it will know how to make use of the info.  If it does not
>understand the extensions, it can just ignore them.
>
> >
> > Others have asked, and I also still would like to know, why
> > you can't define the
> > parameters as uri-parameters instead??? Maybe there is a good
> > reason, and maybe
> > there is something I've missed, so please tell me.
> >
>
>Initially I was looking for url-parameters to put rn, npdi and cic.  After
>consulting with Jonathan and Henning, they suggested me to put in tel URL.
>It made sense because those parameters were closely tied to the TN.  Your
>issue is really how to convert a tel URL (with those extensions) to a sip
>URL.  The present scheme is to leave them with the TN so they all appear in
>the user part.  You are suggesting to put them in the url-parameters.  My
>perception is that most people do not have a problem with the current
>arrangement.  Please feel free to push for using the url-parameters for
>those parameters.  You'll need to defend why you need them.
>
>James
>
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the 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 daemon@ns.ietf.org  Fri Apr 19 17:32:20 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06177
	for <sipping-archive@odin.ietf.org>; Fri, 19 Apr 2002 17:32:16 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA12035
	for sipping-archive@odin.ietf.org; Fri, 19 Apr 2002 17:32:18 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA10997;
	Fri, 19 Apr 2002 17:13:48 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA10970
	for <sipping@ns.ietf.org>; Fri, 19 Apr 2002 17:13:45 -0400 (EDT)
Received: from bdsl.66.12.12.130.gte.net (bdsl.66.12.12.130.gte.net [66.12.12.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04338
	for <sipping@ietf.org>; Fri, 19 Apr 2002 17:13:41 -0400 (EDT)
Received: from TXDWILLIS2 (bdsl.greycouncil.com [127.0.0.1])
	by bdsl.66.12.12.130.gte.net (8.11.6/8.11.6) with ESMTP id g3JLDAd21945;
	Fri, 19 Apr 2002 16:13:10 -0500
From: "Dean Willis" <dean.willis@softarmor.com>
To: <Mpierce1@aol.com>, <sipping@ietf.org>
Cc: <Brian.Rosen@marconi.com>
Subject: RE: [Sipping] Re: Cookies vs. State
Date: Fri, 19 Apr 2002 16:13:03 -0500
Message-ID: <00e301c1e7e6$fea44f80$1e036e3f@TXDWILLIS2>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00E4_01C1E7BD.15CE4780"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
In-Reply-To: <33.25d435b6.29f195f4@aol.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_00E4_01C1E7BD.15CE4780
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Mike said:
------------- 
Exactly. What I've been trying to say it that there are multiple ways to
achieve reliability, and one of them is with redundant, highly reliable
systems that do not need to resort to stored their important data in
someone elses device for backup. So admit that this may be the better
solution in some cases or for some implementors and stop referring to
this method as "undesirable". 
-------------
 
Hey, nobody is forcing you (well, I suppose that depends on your
contract) to build a service platform that relies on cookies for its
reliability mechanism. Likewise, nobody is forcing you to use
shared-state redundancy. 
 
Each is undesirable in some circumstances.
 
--
Dean
 

------=_NextPart_000_00E4_01C1E7BD.15CE4780
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

<META content=3D"MSHTML 6.00.2715.400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial><FONT lang=3D0 color=3D#000000 =
FAMILY=3D"SANSSERIF"><FONT=20
size=3D2><SPAN class=3D611551021-19042002><FONT color=3D#0000ff>Mike=20
said:</FONT></SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT lang=3D0 color=3D#000000 =
FAMILY=3D"SANSSERIF"><FONT=20
size=3D2><SPAN class=3D611551021-19042002><FONT=20
color=3D#0000ff>-------------</FONT>&nbsp;</SPAN><BR>Exactly. What I've =
been=20
trying to say it that there are multiple ways to achieve reliability, =
and one of=20
them is with redundant, highly reliable systems that do not need to =
resort to=20
stored their important data in someone elses device for backup. So admit =
that=20
this may be the better solution in some cases or for some implementors =
and stop=20
referring to this method as "undesirable".&nbsp;<BR><SPAN=20
class=3D611551021-19042002><FONT color=3D#0000ff><FONT=20
color=3D#000000>-</FONT>------------</FONT></SPAN></FONT></FONT></FONT></=
DIV>
<DIV><FONT face=3DArial><FONT lang=3D0 color=3D#000000 =
FAMILY=3D"SANSSERIF"><FONT=20
color=3D#0000ff size=3D2><SPAN=20
class=3D611551021-19042002></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT lang=3D0 color=3D#000000 =
FAMILY=3D"SANSSERIF"><FONT=20
color=3D#0000ff size=3D2><SPAN class=3D611551021-19042002>Hey, nobody is =
forcing you=20
(well, I suppose that depends on your contract) to build a service =
platform that=20
relies on cookies for its reliability mechanism. Likewise, nobody is =
forcing you=20
to use shared-state redundancy. </SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT lang=3D0 color=3D#000000 =
FAMILY=3D"SANSSERIF"><FONT=20
color=3D#0000ff size=3D2><SPAN=20
class=3D611551021-19042002></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT lang=3D0 color=3D#000000 =
FAMILY=3D"SANSSERIF"><FONT=20
color=3D#0000ff size=3D2><SPAN class=3D611551021-19042002>Each is =
undesirable in some=20
circumstances.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT lang=3D0 color=3D#000000 =
FAMILY=3D"SANSSERIF"><FONT=20
color=3D#0000ff size=3D2><SPAN=20
class=3D611551021-19042002></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT lang=3D0 color=3D#000000 =
FAMILY=3D"SANSSERIF"><FONT=20
color=3D#0000ff size=3D2><SPAN=20
class=3D611551021-19042002>--</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT lang=3D0 color=3D#000000 =
FAMILY=3D"SANSSERIF"><FONT=20
color=3D#0000ff size=3D2><SPAN=20
class=3D611551021-19042002>Dean</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT lang=3D0 color=3D#000000 =
FAMILY=3D"SANSSERIF"><FONT=20
color=3D#0000ff size=3D2><SPAN=20
class=3D611551021-19042002></SPAN></FONT></FONT></FONT>&nbsp;</DIV></BODY=
></HTML>

------=_NextPart_000_00E4_01C1E7BD.15CE4780--


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



From daemon@ns.ietf.org  Fri Apr 19 18:14:36 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10795
	for <sipping-archive@odin.ietf.org>; Fri, 19 Apr 2002 18:14:35 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA13558
	for sipping-archive@odin.ietf.org; Fri, 19 Apr 2002 18:14:38 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA13089;
	Fri, 19 Apr 2002 18:01:14 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA13050
	for <sipping@ns.ietf.org>; Fri, 19 Apr 2002 18:01:11 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09258
	for <sipping@ietf.org>; Fri, 19 Apr 2002 18:01:07 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3JM0cl29280
	for <sipping@ietf.org>; Fri, 19 Apr 2002 18:00:39 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JCV29XF9>; Fri, 19 Apr 2002 18:00:39 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A338@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: sipping@ietf.org
Date: Fri, 19 Apr 2002 18:00:39 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Sipping] Call Flows and Service Examples Documents
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Many apologies for being so last-minute.  I've been totally absorbed in
teaching this week.  I used the call flows and service examples drafts as
teaching material and found them very useful.  I found a few editorial
glitches, which I have to go back to and collate.  I know Last Call is
ending today, so I thought I'd get this word in.  The editorial fixes will
be sent to the authors over the weekend.

Tom Taylor
taylor@nortelnetworks.com
Ph. +1 613 736 0961 (ESN 396 1490)
 

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



From daemon@ns.ietf.org  Fri Apr 19 18:56:48 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15227
	for <sipping-archive@odin.ietf.org>; Fri, 19 Apr 2002 18:56:47 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA15452
	for sipping-archive@odin.ietf.org; Fri, 19 Apr 2002 18:56:49 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA14919;
	Fri, 19 Apr 2002 18:39:16 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA14888
	for <sipping@ns.ietf.org>; Fri, 19 Apr 2002 18:39:13 -0400 (EDT)
Received: from pine.neustar.com (pine.neustar.com [209.173.57.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13332
	for <sipping@ietf.org>; Fri, 19 Apr 2002 18:39:08 -0400 (EDT)
Received: from chiimc01.il.neustar.com (chih650b-s3p2.il.neustar.com [209.173.57.65])
	by pine.neustar.com (8.11.0/8.11.0) with ESMTP id g3JMcf707084;
	Fri, 19 Apr 2002 17:38:41 -0500
Received: by chiimc01.il.neustar.com with Internet Mail Service (5.5.2653.19)
	id <JB0ZV9L0>; Fri, 19 Apr 2002 17:38:36 -0500
Message-ID: <70565611B164D511957A001083FCDD5601870237@va02.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'sipping@ietf.org'" <sipping@ietf.org>,
        "'mwatson@nortelnetworks.com'" <mwatson@nortelnetworks.com>
Subject: RE: [Sipping] RE: Network Asserted Identity
Date: Fri, 19 Apr 2002 17:38:29 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E7F2.ED6BA040"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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

Well, in short, you have an admirable model that carves out a good
definition of the space of applicability of the short-term work. It has
actually helped me quite a bit to understand your position to stare at the
model (especially the distinction between NAI1, NAI3 and NAI4), so, thanks.
 
You have convineced me that the Iraqi problem is separable from NAI1, and
that we don't need to solve this problem in the proposed short-term work
provided that the short-term work embraces interpretations (i) and (ii) -
the current applicability statement in sip-privacy-04 is substantially
weaker than those. I think the fact that conformity to (i) and (ii) is not
reflected in the protocol must also become an important caveat to the
short-term work. I also hope that definition of an appropriate Spec(T) is
now a prerequisite for the short-term work? This could actually be
tractable...
 
I do however remain somewhat unconvinced on the separation of NAI1 and NAI2;
though I now understand the formal distinction you're drawing, any
behavioral motivations for the distinction remain unclear to me. If you take
as granted the caveat about privacy in NAI2, how would the behavior differ
for an entity sending an NAI to a trusted versus an untrusted destination?
If the answer is 'not at all', then you'll see why I'm saying you can
extract out the privacy requirement and conflate NAI1 and NAI2. In other
words, privacy creates the need to distinguish between these two. Or is
there some tacit requirement I'm missing that makes the behavior different
in this case? But otherwise I'm not opposed to the spirit of NAI1 and NAI2,
in any event. They seem like a reasonable scope for the short-term work.
 
A few other matters noted below.
 
Jon Peterson
NeuStar, Inc.

-----Original Message-----
From: Mark Watson [mailto:mwatson@nortelnetworks.com]
Sent: Friday, April 19, 2002 10:06 AM
To: 'sipping@ietf.org'; 'Peterson, Jon'
Subject: RE: [Sipping] RE: Network Asserted Identity



[snip]

> NAI3 and NAI4 
> especially seem to make assumptions about how trust operates 
> that are a little silly. For NAI3, why would a SIP 'trusted' 
> domain send something through an untrusted domain to get back 
> to itself, to the same trusted domain? 

Because the Trust Domain is not a fully connected network. There are
elements which are not interconnected by any path through trusted elements,
and so the only way of passing information between them is via untrusted
parts of the network. One solution would be to encrypt the information using
a key known to all elements in the Trust Domain. It also encompasses the
Call Trace solution where the user is given the encrypted NAI and passes it
back to (the owner of) the Trust Domain.

If we don't have this requirement, then we don't need encryption. 
[Peterson, Jon] Well, the idea that a trust domain isn't a 'fully connected
network' is exactly what strikes the Internet-minded as a little odd. I
don't think the need for encryption is predicated on a network that isn't
fully connected. I think that encryption potentially enables the creator of
an NAI to determine who will be able to inspect it, rather than relying on
downstream entities to decide when they should or shouldn't share it with
others. An encrypted NAI that arrives at a UAS that cannot decrypt it meets
privacy requirements, I believe, regardless of call trace. I remain deeply
confused by the purpose of the encryption stuff in sip-privacy-04 (is it
anonymous call-back?). Since you're not considering NAI3 I presume this is
outside the context of the proposed short-term work.

[snip] 

I don't think the assumption you claim is made by the draft. 'Trustedness'
is indeed an 'opinion' that one node has about another, based on
configuration by human beings who know the properties of the devices (i.e.
that they are indeed compliant to the relevant specifications and so can be
trusted to act in a particular way).
[Peterson, Jon] Trustedness in the draft now is currently an opinion about
whom you receive an NAI from, which is oftentimes not the party that created
the NAI. Obviously, everyone should be entitled to their own degree of trust
with respect to the creator of the NAI, and this should have little or
nothing to do with who relays the NAI to you. This whole trusted network
concept forces you to trust everyone in the trust domain equally -
trustedness is an intrinsic, binary quality of elements and identities. I
think this is a fundamental limitation of the short-term work (it's built
into your model definitions), and ultimately your opinion of the value of
the short-term work is probably largely predicated on how damaging you
believe this limitation is.

  


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [Sipping] RE: Network Asserted Identity</TITLE>

<META content="MSHTML 5.00.3315.2870" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=122501721-19042002>Well, 
in short, you have an admirable model that carves out a good definition of the 
space of applicability of the short-term work. It has actually helped me quite a 
bit to understand your position to stare at the model (especially the 
distinction between NAI1, NAI3 and NAI4), so, thanks.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=122501721-19042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=122501721-19042002>You 
have convineced me that the Iraqi problem is separable from NAI1, and that we 
don't need to solve this problem in the proposed short-term work provided that 
the short-term work embraces interpretations (i) and (ii) - the current 
applicability statement in sip-privacy-04 is substantially weaker than those. I 
think the fact that&nbsp;conformity to (i) and (ii) is&nbsp;not reflected in the 
protocol must also become an important caveat to the short-term work. I also 
hope that definition of an appropriate Spec(T) is now a prerequisite for the 
short-term work? This could actually be tractable...</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=122501721-19042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=122501721-19042002>I do 
however remain somewhat unconvinced on the separation of NAI1 and NAI2; though 
I&nbsp;now understand the formal distinction you're drawing, any behavioral 
motivations for the distinction remain unclear to me. If you take as granted the 
caveat about privacy in NAI2, how would the behavior differ&nbsp;for an entity 
sending an NAI to a trusted versus an untrusted destination? If the answer is 
'not at all', then you'll see why I'm saying you can extract out the privacy 
requirement and conflate NAI1 and NAI2. In other words, privacy creates the need 
to distinguish between these two. Or is there some tacit requirement I'm missing 
that makes the behavior different in this case? But otherwise I'm not opposed to 
the spirit of NAI1 and NAI2, in any event. They seem like a reasonable scope for 
the short-term work.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=122501721-19042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=122501721-19042002>A few 
other matters noted below.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=122501721-19042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=122501721-19042002>Jon 
Peterson</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=122501721-19042002>NeuStar, Inc.</SPAN></FONT></DIV>
<BLOCKQUOTE 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma><FONT 
  size=2>-----Original Message-----<BR><B>From:</B> Mark Watson 
  [mailto:mwatson@nortelnetworks.com]<BR><B>Sent:</B> Friday, April 19, 2002 
  10:06 AM<BR><B>To:</B> 'sipping@ietf.org'; 'Peterson, Jon'<BR><B>Subject:</B> 
  RE: [Sipping] RE: Network Asserted Identity<BR><BR></FONT></DIV></FONT>
  <P><FONT color=#0000ff face=Arial size=2><SPAN 
  class=122501721-19042002>[snip]</SPAN></FONT></P>
  <P><FONT size=2>&gt; NAI3 and NAI4 </FONT><BR><FONT size=2>&gt; especially 
  seem to make assumptions about how trust operates </FONT><BR><FONT size=2>&gt; 
  that are a little silly. For NAI3, why would a SIP 'trusted' </FONT><BR><FONT 
  size=2>&gt; domain send something through an untrusted domain to get back 
  </FONT><BR><FONT size=2>&gt; to itself, to the same trusted domain? 
</FONT></P>
  <P><FONT size=2>Because the Trust Domain is not a fully connected network. 
  There are elements which are not interconnected by any path through trusted 
  elements, and so the only way of passing information between them is via 
  untrusted parts of the network. One solution would be to encrypt the 
  information using a key known to all elements in the Trust Domain. It also 
  encompasses the Call Trace solution where the user is given the encrypted NAI 
  and passes it back to (the owner of) the Trust Domain.</FONT></P>
  <P><FONT size=2>If we don't have this requirement, then we don't need 
  encryption.</FONT> <BR><FONT color=#0000ff face=Arial size=2><SPAN 
  class=122501721-19042002>[Peterson, Jon]&nbsp;Well, the idea that a trust 
  domain isn't a 'fully connected network' is exactly what strikes the 
  Internet-minded as a little odd. I don't think the need for encryption is 
  predicated on a network that isn't fully connected. I think that encryption 
  potentially enables the creator of an NAI to determine who will be able to 
  inspect it, rather than relying on downstream entities to decide when they 
  should or shouldn't share it with others. An encrypted NAI that arrives at a 
  UAS that cannot decrypt it meets privacy requirements, I believe, regardless 
  of call trace. I remain deeply confused by the purpose of the encryption stuff 
  in sip-privacy-04 (is it anonymous call-back?). Since you're not considering 
  NAI3 I presume this is outside the context of the proposed short-term 
  work.</SPAN></FONT></P>
  <P><FONT color=#0000ff face=Arial size=2><SPAN 
  class=122501721-19042002>[snip]&nbsp;</SPAN></FONT></P>
  <P><FONT size=2>I don't think the assumption you claim is made by the draft. 
  'Trustedness' is indeed an 'opinion' that one node has about another, based on 
  configuration by human beings who know the properties of the devices (i.e. 
  that they are indeed compliant to the relevant specifications and so can be 
  trusted to act in a particular way).<BR><FONT color=#0000ff face=Arial><SPAN 
  class=122501721-19042002>[Peterson, Jon]&nbsp;Trustedness in the draft now is 
  currently&nbsp;an opinion about whom you receive an NAI from, which is 
  oftentimes not the party that created the NAI.&nbsp;Obviously, everyone should 
  be entitled to their own degree of trust with respect to the creator of the 
  NAI, and this should have little or nothing to do with who relays the NAI to 
  you. This whole trusted network concept forces you to trust everyone in the 
  trust domain equally - trustedness is an intrinsic, binary quality of elements 
  and identities. I think this is a fundamental limitation of the short-term 
  work (it's built into your model definitions), and ultimately your opinion of 
  the value of the short-term work is probably largely predicated on how 
  damaging you believe this limitation is.</SPAN></FONT></FONT></P>
  <P><FONT size=2>&nbsp;</FONT> </P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1E7F2.ED6BA040--

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



From daemon@optimus.ietf.org  Sat Apr 20 05:44:18 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00094
	for <sipping-archive@odin.ietf.org>; Sat, 20 Apr 2002 05:44:18 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA20674
	for sipping-archive@odin.ietf.org; Sat, 20 Apr 2002 05:44:21 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA18874;
	Sat, 20 Apr 2002 05:13:11 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA18842
	for <sipping@optimus.ietf.org>; Sat, 20 Apr 2002 05:13:07 -0400 (EDT)
Received: from smtp3.arnet.com.ar (smtp3.arnet.com.ar [200.45.191.14])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA29864
	for <sipping@ietf.org>; Sat, 20 Apr 2002 05:13:03 -0400 (EDT)
Received: (qmail 26722 invoked from network); 20 Apr 2002 09:12:22 -0000
Received: from unknown (HELO mail2.arnet.com.ar) (200.45.0.5)
  by smtp3.arnet.com.ar with SMTP; 20 Apr 2002 09:12:22 -0000
Received: from mail pickup service by mail2.arnet.com.ar with Microsoft SMTPSVC;
	 Sat, 20 Apr 2002 06:10:02 -0300
Received: from mx2.arnet.com.ar ([200.45.0.3]) by mail2.arnet.com.ar  with Microsoft SMTPSVC(5.5.1877.677.67);
	 Thu, 18 Apr 2002 11:29:09 -0300
Received: from loki.ietf.org ([132.151.1.177]) by mx2.arnet.com.ar  with Microsoft SMTPSVC(5.5.1877.357.35);
	 Thu, 18 Apr 2002 11:28:30 -0300
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id KAA20446
	for ietf-123-outbound.01@ietf.org; Thu, 18 Apr 2002 10:25:00 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id IAA19178
	for <all-ietf@loki.ietf.org>; Thu, 18 Apr 2002 08:01:04 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02059;
	Thu, 18 Apr 2002 08:01:00 -0400 (EDT)
Message-Id: <200204181201.IAA02059@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Thu, 18 Apr 2002 08:01:00 -0400
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-deaf-req-01.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

--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		: User Requirements for SIP in support of deaf, hard of 
                          hearing and speech-impaired individuals
	Author(s)	: N. Charlton et al.
	Filename	: draft-ietf-sipping-deaf-req-01.txt
	Pages		: 13
	Date		: 17-Apr-02
	
This document aims to present a set of SIP user requirements that
support communications for deaf, hard of hearing and speech-impaired
individuals. These user requirements address the current difficulties
of deaf, hard of hearing and speech-impaired individuals in using
communications facilities, while acknowledging the multi-functional
potential of SIP-based communications.
A number of issues related to these user requirements are further
raised in this document.
Also included are some real world scenarios and some technical
requirements to show the robustness of these requirements on a
concept-level.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-deaf-req-01.txt

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-sipping-deaf-req-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-deaf-req-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:	<20020417151748.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-deaf-req-01.txt

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

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

--OtherAccess--

--NextPart--


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



From daemon@optimus.ietf.org  Sun Apr 21 10:53:07 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26240
	for <sipping-archive@odin.ietf.org>; Sun, 21 Apr 2002 10:53:07 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA01824
	for sipping-archive@odin.ietf.org; Sun, 21 Apr 2002 10:53:08 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA00794;
	Sun, 21 Apr 2002 10:23:34 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA00762
	for <sipping@optimus.ietf.org>; Sun, 21 Apr 2002 10:23:31 -0400 (EDT)
Received: from public.szptt.net.cn (mail2-smtp.szptt.net.cn [202.96.136.222])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA25706
	for <sipping@ietf.org>; Sun, 21 Apr 2002 10:23:28 -0400 (EDT)
Received: from public.szptt.net.cn([202.96.136.222]) by public.szptt.net.cn(JetMail 2.5.3.0)
	with SMTP id jm103cc2dc05; Sun, 21 Apr 2002 14:23:10 -0000
Received: from loki.ietf.org([132.151.1.177]) by public.szptt.net.cn(JetMail 2.5.3.0)
	with SMTP id jm213cc06c97; Fri, 19 Apr 2002 14:02:27 -0000
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id IAA26093
	for ietf-123-outbound.01@ietf.org; Fri, 19 Apr 2002 08:05:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id HAA25695
	for <all-ietf@loki.ietf.org>; Fri, 19 Apr 2002 07:22:35 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15918;
	Fri, 19 Apr 2002 07:22:34 -0400 (EDT)
Message-Id: <200204191122.HAA15918@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 19 Apr 2002 07:22:34 -0400
Subject: [Sipping] I-D ACTION:draft-watson-sipping-req-history-01.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

--NextPart

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


	Title		: Generic Request History Capability - Requirements
	Author(s)	: M. Watson, M. Barnes, C. Jennings, J. Peterson
	Filename	: draft-watson-sipping-req-history-01.txt
	Pages		: 10
	Date		: 18-Apr-02
	
Many services that SIP is anticipated to support require the 
ability to determine why and how the call arrived at a specific 
application.  Examples of such services include (but are not 
limited to) sessions initiated to call centers via 'click to talk' 
SIP URLs on a web page, 'call history/logging' style services 
within intelligent 'call management' software for SIP UAs and calls 
to voicemail servers and call centers.  While SIP implicitly 
provides the redirect/retarget capabilities that enable calls to be 
routed to chosen applications, there is currently no standard 
mechanism within SIP for communicating the history of such a 
request. This 'request history' information allows the receiving 
application to determine hints about how and why the call arrived 
at the application/user.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-watson-sipping-req-history-01.txt

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-watson-sipping-req-history-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-watson-sipping-req-history-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:	<20020418140916.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-watson-sipping-req-history-01.txt

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

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

--OtherAccess--

--NextPart--



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



From daemon@ns.ietf.org  Mon Apr 22 09:02:24 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24256
	for <sipping-archive@odin.ietf.org>; Mon, 22 Apr 2002 09:02:24 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA12891
	for sipping-archive@odin.ietf.org; Mon, 22 Apr 2002 09:02:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA11726;
	Mon, 22 Apr 2002 08:38:30 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA11696
	for <sipping@ns.ietf.org>; Mon, 22 Apr 2002 08:38:26 -0400 (EDT)
Received: from zctfs063.europe.nortel.com (zctfs063.nortelnetworks.com [47.164.128.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23783
	for <sipping@ietf.org>; Mon, 22 Apr 2002 08:38:18 -0400 (EDT)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by zctfs063.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3MCbWx05721;
	Mon, 22 Apr 2002 14:37:33 +0200 (MEST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JDW4RM8K>; Mon, 22 Apr 2002 13:37:45 +0100
Message-ID: <A3C2399B2FACD411A54200508BE39C740703DE13@zwcwd00r.europe.nortel.com>
From: "Mark Watson"<mwatson@nortelnetworks.com>
To: "Peterson, Jon" <jon.peterson@neustar.biz>,
        "'sipping@ietf.org'"
	 <sipping@ietf.org>
Subject: RE: [Sipping] RE: Network Asserted Identity
Date: Mon, 22 Apr 2002 13:37:38 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1E9FA.7ABC5224"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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

Jon,
 
Distinction between NAI1 and NAI2 - I agree that in practice it is hard to
see why a single coding solution would not suffice for these two. So it is
debatable whether they need to be separated.
 
However, in terms of the Trust Domain model, they *are*different things -
passing an identity to another entity within the Trust Domain is a different
thing from passing it outside. The specification we develop as part of this
will specify procedures for passing the information to trusted and untusted
entities. Since we know that trusted entities DO follow these procedures
(part of the definition of Trust Domain) we COULD define something which
would meet NAI1 but not NA2 (because we would not define the procedures for
the NAI2 part).
 
I have stated the requirements independent of privacy - the requirement is
for the 'ability' to pass NAI about. I have not stated any requirements
about when this capability would be used, which would obviously depend on
where the information was going and its privacy status.
 
Further comments below.
 
...Mark
 

 <snip>
 Because the Trust Domain is not a fully connected network. There are
elements which are not interconnected by any path through trusted elements,
and so the only way of passing information between them is via untrusted
parts of the network. One solution would be to encrypt the information using
a key known to all elements in the Trust Domain. It also encompasses the
Call Trace solution where the user is given the encrypted NAI and passes it
back to (the owner of) the Trust Domain.

If we don't have this requirement, then we don't need encryption. 
[Peterson, Jon] Well, the idea that a trust domain isn't a 'fully connected
network' is exactly what strikes the Internet-minded as a little odd. I
don't think the need for encryption is predicated on a network that isn't
fully connected. I think that encryption potentially enables the creator of
an NAI to determine who will be able to inspect it, rather than relying on
downstream entities to decide when they should or shouldn't share it with
others. An encrypted NAI that arrives at a UAS that cannot decrypt it meets
privacy requirements, I believe, regardless of call trace. I remain deeply
confused by the purpose of the encryption stuff in sip-privacy-04 (is it
anonymous call-back?). Since you're not considering NAI3 I presume this is
outside the context of the proposed short-term work.

MW> The network is fully connected from a *connectivity* point of view, but
the network of 'Trusted' nodes with secure connections between them, which
is a kind of overlay, may not be connected. As soon as we leave the very
simple 'trusted nodes with secure connections' system, then we need
cryptography. 

I don't think the assumption you claim is made by the draft. 'Trustedness'
is indeed an 'opinion' that one node has about another, based on
configuration by human beings who know the properties of the devices (i.e.
that they are indeed compliant to the relevant specifications and so can be
trusted to act in a particular way).
[Peterson, Jon] Trustedness in the draft now is currently an opinion about
whom you receive an NAI from, which is oftentimes not the party that created
the NAI. Obviously, everyone should be entitled to their own degree of trust
with respect to the creator of the NAI, and this should have little or
nothing to do with who relays the NAI to you. This whole trusted network
concept forces you to trust everyone in the trust domain equally -
trustedness is an intrinsic, binary quality of elements and identities. I
think this is a fundamental limitation of the short-term work (it's built
into your model definitions), and ultimately your opinion of the value of
the short-term work is probably largely predicated on how damaging you
believe this limitation is. 

MW> OK, I see your point. Yes, the Trust Domain concept relies on transitive
trust - within the scope of the NAI mechanism anything received from an
element that you know to be a member of the Trust Domain gets trusted, full
stop. i.e. there is no sense that information you receive has variable of
'trust status' depending (e.g.) on who *originally* generated it. It is part
of the procedures of a Trusted Element that it does not pass on to another
Trusted Element information which it doesn't trust (unless marked as such).

I now think that to meet NAI4 you would need some kind of indication of
*which* trust domain you received the identity from, rather than just the
'screen=yes' which only indicated that the information was from *some* Trust
Domain.

But now this is getting closer to your more general mechanism, which
indicates exactly which 'authentication service' generated the information
and works without the Trust Domain model.

...Mark

  


------_=_NextPart_001_01C1E9FA.7ABC5224
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [Sipping] RE: Network Asserted Identity</TITLE>

<META content="MSHTML 5.00.3315.2870" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=740320608-22042002>Jon,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=740320608-22042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=740320608-22042002>Distinction between NAI1 and NAI2 - I agree that in 
practice it is hard to see why a single coding solution would not suffice for 
these two. So it is debatable whether they need to be 
separated.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=740320608-22042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=740320608-22042002>However, in terms of the Trust Domain model, they 
*are*different things - passing an identity to another entity within the Trust 
Domain is a different thing from passing it outside. The specification we 
develop as part of this will specify procedures for passing the information to 
trusted and untusted entities. Since we know that trusted entities DO follow 
these procedures (part of the definition of Trust Domain) we COULD define 
something which would meet NAI1 but not NA2 (because we would not define the 
procedures for the NAI2 part).</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=740320608-22042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN class=740320608-22042002>I 
have stated the requirements independent of privacy - the requirement is for the 
'ability' to pass NAI about. I have not stated any requirements about when this 
capability would be used, which would obviously depend on where the information 
was going and its privacy status.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=740320608-22042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=740320608-22042002>Further comments below.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=740320608-22042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=740320608-22042002>...Mark</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=740320608-22042002></SPAN></FONT>&nbsp;</DIV>
<BLOCKQUOTE 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT color=#0000ff 
  face=Verdana size=1><SPAN 
  class=740320608-22042002>&nbsp;&lt;snip&gt;</SPAN></FONT></DIV>
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT color=#0000ff 
  face=Verdana size=1><SPAN class=740320608-22042002>&nbsp;</SPAN></FONT><FONT 
  size=2>Because the Trust Domain is not a fully connected network. There are 
  elements which are not interconnected by any path through trusted elements, 
  and so the only way of passing information between them is via untrusted parts 
  of the network. One solution would be to encrypt the information using a key 
  known to all elements in the Trust Domain. It also encompasses the Call Trace 
  solution where the user is given the encrypted NAI and passes it back to (the 
  owner of) the Trust Domain.</FONT></DIV>
  <BLOCKQUOTE 
  style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
    <P><FONT size=2>If we don't have this requirement, then we don't need 
    encryption.</FONT> <BR><FONT color=#0000ff face=Arial size=2><SPAN 
    class=122501721-19042002>[Peterson, Jon]&nbsp;Well, the idea that a trust 
    domain isn't a 'fully connected network' is exactly what strikes the 
    Internet-minded as a little odd. I don't think the need for encryption is 
    predicated on a network that isn't fully connected. I think that encryption 
    potentially enables the creator of an NAI to determine who will be able to 
    inspect it, rather than relying on downstream entities to decide when they 
    should or shouldn't share it with others. An encrypted NAI that arrives at a 
    UAS that cannot decrypt it meets privacy requirements, I believe, regardless 
    of call trace. I remain deeply confused by the purpose of the encryption 
    stuff in sip-privacy-04 (is it anonymous call-back?). Since you're not 
    considering NAI3 I presume this is outside the context of the proposed 
    short-term work.</SPAN></FONT></P></BLOCKQUOTE></BLOCKQUOTE>
<P><FONT color=#0000ff face=Arial size=2><SPAN class=740320608-22042002>MW&gt; 
The network is fully connected from a *connectivity* point of view, but the 
network of 'Trusted' nodes with secure connections between them, which is a kind 
of overlay, may not be connected. As soon as we leave the very simple 'trusted 
nodes with secure connections' system, then we need cryptography. 
</SPAN></FONT></P>
<BLOCKQUOTE 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <BLOCKQUOTE 
  style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
    <P><FONT size=2>I don't think the assumption you claim is made by the draft. 
    'Trustedness' is indeed an 'opinion' that one node has about another, based 
    on configuration by human beings who know the properties of the devices 
    (i.e. that they are indeed compliant to the relevant specifications and so 
    can be trusted to act in a particular way).<BR><FONT color=#0000ff><FONT 
    face=Arial><SPAN class=122501721-19042002>[Peterson, Jon]&nbsp;Trustedness 
    in the draft now is currently&nbsp;an opinion about whom you receive an NAI 
    from, which is oftentimes not the party that created the 
    NAI.&nbsp;Obviously, everyone should be entitled to their own degree of 
    trust with respect to the creator of the NAI, and this should have little or 
    nothing to do with who relays the NAI to you. This whole trusted network 
    concept forces you to trust everyone in the trust domain equally - 
    trustedness is an intrinsic, binary quality of elements and identities. I 
    think this is a fundamental limitation of the short-term work (it's built 
    into your model definitions), and ultimately your opinion of the value of 
    the short-term work is probably largely predicated on how damaging you 
    believe this limitation is.<FONT face=Verdana size=1><SPAN 
    class=740320608-22042002>&nbsp;</SPAN></FONT></SPAN></FONT></FONT></FONT></P></BLOCKQUOTE></BLOCKQUOTE>
<P><FONT size=2><FONT color=#0000ff><FONT face=Arial><SPAN 
class=122501721-19042002><FONT face=Verdana size=1><SPAN 
class=740320608-22042002>MW&gt; OK, I see your point. Yes, the Trust Domain 
concept relies on&nbsp;transitive trust - within the scope of the NAI mechanism 
anything received from an element that you know to be a member of the Trust 
Domain gets trusted, full stop. i.e. there is no sense that information you 
receive has variable of 'trust status' depending (e.g.) on who *originally* 
generated it. It is part of the procedures of a Trusted Element that it does not 
pass on to another Trusted Element information which it doesn't trust (unless 
marked as such).</SPAN></FONT></SPAN></FONT></FONT></FONT></P>
<P><FONT size=2><FONT color=#0000ff><FONT face=Arial><SPAN 
class=122501721-19042002><FONT face=Verdana size=1><SPAN 
class=740320608-22042002>I now think that to meet NAI4 you would need some kind 
of indication of *which* trust domain you received the identity from, rather 
than just the 'screen=yes' which only indicated that the information was from 
*some* Trust Domain.</SPAN></FONT></SPAN></FONT></FONT></FONT></P>
<P><FONT color=#0000ff face=Verdana size=1><SPAN class=740320608-22042002>But 
now this is getting closer to your more general mechanism, which indicates 
exactly which 'authentication service' generated the information and works 
without the Trust Domain model.</SPAN></FONT></P>
<P><FONT color=#0000ff face=Verdana size=1><SPAN 
class=740320608-22042002>...Mark</SPAN></FONT></P>
<BLOCKQUOTE 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <BLOCKQUOTE 
  style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
    <P><FONT size=2>&nbsp;</FONT> </P></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1E9FA.7ABC5224--

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



From daemon@ns.ietf.org  Mon Apr 22 16:31:33 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11982
	for <sipping-archive@odin.ietf.org>; Mon, 22 Apr 2002 16:31:33 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA18050
	for sipping-archive@odin.ietf.org; Mon, 22 Apr 2002 16:31:37 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA16525;
	Mon, 22 Apr 2002 16:14:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA16493
	for <sipping@ns.ietf.org>; Mon, 22 Apr 2002 16:14:28 -0400 (EDT)
Received: from imo-m10.mx.aol.com (imo-m10.mx.aol.com [64.12.136.165])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11362
	for <sipping@ietf.org>; Mon, 22 Apr 2002 16:14:24 -0400 (EDT)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-m10.mx.aol.com (mail_out_v32.5.) id l.1a1.11e3452 (4561)
	 for <sipping@ietf.org>; Mon, 22 Apr 2002 16:13:53 -0400 (EDT)
Message-ID: <1a1.11e3452.29f5c901@aol.com>
Date: Mon, 22 Apr 2002 16:13:53 EDT
To: sipping@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_1a1.11e3452.29f5c901_boundary"
X-Mailer: AOL 6.0 for Windows US sub 10524
Subject: [Sipping] Three Assured Service Drafts
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


--part1_1a1.11e3452.29f5c901_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

I have uploaded 3 IDs on the subject of Assured Service:

draft-pierce-sipping-assured-service-02 is a further revision of the previous 
draft to define the requirements. Informative material has been moved to the 
following two drafts.

draft-pierce-sipping-assured-service-arch-00 defines the architecture which 
is assumed to be necessary to meet the requirements for Assured Service. It 
describes the use of a trusted proxy to handle origination and termination of 
Assured Service calls.

draft-pierce-sipping-pref-treat-examples-00 describes ways in which 
preferential treatment can be provided to high priority calls. It focuses on 
meeting the requirements for "Assured Service" as defined in the above 
requirements, but the procedures described may also be used in other cases 
such as the "Emergency Preparedness" services.

Mike Pierce
Artel


--part1_1a1.11e3452.29f5c901_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>I have uploaded 3 IDs on the subject of Assured Service:
<BR>
<BR>draft-pierce-sipping-assured-service-02 is a further revision of the previous draft to define the requirements. Informative material has been moved to the following two drafts.
<BR>
<BR>draft-pierce-sipping-assured-service-arch-00 defines the architecture which is assumed to be necessary to meet the requirements for Assured Service. It describes the use of a trusted proxy to handle origination and termination of Assured Service calls.
<BR>
<BR>draft-pierce-sipping-pref-treat-examples-00 describes ways in which preferential treatment can be provided to high priority calls. It focuses on meeting the requirements for "Assured Service" as defined in the above requirements, but the procedures described may also be used in other cases such as the "Emergency Preparedness" services.
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_1a1.11e3452.29f5c901_boundary--

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



From daemon@ns.ietf.org  Mon Apr 22 16:38:17 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12108
	for <sipping-archive@odin.ietf.org>; Mon, 22 Apr 2002 16:38:17 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA18471
	for sipping-archive@odin.ietf.org; Mon, 22 Apr 2002 16:38:21 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAB17276;
	Mon, 22 Apr 2002 16:24:18 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA09857
	for <sipping@ns.ietf.org>; Mon, 22 Apr 2002 14:52:41 -0400 (EDT)
Received: from exmail.lboard.com ([204.17.219.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08328
	for <sipping@ietf.org>; Mon, 22 Apr 2002 14:52:35 -0400 (EDT)
Received: by exmail.lboard.com with Internet Mail Service (5.5.2653.19)
	id <2ZSHPP4Z>; Mon, 22 Apr 2002 11:50:14 -0700
Message-ID: <CB1C47E7B148D511A2330008C786AAA749BF2F@exmail.lboard.com>
From: Subir Saha <ssaha@longboard.com>
To: "'sipping@ietf.org'" <sipping@ietf.org>
Date: Mon, 22 Apr 2002 11:50:12 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sipping] what differentiate a Private caller or call?
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Lets look at he following example:

A calls B. B does not accept private calls [private in the sense of PSTN of
today]. How does B decide the call from A is private or not? 
Assuming that A put garbage in 'Display Name' and 'From' field, how B can
make such decision? From A's perspective, his privacy is achieved.


Subir Saha (Ph.D.)
Sr. Product Architect
LongBoard Inc.
www.longboard.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 daemon@ns.ietf.org  Mon Apr 22 20:10:57 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18874
	for <sipping-archive@odin.ietf.org>; Mon, 22 Apr 2002 20:10:57 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA02797
	for sipping-archive@odin.ietf.org; Mon, 22 Apr 2002 20:11:00 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA02045;
	Mon, 22 Apr 2002 20:00:56 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA01998
	for <sipping@ns.ietf.org>; Mon, 22 Apr 2002 20:00:52 -0400 (EDT)
Received: from dns2.ulticomdal.com (IDENT:root@dns2.ulticomdal.com [204.130.158.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18659
	for <sipping@ietf.org>; Mon, 22 Apr 2002 20:00:47 -0400 (EDT)
Received: from pcsun63 (pc-sun63.ulticomdal.com [204.130.158.238])
	by dns2.ulticomdal.com (8.9.3/8.9.3) with SMTP id TAA06173
	for <sipping@ietf.org>; Mon, 22 Apr 2002 19:00:44 -0500
From: "Hussam Jarada" <hussam.jarada@ulticomdal.com>
To: <sipping@ietf.org>
Date: Mon, 22 Apr 2002 19:00:43 -0500
Message-ID: <002a01c1ea59$ea356000$ee9e82cc@ulticomdal.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <200204191122.HAA15918@ietf.org>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [Sipping] draft-ietf-sipping-call-flows-00.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

In draft-ietf-sipping-call-flows-00.txt, there's many sections like section
2.1.1 and section 2.1.2 were the To header field is missing tag parameter,
is this a miss typed error ?, I thought per bis-0.9 SIP spec that the tag
parameter must be added to final responses as well provisional responses
except 100 (which may).

Hussam Jarada
Ulticom Inc.





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



From daemon@optimus.ietf.org  Tue Apr 23 03:33:00 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA08430
	for <sipping-archive@odin.ietf.org>; Tue, 23 Apr 2002 03:33:00 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA05794
	for sipping-archive@odin.ietf.org; Tue, 23 Apr 2002 03:33:02 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA04516;
	Tue, 23 Apr 2002 03:16:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA04486
	for <sipping@optimus.ietf.org>; Tue, 23 Apr 2002 03:16:34 -0400 (EDT)
Received: from oak.neustar.com (oak.neustar.com [209.173.53.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA08238
	for <sipping@ietf.org>; Tue, 23 Apr 2002 03:16:31 -0400 (EDT)
Received: from chiimc01.il.neustar.com (stih650b-s1p2.va.neustar.com [209.173.53.65])
	by oak.neustar.com (8.11.0/8.11.0) with ESMTP id g3N7G1H24680;
	Tue, 23 Apr 2002 03:16:01 -0400
Received: by chiimc01.il.neustar.com with Internet Mail Service (5.5.2653.19)
	id <J25ZMCL8>; Tue, 23 Apr 2002 02:15:56 -0500
Message-ID: <70565611B164D511957A001083FCDD5601870251@va02.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Vijay K. Gurbani'" <vkg@lucent.com>, SIPPING LIST <sipping@ietf.org>
Date: Tue, 23 Apr 2002 02:15:50 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sipping] RE: [Sip] SIP support for IN services
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Trimming the distribution back to the SIPPING list.

I have one comment off the bat - have you compared this work at all to the
following draft:

http://www.ietf.org/internet-drafts/draft-ietf-sipping-isup-01.txt

As you may know, this draft is a SIPPING WG last item, and it is currently
past WGLC. It contains, among other things, a SIP response code to Q.850
cause code mapping similar to the one in Appendix A of your document.
However, there are some discrepancies between the mappings suggested by the
two documents (it looks like yours may have been influenced by an earlier
version of sipping-isup?). The mappings in the SIPPING-ISUP draft have been
subjected to a reasonable amount of public scrutiny over the last two years
or so, and I feel they tell a reasonably good story at this point. Some of
the mappings in your draft look a little misplaced to me - to pick an
example at random, '403 Forbidden' mapping to '1 Unallocated number'.

I would actually suggest that your SIN draft should refer normatively to
SIPPING-ISUP for this mapping and any other SIP-to-ISUP needs.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Vijay K. Gurbani [mailto:vkg@lucent.com]
> Sent: Friday, April 19, 2002 8:24 AM
> To: SIP LIST; SIPPING LIST; SPIRITS list; pint@lists.bell-labs.com
> Subject: [Sip] SIP support for IN services
> 
> 
> Folks:
> 
> Enclosed is an I-D for review that describes SIP support for IN
> services.  The I-D represents agreement of the IETF SIN 
> (SIP/IN) design
> team and is intended for publication as an informational RFC.  It has
> been through Last Call in the IETF SIN DT and the comments of the WGs
> identified in the To list of this email are now being solicited.
> 
> http://search.ietf.org/internet-drafts/draft-gurbani-sin-00.txt
> 
> Thanks,
> 
> - vijay
> -- 
> Vijay K. Gurbani  vkg@{lucent.com,research.bell-labs.com,acm.org}
> Wireless Networks Group/Internet Software and eServices
> Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440
> Naperville, Illinois 60566     Voice: +1 630 224 0216
> 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 

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



From daemon@optimus.ietf.org  Tue Apr 23 06:08:37 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10355
	for <sipping-archive@odin.ietf.org>; Tue, 23 Apr 2002 06:08:37 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA13618
	for sipping-archive@odin.ietf.org; Tue, 23 Apr 2002 06:08:41 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA12551;
	Tue, 23 Apr 2002 05:50:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA12520
	for <sipping@optimus.ietf.org>; Tue, 23 Apr 2002 05:50:01 -0400 (EDT)
Received: from btclick.com (mta03.btfusion.com [62.172.195.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10153
	for <sipping@ietf.org>; Tue, 23 Apr 2002 05:49:56 -0400 (EDT)
Received: from ictgateway.ictrnid.org.uk ([217.34.231.189]) by
          btclick.com (Netscape Messaging Server 4.15) with SMTP id
          GV0LYI03.MXJ for <sipping@ietf.org>; Tue, 23 Apr 2002 10:49:30 +0100 
Received: from 192.168.1.35 ([192.168.1.35]) by ictgateway.ictrnid.org.uk (WinRoute Pro 4.1.29) with SMTP; Tue, 23 Apr 2002 11:00:23 +0100
Message-ID: <001e01c1eaac$574e0550$2301a8c0@LTGUIDO>
From: "Guido Gybels" <guido.gybels@rnid.org.uk>
To: <sipping@ietf.org>
Date: Tue, 23 Apr 2002 10:50:46 +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 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 7bit
Subject: [Sipping] draft-ietf-sipping-deaf-req-02.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Hi all,

The draft on "User requirements for the Session Initiation Protocol (SIP) in
support of deaf, hard of hearing and speech-impaired individuals" has been
updated into draft-ietf-sipping-deaf-req-02.txt and submitted to IETF as
well as to the chair of the SIPPING WG. In the mean time, you can find the
new draft on the Design Team Home Page at www.ictrnid.org.uk/sipping/
The Activities page on the Design Team's homepage describes the changes to
this draft. Please also have a look at the open issues.
The Design Team looks, as usual, forward to your comments.

Guido

Guido Gybels, Head of ICT
guido.gybels@rnid.org.uk
Tel. 020-7294 3713
--
The Royal National Institute for Deaf People
Technology Directorate
19-23 Featherstone Street
London EC1Y 8SL - UK





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



From daemon@ns.ietf.org  Tue Apr 23 16:37:59 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06059
	for <sipping-archive@odin.ietf.org>; Tue, 23 Apr 2002 16:37:58 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA28283
	for sipping-archive@odin.ietf.org; Tue, 23 Apr 2002 16:38:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA26072;
	Tue, 23 Apr 2002 16:00:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA26032
	for <sipping@ns.ietf.org>; Tue, 23 Apr 2002 16:00:11 -0400 (EDT)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04897
	for <sipping@ietf.org>; Tue, 23 Apr 2002 16:00:06 -0400 (EDT)
Received: from mira-sjc5-9.cisco.com (IDENT:mirapoint@mira-sjc5-9.cisco.com [171.71.163.32])
	by sj-msg-core-2.cisco.com (8.12.2/8.12.2) with ESMTP id g3NJxdkL009556;
	Tue, 23 Apr 2002 12:59:39 -0700 (PDT)
Received: from OranLT ([161.44.238.37])
	by mira-sjc5-9.cisco.com (Mirapoint)
	with ESMTP id ACS08662;
	Tue, 23 Apr 2002 12:59:49 -0700 (PDT)
From: "David R. Oran" <oran@cisco.com>
To: "'William Marshall'" <wtm@research.att.com>, <Brian.Rosen@marconi.com>
Cc: <sipping@ietf.org>
Subject: RE: [Sipping] RE: Network Asserted Identity
Date: Tue, 23 Apr 2002 15:58:37 -0400
Organization: Cisco Systems
Message-ID: <021701c1eb01$429f37f0$25ee2ca1@OranLT>
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.3416
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <200204191828.OAA11550@fish.research.att.com>
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Small quibble with Bill's assertion - not trying to de-rail the
discussion.

> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] 
> On Behalf Of William Marshall
> Sent: Friday, April 19, 2002 2:28 PM
> To: Brian.Rosen@marconi.com
> Cc: sipping@ietf.org
> Subject: Re: [Sipping] RE: Network Asserted Identity
>
[snip] 
> 
> Leaving the philosophy, and on a more practical level, the 
> whole reason caller-id is a useful service is that it is NOT 
> user-provided.
>
I disagree. The reason network-asserted caller-id it is/was useful on
the PSTN was because the PSTN did not have end-to-end authentication. In
all cases the callee wants to see an identity for the caller which is
vouched for by someone he trusts. In the IP world, that *could* be the
calling user's service provider, but it could just as easily be any
trusted third party.

I see no practical difference from a *caller id* perspective between an
NAI and a certificate signed by this third party saying that the From
field represents a user is who he claims to be. This can be challenged
end-to-end at the callee's discretion.

From my perspective, the *ONLY* reason the information has to originate
with the service provider rather than the user is to enable call trace,
which is something the calling user would rather NOT have happen. All
the other machinations with privacy and protecting the NAI derive from
the call trace requirement and the tricky need to do call trace while
preserving privacy.

I must be missing something basic here, given how tortuous this thread
has been and continues to be.


> Bill Marshall
> wtm@research.att.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 daemon@ns.ietf.org  Tue Apr 23 17:26:16 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06062
	for <sipping-archive@odin.ietf.org>; Tue, 23 Apr 2002 16:37:59 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA28282
	for sipping-archive@odin.ietf.org; Tue, 23 Apr 2002 16:38:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA25805;
	Tue, 23 Apr 2002 15:58:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA25757
	for <sipping@ns.ietf.org>; Tue, 23 Apr 2002 15:58:17 -0400 (EDT)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04764
	for <sipping@ietf.org>; Tue, 23 Apr 2002 15:58:13 -0400 (EDT)
Received: from orion.cs.columbia.edu (orion.cs.columbia.edu [128.59.16.21])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id PAA25357
	for <sipping@ietf.org>; Tue, 23 Apr 2002 15:58:16 -0400 (EDT)
Received: from ind.cs.columbia.edu (ind.cs.columbia.edu [128.59.19.27])
	by orion.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g3NJwFT5003265
	for <sipping@ietf.org>; Tue, 23 Apr 2002 15:58:15 -0400 (EDT)
Date: Tue, 23 Apr 2002 15:58:15 -0400 (EDT)
From: Xiaotao Wu <xiaotaow@cs.columbia.edu>
To: <sipping@ietf.org>
Message-ID: <Pine.SOL.4.33.0204231544290.4998-100000@ind.cs.columbia.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Sipping] draft-wu-sipping-floor-control-01.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Hi all,

The draft on "Use of SIP and SOAP for Conference Floor Control"
has been updated into draft-wu-sipping-floor-control-01.txt.
In the new draft, the definition of floor control events and commands has
been changed from DTD to XML schema. The naming is changed from
words_lashed_together style to camel-case style.

-Xiaotao

=========================================================
Name  : Xiaotao Wu
Email : xiaotaow@cs.columbia.edu, xw71@columbia.edu
URL   : http://www.cs.columbia.edu/~xiaotaow
Phone : (212)939-7020, (212)939-7133,  Fax: (801)751-0217
SIP   : sip:xiaotaow@conductor.cs.columbia.edu
Office: Room 463, Mudd building, West 120th
=========================================================


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



From daemon@ns.ietf.org  Tue Apr 23 18:01:54 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07830
	for <sipping-archive@odin.ietf.org>; Tue, 23 Apr 2002 18:01:54 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA03286
	for sipping-archive@odin.ietf.org; Tue, 23 Apr 2002 18:01:59 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA02175;
	Tue, 23 Apr 2002 17:39:19 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA02146
	for <sipping@ns.ietf.org>; Tue, 23 Apr 2002 17:39:16 -0400 (EDT)
Received: from auemail2.firewall.lucent.com (auemail2.lucent.com [192.11.223.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07467
	for <sipping@ietf.org>; Tue, 23 Apr 2002 17:39:11 -0400 (EDT)
Received: from ih2mail.ih.lucent.com (h135-1-241-39.lucent.com [135.1.241.39])
	by auemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3NLcZ021948;
	Tue, 23 Apr 2002 17:38:35 -0400 (EDT)
Received: from lucent.com by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id QAA26392; Tue, 23 Apr 2002 16:38:34 -0500 (CDT)
Message-ID: <3CC5D429.4090801@lucent.com>
Date: Tue, 23 Apr 2002 16:37:45 -0500
From: "Vijay K. Gurbani" <vkg@lucent.com>
Organization: Lucent Technologies, Inc./Bell Laboratories
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1
X-Accept-Language: en-us
MIME-Version: 1.0
To: "Peterson, Jon" <jon.peterson@neustar.biz>
CC: SIPPING LIST <sipping@ietf.org>
References: <70565611B164D511957A001083FCDD5601870251@va02.va.neustar.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Re: [Sip] SIP support for IN services
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Peterson, Jon wrote:

> I have one comment off the bat - have you compared this work at all to the
> following draft:
> 
> http://www.ietf.org/internet-drafts/draft-ietf-sipping-isup-01.txt
> 
> As you may know, this draft is a SIPPING WG last item, and it is currently
> past WGLC. It contains, among other things, a SIP response code to Q.850
> cause code mapping similar to the one in Appendix A of your document.
> However, there are some discrepancies between the mappings suggested by the
> two documents.


Jon:

There are 2 tables in Appendix A of my I-D; the second table which
attempts to map ISUP cause values to SIP responses is legacy, carried
over from older versions of the I-D.

You are right in your suggestion that,

> your SIN draft should refer normatively to SIPPING-ISUP for this 

> mapping and any other SIP-to-ISUP needs.


I will add a normative reference in lieu of the second table.


Thanks,


- vijay

-- 
Vijay K. Gurbani  vkg@{lucent.com,research.bell-labs.com,acm.org}
Wireless Networks Group/Internet Software and eServices
Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440
Naperville, Illinois 60566     Voice: +1 630 224 0216


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



From daemon@optimus.ietf.org  Wed Apr 24 07:18:55 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29534
	for <sipping-archive@odin.ietf.org>; Wed, 24 Apr 2002 07:18:54 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA21140
	for sipping-archive@odin.ietf.org; Wed, 24 Apr 2002 07:18:56 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA20240;
	Wed, 24 Apr 2002 07:04:00 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA20209
	for <sipping@optimus.ietf.org>; Wed, 24 Apr 2002 07:03:57 -0400 (EDT)
Received: from mail1.telekom.de (mail1.telekom.de [62.225.183.235])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA29300
	for <sipping@ietf.org>; Wed, 24 Apr 2002 07:03:54 -0400 (EDT)
Received: from g9jbr.mgb01.telekom.de by G8SBV.dmz.telekom.de with ESMTP for sipping@ietf.org; Wed, 24 Apr 2002 13:02:07 +0200
Received: by G9JBR.mgb01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <2Q8XJQ01>; Wed, 24 Apr 2002 13:03:20 +0200
Message-Id: <A89A213731F7D51196A0000347055C83E391DE@G9JNT.mgb01.telekom.de>
From: "Alexeitsev, D" <D.Alexeitsev@telekom.de>
To: sipping@ietf.org
Date: Wed, 24 Apr 2002 13:03:18 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Subject: [Sipping] Internet-Draft on ISUP-SIP
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Good day,

While looking at the official SIPPING working group web page I have found, that under Goals and Milestones is says that ISUP-SIP interworking draft will be considered as Proposed Standard. My question is have there been any interoperability test for the interworking? if yes, could you please point to the results?

Best regards,

Denis Alexeitsev


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



From daemon@optimus.ietf.org  Wed Apr 24 08:18:56 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01141
	for <sipping-archive@odin.ietf.org>; Wed, 24 Apr 2002 08:18:55 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA24976
	for sipping-archive@odin.ietf.org; Wed, 24 Apr 2002 08:18:58 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA24374;
	Wed, 24 Apr 2002 08:04:51 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA24342
	for <sipping@optimus.ietf.org>; Wed, 24 Apr 2002 08:04:48 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00782;
	Wed, 24 Apr 2002 08:04:44 -0400 (EDT)
Message-Id: <200204241204.IAA00782@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Wed, 24 Apr 2002 08:04:44 -0400
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-deaf-req-02.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

--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		: User Requirements for the Session Initiation Protocol 
                          (SIP) in support of deaf, hard of hearing and 
                          speech-impaired individuals
	Author(s)	: N. Charlton et al.
	Filename	: draft-ietf-sipping-deaf-req-02.txt
	Pages		: 13
	Date		: 23-Apr-02
	
This document aims to present a set of SIP user requirements that
support communications for deaf, hard of hearing and speech-impaired
individuals. These user requirements address the current difficulties
of deaf, hard of hearing and speech-impaired individuals in using
communications facilities, while acknowledging the multi-functional
potential of SIP-based communications.
A number of issues related to these user requirements are further
raised in this document.
Also included are some real world scenarios and some technical
requirements to show the robustness of these requirements on a
concept-level.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-deaf-req-02.txt

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-sipping-deaf-req-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-deaf-req-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:	<20020423121433.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-deaf-req-02.txt

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

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

--OtherAccess--

--NextPart--



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



From daemon@optimus.ietf.org  Wed Apr 24 10:59:57 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17477
	for <sipping-archive@odin.ietf.org>; Wed, 24 Apr 2002 10:59:56 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA06412
	for sipping-archive@odin.ietf.org; Wed, 24 Apr 2002 10:59:59 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA05168;
	Wed, 24 Apr 2002 10:47:01 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA05137
	for <sipping@optimus.ietf.org>; Wed, 24 Apr 2002 10:46:57 -0400 (EDT)
Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16912
	for <sipping@ietf.org>; Wed, 24 Apr 2002 10:46:53 -0400 (EDT)
Received: from m2.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX0204-Fujitsu Gateway)
	id XAA03769 for <sipping@ietf.org>; Wed, 24 Apr 2002 23:46:24 +0900 (JST)
	(envelope-from iwayama@flab.fujitsu.co.jp)
Received: from PINK by m2.gw.fujitsu.co.jp (8.9.3/3.7W-0204-Fujitsu Domain Master)
	id XAA07558 for <sipping@ietf.org>; Wed, 24 Apr 2002 23:46:22 +0900 (JST)
	(envelope-from iwayama@flab.fujitsu.co.jp)
Reply-To: <iwayama.noboru@jp.fujitsu.com>
From: <iwayama.noboru@jp.fujitsu.com>
To: <sipping@ietf.org>
Subject: Re: [Sipping] Binding published data to services
Date: Wed, 24 Apr 2002 23:46:20 +0900
Organization: Fujitsu Laboratories
Message-ID: <000001c1eb9e$cd4473a0$0de11dac@PINK>
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.3416
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

All,

There was the discussion on binding published data to services about two
weeks ago.
Even I have read through the discussion and minute in last IETF meeting,
I could not have the big picture as a whole system.
Maybe I misunderstand something important.
I appreciate your kind help.

What I have in mind based on the emails, which Ben Campbell started in
this list, is as follows:

In general, SIP UA has a need to upload some data towards a SIP service
network.
CPI script and presence info are examples of those data.
Before considering a particular mechanism (i.e., protocol) for uploading
the data,
this SIPPING WG decided to investigate the fact that the uploaded data
onto SIP network must be
binded some SIP service element. For example,
in the case of presence, in order for a presentitiy to update presence
info,
the presentitiy uploads his or her updated presence info towards some
URI.
It is needed to ensure that the URI should be right point for the
presentitiy to upload his
updated presence info, otherwise, his presence info could not be handled
nor notified to correct
watchers.
The assumption here is that we do not discuss underlying uploading
mechanism but
we focus only on binding URI of data publication point to URI of SIP
service element.
The whole discussion was all about how this binding should be archived (
if I could
correctly read mails).


But I think that other kind of bindings seems to be managed for making 
the whole system work.
Let me give an example about presence.
(I think CPL uploading has same issue)

The uploaded presence received by a uploading target point will be
passed to a presence server to which
the uploading target point is binded. When the data will be passed to
the presence server,
the data must be treated as the presence info for intended presentity.
In some cases, the entity uploading the data is exactly the intended
presentity,
but I can imagine that third party entities may upload presence info for
some presentity.
In this case ( the third party entity upload), the uploaded info must be
treated as for correct presentity.
This kind of binding, "binding data to SIP identity" should be kept in
mind, I believe.

Apart from "binding data to SIP identity" problem,
authentication of uploading entity by uploading target point does not
seem to be easy especially
on the third party upload, because this authentication is not
independent
from authentication of SIP UA by SIP service element.

Is this worth to take care? Tiny thing? Or, I dropped some assumption?
If this is important, do we have to make some standardized way of the
new type of binding?
Or, out of scope?

Best regards,
Noboru Iwayama



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



From daemon@optimus.ietf.org  Wed Apr 24 11:45:48 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19801
	for <sipping-archive@odin.ietf.org>; Wed, 24 Apr 2002 11:45:48 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA09852
	for sipping-archive@odin.ietf.org; Wed, 24 Apr 2002 11:45:51 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA09397;
	Wed, 24 Apr 2002 11:33:45 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA09366
	for <sipping@optimus.ietf.org>; Wed, 24 Apr 2002 11:33:42 -0400 (EDT)
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19116
	for <sipping@ietf.org>; Wed, 24 Apr 2002 11:33:38 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.76])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g3OFYXLC004606
	for <sipping@ietf.org>; Wed, 24 Apr 2002 11:34:33 -0400 (EDT)
Message-ID: <3CC6D034.B5DD5B14@dynamicsoft.com>
Date: Wed, 24 Apr 2002 11:33:08 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: sipping@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] new I-D on markup languages for DTMF and user input
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Folks,

I've just submitted an I-D that discusses a SIP framework for the usage
of markup languages (HTML, VoiceXML, WML) for stimulus signaling for
driving sip applications. The draft also proposes a DTMF markup
language, DML, that operates within the framework. 

Until it appears in the archives, you can pick up a copy at:

http://www.jdrosen.net/papers/draft-rosenberg-sipping-markup-00.txt

Comments and questions welcome as always.

-Jonathan R.
-- 
Jonathan D. Rosenberg, Ph.D.            72 Eagle Rock Avenue
Chief Scientist                         First Floor
dynamicsoft                             East Hanover, NJ 07936
jdrosen@dynamicsoft.com                 FAX: (973) 952-5050
http://www.jdrosen.net                  PH:  (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 daemon@ns.ietf.org  Wed Apr 24 13:59:50 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01675
	for <sipping-archive@odin.ietf.org>; Wed, 24 Apr 2002 13:59:50 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA20268
	for sipping-archive@odin.ietf.org; Wed, 24 Apr 2002 13:59:52 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA19706;
	Wed, 24 Apr 2002 13:48:04 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA19634
	for <sipping@ns.ietf.org>; Wed, 24 Apr 2002 13:47:59 -0400 (EDT)
Received: from chuckie.dgms.com (angelica.ulticom.com [208.255.120.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00797;
	Wed, 24 Apr 2002 13:47:55 -0400 (EDT)
Received: from ulticom.com (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with ESMTP id NAA10970;
	Wed, 24 Apr 2002 13:47:22 -0400 (EDT)
Message-ID: <3CC6F0A2.C33A694E@ulticom.com>
Date: Wed, 24 Apr 2002 13:51:31 -0400
From: Vijaya Venkatachalam <vijaya@ulticom.com>
Organization: Ulticom, Inc.
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony}  (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: sipping@ietf.org, sip@ietf.org
References: <Pine.WNT.4.44.0204180747240.-441563@chorizo.rapidconvergence.com>
Content-Type: multipart/mixed;
 boundary="------------5DB090691C5FC8CEEA1708CD"
Subject: [Sipping] Difference between the isup-sip mapping draft
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


This is a multi-part message in MIME format.
--------------5DB090691C5FC8CEEA1708CD
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,

Why are two drafts for ISUP to SIP mapping?
There is one in SIP WG (draft-ietf-sip-isup-03.txt)
and the other in SIPPING WG (draft-ietf-sipping-isup-01.txt).

Thanks,
Vijaya

--------------5DB090691C5FC8CEEA1708CD
Content-Type: text/x-vcard; charset=us-ascii;
 name="vijaya.vcf"
Content-Description: Card for Vijaya Venkatachalam
Content-Disposition: attachment;
 filename="vijaya.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard 
n:Venkatachalam;Vijaya
tel;fax:+1-856-866-2033
tel;work:+1-856-787-2853
x-mozilla-html:FALSE
url:www.ulticom.com
org:Ulticom, Inc.;Advanced Research 
adr:;;1020 Briggs Rd;Mt. Laurel;NJ;08054;USA
version:2.1
email;internet:vijaya@ulticom.com
fn:Vijaya Venkatachalam
end:vcard

--------------5DB090691C5FC8CEEA1708CD--


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



From daemon@ns.ietf.org  Wed Apr 24 14:33:32 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18042
	for <sipping-archive@odin.ietf.org>; Wed, 24 Apr 2002 14:33:32 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA22670
	for sipping-archive@odin.ietf.org; Wed, 24 Apr 2002 14:33:34 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA21771;
	Wed, 24 Apr 2002 14:22:23 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA21739
	for <sipping@ns.ietf.org>; Wed, 24 Apr 2002 14:22:20 -0400 (EDT)
Received: from magus.nostrum.com (root@magus.nostrum.com [66.119.225.66])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17447
	for <sipping@ietf.org>; Wed, 24 Apr 2002 14:22:16 -0400 (EDT)
Received: from txbcampbell (root@magus.nostrum.com [66.119.225.66])
	by magus.nostrum.com (8.11.0/8.11.0) with SMTP id g3OILjX13108;
	Wed, 24 Apr 2002 13:21:46 -0500 (CDT)
From: "Ben Campbell" <bcampbell@dynamicsoft.com>
To: <iwayama.noboru@jp.fujitsu.com>, <sipping@ietf.org>
Subject: RE: [Sipping] Binding published data to services
Date: Wed, 24 Apr 2002 13:21:05 -0500
Message-ID: <HNEOJECGFHIABDLENMMCMEPFCGAA.bcampbell@dynamicsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <000001c1eb9e$cd4473a0$0de11dac@PINK>
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit



> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]On Behalf Of
> iwayama.noboru@jp.fujitsu.com
> Sent: Wednesday, April 24, 2002 9:46 AM
> To: sipping@ietf.org
> Subject: Re: [Sipping] Binding published data to services
>
>
> All,
>
> There was the discussion on binding published data to services about two
> weeks ago.
> Even I have read through the discussion and minute in last IETF meeting,
> I could not have the big picture as a whole system.
> Maybe I misunderstand something important.
> I appreciate your kind help.
>
> What I have in mind based on the emails, which Ben Campbell started in
> this list, is as follows:
>
> In general, SIP UA has a need to upload some data towards a SIP service
> network.
> CPI script and presence info are examples of those data.
> Before considering a particular mechanism (i.e., protocol) for uploading
> the data,
> this SIPPING WG decided to investigate the fact that the uploaded data
> onto SIP network must be
> binded some SIP service element. For example,
> in the case of presence, in order for a presentitiy to update presence
> info,
> the presentitiy uploads his or her updated presence info towards some
> URI.
> It is needed to ensure that the URI should be right point for the
> presentitiy to upload his
> updated presence info, otherwise, his presence info could not be handled
> nor notified to correct
> watchers.
> The assumption here is that we do not discuss underlying uploading
> mechanism but
> we focus only on binding URI of data publication point to URI of SIP
> service element.
> The whole discussion was all about how this binding should be archived (
> if I could
> correctly read mails).

That is a fair summary.

>
>
> But I think that other kind of bindings seems to be managed for making
> the whole system work.
> Let me give an example about presence.
> (I think CPL uploading has same issue)
>
> The uploaded presence received by a uploading target point will be
> passed to a presence server to which
> the uploading target point is binded. When the data will be passed to
> the presence server,
> the data must be treated as the presence info for intended presentity.
> In some cases, the entity uploading the data is exactly the intended
> presentity,
> but I can imagine that third party entities may upload presence info for
> some presentity.
> In this case ( the third party entity upload), the uploaded info must be
> treated as for correct presentity.
> This kind of binding, "binding data to SIP identity" should be kept in
> mind, I believe.

This simply means that the authorization mechanism for whatever protocols
get chosen allow for the possibility that identities _other_ than the
principle may be allowed to upload publish information. I don't think we
have made any assumptions so far that preclude this.


>
> Apart from "binding data to SIP identity" problem,
> authentication of uploading entity by uploading target point does not
> seem to be easy especially
> on the third party upload, because this authentication is not
> independent
> from authentication of SIP UA by SIP service element.
>
> Is this worth to take care? Tiny thing? Or, I dropped some assumption?
> If this is important, do we have to make some standardized way of the
> new type of binding?
> Or, out of scope?

I agree authentication will be an important consideration for any protocol
used to upload service data. However, I think that is a consideration for
those protocols, and out of scope for the binding discussion.

Or are you refering to authentication those who wish to _learn_ where to
publish service information? So that we might release that information only
to those with the proper privilige? I am not sure if that is a requirement
or not. It would certianly not be possible with any algorithmic
transformation, or any approach based on DNS. It could be possible with a
query based approach. I suspect that requirement would do us more harm than
good. We may be better off saying that the publication point is public
knowledge, but that any protocol used for publication must allow
authentication.



> Best regards,
> Noboru Iwayama
>
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 daemon@ns.ietf.org  Wed Apr 24 17:45:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10080
	for <sipping-archive@odin.ietf.org>; Wed, 24 Apr 2002 17:45:28 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA03400
	for sipping-archive@odin.ietf.org; Wed, 24 Apr 2002 17:45:32 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA02763;
	Wed, 24 Apr 2002 17:31:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA02724
	for <sipping@ns.ietf.org>; Wed, 24 Apr 2002 17:31:48 -0400 (EDT)
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09901
	for <sipping@ietf.org>; Wed, 24 Apr 2002 17:31:44 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.76])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g3OLWbLC005194;
	Wed, 24 Apr 2002 17:32:37 -0400 (EDT)
Message-ID: <3CC72423.FB1234D@dynamicsoft.com>
Date: Wed, 24 Apr 2002 17:31:15 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Vijay K. Gurbani" <vkg@lucent.com>
CC: SIPPING LIST <sipping@ietf.org>
Subject: Re: [Sipping] SIP support for IN services
References: <3CC03681.2060701@lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Trimming to sipping.

I think this draft would benefit from an applicability statement of
sorts up front. There are definitely issues with this kind of approach.
It will pretty much require a b2bua unless the SIP element KNOWS that
the only services involved won't require it. It is limited to services
deployed in the PSTN. There are other ways to get those services without
this kind of approach. For example, to get an 800 number service, you
could alternatively have the proxy query a DB (using enum, for example),
to get the routing number. I don't want the readership to believe that
this is the IETFs preferred model for services in SIP. I know the draft
doesn't claim that, but an applicability statement clearly saying it
isn't would be a good thing, IMHO.

Thanks,
Jonathan R.


"Vijay K. Gurbani" wrote:
> 
> Folks:
> 
> Enclosed is an I-D for review that describes SIP support for IN
> services.  The I-D represents agreement of the IETF SIN (SIP/IN) design
> team and is intended for publication as an informational RFC.  It has
> been through Last Call in the IETF SIN DT and the comments of the WGs
> identified in the To list of this email are now being solicited.
> 
> http://search.ietf.org/internet-drafts/draft-gurbani-sin-00.txt
> 
> Thanks,
> 
> - vijay
> --
> Vijay K. Gurbani  vkg@{lucent.com,research.bell-labs.com,acm.org}
> Wireless Networks Group/Internet Software and eServices
> Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440
> Naperville, Illinois 60566     Voice: +1 630 224 0216
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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.            72 Eagle Rock Avenue
Chief Scientist                         First Floor
dynamicsoft                             East Hanover, NJ 07936
jdrosen@dynamicsoft.com                 FAX: (973) 952-5050
http://www.jdrosen.net                  PH:  (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 daemon@ns.ietf.org  Wed Apr 24 19:05:35 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11218
	for <sipping-archive@odin.ietf.org>; Wed, 24 Apr 2002 19:05:04 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA07593
	for sipping-archive@odin.ietf.org; Wed, 24 Apr 2002 19:05:06 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA06715;
	Wed, 24 Apr 2002 18:52:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA06674
	for <sipping@ns.ietf.org>; Wed, 24 Apr 2002 18:52:44 -0400 (EDT)
Received: from oak.neustar.com (oak.neustar.com [209.173.53.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10921
	for <sipping@ietf.org>; Wed, 24 Apr 2002 18:52:39 -0400 (EDT)
Received: from chiimc01.il.neustar.com (stih650b-s1p2.va.neustar.com [209.173.53.65])
	by oak.neustar.com (8.11.0/8.11.0) with ESMTP id g3OMpJH14811;
	Wed, 24 Apr 2002 18:51:20 -0400
Received: by chiimc01.il.neustar.com with Internet Mail Service (5.5.2653.19)
	id <J25ZMWYP>; Wed, 24 Apr 2002 17:51:14 -0500
Message-ID: <70565611B164D511957A001083FCDD5601870276@va02.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Vijaya Venkatachalam'" <vijaya@ulticom.com>, sipping@ietf.org
Subject: RE: [Sipping] Difference between the isup-sip mapping draft
Date: Wed, 24 Apr 2002 17:51:13 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

draft-ietf-sipping-isup-01 is the current version. For whatever reason,
draft-ietf-sip-isup-03 was not removed from the repository when the draft
was moved from the SIP WG to the SIPPING WG. As you can see from the dates
on the respective drafts, the SIPPING draft is more recent.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Vijaya Venkatachalam [mailto:vijaya@ulticom.com]
> Sent: Wednesday, April 24, 2002 10:52 AM
> To: sipping@ietf.org; sip@ietf.org
> Subject: [Sipping] Difference between the isup-sip mapping draft
> 
> 
> Hi,
> 
> Why are two drafts for ISUP to SIP mapping?
> There is one in SIP WG (draft-ietf-sip-isup-03.txt)
> and the other in SIPPING WG (draft-ietf-sipping-isup-01.txt).
> 
> Thanks,
> Vijaya
> 

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



From daemon@ns.ietf.org  Wed Apr 24 19:35:56 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11723
	for <sipping-archive@odin.ietf.org>; Wed, 24 Apr 2002 19:35:51 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA09337
	for sipping-archive@odin.ietf.org; Wed, 24 Apr 2002 19:35:54 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA08492;
	Wed, 24 Apr 2002 19:23:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA08462
	for <sipping@ns.ietf.org>; Wed, 24 Apr 2002 19:23:28 -0400 (EDT)
Received: from pine.neustar.com (pine.neustar.com [209.173.57.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11549
	for <sipping@ietf.org>; Wed, 24 Apr 2002 19:23:25 -0400 (EDT)
Received: from chiimc01.il.neustar.com (chih650b-s3p2.il.neustar.com [209.173.57.65])
	by pine.neustar.com (8.11.0/8.11.0) with ESMTP id g3ONMm700727;
	Wed, 24 Apr 2002 18:22:48 -0500
Received: by chiimc01.il.neustar.com with Internet Mail Service (5.5.2653.19)
	id <J25ZMXBV>; Wed, 24 Apr 2002 18:22:43 -0500
Message-ID: <70565611B164D511957A001083FCDD5601870277@va02.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Alexeitsev, D'" <D.Alexeitsev@telekom.de>, sipping@ietf.org
Subject: RE: [Sipping] Internet-Draft on ISUP-SIP
Date: Wed, 24 Apr 2002 18:22:43 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


It is my understanding that the SIP-ISUP interworking draft
(draft-ietf-sipping-isup-01) will be considered as a Best Common Practice.

I am aware that the International Softswitch Consortium (a body unrelated to
the IETF) was planning some sort of interoperability trials that were based
on the IETF SIP-T work, but I'm unsure of their status. 

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Alexeitsev, D [mailto:D.Alexeitsev@telekom.de]
> Sent: Wednesday, April 24, 2002 4:03 AM
> To: sipping@ietf.org
> Subject: [Sipping] Internet-Draft on ISUP-SIP
> 
> 
> Good day,
> 
> While looking at the official SIPPING working group web page 
> I have found, that under Goals and Milestones is says that 
> ISUP-SIP interworking draft will be considered as Proposed 
> Standard. My question is have there been any interoperability 
> test for the interworking? if yes, could you please point to 
> the results?
> 
> Best regards,
> 
> Denis Alexeitsev
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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 daemon@ns.ietf.org  Wed Apr 24 20:03:38 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11975
	for <sipping-archive@odin.ietf.org>; Wed, 24 Apr 2002 20:03:38 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA10765
	for sipping-archive@odin.ietf.org; Wed, 24 Apr 2002 20:03:40 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA09748;
	Wed, 24 Apr 2002 19:48:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA09686
	for <sipping@ns.ietf.org>; Wed, 24 Apr 2002 19:48:31 -0400 (EDT)
Received: from out002.verizon.net (out002pub.verizon.net [206.46.170.141])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11864
	for <sipping@ietf.org>; Wed, 24 Apr 2002 19:48:28 -0400 (EDT)
Received: from matt.verizon.net ([4.33.209.215]) by out002.verizon.net
          (InterMail vM.5.01.04.05 201-253-122-122-105-20011231) with ESMTP
          id <20020424234835.ULMD4379.out002.verizon.net@matt.verizon.net>;
          Wed, 24 Apr 2002 18:48:35 -0500
Message-Id: <5.1.0.14.2.20020424164706.02a3cc90@mail.verizon.net>
X-Sender: res06gzk@mail.verizon.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 24 Apr 2002 16:47:52 -0700
To: "Peterson, Jon" <jon.peterson@neustar.biz>,
        "'Alexeitsev, D'" <D.Alexeitsev@telekom.de>, sipping@ietf.org
From: Matt Holdrege <matt.holdrege@verizon.net>
Subject: RE: [Sipping] Internet-Draft on ISUP-SIP
In-Reply-To: <70565611B164D511957A001083FCDD5601870277@va02.va.neustar.c
 om>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

The ISC (www.softswitch.org) is working on this as is ITU-T SG11.

At 04:22 PM 4/24/2002, Peterson, Jon wrote:

>It is my understanding that the SIP-ISUP interworking draft
>(draft-ietf-sipping-isup-01) will be considered as a Best Common Practice.
>
>I am aware that the International Softswitch Consortium (a body unrelated to
>the IETF) was planning some sort of interoperability trials that were based
>on the IETF SIP-T work, but I'm unsure of their status.
>
>Jon Peterson
>NeuStar, Inc.
>
> > -----Original Message-----
> > From: Alexeitsev, D [mailto:D.Alexeitsev@telekom.de]
> > Sent: Wednesday, April 24, 2002 4:03 AM
> > To: sipping@ietf.org
> > Subject: [Sipping] Internet-Draft on ISUP-SIP
> >
> >
> > Good day,
> >
> > While looking at the official SIPPING working group web page
> > I have found, that under Goals and Milestones is says that
> > ISUP-SIP interworking draft will be considered as Proposed
> > Standard. My question is have there been any interoperability
> > test for the interworking? if yes, could you please point to
> > the results?
> >
> > Best regards,
> >
> > Denis Alexeitsev
> >
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the 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 daemon@ns.ietf.org  Wed Apr 24 20:56:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11985
	for <sipping-archive@odin.ietf.org>; Wed, 24 Apr 2002 20:03:38 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA10779
	for sipping-archive@odin.ietf.org; Wed, 24 Apr 2002 20:03:41 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA09729;
	Wed, 24 Apr 2002 19:48:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA09681
	for <sipping@ns.ietf.org>; Wed, 24 Apr 2002 19:48:31 -0400 (EDT)
Received: from pine.neustar.com (pine.neustar.com [209.173.57.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11863
	for <sipping@ietf.org>; Wed, 24 Apr 2002 19:48:28 -0400 (EDT)
Received: from chiimc01.il.neustar.com (chih650b-s3p2.il.neustar.com [209.173.57.65])
	by pine.neustar.com (8.11.0/8.11.0) with ESMTP id g3ONm0701254
	for <sipping@ietf.org>; Wed, 24 Apr 2002 18:48:00 -0500
Received: by chiimc01.il.neustar.com with Internet Mail Service (5.5.2653.19)
	id <J25ZMXFL>; Wed, 24 Apr 2002 18:47:55 -0500
Message-ID: <70565611B164D511957A001083FCDD5601870279@va02.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: sipping@ietf.org
Subject: RE: [Sipping] Internet-Draft on ISUP-SIP
Date: Wed, 24 Apr 2002 18:47:54 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Actually, I stand corrected - it is apparently now intended to be a Proposed
Standard, not a BCP. My mistake.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> Sent: Wednesday, April 24, 2002 4:23 PM
> To: 'Alexeitsev, D'; sipping@ietf.org
> Subject: RE: [Sipping] Internet-Draft on ISUP-SIP
> 
> 
> 
> It is my understanding that the SIP-ISUP interworking draft
> (draft-ietf-sipping-isup-01) will be considered as a Best 
> Common Practice.
> 
> I am aware that the International Softswitch Consortium (a 
> body unrelated to
> the IETF) was planning some sort of interoperability trials 
> that were based
> on the IETF SIP-T work, but I'm unsure of their status. 
> 
> Jon Peterson
> NeuStar, Inc.
> 
> > -----Original Message-----
> > From: Alexeitsev, D [mailto:D.Alexeitsev@telekom.de]
> > Sent: Wednesday, April 24, 2002 4:03 AM
> > To: sipping@ietf.org
> > Subject: [Sipping] Internet-Draft on ISUP-SIP
> > 
> > 
> > Good day,
> > 
> > While looking at the official SIPPING working group web page 
> > I have found, that under Goals and Milestones is says that 
> > ISUP-SIP interworking draft will be considered as Proposed 
> > Standard. My question is have there been any interoperability 
> > test for the interworking? if yes, could you please point to 
> > the results?
> > 
> > Best regards,
> > 
> > Denis Alexeitsev
> > 
> > 
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the 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 daemon@ns.ietf.org  Thu Apr 25 00:34:57 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17831
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 00:34:56 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA23979
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 00:34:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA22991;
	Thu, 25 Apr 2002 00:20:39 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA22960
	for <sipping@ns.ietf.org>; Thu, 25 Apr 2002 00:20:35 -0400 (EDT)
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17647
	for <sipping@ietf.org>; Thu, 25 Apr 2002 00:20:34 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.76])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g3P4LNLC005365;
	Thu, 25 Apr 2002 00:21:24 -0400 (EDT)
Message-ID: <3CC783EE.11D42E28@dynamicsoft.com>
Date: Thu, 25 Apr 2002 00:19:58 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: iwayama.noboru@jp.fujitsu.com
CC: sipping@ietf.org
Subject: Re: [Sipping] Binding published data to services
References: <000001c1eb9e$cd4473a0$0de11dac@PINK>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

inline.

iwayama.noboru@jp.fujitsu.com wrote:
> 
> All,
> 
> There was the discussion on binding published data to services about two
> weeks ago.
> Even I have read through the discussion and minute in last IETF meeting,
> I could not have the big picture as a whole system.
> Maybe I misunderstand something important.
> I appreciate your kind help.
> 
> What I have in mind based on the emails, which Ben Campbell started in
> this list, is as follows:
> 
> In general, SIP UA has a need to upload some data towards a SIP service
> network.
> CPI script and presence info are examples of those data.
> Before considering a particular mechanism (i.e., protocol) for uploading
> the data,
> this SIPPING WG decided to investigate the fact that the uploaded data
> onto SIP network must be
> binded some SIP service element. For example,
> in the case of presence, in order for a presentitiy to update presence
> info,
> the presentitiy uploads his or her updated presence info towards some
> URI.
> It is needed to ensure that the URI should be right point for the
> presentitiy to upload his
> updated presence info, otherwise, his presence info could not be handled
> nor notified to correct
> watchers.
> The assumption here is that we do not discuss underlying uploading
> mechanism but
> we focus only on binding URI of data publication point to URI of SIP
> service element.
> The whole discussion was all about how this binding should be archived (
> if I could
> correctly read mails).

Thanks for the summary. We need to continue this thread.

I am not convinced that we even have the right model for this
discussion. There is an implicit assumption that the publication URI
needs to be discovered, computed, or derived at all from the SIP URI of
the user for whom the data is to be published. That is, we have assumed
that if I want to publish presence data for sip:jdrosen@dynamicsoft.com,
part of the problem will be to define a system for mapping that URI to
some other URI for publishing presence data,
http://publisher.dynamicsoft.com/user/jdrosen, for example. I am not
sure yet that we really need this.

I don't see the problem in configuring a UA with the URL for supporting
publication services. For example, consider presence publication. My UA
would be configured to perform an HTTP POST to sip:pub.dynamicsoft.com,
and include my SIP URI as part of a header or part of the body. The
pub.dynamicsoft.com server would probably need to do a few things with
that data. It might need to write it to a DB, and it needs to make sure
it gets pushed to the presence servers handling subscriptions for me
(there could be more than one). This could happen with a POST from the
pub.dynamicsoft.com servers to the presence servers in the
dynamicsoft.com network.

What is gained by computing this publication URL, or looking it up in a
dynamic sysem? Surely, it is one of a bunch of different service URIs
that will need to be configured in the UA.

-Jonathan R.
 

-- 
Jonathan D. Rosenberg, Ph.D.            72 Eagle Rock Avenue
Chief Scientist                         First Floor
dynamicsoft                             East Hanover, NJ 07936
jdrosen@dynamicsoft.com                 FAX: (973) 952-5050
http://www.jdrosen.net                  PH:  (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 daemon@optimus.ietf.org  Thu Apr 25 01:14:46 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18285
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 01:14:46 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA02522
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 01:14:46 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA25061;
	Thu, 25 Apr 2002 01:01:14 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA25022
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 01:01:08 -0400 (EDT)
Received: from magus.nostrum.com (root@magus.nostrum.com [66.119.225.66])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18075
	for <sipping@ietf.org>; Thu, 25 Apr 2002 01:00:57 -0400 (EDT)
Received: from txbcampbell (root@magus.nostrum.com [66.119.225.66])
	by magus.nostrum.com (8.11.0/8.11.0) with SMTP id g3P50rX61838;
	Thu, 25 Apr 2002 00:00:53 -0500 (CDT)
From: "Ben Campbell" <bcampbell@dynamicsoft.com>
To: "Jonathan Rosenberg" <jdrosen@dynamicsoft.com>,
        <iwayama.noboru@jp.fujitsu.com>
Cc: <sipping@ietf.org>
Subject: RE: [Sipping] Binding published data to services
Date: Thu, 25 Apr 2002 00:00:13 -0500
Message-ID: <HNEOJECGFHIABDLENMMCCEABCHAA.bcampbell@dynamicsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <3CC783EE.11D42E28@dynamicsoft.com>
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit



> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]On Behalf Of
> Jonathan Rosenberg
> Sent: Wednesday, April 24, 2002 11:20 PM
> To: iwayama.noboru@jp.fujitsu.com
> Cc: sipping@ietf.org
> Subject: Re: [Sipping] Binding published data to services
>
>
> inline.
>
> iwayama.noboru@jp.fujitsu.com wrote:
> >
> > All,
> >
> > There was the discussion on binding published data to services about two
> > weeks ago.
> > Even I have read through the discussion and minute in last IETF meeting,
> > I could not have the big picture as a whole system.
> > Maybe I misunderstand something important.
> > I appreciate your kind help.
> >
> > What I have in mind based on the emails, which Ben Campbell started in
> > this list, is as follows:
> >
> > In general, SIP UA has a need to upload some data towards a SIP service
> > network.
> > CPI script and presence info are examples of those data.
> > Before considering a particular mechanism (i.e., protocol) for uploading
> > the data,
> > this SIPPING WG decided to investigate the fact that the uploaded data
> > onto SIP network must be
> > binded some SIP service element. For example,
> > in the case of presence, in order for a presentitiy to update presence
> > info,
> > the presentitiy uploads his or her updated presence info towards some
> > URI.
> > It is needed to ensure that the URI should be right point for the
> > presentitiy to upload his
> > updated presence info, otherwise, his presence info could not be handled
> > nor notified to correct
> > watchers.
> > The assumption here is that we do not discuss underlying uploading
> > mechanism but
> > we focus only on binding URI of data publication point to URI of SIP
> > service element.
> > The whole discussion was all about how this binding should be archived (
> > if I could
> > correctly read mails).
>
> Thanks for the summary. We need to continue this thread.
>
> I am not convinced that we even have the right model for this
> discussion. There is an implicit assumption that the publication URI
> needs to be discovered, computed, or derived at all from the SIP URI of
> the user for whom the data is to be published. That is, we have assumed
> that if I want to publish presence data for sip:jdrosen@dynamicsoft.com,
> part of the problem will be to define a system for mapping that URI to
> some other URI for publishing presence data,
> http://publisher.dynamicsoft.com/user/jdrosen, for example. I am not
> sure yet that we really need this.
>
> I don't see the problem in configuring a UA with the URL for supporting
> publication services. For example, consider presence publication. My UA
> would be configured to perform an HTTP POST to sip:pub.dynamicsoft.com,
> and include my SIP URI as part of a header or part of the body. The
> pub.dynamicsoft.com server would probably need to do a few things with
> that data. It might need to write it to a DB, and it needs to make sure
> it gets pushed to the presence servers handling subscriptions for me
> (there could be more than one). This could happen with a POST from the
> pub.dynamicsoft.com servers to the presence servers in the
> dynamicsoft.com network.
>
> What is gained by computing this publication URL, or looking it up in a
> dynamic sysem? Surely, it is one of a bunch of different service URIs
> that will need to be configured in the UA.
>

I don't have a problem with that approach at all--but lots of people seem to
object to provisioning anything like this. It does presume your publication
destination is static, i.e. it doesn't change much over time. That is
probably OK.

So, does it make sense to apply RFC3087 to the publication URL? (realizing
of course that it is a non-SIP URI, but the concepts seem to apply.)


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



From daemon@optimus.ietf.org  Thu Apr 25 01:33:05 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18461
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 01:33:04 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA07612
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 01:33:05 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA05206;
	Thu, 25 Apr 2002 01:19:34 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA05098
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 01:19:27 -0400 (EDT)
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18334
	for <sipping@ietf.org>; Thu, 25 Apr 2002 01:19:21 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.76])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g3P5KCLC005390;
	Thu, 25 Apr 2002 01:20:12 -0400 (EDT)
Message-ID: <3CC791B7.B538B36@dynamicsoft.com>
Date: Thu, 25 Apr 2002 01:18:47 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Fairlie-Cuninghame, Robert" <rfairlie@nuera.com>
CC: sipping@ietf.org, "'Bert Culpepper'" <bert.culpepper@intervoice-brite.com>
Subject: Re: [Sipping] I-D  
 ACTION:draft-culpepper-sipping-app-interact-reqs-00.txt
References: <E79883AEA37FD411A58C00508BAC5F4B01D38C5F@exchange1.nuera.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

inline.

"Fairlie-Cuninghame, Robert" wrote:
> 

> > > R5:  A network entity desiring user indications must be able to
> > >         request user indications from another network entity.  The
> > >         entity receiving a request must be able to respond with its
> > >         capability/intent to transmit user indications.
> >
> > We should be more specific here. We have a caller and a
> > callee. I think
> > that by "entity" you mean one of those two.
> 
> No, we are purposefully not restricting the mechanism to only caller and
> callee (or even proxy). So, yes, I agree we need to re-word to
> explicitly
> define. Further discussion later.

That doesn't make sense to me. By definition, user input indication is
possible only from a human, NOT from an automata. An automata can try
(web screen scraping...) but that is a known bad thing.

> > > R15: The receiving application must be able to detect user activity
> > >         indication loss due to packet loss from received
> > user activity
> > >         indications.
> >
> > I don't know what this means.
> 
> Detecting missing indications.  For example, a PIN is transmitted one
> digit
> at a time.  If one message (network packet) gets lost, we want to be
> able to
> determine this at the receiver. Will re-word.

There is an implicit assumption here of UDP based notifications and/or
notifications that are not stop-and-wait. I think the real requirement
you want here is ordering - events are delivered to the observer in the
same order they occurred at the reporter.


> 
> >
> > > D4:  The mechanism should support routing and
> > identification that is
> > >         compatible with use in a SIP-based network.
> >
> > This is too vague to be useful.
> >
> 
> Are you suggesting we reword or simply drop ? Can you suggest anything
> more
> useful/specific?

I am suggesting to drop unless you can define more specifically what the
requirement is.


> > * The mechanism should support devices that possess a UI, and those
> > which do not possess a UI
> 
> Jonathan can you please explain exactly what you mean by this. My
> feeling is
> that this is the crux of your new requirements, yet I don't have a clear
> idea of what you mean by "The mechanism should support devices ... which
> do
> not possess a UI."

Hopefully the recent draft on markup I just submitted explains better.
The basic idea is that there are many devices that have the ability to
interact with the user. There could, for example, be a display with
buttons. The display would present the user with choices, and the user
would press a button, causing a notification to be sent into the
network. This is in contrast with devices, like a traditional dumb black
phone, which have no ability to interact with the user. There is no
display. There is no way to know, when a user presses a DTMF key, what
application they were trying to interact with. 


> 
> By this requirement, do you mean
> 1) The mechanism should allow an application to present a virtual user
> interface and/or the transport of user indications on the virtual
> interface
> (when a device has no physical interface aside from a display and
> possibly a
> touch-screen or pointing device); or
> 2) the mechanism should allow an application to determine that a device
> has
> no physical interface aside from a display (and possibly a touch-screen
> or
> pointing device) and how that resource is accessed?
> 
> These are two very different requirements. Or do you have something
> entirely
> different in mind?

The mechanism should support devices like black phones, which have no
display capabilities that can be used to interact with the user, and
devices like PC phones which have web browsers that can be used to
interact with the user. 


> >
> > * The mechanism should be capable of handling UIs from simple screens
> > with buttons, to voice input
> 
> I'm not sure what the functional requirement you are asking for here
> (apart
> from the fact that the mechanism should be extensible that is mentioned
> in
> the next point): "The mechanism should be capable of handling UI's ...
> with
> voice input?" Are you meaning local recognition software that allows a
> user
> to "say a command" or something similar? 

Yes. 

> [I presume you aren't talking
> about
> voice recog on the application server here.] Surely, this is just
> another
> permutation of mapping some local interface to application specific
> stimuli?

Yes. I just want to make sure we cover a range of media, not just
physical buttons. Hyperlinks, voice, even visual recognition should be
possible.

> 
> >
> > * The mechanism should be capable of handling future user interfaces
> > that may be defined down the road
> 
> R10 was supposed to cover that ...
> 
> R10:    The mechanism must be extensible so that some non key-based user
> indications can be supported in the future, for instance, sliders, dials
> or
> wheels.
> 
> Perhaps it could be broadened. Any suggestions?

Voice, hyperlinks, biometrics, brain waves, etc.

> >
> > * The mechanism should support user interfaces which require a new
> > content to be presented to the user upon input from the user (i.e.,
> > change the screen when a user presses a button)
> >
> 
> Hmm, this goes beyond "getting indications a device supports" and is
> more to
> do with "application action in response to input". I'm not sure it is in
> scope.

I think it has to be - thats the whole problem! I think we've been
thinking far too narrowly on this problem. Its not just about
notifications of user input. We are talking about supporting stimulus
signaling for applications, where stimulus signaling is defined in the
broadest sense. 

> 
> > * The mechanism should support user interfaces where user input can be
> > sent to the application without waiting for a response from
> > the previous
> > input
> 
> Agreed.  A requirement that the mechanism is not limited to stop and
> wait.
> This was what we were aiming at in D3:
> 
> D3:     The mechanism should attempt to reduce recovery delays under
> packet
> loss scenarios.

I don't read D3 as saying the same thing as above.


> > * The mechanism should allow the user to interface with multiple user
> > interfaces for different applications within the same call
> > (for example,
> > a single call may involve a call recording application and a prepaid
> > calling application, both of which might support a UI)
> 
> Good one, although I'm not sure how this is a requirement on the
> mechanism
> rather than simply how the user locally selects their user interface
> (which
> would be a requirement on how to design a user device, i.e., not in
> scope).
> Each relationship between an application and a user interface would be a
> separate subscription.

No. We have a fundamental disconnect here. There are two radically
different approaches for interacting with applications. In approach 1,
there are a set of applications listening for user input. The user input
is not directed; that is, the user has no ability to say "this input is
for app 1" or "this input is for app 2". Directing user input generally
requires a user interface of sorts, and in approach 1, there is no UI.
In approach 2, input can be directed. The device has a user interface
that allows the user to send feedback to specific applications. 

Let me give concrete examples. A black phone is an example of approach
1. Multiple apps can listen for DTMF, but the user can't direct DTMF to
a specific application. This, BTW, is the source of countless feature
interaction problems, and is an artifact of the legacy interface of the
phone. An example of approach 2 is a PC. Lets say I make a call from my
PC, and there are two applications involved in processing that call. One
is a prepaid calling app. One of the things this app allows me, the
user, to do, is to hang up the call and make another without re-entering
my PIN. The other application is a voice recorder app, which allows me
to record the audio of the call. This app needs my input to start and
stop the recording. Once I make the call, two windows pop up. One is a
control panel for the voice recorder (with start and stop buttons) and
another is a control panel for the prepaid app. When I click "start
recording" on the control panel for the voice recorder, this starts the
recording process. That happens through user input indications, but they
are directed towards the voice recorder app. They can be directed since
they occur within a context - a user interface - which allows them to go
to the right place. Approach 2 has MUCH better feature interaction
properties, and a much more compelling user experience.

Approach 1 is a subset of approach 2. We should be seeking to solve
approach 2, and a result, knock off approach 1. The worst thing we can
do is continue to develop specifications that proliferate the broken
mode of user interface which the PSTN has provided us! We should support
it, but it is not the design goal. 


> 
> >
> > * The mechanism should allow the user to know which application is
> > associated with which user interface/input
> 
> OK.  (satisfied through authentication/authorization of the SUBSCRIBE?)

You presume SUBSCRIBE - thats a mechanism. The requirement is as it is
written. In the example above, my PC should be able to tell me that one
of the popups is for a voice recorder, and the other is for a prepaid
calling app.

> 
> >
> > * The mechanism must allow a user to have assurances that the
> > user input
> > it is providing is only to applications/servers on the call
> > path between
> > caller and callee.
> 
> I think this is covered by R16 & R17:
> 
> R16:    The mechanism must allow for end-to-end security/privacy between
> source and destination.
> 
> R17:    Both entities must be able to authenticate each other.

No - these are not the same at all. I don't know what end-to-end
security is. Security encapsulates a lot of functions. I am saying that
the mechanism should support a specific authorization model - that the
system can provide guarantees that only servers on the call path can ask
for my user input. 


> >
> > * The mechanism must work with applications that are both proxy and
> > b2bua.
> 
> As mentioned in the discussion of R5, the use of the term "network
> entity"
> is purposefully designed to NOT limit the interaction to just proxies or
> b2bua's. SIP Event's has no such constraints and I don't see that this
> mechanism should either. Will re-word to make clearer our intent. Do you
> have a problem with this generalization?

There are two participants here. There is the user, and the application.
The application can be a proxy, B2bua, or just UA. The user has to be a
user, though, not a proxy (see above).

-Jonathan R.


-- 
Jonathan D. Rosenberg, Ph.D.            72 Eagle Rock Avenue
Chief Scientist                         First Floor
dynamicsoft                             East Hanover, NJ 07936
jdrosen@dynamicsoft.com                 FAX: (973) 952-5050
http://www.jdrosen.net                  PH:  (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 daemon@optimus.ietf.org  Thu Apr 25 01:41:06 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18718
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 01:41:06 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA08216
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 01:41:07 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA06900;
	Thu, 25 Apr 2002 01:25:43 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA06872
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 01:25:40 -0400 (EDT)
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18395
	for <sipping@ietf.org>; Thu, 25 Apr 2002 01:25:38 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.76])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g3P5QULC005393;
	Thu, 25 Apr 2002 01:26:30 -0400 (EDT)
Message-ID: <3CC79331.23C093EB@dynamicsoft.com>
Date: Thu, 25 Apr 2002 01:25:05 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Fairlie-Cuninghame, Robert" <rfairlie@nuera.com>
CC: "'Bert Culpepper'" <bert.culpepper@intervoice-brite.com>, sipping@ietf.org
Subject: Re: [Sipping] I-D  
 ACTION:draft-culpepper-sipping-app-interact-reqs-00.txt
References: <E79883AEA37FD411A58C00508BAC5F4B01D38C6C@exchange1.nuera.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit



"Fairlie-Cuninghame, Robert" wrote:
> 
> >
> > The "outside of a session" part was added to support being
> > able to receive
> > indications before a SIP session was fully established, (aka "early
> > sessions").  So do we want to limit the mechanism to
> > established sessions?
> 
> I believe that "outside of a session" and "early dialog" dialog
> subscription
> are two entirely different beasts and should be considered differently.
> "Outside a session" subscriptions relate to NO other dialogs; "early
> "subscriptions relate to a session that is in the progress of being
> established - but they still relate to a dialog. .

I was concerned about the "outside of a session" case. I think its ok to
have user input indications for early dialogs.


> 
> I guess there are two types of "early" subscription. The first is a
> subscription established before the session dialog has become
> established
> but only becomes active when the session becomes established. This is
> needed
> to ensure an appln doesn't miss any user indications when the session
> becomes active. The second is where the subscription becomes active
> while
> the sessions is still only an early dialog. This allows a number of
> services
> such as pre-ring PIN identification. We allowed this type of
> subscription in
> our key-events draft but now I'm having second thoughts. Allowing this
> mechanism could encourage people to do things in early dialogs that
> should
> only be done in established sessions. 

A dialog and a session are not the same thing.


For instance, the pre-ring PIN
> identification should perhaps really be done in an established session
> to
> the "SIP answering machine"  rather than an early session.

pre-ring PIN identification will require a session to be established
(meaning, an O/A exchange has completed). Otherwise, the user doesn't
get the voice prompts to input the PIN code. Now, the dialog could be
early, or it could be established, but that doesn't seem to be terribly
relevant. 

I can think of scenarios where you can only make the app work if the
user input indication is sent during an early dialog.


-Jonathan R.

-- 
Jonathan D. Rosenberg, Ph.D.            72 Eagle Rock Avenue
Chief Scientist                         First Floor
dynamicsoft                             East Hanover, NJ 07936
jdrosen@dynamicsoft.com                 FAX: (973) 952-5050
http://www.jdrosen.net                  PH:  (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 daemon@optimus.ietf.org  Thu Apr 25 01:49:05 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18819
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 01:49:05 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA08484
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 01:49:05 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA07957;
	Thu, 25 Apr 2002 01:36:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA07926
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 01:36:02 -0400 (EDT)
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18558
	for <sipping@ietf.org>; Thu, 25 Apr 2002 01:36:00 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.76])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g3P5arLC005397;
	Thu, 25 Apr 2002 01:36:53 -0400 (EDT)
Message-ID: <3CC795A0.8243CB3D@dynamicsoft.com>
Date: Thu, 25 Apr 2002 01:35:28 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Fairlie-Cuninghame, Robert" <rfairlie@nuera.com>
CC: sipping@ietf.org
Subject: Re: [Sipping] I-D  
 ACTION:draft-culpepper-sipping-app-interact-reqs-00.txt
References: <E79883AEA37FD411A58C00508BAC5F4B01D38C7E@exchange1.nuera.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit



"Fairlie-Cuninghame, Robert" wrote:
> 
> Just to provide a break in the monotony of Subject fields ...
> 
> Jonathan,
> 
>  I've given some more thought to a couple of your requirements:
> 
> > * The mechanism should allow a device to indicate support for multiple
> > user interfaces, and allow the application to select which
> > one is to be
> > used
> >
> > * The mechanism should allow a device to indicate relative preferences
> > amongst the various user interfaces
> >
> 
> I don't think your requirement adequately answers the questions: what is
> a
> "user interface" and what does it mean to have "multiple user
> interfaces"?
> Assumedly a device normally has only one *physical* interface (be it
> keys or
> display or whatever). Now we all agree that the mechanism must not force
> the
> device's interface to be "taken over" by an application.
> 
> One logical way to define multiple user interfaces or rather "virtual
> user
> interfaces" is to create a virtual instance of the physical instance
> that is
> active when the application/session is in focus to the user (much in the
> way
> a multiline SIP phone may work). 

THis seems reasonable. 

> There are other approaches but most of
> the
> ones I can think of are diminuitive cases of this general approach. In
> any
> case, how this interface is selected or created will largely depend on
> the
> user device and not this mechanism.

There is a subtle problem here. You indicated that the user needs to put
a particular virtual UI into focus. Doing that is only possible if there
is some display to the user that allows them to know which one it is
they need. This means there has to be a way for the application to
provide some kind of display to the user. THus, it is an issue for the
mechanism. The mechanism has to have a way to provide a display to the
user.


> 
> It is my contention therefore, that it should not be a requirement on
> the
> network application interaction mechanism to present multiple
> (prioritized)
> permutations or instances of user interfaces to an application. Rather,
> the
> relevant requirement should be:
> 
> * The mechanism should support the identification of a requesting
> application identity [e.g. application name+version @ creator's domain]
> and
> application instance [e.g. instance@ service perovider's domain].

OK.

> * The mechanism should the ability for a user interface instance to be
> shared between subscriptions (and probably applications when multiple
> applications are co-operating).

In my model, there is a one-to-one mapping of "subscriptions" to
applications.

> 
> This allows a device to create and offer virtual user interfaces as it
> sees
> fit. The application always operates on the "virtual" user interface
> instance. This is also a MUCH, MUCH simpler problem - merely one of
> identification - not presentation or negotiation (this is a highly
> complicated area already). [This approach also allows the device to
> store
> customized application-specific interfaces that can be recalled as
> required
> whenever interacting with the same application.]

No - how can the phone create custom UI for an app when it doesn't know
what the app is ahead of time? The app presents the user interface. In
the case of a phone with buttons, that means the app provides labels
that should be associated with some of the buttons. In the case of a
voice recording app, there could be one button that is labeled "start
recording" and another "stop recording". The app needs a way to tell the
phone "label one button with 'start recording' and another with 'stop
recording'. Tell me when one of these is pressed, and tell me which".
The phone can decide whether to use the two top right buttons or the
bottom left buttons; I agree on that. But, the key idea is that the app
is telling the phone information it must render to the user in order to
provide context for the button.

-Jonathan R.


-- 
Jonathan D. Rosenberg, Ph.D.            72 Eagle Rock Avenue
Chief Scientist                         First Floor
dynamicsoft                             East Hanover, NJ 07936
jdrosen@dynamicsoft.com                 FAX: (973) 952-5050
http://www.jdrosen.net                  PH:  (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 daemon@optimus.ietf.org  Thu Apr 25 03:58:50 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28769
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 03:58:50 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA15135
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 03:58:52 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA14400;
	Thu, 25 Apr 2002 03:46:04 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA14369
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 03:46:01 -0400 (EDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk [194.129.217.115])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28575
	for <sipping@ietf.org>; Thu, 25 Apr 2002 03:45:57 -0400 (EDT)
Received: from CONVERSION-DAEMON.siemenscomms.co.uk by siemenscomms.co.uk
 (PMDF V6.0-24 #45905) id <0GV4002015FNCZ@siemenscomms.co.uk> for
 sipping@ietf.org; Thu, 25 Apr 2002 08:42:59 +0100 (BST)
Received: from beex10.siemenscomms.co.uk ([137.223.246.252])
 by siemenscomms.co.uk (PMDF V6.0-24 #45905)
 with ESMTP id <0GV4000J95FNLN@siemenscomms.co.uk> for sipping@ietf.org; Thu,
 25 Apr 2002 08:42:59 +0100 (BST)
Received: by beex10.siemenscomms.co.uk with Internet Mail Service (5.5.2650.21)
	id <JMXMBJ3X>; Thu, 25 Apr 2002 08:45:29 +0100
Content-return: allowed
Date: Thu, 25 Apr 2002 08:44:56 +0100
From: "Elwell, John" <John.Elwell@siemenscomms.co.uk>
To: "'sipping@ietf.org'" <sipping@ietf.org>
Message-id: <0E644D072B76C740BC1CBD2CBB51AEFE0312E553@Beex50.siemenscomms.co.uk>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Content-Transfer-Encoding: 7BIT
Subject: [Sipping] New draft in interworking between SIP and QSIG
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7BIT

A new Internet-Draft on interworking between SIP and QSIG will shortly be
posted. In the meantime it is available in .txt and .pdf formats at:

www.ecma.ch/ecma1/topics/ietf.htm

Abstract:

	This document specifies interworking between the Session Initiation
Protocol (SIP) and QSIG within corporate networks. SIP is an Internet
application-layer control (signalling) protocol for creating, modifying, and
terminating sessions with one or more participants. These sessions include,
in particular, telephone calls. QSIG is a signalling protocol for creating,
modifying and terminating circuit-switched calls, in particular telephone
calls, within Private Integrated Services Networks (PISNs). QSIG is
specified in a number of ECMA Standards and published also as ISO/IEC
standards.

	As the support of telephony within corporate networks evolves from
circuit-switched technology to Internet technology, the two technologies
will co-exist in many networks for a period, perhaps several years.
Therefore there is a need to be able to establish, modify and terminate
sessions involving a participant in the SIP network and a participant in the
QSIG network. Such calls are supported by gateways that perform interworking
between SIP and QSIG.

	This document is a product of the authors' activities in ECMA
(www.ecma.ch) on interoperability of QSIG with IP networks.

The authors are keen to receive comments.

--------------------------------------------------------------
John Elwell (john.elwell@siemenscomms.co.uk)
Siemens Communications Limited,
--------------------------------------------------------------
	Internet communications are not secure and therefore Siemens
Communications Limited does not accept legal responsibility for the contents
of this message. Any views or opinions presented are solely those of the
author and do not necessarily represent those of Siemens Communications
Limited unless otherwise specifically stated.




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



From daemon@optimus.ietf.org  Thu Apr 25 04:18:48 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29089
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 04:18:48 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA16680
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 04:18:51 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA16163;
	Thu, 25 Apr 2002 04:07:19 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA16133
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 04:07:15 -0400 (EDT)
Received: from mail1.telekom.de (mail1.telekom.de [62.225.183.235])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28924
	for <sipping@ietf.org>; Thu, 25 Apr 2002 04:07:11 -0400 (EDT)
Received: from g9jbr.mgb01.telekom.de by G8SBV.dmz.telekom.de with ESMTP; Thu, 25 Apr 2002 10:05:20 +0200
Received: by G9JBR.mgb01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <2Q8XKRS1>; Thu, 25 Apr 2002 10:06:33 +0200
Message-Id: <A89A213731F7D51196A0000347055C83E391E3@G9JNT.mgb01.telekom.de>
From: "Alexeitsev, D" <D.Alexeitsev@telekom.de>
To: jon.peterson@neustar.biz
Cc: sipping@ietf.org
Subject: AW: [Sipping] Internet-Draft on ISUP-SIP
Date: Thu, 25 Apr 2002 10:06:32 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id EAA16135
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 8bit

Thank you for the response,

What is the rationale behind the decision to put the interworking on the standards track without interops and other requirements? Would not that create the duplication of the work that is being done by the ITU-T SG11 or even come into the case of competition between several specs?

Greeting Denis Alexeitsev

-----Ursprüngliche Nachricht-----
Von: Peterson, Jon [mailto:jon.peterson@neustar.biz]
Gesendet am: Donnerstag, 25. April 2002 01:48
An: sipping@ietf.org
Betreff: RE: [Sipping] Internet-Draft on ISUP-SIP

Actually, I stand corrected - it is apparently now intended to be a Proposed
Standard, not a BCP. My mistake.

Jon Peterson
NeuStar, Inc.


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



From daemon@optimus.ietf.org  Thu Apr 25 05:43:42 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00096
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 05:43:42 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA21385
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 05:43:45 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA20118;
	Thu, 25 Apr 2002 05:18:09 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA20088
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 05:18:05 -0400 (EDT)
Received: from oak.neustar.com (oak.neustar.com [209.173.53.70])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA29833
	for <sipping@ietf.org>; Thu, 25 Apr 2002 05:18:02 -0400 (EDT)
Received: from chiimc01.il.neustar.com (stih650b-s1p2.va.neustar.com [209.173.53.65])
	by oak.neustar.com (8.11.0/8.11.0) with ESMTP id g3P9HXH24178;
	Thu, 25 Apr 2002 05:17:33 -0400
Received: by chiimc01.il.neustar.com with Internet Mail Service (5.5.2653.19)
	id <J25ZMYVP>; Thu, 25 Apr 2002 04:17:28 -0500
Message-ID: <70565611B164D511957A001083FCDD560187027D@va02.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Alexeitsev, D'" <D.Alexeitsev@telekom.de>
Cc: sipping@ietf.org
Subject: RE: [Sipping] Internet-Draft on ISUP-SIP
Date: Thu, 25 Apr 2002 04:17:27 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id FAA20089
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 8bit

As far as I understand the IETF process, proving interoperability is not a
prerequisite for admittance to the Proposed Standard stage. Interoperability
is required before a document progresses to Draft Standard. If the SIP-T
work reaches that stage of maturity, it will not be exempt from those
requirements, I'm sure.

With regards to the work in the ITU-T, at least, I understand that they have
taken the (work in progress) IETF drafts on SIP-ISUP mapping as initial
inputs to their own process. By making these SIPPING WG items candidates for
Proposed Standard status, we enable the ITU-T to reference these documents
formally - hopefully fostering a cooperative, rather than competitive,
relationship. In my opinion, there are a number of good reasons to stage
this work in the IETF - some of them are discussed in the introduction to
sipping-sipt-01, actually.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Alexeitsev, D [mailto:D.Alexeitsev@telekom.de]
> Sent: Thursday, April 25, 2002 1:07 AM
> To: jon.peterson@neustar.biz
> Cc: sipping@ietf.org
> Subject: AW: [Sipping] Internet-Draft on ISUP-SIP
> 
> 
> Thank you for the response,
> 
> What is the rationale behind the decision to put the 
> interworking on the standards track without interops and 
> other requirements? Would not that create the duplication of 
> the work that is being done by the ITU-T SG11 or even come 
> into the case of competition between several specs?
> 
> Greeting Denis Alexeitsev
> 
> -----Ursprüngliche Nachricht-----
> Von: Peterson, Jon [mailto:jon.peterson@neustar.biz]
> Gesendet am: Donnerstag, 25. April 2002 01:48
> An: sipping@ietf.org
> Betreff: RE: [Sipping] Internet-Draft on ISUP-SIP
> 
> Actually, I stand corrected - it is apparently now intended 
> to be a Proposed
> Standard, not a BCP. My mistake.
> 
> Jon Peterson
> NeuStar, Inc.
> 

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



From daemon@optimus.ietf.org  Thu Apr 25 06:43:58 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00727
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 06:43:58 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA24257
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 06:43:59 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA23189;
	Thu, 25 Apr 2002 06:26:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA23162
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 06:26:14 -0400 (EDT)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.47])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00514
	for <sipping@ietf.org>; Thu, 25 Apr 2002 06:26:10 -0400 (EDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g3PAQ7s7003038;
	Thu, 25 Apr 2002 12:26:08 +0200 (MEST)
Received: from lmf.ericsson.se (EF5DM00K04BAV71.lmf.ericsson.se [131.160.30.98])
	by fogerty.lmf.ericsson.se (8.12.1/8.12.1/lmf.8.12.1.jcs) with ESMTP id g3PAQ7kw016414;
	Thu, 25 Apr 2002 13:26:07 +0300 (EET DST)
Message-ID: <3CC7D9B9.54D188DF@lmf.ericsson.se>
Date: Thu, 25 Apr 2002 13:26:01 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
CC: sipping@ietf.org
Subject: Re: [Sipping] I-D ACTION:draft-camarillo-sipping-reason-00.txt
References: <200204091241.IAA03423@ietf.org> <3CBC2D2C.411D97E5@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Hello Paul,

I believe the new version of Reason cover these scenarios. The only
thing we would need to define (I already said this somewhere, but I do
not remember whether it was in the SIP mailing list or here) a new
status code: no media received.

It was claimed that this may be a too specific reason code, but I still
think that it is quite general.

Regards,

Gonzalo

Paul Kyzivat wrote:
> 
> Gonzalo,
> 
> I have another possible reason for Reason:
> 
> 7. Identifying purpose of dialog refresh
> 
>    There are multiple reasons for sending a dialog refresh
>    message (e.g. reINVITE). It may be sent simply to update
>    a session timer, or it may be sent to test the signalling
>    path. In these cases the server need not do anything special.
> 
>    But another reason may be that the sender believes there is
>    some problem that might be resolved by changing something
>    at the other endpoint. For instance the sender may be
>    receiving errors attempting to send media to the receiver.
>    A change in media port at the receiving endpoint might fix
>    this problem. However there is currently no way to distinguish
>    this case from a simple refresh.
> 
> (I numbered this 7 because you have two 5s in your draft.)
> 
> There is another case I don't see mentioned, but I am not sure
> where to put it. This is the case of CANCEL or BYE used to
> drop extra call legs of a forked invite. Would like to indicate
> the difference between dropping because answered elsewhere and
> dropping because changed mind or got tired of waiting.
> This could be important to avoid later callbacks. This is similar
> to stuff in your Service Creation section, but the name seems
> wrong.
> 
>         Paul
> 
> Internet-Drafts@ietf.org wrote:
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts directories.
> >
> >         Title           : Session Initiation Protocol: Requirements on Reason
> >                           Information beyond the Status Code
> >         Author(s)       : G. Camarillo
> >         Filename        : draft-camarillo-sipping-reason-00.txt
> >         Pages           : 5
> >         Date            : 08-Apr-02
> >
> > Some applications need to know why a particular SIP message was
> > issued. This document describes those applications and provides a
> > set of requirements that a mechanism used to transport this type of
> > information has to fulfill.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-camarillo-sipping-reason-00.txt
> >
> > To remove yourself from the IETF Announcement list, send a message to
> > ietf-announce-request with the word unsubscribe in the body of the message.
> >
> > Internet-Drafts are also available by anonymous FTP. Login with the username
> > "anonymous" and a password of your e-mail address. After logging in,
> > type "cd internet-drafts" and then
> >         "get draft-camarillo-sipping-reason-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-camarillo-sipping-reason-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.
> >
> >   ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> > Content-Type: text/plain
> > Content-ID:     <20020408122729.I-D@ietf.org>
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP

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

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



From daemon@optimus.ietf.org  Thu Apr 25 08:47:14 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03819
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 08:47:14 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA03791
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 08:47:16 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA01895;
	Thu, 25 Apr 2002 08:23:39 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA01864
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 08:23:36 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02886;
	Thu, 25 Apr 2002 08:23:32 -0400 (EDT)
Message-Id: <200204251223.IAA02886@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Thu, 25 Apr 2002 08:23:31 -0400
Subject: [Sipping] I-D ACTION:draft-elwell-sipping-qsig2sip-00.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

--NextPart

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


	Title		: Interworking between SIP and QSIG
	Author(s)	: J. Elwell
	Filename	: draft-elwell-sipping-qsig2sip-00.txt
	Pages		: 43
	Date		: 25-Apr-02
	
This document specifies interworking between the Session Initiation 
Protocol (SIP) and QSIG within corporate networks. SIP is an Internet 
application-layer control (signalling) protocol for creating, 
modifying, and terminating sessions with one or more participants. 
These sessions include, in particular, telephone calls. QSIG is a 
signalling protocol for creating, modifying and terminating circuit-
switched calls, in particular telephone calls, within Private 
Integrated Services Networks (PISNs). QSIG is specified in a number 
of ECMA Standards and published also as ISO/IEC standards. 
As the support of telephony within corporate networks evolves from 
circuit-switched technology to Internet technology, the two 
technologies will co-exist in many networks for a period, perhaps 
several years. Therefore there is a need to be able to establish, 
modify and terminate sessions involving a participant in the SIP 
network and a participant in the QSIG network. Such calls are 
supported by gateways that perform interworking between SIP and QSIG. 
This document is a product of the authors' activities in ECMA 
(www.ecma.ch) on interoperability of QSIG with IP networks.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-elwell-sipping-qsig2sip-00.txt

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-elwell-sipping-qsig2sip-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-elwell-sipping-qsig2sip-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:	<20020424105147.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-elwell-sipping-qsig2sip-00.txt

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

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

--OtherAccess--

--NextPart--



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



From daemon@optimus.ietf.org  Thu Apr 25 08:51:18 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03971
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 08:51:18 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA03933
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 08:51:20 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA02022;
	Thu, 25 Apr 2002 08:24:14 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA01989
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 08:24:10 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03015;
	Thu, 25 Apr 2002 08:24:06 -0400 (EDT)
Message-Id: <200204251224.IAA03015@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Thu, 25 Apr 2002 08:24:06 -0400
Subject: [Sipping] I-D ACTION:draft-rosenberg-sipping-markup-00.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

--NextPart

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


	Title		: A Framework for Stimulus Signaling in SIP Using Markup
	Author(s)	: J. Rosenberg
	Filename	: draft-rosenberg-sipping-markup-00.txt
	Pages		: 23
	Date		: 24-Apr-02
	
In order for SIP applications to work, they will frequently need to
collect user input and provide feedback to users. Traditionally, user
input has been done in the PSTN through DTMF. Much work has occurred
on extending these DTMF models into the domain of SIP, typically by
transporting DTMF digits or user input through some SIP message to an
application server. We propose a broader framework for stimulus using
markup. The approach can support traditional DTMF user input, but
also a rich variety of devices, user interfaces and stimulus that
goes well beyond DTMF.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-rosenberg-sipping-markup-00.txt

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-rosenberg-sipping-markup-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-rosenberg-sipping-markup-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:	<20020424114515.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-rosenberg-sipping-markup-00.txt

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

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

--OtherAccess--

--NextPart--



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



From daemon@optimus.ietf.org  Thu Apr 25 09:54:20 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06197
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 09:54:20 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA08339
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 09:54:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA07096;
	Thu, 25 Apr 2002 09:35:43 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA07065
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 09:35:39 -0400 (EDT)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05371
	for <sipping@ietf.org>; Thu, 25 Apr 2002 09:35:36 -0400 (EDT)
Received: from cannon.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g3PDZQJo026654;
	Thu, 25 Apr 2002 09:35:26 -0400 (EDT)
Received: from cisco.com (dhcp-161-44-241-140.cisco.com [161.44.241.140])
	by cannon.cisco.com (Mirapoint)
	with ESMTP id AAI98179;
	Thu, 25 Apr 2002 09:38:19 -0400 (EDT)
Message-ID: <3CC80603.14C4BCC3@cisco.com>
Date: Thu, 25 Apr 2002 09:34:59 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD   (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: iwayama.noboru@jp.fujitsu.com, sipping@ietf.org
Subject: Re: [Sipping] Binding published data to services
References: <000001c1eb9e$cd4473a0$0de11dac@PINK> <3CC783EE.11D42E28@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Comments below.

	Paul

Jonathan Rosenberg wrote (reordered for convenience of discussion):
> 
> What is gained by computing this publication URL, or looking it up in a
> dynamic sysem? Surely, it is one of a bunch of different service URIs
> that will need to be configured in the UA.

I still have an open mind about this. But every new thing that must be provisioned adds to the complexity of managing devices, so schemes that don't require provisioning
are attractive.
 
> I don't see the problem in configuring a UA with the URL for supporting
> publication services. For example, consider presence publication. My UA
> would be configured to perform an HTTP POST to sip:pub.dynamicsoft.com,
> and include my SIP URI as part of a header or part of the body.

The problem seems to be a bit more than just provisioning the URL. To permit interoperation between independently built clients and presence servers, it is essential that
everything about publication technique either be provisionable or else be standard. Your description above suggests that the content of the POST must perhaps be tailored to
provide extra context to the server. (Sorry if I have misinterpretted 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



From daemon@optimus.ietf.org  Thu Apr 25 09:59:38 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06392
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 09:59:38 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA08623
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 09:59:39 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA06510;
	Thu, 25 Apr 2002 09:30:44 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA06464
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 09:30:39 -0400 (EDT)
Received: from dgesmtp02.wcom.com (dgesmtp02.wcom.com [199.249.16.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05283
	for <sipping@ietf.org>; Thu, 25 Apr 2002 09:30:35 -0400 (EDT)
Received: from CONVERSION-DAEMON by firewall.wcom.com (PMDF V5.2-33 #42261)
 id <0GV400B01LGYGI@firewall.wcom.com> for sipping@ietf.org; Thu,
 25 Apr 2002 13:29:23 +0000 (GMT)
Received: from dgismtp02.wcomnet.com ([166.38.58.142])
 by firewall.wcom.com (PMDF V5.2-33 #42261)
 with ESMTP id <0GV400B1ALGXD3@firewall.wcom.com>; Thu,
 25 Apr 2002 13:29:22 +0000 (GMT)
Received: from dgismtp02.wcomnet.com by dgismtp02.wcomnet.com
 (PMDF V5.2-33 #42263) with SMTP id <0GV400801LGTIP@dgismtp02.wcomnet.com>;
 Thu, 25 Apr 2002 13:29:21 +0000 (GMT)
Received: from ajohnston ([166.42.40.30])
 by dgismtp02.wcomnet.com (PMDF V5.2-33 #42263)
 with ESMTP id <0GV40081XLGIC8@dgismtp02.wcomnet.com>; Thu,
 25 Apr 2002 13:29:09 +0000 (GMT)
Date: Thu, 25 Apr 2002 08:28:39 -0500
From: Alan Johnston <alan.johnston@wcom.com>
Subject: RE: [Sipping] draft-ietf-sipping-call-flows-00.txt
In-reply-to: <002a01c1ea59$ea356000$ee9e82cc@ulticomdal.com>
To: "'Hussam Jarada'" <hussam.jarada@ulticomdal.com>, sipping@ietf.org
Message-id: <005a01c1ec5d$1e1c0130$1e282aa6@ajohnston>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Hi Hussan,

Your understanding is correct - these flows should have a To tag
generated by the Registrar.  I will fix it.

Thanks,
Alan Johnston
WorldCom
sip:alan@siptest.wcom.com

> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] 
> On Behalf Of Hussam Jarada
> Sent: Monday, April 22, 2002 7:01 PM
> To: sipping@ietf.org
> Subject: [Sipping] draft-ietf-sipping-call-flows-00.txt
> 
> 
> In draft-ietf-sipping-call-flows-00.txt, there's many 
> sections like section 2.1.1 and section 2.1.2 were the To 
> header field is missing tag parameter, is this a miss typed 
> error ?, I thought per bis-0.9 SIP spec that the tag 
> parameter must be added to final responses as well 
> provisional responses except 100 (which may).
> 
> Hussam Jarada
> Ulticom Inc.
> 
> 
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sip@ietf.org for new developments of core SIP
> 


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



From daemon@optimus.ietf.org  Thu Apr 25 12:04:54 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25015
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 12:04:49 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA18487
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 12:04:53 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA13643;
	Thu, 25 Apr 2002 11:14:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA13535
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 11:13:59 -0400 (EDT)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08946
	for <sipping@ietf.org>; Thu, 25 Apr 2002 11:13:50 -0400 (EDT)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id LAA08715;
	Thu, 25 Apr 2002 11:13:49 -0400 (EDT)
Received: from cs.columbia.edu (cta.cs.columbia.edu [128.59.19.46])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g3PFDi2i011902
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Thu, 25 Apr 2002 11:13:45 -0400 (EDT)
Message-ID: <3CC81D24.2D63062@cs.columbia.edu>
Date: Thu, 25 Apr 2002 11:13:40 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: iwayama.noboru@jp.fujitsu.com, sipping@ietf.org
Subject: Re: [Sipping] Binding published data to services
References: <000001c1eb9e$cd4473a0$0de11dac@PINK> <3CC783EE.11D42E28@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

To amplify earlier remarks: I think the goal should be that a SIP entity
has exactly one configurable attribute, namely the user's SIP URI (and
possibly a secret of some kind). That's easy to explain to users -
everybody knows their email address today. Anything beyond that is
likely to be error prone. (Configuring, for example, a PC to do IMAP is
very tedious - you have to remember the server address, distinguish
between SMTP and IMAP addresses, remember the directory and prefix and
whether the system uses SSL or not, plus probably some parameters I'm
not recalling right now. We don't want to go there.)

We can't assume that configurations are easily movable, so having to key
in half a dozen different, random-looking URIs when borrowing a PC for a
day is just not good design. This is even more of a problem if you have
to do this using a 12-key keypad.

While one extra URI may not seem that bad, the basic problem is that
presence is likely to be just one such URI. We already know about the
need to push CPL and to retrieve configuration information and I suspect
that conferencing will add other parameters.

This is why I like a REGISTER-based model that ties the AOR to other
URIs, by function. What exactly is the problem with that?

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



From daemon@optimus.ietf.org  Thu Apr 25 12:11:41 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25534
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 12:10:26 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA18884
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 12:10:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA13929;
	Thu, 25 Apr 2002 11:20:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA13898
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 11:20:54 -0400 (EDT)
Received: from ihemail2.firewall.lucent.com (ihemail2.lucent.com [192.11.222.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16584
	for <sipping@ietf.org>; Thu, 25 Apr 2002 11:20:49 -0400 (EDT)
Received: from ih2mail.ih.lucent.com (h135-1-241-39.lucent.com [135.1.241.39])
	by ihemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3PFKkC29904;
	Thu, 25 Apr 2002 11:20:46 -0400 (EDT)
Received: from lucent.com by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id KAA20277; Thu, 25 Apr 2002 10:20:44 -0500 (CDT)
Message-ID: <3CC81ECD.9010704@lucent.com>
Date: Thu, 25 Apr 2002 10:20:45 -0500
From: "Vijay K. Gurbani" <vkg@lucent.com>
Organization: Lucent Technologies, Inc./Bell Laboratories
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1
X-Accept-Language: en-us
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: SIPPING LIST <sipping@ietf.org>
Subject: Re: [Sipping] SIP support for IN services
References: <3CC03681.2060701@lucent.com> <3CC72423.FB1234D@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Jonathan:

Thanks for the comments; responses inline.

Jonathan Rosenberg wrote:

> I think this draft would benefit from an applicability statement of
> sorts up front. There are definitely issues with this kind of approach.
> It will pretty much require a b2bua unless the SIP element KNOWS that
> the only services involved won't require it. 


The I-D contains a statement to that effect:

    It is not the intent of this draft to specify which SIP entity shall
    operate as a SSP; however, for the sake of completeness it should be
    mentioned that this job should be performed by SIP entities at (or
    near the) core of the network instead of the SIP end points
    themselves.  To that extent, SIP entities like proxy servers and
    Back-to-Back UAs (B2BUAs) may be employed.  Generally speaking, proxy
    servers can be used for IN services that occur during a call setup or
    teardown.  For IN services requiring media handling (DTMF), B2BUAs or
    proxies that actively control media gateways will be needed.

> It is limited to services deployed in the PSTN. 


The I-D also recognizes that:

      This draft is only applicable when SIP-controlled Internet
      telephony devices are to interoperate with PSTN devices.

> I don't want the readership to believe that
> this is the IETFs preferred model for services in SIP. I know the draft
> doesn't claim that, but an applicability statement clearly saying it
> isn't would be a good thing, IMHO.

OK, no problem; just some guidance -- are applicability statements
paragraphs at the beginning of an I-D, or are they I-Ds in themselves?

Thanks,

- vijay
-- 
Vijay K. Gurbani  vkg@{lucent.com,research.bell-labs.com,acm.org}
Wireless Networks Group/Internet Software and eServices
Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440
Naperville, Illinois 60566     Voice: +1 630 224 0216


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



From daemon@optimus.ietf.org  Thu Apr 25 12:30:25 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26456
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 12:30:25 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA20346
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 12:30:29 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15737;
	Thu, 25 Apr 2002 11:44:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15704
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 11:44:27 -0400 (EDT)
Received: from gbnewp0915s1.eu.ubiquity.net (news.ubiquity.net [194.202.146.92])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA24263
	for <sipping@ietf.org>; Thu, 25 Apr 2002 11:44:23 -0400 (EDT)
Received: from mailhost.eu.ubiquity.net by gbnewp0915s1.eu.ubiquity.net
          via smtpd (for odin.ietf.org [132.151.1.176]) with SMTP; 25 Apr 2002 15:44:46 UT
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] Binding published data to services
Date: Thu, 25 Apr 2002 16:45:04 +0100
Message-ID: <45730E094814E44488F789C1CDED27AEC552E9@GBNEWP0758M.eu.ubiquity.net>
Thread-Topic: [Sipping] Binding published data to services
Thread-Index: AcHsbWTSF3V5T0gNRKCKYCVfe2m8WQAAYOCw
From: "James Undery" <jundery@ubiquity.net>
To: "Henning Schulzrinne" <hgs@cs.columbia.edu>,
        "Jonathan Rosenberg" <jdrosen@dynamicsoft.com>
Cc: <iwayama.noboru@jp.fujitsu.com>, <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA15705
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 8bit



> -----Original Message-----
> From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]

 
> This is why I like a REGISTER-based model that ties the AOR to other
> URIs, by function. What exactly is the problem with that?

The problem is how to tie the other URIs to their function i.e How do I
REGISTER to say push my CPL scripts to
http://www.example.com/scripts/james.cpl. I am concerned any REGISTER
based solution will be a hack, REGISTER like semantics would make me
happier.

James

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



From daemon@optimus.ietf.org  Thu Apr 25 12:38:15 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26675
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 12:38:11 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA21042
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 12:38:13 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA18996;
	Thu, 25 Apr 2002 12:11:57 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA18897
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 12:10:40 -0400 (EDT)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25536
	for <sipping@ietf.org>; Thu, 25 Apr 2002 12:10:34 -0400 (EDT)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id MAA13768;
	Thu, 25 Apr 2002 12:06:34 -0400 (EDT)
Received: from cs.columbia.edu (cta.cs.columbia.edu [128.59.19.46])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g3PG6S2i014442
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Thu, 25 Apr 2002 12:06:28 -0400 (EDT)
Message-ID: <3CC8297F.63DC71B5@cs.columbia.edu>
Date: Thu, 25 Apr 2002 12:06:23 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: James Undery <jundery@ubiquity.net>
CC: Jonathan Rosenberg <jdrosen@dynamicsoft.com>,
        iwayama.noboru@jp.fujitsu.com, sipping@ietf.org
Subject: Re: [Sipping] Binding published data to services
References: <45730E094814E44488F789C1CDED27AEC552E9@GBNEWP0758M.eu.ubiquity.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

> The problem is how to tie the other URIs to their function i.e How do I
> REGISTER to say push my CPL scripts to
> http://www.example.com/scripts/james.cpl. I am concerned any REGISTER
> based solution will be a hack, REGISTER like semantics would make me
> happier.

Similar to Content-Disposition and Call-Info, i.e., with a registered
tag identifying the function of the URI.

It's hard to discuss "hack quotients". Could you be more specific in
your objections?

> 
> James

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



From daemon@optimus.ietf.org  Thu Apr 25 12:43:56 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26912
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 12:43:56 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA21506
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 12:43:58 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA19676;
	Thu, 25 Apr 2002 12:23:45 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA19644
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 12:23:41 -0400 (EDT)
Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26201
	for <sipping@ietf.org>; Thu, 25 Apr 2002 12:23:36 -0400 (EDT)
Received: from m3.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0204-Fujitsu Gateway)
	id BAA15219; Fri, 26 Apr 2002 01:23:08 +0900 (JST)
	(envelope-from iwayama@flab.fujitsu.co.jp)
Received: from PINK by m3.gw.fujitsu.co.jp (8.9.3/3.7W-0204-Fujitsu Domain Master)
	id BAA28089; Fri, 26 Apr 2002 01:23:06 +0900 (JST)
	(envelope-from iwayama@flab.fujitsu.co.jp)
From: <iwayama.noboru@jp.fujitsu.com>
To: "'Ben Campbell'" <bcampbell@dynamicsoft.com>, <sipping@ietf.org>
Subject: RE: [Sipping] Binding published data to services
Date: Fri, 26 Apr 2002 01:23:05 +0900
Organization: Fujitsu Laboratories
Message-ID: <000001c1ec75$7bab09a0$e6df1dac@PINK>
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.3416
Importance: Normal
In-Reply-To: <HNEOJECGFHIABDLENMMCMEPFCGAA.bcampbell@dynamicsoft.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Ben and Jonathan,
thank you for your comments,

Jonathan's example seems to let me know on what point I am not so clear
and
what I am afraid.

It is not clear for me  why binding upload point to SIP service is
current focus of discussion.
The original proposal was on a new SIP method for data upload, and this
proposal was the starting point of
current discussion of "binding" in Minneapolis meeting.
I cannot find logical steps from the new method to binding dicussion.

I do not try to say "binding" is not important. Rather, 
it is reasonable to separate upload point from SIP service element.
Data upload point should be distinguishable from SIP service element and
the upload point should be referred by different URI from the URI of SIP
service element.
Things become more simple by this way, I think.
Is this right understanding? is there any other rational bind binding
discussion?

About authentication, I do not care about authentication for "binding
resolution" procedure.
As Ben said, it is ok to be open for public.
My concern was authentication of data upload mechanism itself.
I agree that that is out of scope of binding discussion.

Here, I was trapped in the following assumption.
Since the proposal of the new method for data publication makes use of
SIP notions,
I have assumed that the protocol used for data upload is also SIP.
With regard to this assumption, I do not see any difficulty on
authentication for data upload.
Just reuse of SIP mechanism.
Same information (password, etc) for authentication as usual SIP
transactions is utilized for data
upload SIP transaction.

However, the "binding" of URI allows us any protocol for data upload
theoretically,
and the allowed protocol may use its own security mechanism which is
different
from SIP security framework. If we can avoid this, we had better avoid.
I cannot imagine delivering two different passwords or keys, one for
data upload and one
for SIP transaction.

How about this thought?

Noboru Iwayama


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



From daemon@optimus.ietf.org  Thu Apr 25 12:45:10 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26950
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 12:45:09 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA21558
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 12:45:11 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA19465;
	Thu, 25 Apr 2002 12:20:25 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA19434
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 12:20:22 -0400 (EDT)
Received: from gbnewp0915s1.eu.ubiquity.net (news.ubiquity.net [194.202.146.92])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA26100
	for <sipping@ietf.org>; Thu, 25 Apr 2002 12:20:17 -0400 (EDT)
Received: from mailhost.eu.ubiquity.net by gbnewp0915s1.eu.ubiquity.net
          via smtpd (for odin.ietf.org [132.151.1.176]) with SMTP; 25 Apr 2002 16:20:40 UT
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] Binding published data to services
Date: Thu, 25 Apr 2002 17:20:55 +0100
Message-ID: <45730E094814E44488F789C1CDED27AEC552EA@GBNEWP0758M.eu.ubiquity.net>
Thread-Topic: [Sipping] Binding published data to services
Thread-Index: AcHsc+L733gbeCsARAK//ufmH029OQAADlXg
From: "James Undery" <jundery@ubiquity.net>
To: "Henning Schulzrinne" <hgs@cs.columbia.edu>
Cc: "Jonathan Rosenberg" <jdrosen@dynamicsoft.com>,
        <iwayama.noboru@jp.fujitsu.com>, <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id MAA19435
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 8bit



> -----Original Message-----
> From: Henning Schulzrinne [mailto:hgs@cs.columbia.edu]

> > The problem is how to tie the other URIs to their function 
> i.e How do I
> > REGISTER to say push my CPL scripts to
> > http://www.example.com/scripts/james.cpl. I am concerned 
> any REGISTER
> > based solution will be a hack, REGISTER like semantics would make me
> > happier.
> 
> Similar to Content-Disposition and Call-Info, i.e., with a registered
> tag identifying the function of the URI.

This okay we pick a tag compatible with sip, http and various others,
this means we are at risk of interfering with scheme foo.

> It's hard to discuss "hack quotients". Could you be more specific in
> your objections?

It also interfers with "Contact: *, Expires: 0" as we don't want those
function mapped URIs to be removed just the standard ones. If we don't
have this we're back to the configuration problem we were trying to
avoid. (Or thinking about it we could fetch and then restore the
function mapped URIs but I'd definately describe that as hackish and
highly non backwardly compatible.)

James

> > 
> > James
> 

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



From daemon@optimus.ietf.org  Thu Apr 25 12:55:20 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27387
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 12:55:20 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA22288
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 12:55:22 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA20971;
	Thu, 25 Apr 2002 12:35:59 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA20942
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 12:35:55 -0400 (EDT)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26638
	for <sipping@ietf.org>; Thu, 25 Apr 2002 12:35:51 -0400 (EDT)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id MAA17111;
	Thu, 25 Apr 2002 12:35:48 -0400 (EDT)
Received: from cs.columbia.edu (cta.cs.columbia.edu [128.59.19.46])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g3PGZl2i015760
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Thu, 25 Apr 2002 12:35:47 -0400 (EDT)
Message-ID: <3CC8305E.FD9D2025@cs.columbia.edu>
Date: Thu, 25 Apr 2002 12:35:42 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: James Undery <jundery@ubiquity.net>
CC: sipping@ietf.org
Subject: Re: [Sipping] Binding published data to services
References: <45730E094814E44488F789C1CDED27AEC552EA@GBNEWP0758M.eu.ubiquity.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

> 
> This okay we pick a tag compatible with sip, http and various others,
> this means we are at risk of interfering with scheme foo.

I suspect that we may have a different notion of how this would work.
I'm proposing something like

Service-Info: <http://i-am-here.com> ;service=presence,
<http://filter.com> ;service=cpl

being *returned* in the REGISTER response.


> 
> > It's hard to discuss "hack quotients". Could you be more specific in
> > your objections?
> 
> It also interfers with "Contact: *, Expires: 0" as we don't want those
> function mapped URIs to be removed just the standard ones. If we don't
> have this we're back to the configuration problem we were trying to
> avoid. (Or thinking about it we could fetch and then restore the
> function mapped URIs but I'd definately describe that as hackish and
> highly non backwardly compatible.)
> 

I'm assuming that these URLs are part of the service. The whole point is
not to have the client register anything, as the client only knows its
IP address (if it's lucky) and AOR.

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



From daemon@optimus.ietf.org  Thu Apr 25 13:39:35 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28873
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 13:39:35 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA25872
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 13:39:33 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA24451;
	Thu, 25 Apr 2002 13:20:56 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA24424
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 13:20:53 -0400 (EDT)
Received: from web11603.mail.yahoo.com (web11603.mail.yahoo.com [216.136.172.55])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA28185
	for <sipping@ietf.org>; Thu, 25 Apr 2002 13:20:50 -0400 (EDT)
Message-ID: <20020425172052.34045.qmail@web11603.mail.yahoo.com>
Received: from [207.46.137.8] by web11603.mail.yahoo.com via HTTP; Thu, 25 Apr 2002 10:20:52 PDT
Date: Thu, 25 Apr 2002 10:20:52 -0700 (PDT)
From: Sean Olson <seancolson@yahoo.com>
Subject: Re: [Sipping] Binding published data to services
To: Henning Schulzrinne <hgs@cs.columbia.edu>,
        James Undery <jundery@ubiquity.net>
Cc: sipping@ietf.org
In-Reply-To: <3CC8305E.FD9D2025@cs.columbia.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

I think there are two different models for how
this would work. One is the model where
a server (in your example, the registrar) 
creates the binding and pushes this to the client.

The other model would be where the client creates
a binding and informs the server of the binding.

I think both models are valid. Implicit in both
is that a binding is "created" and must be 
"published" to interested parties. In other words,
we are not talking about an algorithmic approach
for associating one URL with another.

The second model
could be seen as an application of the content
indirection concept (if SIP is used to push the
binding). 

The first model is 
essentially provisioning and the sticky point is
what protocol you use to do this. If SIP, how? 
If not SIP, where does this work go?

A related issue
is the time validity of this information. 
(Does it change per registration, per session, 
per device, never, etc.?)

/sean

--- Henning Schulzrinne <hgs@cs.columbia.edu> wrote:
> > 
> > This okay we pick a tag compatible with sip, http
> and various others,
> > this means we are at risk of interfering with
> scheme foo.
> 
> I suspect that we may have a different notion of how
> this would work.
> I'm proposing something like
> 
> Service-Info: <http://i-am-here.com>
> ;service=presence,
> <http://filter.com> ;service=cpl
> 
> being *returned* in the REGISTER response.
> 
> 
> > 
> > > It's hard to discuss "hack quotients". Could you
> be more specific in
> > > your objections?
> > 
> > It also interfers with "Contact: *, Expires: 0" as
> we don't want those
> > function mapped URIs to be removed just the
> standard ones. If we don't
> > have this we're back to the configuration problem
> we were trying to
> > avoid. (Or thinking about it we could fetch and
> then restore the
> > function mapped URIs but I'd definately describe
> that as hackish and
> > highly non backwardly compatible.)
> > 
> 
> I'm assuming that these URLs are part of the
> service. The whole point is
> not to have the client register anything, as the
> client only knows its
> IP address (if it's lucky) and AOR.
> 
> _______________________________________________
> Sipping mailing list 
> https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application
> of SIP
> Use sip-implementors@cs.columbia.edu for questions
> on current sip
> Use sip@ietf.org for new developments of core SIP


=====
Sean Olson <seancolson@yahoo.com>

__________________________________________________
Do You Yahoo!?
Yahoo! Games - play chess, backgammon, pool and more
http://games.yahoo.com/

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



From daemon@optimus.ietf.org  Thu Apr 25 13:47:38 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29089
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 13:47:38 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA26536
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 13:47:41 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA25425;
	Thu, 25 Apr 2002 13:32:59 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA25380
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 13:32:53 -0400 (EDT)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28639
	for <sipping@ietf.org>; Thu, 25 Apr 2002 13:32:48 -0400 (EDT)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id NAA22953;
	Thu, 25 Apr 2002 13:30:38 -0400 (EDT)
Received: from cs.columbia.edu (cta.cs.columbia.edu [128.59.19.46])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g3PHUb2i018518
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Thu, 25 Apr 2002 13:30:38 -0400 (EDT)
Message-ID: <3CC83D39.BCFEB289@cs.columbia.edu>
Date: Thu, 25 Apr 2002 13:30:33 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Sean Olson <seancolson@yahoo.com>
CC: James Undery <jundery@ubiquity.net>, sipping@ietf.org
Subject: Re: [Sipping] Binding published data to services
References: <20020425172052.34045.qmail@web11603.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Agreed. For the "client informs AOR" (since this has to be the common
reference point), the question is also what happens with this. There are
at least two cases:

- Effectively, just "cookies": the client stores and retrieves this
information, so that multiple instances affiliated with the AOR get the
same information. The server doesn't do anything except store it (and
possibly expire it).

- The information has meaning to the registrar (or the server affiliated
with it), e.g., to retrieve CPL information or to use this to retrieve
presence information.

For the "client informs server", I agree with earlier remarks that
REGISTER may not be the right thing, as it causes multiple failure modes
and you have to deal with multiple different expiration times. I think
the latter is less of an issue, as we already have multiple expiration
times for Contact headers and since REGISTER is incremental (i.e.,
things that don't get removed explicitly stay around until their time is
up, even if not refreshed each time.) Thus, there would be no problem
just refreshing a service binding or just refreshing a Contact.

Pretty clearly, this has nothing to do with Contact and should be
treated separately. However, it may well make sense to make the
semantics similar, to avoid having too many different concepts.

Sean Olson wrote:
> 
> I think there are two different models for how
> this would work. One is the model where
> a server (in your example, the registrar)
> creates the binding and pushes this to the client.
> 
> The other model would be where the client creates
> a binding and informs the server of the binding.
> 
> I think both models are valid. Implicit in both
> is that a binding is "created" and must be
> "published" to interested parties. In other words,
> we are not talking about an algorithmic approach
> for associating one URL with another.
> 
> The second model
> could be seen as an application of the content
> indirection concept (if SIP is used to push the
> binding).
> 
> The first model is
> essentially provisioning and the sticky point is
> what protocol you use to do this. If SIP, how?
> If not SIP, where does this work go?
> 
> A related issue
> is the time validity of this information.
> (Does it change per registration, per session,
> per device, never, etc.?)
> 
> /sean
> 
> --- Henning Schulzrinne <hgs@cs.columbia.edu> wrote:
> > >
> > > This okay we pick a tag compatible with sip, http
> > and various others,
> > > this means we are at risk of interfering with
> > scheme foo.
> >
> > I suspect that we may have a different notion of how
> > this would work.
> > I'm proposing something like
> >
> > Service-Info: <http://i-am-here.com>
> > ;service=presence,
> > <http://filter.com> ;service=cpl
> >
> > being *returned* in the REGISTER response.
> >
> >
> > >
> > > > It's hard to discuss "hack quotients". Could you
> > be more specific in
> > > > your objections?
> > >
> > > It also interfers with "Contact: *, Expires: 0" as
> > we don't want those
> > > function mapped URIs to be removed just the
> > standard ones. If we don't
> > > have this we're back to the configuration problem
> > we were trying to
> > > avoid. (Or thinking about it we could fetch and
> > then restore the
> > > function mapped URIs but I'd definately describe
> > that as hackish and
> > > highly non backwardly compatible.)
> > >
> >
> > I'm assuming that these URLs are part of the
> > service. The whole point is
> > not to have the client register anything, as the
> > client only knows its
> > IP address (if it's lucky) and AOR.
> >
> > _______________________________________________
> > Sipping mailing list
> > https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application
> > of SIP
> > Use sip-implementors@cs.columbia.edu for questions
> > on current sip
> > Use sip@ietf.org for new developments of core SIP
> 
> =====
> Sean Olson <seancolson@yahoo.com>
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Games - play chess, backgammon, pool and more
> http://games.yahoo.com/

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



From daemon@optimus.ietf.org  Thu Apr 25 14:21:18 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00850
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 14:21:17 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA29704
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 14:21:20 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA27283;
	Thu, 25 Apr 2002 13:59:36 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA27177
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 13:59:26 -0400 (EDT)
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29662
	for <sipping@ietf.org>; Thu, 25 Apr 2002 13:59:22 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.76])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g3PI0DLC005877;
	Thu, 25 Apr 2002 14:00:14 -0400 (EDT)
Message-ID: <3CC843DA.C420E580@dynamicsoft.com>
Date: Thu, 25 Apr 2002 13:58:50 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
CC: iwayama.noboru@jp.fujitsu.com, sipping@ietf.org
Subject: Re: [Sipping] Binding published data to services
References: <3CC80603.14C4BCC3@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit



Paul Kyzivat wrote:
> 
> Comments below.
> 
>         Paul
> 
> Jonathan Rosenberg wrote (reordered for convenience of discussion):
> >
> > What is gained by computing this publication URL, or looking it up in
> a
> > dynamic sysem? Surely, it is one of a bunch of different service URIs
> > that will need to be configured in the UA.
> 
> I still have an open mind about this. But every new thing that must be
> provisioned adds to the complexity of managing devices, so schemes that
> don't require provisioning
> are attractive.
> 
> > I don't see the problem in configuring a UA with the URL for
> supporting
> > publication services. For example, consider presence publication. My
> UA
> > would be configured to perform an HTTP POST to
> sip:pub.dynamicsoft.com,
> > and include my SIP URI as part of a header or part of the body.
> 
> The problem seems to be a bit more than just provisioning the URL. To
> permit interoperation between independently built clients and presence
> servers, it is essential that
> everything about publication technique either be provisionable or else
> be standard. Your description above suggests that the content of the
> POST must perhaps be tailored to
> provide extra context to the server. (Sorry if I have misinterpretted
> you.)

No, I wasn't proposing that it all be proprietary. Of course you need to
standardize the content of the POST as well. Right now, we are
determining how you learn that URL to make the POST to in the first
place.

-Jonathan R.

-- 
Jonathan D. Rosenberg, Ph.D.            72 Eagle Rock Avenue
Chief Scientist                         First Floor
dynamicsoft                             East Hanover, NJ 07936
jdrosen@dynamicsoft.com                 FAX: (973) 952-5050
http://www.jdrosen.net                  PH:  (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 daemon@optimus.ietf.org  Thu Apr 25 14:21:35 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00880
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 14:21:35 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA29807
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 14:21:37 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA28515;
	Thu, 25 Apr 2002 14:07:12 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA28484
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 14:07:10 -0400 (EDT)
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00068
	for <sipping@ietf.org>; Thu, 25 Apr 2002 14:07:06 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.76])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g3PI7wLC005891;
	Thu, 25 Apr 2002 14:07:58 -0400 (EDT)
Message-ID: <3CC845AC.94539322@dynamicsoft.com>
Date: Thu, 25 Apr 2002 14:06:36 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Vijay K. Gurbani" <vkg@lucent.com>
CC: SIPPING LIST <sipping@ietf.org>
Subject: Re: [Sipping] SIP support for IN services
References: <3CC81ECD.9010704@lucent.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit



"Vijay K. Gurbani" wrote:
> 
> Jonathan:
> 
> Thanks for the comments; responses inline.
> 
> Jonathan Rosenberg wrote:
> 
> > I think this draft would benefit from an applicability statement of
> > sorts up front. There are definitely issues with this kind of
> approach.
> > It will pretty much require a b2bua unless the SIP element KNOWS that
> > the only services involved won't require it.
> 
> The I-D contains a statement to that effect:
> 
>     It is not the intent of this draft to specify which SIP entity shall
>     operate as a SSP; however, for the sake of completeness it should be
>     mentioned that this job should be performed by SIP entities at (or
>     near the) core of the network instead of the SIP end points
>     themselves.  To that extent, SIP entities like proxy servers and
>     Back-to-Back UAs (B2BUAs) may be employed.  Generally speaking,
> proxy
>     servers can be used for IN services that occur during a call setup
> or
>     teardown.  For IN services requiring media handling (DTMF), B2BUAs
> or
>     proxies that actively control media gateways will be needed.

Thats just a statement of fact; what I am looking for is soemthing like
"this approach will require elements to be b2bua's. B2BUAs are frowned
upon because of their usage of call state, scalability issues, and
potential for removing service transparency".

> 
> > It is limited to services deployed in the PSTN.
> 
> The I-D also recognizes that:
> 
>       This draft is only applicable when SIP-controlled Internet
>       telephony devices are to interoperate with PSTN devices.
> 
> > I don't want the readership to believe that
> > this is the IETFs preferred model for services in SIP. I know the
> draft
> > doesn't claim that, but an applicability statement clearly saying it
> > isn't would be a good thing, IMHO.
> 
> OK, no problem; just some guidance -- are applicability statements
> paragraphs at the beginning of an I-D, or are they I-Ds in themselves?

No, they are a statement at the beginning that discusses the
applicability and problems with the approach. See the infamous privacy
draft for an example of how the applicability statement gets placed and
worded. 

I would suggest something like:

This mechanism provides a way for SIP elements to make use of IN
services defined within the PSTN. It does not represent a general model
for providing of services within SIP. The approach has several
drawbacks. It is limited to providing only services defined within the
context of IN (many of which can be implemented within SIP without usage
of IN techniques). It is limited to services associated with calls
(presence and IM have no role). It will generally require SIP elements
to act as B2BUAs, which introduces fault tolerance, scale, and service
transparency issues. 



-JOnathan R.

> 
> Thanks,
> 
> - vijay
> --
> Vijay K. Gurbani  vkg@{lucent.com,research.bell-labs.com,acm.org}
> Wireless Networks Group/Internet Software and eServices
> Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440
> Naperville, Illinois 60566     Voice: +1 630 224 0216

-- 
Jonathan D. Rosenberg, Ph.D.            72 Eagle Rock Avenue
Chief Scientist                         First Floor
dynamicsoft                             East Hanover, NJ 07936
jdrosen@dynamicsoft.com                 FAX: (973) 952-5050
http://www.jdrosen.net                  PH:  (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 daemon@optimus.ietf.org  Thu Apr 25 14:22:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00933
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 14:22:28 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA29876
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 14:22:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA28735;
	Thu, 25 Apr 2002 14:09:32 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA28704
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 14:09:28 -0400 (EDT)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00141
	for <sipping@ietf.org>; Thu, 25 Apr 2002 14:09:24 -0400 (EDT)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id OAA26458;
	Thu, 25 Apr 2002 14:09:20 -0400 (EDT)
Received: from cs.columbia.edu (cta.cs.columbia.edu [128.59.19.46])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g3PI9K2i020199
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Thu, 25 Apr 2002 14:09:20 -0400 (EDT)
Message-ID: <3CC8464B.3488B06F@cs.columbia.edu>
Date: Thu, 25 Apr 2002 14:09:15 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: James Undery <jundery@ubiquity.net>, sipping@ietf.org
Subject: Re: [Sipping] Binding published data to services
References: <3CC8305E.FD9D2025@cs.columbia.edu> <3CC84375.F7A4D5AD@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

The problem I have is that you have to bootstrap somehow from the only
thing that the SIP entity knows, its AOR. "Somehow" just doesn't cut it
for me. I think the REGISTER response has the right semantics, since
it's tied to the AOR. It might be helpful to enumerate the alternatives
and see what the trade-offs are. (Manual configuration is always one,
but it better not be the only one.)

> Ah. To me, this is "configuration". I would certainly not propose that a
> user type in anything. Rather, this is one of many parameters that need
> to be read into the phone when it starts up. What I was arguing for is
> exactly the approach you are talking about here, although I am not
> entirely sure that the information is returned in a register response,
> as opposed to through some other configuration bootstrap approach.
>

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



From daemon@optimus.ietf.org  Thu Apr 25 14:26:04 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01035
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 14:26:04 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA00190
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 14:26:06 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA27064;
	Thu, 25 Apr 2002 13:58:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA27033
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 13:58:14 -0400 (EDT)
Received: from mail3.dynamicsoft.com ([63.113.44.69])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29585
	for <sipping@ietf.org>; Thu, 25 Apr 2002 13:58:11 -0400 (EDT)
Received: from dynamicsoft.com ([63.113.46.76])
	by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g3PHwWLC005868;
	Thu, 25 Apr 2002 13:58:32 -0400 (EDT)
Message-ID: <3CC84375.F7A4D5AD@dynamicsoft.com>
Date: Thu, 25 Apr 2002 13:57:09 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Henning Schulzrinne <hgs@cs.columbia.edu>
CC: James Undery <jundery@ubiquity.net>, sipping@ietf.org
Subject: Re: [Sipping] Binding published data to services
References: <3CC8305E.FD9D2025@cs.columbia.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit



Henning Schulzrinne wrote:
> 
> >
> > This okay we pick a tag compatible with sip, http and various others,
> > this means we are at risk of interfering with scheme foo.
> 
> I suspect that we may have a different notion of how this would work.
> I'm proposing something like
> 
> Service-Info: <http://i-am-here.com> ;service=presence,
> <http://filter.com> ;service=cpl
> 
> being *returned* in the REGISTER response.

Ah. To me, this is "configuration". I would certainly not propose that a
user type in anything. Rather, this is one of many parameters that need
to be read into the phone when it starts up. What I was arguing for is
exactly the approach you are talking about here, although I am not
entirely sure that the information is returned in a register response,
as opposed to through some other configuration bootstrap approach. 

-Jonathan R.

-- 
Jonathan D. Rosenberg, Ph.D.            72 Eagle Rock Avenue
Chief Scientist                         First Floor
dynamicsoft                             East Hanover, NJ 07936
jdrosen@dynamicsoft.com                 FAX: (973) 952-5050
http://www.jdrosen.net                  PH:  (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 daemon@optimus.ietf.org  Thu Apr 25 14:29:51 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01143
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 14:29:51 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA00347
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 14:29:53 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA26415;
	Thu, 25 Apr 2002 13:46:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA26380
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 13:46:34 -0400 (EDT)
Received: from zrc2s0jx.us.nortel.com (zrc2s0jx.nortelnetworks.com [47.103.122.112])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29034
	for <sipping@ietf.org>; Thu, 25 Apr 2002 13:46:18 -0400 (EDT)
Received: from zrc2c011.us.nortel.com (zrc2c011.us.nortel.com [47.103.120.51])
	by zrc2s0jx.us.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3PHjpj27706
	for <sipping@ietf.org>; Thu, 25 Apr 2002 12:45:51 -0500 (CDT)
Received: by zrc2c011.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <J4K5TQ09>; Thu, 25 Apr 2002 12:42:50 -0500
Message-ID: <1B54FA3A2709D51195C800508BF9386A03DE3A44@zrc2c000.us.nortel.com>
From: "Mary Barnes"<mbarnes@nortelnetworks.com>
To: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: FW: [Sipping] I-D ACTION:draft-watson-sipping-req-history-01.txt
Date: Thu, 25 Apr 2002 12:42:48 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C1EC80.9D486160"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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_01C1EC80.9D486160
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1EC80.9D486160"


------_=_NextPart_001_01C1EC80.9D486160
Content-Type: text/plain;
	charset="iso-8859-1"

Hi all,

We'd like to receive some feedback on our updated draft for the "Generic
Request History Capability" which appeared in the archives the end of last
week.

We have tried to incorporate/address all the concerns which were raised
around this draft via email and during discussions in Minneapolis:

1. An appendix has been added to include some example scenarios.

2. We've pruned the requirements a bit in an effort to make them more
concise and explicit, hopefully resolving some of the previous
misunderstandings.

3. We've added a section that highlights additional considerations
introduced by specific requirements, some of which will need to be further
clarified by the specific application making use of this capability. 

As the conclusion of the draft suggests, we'd like to get WG concensus on
these requirements so that we can progress to the next step which would be
to evaluate solution options. 

Regards,
Mary H. Barnes
mbarnes@nortelnetworks.com
972-684-5432
Wireless 817-703-4806

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: Friday, April 19, 2002 6:23 AM
Cc: sipping@ietf.org
Subject: [Sipping] I-D ACTION:draft-watson-sipping-req-history-01.txt


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


	Title		: Generic Request History Capability - Requirements
	Author(s)	: M. Watson, M. Barnes, C. Jennings, J. Peterson
	Filename	: draft-watson-sipping-req-history-01.txt
	Pages		: 10
	Date		: 18-Apr-02
	
Many services that SIP is anticipated to support require the 
ability to determine why and how the call arrived at a specific 
application.  Examples of such services include (but are not 
limited to) sessions initiated to call centers via 'click to talk' 
SIP URLs on a web page, 'call history/logging' style services 
within intelligent 'call management' software for SIP UAs and calls 
to voicemail servers and call centers.  While SIP implicitly 
provides the redirect/retarget capabilities that enable calls to be 
routed to chosen applications, there is currently no standard 
mechanism within SIP for communicating the history of such a 
request. This 'request history' information allows the receiving 
application to determine hints about how and why the call arrived 
at the application/user.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-watson-sipping-req-history-01.txt

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-watson-sipping-req-history-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-watson-sipping-req-history-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_001_01C1EC80.9D486160
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>FW: [Sipping] I-D =
ACTION:draft-watson-sipping-req-history-01.txt</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Hi all,</FONT>
</P>

<P><FONT SIZE=3D2>We'd like to receive some feedback on our updated =
draft for the &quot;Generic Request History Capability&quot; which =
appeared in the archives the end of last week.</FONT></P>

<P><FONT SIZE=3D2>We have tried to incorporate/address all the concerns =
which were raised around this draft via email and during discussions in =
Minneapolis:</FONT></P>

<P><FONT SIZE=3D2>1. An appendix has been added to include some example =
scenarios.</FONT>
</P>

<P><FONT SIZE=3D2>2. We've pruned the requirements a bit in an effort =
to make them more concise and explicit, hopefully resolving some of the =
previous misunderstandings.</FONT></P>

<P><FONT SIZE=3D2>3. We've added a section that highlights additional =
considerations introduced by specific requirements, some of which will =
need to be further clarified by the specific application making use of =
this capability. </FONT></P>

<P><FONT SIZE=3D2>As the conclusion of the draft suggests, we'd like to =
get WG concensus on these requirements so that we can progress to the =
next step which would be to evaluate solution options. </FONT></P>

<P><FONT SIZE=3D2>Regards,</FONT>
<BR><FONT SIZE=3D2>Mary H. Barnes</FONT>
<BR><FONT SIZE=3D2>mbarnes@nortelnetworks.com</FONT>
<BR><FONT SIZE=3D2>972-684-5432</FONT>
<BR><FONT SIZE=3D2>Wireless 817-703-4806</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Internet-Drafts@ietf.org [<A =
HREF=3D"mailto:Internet-Drafts@ietf.org">mailto:Internet-Drafts@ietf.org=
</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Friday, April 19, 2002 6:23 AM</FONT>
<BR><FONT SIZE=3D2>Cc: sipping@ietf.org</FONT>
<BR><FONT SIZE=3D2>Subject: [Sipping] I-D =
ACTION:draft-watson-sipping-req-history-01.txt</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>A New Internet-Draft is available from the on-line =
Internet-Drafts directories.</FONT>
</P>
<BR>

<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>Title&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
Generic Request History Capability - Requirements</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : M. Watson, M. =
Barnes, C. Jennings, J. Peterson</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
draft-watson-sipping-req-history-01.txt</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>Pages&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =
10</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>Date&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 18-Apr-02</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
<BR><FONT SIZE=3D2>Many services that SIP is anticipated to support =
require the </FONT>
<BR><FONT SIZE=3D2>ability to determine why and how the call arrived at =
a specific </FONT>
<BR><FONT SIZE=3D2>application.&nbsp; Examples of such services include =
(but are not </FONT>
<BR><FONT SIZE=3D2>limited to) sessions initiated to call centers via =
'click to talk' </FONT>
<BR><FONT SIZE=3D2>SIP URLs on a web page, 'call history/logging' style =
services </FONT>
<BR><FONT SIZE=3D2>within intelligent 'call management' software for =
SIP UAs and calls </FONT>
<BR><FONT SIZE=3D2>to voicemail servers and call centers.&nbsp; While =
SIP implicitly </FONT>
<BR><FONT SIZE=3D2>provides the redirect/retarget capabilities that =
enable calls to be </FONT>
<BR><FONT SIZE=3D2>routed to chosen applications, there is currently no =
standard </FONT>
<BR><FONT SIZE=3D2>mechanism within SIP for communicating the history =
of such a </FONT>
<BR><FONT SIZE=3D2>request. This 'request history' information allows =
the receiving </FONT>
<BR><FONT SIZE=3D2>application to determine hints about how and why the =
call arrived </FONT>
<BR><FONT SIZE=3D2>at the application/user.</FONT>
</P>

<P><FONT SIZE=3D2>A URL for this Internet-Draft is:</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-watson-sipping-req-his=
tory-01.txt" =
TARGET=3D"_blank">http://www.ietf.org/internet-drafts/draft-watson-sippi=
ng-req-history-01.txt</A></FONT>
</P>

<P><FONT SIZE=3D2>To remove yourself from the IETF Announcement list, =
send a message to </FONT>
<BR><FONT SIZE=3D2>ietf-announce-request with the word unsubscribe in =
the body of the message.</FONT>
</P>

<P><FONT SIZE=3D2>Internet-Drafts are also available by anonymous FTP. =
Login with the username</FONT>
<BR><FONT SIZE=3D2>&quot;anonymous&quot; and a password of your e-mail =
address. After logging in,</FONT>
<BR><FONT SIZE=3D2>type &quot;cd internet-drafts&quot; and then</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>&quot;get =
draft-watson-sipping-req-history-01.txt&quot;.</FONT>
</P>

<P><FONT SIZE=3D2>A list of Internet-Drafts directories can be found =
in</FONT>
<BR><FONT SIZE=3D2><A HREF=3D"http://www.ietf.org/shadow.html" =
TARGET=3D"_blank">http://www.ietf.org/shadow.html</A> </FONT>
<BR><FONT SIZE=3D2>or <A =
HREF=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" =
TARGET=3D"_blank">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</A></FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Internet-Drafts can also be obtained by =
e-mail.</FONT>
</P>

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

<P><FONT FACE=3D"Arial" SIZE=3D2 COLOR=3D"#000000"></FONT>&nbsp;

</BODY>
</HTML>
------_=_NextPart_001_01C1EC80.9D486160--

------_=_NextPart_000_01C1EC80.9D486160
Content-Type: message/rfc822

To: 
Subject: 
Date: Thu, 25 Apr 2002 12:42:50 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_002_01C1EC80.9D486160"


------_=_NextPart_002_01C1EC80.9D486160
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_003_01C1EC80.9D486160"


------_=_NextPart_003_01C1EC80.9D486160
Content-Type: text/plain



------_=_NextPart_003_01C1EC80.9D486160
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.89">
<TITLE></TITLE>
</HEAD>
<BODY>

<P><FONT FACE="Arial" SIZE=2 COLOR="#000000"></FONT><FONT FACE="Arial" SIZE=2 COLOR="#000000"></FONT>&nbsp;

</BODY>
</HTML>
------_=_NextPart_003_01C1EC80.9D486160--

------_=_NextPart_002_01C1EC80.9D486160
Content-Type: application/octet-stream;
	name="ATT93244"
Content-Disposition: attachment;
	filename="ATT93244"

Content-type: message/external-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-watson-sipping-req-history-01.txt

------_=_NextPart_002_01C1EC80.9D486160
Content-Type: message/external-body;
	site="internet-drafts";
	dir="draft-watson-sipping-req-history-01";
	mode="ftp.ietf.org";
	access-type="anon-ftp"


------_=_NextPart_002_01C1EC80.9D486160--

------_=_NextPart_000_01C1EC80.9D486160--

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



From daemon@optimus.ietf.org  Thu Apr 25 15:38:13 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03582
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 15:38:12 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA05133
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 15:38:15 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA04113;
	Thu, 25 Apr 2002 15:25:38 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA04078
	for <sipping@optimus.ietf.org>; Thu, 25 Apr 2002 15:25:34 -0400 (EDT)
Received: from auemail1.firewall.lucent.com (auemail1.lucent.com [192.11.223.161])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03076
	for <sipping@ietf.org>; Thu, 25 Apr 2002 15:25:27 -0400 (EDT)
Received: from ih2mail.ih.lucent.com (h135-1-241-39.lucent.com [135.1.241.39])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3PJOrt18480;
	Thu, 25 Apr 2002 15:24:54 -0400 (EDT)
Received: from lucent.com by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id OAA15906; Thu, 25 Apr 2002 14:24:51 -0500 (CDT)
Message-ID: <3CC85804.10506@lucent.com>
Date: Thu, 25 Apr 2002 14:24:52 -0500
From: "Vijay K. Gurbani" <vkg@lucent.com>
Organization: Lucent Technologies, Inc./Bell Laboratories
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1
X-Accept-Language: en-us
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: SIPPING LIST <sipping@ietf.org>
Subject: Re: [Sipping] SIP support for IN services
References: <3CC81ECD.9010704@lucent.com> <3CC845AC.94539322@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Jonathan Rosenberg wrote:
[...]
 > I would suggest something like:

Jonathan:

Some feedback on your suggestion:


> This mechanism provides a way for SIP elements to make use of 

> IN services defined within the PSTN. It does not represent a 

> general model for providing of services within SIP. 


This is fine -- there are several models for providing service in SIP;
this happens to a specific model that can be used when interworking
with the PSTN.

> The approach has several drawbacks. It is limited to providing 

> only services defined within the context of IN (many of which can 

> be implemented within SIP without usage of IN techniques). 


This I don't agree with, IMHO.  The prior example of using ENUM to
resolve a 800 number does not fit an IN service, in my mind anyway.
ENUM operates in the Internet; a DNS server is consulted, not a
PSTN data repository, for instance.  The approach outlined in the
I-D has the advantage that the data being accessed is in the PSTN
domain and is accessed transparently from the Internet.  While not
technically impossible, why duplicate the all the 800 number databases
in the Internet if we can access them transparently from the PSTN?

> It is limited to services associated with calls
> (presence and IM have no role). It will generally require SIP elements
> to act as B2BUAs, which introduces fault tolerance, scale, and service
> transparency issues. 


The travails of a B2BUA are well documented in the SIP/SIPPING WG
email lists.  I am neither condoning nor endangering its use.  I
simply list it as a possible SIP entity where certain services can
be provided, without saying that an implementor MUST use a B2BUA.

Thanks,


- vijay

--
Vijay K. Gurbani  vkg@{lucent.com,research.bell-labs.com,acm.org}
Wireless Networks Group/Internet Software and eServices
Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440
Naperville, Illinois 60566     Voice: +1 630 224 0216


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



From daemon@ns.ietf.org  Thu Apr 25 18:29:41 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08126
	for <sipping-archive@odin.ietf.org>; Thu, 25 Apr 2002 18:29:35 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA16136
	for sipping-archive@odin.ietf.org; Thu, 25 Apr 2002 18:29:39 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA15134;
	Thu, 25 Apr 2002 18:08:18 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA15099
	for <sipping@ns.ietf.org>; Thu, 25 Apr 2002 18:08:10 -0400 (EDT)
Received: from imo-r06.mx.aol.com (imo-r06.mx.aol.com [152.163.225.102])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07671
	for <sipping@ietf.org>; Thu, 25 Apr 2002 18:08:05 -0400 (EDT)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r06.mx.aol.com (mail_out_v32.5.) id r.a3.27621d64 (4394);
	Thu, 25 Apr 2002 18:07:25 -0400 (EDT)
Message-ID: <a3.27621d64.29f9d81d@aol.com>
Date: Thu, 25 Apr 2002 18:07:25 EDT
Subject: Re: [Sipping] new I-D on markup languages for DTMF and user input
To: jdrosen@dynamicsoft.com, sipping@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_a3.27621d64.29f9d81d_boundary"
X-Mailer: AOL 6.0 for Windows US sub 10524
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


--part1_a3.27621d64.29f9d81d_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 4/24/02 11:34:18 AM Eastern Daylight Time, 
jdrosen@dynamicsoft.com writes:


> Comments and questions welcome as always.
> 
> 

So here are some thoughts on the subject:

1. 2nd para says: "stimulus signaling in the PSTN has traditionally been done 
through DTMF input and with speech recognition." In fact, it has been done 
through "digit" input, whether DTMF or dial pulse. On/off hook signaling is 
also used, for example, hookswitch flashes. But what is defined in this draft 
better ignore dial pulse and hookswitch flashes.

Since the point of having DML is to eliminate the need to actually generate 
DTMF tones in a phone and send them to the network, it appears that this plan 
requires only that the phone have an appropriate keypad, maybe 12 buttons 
like a DTMF keypad, but maybe more like the keypad on a computer keyboard or 
some other arrangement. Note that requirement R8 in Section 5 says that "the 
mechanisms must support user indications via keys or buttons and at the very 
least must define support for user interaction via a standard, generic 
computer keyboard." One could even envision a nostalgia-evoking black SIP 
phone with a rotary dial ! In any case, it would no longer be based on actual 
use of DTMF, so the markup language should not be called "DTMF". How about 
Digit-entry Markup Language?

3. To make DML useful in some situations to solve the excessive delay of 
other techniques, it could also provide capabilities to apply and remove dial 
tones at specific places in the digit map, but that is obviously going beyond 
the intent.

For example, in the example for 91xxx... in 3.2, actual use requires that the 
first dial tone be removed as soon as the 9 starts, a second dial tone be 
applied after the 9 and removed as soon as the 1 starts. In practice, the 
dial tone from before the 9 could just be left until the 1 and the user won't 
notice, but there are applications which require a different dial tone for 
these two parts. MGC apparently has trouble doing this.

3.2 In the examples it is unknown why "T" is appended to some of the entries 
(copied from RFC 2705). These are not included in H.248, but the application 
of timers is covered by the procedures. In any case, no timeout would be 
applied after "00" in this dial plan. (Incidentally, I know of no place where 
this dial plan would be valid. Access to a long distance operator from inside 
a PBX would typically require dialing 9 and 00.)

In the example for 9011x.T, as in RFC 2705, there is no provision to know 
that dialing is complete when it gets to 15 digits. The user could dial 
forever, and the UA would be required to store all the digits. If multiple 
potentially matching strings are processed as defined in H.248, then there 
should be multiple conditions as follows to limit digit collection to 15 
after the 9011:

9011xxxxxxxxxxxxxxx (15 x's)
9011x .

According to the procedures, this would result in application of a short 
timeout after each digit after 9011x since, at this point, the dialed string 
may match either condition. In fact, in traditional telephony 
implementations, this short time-out is not applied until some minimum number 
of digits have been received to prevent incorrectly timing out. It is only 
applied at the specific ambiguous points in the digit string. MGC/H.248 do 
not appear to include a way to do this without generation of huge digit maps. 
While a Gateway could easily store such large maps, it seem infeasible to 
download them to UAs for each call setup (just in case the user dials an 
international call).

4.1 With a UA supporting DML, there is no longer a need for the entry of the 
"pound" to actually be "long". Local detection of a key press separate from 
the actual voice channel eliminates the need for the key depression to be 
"long". It was long in the traditional model only to allow more precise 
detection of the tone pair in the presence of speech and to allow a single 
device to look for it on many simultaneous calls.

4.1.3. The third sentence should read "However, once the call is established, 
the indication of the desire to place a second call (possibly by the entry of 
the pound key on the DTMF keypad) is detected at the client with DML." 

The first full sentence under Figure 3 would be clearer if it read: "The 
script that is returned (8) causes the VoiceXML server to generate audible 
prompts to ask the user to enter ..." Again, the references in this paragraph 
to "listen for a long pound" and "enters a long pound" should be changed.

It isn't clear how a UA can handle both cases that require DML and those that 
don't. In the examples given, it may be assumed that, when normal calls are 
placed, the UA actually sends DTMF tones corresponding to the pressing of 
buttons (as implied in Section 4.1.3). This would be used to support 
traditional services that did not use DML. In other cases, the UA must buffer 
the keypad presses until it gets the appropriate DML script to tell it what 
to do. The whole point of DML is that the UA doesn't understand the service 
being provided, so it would need to be told when to apply each procedure.

Mike Pierce
Artel

--part1_a3.27621d64.29f9d81d_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 4/24/02 11:34:18 AM Eastern Daylight Time, jdrosen@dynamicsoft.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Comments and questions welcome as always.
<BR>
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>So here are some thoughts on the subject:
<BR>
<BR>1. 2nd para says: "stimulus signaling in the PSTN has traditionally been done through DTMF input and with speech recognition." In fact, it has been done through "digit" input, whether DTMF or dial pulse. On/off hook signaling is also used, for example, hookswitch flashes. But what is defined in this draft better ignore dial pulse and hookswitch flashes.
<BR>
<BR>Since the point of having DML is to eliminate the need to actually generate DTMF tones in a phone and send them to the network, it appears that this plan requires only that the phone have an appropriate keypad, maybe 12 buttons like a DTMF keypad, but maybe more like the keypad on a computer keyboard or some other arrangement. Note that requirement R8 in Section 5 says that "the mechanisms must support user indications via keys or buttons and at the very least must define support for user interaction via a standard, generic computer keyboard." One could even envision a nostalgia-evoking black SIP phone with a rotary dial ! In any case, it would no longer be based on actual use of DTMF, so the markup language should not be called "DTMF". How about Digit-entry Markup Language?
<BR>
<BR>3. To make DML useful in some situations to solve the excessive delay of other techniques, it could also provide capabilities to apply and remove dial tones at specific places in the digit map, but that is obviously going beyond the intent.
<BR>
<BR>For example, in the example for 91xxx... in 3.2, actual use requires that the first dial tone be removed as soon as the 9 starts, a second dial tone be applied after the 9 and removed as soon as the 1 starts. In practice, the dial tone from before the 9 could just be left until the 1 and the user won't notice, but there are applications which require a different dial tone for these two parts. MGC apparently has trouble doing this.
<BR>
<BR>3.2 In the examples it is unknown why "T" is appended to some of the entries (copied from RFC 2705). These are not included in H.248, but the application of timers is covered by the procedures. In any case, no timeout would be applied after "00" in this dial plan. (Incidentally, I know of no place where this dial plan would be valid. Access to a long distance operator from inside a PBX would typically require dialing 9 and 00.)
<BR>
<BR>In the example for 9011x.T, as in RFC 2705, there is no provision to know that dialing is complete when it gets to 15 digits. The user could dial forever, and the UA would be required to store all the digits. If multiple potentially matching strings are processed as defined in H.248, then there should be multiple conditions as follows to limit digit collection to 15 after the 9011:
<BR>
<BR>9011xxxxxxxxxxxxxxx (15 x's)
<BR>9011x .
<BR>
<BR>According to the procedures, this would result in application of a short timeout after each digit after 9011x since, at this point, the dialed string may match either condition. In fact, in traditional telephony implementations, this short time-out is not applied until some minimum number of digits have been received to prevent incorrectly timing out. It is only applied at the specific ambiguous points in the digit string. MGC/H.248 do not appear to include a way to do this without generation of huge digit maps. While a Gateway could easily store such large maps, it seem infeasible to download them to UAs for each call setup (just in case the user dials an international call).
<BR>
<BR>4.1 With a UA supporting DML, there is no longer a need for the entry of the "pound" to actually be "long". Local detection of a key press separate from the actual voice channel eliminates the need for the key depression to be "long". It was long in the traditional model only to allow more precise detection of the tone pair in the presence of speech and to allow a single device to look for it on many simultaneous calls.
<BR>
<BR>4.1.3. The third sentence should read "However, once the call is established, the indication of the desire to place a second call (possibly by the entry of the pound key on the DTMF keypad) is detected at the client with DML." 
<BR>
<BR>The first full sentence under Figure 3 would be clearer if it read: "The script that is returned (8) causes the VoiceXML server to generate audible prompts to ask the user to enter ..." Again, the references in this paragraph to "listen for a long pound" and "enters a long pound" should be changed.
<BR>
<BR>It isn't clear how a UA can handle both cases that require DML and those that don't. In the examples given, it may be assumed that, when normal calls are placed, the UA actually sends DTMF tones corresponding to the pressing of buttons (as implied in Section 4.1.3). This would be used to support traditional services that did not use DML. In other cases, the UA must buffer the keypad presses until it gets the appropriate DML script to tell it what to do. The whole point of DML is that the UA doesn't understand the service being provided, so it would need to be told when to apply each procedure.
<BR>
<BR>Mike Pierce
<BR>Artel</FONT></HTML>

--part1_a3.27621d64.29f9d81d_boundary--

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



From daemon@optimus.ietf.org  Fri Apr 26 05:32:30 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28135
	for <sipping-archive@odin.ietf.org>; Fri, 26 Apr 2002 05:32:29 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA27407
	for sipping-archive@odin.ietf.org; Fri, 26 Apr 2002 05:32:33 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA25341;
	Fri, 26 Apr 2002 04:59:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA25238
	for <sipping@optimus.ietf.org>; Fri, 26 Apr 2002 04:59:25 -0400 (EDT)
Received: from exchange1.nuera.com ([12.105.228.79])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27667
	for <sipping@ietf.org>; Fri, 26 Apr 2002 04:59:21 -0400 (EDT)
Received: by exchange1.nuera.com with Internet Mail Service (5.5.2653.19)
	id <JK3N5VWR>; Fri, 26 Apr 2002 01:59:29 -0700
Message-ID: <E79883AEA37FD411A58C00508BAC5F4B01D38CB8@exchange1.nuera.com>
From: "Fairlie-Cuninghame, Robert" <rfairlie@nuera.com>
To: "'jdrosen@dynamicsoft.com'" <jdrosen@dynamicsoft.com>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Date: Fri, 26 Apr 2002 01:59:29 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sipping] RE:  I-D   ACTION:draft-culpepper-sipping-app-interact-reqs-00.tx
 t
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Hi Jonathan,

I agree that your approach has a degree of elegance for in handling
user-presentation aspects. However, I think that there are problems with
some areas of your mechanism (as written). I have yet to fully cogitate the
implications. I guess Bert, JF & myself also need to discuss the future
direction of our proposal. 

Hopefully there will be a way to bring out the best of both proposals. As I
see there are definite advantages of both schemes (and not necessarily
mutually exclusive). 

Foremost in my mind is the fact that there is no way an application can
indicate a change or end of a markup/interface (e.g. revoke or update the
markup when the application closes or updates). This is something that is
inherently possible in a subscription (e.g., for stimuli) but awkward in a
traditional markup paradigm [which is more designed for ongoing applications
where all the interaction is through the markup]. 

I don't see any reason that it wouldn't be possible to place the markup in a
subscription .... or rather, I think perhaps a session is more appropriate
than a subscription for this model.

When you think about it, your user-interface is really a session - an
applications wants to setup the presentation/stimuli, possibly periodically
update it and eventually close it. Perhaps it would be possible to have a
SIP session wrapper around an HTML/DML (or any other markup) reference so
that the application can re-INVITE or BYE it. This would also solve a couple
of OPEN ISSUEs in your draft of enacting and associating/authenticating
markup updates. There's issues in doing this as well but its worth further
thought [and could replace the need for App-Info header with the use of a
Join operation].

One limitation of the current proposal which I believe that needs to be
either accepted or addressed is how to retrieve *specific* information about
the device's user interface. This information goes beyond what would be
classified as device capabilities and user preferences (CC/PP) information
but rather would be "on-demand" information about a particular stimulus. For
example, if an application may want to know the physical label for a
particular key or perhaps the state of a device widget (e.g. volume control,
switch, etc). [HTTP GET? by application to user provided reference]

A minor quibble that I'll raise at this time: If it's decided that the best
approach is to have a separate DML markup just for phone keys [a simplified
subset of full key-based input] (which doesn't sound too unreasonable to
me), then in DML I see no justification for implementing the complicated
digit map logic that MGCP or Megaco allows. This was designed to allow
complicated number matching schemes to avoid post-dial delay which is not a
problem for most applications (and here, digit accumulation does not justify
the complexity either IMO). DML should just allow immediate or stop-and-wait
notification of supported stimuli (*,#,0-9,L and any other telephony related
stimuli allowed) - this makes the UA devices a lot simpler (which is the
whole point of DML). Anyway, this is a minor issue that has no bearing on
the larger model.

Thanks for your responses to the previous mails. I will answer them in
another email.

Regards,

Robert.

> -----Original Message-----
> From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com]
> Sent: Thursday, April 25, 2002 6:19 AM
> To: Fairlie-Cuninghame, Robert
> Cc: sipping@ietf.org; 'Bert Culpepper'
> Subject: Re: [Sipping] I-D
> ACTION:draft-culpepper-sipping-app-interact-reqs-00.txt
> 
> 
> inline.
> 
> "Fairlie-Cuninghame, Robert" wrote:
> > 
> 
> > > > R5:  A network entity desiring user indications must be able to
> > > >         request user indications from another network 
> entity.  The
> > > >         entity receiving a request must be able to 
> respond with its
> > > >         capability/intent to transmit user indications.
> > >
> > > We should be more specific here. We have a caller and a
> > > callee. I think
> > > that by "entity" you mean one of those two.
> > 
> > No, we are purposefully not restricting the mechanism to 
> only caller and
> > callee (or even proxy). So, yes, I agree we need to re-word to
> > explicitly
> > define. Further discussion later.
> 
> That doesn't make sense to me. By definition, user input indication is
> possible only from a human, NOT from an automata. An automata can try
> (web screen scraping...) but that is a known bad thing.
> 
> > > > R15: The receiving application must be able to detect 
> user activity
> > > >         indication loss due to packet loss from received
> > > user activity
> > > >         indications.
> > >
> > > I don't know what this means.
> > 
> > Detecting missing indications.  For example, a PIN is 
> transmitted one
> > digit
> > at a time.  If one message (network packet) gets lost, we want to be
> > able to
> > determine this at the receiver. Will re-word.
> 
> There is an implicit assumption here of UDP based notifications and/or
> notifications that are not stop-and-wait. I think the real requirement
> you want here is ordering - events are delivered to the 
> observer in the
> same order they occurred at the reporter.
> 
> 
> > 
> > >
> > > > D4:  The mechanism should support routing and
> > > identification that is
> > > >         compatible with use in a SIP-based network.
> > >
> > > This is too vague to be useful.
> > >
> > 
> > Are you suggesting we reword or simply drop ? Can you 
> suggest anything
> > more
> > useful/specific?
> 
> I am suggesting to drop unless you can define more 
> specifically what the
> requirement is.
> 
> 
> > > * The mechanism should support devices that possess a UI, 
> and those
> > > which do not possess a UI
> > 
> > Jonathan can you please explain exactly what you mean by this. My
> > feeling is
> > that this is the crux of your new requirements, yet I don't 
> have a clear
> > idea of what you mean by "The mechanism should support 
> devices ... which
> > do
> > not possess a UI."
> 
> Hopefully the recent draft on markup I just submitted explains better.
> The basic idea is that there are many devices that have the ability to
> interact with the user. There could, for example, be a display with
> buttons. The display would present the user with choices, and the user
> would press a button, causing a notification to be sent into the
> network. This is in contrast with devices, like a traditional 
> dumb black
> phone, which have no ability to interact with the user. There is no
> display. There is no way to know, when a user presses a DTMF key, what
> application they were trying to interact with. 
> 
> 
> > 
> > By this requirement, do you mean
> > 1) The mechanism should allow an application to present a 
> virtual user
> > interface and/or the transport of user indications on the virtual
> > interface
> > (when a device has no physical interface aside from a display and
> > possibly a
> > touch-screen or pointing device); or
> > 2) the mechanism should allow an application to determine 
> that a device
> > has
> > no physical interface aside from a display (and possibly a 
> touch-screen
> > or
> > pointing device) and how that resource is accessed?
> > 
> > These are two very different requirements. Or do you have something
> > entirely
> > different in mind?
> 
> The mechanism should support devices like black phones, which have no
> display capabilities that can be used to interact with the user, and
> devices like PC phones which have web browsers that can be used to
> interact with the user. 
> 
> 
> > >
> > > * The mechanism should be capable of handling UIs from 
> simple screens
> > > with buttons, to voice input
> > 
> > I'm not sure what the functional requirement you are asking for here
> > (apart
> > from the fact that the mechanism should be extensible that 
> is mentioned
> > in
> > the next point): "The mechanism should be capable of 
> handling UI's ...
> > with
> > voice input?" Are you meaning local recognition software 
> that allows a
> > user
> > to "say a command" or something similar? 
> 
> Yes. 
> 
> > [I presume you aren't talking
> > about
> > voice recog on the application server here.] Surely, this is just
> > another
> > permutation of mapping some local interface to application specific
> > stimuli?
> 
> Yes. I just want to make sure we cover a range of media, not just
> physical buttons. Hyperlinks, voice, even visual recognition should be
> possible.
> 
> > 
> > >
> > > * The mechanism should be capable of handling future user 
> interfaces
> > > that may be defined down the road
> > 
> > R10 was supposed to cover that ...
> > 
> > R10:    The mechanism must be extensible so that some non 
> key-based user
> > indications can be supported in the future, for instance, 
> sliders, dials
> > or
> > wheels.
> > 
> > Perhaps it could be broadened. Any suggestions?
> 
> Voice, hyperlinks, biometrics, brain waves, etc.
> 
> > >
> > > * The mechanism should support user interfaces which require a new
> > > content to be presented to the user upon input from the 
> user (i.e.,
> > > change the screen when a user presses a button)
> > >
> > 
> > Hmm, this goes beyond "getting indications a device supports" and is
> > more to
> > do with "application action in response to input". I'm not 
> sure it is in
> > scope.
> 
> I think it has to be - thats the whole problem! I think we've been
> thinking far too narrowly on this problem. Its not just about
> notifications of user input. We are talking about supporting stimulus
> signaling for applications, where stimulus signaling is defined in the
> broadest sense. 
> 
> > 
> > > * The mechanism should support user interfaces where user 
> input can be
> > > sent to the application without waiting for a response from
> > > the previous
> > > input
> > 
> > Agreed.  A requirement that the mechanism is not limited to stop and
> > wait.
> > This was what we were aiming at in D3:
> > 
> > D3:     The mechanism should attempt to reduce recovery delays under
> > packet
> > loss scenarios.
> 
> I don't read D3 as saying the same thing as above.
> 
> 
> > > * The mechanism should allow the user to interface with 
> multiple user
> > > interfaces for different applications within the same call
> > > (for example,
> > > a single call may involve a call recording application 
> and a prepaid
> > > calling application, both of which might support a UI)
> > 
> > Good one, although I'm not sure how this is a requirement on the
> > mechanism
> > rather than simply how the user locally selects their user interface
> > (which
> > would be a requirement on how to design a user device, i.e., not in
> > scope).
> > Each relationship between an application and a user 
> interface would be a
> > separate subscription.
> 
> No. We have a fundamental disconnect here. There are two radically
> different approaches for interacting with applications. In approach 1,
> there are a set of applications listening for user input. The 
> user input
> is not directed; that is, the user has no ability to say 
> "this input is
> for app 1" or "this input is for app 2". Directing user input 
> generally
> requires a user interface of sorts, and in approach 1, there is no UI.
> In approach 2, input can be directed. The device has a user interface
> that allows the user to send feedback to specific applications. 
> 
> Let me give concrete examples. A black phone is an example of approach
> 1. Multiple apps can listen for DTMF, but the user can't 
> direct DTMF to
> a specific application. This, BTW, is the source of countless feature
> interaction problems, and is an artifact of the legacy 
> interface of the
> phone. An example of approach 2 is a PC. Lets say I make a 
> call from my
> PC, and there are two applications involved in processing 
> that call. One
> is a prepaid calling app. One of the things this app allows me, the
> user, to do, is to hang up the call and make another without 
> re-entering
> my PIN. The other application is a voice recorder app, which allows me
> to record the audio of the call. This app needs my input to start and
> stop the recording. Once I make the call, two windows pop up. One is a
> control panel for the voice recorder (with start and stop buttons) and
> another is a control panel for the prepaid app. When I click "start
> recording" on the control panel for the voice recorder, this 
> starts the
> recording process. That happens through user input 
> indications, but they
> are directed towards the voice recorder app. They can be 
> directed since
> they occur within a context - a user interface - which allows 
> them to go
> to the right place. Approach 2 has MUCH better feature interaction
> properties, and a much more compelling user experience.
> 
> Approach 1 is a subset of approach 2. We should be seeking to solve
> approach 2, and a result, knock off approach 1. The worst thing we can
> do is continue to develop specifications that proliferate the broken
> mode of user interface which the PSTN has provided us! We 
> should support
> it, but it is not the design goal. 
> 
> 
> > 
> > >
> > > * The mechanism should allow the user to know which application is
> > > associated with which user interface/input
> > 
> > OK.  (satisfied through authentication/authorization of the 
> SUBSCRIBE?)
> 
> You presume SUBSCRIBE - thats a mechanism. The requirement is as it is
> written. In the example above, my PC should be able to tell 
> me that one
> of the popups is for a voice recorder, and the other is for a prepaid
> calling app.
> 
> > 
> > >
> > > * The mechanism must allow a user to have assurances that the
> > > user input
> > > it is providing is only to applications/servers on the call
> > > path between
> > > caller and callee.
> > 
> > I think this is covered by R16 & R17:
> > 
> > R16:    The mechanism must allow for end-to-end 
> security/privacy between
> > source and destination.
> > 
> > R17:    Both entities must be able to authenticate each other.
> 
> No - these are not the same at all. I don't know what end-to-end
> security is. Security encapsulates a lot of functions. I am 
> saying that
> the mechanism should support a specific authorization model - that the
> system can provide guarantees that only servers on the call 
> path can ask
> for my user input. 
> 
> 
> > >
> > > * The mechanism must work with applications that are both 
> proxy and
> > > b2bua.
> > 
> > As mentioned in the discussion of R5, the use of the term "network
> > entity"
> > is purposefully designed to NOT limit the interaction to 
> just proxies or
> > b2bua's. SIP Event's has no such constraints and I don't 
> see that this
> > mechanism should either. Will re-word to make clearer our 
> intent. Do you
> > have a problem with this generalization?
> 
> There are two participants here. There is the user, and the 
> application.
> The application can be a proxy, B2bua, or just UA. The user 
> has to be a
> user, though, not a proxy (see above).
> 
> -Jonathan R.
> 
> 
> -- 
> Jonathan D. Rosenberg, Ph.D.            72 Eagle Rock Avenue
> Chief Scientist                         First Floor
> dynamicsoft                             East Hanover, NJ 07936
> jdrosen@dynamicsoft.com                 FAX: (973) 952-5050
> http://www.jdrosen.net                  PH:  (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 daemon@optimus.ietf.org  Fri Apr 26 06:06:14 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28597
	for <sipping-archive@odin.ietf.org>; Fri, 26 Apr 2002 06:06:14 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA29518
	for sipping-archive@odin.ietf.org; Fri, 26 Apr 2002 06:06:17 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA27845;
	Fri, 26 Apr 2002 05:46:14 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA27814
	for <sipping@optimus.ietf.org>; Fri, 26 Apr 2002 05:46:11 -0400 (EDT)
Received: from auds953.usa.alcatel.com (auds953.usa.alcatel.com [143.209.238.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28306
	for <sipping@ietf.org>; Fri, 26 Apr 2002 05:46:07 -0400 (EDT)
Received: from axsppc65 (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.10.2/8.10.2) with SMTP id g3Q9jd413197
	for <sipping@ietf.org>; Fri, 26 Apr 2002 04:45:39 -0500 (CDT)
Message-ID: <007001c1ef62$d4ce5510$7301ff0a@axsppc65>
From: "Jagannathan R" <jaganathan.ramaswamy@alcatel.com>
To: <sipping@ietf.org>
Date: Mon, 29 Apr 2002 15:17:07 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_006D_01C1EF90.ECE256F0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Subject: [Sipping] SIP/SIPT - ISUP/BICC Interworking
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_006D_01C1EF90.ECE256F0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

   After having look at the I-D draft-chang-sipping-bicc-network-00.txt =
and draft-ietf-sipping-sipt-01.txt, I am thoroughly confused about the =
interworking of SIP-PSTN. Can some one help me to understand the =
difference between or the different purposes of=20

1. SIP-T which is primarily conceived for SIP-PSTN interworking (???)
2. SIP - BICC interworking.

I do know that BICC is basically for Inter MGC communication either =
within a single network or across the networks.=20

This bicc draft describes that extending SIP to support call control =
across different networks. This extension encapsulates
BICC in the SIP message to provide the information needed across =
networks. Integrating both SIP and BICC features,
this extension provides service providers a vehicle to deploy services =
across different administration domains and different types of network.

My basic doubt is, by deploying SIP-T across the networks can't we =
achieve this same purpose. If yes then, why one more framework on bicc?

Or am I missing some thing?

thanks,
jagannathan


------=_NextPart_000_006D_01C1EF90.ECE256F0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; After having look at the =
I-D=20
<STRONG>draft-chang-sipping-bicc-network-00.txt</STRONG> and=20
<STRONG>draft-ietf-sipping-sipt-01.txt,</STRONG> I am thoroughly =
confused about=20
the interworking of SIP-PSTN. Can some one help me to understand the =
difference=20
between or the different purposes of&nbsp;</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>1.&nbsp;SIP-T which is primarily =
conceived for=20
SIP-PSTN interworking (???)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>2. SIP - BICC =
interworking.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I do know that BICC is basically for =
Inter MGC=20
communication either within a single network or across the networks.=20
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>This&nbsp;bicc draft describes =
that&nbsp;extending=20
SIP to support call control across different networks. This extension=20
encapsulates<BR>BICC in the SIP message to provide the information =
needed across=20
networks. Integrating both SIP and BICC features,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>this extension provides service =
providers a vehicle=20
to deploy services across different administration domains and different =
types=20
of network.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>My basic doubt is, by deploying SIP-T =
across the=20
networks can't we achieve this same purpose. If yes then, why one more =
framework=20
on bicc?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Or am I missing some =
thing?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>thanks,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>jagannathan</FONT></DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_006D_01C1EF90.ECE256F0--


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



From daemon@optimus.ietf.org  Fri Apr 26 11:33:26 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07925
	for <sipping-archive@odin.ietf.org>; Fri, 26 Apr 2002 11:33:26 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA20348
	for sipping-archive@odin.ietf.org; Fri, 26 Apr 2002 11:33:29 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA18984;
	Fri, 26 Apr 2002 11:11:21 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA18955
	for <sipping@optimus.ietf.org>; Fri, 26 Apr 2002 11:11:18 -0400 (EDT)
Received: from iere.net.avaya.com (iere.net.avaya.com [198.152.12.101])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07183
	for <sipping@ietf.org>; Fri, 26 Apr 2002 11:11:14 -0400 (EDT)
Received: from iere.net.avaya.com (localhost [127.0.0.1])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g3QF9cJ22601
	for <sipping@ietf.org>; Fri, 26 Apr 2002 11:09:38 -0400 (EDT)
Received: from cof110avexu1.global.avaya.com (h135-9-6-16.avaya.com [135.9.6.16])
	by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id g3QF9cI22592
	for <sipping@ietf.org>; Fri, 26 Apr 2002 11:09:38 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Sipping] new I-D on markup languages for DTMF and user input
Date: Fri, 26 Apr 2002 09:11:59 -0600
Message-ID: <EF4C65F18BE6464B8E9DF3C212B6B293017012FA@cof110avexu1.global.avaya.com>
Thread-Topic: [Sipping] new I-D on markup languages for DTMF and user input
Thread-Index: AcHrpb0lMHVnjcAQQISck7Ky8FeS9QBjZXnA
From: "Zmolek, Andrew (Andrew)" <zmolek@avaya.com>
To: "Jonathan Rosenberg" <jdrosen@dynamicsoft.com>, <sipping@ietf.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA18956
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 8bit

This draft is very timely. I'd like to forward on a comment on the need for a scripting requirement that I received after circulating this internally - see below

--Andy

----------------------------

 - how would this accommodate "type-ahead"?  For example, when I interact with my voice mail system from my cell phone, I have one speed dial button programmed with the following sequence:
      3134145000<pause><pause>45000#3456789#2#0#
What does this do?  it dials my Audix, pauses for the greeting to connect, and dials my extension and my password, then selects "play messages" and then starts playing the first message - all in one button push for me.  

I don't see how Rosenberg's scheme accommodates something like this.   If each interaction must wait for a HTML response with a page to load, then the next step cannot be completed until that page has downloaded and been rendered.  Each user entry (e.g. extension, then password, then play messages) must be entered separately.  And I don't see a way to preprogram it.   Users would view this as a loss of functionality.

Rosenberg's requirements in section 5 don't include a requirement for user "scripting" or "preprogramming of responses" like I have described.  I think this is an omission.

-----------------------------


> -----Original Message-----
> From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com]
> Sent: Wednesday, April 24, 2002 9:33 AM
> To: sipping@ietf.org
> Subject: [Sipping] new I-D on markup languages for DTMF and user input
> 
> 
> Folks,
> 
> I've just submitted an I-D that discusses a SIP framework for 
> the usage
> of markup languages (HTML, VoiceXML, WML) for stimulus signaling for
> driving sip applications. The draft also proposes a DTMF markup
> language, DML, that operates within the framework. 
> 
> Until it appears in the archives, you can pick up a copy at:
> 
> http://www.jdrosen.net/papers/draft-rosenberg-sipping-markup-00.txt
> 
> Comments and questions welcome as always.
> 
> -Jonathan R.
> -- 
> Jonathan D. Rosenberg, Ph.D.            72 Eagle Rock Avenue
> Chief Scientist                         First Floor
> dynamicsoft                             East Hanover, NJ 07936
> jdrosen@dynamicsoft.com                 FAX: (973) 952-5050
> http://www.jdrosen.net                  PH:  (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 daemon@ns.ietf.org  Fri Apr 26 13:14:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11460
	for <sipping-archive@odin.ietf.org>; Fri, 26 Apr 2002 13:14:23 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA27326
	for sipping-archive@odin.ietf.org; Fri, 26 Apr 2002 13:14:25 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA25732;
	Fri, 26 Apr 2002 12:59:38 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA25700
	for <sipping@ns.ietf.org>; Fri, 26 Apr 2002 12:59:34 -0400 (EDT)
Received: from exchange1.nuera.com ([12.105.228.79])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10652
	for <sipping@ietf.org>; Fri, 26 Apr 2002 12:59:31 -0400 (EDT)
Received: by exchange1.nuera.com with Internet Mail Service (5.5.2653.19)
	id <JK3N5XF1>; Fri, 26 Apr 2002 09:59:37 -0700
Message-ID: <E79883AEA37FD411A58C00508BAC5F4B01D38CC2@exchange1.nuera.com>
From: "Fairlie-Cuninghame, Robert" <rfairlie@nuera.com>
To: "'Zmolek, Andrew (Andrew)'" <zmolek@avaya.com>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: RE: [Sipping] new I-D on markup languages for DTMF and user input
Date: Fri, 26 Apr 2002 09:59:35 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Hi Andrew,

The requirements listed in draft-rosenberg-sipping-markup-00 are actually
referring the requirements drafted in
draft-culpepper-sipping-app-interact-reqs-00. 

We (Bert Culpepper and myself) are currently working on putting out another
version of the requirements draft to address some of Jonathan's comments.
Please feel free to add more comments.

In Jonathan's Markup draft did present a mode=immediate in DML that allowed
you to send subsequent indication without stop-and-wait'ing for the response
to the first. Additionally, one of the requirements in the abovementioned
requirements draft attempted to address the fact that stop-and-wait is not
acceptable. 

Is this adequate to fulfill your concerns? Otherwise, what functional
requirement did you have in mind?

Regards,

Robert.



> -----Original Message-----
> From: Zmolek, Andrew (Andrew) [mailto:zmolek@avaya.com]
> Sent: Friday, April 26, 2002 4:12 PM
> To: Jonathan Rosenberg; sipping@ietf.org
> Subject: RE: [Sipping] new I-D on markup languages for DTMF and user
> input
> 
> 
> This draft is very timely. I'd like to forward on a comment 
> on the need for a scripting requirement that I received after 
> circulating this internally - see below
> 
> --Andy
> 
> ----------------------------
> 
>  - how would this accommodate "type-ahead"?  For example, 
> when I interact with my voice mail system from my cell phone, 
> I have one speed dial button programmed with the following sequence:
>       3134145000<pause><pause>45000#3456789#2#0#
> What does this do?  it dials my Audix, pauses for the 
> greeting to connect, and dials my extension and my password, 
> then selects "play messages" and then starts playing the 
> first message - all in one button push for me.  
> 
> I don't see how Rosenberg's scheme accommodates something 
> like this.   If each interaction must wait for a HTML 
> response with a page to load, then the next step cannot be 
> completed until that page has downloaded and been rendered.  
> Each user entry (e.g. extension, then password, then play 
> messages) must be entered separately.  And I don't see a way 
> to preprogram it.   Users would view this as a loss of functionality.
> 
> Rosenberg's requirements in section 5 don't include a 
> requirement for user "scripting" or "preprogramming of 
> responses" like I have described.  I think this is an omission.
> 
> -----------------------------
> 
> 
> > -----Original Message-----
> > From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com]
> > Sent: Wednesday, April 24, 2002 9:33 AM
> > To: sipping@ietf.org
> > Subject: [Sipping] new I-D on markup languages for DTMF and 
> user input
> > 
> > 
> > Folks,
> > 
> > I've just submitted an I-D that discusses a SIP framework for 
> > the usage
> > of markup languages (HTML, VoiceXML, WML) for stimulus signaling for
> > driving sip applications. The draft also proposes a DTMF markup
> > language, DML, that operates within the framework. 
> > 
> > Until it appears in the archives, you can pick up a copy at:
> > 
> > http://www.jdrosen.net/papers/draft-rosenberg-sipping-markup-00.txt
> > 
> > Comments and questions welcome as always.
> > 
> > -Jonathan R.
> > -- 
> > Jonathan D. Rosenberg, Ph.D.            72 Eagle Rock Avenue
> > Chief Scientist                         First Floor
> > dynamicsoft                             East Hanover, NJ 07936
> > jdrosen@dynamicsoft.com                 FAX: (973) 952-5050
> > http://www.jdrosen.net                  PH:  (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



From daemon@ns.ietf.org  Fri Apr 26 16:08:04 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04335
	for <sipping-archive@odin.ietf.org>; Fri, 26 Apr 2002 16:07:59 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA20666
	for sipping-archive@odin.ietf.org; Fri, 26 Apr 2002 16:08:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA19290;
	Fri, 26 Apr 2002 15:42:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA19261
	for <sipping@ns.ietf.org>; Fri, 26 Apr 2002 15:42:49 -0400 (EDT)
Received: from imo-r07.mx.aol.com (imo-r07.mx.aol.com [152.163.225.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01321
	for <sipping@ietf.org>; Fri, 26 Apr 2002 15:42:45 -0400 (EDT)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r07.mx.aol.com (mail_out_v32.5.) id l.95.1b9390bb (25512)
	 for <sipping@ietf.org>; Fri, 26 Apr 2002 15:42:15 -0400 (EDT)
Message-ID: <95.1b9390bb.29fb0796@aol.com>
Date: Fri, 26 Apr 2002 15:42:14 EDT
To: sipping@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_95.1b9390bb.29fb0796_boundary"
X-Mailer: AOL 6.0 for Windows US sub 10524
Subject: [Sipping] Comments on draft-cc-framework
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


--part1_95.1b9390bb.29fb0796_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

To all,

I submitted comments on draft-ietf-sipping-cc-framework-00 (Feb) before the 
March meeting, but have seen no responses or other comments. I will repeat 
these comments with some others added:

3.1 Final bullet item: It isn't clear what point is being made about the 
model from H.450.  While the goal says "do not reinvent", the rest of the 
statement seems to say that SIP will not use an existing model, but rather 
reinvent it.

4.1.1 This section notes that existing terms "call" and "conference" are not 
well defined, so it uses a new term "conversation space". While this concept 
seems useful, it is not well defined either. The statement that it is 
"essentially a set of participants who believe they are all communicating 
among one another" is not precise enough.

4.5.2 Reference to serving the queue should refer to "the first call in the 
relevant queue" not the "last".

4.7 This statement that "only the invoker[s] of features in SIP know exactly 
which feature they are invoking" sounds good in theory, but the reality for 
telephony services is that often both parties (devices) need to explicitly 
know what service is being performed, not just what signaling primitives are 
being used. It is clear, for example, that the processing of an INVITE or a 
REFER depends on the reason it was sent, whether it is a new call or a 
transfer or a barge in, etc.

The example of Alice calling Bob who transfers to Carol, while Alice has her 
robotic assistant Alice "conferenced" illustrates this. First, the 
independence of these two separate "features" would not be compromised if the 
message from Bob to Alice explicitly said "transfer" rather than the generic 
"REFER". Secondly, one should assume that the interaction between the 
"robotic" feature at Alice with transfer (caused by receipt of the REFER) 
might have to be different than the interaction between this "robotic 
feature" and other features caused by receipt of REFER. When this happens, 
attempts will have to be made at the receiving end (Ann) to deduce what was 
intended in order to figure out what the best course of action is to provide 
a good service.

5.2.2 The statement that "there is no way to distinguish between the desire 
to go on or off hold" is interesting. Is this meant to say that the REFER 
method mentioned won't work for this and some better method is needed?

5.3 1 Since B apparently has to do something before C replaces A, the 
description of this primitive should be: "A requests to be replaced with C"

5.3.2 Since B has to do something with the INVITE (stop sending media to C, 
start using media from A rather than C, etc) this really isn't "A forcibly 
replacing C with itself". It's really still just a request from A for B to 
replace C with A.

The note regarding the need to take different action depending on the state 
of the receiving entity "B", refers to a problem that affects many of the 
primitives described. Because of overlapping actions, practically every 
action at the receiving entity needs to consider the state of the receiver 
before taking the described action. However, the model for this work seems to 
be that the sender decides the action required and the receiver must do it.

5.3.5 As above, this is just a "request" by A to be inserted into an existing 
space. B must actually do it upon receipt of the INVITE, meaning that B can 
refuse (as implied by the phrase "if B accepted the INVITE..."). Therefore, 
the statement should be:

A requests to be inserted into a conversation space.

5.3.6 should have a statement added after the depiction of the change of 
conversation space that says what is happening. It appears to be the 
following:

A causes conversation space to be split into two with itself and B making up 
the new conversation space.

5.3.7 It is not clear from the diagram and statement before it what has 
happened. It should say:

The conversation space changes like this:
( A , B ) --> (B , A ) & ( A , C )
A creates a new conversation space with C and participates in both as the 
"anchor".


Mike Pierce
Artel


--part1_95.1b9390bb.29fb0796_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">To all,
<BR>
<BR>I submitted comments on draft-ietf-sipping-cc-framework-00 (Feb) before the March meeting, but have seen no responses or other comments. I will repeat these comments with some others added:
<BR>
<BR>3.1 Final bullet item: It isn't clear what point is being made about the model from H.450. &nbsp;While the goal says "do not reinvent", the rest of the statement seems to say that SIP will not use an existing model, but rather reinvent it.
<BR>
<BR>4.1.1 This section notes that existing terms "call" and "conference" are not well defined, so it uses a new term "conversation space". While this concept seems useful, it is not well defined either. The statement that it is "essentially a set of participants who believe they are all communicating among one another" is not precise enough.
<BR>
<BR>4.5.2 Reference to serving the queue should refer to "the first call in the relevant queue" not the "last".
<BR>
<BR>4.7 This statement that "only the invoker[s] of features in SIP know exactly which feature they are invoking" sounds good in theory, but the reality for telephony services is that often both parties (devices) need to explicitly know what service is being performed, not just what signaling primitives are being used. It is clear, for example, that the processing of an INVITE or a REFER depends on the reason it was sent, whether it is a new call or a transfer or a barge in, etc.
<BR>
<BR>The example of Alice calling Bob who transfers to Carol, while Alice has her robotic assistant Alice "conferenced" illustrates this. First, the independence of these two separate "features" would not be compromised if the message from Bob to Alice explicitly said "transfer" rather than the generic "REFER". Secondly, one should assume that the interaction between the "robotic" feature at Alice with transfer (caused by receipt of the REFER) might have to be different than the interaction between this "robotic feature" and other features caused by receipt of REFER. When this happens, attempts will have to be made at the receiving end (Ann) to deduce what was intended in order to figure out what the best course of action is to provide a good service.
<BR>
<BR>5.2.2 The statement that "there is no way to distinguish between the desire to go on or off hold" is interesting. Is this meant to say that the REFER method mentioned won't work for this and some better method is needed?
<BR>
<BR>5.3 1 Since B apparently has to do something before C replaces A, the description of this primitive should be: "A requests to be replaced with C"
<BR>
<BR>5.3.2 Since B has to do something with the INVITE (stop sending media to C, start using media from A rather than C, etc) this really isn't "A forcibly replacing C with itself". It's really still just a request from A for B to replace C with A.
<BR>
<BR>The note regarding the need to take different action depending on the state of the receiving entity "B", refers to a problem that affects many of the primitives described. Because of overlapping actions, practically every action at the receiving entity needs to consider the state of the receiver before taking the described action. However, the model for this work seems to be that the sender decides the action required and the receiver must do it.
<BR>
<BR>5.3.5 As above, this is just a "request" by A to be inserted into an existing space. B must actually do it upon receipt of the INVITE, meaning that B can refuse (as implied by the phrase "if B accepted the INVITE..."). Therefore, the statement should be:
<BR>
<BR></FONT><FONT  COLOR="#000000" SIZE=4 FAMILY="FIXED" FACE="Courier New" LANG="0">A requests to be inserted into a conversation space.</FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>5.3.6 should have a statement added after the depiction of the change of conversation space that says what is happening. It appears to be the following:
<BR>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="FIXED" FACE="Courier New" LANG="0">A causes conversation space to be split into two with itself and B making up the new conversation space.</FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>5.3.7 It is not clear from the diagram and statement before it what has happened. It should say:
<BR>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="FIXED" FACE="Courier New" LANG="0">The conversation space changes like this:
<BR>( A , B ) --&gt; (B , A ) &amp; ( A , C )
<BR>A creates a new conversation space with C and participates in both as the "anchor".</FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>
<BR>
<BR>Mike Pierce
<BR>Artel
<BR></FONT></HTML>

--part1_95.1b9390bb.29fb0796_boundary--

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



From daemon@ns.ietf.org  Fri Apr 26 16:52:44 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09906
	for <sipping-archive@odin.ietf.org>; Fri, 26 Apr 2002 16:52:43 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA22611
	for sipping-archive@odin.ietf.org; Fri, 26 Apr 2002 16:52:47 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA22236;
	Fri, 26 Apr 2002 16:43:53 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA22205
	for <sipping@ns.ietf.org>; Fri, 26 Apr 2002 16:43:49 -0400 (EDT)
Received: from mail2.intervoice-brite.com (mail2.intervoice-brite.com [204.62.8.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08836
	for <sipping@ietf.org>; Fri, 26 Apr 2002 16:43:45 -0400 (EDT)
Received: from DALNTMS02.ivbi.com (dalntms02.ivbi.com [151.214.90.44])
	by mail2.intervoice-brite.com (Build 101 8.9.3/NT-8.9.3) with ESMTP id PAA03349
	for <sipping@ietf.org>; Fri, 26 Apr 2002 15:49:14 -0500
Received: from 172.16.16.64 (unverified) by DALNTMS02.ivbi.com
 (Content Technologies SMTPRS 4.2.10) with SMTP id <T5a7f58dfac97d65a2c398@DALNTMS02.ivbi.com> for <sipping@ietf.org>;
 Fri, 26 Apr 2002 15:39:47 -0500
Received: from bculpepperpc
	([151.214.151.115])
	by 172.16.16.64; Fri, 26 Apr 2002 15:42:57 -0500
From: "Bert Culpepper" <bert.culpepper@intervoice-brite.com>
To: "'Zmolek, Andrew \(Andrew\)'" <zmolek@avaya.com>,
        "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>, <sipping@ietf.org>
Subject: RE: [Sipping] new I-D on markup languages for DTMF and user input
Date: Fri, 26 Apr 2002 16:42:22 -0400
Message-ID: <005401c1ed62$dea99c40$7397d697@bculpepperpc>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <EF4C65F18BE6464B8E9DF3C212B6B293017012FA@cof110avexu1.global.avaya.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

The requirements Jonathan's proposal address were not meant to address what
functionality an application within a device might provide in terms of its
user interface/user features.  But rather a SIP-based protocol mechanism for
a network application, someplace along the SIP signaling route/path, to be
able to ask for and a mechanism to transmit user indications generated using
whatever user interface a device may possess.

IMHO, the scenario below is an application feature, outside the scope of the
problem to be solved.  However, other folks have suggested the scope be
extended to allow an application to present its user interface to a user
agent/device.  And then report user indications via the specific interface's
widgets (or whathaveyou).  And Jonathan's framework handles this very
nicely.  But the only thing that's SIP is the header to indicate what "page"
to retrieve.  Certainly elegant and simple from a SIP point of view.

What the writer below seems to be asking for (presuming use of SIP here) is
for the Speed Dial application to establish a session with a voice mail
server, and provide the voice mail application with the input it needs to
perform the desired function.  In SIP, this seems better supported using a
specific URI associated with the desired speed dial button.  Where the URI
(and any needed parameters) indicate the service to be provided on the voice
mail server.  No DTMF, keypresses, or whatever are needed.  The SIP protocol
can support this application today.  Now, if you want to access some
DTMF-based voice mail system, then that is another story... (as I'm sure
you're aware :)

Well, some thoughts here, and maybe unrelated to the subject.

Regards,
Bert

Zmolek, Andrew (Andrew) wrote:
>
> This draft is very timely. I'd like to forward on a comment
> on the need for a scripting requirement that I received after
> circulating this internally - see below
>
> --Andy
>
> ----------------------------
>
>  - how would this accommodate "type-ahead"?  For example,
> when I interact with my voice mail system from my cell phone,
> I have one speed dial button programmed with the following sequence:
>       3134145000<pause><pause>45000#3456789#2#0#
> What does this do?  it dials my Audix, pauses for the
> greeting to connect, and dials my extension and my password,
> then selects "play messages" and then starts playing the
> first message - all in one button push for me.
>
> I don't see how Rosenberg's scheme accommodates something
> like this.   If each interaction must wait for a HTML
> response with a page to load, then the next step cannot be
> completed until that page has downloaded and been rendered.
> Each user entry (e.g. extension, then password, then play
> messages) must be entered separately.  And I don't see a way
> to preprogram it.   Users would view this as a loss of functionality.
>
> Rosenberg's requirements in section 5 don't include a
> requirement for user "scripting" or "preprogramming of
> responses" like I have described.  I think this is an omission.
>
> -----------------------------
>
>


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



From daemon@optimus.ietf.org  Sun Apr 28 08:34:55 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06819
	for <sipping-archive@odin.ietf.org>; Sun, 28 Apr 2002 08:34:55 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA09095
	for sipping-archive@odin.ietf.org; Sun, 28 Apr 2002 08:34:58 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA08190;
	Sun, 28 Apr 2002 08:10:52 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA08159
	for <sipping@optimus.ietf.org>; Sun, 28 Apr 2002 08:10:49 -0400 (EDT)
Received: from exchange1.nuera.com ([12.105.228.79])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04450
	for <sipping@ietf.org>; Sun, 28 Apr 2002 08:10:44 -0400 (EDT)
Received: by exchange1.nuera.com with Internet Mail Service (5.5.2653.19)
	id <JK3N56QX>; Sun, 28 Apr 2002 05:10:50 -0700
Message-ID: <E79883AEA37FD411A58C00508BAC5F4B01D38CC3@exchange1.nuera.com>
From: "Fairlie-Cuninghame, Robert" <rfairlie@nuera.com>
To: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>
Cc: sipping@ietf.org
Date: Sun, 28 Apr 2002 05:10:44 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sipping] App Interact Reqs discussion [Was: ID-ACTION: draft-culpepper-...
 ]
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Hi Jonathan,

Responses inline [two emails combined.]

> > > > R5:  A network entity desiring user indications must be able to
> > > >         request user indications from another network 
> entity.  The
> > > >         entity receiving a request must be able to 
> respond with its
> > > >         capability/intent to transmit user indications.
> > >
> > > We should be more specific here. We have a caller and a
> > > callee. I think
> > > that by "entity" you mean one of those two.
> > 
> > No, we are purposefully not restricting the mechanism to 
> only caller and
> > callee (or even proxy). So, yes, I agree we need to re-word to
> > explicitly
> > define. Further discussion later.
> 
> That doesn't make sense to me. By definition, user input indication is
> possible only from a human, NOT from an automata. An automata can try
> (web screen scraping...) but that is a known bad thing.
> 

Admittedly, yes normally one network entity will normally be an application
and the other will normally be a user but I do not see that this should be a
requirement. Sure, it is not feasible for automatas to analyze voice prompts
or HTML presentations but who's to say that people will not invent
automata-friendly presentation (and stimulus) methods. Why add this
artificial restriction?

I am however fine with adding the restriction that at least *one* of the
network entities must be a UA of the associated session (given that we are
now saying that all interaction MUST be session associated). It means that a
proxy or co-operating device cannot act on a user's behalf but I can live
with that restriction.

> > > > R15: The receiving application must be able to detect 
> user activity
> > > >         indication loss due to packet loss from received
> > > user activity
> > > >         indications.
> > >
> > > I don't know what this means.
> > 
> > Detecting missing indications.  For example, a PIN is 
> transmitted one
> > digit
> > at a time.  If one message (network packet) gets lost, we want to be
> > able to
> > determine this at the receiver. Will re-word.
> 
> There is an implicit assumption here of UDP based notifications and/or
> notifications that are not stop-and-wait. I think the real requirement
> you want here is ordering - events are delivered to the 
> observer in the
> same order they occurred at the reporter.
> 

Yes I came to same conclusion after reading your draft. 
 
> > > * The mechanism should support devices that possess a UI, 
> and those
> > > which do not possess a UI
> > 
> > Jonathan can you please explain exactly what you mean by this. My
> > feeling is
> > that this is the crux of your new requirements, yet I don't 
> have a clear
> > idea of what you mean by "The mechanism should support 
> devices ... which
> > do
> > not possess a UI."
> 
> Hopefully the recent draft on markup I just submitted explains better.
> The basic idea is that there are many devices that have the ability to
> interact with the user. There could, for example, be a display with
> buttons. The display would present the user with choices, and the user
> would press a button, causing a notification to be sent into the
> network. This is in contrast with devices, like a traditional 
> dumb black
> phone, which have no ability to interact with the user. There is no
> display. There is no way to know, when a user presses a DTMF key, what
> application they were trying to interact with. 
> 

I disagree here but I believe this is partially due to the need to
standardize terms.

By "device with no user interface" it seems like you are referring to
devices possessing no physical, visual, presentation-based UI components. 

In my mind, a dump phone _does_ possess a user interface (speaker,
microphone & dialpad) and does even possess a UI component capable of
presentation - the speaker - its just that presentation is audio not visual.
A user-interface for me refers to all components: input or presentation,
session-initiated or external markup (or other).

I also believe we need to define a "virtual user interface" more clearly.
For me this represents the notional user interface consisting of all user
interface components (presentation- or input-based) of co-operating
applications that *explicitly* desire to be on the same logical user
interface. 

So now non-co-operating applications will refer to separate virtual user
interfaces but it is up to the device to decide how to map those virtual
user interfaces onto the physical interface. This gets down to an device
design issue raised later.

Additionally I feel, just because a device does not support visual,
presentation-based application interaction, this does not preclude the
ability to select and identify different virtual user interfaces. These are
simply separable issues. [The device may have display but perhaps it is not
available for application use.] 

> > > * The mechanism should support user interfaces which require a new
> > > content to be presented to the user upon input from the 
> user (i.e.,
> > > change the screen when a user presses a button)
> > >
> > 
> > Hmm, this goes beyond "getting indications a device supports" and is
> > more to
> > do with "application action in response to input". I'm not 
> sure it is in
> > scope.
> 
> I think it has to be - that's the whole problem! I think we've been
> thinking far too narrowly on this problem. Its not just about
> notifications of user input. We are talking about supporting stimulus
> signaling for applications, where stimulus signaling is defined in the
> broadest sense. 
> 

Okay I've done a U-turn on this one. I agree with you that requirements need
to address application interaction as a whole and after more thought I think
I would actually reword and strengthen these requirements.

* The mechanism must allow user interface components created through this
mechanism to be updated and terminated by the creating application.

[Remove any reference to "in response to stimulus input"]

> > > * The mechanism should allow the user to interface with 
> multiple user
> > > interfaces for different applications within the same call
> > > (for example,
> > > a single call may involve a call recording application 
> and a prepaid
> > > calling application, both of which might support a UI)
> > 
> > Good one, although I'm not sure how this is a requirement on the
> > mechanism
> > rather than simply how the user locally selects their user interface
> > (which
> > would be a requirement on how to design a user device, i.e., not in
> > scope).
> > Each relationship between an application and a user 
> interface would be a
> > separate subscription.
> 
> No. We have a fundamental disconnect here. There are two radically
> different approaches for interacting with applications. In approach 1,
> there are a set of applications listening for user input. The 
> user input
> is not directed; that is, the user has no ability to say 
> "this input is
> for app 1" or "this input is for app 2". Directing user input 
> generally
> requires a user interface of sorts, and in approach 1, there is no UI.
> In approach 2, input can be directed. The device has a user interface
> that allows the user to send feedback to specific applications. 
> 
> Let me give concrete examples. A black phone is an example of approach
> 1. Multiple apps can listen for DTMF, but the user can't 
> direct DTMF to
> a specific application. This, BTW, is the source of countless feature
> interaction problems, and is an artifact of the legacy 
> interface of the
> phone. An example of approach 2 is a PC. Lets say I make a 
> call from my
> PC, and there are two applications involved in processing 
> that call. One
> is a prepaid calling app. One of the things this app allows me, the
> user, to do, is to hang up the call and make another without 
> re-entering
> my PIN. The other application is a voice recorder app, which allows me
> to record the audio of the call. This app needs my input to start and
> stop the recording. Once I make the call, two windows pop up. One is a
> control panel for the voice recorder (with start and stop buttons) and
> another is a control panel for the prepaid app. When I click "start
> recording" on the control panel for the voice recorder, this 
> starts the
> recording process. That happens through user input 
> indications, but they
> are directed towards the voice recorder app. They can be 
> directed since
> they occur within a context - a user interface - which allows 
> them to go
> to the right place. Approach 2 has MUCH better feature interaction
> properties, and a much more compelling user experience.
> 
> Approach 1 is a subset of approach 2. We should be seeking to solve
> approach 2, and a result, knock off approach 1. The worst thing we can
> do is continue to develop specifications that proliferate the broken
> mode of user interface which the PSTN has provided us! We 
> should support
> it, but it is not the design goal. 

Ok I agree then - we add a requirement that Approach 2 is possible.
However, we also then need to add a requirement that Approach 1 is possible,
that is, 2 (co-operating) applications can share the same virtual user
interface (which I disagree is inherently a subset of Approach 2). 
 
> > > * The mechanism must allow a user to have assurances that the
> > > user input
> > > it is providing is only to applications/servers on the call
> > > path between
> > > caller and callee.
> > 
> > I think this is covered by R16 & R17:
> > 
> > R16:    The mechanism must allow for end-to-end 
> security/privacy between
> > source and destination.
> > 
> > R17:    Both entities must be able to authenticate each other.
> 
> No - these are not the same at all. I don't know what end-to-end
> security is. Security encapsulates a lot of functions. I am 
> saying that
> the mechanism should support a specific authorization model - that the
> system can provide guarantees that only servers on the call 
> path can ask
> for my user input. 
> 

I disagree. There should be no requirement to restrict application servers
to entities on the call path of a particular dialog. What about when there
are multiple co-operating application modules/entities - must they all exist
on the same server? This goes against the distributed model and ties
"sessions" to dialogs - something that we've agreed is bad. 

Besides, how do you authenticate a downstream proxy on the call path any
better than you can authorize any other network entity?

Responses to the other email ...
 
> >  I've given some more thought to a couple of your requirements:
> > 
> > > * The mechanism should allow a device to indicate support 
> for multiple
> > > user interfaces, and allow the application to select which
> > > one is to be
> > > used
> > >
> > > * The mechanism should allow a device to indicate 
> relative preferences
> > > amongst the various user interfaces
> > >
> > 
> > I don't think your requirement adequately answers the 
> questions: what is
> > a
> > "user interface" and what does it mean to have "multiple user
> > interfaces"?
> > Assumedly a device normally has only one *physical* interface (be it
> > keys or
> > display or whatever). Now we all agree that the mechanism 
> must not force
> > the
> > device's interface to be "taken over" by an application.
> > 
> > One logical way to define multiple user interfaces or 
> rather "virtual
> > user
> > interfaces" is to create a virtual instance of the physical instance
> > that is
> > active when the application/session is in focus to the user 
> (much in the
> > way
> > a multiline SIP phone may work). 
> 
> THis seems reasonable. 
> 
> > There are other approaches but most of
> > the
> > ones I can think of are diminuitive cases of this general 
> approach. In
> > any
> > case, how this interface is selected or created will 
> largely depend on
> > the
> > user device and not this mechanism.
> 
> There is a subtle problem here. You indicated that the user 
> needs to put
> a particular virtual UI into focus. Doing that is only 
> possible if there
> is some display to the user that allows them to know which one it is
> they need. This means there has to be a way for the application to
> provide some kind of display to the user. THus, it is an issue for the
> mechanism. The mechanism has to have a way to provide a display to the
> user.
 
Not at all. The mechanism must simply allow a user interface component to be
associated with the application. [Or a virtual user interface with the set
of participating (co-operating) applications]. We cannot dictate that the
device must support some mechanism to display that identification or must
support multiple switchable user interfaces - these are device design
decisions or capability limitations. We can only require that it is
*possible* to identify the application that created the UI component and
that it is possible to identify components within the same virtual user
interface.

Once again, how a device display, maps or switches between virtual user
interfaces is, I contend, largely a device design decision - the requirement
is that the required information is available.

Perhaps I am missing your point?

> > 
> > It is my contention therefore, that it should not be a 
> requirement on
> > the
> > network application interaction mechanism to present multiple
> > (prioritized)
> > permutations or instances of user interfaces to an 
> application. Rather,
> > the
> > relevant requirement should be:
> > 
> > * The mechanism should support the identification of a requesting
> > application identity [e.g. application name+version @ 
> creator's domain]
> > and
> > application instance [e.g. instance@ service perovider's domain].
> 
> OK.
> 
> > * The mechanism should the ability for a user interface 
> instance to be
> > shared between subscriptions (and probably applications 
> when multiple
> > applications are co-operating).
> 
> In my model, there is a one-to-one mapping of "subscriptions" to
> applications.

I disagree. Your model does not create subscriptions or sessions at all. The
markups exist in their own little world. I think this is one area that needs
to be addressed. 
 
> > 
> > This allows a device to create and offer virtual user 
> interfaces as it
> > sees
> > fit. The application always operates on the "virtual" user interface
> > instance. This is also a MUCH, MUCH simpler problem - merely one of
> > identification - not presentation or negotiation (this is a highly
> > complicated area already). [This approach also allows the device to
> > store
> > customized application-specific interfaces that can be recalled as
> > required
> > whenever interacting with the same application.]
> 
> No - how can the phone create custom UI for an app when it 
> doesn't know
> what the app is ahead of time? The app presents the user interface. In
> the case of a phone with buttons, that means the app provides labels
> that should be associated with some of the buttons. In the case of a
> voice recording app, there could be one button that is labelled "start
> recording" and another "stop recording". The app needs a way 
> to tell the
> phone "label one button with 'start recording' and another with 'stop
> recording'. Tell me when one of these is pressed, and tell me which".
> The phone can decide whether to use the two top right buttons or the
> bottom left buttons; I agree on that. But, the key idea is 
> that the app
> is telling the phone information it must render to the user 
> in order to
> provide context for the button.
 
Okay now we are getting to a different discussion - how to do key-based
input. I'm sure we can fill another email with this discussion alone (and
this email is long enough already).

Anyway, I think we are thrashing out a few key model assumptions in building
these requirements - which is a very good thing. 

Regards,

Robert.

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



From daemon@ns.ietf.org  Mon Apr 29 06:16:54 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19212
	for <sipping-archive@odin.ietf.org>; Mon, 29 Apr 2002 06:16:54 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA10110
	for sipping-archive@odin.ietf.org; Mon, 29 Apr 2002 06:16:54 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA09093;
	Mon, 29 Apr 2002 05:59:42 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA09062
	for <sipping@ns.ietf.org>; Mon, 29 Apr 2002 05:59:34 -0400 (EDT)
Received: from btclick.com (mta04.btfusion.com [62.172.195.246])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18137
	for <sipping@ietf.org>; Mon, 29 Apr 2002 05:59:31 -0400 (EDT)
Received: from ictgateway.ictrnid.org.uk ([217.34.231.189]) by
          btclick.com (Netscape Messaging Server 4.15) with SMTP id
          GVBQEA03.9AT for <sipping@ietf.org>; Mon, 29 Apr 2002 10:58:58 +0100 
Received: from 192.168.1.35 ([192.168.1.35]) by ictgateway.ictrnid.org.uk (WinRoute Pro 4.1.29) with SMTP; Mon, 29 Apr 2002 11:10:07 +0100
Message-ID: <003901c1ef64$aac156d0$2301a8c0@LTGUIDO>
From: "Guido Gybels" <guido.gybels@rnid.org.uk>
To: <sipping@ietf.org>
Date: Mon, 29 Apr 2002 11:00:18 +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 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 7bit
Subject: [Sipping] draft-ietf-sipping-deaf-req-03.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Hi all,

The draft on "User requirements for the Session Initiation Protocol (SIP) in
support of deaf, hard of hearing and speech-impaired individuals" has been
updated into draft-ietf-sipping-deaf-req-03.txt and submitted to IETF as
well as to the chair of the SIPPING WG. In the mean time, you can find the
new draft on the Design Team Home Page at www.ictrnid.org.uk/sipping/ The
Activities page on the Design Team's homepage describes the changes to this
draft, mainly following up on comments from the Area Director. Please also
have a look at the open issues. The Design Team looks, as usual, forward to
your comments.

Guido

Guido Gybels, Head of ICT
guido.gybels@rnid.org.uk
Tel. 020-7294 3713
--
The Royal National Institute for Deaf People
Technology Directorate
19-23 Featherstone Street
London EC1Y 8SL - UK





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



From daemon@optimus.ietf.org  Mon Apr 29 08:47:37 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00445
	for <sipping-archive@odin.ietf.org>; Mon, 29 Apr 2002 08:47:36 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA18225
	for sipping-archive@odin.ietf.org; Mon, 29 Apr 2002 08:47:38 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA17727;
	Mon, 29 Apr 2002 08:36:03 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA17696
	for <sipping@optimus.ietf.org>; Mon, 29 Apr 2002 08:36:00 -0400 (EDT)
Received: from mail1.telekom.de (mail1.telekom.de [62.225.183.235])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29402
	for <sipping@ietf.org>; Mon, 29 Apr 2002 08:35:56 -0400 (EDT)
Received: from g8pbr.blf01.telekom.de by G8SBV.dmz.telekom.de with ESMTP for sipping@ietf.org; Mon, 29 Apr 2002 14:34:15 +0200
Received: by G8PBR.blf01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <JH632XQG>; Mon, 29 Apr 2002 14:35:27 +0200
Message-Id: <C835D57E3730D6119F5000A0C9F019A94A9A6C@U8P13.blf01.telekom.de>
From: "Jesske, R" <R.Jesske@telekom.de>
To: sipping@ietf.org
Date: Mon, 29 Apr 2002 14:35:26 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sipping] Question on draft-ietf-sipping-sipt-01
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Dear all,
within the above mentioned draft I have a question regarding the following section.

3.2.2 Terminator
   
   ...In order to make
   the determination about the PSTN termination the terminator looks
   either into the encapsulated ISUP that it has received, or the SIP
   header. ...

Are there any rules defined which information should be preferred, if there are differences between SIP headers and the encapsulated ISUP. 


Best Regards

Roland 


Deutsche Telekom AG
Zentralbereich Netzinfrastruktur (ZB NI)
Section NI196; Signalling, Gateways and Switching Systems 
Roland Jesske, NI196a12
Am Kavalleriesand 3, 64295 Darmstadt, Germany
Phone:  +49 6151 83-5940 
Fax:    +49 6151 83-4577 
mailto: r.jesske@telekom.de

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



From daemon@optimus.ietf.org  Mon Apr 29 09:14:26 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03591
	for <sipping-archive@odin.ietf.org>; Mon, 29 Apr 2002 09:14:26 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA19858
	for sipping-archive@odin.ietf.org; Mon, 29 Apr 2002 09:14:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA19118;
	Mon, 29 Apr 2002 09:01:11 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA19079
	for <sipping@optimus.ietf.org>; Mon, 29 Apr 2002 09:01:07 -0400 (EDT)
Received: from brmx1.fl.icn.siemens.com ([12.147.96.32])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02093
	for <sipping@ietf.org>; Mon, 29 Apr 2002 09:01:04 -0400 (EDT)
Received: from boca210a.boca.ssc.siemens.com (boca210a.boca.ssc.siemens.com [165.218.12.110])
	by brmx1.fl.icn.siemens.com (8.9.3/8.9.3) with ESMTP id JAA05791
	for <sipping@ietf.org>; Mon, 29 Apr 2002 09:01:06 -0400 (EDT)
Received: by boca210a.boca.ssc.siemens.com with Internet Mail Service (5.5.2653.19)
	id <JW98R1BZ>; Mon, 29 Apr 2002 09:01:06 -0400
Message-ID: <180577A42806D61189D30008C7E632E82715D9@boca213a.boca.ssc.siemens.com>
From: "Chaney, Charles" <Charles.Chaney@icn.siemens.com>
To: sipping@ietf.org
Subject: [Sipping] SIP-T signaling to manage bilateral agreements
Date: Mon, 29 Apr 2002 09:01:06 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1EF7D.EC7E1180"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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

It's likely this has come up before but I can't seem to locate any
information on it:
 
From the information in <draft-ietf-sipping-isup-01> and RFC 3204, there is
no mention for including the circuit identification code from the ISUP
header in the SIP message body or the encapsulated ISUP since the
encapsulation starts at the message type code. In the PSTN the circuit code
is part of the ISUP message header and its handling is fully standardized.
It is used to not only identify the involved circuit or connection but also
allows assignment of specific handling by the source and destination network
nodes via bilateral agreements. These circuits are typically grouped
together in ranges, a.k.a., Trunk Groups and assigned special handling
properties. For there to be any form of interoperability between networks
(e.g., SIP bridging) support for this is fundamental. 
 
While there are some options that could be considered, the support must be
agreed (as a standard?) since multi-vendors are likely involved. Some
examples that one might consider for signaling the bilateral agreement
requirements:
 
- Dedicated SIP Call-Id allocation algorithms, known by the involved
signaling nodes.
 
- MG SDP (e.g., RTP address and port number) assignment and bilateral
knowledge about this allocation in involved call partner MGC assignments,
SDP.  
 
- Static assignment at the transport level, e.g., UDP port number could be
associated with a grouping of these circuits if UDP is used. Other transport
support would require further investigation.
 
- None of the above are proposals at this time, they are only meant to be
examples to further the discussion. Maybe there are others?
 
 
Regards,
Chuck Chaney

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

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


<META content="MSHTML 5.00.2920.0" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2><SPAN class=131065311-29042002>It's likely 
this&nbsp;has come up before but I can't seem to locate any information on 
it:</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN 
class=131065311-29042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2><SPAN class=131065311-29042002>From the information 
in &lt;draft-ietf-sipping-isup-01&gt; and RFC 3204, there is no 
mention&nbsp;for&nbsp;including the circuit identification code from the ISUP 
header in the SIP message body or the encapsulated ISUP since the encapsulation 
starts at the message type code. In the PSTN the circuit code is part of the 
ISUP message header and its handling&nbsp;is fully standardized. It is 
used&nbsp;to not only identify the involved circuit or connection but&nbsp;also 
allows assignment of specific handling by the&nbsp;source and destination 
network&nbsp;nodes via&nbsp;bilateral agreements. These circuits are typically 
grouped together in ranges, a.k.a., Trunk Groups and assigned special handling 
properties. For there to be any&nbsp;form of interoperability between networks 
(e.g., SIP&nbsp;bridging) support for this is fundamental. </SPAN></FONT></DIV>
<DIV><FONT size=2><SPAN class=131065311-29042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2><SPAN class=131065311-29042002>While there are some 
options that could be considered, the support&nbsp;must&nbsp;be&nbsp;agreed (as 
a standard?) since multi-vendors are likely involved. Some examples&nbsp;that 
one might&nbsp;consider for signaling the&nbsp;bilateral agreement 
requirements:</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN 
class=131065311-29042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2><SPAN class=131065311-29042002>- Dedicated SIP 
Call-Id allocation algorithms, known by the involved signaling 
nodes.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN 
class=131065311-29042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2><SPAN class=131065311-29042002>- MG&nbsp;SDP (e.g., 
RTP address and port number) assignment and bilateral knowledge about this 
allocation in involved&nbsp;call partner MGC assignments,&nbsp;SDP.&nbsp; 
</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN 
class=131065311-29042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2><SPAN class=131065311-29042002>-&nbsp;Static 
assignment at the transport level, e.g.,&nbsp;UDP port number could be 
associated with a grouping of these circuits if UDP is used. Other transport 
support would require further investigation.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN 
class=131065311-29042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2><SPAN class=131065311-29042002>- None of the above 
are proposals at this time, they are only meant to be examples to further the 
discussion. Maybe there are others?</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial size=2><SPAN 
class=131065311-29042002>Regards,</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=131065311-29042002>Chuck 
Chaney</SPAN></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01C1EF7D.EC7E1180--

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



From daemon@optimus.ietf.org  Mon Apr 29 11:13:29 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17178
	for <sipping-archive@odin.ietf.org>; Mon, 29 Apr 2002 11:13:29 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA27868
	for sipping-archive@odin.ietf.org; Mon, 29 Apr 2002 11:13:28 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA27121;
	Mon, 29 Apr 2002 11:00:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA27091
	for <sipping@optimus.ietf.org>; Mon, 29 Apr 2002 11:00:54 -0400 (EDT)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15596
	for <sipping@ietf.org>; Mon, 29 Apr 2002 11:00:51 -0400 (EDT)
Received: from cia.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g3TF0hEN012768;
	Mon, 29 Apr 2002 11:00:43 -0400 (EDT)
Received: from MHAMMER-W2K.cisco.com (hrn2-dhcp-161-44-87-145.cisco.com [161.44.87.145])
	by cia.cisco.com (Mirapoint)
	with ESMTP id AAU88041;
	Mon, 29 Apr 2002 10:55:16 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020429105547.00b79a08@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 29 Apr 2002 11:00:15 -0400
To: "Jesske, R" <R.Jesske@telekom.de>
From: Michael Hammer <mhammer@cisco.com>
Subject: Re: [Sipping] Question on draft-ietf-sipping-sipt-01
Cc: sipping@ietf.org
In-Reply-To: <C835D57E3730D6119F5000A0C9F019A94A9A6C@U8P13.blf01.telekom
 .de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Roland,

I would suggest that having traveled through a SIP network that may modify 
SIP headers, that those generally would be preferred.  However, there are 
transit cases where you want to preserve information from the ingress to 
the SIP network on egress from SIP to a PSTN network, such as Cause 
codes.  A SIP node that can modify the ISUP should also update 
corresponding SIP headers.  Only when there is no equivalent SIP header, 
should an ISUP header be preferred.  To be sure, you have to look at each 
header or ISUP parameter on a case by case basis.

Mike


At 02:35 PM 4/29/2002 +0200, Jesske, R wrote:
>Dear all,
>within the above mentioned draft I have a question regarding the following 
>section.
>
>3.2.2 Terminator
>
>    ...In order to make
>    the determination about the PSTN termination the terminator looks
>    either into the encapsulated ISUP that it has received, or the SIP
>    header. ...
>
>Are there any rules defined which information should be preferred, if 
>there are differences between SIP headers and the encapsulated ISUP.
>
>
>Best Regards
>
>Roland
>
>
>Deutsche Telekom AG
>Zentralbereich Netzinfrastruktur (ZB NI)
>Section NI196; Signalling, Gateways and Switching Systems
>Roland Jesske, NI196a12
>Am Kavalleriesand 3, 64295 Darmstadt, Germany
>Phone:  +49 6151 83-5940
>Fax:    +49 6151 83-4577
>mailto: r.jesske@telekom.de
>
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the 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 daemon@ns.ietf.org  Mon Apr 29 12:46:22 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27088
	for <sipping-archive@odin.ietf.org>; Mon, 29 Apr 2002 12:46:22 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA03858
	for sipping-archive@odin.ietf.org; Mon, 29 Apr 2002 12:46:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA03585;
	Mon, 29 Apr 2002 12:36:33 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA03554
	for <sipping@ns.ietf.org>; Mon, 29 Apr 2002 12:36:30 -0400 (EDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25713
	for <sipping@ietf.org>; Mon, 29 Apr 2002 12:36:28 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g3TGZwTZ010130;
	Mon, 29 Apr 2002 09:35:58 -0700 (PDT)
Received: from localhost (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint Messaging Server MOS 3.1.0.54-GA)
	with ESMTP id AAC24303;
	Mon, 29 Apr 2002 09:35:56 -0700 (PDT)
Date: Mon, 29 Apr 2002 09:32:49 -0700 (Pacific Daylight Time)
From: Rohan Mahy <rohan@cisco.com>
To: mpierce1@aol.com
cc: sipping@ietf.org
Message-ID: <Pine.WNT.4.44.0204290918100.-249533@chorizo.rapidconvergence.com>
X-X-Sender: rmahy@imop.cisco.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Sipping] re: comments on cc-framework
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Hi,

I haven't received enough comments to warrant an update to the draft at
this point.  I am planning to incorporate almost all of Mike's comments. I
would like to reply to one of Mike's comments here however.

----
4.7 This statement that "only the invoker[s] of features in SIP know
exactly which feature they are invoking" sounds good in theory, but the
reality for telephony services is that often both parties (devices) need
to explicitly know what service is being performed, not just what
signaling primitives are being used. It is clear, for example, that the
processing of an INVITE or a REFER depends on the reason it was sent,
whether it is a new call or a transfer or a barge in, etc.

Rohan> I disagree.  I have run through dozens of features which use these
Rohan> features and I have never had this problem.  I suppose I can't
Rohan> expect you and others to just take my word on faith so I will try
Rohan> to come up with some more convincing examples.  Please feel free
Rohan> to come up with a counter-example.

The example of Alice calling Bob who transfers to Carol, while Alice has
her robotic assistant Alice "conferenced" illustrates this. First, the
independence of these two separate "features" would not be compromised if
the message from Bob to Alice explicitly said "transfer" rather than the
generic "REFER".

Rohan> I'm not convinced, but assuming you are correct, what benefit would
Rohan> this have?

Secondly, one should assume that the interaction between
the "robotic" feature at Alice with transfer (caused by receipt of the
REFER) might have to be different than the interaction between this
"robotic feature" and other features caused by receipt of REFER.

Rohan> Why?

When this
happens, attempts will have to be made at the receiving end (Ann) to
deduce what was intended in order to figure out what the best course of
action is to provide a good service.

Rohan> I disagree.  The basis for the model is that the sender asks the
Rohan> receiver to invoke a well-defined primitive.  The receiver can use
Rohan> very simple rules to figure out whether to authorize whole
Rohan> categories of requests or not.  The sender is free to use these
Rohan> primitives for whatever service they can invoke with the primitives
Rohan> at hand.

thanks,
-rohan

------------

To: sipping@ietf.org
Subject: [Sipping] Comments on draft-cc-framework
From: Mpierce1@aol.com
Date: Fri, 26 Apr 2002 15:42:14 EDT
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
Sender: sipping-admin@ietf.org

--------------------------------------------------------------------------------
To all,

I submitted comments on draft-ietf-sipping-cc-framework-00 (Feb) before
the March meeting, but have seen no responses or other comments. I will
repeat these comments with some others added:

3.1 Final bullet item: It isn't clear what point is being made about the
model from H.450.  While the goal says "do not reinvent", the rest of the
statement seems to say that SIP will not use an existing model, but rather
reinvent it.

4.1.1 This section notes that existing terms "call" and "conference" are
not well defined, so it uses a new term "conversation space". While this
concept seems useful, it is not well defined either. The statement that it
is "essentially a set of participants who believe they are all
communicating among one another" is not precise enough.

4.5.2 Reference to serving the queue should refer to "the first call in
the relevant queue" not the "last".

5.2.2 The statement that "there is no way to distinguish between the
desire to go on or off hold" is interesting. Is this meant to say that the
REFER method mentioned won't work for this and some better method is
needed?

5.3 1 Since B apparently has to do something before C replaces A, the
description of this primitive should be: "A requests to be replaced with
C"

5.3.2 Since B has to do something with the INVITE (stop sending media to
C, start using media from A rather than C, etc) this really isn't "A
forcibly replacing C with itself". It's really still just a request from A
for B to replace C with A.

The note regarding the need to take different action depending on the
state of the receiving entity "B", refers to a problem that affects many
of the primitives described. Because of overlapping actions, practically
every action at the receiving entity needs to consider the state of the
receiver before taking the described action. However, the model for this
work seems to be that the sender decides the action required and the
receiver must do it.

5.3.5 As above, this is just a "request" by A to be inserted into an
existing space. B must actually do it upon receipt of the INVITE, meaning
that B can refuse (as implied by the phrase "if B accepted the
INVITE..."). Therefore, the statement should be:

A requests to be inserted into a conversation space.

5.3.6 should have a statement added after the depiction of the change of
conversation space that says what is happening. It appears to be the
following:

A causes conversation space to be split into two with itself and B making
up the new conversation space.

5.3.7 It is not clear from the diagram and statement before it what has
happened. It should say:

The conversation space changes like this:
( A , B ) --> (B , A ) & ( A , C )
A creates a new conversation space with C and participates in both as the
"anchor".


Mike Pierce
Artel



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



From daemon@ns.ietf.org  Mon Apr 29 13:09:55 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29248
	for <sipping-archive@odin.ietf.org>; Mon, 29 Apr 2002 13:09:55 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA05509
	for sipping-archive@odin.ietf.org; Mon, 29 Apr 2002 13:09:56 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA04358;
	Mon, 29 Apr 2002 12:58:34 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA04324
	for <sipping@ns.ietf.org>; Mon, 29 Apr 2002 12:58:31 -0400 (EDT)
Received: from zctfs063.europe.nortel.com (zctfs063.nortelnetworks.com [47.164.128.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28586
	for <sipping@ietf.org>; Mon, 29 Apr 2002 12:58:29 -0400 (EDT)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zctfs063.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3TGvr918344;
	Mon, 29 Apr 2002 18:57:53 +0200 (MEST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3TGvAZ22501;
	Mon, 29 Apr 2002 17:57:10 +0100 (BST)
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <J7Q0Y2WY>; Mon, 29 Apr 2002 17:57:52 +0100
Message-ID: <A3C2399B2FACD411A54200508BE39C74054F71A7@zwcwd00r.europe.nortel.com>
From: "Mark Watson"<mwatson@nortelnetworks.com>
To: "'Jagannathan R'" <jaganathan.ramaswamy@alcatel.com>, sipping@ietf.org
Subject: RE: [Sipping] SIP/SIPT - ISUP/BICC Interworking
Date: Mon, 29 Apr 2002 17:57:49 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1EF9E.FE1D5B14"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

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

Hmm - I missed this draft. Not sure if it was sent to this list ?
 
We discussed this some 18 months ago on the SIP list.
 
BICC is basically ISUP plus extensions for controlling IP/ATM bearers in
place of TDM bearers. If you take the IP/ATM stuff out of BICC, then ISUP is
all that you are (should be) left with.
 
If you're interworking BICC with SIP, then you interwork all the bearer
stuff with SDP, so all you're left with is ISUP. So you never need to carry
BICC in SIP, you only need to carry ISUP.
 
Even if there was something which was in BICC and not ISUP, and which was
not related to Bearer Control, then we should discuss the correct way to
incorporate the function into SIP, not encapsulate BICC. What exactly are
the BICC capabilities that fall into this category that are applicable in a
SIP environment ?
 
Regards,
 
Mark

-----Original Message-----
From: Jagannathan R [mailto:jaganathan.ramaswamy@alcatel.com]
Sent: 29 April 2002 10:47
To: sipping@ietf.org
Subject: [Sipping] SIP/SIPT - ISUP/BICC Interworking


Hi,
 
   After having look at the I-D draft-chang-sipping-bicc-network-00.txt and
draft-ietf-sipping-sipt-01.txt, I am thoroughly confused about the
interworking of SIP-PSTN. Can some one help me to understand the difference
between or the different purposes of 
 
1. SIP-T which is primarily conceived for SIP-PSTN interworking (???)
2. SIP - BICC interworking.
 
I do know that BICC is basically for Inter MGC communication either within a
single network or across the networks. 
 
This bicc draft describes that extending SIP to support call control across
different networks. This extension encapsulates
BICC in the SIP message to provide the information needed across networks.
Integrating both SIP and BICC features,
this extension provides service providers a vehicle to deploy services
across different administration domains and different types of network.
 
My basic doubt is, by deploying SIP-T across the networks can't we achieve
this same purpose. If yes then, why one more framework on bicc?
 
Or am I missing some thing?
 
thanks,
jagannathan
 


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

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


<META content="MSHTML 5.00.3315.2870" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN class=027594616-29042002>Hmm 
- I missed this draft. Not sure if it was sent to this list 
?</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=027594616-29042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN class=027594616-29042002>We 
discussed this some 18 months ago on the SIP list.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=027594616-29042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN class=027594616-29042002>BICC 
is basically ISUP plus extensions for controlling IP/ATM bearers in place of TDM 
bearers. If you take the IP/ATM stuff out of BICC, then ISUP is all that you are 
(should be) left with.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=027594616-29042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN class=027594616-29042002>If 
you're interworking BICC with SIP, then you interwork all the bearer stuff with 
SDP, so all you're left with is ISUP. So you never need to carry BICC in SIP, 
you only need to carry ISUP.</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN class=027594616-29042002>Even 
if there was something which was in BICC and not ISUP, and which was not related 
to Bearer Control, then we should discuss the correct way to incorporate the 
function into SIP, not encapsulate BICC. What exactly are the BICC capabilities 
that fall into this category that are applicable in a SIP environment 
?</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=027594616-29042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=027594616-29042002>Regards,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=027594616-29042002></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Verdana size=1><SPAN 
class=027594616-29042002>Mark</SPAN></FONT></DIV>
<BLOCKQUOTE 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Jagannathan R 
  [mailto:jaganathan.ramaswamy@alcatel.com]<BR><B>Sent:</B> 29 April 2002 
  10:47<BR><B>To:</B> sipping@ietf.org<BR><B>Subject:</B> [Sipping] SIP/SIPT - 
  ISUP/BICC Interworking<BR><BR></DIV></FONT>
  <DIV><FONT face=Arial size=2>Hi,</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>&nbsp;&nbsp; After having look at the I-D 
  <STRONG>draft-chang-sipping-bicc-network-00.txt</STRONG> and 
  <STRONG>draft-ietf-sipping-sipt-01.txt,</STRONG> I am thoroughly confused 
  about the interworking of SIP-PSTN. Can some one help me to understand the 
  difference between or the different purposes of&nbsp;</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>1.&nbsp;SIP-T which is primarily conceived for 
  SIP-PSTN interworking (???)</FONT></DIV>
  <DIV><FONT face=Arial size=2>2. SIP - BICC interworking.</FONT></DIV>
  <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>I do know that BICC is basically for Inter MGC 
  communication either within a single network or across the networks. 
  </FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>This&nbsp;bicc draft describes 
  that&nbsp;extending SIP to support call control across different networks. 
  This extension encapsulates<BR>BICC in the SIP message to provide the 
  information needed across networks. Integrating both SIP and BICC 
  features,</FONT></DIV>
  <DIV><FONT face=Arial size=2>this extension provides service providers a 
  vehicle to deploy services across different administration domains and 
  different types of network.</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>My basic doubt is, by deploying SIP-T across the 
  networks can't we achieve this same purpose. If yes then, why one more 
  framework on bicc?</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>Or am I missing some thing?</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=Arial size=2>thanks,</FONT></DIV>
  <DIV><FONT face=Arial size=2>jagannathan</FONT></DIV>
  <DIV>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C1EF9E.FE1D5B14--

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



From daemon@ns.ietf.org  Mon Apr 29 17:45:03 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21000
	for <sipping-archive@odin.ietf.org>; Mon, 29 Apr 2002 17:45:03 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA24204
	for sipping-archive@odin.ietf.org; Mon, 29 Apr 2002 17:45:06 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA23595;
	Mon, 29 Apr 2002 17:31:42 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA23568
	for <sipping@ns.ietf.org>; Mon, 29 Apr 2002 17:31:39 -0400 (EDT)
Received: from dgesmtp02.wcom.com (dgesmtp02.wcom.com [199.249.16.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20699
	for <sipping@ietf.org>; Mon, 29 Apr 2002 17:31:35 -0400 (EDT)
Received: from CONVERSION-DAEMON by firewall.wcom.com (PMDF V5.2-33 #42261)
 id <0GVC00301MFTIB@firewall.wcom.com> for sipping@ietf.org; Mon,
 29 Apr 2002 21:31:06 +0000 (GMT)
Received: from dgismtp04.wcomnet.com ([166.38.58.144])
 by firewall.wcom.com (PMDF V5.2-33 #42261)
 with ESMTP id <0GVC000EPM9QMH@firewall.wcom.com>; Mon,
 29 Apr 2002 21:31:05 +0000 (GMT)
Received: from dgismtp04.wcomnet.com by dgismtp04.wcomnet.com
 (iPlanet Messaging Server 5.1 (built May  7 2001))
 with SMTP id <0GVC00A01ME2P4@dgismtp04.wcomnet.com>; Mon,
 29 Apr 2002 21:30:43 +0000 (GMT)
Received: from hsinnreich2 ([166.35.224.250])
 by dgismtp04.wcomnet.com (iPlanet Messaging Server 5.1 (built May  7 2001))
 with ESMTP id <0GVC00A8QMEW6X@dgismtp04.wcomnet.com>; Mon,
 29 Apr 2002 21:30:34 +0000 (GMT)
Date: Mon, 29 Apr 2002 16:30:32 -0500
From: Henry Sinnreich <Henry.Sinnreich@wcom.com>
Subject: RE: [Sipping] re: comments on cc-framework
In-reply-to: <Pine.WNT.4.44.0204290918100.-249533@chorizo.rapidconvergence.com>
To: "'Rohan Mahy'" <rohan@cisco.com>, mpierce1@aol.com
Cc: sipping@ietf.org
Message-id: <002f01c1efc5$18665540$fae023a6@hsinnreich2>
Organization: WorldCom, Inc.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

> I haven't received enough comments 

The only comment I have is keep going with this excellent draft!

Henry

> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] 
> On Behalf Of Rohan Mahy
> Sent: Monday, April 29, 2002 11:33 AM
> To: mpierce1@aol.com
> Cc: sipping@ietf.org
> Subject: [Sipping] re: comments on cc-framework
> 
> 
> Hi,
> 
> I haven't received enough comments to warrant an update to 
> the draft at this point.  I am planning to incorporate almost 
> all of Mike's comments. I would like to reply to one of 
> Mike's comments here however.
> 
> ----
> 4.7 This statement that "only the invoker[s] of features in 
> SIP know exactly which feature they are invoking" sounds good 
> in theory, but the reality for telephony services is that 
> often both parties (devices) need to explicitly know what 
> service is being performed, not just what signaling 
> primitives are being used. It is clear, for example, that the 
> processing of an INVITE or a REFER depends on the reason it 
> was sent, whether it is a new call or a transfer or a barge in, etc.
> 
> Rohan> I disagree.  I have run through dozens of features which use 
> Rohan> these features and I have never had this problem.  I suppose I 
> Rohan> can't expect you and others to just take my word on faith so I 
> Rohan> will try to come up with some more convincing 
> examples.  Please 
> Rohan> feel free to come up with a counter-example.
> 
> The example of Alice calling Bob who transfers to Carol, 
> while Alice has her robotic assistant Alice "conferenced" 
> illustrates this. First, the independence of these two 
> separate "features" would not be compromised if the message 
> from Bob to Alice explicitly said "transfer" rather than the 
> generic "REFER".
> 
> Rohan> I'm not convinced, but assuming you are correct, what benefit 
> Rohan> would this have?
> 
> Secondly, one should assume that the interaction between
> the "robotic" feature at Alice with transfer (caused by receipt of the
> REFER) might have to be different than the interaction 
> between this "robotic feature" and other features caused by 
> receipt of REFER.
> 
> Rohan> Why?
> 
> When this
> happens, attempts will have to be made at the receiving end 
> (Ann) to deduce what was intended in order to figure out what 
> the best course of action is to provide a good service.
> 
> Rohan> I disagree.  The basis for the model is that the 
> sender asks the 
> Rohan> receiver to invoke a well-defined primitive.  The receiver can 
> Rohan> use very simple rules to figure out whether to authorize whole 
> Rohan> categories of requests or not.  The sender is free to 
> use these 
> Rohan> primitives for whatever service they can invoke with the 
> Rohan> primitives at hand.
> 
> thanks,
> -rohan
> 
> ------------
> 
> To: sipping@ietf.org
> Subject: [Sipping] Comments on draft-cc-framework
> From: Mpierce1@aol.com
> Date: Fri, 26 Apr 2002 15:42:14 EDT
> List-Id: SIPPING Working Group (applications of SIP) 
> <sipping.ietf.org>
> Sender: sipping-admin@ietf.org
> 
> --------------------------------------------------------------
> ------------------
> To all,
> 
> I submitted comments on draft-ietf-sipping-cc-framework-00 
> (Feb) before the March meeting, but have seen no responses or 
> other comments. I will repeat these comments with some others added:
> 
> 3.1 Final bullet item: It isn't clear what point is being 
> made about the model from H.450.  While the goal says "do not 
> reinvent", the rest of the statement seems to say that SIP 
> will not use an existing model, but rather reinvent it.
> 
> 4.1.1 This section notes that existing terms "call" and 
> "conference" are not well defined, so it uses a new term 
> "conversation space". While this concept seems useful, it is 
> not well defined either. The statement that it is 
> "essentially a set of participants who believe they are all 
> communicating among one another" is not precise enough.
> 
> 4.5.2 Reference to serving the queue should refer to "the 
> first call in the relevant queue" not the "last".
> 
> 5.2.2 The statement that "there is no way to distinguish 
> between the desire to go on or off hold" is interesting. Is 
> this meant to say that the REFER method mentioned won't work 
> for this and some better method is needed?
> 
> 5.3 1 Since B apparently has to do something before C 
> replaces A, the description of this primitive should be: "A 
> requests to be replaced with C"
> 
> 5.3.2 Since B has to do something with the INVITE (stop 
> sending media to C, start using media from A rather than C, 
> etc) this really isn't "A forcibly replacing C with itself". 
> It's really still just a request from A for B to replace C with A.
> 
> The note regarding the need to take different action 
> depending on the state of the receiving entity "B", refers to 
> a problem that affects many of the primitives described. 
> Because of overlapping actions, practically every action at 
> the receiving entity needs to consider the state of the 
> receiver before taking the described action. However, the 
> model for this work seems to be that the sender decides the 
> action required and the receiver must do it.
> 
> 5.3.5 As above, this is just a "request" by A to be inserted 
> into an existing space. B must actually do it upon receipt of 
> the INVITE, meaning that B can refuse (as implied by the 
> phrase "if B accepted the INVITE..."). Therefore, the 
> statement should be:
> 
> A requests to be inserted into a conversation space.
> 
> 5.3.6 should have a statement added after the depiction of 
> the change of conversation space that says what is happening. 
> It appears to be the
> following:
> 
> A causes conversation space to be split into two with itself 
> and B making up the new conversation space.
> 
> 5.3.7 It is not clear from the diagram and statement before 
> it what has happened. It should say:
> 
> The conversation space changes like this:
> ( A , B ) --> (B , A ) & ( A , C )
> A creates a new conversation space with C and participates in 
> both as the "anchor".
> 
> 
> Mike Pierce
> Artel
> 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sip@ietf.org for new developments of core SIP
> 


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



From daemon@ns.ietf.org  Mon Apr 29 18:34:44 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21777
	for <sipping-archive@odin.ietf.org>; Mon, 29 Apr 2002 18:34:44 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA27163
	for sipping-archive@odin.ietf.org; Mon, 29 Apr 2002 18:34:45 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA25816;
	Mon, 29 Apr 2002 18:21:54 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA25780
	for <sipping@ns.ietf.org>; Mon, 29 Apr 2002 18:21:51 -0400 (EDT)
Received: from radvpost.us.radvision.com ([12.44.63.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21542
	for <sipping@ietf.org>; Mon, 29 Apr 2002 18:21:47 -0400 (EDT)
Received: by RADVPOST with Internet Mail Service (5.5.2650.21)
	id <G2V5L9HX>; Mon, 29 Apr 2002 18:20:17 -0400
Message-ID: <0D5BBF5D638DD4119E3400508BD949459ED997@RADVPOST>
From: Orit Levin <orit@radvision.com>
To: "'sipping@ietf.org'" <sipping@ietf.org>
Cc: "'roni.even@polycom.co.il'" <roni.even@polycom.co.il>,
        "'zmolek@avaya.com'" <zmolek@avaya.com>,
        "'dpetrie@pingtel.com'"
	 <dpetrie@pingtel.com>,
        "'petkos@cs.columbia.edu'"
	 <IMCEAMAILTO-petkos+40cs+2Ecolumbia+2Eedu@radvision.com>
Date: Mon, 29 Apr 2002 18:20:16 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sipping] draft-levin-sipping-conferencing-requirements-00.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

We submitted this morning a 
"Conferencing Requirements for SIP Based Applications" draft
which is based on the direction discussed during a "Conferencing Lunch" in
Minneapolis.
Till the draft appears in the IETF directory, please, pick up a copy for
your review at
ftp://ftp.radvision.com/Standards/ <ftp://ftp.radvision.com/Standards/> 

Abstract 
    
   At present, SIP signaling sessions under a conferencing application 
   must rely on out-of-band signaling for participant information and 
   conference manipulation. This document suggests an integrated 
   approach that defines a Hierarchal Application Signaling Model and 
   allows SIP to support both basic and complex applications based on 
   more basic applications. As example conferencing applications, a 
   general "SIP Star Conferencing Application" and a more specialized 
   "SIP Star Real Time Multimedia Conferencing Application" are defined 
   within this Hierarchical Application Signaling Model. This document 
   identifies requirements for SIP entities that participate or host 
   these applications. 
   A future document will suggest the mapping of the requirements to 
   corresponding protocols and their primitives. 

Best Regards,
Orit Levin
Chief Architect
RADVISION Inc.
TEL: +1.201.529.4300 x 230
FAX: +1.201.529.3516


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



From daemon@ns.ietf.org  Mon Apr 29 19:16:26 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22753
	for <sipping-archive@odin.ietf.org>; Mon, 29 Apr 2002 19:16:25 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA00600
	for sipping-archive@odin.ietf.org; Mon, 29 Apr 2002 19:16:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA28914;
	Mon, 29 Apr 2002 19:03:56 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA28885
	for <sipping@ns.ietf.org>; Mon, 29 Apr 2002 19:03:53 -0400 (EDT)
Received: from bdsl.66.12.12.130.gte.net (bdsl.66.12.12.130.gte.net [66.12.12.130])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22351
	for <sipping@ietf.org>; Mon, 29 Apr 2002 19:03:50 -0400 (EDT)
Received: from TXDWILLIS2 (bdsl.greycouncil.com [127.0.0.1])
	by bdsl.66.12.12.130.gte.net (8.11.6/8.11.6) with ESMTP id g3TN3Md12920
	for <sipping@ietf.org>; Mon, 29 Apr 2002 18:03:22 -0500
From: "Dean Willis" <dean.willis@softarmor.com>
To: <sipping@ietf.org>
Date: Mon, 29 Apr 2002 18:03:03 -0500
Message-ID: <077c01c1efd2$04821890$1c2e713f@TXDWILLIS2>
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.3416
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [Sipping] FW: Request for Expert Review, draft-garcia-sip-associated-uri
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit


Sean suggested I cross-post to SIPPING as he thinks this might be
related to a topic of discussion here as well.

Please discuss the draft itself on the SIP list, and its applicability
to the SIPPING problem on the SIPPING list.

Thanks.

--
Dean

-----Original Message-----
From: Dean Willis [mailto:dwillis@dynamicsoft.com] 
Sent: Monday, April 29, 2002 5:34 PM
To: 'sip@ietf.org'
Cc: 'Miguel A. Garcia'; 'Rohan Mahy'; 'brian.rosen@marconi.com';
'jo@ipdialog.com'; 'Allison Mankin'
Subject: Request for Expert Review, draft-garcia-sip-associated-uri



The SIP WG has been asked to provide expert review on the individual
informational track draft-garcia-sip-associated-URI.

This draft provides a lightweight mechanism proposed by 3GPP by which
registrars may inform registering UAs of additional identities (not
listed in the To: header) that the registrar will assoicate with the
registered contact.

We would like to conclude review of this by March 10. 

The current version of the draft has been sent to internet-drafts and is
also available at:

http://www.softarmor.com/sipwg/drafts/draft-garcia-sip-associated-uri-00
.txt


Please copy comments to the list and to the author,
miguel.a.garcia@ericsson.com.

Thanks,

--
Dean Willis






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



From daemon@ns.ietf.org  Mon Apr 29 19:41:51 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23484
	for <sipping-archive@odin.ietf.org>; Mon, 29 Apr 2002 19:41:51 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA02940
	for sipping-archive@odin.ietf.org; Mon, 29 Apr 2002 19:41:53 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA01278;
	Mon, 29 Apr 2002 19:25:16 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA01247
	for <sipping@ns.ietf.org>; Mon, 29 Apr 2002 19:25:12 -0400 (EDT)
Received: from web11601.mail.yahoo.com (web11601.mail.yahoo.com [216.136.172.53])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA22993
	for <sipping@ietf.org>; Mon, 29 Apr 2002 19:25:10 -0400 (EDT)
Message-ID: <20020429232435.37878.qmail@web11601.mail.yahoo.com>
Received: from [207.46.137.9] by web11601.mail.yahoo.com via HTTP; Mon, 29 Apr 2002 16:24:35 PDT
Date: Mon, 29 Apr 2002 16:24:35 -0700 (PDT)
From: Sean Olson <seancolson@yahoo.com>
Subject: Re: [Sipping] FW: Request for Expert Review, draft-garcia-sip-associated-uri
To: Dean Willis <dean.willis@softarmor.com>, sipping@ietf.org
In-Reply-To: <077c01c1efd2$04821890$1c2e713f@TXDWILLIS2>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

To clarify,

I believe this extension might be related to the
binding problem that has been discussed in relation
to presence publication, CPL publication, etc.

/sean

--- Dean Willis <dean.willis@softarmor.com> wrote:
> 
> Sean suggested I cross-post to SIPPING as he thinks
> this might be
> related to a topic of discussion here as well.
> 
> Please discuss the draft itself on the SIP list, and
> its applicability
> to the SIPPING problem on the SIPPING list.
> 
> Thanks.
> 
> --
> Dean
> 
> -----Original Message-----
> From: Dean Willis [mailto:dwillis@dynamicsoft.com] 
> Sent: Monday, April 29, 2002 5:34 PM
> To: 'sip@ietf.org'
> Cc: 'Miguel A. Garcia'; 'Rohan Mahy';
> 'brian.rosen@marconi.com';
> 'jo@ipdialog.com'; 'Allison Mankin'
> Subject: Request for Expert Review,
> draft-garcia-sip-associated-uri
> 
> 
> 
> The SIP WG has been asked to provide expert review
> on the individual
> informational track draft-garcia-sip-associated-URI.
> 
> This draft provides a lightweight mechanism proposed
> by 3GPP by which
> registrars may inform registering UAs of additional
> identities (not
> listed in the To: header) that the registrar will
> assoicate with the
> registered contact.
> 
> We would like to conclude review of this by March
> 10. 
> 
> The current version of the draft has been sent to
> internet-drafts and is
> also available at:
> 
>
http://www.softarmor.com/sipwg/drafts/draft-garcia-sip-associated-uri-00
> .txt
> 
> 
> Please copy comments to the list and to the author,
> miguel.a.garcia@ericsson.com.
> 
> Thanks,
> 
> --
> Dean Willis
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Sipping mailing list 
> https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application
> of SIP
> Use sip-implementors@cs.columbia.edu for questions
> on current sip
> Use sip@ietf.org for new developments of core SIP


__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com

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



From daemon@optimus.ietf.org  Tue Apr 30 08:01:55 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15088
	for <sipping-archive@odin.ietf.org>; Tue, 30 Apr 2002 08:01:55 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA17928
	for sipping-archive@odin.ietf.org; Tue, 30 Apr 2002 08:01:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA16701;
	Tue, 30 Apr 2002 07:44:47 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA17234
	for <sipping@optimus.ietf.org>; Tue, 30 Apr 2002 00:30:05 -0400 (EDT)
Received: from ish7.ericsson.com.au (ish7.ericsson.com.au [203.61.155.111])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29690
	for <sipping@ietf.org>; Tue, 30 Apr 2002 00:30:01 -0400 (EDT)
Received: from brsf10.epa.ericsson.se (brsf10 [146.11.8.4])
	by ish7.ericsson.com.au (8.11.6+Sun/8.11.6) with ESMTP id g3U4SP019083;
	Tue, 30 Apr 2002 14:28:25 +1000 (EST)
Received: from ericsson.com.au (dhcp-239-110.epa.ericsson.se [146.11.239.110])
	by brsf10.epa.ericsson.se (8.11.6+Sun/8.9.3) with ESMTP id g3U4U0N13012;
	Tue, 30 Apr 2002 14:30:00 +1000 (EST)
Message-ID: <3CCDFA53.929C63EE@ericsson.com.au>
Date: Tue, 30 Apr 2002 11:58:43 +1000
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Mark Watson <mwatson@nortelnetworks.com>
CC: "'Jagannathan R'" <jaganathan.ramaswamy@alcatel.com>, sipping@ietf.org
Subject: Re: [Sipping] SIP/SIPT - ISUP/BICC Interworking
References: <A3C2399B2FACD411A54200508BE39C74054F71A7@zwcwd00r.europe.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

G'Day Mark,

I surprised on your bought of amnesia :). There's a few other differences
between ISUP and BICC:
o the CIC size was increased in BICC
o BICC supports codec negotiation
o BICC supports in-call bearer modification
o BICC supports bearer redirection
o BICC supports a split MGC (CSF) & MG(BIWF) architecture

But I agree with you in that we shouldn't be looking at encapsulating BICC, I
wouldn't be encapsulating ISUP either though.

Cheers, Christian




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



From daemon@optimus.ietf.org  Tue Apr 30 08:36:47 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17156
	for <sipping-archive@odin.ietf.org>; Tue, 30 Apr 2002 08:36:47 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA20576
	for sipping-archive@odin.ietf.org; Tue, 30 Apr 2002 08:36:49 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA15148;
	Tue, 30 Apr 2002 07:16:29 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA14947
	for <sipping@optimus.ietf.org>; Tue, 30 Apr 2002 07:16:10 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13188;
	Tue, 30 Apr 2002 07:16:01 -0400 (EDT)
Message-Id: <200204301116.HAA13188@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 30 Apr 2002 07:16:01 -0400
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-sipt-02.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

--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		: SIP for Telephones (SIP-T): Context and Architectures
	Author(s)	: A. Vemuri, J. Peterson
	Filename	: draft-ietf-sipping-sipt-02.txt
	Pages		: 30
	Date		: 29-Apr-02
	
SIP-T (earlier referred to as 'SIP-BCP-T') is a mechanism that uses
SIP to facilitate the interconnection of the PSTN with SIP networks.
This document explains the context and the architectures in which
SIP-T may be used.

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

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-sipping-sipt-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-sipt-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:	<20020429151423.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--



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



From daemon@optimus.ietf.org  Tue Apr 30 08:40:12 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17494
	for <sipping-archive@odin.ietf.org>; Tue, 30 Apr 2002 08:40:12 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA20871
	for sipping-archive@odin.ietf.org; Tue, 30 Apr 2002 08:40:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA15094;
	Tue, 30 Apr 2002 07:16:24 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA14915
	for <sipping@optimus.ietf.org>; Tue, 30 Apr 2002 07:16:08 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13205;
	Tue, 30 Apr 2002 07:16:06 -0400 (EDT)
Message-Id: <200204301116.HAA13205@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 30 Apr 2002 07:16:05 -0400
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-deaf-req-03.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

--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		: User Requirements for the Session Initiation Protocol 
                         (SIP) in support of deaf, hard of hearing and 
                         speech-impaired individuals
	Author(s)	: N. Charlton et al.
	Filename	: draft-ietf-sipping-deaf-req-03.txt
	Pages		: 13
	Date		: 29-Apr-02
	
This document aims to present a set of SIP user requirements that
support communications for deaf, hard of hearing and speech-impaired
individuals. These user requirements address the current difficulties
of deaf, hard of hearing and speech-impaired individuals in using
communications facilities, while acknowledging the multi-functional
potential of SIP-based communications.
A number of issues related to these user requirements are further
raised in this document.
Also included are some real world scenarios and some technical
requirements to show the robustness of these requirements on a
concept-level.

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

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-sipping-deaf-req-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-deaf-req-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:	<20020429151432.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-deaf-req-03.txt

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

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

--OtherAccess--

--NextPart--



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



From daemon@optimus.ietf.org  Tue Apr 30 09:21:24 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19143
	for <sipping-archive@odin.ietf.org>; Tue, 30 Apr 2002 09:21:24 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA23019
	for sipping-archive@odin.ietf.org; Tue, 30 Apr 2002 09:21:27 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA22441;
	Tue, 30 Apr 2002 09:06:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA22410
	for <sipping@optimus.ietf.org>; Tue, 30 Apr 2002 09:06:28 -0400 (EDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18621
	for <sipping@ietf.org>; Tue, 30 Apr 2002 09:06:25 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g3UD5qd12892
	for <sipping@ietf.org>; Tue, 30 Apr 2002 09:05:52 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <JZN78B59>; Tue, 30 Apr 2002 09:05:56 -0400
Message-ID: <4D79C746863DD51197690002A52CDA0001E8A3B9@zcard0kc.ca.nortel.com>
From: "Tom-PT Taylor"<taylor@nortelnetworks.com>
To: "'Christian Groves'" <Christian.Groves@ericsson.com.au>
Cc: "'Jagannathan R'" <jaganathan.ramaswamy@alcatel.com>, sipping@ietf.org,
        "Mark Watson"<mwatson@nortelnetworks.com>
Subject: RE: [Sipping] SIP/SIPT - ISUP/BICC Interworking
Date: Tue, 30 Apr 2002 09:05:54 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Aside from the CIC size issue, doesn't BICC hive off the bearer-related
stuff in the APM message, which makes it just as easy to use SDP instead in
SIP messages?  Also, I thought the BIWF included more than the MG function,
since it adds the Bearer Control function needed for ATM networks.

-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@ericsson.com.au]
Sent: Monday, April 29, 2002 9:59 PM
To: Watson, Mark [MDN05:EP10:EXCH]
Cc: 'Jagannathan R'; sipping@ietf.org
Subject: Re: [Sipping] SIP/SIPT - ISUP/BICC Interworking


G'Day Mark,

I surprised on your bought of amnesia :). There's a few other differences
between ISUP and BICC:
o the CIC size was increased in BICC
o BICC supports codec negotiation
o BICC supports in-call bearer modification
o BICC supports bearer redirection
o BICC supports a split MGC (CSF) & MG(BIWF) architecture

But I agree with you in that we shouldn't be looking at encapsulating BICC,
I
wouldn't be encapsulating ISUP either though.

Cheers, Christian




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

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



From daemon@optimus.ietf.org  Tue Apr 30 12:18:04 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27329
	for <sipping-archive@odin.ietf.org>; Tue, 30 Apr 2002 12:18:04 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA06191
	for sipping-archive@odin.ietf.org; Tue, 30 Apr 2002 12:18:07 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA05334;
	Tue, 30 Apr 2002 12:04:25 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA05305
	for <sipping@optimus.ietf.org>; Tue, 30 Apr 2002 12:04:22 -0400 (EDT)
Received: from smtp1.arnet.com.ar (smtp1.arnet.com.ar [200.45.191.6])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA26814
	for <sipping@ietf.org>; Tue, 30 Apr 2002 12:04:18 -0400 (EDT)
Received: (qmail 19942 invoked from network); 30 Apr 2002 15:38:02 -0000
Received: from host000004.arnet.net.ar (HELO mail1.arnet.com.ar) (200.45.0.4)
  by smtp1.arnet.com.ar with SMTP; 30 Apr 2002 15:38:02 -0000
Received: from mail pickup service by mail1.arnet.com.ar with Microsoft SMTPSVC;
	 Tue, 30 Apr 2002 12:37:44 -0300
Received: from mx2.arnet.com.ar ([200.45.0.3]) by mail1.arnet.com.ar  with Microsoft SMTPSVC(5.5.1877.677.67);
	 Tue, 30 Apr 2002 11:30:25 -0300
Received: from smtp-mx-01.ti.local ([200.45.48.20]) by mx2.arnet.com.ar  with Microsoft SMTPSVC(5.5.1877.357.35);
	 Tue, 30 Apr 2002 11:29:23 -0300
Received: from loki.ietf.org ([132.151.1.177]) by smtp-mx-01.ti.local with Microsoft SMTPSVC(5.0.2195.4905);
	 Tue, 30 Apr 2002 11:26:04 -0300
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id KAA21248
	for ietf-123-outbound.01@ietf.org; Tue, 30 Apr 2002 10:25:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id HAA19705
	for <all-ietf@loki.ietf.org>; Tue, 30 Apr 2002 07:16:08 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13205;
	Tue, 30 Apr 2002 07:16:06 -0400 (EDT)
Message-Id: <200204301116.HAA13205@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 30 Apr 2002 07:16:05 -0400
X-OriginalArrivalTime: 30 Apr 2002 14:26:04.0882 (UTC) FILETIME=[F6087B20:01C1F052]
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-deaf-req-03.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

--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		: User Requirements for the Session Initiation Protocol 
                         (SIP) in support of deaf, hard of hearing and 
                         speech-impaired individuals
	Author(s)	: N. Charlton et al.
	Filename	: draft-ietf-sipping-deaf-req-03.txt
	Pages		: 13
	Date		: 29-Apr-02
	
This document aims to present a set of SIP user requirements that
support communications for deaf, hard of hearing and speech-impaired
individuals. These user requirements address the current difficulties
of deaf, hard of hearing and speech-impaired individuals in using
communications facilities, while acknowledging the multi-functional
potential of SIP-based communications.
A number of issues related to these user requirements are further
raised in this document.
Also included are some real world scenarios and some technical
requirements to show the robustness of these requirements on a
concept-level.

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

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-sipping-deaf-req-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-deaf-req-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:	<20020429151432.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-deaf-req-03.txt

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

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

--OtherAccess--

--NextPart--


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



From daemon@optimus.ietf.org  Tue Apr 30 13:16:38 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29391
	for <sipping-archive@odin.ietf.org>; Tue, 30 Apr 2002 13:16:38 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA09631
	for sipping-archive@odin.ietf.org; Tue, 30 Apr 2002 13:16:40 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA08620;
	Tue, 30 Apr 2002 13:01:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA08585
	for <sipping@optimus.ietf.org>; Tue, 30 Apr 2002 13:01:13 -0400 (EDT)
Received: from smtp2.arnet.com.ar (smtp2.arnet.com.ar [200.45.191.5])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA28926
	for <sipping@ietf.org>; Tue, 30 Apr 2002 13:01:07 -0400 (EDT)
Received: (qmail 10893 invoked from network); 30 Apr 2002 15:39:25 -0000
Received: from unknown (HELO arnet.com.ar) (200.45.0.20)
  by smtp2.arnet.com.ar with SMTP; 30 Apr 2002 15:39:25 -0000
Received: from mail pickup service by arnet.com.ar with Microsoft SMTPSVC;
	 Tue, 30 Apr 2002 12:37:04 -0300
Received: from mx1.arnet.com.ar ([200.45.0.2]) by mail1.arnet.com.ar  with Microsoft SMTPSVC(5.5.1877.677.67);
	 Tue, 30 Apr 2002 11:19:44 -0300
Received: from smtp-mx-02.ti.local ([200.45.48.21]) by mx1.arnet.com.ar  with Microsoft SMTPSVC(5.5.1877.357.35);
	 Tue, 30 Apr 2002 11:19:44 -0300
Received: from loki.ietf.org ([132.151.1.177]) by smtp-mx-02.ti.local with Microsoft SMTPSVC(5.0.2195.4905);
	 Tue, 30 Apr 2002 11:15:54 -0300
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id KAA21179
	for ietf-123-outbound.01@ietf.org; Tue, 30 Apr 2002 10:15:00 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id HAA19692
	for <all-ietf@loki.ietf.org>; Tue, 30 Apr 2002 07:16:04 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13188;
	Tue, 30 Apr 2002 07:16:01 -0400 (EDT)
Message-Id: <200204301116.HAA13188@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: sipping@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 30 Apr 2002 07:16:01 -0400
X-OriginalArrivalTime: 30 Apr 2002 14:16:15.0046 (UTC) FILETIME=[9676A660:01C1F051]
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-sipt-02.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

--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		: SIP for Telephones (SIP-T): Context and Architectures
	Author(s)	: A. Vemuri, J. Peterson
	Filename	: draft-ietf-sipping-sipt-02.txt
	Pages		: 30
	Date		: 29-Apr-02
	
SIP-T (earlier referred to as 'SIP-BCP-T') is a mechanism that uses
SIP to facilitate the interconnection of the PSTN with SIP networks.
This document explains the context and the architectures in which
SIP-T may be used.

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

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

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-sipping-sipt-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-sipt-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:	<20020429151423.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--


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



From daemon@optimus.ietf.org  Tue Apr 30 14:29:56 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02951
	for <sipping-archive@odin.ietf.org>; Tue, 30 Apr 2002 14:29:56 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA15883
	for sipping-archive@odin.ietf.org; Tue, 30 Apr 2002 14:29:59 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA15068;
	Tue, 30 Apr 2002 14:16:23 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA15024
	for <sipping@optimus.ietf.org>; Tue, 30 Apr 2002 14:16:18 -0400 (EDT)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02338
	for <sipping@ietf.org>; Tue, 30 Apr 2002 14:16:15 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g3UIFipY006833;
	Tue, 30 Apr 2002 11:15:44 -0700 (PDT)
Received: from localhost (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint Messaging Server MOS 3.1.0.54-GA)
	with ESMTP id AAC38021;
	Tue, 30 Apr 2002 11:15:45 -0700 (PDT)
Date: Tue, 30 Apr 2002 11:12:35 -0700 (Pacific Daylight Time)
From: Rohan Mahy <rohan@cisco.com>
To: sipping@ietf.org
cc: john.loughney@nokia.com
Message-ID: <Pine.WNT.4.44.0204301106440.-632041@chorizo.rapidconvergence.com>
X-X-Sender: rmahy@imop.cisco.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Sipping] SIP-AAA Requirements (fwd)
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Hi,

John Loughney has just submitted a first draft rewrite of the SIP AAA
requirements.  Until it appears in the archive, you can download it from:

http://www-nrc.nokia.com/sua/draft-loughney-sip-aaa-req-00.txt

Comments are solicited on the SIPPING list only.

John will also be leading discussion on this topic at the interim meeting
next week.

thanks,
-rohan



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



From daemon@optimus.ietf.org  Tue Apr 30 15:00:39 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04512
	for <sipping-archive@odin.ietf.org>; Tue, 30 Apr 2002 15:00:39 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA17936
	for sipping-archive@odin.ietf.org; Tue, 30 Apr 2002 15:00:42 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA17062;
	Tue, 30 Apr 2002 14:41:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA15076
	for <sipping@optimus.ietf.org>; Tue, 30 Apr 2002 14:16:27 -0400 (EDT)
Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02343
	for <sipping@ietf.org>; Tue, 30 Apr 2002 14:16:23 -0400 (EDT)
Received: from dynamo.cs.columbia.edu (dynamo.cs.columbia.edu [128.59.16.4])
	by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id OAA28371
	for <sipping@ietf.org>; Tue, 30 Apr 2002 14:16:25 -0400 (EDT)
Received: from dynamo.cs.columbia.edu (localhost [127.0.0.1])
	by dynamo.cs.columbia.edu (8.12.1/8.12.1) with ESMTP id g3UIGPMI023018
	for <sipping@ietf.org>; Tue, 30 Apr 2002 14:16:25 -0400 (EDT)
Received: (from petkos@localhost)
	by dynamo.cs.columbia.edu (8.12.1/8.12.1/Submit) id g3UIGPLQ023017
	for sipping@ietf.org; Tue, 30 Apr 2002 14:16:25 -0400 (EDT)
From: "Petri K. Koskelainen" <petkos@cs.columbia.edu>
Message-Id: <200204301816.g3UIGPLQ023017@dynamo.cs.columbia.edu>
To: sipping@ietf.org
Date: Tue, 30 Apr 2002 14:16:24 -0400 (EDT)
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Conferencing and User Management requirements (new draft)
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit


Here is another conferencing requirements document:
"Additional Requirements to Conferencing"
Until it appears in the archives, you can pick up a copy at:

http://www.cs.columbia.edu/~petkos/draft-koskelainen-sipping-conf-requirements-00.txt

It proposes additional user-management related requirements
such as ACL management, user privilege levels, group management,
and real-time authorization. It should be in line
with draft-levin-sipping-conferencing-requirements 
(terminology not yet fully aligned), but currently it 
is unclear whether these user management
issues are out of scope (at least for now).

Anyway, the purpose of the draft is to raise the issue
about user management in a conferencing context.


--
Petri


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



From daemon@optimus.ietf.org  Tue Apr 30 15:43:54 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06251
	for <sipping-archive@odin.ietf.org>; Tue, 30 Apr 2002 15:43:54 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA20570
	for sipping-archive@odin.ietf.org; Tue, 30 Apr 2002 15:43:57 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA19570;
	Tue, 30 Apr 2002 15:28:59 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA19534
	for <sipping@optimus.ietf.org>; Tue, 30 Apr 2002 15:28:56 -0400 (EDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05821;
	Tue, 30 Apr 2002 15:28:51 -0400 (EDT)
Received: from imop.cisco.com (IDENT:mirapoint@imop.cisco.com [171.69.11.44])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g3UJSOTZ028169;
	Tue, 30 Apr 2002 12:28:24 -0700 (PDT)
Received: from localhost (ssh-sjc-1.cisco.com [171.68.225.134])
	by imop.cisco.com (Mirapoint Messaging Server MOS 3.1.0.54-GA)
	with ESMTP id AAC38913;
	Tue, 30 Apr 2002 12:28:23 -0700 (PDT)
Date: Tue, 30 Apr 2002 12:25:12 -0700 (Pacific Daylight Time)
From: Rohan Mahy <rohan@cisco.com>
To: sip@ietf.org, <sipping@ietf.org>
cc: rohan@cisco.com
Message-ID: <Pine.WNT.4.44.0204301214330.-632041@chorizo.rapidconvergence.com>
X-X-Sender: rmahy@imop.cisco.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Sipping] Updated agenda for SIP/SIPPING Interim Meeting
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org

Hi,

Below is updated agenda information for the interim:  (Note that I
rearranged several of the slots within each day.)

SIP/SIPPING Interim Meeting
May 6-7, 2002
Room S225  (2nd Floor of South Hall)
Las Vegas Convention Center
3150 Paradise Road at Convention Center Drive
Las Vegas, Nevada, USA

The meeting space and network connectivity is being sponsored by
pulver.com's SIP Summit (pulver is part of Key3Media who also runs
Interop).  If you get lost, just ask where SIP summit is.
You do not need to register, but if you have not already done so, please
let me know if you are coming so I can get a reasonable estimate of
attendance.  If you want a shirt, please bring some cash.

Also please note that unfortunately the wireless network won't be up until
Monday afternoon.

thanks,
-rohan

Rohan Mahy
SIPPING co-chair

------------

Monday, May 6

08:30  Welcome, Logistics, Agenda Bashing -- Rohan Mahy

09:00  Multiparty Apps Framework and Conferencing Requirements --
Dan Petrie, Orit Levin
http://www.ietf.org/internet-drafts/draft-ietf-sipping-cc-framework-00.txt
http://www.softarmor.com/sipping/drafts/draft-levin-sipping-conferencing-requirements-00.txt

10:30  REFER / Replaces / cc-transfer / service examples -- Robert Sparks,
Rohan Mahy, Alan Johnston
http://www.ietf.org/internet-drafts/draft-ietf-sip-refer-02.txt
http://www.ietf.org/internet-drafts/draft-sparks-sip-refer-split-00.txt
http://www.ietf.org/internet-drafts/draft-sparks-sip-referredby-split-00.txt
http://www.ietf.org/internet-drafts/draft-sparks-sip-sec-options-00.txt
http://www.ietf.org/internet-drafts/draft-sparks-sip-mimetypes-03.txt
http://www.ietf.org/internet-drafts/draft-ietf-sip-replaces-01.txt
http://www.softarmor.com/sipwg/drafts/draft-ietf-sip-cc-transfer-05.txt
http://www.softarmor.com/sipping/drafts/draft-ietf-sipping-service-examples-01.txt

13:00  Lunch

14:00  The call-info and conference-info packages -- Jonathan Rosenberg
http://www.ietf.org/internet-drafts/draft-rosenberg-sip-call-package-01.txt

15:30  Content Indirection
http://www.ietf.org/internet-drafts/draft-olson-sipping-content-indirect-00.txt

16:30  Binding Published data to SIP -- Ben Campbell
very long mailing list thread beginning with:
http://www1.ietf.org/mail-archive/working-groups/sipping/current/msg01544.html

17:15  Key Events/ Stimulus Markup -- Jonathan Rosenberg
http://www.ietf.org/internet-drafts/draft-culpepper-sipping-app-interact-reqs-00.txt
http://www.ietf.org/internet-drafts/draft-rosenberg-sipping-markup-00.txt

18:00  Wrap

Tuesday, May 7

08:30  AAA requirements (Requirements) -- John Loughney and Gonzalo
Camarillo
http://www.ietf.org/internet-drafts/draft-calhoun-sip-aaa-reqs-04.txt
http://www.softarmor.com/sipping/drafts/draft-loughney-sip-aaa-req-00.txt

10:30  URI as service indicator -- Ben Campbell
RFC 3087

11:15  Request History (Requirements) -- Mary Barnes and Mark Watson
http://www.ietf.org/internet-drafts/draft-watson-sipping-request-history-01.txt

12:00  Lunch

13:00  Privacy and Network Asserted Identity (Direction Forward) -- Cullen
Jennings
http://www.softarmor.com/sipping/drafts/draft-watson-sipping-nai-reqs-00.txt
http://www.ietf.org/internet-drafts/draft-ietf-sip-privacy-04.txt
http://www.ietf.org/internet-drafts/draft-peterson-sip-longterm-privacy-00.txt
http://www.ietf.org/internet-drafts/draft-peterson-sip-identity-00.txt

16:30  Future Security Needs (Discussion)
http://www.ietf.org/internet-drafts/draft-ietf-sip-sec-agree-00.txt
http://www.ietf.org/internet-drafts/draft-undery-sip-auth-00.txt
http://www.softarmor.com/sipwg/drafts/draft-thomas-sip-sec-req-00.txt

18:00 Wrap



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



From daemon@optimus.ietf.org  Tue Apr 30 17:16:29 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09201
	for <sipping-archive@odin.ietf.org>; Tue, 30 Apr 2002 17:16:29 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA26670
	for sipping-archive@odin.ietf.org; Tue, 30 Apr 2002 17:16:33 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA26182;
	Tue, 30 Apr 2002 17:02:32 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA26151
	for <sipping@optimus.ietf.org>; Tue, 30 Apr 2002 17:02:29 -0400 (EDT)
Received: from imo-r02.mx.aol.com (imo-r02.mx.aol.com [152.163.225.98])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08872
	for <sipping@ietf.org>; Tue, 30 Apr 2002 17:02:25 -0400 (EDT)
From: Mpierce1@aol.com
Received: from Mpierce1@aol.com
	by imo-r02.mx.aol.com (mail_out_v32.5.) id c.141.dc749e4 (4561);
	Tue, 30 Apr 2002 17:01:44 -0400 (EDT)
Message-ID: <141.dc749e4.2a006037@aol.com>
Date: Tue, 30 Apr 2002 17:01:43 EDT
To: rohan@cisco.com
CC: sipping@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_141.dc749e4.2a006037_boundary"
X-Mailer: AOL 6.0 for Windows US sub 10524
Subject: [Sipping] Re: comments on cc-framework
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org


--part1_141.dc749e4.2a006037_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 4/29/02 12:36:35 PM Eastern Daylight Time, rohan@cisco.com 
writes:


> 4.7 This statement that "only the invoker[s] of features in SIP know
> exactly which feature they are invoking" sounds good in theory, but the
> reality for telephony services is that often both parties (devices) need
> to explicitly know what service is being performed, not just what
> signaling primitives are being used. It is clear, for example, that the
> processing of an INVITE or a REFER depends on the reason it was sent,
> whether it is a new call or a transfer or a barge in, etc.
> 
> Rohan> I disagree.  I have run through dozens of features which use these
> Rohan> features and I have never had this problem.  I suppose I can't
> Rohan> expect you and others to just take my word on faith so I will try
> Rohan> to come up with some more convincing examples.  Please feel free
> Rohan> to come up with a counter-example.
> 
> The example of Alice calling Bob who transfers to Carol, while Alice has
> her robotic assistant Albert "conferenced" illustrates this. First, the
> independence of these two separate "features" would not be compromised if
> the message from Bob to Alice explicitly said "transfer" rather than the
> generic "REFER".
> 
> Rohan> I'm not convinced, but assuming you are correct, what benefit would
> Rohan>

It has the benefit of being explicit, allowing processing at Alice to do the 
right thing based on what Bob wants. For example, if Alice has hung up just 
before she receives the REFER (request for transfer) it needs to be processed 
differently. I have not been able to put my finger on a specific case yet, 
since the target seems to keep moving somewhat (the interpretation of REFER 
in different cases). But I certainly get the impression that the desired 
interaction between different services will require that the REFER be 
processed differently depending not only on the exact state the receiver is 
in when she gets it, but also on exactly what the sender intended when he 
sent it. Guess it comes from so much such discussion during the development 
of ISDN standards. Yes, I know what the usual response to that is: "We don't 
want to repeat the mistakes of telephony or base this on their model", but 
the service requirement hasn't changed just because the protocol has changed.

Meanwhile, I'm trying to follow all the twists and turns in the rules for 
processing REFERS and INVITES, etc and to identify specific cases that won't 
work.


> 
> Secondly, one should assume that the interaction between
> the "robotic" feature at Alice with transfer (caused by receipt of the
> REFER) might have to be different than the interaction between this
> "robotic feature" and other features caused by receipt of REFER.
> 
> Rohan> Why?
> 
> When this
> happens, attempts will have to be made at the receiving end (Alice) to
> deduce what was intended in order to figure out what the best course of
> action is to provide a good service.
> 
> Rohan> I disagree.  The basis for the model is that the sender asks the
> Rohan> receiver to invoke a well-defined primitive.  The receiver can use
> Rohan> very simple rules to figure out whether to authorize whole
> Rohan> categories of requests or not.  The sender is free to use these
> Rohan> primitives for whatever service they can invoke with the primitives
> Rohan>

The problem is that, regardless of your protocol model, what the sender 
really wants to do is to invoke a well known service, not a primitive. A 
"primitive" is just one way to attempt to do it. The discussion of the last 
few months should have convinced others besides myself that there are no 
"very simple rules" for how to invoke "a well known primitive". It seems that 
everytime someone has asked a question regarding interaction of one primitive 
with another or with a timeout, that there was a further refinement on the 
"simple rules". Am I wrong here?

Don't get me wrong. There are a lot of things that can be done sending 
"primitives" between end points, just as a lot was done in the PSTN (even 
with ISDN) just by passing basic SETUP and RELEASE messages (or off-hook and 
on-hook) back and forth. It allowed many services that were totally 
controlled by one end (network provider switch). But there are a lot more 
complicated things that we want to do and I haven't seen any movement towards 
establishing a framework for that to happen. Rather, there seems to be a 
complete opposition to it. Is that maybe just considered as being outside of 
SIP, that is, a higher layer protocol portion? That would really raise 
feature interaction concerns!

> 
> thanks,
> -rohan
> 

Mike


--part1_141.dc749e4.2a006037_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 4/29/02 12:36:35 PM Eastern Daylight Time, rohan@cisco.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">4.7 This statement that "only the invoker[s] of features in SIP know
<BR>exactly which feature they are invoking" sounds good in theory, but the
<BR>reality for telephony services is that often both parties (devices) need
<BR>to explicitly know what service is being performed, not just what
<BR>signaling primitives are being used. It is clear, for example, that the
<BR>processing of an INVITE or a REFER depends on the reason it was sent,
<BR>whether it is a new call or a transfer or a barge in, etc.
<BR>
<BR>Rohan&gt; I disagree. &nbsp;I have run through dozens of features which use these
<BR>Rohan&gt; features and I have never had this problem. &nbsp;I suppose I can't
<BR>Rohan&gt; expect you and others to just take my word on faith so I will try
<BR>Rohan&gt; to come up with some more convincing examples. &nbsp;Please feel free
<BR>Rohan&gt; to come up with a counter-example.
<BR>
<BR>The example of Alice calling Bob who transfers to Carol, while Alice has
<BR>her robotic assistant Albert "conferenced" illustrates this. First, the
<BR>independence of these two separate "features" would not be compromised if
<BR>the message from Bob to Alice explicitly said "transfer" rather than the
<BR>generic "REFER".
<BR>
<BR>Rohan&gt; I'm not convinced, but assuming you are correct, what benefit would
<BR>Rohan&gt; this have?</BLOCKQUOTE>
<BR>
<BR>It has the benefit of being explicit, allowing processing at Alice to do the right thing based on what Bob wants. For example, if Alice has hung up just before she receives the REFER (request for transfer) it needs to be processed differently. I have not been able to put my finger on a specific case yet, since the target seems to keep moving somewhat (the interpretation of REFER in different cases). But I certainly get the impression that the desired interaction between different services will require that the REFER be processed differently depending not only on the exact state the receiver is in when she gets it, but also on exactly what the sender intended when he sent it. Guess it comes from so much such discussion during the development of ISDN standards. Yes, I know what the usual response to that is: "We don't want to repeat the mistakes of telephony or base this on their model", but the service requirement hasn't changed just because the protocol has changed.
<BR>
<BR>Meanwhile, I'm trying to follow all the twists and turns in the rules for processing REFERS and INVITES, etc and to identify specific cases that won't work.
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
<BR>Secondly, one should assume that the interaction between
<BR>the "robotic" feature at Alice with transfer (caused by receipt of the
<BR>REFER) might have to be different than the interaction between this
<BR>"robotic feature" and other features caused by receipt of REFER.
<BR>
<BR>Rohan&gt; Why?
<BR>
<BR>When this
<BR>happens, attempts will have to be made at the receiving end (Alice) to
<BR>deduce what was intended in order to figure out what the best course of
<BR>action is to provide a good service.
<BR>
<BR>Rohan&gt; I disagree. &nbsp;The basis for the model is that the sender asks the
<BR>Rohan&gt; receiver to invoke a well-defined primitive. &nbsp;The receiver can use
<BR>Rohan&gt; very simple rules to figure out whether to authorize whole
<BR>Rohan&gt; categories of requests or not. &nbsp;The sender is free to use these
<BR>Rohan&gt; primitives for whatever service they can invoke with the primitives
<BR>Rohan&gt; at hand.</BLOCKQUOTE>
<BR>
<BR>The problem is that, regardless of your protocol model, what the sender really wants to do is to invoke a well known service, not a primitive. A "primitive" is just one way to attempt to do it. The discussion of the last few months should have convinced others besides myself that there are no "very simple rules" for how to invoke "a well known primitive". It seems that everytime someone has asked a question regarding interaction of one primitive with another or with a timeout, that there was a further refinement on the "simple rules". Am I wrong here?
<BR>
<BR>Don't get me wrong. There are a lot of things that can be done sending "primitives" between end points, just as a lot was done in the PSTN (even with ISDN) just by passing basic SETUP and RELEASE messages (or off-hook and on-hook) back and forth. It allowed many services that were totally controlled by one end (network provider switch). But there are a lot more complicated things that we want to do and I haven't seen any movement towards establishing a framework for that to happen. Rather, there seems to be a complete opposition to it. Is that maybe just considered as being outside of SIP, that is, a higher layer protocol portion? That would really raise feature interaction concerns!
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
<BR>thanks,
<BR>-rohan
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>Mike
<BR></FONT></HTML>

--part1_141.dc749e4.2a006037_boundary--

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



From daemon@optimus.ietf.org  Tue Apr 30 22:26:27 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA16271
	for <sipping-archive@odin.ietf.org>; Tue, 30 Apr 2002 22:26:25 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA11854
	for sipping-archive@odin.ietf.org; Tue, 30 Apr 2002 22:26:29 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA11211;
	Tue, 30 Apr 2002 22:04:11 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA11179
	for <sipping@optimus.ietf.org>; Tue, 30 Apr 2002 22:04:08 -0400 (EDT)
Received: from mail2.intervoice-brite.com (mail2.intervoice-brite.com [204.62.8.15])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15752
	for <sipping@ietf.org>; Tue, 30 Apr 2002 22:04:04 -0400 (EDT)
Received: from DALNTMS02.ivbi.com (dalntms02.ivbi.com [151.214.90.44])
	by mail2.intervoice-brite.com (Build 101 8.9.3/NT-8.9.3) with ESMTP id VAA03536
	for <sipping@ietf.org>; Tue, 30 Apr 2002 21:09:43 -0500
Received: from 172.16.16.64 (unverified) by DALNTMS02.ivbi.com
 (Content Technologies SMTPRS 4.2.10) with SMTP id <T5a9517734f97d65a2c398@DALNTMS02.ivbi.com> for <sipping@ietf.org>;
 Tue, 30 Apr 2002 20:59:58 -0500
Received: from bculpepperpc
	([151.214.91.137])
	by 172.16.16.64; Tue, 30 Apr 2002 21:03:27 -0500
From: "Bert Culpepper" <bert.culpepper@intervoice-brite.com>
To: <sipping@ietf.org>
Date: Tue, 30 Apr 2002 22:02:53 -0400
Message-ID: <000601c1f0b4$4ef1e620$6500a8c0@bculpepperpc>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Importance: Normal
In-Reply-To: <E79883AEA37FD411A58C00508BAC5F4B01D38CC3@exchange1.nuera.com>
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Revised App Interact Reqs I-D
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

Hi all,

Seeing that "Key Events/Stimulus Markup" has been added to the Interim
Meeting's agenda, Robert and I have modified the requirements I-D.  The
document has been significantly updated since the last revision (based on
list comment so far).  Hopefully this version will be more useful during the
meeting than the previous version.

I've submitted the I-D, until it appears in the archives a copy can be
gotten from
http://home.cfl.rr.com/bculpepper/draft-culpepper-sipping-app-interact-reqs-
01.txt.

Comments, suggestions, etc. are very welcome.

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 daemon@optimus.ietf.org  Tue Apr 30 22:59:14 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18023
	for <sipping-archive@odin.ietf.org>; Tue, 30 Apr 2002 22:59:14 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA13505
	for sipping-archive@odin.ietf.org; Tue, 30 Apr 2002 22:59:18 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA12660;
	Tue, 30 Apr 2002 22:39:47 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA12628
	for <sipping@optimus.ietf.org>; Tue, 30 Apr 2002 22:39:44 -0400 (EDT)
Received: from dgesmtp01.wcom.com (dgesmtp01.wcom.com [199.249.16.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA17451
	for <sipping@ietf.org>; Tue, 30 Apr 2002 22:39:40 -0400 (EDT)
Received: from CONVERSION-DAEMON by firewall.wcom.com (PMDF V5.2-33 #42260)
 id <0GVE00101VDCO4@firewall.wcom.com> for sipping@ietf.org; Wed,
 1 May 2002 02:39:12 +0000 (GMT)
Received: from dgismtp01.wcomnet.com ([166.38.58.141])
 by firewall.wcom.com (PMDF V5.2-33 #42260)
 with ESMTP id <0GVE00MH3VDB14@firewall.wcom.com>; Wed,
 01 May 2002 02:39:12 +0000 (GMT)
Received: from dgismtp01.wcomnet.com by dgismtp01.wcomnet.com
 (PMDF V5.2-33 #42262) with SMTP id <0GVE00601VD9CM@dgismtp01.wcomnet.com>;
 Wed, 01 May 2002 02:39:11 +0000 (GMT)
Received: from hsinnreich2 ([153.39.76.99])
 by dgismtp01.wcomnet.com (PMDF V5.2-33 #42262)
 with ESMTP id <0GVE0047GVD2XY@dgismtp01.wcomnet.com>; Wed,
 01 May 2002 02:39:03 +0000 (GMT)
Date: Tue, 30 Apr 2002 21:39:04 -0500
From: Henry Sinnreich <Henry.Sinnreich@wcom.com>
Subject: RE: [Sipping] SIP-AAA Requirements (fwd)
In-reply-to: <Pine.WNT.4.44.0204301106440.-632041@chorizo.rapidconvergence.com>
To: "'Rohan Mahy'" <rohan@cisco.com>, sipping@ietf.org,
        mobile-ip@sunroof.eng.sun.com
Cc: john.loughney@nokia.com,
        Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>,
        Pat Calhoun <Pat.Calhoun@eng.sun.com>,
        Charles Perkins <Charles.Perkins@eng.sun.com>,
        "'C. de Laat'" <C.T.A.M.deLaat@phys.uu.nl>, jrv@merit.edu
Message-id: <000001c1f0b9$5cc7f9b0$634c2799@hsinnreich2>
Organization: WorldCom, Inc.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

As 3GPP, 3GPP2 and 802.11 wireless networks are poised to use both SIP
and Mobile IP, one cannot help notice there seems to be a lot
commonality between:

1-SIP AAA requirements
http://www-nrc.nokia.com/sua/draft-loughney-sip-aaa-req-00.txt

2-3GPP Requirements on SIP
http://ietf.org/internet-drafts/draft-garcia-sipping-3gpp-reqs-03.txt

3-and most of all, Mobile IP AAA Requirements, RFC 2977
ftp://ftp.isi.edu/in-notes/rfc2977.txt

The mobile IP WG http://ietf.org/html.charters/mobileip-charter.html has
actually covered a lot of groundwork, where it may make sense to avoid
duplication, such as for example for AAA Registration Keys
http://ietf.org/internet-drafts/draft-ietf-mobileip-aaa-key-09.txt

Here are some striking analogies:

Mobile IP    SIP
================
MN-----------UA
FA-----------Visited SIP Registrar
AAAL/H-------SIP AAA
AAAB---------Clearinghouse
See the AAAarch web page
http://iridal.phys.uu.nl/~aaaarch/doc10/home.html and also
http://ietf.org/internet-drafts/draft-johnston-sip-osp-token-02.txt

One more item that the Mobile IP WG has successfully solved is the
separation of specific AAA solutions such as RADIUS, DIAMETER or XML web
services from the mobile IP protocol itself. It is not for the SIPPING
WG to pick winners and losers in AAA solutions and promote one or
another, as has been discussed.

We should try to avoid coming up with several different/incompatible
infrastructures, multiple logons and general annoyance from duplication
of work. Or have the IESG step in to make order.

I believe the SIPPING Mobile IP and AAAarch IP folks should talk to each
other during the WG discussions or maybe possibly at a Bar BOF. I have
taken therefore the liberty to copy the Mobile IP and AAAarch lists.

>John will also be leading discussion on this topic at the interim
meeting next week.
The interested Mobile IP and AAAarch people cannot attend at such short
notice.

Thanks, Henry

Henry Sinnreich
WorldCom
400 International Parkway
Richardson, Texas 75081
USA

> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]
> On Behalf Of Rohan Mahy
> Sent: Tuesday, April 30, 2002 1:13 PM
> To: sipping@ietf.org
> Cc: john.loughney@nokia.com
> Subject: [Sipping] SIP-AAA Requirements (fwd)
>
>
> Hi,
>
> John Loughney has just submitted a first draft rewrite of the
> SIP AAA requirements.  Until it appears in the archive, you
> can download it from:
>
http://www-nrc.nokia.com/sua/draft-loughney-sip-aaa-req-00.txt

Comments are solicited on the SIPPING list only.

John will also be leading discussion on this topic at the interim
meeting next week.

thanks,
-rohan



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


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



From daemon@optimus.ietf.org  Tue Apr 30 23:07:40 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18134
	for <sipping-archive@odin.ietf.org>; Tue, 30 Apr 2002 23:07:40 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA14138
	for sipping-archive@odin.ietf.org; Tue, 30 Apr 2002 23:07:44 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA13024;
	Tue, 30 Apr 2002 22:50:17 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA12916
	for <sipping@optimus.ietf.org>; Tue, 30 Apr 2002 22:50:08 -0400 (EDT)
Received: from dgesmtp02.wcom.com (dgesmtp02.wcom.com [199.249.16.17])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA17831
	for <sipping@ietf.org>; Tue, 30 Apr 2002 22:50:03 -0400 (EDT)
Received: from CONVERSION-DAEMON by firewall.wcom.com (PMDF V5.2-33 #42261)
 id <0GVE00B01VUN51@firewall.wcom.com> for sipping@ietf.org; Wed,
 1 May 2002 02:49:36 +0000 (GMT)
Received: from dgismtp06.wcomnet.com ([166.38.58.89])
 by firewall.wcom.com (PMDF V5.2-33 #42261)
 with ESMTP id <0GVE00A4QVUM7I@firewall.wcom.com>; Wed,
 01 May 2002 02:49:35 +0000 (GMT)
Received: from dgismtp06.wcomnet.com by dgismtp06.wcomnet.com
 (iPlanet Messaging Server 5.1 (built May  7 2001))
 with SMTP id <0GVE00801VUICL@dgismtp06.wcomnet.com>; Wed,
 01 May 2002 02:49:30 +0000 (GMT)
Received: from hsinnreich2 ([153.39.68.163])
 by dgismtp06.wcomnet.com (iPlanet Messaging Server 5.1 (built May  7 2001))
 with ESMTP id <0GVE006AXVUHAB@dgismtp06.wcomnet.com>; Wed,
 01 May 2002 02:49:30 +0000 (GMT)
Date: Tue, 30 Apr 2002 21:49:35 -0500
From: Henry Sinnreich <Henry.Sinnreich@wcom.com>
Subject: RE: [Sipping] SIP-AAA Requirements (fwd)
In-reply-to: <Pine.WNT.4.44.0204301106440.-632041@chorizo.rapidconvergence.com>
To: "'Rohan Mahy'" <rohan@cisco.com>, sipping@ietf.org,
        mobile-ip@sunroof.eng.sun.com
Cc: john.loughney@nokia.com,
        Gonzalo Camarillo <Gonzalo.Camarillo@lmf.ericsson.se>,
        Pat Calhoun <Pat.Calhoun@eng.sun.com>, charliep@iprg.nokia.com,
        "'C. de Laat'" <C.T.A.M.deLaat@phys.uu.nl>, jrv@merit.edu
Message-id: <000501c1f0ba$d4cb6f90$a3442799@hsinnreich2>
Organization: WorldCom, Inc.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Content-Transfer-Encoding: 7bit

As 3GPP, 3GPP2 and 802.11 wireless networks are poised to use both SIP
and Mobile IP, one cannot help notice there seems to be a lot
commonality between:

1-SIP AAA requirements
http://www-nrc.nokia.com/sua/draft-loughney-sip-aaa-req-00.txt

2-3GPP Requirements on SIP
http://ietf.org/internet-drafts/draft-garcia-sipping-3gpp-reqs-03.txt

3-and most of all, Mobile IP AAA Requirements, RFC 2977
ftp://ftp.isi.edu/in-notes/rfc2977.txt

The mobile IP WG http://ietf.org/html.charters/mobileip-charter.html has
actually covered a lot of groundwork, where it may make sense to avoid
duplication, such as for example for AAA Registration Keys
http://ietf.org/internet-drafts/draft-ietf-mobileip-aaa-key-09.txt

Here are some striking analogies:

Mobile IP    SIP
================
MN-----------UA
FA-----------Visited SIP Registrar
AAAL/H-------SIP AAA
AAAB---------Clearinghouse
See the AAAarch web page
http://iridal.phys.uu.nl/~aaaarch/doc10/home.html and also
http://ietf.org/internet-drafts/draft-johnston-sip-osp-token-02.txt

One more item that the Mobile IP WG has successfully solved is the
separation of specific AAA solutions such as RADIUS, DIAMETER or XML web
services from the mobile IP protocol itself. It is not for the SIPPING
WG to pick winners and losers in AAA solutions and promote one or
another, as has been discussed.

We should try to avoid coming up with several different/incompatible
infrastructures, multiple logons and general annoyance from duplication
of work. Or have the IESG step in to make order.

I believe the SIPPING Mobile IP and AAAarch IP folks should talk to each
other during the WG discussions or maybe possibly at a Bar BOF. I have
taken therefore the liberty to copy the Mobile IP and AAAarch lists.

>John will also be leading discussion on this topic at the interim
meeting next week.
The interested Mobile IP and AAAarch people cannot attend at such short
notice.

Thanks, Henry

Henry Sinnreich
WorldCom
400 International Parkway
Richardson, Texas 75081
USA

> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]
> On Behalf Of Rohan Mahy
> Sent: Tuesday, April 30, 2002 1:13 PM
> To: sipping@ietf.org
> Cc: john.loughney@nokia.com
> Subject: [Sipping] SIP-AAA Requirements (fwd)
>
>
> Hi,
>
> John Loughney has just submitted a first draft rewrite of the
> SIP AAA requirements.  Until it appears in the archive, you
> can download it from:
>
http://www-nrc.nokia.com/sua/draft-loughney-sip-aaa-req-00.txt

Comments are solicited on the SIPPING list only.

John will also be leading discussion on this topic at the interim
meeting next week.

thanks,
-rohan



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


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



