From exim@www1.ietf.org  Mon Dec  1 08:17:26 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09467
	for <sipping-archive@odin.ietf.org>; Mon, 1 Dec 2003 08:17:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQnvL-0005Mz-9x
	for sipping-archive@odin.ietf.org; Mon, 01 Dec 2003 08:17:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB1DHBiQ020637
	for sipping-archive@odin.ietf.org; Mon, 1 Dec 2003 08:17:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQnvL-0005Mm-6e
	for sipping-web-archive@optimus.ietf.org; Mon, 01 Dec 2003 08:17:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09398
	for <sipping-web-archive@ietf.org>; Mon, 1 Dec 2003 08:16:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQnvK-0001Qn-00
	for sipping-web-archive@ietf.org; Mon, 01 Dec 2003 08:17:10 -0500
Received: from manatick.foretec.com ([4.17.168.5] helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQnmN-0001Bx-00
	for sipping-web-archive@ietf.org; Mon, 01 Dec 2003 08:07:55 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org)
	by manatick with esmtp (Exim 4.24)
	id 1AQnc3-0005am-G8
	for sipping-web-archive@ietf.org; Mon, 01 Dec 2003 07:57:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQnbq-00040T-Ij; Mon, 01 Dec 2003 07:57:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOncu-0004o9-PJ
	for sipping@optimus.ietf.org; Tue, 25 Nov 2003 19:33:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19424;
	Tue, 25 Nov 2003 19:33:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOncs-0003VG-00; Tue, 25 Nov 2003 19:33:50 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOncr-0003US-00; Tue, 25 Nov 2003 19:33:50 -0500
Received: from cisco.com (171.68.223.137)
  by sj-iport-5.cisco.com with ESMTP; 25 Nov 2003 16:33:02 -0800
Received: from mbaugher-w2k07.cisco.com (sjc-vpn1-41.cisco.com [10.21.96.41])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id hAQ0XDrY019735;
	Tue, 25 Nov 2003 16:33:14 -0800 (PST)
Message-Id: <6.0.0.22.2.20031125160613.03fd89d8@mira-sjc5-6.cisco.com>
X-Sender: mbaugher@mira-sjc5-6.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Tue, 25 Nov 2003 16:33:12 -0800
To: ono.kumiko@lab.ntt.co.jp, mary.barnes@nortelnetworks.com,
        tachimoto.shinya@lab.ntt.co.jp
From: Mark Baugher <mbaugher@cisco.com>
Cc: sipping@ietf.org, mmusic@ietf.org, cyrus@ntt-at.com, fandreas@cisco.com,
        dwing@cisco.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Sipping] e2m, m2m security drafts
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


hi
   I have read the three drafts dealing with end-to-middle and 
middle-to-middle security, both requirements and mechanisms.

http://www.ietf.org/internet-drafts/draft-ietf-sipping-e2m-sec-reqs-00.txt
http://www.ietf.org/internet-drafts/draft-barnes-sipping-sec-inserted-info-01.txt
http://www.ietf.org/internet-drafts/draft-ono-sipping-end2middle-security-00.txt

As you may know, we developed SDP security descriptions to describe a key 
and security parameters for a media session.  We need to have end-to-end 
authentication and encryption of this information and secure multiparts 
looks like a promising approach to our security-description needs.  So, 
I'll have a lot of comments and questions on these drafts.

In this note, I'll limit myself to one question and one comment.

1. Section 5.1 of 
http://www.ietf.org/internet-drafts/draft-ono-sipping-end2middle-security-00.txt 
shows an example of an encrypted SDP in an INVITE but the key to this 
encrypted SDP is selectively shared with some proxies so they can view the 
encrypted data.  There is undoubtedly some information in the SDP that a 
proxy needs to view and some that it does not need to view, such as the 
end-to-end keying material.  Can we accommodate this requirement in the 
current proposals?  That is, could we keep the keying material encrypted 
end-to-end while allowing a proxy to view other parts of the SDP message?

2. Have you considered writing a core specification like RFC 1847 and allow 
for one or more profiles such as S/MIME (today) and PGP MIME (in the 
future)?  I understand that S/MIME is the designated SIP solution, but it 
might be wise to allow for future extensions.

Thanks for doing this work.

Mark


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



From exim@www1.ietf.org  Mon Dec  1 08:17:30 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09482
	for <sipping-archive@odin.ietf.org>; Mon, 1 Dec 2003 08:17:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQnvP-0005Nq-Ob
	for sipping-archive@odin.ietf.org; Mon, 01 Dec 2003 08:17:16 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB1DHFBg020688
	for sipping-archive@odin.ietf.org; Mon, 1 Dec 2003 08:17:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQnvP-0005Nb-LM
	for sipping-web-archive@optimus.ietf.org; Mon, 01 Dec 2003 08:17:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09421
	for <sipping-web-archive@ietf.org>; Mon, 1 Dec 2003 08:16:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQnvO-0001TB-00
	for sipping-web-archive@ietf.org; Mon, 01 Dec 2003 08:17:14 -0500
Received: from manatick.foretec.com ([4.17.168.5] helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQnmM-0001Bx-03
	for sipping-web-archive@ietf.org; Mon, 01 Dec 2003 08:07:55 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org)
	by manatick with esmtp (Exim 4.24)
	id 1AQnc4-0005an-Bz
	for sipping-web-archive@ietf.org; Mon, 01 Dec 2003 07:57:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQnbp-00040I-Jf; Mon, 01 Dec 2003 07:57:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOP9w-0007Fk-6n
	for sipping@optimus.ietf.org; Mon, 24 Nov 2003 17:26:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06889;
	Mon, 24 Nov 2003 17:26:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOP9t-0007DC-00; Mon, 24 Nov 2003 17:26:17 -0500
Received: from relay1.csc.com ([20.137.252.211] helo=amer-bmta04.csc.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOP9p-0007D8-00; Mon, 24 Nov 2003 17:26:13 -0500
Received: from csc.com (va-fch32.csc.com [20.6.39.233])
	by amer-bmta04.csc.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id hAOMQPxP005030;
	Mon, 24 Nov 2003 17:26:25 -0500 (EST)
Subject: Re: [Sipping] Resource-Priority header decisions at IETF 58?
To: "Eagan, Christopher" <christopher.eagan@lmco.com>
Cc: jmpolk@cisco.com, schulzrinne@cs.columbia.edu, sipping@ietf.org,
        sipping-admin@ietf.org
X-Mailer: Lotus Notes Release 5.0.11   July 24, 2002
Message-ID: <OF1E669894.02F81B56-ON85256DE8.007B3204-85256DE8.007B709E@com>
From: "Janet P Gunn" <jgunn6@csc.com>
Date: Mon, 24 Nov 2003 17:28:17 -0500
X-MIMETrack: Serialize by Router on VA-FCH32/SRV/CSC(Release 5.0.11  |July 24, 2002) at
 11/24/2003 05:27:04 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


The Resource Priority Header is now in sip, not sipping.

In the sip meeting they said something about "moving forward with it" in
Jan '04 or Feb'04 (I forget which now).

If you can find the sip minutes, it should be there.


----------------------------------------------------------------------------------------

This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
----------------------------------------------------------------------------------------




                                                                                                                                 
                      "Eagan,                                                                                                    
                      Christopher"             To:      sipping@ietf.org                                                         
                      <christopher.eag         cc:      jmpolk@cisco.com, schulzrinne@cs.columbia.edu                            
                      an                       Subject: [Sipping] Resource-Priority header decisions at IETF 58?                 
                      @lmco.com>                                                                                                 
                      Sent by:                                                                                                   
                      sipping-admin                                                                                              
                                                                                                                                 
                                                                                                                                 
                      11/21/2003 04:48                                                                                           
                      PM                                                                                                         
                                                                                                                                 
                                                                                                                                 




Was there any movement or decisions on the Resource-Priority header at IETF
58 that someone can summarize?  (missed that session unfortunately)

Thanks!

Chris

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






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



From exim@www1.ietf.org  Mon Dec  1 10:11:25 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13689
	for <sipping-archive@odin.ietf.org>; Mon, 1 Dec 2003 10:11:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQphd-0004Xz-Jc
	for sipping-archive@odin.ietf.org; Mon, 01 Dec 2003 10:11:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB1FB9ig017473
	for sipping-archive@odin.ietf.org; Mon, 1 Dec 2003 10:11:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQphd-0004Xk-FZ
	for sipping-web-archive@optimus.ietf.org; Mon, 01 Dec 2003 10:11:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13592
	for <sipping-web-archive@ietf.org>; Mon, 1 Dec 2003 10:10:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQphb-00035Y-00
	for sipping-web-archive@ietf.org; Mon, 01 Dec 2003 10:11:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQpha-00035V-00
	for sipping-web-archive@ietf.org; Mon, 01 Dec 2003 10:11:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQphV-0004VY-Fu; Mon, 01 Dec 2003 10:11:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQpgp-0004TS-Aj
	for sipping@optimus.ietf.org; Mon, 01 Dec 2003 10:10:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13479
	for <sipping@ietf.org>; Mon, 1 Dec 2003 10:10:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQpgn-000356-00
	for sipping@ietf.org; Mon, 01 Dec 2003 10:10:17 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQpgm-00034l-00
	for sipping@ietf.org; Mon, 01 Dec 2003 10:10:16 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA26385;
	Mon, 1 Dec 2003 10:09:35 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA14638;
	Mon, 1 Dec 2003 10:09:29 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <W9W755VW>; Mon, 1 Dec 2003 10:09:28 -0500
Message-ID: <313680C9A886D511A06000204840E1CF070B6135@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Paul Kyzivat'" <pkyzivat@cisco.com>
Cc: sipping@ietf.org
Subject: RE: [Sipping] User=Phone/DialString and Pause and Wait
Date: Mon, 1 Dec 2003 10:09:26 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

 
> > I think that covers all cases of dumb phones.  It might also covers
> > a case you suggest, which would be an incomplete digitmap that
> > needed an escape clause.  Digitmap capable phones need more work,
> > and I agree we need to standardize that, and we both are aware
> > of the efforts to do that.
> 
> It would also be very sensible for the translation that is 
> used by dumb 
> phones is of exactly the same form as one entry in a dial map for a 
> smart phone. Rather than using the transformation you mention 
> above on 
> each dialstring, it would be straightforward to say that a single 
> template is either configured, or is created from 
> discoverable data. If 
> you can discover a context to use with dialstrings you can 
> just as well 
> discover a template.
If you are proposing that a dumb phone is just a smart phone with a
default translation rule, then I don't see a problem as long as the
default rule is as I suggest (sip: in the front, user=dialstring and
phone-context in the back.

> 
> > None of this is pushback to the argument that user=phone is only
> > appropriate when the userpart is the address of a terminal (ie
> > phone number).  I do want a simple rule - if you don't understand 
> > what the string of digits is, it's a dialstring and send 
> user=dialstring.  
> > If you can, translate the dialstring to a phone number and send 
> > user=phone (or tel uri).  There is no third case that I know of.
> 
> Suppose I had a dial plan that said:
> 
> 	translate all numbers that start with "8"
> 	to "tel:" + dialstring + ";phone-context=dial.cisco.com"
> 
> I think that should be ok with you. Now instead, suppose I 
> made the rule:
> 
> 	translate all numbers that start with "0"..."9","*","#"
> 	to "tel:" + dialstring + ";phone-context=dial.cisco.com"
> 
> 	translate all other numbers to
> 	"sip:" + dialstring + ";phone-context=dial.cisco.com"
> 	       + "@cisco.com;user=dialstring"
> 
> Is that still ok with you? Why not?
The problem that I have with this is that a dialstring starting
with pound or star is not (at least usually) a phone number.
They are usually service invocations.  You rarely route such
a number to a terminal without a fair amount of processing.
The text states that they are possible characters in a local
phone number, so the syntax is permitted by the draft, but
in most cases you are using the tel uri to carry a dialstring,
which the draft says is out of scope.

So, I claim that you have extended the tel uri.  It's okay to have
a phone that does this, as well as your proxy implements the same
extension.  I don't know of any document that would describe such
an extension, and I don't want to support creating one.

Nevertheless, if that's what the administrator wants to happen,
and both ends can handle it, I wouldn't say that it's wrong.

> 
> Its my system, my dial plan, my definition of the "dial.cisco.com" 
> phone-context, so I don't see what you have to complain 
> about. You say I 
> can only use user=phone (or tel:) when the address is that of a 
> terminal. But I get to decide what the addresses of terminals 
> are. I say 
> I am using my dialplan to translate dial strings into addresses of 
> terminals - it just happens that my terminal addresses look 
> remarkably 
> similar to dialstrings.
I would say that your proxy would be going above and beyond the
minimal definition of routing a sip uri that has user=phone, but
I wouldn't want to prohibit it.  What I would want to "prohibit"
is a requirement that any phone that didn't have a digitmap be able
to send such a string.

> 
> Of course the last rule isn't needed any more because it can never be 
> reached. So my complete dialplan is just:
> 
> 	translate all numbers that start with "0"..."9","*","#"
> 	to "tel:" + dialstring + ";phone-context=dial.cisco.com"
> 
> What am I doing wrong here?
Nothing, as long as your proxy can do this.  Not all proxies will.
Of course, not all proxies will process user=dialstring either.
The key issue for me is that dumb phones always process user
keypresses into user=dialstring+phone-context, and that is the one
way to get dialstring processing done.  If you happen to have a
proxy that can also process a dialstring that has user=phone, fine,
but the only phones that are going to do that are phones that have
digitmaps, and administrators who create a digitmap that does your
example for a proxy that implements things beyond the spec.

You could just as well have a digitmap that said:
	translate all numbers that start with "0".."9","*","#"
	to "sip:dialstring" + dialstring + "@cisco.com"
As long as your proxy can process a sip uri that looks like that,
then it's going to work.  Some proxies might work fine with that,
because they have regexp processing, and the regexp can handle
the example I gave.  No problem.  

I don't want to see your example, or mine for that matter, in any
standards document.

Brian
 

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



From exim@www1.ietf.org  Tue Dec  2 11:46:25 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26200
	for <sipping-archive@odin.ietf.org>; Tue, 2 Dec 2003 11:46:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARDf6-0000eZ-CA
	for sipping-archive@odin.ietf.org; Tue, 02 Dec 2003 11:46:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB2Gk8ar002507
	for sipping-archive@odin.ietf.org; Tue, 2 Dec 2003 11:46:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARDf6-0000eM-8l
	for sipping-web-archive@optimus.ietf.org; Tue, 02 Dec 2003 11:46:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26181
	for <sipping-web-archive@ietf.org>; Tue, 2 Dec 2003 11:45:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARDf5-0003wu-00
	for sipping-web-archive@ietf.org; Tue, 02 Dec 2003 11:46:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARDf4-0003wq-00
	for sipping-web-archive@ietf.org; Tue, 02 Dec 2003 11:46:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARDf0-0000bv-VM; Tue, 02 Dec 2003 11:46:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARDeQ-0000aH-1C
	for sipping@optimus.ietf.org; Tue, 02 Dec 2003 11:45:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26117
	for <sipping@ietf.org>; Tue, 2 Dec 2003 11:45:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARDeO-0003vr-00
	for sipping@ietf.org; Tue, 02 Dec 2003 11:45:24 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARDeO-0003vH-00
	for sipping@ietf.org; Tue, 02 Dec 2003 11:45:24 -0500
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id hB2Gipw5016787;
	Tue, 2 Dec 2003 08:44:51 -0800 (PST)
Received: from cisco.com ([161.44.79.239])
	by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AEI95710;
	Tue, 2 Dec 2003 11:44:50 -0500 (EST)
Message-ID: <3FCCC182.5000301@cisco.com>
Date: Tue, 02 Dec 2003 11:44:50 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Rosen, Brian" <Brian.Rosen@marconi.com>
CC: sipping@ietf.org
Subject: Re: [Sipping] User=Phone/DialString and Pause and Wait
References: <313680C9A886D511A06000204840E1CF070B6135@whq-msgusr-02.pit.comms.marconi.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Brian,

I don't have any major disagreements with what you say below, though I 
think I would still spin it or explain it somewhat differently. I think 
this is ultimately coming down to how you configure phones - especially 
dumb phones - and how dumb a dumb phone is.

I imagine we can safely say that there aren't yet any phones that 
generate uris containing user=dialstring, so we are only talking about 
phones that are yet to be built, or at least new software loads for 
existing phones. And practically speaking, for awhile now there will 
probably be little market for phones that *always* generate uris with 
user=dialstring, because they won't work with older systems. So we are 
probably talking about phones that can be configured with that part of 
the translation. So I think even the dumbest of phones that can do any 
of this will probably be smart enough to do more than you expect from a 
dumb phone.

It may be that the best thing would be to standardize the configuration 
of dialplans in a phone, with the possibility that the dialplan could be 
as simple as a single mapping for all dialstrings, with the proxy 
expected to do the rest.

	Paul

Rosen, Brian wrote:
>  
> 
>>>I think that covers all cases of dumb phones.  It might also covers
>>>a case you suggest, which would be an incomplete digitmap that
>>>needed an escape clause.  Digitmap capable phones need more work,
>>>and I agree we need to standardize that, and we both are aware
>>>of the efforts to do that.
>>
>>It would also be very sensible for the translation that is 
>>used by dumb 
>>phones is of exactly the same form as one entry in a dial map for a 
>>smart phone. Rather than using the transformation you mention 
>>above on 
>>each dialstring, it would be straightforward to say that a single 
>>template is either configured, or is created from 
>>discoverable data. If 
>>you can discover a context to use with dialstrings you can 
>>just as well 
>>discover a template.
> 
> If you are proposing that a dumb phone is just a smart phone with a
> default translation rule, then I don't see a problem as long as the
> default rule is as I suggest (sip: in the front, user=dialstring and
> phone-context in the back.
> 
> 
>>>None of this is pushback to the argument that user=phone is only
>>>appropriate when the userpart is the address of a terminal (ie
>>>phone number).  I do want a simple rule - if you don't understand 
>>>what the string of digits is, it's a dialstring and send 
>>
>>user=dialstring.  
>>
>>>If you can, translate the dialstring to a phone number and send 
>>>user=phone (or tel uri).  There is no third case that I know of.
>>
>>Suppose I had a dial plan that said:
>>
>>	translate all numbers that start with "8"
>>	to "tel:" + dialstring + ";phone-context=dial.cisco.com"
>>
>>I think that should be ok with you. Now instead, suppose I 
>>made the rule:
>>
>>	translate all numbers that start with "0"..."9","*","#"
>>	to "tel:" + dialstring + ";phone-context=dial.cisco.com"
>>
>>	translate all other numbers to
>>	"sip:" + dialstring + ";phone-context=dial.cisco.com"
>>	       + "@cisco.com;user=dialstring"
>>
>>Is that still ok with you? Why not?
> 
> The problem that I have with this is that a dialstring starting
> with pound or star is not (at least usually) a phone number.
> They are usually service invocations.  You rarely route such
> a number to a terminal without a fair amount of processing.
> The text states that they are possible characters in a local
> phone number, so the syntax is permitted by the draft, but
> in most cases you are using the tel uri to carry a dialstring,
> which the draft says is out of scope.
> 
> So, I claim that you have extended the tel uri.  It's okay to have
> a phone that does this, as well as your proxy implements the same
> extension.  I don't know of any document that would describe such
> an extension, and I don't want to support creating one.
> 
> Nevertheless, if that's what the administrator wants to happen,
> and both ends can handle it, I wouldn't say that it's wrong.
> 
> 
>>Its my system, my dial plan, my definition of the "dial.cisco.com" 
>>phone-context, so I don't see what you have to complain 
>>about. You say I 
>>can only use user=phone (or tel:) when the address is that of a 
>>terminal. But I get to decide what the addresses of terminals 
>>are. I say 
>>I am using my dialplan to translate dial strings into addresses of 
>>terminals - it just happens that my terminal addresses look 
>>remarkably 
>>similar to dialstrings.
> 
> I would say that your proxy would be going above and beyond the
> minimal definition of routing a sip uri that has user=phone, but
> I wouldn't want to prohibit it.  What I would want to "prohibit"
> is a requirement that any phone that didn't have a digitmap be able
> to send such a string.
> 
> 
>>Of course the last rule isn't needed any more because it can never be 
>>reached. So my complete dialplan is just:
>>
>>	translate all numbers that start with "0"..."9","*","#"
>>	to "tel:" + dialstring + ";phone-context=dial.cisco.com"
>>
>>What am I doing wrong here?
> 
> Nothing, as long as your proxy can do this.  Not all proxies will.
> Of course, not all proxies will process user=dialstring either.
> The key issue for me is that dumb phones always process user
> keypresses into user=dialstring+phone-context, and that is the one
> way to get dialstring processing done.  If you happen to have a
> proxy that can also process a dialstring that has user=phone, fine,
> but the only phones that are going to do that are phones that have
> digitmaps, and administrators who create a digitmap that does your
> example for a proxy that implements things beyond the spec.
> 
> You could just as well have a digitmap that said:
> 	translate all numbers that start with "0".."9","*","#"
> 	to "sip:dialstring" + dialstring + "@cisco.com"
> As long as your proxy can process a sip uri that looks like that,
> then it's going to work.  Some proxies might work fine with that,
> because they have regexp processing, and the regexp can handle
> the example I gave.  No problem.  
> 
> I don't want to see your example, or mine for that matter, in any
> standards document.
> 
> Brian
>  
> 


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



From exim@www1.ietf.org  Tue Dec  2 11:58:32 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27009
	for <sipping-archive@odin.ietf.org>; Tue, 2 Dec 2003 11:58:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARDqo-00021n-J2
	for sipping-archive@odin.ietf.org; Tue, 02 Dec 2003 11:58:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB2GwE3U007789
	for sipping-archive@odin.ietf.org; Tue, 2 Dec 2003 11:58:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARDqo-00021Y-Di
	for sipping-web-archive@optimus.ietf.org; Tue, 02 Dec 2003 11:58:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26958
	for <sipping-web-archive@ietf.org>; Tue, 2 Dec 2003 11:57:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARDqm-0004Gy-00
	for sipping-web-archive@ietf.org; Tue, 02 Dec 2003 11:58:12 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARDql-0004Gu-00
	for sipping-web-archive@ietf.org; Tue, 02 Dec 2003 11:58:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARDqc-0001w2-1J; Tue, 02 Dec 2003 11:58:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARDqM-0001sB-0f
	for sipping@optimus.ietf.org; Tue, 02 Dec 2003 11:57:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26929
	for <sipping@ietf.org>; Tue, 2 Dec 2003 11:57:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARDqK-0004Fe-00
	for sipping@ietf.org; Tue, 02 Dec 2003 11:57:44 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARDqJ-0004Eq-00
	for sipping@ietf.org; Tue, 02 Dec 2003 11:57:43 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA10688;
	Tue, 2 Dec 2003 11:57:09 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA29893;
	Tue, 2 Dec 2003 11:57:10 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <W9W7678N>; Tue, 2 Dec 2003 11:57:09 -0500
Message-ID: <313680C9A886D511A06000204840E1CF070B6155@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Paul Kyzivat'" <pkyzivat@cisco.com>
Cc: sipping@ietf.org
Subject: RE: [Sipping] User=Phone/DialString and Pause and Wait
Date: Tue, 2 Dec 2003 11:57:09 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

I'm a little conflicted on this.

Generally, we see phones that have only a small amount of configuration.
I usually am quoted as saying "configuration is evil".  I like discovery,
rather than configuration.  So, SRV or DHCP discovery of your
outgoing proxy server is a Good Thing (tm).  I'd prefer to get the
phone context from DHCP because it's usually exactly the right level
of hierarchy on where context boundaries are (one or a small set of
subnets).

OTOH, I agree that a single default substitution rule is easy to implement,
easy to specify, and provides a lot of flexibility to administrators.

Brian

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> Sent: Tuesday, December 02, 2003 11:45 AM
> To: Rosen, Brian
> Cc: sipping@ietf.org
> Subject: Re: [Sipping] User=Phone/DialString and Pause and Wait
> 
> 
> Brian,
> 
> I don't have any major disagreements with what you say below, 
> though I 
> think I would still spin it or explain it somewhat 
> differently. I think 
> this is ultimately coming down to how you configure phones - 
> especially 
> dumb phones - and how dumb a dumb phone is.
> 
> I imagine we can safely say that there aren't yet any phones that 
> generate uris containing user=dialstring, so we are only 
> talking about 
> phones that are yet to be built, or at least new software loads for 
> existing phones. And practically speaking, for awhile now there will 
> probably be little market for phones that *always* generate uris with 
> user=dialstring, because they won't work with older systems. 
> So we are 
> probably talking about phones that can be configured with 
> that part of 
> the translation. So I think even the dumbest of phones that 
> can do any 
> of this will probably be smart enough to do more than you 
> expect from a 
> dumb phone.
> 
> It may be that the best thing would be to standardize the 
> configuration 
> of dialplans in a phone, with the possibility that the 
> dialplan could be 
> as simple as a single mapping for all dialstrings, with the proxy 
> expected to do the rest.
> 
> 	Paul
> 
> Rosen, Brian wrote:
> >  
> > 
> >>>I think that covers all cases of dumb phones.  It might also covers
> >>>a case you suggest, which would be an incomplete digitmap that
> >>>needed an escape clause.  Digitmap capable phones need more work,
> >>>and I agree we need to standardize that, and we both are aware
> >>>of the efforts to do that.
> >>
> >>It would also be very sensible for the translation that is 
> >>used by dumb 
> >>phones is of exactly the same form as one entry in a dial map for a 
> >>smart phone. Rather than using the transformation you mention 
> >>above on 
> >>each dialstring, it would be straightforward to say that a single 
> >>template is either configured, or is created from 
> >>discoverable data. If 
> >>you can discover a context to use with dialstrings you can 
> >>just as well 
> >>discover a template.
> > 
> > If you are proposing that a dumb phone is just a smart phone with a
> > default translation rule, then I don't see a problem as long as the
> > default rule is as I suggest (sip: in the front, user=dialstring and
> > phone-context in the back.
> > 
> > 
> >>>None of this is pushback to the argument that user=phone is only
> >>>appropriate when the userpart is the address of a terminal (ie
> >>>phone number).  I do want a simple rule - if you don't understand 
> >>>what the string of digits is, it's a dialstring and send 
> >>
> >>user=dialstring.  
> >>
> >>>If you can, translate the dialstring to a phone number and send 
> >>>user=phone (or tel uri).  There is no third case that I know of.
> >>
> >>Suppose I had a dial plan that said:
> >>
> >>	translate all numbers that start with "8"
> >>	to "tel:" + dialstring + ";phone-context=dial.cisco.com"
> >>
> >>I think that should be ok with you. Now instead, suppose I 
> >>made the rule:
> >>
> >>	translate all numbers that start with "0"..."9","*","#"
> >>	to "tel:" + dialstring + ";phone-context=dial.cisco.com"
> >>
> >>	translate all other numbers to
> >>	"sip:" + dialstring + ";phone-context=dial.cisco.com"
> >>	       + "@cisco.com;user=dialstring"
> >>
> >>Is that still ok with you? Why not?
> > 
> > The problem that I have with this is that a dialstring starting
> > with pound or star is not (at least usually) a phone number.
> > They are usually service invocations.  You rarely route such
> > a number to a terminal without a fair amount of processing.
> > The text states that they are possible characters in a local
> > phone number, so the syntax is permitted by the draft, but
> > in most cases you are using the tel uri to carry a dialstring,
> > which the draft says is out of scope.
> > 
> > So, I claim that you have extended the tel uri.  It's okay to have
> > a phone that does this, as well as your proxy implements the same
> > extension.  I don't know of any document that would describe such
> > an extension, and I don't want to support creating one.
> > 
> > Nevertheless, if that's what the administrator wants to happen,
> > and both ends can handle it, I wouldn't say that it's wrong.
> > 
> > 
> >>Its my system, my dial plan, my definition of the "dial.cisco.com" 
> >>phone-context, so I don't see what you have to complain 
> >>about. You say I 
> >>can only use user=phone (or tel:) when the address is that of a 
> >>terminal. But I get to decide what the addresses of terminals 
> >>are. I say 
> >>I am using my dialplan to translate dial strings into addresses of 
> >>terminals - it just happens that my terminal addresses look 
> >>remarkably 
> >>similar to dialstrings.
> > 
> > I would say that your proxy would be going above and beyond the
> > minimal definition of routing a sip uri that has user=phone, but
> > I wouldn't want to prohibit it.  What I would want to "prohibit"
> > is a requirement that any phone that didn't have a digitmap be able
> > to send such a string.
> > 
> > 
> >>Of course the last rule isn't needed any more because it 
> can never be 
> >>reached. So my complete dialplan is just:
> >>
> >>	translate all numbers that start with "0"..."9","*","#"
> >>	to "tel:" + dialstring + ";phone-context=dial.cisco.com"
> >>
> >>What am I doing wrong here?
> > 
> > Nothing, as long as your proxy can do this.  Not all proxies will.
> > Of course, not all proxies will process user=dialstring either.
> > The key issue for me is that dumb phones always process user
> > keypresses into user=dialstring+phone-context, and that is the one
> > way to get dialstring processing done.  If you happen to have a
> > proxy that can also process a dialstring that has user=phone, fine,
> > but the only phones that are going to do that are phones that have
> > digitmaps, and administrators who create a digitmap that does your
> > example for a proxy that implements things beyond the spec.
> > 
> > You could just as well have a digitmap that said:
> > 	translate all numbers that start with "0".."9","*","#"
> > 	to "sip:dialstring" + dialstring + "@cisco.com"
> > As long as your proxy can process a sip uri that looks like that,
> > then it's going to work.  Some proxies might work fine with that,
> > because they have regexp processing, and the regexp can handle
> > the example I gave.  No problem.  
> > 
> > I don't want to see your example, or mine for that matter, in any
> > standards document.
> > 
> > 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 exim@www1.ietf.org  Tue Dec  2 14:34:25 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03774
	for <sipping-archive@odin.ietf.org>; Tue, 2 Dec 2003 14:34:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARGHg-00037T-IN
	for sipping-archive@odin.ietf.org; Tue, 02 Dec 2003 14:34:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB2JY874011987
	for sipping-archive@odin.ietf.org; Tue, 2 Dec 2003 14:34:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARGHg-00037G-D8
	for sipping-web-archive@optimus.ietf.org; Tue, 02 Dec 2003 14:34:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03758
	for <sipping-web-archive@ietf.org>; Tue, 2 Dec 2003 14:33:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARGHd-0006nK-00
	for sipping-web-archive@ietf.org; Tue, 02 Dec 2003 14:34:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARGHd-0006nH-00
	for sipping-web-archive@ietf.org; Tue, 02 Dec 2003 14:34:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARGHZ-00035s-Rk; Tue, 02 Dec 2003 14:34:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARGGk-000354-CO
	for sipping@optimus.ietf.org; Tue, 02 Dec 2003 14:33:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03721
	for <sipping@ietf.org>; Tue, 2 Dec 2003 14:32:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARGGh-0006my-00
	for sipping@ietf.org; Tue, 02 Dec 2003 14:33:07 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARGGh-0006mU-00
	for sipping@ietf.org; Tue, 02 Dec 2003 14:33:07 -0500
Received: from cisco.com (171.68.223.138)
  by sj-iport-5.cisco.com with ESMTP; 02 Dec 2003 11:31:57 -0800
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62])
	by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id hB2JWYiN016419;
	Tue, 2 Dec 2003 11:32:34 -0800 (PST)
Received: from cisco.com ([161.44.79.239])
	by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AEJ13280;
	Tue, 2 Dec 2003 14:32:32 -0500 (EST)
Message-ID: <3FCCE8D0.1070202@cisco.com>
Date: Tue, 02 Dec 2003 14:32:32 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Rosen, Brian" <Brian.Rosen@marconi.com>
CC: sipping@ietf.org
Subject: Re: [Sipping] User=Phone/DialString and Pause and Wait
References: <313680C9A886D511A06000204840E1CF070B6155@whq-msgusr-02.pit.comms.marconi.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Brian - inline.

	Paul

Rosen, Brian wrote:
> I'm a little conflicted on this.
> 
> Generally, we see phones that have only a small amount of configuration.
> I usually am quoted as saying "configuration is evil".  I like discovery,
> rather than configuration.  So, SRV or DHCP discovery of your
> outgoing proxy server is a Good Thing (tm).  I'd prefer to get the
> phone context from DHCP because it's usually exactly the right level
> of hierarchy on where context boundaries are (one or a small set of
> subnets).
> 
> OTOH, I agree that a single default substitution rule is easy to implement,
> easy to specify, and provides a lot of flexibility to administrators.
> 
> Brian

Well, the configuration you don't do for the phone is configuration you 
have to do for the proxy instead. It doesn't substantially change the 
problem.

If I have to manually enter the configuration into the phone I agree it 
is pretty evil in general. But if the configuration data for the phone 
lives somewhere in the network and is "discovered" when the phone boots, 
then it is much less evil. Then it doesn't matter much whether that 
config data is consumed  by the phone or by a proxy.

Sip is postulated on smart endpoints. But smart endpoints need 
information before they can act smart. It is still going to take a bit 
of work before phones can act smart and yet be used mix and match in 
heterogeneous sip systems.

I think there ought to be standards for configuring dial plans that will 
be executed by phones.

	Paul

>>-----Original Message-----
>>From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
>>Sent: Tuesday, December 02, 2003 11:45 AM
>>To: Rosen, Brian
>>Cc: sipping@ietf.org
>>Subject: Re: [Sipping] User=Phone/DialString and Pause and Wait
>>
>>
>>Brian,
>>
>>I don't have any major disagreements with what you say below, 
>>though I 
>>think I would still spin it or explain it somewhat 
>>differently. I think 
>>this is ultimately coming down to how you configure phones - 
>>especially 
>>dumb phones - and how dumb a dumb phone is.
>>
>>I imagine we can safely say that there aren't yet any phones that 
>>generate uris containing user=dialstring, so we are only 
>>talking about 
>>phones that are yet to be built, or at least new software loads for 
>>existing phones. And practically speaking, for awhile now there will 
>>probably be little market for phones that *always* generate uris with 
>>user=dialstring, because they won't work with older systems. 
>>So we are 
>>probably talking about phones that can be configured with 
>>that part of 
>>the translation. So I think even the dumbest of phones that 
>>can do any 
>>of this will probably be smart enough to do more than you 
>>expect from a 
>>dumb phone.
>>
>>It may be that the best thing would be to standardize the 
>>configuration 
>>of dialplans in a phone, with the possibility that the 
>>dialplan could be 
>>as simple as a single mapping for all dialstrings, with the proxy 
>>expected to do the rest.
>>
>>	Paul
>>
>>Rosen, Brian wrote:
>>
>>> 
>>>
>>>
>>>>>I think that covers all cases of dumb phones.  It might also covers
>>>>>a case you suggest, which would be an incomplete digitmap that
>>>>>needed an escape clause.  Digitmap capable phones need more work,
>>>>>and I agree we need to standardize that, and we both are aware
>>>>>of the efforts to do that.
>>>>
>>>>It would also be very sensible for the translation that is 
>>>>used by dumb 
>>>>phones is of exactly the same form as one entry in a dial map for a 
>>>>smart phone. Rather than using the transformation you mention 
>>>>above on 
>>>>each dialstring, it would be straightforward to say that a single 
>>>>template is either configured, or is created from 
>>>>discoverable data. If 
>>>>you can discover a context to use with dialstrings you can 
>>>>just as well 
>>>>discover a template.
>>>
>>>If you are proposing that a dumb phone is just a smart phone with a
>>>default translation rule, then I don't see a problem as long as the
>>>default rule is as I suggest (sip: in the front, user=dialstring and
>>>phone-context in the back.
>>>
>>>
>>>
>>>>>None of this is pushback to the argument that user=phone is only
>>>>>appropriate when the userpart is the address of a terminal (ie
>>>>>phone number).  I do want a simple rule - if you don't understand 
>>>>>what the string of digits is, it's a dialstring and send 
>>>>
>>>>user=dialstring.  
>>>>
>>>>
>>>>>If you can, translate the dialstring to a phone number and send 
>>>>>user=phone (or tel uri).  There is no third case that I know of.
>>>>
>>>>Suppose I had a dial plan that said:
>>>>
>>>>	translate all numbers that start with "8"
>>>>	to "tel:" + dialstring + ";phone-context=dial.cisco.com"
>>>>
>>>>I think that should be ok with you. Now instead, suppose I 
>>>>made the rule:
>>>>
>>>>	translate all numbers that start with "0"..."9","*","#"
>>>>	to "tel:" + dialstring + ";phone-context=dial.cisco.com"
>>>>
>>>>	translate all other numbers to
>>>>	"sip:" + dialstring + ";phone-context=dial.cisco.com"
>>>>	       + "@cisco.com;user=dialstring"
>>>>
>>>>Is that still ok with you? Why not?
>>>
>>>The problem that I have with this is that a dialstring starting
>>>with pound or star is not (at least usually) a phone number.
>>>They are usually service invocations.  You rarely route such
>>>a number to a terminal without a fair amount of processing.
>>>The text states that they are possible characters in a local
>>>phone number, so the syntax is permitted by the draft, but
>>>in most cases you are using the tel uri to carry a dialstring,
>>>which the draft says is out of scope.
>>>
>>>So, I claim that you have extended the tel uri.  It's okay to have
>>>a phone that does this, as well as your proxy implements the same
>>>extension.  I don't know of any document that would describe such
>>>an extension, and I don't want to support creating one.
>>>
>>>Nevertheless, if that's what the administrator wants to happen,
>>>and both ends can handle it, I wouldn't say that it's wrong.
>>>
>>>
>>>
>>>>Its my system, my dial plan, my definition of the "dial.cisco.com" 
>>>>phone-context, so I don't see what you have to complain 
>>>>about. You say I 
>>>>can only use user=phone (or tel:) when the address is that of a 
>>>>terminal. But I get to decide what the addresses of terminals 
>>>>are. I say 
>>>>I am using my dialplan to translate dial strings into addresses of 
>>>>terminals - it just happens that my terminal addresses look 
>>>>remarkably 
>>>>similar to dialstrings.
>>>
>>>I would say that your proxy would be going above and beyond the
>>>minimal definition of routing a sip uri that has user=phone, but
>>>I wouldn't want to prohibit it.  What I would want to "prohibit"
>>>is a requirement that any phone that didn't have a digitmap be able
>>>to send such a string.
>>>
>>>
>>>
>>>>Of course the last rule isn't needed any more because it 
>>>
>>can never be 
>>
>>>>reached. So my complete dialplan is just:
>>>>
>>>>	translate all numbers that start with "0"..."9","*","#"
>>>>	to "tel:" + dialstring + ";phone-context=dial.cisco.com"
>>>>
>>>>What am I doing wrong here?
>>>
>>>Nothing, as long as your proxy can do this.  Not all proxies will.
>>>Of course, not all proxies will process user=dialstring either.
>>>The key issue for me is that dumb phones always process user
>>>keypresses into user=dialstring+phone-context, and that is the one
>>>way to get dialstring processing done.  If you happen to have a
>>>proxy that can also process a dialstring that has user=phone, fine,
>>>but the only phones that are going to do that are phones that have
>>>digitmaps, and administrators who create a digitmap that does your
>>>example for a proxy that implements things beyond the spec.
>>>
>>>You could just as well have a digitmap that said:
>>>	translate all numbers that start with "0".."9","*","#"
>>>	to "sip:dialstring" + dialstring + "@cisco.com"
>>>As long as your proxy can process a sip uri that looks like that,
>>>then it's going to work.  Some proxies might work fine with that,
>>>because they have regexp processing, and the regexp can handle
>>>the example I gave.  No problem.  
>>>
>>>I don't want to see your example, or mine for that matter, in any
>>>standards document.
>>>
>>>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 exim@www1.ietf.org  Tue Dec  2 14:47:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04438
	for <sipping-archive@odin.ietf.org>; Tue, 2 Dec 2003 14:47:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARGUD-0004CQ-EY
	for sipping-archive@odin.ietf.org; Tue, 02 Dec 2003 14:47:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB2Jl5bp016141
	for sipping-archive@odin.ietf.org; Tue, 2 Dec 2003 14:47:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARGUD-0004CG-AX
	for sipping-web-archive@optimus.ietf.org; Tue, 02 Dec 2003 14:47:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04426
	for <sipping-web-archive@ietf.org>; Tue, 2 Dec 2003 14:46:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARGUA-0006zw-00
	for sipping-web-archive@ietf.org; Tue, 02 Dec 2003 14:47:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARGUA-0006zt-00
	for sipping-web-archive@ietf.org; Tue, 02 Dec 2003 14:47:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARGU9-0004B3-22; Tue, 02 Dec 2003 14:47:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARGTd-0004Ad-FT
	for sipping@optimus.ietf.org; Tue, 02 Dec 2003 14:46:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04407
	for <sipping@ietf.org>; Tue, 2 Dec 2003 14:46:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARGTa-0006yu-00
	for sipping@ietf.org; Tue, 02 Dec 2003 14:46:26 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARGTa-0006yg-00
	for sipping@ietf.org; Tue, 02 Dec 2003 14:46:26 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA16796;
	Tue, 2 Dec 2003 14:45:49 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA29717;
	Tue, 2 Dec 2003 14:45:49 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <W9W77C5B>; Tue, 2 Dec 2003 14:45:49 -0500
Message-ID: <313680C9A886D511A06000204840E1CF070B6159@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Paul Kyzivat'" <pkyzivat@cisco.com>
Cc: sipping@ietf.org
Subject: RE: [Sipping] User=Phone/DialString and Pause and Wait
Date: Tue, 2 Dec 2003 14:45:48 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

> Well, the configuration you don't do for the phone is 
> configuration you 
> have to do for the proxy instead. It doesn't substantially change the 
> problem.
Our experience is that it's quite a lot different.
You configure DHCP or the proxy once, and it's done.
Phones, you keep having to fiddle with
	Because every brand is just a little different
	Because users want to change things
	Because they come and go
> 
> If I have to manually enter the configuration into the phone 
> I agree it 
> is pretty evil in general. But if the configuration data for 
> the phone 
> lives somewhere in the network and is "discovered" when the 
> phone boots, 
> then it is much less evil. Then it doesn't matter much whether that 
> config data is consumed  by the phone or by a proxy.
If it's really discovered and really standardized I agree.
I think we have quite a long way to go before we get there.

> 
> Sip is postulated on smart endpoints. But smart endpoints need 
> information before they can act smart. It is still going to 
> take a bit 
> of work before phones can act smart and yet be used mix and match in 
> heterogeneous sip systems.
I'm actually surprised at how untrue this is.
If you know your outgoing proxy server, and the details of authentication,
you can get A LONG way towards zero touch.

It's when you do get into things like digitmaps that things get weird.
I think some phones try to be too configurable.

Our present systems, which to be sure usually work homogeneously
with our proxy, is zero touch.  Out of the box, plug in, and
logon (with a PC username and password).  Everything is discovered.
We do in fact use a discoverable configuration mechanism, which
is currently proprietary, to deal with terminal specific configuration.
Most of the personalization that we see in many other brands of phones
we think is misplaced from the user to the phone.  Things like
speed dials, UI choices, etc belong to a user, and not a phone,
and should be downloaded when you authenticate, and not when you boot 
the phone.  If you authenticate as the same user to a different 
phone, your personality should follow you.   But I digress.
> 
> I think there ought to be standards for configuring dial 
> plans that will 
> be executed by phones.
I agree
 

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



From exim@www1.ietf.org  Thu Dec  4 16:29:39 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16214
	for <sipping-archive@odin.ietf.org>; Thu, 4 Dec 2003 16:29:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS12J-0001mo-Rm
	for sipping-archive@odin.ietf.org; Thu, 04 Dec 2003 16:29:24 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB4LTNUt006860
	for sipping-archive@odin.ietf.org; Thu, 4 Dec 2003 16:29:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS12J-0001mZ-Ka
	for sipping-web-archive@optimus.ietf.org; Thu, 04 Dec 2003 16:29:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16096
	for <sipping-web-archive@ietf.org>; Thu, 4 Dec 2003 16:28:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS125-0000vy-00
	for sipping-web-archive@ietf.org; Thu, 04 Dec 2003 16:29:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS124-0000vv-00
	for sipping-web-archive@ietf.org; Thu, 04 Dec 2003 16:29:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS11y-0001g7-3N; Thu, 04 Dec 2003 16:29:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS11J-0001fG-4s
	for sipping@optimus.ietf.org; Thu, 04 Dec 2003 16:28:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16028
	for <sipping@ietf.org>; Thu, 4 Dec 2003 16:28:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS11H-0000uH-00
	for sipping@ietf.org; Thu, 04 Dec 2003 16:28:19 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS11G-0000tm-00
	for sipping@ietf.org; Thu, 04 Dec 2003 16:28:18 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id QAA04770;
	Thu, 4 Dec 2003 16:27:36 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id QAA03974;
	Thu, 4 Dec 2003 16:27:35 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <W9W79DM1>; Thu, 4 Dec 2003 16:27:35 -0500
Message-ID: <313680C9A886D511A06000204840E1CF070B6189@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Paul Kyzivat'" <pkyzivat@cisco.com>
Cc: sipping@ietf.org
Subject: RE: [Sipping] User=Phone/DialString and Pause and Wait
Date: Thu, 4 Dec 2003 16:27:26 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

> > I think some phones try to be too configurable.
>  >
> > Our present systems, which to be sure usually work homogeneously
> > with our proxy, is zero touch.  Out of the box, plug in, and
> > logon (with a PC username and password). 
> 
> This is to register a PC softphone? Or to register a real sip phone?
Real phone - but a videophone

> 
> How do you enter a PC username and password into a phone with just a 
> number pad? Do you expect grandma to be able to do so?
Touch screen keyboard, but 99.9% of the time the username is defaulted,
Since it's a heck of a lot more reliable than the PC, you rarely
do this unless you actually roam.  When you roam to another site,
you have to type.  The payback, on the other hand is pretty large.
	One identity, one password, that you actually usually do memorize
	Automatic association with your PC for CTI stuff
	Complete personalization that really does roam correctly
Users like it a lot.

> 
>  > Everything is discovered.
> > We do in fact use a discoverable configuration mechanism, which
> > is currently proprietary, to deal with terminal specific 
> configuration.
> 
> Yeah. And it will of course continue to be proprietary until 
> there is a 
> standard. But if you have this, proprietary or standard, then 
> it can be 
> used to load dialplans into a phone. Then the issue of sending 
> dialstrings to the proxy becomes moot.
Depends.  On our system, its easy to put digitmap processing
in place because we have lots of code space and lots of horsepower.
Cheap phones have more problems, depending on how complex you want
the processor.  I gather that the current proposal is a regexp.
On the one hand, that's pretty easily liftable code, but it's not
very small.  When the proposal was 3 mechanisms (or was it 4),
I was really thinking that it would never get done in cheap phones.

I expect that long term we will in fact move to regexps in the phone,
but I also expect it will take a lot longer than you would like.

> 
> > Most of the personalization that we see in many other 
> brands of phones
> > we think is misplaced from the user to the phone.  Things like
> > speed dials, UI choices, etc belong to a user, and not a phone,
> > and should be downloaded when you authenticate, and not 
> when you boot 
> > the phone.  If you authenticate as the same user to a different 
> > phone, your personality should follow you.   But I digress.
> 
> No disagreement here. But this provides considerable latitude 
> in where 
> things are done. As long as the personalization info for the 
> user/phone 
> is managed centrally, it doesn't matter whether it is consumed by the 
> phone or a proxy.
This specific issue is a very nasty problem that consumed a lot of
arguments when we worked on roaming.  The fundamental question is:
	Is a dial plan site specific or user specific when you roam?

Generally, it's taken as site specific.  That means, for us, it
goes in the phone, rather than with the user personality stuff.
But a lot of users in our testing preferred that it be consistent
for them as they roamed, because they usually didn't know the
local dialing plan, but they did know their home plan.

Implementation of this is also pretty tricky; if you want caller-ID
correct on enterprise systems that aren't 100% VoIP, you end up
having to route to the home gateway for calls that are PSTN or
on any enterprise PBX.  But again, I digress.

YMMV

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



From exim@www1.ietf.org  Thu Dec  4 16:34:10 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17597
	for <sipping-archive@odin.ietf.org>; Thu, 4 Dec 2003 16:34:10 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS16h-00023O-Mb
	for sipping-archive@odin.ietf.org; Thu, 04 Dec 2003 16:33:56 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB4LXtoS007888
	for sipping-archive@odin.ietf.org; Thu, 4 Dec 2003 16:33:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS16h-000238-JJ
	for sipping-web-archive@optimus.ietf.org; Thu, 04 Dec 2003 16:33:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17492
	for <sipping-web-archive@ietf.org>; Thu, 4 Dec 2003 16:33:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS16f-0001X2-00
	for sipping-web-archive@ietf.org; Thu, 04 Dec 2003 16:33:53 -0500
Received: from manatick.foretec.com ([4.17.168.5] helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS0sW-0000h0-00
	for sipping-web-archive@ietf.org; Thu, 04 Dec 2003 16:19:16 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org)
	by manatick with esmtp (Exim 4.24)
	id 1AS0ck-0003sU-4C
	for sipping-web-archive@ietf.org; Thu, 04 Dec 2003 16:03:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS0bp-0000Yd-FZ; Thu, 04 Dec 2003 16:02:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS0bd-0000YH-Ub
	for sipping@optimus.ietf.org; Thu, 04 Dec 2003 16:01:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14308
	for <sipping@ietf.org>; Thu, 4 Dec 2003 16:01:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS0bX-0000HX-00
	for sipping@ietf.org; Thu, 04 Dec 2003 16:01:43 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS0as-0000Ge-00
	for sipping@ietf.org; Thu, 04 Dec 2003 16:01:03 -0500
Received: from rtp-core-1.cisco.com (64.102.124.12)
  by sj-iport-5.cisco.com with ESMTP; 04 Dec 2003 13:00:20 +0000
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62])
	by rtp-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hB4Kxexg016771;
	Thu, 4 Dec 2003 15:59:40 -0500 (EST)
Received: from cisco.com ([161.44.79.239])
	by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AEK86978;
	Thu, 4 Dec 2003 15:59:38 -0500 (EST)
Message-ID: <3FCFA03A.2000903@cisco.com>
Date: Thu, 04 Dec 2003 15:59:38 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Rosen, Brian" <Brian.Rosen@marconi.com>
CC: sipping@ietf.org
Subject: Re: [Sipping] User=Phone/DialString and Pause and Wait
References: <313680C9A886D511A06000204840E1CF070B6159@whq-msgusr-02.pit.comms.marconi.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



Rosen, Brian wrote:
>>Well, the configuration you don't do for the phone is 
>>configuration you 
>>have to do for the proxy instead. It doesn't substantially change the 
>>problem.
> 
> Our experience is that it's quite a lot different.
> You configure DHCP or the proxy once, and it's done.
> Phones, you keep having to fiddle with
> 	Because every brand is just a little different
> 	Because users want to change things
> 	Because they come and go
> 
>>If I have to manually enter the configuration into the phone 
>>I agree it 
>>is pretty evil in general. But if the configuration data for 
>>the phone 
>>lives somewhere in the network and is "discovered" when the 
>>phone boots, 
>>then it is much less evil. Then it doesn't matter much whether that 
>>config data is consumed  by the phone or by a proxy.
> 
> If it's really discovered and really standardized I agree.
> I think we have quite a long way to go before we get there.

Sure. But that is something we ought to be working on, because it is 
essential to interop. There is already some work in progress (though 
still at a very early stage):

- draft-ietf-sipping-ua-prof-framewk-reqs-00
- draft-stredicke-sipping-ep-config-00
   (now expired)

>>Sip is postulated on smart endpoints. But smart endpoints need 
>>information before they can act smart. It is still going to 
>>take a bit 
>>of work before phones can act smart and yet be used mix and match in 
>>heterogeneous sip systems.
> 
> I'm actually surprised at how untrue this is.
> If you know your outgoing proxy server, and the details of authentication,
> you can get A LONG way towards zero touch.
> 
> It's when you do get into things like digitmaps that things get weird.

Sure. But that is the subject isn't it?

> I think some phones try to be too configurable.
 >
> Our present systems, which to be sure usually work homogeneously
> with our proxy, is zero touch.  Out of the box, plug in, and
> logon (with a PC username and password). 

This is to register a PC softphone? Or to register a real sip phone?

How do you enter a PC username and password into a phone with just a 
number pad? Do you expect grandma to be able to do so?

 > Everything is discovered.
> We do in fact use a discoverable configuration mechanism, which
> is currently proprietary, to deal with terminal specific configuration.

Yeah. And it will of course continue to be proprietary until there is a 
standard. But if you have this, proprietary or standard, then it can be 
used to load dialplans into a phone. Then the issue of sending 
dialstrings to the proxy becomes moot.

> Most of the personalization that we see in many other brands of phones
> we think is misplaced from the user to the phone.  Things like
> speed dials, UI choices, etc belong to a user, and not a phone,
> and should be downloaded when you authenticate, and not when you boot 
> the phone.  If you authenticate as the same user to a different 
> phone, your personality should follow you.   But I digress.

No disagreement here. But this provides considerable latitude in where 
things are done. As long as the personalization info for the user/phone 
is managed centrally, it doesn't matter whether it is consumed by the 
phone or a proxy.

>>I think there ought to be standards for configuring dial 
>>plans that will 
>>be executed by phones.
> 
> I agree

Great!

	Paul


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



From exim@www1.ietf.org  Sat Dec  6 13:20:28 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15249
	for <sipping-archive@odin.ietf.org>; Sat, 6 Dec 2003 13:20:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASh2L-0001mr-Pg
	for sipping-archive@odin.ietf.org; Sat, 06 Dec 2003 13:20:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB6IKDnt006865
	for sipping-archive@odin.ietf.org; Sat, 6 Dec 2003 13:20:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASh2L-0001me-HF
	for sipping-web-archive@optimus.ietf.org; Sat, 06 Dec 2003 13:20:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15235
	for <sipping-web-archive@ietf.org>; Sat, 6 Dec 2003 13:19:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASh2J-0004mD-00
	for sipping-web-archive@ietf.org; Sat, 06 Dec 2003 13:20:11 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASh2J-0004m9-00
	for sipping-web-archive@ietf.org; Sat, 06 Dec 2003 13:20:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASh2C-0001lN-DD; Sat, 06 Dec 2003 13:20:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASh22-0001ke-DN
	for sipping@optimus.ietf.org; Sat, 06 Dec 2003 13:19:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15230
	for <sipping@ietf.org>; Sat, 6 Dec 2003 13:19:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASh20-0004m6-00
	for sipping@ietf.org; Sat, 06 Dec 2003 13:19:52 -0500
Received: from imr1.ericy.com ([198.24.6.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASh1z-0004lO-00
	for sipping@ietf.org; Sat, 06 Dec 2003 13:19:51 -0500
Received: from eamrcnt750.exu.ericsson.se (eamrcnt750.exu.ericsson.se [138.85.133.51])
	by imr1.ericy.com (8.12.10/8.12.10) with ESMTP id hB6IJ7Wm012866;
	Sat, 6 Dec 2003 12:19:07 -0600 (CST)
Received: from ericsson.com (rvi2-92-224.sw.ericsson.se [153.88.92.224]) by eamrcnt750.exu.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id YGLP9D0H; Sat, 6 Dec 2003 12:19:00 -0600
Message-ID: <3FD21D7F.7030500@ericsson.com>
Date: Sat, 06 Dec 2003 20:18:39 +0200
X-Sybari-Trust: 6e097109 6fa56f4d 884b220c 00000138
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
CC: sipping <sipping@ietf.org>, Adam Roach <adam@dynamicsoft.com>,
        Robert Sparks <rsparks@dynamicsoft.com>
Subject: Re: [Sipping] Exploders anad ad-hoc lists
References: <3FC209FA.6030004@ericsson.com> <3FC4ED22.3040604@cisco.com>
In-Reply-To: <3FC4ED22.3040604@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Paul,

regadring where to place the ad-hoc list, in a URI parameter or in a 
header, I personally do not have a strong opinion. Nevertheless, I was 
talking to Adam and Robert, and they said that, based on their 
experience with the SUBSCRIBE/NOTIFY and the REFER spec, they would 
rather use a URI parameter.

Thanks,

Gonzalo

Paul Kyzivat wrote:

> Gonzalo,
> 
> I like the concept, but I am troubled by passing the reference to the 
> list as a sip/sips url parameter, for the following reasons:
> 
> - how does it get there? In your examples, you have the parameter
>   in the request uri, but not in the To uri. Normally a UA would
>   determine the destination, and put it in both To and request URIs.
>   This implies some extra special casing.
> 
> - How does it stay there. If the address in the request uri is of
>   an AoR, a proxy may replace it with a corresponding registered
>   contact. If so, the reference to the list will be lost.
> 
> - logically the request is being addressed to the service, and the
>   list is a parameter to the service and the particular method the
>   service is being asked to perform. Embedding the list in the address
>   of the service seems inappropriate.
> 
> I think there needs to be a better place to put the reference to the 
> list. A new header would seem to be the logical answer.
> 
> Regarding draft-camarillo-sipping-exploders-solution-00:
> 
> You say the requester should subscribe to a url returned in the response 
> to learn the outcome of the exploded requests. But that opens a time 
> window when some status may lost. Do you have any thoughts on how to 
> close that? (E.g. the first response to a subscription gives all the 
> cumulative history of what has happened.)
> 
> There are a couple of references to an Explode-To header, but no 
> explanation and no examples. It seems redundant to the list, unless it 
> is intended as a way to convey the reference to the list.
> 
>     Paul
> 
> Gonzalo Camarillo wrote:
> 
>> Folks,
>>
>> we have just submitted three drafts about exploders and ad-hoc lists.
>>
>> We have added more requirements to the following draft. The new 
>> requirements were mainly discussed in the SIMPLE mailing list.
>>
>> http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-exploders-01.txt 
>>
>>
>> The following draft describes how to carry lists of URIs in SIP 
>> requests. It is not a finished draft. It is intended to trigger 
>> discussions on this topic to see whether this is a step the right 
>> direction.
>>
>> http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-uri-list-00.txt 
>>
>>
>> The following draft defines a new method called EXPLODE. EXPLODE does 
>> the same as REFER. That is, it tells a UA to send a request somewhere. 
>> The differences are that EXPLODE accepts more than one destination 
>> (REFER carries a single Refer-To header field) and that EXPLODE does 
>> not establish implicit subscriptions of any type. This draft is also 
>> intended to trigger discussions within the WG.
>>
>> http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-explode-method-00.txt 
>>
>>
>> Let's try to keep discussions about this topic in the SIPPING mailing 
>> list. I will forward this mail to the SIMPLE mailing list to let them 
>> know.
>>
>> Comments are welcome,
>>
>> Gonzalo
>>
>>
>>
>> _______________________________________________
>> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>> This list is for NEW development of the application of SIP
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sip@ietf.org for new developments of core SIP
>>

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


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



From exim@www1.ietf.org  Sat Dec  6 13:25:19 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15565
	for <sipping-archive@odin.ietf.org>; Sat, 6 Dec 2003 13:25:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASh72-00024v-9m
	for sipping-archive@odin.ietf.org; Sat, 06 Dec 2003 13:25:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB6IP4Zf007983
	for sipping-archive@odin.ietf.org; Sat, 6 Dec 2003 13:25:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASh72-00024g-3l
	for sipping-web-archive@optimus.ietf.org; Sat, 06 Dec 2003 13:25:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15553
	for <sipping-web-archive@ietf.org>; Sat, 6 Dec 2003 13:24:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASh70-0004uU-00
	for sipping-web-archive@ietf.org; Sat, 06 Dec 2003 13:25:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASh6z-0004uR-00
	for sipping-web-archive@ietf.org; Sat, 06 Dec 2003 13:25:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASh70-00023b-SQ; Sat, 06 Dec 2003 13:25:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASh6h-00022w-3h
	for sipping@optimus.ietf.org; Sat, 06 Dec 2003 13:24:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15550
	for <sipping@ietf.org>; Sat, 6 Dec 2003 13:24:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASh6f-0004uI-00
	for sipping@ietf.org; Sat, 06 Dec 2003 13:24:41 -0500
Received: from imr1.ericy.com ([198.24.6.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASh6e-0004u2-00
	for sipping@ietf.org; Sat, 06 Dec 2003 13:24:40 -0500
Received: from eamrcnt750.exu.ericsson.se (eamrcnt750.exu.ericsson.se [138.85.133.51])
	by imr1.ericy.com (8.12.10/8.12.10) with ESMTP id hB6IO6Wm013451;
	Sat, 6 Dec 2003 12:24:06 -0600 (CST)
Received: from ericsson.com (rvi2-92-224.sw.ericsson.se [153.88.92.224]) by eamrcnt750.exu.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id YGLP912X; Sat, 6 Dec 2003 12:24:00 -0600
Message-ID: <3FD21EB9.6090101@ericsson.com>
Date: Sat, 06 Dec 2003 20:23:53 +0200
X-Sybari-Trust: 20aaef4b 6fa56f4d 884b220c 00000138
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Orit Levin <oritl@microsoft.com>
CC: sipping <sipping@ietf.org>, Adam Roach <adam@dynamicsoft.com>,
        Aki.Niemi@nokia.com, Hisham.Khartabil@nokia.com,
        Markus.Isomaki@nokia.com
Subject: Re: [Sipping] Exploders anad ad-hoc lists
References: <DD07841287D0AD428833021705E0D14ED37899@RED-MSG-52.redmond.corp.microsoft.com>
In-Reply-To: <DD07841287D0AD428833021705E0D14ED37899@RED-MSG-52.redmond.corp.microsoft.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Orit,

> 1. How do you propose sending the deltas? (Consistently with the updated
> requirements' draft.)

The idea would be to send them as a URI parameter of a subsequent 
request. Which request to use would depend on the application you are 
implementing. For example, for ad-hoc presence, the natural choice would 
be a SUBSCRIBE.

Regarding how to indicate that what you are sending is a delta rather 
than a full list, it should be handled by the XML definition of the list.

Gonzalo



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



From exim@www1.ietf.org  Sun Dec  7 04:55:28 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18664
	for <sipping-archive@odin.ietf.org>; Sun, 7 Dec 2003 04:55:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASvd9-000648-JH
	for sipping-archive@odin.ietf.org; Sun, 07 Dec 2003 04:55:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB79tBNW023292
	for sipping-archive@odin.ietf.org; Sun, 7 Dec 2003 04:55:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASvd7-00063b-4L
	for sipping-web-archive@optimus.ietf.org; Sun, 07 Dec 2003 04:55:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18644
	for <sipping-web-archive@ietf.org>; Sun, 7 Dec 2003 04:54:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASvd3-0006be-00
	for sipping-web-archive@ietf.org; Sun, 07 Dec 2003 04:55:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASvd3-0006bb-00
	for sipping-web-archive@ietf.org; Sun, 07 Dec 2003 04:55:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASvcz-000617-VK; Sun, 07 Dec 2003 04:55:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQrFh-0001GQ-80
	for sipping@optimus.ietf.org; Mon, 01 Dec 2003 11:50:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17389
	for <sipping@ietf.org>; Mon, 1 Dec 2003 11:50:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQrFg-00053j-00
	for sipping@ietf.org; Mon, 01 Dec 2003 11:50:24 -0500
Received: from pooh.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQrFe-00053g-00
	for sipping@ietf.org; Mon, 01 Dec 2003 11:50:23 -0500
Received: from pcmiller (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with SMTP id LAA10288
	for <sipping@ietf.org>; Mon, 1 Dec 2003 11:50:17 -0500 (EST)
From: "Stuart Miller" <stuart.miller@ulticom.com>
To: <sipping@ietf.org>
Date: Mon, 1 Dec 2003 11:48:45 -0500
Message-ID: <001c01c3b82a$fd140230$f22119ac@pcmiller>
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 V6.00.2600.0000
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [Sipping] draft-ietf-sipping-torture-tests-02 questions
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,

I have two questions regarding the Torture Tests draft version 02:

1)  For, 3.3.7 Unknown authorization scheme, does the Authorization line
follow the
     correct syntax?  I was told that
         Authorization: NoOneKnowsThisScheme opaque data here

     needs to be changed to something like
         Authorization: NoOneKnowsThisScheme param1=opaquedatahere1234

     Is this person correct?
2)  For, 3.1.1.2 Wide range of valid characters, the line with

         extensionHeader-!.%*+_`'~=

     does not have a colon following "extensionHeader".  Does it need to
have the colon?

Thank you,
Stu Miller
Ulticom, Inc
miller@ulticom.com



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



From exim@www1.ietf.org  Sun Dec  7 04:55:30 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18679
	for <sipping-archive@odin.ietf.org>; Sun, 7 Dec 2003 04:55:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASvd9-000647-JG
	for sipping-archive@odin.ietf.org; Sun, 07 Dec 2003 04:55:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB79tBN2023308
	for sipping-archive@odin.ietf.org; Sun, 7 Dec 2003 04:55:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASvd8-00063q-5t
	for sipping-web-archive@optimus.ietf.org; Sun, 07 Dec 2003 04:55:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18647
	for <sipping-web-archive@ietf.org>; Sun, 7 Dec 2003 04:54:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASvd3-0006bi-00
	for sipping-web-archive@ietf.org; Sun, 07 Dec 2003 04:55:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASvd3-0006bf-00
	for sipping-web-archive@ietf.org; Sun, 07 Dec 2003 04:55:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASvd1-00061I-6w; Sun, 07 Dec 2003 04:55:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQz0V-0000yP-8q
	for sipping@optimus.ietf.org; Mon, 01 Dec 2003 20:07:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14908;
	Mon, 1 Dec 2003 20:06:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQz0R-0006q1-00; Mon, 01 Dec 2003 20:07:11 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQz0R-0006pr-00; Mon, 01 Dec 2003 20:07:11 -0500
Received: from mbaugher-w2k07.cisco.com (sjc-vpn1-875.cisco.com [10.21.99.107])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id hB216brY013145;
	Mon, 1 Dec 2003 17:06:38 -0800 (PST)
Message-Id: <6.0.0.22.2.20031201163158.03cb0a28@mira-sjc5-6.cisco.com>
X-Sender: mbaugher@mira-sjc5-6.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Mon, 01 Dec 2003 17:06:34 -0800
To: Kumiko Ono <ono.kumiko@lab.ntt.co.jp>
From: Mark Baugher <mbaugher@cisco.com>
Cc: mary.barnes@nortelnetworks.com, tachimoto.shinya@lab.ntt.co.jp,
        sipping@ietf.org, mmusic@ietf.org, cyrus@ntt-at.com,
        fandreas@cisco.com, dwing@cisco.com
In-Reply-To: <2EC3B401E99BAEono.kumiko@lab.ntt.co.jp>
References: <6.0.0.22.2.20031125160613.03fd89d8@mira-sjc5-6.cisco.com>
 <2EC3B401E99BAEono.kumiko@lab.ntt.co.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Sipping] Re: e2m, m2m security drafts
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

hi Kumiko-san,

At 01:44 AM 11/26/2003, Kumiko Ono wrote:
>Hi Mark,
>
>Thanks for your comments. Inline-
>
><mbaugher@cisco.com> wrote:
> >1. Section 5.1 of
> >http://www.ietf.org/internet-drafts/draft-ono-sipping-end2middle-security-
> >00.txt
> >shows an example of an encrypted SDP in an INVITE but the key to this
> >encrypted SDP is selectively shared with some proxies so they can view the
> >encrypted data.  There is undoubtedly some information in the SDP that a
> >proxy needs to view and some that it does not need to view, such as the
> >end-to-end keying material.  Can we accommodate this requirement in the
> >current proposals?  That is, could we keep the keying material encrypted
> >end-to-end while allowing a proxy to view other parts of the SDP message?
>
>Yes, definitely.
>Section 3.1 of the requirement draft says that
>"The solution MUST work even with  SIP end-to-end encryption for
>confidentiality service enabled".
>
>To clarify this requirement, I would say:
>- It MUST work even with end-to-end encryption of some data.
>   That is, encrypted data can be shared with the end user and selected
>proxies.
>- It MUST NOT violate end-to-end encryption when the encrypted data does
>not need to be shared with any proxies.

Thanks.  One more clarification, please.  By "encrypted data" (which in
my case is the SDP crypto attribute that carries keying material and
parameters), do you mean the entire SDP message or can it be restricted
to selected lines of the SDP message?  Will it be possible to share
all needed information in the SDP message *except* the security
descriptions attribute in the SDP message?

>
> >2. Have you considered writing a core specification like RFC 1847 and allow
> >for one or more profiles such as S/MIME (today) and PGP MIME (in the
> >future)?  I understand that S/MIME is the designated SIP solution, but it
> >might be wise to allow for future extensions.
>
>Hmm... in the future, such extensions might be needed.
>However, I have not considered that yet.
>I think there are still more work to use S/MIME practically in SIP.

Yes,  I think so, too.  It is also possible that an X.509 PKI
is found to be not the most deployable solution for global
telephony.  Hence, my point about accommodating different
structures in the future.  Today, there are S/MIME and PGP MIME.
A core specification would enable one to apply what you develop
for one security specification (S/MIME) to others (PGP MIME, etc).
To do this would require one to take out the features of the
e2m and m2m security that are general to all secure multipart
specifications, put these features into one document and then put
the features that are specific to S/MIME in a second document.

Just a thought.  I can understand how this seems less important
in the context of the current SIP specification.  But I am a bit
skeptical about the future of X.509 PKI and expect that other
approaches might be tried in the future.

Regarding S/MIME, do you intend to give a PKI design for the
solution?  That is, who is going to design the PKI that is needed
for e2m security?

I have some more questions on the I-Ds.  I won't list all of them
and won't present them in any particular order.

3. In the requirements document and in your previous I-D, I read that
"it is not appropriate for the UA on the opposite-side to have
knowledge of the public key certificate of the proxy server on
the originating network."  Number 7, p. 7 of the requirements I-D.
Why is the public key protected in this way?

4.  Requirements Number 4 and 5 on p. 7 state that it should allow
a UA to discover which proxy needs to view some data and what they
need to view.  This sounds like it can add a lot of time to call
establishment.  I'm curious to know how this can be done without
a very large number of exchanges taking place prior to establishing
the call.

5. The words "trusted" and "partially trusted" appear in the I-D.
The word "trusted" to me always begs the question "trusted to do
what?"  Since I don't have a clear idea about what you mean by
"trusted," it's hard to tell what you mean by "partially trusted."
Precision is important here.  Have you considered doing an "assets,
risks and threats" analysis on the information to identify the
particular assets in the SIP message, such as caller, callee, SDP
message fields, etc.?  What are the risks to these assets?  And
who might try to gain unauthorized read or write access to them?

regards, Mark

>Thanks a lot,
>
>Kumiko
>
>--
>Kumiko Ono
>NTT Network Service Systems Labs.
>Tel +81 422 59 4508/Fax +81 422 60 4012



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



From exim@www1.ietf.org  Sun Dec  7 23:05:00 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA12437
	for <sipping-archive@odin.ietf.org>; Sun, 7 Dec 2003 23:05:00 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATCda-0002kP-1Q
	for sipping-archive@odin.ietf.org; Sun, 07 Dec 2003 23:04:46 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB844kvk010557
	for sipping-archive@odin.ietf.org; Sun, 7 Dec 2003 23:04:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATCdZ-0002kC-Ua
	for sipping-web-archive@optimus.ietf.org; Sun, 07 Dec 2003 23:04:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA12410
	for <sipping-web-archive@ietf.org>; Sun, 7 Dec 2003 23:04:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATCdW-000415-00
	for sipping-web-archive@ietf.org; Sun, 07 Dec 2003 23:04:42 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATCdV-00040b-00
	for sipping-web-archive@ietf.org; Sun, 07 Dec 2003 23:04:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATCbt-0002cn-Pm; Sun, 07 Dec 2003 23:03:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATCb4-0002cO-Do
	for sipping@optimus.ietf.org; Sun, 07 Dec 2003 23:02:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA12370
	for <sipping@ietf.org>; Sun, 7 Dec 2003 23:01:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATCb0-0003zB-00
	for sipping@ietf.org; Sun, 07 Dec 2003 23:02:06 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATCb0-0003xd-00
	for sipping@ietf.org; Sun, 07 Dec 2003 23:02:06 -0500
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id hB841Yw5005552;
	Sun, 7 Dec 2003 20:01:34 -0800 (PST)
Received: from cisco.com (che-vpn-cluster-2-11.cisco.com [10.86.242.11])
	by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AEM29629;
	Sun, 7 Dec 2003 23:01:33 -0500 (EST)
Message-ID: <3FD3F79D.8030904@cisco.com>
Date: Sun, 07 Dec 2003 23:01:33 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
CC: sipping <sipping@ietf.org>, Adam Roach <adam@dynamicsoft.com>,
        Robert Sparks <rsparks@dynamicsoft.com>
Subject: Re: [Sipping] Exploders anad ad-hoc lists
References: <3FC209FA.6030004@ericsson.com> <3FC4ED22.3040604@cisco.com> <3FD21D7F.7030500@ericsson.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Gonzalo,

I don't have strong opinions either, other than that the choice work 
well. But you didn't answer any of my questions. Maybe if using uri 
parameters is Adam and Robert's idea they can answer them.

	Paul

Gonzalo Camarillo wrote:
> Paul,
> 
> regadring where to place the ad-hoc list, in a URI parameter or in a 
> header, I personally do not have a strong opinion. Nevertheless, I was 
> talking to Adam and Robert, and they said that, based on their 
> experience with the SUBSCRIBE/NOTIFY and the REFER spec, they would 
> rather use a URI parameter.
> 
> Thanks,
> 
> Gonzalo
> 
> Paul Kyzivat wrote:
> 
>> Gonzalo,
>>
>> I like the concept, but I am troubled by passing the reference to the 
>> list as a sip/sips url parameter, for the following reasons:
>>
>> - how does it get there? In your examples, you have the parameter
>>   in the request uri, but not in the To uri. Normally a UA would
>>   determine the destination, and put it in both To and request URIs.
>>   This implies some extra special casing.
>>
>> - How does it stay there. If the address in the request uri is of
>>   an AoR, a proxy may replace it with a corresponding registered
>>   contact. If so, the reference to the list will be lost.
>>
>> - logically the request is being addressed to the service, and the
>>   list is a parameter to the service and the particular method the
>>   service is being asked to perform. Embedding the list in the address
>>   of the service seems inappropriate.
>>
>> I think there needs to be a better place to put the reference to the 
>> list. A new header would seem to be the logical answer.
>>
>> Regarding draft-camarillo-sipping-exploders-solution-00:
>>
>> You say the requester should subscribe to a url returned in the 
>> response to learn the outcome of the exploded requests. But that opens 
>> a time window when some status may lost. Do you have any thoughts on 
>> how to close that? (E.g. the first response to a subscription gives 
>> all the cumulative history of what has happened.)
>>
>> There are a couple of references to an Explode-To header, but no 
>> explanation and no examples. It seems redundant to the list, unless it 
>> is intended as a way to convey the reference to the list.
>>
>>     Paul
>>
>> Gonzalo Camarillo wrote:
>>
>>> Folks,
>>>
>>> we have just submitted three drafts about exploders and ad-hoc lists.
>>>
>>> We have added more requirements to the following draft. The new 
>>> requirements were mainly discussed in the SIMPLE mailing list.
>>>
>>> http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-exploders-01.txt 
>>>
>>>
>>> The following draft describes how to carry lists of URIs in SIP 
>>> requests. It is not a finished draft. It is intended to trigger 
>>> discussions on this topic to see whether this is a step the right 
>>> direction.
>>>
>>> http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-uri-list-00.txt 
>>>
>>>
>>> The following draft defines a new method called EXPLODE. EXPLODE does 
>>> the same as REFER. That is, it tells a UA to send a request 
>>> somewhere. The differences are that EXPLODE accepts more than one 
>>> destination (REFER carries a single Refer-To header field) and that 
>>> EXPLODE does not establish implicit subscriptions of any type. This 
>>> draft is also intended to trigger discussions within the WG.
>>>
>>> http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-explode-method-00.txt 
>>>
>>>
>>> Let's try to keep discussions about this topic in the SIPPING mailing 
>>> list. I will forward this mail to the SIMPLE mailing list to let them 
>>> know.
>>>
>>> Comments are welcome,
>>>
>>> Gonzalo
>>>
>>>
>>>
>>> _______________________________________________
>>> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>> This list is for NEW development of the application of SIP
>>> Use sip-implementors@cs.columbia.edu for questions on current sip
>>> Use sip@ietf.org for new developments of core SIP
>>>
> 


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



From exim@www1.ietf.org  Mon Dec  8 08:37:30 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09038
	for <sipping-archive@odin.ietf.org>; Mon, 8 Dec 2003 08:37:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATLZa-0006Lr-Hu
	for sipping-archive@odin.ietf.org; Mon, 08 Dec 2003 08:37:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB8DbEov024406
	for sipping-archive@odin.ietf.org; Mon, 8 Dec 2003 08:37:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATLZZ-0006J1-52
	for sipping-web-archive@optimus.ietf.org; Mon, 08 Dec 2003 08:37:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09015
	for <sipping-web-archive@ietf.org>; Mon, 8 Dec 2003 08:36:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATLZX-0003eE-00
	for sipping-web-archive@ietf.org; Mon, 08 Dec 2003 08:37:11 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATLZX-0003eB-00
	for sipping-web-archive@ietf.org; Mon, 08 Dec 2003 08:37:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATLZN-0006EP-JP; Mon, 08 Dec 2003 08:37:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATLYi-0006Do-Hb
	for sipping@optimus.ietf.org; Mon, 08 Dec 2003 08:36:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08990
	for <sipping@ietf.org>; Mon, 8 Dec 2003 08:36:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATLYg-0003d5-00
	for sipping@ietf.org; Mon, 08 Dec 2003 08:36:18 -0500
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATLYg-0003d2-00
	for sipping@ietf.org; Mon, 08 Dec 2003 08:36:18 -0500
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id hB8DaG225716;
	Mon, 8 Dec 2003 14:36:16 +0100 (MET)
Received: from moody.mchh.siemens.de (moody.mchh.siemens.de [139.21.205.85])
	by mail3.siemens.de (8.11.7/8.11.7) with ESMTP id hB8DaFj14310;
	Mon, 8 Dec 2003 14:36:15 +0100 (MET)
Received: from mchh248e.mchh.siemens.de (mchh248e.mchh.siemens.de [139.21.200.58])
	by moody.mchh.siemens.de (8.9.3/8.9.1) with ESMTP id OAA04409;
	Mon, 8 Dec 2003 14:36:15 +0100 (MET)
Received: by mchh248e.mchh.siemens.de with Internet Mail Service (5.5.2653.19)
	id <XZKP3JL9>; Mon, 8 Dec 2003 14:36:14 +0100
Message-ID: <79D5F4B2D775204D9C7852EE41C54773028D2F39@mchh2a1e.mchh.siemens.de>
From: Milinski Alexander <alexander.milinski@siemens.com>
To: "'Karim.el-malki@ericsson.com'" <Karim.el-malki@ericsson.com>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Date: Mon, 8 Dec 2003 14:36:12 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [Sipping] Question on draft-elmalki-sipping-3gpp-translator-00.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Hello Karim, 
can you please summarise the changes in draft-elmalki-sipping-3gpp-translator-00.txt compared to draft-elmalki-v6ops-3gpp-translator-00.txt?
Thanks,
Alexander

Alexander Milinski
Siemens

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



From exim@www1.ietf.org  Mon Dec  8 09:34:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10650
	for <sipping-archive@odin.ietf.org>; Mon, 8 Dec 2003 09:34:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATMSe-0008Mn-5o
	for sipping-archive@odin.ietf.org; Mon, 08 Dec 2003 09:34:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB8EY8i8032155
	for sipping-archive@odin.ietf.org; Mon, 8 Dec 2003 09:34:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATMSe-0008MY-2H
	for sipping-web-archive@optimus.ietf.org; Mon, 08 Dec 2003 09:34:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10636
	for <sipping-web-archive@ietf.org>; Mon, 8 Dec 2003 09:33:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATMSc-0004sV-00
	for sipping-web-archive@ietf.org; Mon, 08 Dec 2003 09:34:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATMSb-0004sS-00
	for sipping-web-archive@ietf.org; Mon, 08 Dec 2003 09:34:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATMSX-0008LR-EJ; Mon, 08 Dec 2003 09:34:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATMRk-0008Kq-CO
	for sipping@optimus.ietf.org; Mon, 08 Dec 2003 09:33:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10626
	for <sipping@ietf.org>; Mon, 8 Dec 2003 09:32:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATMRh-0004s6-00
	for sipping@ietf.org; Mon, 08 Dec 2003 09:33:09 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATMRg-0004rj-00
	for sipping@ietf.org; Mon, 08 Dec 2003 09:33:08 -0500
Received: from sj-core-3.cisco.com (171.68.223.137)
  by sj-iport-5.cisco.com with ESMTP; 08 Dec 2003 14:33:18 +0000
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id hB8EWZrX010935;
	Mon, 8 Dec 2003 06:32:35 -0800 (PST)
Received: from cisco.com ([161.44.79.239])
	by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AEM44665;
	Mon, 8 Dec 2003 09:32:33 -0500 (EST)
Message-ID: <3FD48B80.1030800@cisco.com>
Date: Mon, 08 Dec 2003 09:32:32 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Marjou Xavier <xavier.marjou@siemens.com>
CC: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: Re: [Sipping] Exploders and ad-hoc lists
References: <5B788FC2CAFBD6118BAE0030848B025C7A21C3@LNN201E>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Xavier,

Depending on circumstance and preference, it is ok for the subscription 
to either share the dialog with the invite or create a new one.

Circumstances that may affect the decision:
- if the contact from the invite is not globally routable,
   then reusing the dialog will be successful while
   attempting to establish a new one may not be.
- if the contact is globally routable, (see GRUU proposal)
   then either way should work.
- there may be some slight efficiency to reusing a dialog
- there may be some UAs that don't support dialog sharing

If everybody is fully compliant to all the rules, then the contact will 
be globally routable, and dialog sharing will be supported, so that 
either choice is ok. If one end or the other isn't fully compliant, then 
one or the other may be preferable, but there is no general way to tell 
which one is most likely to work.

	Paul

Marjou Xavier wrote:
> Hi,
> 
> In draft-camarillo-sipping-uri-list-00.txt, it is written that:
> "The conference server responds with a 200 (OK) that carries the URI for the conference in its Contact header field. If the UA wants to obtain information about the status of the conference, for instance, it will SUBSCRIBE to the conference package using this URI."
> 
> Will the SUBSCRIBE be sent in the dialog of the INVITE, or will it create its own dialog?
> 
> Regards,
> Xavier
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 


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



From exim@www1.ietf.org  Mon Dec  8 13:01:25 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21349
	for <sipping-archive@odin.ietf.org>; Mon, 8 Dec 2003 13:01:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATPh2-0003Ri-1P
	for sipping-archive@odin.ietf.org; Mon, 08 Dec 2003 13:01:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB8I1BgM013240
	for sipping-archive@odin.ietf.org; Mon, 8 Dec 2003 13:01:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATPh1-0003RT-SQ
	for sipping-web-archive@optimus.ietf.org; Mon, 08 Dec 2003 13:01:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21311
	for <sipping-web-archive@ietf.org>; Mon, 8 Dec 2003 13:00:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATPh0-0001Wi-00
	for sipping-web-archive@ietf.org; Mon, 08 Dec 2003 13:01:10 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATPgz-0001Wf-00
	for sipping-web-archive@ietf.org; Mon, 08 Dec 2003 13:01:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATPgt-0003NV-HC; Mon, 08 Dec 2003 13:01:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATPgM-0003LO-DH
	for sipping@optimus.ietf.org; Mon, 08 Dec 2003 13:00:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21252
	for <sipping@ietf.org>; Mon, 8 Dec 2003 13:00:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATPgK-0001V7-00
	for sipping@ietf.org; Mon, 08 Dec 2003 13:00:28 -0500
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATPgJ-0001V4-00
	for sipping@ietf.org; Mon, 08 Dec 2003 13:00:28 -0500
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118])
	by penguin-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8) with ESMTP id hB8I0PSs012877;
	Mon, 8 Dec 2003 19:00:26 +0100 (MET)
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <XW62FJ3N>; Mon, 8 Dec 2003 19:00:25 +0100
Message-ID: <37FB7AA6F5F9814FB634A7BF4C35A6F563999C@ESEALNT442.al.sw.ericsson.se>
From: "Karim El-Malki (HF/EAB)" <karim.el-malki@ericsson.com>
To: "'Milinski Alexander'" <alexander.milinski@siemens.com>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>
Date: Mon, 8 Dec 2003 18:59:40 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sipping] RE: Question on draft-elmalki-sipping-3gpp-translator-00.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

Hi

Most changes were to clarify the text so the basic usage of
ICE, ALT and session policies hasn't changed.
Main changes:
- simple mechanism added for the source address mapping of
STUN messages in 4.5.2
- added message diagrams
- added new text to clarify usage of session policies
- several editorials to improve text
- removed non-IMS section 5

/Karim

 > -----Original Message-----
 > From: Milinski Alexander [mailto:alexander.milinski@siemens.com]
 > Sent: den 8 december 2003 14:36
 > To: Karim El-Malki (HF/EAB)
 > Cc: 'sipping@ietf.org'
 > Subject: Question on draft-elmalki-sipping-3gpp-translator-00.txt
 > 
 > 
 > Hello Karim, 
 > can you please summarise the changes in 
 > draft-elmalki-sipping-3gpp-translator-00.txt compared to 
 > draft-elmalki-v6ops-3gpp-translator-00.txt?
 > Thanks,
 > Alexander
 > 
 > Alexander Milinski
 > Siemens
 > 

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



From exim@www1.ietf.org  Mon Dec  8 15:41:33 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01052
	for <sipping-archive@odin.ietf.org>; Mon, 8 Dec 2003 15:41:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATSBy-0004HX-9g
	for sipping-archive@odin.ietf.org; Mon, 08 Dec 2003 15:41:18 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB8KfIJG016453
	for sipping-archive@odin.ietf.org; Mon, 8 Dec 2003 15:41:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATSBx-0004HH-Jd
	for sipping-web-archive@optimus.ietf.org; Mon, 08 Dec 2003 15:41:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01007
	for <sipping-web-archive@ietf.org>; Mon, 8 Dec 2003 15:41:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATSBw-0004pb-00
	for sipping-web-archive@ietf.org; Mon, 08 Dec 2003 15:41:16 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATSBv-0004pY-00
	for sipping-web-archive@ietf.org; Mon, 08 Dec 2003 15:41:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATSBl-0004FF-OA; Mon, 08 Dec 2003 15:41:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATSAw-0004DR-3T
	for sipping@optimus.ietf.org; Mon, 08 Dec 2003 15:40:14 -0500
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00902
	for <sipping@odin.ietf.org>; Mon, 8 Dec 2003 15:39:58 -0500 (EST)
Received: from apache by asgard.ietf.org with local (Exim 4.14)
	id 1ATS3G-0007uv-TC; Mon, 08 Dec 2003 15:32:18 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Cc: Internet Architecture Board <iab@iab.org>,
        RFC Editor <rfc-editor@rfc-editor.org>, <sipping@ietf.org>
Message-Id: <E1ATS3G-0007uv-TC@asgard.ietf.org>
Date: Mon, 08 Dec 2003 15:32:18 -0500
Subject: [Sipping] Document Action: 'Using E.164 numbers with the Session
 Initiation Protocol (SIP)' to Informational RFC
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>

The IESG has approved following document:

- 'Using E.164 numbers with the Session Initiation Protocol (SIP) '
   <draft-ietf-sipping-e164-04.txt> as an Informational RFC

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

The IESG contact persons are Allison Mankin and Jon Peterson.

RFC Editor Note

Add to the end of the Security Considerations:

  An analysis of threats specific to the dependence of ENUM on
  the DNS, and the applicability of DNSSEC [##] to these, is
  provided in [1].

Append to the Informative References:

[##]  R. Arends, et al, Protocol Modifications for the DNS Security
         Extensions, draft-ietf-dnsext-dnssec-protocol-03.txt


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



From exim@www1.ietf.org  Mon Dec  8 19:50:07 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16394
	for <sipping-archive@odin.ietf.org>; Mon, 8 Dec 2003 19:50:07 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATW4V-0006lZ-4l
	for sipping-archive@odin.ietf.org; Mon, 08 Dec 2003 19:49:51 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB90npUT026004
	for sipping-archive@odin.ietf.org; Mon, 8 Dec 2003 19:49:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATW4V-0006lL-1B
	for sipping-web-archive@optimus.ietf.org; Mon, 08 Dec 2003 19:49:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16278
	for <sipping-web-archive@ietf.org>; Mon, 8 Dec 2003 19:49:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATW4T-0003C4-00
	for sipping-web-archive@ietf.org; Mon, 08 Dec 2003 19:49:49 -0500
Received: from manatick.foretec.com ([4.17.168.5] helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATW4S-0003Bk-00
	for sipping-web-archive@ietf.org; Mon, 08 Dec 2003 19:49:48 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org)
	by manatick with esmtp (Exim 4.24)
	id 1ATW2z-0001aY-5O
	for sipping-web-archive@ietf.org; Mon, 08 Dec 2003 19:48:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATW2j-0006aZ-1j; Mon, 08 Dec 2003 19:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATW2d-0006a5-U0
	for sipping@optimus.ietf.org; Mon, 08 Dec 2003 19:47:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16191
	for <sipping@ietf.org>; Mon, 8 Dec 2003 19:47:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATW2P-00039b-00
	for sipping@ietf.org; Mon, 08 Dec 2003 19:47:41 -0500
Received: from mail3.microsoft.com ([131.107.3.123])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATW2P-000391-00
	for sipping@ietf.org; Mon, 08 Dec 2003 19:47:41 -0500
Received: from INET-VRS-03.redmond.corp.microsoft.com ([157.54.5.27]) by mail3.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 8 Dec 2003 16:47:04 -0800
Received: from 157.54.8.23 by INET-VRS-03.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 08 Dec 2003 16:46:34 -0800
Received: from RED-MSG-52.redmond.corp.microsoft.com ([157.54.12.12]) by inet-hub-01.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 8 Dec 2003 16:48:20 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Exploders anad ad-hoc lists
Date: Mon, 8 Dec 2003 16:47:06 -0800
Message-ID: <DD07841287D0AD428833021705E0D14EEBB14A@RED-MSG-52.redmond.corp.microsoft.com>
Thread-Topic: [Sipping] Exploders anad ad-hoc lists
Thread-Index: AcO8JnMGlEj1caKJQY+wUEcMp7sASABxHUcg
From: "Orit Levin" <oritl@microsoft.com>
To: "Gonzalo Camarillo" <Gonzalo.Camarillo@ericsson.com>, <sipping@ietf.org>
Cc: "Adam Roach" <adam@dynamicsoft.com>, <Aki.Niemi@nokia.com>,
        <Hisham.Khartabil@nokia.com>, <Markus.Isomaki@nokia.com>
X-OriginalArrivalTime: 09 Dec 2003 00:48:20.0766 (UTC) FILETIME=[246F83E0:01C3BDEE]
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable


Do you mean providing a kind of "operation" definition such as in
draft-levin-simple-adhoc-list-01.txt?

       <xs:element name=3D"adhoclist">
          <xs:complexType>

            <xs:sequence>
              <xs:element name=3D"delete" type=3D"roster" =
minOccurs=3D"0"
maxOccurs=3D"1"/>
              <xs:element name=3D"create" type=3D"roster" =
minOccurs=3D"0"
maxOccurs=3D"1"/>
              <xs:element name=3D"add"    type=3D"roster" =
minOccurs=3D"0"
maxOccurs=3D"1"/>
              <xs:any     minOccurs=3D"0" maxOccurs=3D"unbounded" />
            </xs:sequence>

            <xs:attribute name=3D"uri" type=3D"xs:anyURI" =
use=3D"required" />
            <xs:attribute name=3D"name" type=3D"xs:string" =
use=3D"required" />
            <xs:anyAttribute />
          </xs:complexType>
        </xs:element>

Here "roster" stands for "resources-list".=20

If yes, I would suggest adding this definition to the
"camarillo-sipping-uri-list" draft (as MMIME or as a part of a single
XML schema) in order to standardise on it ASAP. Then I will be able to
update my draft with just a pointer to the Sipping draft. When are you
planning to submit the next version?

Also, could you, please, emphasize that the "Examples" section is
informative only because the application-specific behavior details need
to be defined in SIMPLE and cc-conferencing drafts.

Thanks a lot,
Orit.=20


-----Original Message-----
From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com]=20
Sent: Saturday, December 06, 2003 10:24 AM
To: Orit Levin
Cc: sipping; Adam Roach; Aki.Niemi@nokia.com;
Hisham.Khartabil@nokia.com; Markus.Isomaki@nokia.com
Subject: Re: [Sipping] Exploders anad ad-hoc lists

Orit,

> 1. How do you propose sending the deltas? (Consistently with the=20
> updated requirements' draft.)

The idea would be to send them as a URI parameter of a subsequent
request. Which request to use would depend on the application you are
implementing. For example, for ad-hoc presence, the natural choice would
be a SUBSCRIBE.

Regarding how to indicate that what you are sending is a delta rather
than a full list, it should be handled by the XML definition of the
list.

Gonzalo





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



From exim@www1.ietf.org  Mon Dec  8 19:56:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16727
	for <sipping-archive@odin.ietf.org>; Mon, 8 Dec 2003 19:56:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATWAY-00074D-H9
	for sipping-archive@odin.ietf.org; Mon, 08 Dec 2003 19:56:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB90u6MP027159
	for sipping-archive@odin.ietf.org; Mon, 8 Dec 2003 19:56:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATWAY-00073y-DU
	for sipping-web-archive@optimus.ietf.org; Mon, 08 Dec 2003 19:56:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16705
	for <sipping-web-archive@ietf.org>; Mon, 8 Dec 2003 19:55:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATWAW-0003M4-00
	for sipping-web-archive@ietf.org; Mon, 08 Dec 2003 19:56:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATWAW-0003M1-00
	for sipping-web-archive@ietf.org; Mon, 08 Dec 2003 19:56:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATWAU-00072W-GX; Mon, 08 Dec 2003 19:56:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATWAN-00071w-F1
	for sipping@optimus.ietf.org; Mon, 08 Dec 2003 19:55:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16684;
	Mon, 8 Dec 2003 19:55:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATWAK-0003Ls-00; Mon, 08 Dec 2003 19:55:52 -0500
Received: from pine.neustar.com ([209.173.57.70])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATWAK-0003LV-00; Mon, 08 Dec 2003 19:55:52 -0500
Received: from chiimc01.npac.com (chiimc01.neustar.com [10.32.90.4])
	by pine.neustar.com (8.12.8/8.11.0) with ESMTP id hB90seb9030155;
	Tue, 9 Dec 2003 00:54:40 GMT
Received: by CHIIMC01 with Internet Mail Service (5.5.2653.19)
	id <VDKHLYXX>; Mon, 8 Dec 2003 18:54:45 -0600
Message-ID: <A9DECB0B8A01A54DBECC03B25D29513CD564E8@stntexch03.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Mark Baugher'" <mbaugher@cisco.com>,
        Kumiko Ono
	 <ono.kumiko@lab.ntt.co.jp>
Cc: mary.barnes@nortelnetworks.com, tachimoto.shinya@lab.ntt.co.jp,
        sipping@ietf.org, mmusic@ietf.org, cyrus@ntt-at.com,
        fandreas@cisco.com, dwing@cisco.com
Date: Mon, 8 Dec 2003 18:54:34 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Sipping] RE: [MMUSIC] Re: e2m, m2m security drafts
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>


A couple of notes on all this.

> Thanks.  One more clarification, please.  By "encrypted data" (which in
> my case is the SDP crypto attribute that carries keying material and
> parameters), do you mean the entire SDP message or can it be restricted
> to selected lines of the SDP message?  Will it be possible to share
> all needed information in the SDP message *except* the security
> descriptions attribute in the SDP message?

Today, we don't really have a way in SIP to encrypt only part of an SDP
message - a requirement for partial encryption has never really been fully
articulated or understood. I imagine that any such requirement would be
satisfied by splitting an SDP body into different MIME components to which
separate security properties would be applied.

I understand why you'd think that sdescriptions should be end-to-end, since
they are only for the consumption of endpoints that aspire to use sRTP, or
something similar. But I'm not sure that we should grant keying material for
sRTP a specific exemption from the principles underlying the e2m work.
Unfortunately, I suspect that operators are as likely to want a degree of
control over the use of e2e media encryption as they are to want to munge
anything else in SDP.

[snip]
> 
> It is also possible that an X.509 PKI
> is found to be not the most deployable solution for global
> telephony.  Hence, my point about accommodating different
> structures in the future.  Today, there are S/MIME and PGP MIME.

I doubt that PGP MIME is any more 'deployable' than PKI, unfortunately. The
original version of the SIP standard (RFC2543) contained some PGP-related
text, and it was not included in subsequent revisions for a number of
reasons. But certainly it's very unlikely that we'll get any closer to
interoperable end-to-end security by introducing more alternatives for e2e
security in SIP. Giving implementers a choice between S/MIME and PGP MIME
is, in fact, guaranteed to get us farther from our goal.

It is also important to note that support for S/MIME does not directly
entail the use of X.509. There are a number of specifications (notably
RFC3211) that define symmetric key schemes usable by S/MIME in place of
X.509. Self-signed certificates are also meaningful for S/MIME - in fact,
there's a great deal of text in RFC3261 (notably in Section 23.1/23.2)
dedicated to exchanging self-signed certs.

> A core specification would enable one to apply what you develop
> for one security specification (S/MIME) to others (PGP MIME, etc).
> To do this would require one to take out the features of the
> e2m and m2m security that are general to all secure multipart
> specifications, put these features into one document and then put
> the features that are specific to S/MIME in a second document.

I agree that the e2m work is not the right place to explore whether or not
we should introduce new options for e2e security in SIP. That is a core SIP
issue, and not something that should be considered solely in light of the
e2m requirements. That much said, I do not advocate reopening the underlying
principles of MIME security for SIP. I think the e2m work should focus on
the existing security mechanisms that have been established for SIP in
RFC3261, and should not complicate itself by creating modularities that
depend on the (speculative) use of other MIME security systems.

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 exim@www1.ietf.org  Mon Dec  8 22:58:05 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24903
	for <sipping-archive@odin.ietf.org>; Mon, 8 Dec 2003 22:58:05 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATZ0Q-0005nU-1V
	for sipping-archive@odin.ietf.org; Mon, 08 Dec 2003 22:57:52 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB93voGp022280
	for sipping-archive@odin.ietf.org; Mon, 8 Dec 2003 22:57:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATZ0P-0005nH-Tg
	for sipping-web-archive@optimus.ietf.org; Mon, 08 Dec 2003 22:57:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24810
	for <sipping-web-archive@ietf.org>; Mon, 8 Dec 2003 22:57:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATZ0M-0006nN-00
	for sipping-web-archive@ietf.org; Mon, 08 Dec 2003 22:57:46 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATZ0L-0006nJ-00
	for sipping-web-archive@ietf.org; Mon, 08 Dec 2003 22:57:45 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATYzd-0005fY-5p; Mon, 08 Dec 2003 22:57:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATYzI-0005fB-H5
	for sipping@optimus.ietf.org; Mon, 08 Dec 2003 22:56:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24717
	for <sipping@ietf.org>; Mon, 8 Dec 2003 22:56:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATYzE-0006kl-00
	for sipping@ietf.org; Mon, 08 Dec 2003 22:56:36 -0500
Received: from tama5.ecl.ntt.co.jp ([129.60.39.102])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATYzD-0006kg-00
	for sipping@ietf.org; Mon, 08 Dec 2003 22:56:36 -0500
Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110])
	by tama5.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id hB93toUC012653;
	Tue, 9 Dec 2003 12:55:50 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp (localhost [127.0.0.1])
	by vcs3.rdh.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id hB93topo029316;
	Tue, 9 Dec 2003 12:55:50 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp [129.60.5.69])
	by nttmail3.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id hB93tn8H021940;
	Tue, 9 Dec 2003 12:55:49 +0900 (JST)
Received: from img.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan3.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with ESMTP id MAA10676;
	Tue, 9 Dec 2003 12:55:48 +0900 (JST)
Received: from lab.ntt.co.jp
	by img.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with SMTP id MAA25724;
	Tue, 9 Dec 2003 12:55:48 +0900 (JST)
Date: Tue, 09 Dec 2003 12:55:45 +0900
From: Kumiko Ono <ono.kumiko@lab.ntt.co.jp>
Subject: Re: [Sipping] Re: e2m, m2m security drafts
To: Mark Baugher <mbaugher@cisco.com>
Cc: mary.barnes@nortelnetworks.com, tachimoto.shinya@lab.ntt.co.jp,
        sipping@ietf.org, cyrus@ntt-at.com, fandreas@cisco.com,
        dwing@cisco.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: TuruKame 3.07beta6 (WinNT,501)
In-Reply-To: <6.0.0.22.2.20031201163158.03cb0a28@mira-sjc5-6.cisco.com>
References: <6.0.0.22.2.20031201163158.03cb0a28@mira-sjc5-6.cisco.com>
Message-Id: <89C3BE0852ABBBono.kumiko@lab.ntt.co.jp>
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Mark,

You don't have to add -san when you call me. :-)

[snip]
>> Thanks.  One more clarification, please.  By "encrypted data" (which in
>> my case is the SDP crypto attribute that carries keying material and
>> parameters), do you mean the entire SDP message or can it be restricted
>> to selected lines of the SDP message?  Will it be possible to share
>> all needed information in the SDP message *except* the security
>> descriptions attribute in the SDP message?

The "encrypted data" is not restricted to the entire SDP message or a 
subset of the SDP message. It depends on the use case. 
In your case, you could set two encrypted SDP in a SIP message: 
one contains keying parameters for SRTP and is encrypted only to a UAS, 
and another doesn't contain them and is encrypted to a selected proxy.

[snip]
>> Yes,  I think so, too.  It is also possible that an X.509 PKI
>> is found to be not the most deployable solution for global
>> telephony.  Hence, my point about accommodating different
>> structures in the future.  Today, there are S/MIME and PGP MIME.
>> A core specification would enable one to apply what you develop
>> for one security specification (S/MIME) to others (PGP MIME, etc).
>> To do this would require one to take out the features of the
>> e2m and m2m security that are general to all secure multipart
>> specifications, put these features into one document and then put
>> the features that are specific to S/MIME in a second document.
>>
>> Just a thought.  I can understand how this seems less important
>> in the context of the current SIP specification.  But I am a bit
>> skeptical about the future of X.509 PKI and expect that other
>> approaches might be tried in the future.
>>
>> Regarding S/MIME, do you intend to give a PKI design for the
>> solution?  That is, who is going to design the PKI that is needed
>> for e2m security?

I don't think that a special PKI design to e2m security is needed. 
So, the PKI design is out of scope, but there is a lot of other work 
going on in the IETF on PKI. Also, non-PKI solutions for S/MIME or CMS 
are being proposed as well.

[snip]
>> 3. In the requirements document and in your previous I-D, I read that
>> "it is not appropriate for the UA on the opposite-side to have
>> knowledge of the public key certificate of the proxy server on
>> the originating network."  Number 7, p. 7 of the requirements I-D.
>> Why is the public key protected in this way?

It does not mean that the PKC of the proxy needs to be protected. 

The UA on the opposite-side does not usually know the PKC of the proxy 
on the origination network. It is not a valid assumption for the UA on 
the opposite-side to need to know the PKC of the proxy.

If a SIP response message carries some data to be shared with the proxy 
on the originating network, the UAS would need to encrypt the data for 
the proxy. There are two ways to encrypt the data for proxy: one is to 
use the PKC of the proxy, and the other is to reuse the  CEK of the 
request message. In the former way, the UAS needs to get the PKC of the 
proxy in some way and to validate the PKC. The latter way is simpler. 
Therefore, it is better for the UAS to encrypt the response message to 
the proxy without the PKC of the proxy.

To clafiry this requirement, I would say that "It SHOULD enable  the UA 
on the opposite-side to encrypt some data in a response message to the 
proxy on the originating network without using the PKC of the proxy."

>> 4.  Requirements Number 4 and 5 on p. 7 state that it should allow
>> a UA to discover which proxy needs to view some data and what they
>> need to view.  This sounds like it can add a lot of time to call
>> establishment.  I'm curious to know how this can be done without
>> a very large number of exchanges taking place prior to establishing
>> the call.

The discovery mechanism will be similar to the challenge-response 
authentication, or an event package mechanism. 
With a similar mechanism to the challenge-response, it will take 
additional three messages per a proxy. These additional messages are not 
always required. If a UA has already known the disclosure requirement of 
the proxies, the UA does not need these additional messages.

>> 5. The words "trusted" and "partially trusted" appear in the I-D.
>> The word "trusted" to me always begs the question "trusted to do
>> what?"  Since I don't have a clear idea about what you mean by
>> "trusted," it's hard to tell what you mean by "partially trusted."
>> Precision is important here.  Have you considered doing an "assets,
>> risks and threats" analysis on the information to identify the
>> particular assets in the SIP message, such as caller, callee, SDP
>> message fields, etc.?  What are the risks to these assets?  And
>> who might try to gain unauthorized read or write access to them?

Good comments. I have to clafiry the words and describe security threat 
models.

I meant that a "partially trusted proxy" is a proxy that a UA 
trusts to view *only routing-related* SIP headers in a SIP message 
in order to forward the message.

A "trusted proxy" is a proxy that a UA trusts to view *all* the 
information ,or *a part* of the information besides routing-related 
SIP headers in a SIP message in order to provide some features.

Regarding SDP message fields, you know, there are several risks to 
disclose them.
Using TLS in all hops, the risks could  be restricted to all the proxies 
in a request path. Some proxies might need to view RTP port numbers to 
control a firewall, and other malicious proxies might monitor/log media 
streams without notice.

Thanks a lot,

Kumiko

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


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



From exim@www1.ietf.org  Tue Dec  9 00:59:17 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29047
	for <sipping-archive@odin.ietf.org>; Tue, 9 Dec 2003 00:59:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATatk-0001Bl-NA
	for sipping-archive@odin.ietf.org; Tue, 09 Dec 2003 00:59:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB95x4SN004570
	for sipping-archive@odin.ietf.org; Tue, 9 Dec 2003 00:59:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATatk-0001Bd-Jw
	for sipping-web-archive@optimus.ietf.org; Tue, 09 Dec 2003 00:59:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29041
	for <sipping-web-archive@ietf.org>; Tue, 9 Dec 2003 00:58:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATath-00011l-00
	for sipping-web-archive@ietf.org; Tue, 09 Dec 2003 00:59:01 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATatg-00011h-00
	for sipping-web-archive@ietf.org; Tue, 09 Dec 2003 00:59:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATatg-0001AU-KG; Tue, 09 Dec 2003 00:59:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATatU-00019a-B3
	for sipping@optimus.ietf.org; Tue, 09 Dec 2003 00:58:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29032
	for <sipping@ietf.org>; Tue, 9 Dec 2003 00:58:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATatR-00011Y-00
	for sipping@ietf.org; Tue, 09 Dec 2003 00:58:45 -0500
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATatQ-00011B-00
	for sipping@ietf.org; Tue, 09 Dec 2003 00:58:45 -0500
Received: from dynamicsoft.com (dyn-tx-app-004.dfw.dynamicsoft.com [63.110.3.2])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id hB95wBca001897;
	Tue, 9 Dec 2003 00:58:12 -0500 (EST)
Message-ID: <3FD56469.8050605@dynamicsoft.com>
Date: Tue, 09 Dec 2003 00:58:01 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
CC: Marjou Xavier <xavier.marjou@siemens.com>,
        "'sipping@ietf.org'" <sipping@ietf.org>
Subject: Re: [Sipping] Exploders and ad-hoc lists
References: <5B788FC2CAFBD6118BAE0030848B025C7A21C3@LNN201E> <3FD48B80.1030800@cisco.com>
In-Reply-To: <3FD48B80.1030800@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



Paul Kyzivat wrote:

> Xavier,
> 
> Depending on circumstance and preference, it is ok for the subscription 
> to either share the dialog with the invite or create a new one.
> 
> Circumstances that may affect the decision:
> - if the contact from the invite is not globally routable,
>   then reusing the dialog will be successful while
>   attempting to establish a new one may not be.
> - if the contact is globally routable, (see GRUU proposal)
>   then either way should work.
> - there may be some slight efficiency to reusing a dialog
> - there may be some UAs that don't support dialog sharing
> 
> If everybody is fully compliant to all the rules, then the contact will 
> be globally routable, and dialog sharing will be supported, so that 
> either choice is ok. If one end or the other isn't fully compliant, then 
> one or the other may be preferable, but there is no general way to tell 
> which one is most likely to work.

You are mixing two cases - one case where the UA doesn't support a 
feature mandated by 3261 (dialog sharing), and the other, where it 
doesnt support an extension (gruu). Dealing with the first one of 
these is generally hard, and not something we can really address. 
However, dealing with the second case is easy. If the peer UA 
indicated support for GRUU (from the presence of the Supported: gruu 
header field), send the subscribe in a new dialog. Otherwise, reuse 
the dialog.

-Jonathan R.



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


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



From exim@www1.ietf.org  Tue Dec  9 03:24:27 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16970
	for <sipping-archive@odin.ietf.org>; Tue, 9 Dec 2003 03:24:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATdAB-0001n1-2d
	for sipping-archive@odin.ietf.org; Tue, 09 Dec 2003 03:24:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB98OBC0006878
	for sipping-archive@odin.ietf.org; Tue, 9 Dec 2003 03:24:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATdA9-0001mm-Sa
	for sipping-web-archive@optimus.ietf.org; Tue, 09 Dec 2003 03:24:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16961
	for <sipping-web-archive@ietf.org>; Tue, 9 Dec 2003 03:23:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATdA7-0003Jc-00
	for sipping-web-archive@ietf.org; Tue, 09 Dec 2003 03:24:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATdA6-0003JV-00
	for sipping-web-archive@ietf.org; Tue, 09 Dec 2003 03:24:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATdA2-0001k6-24; Tue, 09 Dec 2003 03:24:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATd9B-0001gv-OM
	for sipping@optimus.ietf.org; Tue, 09 Dec 2003 03:23:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16792
	for <sipping@ietf.org>; Tue, 9 Dec 2003 03:22:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATd99-0003Go-00
	for sipping@ietf.org; Tue, 09 Dec 2003 03:23:07 -0500
Received: from tama5.ecl.ntt.co.jp ([129.60.39.102])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATd96-0003Fk-00
	for sipping@ietf.org; Tue, 09 Dec 2003 03:23:04 -0500
Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110])
	by tama5.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id hB98MDUC011397;
	Tue, 9 Dec 2003 17:22:13 +0900 (JST)
Received: from nttmail3.ecl.ntt.co.jp (localhost [127.0.0.1])
	by vcs3.rdh.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id hB98MDpo019020;
	Tue, 9 Dec 2003 17:22:13 +0900 (JST)
Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp [129.60.5.69])
	by nttmail3.ecl.ntt.co.jp (8.12.8p1/8.12.8) with ESMTP id hB98MC8H017029;
	Tue, 9 Dec 2003 17:22:12 +0900 (JST)
Received: from img.m.ecl.ntt.co.jp (localhost [127.0.0.1])
	by eclscan3.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with ESMTP id RAA05778;
	Tue, 9 Dec 2003 17:22:12 +0900 (JST)
Received: from lab.ntt.co.jp
	by img.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with SMTP id RAA20591;
	Tue, 9 Dec 2003 17:22:11 +0900 (JST)
Date: Tue, 09 Dec 2003 17:22:08 +0900
From: Kumiko Ono <ono.kumiko@lab.ntt.co.jp>
Subject: Re: [Sipping] RE: [MMUSIC] Re: e2m, m2m security drafts
To: "Peterson, Jon" <jon.peterson@neustar.biz>,
        "'Mark Baugher'" <mbaugher@cisco.com>
Cc: mary.barnes@nortelnetworks.com, tachimoto.shinya@lab.ntt.co.jp,
        sipping@ietf.org, cyrus@ntt-at.com, fandreas@cisco.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: TuruKame 3.07beta6 (WinNT,501)
In-Reply-To: <A9DECB0B8A01A54DBECC03B25D29513CD564E8@stntexch03.va.neustar.com>
References: <A9DECB0B8A01A54DBECC03B25D29513CD564E8@stntexch03.va.neustar.com>
Message-Id: <90C3BE2D893A9Aono.kumiko@lab.ntt.co.jp>
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Jon,

I agree with your comments for the scope.
See inline.

# I am not sending this mail to the mmusic ML to avoid cross posting.

>A couple of notes on all this.
>
>> Thanks.  One more clarification, please.  By "encrypted data" (which in
>> my case is the SDP crypto attribute that carries keying material and
>> parameters), do you mean the entire SDP message or can it be restricted
>> to selected lines of the SDP message?  Will it be possible to share
>> all needed information in the SDP message *except* the security
>> descriptions attribute in the SDP message?
>
>Today, we don't really have a way in SIP to encrypt only part of an SDP
>message - a requirement for partial encryption has never really been fully
>articulated or understood. I imagine that any such requirement would be
>satisfied by splitting an SDP body into different MIME components to which
>separate security properties would be applied.

We don't have a Content-Type that indicates only part of an SDP message.
Is that the reason why you said that we don't have a way in SIP to 
encrypt only part of an SDP?

I want to note that the e2m work is applied not only for SDP, but also 
for some SIP headers or some XML data, such as message contents or 
location data.

Thanks a lot,

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

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



From exim@www1.ietf.org  Fri Dec 12 03:57:33 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01638
	for <sipping-archive@odin.ietf.org>; Fri, 12 Dec 2003 03:57:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUj6e-0008N7-UF
	for sipping-archive@odin.ietf.org; Fri, 12 Dec 2003 03:57:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBC8v4BO032173
	for sipping-archive@odin.ietf.org; Fri, 12 Dec 2003 03:57:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUj6e-0008Mp-KA
	for sipping-web-archive@optimus.ietf.org; Fri, 12 Dec 2003 03:57:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01634
	for <sipping-web-archive@ietf.org>; Fri, 12 Dec 2003 03:57:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUj6b-00004b-00
	for sipping-web-archive@ietf.org; Fri, 12 Dec 2003 03:57:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUj6b-00004X-00
	for sipping-web-archive@ietf.org; Fri, 12 Dec 2003 03:57:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUj6b-0008Lb-R2; Fri, 12 Dec 2003 03:57:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATN1M-0001gC-8G
	for sipping@optimus.ietf.org; Mon, 08 Dec 2003 10:10:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12298
	for <sipping@ietf.org>; Mon, 8 Dec 2003 10:09:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATN1K-0005ka-00
	for sipping@ietf.org; Mon, 08 Dec 2003 10:09:58 -0500
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATN1J-0005kS-00
	for sipping@ietf.org; Mon, 08 Dec 2003 10:09:57 -0500
Received: from parmhs4.rd.francetelecom.fr ([10.193.117.63]) by parsmtp2.rd.francetelecom.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Mon, 8 Dec 2003 16:09:32 +0100
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: [sipping] comment on draft-polk-sipping-location-requirements-01.txt
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Date: Mon, 8 Dec 2003 16:09:31 +0100
Message-ID: <57F140DC5CDA10438C41674629DE0D870159030B@parmhs4.rd.francetelecom.fr>
Thread-Topic: [sipping] comment on draft-polk-sipping-location-requirements-01.txt
Thread-Index: AcO9nUbh3EhY71fWTKeAITREonPjww==
From: =?iso-8859-1?Q?PROUVOST_S=E9bastien_FTRD/DAC/ISS?= <sebastien.prouvost@francetelecom.com>
To: <jmpolk@cisco.com>, <Brian.rosen@marconi.com>
Cc: <sipping@ietf.org>
X-OriginalArrivalTime: 08 Dec 2003 15:09:32.0133 (UTC) FILETIME=[488EA950:01C3BD9D]
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi,

I fully support the idea of having location information conveyed in SIP.

However, I fail to see in the draft a requirement for a proxy to be able =
to insert the location object on behalf of the UA.=20
It is likely that in some cases terminals may not have this information. =
In some architectures, an outbound proxy may be able to retrieve this =
information (eg. Through a MIDCOM or COPS interface with an entity in =
the transport plane) and it is useful to allow such an outbound proxy to =
insert this location object. =20

As stated in requirement E-3 regarding emergency calls, it may be a =
regulatory obligation for an operator to make this location information =
available to certain users. Operators may therefore be mandated to have =
this information inserted by proxies if the terminal does not insert it.

Regards,

S=E9bastien Prouvost
France T=E9l=E9com R&D/DAC/CAR
http://www.francetelecom.com/rd


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



From exim@www1.ietf.org  Fri Dec 12 08:05:53 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06937
	for <sipping-archive@odin.ietf.org>; Fri, 12 Dec 2003 08:05:53 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUmyy-0000m6-VF
	for sipping-archive@odin.ietf.org; Fri, 12 Dec 2003 08:05:25 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBCD5OiU002972
	for sipping-archive@odin.ietf.org; Fri, 12 Dec 2003 08:05:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUmyy-0000lr-Qo
	for sipping-web-archive@optimus.ietf.org; Fri, 12 Dec 2003 08:05:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06891
	for <sipping-web-archive@ietf.org>; Fri, 12 Dec 2003 08:05:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUmyx-0003xi-00
	for sipping-web-archive@ietf.org; Fri, 12 Dec 2003 08:05:23 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUmyx-0003xf-00
	for sipping-web-archive@ietf.org; Fri, 12 Dec 2003 08:05:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUmyd-0000hx-36; Fri, 12 Dec 2003 08:05:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUmxp-0000gV-Dy
	for sipping@optimus.ietf.org; Fri, 12 Dec 2003 08:04:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06785
	for <sipping@ietf.org>; Fri, 12 Dec 2003 08:04:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUmxo-0003u4-00
	for sipping@ietf.org; Fri, 12 Dec 2003 08:04:12 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUmxn-0003tO-00
	for sipping@ietf.org; Fri, 12 Dec 2003 08:04:11 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id IAA06063;
	Fri, 12 Dec 2003 08:03:26 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id IAA20406;
	Fri, 12 Dec 2003 08:03:26 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <W9W8D73T>; Fri, 12 Dec 2003 08:03:26 -0500
Message-ID: <313680C9A886D511A06000204840E1CF070B61DA@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: =?iso-8859-1?Q?=27PROUVOST_S=E9bastien_FTRD/DAC/ISS=27?=
	 <sebastien.prouvost@francetelecom.com>
Cc: sipping@ietf.org, jmpolk@cisco.com
Subject: RE: [sipping] comment on draft-polk-sipping-location-requirements
	-01.txt
Date: Fri, 12 Dec 2003 08:03:24 -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: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

I think that the issue is one of privacy control.  If some
intermediary puts your location on the message without your
consent, there is a significant breach of privacy.

The emergency case is somewhat different, and we are looking
into how best to accommodate it.  In general, our approach
is to get the UA to know its location and report it with
the call.  We understand the issue of authentication of
location, and will need to assure that the location is accurate
when a carrier knows what it is.   If the location is
provided to the UA, and it chooses to NOT send it, I believe
he should be allowed to do so.  There are several ways the UA
could learn its location from some other entity.  One of them
is DHCP (for a non-mobile UA).=20

Do you see any problem with that approach?

Brian

> -----Original Message-----
> From: PROUVOST S=E9bastien FTRD/DAC/ISS
> [mailto:sebastien.prouvost@francetelecom.com]
> Sent: Monday, December 08, 2003 10:10 AM
> To: jmpolk@cisco.com; Brian.rosen@marconi.com
> Cc: sipping@ietf.org
> Subject: [sipping] comment on
> draft-polk-sipping-location-requirements-01.txt
>=20
>=20
> Hi,
>=20
> I fully support the idea of having location information=20
> conveyed in SIP.
>=20
> However, I fail to see in the draft a requirement for a proxy=20
> to be able to insert the location object on behalf of the UA.=20
> It is likely that in some cases terminals may not have this=20
> information. In some architectures, an outbound proxy may be=20
> able to retrieve this information (eg. Through a MIDCOM or=20
> COPS interface with an entity in the transport plane) and it=20
> is useful to allow such an outbound proxy to insert this=20
> location object. =20
>=20
> As stated in requirement E-3 regarding emergency calls, it=20
> may be a regulatory obligation for an operator to make this=20
> location information available to certain users. Operators=20
> may therefore be mandated to have this information inserted=20
> by proxies if the terminal does not insert it.
>=20
> Regards,
>=20
> S=E9bastien Prouvost
> France T=E9l=E9com R&D/DAC/CAR
> http://www.francetelecom.com/rd
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>=20

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



From exim@www1.ietf.org  Fri Dec 12 09:51:36 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09610
	for <sipping-archive@odin.ietf.org>; Fri, 12 Dec 2003 09:51:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUodH-0005H2-93
	for sipping-archive@odin.ietf.org; Fri, 12 Dec 2003 09:51:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBCEp7Zs020266
	for sipping-archive@odin.ietf.org; Fri, 12 Dec 2003 09:51:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUodH-0005Gn-5Q
	for sipping-web-archive@optimus.ietf.org; Fri, 12 Dec 2003 09:51:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09601
	for <sipping-web-archive@ietf.org>; Fri, 12 Dec 2003 09:51:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUodF-0006Hk-00
	for sipping-web-archive@ietf.org; Fri, 12 Dec 2003 09:51:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUodE-0006Hh-00
	for sipping-web-archive@ietf.org; Fri, 12 Dec 2003 09:51:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUodB-0005Fg-88; Fri, 12 Dec 2003 09:51:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUocV-0005FG-9v
	for sipping@optimus.ietf.org; Fri, 12 Dec 2003 09:50:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09593
	for <sipping@ietf.org>; Fri, 12 Dec 2003 09:50:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUocT-0006HV-00
	for sipping@ietf.org; Fri, 12 Dec 2003 09:50:17 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUocS-0006Gi-00
	for sipping@ietf.org; Fri, 12 Dec 2003 09:50:16 -0500
Received: from zcard307.ca.nortel.com (zcard307.ca.nortel.com [47.129.242.67])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hBCEnf625609;
	Fri, 12 Dec 2003 09:49:41 -0500 (EST)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard307.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id XLYJD4ST; Fri, 12 Dec 2003 09:49:41 -0500
Received: from nortelnetworks.com (acart1hj.ca.nortel.com [47.129.129.226]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id XLPWNBDJ; Fri, 12 Dec 2003 09:49:41 -0500
Message-ID: <3FD9D584.4000101@nortelnetworks.com>
Date: Fri, 12 Dec 2003 09:49:40 -0500
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Rosen, Brian" <Brian.Rosen@marconi.com>
CC: =?ISO-8859-1?Q?=27PROUVOST_S=E9bastien_FTRD/DAC/ISS=27?=
 <sebastien.prouvost@francetelecom.com>,
        sipping@ietf.org, jmpolk@cisco.com
Subject: Re: [sipping] comment on draft-polk-sipping-location-requirements
 -01.txt
References: <313680C9A886D511A06000204840E1CF070B61DA@whq-msgusr-02.pit.comms.marconi.com>
In-Reply-To: <313680C9A886D511A06000204840E1CF070B61DA@whq-msgusr-02.pit.comms.marconi.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by zcars04f.nortelnetworks.com id hBCEnf625609
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

I still maintain that location is no more sensitive in terms of privacy=20
requirements than the rest of call signalling.

As a separate issue, I also still maintain that even if a proxy does not=20
insert location, it must stiull be able to read it in order to route an=20
emergency call correctly.  I've been considering when to reraise this=20
issue, but S=E9bastien has created the occasion.

Rosen, Brian wrote:
> I think that the issue is one of privacy control.  If some
> intermediary puts your location on the message without your
> consent, there is a significant breach of privacy.
>=20
> The emergency case is somewhat different, and we are looking
> into how best to accommodate it.  In general, our approach
> is to get the UA to know its location and report it with
> the call.  We understand the issue of authentication of
> location, and will need to assure that the location is accurate
> when a carrier knows what it is.   If the location is
> provided to the UA, and it chooses to NOT send it, I believe
> he should be allowed to do so.  There are several ways the UA
> could learn its location from some other entity.  One of them
> is DHCP (for a non-mobile UA).=20
>=20
> Do you see any problem with that approach?
>=20
> Brian
>=20
>=20
>>-----Original Message-----
>>From: PROUVOST S=E9bastien FTRD/DAC/ISS
>>[mailto:sebastien.prouvost@francetelecom.com]
>>Sent: Monday, December 08, 2003 10:10 AM
>>To: jmpolk@cisco.com; Brian.rosen@marconi.com
>>Cc: sipping@ietf.org
>>Subject: [sipping] comment on
>>draft-polk-sipping-location-requirements-01.txt
>>
>>
>>Hi,
>>
>>I fully support the idea of having location information=20
>>conveyed in SIP.
>>
>>However, I fail to see in the draft a requirement for a proxy=20
>>to be able to insert the location object on behalf of the UA.=20
>>It is likely that in some cases terminals may not have this=20
>>information. In some architectures, an outbound proxy may be=20
>>able to retrieve this information (eg. Through a MIDCOM or=20
>>COPS interface with an entity in the transport plane) and it=20
>>is useful to allow such an outbound proxy to insert this=20
>>location object. =20
>>
>>As stated in requirement E-3 regarding emergency calls, it=20
>>may be a regulatory obligation for an operator to make this=20
>>location information available to certain users. Operators=20
>>may therefore be mandated to have this information inserted=20
>>by proxies if the terminal does not insert it.
>>
>>Regards,
>>
>>S=E9bastien Prouvost
>>France T=E9l=E9com R&D/DAC/CAR
>>http://www.francetelecom.com/rd
>>
>>
>>_______________________________________________
>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>This list is for NEW development of the application of SIP
>>Use sip-implementors@cs.columbia.edu for questions on current sip
>>Use sip@ietf.org for new developments of core SIP
>>
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>=20


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



From exim@www1.ietf.org  Fri Dec 12 10:13:32 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11176
	for <sipping-archive@odin.ietf.org>; Fri, 12 Dec 2003 10:13:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUoyW-0006Ps-Mp
	for sipping-archive@odin.ietf.org; Fri, 12 Dec 2003 10:13:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBCFD4pZ024658
	for sipping-archive@odin.ietf.org; Fri, 12 Dec 2003 10:13:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUoyW-0006Pd-JY
	for sipping-web-archive@optimus.ietf.org; Fri, 12 Dec 2003 10:13:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11108
	for <sipping-web-archive@ietf.org>; Fri, 12 Dec 2003 10:13:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUoyU-0006eN-00
	for sipping-web-archive@ietf.org; Fri, 12 Dec 2003 10:13:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUoyT-0006eK-00
	for sipping-web-archive@ietf.org; Fri, 12 Dec 2003 10:13:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUoyT-0006OV-Mv; Fri, 12 Dec 2003 10:13:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUoxw-0006O2-N4
	for sipping@optimus.ietf.org; Fri, 12 Dec 2003 10:12:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11033
	for <sipping@ietf.org>; Fri, 12 Dec 2003 10:12:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUoxu-0006d5-00
	for sipping@ietf.org; Fri, 12 Dec 2003 10:12:26 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUoxt-0006cI-00
	for sipping@ietf.org; Fri, 12 Dec 2003 10:12:25 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA11101;
	Fri, 12 Dec 2003 10:11:37 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA11693;
	Fri, 12 Dec 2003 10:11:31 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <W9W81AHT>; Fri, 12 Dec 2003 10:11:30 -0500
Message-ID: <313680C9A886D511A06000204840E1CF070B61DC@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Tom Taylor'" <taylor@nortelnetworks.com>
Cc: =?iso-8859-1?Q?=27PROUVOST_S=E9bastien_FTRD/DAC/ISS=27?=
	 <sebastien.prouvost@francetelecom.com>,
        sipping@ietf.org, jmpolk@cisco.com
Subject: RE: [sipping] comment on draft-polk-sipping-location-requirements
	 -01.txt
Date: Fri, 12 Dec 2003 10:11:28 -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: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Tom

There is a considerable amount of pressure by those who are
concerned about privacy to keep location information under
very tight control.  One attempt to deal with location in the
IETF went down in flames, and the present one has 90% of
its efforts directed to privacy and 10% to location.

This is a reality we have to deal with, or we aren't going
to get anything through the process.

On emergency calls, we have achieved of late, compromises,
which in my opinion are very reasonable, which will allow
us to make emergency calls work well.  These compromises
deal directly with the issue of making location available
to routing entities.  The protection for location information
will be hop-by-hop, precisely so that routing based on location
can be done.

See this thread:
http://www1.ietf.org/mail-archive/working-groups/geopriv/current/msg0013=
8.ht
ml

Brian

> -----Original Message-----
> From: Tom Taylor [mailto:taylor@nortelnetworks.com]
> Sent: Friday, December 12, 2003 9:50 AM
> To: Rosen, Brian
> Cc: 'PROUVOST S=E9bastien FTRD/DAC/ISS'; sipping@ietf.org;
> jmpolk@cisco.com
> Subject: Re: [sipping] comment on
> draft-polk-sipping-location-requirements -01.txt
>=20
>=20
> I still maintain that location is no more sensitive in terms=20
> of privacy=20
> requirements than the rest of call signalling.
>=20
> As a separate issue, I also still maintain that even if a=20
> proxy does not=20
> insert location, it must stiull be able to read it in order=20
> to route an=20
> emergency call correctly.  I've been considering when to reraise this =

> issue, but S=E9bastien has created the occasion.
>=20
> Rosen, Brian wrote:
> > I think that the issue is one of privacy control.  If some
> > intermediary puts your location on the message without your
> > consent, there is a significant breach of privacy.
> >=20
> > The emergency case is somewhat different, and we are looking
> > into how best to accommodate it.  In general, our approach
> > is to get the UA to know its location and report it with
> > the call.  We understand the issue of authentication of
> > location, and will need to assure that the location is accurate
> > when a carrier knows what it is.   If the location is
> > provided to the UA, and it chooses to NOT send it, I believe
> > he should be allowed to do so.  There are several ways the UA
> > could learn its location from some other entity.  One of them
> > is DHCP (for a non-mobile UA).=20
> >=20
> > Do you see any problem with that approach?
> >=20
> > Brian
> >=20
> >=20
> >>-----Original Message-----
> >>From: PROUVOST S=E9bastien FTRD/DAC/ISS
> >>[mailto:sebastien.prouvost@francetelecom.com]
> >>Sent: Monday, December 08, 2003 10:10 AM
> >>To: jmpolk@cisco.com; Brian.rosen@marconi.com
> >>Cc: sipping@ietf.org
> >>Subject: [sipping] comment on
> >>draft-polk-sipping-location-requirements-01.txt
> >>
> >>
> >>Hi,
> >>
> >>I fully support the idea of having location information=20
> >>conveyed in SIP.
> >>
> >>However, I fail to see in the draft a requirement for a proxy=20
> >>to be able to insert the location object on behalf of the UA.=20
> >>It is likely that in some cases terminals may not have this=20
> >>information. In some architectures, an outbound proxy may be=20
> >>able to retrieve this information (eg. Through a MIDCOM or=20
> >>COPS interface with an entity in the transport plane) and it=20
> >>is useful to allow such an outbound proxy to insert this=20
> >>location object. =20
> >>
> >>As stated in requirement E-3 regarding emergency calls, it=20
> >>may be a regulatory obligation for an operator to make this=20
> >>location information available to certain users. Operators=20
> >>may therefore be mandated to have this information inserted=20
> >>by proxies if the terminal does not insert it.
> >>
> >>Regards,
> >>
> >>S=E9bastien Prouvost
> >>France T=E9l=E9com R&D/DAC/CAR
> >>http://www.francetelecom.com/rd
> >>
> >>
> >>_______________________________________________
> >>Sipping mailing list  =
https://www1.ietf.org/mailman/listinfo/sipping
> >>This list is for NEW development of the application of SIP
> >>Use sip-implementors@cs.columbia.edu for questions on current sip
> >>Use sip@ietf.org for new developments of core SIP
> >>
> >=20
> >=20
> > _______________________________________________
> > Sipping mailing list  =
https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> >=20
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>=20

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



From exim@www1.ietf.org  Fri Dec 12 13:41:35 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19549
	for <sipping-archive@odin.ietf.org>; Fri, 12 Dec 2003 13:41:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUsDr-0000tc-J2
	for sipping-archive@odin.ietf.org; Fri, 12 Dec 2003 13:41:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBCIf7cr003440
	for sipping-archive@odin.ietf.org; Fri, 12 Dec 2003 13:41:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUsDr-0000tP-F6
	for sipping-web-archive@optimus.ietf.org; Fri, 12 Dec 2003 13:41:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19536
	for <sipping-web-archive@ietf.org>; Fri, 12 Dec 2003 13:41:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUsDp-0003l6-00
	for sipping-web-archive@ietf.org; Fri, 12 Dec 2003 13:41:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUsDo-0003l3-00
	for sipping-web-archive@ietf.org; Fri, 12 Dec 2003 13:41:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUsDm-0000sW-45; Fri, 12 Dec 2003 13:41:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUsDS-0000ry-PP
	for sipping@optimus.ietf.org; Fri, 12 Dec 2003 13:40:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19522
	for <sipping@ietf.org>; Fri, 12 Dec 2003 13:40:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUsDQ-0003ka-00
	for sipping@ietf.org; Fri, 12 Dec 2003 13:40:40 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUsDQ-0003jr-00
	for sipping@ietf.org; Fri, 12 Dec 2003 13:40:40 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA19196;
	Fri, 12 Dec 2003 13:39:18 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA19893;
	Fri, 12 Dec 2003 13:39:19 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <W9W81G9B>; Fri, 12 Dec 2003 13:39:19 -0500
Message-ID: <313680C9A886D511A06000204840E1CF070B61DF@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: =?iso-8859-1?Q?=27PROUVOST_S=E9bastien_FTRD/DAC/ISS=27?=
	 <sebastien.prouvost@francetelecom.com>
Cc: sipping@ietf.org, jmpolk@cisco.com
Subject: RE: RE : [sipping] comment on draft-polk-sipping-location-require
	ments-01.txt
Date: Fri, 12 Dec 2003 13:39:17 -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: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

S=E9bastien

When would there be a situation where the terminal is not
able to obtain its own location?  Are you arguing on technical
grounds or business reasons? =20

If the international standards for VoIP emergency calls=20
were structured so that UAs were informed of their location,
and included that information on an emergency call, would you
still worry that some country would impose regulations requiring
a carrier to insert location?  If that happened, would you
expect the IETF to change the specifications?

Don't you see that the mechanism for having proxy insertion
PLUS mechanisms for UAs to request that proxies not insert
is more complicated, without having a compelling technical
advantage?

Brian

> -----Original Message-----
> From: PROUVOST S=E9bastien FTRD/DAC/ISS
> [mailto:sebastien.prouvost@francetelecom.com]
> Sent: Friday, December 12, 2003 1:30 PM
> To: Rosen, Brian
> Cc: sipping@ietf.org; jmpolk@cisco.com
> Subject: RE : [sipping] comment on
> draft-polk-sipping-location-requirements-01.txt
>=20
>=20
> Well, I still believe that the cases where the terminal will=20
> not be able to get information shall be covered and that a=20
> proxy should be allowed to insert this information in such a=20
> case (if it is able to obtain it).
> =20
> If not, there is a significant issue with emergency calls :=20
> it may be a regulatory obligation for an operator to make=20
> this location information available.
>=20
> I also agree that privacy considerations regarding the=20
> divulgation of location information is important and that=20
> except for emergency calls this information shall not be=20
> delivered to any entity without the agreement of the UA.
> If a proxy in the path is allowed to insert the info, this=20
> shall lead to the additionnal requirement that a UA shall be=20
> able to inform proxies in the path whether of not they are=20
> allowed to insert this information.
> =20
> =20
> Regards,
>=20
> S=E9bastien Prouvost
> France T=E9l=E9com R&D/DAC/CAR
> http://www.francetelecom.com/rd
>=20
> -----Message d'origine-----
> De : Rosen, Brian [mailto:Brian.Rosen@marconi.com]=20
> Envoy=E9 : vendredi 12 d=E9cembre 2003 14:03
> =C0 : PROUVOST S=E9bastien FTRD/DAC/ISS
> Cc : sipping@ietf.org; jmpolk@cisco.com
> Objet : RE: [sipping] comment on=20
> draft-polk-sipping-location-requirements-01.txt
>=20
>=20
> I think that the issue is one of privacy control.  If some=20
> intermediary puts your location on the message without your=20
> consent, there is a significant breach of privacy.
>=20
> The emergency case is somewhat different, and we are looking=20
> into how best to accommodate it.  In general, our approach is=20
> to get the UA to know its location and report it with the=20
> call.  We understand the issue of authentication of location,=20
> and will need to assure that the location is accurate
> when a carrier knows what it is.   If the location is
> provided to the UA, and it chooses to NOT send it, I believe
> he should be allowed to do so.  There are several ways the UA=20
> could learn its location from some other entity.  One of them=20
> is DHCP (for a non-mobile UA).=20
>=20
> Do you see any problem with that approach?
>=20
> Brian
>=20
> > -----Original Message-----
> > From: PROUVOST S=E9bastien FTRD/DAC/ISS
> > [mailto:sebastien.prouvost@francetelecom.com]
> > Sent: Monday, December 08, 2003 10:10 AM
> > To: jmpolk@cisco.com; Brian.rosen@marconi.com
> > Cc: sipping@ietf.org
> > Subject: [sipping] comment on=20
> > draft-polk-sipping-location-requirements-01.txt
> >=20
> >=20
> > Hi,
> >=20
> > I fully support the idea of having location information conveyed in =

> > SIP.
> >=20
> > However, I fail to see in the draft a requirement for a proxy to be =

> > able to insert the location object on behalf of the UA. It=20
> is likely=20
> > that in some cases terminals may not have this information. In some =

> > architectures, an outbound proxy may be able to retrieve this=20
> > information (eg. Through a MIDCOM or COPS interface with an=20
> entity in=20
> > the transport plane) and it is useful to allow such an=20
> outbound proxy=20
> > to insert this location object.
> >=20
> > As stated in requirement E-3 regarding emergency calls, it may be a =

> > regulatory obligation for an operator to make this location=20
> > information available to certain users. Operators may therefore be=20
> > mandated to have this information inserted by proxies if=20
> the terminal=20
> > does not insert it.
> >=20
> > Regards,
> >=20
> > S=E9bastien Prouvost
> > France T=E9l=E9com R&D/DAC/CAR
> > http://www.francetelecom.com/rd
> >=20
> >=20
> > _______________________________________________
> > Sipping mailing list  =
https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP Use
> > sip-implementors@cs.columbia.edu for questions on current sip Use=20
> > sip@ietf.org for new developments of core SIP
> >=20
>=20

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



From exim@www1.ietf.org  Fri Dec 12 14:01:33 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20201
	for <sipping-archive@odin.ietf.org>; Fri, 12 Dec 2003 14:01:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUsXA-0001fs-Vw
	for sipping-archive@odin.ietf.org; Fri, 12 Dec 2003 14:01:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBCJ14a5006430
	for sipping-archive@odin.ietf.org; Fri, 12 Dec 2003 14:01:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUsXA-0001fd-SG
	for sipping-web-archive@optimus.ietf.org; Fri, 12 Dec 2003 14:01:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20171
	for <sipping-web-archive@ietf.org>; Fri, 12 Dec 2003 14:01:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUsX8-00049m-00
	for sipping-web-archive@ietf.org; Fri, 12 Dec 2003 14:01:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUsX8-00049j-00
	for sipping-web-archive@ietf.org; Fri, 12 Dec 2003 14:01:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUsX7-0001dq-Gs; Fri, 12 Dec 2003 14:01:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUsWN-0001ch-Qi
	for sipping@optimus.ietf.org; Fri, 12 Dec 2003 14:00:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20137
	for <sipping@ietf.org>; Fri, 12 Dec 2003 14:00:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUsWL-00047U-00
	for sipping@ietf.org; Fri, 12 Dec 2003 14:00:13 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUsWL-000473-00
	for sipping@ietf.org; Fri, 12 Dec 2003 14:00:13 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
  by sj-iport-3.cisco.com with ESMTP; 12 Dec 2003 11:02:16 +0000
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hBCIxeAt011557;
	Fri, 12 Dec 2003 10:59:40 -0800 (PST)
Received: from [10.32.245.157] (stealth-10-32-245-157.cisco.com [10.32.245.157])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with SMTP id AKS18183;
	Fri, 12 Dec 2003 10:59:37 -0800 (PST)
Date: Fri, 12 Dec 2003 13:59:36 -0500
From: David Oran <oran@cisco.com>
To: Tom Taylor <taylor@nortelnetworks.com>,
        "Rosen, Brian" <Brian.Rosen@marconi.com>
cc: "=?ISO-8859-1?Q?'PROUVOST_S=E9bastien_FTRD=2FDAC=2FISS'?=" <sebastien.prouvost@francetelecom.com>,
        sipping@ietf.org, jmpolk@cisco.com
Subject: Re: [sipping] comment on draft-polk-sipping-location-requirements
 -01.txt
Message-ID: <2147483647.1071237576@[10.32.245.157]>
In-Reply-To: <3FD9D584.4000101@nortelnetworks.com>
References: <313680C9A886D511A06000204840E1CF070B61DA@whq-msgusr-02.pit.comms
 .marconi.com> <3FD9D584.4000101@nortelnetworks.com>
X-Mailer: Mulberry/3.1.0 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

--On Friday, December 12, 2003 9:49 AM -0500 Tom Taylor=20
<taylor@nortelnetworks.com> wrote:

> I still maintain that location is no more sensitive in terms of privacy
> requirements than the rest of call signalling.
>
What else in the signaling can be used to target tactical nukes or send in=20
hit squads?

> As a separate issue, I also still maintain that even if a proxy does not
> insert location, it must stiull be able to read it in order to route an
> emergency call correctly.  I've been considering when to reraise this
> issue, but S=E9bastien has created the occasion.
>
Sure, but as Brian points out, the policy about revealing your location=20
needs to be under control of the user.

Dave.

> Rosen, Brian wrote:
>> I think that the issue is one of privacy control.  If some
>> intermediary puts your location on the message without your
>> consent, there is a significant breach of privacy.
>>
>> The emergency case is somewhat different, and we are looking
>> into how best to accommodate it.  In general, our approach
>> is to get the UA to know its location and report it with
>> the call.  We understand the issue of authentication of
>> location, and will need to assure that the location is accurate
>> when a carrier knows what it is.   If the location is
>> provided to the UA, and it chooses to NOT send it, I believe
>> he should be allowed to do so.  There are several ways the UA
>> could learn its location from some other entity.  One of them
>> is DHCP (for a non-mobile UA).
>>
>> Do you see any problem with that approach?
>>
>> Brian
>>
>>
>>> -----Original Message-----
>>> From: PROUVOST S=E9bastien FTRD/DAC/ISS
>>> [mailto:sebastien.prouvost@francetelecom.com]
>>> Sent: Monday, December 08, 2003 10:10 AM
>>> To: jmpolk@cisco.com; Brian.rosen@marconi.com
>>> Cc: sipping@ietf.org
>>> Subject: [sipping] comment on
>>> draft-polk-sipping-location-requirements-01.txt
>>>
>>>
>>> Hi,
>>>
>>> I fully support the idea of having location information
>>> conveyed in SIP.
>>>
>>> However, I fail to see in the draft a requirement for a proxy
>>> to be able to insert the location object on behalf of the UA.
>>> It is likely that in some cases terminals may not have this
>>> information. In some architectures, an outbound proxy may be
>>> able to retrieve this information (eg. Through a MIDCOM or
>>> COPS interface with an entity in the transport plane) and it
>>> is useful to allow such an outbound proxy to insert this
>>> location object.
>>>
>>> As stated in requirement E-3 regarding emergency calls, it
>>> may be a regulatory obligation for an operator to make this
>>> location information available to certain users. Operators
>>> may therefore be mandated to have this information inserted
>>> by proxies if the terminal does not insert it.
>>>
>>> Regards,
>>>
>>> S=E9bastien Prouvost
>>> France T=E9l=E9com R&D/DAC/CAR
>>> http://www.francetelecom.com/rd
>>>
>>>
>>> _______________________________________________
>>> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>> This list is for NEW development of the application of SIP
>>> Use sip-implementors@cs.columbia.edu for questions on current sip
>>> Use sip@ietf.org for new developments of core SIP
>>>
>>
>>
>> _______________________________________________
>> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>> This list is for NEW development of the application of SIP
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sip@ietf.org for new developments of core SIP
>>
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP





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



From exim@www1.ietf.org  Fri Dec 12 14:19:33 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20967
	for <sipping-archive@odin.ietf.org>; Fri, 12 Dec 2003 14:19:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUsoc-0002ad-D8
	for sipping-archive@odin.ietf.org; Fri, 12 Dec 2003 14:19:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBCJJ6ln009949
	for sipping-archive@odin.ietf.org; Fri, 12 Dec 2003 14:19:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUsoc-0002aO-9D
	for sipping-web-archive@optimus.ietf.org; Fri, 12 Dec 2003 14:19:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20950
	for <sipping-web-archive@ietf.org>; Fri, 12 Dec 2003 14:19:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUsoZ-0004kJ-00
	for sipping-web-archive@ietf.org; Fri, 12 Dec 2003 14:19:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUsoZ-0004kG-00
	for sipping-web-archive@ietf.org; Fri, 12 Dec 2003 14:19:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUsoY-0002ZJ-0x; Fri, 12 Dec 2003 14:19:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUso5-0002YR-2U
	for sipping@optimus.ietf.org; Fri, 12 Dec 2003 14:18:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20946
	for <sipping@ietf.org>; Fri, 12 Dec 2003 14:18:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUso2-0004ja-00
	for sipping@ietf.org; Fri, 12 Dec 2003 14:18:30 -0500
Received: from zcars04e.nortelnetworks.com ([47.129.242.56])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUso2-0004ig-00
	for sipping@ietf.org; Fri, 12 Dec 2003 14:18:30 -0500
Received: from zcard307.ca.nortel.com (americasm07.nt.com [47.129.242.67])
	by zcars04e.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hBCJHFC27292;
	Fri, 12 Dec 2003 14:17:15 -0500 (EST)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard307.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id XLYJ1V2T; Fri, 12 Dec 2003 14:17:15 -0500
Received: from nortelnetworks.com (acart1hj.ca.nortel.com [47.129.129.226]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id XLPWNBHQ; Fri, 12 Dec 2003 14:17:14 -0500
Message-ID: <3FDA1438.6040403@nortelnetworks.com>
Date: Fri, 12 Dec 2003 14:17:12 -0500
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: David Oran <oran@cisco.com>
CC: "Rosen, Brian" <Brian.Rosen@marconi.com>,
        =?ISO-8859-1?Q?=27PROUVOST_?=
 =?ISO-8859-1?Q?S=E9bastien_FTRD/DAC/ISS=27?=
 <sebastien.prouvost@francetelecom.com>,
        sipping@ietf.org, jmpolk@cisco.com
Subject: Re: [sipping] comment on draft-polk-sipping-location-requirements
 -01.txt
References: <313680C9A886D511A06000204840E1CF070B61DA@whq-msgusr-02.pit.comms .marconi.com> <3FD9D584.4000101@nortelnetworks.com> <2147483647.1071237576@[10.32.245.157]>
In-Reply-To: <2147483647.1071237576@[10.32.245.157]>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



David Oran wrote:

> --On Friday, December 12, 2003 9:49 AM -0500 Tom Taylor 
> <taylor@nortelnetworks.com> wrote:
> 
>> I still maintain that location is no more sensitive in terms of privacy
>> requirements than the rest of call signalling.
>>
> What else in the signaling can be used to target tactical nukes or send 
> in hit squads?
> 
> 
Gross exaggeration when I'm trying to get an ambulance or call the fire 
department, but I see your point.  My point was that call signalling in 
general is sensitive, which is why the FBI is interested in intercepting 
it when they have legal justification.  I can see that there will be 
circumstances where callers are trying to get help while hiding from 
potential attackers, and the possibility that the latter know a call for 
help has gone out is less threatening than the possibility that they 
know the caller's location.


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



From exim@www1.ietf.org  Fri Dec 12 15:41:44 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25432
	for <sipping-archive@odin.ietf.org>; Fri, 12 Dec 2003 15:41:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUu66-0007gr-EA
	for sipping-archive@odin.ietf.org; Fri, 12 Dec 2003 15:41:16 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBCKfEXf029555
	for sipping-archive@odin.ietf.org; Fri, 12 Dec 2003 15:41:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUu66-0007gc-4n
	for sipping-web-archive@optimus.ietf.org; Fri, 12 Dec 2003 15:41:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25370
	for <sipping-web-archive@ietf.org>; Fri, 12 Dec 2003 15:41:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUu64-0007mP-00
	for sipping-web-archive@ietf.org; Fri, 12 Dec 2003 15:41:12 -0500
Received: from [65.246.255.50] (helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUu63-0007m3-01
	for sipping-web-archive@ietf.org; Fri, 12 Dec 2003 15:41:12 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org)
	by manatick with esmtp (Exim 4.24)
	id 1AUu29-0007Ci-Cx
	for sipping-web-archive@ietf.org; Fri, 12 Dec 2003 15:37:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUu21-0006qo-Ri; Fri, 12 Dec 2003 15:37:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUu12-0006nx-TR
	for sipping@optimus.ietf.org; Fri, 12 Dec 2003 15:36:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25184
	for <sipping@ietf.org>; Fri, 12 Dec 2003 15:35:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUu0y-0007dU-00
	for sipping@ietf.org; Fri, 12 Dec 2003 15:35:56 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUu0y-0007cq-00
	for sipping@ietf.org; Fri, 12 Dec 2003 15:35:56 -0500
Received: from caryfitz-w2k.amer.cisco.com (sjc-vpn3-830.cisco.com [10.21.67.62])
	by rtp-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hBCKZLxg022982;
	Fri, 12 Dec 2003 15:35:21 -0500 (EST)
Date: Fri, 12 Dec 2003 12:35:20 -0800
From: Cary FitzGerald <caryfitz@cisco.com>
To: David Oran <oran@cisco.com>, Tom Taylor <taylor@nortelnetworks.com>,
        "Rosen, Brian" <Brian.Rosen@marconi.com>
cc: "=?ISO-8859-1?Q?'PROUVOST_S=E9bastien_FTRD=2FDAC=2FISS'?=" <sebastien.prouvost@francetelecom.com>,
        sipping@ietf.org, jmpolk@cisco.com
Subject: Re: [sipping] comment on
 draft-polk-sipping-location-requirements -01.txt
Message-ID: <88844611.1071232520@[192.168.1.101]>
In-Reply-To: <2147483647.1071237576@[10.32.245.157]>
References: <313680C9A886D511A06000204840E1CF070B61DA@whq-msgusr-02.pit
 .comms .marconi.com> <3FD9D584.4000101@nortelnetworks.com>
 <2147483647.1071237576@[10.32.245.157]>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

The telephony equivalent of hit squad are unsolicited sales calls. 
Not all threats are physical.

Cary.

--On Friday, December 12, 2003 1:59 PM -0500 David Oran 
<oran@cisco.com> wrote:

> --On Friday, December 12, 2003 9:49 AM -0500 Tom Taylor
> <taylor@nortelnetworks.com> wrote:
>
>> I still maintain that location is no more sensitive in terms of
>> privacy requirements than the rest of call signalling.
>>
> What else in the signaling can be used to target tactical nukes or
> send in hit squads?

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



From exim@www1.ietf.org  Mon Dec 15 03:48:43 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29597
	for <sipping-archive@odin.ietf.org>; Mon, 15 Dec 2003 03:48:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVoOj-0001BQ-D5
	for sipping-archive@odin.ietf.org; Mon, 15 Dec 2003 03:48:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBF8mCOW004544
	for sipping-archive@odin.ietf.org; Mon, 15 Dec 2003 03:48:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVoOg-0001BD-9i
	for sipping-web-archive@optimus.ietf.org; Mon, 15 Dec 2003 03:48:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29583
	for <sipping-web-archive@ietf.org>; Mon, 15 Dec 2003 03:48:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVoOd-0007S7-00
	for sipping-web-archive@ietf.org; Mon, 15 Dec 2003 03:48:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVoOd-0007S2-00
	for sipping-web-archive@ietf.org; Mon, 15 Dec 2003 03:48:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVoOZ-0001A0-2u; Mon, 15 Dec 2003 03:48:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVoNa-00018x-G9
	for sipping@optimus.ietf.org; Mon, 15 Dec 2003 03:47:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29563
	for <sipping@ietf.org>; Mon, 15 Dec 2003 03:47:00 -0500 (EST)
From: hector.berna@vodafone.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVoNY-0007RK-00
	for sipping@ietf.org; Mon, 15 Dec 2003 03:47:00 -0500
Received: from [212.166.209.12] (helo=m2-pasarela3.airtel.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVoNX-0007RG-00
	for sipping@ietf.org; Mon, 15 Dec 2003 03:46:59 -0500
To: sipping@ietf.org
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF9F114AB3.F7D5DE4F-ONC1256DFD.003016A8@airtel.es>
Date: Mon, 15 Dec 2003 09:46:28 +0100
X-MIMETrack: Serialize by Router on M2-SMTP3/AIRTEL(Release 5.0.11  |July 24, 2002) at
 12/15/2003 09:47:01 AM
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Subject: [Sipping] Push-to-Talk specifications
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hello,

I would like to know if there is any RFC or Draft that states the speci=
fications of the Push-to-Talk
service.

Thanks in advance,

Hector Berna




.......................................................................=
.......................................................................=
.......................................................................=
.............


Confidencialidad


Este  correo  electr=F3nico  y,  en su caso, cualquier fichero anexo al=
 mismo, contiene informaci=F3n de
car=E1cter  confidencial  exclusivamente  dirigida  a  su  destinatario=
 o destinatarios y propiedad de
Vodafone  Espa=F1a.  Queda  prohibida  su  divulgaci=F3n,  copia o dist=
ribuci=F3n a terceros sin la previa
autorizaci=F3n  escrita  de  Vodafone Espa=F1a, en virtud de la legisla=
ci=F3n vigente. En el caso de haber
recibido  este  correo  electr=F3nico  por error, se ruega notificar in=
mediatamente esta circunstancia
mediante reenv=EDo a la direcci=F3n electr=F3nica del remitente y la de=
strucci=F3n del mismo.


Confidentiality


The  information in this e-mail and in any attachments is classified as=
 Vodafone Espa=F1a Confidential
and  Proprietary Information and solely for the attention and use of th=
e named addressee(s). You are
hereby  notified  that  any  dissemination, distribution or copy of thi=
s communication is prohibited
without  the  prior  written consent of Vodafone Espa=F1a and it is str=
ictly prohibited by law. If you
have received this communication by error, please, notify the sender by=
 replying e-mail.
=



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



From exim@www1.ietf.org  Mon Dec 15 03:57:37 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29786
	for <sipping-archive@odin.ietf.org>; Mon, 15 Dec 2003 03:57:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVoXM-0001U6-Cg
	for sipping-archive@odin.ietf.org; Mon, 15 Dec 2003 03:57:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBF8v7YN005640
	for sipping-archive@odin.ietf.org; Mon, 15 Dec 2003 03:57:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVoXK-0001SV-GO
	for sipping-web-archive@optimus.ietf.org; Mon, 15 Dec 2003 03:57:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29772
	for <sipping-web-archive@ietf.org>; Mon, 15 Dec 2003 03:57:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVoXH-0007Zo-00
	for sipping-web-archive@ietf.org; Mon, 15 Dec 2003 03:57:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVoXH-0007Zl-00
	for sipping-web-archive@ietf.org; Mon, 15 Dec 2003 03:57:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVoXI-0001RQ-1i; Mon, 15 Dec 2003 03:57:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVoXA-0001Qw-6N
	for sipping@optimus.ietf.org; Mon, 15 Dec 2003 03:56:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29766
	for <sipping@ietf.org>; Mon, 15 Dec 2003 03:56:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVoX7-0007Zb-00
	for sipping@ietf.org; Mon, 15 Dec 2003 03:56:53 -0500
Received: from imr1.ericy.com ([198.24.6.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVoX7-0007ZJ-00
	for sipping@ietf.org; Mon, 15 Dec 2003 03:56:53 -0500
Received: from eamrcnt750.exu.ericsson.se (eamrcnt750.exu.ericsson.se [138.85.133.51])
	by imr1.ericy.com (8.12.10/8.12.10) with ESMTP id hBF8uPWm029203;
	Mon, 15 Dec 2003 02:56:25 -0600 (CST)
Received: from ericsson.com (EFO9N000L5C7100.lmf.ericsson.se [131.160.31.211]) by eamrcnt750.exu.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id YGLQ7T7M; Mon, 15 Dec 2003 02:56:09 -0600
Message-ID: <3FDD7735.1080604@ericsson.com>
Date: Mon, 15 Dec 2003 10:56:21 +0200
X-Sybari-Trust: 824e8cb3 76be5e0c 125231cb 00000138
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: hector.berna@vodafone.com
CC: sipping@ietf.org
Subject: Re: [Sipping] Push-to-Talk specifications
References: <OF9F114AB3.F7D5DE4F-ONC1256DFD.003016A8@airtel.es>
In-Reply-To: <OF9F114AB3.F7D5DE4F-ONC1256DFD.003016A8@airtel.es>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hector,

no, there are no RFCs or I-Ds about Push-To-Talk. There are several 
companies providing this type of service, and there is not a single 
standard for Push-To-Talk.

In any case, you can find the specifications developed by an industry 
consortium in the link below (at the bottom of the page.) These specs 
were taken by OMA as an starting point for their own specs.

http://www.ericsson.com/products/product_selector/Inst_Talk_hpsol.shtml

Regards,

Gonzalo

hector.berna@vodafone.com wrote:
> Hello,
> 
> I would like to know if there is any RFC or Draft that states the specifications of the Push-to-Talk
> service.
> 
> Thanks in advance,
> 
> Hector Berna


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



From exim@www1.ietf.org  Mon Dec 15 04:06:37 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00194
	for <sipping-archive@odin.ietf.org>; Mon, 15 Dec 2003 04:06:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVog4-00025b-Bk
	for sipping-archive@odin.ietf.org; Mon, 15 Dec 2003 04:06:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBF968Jx008025
	for sipping-archive@odin.ietf.org; Mon, 15 Dec 2003 04:06:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVog4-00025M-0u
	for sipping-web-archive@optimus.ietf.org; Mon, 15 Dec 2003 04:06:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00141
	for <sipping-web-archive@ietf.org>; Mon, 15 Dec 2003 04:06:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVog1-0007kw-00
	for sipping-web-archive@ietf.org; Mon, 15 Dec 2003 04:06:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVog0-0007kt-00
	for sipping-web-archive@ietf.org; Mon, 15 Dec 2003 04:06:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVog0-00023m-8S; Mon, 15 Dec 2003 04:06:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVoff-00021o-M5
	for sipping@optimus.ietf.org; Mon, 15 Dec 2003 04:05:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00128
	for <sipping@ietf.org>; Mon, 15 Dec 2003 04:05:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVofd-0007ke-00
	for sipping@ietf.org; Mon, 15 Dec 2003 04:05:41 -0500
Received: from david.siemens.de ([192.35.17.14])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVofc-0007kb-00
	for sipping@ietf.org; Mon, 15 Dec 2003 04:05:40 -0500
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14])
	by david.siemens.de (8.11.7/8.11.7) with ESMTP id hBF95cF21484;
	Mon, 15 Dec 2003 10:05:38 +0100 (MET)
Received: from moody.mchh.siemens.de (moody.mchh.siemens.de [139.21.205.85])
	by mail1.siemens.de (8.11.7/8.11.7) with ESMTP id hBF95cL10587;
	Mon, 15 Dec 2003 10:05:38 +0100 (MET)
Received: from mchh248e.mchh.siemens.de (mchh248e.mchh.siemens.de [139.21.200.58])
	by moody.mchh.siemens.de (8.9.3/8.9.1) with ESMTP id KAA15146;
	Mon, 15 Dec 2003 10:05:37 +0100 (MET)
Received: by mchh248e.mchh.siemens.de with Internet Mail Service (5.5.2653.19)
	id <YZ6X040H>; Mon, 15 Dec 2003 10:05:37 +0100
Message-ID: <5B788FC2CAFBD6118BAE0030848B025C66CB38@LNN201E>
From: Priem Xavier <xavier.priem@siemens.com>
To: "'hector.berna@vodafone.com'" <hector.berna@vodafone.com>
Cc: sipping@ietf.org, Marjou Xavier <xavier.marjou@siemens.com>
Subject: RE: [Sipping] Push-to-Talk specifications
Date: Mon, 15 Dec 2003 10:05:21 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi Hector,

You may know about the PoC (Push-to-Talk Over Cellular) standard, =
emerging from Ericsson, Motorola, Nokia and Siemens consortium.=20

If this is the one you search for, you will find under =
http://www.siemens.com/Daten/siecom/HQ/ICM/Internet/ICM_Unitwide/WORKARE=
A/ICMPress/templatedata/English/file/binary/ICM_200309_149_e_Push_to_Tal=
k_1093999.pdf

Some press info.

If you need docs or more info, please ask my colleague Xavier Marjou...

Best regards

Xavier Priem
Cordialement / Mit freundlichem Gru=DF / With kind regards=20
Xavier PRIEM=20
R&D Consultant / Patent Delegate
Dept System Engineering & Project Acquisition
---------------------------------------------------------=20
SRIT Lannion=20
SIEMENS R=E9seaux Informatique et T=E9l=E9communications=20
3, Rue Blaise Pascal=20
22300 LANNION - FRANCE=20
http://www.siemens-srit.com/
Phone:  +33 2 96 48 74 30=20
Fax:    +33 2 96 48 74 73=20
Email:  xavier.priem@siemens.com <mailto:xavier.priem@siemens.com>=20
---------------------------------------------------------=20



-----Original Message-----
From: hector.berna@vodafone.com [mailto:hector.berna@vodafone.com]=20
Sent: lundi 15 d=E9cembre 2003 09:46
To: sipping@ietf.org
Subject: [Sipping] Push-to-Talk specifications


Hello,

I would like to know if there is any RFC or Draft that states the =
specifications of the Push-to-Talk service.

Thanks in advance,

Hector Berna




.......................................................................=
.......................................................................=
.......................................................................=
.............


Confidencialidad


Este  correo  electr=F3nico  y,  en su caso, cualquier fichero anexo al =
mismo, contiene informaci=F3n de car=E1cter  confidencial  =
exclusivamente  dirigida  a  su  destinatario o destinatarios y =
propiedad de Vodafone  Espa=F1a.  Queda  prohibida  su  divulgaci=F3n,  =
copia o distribuci=F3n a terceros sin la previa autorizaci=F3n  escrita =
 de  Vodafone Espa=F1a, en virtud de la legislaci=F3n vigente. En el =
caso de haber recibido  este  correo  electr=F3nico  por error, se =
ruega notificar inmediatamente esta circunstancia mediante reenv=EDo a =
la direcci=F3n electr=F3nica del remitente y la destrucci=F3n del =
mismo.


Confidentiality


The  information in this e-mail and in any attachments is classified as =
Vodafone Espa=F1a Confidential and  Proprietary Information and solely =
for the attention and use of the named addressee(s). You are hereby  =
notified  that  any  dissemination, distribution or copy of this =
communication is prohibited without  the  prior  written consent of =
Vodafone Espa=F1a and it is strictly prohibited by law. If you have =
received this communication by error, please, notify the sender by =
replying e-mail.



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

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



From exim@www1.ietf.org  Mon Dec 15 04:22:37 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00661
	for <sipping-archive@odin.ietf.org>; Mon, 15 Dec 2003 04:22:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVovY-00033O-AM
	for sipping-archive@odin.ietf.org; Mon, 15 Dec 2003 04:22:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBF9M767011732
	for sipping-archive@odin.ietf.org; Mon, 15 Dec 2003 04:22:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVovX-000337-AT
	for sipping-web-archive@optimus.ietf.org; Mon, 15 Dec 2003 04:22:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00650
	for <sipping-web-archive@ietf.org>; Mon, 15 Dec 2003 04:22:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVovU-0000DZ-00
	for sipping-web-archive@ietf.org; Mon, 15 Dec 2003 04:22:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVovU-0000DW-00
	for sipping-web-archive@ietf.org; Mon, 15 Dec 2003 04:22:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVovS-000322-I8; Mon, 15 Dec 2003 04:22:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVouV-00031G-0V
	for sipping@optimus.ietf.org; Mon, 15 Dec 2003 04:21:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00642
	for <sipping@ietf.org>; Mon, 15 Dec 2003 04:21:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVouS-0000DN-00
	for sipping@ietf.org; Mon, 15 Dec 2003 04:21:00 -0500
Received: from fw1.covansys.com ([12.162.224.20] helo=fth-smtp02.covansys.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVouR-0000DE-00
	for sipping@ietf.org; Mon, 15 Dec 2003 04:20:59 -0500
Received: from fth-owa1.covansys.com ([10.3.82.25]) by fth-smtp02.covansys.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 15 Dec 2003 04:05:36 -0500
Received: from chn-ex01.covansys.com ([10.6.4.56]) by fth-owa1.covansys.com with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 15 Dec 2003 04:05:35 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Push-to-Talk specifications
Date: Mon, 15 Dec 2003 14:34:04 +0530
Message-ID: <B51554B08F5AC243A26D66BD6E076143024EB247@chn-ex01.cvns.corp.covansys.com>
Thread-Topic: [Sipping] Push-to-Talk specifications
Thread-Index: AcPC6KE9XLeErUyITCKs/oqfpHNRvwAAZSmQ
From: "KANUMURI Sreeram" <SKanumur@covansys.com>
To: <hector.berna@vodafone.com>, <sipping@ietf.org>
X-OriginalArrivalTime: 15 Dec 2003 09:05:35.0842 (UTC) FILETIME=[9A015420:01C3C2EA]
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

still Push-to-talk is in discussion state and it has no drafts/RFC yet.

Sreeram
-----Original Message-----
From: hector.berna@vodafone.com [mailto:hector.berna@vodafone.com]
Sent: Monday, December 15, 2003 2:16 PM
To: sipping@ietf.org
Subject: [Sipping] Push-to-Talk specifications


Hello,

I would like to know if there is any RFC or Draft that states the =
specifications of the Push-to-Talk
service.

Thanks in advance,

Hector Berna




.........................................................................=
.........................................................................=
.........................................................................=
.......


Confidencialidad


Este  correo  electr=F3nico  y,  en su caso, cualquier fichero anexo al =
mismo, contiene informaci=F3n de
car=E1cter  confidencial  exclusivamente  dirigida  a  su  destinatario =
o destinatarios y propiedad de
Vodafone  Espa=F1a.  Queda  prohibida  su  divulgaci=F3n,  copia o =
distribuci=F3n a terceros sin la previa
autorizaci=F3n  escrita  de  Vodafone Espa=F1a, en virtud de la =
legislaci=F3n vigente. En el caso de haber
recibido  este  correo  electr=F3nico  por error, se ruega notificar =
inmediatamente esta circunstancia
mediante reenv=EDo a la direcci=F3n electr=F3nica del remitente y la =
destrucci=F3n del mismo.


Confidentiality


The  information in this e-mail and in any attachments is classified as =
Vodafone Espa=F1a Confidential
and  Proprietary Information and solely for the attention and use of the =
named addressee(s). You are
hereby  notified  that  any  dissemination, distribution or copy of this =
communication is prohibited
without  the  prior  written consent of Vodafone Espa=F1a and it is =
strictly prohibited by law. If you
have received this communication by error, please, notify the sender by =
replying e-mail.



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

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



From exim@www1.ietf.org  Mon Dec 15 08:33:41 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07634
	for <sipping-archive@odin.ietf.org>; Mon, 15 Dec 2003 08:33:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVsqW-0002v5-G9
	for sipping-archive@odin.ietf.org; Mon, 15 Dec 2003 08:33:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBFDXCR4011217
	for sipping-archive@odin.ietf.org; Mon, 15 Dec 2003 08:33:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVsqW-0002uq-Cq
	for sipping-web-archive@optimus.ietf.org; Mon, 15 Dec 2003 08:33:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07627
	for <sipping-web-archive@ietf.org>; Mon, 15 Dec 2003 08:33:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVsqV-0004V1-00
	for sipping-web-archive@ietf.org; Mon, 15 Dec 2003 08:33:11 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVsqU-0004Uy-00
	for sipping-web-archive@ietf.org; Mon, 15 Dec 2003 08:33:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVsqL-0002ti-Fg; Mon, 15 Dec 2003 08:33:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVspO-0002sK-So
	for sipping@optimus.ietf.org; Mon, 15 Dec 2003 08:32:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07596
	for <sipping@ietf.org>; Mon, 15 Dec 2003 08:32:01 -0500 (EST)
From: hector.berna@vodafone.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVspN-0004Ty-00
	for sipping@ietf.org; Mon, 15 Dec 2003 08:32:01 -0500
Received: from [212.166.209.12] (helo=m2-pasarela3.airtel.es)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVspN-0004Tk-00
	for sipping@ietf.org; Mon, 15 Dec 2003 08:32:01 -0500
To: sipping@ietf.org
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF33972403.ABA5F72A-ONC1256DFD.0049F80F@airtel.es>
Date: Mon, 15 Dec 2003 14:31:33 +0100
X-MIMETrack: Serialize by Router on M2-SMTP3/AIRTEL(Release 5.0.11  |July 24, 2002) at
 12/15/2003 02:32:01 PM
MIME-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Subject: [Sipping] Interworking IPv4 / IPv6 with SIP
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable


Hello,

I am wondering in interworking IPv4 and IPv6  networks.

How does it affect to SIP protocol?

There are several ways to translate from IPv4 to IPv6 and viceversa. Wh=
ich is the best one for SIP?

Thanks in advance.

Kind regards,

Hector Berna


.......................................................................=
.......................................................................=
.......................................................................=
.............


Confidencialidad


Este  correo  electr=F3nico  y,  en su caso, cualquier fichero anexo al=
 mismo, contiene informaci=F3n de
car=E1cter  confidencial  exclusivamente  dirigida  a  su  destinatario=
 o destinatarios y propiedad de
Vodafone  Espa=F1a.  Queda  prohibida  su  divulgaci=F3n,  copia o dist=
ribuci=F3n a terceros sin la previa
autorizaci=F3n  escrita  de  Vodafone Espa=F1a, en virtud de la legisla=
ci=F3n vigente. En el caso de haber
recibido  este  correo  electr=F3nico  por error, se ruega notificar in=
mediatamente esta circunstancia
mediante reenv=EDo a la direcci=F3n electr=F3nica del remitente y la de=
strucci=F3n del mismo.


Confidentiality


The  information in this e-mail and in any attachments is classified as=
 Vodafone Espa=F1a Confidential
and  Proprietary Information and solely for the attention and use of th=
e named addressee(s). You are
hereby  notified  that  any  dissemination, distribution or copy of thi=
s communication is prohibited
without  the  prior  written consent of Vodafone Espa=F1a and it is str=
ictly prohibited by law. If you
have received this communication by error, please, notify the sender by=
 replying e-mail.
=



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



From exim@www1.ietf.org  Mon Dec 15 08:37:35 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07726
	for <sipping-archive@odin.ietf.org>; Mon, 15 Dec 2003 08:37:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVsuH-0003Cl-Sp
	for sipping-archive@odin.ietf.org; Mon, 15 Dec 2003 08:37:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBFDb51q012306
	for sipping-archive@odin.ietf.org; Mon, 15 Dec 2003 08:37:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVsuF-0003AM-4F
	for sipping-web-archive@optimus.ietf.org; Mon, 15 Dec 2003 08:37:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07711
	for <sipping-web-archive@ietf.org>; Mon, 15 Dec 2003 08:37:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVsuD-0004Wm-00
	for sipping-web-archive@ietf.org; Mon, 15 Dec 2003 08:37:01 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVsuD-0004Wj-00
	for sipping-web-archive@ietf.org; Mon, 15 Dec 2003 08:37:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVsuC-00037z-MZ; Mon, 15 Dec 2003 08:37:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVstd-00036w-0e
	for sipping@optimus.ietf.org; Mon, 15 Dec 2003 08:36:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07705
	for <sipping@ietf.org>; Mon, 15 Dec 2003 08:36:22 -0500 (EST)
From: john.loughney@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVstb-0004WZ-00
	for sipping@ietf.org; Mon, 15 Dec 2003 08:36:23 -0500
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVsta-0004WW-00
	for sipping@ietf.org; Mon, 15 Dec 2003 08:36:23 -0500
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hBFDaKH21620
	for <sipping@ietf.org>; Mon, 15 Dec 2003 15:36:21 +0200 (EET)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6686f041aeac158f2492c@esvir04nok.ntc.nokia.com>;
 Mon, 15 Dec 2003 15:35:56 +0200
Received: from esebe023.NOE.Nokia.com ([172.21.138.115]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Mon, 15 Dec 2003 15:35:56 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] Interworking IPv4 / IPv6 with SIP
Date: Mon, 15 Dec 2003 15:35:55 +0200
Message-ID: <DADF50F5EC506B41A0F375ABEB320636A8BD47@esebe023.ntc.nokia.com>
Thread-Topic: [Sipping] Interworking IPv4 / IPv6 with SIP
Thread-Index: AcPDEAhkzDJO8JBwT2a8Qh+Lc8c63gAACXIw
To: <hector.berna@vodafone.com>, <sipping@ietf.org>
X-OriginalArrivalTime: 15 Dec 2003 13:35:56.0428 (UTC) FILETIME=[5E3A54C0:01C3C310]
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hector,

> I am wondering in interworking IPv4 and IPv6  networks.
>=20
> How does it affect to SIP protocol?
>=20
> There are several ways to translate from IPv4 to IPv6 and=20
> viceversa. Which is the best one for SIP?

You might like to look at V6OPS wg:
http://www.ietf.org/html.charters/v6ops-charter.html

Some relevant documents are:

Transition Scenarios for 3GPP Networks (RFC 3574)=20
http://www.ietf.org/rfc/rfc3574.txt

Analysis on IPv6 Transition in 3GPP Networks
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-3gpp-analysis-07.txt=


There are more documents that might interest you.

John

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



From exim@www1.ietf.org  Mon Dec 15 09:41:55 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09915
	for <sipping-archive@odin.ietf.org>; Mon, 15 Dec 2003 09:41:54 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVtuY-00069a-1F
	for sipping-archive@odin.ietf.org; Mon, 15 Dec 2003 09:41:27 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBFEfPSj023589
	for sipping-archive@odin.ietf.org; Mon, 15 Dec 2003 09:41:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVtuX-00068O-20
	for sipping-web-archive@optimus.ietf.org; Mon, 15 Dec 2003 09:41:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09885
	for <sipping-web-archive@ietf.org>; Mon, 15 Dec 2003 09:41:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVtuV-0005gW-00
	for sipping-web-archive@ietf.org; Mon, 15 Dec 2003 09:41:23 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVtuU-0005gT-00
	for sipping-web-archive@ietf.org; Mon, 15 Dec 2003 09:41:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVtuG-00066S-Qo; Mon, 15 Dec 2003 09:41:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVtth-00065V-OA
	for sipping@optimus.ietf.org; Mon, 15 Dec 2003 09:40:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09856
	for <sipping@ietf.org>; Mon, 15 Dec 2003 09:40:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVttf-0005fT-00
	for sipping@ietf.org; Mon, 15 Dec 2003 09:40:31 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVttf-0005f9-00
	for sipping@ietf.org; Mon, 15 Dec 2003 09:40:31 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA18559;
	Mon, 15 Dec 2003 09:39:08 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA09761;
	Mon, 15 Dec 2003 09:39:07 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <W9W8FTMA>; Mon, 15 Dec 2003 09:39:07 -0500
Message-ID: <313680C9A886D511A06000204840E1CF070B61ED@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: =?iso-8859-1?Q?=27PROUVOST_S=E9bastien_FTRD/DAC/ISS=27?=
	 <sebastien.prouvost@francetelecom.com>
Cc: sipping@ietf.org, jmpolk@cisco.com
Subject: RE: RE : RE : [sipping] comment on draft-polk-sipping-location-re
	quirements-01.txt
Date: Mon, 15 Dec 2003 09:39:06 -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: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

S=E9bastien

Presently, there are no phones with any support at all for emergency
calls, nor any but a very few proxy servers.  We are now defining=20
how they should work.  This will require changes in UAs and servers=20
eventually.  There will need to be a transition plan, which would=20
allow older system components to work.  Such a transition plan would=20
have to start with the existing emergency calling system, and work=20
forward to what we eventually want.

I think having the phone know its location is not difficult, even=20
for very inexpensive phones, and is very useful.  It is also best,
where emergency services is concerned, to have simple rules, without
a lot of options.  Having some phones know where they are, with
others reliant on some kind of proxy action creates the kind of
incompatibilities that could cause serious harm.  I would prefer to
have ONE way, even if this makes one more piece of work in the
transition plan.

Brian

> -----Original Message-----
> From: PROUVOST S=E9bastien FTRD/DAC/ISS
> [mailto:sebastien.prouvost@francetelecom.com]
> Sent: Monday, December 15, 2003 8:54 AM
> To: Rosen, Brian
> Cc: sipping@ietf.org; jmpolk@cisco.com
> Subject: RE : RE : [sipping] comment on
> draft-polk-sipping-location-requirements-01.txt
>=20
>=20
> Brian,
>=20
> In a context as sensible as emergency services, we cannot=20
> rely only on terminal capabilities. We shall be able to=20
> rescue a person making an emergency call even if its terminal=20
> does not support such and such options.
>=20
> S=E9bastien Prouvost
> France T=E9l=E9com R&D/DAC/CAR
> http://www.francetelecom.com/rd
>=20
> -----Message d'origine-----
> De : Rosen, Brian [mailto:Brian.Rosen@marconi.com]=20
> Envoy=E9 : vendredi 12 d=E9cembre 2003 19:39
> =C0 : PROUVOST S=E9bastien FTRD/DAC/ISS
> Cc : sipping@ietf.org; jmpolk@cisco.com
> Objet : RE: RE : [sipping] comment on=20
> draft-polk-sipping-location-requirements-01.txt
>=20
>=20
> S=E9bastien
>=20
> When would there be a situation where the terminal is not
> able to obtain its own location?  Are you arguing on=20
> technical grounds or business reasons? =20
>=20
> If the international standards for VoIP emergency calls=20
> were structured so that UAs were informed of their location,=20
> and included that information on an emergency call, would you=20
> still worry that some country would impose regulations=20
> requiring a carrier to insert location?  If that happened,=20
> would you expect the IETF to change the specifications?
>=20
> Don't you see that the mechanism for having proxy insertion=20
> PLUS mechanisms for UAs to request that proxies not insert is=20
> more complicated, without having a compelling technical advantage?
>=20
> Brian
>=20
> > -----Original Message-----
> > From: PROUVOST S=E9bastien FTRD/DAC/ISS
> > [mailto:sebastien.prouvost@francetelecom.com]
> > Sent: Friday, December 12, 2003 1:30 PM
> > To: Rosen, Brian
> > Cc: sipping@ietf.org; jmpolk@cisco.com
> > Subject: RE : [sipping] comment on=20
> > draft-polk-sipping-location-requirements-01.txt
> >=20
> >=20
> > Well, I still believe that the cases where the terminal will not be =

> > able to get information shall be covered and that a proxy should be =

> > allowed to insert this information in such a case (if it is able to =

> > obtain it).
> > =20
> > If not, there is a significant issue with emergency calls :=20
> it may be=20
> > a regulatory obligation for an operator to make this location=20
> > information available.
> >=20
> > I also agree that privacy considerations regarding the=20
> divulgation of=20
> > location information is important and that except for=20
> emergency calls=20
> > this information shall not be delivered to any entity without the=20
> > agreement of the UA. If a proxy in the path is allowed to=20
> insert the=20
> > info, this shall lead to the additionnal requirement that a=20
> UA shall=20
> > be able to inform proxies in the path whether of not they are
> > allowed to insert this information.
> > =20
> > =20
> > Regards,
> >=20
> > S=E9bastien Prouvost
> > France T=E9l=E9com R&D/DAC/CAR
> > http://www.francetelecom.com/rd
> >=20
> > -----Message d'origine-----
> > De : Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> > Envoy=E9 : vendredi 12 d=E9cembre 2003 14:03
> > =C0 : PROUVOST S=E9bastien FTRD/DAC/ISS
> > Cc : sipping@ietf.org; jmpolk@cisco.com
> > Objet : RE: [sipping] comment on
> > draft-polk-sipping-location-requirements-01.txt
> >=20
> >=20
> > I think that the issue is one of privacy control.  If some=20
> > intermediary puts your location on the message without your=20
> consent,=20
> > there is a significant breach of privacy.
> >=20
> > The emergency case is somewhat different, and we are=20
> looking into how=20
> > best to accommodate it.  In general, our approach is to get=20
> the UA to=20
> > know its location and report it with the call.  We understand the=20
> > issue of authentication of location, and will need to=20
> assure that the=20
> > location is accurate
> > when a carrier knows what it is.   If the location is
> > provided to the UA, and it chooses to NOT send it, I=20
> believe he should=20
> > be allowed to do so.  There are several ways the UA could learn its =

> > location from some other entity.  One of them is DHCP (for a=20
> > non-mobile UA).
> >=20
> > Do you see any problem with that approach?
> >=20
> > Brian
> >=20
> > > -----Original Message-----
> > > From: PROUVOST S=E9bastien FTRD/DAC/ISS
> > > [mailto:sebastien.prouvost@francetelecom.com]
> > > Sent: Monday, December 08, 2003 10:10 AM
> > > To: jmpolk@cisco.com; Brian.rosen@marconi.com
> > > Cc: sipping@ietf.org
> > > Subject: [sipping] comment on
> > > draft-polk-sipping-location-requirements-01.txt
> > >=20
> > >=20
> > > Hi,
> > >=20
> > > I fully support the idea of having location information=20
> conveyed in=20
> > > SIP.
> > >=20
> > > However, I fail to see in the draft a requirement for a=20
> proxy to be=20
> > > able to insert the location object on behalf of the UA. It
> > is likely
> > > that in some cases terminals may not have this=20
> information. In some=20
> > > architectures, an outbound proxy may be able to retrieve this=20
> > > information (eg. Through a MIDCOM or COPS interface with an
> > entity in
> > > the transport plane) and it is useful to allow such an
> > outbound proxy
> > > to insert this location object.
> > >=20
> > > As stated in requirement E-3 regarding emergency calls,=20
> it may be a=20
> > > regulatory obligation for an operator to make this location=20
> > > information available to certain users. Operators may=20
> therefore be=20
> > > mandated to have this information inserted by proxies if
> > the terminal
> > > does not insert it.
> > >=20
> > > Regards,
> > >=20
> > > S=E9bastien Prouvost
> > > France T=E9l=E9com R&D/DAC/CAR
> > > http://www.francetelecom.com/rd
> > >=20
> > >=20
> > > _______________________________________________
> > > Sipping mailing list =20
> https://www1.ietf.org/mailman/listinfo/sipping
> > > This list is for NEW development of the application of SIP Use
> > > sip-implementors@cs.columbia.edu for questions on current sip Use =

> > > sip@ietf.org for new developments of core SIP
> > >=20
> >=20
>=20

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



From exim@www1.ietf.org  Mon Dec 15 15:30:43 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26197
	for <sipping-archive@odin.ietf.org>; Mon, 15 Dec 2003 15:30:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVzM7-0005Iw-7d
	for sipping-archive@odin.ietf.org; Mon, 15 Dec 2003 15:30:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBFKUFww020384
	for sipping-archive@odin.ietf.org; Mon, 15 Dec 2003 15:30:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVzM7-0005Ih-37
	for sipping-web-archive@optimus.ietf.org; Mon, 15 Dec 2003 15:30:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26141
	for <sipping-web-archive@ietf.org>; Mon, 15 Dec 2003 15:30:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVzM5-0005Jx-00
	for sipping-web-archive@ietf.org; Mon, 15 Dec 2003 15:30:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AVzM4-0005Jo-00
	for sipping-web-archive@ietf.org; Mon, 15 Dec 2003 15:30:13 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVzM4-0005Ji-00
	for sipping-web-archive@ietf.org; Mon, 15 Dec 2003 15:30:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVzLx-0005Ez-LF; Mon, 15 Dec 2003 15:30:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVzLJ-0005DS-I7
	for sipping@optimus.ietf.org; Mon, 15 Dec 2003 15:29:25 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26053;
	Mon, 15 Dec 2003 15:29:23 -0500 (EST)
Message-Id: <200312152029.PAA26053@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: Mon, 15 Dec 2003 15:29:23 -0500
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-mwi-04.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,MIME_BOUND_NEXTPART,
	NO_REAL_NAME autolearn=no version=2.60

--NextPart

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

	Title		: A Message Summary and Message Waiting Indication 
			  Event Package for the Session Initiation Protocol (SIP)
	Author(s)	: R. Mahy
	Filename	: draft-ietf-sipping-mwi-04.txt
	Pages		: 22
	Date		: 2003-12-15
	
This draft proposes a SIP event package to carry message waiting
status and message summaries from a messaging system to an interested
User Agent.

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-mwi-04.txt

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

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

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Tue Dec 16 05:18:50 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08024
	for <sipping-archive@odin.ietf.org>; Tue, 16 Dec 2003 05:18:50 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWCHW-0002S0-Jw
	for sipping-archive@odin.ietf.org; Tue, 16 Dec 2003 05:18:22 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBGAIMnm009414
	for sipping-archive@odin.ietf.org; Tue, 16 Dec 2003 05:18:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWCHU-0002Rl-D3
	for sipping-web-archive@optimus.ietf.org; Tue, 16 Dec 2003 05:18:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08020
	for <sipping-web-archive@ietf.org>; Tue, 16 Dec 2003 05:18:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWCHQ-0000xt-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 05:18:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWCHP-0000xk-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 05:18:16 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWCHP-0000xh-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 05:18:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWCHF-0002QC-CX; Tue, 16 Dec 2003 05:18:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWCGF-0002Mx-KU
	for sipping@optimus.ietf.org; Tue, 16 Dec 2003 05:17:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07915
	for <sipping@ietf.org>; Tue, 16 Dec 2003 05:16:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWCG5-0000tc-00
	for sipping@ietf.org; Tue, 16 Dec 2003 05:16:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWCFp-0000tS-00
	for sipping@ietf.org; Tue, 16 Dec 2003 05:16:38 -0500
Received: from ihemail2.lucent.com ([192.11.222.163] helo=ihemail2.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWCFo-0000qT-00
	for sipping@ietf.org; Tue, 16 Dec 2003 05:16:36 -0500
Received: from uk0006exch001h.wins.lucent.com (h135-86-145-57.lucent.com [135.86.145.57])
	by ihemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id hBGAFdG25514
	for <sipping@ietf.org>; Tue, 16 Dec 2003 04:15:40 -0600 (CST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2657.72)
	id <Y9ZVHYAV>; Tue, 16 Dec 2003 10:15:38 -0000
Message-ID: <475FF955A05DD411980D00508B6D5FB00439EF6A@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: "'Rosen, Brian'" <Brian.Rosen@marconi.com>,
        =?iso-8859-1?Q?=27PROUV?=
	=?iso-8859-1?Q?OST_S=E9bastien_FTRD/DAC/ISS=27?=
	 <sebastien.prouvost@francetelecom.com>
Cc: sipping@ietf.org, jmpolk@cisco.com
Subject: RE: RE : RE : [sipping] comment on draft-polk-sipping-location-re
	 quirements-01.txt
Date: Tue, 16 Dec 2003 10:15:36 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

I would suggest that even if the terminal information is not =
necessarily reliable, the emergency call centres will still require it =
if it is available.

It is then up to the emergency centre (and its staff) to make a =
judgement call as to its reliability, in the context of other =
information provided by outbound proxies and other SIP servers.

regards

Keith

> -----Original Message-----
> From: Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> Sent: 15 December 2003 14:39
> To: 'PROUVOST S=E9bastien FTRD/DAC/ISS'
> Cc: sipping@ietf.org; jmpolk@cisco.com
> Subject: RE: RE : RE : [sipping] comment on
> draft-polk-sipping-location-re quirements-01.txt
>=20
>=20
> S=E9bastien
>=20
> Presently, there are no phones with any support at all for emergency
> calls, nor any but a very few proxy servers.  We are now defining=20
> how they should work.  This will require changes in UAs and servers=20
> eventually.  There will need to be a transition plan, which would=20
> allow older system components to work.  Such a transition plan would=20
> have to start with the existing emergency calling system, and work=20
> forward to what we eventually want.
>=20
> I think having the phone know its location is not difficult, even=20
> for very inexpensive phones, and is very useful.  It is also best,
> where emergency services is concerned, to have simple rules, without
> a lot of options.  Having some phones know where they are, with
> others reliant on some kind of proxy action creates the kind of
> incompatibilities that could cause serious harm.  I would prefer to
> have ONE way, even if this makes one more piece of work in the
> transition plan.
>=20
> Brian
>=20
> > -----Original Message-----
> > From: PROUVOST S=E9bastien FTRD/DAC/ISS
> > [mailto:sebastien.prouvost@francetelecom.com]
> > Sent: Monday, December 15, 2003 8:54 AM
> > To: Rosen, Brian
> > Cc: sipping@ietf.org; jmpolk@cisco.com
> > Subject: RE : RE : [sipping] comment on
> > draft-polk-sipping-location-requirements-01.txt
> >=20
> >=20
> > Brian,
> >=20
> > In a context as sensible as emergency services, we cannot=20
> > rely only on terminal capabilities. We shall be able to=20
> > rescue a person making an emergency call even if its terminal=20
> > does not support such and such options.
> >=20
> > S=E9bastien Prouvost
> > France T=E9l=E9com R&D/DAC/CAR
> > http://www.francetelecom.com/rd
> >=20
> > -----Message d'origine-----
> > De : Rosen, Brian [mailto:Brian.Rosen@marconi.com]=20
> > Envoy=E9 : vendredi 12 d=E9cembre 2003 19:39
> > =C0 : PROUVOST S=E9bastien FTRD/DAC/ISS
> > Cc : sipping@ietf.org; jmpolk@cisco.com
> > Objet : RE: RE : [sipping] comment on=20
> > draft-polk-sipping-location-requirements-01.txt
> >=20
> >=20
> > S=E9bastien
> >=20
> > When would there be a situation where the terminal is not
> > able to obtain its own location?  Are you arguing on=20
> > technical grounds or business reasons? =20
> >=20
> > If the international standards for VoIP emergency calls=20
> > were structured so that UAs were informed of their location,=20
> > and included that information on an emergency call, would you=20
> > still worry that some country would impose regulations=20
> > requiring a carrier to insert location?  If that happened,=20
> > would you expect the IETF to change the specifications?
> >=20
> > Don't you see that the mechanism for having proxy insertion=20
> > PLUS mechanisms for UAs to request that proxies not insert is=20
> > more complicated, without having a compelling technical advantage?
> >=20
> > Brian
> >=20
> > > -----Original Message-----
> > > From: PROUVOST S=E9bastien FTRD/DAC/ISS
> > > [mailto:sebastien.prouvost@francetelecom.com]
> > > Sent: Friday, December 12, 2003 1:30 PM
> > > To: Rosen, Brian
> > > Cc: sipping@ietf.org; jmpolk@cisco.com
> > > Subject: RE : [sipping] comment on=20
> > > draft-polk-sipping-location-requirements-01.txt
> > >=20
> > >=20
> > > Well, I still believe that the cases where the terminal=20
> will not be=20
> > > able to get information shall be covered and that a proxy=20
> should be=20
> > > allowed to insert this information in such a case (if it=20
> is able to=20
> > > obtain it).
> > > =20
> > > If not, there is a significant issue with emergency calls :=20
> > it may be=20
> > > a regulatory obligation for an operator to make this location=20
> > > information available.
> > >=20
> > > I also agree that privacy considerations regarding the=20
> > divulgation of=20
> > > location information is important and that except for=20
> > emergency calls=20
> > > this information shall not be delivered to any entity without the =

> > > agreement of the UA. If a proxy in the path is allowed to=20
> > insert the=20
> > > info, this shall lead to the additionnal requirement that a=20
> > UA shall=20
> > > be able to inform proxies in the path whether of not they are
> > > allowed to insert this information.
> > > =20
> > > =20
> > > Regards,
> > >=20
> > > S=E9bastien Prouvost
> > > France T=E9l=E9com R&D/DAC/CAR
> > > http://www.francetelecom.com/rd
> > >=20
> > > -----Message d'origine-----
> > > De : Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> > > Envoy=E9 : vendredi 12 d=E9cembre 2003 14:03
> > > =C0 : PROUVOST S=E9bastien FTRD/DAC/ISS
> > > Cc : sipping@ietf.org; jmpolk@cisco.com
> > > Objet : RE: [sipping] comment on
> > > draft-polk-sipping-location-requirements-01.txt
> > >=20
> > >=20
> > > I think that the issue is one of privacy control.  If some=20
> > > intermediary puts your location on the message without your=20
> > consent,=20
> > > there is a significant breach of privacy.
> > >=20
> > > The emergency case is somewhat different, and we are=20
> > looking into how=20
> > > best to accommodate it.  In general, our approach is to get=20
> > the UA to=20
> > > know its location and report it with the call.  We understand the =

> > > issue of authentication of location, and will need to=20
> > assure that the=20
> > > location is accurate
> > > when a carrier knows what it is.   If the location is
> > > provided to the UA, and it chooses to NOT send it, I=20
> > believe he should=20
> > > be allowed to do so.  There are several ways the UA could=20
> learn its=20
> > > location from some other entity.  One of them is DHCP (for a=20
> > > non-mobile UA).
> > >=20
> > > Do you see any problem with that approach?
> > >=20
> > > Brian
> > >=20
> > > > -----Original Message-----
> > > > From: PROUVOST S=E9bastien FTRD/DAC/ISS
> > > > [mailto:sebastien.prouvost@francetelecom.com]
> > > > Sent: Monday, December 08, 2003 10:10 AM
> > > > To: jmpolk@cisco.com; Brian.rosen@marconi.com
> > > > Cc: sipping@ietf.org
> > > > Subject: [sipping] comment on
> > > > draft-polk-sipping-location-requirements-01.txt
> > > >=20
> > > >=20
> > > > Hi,
> > > >=20
> > > > I fully support the idea of having location information=20
> > conveyed in=20
> > > > SIP.
> > > >=20
> > > > However, I fail to see in the draft a requirement for a=20
> > proxy to be=20
> > > > able to insert the location object on behalf of the UA. It
> > > is likely
> > > > that in some cases terminals may not have this=20
> > information. In some=20
> > > > architectures, an outbound proxy may be able to retrieve this=20
> > > > information (eg. Through a MIDCOM or COPS interface with an
> > > entity in
> > > > the transport plane) and it is useful to allow such an
> > > outbound proxy
> > > > to insert this location object.
> > > >=20
> > > > As stated in requirement E-3 regarding emergency calls,=20
> > it may be a=20
> > > > regulatory obligation for an operator to make this location=20
> > > > information available to certain users. Operators may=20
> > therefore be=20
> > > > mandated to have this information inserted by proxies if
> > > the terminal
> > > > does not insert it.
> > > >=20
> > > > Regards,
> > > >=20
> > > > S=E9bastien Prouvost
> > > > France T=E9l=E9com R&D/DAC/CAR
> > > > http://www.francetelecom.com/rd
> > > >=20
> > > >=20
> > > > _______________________________________________
> > > > Sipping mailing list =20
> > https://www1.ietf.org/mailman/listinfo/sipping
> > > > This list is for NEW development of the application of SIP Use
> > > > sip-implementors@cs.columbia.edu for questions on=20
> current sip Use=20
> > > > sip@ietf.org for new developments of core SIP
> > > >=20
> > >=20
> >=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>=20

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



From exim@www1.ietf.org  Tue Dec 16 10:36:33 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17933
	for <sipping-archive@odin.ietf.org>; Tue, 16 Dec 2003 10:36:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHF0-00054A-89
	for sipping-archive@odin.ietf.org; Tue, 16 Dec 2003 10:36:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBGFa6KJ019468
	for sipping-archive@odin.ietf.org; Tue, 16 Dec 2003 10:36:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHF0-00053v-3l
	for sipping-web-archive@optimus.ietf.org; Tue, 16 Dec 2003 10:36:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17868
	for <sipping-web-archive@ietf.org>; Tue, 16 Dec 2003 10:36:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHEx-0004Tu-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 10:36:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWHEw-0004Tm-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 10:36:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHEw-0004Ti-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 10:36:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHEv-00052Z-HM; Tue, 16 Dec 2003 10:36:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHEj-00051k-L0
	for sipping@optimus.ietf.org; Tue, 16 Dec 2003 10:35:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17832
	for <sipping@ietf.org>; Tue, 16 Dec 2003 10:35:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHEh-0004Rt-00
	for sipping@ietf.org; Tue, 16 Dec 2003 10:35:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWHEd-0004RN-00
	for sipping@ietf.org; Tue, 16 Dec 2003 10:35:47 -0500
Received: from [65.246.255.50] (helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHEd-0004Pg-00
	for sipping@ietf.org; Tue, 16 Dec 2003 10:35:43 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by manatick with esmtp (Exim 4.24)
	id 1AWGvx-0001W5-Dw
	for sipping@ietf.org; Tue, 16 Dec 2003 10:16:25 -0500
Received: from esealnt612.al.sw.ericsson.se ([153.88.254.118])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8) with ESMTP id hBGFGMI2027015;
	Tue, 16 Dec 2003 16:16:22 +0100 (MET)
Received: by esealnt612.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <ZAP90BDH>; Tue, 16 Dec 2003 16:16:22 +0100
Message-ID: <37FB7AA6F5F9814FB634A7BF4C35A6F56399AB@ESEALNT442.al.sw.ericsson.se>
From: "Karim El-Malki (HF/EAB)" <karim.el-malki@ericsson.com>
To: "'hector.berna@vodafone.com'" <hector.berna@vodafone.com>,
        sipping@ietf.org
Subject: RE: [Sipping] Interworking IPv4 / IPv6 with SIP
Date: Mon, 15 Dec 2003 15:47:55 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

 > Hello,
 > 
 > I am wondering in interworking IPv4 and IPv6  networks.
 > 
 > How does it affect to SIP protocol?
 > 
 > There are several ways to translate from IPv4 to IPv6 and 
 > viceversa. Which is the best one for SIP?

If you are interested in 3gpp sip-based ims this draft may help:
http://www.ietf.org/internet-drafts/draft-elmalki-sipping-3gpp-translator-00.txt

/Karim

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



From exim@www1.ietf.org  Tue Dec 16 10:42:36 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19136
	for <sipping-archive@odin.ietf.org>; Tue, 16 Dec 2003 10:42:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHKU-0006IS-UD
	for sipping-archive@odin.ietf.org; Tue, 16 Dec 2003 10:41:47 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBGFfkb8024198
	for sipping-archive@odin.ietf.org; Tue, 16 Dec 2003 10:41:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHKU-0006ID-Qo
	for sipping-web-archive@optimus.ietf.org; Tue, 16 Dec 2003 10:41:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18955
	for <sipping-web-archive@ietf.org>; Tue, 16 Dec 2003 10:41:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHKS-0005Te-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 10:41:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWHK4-0005Pv-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 10:41:42 -0500
Received: from [65.246.255.50] (helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHK2-0005Pc-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 10:41:18 -0500
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by manatick with esmtp (Exim 4.24)
	id 1AWHJt-00031A-Dd
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 10:41:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHJo-00067C-LJ; Tue, 16 Dec 2003 10:41:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHJg-00065H-7u
	for sipping@optimus.ietf.org; Tue, 16 Dec 2003 10:40:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18804
	for <sipping@ietf.org>; Tue, 16 Dec 2003 10:40:52 -0500 (EST)
From: Mpierce1@aol.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHJd-0005Kw-00
	for sipping@ietf.org; Tue, 16 Dec 2003 10:40:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWHJH-0005HR-00
	for sipping@ietf.org; Tue, 16 Dec 2003 10:40:52 -0500
Received: from [65.246.255.50] (helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHHV-0004jS-00
	for sipping@ietf.org; Tue, 16 Dec 2003 10:38:41 -0500
Received: from imo-m03.mx.aol.com ([64.12.136.6])
	by manatick with esmtp (Exim 4.24)
	id 1AWFO0-0006KN-Pm
	for sipping@ietf.org; Tue, 16 Dec 2003 08:37:16 -0500
Received: from Mpierce1@aol.com
	by imo-m03.mx.aol.com (mail_out_v36_r4.8.) id e.155.29ab4d4f (4246);
	Tue, 16 Dec 2003 08:35:00 -0500 (EST)
Message-ID: <155.29ab4d4f.2d106403@aol.com>
Date: Tue, 16 Dec 2003 08:34:59 EST
Subject: Re: [sipping] comment on draft-polk-sipping-location-requirements -01.txt
To: Brian.Rosen@marconi.com, taylor@nortelnetworks.com
CC: sebastien.prouvost@francetelecom.com, sipping@ietf.org, jmpolk@cisco.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_155.29ab4d4f.2d106403_boundary"
X-Mailer: 6.0 for Windows XP sub 10501
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=HTML_MESSAGE,NO_REAL_NAME 
	autolearn=no version=2.60


--part1_155.29ab4d4f.2d106403_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 12/12/2003 10:14:07 AM Eastern Standard Time, 
Brian.Rosen@marconi.com writes:


> There is a considerable amount of pressure by those who are
> concerned about privacy to keep location information under
> very tight control.  One attempt to deal with location in the
> IETF went down in flames, and the present one has 90% of
> its efforts directed to privacy and 10% to location.
> 
> This is a reality we have to deal with, or we aren't going
> to get anything through the process.
> 

Unfortunately, I don't believe that the previous attempt (or the present one 
in GEOPRIV) is concerned with "the reality" of the situation. It continues to 
believe that it will somehow be forever exempt from government regulations, so 
it can ignore "reality".

The truth is, today I can not make a 911 call in the US and expect to keep my 
location private (from the service provider or the emergency service 
provider). In fact, recent regulations are closing the gap where exact locatoin was 
not being provided due to technical limitations, such as for cellular and PBXs.

Yes, one needs to be concerned with privacy, but the requirements of 
emergency calling (e.g., 911) override this pricavy because of government 
requirements. (I know, many in this effort want to ignore govenments, but they still 
exist, and probablu will for some time.) If the UA doesn't know it's location and 
report it, then an entity that claims to provide telephone service must provide 
that location information.

Now that I've inflamed this discssuion more with the truth ...

Mike


--part1_155.29ab4d4f.2d106403_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<HTML><FONT FACE=3Darial,helvetica><FONT  SIZE=3D2 PTSIZE=3D10>In a message=20=
dated 12/12/2003 10:14:07 AM Eastern Standard Time, Brian.Rosen@marconi.com=20=
writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-=
LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">There is a considerable amo=
unt of pressure by those who are
<BR>concerned about privacy to keep location information under
<BR>very tight control. &nbsp;One attempt to deal with location in the
<BR>IETF went down in flames, and the present one has 90% of
<BR>its efforts directed to privacy and 10% to location.
<BR>
<BR>This is a reality we have to deal with, or we aren't going
<BR>to get anything through the process.
<BR></FONT><FONT  COLOR=3D"#000000" BACK=3D"#ffffff" style=3D"BACKGROUND-COL=
OR: #ffffff" SIZE=3D3 PTSIZE=3D12 FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=
=3D"0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR=3D"#000000" BACK=3D"#ffffff" style=3D"BACKGROUND-COL=
OR: #ffffff" SIZE=3D2 PTSIZE=3D10 FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=
=3D"0">
<BR>Unfortunately, I don't believe that the previous attempt (or the present=
 one in GEOPRIV) is concerned with "the reality" of the situation. It contin=
ues to believe that it will somehow be forever exempt from government regula=
tions, so it can ignore "reality".
<BR>
<BR>The truth is, today I can not make a 911 call in the US and expect to ke=
ep my location private (from the service provider or the emergency service p=
rovider). In fact, recent regulations are closing the gap where exact locato=
in was not being provided due to technical limitations, such as for cellular=
 and PBXs.
<BR>
<BR>Yes, one needs to be concerned with privacy, but the requirements of eme=
rgency calling (e.g., 911) override this pricavy because of government requi=
rements. (I know, many in this effort want to ignore govenments, but they st=
ill exist, and probablu will for some time.) If the UA doesn't know it's loc=
ation and report it, then an entity that claims to provide telephone service=
 must provide that location information.
<BR>
<BR>Now that I've inflamed this discssuion more with the truth ...
<BR>
<BR>Mike
<BR></FONT></HTML>

--part1_155.29ab4d4f.2d106403_boundary--

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



From exim@www1.ietf.org  Tue Dec 16 10:55:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20893
	for <sipping-archive@odin.ietf.org>; Tue, 16 Dec 2003 10:55:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHXD-0007xf-9V
	for sipping-archive@odin.ietf.org; Tue, 16 Dec 2003 10:54:55 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBGFstMJ030597
	for sipping-archive@odin.ietf.org; Tue, 16 Dec 2003 10:54:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHXD-0007xQ-63
	for sipping-web-archive@optimus.ietf.org; Tue, 16 Dec 2003 10:54:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20778
	for <sipping-web-archive@ietf.org>; Tue, 16 Dec 2003 10:54:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHXA-0007PM-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 10:54:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWHX1-0007Ni-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 10:54:51 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHX0-0007NO-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 10:54:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHOn-0006mM-9d; Tue, 16 Dec 2003 10:46:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVtZF-00056y-9v
	for sipping@optimus.ietf.org; Mon, 15 Dec 2003 09:19:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08807
	for <sipping@ietf.org>; Mon, 15 Dec 2003 09:19:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVtZC-00059p-00
	for sipping@ietf.org; Mon, 15 Dec 2003 09:19:22 -0500
Received: from mailhub.fokus.fraunhofer.de ([193.174.154.14])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVtZA-00059Z-00
	for sipping@ietf.org; Mon, 15 Dec 2003 09:19:20 -0500
Received: from dhcp105.fokus.fraunhofer.de (dhcp105 [195.37.78.105])
	by mailhub.fokus.fraunhofer.de (8.11.6p2/8.11.6) with ESMTP id hBFEIpc07687;
	Mon, 15 Dec 2003 15:18:51 +0100 (MET)
Date: Mon, 15 Dec 2003 15:22:40 +0100
From: Dorgham Sisalem <sisalem@fokus.fraunhofer.de>
X-Mailer: The Bat! (v1.51) Personal
Reply-To: Dorgham Sisalem <sisalem@fokus.fraunhofer.de>
Organization: FhG Fokus
X-Priority: 3 (Normal)
Message-ID: <189174130386.20031215152240@fokus.fraunhofer.de>
To: hector.berna@vodafone.com
CC: sipping@ietf.org
Subject: Re: [Sipping] Interworking IPv4 / IPv6 with SIP
In-Reply-To: <OF33972403.ABA5F72A-ONC1256DFD.0049F80F@airtel.es>
References: <OF33972403.ABA5F72A-ONC1256DFD.0049F80F@airtel.es>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mailhub.fokus.fraunhofer.de id hBFEIpc07687
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hello,


check  www.fokus.fhg.de/mobis/publ/Sisa0301:SIP.pdf for
a paper describing a translation possibility.
the SIP implementation under www.iptel.org/ser is capable
of translating between the two worlds

cheers

Monday, December 15, 2003, 2:31:33 PM, you wrote:


> Hello,

> I am wondering in interworking IPv4 and IPv6  networks.

> How does it affect to SIP protocol?

> There are several ways to translate from IPv4 to IPv6 and viceversa. Wh=
ich is the best one for SIP?

> Thanks in advance.

> Kind regards,

> Hector Berna


> .......................................................................=
.........................................................................=
.........................................................................=
.........


> Confidencialidad


> Este  correo  electr=F3nico  y,  en su caso, cualquier fichero anexo al=
 mismo, contiene informaci=F3n de
> car=E1cter  confidencial  exclusivamente  dirigida  a  su  destinatario=
 o destinatarios y propiedad de
> Vodafone  Espa=F1a.  Queda  prohibida  su  divulgaci=F3n,  copia o dist=
ribuci=F3n a terceros sin la previa
> autorizaci=F3n  escrita  de  Vodafone Espa=F1a, en virtud de la legisla=
ci=F3n vigente. En el caso de haber
> recibido  este  correo  electr=F3nico  por error, se ruega notificar in=
mediatamente esta circunstancia
> mediante reenv=EDo a la direcci=F3n electr=F3nica del remitente y la de=
strucci=F3n del mismo.


> Confidentiality


> The  information in this e-mail and in any attachments is classified as=
 Vodafone Espa=F1a Confidential
> and  Proprietary Information and solely for the attention and use of th=
e named addressee(s). You are
> hereby  notified  that  any  dissemination, distribution or copy of thi=
s communication is prohibited
> without  the  prior  written consent of Vodafone Espa=F1a and it is str=
ictly prohibited by law. If you
> have received this communication by error, please, notify the sender by=
 replying e-mail.



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



--=20
Best regards,
 Dorgham                            mailto:sisalem@fokus.fraunhofer.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 exim@www1.ietf.org  Tue Dec 16 11:04:33 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21424
	for <sipping-archive@odin.ietf.org>; Tue, 16 Dec 2003 11:04:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHg6-0008NZ-Vc
	for sipping-archive@odin.ietf.org; Tue, 16 Dec 2003 11:04:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBGG46NT032203
	for sipping-archive@odin.ietf.org; Tue, 16 Dec 2003 11:04:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHg6-0008NI-Qv
	for sipping-web-archive@optimus.ietf.org; Tue, 16 Dec 2003 11:04:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21411
	for <sipping-web-archive@ietf.org>; Tue, 16 Dec 2003 11:04:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHg4-0000HU-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 11:04:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWHg2-0000HG-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 11:04:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHg1-0000HD-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 11:04:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHg1-0008Li-NF; Tue, 16 Dec 2003 11:04:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHf2-0008FY-De
	for sipping@optimus.ietf.org; Tue, 16 Dec 2003 11:03:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21319
	for <sipping@ietf.org>; Tue, 16 Dec 2003 11:02:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHez-0000AI-00
	for sipping@ietf.org; Tue, 16 Dec 2003 11:02:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWHey-0000AB-00
	for sipping@ietf.org; Tue, 16 Dec 2003 11:02:57 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHey-00008z-00
	for sipping@ietf.org; Tue, 16 Dec 2003 11:02:56 -0500
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com [64.102.16.27])
	by rtp-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hBGG2Jxi025161;
	Tue, 16 Dec 2003 11:02:21 -0500 (EST)
Received: from mhammer-w2k03.cisco.com (dhcp-hrn-64-100-229-166.cisco.com [64.100.229.166])
	by fruitpie.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AVR43625;
	Tue, 16 Dec 2003 08:02:18 -0800 (PST)
Message-Id: <4.3.2.7.2.20031216104824.00b22098@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 16 Dec 2003 11:02:18 -0500
To: dick.rr.knight@bt.com
From: Michael Hammer <mhammer@cisco.com>
Subject: RE: [sipping] comment on
  draft-polk-sipping-location-requirements-01.txt
Cc: <Brian.Rosen@marconi.com>, <sebastien.prouvost@francetelecom.com>,
        <sipping@ietf.org>, <jmpolk@cisco.com>
In-Reply-To: <E0E9F9BE940EFC4186DB15A079FF315025329F@i2km35-ukdy.domain1
 .systemhost.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Dick,

Not sure how it is in the UK or elsewhere, but in the US court cases have=20
already  established that a caller to a 911 number has no right to privacy=
=20
by the very nature of who they called.  In other words the act of calling=20
911 waives those privacy rights.

But, to clarify an important point you bring out below, there may be=20
multiple sources of the location information with varying degrees of=20
accuracy.  A network based solution may be less accurate than say a GPS=20
built into a mobile phone.  The network could be providing location service=
=20
to the phone, which in turn reflects that location back in a 911/112=20
call.  So, depending on circumstance there could be 2 measurements, with=20
different degrees or accuracy due to tampering or just the difficulty of=20
measuring.

I think it would be a mistake if the proxy over-wrote the location provided=
=20
by the handset, if in fact the handset had better accuracy, or if the proxy=
=20
had faulty data.  Best to provide both measurements to the emergency=20
center.  If the locations agree, then they have a higher degree of=20
confidence in the data.  If they disagree severely, then they could suspect=
=20
tampering.  But, it could just be the odd canyon-effects some mobiles=20
experience in cities with tall smooth symmetrically-aligned buildings (i.e.=
=20
the canyon).  Legal consequences must deal with the former.

It would be bad if the network had a bad location measurement, the phone=20
had a correct one, and the network suppressed it.  Could present liability=
=20
problems for that network operator.

Mike


At 01:56 PM 12/16/2003 +0000, dick.rr.knight@bt.com wrote:
>I think there is a mix up here.
>
>Location is needed for two reasons:
>Firstly to determine the correct emergency answering operator.
>Secondly to determine where to send the emergency response.
>
>If we don't get the first one right then there is no chance of even being=
=20
>close on the second.
>
>But there is another requirement: avoiding abuse.
>
>It is well known that calling the fire brigade and claiming there is a=20
>fire at the cremetorium is a supposedly funny gag that puts lives at risk=
=20
>(as the emergency services must respond).
>Security is important in authorisation and location determination to=20
>ensure that the information given is consistent.
>
>There are times when the terminal knows that it is not where the Proxy=20
>thinks it is, but verification by the first proxy is an important factor=20
>in verifying that this looks as though it is a genuine emergency call.
>
>Hence I conclude that the Proxy SHOULD be allowed to insert location=20
>information (suitably protected) in order to assist in the verification=20
>process. Also the teminal needs to be able to indicate that the proxy is=20
>probably wrong (e.g. connected via a secure VPN tunnel to corporate=
 intranet).
>
>Privacy is important to outsiders but not to a genuine emergency caller=20
>wanting to share their location with an emergency operator (clearly a=20
>trusted entity), and there are advantages in having a proxy verify that=20
>the information is correct. This provides a real improvement to response=20
>times (in the UK) by the emergency services (fire police ambulance etc.).
>
>Dick Knight
>
>-----Original Message-----
>From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]On Behalf Of
>Rosen, Brian
>Sent: 12 December 2003 13:03
>To: 'PROUVOST S=E9bastien FTRD/DAC/ISS'
>Cc: sipping@ietf.org; jmpolk@cisco.com
>Subject: RE: [sipping] comment on
>draft-polk-sipping-location-requirements-01.txt
>
>
>I think that the issue is one of privacy control.  If some
>intermediary puts your location on the message without your
>consent, there is a significant breach of privacy.
>
>The emergency case is somewhat different, and we are looking
>into how best to accommodate it.  In general, our approach
>is to get the UA to know its location and report it with
>the call.  We understand the issue of authentication of
>location, and will need to assure that the location is accurate
>when a carrier knows what it is.   If the location is
>provided to the UA, and it chooses to NOT send it, I believe
>he should be allowed to do so.  There are several ways the UA
>could learn its location from some other entity.  One of them
>is DHCP (for a non-mobile UA).
>
>Do you see any problem with that approach?
>
>Brian
>
> > -----Original Message-----
> > From: PROUVOST S=E9bastien FTRD/DAC/ISS
> > [mailto:sebastien.prouvost@francetelecom.com]
> > Sent: Monday, December 08, 2003 10:10 AM
> > To: jmpolk@cisco.com; Brian.rosen@marconi.com
> > Cc: sipping@ietf.org
> > Subject: [sipping] comment on
> > draft-polk-sipping-location-requirements-01.txt
> >
> >
> > Hi,
> >
> > I fully support the idea of having location information
> > conveyed in SIP.
> >
> > However, I fail to see in the draft a requirement for a proxy
> > to be able to insert the location object on behalf of the UA.
> > It is likely that in some cases terminals may not have this
> > information. In some architectures, an outbound proxy may be
> > able to retrieve this information (eg. Through a MIDCOM or
> > COPS interface with an entity in the transport plane) and it
> > is useful to allow such an outbound proxy to insert this
> > location object.
> >
> > As stated in requirement E-3 regarding emergency calls, it
> > may be a regulatory obligation for an operator to make this
> > location information available to certain users. Operators
> > may therefore be mandated to have this information inserted
> > by proxies if the terminal does not insert it.
> >
> > Regards,
> >
> > S=E9bastien Prouvost
> > France T=E9l=E9com R&D/DAC/CAR
> > http://www.francetelecom.com/rd
> >
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> >
>
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the application of SIP
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sip@ietf.org for new developments of core SIP
>
>_______________________________________________
>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>This list is for NEW development of the application of SIP
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sip@ietf.org for new developments of core SIP


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



From exim@www1.ietf.org  Tue Dec 16 11:07:35 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21591
	for <sipping-archive@odin.ietf.org>; Tue, 16 Dec 2003 11:07:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHj0-0000LN-8V
	for sipping-archive@odin.ietf.org; Tue, 16 Dec 2003 11:07:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBGG76Xi001309
	for sipping-archive@odin.ietf.org; Tue, 16 Dec 2003 11:07:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHiz-0000Iw-F6
	for sipping-web-archive@optimus.ietf.org; Tue, 16 Dec 2003 11:07:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21578
	for <sipping-web-archive@ietf.org>; Tue, 16 Dec 2003 11:07:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHiw-0000Py-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 11:07:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWHiv-0000Pq-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 11:07:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHiu-0000Pn-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 11:07:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHiw-0000E7-BL; Tue, 16 Dec 2003 11:07:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHir-0000DW-TY
	for sipping@optimus.ietf.org; Tue, 16 Dec 2003 11:06:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21572
	for <sipping@ietf.org>; Tue, 16 Dec 2003 11:06:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHip-0000PI-00
	for sipping@ietf.org; Tue, 16 Dec 2003 11:06:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWHim-0000Oz-00
	for sipping@ietf.org; Tue, 16 Dec 2003 11:06:54 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHik-0000Ne-00
	for sipping@ietf.org; Tue, 16 Dec 2003 11:06:52 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA25089;
	Tue, 16 Dec 2003 10:57:59 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA22637;
	Tue, 16 Dec 2003 10:18:41 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <W9W8GTMJ>; Tue, 16 Dec 2003 10:18:41 -0500
Message-ID: <313680C9A886D511A06000204840E1CF070B61F3@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Drage, Keith (Keith)'" <drage@lucent.com>,
        =?iso-8859-1?Q?=27PROU?=
	=?iso-8859-1?Q?VOST_S=E9bastien_FTRD/DAC/ISS=27?=
	 <sebastien.prouvost@francetelecom.com>
Cc: sipping@ietf.org, jmpolk@cisco.com
Subject: RE: RE : RE : [sipping] comment on draft-polk-sipping-location-re
	 quirements-01.txt
Date: Tue, 16 Dec 2003 10:18:40 -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: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

I agree.

Most emergency centers still ask you where you are, even if they have
location.  Some centers do follow up investigations if location was
not provided, or the location differed from that reported by the caller
to see what failed.

Brian

> -----Original Message-----
> From: Drage, Keith (Keith) [mailto:drage@lucent.com]
> Sent: Tuesday, December 16, 2003 5:16 AM
> To: 'Rosen, Brian'; 'PROUVOST S=E9bastien FTRD/DAC/ISS'
> Cc: sipping@ietf.org; jmpolk@cisco.com
> Subject: RE: RE : RE : [sipping] comment on
> draft-polk-sipping-location-re quirements-01.txt
>=20
>=20
> I would suggest that even if the terminal information is not=20
> necessarily reliable, the emergency call centres will still=20
> require it if it is available.
>=20
> It is then up to the emergency centre (and its staff) to make=20
> a judgement call as to its reliability, in the context of=20
> other information provided by outbound proxies and other SIP servers.
>=20
> regards
>=20
> Keith
>=20
> > -----Original Message-----
> > From: Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> > Sent: 15 December 2003 14:39
> > To: 'PROUVOST S=E9bastien FTRD/DAC/ISS'
> > Cc: sipping@ietf.org; jmpolk@cisco.com
> > Subject: RE: RE : RE : [sipping] comment on
> > draft-polk-sipping-location-re quirements-01.txt
> >=20
> >=20
> > S=E9bastien
> >=20
> > Presently, there are no phones with any support at all for =
emergency
> > calls, nor any but a very few proxy servers.  We are now defining=20
> > how they should work.  This will require changes in UAs and servers =

> > eventually.  There will need to be a transition plan, which would=20
> > allow older system components to work.  Such a transition=20
> plan would=20
> > have to start with the existing emergency calling system, and work=20
> > forward to what we eventually want.
> >=20
> > I think having the phone know its location is not difficult, even=20
> > for very inexpensive phones, and is very useful.  It is also best,
> > where emergency services is concerned, to have simple rules, =
without
> > a lot of options.  Having some phones know where they are, with
> > others reliant on some kind of proxy action creates the kind of
> > incompatibilities that could cause serious harm.  I would prefer to
> > have ONE way, even if this makes one more piece of work in the
> > transition plan.
> >=20
> > Brian
> >=20
> > > -----Original Message-----
> > > From: PROUVOST S=E9bastien FTRD/DAC/ISS
> > > [mailto:sebastien.prouvost@francetelecom.com]
> > > Sent: Monday, December 15, 2003 8:54 AM
> > > To: Rosen, Brian
> > > Cc: sipping@ietf.org; jmpolk@cisco.com
> > > Subject: RE : RE : [sipping] comment on
> > > draft-polk-sipping-location-requirements-01.txt
> > >=20
> > >=20
> > > Brian,
> > >=20
> > > In a context as sensible as emergency services, we cannot=20
> > > rely only on terminal capabilities. We shall be able to=20
> > > rescue a person making an emergency call even if its terminal=20
> > > does not support such and such options.
> > >=20
> > > S=E9bastien Prouvost
> > > France T=E9l=E9com R&D/DAC/CAR
> > > http://www.francetelecom.com/rd
> > >=20
> > > -----Message d'origine-----
> > > De : Rosen, Brian [mailto:Brian.Rosen@marconi.com]=20
> > > Envoy=E9 : vendredi 12 d=E9cembre 2003 19:39
> > > =C0 : PROUVOST S=E9bastien FTRD/DAC/ISS
> > > Cc : sipping@ietf.org; jmpolk@cisco.com
> > > Objet : RE: RE : [sipping] comment on=20
> > > draft-polk-sipping-location-requirements-01.txt
> > >=20
> > >=20
> > > S=E9bastien
> > >=20
> > > When would there be a situation where the terminal is not
> > > able to obtain its own location?  Are you arguing on=20
> > > technical grounds or business reasons? =20
> > >=20
> > > If the international standards for VoIP emergency calls=20
> > > were structured so that UAs were informed of their location,=20
> > > and included that information on an emergency call, would you=20
> > > still worry that some country would impose regulations=20
> > > requiring a carrier to insert location?  If that happened,=20
> > > would you expect the IETF to change the specifications?
> > >=20
> > > Don't you see that the mechanism for having proxy insertion=20
> > > PLUS mechanisms for UAs to request that proxies not insert is=20
> > > more complicated, without having a compelling technical =
advantage?
> > >=20
> > > Brian
> > >=20
> > > > -----Original Message-----
> > > > From: PROUVOST S=E9bastien FTRD/DAC/ISS
> > > > [mailto:sebastien.prouvost@francetelecom.com]
> > > > Sent: Friday, December 12, 2003 1:30 PM
> > > > To: Rosen, Brian
> > > > Cc: sipping@ietf.org; jmpolk@cisco.com
> > > > Subject: RE : [sipping] comment on=20
> > > > draft-polk-sipping-location-requirements-01.txt
> > > >=20
> > > >=20
> > > > Well, I still believe that the cases where the terminal=20
> > will not be=20
> > > > able to get information shall be covered and that a proxy=20
> > should be=20
> > > > allowed to insert this information in such a case (if it=20
> > is able to=20
> > > > obtain it).
> > > > =20
> > > > If not, there is a significant issue with emergency calls :=20
> > > it may be=20
> > > > a regulatory obligation for an operator to make this location=20
> > > > information available.
> > > >=20
> > > > I also agree that privacy considerations regarding the=20
> > > divulgation of=20
> > > > location information is important and that except for=20
> > > emergency calls=20
> > > > this information shall not be delivered to any entity=20
> without the=20
> > > > agreement of the UA. If a proxy in the path is allowed to=20
> > > insert the=20
> > > > info, this shall lead to the additionnal requirement that a=20
> > > UA shall=20
> > > > be able to inform proxies in the path whether of not they are
> > > > allowed to insert this information.
> > > > =20
> > > > =20
> > > > Regards,
> > > >=20
> > > > S=E9bastien Prouvost
> > > > France T=E9l=E9com R&D/DAC/CAR
> > > > http://www.francetelecom.com/rd
> > > >=20
> > > > -----Message d'origine-----
> > > > De : Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> > > > Envoy=E9 : vendredi 12 d=E9cembre 2003 14:03
> > > > =C0 : PROUVOST S=E9bastien FTRD/DAC/ISS
> > > > Cc : sipping@ietf.org; jmpolk@cisco.com
> > > > Objet : RE: [sipping] comment on
> > > > draft-polk-sipping-location-requirements-01.txt
> > > >=20
> > > >=20
> > > > I think that the issue is one of privacy control.  If some=20
> > > > intermediary puts your location on the message without your=20
> > > consent,=20
> > > > there is a significant breach of privacy.
> > > >=20
> > > > The emergency case is somewhat different, and we are=20
> > > looking into how=20
> > > > best to accommodate it.  In general, our approach is to get=20
> > > the UA to=20
> > > > know its location and report it with the call.  We=20
> understand the=20
> > > > issue of authentication of location, and will need to=20
> > > assure that the=20
> > > > location is accurate
> > > > when a carrier knows what it is.   If the location is
> > > > provided to the UA, and it chooses to NOT send it, I=20
> > > believe he should=20
> > > > be allowed to do so.  There are several ways the UA could=20
> > learn its=20
> > > > location from some other entity.  One of them is DHCP (for a=20
> > > > non-mobile UA).
> > > >=20
> > > > Do you see any problem with that approach?
> > > >=20
> > > > Brian
> > > >=20
> > > > > -----Original Message-----
> > > > > From: PROUVOST S=E9bastien FTRD/DAC/ISS
> > > > > [mailto:sebastien.prouvost@francetelecom.com]
> > > > > Sent: Monday, December 08, 2003 10:10 AM
> > > > > To: jmpolk@cisco.com; Brian.rosen@marconi.com
> > > > > Cc: sipping@ietf.org
> > > > > Subject: [sipping] comment on
> > > > > draft-polk-sipping-location-requirements-01.txt
> > > > >=20
> > > > >=20
> > > > > Hi,
> > > > >=20
> > > > > I fully support the idea of having location information=20
> > > conveyed in=20
> > > > > SIP.
> > > > >=20
> > > > > However, I fail to see in the draft a requirement for a=20
> > > proxy to be=20
> > > > > able to insert the location object on behalf of the UA. It
> > > > is likely
> > > > > that in some cases terminals may not have this=20
> > > information. In some=20
> > > > > architectures, an outbound proxy may be able to retrieve this =

> > > > > information (eg. Through a MIDCOM or COPS interface with an
> > > > entity in
> > > > > the transport plane) and it is useful to allow such an
> > > > outbound proxy
> > > > > to insert this location object.
> > > > >=20
> > > > > As stated in requirement E-3 regarding emergency calls,=20
> > > it may be a=20
> > > > > regulatory obligation for an operator to make this location=20
> > > > > information available to certain users. Operators may=20
> > > therefore be=20
> > > > > mandated to have this information inserted by proxies if
> > > > the terminal
> > > > > does not insert it.
> > > > >=20
> > > > > Regards,
> > > > >=20
> > > > > S=E9bastien Prouvost
> > > > > France T=E9l=E9com R&D/DAC/CAR
> > > > > http://www.francetelecom.com/rd
> > > > >=20
> > > > >=20
> > > > > _______________________________________________
> > > > > Sipping mailing list =20
> > > https://www1.ietf.org/mailman/listinfo/sipping
> > > > > This list is for NEW development of the application of SIP =
Use
> > > > > sip-implementors@cs.columbia.edu for questions on=20
> > current sip Use=20
> > > > > sip@ietf.org for new developments of core SIP
> > > > >=20
> > > >=20
> > >=20
> >=20
> > _______________________________________________
> > Sipping mailing list  =
https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> >=20
>=20

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



From exim@www1.ietf.org  Tue Dec 16 11:12:31 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21748
	for <sipping-archive@odin.ietf.org>; Tue, 16 Dec 2003 11:12:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHnm-0000ok-6Y
	for sipping-archive@odin.ietf.org; Tue, 16 Dec 2003 11:12:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBGGC2eu003136
	for sipping-archive@odin.ietf.org; Tue, 16 Dec 2003 11:12:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHnm-0000oV-2q
	for sipping-web-archive@optimus.ietf.org; Tue, 16 Dec 2003 11:12:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21732
	for <sipping-web-archive@ietf.org>; Tue, 16 Dec 2003 11:11:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHnl-0000e1-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 11:12:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWHnk-0000du-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 11:12:00 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHnk-0000dr-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 11:12:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHnj-0000nF-4R; Tue, 16 Dec 2003 11:11:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHnU-0000mj-3o
	for sipping@optimus.ietf.org; Tue, 16 Dec 2003 11:11:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21725
	for <sipping@ietf.org>; Tue, 16 Dec 2003 11:11:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHnR-0000dQ-00
	for sipping@ietf.org; Tue, 16 Dec 2003 11:11:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWHnQ-0000dJ-00
	for sipping@ietf.org; Tue, 16 Dec 2003 11:11:41 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHnP-0000cK-00
	for sipping@ietf.org; Tue, 16 Dec 2003 11:11:40 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA25093;
	Tue, 16 Dec 2003 10:58:01 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA22180;
	Tue, 16 Dec 2003 10:17:07 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <W9W8GTJM>; Tue, 16 Dec 2003 10:17:07 -0500
Message-ID: <313680C9A886D511A06000204840E1CF070B61F2@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Mpierce1@aol.com'" <Mpierce1@aol.com>, taylor@nortelnetworks.com
Cc: sebastien.prouvost@francetelecom.com, sipping@ietf.org, jmpolk@cisco.com
Subject: RE: [sipping] comment on draft-polk-sipping-location-requirements
	 -01.txt
Date: Tue, 16 Dec 2003 10:17:05 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

What you claim may be true, or it may be an exaggeration.
Regardless, does the idea that a phone knows its location
and reports it on an emergency call meet what you see
as the requirements for emergency calls?

The current proposal is that TLS is used on an emergency
call.  The geopriv guys want this to protect location (privacy).
The emergency guys would like authentication.  TLS would
provide both.  The emergency center is highly likely to
accept a call that didn't have location and/or was not
protected by TLS.  They might, as a follow up, go looking
for the reason why it didn't.  

If I were designing a UA or a proxy server that was handling
emergency calls, I would implement what I needed to
get location, and I would implement TLS.  I wouldn't fail
if I didn't get location, and I'd probably retry an emergency
call with sip: if the sips: call failed.

Would that be reasonable?

Brian
-----Original Message-----
From: Mpierce1@aol.com [mailto:Mpierce1@aol.com]
Sent: Tuesday, December 16, 2003 8:35 AM
To: Brian.Rosen@marconi.com; taylor@nortelnetworks.com
Cc: sebastien.prouvost@francetelecom.com; sipping@ietf.org; jmpolk@cisco.com
Subject: Re: [sipping] comment on draft-polk-sipping-location-requirements
-01.txt


In a message dated 12/12/2003 10:14:07 AM Eastern Standard Time,
Brian.Rosen@marconi.com writes: 



There is a considerable amount of pressure by those who are 
concerned about privacy to keep location information under 
very tight control.  One attempt to deal with location in the 
IETF went down in flames, and the present one has 90% of 
its efforts directed to privacy and 10% to location. 

This is a reality we have to deal with, or we aren't going 
to get anything through the process. 



Unfortunately, I don't believe that the previous attempt (or the present one
in GEOPRIV) is concerned with "the reality" of the situation. It continues
to believe that it will somehow be forever exempt from government
regulations, so it can ignore "reality". 

The truth is, today I can not make a 911 call in the US and expect to keep
my location private (from the service provider or the emergency service
provider). In fact, recent regulations are closing the gap where exact
locatoin was not being provided due to technical limitations, such as for
cellular and PBXs. 

Yes, one needs to be concerned with privacy, but the requirements of
emergency calling (e.g., 911) override this pricavy because of government
requirements. (I know, many in this effort want to ignore govenments, but
they still exist, and probablu will for some time.) If the UA doesn't know
it's location and report it, then an entity that claims to provide telephone
service must provide that location information. 

Now that I've inflamed this discssuion more with the truth ... 

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 exim@www1.ietf.org  Tue Dec 16 11:19:35 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21922
	for <sipping-archive@odin.ietf.org>; Tue, 16 Dec 2003 11:19:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHuc-0001As-QC
	for sipping-archive@odin.ietf.org; Tue, 16 Dec 2003 11:19:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBGGJ6Yd004508
	for sipping-archive@odin.ietf.org; Tue, 16 Dec 2003 11:19:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHuc-0001Ad-ML
	for sipping-web-archive@optimus.ietf.org; Tue, 16 Dec 2003 11:19:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21916
	for <sipping-web-archive@ietf.org>; Tue, 16 Dec 2003 11:19:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHub-0000qw-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 11:19:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWHua-0000qp-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 11:19:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHua-0000qm-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 11:19:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHuX-00019X-Kr; Tue, 16 Dec 2003 11:19:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWHto-00018q-Fu
	for sipping@optimus.ietf.org; Tue, 16 Dec 2003 11:18:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21902
	for <sipping@ietf.org>; Tue, 16 Dec 2003 11:18:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHtn-0000pS-00
	for sipping@ietf.org; Tue, 16 Dec 2003 11:18:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWHtl-0000pI-00
	for sipping@ietf.org; Tue, 16 Dec 2003 11:18:15 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWHtj-0000nd-00
	for sipping@ietf.org; Tue, 16 Dec 2003 11:18:12 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA25657;
	Tue, 16 Dec 2003 11:14:03 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA28021;
	Tue, 16 Dec 2003 10:52:54 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <W9W8G4QF>; Tue, 16 Dec 2003 10:52:54 -0500
Message-ID: <313680C9A886D511A06000204840E1CF070B61F4@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'dick.rr.knight@bt.com'" <dick.rr.knight@bt.com>,
        sebastien.prouvost@francetelecom.com
Cc: sipping@ietf.org, jmpolk@cisco.com
Subject: RE: [sipping] comment on draft-polk-sipping-location-requirements
	-01.txt
Date: Tue, 16 Dec 2003 10:52:54 -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: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mailgate.pit.comms.marconi.com id LAA25657
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

I think you leaped a little too far.

You correctly point out that abuse is an issue, and that=20
verification is a requirement.  This is actually a fairly=20
complex issue.  For example, it is not uncommon for there=20
to be more than one way to refer to an address.  In most=20
existing emergency systems, there is an "authenticated"
address database.  In North America, this is called the=20
"Master Street Address Guide".  It's not sufficient to=20
report an address, it has to be an address in the MSAG. =20
There are extensive procedures in place to make sure the=20
MSAG is accurate, and that addresses reported are in it.
To be sure, it's never completely accurate, and call=20
centers take calls that report addresses not in the MSAG,=20
but they try hard.

I believe that we need to have a way to authenticate an=20
address in such a way that it can be determined to be=20
equivalent to be in the MSAG.

But, you also raised another issue, which is deliberate=20
falsification of location.  You proposed that for this=20
purpose, the network be able to assert a location.  You point=20
out that there are legitimate reasons why they could be=20
different with the phone's location correct, and the proxy's=20
incorrect.

I believe that there is no reasonable way for the emergency=20
center to differentiate.  Even if they asked, verbally, they=20
would not get any closer to the "truth" (the VPN customer=20
would say the phone is right, but so would the prankster). =20
I would hate to be in the position of trying to figure out=20
which was more likely.  Sending responders to both locations=20
would get the problem you posed (risk to responders, and=20
non-availability of people/equipment).  I conclude that there
the proposed solution is no better than living with the=20
problem.

You will note that you have to have a corruptible UA to make=20
this happen.  Such a thing is pretty easy, to be sure (open=20
source soft client for example).  However, that also makes it=20
trivial to bypass any troublesome proxies.  The emergency centers=20
know that they will get VoIP calls from the open Internet=20
(no proxy) as well as calls from known service providers. =20
They may be more suspicious of calls from random places on the=20
Internet, but they are likely to take them.

I've wondered if there is some value in a single bit of=20
information from the service provider/proxy, which is that it's=20
suspicious of the location.  With that bit, the emergency center=20
is at least alerted that there is something "odd".  In a VPN=20
situation, the caller could, if asked, explain that she is using=20
her employers phone system from the Starbucks.  The prankster=20
would still lie of course.  Also note that a prankster is not=20
a legitimate call; the location the network could report is not=20
useful; that it is different from that reported by the UA is=20
the only useful information.

Brian

> -----Original Message-----
> From: dick.rr.knight@bt.com [mailto:dick.rr.knight@bt.com]
> Sent: Tuesday, December 16, 2003 8:56 AM
> To: Brian.Rosen@marconi.com; sebastien.prouvost@francetelecom.com
> Cc: sipping@ietf.org; jmpolk@cisco.com
> Subject: RE: [sipping] comment on
> draft-polk-sipping-location-requirements-01.txt
>=20
>=20
> I think there is a mix up here.
>=20
> Location is needed for two reasons:
> Firstly to determine the correct emergency answering operator.
> Secondly to determine where to send the emergency response.
>=20
> If we don't get the first one right then there is no chance=20
> of even being close on the second.
>=20
> But there is another requirement: avoiding abuse.
>=20
> It is well known that calling the fire brigade and claiming=20
> there is a fire at the cremetorium is a supposedly funny gag=20
> that puts lives at risk (as the emergency services must respond).
> Security is important in authorisation and location=20
> determination to ensure that the information given is consistent.
>=20
> There are times when the terminal knows that it is not where=20
> the Proxy thinks it is, but verification by the first proxy=20
> is an important factor in verifying that this looks as though=20
> it is a genuine emergency call.
>=20
> Hence I conclude that the Proxy SHOULD be allowed to insert=20
> location information (suitably protected) in order to assist=20
> in the verification process. Also the teminal needs to be=20
> able to indicate that the proxy is probably wrong (e.g.=20
> connected via a secure VPN tunnel to corporate intranet).
>=20
> Privacy is important to outsiders but not to a genuine=20
> emergency caller wanting to share their location with an=20
> emergency operator (clearly a trusted entity), and there are=20
> advantages in having a proxy verify that the information is=20
> correct. This provides a real improvement to response times=20
> (in the UK) by the emergency services (fire police ambulance etc.).
>=20
> Dick Knight
>=20
> -----Original Message-----
> From: sipping-admin@ietf.org=20
> [mailto:sipping-admin@ietf.org]On Behalf Of
> Rosen, Brian
> Sent: 12 December 2003 13:03
> To: 'PROUVOST S=E9bastien FTRD/DAC/ISS'
> Cc: sipping@ietf.org; jmpolk@cisco.com
> Subject: RE: [sipping] comment on
> draft-polk-sipping-location-requirements-01.txt
>=20
>=20
> I think that the issue is one of privacy control.  If some
> intermediary puts your location on the message without your
> consent, there is a significant breach of privacy.
>=20
> The emergency case is somewhat different, and we are looking
> into how best to accommodate it.  In general, our approach
> is to get the UA to know its location and report it with
> the call.  We understand the issue of authentication of
> location, and will need to assure that the location is accurate
> when a carrier knows what it is.   If the location is
> provided to the UA, and it chooses to NOT send it, I believe
> he should be allowed to do so.  There are several ways the UA
> could learn its location from some other entity.  One of them
> is DHCP (for a non-mobile UA).=20
>=20
> Do you see any problem with that approach?
>=20
> Brian
>=20
> > -----Original Message-----
> > From: PROUVOST S=E9bastien FTRD/DAC/ISS
> > [mailto:sebastien.prouvost@francetelecom.com]
> > Sent: Monday, December 08, 2003 10:10 AM
> > To: jmpolk@cisco.com; Brian.rosen@marconi.com
> > Cc: sipping@ietf.org
> > Subject: [sipping] comment on
> > draft-polk-sipping-location-requirements-01.txt
> >=20
> >=20
> > Hi,
> >=20
> > I fully support the idea of having location information=20
> > conveyed in SIP.
> >=20
> > However, I fail to see in the draft a requirement for a proxy=20
> > to be able to insert the location object on behalf of the UA.=20
> > It is likely that in some cases terminals may not have this=20
> > information. In some architectures, an outbound proxy may be=20
> > able to retrieve this information (eg. Through a MIDCOM or=20
> > COPS interface with an entity in the transport plane) and it=20
> > is useful to allow such an outbound proxy to insert this=20
> > location object. =20
> >=20
> > As stated in requirement E-3 regarding emergency calls, it=20
> > may be a regulatory obligation for an operator to make this=20
> > location information available to certain users. Operators=20
> > may therefore be mandated to have this information inserted=20
> > by proxies if the terminal does not insert it.
> >=20
> > Regards,
> >=20
> > S=E9bastien Prouvost
> > France T=E9l=E9com R&D/DAC/CAR
> > http://www.francetelecom.com/rd
> >=20
> >=20
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sip@ietf.org for new developments of core SIP
> >=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>=20

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



From exim@www1.ietf.org  Tue Dec 16 11:37:44 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22677
	for <sipping-archive@odin.ietf.org>; Tue, 16 Dec 2003 11:37:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWICB-0001z7-G9
	for sipping-archive@odin.ietf.org; Tue, 16 Dec 2003 11:37:16 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBGGbFmV007617
	for sipping-archive@odin.ietf.org; Tue, 16 Dec 2003 11:37:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWICB-0001yj-7S
	for sipping-web-archive@optimus.ietf.org; Tue, 16 Dec 2003 11:37:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22666
	for <sipping-web-archive@ietf.org>; Tue, 16 Dec 2003 11:37:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWICA-0001aJ-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 11:37:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWIC8-0001aC-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 11:37:13 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWIC8-0001a9-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 11:37:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWIBx-0001te-PR; Tue, 16 Dec 2003 11:37:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWIBe-0001t2-Di
	for sipping@optimus.ietf.org; Tue, 16 Dec 2003 11:36:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22658
	for <sipping@ietf.org>; Tue, 16 Dec 2003 11:36:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWIBd-0001Zo-00
	for sipping@ietf.org; Tue, 16 Dec 2003 11:36:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWIBb-0001Zg-00
	for sipping@ietf.org; Tue, 16 Dec 2003 11:36:40 -0500
Received: from opus.cs.columbia.edu ([128.59.20.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWIBb-0001ZI-00
	for sipping@ietf.org; Tue, 16 Dec 2003 11:36:39 -0500
Received: from cs.columbia.edu (path.cs.columbia.edu [128.59.19.143])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id hBGGaCe9007468
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Tue, 16 Dec 2003 11:36:17 -0500 (EST)
Message-ID: <3FDF347C.9000301@cs.columbia.edu>
Date: Tue, 16 Dec 2003 11:36:12 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031130
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Rosen, Brian" <Brian.Rosen@marconi.com>
CC: "'dick.rr.knight@bt.com'" <dick.rr.knight@bt.com>,
        sebastien.prouvost@francetelecom.com, sipping@ietf.org,
        jmpolk@cisco.com
Subject: Re: [sipping] comment on draft-polk-sipping-location-requirements
 -01.txt
References: <313680C9A886D511A06000204840E1CF070B61F4@whq-msgusr-02.pit.comms.marconi.com>
In-Reply-To: <313680C9A886D511A06000204840E1CF070B61F4@whq-msgusr-02.pit.comms.marconi.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by opus.cs.columbia.edu id hBGGaCe9007468
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

To avoid further repeating discussions: We do need to design things so=20
that a proxy can, in real-time, provide the 911-calling UA with its=20
estimate of the location, in particular if the INVITE does not contain=20
this location. This does not necessarily imply that the proxy has to=20
insert the location into request; it could, for example, return it as=20
part of a redirect response.

This mechanism allows the UA to (theoretically) inspect the location,=20
thus increasing user control over his or her information.

However, it is unclear to me why such control does not treat me as=20
mature enough to provide explicit consent - "please insert location=20
object". (The UI issues of obtaining consent are similar whether the=20
location object is reflected or included.)

This model comes at a cost, namely requiring UA upgrades and additional=20
round-trip times over a potentially slow air interface. (If the location=20
object is signed by the proxy, it can be quite large, so the additional=20
delay could reach a second or two.)

This same cost makes it unrealistic to assume that the proxy or some=20
other entity will continuously update the mobile with its location. The=20
911 location requirements would require updates at least every second if=20
the mobile is moving at highway speeds.

A secondary disadvantage is that the prankster can remove the location=20
information; more relevantly, a proxy probably has to somehow=20
distinguish that it tried to redirect with location information, but got=20
the same call back later, still without location information (since the=20
UA was buggy or old) and then has to forward the INVITE, without=20
location information.

In general, unless you require proxy operators to be certified by a=20
single government agency, even a signed location object, reflected or=20
inserted, tells the PSAP very little. The signature can be from=20
mafia-r-us.com, after all.


Rosen, Brian wrote:

> I think you leaped a little too far.
>=20
> You correctly point out that abuse is an issue, and that=20
> verification is a requirement.  This is actually a fairly=20
> complex issue.  For example, it is not uncommon for there=20
> to be more than one way to refer to an address.  In most=20
> existing emergency systems, there is an "authenticated"
> address database.  In North America, this is called the=20
> "Master Street Address Guide".  It's not sufficient to=20
> report an address, it has to be an address in the MSAG. =20
> There are extensive procedures in place to make sure the=20
> MSAG is accurate, and that addresses reported are in it.
> To be sure, it's never completely accurate, and call=20
> centers take calls that report addresses not in the MSAG,=20
> but they try hard.
>=20
> I believe that we need to have a way to authenticate an=20
> address in such a way that it can be determined to be=20
> equivalent to be in the MSAG.
>=20
> But, you also raised another issue, which is deliberate=20
> falsification of location.  You proposed that for this=20
> purpose, the network be able to assert a location.  You point=20
> out that there are legitimate reasons why they could be=20
> different with the phone's location correct, and the proxy's=20
> incorrect.
>=20
> I believe that there is no reasonable way for the emergency=20
> center to differentiate.  Even if they asked, verbally, they=20
> would not get any closer to the "truth" (the VPN customer=20
> would say the phone is right, but so would the prankster). =20
> I would hate to be in the position of trying to figure out=20
> which was more likely.  Sending responders to both locations=20
> would get the problem you posed (risk to responders, and=20
> non-availability of people/equipment).  I conclude that there
> the proposed solution is no better than living with the=20
> problem.
>=20
> You will note that you have to have a corruptible UA to make=20
> this happen.  Such a thing is pretty easy, to be sure (open=20
> source soft client for example).  However, that also makes it=20
> trivial to bypass any troublesome proxies.  The emergency centers=20
> know that they will get VoIP calls from the open Internet=20
> (no proxy) as well as calls from known service providers. =20
> They may be more suspicious of calls from random places on the=20
> Internet, but they are likely to take them.
>=20
> I've wondered if there is some value in a single bit of=20
> information from the service provider/proxy, which is that it's=20
> suspicious of the location.  With that bit, the emergency center=20
> is at least alerted that there is something "odd".  In a VPN=20
> situation, the caller could, if asked, explain that she is using=20
> her employers phone system from the Starbucks.  The prankster=20
> would still lie of course.  Also note that a prankster is not=20
> a legitimate call; the location the network could report is not=20
> useful; that it is different from that reported by the UA is=20
> the only useful information.
>=20
> Brian
>=20
>=20
>>-----Original Message-----
>>From: dick.rr.knight@bt.com [mailto:dick.rr.knight@bt.com]
>>Sent: Tuesday, December 16, 2003 8:56 AM
>>To: Brian.Rosen@marconi.com; sebastien.prouvost@francetelecom.com
>>Cc: sipping@ietf.org; jmpolk@cisco.com
>>Subject: RE: [sipping] comment on
>>draft-polk-sipping-location-requirements-01.txt
>>
>>
>>I think there is a mix up here.
>>
>>Location is needed for two reasons:
>>Firstly to determine the correct emergency answering operator.
>>Secondly to determine where to send the emergency response.
>>
>>If we don't get the first one right then there is no chance=20
>>of even being close on the second.
>>
>>But there is another requirement: avoiding abuse.
>>
>>It is well known that calling the fire brigade and claiming=20
>>there is a fire at the cremetorium is a supposedly funny gag=20
>>that puts lives at risk (as the emergency services must respond).
>>Security is important in authorisation and location=20
>>determination to ensure that the information given is consistent.
>>
>>There are times when the terminal knows that it is not where=20
>>the Proxy thinks it is, but verification by the first proxy=20
>>is an important factor in verifying that this looks as though=20
>>it is a genuine emergency call.
>>
>>Hence I conclude that the Proxy SHOULD be allowed to insert=20
>>location information (suitably protected) in order to assist=20
>>in the verification process. Also the teminal needs to be=20
>>able to indicate that the proxy is probably wrong (e.g.=20
>>connected via a secure VPN tunnel to corporate intranet).
>>
>>Privacy is important to outsiders but not to a genuine=20
>>emergency caller wanting to share their location with an=20
>>emergency operator (clearly a trusted entity), and there are=20
>>advantages in having a proxy verify that the information is=20
>>correct. This provides a real improvement to response times=20
>>(in the UK) by the emergency services (fire police ambulance etc.).
>>
>>Dick Knight
>>
>>-----Original Message-----
>>From: sipping-admin@ietf.org=20
>>[mailto:sipping-admin@ietf.org]On Behalf Of
>>Rosen, Brian
>>Sent: 12 December 2003 13:03
>>To: 'PROUVOST S=E9bastien FTRD/DAC/ISS'
>>Cc: sipping@ietf.org; jmpolk@cisco.com
>>Subject: RE: [sipping] comment on
>>draft-polk-sipping-location-requirements-01.txt
>>
>>
>>I think that the issue is one of privacy control.  If some
>>intermediary puts your location on the message without your
>>consent, there is a significant breach of privacy.
>>
>>The emergency case is somewhat different, and we are looking
>>into how best to accommodate it.  In general, our approach
>>is to get the UA to know its location and report it with
>>the call.  We understand the issue of authentication of
>>location, and will need to assure that the location is accurate
>>when a carrier knows what it is.   If the location is
>>provided to the UA, and it chooses to NOT send it, I believe
>>he should be allowed to do so.  There are several ways the UA
>>could learn its location from some other entity.  One of them
>>is DHCP (for a non-mobile UA).=20
>>
>>Do you see any problem with that approach?
>>
>>Brian
>>
>>
>>>-----Original Message-----
>>>From: PROUVOST S=E9bastien FTRD/DAC/ISS
>>>[mailto:sebastien.prouvost@francetelecom.com]
>>>Sent: Monday, December 08, 2003 10:10 AM
>>>To: jmpolk@cisco.com; Brian.rosen@marconi.com
>>>Cc: sipping@ietf.org
>>>Subject: [sipping] comment on
>>>draft-polk-sipping-location-requirements-01.txt
>>>
>>>
>>>Hi,
>>>
>>>I fully support the idea of having location information=20
>>>conveyed in SIP.
>>>
>>>However, I fail to see in the draft a requirement for a proxy=20
>>>to be able to insert the location object on behalf of the UA.=20
>>>It is likely that in some cases terminals may not have this=20
>>>information. In some architectures, an outbound proxy may be=20
>>>able to retrieve this information (eg. Through a MIDCOM or=20
>>>COPS interface with an entity in the transport plane) and it=20
>>>is useful to allow such an outbound proxy to insert this=20
>>>location object. =20
>>>
>>>As stated in requirement E-3 regarding emergency calls, it=20
>>>may be a regulatory obligation for an operator to make this=20
>>>location information available to certain users. Operators=20
>>>may therefore be mandated to have this information inserted=20
>>>by proxies if the terminal does not insert it.
>>>
>>>Regards,
>>>
>>>S=E9bastien Prouvost
>>>France T=E9l=E9com R&D/DAC/CAR
>>>http://www.francetelecom.com/rd
>>>
>>>
>>>_______________________________________________
>>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>>This list is for NEW development of the application of SIP
>>>Use sip-implementors@cs.columbia.edu for questions on current sip
>>>Use sip@ietf.org for new developments of core SIP
>>>
>>
>>_______________________________________________
>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>This list is for NEW development of the application of SIP
>>Use sip-implementors@cs.columbia.edu for questions on current sip
>>Use sip@ietf.org for new developments of core SIP
>>
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP

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



From exim@www1.ietf.org  Tue Dec 16 16:05:02 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04590
	for <sipping-archive@odin.ietf.org>; Tue, 16 Dec 2003 16:05:02 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWMMs-0005bZ-5E
	for sipping-archive@odin.ietf.org; Tue, 16 Dec 2003 16:04:34 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBGL4YAF021544
	for sipping-archive@odin.ietf.org; Tue, 16 Dec 2003 16:04:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWMMr-0005bO-SR
	for sipping-web-archive@optimus.ietf.org; Tue, 16 Dec 2003 16:04:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04523
	for <sipping-web-archive@ietf.org>; Tue, 16 Dec 2003 16:04:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWMMq-0002XK-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 16:04:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWMMn-0002X1-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 16:04:31 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWMMn-0002WG-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 16:04:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWMML-0005Oc-Qu; Tue, 16 Dec 2003 16:04:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWMLX-0005B0-Dk
	for sipping@optimus.ietf.org; Tue, 16 Dec 2003 16:03:11 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04321;
	Tue, 16 Dec 2003 16:03:08 -0500 (EST)
Message-Id: <200312162103.QAA04321@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, 16 Dec 2003 16:03:08 -0500
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-aaa-req-04.txt
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,MIME_BOUND_NEXTPART,
	NO_REAL_NAME autolearn=no version=2.60

--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		: Authentication, Authorization and Accounting 
			  Requirements for the Session Initiation Protocol
	Author(s)	: J. Loughney, G. Camarillo
	Filename	: draft-ietf-sipping-aaa-req-04.txt
	Pages		: 16
	Date		: 2003-12-16
	
As SIP services are deployed on the Internet, there is a need for
authentication, authorization and accounting of SIP sessions. This
document sets out the basic requirements for this work.

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-sipping-aaa-req-04.txt

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

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

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Tue Dec 16 17:27:42 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11133
	for <sipping-archive@odin.ietf.org>; Tue, 16 Dec 2003 17:27:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWNet-0000zG-MM
	for sipping-archive@odin.ietf.org; Tue, 16 Dec 2003 17:27:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBGMRFE3003788
	for sipping-archive@odin.ietf.org; Tue, 16 Dec 2003 17:27:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWNet-0000z1-Hl
	for sipping-web-archive@optimus.ietf.org; Tue, 16 Dec 2003 17:27:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11033
	for <sipping-web-archive@ietf.org>; Tue, 16 Dec 2003 17:27:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWNer-00000q-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 17:27:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWNeo-00000J-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 17:27:12 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWNeo-000006-00
	for sipping-web-archive@ietf.org; Tue, 16 Dec 2003 17:27:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWNee-0000xa-Sj; Tue, 16 Dec 2003 17:27:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWNeL-0000xK-AN
	for sipping@optimus.ietf.org; Tue, 16 Dec 2003 17:26:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11012
	for <sipping@ietf.org>; Tue, 16 Dec 2003 17:26:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWNeB-0007nK-00
	for sipping@ietf.org; Tue, 16 Dec 2003 17:26:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWNdm-0007nA-00
	for sipping@ietf.org; Tue, 16 Dec 2003 17:26:06 -0500
Received: from bdsl.66.12.12.130.gte.net ([66.12.12.130] helo=bdsl.greycouncil.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWNdl-0007mx-00
	for sipping@ietf.org; Tue, 16 Dec 2003 17:26:05 -0500
Received: from txdwillis (bdsl.66.12.12.254.gte.net [66.12.12.254])
	(authenticated bits=0)
	by bdsl.greycouncil.com (8.12.8/8.12.8) with ESMTP id hBGMSvY4005023
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO);
	Tue, 16 Dec 2003 16:28:58 -0600
From: "Dean Willis" <dean.willis@softarmor.com>
To: <sipping@ietf.org>
Cc: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@ericsson.com>, <rohan@cisco.com>
Date: Tue, 16 Dec 2003 16:24:38 -0600
Message-ID: <000101c3c423$64e2caf0$e1036e3f@txdwillis>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: quoted-printable
Subject: [Sipping] WGLC on Early Media Drafts
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable


Based on feedback from the Minneapolis meeting, it seems that the Early
Media work is believed ready to proceed.=20

Please review:

http://www.ietf.org/internet-drafts/draft-ietf-sipping-early-media-01.txt=


http://www.ietf.org/internet-drafts/draft-ietf-sipping-early-disposition-=
00.
txt


Please send any comments back to the authors, and copy the list if your
comments are appropriate for public reading (and they SHOULD be!).

The working group last call for these documents will close January 7, =
2004.

Thanks,

--
Dean



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



From exim@www1.ietf.org  Wed Dec 17 00:45:39 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25924
	for <sipping-archive@odin.ietf.org>; Wed, 17 Dec 2003 00:45:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWUUh-0000Hv-CF
	for sipping-archive@odin.ietf.org; Wed, 17 Dec 2003 00:45:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBH5jBqL001103
	for sipping-archive@odin.ietf.org; Wed, 17 Dec 2003 00:45:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWUUh-0000Hi-7l
	for sipping-web-archive@optimus.ietf.org; Wed, 17 Dec 2003 00:45:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25917
	for <sipping-web-archive@ietf.org>; Wed, 17 Dec 2003 00:45:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWUUe-0003w9-00
	for sipping-web-archive@ietf.org; Wed, 17 Dec 2003 00:45:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWUUd-0003w2-00
	for sipping-web-archive@ietf.org; Wed, 17 Dec 2003 00:45:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWUUd-0003vz-00
	for sipping-web-archive@ietf.org; Wed, 17 Dec 2003 00:45:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWUUZ-0000GH-Mj; Wed, 17 Dec 2003 00:45:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWUTn-0000EA-Vk
	for sipping@optimus.ietf.org; Wed, 17 Dec 2003 00:44:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25896
	for <sipping@ietf.org>; Wed, 17 Dec 2003 00:44:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWUTl-0003uJ-00
	for sipping@ietf.org; Wed, 17 Dec 2003 00:44:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWUTk-0003uC-00
	for sipping@ietf.org; Wed, 17 Dec 2003 00:44:13 -0500
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWUTj-0003td-00
	for sipping@ietf.org; Wed, 17 Dec 2003 00:44:12 -0500
Received: from dynamicsoft.com ([63.113.46.18])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id hBH5hTmR002920;
	Wed, 17 Dec 2003 00:43:29 -0500 (EST)
Message-ID: <3FDFECFB.4090209@dynamicsoft.com>
Date: Wed, 17 Dec 2003 00:43:23 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Henning Schulzrinne <hgs@cs.columbia.edu>
CC: "Rosen, Brian" <Brian.Rosen@marconi.com>,
        "'dick.rr.knight@bt.com'" <dick.rr.knight@bt.com>,
        sebastien.prouvost@francetelecom.com, sipping@ietf.org,
        jmpolk@cisco.com
Subject: Re: [sipping] comment on draft-polk-sipping-location-requirements
 -01.txt
References: <313680C9A886D511A06000204840E1CF070B61F4@whq-msgusr-02.pit.comms.marconi.com> <3FDF347C.9000301@cs.columbia.edu>
In-Reply-To: <3FDF347C.9000301@cs.columbia.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

inline.

Henning Schulzrinne wrote:

> To avoid further repeating discussions: We do need to design things so 
> that a proxy can, in real-time, provide the 911-calling UA with its 
> estimate of the location, in particular if the INVITE does not contain 
> this location. This does not necessarily imply that the proxy has to 
> insert the location into request; it could, for example, return it as 
> part of a redirect response.
> 
> This mechanism allows the UA to (theoretically) inspect the location, 
> thus increasing user control over his or her information.

In the case of 911, though, does this matter? Calling 911 does imply 
that you have waived your right to privacy. Furthermore, I doubt that, 
while in the process of having a heart attack and having managed to 
dial 911, I will really want to inspect the location information 
provided by my proxy. A 911 call is exactly the kind of case where you 
dont want user interaction for the call to proceed.

> 
> However, it is unclear to me why such control does not treat me as 
> mature enough to provide explicit consent - "please insert location 
> object". (The UI issues of obtaining consent are similar whether the 
> location object is reflected or included.)
> 
> This model comes at a cost, namely requiring UA upgrades and additional 
> round-trip times over a potentially slow air interface. (If the location 
> object is signed by the proxy, it can be quite large, so the additional 
> delay could reach a second or two.)
> 
> This same cost makes it unrealistic to assume that the proxy or some 
> other entity will continuously update the mobile with its location. The 
> 911 location requirements would require updates at least every second if 
> the mobile is moving at highway speeds.
> 
> A secondary disadvantage is that the prankster can remove the location 
> information; more relevantly, a proxy probably has to somehow 
> distinguish that it tried to redirect with location information, but got 
> the same call back later, still without location information (since the 
> UA was buggy or old) and then has to forward the INVITE, without 
> location information.

You have quoted several disadvantages to the redirect model, but no 
advantages over the proxy-inserted model. I really don't see what is 
lost, but see that a lot can potentially be gained. Indeed, I see no 
problem with having the proxy insert location inforamtion in addition 
to that provided by the device. This would allow the emergency call 
center, in many cases, to get verification of accuracy of the address 
when the device has more accurate data than the network; they would 
see that the network indicated a location of "New Jersey", and the 
handset indicated a location of "600 Lanidex Plaza, Parsippany, NJ", 
giving some confidence that the handset-provided location is not 
falsified. Havign vastly different addresses would also send a signal 
to the emergency operator that they really need to verify the address.

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


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



From exim@www1.ietf.org  Wed Dec 17 02:12:38 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09994
	for <sipping-archive@odin.ietf.org>; Wed, 17 Dec 2003 02:12:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWVqs-0004MR-8i
	for sipping-archive@odin.ietf.org; Wed, 17 Dec 2003 02:12:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBH7CAXr016762
	for sipping-archive@odin.ietf.org; Wed, 17 Dec 2003 02:12:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWVqr-0004MH-Tk
	for sipping-web-archive@optimus.ietf.org; Wed, 17 Dec 2003 02:12:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09770
	for <sipping-web-archive@ietf.org>; Wed, 17 Dec 2003 02:12:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWVqo-0005hC-00
	for sipping-web-archive@ietf.org; Wed, 17 Dec 2003 02:12:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWVqn-0005h5-00
	for sipping-web-archive@ietf.org; Wed, 17 Dec 2003 02:12:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWVqn-0005h2-00
	for sipping-web-archive@ietf.org; Wed, 17 Dec 2003 02:12:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWVqj-0004Kc-Ou; Wed, 17 Dec 2003 02:12:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWVqX-0004J6-NR
	for sipping@optimus.ietf.org; Wed, 17 Dec 2003 02:11:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09538
	for <sipping@ietf.org>; Wed, 17 Dec 2003 02:11:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWVqU-0005es-00
	for sipping@ietf.org; Wed, 17 Dec 2003 02:11:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWVqS-0005ef-00
	for sipping@ietf.org; Wed, 17 Dec 2003 02:11:45 -0500
Received: from imr1.ericy.com ([198.24.6.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWVqS-0005Zs-00
	for sipping@ietf.org; Wed, 17 Dec 2003 02:11:44 -0500
Received: from eamrcnt750.exu.ericsson.se (eamrcnt750.exu.ericsson.se [138.85.133.51])
	by imr1.ericy.com (8.12.10/8.12.10) with ESMTP id hBH7B3Wm006129;
	Wed, 17 Dec 2003 01:11:03 -0600 (CST)
Received: from ericsson.com (rvi2-92-49.sw.ericsson.se [153.88.92.49]) by eamrcnt750.exu.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id YGLRFNVB; Wed, 17 Dec 2003 01:10:43 -0600
Message-ID: <3FE00183.7060406@ericsson.com>
Date: Wed, 17 Dec 2003 09:10:59 +0200
X-Sybari-Trust: a283f9e3 76be5e0c 125231cb 00000138
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
CC: sipping@ietf.org, rohan@cisco.com
Subject: Re: [Sipping] WGLC on Early Media Drafts
References: <000101c3c423$64e2caf0$e1036e3f@txdwillis>
In-Reply-To: <000101c3c423$64e2caf0$e1036e3f@txdwillis>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

I have received one comment on the early media disposition type draft 
that will be addressed adding the following text at the end of the first 
paragraph of Section 4:

***
It is also NOT RECOMMENDED to use the same transport address (IP address 
plus port) in a session body and in an early-session body. Using 
different transport addresses (e.g., different ports) to receive early 
and regular media makes it easy to detect the start of the regular media.
***

Gonzalo

Dean Willis wrote:

> Based on feedback from the Minneapolis meeting, it seems that the Early
> Media work is believed ready to proceed. 
> 
> Please review:
> 
> http://www.ietf.org/internet-drafts/draft-ietf-sipping-early-media-01.txt
> 
> http://www.ietf.org/internet-drafts/draft-ietf-sipping-early-disposition-00.
> txt
> 
> 
> Please send any comments back to the authors, and copy the list if your
> comments are appropriate for public reading (and they SHOULD be!).
> 
> The working group last call for these documents will close January 7, 2004.
> 
> Thanks,
> 
> --
> Dean
> 


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



From exim@www1.ietf.org  Wed Dec 17 09:49:46 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09511
	for <sipping-archive@odin.ietf.org>; Wed, 17 Dec 2003 09:49:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWczG-0004ZK-5L
	for sipping-archive@odin.ietf.org; Wed, 17 Dec 2003 09:49:19 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBHEnICq017558
	for sipping-archive@odin.ietf.org; Wed, 17 Dec 2003 09:49:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWczG-0004Z7-24
	for sipping-web-archive@optimus.ietf.org; Wed, 17 Dec 2003 09:49:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09462
	for <sipping-web-archive@ietf.org>; Wed, 17 Dec 2003 09:49:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWczE-0005Gr-00
	for sipping-web-archive@ietf.org; Wed, 17 Dec 2003 09:49:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWczD-0005Gj-00
	for sipping-web-archive@ietf.org; Wed, 17 Dec 2003 09:49:15 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWczC-0005Gg-00
	for sipping-web-archive@ietf.org; Wed, 17 Dec 2003 09:49:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWcyz-0004Xe-2o; Wed, 17 Dec 2003 09:49:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWcyr-0004X5-3H
	for sipping@optimus.ietf.org; Wed, 17 Dec 2003 09:48:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09427
	for <sipping@ietf.org>; Wed, 17 Dec 2003 09:48:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWcyp-0005F0-00
	for sipping@ietf.org; Wed, 17 Dec 2003 09:48:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWcyo-0005Es-00
	for sipping@ietf.org; Wed, 17 Dec 2003 09:48:50 -0500
Received: from opus.cs.columbia.edu ([128.59.20.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWcyn-0005Eo-00
	for sipping@ietf.org; Wed, 17 Dec 2003 09:48:50 -0500
Received: from cs.columbia.edu (path.cs.columbia.edu [128.59.19.143])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id hBHEmOe9005229
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Wed, 17 Dec 2003 09:48:27 -0500 (EST)
Message-ID: <3FE06CB8.10306@cs.columbia.edu>
Date: Wed, 17 Dec 2003 09:48:24 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031130
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: "Rosen, Brian" <Brian.Rosen@marconi.com>,
        "'dick.rr.knight@bt.com'" <dick.rr.knight@bt.com>,
        sebastien.prouvost@francetelecom.com, sipping@ietf.org,
        jmpolk@cisco.com
Subject: Re: [sipping] comment on draft-polk-sipping-location-requirements
 -01.txt
References: <313680C9A886D511A06000204840E1CF070B61F4@whq-msgusr-02.pit.comms.marconi.com> <3FDF347C.9000301@cs.columbia.edu> <3FDFECFB.4090209@dynamicsoft.com>
In-Reply-To: <3FDFECFB.4090209@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


> In the case of 911, though, does this matter? Calling 911 does imply 
> that you have waived your right to privacy. Furthermore, I doubt that, 
> while in the process of having a heart attack and having managed to dial 
> 911, I will really want to inspect the location information provided by 
> my proxy. A 911 call is exactly the kind of case where you dont want 
> user interaction for the call to proceed.

I fully agree; I was simply trying to represent the motivation leading 
to the end-system-control argument by some in this discussion. Maybe I 
should just let them speak for themselves.


> 
> You have quoted several disadvantages to the redirect model, but no 
> advantages over the proxy-inserted model. I really don't see what is 
> lost, but see that a lot can potentially be gained. Indeed, I see no 
> problem with having the proxy insert location inforamtion in addition to 
> that provided by the device. This would allow the emergency call center, 
> in many cases, to get verification of accuracy of the address when the 
> device has more accurate data than the network; they would see that the 
> network indicated a location of "New Jersey", and the handset indicated 
> a location of "600 Lanidex Plaza, Parsippany, NJ", giving some 
> confidence that the handset-provided location is not falsified. Havign 
> vastly different addresses would also send a signal to the emergency 
> operator that they really need to verify the address.

No disagreement.

> 
> -Jonathan R.

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



From exim@www1.ietf.org  Wed Dec 17 10:09:36 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11987
	for <sipping-archive@odin.ietf.org>; Wed, 17 Dec 2003 10:09:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWdIS-0005hO-HQ
	for sipping-archive@odin.ietf.org; Wed, 17 Dec 2003 10:09:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBHF98Zn021900
	for sipping-archive@odin.ietf.org; Wed, 17 Dec 2003 10:09:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWdIS-0005h9-Bz
	for sipping-web-archive@optimus.ietf.org; Wed, 17 Dec 2003 10:09:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11884
	for <sipping-web-archive@ietf.org>; Wed, 17 Dec 2003 10:09:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWdIQ-00079Z-00
	for sipping-web-archive@ietf.org; Wed, 17 Dec 2003 10:09:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWdIM-000790-00
	for sipping-web-archive@ietf.org; Wed, 17 Dec 2003 10:09:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWdIM-00078x-00
	for sipping-web-archive@ietf.org; Wed, 17 Dec 2003 10:09:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWdIL-0005fV-JJ; Wed, 17 Dec 2003 10:09:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWdHb-0005dR-8i
	for sipping@optimus.ietf.org; Wed, 17 Dec 2003 10:08:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11510
	for <sipping@ietf.org>; Wed, 17 Dec 2003 10:08:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWdHY-0006yz-00
	for sipping@ietf.org; Wed, 17 Dec 2003 10:08:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWdHL-0006xA-00
	for sipping@ietf.org; Wed, 17 Dec 2003 10:08:10 -0500
Received: from [216.9.243.101] (helo=mhs99ykf.rim.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWdHL-0006wn-00
	for sipping@ietf.org; Wed, 17 Dec 2003 10:07:59 -0500
Received: from ngw04ykf.rim.net (ngw04ykf.rim.net [10.102.100.115])
	by mhs99ykf.rim.net (Postfix) with SMTP id C7A96B5560
	for <sipping@ietf.org>; Wed, 17 Dec 2003 10:07:57 -0500 (EST)
Received: from XCH21YKF.rim.net ([10.102.100.36])
 by ngw04ykf.rim.net (NAVGW 2.5.2.9) with SMTP id M2003121710075728922
 ; Wed, 17 Dec 2003 10:07:57 -0500
Received: from xch15ykf.rim.net ([10.101.21.36]) by XCH21YKF.rim.net with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 17 Dec 2003 10:07:57 -0500
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Subject: Re: [Sipping] Push-to-Talk specifications
Date: Wed, 17 Dec 2003 10:07:57 -0500
Message-ID: <A274B1B8C42A6C4AA9A4262C7AC96AF9B70334@xch15ykf.rim.net>
Thread-Topic: [Sipping] Push-to-Talk specifications
Thread-Index: AcPC6rEiEaCQ08mMTzSuPPTDuf6yvgBxNxlP
From: "Andrew Allen" <aallen@rim.net>
To: <xavier.priem@siemens.com>, <hector.berna@vodafone.com>,
        <sipping@ietf.org>
Cc: <xavier.marjou@siemens.com>
X-OriginalArrivalTime: 17 Dec 2003 15:07:57.0426 (UTC) FILETIME=[8DD34520:01C3C4AF]
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable



As someone involved in the OMA work on PoC I feel that Xavier's response =
is a little misleading in referring to the specifications produced by =
the Ericsson, Motorola, Nokia and Siemens consortium as a "standard". =
These specifications have not been endorsed by any standards body and =
the work within OMA has already significantly deviated from this initial =
input. In IETF terms the consortium documents could be considered to =
have similar status as  personal internet drafts that have not yet been =
accepted as WG items. The OMA standards work is still at an early stage.

The OMA PoC architecture document which is Work in Progress has been =
made public on the OMA web site recently.

If you go to =
http://www.openmobilealliance.org/tech/wg_committees/poc.html
and follow the link to "Public Available Documents (link to Documents =
Repository" you should find it amongst the 2003 documents.

Regards
Andrew


--------------------------
Andrew Allen
Manager Standards
Research In Motion Ltd
BlackBerry Mobile  +1 847 809 8636
European Mobile    +358 50 467 5870
http://www.rim.com/

Sent from my BlackBerry Wireless Handheld


-----Original Message-----
From: Priem Xavier <xavier.priem@siemens.com>
To: 'hector.berna@vodafone.com' <hector.berna@vodafone.com>
CC: sipping@ietf.org <sipping@ietf.org>; Marjou Xavier =
<xavier.marjou@siemens.com>
Sent: Mon Dec 15 04:05:21 2003
Subject: RE: [Sipping] Push-to-Talk specifications

Hi Hector,

You may know about the PoC (Push-to-Talk Over Cellular) standard, =
emerging from Ericsson, Motorola, Nokia and Siemens consortium.=20

If this is the one you search for, you will find under =
http://www.siemens.com/Daten/siecom/HQ/ICM/Internet/ICM_Unitwide/WORKAREA=
/ICMPress/templatedata/English/file/binary/ICM_200309_149_e_Push_to_Talk_=
1093999.pdf

Some press info.

If you need docs or more info, please ask my colleague Xavier Marjou...

Best regards

Xavier Priem
Cordialement / Mit freundlichem Gru=DF / With kind regards=20
Xavier PRIEM=20
R&D Consultant / Patent Delegate
Dept System Engineering & Project Acquisition
---------------------------------------------------------=20
SRIT Lannion=20
SIEMENS R=E9seaux Informatique et T=E9l=E9communications=20
3, Rue Blaise Pascal=20
22300 LANNION - FRANCE=20
http://www.siemens-srit.com/
Phone:  +33 2 96 48 74 30=20
Fax:    +33 2 96 48 74 73=20
Email:  xavier.priem@siemens.com <mailto:xavier.priem@siemens.com>=20
---------------------------------------------------------=20



-----Original Message-----
From: hector.berna@vodafone.com [mailto:hector.berna@vodafone.com]=20
Sent: lundi 15 d=E9cembre 2003 09:46
To: sipping@ietf.org
Subject: [Sipping] Push-to-Talk specifications


Hello,

I would like to know if there is any RFC or Draft that states the =
specifications of the Push-to-Talk service.

Thanks in advance,

Hector Berna




.........................................................................=
.........................................................................=
.........................................................................=
.......


Confidencialidad


Este  correo  electr=F3nico  y,  en su caso, cualquier fichero anexo al =
mismo, contiene informaci=F3n de car=E1cter  confidencial  =
exclusivamente  dirigida  a  su  destinatario o destinatarios y =
propiedad de Vodafone  Espa=F1a.  Queda  prohibida  su  divulgaci=F3n,  =
copia o distribuci=F3n a terceros sin la previa autorizaci=F3n  escrita  =
de  Vodafone Espa=F1a, en virtud de la legislaci=F3n vigente. En el caso =
de haber recibido  este  correo  electr=F3nico  por error, se ruega =
notificar inmediatamente esta circunstancia mediante reenv=EDo a la =
direcci=F3n electr=F3nica del remitente y la destrucci=F3n del mismo.


Confidentiality


The  information in this e-mail and in any attachments is classified as =
Vodafone Espa=F1a Confidential and  Proprietary Information and solely =
for the attention and use of the named addressee(s). You are hereby  =
notified  that  any  dissemination, distribution or copy of this =
communication is prohibited without  the  prior  written consent of =
Vodafone Espa=F1a and it is strictly prohibited by law. If you have =
received this communication by error, please, notify the sender by =
replying e-mail.



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

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


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



From exim@www1.ietf.org  Thu Dec 18 04:04:36 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11973
	for <sipping-archive@odin.ietf.org>; Thu, 18 Dec 2003 04:04:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWu4l-0007hy-It
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 04:04:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBI946GS029624
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 04:04:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWu4k-0007hj-Mp
	for sipping-web-archive@optimus.ietf.org; Thu, 18 Dec 2003 04:04:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11967
	for <sipping-web-archive@ietf.org>; Thu, 18 Dec 2003 04:04:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWu4i-0006XO-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 04:04:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWu4g-0006XH-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 04:04:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWu4g-0006XE-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 04:04:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWu4g-0007gW-7S; Thu, 18 Dec 2003 04:04:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWu3h-0007bl-BA
	for sipping@optimus.ietf.org; Thu, 18 Dec 2003 04:03:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11939
	for <sipping@ietf.org>; Thu, 18 Dec 2003 04:02:59 -0500 (EST)
From: dick.rr.knight@bt.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWu3e-0006Vh-00
	for sipping@ietf.org; Thu, 18 Dec 2003 04:02:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWu3d-0006Va-00
	for sipping@ietf.org; Thu, 18 Dec 2003 04:02:58 -0500
Received: from smtp5.smtp.bt.com ([217.32.164.139] helo=i2kc05-ukbr.domain1.systemhost.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWu3d-0006VU-00
	for sipping@ietf.org; Thu, 18 Dec 2003 04:02:57 -0500
Received: from i2km98-ukbr.domain1.systemhost.net ([193.113.197.85]) by i2kc05-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 18 Dec 2003 09:02:27 +0000
Received: from i2km35-ukdy.domain1.systemhost.net ([193.113.30.26]) by i2km98-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 18 Dec 2003 09:02:27 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [sipping] comment on draft-polk-sipping-location-requirements -01.txt
Date: Thu, 18 Dec 2003 09:02:26 -0000
Message-ID: <E0E9F9BE940EFC4186DB15A079FF31500518FEC2@i2km35-ukdy.domain1.systemhost.net>
Thread-Topic: [sipping] comment on draft-polk-sipping-location-requirements -01.txt
Thread-Index: AcPEYLKG3gJzLhZmT5mATQMoBnAafgA5QqbA
To: <jdrosen@dynamicsoft.com>, <hgs@cs.columbia.edu>
Cc: <Brian.Rosen@marconi.com>, <sebastien.prouvost@francetelecom.com>,
        <sipping@ietf.org>, <jmpolk@cisco.com>
X-OriginalArrivalTime: 18 Dec 2003 09:02:27.0083 (UTC) FILETIME=[A8BC3DB0:01C3C545]
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

I think Jonathon has summed up the needs for emergency calling. The =
proxy must be allowed to add to the SIP-device's location information. =
Then let the operator make the decision about accuracy.

Dick

-----Original Message-----
From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com]
Sent: 17 December 2003 05:43
To: Henning Schulzrinne
Cc: Rosen, Brian; Knight,RR,Dick,XJG4 KNIGHTRR R;
sebastien.prouvost@francetelecom.com; sipping@ietf.org; jmpolk@cisco.com
Subject: Re: [sipping] comment on
draft-polk-sipping-location-requirements -01.txt


inline.

Henning Schulzrinne wrote:

> To avoid further repeating discussions: We do need to design things so =

> that a proxy can, in real-time, provide the 911-calling UA with its=20
> estimate of the location, in particular if the INVITE does not contain =

> this location. This does not necessarily imply that the proxy has to=20
> insert the location into request; it could, for example, return it as=20
> part of a redirect response.
>=20
> This mechanism allows the UA to (theoretically) inspect the location,=20
> thus increasing user control over his or her information.

In the case of 911, though, does this matter? Calling 911 does imply=20
that you have waived your right to privacy. Furthermore, I doubt that,=20
while in the process of having a heart attack and having managed to=20
dial 911, I will really want to inspect the location information=20
provided by my proxy. A 911 call is exactly the kind of case where you=20
dont want user interaction for the call to proceed.

>=20
> However, it is unclear to me why such control does not treat me as=20
> mature enough to provide explicit consent - "please insert location=20
> object". (The UI issues of obtaining consent are similar whether the=20
> location object is reflected or included.)
>=20
> This model comes at a cost, namely requiring UA upgrades and =
additional=20
> round-trip times over a potentially slow air interface. (If the =
location=20
> object is signed by the proxy, it can be quite large, so the =
additional=20
> delay could reach a second or two.)
>=20
> This same cost makes it unrealistic to assume that the proxy or some=20
> other entity will continuously update the mobile with its location. =
The=20
> 911 location requirements would require updates at least every second =
if=20
> the mobile is moving at highway speeds.
>=20
> A secondary disadvantage is that the prankster can remove the location =

> information; more relevantly, a proxy probably has to somehow=20
> distinguish that it tried to redirect with location information, but =
got=20
> the same call back later, still without location information (since =
the=20
> UA was buggy or old) and then has to forward the INVITE, without=20
> location information.

You have quoted several disadvantages to the redirect model, but no=20
advantages over the proxy-inserted model. I really don't see what is=20
lost, but see that a lot can potentially be gained. Indeed, I see no=20
problem with having the proxy insert location inforamtion in addition=20
to that provided by the device. This would allow the emergency call=20
center, in many cases, to get verification of accuracy of the address=20
when the device has more accurate data than the network; they would=20
see that the network indicated a location of "New Jersey", and the=20
handset indicated a location of "600 Lanidex Plaza, Parsippany, NJ",=20
giving some confidence that the handset-provided location is not=20
falsified. Havign vastly different addresses would also send a signal=20
to the emergency operator that they really need to verify the address.

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


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



From exim@www1.ietf.org  Thu Dec 18 09:37:42 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23696
	for <sipping-archive@odin.ietf.org>; Thu, 18 Dec 2003 09:37:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWzH6-0004sX-95
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 09:37:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBIEbCsI018749
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 09:37:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWzH5-0004sK-FF
	for sipping-web-archive@optimus.ietf.org; Thu, 18 Dec 2003 09:37:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23689
	for <sipping-web-archive@ietf.org>; Thu, 18 Dec 2003 09:37:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWzH3-00049P-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 09:37:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWzH1-000499-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 09:37:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWzH1-000495-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 09:37:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWzGv-0004pB-Ed; Thu, 18 Dec 2003 09:37:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWzG9-0004nM-HO
	for sipping@optimus.ietf.org; Thu, 18 Dec 2003 09:36:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23621
	for <sipping@ietf.org>; Thu, 18 Dec 2003 09:36:10 -0500 (EST)
From: Mpierce1@aol.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWzG5-000434-00
	for sipping@ietf.org; Thu, 18 Dec 2003 09:36:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWzFU-00042a-00
	for sipping@ietf.org; Thu, 18 Dec 2003 09:35:33 -0500
Received: from imo-r07.mx.aol.com ([152.163.225.103])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWzFU-0003zo-00
	for sipping@ietf.org; Thu, 18 Dec 2003 09:35:32 -0500
Received: from Mpierce1@aol.com
	by imo-r07.mx.aol.com (mail_out_v36_r4.8.) id p.130.29430c6a (4380);
	Thu, 18 Dec 2003 09:33:50 -0500 (EST)
Message-ID: <130.29430c6a.2d1314cd@aol.com>
Date: Thu, 18 Dec 2003 09:33:49 EST
Subject: Re: [sipping] comment on draft-polk-sipping-location-requirements -01.txt
To: dick.rr.knight@bt.com, jdrosen@dynamicsoft.com, hgs@cs.columbia.edu
CC: Brian.Rosen@marconi.com, sebastien.prouvost@francetelecom.com,
        sipping@ietf.org, jmpolk@cisco.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_130.29430c6a.2d1314cd_boundary"
X-Mailer: 6.0 for Windows XP sub 10501
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE,
	NO_REAL_NAME autolearn=no version=2.60


--part1_130.29430c6a.2d1314cd_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 12/18/2003 4:04:42 AM Eastern Standard Time, 
dick.rr.knight@bt.com writes:


> I think Jonathon has summed up the needs for emergency calling. The proxy 
> must be allowed to add to the SIP-device's location information. Then let the 
> operator make the decision about accuracy.
> 

Sounds good, but I still don't see how the operator (emergency service 
bureau) can make the decision between two conflicting pieces of information. What 
specifically can the proxy add to allow this decision to be made?

Mike


--part1_130.29430c6a.2d1314cd_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<HTML><FONT FACE=3Darial,helvetica><FONT  SIZE=3D2 PTSIZE=3D10>In a message=20=
dated 12/18/2003 4:04:42 AM Eastern Standard Time, dick.rr.knight@bt.com wri=
tes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-=
LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">I think Jonathon has summed=
 up the needs for emergency calling. The proxy must be allowed to add to the=
 SIP-device's location information. Then let the operator make the decision=20=
about accuracy.
<BR></FONT><FONT  COLOR=3D"#000000" BACK=3D"#ffffff" style=3D"BACKGROUND-COL=
OR: #ffffff" SIZE=3D3 PTSIZE=3D12 FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=
=3D"0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR=3D"#000000" BACK=3D"#ffffff" style=3D"BACKGROUND-COL=
OR: #ffffff" SIZE=3D2 PTSIZE=3D10 FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=
=3D"0">
<BR>Sounds good, but I still don't see how the operator (emergency service b=
ureau) can make the decision between two conflicting pieces of information.=20=
What specifically can the proxy add to allow this decision to be made?
<BR>
<BR>Mike
<BR></FONT></HTML>

--part1_130.29430c6a.2d1314cd_boundary--

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



From exim@www1.ietf.org  Thu Dec 18 10:04:45 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25513
	for <sipping-archive@odin.ietf.org>; Thu, 18 Dec 2003 10:04:45 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWzhJ-0006W4-8u
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 10:04:17 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBIF4HWw025042
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 10:04:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWzhJ-0006Vp-4E
	for sipping-web-archive@optimus.ietf.org; Thu, 18 Dec 2003 10:04:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25442
	for <sipping-web-archive@ietf.org>; Thu, 18 Dec 2003 10:04:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWzhG-0005xY-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 10:04:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWzhF-0005xP-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 10:04:14 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWzhF-0005xM-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 10:04:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWzh4-0006UH-2n; Thu, 18 Dec 2003 10:04:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWzgt-0006TK-Gh
	for sipping@optimus.ietf.org; Thu, 18 Dec 2003 10:03:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25347
	for <sipping@ietf.org>; Thu, 18 Dec 2003 10:03:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWzgo-0005tO-00
	for sipping@ietf.org; Thu, 18 Dec 2003 10:03:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWzgm-0005tF-00
	for sipping@ietf.org; Thu, 18 Dec 2003 10:03:45 -0500
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWzgm-0005tB-00
	for sipping@ietf.org; Thu, 18 Dec 2003 10:03:44 -0500
Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11])
	by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id hBIF3g706754
	for <sipping@ietf.org>; Thu, 18 Dec 2003 16:03:43 +0100 (MET)
Received: from blues.mchh.siemens.de (blues.mchh.siemens.de [139.21.204.206])
	by mail2.siemens.de (8.11.7/8.11.7) with ESMTP id hBIF3gP23476
	for <sipping@ietf.org>; Thu, 18 Dec 2003 16:03:42 +0100 (MET)
Received: from mchh273e.mchh.siemens.de (mchh273e.mchh.siemens.de [139.21.200.83])
	by blues.mchh.siemens.de (8.9.3/8.9.1) with ESMTP id QAA19204
	for <sipping@ietf.org>; Thu, 18 Dec 2003 16:03:33 +0100 (MET)
Received: by mchh273e.mchh.siemens.de with Internet Mail Service (5.5.2656.59)
	id <YYHD7RZH>; Thu, 18 Dec 2003 16:03:40 +0100
Message-ID: <5B788FC2CAFBD6118BAE0030848B025C80F6A1@LNN201E>
From: Pinal Jean-Pierre <jean-pierre.pinal@siemens.com>
To: "'sipping@ietf.org'" <sipping@ietf.org>
Date: Thu, 18 Dec 2003 16:03:36 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3C578.1CD53CB0"
Subject: [Sipping] consecutive NOTIFY and automatic unsubscription upon 500 error re
 sponse
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,HTML_60_70,HTML_MESSAGE 
	autolearn=no version=2.60

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_01C3C578.1CD53CB0
Content-Type: text/plain

Hello 

 

1)

As described in RFC 3261, a UA may start a next transaction before the previous is terminated 

(except for INVITE)

 

2)

After subscription, if notifier sends two consecutive NOTIFYs, the 

subscriber may receive the second NOTIFY first and reject the first 

with 500 in conformance with RFC 3261

 

RFC 3261

12.2.2 UAS Behavior

"If the remote sequence number was not empty, but the sequence number

   of the request is lower than the remote sequence number, the request

   is out of order and MUST be rejected with a 500 (Server Internal

   Error) response."

 

3)

And in RFC 3265

 

"A NOTIFY request is considered failed if the response times out, or a

non-200 class response code is received which has no "Retry-After"

header and no implied further action which can be taken to retry 

therequest (e.g., "401 Authorization Required".)"

...

"If the NOTIFY request fails (as defined above) due to an error

response, and the subscription was installed using a soft-state

mechanism, the notifier MUST remove the corresponding 

subscription."

 

=> In the case when second NOTIFY is received before first, the NOTIFIER receives a 500 for the first NOTIFY and the subscription is removed!

But the subscriber does not want that its subscription is removed! 

 

Here, what is wrong?

 

Must the subscriber sends a 500 with always a Retry-After header in order to avoid subscription deletion?

 

In this case, must the NOTIFIER send a new NOTIFY with a full description of subscribed state?

 

I found nothing in RFC3265 about consecutive NOTIFYs.

 

Or must the implied event package define in "Notifier generation of NOTIFY requests" section that the notifier can not generate a new NOTIFY before response of the previous NOTIFY has been received?

I think it is not the responsibility of event package

  

Is there a lack in RFC3265?

 

 

Best regards

 

Jean-Pierre

 


------_=_NextPart_001_01C3C578.1CD53CB0
Content-Type: text/html

<html>

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


<meta name=Generator content="Microsoft Word 10 (filtered)">

<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:#606420;
	text-decoration:underline;}
p
	{margin-right:0cm;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=EN-US link=blue vlink="#606420">

<div class=Section1>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>Hello </span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>1)</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>As described in RFC 3261, a UA may start a next
transaction before the previous is terminated </span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>(except for INVITE)</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>2)</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>After subscription, if notifier sends two
consecutive NOTIFYs, the </span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>subscriber may receive the second NOTIFY first and
reject the first </span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>with 500 in conformance with RFC 3261</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>RFC 3261</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>12.2.2 UAS Behavior</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>"If the remote sequence number was not empty, but the
sequence number</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; of the request is lower than the remote sequence
number, the request</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; is out of order and MUST be rejected with a 500
(Server Internal</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>&nbsp;&nbsp; Error) response."</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>3)</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>And in RFC 3265</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>&quot;A NOTIFY request is considered failed if the
response times out, or a</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>non-200 class response code is received which has no
&quot;Retry-After&quot;</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>header and no implied further action which can be
taken to retry </span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>therequest (e.g., &quot;401 Authorization
Required&quot;.)&quot;</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>...</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>&quot;If the NOTIFY request fails (as defined above)
due to an error</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>response, and the subscription was installed using a
soft-state</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>mechanism, the notifier MUST remove the
corresponding </span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>subscription.&quot;</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>=&gt; In the case when second NOTIFY is received
before first, the NOTIFIER receives a 500 for the first NOTIFY and the
subscription is removed!</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>But the subscriber does not want that its
subscription is removed! </span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>Here, what is wrong?</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>Must the subscriber sends a 500 with always a
Retry-After header in order to avoid subscription deletion?</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face="Courier New"><span style='font-size:10.0pt;
font-family:"Courier New"'>In this case, must the NOTIFIER send a new NOTIFY
with a full description of subscribed state?</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>I found nothing in RFC3265 about consecutive NOTIFYs.</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Or must the implied event package define in "Notifier
generation of NOTIFY requests" section that the notifier can not generate
a new NOTIFY before response of the previous NOTIFY has been received?</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>I think it is not the responsibility of event package</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>&nbsp; </span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Is there a lack in RFC3265?</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Best regards</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Jean-Pierre</span></font></p>

<p><font size=3 face="Times New Roman"><span lang=FR style='font-size:12.0pt'>&nbsp;</span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C3C578.1CD53CB0--

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



From exim@www1.ietf.org  Thu Dec 18 10:24:15 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28511
	for <sipping-archive@odin.ietf.org>; Thu, 18 Dec 2003 10:24:14 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX00A-0007vP-Tk
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 10:23:47 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBIFNkkr030464
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 10:23:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX00A-0007vH-4i
	for sipping-web-archive@optimus.ietf.org; Thu, 18 Dec 2003 10:23:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28443
	for <sipping-web-archive@ietf.org>; Thu, 18 Dec 2003 10:23:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX006-0000zK-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 10:23:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWzzX-0000tK-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 10:23:39 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWzzV-0000tC-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 10:23:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWzzR-0007kG-BY; Thu, 18 Dec 2003 10:23:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWzz7-0007iF-K0
	for sipping@optimus.ietf.org; Thu, 18 Dec 2003 10:22:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28335
	for <sipping@ietf.org>; Thu, 18 Dec 2003 10:22:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWzz4-0000na-00
	for sipping@ietf.org; Thu, 18 Dec 2003 10:22:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWzyR-0000h4-00
	for sipping@ietf.org; Thu, 18 Dec 2003 10:22:36 -0500
Received: from pooh.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWzyP-0000gq-00
	for sipping@ietf.org; Thu, 18 Dec 2003 10:21:57 -0500
Received: from pcasveren (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with SMTP id KAA22129;
	Thu, 18 Dec 2003 10:21:52 -0500 (EST)
From: "Tolga Asveren" <asveren@ulticom.com>
To: "Pinal Jean-Pierre" <jean-pierre.pinal@siemens.com>, <sipping@ietf.org>
Subject: RE: [Sipping] consecutive NOTIFY and automatic unsubscription upon 500 error re sponse
Date: Thu, 18 Dec 2003 10:21:20 -0500
Message-ID: <GBEBKGPKHGPAOFCLBNAMIEPICCAA.asveren@ulticom.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_015F_01C3C550.AE461570"
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.2800.1165
In-Reply-To: <5B788FC2CAFBD6118BAE0030848B025C80F6A1@LNN201E>
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,HTML_50_60,
	HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60


This is a multi-part message in MIME format.

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

inline......
  -----Original Message-----
  From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]On Behalf Of
Pinal Jean-Pierre
  Sent: Thursday, December 18, 2003 10:04 AM
  To: 'sipping@ietf.org'
  Subject: [Sipping] consecutive NOTIFY and automatic unsubscription upon
500 error re sponse


  Hello



  1)

  As described in RFC 3261, a UA may start a next transaction before the
previous is terminated

  (except for INVITE)



  2)

  After subscription, if notifier sends two consecutive NOTIFYs, the

  subscriber may receive the second NOTIFY first and reject the first

  with 500 in conformance with RFC 3261

  12.2.2 UAS Behavior

  "If the remote sequence number was not empty, but the sequence number

     of the request is lower than the remote sequence number, the request

     is out of order and MUST be rejected with a 500 (Server Internal

     Error) response."

  [TOLGA] Based on the error code, it seems to me like an oversight. For
UDP -or if different streams are used per transaction for SCTP- there might
be reordering of requests. To cover such a case, I would expect some other
error code. 500(Server Internal Error) sounds to me more like implying
something wrong on the UAS, rather than missequencing on the network. In
fact the above statement in RFC3261 12.2.2. makes me think that as long as
there is a possibility of missequencing in the network, it is better to wait
a transaction to end, before starting a new one. At least, I would do it
that way in my application, you won't loose much. Non-INVITE tranasactions
are supposed to end with no significant delays.



  3)

  And in RFC 3265



  "A NOTIFY request is considered failed if the response times out, or a

  non-200 class response code is received which has no "Retry-After"

  header and no implied further action which can be taken to retry

  therequest (e.g., "401 Authorization Required".)"

  ...

  "If the NOTIFY request fails (as defined above) due to an error

  response, and the subscription was installed using a soft-state

  mechanism, the notifier MUST remove the corresponding

  subscription."



  => In the case when second NOTIFY is received before first, the NOTIFIER
receives a 500 for the first NOTIFY and the subscription is removed!

  But the subscriber does not want that its subscription is removed!



  Here, what is wrong?



  Must the subscriber sends a 500 with always a Retry-After header in order
to avoid subscription deletion?



  In this case, must the NOTIFIER send a new NOTIFY with a full description
of subscribed state?



  I found nothing in RFC3265 about consecutive NOTIFYs.

  [TOLGA]Although there are no hard limits there is the following:

  RFC3265 4.1

  "Further, it is expected that this mechanism is not to be used in
applicationss where the frequency of reportable events is excessively
rapid(e.g., more than about once a second)."





  Or must the implied event package define in "Notifier generation of NOTIFY
requests" section that the notifier can not generate a new NOTIFY before
response of the previous NOTIFY has been received?

  I think it is not the responsibility of event package



  Is there a lack in RFC3265?





  Best regards



  Jean-Pierre



------=_NextPart_000_015F_01C3C550.AE461570
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.2800.1264" name=3DGENERATOR>
<STYLE>@page Section1 {size: 612.0pt 792.0pt; margin: 72.0pt 90.0pt =
72.0pt 90.0pt; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: #606420; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: #606420; TEXT-DECORATION: underline
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: =
"Times New Roman"
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3D#606420 link=3Dblue>
<DIV><SPAN class=3D705530815-18122003><FONT face=3DArial color=3D#0000ff =

size=3D2>inline......</FONT></SPAN></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>Pinal=20
  Jean-Pierre<BR><B>Sent:</B> Thursday, December 18, 2003 10:04 =
AM<BR><B>To:</B>=20
  'sipping@ietf.org'<BR><B>Subject:</B> [Sipping] consecutive NOTIFY and =

  automatic unsubscription upon 500 error re sponse<BR><BR></FONT></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">Hello =
</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'">1)</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">As described in =
RFC 3261,=20
  a UA may start a next transaction before the previous is terminated=20
  </SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">(except for=20
  INVITE)</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'">2)</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">After =
subscription, if=20
  notifier sends two consecutive NOTIFYs, the </SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">subscriber may =
receive the=20
  second NOTIFY first and reject the first </SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New"><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">with 500 in =
conformance=20
  with RFC 3261<SPAN class=3D705530815-18122003><FONT face=3DArial=20
  color=3D#0000ff>&nbsp;</FONT></SPAN></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New"><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'"><SPAN=20
  class=3D705530815-18122003></SPAN></SPAN></FONT><FONT face=3DArial =
size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">12.2.2 UAS=20
  Behavior</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">"If the remote sequence =
number was=20
  not empty, but the sequence number</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; of the =
request is=20
  lower than the remote sequence number, the request</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; is out of =
order and=20
  MUST be rejected with a 500 (Server Internal</SPAN></FONT></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; Error)=20
  response."<SPAN class=3D705530815-18122003><FONT=20
  color=3D#0000ff>&nbsp;</FONT></SPAN></SPAN></P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><SPAN=20
  class=3D705530815-18122003><FONT color=3D#0000ff>[TOLGA] Based on the =
error code,=20
  it seems to me like an oversight. For UDP -or if different streams are =
used=20
  per transaction for SCTP- there might be reordering&nbsp;of =
requests.&nbsp;To=20
  cover such a case, I would expect&nbsp;some other error code. =
500(Server=20
  Internal Error) sounds to me more like implying something wrong on the =
UAS,=20
  rather than&nbsp;missequencing on the network. In fact the above =
statement=20
  in&nbsp;RFC3261 12.2.2.&nbsp;makes me think that&nbsp;as long as there =
is a=20
  possibility of missequencing in the network, it is better to wait a=20
  transaction to end, before starting a new one. At least, I would do it =
that=20
  way in my application, you won't loose much. Non-INVITE tranasactions =
are=20
  supposed to end with no significant delays.</FONT></SPAN></SPAN></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'">3)</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">And in RFC=20
  3265</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">"A NOTIFY =
request is=20
  considered failed if the response times out, or a</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">non-200 class =
response=20
  code is received which has no "Retry-After"</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">header and no =
implied=20
  further action which can be taken to retry </SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">therequest =
(e.g., "401=20
  Authorization Required".)"</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'">...</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">"If the NOTIFY =
request=20
  fails (as defined above) due to an error</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">response, and =
the=20
  subscription was installed using a soft-state</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">mechanism, the =
notifier=20
  MUST remove the corresponding </SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'">subscription."</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">=3D&gt; In the =
case when=20
  second NOTIFY is received before first, the NOTIFIER receives a 500 =
for the=20
  first NOTIFY and the subscription is removed!</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">But the =
subscriber does=20
  not want that its subscription is removed! </SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">Here, what is=20
  wrong?</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">Must the =
subscriber sends=20
  a 500 with always a Retry-After header in order to avoid subscription=20
  deletion?</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier =
New'"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3D"Courier New" size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'">In this case, =
must the=20
  NOTIFIER send a new NOTIFY with a full description of subscribed=20
  state?</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">I found=20
  nothing in RFC3265 about consecutive NOTIFYs.<SPAN=20
  class=3D705530815-18122003><FONT=20
  color=3D#0000ff>&nbsp;</FONT></SPAN></SPAN></P><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><SPAN =
class=3D705530815-18122003>
  <P class=3DMsoNormal><FONT face=3D"Courier New"><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'"><SPAN=20
  class=3D705530815-18122003><FONT face=3DArial =
color=3D#0000ff>[TOLGA]Although there=20
  are no hard limits there is the =
following:</FONT></SPAN></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New"><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'"><SPAN=20
  class=3D705530815-18122003><FONT face=3DArial color=3D#0000ff>RFC3265=20
  4.1</FONT></SPAN></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Courier New"><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'"><SPAN=20
  class=3D705530815-18122003><FONT face=3DArial =
color=3D#0000ff>"Further, it is=20
  expected that this mechanism is not to be used in applicationss where =
the=20
  frequency of reportable events is excessively rapid(e.g., more than =
about once=20
  a second)."</FONT></SPAN></SPAN></FONT></P>
  <P class=3DMsoNormal>&nbsp;</SPAN></SPAN></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Or must the implied =
event package=20
  define in "Notifier generation of NOTIFY requests" section that the =
notifier=20
  can not generate a new NOTIFY before response of the previous NOTIFY =
has been=20
  received?</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I think it is not the=20
  responsibility of event package</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp; =
</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Is there a lack in=20
  RFC3265?</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Best =
regards</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Jean-Pierre</SPAN></FONT></P>
  <P><FONT face=3D"Times New Roman" size=3D3><SPAN lang=3DFR=20
  style=3D"FONT-SIZE: =
12pt"></SPAN></FONT>&nbsp;</P></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_015F_01C3C550.AE461570--


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



From exim@www1.ietf.org  Thu Dec 18 11:17:41 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01420
	for <sipping-archive@odin.ietf.org>; Thu, 18 Dec 2003 11:17:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX0pr-00029x-6k
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 11:17:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBIGHBcB008298
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 11:17:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX0pr-00029l-0a
	for sipping-web-archive@optimus.ietf.org; Thu, 18 Dec 2003 11:17:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01408
	for <sipping-web-archive@ietf.org>; Thu, 18 Dec 2003 11:17:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX0pq-0003Vm-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 11:17:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX0pp-0003Vf-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 11:17:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX0pp-0003Vc-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 11:17:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX0ph-000263-En; Thu, 18 Dec 2003 11:17:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX0pD-00025j-CA
	for sipping@optimus.ietf.org; Thu, 18 Dec 2003 11:16:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01383
	for <sipping@ietf.org>; Thu, 18 Dec 2003 11:16:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX0pC-0003Tw-00
	for sipping@ietf.org; Thu, 18 Dec 2003 11:16:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX0pB-0003Tp-00
	for sipping@ietf.org; Thu, 18 Dec 2003 11:16:30 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX0pB-0003TY-00
	for sipping@ietf.org; Thu, 18 Dec 2003 11:16:29 -0500
Received: from rtp-core-2.cisco.com (64.102.124.13)
  by sj-iport-5.cisco.com with ESMTP; 18 Dec 2003 16:16:26 +0000
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com [64.102.16.27])
	by rtp-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id hBIGFsDM013825;
	Thu, 18 Dec 2003 11:15:54 -0500 (EST)
Received: from mhammer-w2k03.cisco.com (dhcp-hrn-64-100-229-166.cisco.com [64.100.229.166])
	by fruitpie.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AVT08317;
	Thu, 18 Dec 2003 08:15:52 -0800 (PST)
Message-Id: <4.3.2.7.2.20031218111515.00b31be8@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 18 Dec 2003 11:15:52 -0500
To: Mpierce1@aol.com
From: Michael Hammer <mhammer@cisco.com>
Subject: Re: [sipping] comment on
  draft-polk-sipping-location-requirements -01.txt
Cc: dick.rr.knight@bt.com, jdrosen@dynamicsoft.com, hgs@cs.columbia.edu,
        Brian.Rosen@marconi.com, sebastien.prouvost@francetelecom.com,
        sipping@ietf.org, jmpolk@cisco.com
In-Reply-To: <130.29430c6a.2d1314cd@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-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

At 09:33 AM 12/18/2003 -0500, Mpierce1@aol.com wrote:
>In a message dated 12/18/2003 4:04:42 AM Eastern Standard Time, 
>dick.rr.knight@bt.com writes:
>
>
>>I think Jonathon has summed up the needs for emergency calling. The proxy 
>>must be allowed to add to the SIP-device's location information. Then let 
>>the operator make the decision about accuracy.
>
>
>Sounds good, but I still don't see how the operator (emergency service 
>bureau) can make the decision between two conflicting pieces of 
>information. What specifically can the proxy add to allow this decision to 
>be made?

You don't decide, you pass on both pieces of information along with an 
indication of the source.

Mike Hammer


>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 exim@www1.ietf.org  Thu Dec 18 12:14:43 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03369
	for <sipping-archive@odin.ietf.org>; Thu, 18 Dec 2003 12:14:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX1j5-0004vt-BJ
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 12:14:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBIHEFb6018955
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 12:14:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX1j5-0004ve-6I
	for sipping-web-archive@optimus.ietf.org; Thu, 18 Dec 2003 12:14:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03339
	for <sipping-web-archive@ietf.org>; Thu, 18 Dec 2003 12:14:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX1j3-0005AA-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 12:14:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX1j1-00059q-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 12:14:13 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX1j1-00059n-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 12:14:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX1is-0004u9-Dd; Thu, 18 Dec 2003 12:14:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX1in-0004tU-W2
	for sipping@optimus.ietf.org; Thu, 18 Dec 2003 12:13:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03318
	for <sipping@ietf.org>; Thu, 18 Dec 2003 12:13:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX1im-00058d-00
	for sipping@ietf.org; Thu, 18 Dec 2003 12:13:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX1ik-00058F-00
	for sipping@ietf.org; Thu, 18 Dec 2003 12:13:56 -0500
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX1ij-00054w-00
	for sipping@ietf.org; Thu, 18 Dec 2003 12:13:53 -0500
Received: from dynamicsoft.com ([63.113.46.85])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id hBIHDPmR003631
	for <sipping@ietf.org>; Thu, 18 Dec 2003 12:13:25 -0500 (EST)
Message-ID: <3FE1E027.2090305@dynamicsoft.com>
Date: Thu, 18 Dec 2003 12:13:11 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Problem with reg-event that needs immediate fix
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

While implementing the sipping reg-event draft, we ran into a serious 
technical problem.

The problem is that the specification has not left sufficient room for 
extensibility within the XML schema. It allows for new information to 
be added to the <registration> element (which describes the AOR), but 
does not allow any additional information to be provided about a 
contact. We ran into this problem because we needed to add path 
information (ala rfc 3327) to the notifications, but this information 
is per contact. There is no way to do this with the current specification.

The essence of the problem is that the contact element has, as 
content, the actual URI. This makes it difficult to add other 
information about the contact. A better approach would have been to 
make the contact element a complex type, which would include an 
element called <uri> that contains the uri.

For example, today we have:

<?xml version="1.0"?>
    <reginfo xmlns="urn:ietf:params:xml:ns:reginfo"
                 version="1" state="partial">
      <registration aor="sip:joe@bar.com" id="a7" state="active">
        <contact id="76" state="active" event="registered"
                 duration-registered="0">sip:joe@pc34.bar.com</contact>
      </registration>
    </reginfo>

whereas it ought to have been:

<?xml version="1.0"?>
    <reginfo xmlns="urn:ietf:params:xml:ns:reginfo"
                 version="1" state="partial">
      <registration aor="sip:joe@bar.com" id="a7" state="active">
        <contact id="76" state="active" event="registered"
                 duration-registered="0">
                    <uri>sip:joe@pc34.bar.com</uri>
        </contact>
      </registration>
    </reginfo>


The schema for the contact element could then allow for other children 
in other namespaces, giving us the needed extensibility.

Unfortunately, there is other per-contact data we might want to add in 
the not-too-distant future, such as callee-caps information. That kind 
of data would be very useful for presence applications, where the 
presence server could obtain it from the registrar using reg-event.

I believe that this problem is significant enough that we should try 
and address it during auth48. For those of you not familiar with it, 
auth48 is a brief period just before publication of the actual RFC 
where the author can correct typos or minor other problems. It is 
possible, with AD approval, to make more substantive changes as I am 
suggesting (and indeed I already ran this by Allison and she is OK). 
Of course, I still need group consensus on any change. So, here is my 
proposal.

PROPOSAL

My proposal for fixing this, as outlined above, is to modify the XML 
schema. The <contact> element will instead become a complex type. It 
will have, as children, a sequence of <uri> followed by an optional 
element from any other namespace. The <uri> element will contain the 
actual contact URI.

Unfortunately, this proposed solution above is not backwards 
compatible with the current draft.

I considered other solutions as well:


ALTERNATE 1

Modify the schema to allow attributes in the contact element from 
other namespaces. Adds some extensibility, but is very bad for more 
complex data, such as path or callee-cap data. Using attributes for 
that data will require us to define a lot of structure within each 
attribute. This approach is backwards compatible, but not forwards 
compatible. That is, an implementation compliant to the schema before 
this change would reject documents created by an implementation 
compliant to the schema after the change.

ALTERNATE 2

Modify the schema to contain a new element, child to the 
<registration> element. This element would be called "alt-contact", 
and would be defined as I suggest above for contact. Whenever new 
information is needed about a contact, the "alt-contact" element would 
be present, and contain that extension data. The document would also 
still contain a contact element, repeating the URI and other 
attributes. This would provide forwards and backwards compatibility, 
at the expense of a horrible hack that would repeat a lot of 
information in the document.


I found neither of the two alternatives very palatable, which is why 
my proposal is to fix this now, and do it properly, while we still can.

Please provide input on the proposal ASAP. I'd like to come to 
consensus in the next week or so (before everyone disappears for 
vacations).

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



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



From exim@www1.ietf.org  Thu Dec 18 14:32:32 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10702
	for <sipping-archive@odin.ietf.org>; Thu, 18 Dec 2003 14:32:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX3sS-0003CK-1f
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 14:32:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBIJW4H8012286
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 14:32:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX3sR-0003Bu-S0
	for sipping-web-archive@optimus.ietf.org; Thu, 18 Dec 2003 14:32:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10641
	for <sipping-web-archive@ietf.org>; Thu, 18 Dec 2003 14:32:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX3sK-0003LS-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 14:31:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX3rt-0003Kv-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 14:31:30 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX3rs-0003Ji-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 14:31:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX3rT-000326-6u; Thu, 18 Dec 2003 14:31:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX3ql-00030j-GZ
	for sipping@optimus.ietf.org; Thu, 18 Dec 2003 14:30:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10393
	for <sipping@ietf.org>; Thu, 18 Dec 2003 14:30:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX3qY-0003Cb-00
	for sipping@ietf.org; Thu, 18 Dec 2003 14:30:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX3q6-0003Ba-00
	for sipping@ietf.org; Thu, 18 Dec 2003 14:29:40 -0500
Received: from zrc2s0jx.nortelnetworks.com ([47.103.122.112])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX3q6-00038h-00
	for sipping@ietf.org; Thu, 18 Dec 2003 14:29:38 -0500
Received: from zsc3c028.us.nortel.com (zsc3c028.us.nortel.com [47.81.138.28])
	by zrc2s0jx.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hBIJScN20676;
	Thu, 18 Dec 2003 13:28:38 -0600 (CST)
Received: by zsc3c028.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <XRCF69QR>; Thu, 18 Dec 2003 11:28:38 -0800
Message-ID: <2F1FC1DEA077D5119FAD00508BCFD6D20CF16BDD@zsc3c030.us.nortel.com>
From: "Francois Audet" <audet@nortelnetworks.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@ericsson.com>,
        "'Dean Willis'"
	 <dean.willis@softarmor.com>
Cc: "'sipping@ietf.org'" <sipping@ietf.org>,
        "'rohan@cisco.com'"
	 <rohan@cisco.com>
Subject: RE: [Sipping] WGLC on Early Media Drafts
Date: Thu, 18 Dec 2003 11:28:29 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3C59D.1D5B4948"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.8 required=5.0 tests=HTML_30_40,HTML_MESSAGE 
	autolearn=no version=2.60

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_01C3C59D.1D5B4948
Content-Type: text/plain

Gonzallo, Dean,

I'm not sure if I like Dean's recommendation, as many terminals may not
be able or may have no need to distinguish between early and regular media.
I would agree however that if you DO want to distinguish between early
and regular media, Dean's recommendation is good.

In my opinion, the use of different ports is recommended only if you
want to distinguish between the early and the regular media.

I would thus reword the sentence like this:

***
If distinguishing between early and regular media is required,
different transport addresses (IP address plus port) MUST 
be used in a session body and in an early-session body. Using 
different transport addresses (e.g., different ports) to 
receive early and regular media makes it easy to detect the 
start of the regular media.
****

Comments?

> -----Original Message-----
> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com] 
> Sent: Tuesday, December 16, 2003 23:11
> To: Dean Willis
> Cc: sipping@ietf.org; rohan@cisco.com
> Subject: Re: [Sipping] WGLC on Early Media Drafts
> 
> 
> Folks,
> 
> I have received one comment on the early media disposition type draft 
> that will be addressed adding the following text at the end 
> of the first 
> paragraph of Section 4:
> 
> ***
> It is also NOT RECOMMENDED to use the same transport address 
> (IP address 
> plus port) in a session body and in an early-session body. Using 
> different transport addresses (e.g., different ports) to 
> receive early 
> and regular media makes it easy to detect the start of the 
> regular media.
> ***
> 
> Gonzalo
> 
> Dean Willis wrote:
> 
> > Based on feedback from the Minneapolis meeting, it seems that the 
> > Early Media work is believed ready to proceed.
> > 
> > Please review:
> > 
> > 
> http://www.ietf.org/internet-drafts/draft-> ietf-sipping-early-media-01.
> > txt
> > 
> > 
> http://www.ietf.org/internet-drafts/draft-> ietf-sipping-early-dispositi
> > on-00.
> > txt
> > 
> > 
> > Please send any comments back to the authors, and copy the list if 
> > your comments are appropriate for public reading (and they SHOULD 
> > be!).
> > 
> > The working group last call for these documents will close 
> January 7, 
> > 2004.
> > 
> > Thanks,
> > 
> > --
> > Dean
> > 
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current 
> sip Use sip@ietf.org for new developments of core SIP
> 

------_=_NextPart_001_01C3C59D.1D5B4948
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.2656.31">
<TITLE>RE: [Sipping] WGLC on Early Media Drafts</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Gonzallo, Dean,</FONT>
</P>

<P><FONT SIZE=3D2>I'm not sure if I like Dean's recommendation, as many =
terminals may not</FONT>
<BR><FONT SIZE=3D2>be able or may have no need to distinguish between =
early and regular media.</FONT>
<BR><FONT SIZE=3D2>I would agree however that if you DO want to =
distinguish between early</FONT>
<BR><FONT SIZE=3D2>and regular media, Dean's recommendation is =
good.</FONT>
</P>

<P><FONT SIZE=3D2>In my opinion, the use of different ports is =
recommended only if you</FONT>
<BR><FONT SIZE=3D2>want to distinguish between the early and the =
regular media.</FONT>
</P>

<P><FONT SIZE=3D2>I would thus reword the sentence like this:</FONT>
</P>

<P><FONT SIZE=3D2>***</FONT>
<BR><FONT SIZE=3D2>If distinguishing between early and regular media is =
required,</FONT>
<BR><FONT SIZE=3D2>different transport addresses (IP address plus port) =
MUST </FONT>
<BR><FONT SIZE=3D2>be used in a session body and in an early-session =
body. Using </FONT>
<BR><FONT SIZE=3D2>different transport addresses (e.g., different =
ports) to </FONT>
<BR><FONT SIZE=3D2>receive early and regular media makes it easy to =
detect the </FONT>
<BR><FONT SIZE=3D2>start of the regular media.</FONT>
<BR><FONT SIZE=3D2>****</FONT>
</P>

<P><FONT SIZE=3D2>Comments?</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Gonzalo Camarillo [<A =
HREF=3D"mailto:Gonzalo.Camarillo@ericsson.com">mailto:Gonzalo.Camarillo@=
ericsson.com</A>] </FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Tuesday, December 16, 2003 23:11</FONT>
<BR><FONT SIZE=3D2>&gt; To: Dean Willis</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: sipping@ietf.org; rohan@cisco.com</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [Sipping] WGLC on Early Media =
Drafts</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Folks,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I have received one comment on the early media =
disposition type draft </FONT>
<BR><FONT SIZE=3D2>&gt; that will be addressed adding the following =
text at the end </FONT>
<BR><FONT SIZE=3D2>&gt; of the first </FONT>
<BR><FONT SIZE=3D2>&gt; paragraph of Section 4:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; ***</FONT>
<BR><FONT SIZE=3D2>&gt; It is also NOT RECOMMENDED to use the same =
transport address </FONT>
<BR><FONT SIZE=3D2>&gt; (IP address </FONT>
<BR><FONT SIZE=3D2>&gt; plus port) in a session body and in an =
early-session body. Using </FONT>
<BR><FONT SIZE=3D2>&gt; different transport addresses (e.g., different =
ports) to </FONT>
<BR><FONT SIZE=3D2>&gt; receive early </FONT>
<BR><FONT SIZE=3D2>&gt; and regular media makes it easy to detect the =
start of the </FONT>
<BR><FONT SIZE=3D2>&gt; regular media.</FONT>
<BR><FONT SIZE=3D2>&gt; ***</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Gonzalo</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Dean Willis wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Based on feedback from the Minneapolis =
meeting, it seems that the </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Early Media work is believed ready to =
proceed.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Please review:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-" =
TARGET=3D"_blank">http://www.ietf.org/internet-drafts/draft-</A>&gt; =
ietf-sipping-early-media-01.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; txt</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-" =
TARGET=3D"_blank">http://www.ietf.org/internet-drafts/draft-</A>&gt; =
ietf-sipping-early-dispositi</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; on-00.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; txt</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Please send any comments back to the =
authors, and copy the list if </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; your comments are appropriate for public =
reading (and they SHOULD </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; be!).</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; The working group last call for these =
documents will close </FONT>
<BR><FONT SIZE=3D2>&gt; January 7, </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; 2004.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Thanks,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; --</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Dean</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Sipping mailing list&nbsp; <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/sipping" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/sipping</A></FO=
NT>
<BR><FONT SIZE=3D2>&gt; This list is for NEW development of the =
application of SIP</FONT>
<BR><FONT SIZE=3D2>&gt; Use sip-implementors@cs.columbia.edu for =
questions on current </FONT>
<BR><FONT SIZE=3D2>&gt; sip Use sip@ietf.org for new developments of =
core SIP</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C3C59D.1D5B4948--

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



From exim@www1.ietf.org  Thu Dec 18 14:54:37 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12085
	for <sipping-archive@odin.ietf.org>; Thu, 18 Dec 2003 14:54:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX4Do-0004Fb-BZ
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 14:54:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBIJs8SS016333
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 14:54:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX4Do-0004FM-6L
	for sipping-web-archive@optimus.ietf.org; Thu, 18 Dec 2003 14:54:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12075
	for <sipping-web-archive@ietf.org>; Thu, 18 Dec 2003 14:54:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX4Dl-0004dm-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 14:54:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX4Dk-0004df-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 14:54:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX4Dk-0004dc-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 14:54:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX4Dh-0004DN-He; Thu, 18 Dec 2003 14:54:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX4DH-0004D6-Bn
	for sipping@optimus.ietf.org; Thu, 18 Dec 2003 14:53:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12059
	for <sipping@ietf.org>; Thu, 18 Dec 2003 14:53:32 -0500 (EST)
From: Mpierce1@aol.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX4DE-0004cc-00
	for sipping@ietf.org; Thu, 18 Dec 2003 14:53:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX4DD-0004cV-00
	for sipping@ietf.org; Thu, 18 Dec 2003 14:53:32 -0500
Received: from imo-d03.mx.aol.com ([205.188.157.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX4DD-0004br-00
	for sipping@ietf.org; Thu, 18 Dec 2003 14:53:31 -0500
Received: from Mpierce1@aol.com
	by imo-d03.mx.aol.com (mail_out_v36_r4.8.) id c.15.1eed8232 (4402);
	Thu, 18 Dec 2003 14:51:19 -0500 (EST)
Message-ID: <15.1eed8232.2d135f37@aol.com>
Date: Thu, 18 Dec 2003 14:51:19 EST
Subject: Re: [sipping] comment on draft-polk-sipping-location-requirements -01.txt
To: mhammer@cisco.com
CC: dick.rr.knight@bt.com, jdrosen@dynamicsoft.com, hgs@cs.columbia.edu,
        Brian.Rosen@marconi.com, sebastien.prouvost@francetelecom.com,
        sipping@ietf.org, jmpolk@cisco.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_15.1eed8232.2d135f37_boundary"
X-Mailer: 6.0 for Windows XP sub 10501
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,HTML_MESSAGE,NO_REAL_NAME 
	autolearn=no version=2.60


--part1_15.1eed8232.2d135f37_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 12/18/2003 11:16:22 AM Eastern Standard Time, 
mhammer@cisco.com writes:


> >Sounds good, but I still don't see how the operator (emergency service 
> >bureau) can make the decision between two conflicting pieces of 
> >information. What specifically can the proxy add to allow this decision to 
> >be made?
> 
> You don't decide, you pass on both pieces of information along with an 
> indication of the source.
> 


I seriously doubt that this would be acceptable to the authorities in the US. 
We need NENA (in the US), and similar organizations in other countries, to 
tell the IETF what the requirements are. Then the IETF can figure out how to do 
it.

Note that a joint press release and 6-point agreement between the VON 
Coalition and NENA on Dec 1 calls for "(c) providing location of caller". It doesn't 
say "providing several possible locations of caller from which the PSAP can 
choose which one it thinks is correct".

Mike


--part1_15.1eed8232.2d135f37_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<HTML><FONT FACE=3Darial,helvetica><FONT  SIZE=3D2 PTSIZE=3D10>In a message=20=
dated 12/18/2003 11:16:22 AM Eastern Standard Time, mhammer@cisco.com writes=
:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-=
LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">&gt;Sounds good, but I stil=
l don't see how the operator (emergency service=20
<BR>&gt;bureau) can make the decision between two conflicting pieces of=20
<BR>&gt;information. What specifically can the proxy add to allow this decis=
ion to=20
<BR>&gt;be made?
<BR>
<BR>You don't decide, you pass on both pieces of information along with an=20
<BR>indication of the source.
<BR></FONT><FONT  COLOR=3D"#000000" BACK=3D"#ffffff" style=3D"BACKGROUND-COL=
OR: #ffffff" SIZE=3D3 PTSIZE=3D12 FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=
=3D"0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR=3D"#000000" BACK=3D"#ffffff" style=3D"BACKGROUND-COL=
OR: #ffffff" SIZE=3D2 PTSIZE=3D10 FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=
=3D"0">
<BR>
<BR>I seriously doubt that this would be acceptable to the authorities in th=
e US. We need NENA (in the US), and similar organizations in other countries=
, to tell the IETF what the requirements are. Then the IETF can figure out h=
ow to do it.
<BR>
<BR>Note that a joint press release and 6-point agreement between the VON Co=
alition and NENA on Dec 1 calls for "(c) providing location of caller". It d=
oesn't say "providing several possible locations of caller from which the PS=
AP can choose which one it thinks is correct".
<BR>
<BR>Mike
<BR></FONT></HTML>

--part1_15.1eed8232.2d135f37_boundary--

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



From exim@www1.ietf.org  Thu Dec 18 15:07:39 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13080
	for <sipping-archive@odin.ietf.org>; Thu, 18 Dec 2003 15:07:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX4QR-0004t9-7r
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 15:07:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBIK7B68018782
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 15:07:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX4QQ-0004sm-TH
	for sipping-web-archive@optimus.ietf.org; Thu, 18 Dec 2003 15:07:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13020
	for <sipping-web-archive@ietf.org>; Thu, 18 Dec 2003 15:07:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX4QN-00058b-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 15:07:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX4QM-00058U-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 15:07:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX4QM-00058R-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 15:07:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX4QH-0004p7-8f; Thu, 18 Dec 2003 15:07:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX4PP-0004oN-IU
	for sipping@optimus.ietf.org; Thu, 18 Dec 2003 15:06:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12905
	for <sipping@ietf.org>; Thu, 18 Dec 2003 15:06:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX4PM-00056t-00
	for sipping@ietf.org; Thu, 18 Dec 2003 15:06:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX4PL-00056m-00
	for sipping@ietf.org; Thu, 18 Dec 2003 15:06:04 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX4PL-00056i-00
	for sipping@ietf.org; Thu, 18 Dec 2003 15:06:03 -0500
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com [64.102.16.27])
	by rtp-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id hBIK5Sxg012041;
	Thu, 18 Dec 2003 15:05:28 -0500 (EST)
Received: from mhammer-w2k03.cisco.com (dhcp-64-100-224-121.cisco.com [64.100.224.121])
	by fruitpie.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AVT31200;
	Thu, 18 Dec 2003 12:05:26 -0800 (PST)
Message-Id: <4.3.2.7.2.20031218150147.00b3b370@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 18 Dec 2003 15:05:26 -0500
To: Mpierce1@aol.com
From: Michael Hammer <mhammer@cisco.com>
Subject: Re: [sipping] comment on
  draft-polk-sipping-location-requirements -01.txt
Cc: dick.rr.knight@bt.com, jdrosen@dynamicsoft.com, hgs@cs.columbia.edu,
        Brian.Rosen@marconi.com, sebastien.prouvost@francetelecom.com,
        sipping@ietf.org, jmpolk@cisco.com
In-Reply-To: <15.1eed8232.2d135f37@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-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

At 02:51 PM 12/18/2003 -0500, Mpierce1@aol.com wrote:
>In a message dated 12/18/2003 11:16:22 AM Eastern Standard Time, 
>mhammer@cisco.com writes:
>
>
>> >Sounds good, but I still don't see how the operator (emergency service
>> >bureau) can make the decision between two conflicting pieces of
>> >information. What specifically can the proxy add to allow this decision to
>> >be made?
>>
>>You don't decide, you pass on both pieces of information along with an
>>indication of the source.
>
>
>
>I seriously doubt that this would be acceptable to the authorities in the 
>US. We need NENA (in the US), and similar organizations in other 
>countries, to tell the IETF what the requirements are. Then the IETF can 
>figure out how to do it.
>
>Note that a joint press release and 6-point agreement between the VON 
>Coalition and NENA on Dec 1 calls for "(c) providing location of caller". 
>It doesn't say "providing several possible locations of caller from which 
>the PSAP can choose which one it thinks is correct".

It doesn't say you can't provide more than one type of measurement, does it?

What liability would a carrier assume if the handset using GPS provided a 
location to 10 meters, and that got over-ridden by a carrier network using 
TOA providing an accuracy of 100 meters, and the ambulance arrives too late?

Also, I wouldn't want to base a solution an an assumption that all parts of 
the network are operated by a single SP.

Mike


>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 exim@www1.ietf.org  Thu Dec 18 15:42:18 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16414
	for <sipping-archive@odin.ietf.org>; Thu, 18 Dec 2003 15:42:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX4uR-0007Wh-F7
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 15:38:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBIKcBBs028922
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 15:38:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX4uQ-0007WK-Sb
	for sipping-web-archive@optimus.ietf.org; Thu, 18 Dec 2003 15:38:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16073
	for <sipping-web-archive@ietf.org>; Thu, 18 Dec 2003 15:38:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX4uP-0006R9-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 15:38:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX4uO-0006R2-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 15:38:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX4uO-0006Qz-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 15:38:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX4uI-0007Ty-HL; Thu, 18 Dec 2003 15:38:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX4to-0007NA-2d
	for sipping@optimus.ietf.org; Thu, 18 Dec 2003 15:37:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16017
	for <sipping@ietf.org>; Thu, 18 Dec 2003 15:37:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX4tm-0006Q1-00
	for sipping@ietf.org; Thu, 18 Dec 2003 15:37:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX4tl-0006Pu-00
	for sipping@ietf.org; Thu, 18 Dec 2003 15:37:30 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX4tl-0006Mq-00
	for sipping@ietf.org; Thu, 18 Dec 2003 15:37:29 -0500
Received: from zcard307.ca.nortel.com (americasm01.nt.com [47.129.242.67])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hBIKanx28960;
	Thu, 18 Dec 2003 15:36:49 -0500 (EST)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard307.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id XLYJVPV7; Thu, 18 Dec 2003 15:36:49 -0500
Received: from nortelnetworks.com (acart1fk.ca.nortel.com [47.129.129.161]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id XLPWND17; Thu, 18 Dec 2003 15:36:49 -0500
Message-ID: <3FE20FE0.2060302@nortelnetworks.com>
Date: Thu, 18 Dec 2003 15:36:48 -0500
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Mpierce1@aol.com
CC: sipping@ietf.org
Subject: Re: [sipping] comment on draft-polk-sipping-location-requirements
 -01.txt
References: <15.1eed8232.2d135f37@aol.com>
In-Reply-To: <15.1eed8232.2d135f37@aol.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

You're implying that NENA is the only game in town.  What about the rest 
of the world?

Mpierce1@aol.com wrote:

> In a message dated 12/18/2003 11:16:22 AM Eastern Standard Time, 
> mhammer@cisco.com writes:
> 
> 
>> >Sounds good, but I still don't see how the operator (emergency service
>> >bureau) can make the decision between two conflicting pieces of
>> >information. What specifically can the proxy add to allow this 
>> decision to
>> >be made?
>>
>> You don't decide, you pass on both pieces of information along with an
>> indication of the source.
> 
> 
> 
> 
> I seriously doubt that this would be acceptable to the authorities in 
> the US. We need NENA (in the US), and similar organizations in other 
> countries, to tell the IETF what the requirements are. Then the IETF can 
> figure out how to do it.
> 
> Note that a joint press release and 6-point agreement between the VON 
> Coalition and NENA on Dec 1 calls for "(c) providing location of 
> caller". It doesn't say "providing several possible locations of caller 
> from which the PSAP can choose which one it thinks is correct".
> 
> 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 exim@www1.ietf.org  Thu Dec 18 15:43:32 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16478
	for <sipping-archive@odin.ietf.org>; Thu, 18 Dec 2003 15:43:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX4z9-0007qZ-P6
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 15:43:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBIKh3Id030157
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 15:43:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX4z9-0007qK-LW
	for sipping-web-archive@optimus.ietf.org; Thu, 18 Dec 2003 15:43:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16457
	for <sipping-web-archive@ietf.org>; Thu, 18 Dec 2003 15:43:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX4z8-0006gx-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 15:43:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX4z6-0006gq-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 15:43:01 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX4z6-0006gn-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 15:43:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX4z7-0007pG-7s; Thu, 18 Dec 2003 15:43:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX4yN-0007oV-PW
	for sipping@optimus.ietf.org; Thu, 18 Dec 2003 15:42:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16412
	for <sipping@ietf.org>; Thu, 18 Dec 2003 15:42:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX4yM-0006gR-00
	for sipping@ietf.org; Thu, 18 Dec 2003 15:42:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX4yL-0006gK-00
	for sipping@ietf.org; Thu, 18 Dec 2003 15:42:13 -0500
Received: from h65s138a81n47.user.nortelnetworks.com ([47.81.138.65] helo=zsc3s004.nortelnetworks.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX4yK-0006ez-00
	for sipping@ietf.org; Thu, 18 Dec 2003 15:42:13 -0500
Received: from zrc2c011.us.nortel.com (zrc2c011.us.nortel.com [47.103.120.51])
	by zsc3s004.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hBIKfXQ25123;
	Thu, 18 Dec 2003 12:41:34 -0800 (PST)
Received: by zrc2c011.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <Y2XS5HM9>; Thu, 18 Dec 2003 14:41:33 -0600
Message-ID: <870397D7C140C84DB081B88396458DAF578E9E@zrc2c000.us.nortel.com>
From: "Mary Barnes" <mary.barnes@nortelnetworks.com>
To: "'Jonathan Rosenberg'" <jdrosen@dynamicsoft.com>,
        sipping
	 <sipping@ietf.org>
Cc: "Brian Stucker" <bstucker@nortelnetworks.com>
Subject: RE: [Sipping] Problem with reg-event that needs immediate fix
Date: Thu, 18 Dec 2003 14:41:31 -0600
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


We agree that it's better to fix this adding the <uri> element rather than
one of the alternatives.   

Regards,
Mary (and Brian S.)
  
-----Original Message-----
From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com]
Sent: Thursday, December 18, 2003 11:13 AM
To: sipping
Subject: [Sipping] Problem with reg-event that needs immediate fix


While implementing the sipping reg-event draft, we ran into a serious 
technical problem.

The problem is that the specification has not left sufficient room for 
extensibility within the XML schema. It allows for new information to 
be added to the <registration> element (which describes the AOR), but 
does not allow any additional information to be provided about a 
contact. We ran into this problem because we needed to add path 
information (ala rfc 3327) to the notifications, but this information 
is per contact. There is no way to do this with the current specification.

The essence of the problem is that the contact element has, as 
content, the actual URI. This makes it difficult to add other 
information about the contact. A better approach would have been to 
make the contact element a complex type, which would include an 
element called <uri> that contains the uri.

For example, today we have:

<?xml version="1.0"?>
    <reginfo xmlns="urn:ietf:params:xml:ns:reginfo"
                 version="1" state="partial">
      <registration aor="sip:joe@bar.com" id="a7" state="active">
        <contact id="76" state="active" event="registered"
                 duration-registered="0">sip:joe@pc34.bar.com</contact>
      </registration>
    </reginfo>

whereas it ought to have been:

<?xml version="1.0"?>
    <reginfo xmlns="urn:ietf:params:xml:ns:reginfo"
                 version="1" state="partial">
      <registration aor="sip:joe@bar.com" id="a7" state="active">
        <contact id="76" state="active" event="registered"
                 duration-registered="0">
                    <uri>sip:joe@pc34.bar.com</uri>
        </contact>
      </registration>
    </reginfo>


The schema for the contact element could then allow for other children 
in other namespaces, giving us the needed extensibility.

Unfortunately, there is other per-contact data we might want to add in 
the not-too-distant future, such as callee-caps information. That kind 
of data would be very useful for presence applications, where the 
presence server could obtain it from the registrar using reg-event.

I believe that this problem is significant enough that we should try 
and address it during auth48. For those of you not familiar with it, 
auth48 is a brief period just before publication of the actual RFC 
where the author can correct typos or minor other problems. It is 
possible, with AD approval, to make more substantive changes as I am 
suggesting (and indeed I already ran this by Allison and she is OK). 
Of course, I still need group consensus on any change. So, here is my 
proposal.

PROPOSAL

My proposal for fixing this, as outlined above, is to modify the XML 
schema. The <contact> element will instead become a complex type. It 
will have, as children, a sequence of <uri> followed by an optional 
element from any other namespace. The <uri> element will contain the 
actual contact URI.

Unfortunately, this proposed solution above is not backwards 
compatible with the current draft.

I considered other solutions as well:


ALTERNATE 1

Modify the schema to allow attributes in the contact element from 
other namespaces. Adds some extensibility, but is very bad for more 
complex data, such as path or callee-cap data. Using attributes for 
that data will require us to define a lot of structure within each 
attribute. This approach is backwards compatible, but not forwards 
compatible. That is, an implementation compliant to the schema before 
this change would reject documents created by an implementation 
compliant to the schema after the change.

ALTERNATE 2

Modify the schema to contain a new element, child to the 
<registration> element. This element would be called "alt-contact", 
and would be defined as I suggest above for contact. Whenever new 
information is needed about a contact, the "alt-contact" element would 
be present, and contain that extension data. The document would also 
still contain a contact element, repeating the URI and other 
attributes. This would provide forwards and backwards compatibility, 
at the expense of a horrible hack that would repeat a lot of 
information in the document.


I found neither of the two alternatives very palatable, which is why 
my proposal is to fix this now, and do it properly, while we still can.

Please provide input on the proposal ASAP. I'd like to come to 
consensus in the next week or so (before everyone disappears for 
vacations).

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



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

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



From exim@www1.ietf.org  Thu Dec 18 16:13:01 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19414
	for <sipping-archive@odin.ietf.org>; Thu, 18 Dec 2003 16:13:00 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX5Rg-0000jt-GQ
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 16:12:32 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBILCWCn002835
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 16:12:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX5Rg-0000je-94
	for sipping-web-archive@optimus.ietf.org; Thu, 18 Dec 2003 16:12:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19265
	for <sipping-web-archive@ietf.org>; Thu, 18 Dec 2003 16:12:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX5Re-0001JB-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 16:12:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX5Rd-0001J4-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 16:12:30 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX5MV-000115-01
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 16:07:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX53x-000844-HH; Thu, 18 Dec 2003 15:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX53n-00083k-1n
	for sipping@optimus.ietf.org; Thu, 18 Dec 2003 15:47:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16682
	for <sipping@ietf.org>; Thu, 18 Dec 2003 15:47:47 -0500 (EST)
From: Mpierce1@aol.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX53j-0006tr-00
	for sipping@ietf.org; Thu, 18 Dec 2003 15:47:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX53g-0006tE-00
	for sipping@ietf.org; Thu, 18 Dec 2003 15:47:47 -0500
Received: from imo-m06.mx.aol.com ([64.12.136.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX53g-0006qY-00
	for sipping@ietf.org; Thu, 18 Dec 2003 15:47:44 -0500
Received: from Mpierce1@aol.com
	by imo-m06.mx.aol.com (mail_out_v36_r4.8.) id c.15c.297fe1ba (4004);
	Thu, 18 Dec 2003 15:46:57 -0500 (EST)
Message-ID: <15c.297fe1ba.2d136c41@aol.com>
Date: Thu, 18 Dec 2003 15:46:57 EST
Subject: Re: [sipping] comment on draft-polk-sipping-location-requirements -01.txt
To: mhammer@cisco.com
CC: sipping@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="part1_15c.297fe1ba.2d136c41_boundary"
X-Mailer: 6.0 for Windows XP sub 10501
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=HTML_MESSAGE,NO_REAL_NAME 
	autolearn=no version=2.60


--part1_15c.297fe1ba.2d136c41_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 12/18/2003 3:05:36 PM Eastern Standard Time, 
mhammer@cisco.com writes:


> It doesn't say you can't provide more than one type of measurement, does it?
> 
> What liability would a carrier assume if the handset using GPS provided a 
> location to 10 meters, and that got over-ridden by a carrier network using 
> TOA providing an accuracy of 100 meters, and the ambulance arrives too late?
> 


More than one type of location is not the problem. I believe all the past 
discussion was that the "handset" and the "carrier" came up with conflicting 
information. If they were not conflicting, then why have two. If they are 
conflicting, that is a problem. If the handset gives a physical location to 10 meters, 
why would the carrier network bother to include a value of 100 meters 
accuracy, if the value from the end user were within that 100 meters? If it isn't, 
what should the PSAP do, send an ambulance to both?

If the handset gave a value within 10 meters and the carrier overwrote it 
with a value accurate to only 100 meters, there would be serious liability 
issues, especially if the requirement were for an accuracy of 50 feet.

Like I said, NENA (or some such organization) needs to say what the 
requirements are (in the US). It is silly and hopeless for the IETF to try to agree on 
"requirements".

Mike


--part1_15c.297fe1ba.2d136c41_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<HTML><FONT FACE=3Darial,helvetica><FONT  SIZE=3D2 PTSIZE=3D10>In a message=20=
dated 12/18/2003 3:05:36 PM Eastern Standard Time, mhammer@cisco.com writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-=
LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">It doesn't say you can't pr=
ovide more than one type of measurement, does it?
<BR>
<BR>What liability would a carrier assume if the handset using GPS provided=20=
a=20
<BR>location to 10 meters, and that got over-ridden by a carrier network usi=
ng=20
<BR>TOA providing an accuracy of 100 meters, and the ambulance arrives too l=
ate?
<BR></FONT><FONT  COLOR=3D"#000000" BACK=3D"#ffffff" style=3D"BACKGROUND-COL=
OR: #ffffff" SIZE=3D3 PTSIZE=3D12 FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=
=3D"0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR=3D"#000000" BACK=3D"#ffffff" style=3D"BACKGROUND-COL=
OR: #ffffff" SIZE=3D2 PTSIZE=3D10 FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=
=3D"0">
<BR>
<BR>More than one type of location is not the problem. I believe all the pas=
t discussion was that the "handset" and the "carrier" came up with conflicti=
ng information. If they were not conflicting, then why have two. If they are=
 conflicting, that is a problem. If the handset gives a physical location to=
 10 meters, why would the carrier network bother to include a value of 100 m=
eters accuracy, if the value from the end user were within that 100 meters?=20=
If it isn't, what should the PSAP do, send an ambulance to both?
<BR>
<BR>If the handset gave a value within 10 meters and the carrier overwrote i=
t with a value accurate to only 100 meters, there would be serious liability=
 issues, especially if the requirement were for an accuracy of 50 feet.
<BR>
<BR>Like I said, NENA (or some such organization) needs to say what the requ=
irements are (in the US). It is silly and hopeless for the IETF to try to ag=
ree on "requirements".
<BR>
<BR>Mike
<BR></FONT></HTML>

--part1_15c.297fe1ba.2d136c41_boundary--

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



From exim@www1.ietf.org  Thu Dec 18 16:49:35 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23258
	for <sipping-archive@odin.ietf.org>; Thu, 18 Dec 2003 16:49:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX616-0002Ox-3L
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 16:49:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBILn8Uk009225
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 16:49:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX615-0002Oi-Vx
	for sipping-web-archive@optimus.ietf.org; Thu, 18 Dec 2003 16:49:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23249
	for <sipping-web-archive@ietf.org>; Thu, 18 Dec 2003 16:49:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX613-0004ap-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 16:49:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX612-0004ai-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 16:49:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX612-0004af-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 16:49:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX60z-0002Ne-7D; Thu, 18 Dec 2003 16:49:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX60w-0002NO-9E
	for sipping@optimus.ietf.org; Thu, 18 Dec 2003 16:48:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23246
	for <sipping@ietf.org>; Thu, 18 Dec 2003 16:48:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX60u-0004ac-00
	for sipping@ietf.org; Thu, 18 Dec 2003 16:48:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX60t-0004aV-00
	for sipping@ietf.org; Thu, 18 Dec 2003 16:48:55 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX60s-0004a1-00
	for sipping@ietf.org; Thu, 18 Dec 2003 16:48:55 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id QAA11297;
	Thu, 18 Dec 2003 16:48:20 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id QAA08690;
	Thu, 18 Dec 2003 16:48:20 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <W9W8265Z>; Thu, 18 Dec 2003 16:48:20 -0500
Message-ID: <313680C9A886D511A06000204840E1CF070B6218@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Mpierce1@aol.com'" <Mpierce1@aol.com>, mhammer@cisco.com
Cc: sipping@ietf.org
Subject: RE: [sipping] comment on draft-polk-sipping-location-requirements
	 -01.txt
Date: Thu, 18 Dec 2003 16:48:11 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

And NENA is working on such requirements, and is starting to engage other 
organizations in other parts of the world.  It has not been decided whether 
there will be multiple, possibly conflicting requirements sent in from 
different organizations, or whether an effort will be mounted to negotiate 
a single set of requirements.  I favor the latter, because we don't have 
the expertise in the IETF to deal with conflicts if they were to arise.  

I'd ask that anyone who knows people who should be involved (NENA 
equivalents in other parts of the world), please contact me. 

Brian


-----Original Message-----
From: Mpierce1@aol.com [mailto:Mpierce1@aol.com]
Sent: Thursday, December 18, 2003 3:47 PM
To: mhammer@cisco.com
Cc: sipping@ietf.org
Subject: Re: [sipping] comment on draft-polk-sipping-location-requirements
-01.txt


In a message dated 12/18/2003 3:05:36 PM Eastern Standard Time,
mhammer@cisco.com writes: 



It doesn't say you can't provide more than one type of measurement, does it?


What liability would a carrier assume if the handset using GPS provided a 
location to 10 meters, and that got over-ridden by a carrier network using 
TOA providing an accuracy of 100 meters, and the ambulance arrives too late?





More than one type of location is not the problem. I believe all the past
discussion was that the "handset" and the "carrier" came up with conflicting
information. If they were not conflicting, then why have two. If they are
conflicting, that is a problem. If the handset gives a physical location to
10 meters, why would the carrier network bother to include a value of 100
meters accuracy, if the value from the end user were within that 100 meters?
If it isn't, what should the PSAP do, send an ambulance to both? 

If the handset gave a value within 10 meters and the carrier overwrote it
with a value accurate to only 100 meters, there would be serious liability
issues, especially if the requirement were for an accuracy of 50 feet. 

Like I said, NENA (or some such organization) needs to say what the
requirements are (in the US). It is silly and hopeless for the IETF to try
to agree on "requirements". 

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 exim@www1.ietf.org  Thu Dec 18 18:20:48 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28002
	for <sipping-archive@odin.ietf.org>; Thu, 18 Dec 2003 18:20:47 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX7RM-0007L3-Ae
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 18:20:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBINKKJw028203
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 18:20:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX7RL-0007Ko-DX
	for sipping-web-archive@optimus.ietf.org; Thu, 18 Dec 2003 18:20:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27979
	for <sipping-web-archive@ietf.org>; Thu, 18 Dec 2003 18:20:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX7RH-0007fo-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 18:20:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX7RG-0007fg-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 18:20:14 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX7RG-0007fd-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 18:20:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX7R5-0007Jh-Qe; Thu, 18 Dec 2003 18:20:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX7QZ-0007Hv-VC
	for sipping@optimus.ietf.org; Thu, 18 Dec 2003 18:19:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27969
	for <sipping@ietf.org>; Thu, 18 Dec 2003 18:19:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX7QX-0007f6-00
	for sipping@ietf.org; Thu, 18 Dec 2003 18:19:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX7QW-0007ez-00
	for sipping@ietf.org; Thu, 18 Dec 2003 18:19:28 -0500
Received: from imr1.ericy.com ([198.24.6.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX7QV-0007eL-00
	for sipping@ietf.org; Thu, 18 Dec 2003 18:19:27 -0500
Received: from eamrcnt750.exu.ericsson.se (eamrcnt750.exu.ericsson.se [138.85.133.51])
	by imr1.ericy.com (8.12.10/8.12.10) with ESMTP id hBINInWm015589;
	Thu, 18 Dec 2003 17:18:49 -0600 (CST)
Received: from ericsson.com (EFO9N000L5C7100 [159.107.1.77]) by eamrcnt750.exu.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id YGLRMPLJ; Thu, 18 Dec 2003 17:18:15 -0600
Message-ID: <3FE235C1.10105@ericsson.com>
Date: Fri, 19 Dec 2003 01:18:25 +0200
X-Sybari-Trust: 8014497c 76be5e0c 125231cb 00000138
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francois Audet <audet@nortelnetworks.com>
CC: "'Dean Willis'" <dean.willis@softarmor.com>,
        "'sipping@ietf.org'" <sipping@ietf.org>,
        "'rohan@cisco.com'" <rohan@cisco.com>
Subject: Re: [Sipping] WGLC on Early Media Drafts
References: <2F1FC1DEA077D5119FAD00508BCFD6D20CF16BDD@zsc3c030.us.nortel.com>
In-Reply-To: <2F1FC1DEA077D5119FAD00508BCFD6D20CF16BDD@zsc3c030.us.nortel.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Francois,

> Gonzallo, Dean,

By the way, Gonzalo only has one "l" ;o)... I know that folks have 
problems spelling your name as well ;o)

> I'm not sure if I like Dean's recommendation

To be clear. I came up with that recommendation when I received a 
comment from Christer.

>, as many terminals may not
> be able or may have no need to distinguish between early and regular media.
> I would agree however that if you DO want to distinguish between early
> and regular media, Dean's recommendation is good.
> 
> In my opinion, the use of different ports is recommended only if you
> want to distinguish between the early and the regular media.

I am aware that some implementors, in particular gateway vendors, will 
use the same port anyway. That's why it is a NOT RECOMMENDED, instead of 
a MUST NOT. Nevertheless, from the standard point of view, you really 
need to distinguish between early and regular media every time, because 
if you do not do it, and the INVITE forks, you may get media clipping or 
mixing of media (early and regular) from different sources.

I believe that the NOT RECOMMENDED is a good compromise between what the 
standard should say about a general situation and what the implementors 
will do in controlled environments.

Thanks,

Gonzalo


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



From exim@www1.ietf.org  Thu Dec 18 18:37:36 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28576
	for <sipping-archive@odin.ietf.org>; Thu, 18 Dec 2003 18:37:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX7hd-00083K-Ja
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 18:37:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBINb9Zr030947
	for sipping-archive@odin.ietf.org; Thu, 18 Dec 2003 18:37:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX7hd-000821-4h
	for sipping-web-archive@optimus.ietf.org; Thu, 18 Dec 2003 18:37:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28537
	for <sipping-web-archive@ietf.org>; Thu, 18 Dec 2003 18:37:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX7hZ-0000ET-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 18:37:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX7hY-0000EL-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 18:37:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX7hY-0000EI-00
	for sipping-web-archive@ietf.org; Thu, 18 Dec 2003 18:37:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX7hV-0007yH-RD; Thu, 18 Dec 2003 18:37:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX7gZ-0007v0-4a
	for sipping@optimus.ietf.org; Thu, 18 Dec 2003 18:36:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28457
	for <sipping@ietf.org>; Thu, 18 Dec 2003 18:35:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX7gW-0000Cw-00
	for sipping@ietf.org; Thu, 18 Dec 2003 18:36:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX7gU-0000Cg-00
	for sipping@ietf.org; Thu, 18 Dec 2003 18:35:59 -0500
Received: from h65s138a81n47.user.nortelnetworks.com ([47.81.138.65] helo=zsc3s004.nortelnetworks.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX7gT-0000C5-00
	for sipping@ietf.org; Thu, 18 Dec 2003 18:35:57 -0500
Received: from zsc3c028.us.nortel.com (zsc3c028.us.nortel.com [47.81.138.28])
	by zsc3s004.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hBINZMv24484;
	Thu, 18 Dec 2003 15:35:23 -0800 (PST)
Received: by zsc3c028.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <XRCF7N8D>; Thu, 18 Dec 2003 15:35:22 -0800
Message-ID: <2F1FC1DEA077D5119FAD00508BCFD6D20CF17266@zsc3c030.us.nortel.com>
From: "Francois Audet" <audet@nortelnetworks.com>
To: "'Gonzalo Camarillo'" <Gonzalo.Camarillo@ericsson.com>
Cc: "'Dean Willis'" <dean.willis@softarmor.com>,
        "'sipping@ietf.org'"
	 <sipping@ietf.org>,
        "'rohan@cisco.com'" <rohan@cisco.com>
Subject: RE: [Sipping] WGLC on Early Media Drafts
Date: Thu, 18 Dec 2003 15:35:13 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3C5BF.957547A4"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE 
	autolearn=no version=2.60

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_01C3C5BF.957547A4
Content-Type: text/plain

> I am aware that some implementors, in particular gateway 
> vendors, will 
> use the same port anyway. That's why it is a NOT RECOMMENDED, 
> instead of 
> a MUST NOT. Nevertheless, from the standard point of view, you really 
> need to distinguish between early and regular media every 
> time, because 
> if you do not do it, and the INVITE forks, you may get media 
> clipping or 
> mixing of media (early and regular) from different sources.
> 
> I believe that the NOT RECOMMENDED is a good compromise 
> between what the 
> standard should say about a general situation and what the 
> implementors 
> will do in controlled environments.

I hadn't tought about gateways, but you are right that it would double
the number of required ports.

There are other issues as well, even for IP phones.

Using 2 different ports will mean that if you are using STUN, you will need
one more STUN query for the early media port. Same thing for ICE.

Then if you are using RSVP or NSIS, it will mean that you have to double the
procedures.

It just makes the process heavier in those cases.

Anyways, this is not a big issue to me, so I am OK with it.

------_=_NextPart_001_01C3C5BF.957547A4
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.2656.31">
<TITLE>RE: [Sipping] WGLC on Early Media Drafts</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>&gt; I am aware that some implementors, in particular gateway </FONT>
<BR><FONT SIZE=2>&gt; vendors, will </FONT>
<BR><FONT SIZE=2>&gt; use the same port anyway. That's why it is a NOT RECOMMENDED, </FONT>
<BR><FONT SIZE=2>&gt; instead of </FONT>
<BR><FONT SIZE=2>&gt; a MUST NOT. Nevertheless, from the standard point of view, you really </FONT>
<BR><FONT SIZE=2>&gt; need to distinguish between early and regular media every </FONT>
<BR><FONT SIZE=2>&gt; time, because </FONT>
<BR><FONT SIZE=2>&gt; if you do not do it, and the INVITE forks, you may get media </FONT>
<BR><FONT SIZE=2>&gt; clipping or </FONT>
<BR><FONT SIZE=2>&gt; mixing of media (early and regular) from different sources.</FONT>
<BR><FONT SIZE=2>&gt; </FONT>
<BR><FONT SIZE=2>&gt; I believe that the NOT RECOMMENDED is a good compromise </FONT>
<BR><FONT SIZE=2>&gt; between what the </FONT>
<BR><FONT SIZE=2>&gt; standard should say about a general situation and what the </FONT>
<BR><FONT SIZE=2>&gt; implementors </FONT>
<BR><FONT SIZE=2>&gt; will do in controlled environments.</FONT>
</P>

<P><FONT SIZE=2>I hadn't tought about gateways, but you are right that it would double</FONT>
<BR><FONT SIZE=2>the number of required ports.</FONT>
</P>

<P><FONT SIZE=2>There are other issues as well, even for IP phones.</FONT>
</P>

<P><FONT SIZE=2>Using 2 different ports will mean that if you are using STUN, you will need</FONT>
<BR><FONT SIZE=2>one more STUN query for the early media port. Same thing for ICE.</FONT>
</P>

<P><FONT SIZE=2>Then if you are using RSVP or NSIS, it will mean that you have to double the procedures.</FONT>
</P>

<P><FONT SIZE=2>It just makes the process heavier in those cases.</FONT>
</P>

<P><FONT SIZE=2>Anyways, this is not a big issue to me, so I am OK with it.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C3C5BF.957547A4--

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



From exim@www1.ietf.org  Fri Dec 19 02:44:46 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28271
	for <sipping-archive@odin.ietf.org>; Fri, 19 Dec 2003 02:44:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXFJ4-0004qT-9X
	for sipping-archive@odin.ietf.org; Fri, 19 Dec 2003 02:44:18 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBJ7iIIw018626
	for sipping-archive@odin.ietf.org; Fri, 19 Dec 2003 02:44:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXFJ3-0004qL-Cb
	for sipping-web-archive@optimus.ietf.org; Fri, 19 Dec 2003 02:44:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28265
	for <sipping-web-archive@ietf.org>; Fri, 19 Dec 2003 02:44:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXFIz-0000zA-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 02:44:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXFIy-0000z3-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 02:44:13 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXFIy-0000z0-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 02:44:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXFIo-0004oz-8a; Fri, 19 Dec 2003 02:44:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXFI4-0004nx-8s
	for sipping@optimus.ietf.org; Fri, 19 Dec 2003 02:43:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28261
	for <sipping@ietf.org>; Fri, 19 Dec 2003 02:43:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXFI0-0000yi-00
	for sipping@ietf.org; Fri, 19 Dec 2003 02:43:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXFHz-0000yb-00
	for sipping@ietf.org; Fri, 19 Dec 2003 02:43:12 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXFHy-0000yY-00
	for sipping@ietf.org; Fri, 19 Dec 2003 02:43:10 -0500
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8) with ESMTP id hBJ7h5I2012641;
	Fri, 19 Dec 2003 08:43:06 +0100 (MET)
Received: from ericsson.com (EFQ240013L1IJOG.lmf.ericsson.se [131.160.31.37]) by esealnt610.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id Z1FTXHKL; Fri, 19 Dec 2003 08:43:11 +0100
Message-ID: <3FE2AC09.1020809@ericsson.com>
Date: Fri, 19 Dec 2003 09:43:05 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en, es
MIME-Version: 1.0
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
CC: sipping <sipping@ietf.org>
Subject: Re: [Sipping] Problem with reg-event that needs immediate fix
References: <3FE1E027.2090305@dynamicsoft.com>
In-Reply-To: <3FE1E027.2090305@dynamicsoft.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Jonathan:

Thanks for catching this problem and reporting it.

I support your main proposal of turning the <contact> element into a 
complex type. It seems to be the clean solution.

As you may know, 3GPP is using this draft, so I would expect other 3GPP 
folks to express their opinions as well.

/Miguel

Jonathan Rosenberg wrote:

> While implementing the sipping reg-event draft, we ran into a serious 
> technical problem.
> 
> The problem is that the specification has not left sufficient room for 
> extensibility within the XML schema. It allows for new information to be 
> added to the <registration> element (which describes the AOR), but does 
> not allow any additional information to be provided about a contact. We 
> ran into this problem because we needed to add path information (ala rfc 
> 3327) to the notifications, but this information is per contact. There 
> is no way to do this with the current specification.
> 
> The essence of the problem is that the contact element has, as content, 
> the actual URI. This makes it difficult to add other information about 
> the contact. A better approach would have been to make the contact 
> element a complex type, which would include an element called <uri> that 
> contains the uri.
> 
> For example, today we have:
> 
> <?xml version="1.0"?>
>    <reginfo xmlns="urn:ietf:params:xml:ns:reginfo"
>                 version="1" state="partial">
>      <registration aor="sip:joe@bar.com" id="a7" state="active">
>        <contact id="76" state="active" event="registered"
>                 duration-registered="0">sip:joe@pc34.bar.com</contact>
>      </registration>
>    </reginfo>
> 
> whereas it ought to have been:
> 
> <?xml version="1.0"?>
>    <reginfo xmlns="urn:ietf:params:xml:ns:reginfo"
>                 version="1" state="partial">
>      <registration aor="sip:joe@bar.com" id="a7" state="active">
>        <contact id="76" state="active" event="registered"
>                 duration-registered="0">
>                    <uri>sip:joe@pc34.bar.com</uri>
>        </contact>
>      </registration>
>    </reginfo>
> 
> 
> The schema for the contact element could then allow for other children 
> in other namespaces, giving us the needed extensibility.
> 
> Unfortunately, there is other per-contact data we might want to add in 
> the not-too-distant future, such as callee-caps information. That kind 
> of data would be very useful for presence applications, where the 
> presence server could obtain it from the registrar using reg-event.
> 
> I believe that this problem is significant enough that we should try and 
> address it during auth48. For those of you not familiar with it, auth48 
> is a brief period just before publication of the actual RFC where the 
> author can correct typos or minor other problems. It is possible, with 
> AD approval, to make more substantive changes as I am suggesting (and 
> indeed I already ran this by Allison and she is OK). Of course, I still 
> need group consensus on any change. So, here is my proposal.
> 
> PROPOSAL
> 
> My proposal for fixing this, as outlined above, is to modify the XML 
> schema. The <contact> element will instead become a complex type. It 
> will have, as children, a sequence of <uri> followed by an optional 
> element from any other namespace. The <uri> element will contain the 
> actual contact URI.
> 
> Unfortunately, this proposed solution above is not backwards compatible 
> with the current draft.
> 
> I considered other solutions as well:
> 
> 
> ALTERNATE 1
> 
> Modify the schema to allow attributes in the contact element from other 
> namespaces. Adds some extensibility, but is very bad for more complex 
> data, such as path or callee-cap data. Using attributes for that data 
> will require us to define a lot of structure within each attribute. This 
> approach is backwards compatible, but not forwards compatible. That is, 
> an implementation compliant to the schema before this change would 
> reject documents created by an implementation compliant to the schema 
> after the change.
> 
> ALTERNATE 2
> 
> Modify the schema to contain a new element, child to the <registration> 
> element. This element would be called "alt-contact", and would be 
> defined as I suggest above for contact. Whenever new information is 
> needed about a contact, the "alt-contact" element would be present, and 
> contain that extension data. The document would also still contain a 
> contact element, repeating the URI and other attributes. This would 
> provide forwards and backwards compatibility, at the expense of a 
> horrible hack that would repeat a lot of information in the document.
> 
> 
> I found neither of the two alternatives very palatable, which is why my 
> proposal is to fix this now, and do it properly, while we still can.
> 
> Please provide input on the proposal ASAP. I'd like to come to consensus 
> in the next week or so (before everyone disappears for vacations).
> 
> Thanks,
> Jonathan R.

-- 
Miguel-Angel Garcia                     Oy LM Ericsson AB
                                         Jorvas, Finland
mailto:Miguel.A.Garcia@ericsson.com     Phone:  +358 9 299 3553
mailto:Miguel.A.Garcia@piuha.net        Mobile: +358 40 514 0002


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



From exim@www1.ietf.org  Fri Dec 19 08:50:54 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09029
	for <sipping-archive@odin.ietf.org>; Fri, 19 Dec 2003 08:50:54 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXL1I-0000vT-Ip
	for sipping-archive@odin.ietf.org; Fri, 19 Dec 2003 08:50:25 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBJDoKV9003555
	for sipping-archive@odin.ietf.org; Fri, 19 Dec 2003 08:50:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXL1I-0000vG-Dz
	for sipping-web-archive@optimus.ietf.org; Fri, 19 Dec 2003 08:50:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09015
	for <sipping-web-archive@ietf.org>; Fri, 19 Dec 2003 08:50:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXL1G-0003Ve-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 08:50:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXL1F-0003VW-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 08:50:18 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXL1F-0003VT-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 08:50:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXL11-0000ri-6e; Fri, 19 Dec 2003 08:50:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXL0C-0000r0-Uk
	for sipping@optimus.ietf.org; Fri, 19 Dec 2003 08:49:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08993
	for <sipping@ietf.org>; Fri, 19 Dec 2003 08:49:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXL0B-0003Th-00
	for sipping@ietf.org; Fri, 19 Dec 2003 08:49:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXL0A-0003Ta-00
	for sipping@ietf.org; Fri, 19 Dec 2003 08:49:11 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXL09-0003TU-00
	for sipping@ietf.org; Fri, 19 Dec 2003 08:49:10 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id IAA28811;
	Fri, 19 Dec 2003 08:47:47 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id IAA29059;
	Fri, 19 Dec 2003 08:47:43 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <W9W8JK7Y>; Fri, 19 Dec 2003 08:47:43 -0500
Message-ID: <313680C9A886D511A06000204840E1CF070B621F@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: =?iso-8859-1?Q?=27PROUVOST_S=E9bastien_FTRD/DAC/ISS=27?=
	 <sebastien.prouvost@francetelecom.com>,
        Mpierce1@aol.com, mhammer@cisco.com
Cc: sipping@ietf.org, Henning Schulzrinne <hgs@cs.columbia.edu>,
        Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Subject: RE: RE : [sipping] comment on draft-polk-sipping-location-require
	ments -01.txt
Date: Fri, 19 Dec 2003 08:47:39 -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: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

S=E9bastien

There will HAVE to be a single worldwide set of requirements for
emergency services, because the Internet does not respect national=20
boundaries, and we ALREADY see the effect of this on calls to=20
emergency services.

My usual example would be a patron of a Paris cafe using a WiFi=20
hotspot with a VPN tunnel open to her employers network, in which=20
she is running a sip softclient.  If an accident occurs outside=20
the cafe, and she uses her softclient to call for help, how does=20
the employer, which could be located in another continent,=20
and using its local VoIP carrier, be subject to any=20
laws/specifications of France?  It cannot.  And the hotspot=20
operator, which might be subject to some regulation, is unaware=20
that there is a VoIP call, let alone a call to the emergency system,
and in fact there is likely encryption on the tunnel making it
impossible for it to figure it out.

However, if there is an international standard, such as we produce=20
here in the IETF, then it is VERY likely that the softclient,=20
the employer's PBX, and the VoIP carrier are able to correctly=20
handle the call, routing it to the correct emergency answering point,=20
and including call-back information as well as location information. =20
It is only an international standard that will work as the Internet=20
joins fixed, mobile and roaming users with a variety of devices,=20
proxies and carriers operating over multiple continents.

The IETF has a history of not sanctioning regional variations in
its specifications, and, as the above example illustrates, it is
not feasible to implement regional or national variations.  The
reality of the situation is that regulating emergency calls is
not possible with VoIP (unless there was an international treaty
that had universal applicability), but a single, effective
international standard is very possible.

Such a standard needs an agreed set of requirements, of course.

I've stated my views on the proxy insertion of location. =20

Brian


-----Original Message-----
From: PROUVOST S=E9bastien FTRD/DAC/ISS
[mailto:sebastien.prouvost@francetelecom.com]
Sent: Friday, December 19, 2003 6:32 AM
To: Rosen, Brian; Mpierce1@aol.com; mhammer@cisco.com
Cc: sipping@ietf.org; Henning Schulzrinne; Jonathan Rosenberg
Subject: RE : [sipping] comment on
draft-polk-sipping-location-requirements -01.txt


Two points here :
=20
First I doubt that there will be a single world wide set of =
requirements for
emergency calls.

Second, a requirement listed in the original draft was for a proxy to =
be
able to give its idea of the terminal location (originally by asserting =
the
location given by the terminal). However, it may be easier for a proxy =
to
insert its own info about the location of the terminal rather than to =
assert
the info given by the terminal. It also let the possibility to the =
called
party to get both pieces of information which is useful information as
pointed out by Jonathan. Both pieces of information shall be passed on.


S=E9bastien Prouvost
France T=E9l=E9com R&D/DAC/CAR


-----Message d'origine-----
De : Rosen, Brian [mailto:Brian.Rosen@marconi.com]=20
Envoy=E9 : jeudi 18 d=E9cembre 2003 22:48
=C0 : 'Mpierce1@aol.com'; mhammer@cisco.com
Cc : sipping@ietf.org
Objet : RE: [sipping] comment on =
draft-polk-sipping-location-requirements
-01.txt


And NENA is working on such requirements, and is starting to engage =
other=20
organizations in other parts of the world.  It has not been decided =
whether=20
there will be multiple, possibly conflicting requirements sent in from=20
different organizations, or whether an effort will be mounted to =
negotiate=20
a single set of requirements.  I favor the latter, because we don't =
have=20
the expertise in the IETF to deal with conflicts if they were to arise. =
=20

I'd ask that anyone who knows people who should be involved (NENA=20
equivalents in other parts of the world), please contact me.=20

Brian


-----Original Message-----
From: Mpierce1@aol.com [mailto:Mpierce1@aol.com]
Sent: Thursday, December 18, 2003 3:47 PM
To: mhammer@cisco.com
Cc: sipping@ietf.org
Subject: Re: [sipping] comment on =
draft-polk-sipping-location-requirements
-01.txt


In a message dated 12/18/2003 3:05:36 PM Eastern Standard Time,
mhammer@cisco.com writes:=20



It doesn't say you can't provide more than one type of measurement, =
does it?


What liability would a carrier assume if the handset using GPS provided =
a=20
location to 10 meters, and that got over-ridden by a carrier network =
using=20
TOA providing an accuracy of 100 meters, and the ambulance arrives too =
late?





More than one type of location is not the problem. I believe all the =
past
discussion was that the "handset" and the "carrier" came up with =
conflicting
information. If they were not conflicting, then why have two. If they =
are
conflicting, that is a problem. If the handset gives a physical =
location to
10 meters, why would the carrier network bother to include a value of =
100
meters accuracy, if the value from the end user were within that 100 =
meters?
If it isn't, what should the PSAP do, send an ambulance to both?=20

If the handset gave a value within 10 meters and the carrier overwrote =
it
with a value accurate to only 100 meters, there would be serious =
liability
issues, especially if the requirement were for an accuracy of 50 feet.=20

Like I said, NENA (or some such organization) needs to say what the
requirements are (in the US). It is silly and hopeless for the IETF to =
try
to agree on "requirements".=20

Mike=20

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

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



From exim@www1.ietf.org  Fri Dec 19 09:12:39 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09768
	for <sipping-archive@odin.ietf.org>; Fri, 19 Dec 2003 09:12:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXLMQ-0001pc-F1
	for sipping-archive@odin.ietf.org; Fri, 19 Dec 2003 09:12:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBJECArI007034
	for sipping-archive@odin.ietf.org; Fri, 19 Dec 2003 09:12:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXLMQ-0001pN-AM
	for sipping-web-archive@optimus.ietf.org; Fri, 19 Dec 2003 09:12:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09739
	for <sipping-web-archive@ietf.org>; Fri, 19 Dec 2003 09:12:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXLMO-0004D9-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 09:12:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXLML-0004Ck-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 09:12:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXLML-0004Cg-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 09:12:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXLMH-0001nH-FF; Fri, 19 Dec 2003 09:12:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXLLg-0001lq-Ja
	for sipping@optimus.ietf.org; Fri, 19 Dec 2003 09:11:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09673
	for <sipping@ietf.org>; Fri, 19 Dec 2003 09:11:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXLLe-00046L-00
	for sipping@ietf.org; Fri, 19 Dec 2003 09:11:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXLLb-00045t-00
	for sipping@ietf.org; Fri, 19 Dec 2003 09:11:22 -0500
Received: from zcars04e.nortelnetworks.com ([47.129.242.56])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXLLb-00045C-00
	for sipping@ietf.org; Fri, 19 Dec 2003 09:11:19 -0500
Received: from zcard307.ca.nortel.com (zcard307.ca.nortel.com [47.129.242.67])
	by zcars04e.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id hBJEAff16660;
	Fri, 19 Dec 2003 09:10:41 -0500 (EST)
Received: from zcard0kc.ca.nortel.com ([47.129.242.164]) by zcard307.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id XLYJXH29; Fri, 19 Dec 2003 09:10:42 -0500
Received: from nortelnetworks.com (acart1g0.ca.nortel.com [47.129.129.175]) by zcard0kc.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id XLPWNDKV; Fri, 19 Dec 2003 09:10:41 -0500
Message-ID: <3FE306E0.8000206@nortelnetworks.com>
Date: Fri, 19 Dec 2003 09:10:40 -0500
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Tom Taylor <taylor@nortelnetworks.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Rosen, Brian" <Brian.Rosen@marconi.com>
CC: sipping@ietf.org
Subject: Re: RE : [sipping] comment on draft-polk-sipping-location-require
 ments -01.txt
References: <313680C9A886D511A06000204840E1CF070B621F@whq-msgusr-02.pit.comms.marconi.com>
In-Reply-To: <313680C9A886D511A06000204840E1CF070B621F@whq-msgusr-02.pit.comms.marconi.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by zcars04e.nortelnetworks.com id hBJEAff16660
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

It's nice to think we might put together a solution that works for all=20
situations, but my own analysis suggested that may not be possible.  It=20
depends amongst other things on the administrative arrangements within a=20
given country.  The sensible thing for the the VPN tunneler is to use=20
alternate means -- i.e. yell for help.

Rosen, Brian wrote:

> S=E9bastien
>=20
> There will HAVE to be a single worldwide set of requirements for
> emergency services, because the Internet does not respect national=20
> boundaries, and we ALREADY see the effect of this on calls to=20
> emergency services.
>=20
> My usual example would be a patron of a Paris cafe using a WiFi=20
> hotspot with a VPN tunnel open to her employers network, in which=20
> she is running a sip softclient.  If an accident occurs outside=20
> the cafe, and she uses her softclient to call for help, how does=20
> the employer, which could be located in another continent,=20
> and using its local VoIP carrier, be subject to any=20
> laws/specifications of France?  It cannot.  And the hotspot=20
> operator, which might be subject to some regulation, is unaware=20
> that there is a VoIP call, let alone a call to the emergency system,
> and in fact there is likely encryption on the tunnel making it
> impossible for it to figure it out.
>=20
> However, if there is an international standard, such as we produce=20
> here in the IETF, then it is VERY likely that the softclient,=20
> the employer's PBX, and the VoIP carrier are able to correctly=20
> handle the call, routing it to the correct emergency answering point,=20
> and including call-back information as well as location information. =20
> It is only an international standard that will work as the Internet=20
> joins fixed, mobile and roaming users with a variety of devices,=20
> proxies and carriers operating over multiple continents.
>=20
> The IETF has a history of not sanctioning regional variations in
> its specifications, and, as the above example illustrates, it is
> not feasible to implement regional or national variations.  The
> reality of the situation is that regulating emergency calls is
> not possible with VoIP (unless there was an international treaty
> that had universal applicability), but a single, effective
> international standard is very possible.
>=20
> Such a standard needs an agreed set of requirements, of course.
>=20
> I've stated my views on the proxy insertion of location. =20
>=20
> Brian
>=20
>=20
> -----Original Message-----
> From: PROUVOST S=E9bastien FTRD/DAC/ISS
> [mailto:sebastien.prouvost@francetelecom.com]
> Sent: Friday, December 19, 2003 6:32 AM
> To: Rosen, Brian; Mpierce1@aol.com; mhammer@cisco.com
> Cc: sipping@ietf.org; Henning Schulzrinne; Jonathan Rosenberg
> Subject: RE : [sipping] comment on
> draft-polk-sipping-location-requirements -01.txt
>=20
>=20
> Two points here :
> =20
> First I doubt that there will be a single world wide set of requirement=
s for
> emergency calls.
>=20
> Second, a requirement listed in the original draft was for a proxy to b=
e
> able to give its idea of the terminal location (originally by asserting=
 the
> location given by the terminal). However, it may be easier for a proxy =
to
> insert its own info about the location of the terminal rather than to a=
ssert
> the info given by the terminal. It also let the possibility to the call=
ed
> party to get both pieces of information which is useful information as
> pointed out by Jonathan. Both pieces of information shall be passed on.
>=20
>=20
> S=E9bastien Prouvost
> France T=E9l=E9com R&D/DAC/CAR
>=20
>=20
> -----Message d'origine-----
> De : Rosen, Brian [mailto:Brian.Rosen@marconi.com]=20
> Envoy=E9 : jeudi 18 d=E9cembre 2003 22:48
> =C0 : 'Mpierce1@aol.com'; mhammer@cisco.com
> Cc : sipping@ietf.org
> Objet : RE: [sipping] comment on draft-polk-sipping-location-requiremen=
ts
> -01.txt
>=20
>=20
> And NENA is working on such requirements, and is starting to engage oth=
er=20
> organizations in other parts of the world.  It has not been decided whe=
ther=20
> there will be multiple, possibly conflicting requirements sent in from=20
> different organizations, or whether an effort will be mounted to negoti=
ate=20
> a single set of requirements.  I favor the latter, because we don't hav=
e=20
> the expertise in the IETF to deal with conflicts if they were to arise.=
 =20
>=20
> I'd ask that anyone who knows people who should be involved (NENA=20
> equivalents in other parts of the world), please contact me.=20
>=20
> Brian
>=20
>=20
> -----Original Message-----
> From: Mpierce1@aol.com [mailto:Mpierce1@aol.com]
> Sent: Thursday, December 18, 2003 3:47 PM
> To: mhammer@cisco.com
> Cc: sipping@ietf.org
> Subject: Re: [sipping] comment on draft-polk-sipping-location-requireme=
nts
> -01.txt
>=20
>=20
> In a message dated 12/18/2003 3:05:36 PM Eastern Standard Time,
> mhammer@cisco.com writes:=20
>=20
>=20
>=20
> It doesn't say you can't provide more than one type of measurement, doe=
s it?
>=20
>=20
> What liability would a carrier assume if the handset using GPS provided=
 a=20
> location to 10 meters, and that got over-ridden by a carrier network us=
ing=20
> TOA providing an accuracy of 100 meters, and the ambulance arrives too =
late?
>=20
>=20
>=20
>=20
>=20
> More than one type of location is not the problem. I believe all the pa=
st
> discussion was that the "handset" and the "carrier" came up with confli=
cting
> information. If they were not conflicting, then why have two. If they a=
re
> conflicting, that is a problem. If the handset gives a physical locatio=
n to
> 10 meters, why would the carrier network bother to include a value of 1=
00
> meters accuracy, if the value from the end user were within that 100 me=
ters?
> If it isn't, what should the PSAP do, send an ambulance to both?=20
>=20
> If the handset gave a value within 10 meters and the carrier overwrote =
it
> with a value accurate to only 100 meters, there would be serious liabil=
ity
> issues, especially if the requirement were for an accuracy of 50 feet.=20
>=20
> Like I said, NENA (or some such organization) needs to say what the
> requirements are (in the US). It is silly and hopeless for the IETF to =
try
> to agree on "requirements".=20
>=20
> Mike=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip Use
> sip@ietf.org for new developments of core SIP
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>=20


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



From exim@www1.ietf.org  Fri Dec 19 09:21:34 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09971
	for <sipping-archive@odin.ietf.org>; Fri, 19 Dec 2003 09:21:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXLV3-0002CR-Gc
	for sipping-archive@odin.ietf.org; Fri, 19 Dec 2003 09:21:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBJEL5HA008449
	for sipping-archive@odin.ietf.org; Fri, 19 Dec 2003 09:21:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXLV3-0002CC-CB
	for sipping-web-archive@optimus.ietf.org; Fri, 19 Dec 2003 09:21:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09955
	for <sipping-web-archive@ietf.org>; Fri, 19 Dec 2003 09:21:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXLV1-0004Q4-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 09:21:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXLUz-0004Px-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 09:21:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXLUz-0004Pu-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 09:21:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXLV0-0002B1-5I; Fri, 19 Dec 2003 09:21:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXLUb-0002AE-OX
	for sipping@optimus.ietf.org; Fri, 19 Dec 2003 09:20:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09941
	for <sipping@ietf.org>; Fri, 19 Dec 2003 09:20:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXLUa-0004PH-00
	for sipping@ietf.org; Fri, 19 Dec 2003 09:20:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXLUY-0004PA-00
	for sipping@ietf.org; Fri, 19 Dec 2003 09:20:35 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXLUY-0004Nw-00
	for sipping@ietf.org; Fri, 19 Dec 2003 09:20:34 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA29847;
	Fri, 19 Dec 2003 09:19:40 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA03443;
	Fri, 19 Dec 2003 09:18:52 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <W9W8JL5A>; Fri, 19 Dec 2003 09:18:51 -0500
Message-ID: <313680C9A886D511A06000204840E1CF070B6223@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Tom Taylor'" <taylor@nortelnetworks.com>
Cc: sipping@ietf.org
Subject: RE: RE : [sipping] comment on draft-polk-sipping-location-require
	 ments -01.txt
Date: Fri, 19 Dec 2003 09:18:42 -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: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Tom

It's always hard to work in a situation where politics intrudes. =20
This is one of them.  As engineers, all we can do is sit down with our=20
counterparts and try to work through the engineering issues. =20
In the IETF, this usually works pretty well.  Some countries chose=20
to try to assert more control over the entities that they can regulate. =
=20
That's going to happen.  However, I think our history shows that our=20
process works pretty well, and we are able to build systems that are=20
universally applicable, scale well, and perform to user's satisfaction. =
=20
I believe that it is possible to do so here, and I'm going to be =
working=20
hard to make it happen.

So far, most of the people I've been able to talk to have come around
to the idea that regulation won't work with VoIP but cooperative =
standards
will.  Your Mileage May Vary.

Brian

-----Original Message-----
From: Tom Taylor [mailto:taylor@nortelnetworks.com]
Sent: Friday, December 19, 2003 9:11 AM
To: Rosen, Brian
Cc: sipping@ietf.org
Subject: Re: RE : [sipping] comment on
draft-polk-sipping-location-require ments -01.txt


It's nice to think we might put together a solution that works for all=20
situations, but my own analysis suggested that may not be possible.  It =

depends amongst other things on the administrative arrangements within =
a=20
given country.  The sensible thing for the the VPN tunneler is to use=20
alternate means -- i.e. yell for help.

Rosen, Brian wrote:

> S=E9bastien
>=20
> There will HAVE to be a single worldwide set of requirements for
> emergency services, because the Internet does not respect national=20
> boundaries, and we ALREADY see the effect of this on calls to=20
> emergency services.
>=20
> My usual example would be a patron of a Paris cafe using a WiFi=20
> hotspot with a VPN tunnel open to her employers network, in which=20
> she is running a sip softclient.  If an accident occurs outside=20
> the cafe, and she uses her softclient to call for help, how does=20
> the employer, which could be located in another continent,=20
> and using its local VoIP carrier, be subject to any=20
> laws/specifications of France?  It cannot.  And the hotspot=20
> operator, which might be subject to some regulation, is unaware=20
> that there is a VoIP call, let alone a call to the emergency system,
> and in fact there is likely encryption on the tunnel making it
> impossible for it to figure it out.
>=20
> However, if there is an international standard, such as we produce=20
> here in the IETF, then it is VERY likely that the softclient,=20
> the employer's PBX, and the VoIP carrier are able to correctly=20
> handle the call, routing it to the correct emergency answering point, =

> and including call-back information as well as location information.  =

> It is only an international standard that will work as the Internet=20
> joins fixed, mobile and roaming users with a variety of devices,=20
> proxies and carriers operating over multiple continents.
>=20
> The IETF has a history of not sanctioning regional variations in
> its specifications, and, as the above example illustrates, it is
> not feasible to implement regional or national variations.  The
> reality of the situation is that regulating emergency calls is
> not possible with VoIP (unless there was an international treaty
> that had universal applicability), but a single, effective
> international standard is very possible.
>=20
> Such a standard needs an agreed set of requirements, of course.
>=20
> I've stated my views on the proxy insertion of location. =20
>=20
> Brian
>=20
>=20
> -----Original Message-----
> From: PROUVOST S=E9bastien FTRD/DAC/ISS
> [mailto:sebastien.prouvost@francetelecom.com]
> Sent: Friday, December 19, 2003 6:32 AM
> To: Rosen, Brian; Mpierce1@aol.com; mhammer@cisco.com
> Cc: sipping@ietf.org; Henning Schulzrinne; Jonathan Rosenberg
> Subject: RE : [sipping] comment on
> draft-polk-sipping-location-requirements -01.txt
>=20
>=20
> Two points here :
> =20
> First I doubt that there will be a single world wide set of =
requirements
for
> emergency calls.
>=20
> Second, a requirement listed in the original draft was for a proxy to =
be
> able to give its idea of the terminal location (originally by =
asserting
the
> location given by the terminal). However, it may be easier for a =
proxy to
> insert its own info about the location of the terminal rather than to
assert
> the info given by the terminal. It also let the possibility to the =
called
> party to get both pieces of information which is useful information =
as
> pointed out by Jonathan. Both pieces of information shall be passed =
on.
>=20
>=20
> S=E9bastien Prouvost
> France T=E9l=E9com R&D/DAC/CAR
>=20
>=20
> -----Message d'origine-----
> De : Rosen, Brian [mailto:Brian.Rosen@marconi.com]=20
> Envoy=E9 : jeudi 18 d=E9cembre 2003 22:48
> =C0 : 'Mpierce1@aol.com'; mhammer@cisco.com
> Cc : sipping@ietf.org
> Objet : RE: [sipping] comment on =
draft-polk-sipping-location-requirements
> -01.txt
>=20
>=20
> And NENA is working on such requirements, and is starting to engage =
other=20
> organizations in other parts of the world.  It has not been decided
whether=20
> there will be multiple, possibly conflicting requirements sent in =
from=20
> different organizations, or whether an effort will be mounted to =
negotiate

> a single set of requirements.  I favor the latter, because we don't =
have=20
> the expertise in the IETF to deal with conflicts if they were to =
arise. =20
>=20
> I'd ask that anyone who knows people who should be involved (NENA=20
> equivalents in other parts of the world), please contact me.=20
>=20
> Brian
>=20
>=20
> -----Original Message-----
> From: Mpierce1@aol.com [mailto:Mpierce1@aol.com]
> Sent: Thursday, December 18, 2003 3:47 PM
> To: mhammer@cisco.com
> Cc: sipping@ietf.org
> Subject: Re: [sipping] comment on =
draft-polk-sipping-location-requirements
> -01.txt
>=20
>=20
> In a message dated 12/18/2003 3:05:36 PM Eastern Standard Time,
> mhammer@cisco.com writes:=20
>=20
>=20
>=20
> It doesn't say you can't provide more than one type of measurement, =
does
it?
>=20
>=20
> What liability would a carrier assume if the handset using GPS =
provided a=20
> location to 10 meters, and that got over-ridden by a carrier network =
using

> TOA providing an accuracy of 100 meters, and the ambulance arrives =
too
late?
>=20
>=20
>=20
>=20
>=20
> More than one type of location is not the problem. I believe all the =
past
> discussion was that the "handset" and the "carrier" came up with
conflicting
> information. If they were not conflicting, then why have two. If they =
are
> conflicting, that is a problem. If the handset gives a physical =
location
to
> 10 meters, why would the carrier network bother to include a value of =
100
> meters accuracy, if the value from the end user were within that 100
meters?
> If it isn't, what should the PSAP do, send an ambulance to both?=20
>=20
> If the handset gave a value within 10 meters and the carrier =
overwrote it
> with a value accurate to only 100 meters, there would be serious =
liability
> issues, especially if the requirement were for an accuracy of 50 =
feet.=20
>=20
> Like I said, NENA (or some such organization) needs to say what the
> requirements are (in the US). It is silly and hopeless for the IETF =
to try
> to agree on "requirements".=20
>=20
> Mike=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip Use
> sip@ietf.org for new developments of core SIP
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>=20

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



From exim@www1.ietf.org  Fri Dec 19 09:40:40 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10491
	for <sipping-archive@odin.ietf.org>; Fri, 19 Dec 2003 09:40:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXLnX-0003Hn-FW
	for sipping-archive@odin.ietf.org; Fri, 19 Dec 2003 09:40:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBJEeBcn012625
	for sipping-archive@odin.ietf.org; Fri, 19 Dec 2003 09:40:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXLnX-0003HW-2e
	for sipping-web-archive@optimus.ietf.org; Fri, 19 Dec 2003 09:40:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10482
	for <sipping-web-archive@ietf.org>; Fri, 19 Dec 2003 09:40:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXLnT-0004vl-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 09:40:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXLnS-0004ve-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 09:40:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXLnS-0004vb-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 09:40:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXLnP-0003G2-Oj; Fri, 19 Dec 2003 09:40:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXLmf-0003EW-Ev
	for sipping@optimus.ietf.org; Fri, 19 Dec 2003 09:39:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10455
	for <sipping@ietf.org>; Fri, 19 Dec 2003 09:39:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXLmc-0004tg-00
	for sipping@ietf.org; Fri, 19 Dec 2003 09:39:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXLmK-0004tD-00
	for sipping@ietf.org; Fri, 19 Dec 2003 09:38:57 -0500
Received: from smtpsrv11.isis.unc.edu ([152.2.1.242] helo=smtp.unc.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXLmK-0004sX-00
	for sipping@ietf.org; Fri, 19 Dec 2003 09:38:56 -0500
Received: from email.unc.edu (dhcp25895.wireless.unc.edu [152.23.139.241])
	(authenticated bits=0)
	by smtp.unc.edu (8.12.9/8.12.9) with ESMTP id hBJEbtEQ028049;
	Fri, 19 Dec 2003 09:37:55 -0500 (EST)
Message-ID: <3FE30D42.7000400@email.unc.edu>
Date: Fri, 19 Dec 2003 09:37:54 -0500
From: Tyler Johnson <trjohns1@email.unc.edu>
Reply-To: Tyler_Johnson@unc.edu
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 (CK-UNC-CH)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Rosen, Brian" <Brian.Rosen@marconi.com>
CC: =?ISO-8859-1?Q?=27PROUVOST_S=E9bastien_FTRD/DAC/ISS=27?=
 <sebastien.prouvost@francetelecom.com>,
        Mpierce1@aol.com, mhammer@cisco.com, sipping@ietf.org,
        Henning Schulzrinne
 <hgs@cs.columbia.edu>,
        Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Subject: Re: RE : [sipping] comment on draft-polk-sipping-location-require
 ments -01.txt
References: <313680C9A886D511A06000204840E1CF070B621F@whq-msgusr-02.pit.comms.marconi.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by smtp.unc.edu id hBJEbtEQ028049
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

All,

I have been following this discussion with some interest. It seems to me=20
that in trying to create a 911 service for VoIP, we are applying an old=20
paradigm to a new technology.

I think that emergency services are important for many applications, and=20
VoIP is just one. For example, I should be able to summon help from my=20
email, IM device, Blackberry, etc. Further, I can see a 'Help I've=20
fallen and I can't get up' 802.11b panic pendant for grandmothers. As IP=20
is deployed, it will become increasingly important to provide these=20
services, and municipalities will mandate it.

Because of this, I very much agree with Brian's notion that the physical=20
(or layer 2) network should provide the emergency service signalling.=20
However, it strikes me that it is not appropriate to build this=20
functionality into SIP or the VoIP application. Rather, it should be=20
developed as a standalone generic service (outside of SIPPING) that can=20
be accessed by any application. Then, SIPPING could point to it as the=20
emergency services method of choice.

I am concerned that if we build emergency services into VoIP, then VoIP=20
emergency services will quickly become obsolete as the pace of other IP=20
applications requiring emergency services quickens.

Rosen, Brian wrote:
> S=E9bastien
>=20
> There will HAVE to be a single worldwide set of requirements for
> emergency services, because the Internet does not respect national=20
> boundaries, and we ALREADY see the effect of this on calls to=20
> emergency services.
>=20
> My usual example would be a patron of a Paris cafe using a WiFi=20
> hotspot with a VPN tunnel open to her employers network, in which=20
> she is running a sip softclient.  If an accident occurs outside=20
> the cafe, and she uses her softclient to call for help, how does=20
> the employer, which could be located in another continent,=20
> and using its local VoIP carrier, be subject to any=20
> laws/specifications of France?  It cannot.  And the hotspot=20
> operator, which might be subject to some regulation, is unaware=20
> that there is a VoIP call, let alone a call to the emergency system,
> and in fact there is likely encryption on the tunnel making it
> impossible for it to figure it out.
>=20
> However, if there is an international standard, such as we produce=20
> here in the IETF, then it is VERY likely that the softclient,=20
> the employer's PBX, and the VoIP carrier are able to correctly=20
> handle the call, routing it to the correct emergency answering point,=20
> and including call-back information as well as location information. =20
> It is only an international standard that will work as the Internet=20
> joins fixed, mobile and roaming users with a variety of devices,=20
> proxies and carriers operating over multiple continents.
>=20
> The IETF has a history of not sanctioning regional variations in
> its specifications, and, as the above example illustrates, it is
> not feasible to implement regional or national variations.  The
> reality of the situation is that regulating emergency calls is
> not possible with VoIP (unless there was an international treaty
> that had universal applicability), but a single, effective
> international standard is very possible.
>=20
> Such a standard needs an agreed set of requirements, of course.
>=20
> I've stated my views on the proxy insertion of location. =20
>=20
> Brian
>=20
>=20
> -----Original Message-----
> From: PROUVOST S=E9bastien FTRD/DAC/ISS
> [mailto:sebastien.prouvost@francetelecom.com]
> Sent: Friday, December 19, 2003 6:32 AM
> To: Rosen, Brian; Mpierce1@aol.com; mhammer@cisco.com
> Cc: sipping@ietf.org; Henning Schulzrinne; Jonathan Rosenberg
> Subject: RE : [sipping] comment on
> draft-polk-sipping-location-requirements -01.txt
>=20
>=20
> Two points here :
> =20
> First I doubt that there will be a single world wide set of requirement=
s for
> emergency calls.
>=20
> Second, a requirement listed in the original draft was for a proxy to b=
e
> able to give its idea of the terminal location (originally by asserting=
 the
> location given by the terminal). However, it may be easier for a proxy =
to
> insert its own info about the location of the terminal rather than to a=
ssert
> the info given by the terminal. It also let the possibility to the call=
ed
> party to get both pieces of information which is useful information as
> pointed out by Jonathan. Both pieces of information shall be passed on.
>=20
>=20
> S=E9bastien Prouvost
> France T=E9l=E9com R&D/DAC/CAR
>=20
>=20
> -----Message d'origine-----
> De : Rosen, Brian [mailto:Brian.Rosen@marconi.com]=20
> Envoy=E9 : jeudi 18 d=E9cembre 2003 22:48
> =C0 : 'Mpierce1@aol.com'; mhammer@cisco.com
> Cc : sipping@ietf.org
> Objet : RE: [sipping] comment on draft-polk-sipping-location-requiremen=
ts
> -01.txt
>=20
>=20
> And NENA is working on such requirements, and is starting to engage oth=
er=20
> organizations in other parts of the world.  It has not been decided whe=
ther=20
> there will be multiple, possibly conflicting requirements sent in from=20
> different organizations, or whether an effort will be mounted to negoti=
ate=20
> a single set of requirements.  I favor the latter, because we don't hav=
e=20
> the expertise in the IETF to deal with conflicts if they were to arise.=
 =20
>=20
> I'd ask that anyone who knows people who should be involved (NENA=20
> equivalents in other parts of the world), please contact me.=20
>=20
> Brian
>=20
>=20
> -----Original Message-----
> From: Mpierce1@aol.com [mailto:Mpierce1@aol.com]
> Sent: Thursday, December 18, 2003 3:47 PM
> To: mhammer@cisco.com
> Cc: sipping@ietf.org
> Subject: Re: [sipping] comment on draft-polk-sipping-location-requireme=
nts
> -01.txt
>=20
>=20
> In a message dated 12/18/2003 3:05:36 PM Eastern Standard Time,
> mhammer@cisco.com writes:=20
>=20
>=20
>=20
> It doesn't say you can't provide more than one type of measurement, doe=
s it?
>=20
>=20
> What liability would a carrier assume if the handset using GPS provided=
 a=20
> location to 10 meters, and that got over-ridden by a carrier network us=
ing=20
> TOA providing an accuracy of 100 meters, and the ambulance arrives too =
late?
>=20
>=20
>=20
>=20
>=20
> More than one type of location is not the problem. I believe all the pa=
st
> discussion was that the "handset" and the "carrier" came up with confli=
cting
> information. If they were not conflicting, then why have two. If they a=
re
> conflicting, that is a problem. If the handset gives a physical locatio=
n to
> 10 meters, why would the carrier network bother to include a value of 1=
00
> meters accuracy, if the value from the end user were within that 100 me=
ters?
> If it isn't, what should the PSAP do, send an ambulance to both?=20
>=20
> If the handset gave a value within 10 meters and the carrier overwrote =
it
> with a value accurate to only 100 meters, there would be serious liabil=
ity
> issues, especially if the requirement were for an accuracy of 50 feet.=20
>=20
> Like I said, NENA (or some such organization) needs to say what the
> requirements are (in the US). It is silly and hopeless for the IETF to =
try
> to agree on "requirements".=20
>=20
> Mike=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip Use
> sip@ietf.org for new developments of core SIP
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP



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



From exim@www1.ietf.org  Fri Dec 19 10:34:35 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13342
	for <sipping-archive@odin.ietf.org>; Fri, 19 Dec 2003 10:34:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXMdg-0005Eg-UN
	for sipping-archive@odin.ietf.org; Fri, 19 Dec 2003 10:34:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBJFY422020126
	for sipping-archive@odin.ietf.org; Fri, 19 Dec 2003 10:34:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXMdg-0005EX-Me
	for sipping-web-archive@optimus.ietf.org; Fri, 19 Dec 2003 10:34:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13286
	for <sipping-web-archive@ietf.org>; Fri, 19 Dec 2003 10:34:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXMdY-0006ac-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 10:33:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXMd7-0006aC-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 10:33:31 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXMd7-0006a2-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 10:33:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXMcf-000558-3V; Fri, 19 Dec 2003 10:33:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXMbz-00054h-Eq
	for sipping@optimus.ietf.org; Fri, 19 Dec 2003 10:32:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13204
	for <sipping@ietf.org>; Fri, 19 Dec 2003 10:32:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXMbn-0006YN-00
	for sipping@ietf.org; Fri, 19 Dec 2003 10:32:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXMbM-0006Xv-00
	for sipping@ietf.org; Fri, 19 Dec 2003 10:31:41 -0500
Received: from mail.oefeg.at ([62.47.121.5])
	by ietf-mx with smtp (Exim 4.12)
	id 1AXMbL-0006Uz-00
	for sipping@ietf.org; Fri, 19 Dec 2003 10:31:39 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: RE : [sipping] comment on draft-polk-sipping-location-require ments -01.txt
Date: Fri, 19 Dec 2003 16:36:11 +0100
Message-ID: <06CF906FE3998C4E944213062009F162233A5B@oefeg-s02.oefeg.loc>
Thread-Topic: RE : [sipping] comment on draft-polk-sipping-location-require ments -01.txt
Thread-Index: AcPGPtIyiJc4l+vNQ9C10MFazFxtKgABFykQ
From: "Stastny Richard" <Richard.Stastny@oefeg.at>
To: <Tyler_Johnson@unc.edu>, "Rosen, Brian" <Brian.Rosen@marconi.com>
Cc: =?iso-8859-1?Q?PROUVOST_S=E9bastien_FTRD/DAC/ISS?= <sebastien.prouvost@francetelecom.com>,
        <Mpierce1@aol.com>, <mhammer@cisco.com>, <sipping@ietf.org>,
        "Henning Schulzrinne" <hgs@cs.columbia.edu>,
        "Jonathan Rosenberg" <jdrosen@dynamicsoft.com>
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

I fully agree.

I also was following this and previous discussions with interest, =
because this issue
pops up periodicly over and over again and always dies away because no =
solution
on the application layer is possible in mobile environments (at least =
non has been found yet).
GPS does not work, user entry does not work, DHCP does not work because =
of VPNs,=20
User profile does not work, etc.

So the only possiblity is a very simple basic protocol on layer 2, lets
call it SEP (Simple Emergency Protocol).

If this protocol is simple enough, it may be mandated by regulators to =
be implemented
in every IP access environment and also in any IP access device and it =
should also
work like 112 in mobiles without login to the environment.

The required SW could be made mandatory and part of all IP-enabled =
operating systems.
In its simplest varity it could work with a simple click on a =
(soft)button, it could also use
existing applications (e-mail, chat, SIP, etc.) if available, but this =
is out of scope.

To put the necessary parameters in the access device and get access from =
any device cannot be too complicated.

I propose to set up an own WG to deal with this asap.

best regards
Richard

> -----Original Message-----
> From: Tyler Johnson [mailto:trjohns1@email.unc.edu]=20
> Sent: Friday, December 19, 2003 3:38 PM
> To: Rosen, Brian
> Cc: 'PROUVOST S=E9bastien FTRD/DAC/ISS'; Mpierce1@aol.com;=20
> mhammer@cisco.com; sipping@ietf.org; Henning Schulzrinne;=20
> Jonathan Rosenberg
> Subject: Re: RE : [sipping] comment on=20
> draft-polk-sipping-location-require ments -01.txt
>=20
>=20
> All,
>=20
> I have been following this discussion with some interest. It=20
> seems to me=20
> that in trying to create a 911 service for VoIP, we are=20
> applying an old=20
> paradigm to a new technology.
>=20
> I think that emergency services are important for many=20
> applications, and=20
> VoIP is just one. For example, I should be able to summon=20
> help from my=20
> email, IM device, Blackberry, etc. Further, I can see a 'Help I've=20
> fallen and I can't get up' 802.11b panic pendant for=20
> grandmothers. As IP=20
> is deployed, it will become increasingly important to provide these=20
> services, and municipalities will mandate it.
>=20
> Because of this, I very much agree with Brian's notion that=20
> the physical=20
> (or layer 2) network should provide the emergency service signalling.=20
> However, it strikes me that it is not appropriate to build this=20
> functionality into SIP or the VoIP application. Rather, it should be=20
> developed as a standalone generic service (outside of=20
> SIPPING) that can=20
> be accessed by any application. Then, SIPPING could point to=20
> it as the=20
> emergency services method of choice.
>=20
> I am concerned that if we build emergency services into VoIP,=20
> then VoIP=20
> emergency services will quickly become obsolete as the pace=20
> of other IP=20
> applications requiring emergency services quickens.
>=20
> Rosen, Brian wrote:
> > S=E9bastien
> >=20
> > There will HAVE to be a single worldwide set of requirements for=20
> > emergency services, because the Internet does not respect national=20
> > boundaries, and we ALREADY see the effect of this on calls to=20
> > emergency services.
> >=20
> > My usual example would be a patron of a Paris cafe using a WiFi
> > hotspot with a VPN tunnel open to her employers network, in which=20
> > she is running a sip softclient.  If an accident occurs outside=20
> > the cafe, and she uses her softclient to call for help, how does=20
> > the employer, which could be located in another continent,=20
> > and using its local VoIP carrier, be subject to any=20
> > laws/specifications of France?  It cannot.  And the hotspot=20
> > operator, which might be subject to some regulation, is unaware=20
> > that there is a VoIP call, let alone a call to the emergency system,
> > and in fact there is likely encryption on the tunnel making it
> > impossible for it to figure it out.
> >=20
> > However, if there is an international standard, such as we produce
> > here in the IETF, then it is VERY likely that the softclient,=20
> > the employer's PBX, and the VoIP carrier are able to correctly=20
> > handle the call, routing it to the correct emergency=20
> answering point,=20
> > and including call-back information as well as location=20
> information. =20
> > It is only an international standard that will work as the Internet=20
> > joins fixed, mobile and roaming users with a variety of devices,=20
> > proxies and carriers operating over multiple continents.
> >=20
> > The IETF has a history of not sanctioning regional=20
> variations in its=20
> > specifications, and, as the above example illustrates, it is not=20
> > feasible to implement regional or national variations.  The=20
> reality of=20
> > the situation is that regulating emergency calls is not=20
> possible with=20
> > VoIP (unless there was an international treaty that had universal=20
> > applicability), but a single, effective international=20
> standard is very=20
> > possible.
> >=20
> > Such a standard needs an agreed set of requirements, of course.
> >=20
> > I've stated my views on the proxy insertion of location.
> >=20
> > Brian
> >=20
> >=20
> > -----Original Message-----
> > From: PROUVOST S=E9bastien FTRD/DAC/ISS=20
> > [mailto:sebastien.prouvost@francetelecom.com]
> > Sent: Friday, December 19, 2003 6:32 AM
> > To: Rosen, Brian; Mpierce1@aol.com; mhammer@cisco.com
> > Cc: sipping@ietf.org; Henning Schulzrinne; Jonathan Rosenberg
> > Subject: RE : [sipping] comment on=20
> > draft-polk-sipping-location-requirements -01.txt
> >=20
> >=20
> > Two points here :
> > =20
> > First I doubt that there will be a single world wide set of=20
> > requirements for emergency calls.
> >=20
> > Second, a requirement listed in the original draft was for=20
> a proxy to=20
> > be able to give its idea of the terminal location (originally by=20
> > asserting the location given by the terminal). However, it may be=20
> > easier for a proxy to insert its own info about the location of the=20
> > terminal rather than to assert the info given by the=20
> terminal. It also=20
> > let the possibility to the called party to get both pieces of=20
> > information which is useful information as pointed out by Jonathan.=20
> > Both pieces of information shall be passed on.
> >=20
> >=20
> > S=E9bastien Prouvost
> > France T=E9l=E9com R&D/DAC/CAR
> >=20
> >=20
> > -----Message d'origine-----
> > De : Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> > Envoy=E9 : jeudi 18 d=E9cembre 2003 22:48
> > =C0 : 'Mpierce1@aol.com'; mhammer@cisco.com
> > Cc : sipping@ietf.org
> > Objet : RE: [sipping] comment on=20
> draft-polk-sipping-location-requirements
> > -01.txt
> >=20
> >=20
> > And NENA is working on such requirements, and is starting to engage=20
> > other
> > organizations in other parts of the world.  It has not been=20
> decided whether=20
> > there will be multiple, possibly conflicting requirements=20
> sent in from=20
> > different organizations, or whether an effort will be=20
> mounted to negotiate=20
> > a single set of requirements.  I favor the latter, because=20
> we don't have=20
> > the expertise in the IETF to deal with conflicts if they=20
> were to arise. =20
> >=20
> > I'd ask that anyone who knows people who should be involved (NENA
> > equivalents in other parts of the world), please contact me.=20
> >=20
> > Brian
> >=20
> >=20
> > -----Original Message-----
> > From: Mpierce1@aol.com [mailto:Mpierce1@aol.com]
> > Sent: Thursday, December 18, 2003 3:47 PM
> > To: mhammer@cisco.com
> > Cc: sipping@ietf.org
> > Subject: Re: [sipping] comment on=20
> > draft-polk-sipping-location-requirements
> > -01.txt
> >=20
> >=20
> > In a message dated 12/18/2003 3:05:36 PM Eastern Standard Time,=20
> > mhammer@cisco.com writes:
> >=20
> >=20
> >=20
> > It doesn't say you can't provide more than one type of measurement,=20
> > does it?
> >=20
> >=20
> > What liability would a carrier assume if the handset using GPS=20
> > provided a
> > location to 10 meters, and that got over-ridden by a=20
> carrier network using=20
> > TOA providing an accuracy of 100 meters, and the ambulance=20
> arrives too late?
> >=20
> >=20
> >=20
> >=20
> >=20
> > More than one type of location is not the problem. I=20
> believe all the=20
> > past discussion was that the "handset" and the "carrier"=20
> came up with=20
> > conflicting information. If they were not conflicting, then=20
> why have=20
> > two. If they are conflicting, that is a problem. If the=20
> handset gives=20
> > a physical location to 10 meters, why would the carrier=20
> network bother=20
> > to include a value of 100 meters accuracy, if the value=20
> from the end=20
> > user were within that 100 meters? If it isn't, what should the PSAP=20
> > do, send an ambulance to both?
> >=20
> > If the handset gave a value within 10 meters and the=20
> carrier overwrote=20
> > it with a value accurate to only 100 meters, there would be serious=20
> > liability issues, especially if the requirement were for an=20
> accuracy=20
> > of 50 feet.
> >=20
> > Like I said, NENA (or some such organization) needs to say what the=20
> > requirements are (in the US). It is silly and hopeless for=20
> the IETF to=20
> > try to agree on "requirements".
> >=20
> > Mike
> >=20
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP Use=20
> > sip-implementors@cs.columbia.edu for questions on current sip Use=20
> > sip@ietf.org for new developments of core SIP
> >=20
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP Use=20
> > sip-implementors@cs.columbia.edu for questions on current sip Use=20
> > sip@ietf.org for new developments of core SIP
>=20
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current=20
> sip Use sip@ietf.org for new developments of core SIP
>=20

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



From exim@www1.ietf.org  Fri Dec 19 10:39:33 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13541
	for <sipping-archive@odin.ietf.org>; Fri, 19 Dec 2003 10:39:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXMiY-0005hW-Be
	for sipping-archive@odin.ietf.org; Fri, 19 Dec 2003 10:39:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBJFd6U5021908
	for sipping-archive@odin.ietf.org; Fri, 19 Dec 2003 10:39:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXMiY-0005hF-6q
	for sipping-web-archive@optimus.ietf.org; Fri, 19 Dec 2003 10:39:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13521
	for <sipping-web-archive@ietf.org>; Fri, 19 Dec 2003 10:39:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXMiV-0006iS-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 10:39:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXMiS-0006i8-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 10:39:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXMiS-0006i5-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 10:39:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXMiT-0005er-Un; Fri, 19 Dec 2003 10:39:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXMiH-0005eO-Mo
	for sipping@optimus.ietf.org; Fri, 19 Dec 2003 10:38:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13510
	for <sipping@ietf.org>; Fri, 19 Dec 2003 10:38:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXMiF-0006ho-00
	for sipping@ietf.org; Fri, 19 Dec 2003 10:38:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXMiC-0006he-00
	for sipping@ietf.org; Fri, 19 Dec 2003 10:38:45 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXMiA-0006gc-00
	for sipping@ietf.org; Fri, 19 Dec 2003 10:38:43 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA02364;
	Fri, 19 Dec 2003 10:24:03 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA14227;
	Fri, 19 Dec 2003 10:23:31 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <W9W8J3H7>; Fri, 19 Dec 2003 10:23:30 -0500
Message-ID: <313680C9A886D511A06000204840E1CF070B6225@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Tyler_Johnson@unc.edu'" <Tyler_Johnson@unc.edu>
Cc: =?iso-8859-1?Q?=27PROUVOST_S=E9bastien_FTRD/DAC/ISS=27?=
	 <sebastien.prouvost@francetelecom.com>,
        Mpierce1@aol.com, mhammer@cisco.com, sipping@ietf.org,
        Henning Schulzrinne
	 <hgs@cs.columbia.edu>,
        Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Subject: RE: RE : [sipping] comment on draft-polk-sipping-location-require
	 ments -01.txt
Date: Fri, 19 Dec 2003 10:23:23 -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: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Tyler

You are leaping pretty far, and I think you are pushing beyond anyone's
comfort zone.
The world of emergency calling is pretty limited in how far they are =
willing
to change paradigms.  I'm having a LOT of trouble just getting them to
understand
that they really do have to deal with scenarios like I described.  They =
are
readily able to understand, and appreciate, that calls to emergency =
services
will be multimedia.  When you have a mobile phone with a camera, and =
there
is hazardous materials, people will want to see the images.  IM will be =
a
way to
communicate, as TTY users already do, and the list goes on.

However, to get off the notion that its a "call" to the psap is over =
the top
I think.  SIP is pretty good here; you can have any kind of media in =
the
call,
but its still a call.  So, at least now, I'm not interested in =
extracting
emergency call from SIP.  One reality is that the emergency centers =
really
want to communicate human to human in real time because their =
experience
with
anything automatic is pretty poor.  They take the call, but they don't =
like
it,
because the automatic mechanisms frequently cause the wrong response.  =
They
like pendants, but they want them to have a microphone and a speaker at
least.
"Help I've fallen and I can't get up" is followed by a lot of questions =
that
determine what help to send.  They really want a callback identifier, a
location
and all the rest of the things that sip gives you.

Brian

-----Original Message-----
From: Tyler Johnson [mailto:trjohns1@email.unc.edu]
Sent: Friday, December 19, 2003 9:38 AM
To: Rosen, Brian
Cc: 'PROUVOST S=E9bastien FTRD/DAC/ISS'; Mpierce1@aol.com;
mhammer@cisco.com; sipping@ietf.org; Henning Schulzrinne; Jonathan
Rosenberg
Subject: Re: RE : [sipping] comment on
draft-polk-sipping-location-require ments -01.txt


All,

I have been following this discussion with some interest. It seems to =
me=20
that in trying to create a 911 service for VoIP, we are applying an old =

paradigm to a new technology.

I think that emergency services are important for many applications, =
and=20
VoIP is just one. For example, I should be able to summon help from my=20
email, IM device, Blackberry, etc. Further, I can see a 'Help I've=20
fallen and I can't get up' 802.11b panic pendant for grandmothers. As =
IP=20
is deployed, it will become increasingly important to provide these=20
services, and municipalities will mandate it.

Because of this, I very much agree with Brian's notion that the =
physical=20
(or layer 2) network should provide the emergency service signalling.=20
However, it strikes me that it is not appropriate to build this=20
functionality into SIP or the VoIP application. Rather, it should be=20
developed as a standalone generic service (outside of SIPPING) that can =

be accessed by any application. Then, SIPPING could point to it as the=20
emergency services method of choice.

I am concerned that if we build emergency services into VoIP, then VoIP =

emergency services will quickly become obsolete as the pace of other IP =

applications requiring emergency services quickens.

Rosen, Brian wrote:
> S=E9bastien
>=20
> There will HAVE to be a single worldwide set of requirements for
> emergency services, because the Internet does not respect national=20
> boundaries, and we ALREADY see the effect of this on calls to=20
> emergency services.
>=20
> My usual example would be a patron of a Paris cafe using a WiFi=20
> hotspot with a VPN tunnel open to her employers network, in which=20
> she is running a sip softclient.  If an accident occurs outside=20
> the cafe, and she uses her softclient to call for help, how does=20
> the employer, which could be located in another continent,=20
> and using its local VoIP carrier, be subject to any=20
> laws/specifications of France?  It cannot.  And the hotspot=20
> operator, which might be subject to some regulation, is unaware=20
> that there is a VoIP call, let alone a call to the emergency system,
> and in fact there is likely encryption on the tunnel making it
> impossible for it to figure it out.
>=20
> However, if there is an international standard, such as we produce=20
> here in the IETF, then it is VERY likely that the softclient,=20
> the employer's PBX, and the VoIP carrier are able to correctly=20
> handle the call, routing it to the correct emergency answering point, =

> and including call-back information as well as location information.  =

> It is only an international standard that will work as the Internet=20
> joins fixed, mobile and roaming users with a variety of devices,=20
> proxies and carriers operating over multiple continents.
>=20
> The IETF has a history of not sanctioning regional variations in
> its specifications, and, as the above example illustrates, it is
> not feasible to implement regional or national variations.  The
> reality of the situation is that regulating emergency calls is
> not possible with VoIP (unless there was an international treaty
> that had universal applicability), but a single, effective
> international standard is very possible.
>=20
> Such a standard needs an agreed set of requirements, of course.
>=20
> I've stated my views on the proxy insertion of location. =20
>=20
> Brian
>=20
>=20
> -----Original Message-----
> From: PROUVOST S=E9bastien FTRD/DAC/ISS
> [mailto:sebastien.prouvost@francetelecom.com]
> Sent: Friday, December 19, 2003 6:32 AM
> To: Rosen, Brian; Mpierce1@aol.com; mhammer@cisco.com
> Cc: sipping@ietf.org; Henning Schulzrinne; Jonathan Rosenberg
> Subject: RE : [sipping] comment on
> draft-polk-sipping-location-requirements -01.txt
>=20
>=20
> Two points here :
> =20
> First I doubt that there will be a single world wide set of =
requirements
for
> emergency calls.
>=20
> Second, a requirement listed in the original draft was for a proxy to =
be
> able to give its idea of the terminal location (originally by =
asserting
the
> location given by the terminal). However, it may be easier for a =
proxy to
> insert its own info about the location of the terminal rather than to
assert
> the info given by the terminal. It also let the possibility to the =
called
> party to get both pieces of information which is useful information =
as
> pointed out by Jonathan. Both pieces of information shall be passed =
on.
>=20
>=20
> S=E9bastien Prouvost
> France T=E9l=E9com R&D/DAC/CAR
>=20
>=20
> -----Message d'origine-----
> De : Rosen, Brian [mailto:Brian.Rosen@marconi.com]=20
> Envoy=E9 : jeudi 18 d=E9cembre 2003 22:48
> =C0 : 'Mpierce1@aol.com'; mhammer@cisco.com
> Cc : sipping@ietf.org
> Objet : RE: [sipping] comment on =
draft-polk-sipping-location-requirements
> -01.txt
>=20
>=20
> And NENA is working on such requirements, and is starting to engage =
other=20
> organizations in other parts of the world.  It has not been decided
whether=20
> there will be multiple, possibly conflicting requirements sent in =
from=20
> different organizations, or whether an effort will be mounted to =
negotiate

> a single set of requirements.  I favor the latter, because we don't =
have=20
> the expertise in the IETF to deal with conflicts if they were to =
arise. =20
>=20
> I'd ask that anyone who knows people who should be involved (NENA=20
> equivalents in other parts of the world), please contact me.=20
>=20
> Brian
>=20
>=20
> -----Original Message-----
> From: Mpierce1@aol.com [mailto:Mpierce1@aol.com]
> Sent: Thursday, December 18, 2003 3:47 PM
> To: mhammer@cisco.com
> Cc: sipping@ietf.org
> Subject: Re: [sipping] comment on =
draft-polk-sipping-location-requirements
> -01.txt
>=20
>=20
> In a message dated 12/18/2003 3:05:36 PM Eastern Standard Time,
> mhammer@cisco.com writes:=20
>=20
>=20
>=20
> It doesn't say you can't provide more than one type of measurement, =
does
it?
>=20
>=20
> What liability would a carrier assume if the handset using GPS =
provided a=20
> location to 10 meters, and that got over-ridden by a carrier network =
using

> TOA providing an accuracy of 100 meters, and the ambulance arrives =
too
late?
>=20
>=20
>=20
>=20
>=20
> More than one type of location is not the problem. I believe all the =
past
> discussion was that the "handset" and the "carrier" came up with
conflicting
> information. If they were not conflicting, then why have two. If they =
are
> conflicting, that is a problem. If the handset gives a physical =
location
to
> 10 meters, why would the carrier network bother to include a value of =
100
> meters accuracy, if the value from the end user were within that 100
meters?
> If it isn't, what should the PSAP do, send an ambulance to both?=20
>=20
> If the handset gave a value within 10 meters and the carrier =
overwrote it
> with a value accurate to only 100 meters, there would be serious =
liability
> issues, especially if the requirement were for an accuracy of 50 =
feet.=20
>=20
> Like I said, NENA (or some such organization) needs to say what the
> requirements are (in the US). It is silly and hopeless for the IETF =
to try
> to agree on "requirements".=20
>=20
> Mike=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip Use
> sip@ietf.org for new developments of core SIP
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP


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



From exim@www1.ietf.org  Fri Dec 19 11:04:38 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14195
	for <sipping-archive@odin.ietf.org>; Fri, 19 Dec 2003 11:04:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXN6p-0006RY-9q
	for sipping-archive@odin.ietf.org; Fri, 19 Dec 2003 11:04:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBJG4BWW024762
	for sipping-archive@odin.ietf.org; Fri, 19 Dec 2003 11:04:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXN6p-0006RJ-5z
	for sipping-web-archive@optimus.ietf.org; Fri, 19 Dec 2003 11:04:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14177
	for <sipping-web-archive@ietf.org>; Fri, 19 Dec 2003 11:04:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXN6m-0007NS-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 11:04:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXN6k-0007NL-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 11:04:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXN6k-0007NI-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 11:04:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXN6f-0006Pe-Av; Fri, 19 Dec 2003 11:04:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXN5k-0006Op-R3
	for sipping@optimus.ietf.org; Fri, 19 Dec 2003 11:03:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14144
	for <sipping@ietf.org>; Fri, 19 Dec 2003 11:02:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXN5f-0007Lx-00
	for sipping@ietf.org; Fri, 19 Dec 2003 11:02:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXN5d-0007Li-00
	for sipping@ietf.org; Fri, 19 Dec 2003 11:02:59 -0500
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXN5d-0007Lb-00
	for sipping@ietf.org; Fri, 19 Dec 2003 11:02:57 -0500
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA03636;
	Fri, 19 Dec 2003 11:00:28 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA19667;
	Fri, 19 Dec 2003 11:00:17 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <W9W8JPNS>; Fri, 19 Dec 2003 11:00:16 -0500
Message-ID: <313680C9A886D511A06000204840E1CF070B6226@whq-msgusr-02.pit.comms.marconi.com>
From: "Rosen, Brian" <Brian.Rosen@marconi.com>
To: "'Stastny Richard'" <Richard.Stastny@oefeg.at>, Tyler_Johnson@unc.edu
Cc: =?iso-8859-1?Q?PROUVOST_S=E9bastien_FTRD/DAC/ISS?=
	 <sebastien.prouvost@francetelecom.com>,
        Mpierce1@aol.com, mhammer@cisco.com, sipping@ietf.org,
        Henning Schulzrinne
	 <hgs@cs.columbia.edu>,
        Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Subject: RE: RE : [sipping] comment on draft-polk-sipping-location-require
	 ments -01.txt
Date: Fri, 19 Dec 2003 11:00:06 -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: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Richard

I believe you are confusing the issue of how you determine location =
from the
issue
of how you connect to an emergency center.  I think Tyler was =
addressing the
latter,
while your comments appear to deal with the former.

Actually, I think we see the way forward with location determination.
There will be devices that know where they are via GPS or other =
mechanisms
There will be devices that learn their location from mechanisms that =
are
	either proprietary or out of scope for any IETF working group
For devices that need standardized ways of being told where they are,
  there are two cases:
	The device is fixed (doesn't move from boot to call for help)
		This is addressed with DHCP, and works regardless of VPNs. =20
		The original DHCP probe (hotspot for example) will supply=20
		location, not the interior DHCP (within the VPN).
	The device moves
		This is the subject of the present thread. =20

I sent a message on the subject of separating signalling from sip.

I believe that there is nothing simple about emergency calling, and you
require the kinds of things that SIP provides.  Inventing a new session
initiation protocol for emergency sessions is not reasonable, I think.
You have a session with the psap, you pass media, bidirectionaly. =20
SIP is very appropriate.

Also, please note that considered opinion is that buttons labled=20
"emergency" generally are a bad idea; they get pushed inappropriately=20
much too often.  Most experts prefer a multibutton sequence. =20
There are some amusing stories (right Dick?) about how often various=20
3 digit combinations are accidentally "pressed" on mobiles. =20
Your intuition might very well be wrong here.

Brian

-----Original Message-----
From: Stastny Richard [mailto:Richard.Stastny@oefeg.at]
Sent: Friday, December 19, 2003 10:36 AM
To: Tyler_Johnson@unc.edu; Rosen, Brian
Cc: PROUVOST S=E9bastien FTRD/DAC/ISS; Mpierce1@aol.com;
mhammer@cisco.com; sipping@ietf.org; Henning Schulzrinne; Jonathan
Rosenberg
Subject: RE: RE : [sipping] comment on
draft-polk-sipping-location-require ments -01.txt


I fully agree.

I also was following this and previous discussions with interest, =
because
this issue
pops up periodicly over and over again and always dies away because no
solution
on the application layer is possible in mobile environments (at least =
non
has been found yet).
GPS does not work, user entry does not work, DHCP does not work because =
of
VPNs,=20
User profile does not work, etc.

So the only possiblity is a very simple basic protocol on layer 2, lets
call it SEP (Simple Emergency Protocol).

If this protocol is simple enough, it may be mandated by regulators to =
be
implemented
in every IP access environment and also in any IP access device and it
should also
work like 112 in mobiles without login to the environment.

The required SW could be made mandatory and part of all IP-enabled =
operating
systems.
In its simplest varity it could work with a simple click on a =
(soft)button,
it could also use
existing applications (e-mail, chat, SIP, etc.) if available, but this =
is
out of scope.

To put the necessary parameters in the access device and get access =
from any
device cannot be too complicated.

I propose to set up an own WG to deal with this asap.

best regards
Richard

> -----Original Message-----
> From: Tyler Johnson [mailto:trjohns1@email.unc.edu]=20
> Sent: Friday, December 19, 2003 3:38 PM
> To: Rosen, Brian
> Cc: 'PROUVOST S=E9bastien FTRD/DAC/ISS'; Mpierce1@aol.com;=20
> mhammer@cisco.com; sipping@ietf.org; Henning Schulzrinne;=20
> Jonathan Rosenberg
> Subject: Re: RE : [sipping] comment on=20
> draft-polk-sipping-location-require ments -01.txt
>=20
>=20
> All,
>=20
> I have been following this discussion with some interest. It=20
> seems to me=20
> that in trying to create a 911 service for VoIP, we are=20
> applying an old=20
> paradigm to a new technology.
>=20
> I think that emergency services are important for many=20
> applications, and=20
> VoIP is just one. For example, I should be able to summon=20
> help from my=20
> email, IM device, Blackberry, etc. Further, I can see a 'Help I've=20
> fallen and I can't get up' 802.11b panic pendant for=20
> grandmothers. As IP=20
> is deployed, it will become increasingly important to provide these=20
> services, and municipalities will mandate it.
>=20
> Because of this, I very much agree with Brian's notion that=20
> the physical=20
> (or layer 2) network should provide the emergency service signalling. =

> However, it strikes me that it is not appropriate to build this=20
> functionality into SIP or the VoIP application. Rather, it should be=20
> developed as a standalone generic service (outside of=20
> SIPPING) that can=20
> be accessed by any application. Then, SIPPING could point to=20
> it as the=20
> emergency services method of choice.
>=20
> I am concerned that if we build emergency services into VoIP,=20
> then VoIP=20
> emergency services will quickly become obsolete as the pace=20
> of other IP=20
> applications requiring emergency services quickens.
>=20
> Rosen, Brian wrote:
> > S=E9bastien
> >=20
> > There will HAVE to be a single worldwide set of requirements for=20
> > emergency services, because the Internet does not respect national=20
> > boundaries, and we ALREADY see the effect of this on calls to=20
> > emergency services.
> >=20
> > My usual example would be a patron of a Paris cafe using a WiFi
> > hotspot with a VPN tunnel open to her employers network, in which=20
> > she is running a sip softclient.  If an accident occurs outside=20
> > the cafe, and she uses her softclient to call for help, how does=20
> > the employer, which could be located in another continent,=20
> > and using its local VoIP carrier, be subject to any=20
> > laws/specifications of France?  It cannot.  And the hotspot=20
> > operator, which might be subject to some regulation, is unaware=20
> > that there is a VoIP call, let alone a call to the emergency =
system,
> > and in fact there is likely encryption on the tunnel making it
> > impossible for it to figure it out.
> >=20
> > However, if there is an international standard, such as we produce
> > here in the IETF, then it is VERY likely that the softclient,=20
> > the employer's PBX, and the VoIP carrier are able to correctly=20
> > handle the call, routing it to the correct emergency=20
> answering point,=20
> > and including call-back information as well as location=20
> information. =20
> > It is only an international standard that will work as the Internet =

> > joins fixed, mobile and roaming users with a variety of devices,=20
> > proxies and carriers operating over multiple continents.
> >=20
> > The IETF has a history of not sanctioning regional=20
> variations in its=20
> > specifications, and, as the above example illustrates, it is not=20
> > feasible to implement regional or national variations.  The=20
> reality of=20
> > the situation is that regulating emergency calls is not=20
> possible with=20
> > VoIP (unless there was an international treaty that had universal=20
> > applicability), but a single, effective international=20
> standard is very=20
> > possible.
> >=20
> > Such a standard needs an agreed set of requirements, of course.
> >=20
> > I've stated my views on the proxy insertion of location.
> >=20
> > Brian
> >=20
> >=20
> > -----Original Message-----
> > From: PROUVOST S=E9bastien FTRD/DAC/ISS=20
> > [mailto:sebastien.prouvost@francetelecom.com]
> > Sent: Friday, December 19, 2003 6:32 AM
> > To: Rosen, Brian; Mpierce1@aol.com; mhammer@cisco.com
> > Cc: sipping@ietf.org; Henning Schulzrinne; Jonathan Rosenberg
> > Subject: RE : [sipping] comment on=20
> > draft-polk-sipping-location-requirements -01.txt
> >=20
> >=20
> > Two points here :
> > =20
> > First I doubt that there will be a single world wide set of=20
> > requirements for emergency calls.
> >=20
> > Second, a requirement listed in the original draft was for=20
> a proxy to=20
> > be able to give its idea of the terminal location (originally by=20
> > asserting the location given by the terminal). However, it may be=20
> > easier for a proxy to insert its own info about the location of the =

> > terminal rather than to assert the info given by the=20
> terminal. It also=20
> > let the possibility to the called party to get both pieces of=20
> > information which is useful information as pointed out by Jonathan. =

> > Both pieces of information shall be passed on.
> >=20
> >=20
> > S=E9bastien Prouvost
> > France T=E9l=E9com R&D/DAC/CAR
> >=20
> >=20
> > -----Message d'origine-----
> > De : Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> > Envoy=E9 : jeudi 18 d=E9cembre 2003 22:48
> > =C0 : 'Mpierce1@aol.com'; mhammer@cisco.com
> > Cc : sipping@ietf.org
> > Objet : RE: [sipping] comment on=20
> draft-polk-sipping-location-requirements
> > -01.txt
> >=20
> >=20
> > And NENA is working on such requirements, and is starting to engage =

> > other
> > organizations in other parts of the world.  It has not been=20
> decided whether=20
> > there will be multiple, possibly conflicting requirements=20
> sent in from=20
> > different organizations, or whether an effort will be=20
> mounted to negotiate=20
> > a single set of requirements.  I favor the latter, because=20
> we don't have=20
> > the expertise in the IETF to deal with conflicts if they=20
> were to arise. =20
> >=20
> > I'd ask that anyone who knows people who should be involved (NENA
> > equivalents in other parts of the world), please contact me.=20
> >=20
> > Brian
> >=20
> >=20
> > -----Original Message-----
> > From: Mpierce1@aol.com [mailto:Mpierce1@aol.com]
> > Sent: Thursday, December 18, 2003 3:47 PM
> > To: mhammer@cisco.com
> > Cc: sipping@ietf.org
> > Subject: Re: [sipping] comment on=20
> > draft-polk-sipping-location-requirements
> > -01.txt
> >=20
> >=20
> > In a message dated 12/18/2003 3:05:36 PM Eastern Standard Time,=20
> > mhammer@cisco.com writes:
> >=20
> >=20
> >=20
> > It doesn't say you can't provide more than one type of measurement, =

> > does it?
> >=20
> >=20
> > What liability would a carrier assume if the handset using GPS=20
> > provided a
> > location to 10 meters, and that got over-ridden by a=20
> carrier network using=20
> > TOA providing an accuracy of 100 meters, and the ambulance=20
> arrives too late?
> >=20
> >=20
> >=20
> >=20
> >=20
> > More than one type of location is not the problem. I=20
> believe all the=20
> > past discussion was that the "handset" and the "carrier"=20
> came up with=20
> > conflicting information. If they were not conflicting, then=20
> why have=20
> > two. If they are conflicting, that is a problem. If the=20
> handset gives=20
> > a physical location to 10 meters, why would the carrier=20
> network bother=20
> > to include a value of 100 meters accuracy, if the value=20
> from the end=20
> > user were within that 100 meters? If it isn't, what should the PSAP =

> > do, send an ambulance to both?
> >=20
> > If the handset gave a value within 10 meters and the=20
> carrier overwrote=20
> > it with a value accurate to only 100 meters, there would be serious =

> > liability issues, especially if the requirement were for an=20
> accuracy=20
> > of 50 feet.
> >=20
> > Like I said, NENA (or some such organization) needs to say what the =

> > requirements are (in the US). It is silly and hopeless for=20
> the IETF to=20
> > try to agree on "requirements".
> >=20
> > Mike
> >=20
> > _______________________________________________
> > Sipping mailing list  =
https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP Use=20
> > sip-implementors@cs.columbia.edu for questions on current sip Use=20
> > sip@ietf.org for new developments of core SIP
> >=20
> > _______________________________________________
> > Sipping mailing list  =
https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP Use=20
> > sip-implementors@cs.columbia.edu for questions on current sip Use=20
> > sip@ietf.org for new developments of core SIP
>=20
>=20
>=20
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current=20
> sip Use sip@ietf.org for new developments of core SIP
>=20

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



From exim@www1.ietf.org  Fri Dec 19 12:03:34 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15939
	for <sipping-archive@odin.ietf.org>; Fri, 19 Dec 2003 12:03:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXO1o-0001Vw-Sc
	for sipping-archive@odin.ietf.org; Fri, 19 Dec 2003 12:03:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBJH34cL005815
	for sipping-archive@odin.ietf.org; Fri, 19 Dec 2003 12:03:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXO1k-0001Vd-3E
	for sipping-web-archive@optimus.ietf.org; Fri, 19 Dec 2003 12:03:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15920
	for <sipping-web-archive@ietf.org>; Fri, 19 Dec 2003 12:02:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXO1h-00010c-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 12:02:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXO1g-00010V-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 12:02:56 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXO1g-00010S-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 12:02:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXO0p-0001Pb-EE; Fri, 19 Dec 2003 12:02:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXO0f-0001OE-QW
	for sipping@optimus.ietf.org; Fri, 19 Dec 2003 12:01:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15908
	for <sipping@ietf.org>; Fri, 19 Dec 2003 12:01:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXO0e-0000zL-00
	for sipping@ietf.org; Fri, 19 Dec 2003 12:01:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXO0d-0000zE-00
	for sipping@ietf.org; Fri, 19 Dec 2003 12:01:52 -0500
Received: from auemail2.lucent.com ([192.11.223.163] helo=auemail2.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXO0a-0000yk-00
	for sipping@ietf.org; Fri, 19 Dec 2003 12:01:49 -0500
Received: from uk0006exch001h.wins.lucent.com (h135-86-145-57.lucent.com [135.86.145.57])
	by auemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id hBJH1KZ20484
	for <sipping@ietf.org>; Fri, 19 Dec 2003 11:01:42 -0600 (CST)
Received: by uk0006exch001h.uk.lucent.com with Internet Mail Service (5.5.2657.72)
	id <Y9ZVKJT3>; Fri, 19 Dec 2003 16:59:57 -0000
Message-ID: <475FF955A05DD411980D00508B6D5FB00439EF7C@en0033exch001u.uk.lucent.com>
From: "Drage, Keith (Keith)" <drage@lucent.com>
To: "'Mpierce1@aol.com'" <Mpierce1@aol.com>, mhammer@cisco.com
Cc: sipping@ietf.org
Subject: RE: [sipping] comment on draft-polk-sipping-location-requirements
	 -01.txt
Date: Fri, 19 Dec 2003 16:59:55 -0000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

At least as far as 3GPP is concerned, the proposal is more likely to work the other way round.

For SIP calls, the phone will be able to provide an indication of which cell location the phone is currently in.

The network will have access to the GMLC which will be able to provide a more accurate location. 

In some locations the cell location may be sufficient to determine which emergency centre to route to. If this is insufficient some intermediate entity will have the capability of contacting the GMLC for a more accurate set of location information, on which it can base the routeing decision to find the emergency centre. As the cell location is sent entirely independently from the GMLC provided information, then I assume the emergency centre would have access to both sets of information - programmes already exist for converting cell location into geographic information.

I believe the emergency centre also has the option of either believing the information sent with the call, or it can also contact the GMLC for the current location information.

Of course there is always the possibility that someone has built GPS into the phone and that it is able to insert something more accurate than the GMLC can provide into the SIP message. I believe that for 3GPP environments, it is understood that the GMLC will provide sufficiently accurate information to route to the emergency centre. Therefore any decisions on comparative accuracy and authenticity of information will be an issue for the emergency centre alone, assuming we send all aavailable information to the emergency centre.

I also gather that different methods of location determination have different accuracies depending on the quality of the implementation, and on the environment where the user currently is, so this may not be a simple excercise.

This does of course mean that we need to provide the option of carrying multiple sets of information, and also providing some indication of where the information came from.

regards

Keith

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



-----Original Message-----
From: Mpierce1@aol.com [mailto:Mpierce1@aol.com]
Sent: 18 December 2003 20:47
To: mhammer@cisco.com
Cc: sipping@ietf.org
Subject: Re: [sipping] comment on draft-polk-sipping-location-requirements -01.txt


In a message dated 12/18/2003 3:05:36 PM Eastern Standard Time, mhammer@cisco.com writes: 



It doesn't say you can't provide more than one type of measurement, does it? 

What liability would a carrier assume if the handset using GPS provided a 
location to 10 meters, and that got over-ridden by a carrier network using 
TOA providing an accuracy of 100 meters, and the ambulance arrives too late? 




More than one type of location is not the problem. I believe all the past discussion was that the "handset" and the "carrier" came up with conflicting information. If they were not conflicting, then why have two. If they are conflicting, that is a problem. If the handset gives a physical location to 10 meters, why would the carrier network bother to include a value of 100 meters accuracy, if the value from the end user were within that 100 meters? If it isn't, what should the PSAP do, send an ambulance to both? 

If the handset gave a value within 10 meters and the carrier overwrote it with a value accurate to only 100 meters, there would be serious liability issues, especially if the requirement were for an accuracy of 50 feet. 

Like I said, NENA (or some such organization) needs to say what the requirements are (in the US). It is silly and hopeless for the IETF to try to agree on "requirements". 

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 exim@www1.ietf.org  Fri Dec 19 13:42:46 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19396
	for <sipping-archive@odin.ietf.org>; Fri, 19 Dec 2003 13:42:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXPZk-0005zB-P3
	for sipping-archive@odin.ietf.org; Fri, 19 Dec 2003 13:42:17 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBJIgCvK023003
	for sipping-archive@odin.ietf.org; Fri, 19 Dec 2003 13:42:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXPZk-0005yw-Kn
	for sipping-web-archive@optimus.ietf.org; Fri, 19 Dec 2003 13:42:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19385
	for <sipping-web-archive@ietf.org>; Fri, 19 Dec 2003 13:42:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXPZi-0003w5-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 13:42:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXPZe-0003vc-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 13:42:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXPZe-0003vZ-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 13:42:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXPZZ-0005xm-5c; Fri, 19 Dec 2003 13:42:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXPZB-0005xO-GR
	for sipping@optimus.ietf.org; Fri, 19 Dec 2003 13:41:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19356
	for <sipping@ietf.org>; Fri, 19 Dec 2003 13:41:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXPZ9-0003ti-00
	for sipping@ietf.org; Fri, 19 Dec 2003 13:41:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXPZ7-0003tb-00
	for sipping@ietf.org; Fri, 19 Dec 2003 13:41:34 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXPZ7-0003t2-00
	for sipping@ietf.org; Fri, 19 Dec 2003 13:41:33 -0500
Received: from rtp-core-2.cisco.com (64.102.124.13)
  by sj-iport-5.cisco.com with ESMTP; 19 Dec 2003 18:41:43 +0000
Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com [64.102.16.27])
	by rtp-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id hBJIexK6009795;
	Fri, 19 Dec 2003 13:40:59 -0500 (EST)
Received: from mhammer-w2k03.cisco.com (dhcp-64-100-224-121.cisco.com [64.100.224.121])
	by fruitpie.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AVT96799;
	Fri, 19 Dec 2003 10:40:54 -0800 (PST)
Message-Id: <4.3.2.7.2.20031219133338.00bae720@cia.cisco.com>
X-Sender: mhammer@cia.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 19 Dec 2003 13:40:53 -0500
To: "Stastny Richard" <Richard.Stastny@oefeg.at>
From: Michael Hammer <mhammer@cisco.com>
Subject: RE: RE : [sipping] comment on
  draft-polk-sipping-location-require ments -01.txt
Cc: <Tyler_Johnson@unc.edu>, "Rosen, Brian" <Brian.Rosen@marconi.com>,
        PROUVOST =?iso-8859-1?Q?S=E9bastien?= 
 FTRD/DAC/ISS <sebastien.prouvost@francetelecom.com>,
        <Mpierce1@aol.com>, <sipping@ietf.org>,
        "Henning Schulzrinne" <hgs@cs.columbia.edu>,
        "Jonathan Rosenberg" <jdrosen@dynamicsoft.com>
In-Reply-To: <06CF906FE3998C4E944213062009F162233A5B@oefeg-s02.oefeg.loc
 >
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Would such an application-independent solution require a mapping from host=
=20
network IP pre-fix to an associated Public Service Access Point (PSAP) or=20
911, 112, or whatever center?

I am imagining that a DNS record would have a selection of application=
 types:
sip, im, or whatever to enable all covered modes of communication to be=20
redirected to that PSAP.  For example, VPN tunneled call to PBX in=20
Washington from Paris causes the PBX to do a look-up and redirect a sip=20
call to the local Paris emergency center closest to that Internet cafe.  If=
=20
it is a two-way pager using IM, then the IM is looked up and forwarded, etc.

Mike

At 04:36 PM 12/19/2003 +0100, Stastny Richard wrote:
>I fully agree.
>
>I also was following this and previous discussions with interest, because=
=20
>this issue
>pops up periodicly over and over again and always dies away because no=20
>solution
>on the application layer is possible in mobile environments (at least non=
=20
>has been found yet).
>GPS does not work, user entry does not work, DHCP does not work because of=
=20
>VPNs,
>User profile does not work, etc.
>
>So the only possiblity is a very simple basic protocol on layer 2, lets
>call it SEP (Simple Emergency Protocol).
>
>If this protocol is simple enough, it may be mandated by regulators to be=
=20
>implemented
>in every IP access environment and also in any IP access device and it=20
>should also
>work like 112 in mobiles without login to the environment.
>
>The required SW could be made mandatory and part of all IP-enabled=20
>operating systems.
>In its simplest varity it could work with a simple click on a=20
>(soft)button, it could also use
>existing applications (e-mail, chat, SIP, etc.) if available, but this is=
=20
>out of scope.
>
>To put the necessary parameters in the access device and get access from=20
>any device cannot be too complicated.
>
>I propose to set up an own WG to deal with this asap.
>
>best regards
>Richard
>
> > -----Original Message-----
> > From: Tyler Johnson [mailto:trjohns1@email.unc.edu]
> > Sent: Friday, December 19, 2003 3:38 PM
> > To: Rosen, Brian
> > Cc: 'PROUVOST S=E9bastien FTRD/DAC/ISS'; Mpierce1@aol.com;
> > mhammer@cisco.com; sipping@ietf.org; Henning Schulzrinne;
> > Jonathan Rosenberg
> > Subject: Re: RE : [sipping] comment on
> > draft-polk-sipping-location-require ments -01.txt
> >
> >
> > All,
> >
> > I have been following this discussion with some interest. It
> > seems to me
> > that in trying to create a 911 service for VoIP, we are
> > applying an old
> > paradigm to a new technology.
> >
> > I think that emergency services are important for many
> > applications, and
> > VoIP is just one. For example, I should be able to summon
> > help from my
> > email, IM device, Blackberry, etc. Further, I can see a 'Help I've
> > fallen and I can't get up' 802.11b panic pendant for
> > grandmothers. As IP
> > is deployed, it will become increasingly important to provide these
> > services, and municipalities will mandate it.
> >
> > Because of this, I very much agree with Brian's notion that
> > the physical
> > (or layer 2) network should provide the emergency service signalling.
> > However, it strikes me that it is not appropriate to build this
> > functionality into SIP or the VoIP application. Rather, it should be
> > developed as a standalone generic service (outside of
> > SIPPING) that can
> > be accessed by any application. Then, SIPPING could point to
> > it as the
> > emergency services method of choice.
> >
> > I am concerned that if we build emergency services into VoIP,
> > then VoIP
> > emergency services will quickly become obsolete as the pace
> > of other IP
> > applications requiring emergency services quickens.
> >
> > Rosen, Brian wrote:
> > > S=E9bastien
> > >
> > > There will HAVE to be a single worldwide set of requirements for
> > > emergency services, because the Internet does not respect national
> > > boundaries, and we ALREADY see the effect of this on calls to
> > > emergency services.
> > >
> > > My usual example would be a patron of a Paris cafe using a WiFi
> > > hotspot with a VPN tunnel open to her employers network, in which
> > > she is running a sip softclient.  If an accident occurs outside
> > > the cafe, and she uses her softclient to call for help, how does
> > > the employer, which could be located in another continent,
> > > and using its local VoIP carrier, be subject to any
> > > laws/specifications of France?  It cannot.  And the hotspot
> > > operator, which might be subject to some regulation, is unaware
> > > that there is a VoIP call, let alone a call to the emergency system,
> > > and in fact there is likely encryption on the tunnel making it
> > > impossible for it to figure it out.
> > >
> > > However, if there is an international standard, such as we produce
> > > here in the IETF, then it is VERY likely that the softclient,
> > > the employer's PBX, and the VoIP carrier are able to correctly
> > > handle the call, routing it to the correct emergency
> > answering point,
> > > and including call-back information as well as location
> > information.
> > > It is only an international standard that will work as the Internet
> > > joins fixed, mobile and roaming users with a variety of devices,
> > > proxies and carriers operating over multiple continents.
> > >
> > > The IETF has a history of not sanctioning regional
> > variations in its
> > > specifications, and, as the above example illustrates, it is not
> > > feasible to implement regional or national variations.  The
> > reality of
> > > the situation is that regulating emergency calls is not
> > possible with
> > > VoIP (unless there was an international treaty that had universal
> > > applicability), but a single, effective international
> > standard is very
> > > possible.
> > >
> > > Such a standard needs an agreed set of requirements, of course.
> > >
> > > I've stated my views on the proxy insertion of location.
> > >
> > > Brian
> > >
> > >
> > > -----Original Message-----
> > > From: PROUVOST S=E9bastien FTRD/DAC/ISS
> > > [mailto:sebastien.prouvost@francetelecom.com]
> > > Sent: Friday, December 19, 2003 6:32 AM
> > > To: Rosen, Brian; Mpierce1@aol.com; mhammer@cisco.com
> > > Cc: sipping@ietf.org; Henning Schulzrinne; Jonathan Rosenberg
> > > Subject: RE : [sipping] comment on
> > > draft-polk-sipping-location-requirements -01.txt
> > >
> > >
> > > Two points here :
> > >
> > > First I doubt that there will be a single world wide set of
> > > requirements for emergency calls.
> > >
> > > Second, a requirement listed in the original draft was for
> > a proxy to
> > > be able to give its idea of the terminal location (originally by
> > > asserting the location given by the terminal). However, it may be
> > > easier for a proxy to insert its own info about the location of the
> > > terminal rather than to assert the info given by the
> > terminal. It also
> > > let the possibility to the called party to get both pieces of
> > > information which is useful information as pointed out by Jonathan.
> > > Both pieces of information shall be passed on.
> > >
> > >
> > > S=E9bastien Prouvost
> > > France T=E9l=E9com R&D/DAC/CAR
> > >
> > >
> > > -----Message d'origine-----
> > > De : Rosen, Brian [mailto:Brian.Rosen@marconi.com]
> > > Envoy=E9 : jeudi 18 d=E9cembre 2003 22:48
> > > =C0 : 'Mpierce1@aol.com'; mhammer@cisco.com
> > > Cc : sipping@ietf.org
> > > Objet : RE: [sipping] comment on
> > draft-polk-sipping-location-requirements
> > > -01.txt
> > >
> > >
> > > And NENA is working on such requirements, and is starting to engage
> > > other
> > > organizations in other parts of the world.  It has not been
> > decided whether
> > > there will be multiple, possibly conflicting requirements
> > sent in from
> > > different organizations, or whether an effort will be
> > mounted to negotiate
> > > a single set of requirements.  I favor the latter, because
> > we don't have
> > > the expertise in the IETF to deal with conflicts if they
> > were to arise.
> > >
> > > I'd ask that anyone who knows people who should be involved (NENA
> > > equivalents in other parts of the world), please contact me.
> > >
> > > Brian
> > >
> > >
> > > -----Original Message-----
> > > From: Mpierce1@aol.com [mailto:Mpierce1@aol.com]
> > > Sent: Thursday, December 18, 2003 3:47 PM
> > > To: mhammer@cisco.com
> > > Cc: sipping@ietf.org
> > > Subject: Re: [sipping] comment on
> > > draft-polk-sipping-location-requirements
> > > -01.txt
> > >
> > >
> > > In a message dated 12/18/2003 3:05:36 PM Eastern Standard Time,
> > > mhammer@cisco.com writes:
> > >
> > >
> > >
> > > It doesn't say you can't provide more than one type of measurement,
> > > does it?
> > >
> > >
> > > What liability would a carrier assume if the handset using GPS
> > > provided a
> > > location to 10 meters, and that got over-ridden by a
> > carrier network using
> > > TOA providing an accuracy of 100 meters, and the ambulance
> > arrives too late?
> > >
> > >
> > >
> > >
> > >
> > > More than one type of location is not the problem. I
> > believe all the
> > > past discussion was that the "handset" and the "carrier"
> > came up with
> > > conflicting information. If they were not conflicting, then
> > why have
> > > two. If they are conflicting, that is a problem. If the
> > handset gives
> > > a physical location to 10 meters, why would the carrier
> > network bother
> > > to include a value of 100 meters accuracy, if the value
> > from the end
> > > user were within that 100 meters? If it isn't, what should the PSAP
> > > do, send an ambulance to both?
> > >
> > > If the handset gave a value within 10 meters and the
> > carrier overwrote
> > > it with a value accurate to only 100 meters, there would be serious
> > > liability issues, especially if the requirement were for an
> > accuracy
> > > of 50 feet.
> > >
> > > Like I said, NENA (or some such organization) needs to say what the
> > > requirements are (in the US). It is silly and hopeless for
> > the IETF to
> > > try to agree on "requirements".
> > >
> > > 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
> > >
> > > _______________________________________________
> > > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > > This list is for NEW development of the application of SIP Use
> > > sip-implementors@cs.columbia.edu for questions on current sip Use
> > > sip@ietf.org for new developments of core SIP
> >
> >
> >
> > _______________________________________________
> > Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> > This list is for NEW development of the application of SIP
> > Use sip-implementors@cs.columbia.edu for questions on current
> > sip Use sip@ietf.org for new developments of core SIP
> >


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



From exim@www1.ietf.org  Fri Dec 19 18:29:41 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03680
	for <sipping-archive@odin.ietf.org>; Fri, 19 Dec 2003 18:29:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXU3U-0000jl-69
	for sipping-archive@odin.ietf.org; Fri, 19 Dec 2003 18:29:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBJNTCdk002829
	for sipping-archive@odin.ietf.org; Fri, 19 Dec 2003 18:29:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXU3U-0000jX-2X
	for sipping-web-archive@optimus.ietf.org; Fri, 19 Dec 2003 18:29:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03649
	for <sipping-web-archive@ietf.org>; Fri, 19 Dec 2003 18:29:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXU3Q-00007b-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 18:29:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXU3O-00007P-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 18:29:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXU3O-00007M-00
	for sipping-web-archive@ietf.org; Fri, 19 Dec 2003 18:29:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXU3J-0000ge-Kf; Fri, 19 Dec 2003 18:29:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXU2b-0000fi-Ng
	for sipping@optimus.ietf.org; Fri, 19 Dec 2003 18:28:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03567
	for <sipping@ietf.org>; Fri, 19 Dec 2003 18:28:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXU2Y-00002F-00
	for sipping@ietf.org; Fri, 19 Dec 2003 18:28:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXU2T-00001L-00
	for sipping@ietf.org; Fri, 19 Dec 2003 18:28:14 -0500
Received: from opus.cs.columbia.edu ([128.59.20.100])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXU2T-000019-00
	for sipping@ietf.org; Fri, 19 Dec 2003 18:28:09 -0500
Received: from cs.columbia.edu (path.cs.columbia.edu [128.59.19.143])
	(authenticated bits=0)
	by opus.cs.columbia.edu (8.12.10/8.12.10) with ESMTP id hBJNRoKO010462
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Fri, 19 Dec 2003 18:27:56 -0500 (EST)
Message-ID: <3FE38976.2060508@cs.columbia.edu>
Date: Fri, 19 Dec 2003 18:27:50 -0500
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031130
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Stastny Richard <Richard.Stastny@oefeg.at>
CC: Tyler_Johnson@unc.edu, "Rosen, Brian" <Brian.Rosen@marconi.com>,
        =?ISO-8859-1?Q?PROUVOST_S=E9bastien_FTRD/DAC/ISS?=
 <sebastien.prouvost@francetelecom.com>,
        Mpierce1@aol.com, mhammer@cisco.com, sipping@ietf.org,
        Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Subject: Re: RE : [sipping] comment on draft-polk-sipping-location-require
 ments -01.txt
References: <06CF906FE3998C4E944213062009F162233A5B@oefeg-s02.oefeg.loc>
In-Reply-To: <06CF906FE3998C4E944213062009F162233A5B@oefeg-s02.oefeg.loc>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by opus.cs.columbia.edu id hBJNRoKO010462
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

We have been building and advocating location beacons, for example using=20
BlueTooth or the wireless AP. Low cost and not subject to VPN issues.=20
This is very similar to the Cisco Discovery Protocol (CDP), which could=20
be readily extended to handle this functionality. Unfortunately, that=20
protocol is proprietary.

However, this has very little to do with the signaling and session=20
setup. After all, we don't care about getting IP packets to a PSAP, but=20
rather applications, since the PSAP only cares about a finite set of=20
applications.

Clearly, there are components (such as location objects and DNS or other=20
directory lookups) that are useful across application protocols. Brian=20
and I (and I'm sure, others) have been thinking of various approaches=20
along these lines.

Stastny Richard wrote:

> I fully agree.
>=20
> I also was following this and previous discussions with interest, becau=
se this issue
> pops up periodicly over and over again and always dies away because no =
solution
> on the application layer is possible in mobile environments (at least n=
on has been found yet).
> GPS does not work, user entry does not work, DHCP does not work because=
 of VPNs,=20
> User profile does not work, etc.
>=20
> So the only possiblity is a very simple basic protocol on layer 2, lets
> call it SEP (Simple Emergency Protocol).
>=20
> If this protocol is simple enough, it may be mandated by regulators to =
be implemented
> in every IP access environment and also in any IP access device and it =
should also
> work like 112 in mobiles without login to the environment.
>=20
> The required SW could be made mandatory and part of all IP-enabled oper=
ating systems.
> In its simplest varity it could work with a simple click on a (soft)but=
ton, it could also use
> existing applications (e-mail, chat, SIP, etc.) if available, but this =
is out of scope.
>=20
> To put the necessary parameters in the access device and get access fro=
m any device cannot be too complicated.
>=20
> I propose to set up an own WG to deal with this asap.
>=20
> best regards
> Richard
>=20
>=20
>>-----Original Message-----
>>From: Tyler Johnson [mailto:trjohns1@email.unc.edu]=20
>>Sent: Friday, December 19, 2003 3:38 PM
>>To: Rosen, Brian
>>Cc: 'PROUVOST S=E9bastien FTRD/DAC/ISS'; Mpierce1@aol.com;=20
>>mhammer@cisco.com; sipping@ietf.org; Henning Schulzrinne;=20
>>Jonathan Rosenberg
>>Subject: Re: RE : [sipping] comment on=20
>>draft-polk-sipping-location-require ments -01.txt
>>
>>
>>All,
>>
>>I have been following this discussion with some interest. It=20
>>seems to me=20
>>that in trying to create a 911 service for VoIP, we are=20
>>applying an old=20
>>paradigm to a new technology.
>>
>>I think that emergency services are important for many=20
>>applications, and=20
>>VoIP is just one. For example, I should be able to summon=20
>>help from my=20
>>email, IM device, Blackberry, etc. Further, I can see a 'Help I've=20
>>fallen and I can't get up' 802.11b panic pendant for=20
>>grandmothers. As IP=20
>>is deployed, it will become increasingly important to provide these=20
>>services, and municipalities will mandate it.
>>
>>Because of this, I very much agree with Brian's notion that=20
>>the physical=20
>>(or layer 2) network should provide the emergency service signalling.=20
>>However, it strikes me that it is not appropriate to build this=20
>>functionality into SIP or the VoIP application. Rather, it should be=20
>>developed as a standalone generic service (outside of=20
>>SIPPING) that can=20
>>be accessed by any application. Then, SIPPING could point to=20
>>it as the=20
>>emergency services method of choice.
>>
>>I am concerned that if we build emergency services into VoIP,=20
>>then VoIP=20
>>emergency services will quickly become obsolete as the pace=20
>>of other IP=20
>>applications requiring emergency services quickens.
>>
>>Rosen, Brian wrote:
>>
>>>S=E9bastien
>>>
>>>There will HAVE to be a single worldwide set of requirements for=20
>>>emergency services, because the Internet does not respect national=20
>>>boundaries, and we ALREADY see the effect of this on calls to=20
>>>emergency services.
>>>
>>>My usual example would be a patron of a Paris cafe using a WiFi
>>>hotspot with a VPN tunnel open to her employers network, in which=20
>>>she is running a sip softclient.  If an accident occurs outside=20
>>>the cafe, and she uses her softclient to call for help, how does=20
>>>the employer, which could be located in another continent,=20
>>>and using its local VoIP carrier, be subject to any=20
>>>laws/specifications of France?  It cannot.  And the hotspot=20
>>>operator, which might be subject to some regulation, is unaware=20
>>>that there is a VoIP call, let alone a call to the emergency system,
>>>and in fact there is likely encryption on the tunnel making it
>>>impossible for it to figure it out.
>>>
>>>However, if there is an international standard, such as we produce
>>>here in the IETF, then it is VERY likely that the softclient,=20
>>>the employer's PBX, and the VoIP carrier are able to correctly=20
>>>handle the call, routing it to the correct emergency=20
>>
>>answering point,=20
>>
>>>and including call-back information as well as location=20
>>
>>information. =20
>>
>>>It is only an international standard that will work as the Internet=20
>>>joins fixed, mobile and roaming users with a variety of devices,=20
>>>proxies and carriers operating over multiple continents.
>>>
>>>The IETF has a history of not sanctioning regional=20
>>
>>variations in its=20
>>
>>>specifications, and, as the above example illustrates, it is not=20
>>>feasible to implement regional or national variations.  The=20
>>
>>reality of=20
>>
>>>the situation is that regulating emergency calls is not=20
>>
>>possible with=20
>>
>>>VoIP (unless there was an international treaty that had universal=20
>>>applicability), but a single, effective international=20
>>
>>standard is very=20
>>
>>>possible.
>>>
>>>Such a standard needs an agreed set of requirements, of course.
>>>
>>>I've stated my views on the proxy insertion of location.
>>>
>>>Brian
>>>
>>>
>>>-----Original Message-----
>>>From: PROUVOST S=E9bastien FTRD/DAC/ISS=20
>>>[mailto:sebastien.prouvost@francetelecom.com]
>>>Sent: Friday, December 19, 2003 6:32 AM
>>>To: Rosen, Brian; Mpierce1@aol.com; mhammer@cisco.com
>>>Cc: sipping@ietf.org; Henning Schulzrinne; Jonathan Rosenberg
>>>Subject: RE : [sipping] comment on=20
>>>draft-polk-sipping-location-requirements -01.txt
>>>
>>>
>>>Two points here :
>>>=20
>>>First I doubt that there will be a single world wide set of=20
>>>requirements for emergency calls.
>>>
>>>Second, a requirement listed in the original draft was for=20
>>
>>a proxy to=20
>>
>>>be able to give its idea of the terminal location (originally by=20
>>>asserting the location given by the terminal). However, it may be=20
>>>easier for a proxy to insert its own info about the location of the=20
>>>terminal rather than to assert the info given by the=20
>>
>>terminal. It also=20
>>
>>>let the possibility to the called party to get both pieces of=20
>>>information which is useful information as pointed out by Jonathan.=20
>>>Both pieces of information shall be passed on.
>>>
>>>
>>>S=E9bastien Prouvost
>>>France T=E9l=E9com R&D/DAC/CAR
>>>
>>>
>>>-----Message d'origine-----
>>>De : Rosen, Brian [mailto:Brian.Rosen@marconi.com]
>>>Envoy=E9 : jeudi 18 d=E9cembre 2003 22:48
>>>=C0 : 'Mpierce1@aol.com'; mhammer@cisco.com
>>>Cc : sipping@ietf.org
>>>Objet : RE: [sipping] comment on=20
>>
>>draft-polk-sipping-location-requirements
>>
>>>-01.txt
>>>
>>>
>>>And NENA is working on such requirements, and is starting to engage=20
>>>other
>>>organizations in other parts of the world.  It has not been=20
>>
>>decided whether=20
>>
>>>there will be multiple, possibly conflicting requirements=20
>>
>>sent in from=20
>>
>>>different organizations, or whether an effort will be=20
>>
>>mounted to negotiate=20
>>
>>>a single set of requirements.  I favor the latter, because=20
>>
>>we don't have=20
>>
>>>the expertise in the IETF to deal with conflicts if they=20
>>
>>were to arise. =20
>>
>>>I'd ask that anyone who knows people who should be involved (NENA
>>>equivalents in other parts of the world), please contact me.=20
>>>
>>>Brian
>>>
>>>
>>>-----Original Message-----
>>>From: Mpierce1@aol.com [mailto:Mpierce1@aol.com]
>>>Sent: Thursday, December 18, 2003 3:47 PM
>>>To: mhammer@cisco.com
>>>Cc: sipping@ietf.org
>>>Subject: Re: [sipping] comment on=20
>>>draft-polk-sipping-location-requirements
>>>-01.txt
>>>
>>>
>>>In a message dated 12/18/2003 3:05:36 PM Eastern Standard Time,=20
>>>mhammer@cisco.com writes:
>>>
>>>
>>>
>>>It doesn't say you can't provide more than one type of measurement,=20
>>>does it?
>>>
>>>
>>>What liability would a carrier assume if the handset using GPS=20
>>>provided a
>>>location to 10 meters, and that got over-ridden by a=20
>>
>>carrier network using=20
>>
>>>TOA providing an accuracy of 100 meters, and the ambulance=20
>>
>>arrives too late?
>>
>>>
>>>
>>>
>>>
>>>More than one type of location is not the problem. I=20
>>
>>believe all the=20
>>
>>>past discussion was that the "handset" and the "carrier"=20
>>
>>came up with=20
>>
>>>conflicting information. If they were not conflicting, then=20
>>
>>why have=20
>>
>>>two. If they are conflicting, that is a problem. If the=20
>>
>>handset gives=20
>>
>>>a physical location to 10 meters, why would the carrier=20
>>
>>network bother=20
>>
>>>to include a value of 100 meters accuracy, if the value=20
>>
>>from the end=20
>>
>>>user were within that 100 meters? If it isn't, what should the PSAP=20
>>>do, send an ambulance to both?
>>>
>>>If the handset gave a value within 10 meters and the=20
>>
>>carrier overwrote=20
>>
>>>it with a value accurate to only 100 meters, there would be serious=20
>>>liability issues, especially if the requirement were for an=20
>>
>>accuracy=20
>>
>>>of 50 feet.
>>>
>>>Like I said, NENA (or some such organization) needs to say what the=20
>>>requirements are (in the US). It is silly and hopeless for=20
>>
>>the IETF to=20
>>
>>>try to agree on "requirements".
>>>
>>>Mike
>>>
>>>_______________________________________________
>>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>>This list is for NEW development of the application of SIP Use=20
>>>sip-implementors@cs.columbia.edu for questions on current sip Use=20
>>>sip@ietf.org for new developments of core SIP
>>>
>>>_______________________________________________
>>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>>This list is for NEW development of the application of SIP Use=20
>>>sip-implementors@cs.columbia.edu for questions on current sip Use=20
>>>sip@ietf.org for new developments of core SIP
>>
>>
>>
>>_______________________________________________
>>Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>This list is for NEW development of the application of SIP
>>Use sip-implementors@cs.columbia.edu for questions on current=20
>>sip Use sip@ietf.org for new developments of core SIP
>>

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



From exim@www1.ietf.org  Mon Dec 22 01:38:45 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21737
	for <sipping-archive@odin.ietf.org>; Mon, 22 Dec 2003 01:38:45 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYJho-0001yo-PV
	for sipping-archive@odin.ietf.org; Mon, 22 Dec 2003 01:38:17 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBM6cGEf007604
	for sipping-archive@odin.ietf.org; Mon, 22 Dec 2003 01:38:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYJho-0001yZ-KU
	for sipping-web-archive@optimus.ietf.org; Mon, 22 Dec 2003 01:38:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21722
	for <sipping-web-archive@ietf.org>; Mon, 22 Dec 2003 01:38:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AYJhl-0007TX-00
	for sipping-web-archive@ietf.org; Mon, 22 Dec 2003 01:38:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AYJhi-0007TC-00
	for sipping-web-archive@ietf.org; Mon, 22 Dec 2003 01:38:12 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AYJhi-0007T9-00
	for sipping-web-archive@ietf.org; Mon, 22 Dec 2003 01:38:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYJhZ-0001xU-Sm; Mon, 22 Dec 2003 01:38:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYJgh-0001gk-Fu
	for sipping@optimus.ietf.org; Mon, 22 Dec 2003 01:37:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21704
	for <sipping@ietf.org>; Mon, 22 Dec 2003 01:37:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AYJge-0007Sc-00
	for sipping@ietf.org; Mon, 22 Dec 2003 01:37:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AYJgb-0007SQ-00
	for sipping@ietf.org; Mon, 22 Dec 2003 01:37:03 -0500
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AYJgb-0007S9-00
	for sipping@ietf.org; Mon, 22 Dec 2003 01:37:01 -0500
Received: from dynamicsoft.com ([63.113.46.51])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id hBM6ZYmR004644;
	Mon, 22 Dec 2003 01:35:34 -0500 (EST)
Message-ID: <3FE690B0.5070504@dynamicsoft.com>
Date: Mon, 22 Dec 2003 01:35:28 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Henning Schulzrinne <hgs@cs.columbia.edu>
CC: Stastny Richard <Richard.Stastny@oefeg.at>, Tyler_Johnson@unc.edu,
        "Rosen, Brian" <Brian.Rosen@marconi.com>,
        =?ISO-8859-1?Q?PROUVOST_S=E9bastien_FTRD/DAC/ISS?=
 <sebastien.prouvost@francetelecom.com>,
        Mpierce1@aol.com, mhammer@cisco.com, sipping@ietf.org
Subject: Re: RE : [sipping] comment on draft-polk-sipping-location-require
 ments -01.txt
References: <06CF906FE3998C4E944213062009F162233A5B@oefeg-s02.oefeg.loc> <3FE38976.2060508@cs.columbia.edu>
In-Reply-To: <3FE38976.2060508@cs.columbia.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mail3.dynamicsoft.com id hBM6ZYmR004644
Content-Transfer-Encoding: quoted-printable
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable



Henning Schulzrinne wrote:

> We have been building and advocating location beacons, for example usin=
g=20
> BlueTooth or the wireless AP. Low cost and not subject to VPN issues.=20
> This is very similar to the Cisco Discovery Protocol (CDP), which could=
=20
> be readily extended to handle this functionality. Unfortunately, that=20
> protocol is proprietary.
>=20
> However, this has very little to do with the signaling and session=20
> setup. After all, we don't care about getting IP packets to a PSAP, but=
=20
> rather applications, since the PSAP only cares about a finite set of=20
> applications.
>=20
> Clearly, there are components (such as location objects and DNS or othe=
r=20
> directory lookups) that are useful across application protocols. Brian=20
> and I (and I'm sure, others) have been thinking of various approaches=20
> along these lines.

I think IETF as a whole has been thinking along these lines, and IMHO,=20
done a pretty good job of separating concerns.

One issue is how an entity determines the location of a device; things=20
like GPS, bluetooth, provisioning, etc. will be used here, all of=20
these are outside of IETF scope and there will be many, many solutions=20
for a long time.

Once determined, there is a need for a standardized representation. We=20
have that through geopriv.

Once you have a standardized representation, you may need various=20
application entities to obtain the information in this representation.=20
Thats the role of the using protocol in geopriv. We have one so far,=20
SIMPLE.

Once an application element has location information (either because=20
it knows it itself, or it obtained it from a using protocol), from=20
there what you do with it depends on the application. For SIP, one=20
piece of the problem is routing a call to an emergency center and=20
providing the center with the location of the caller. That is exactly=20
what we are discussing here - encapsulating the location information=20
into the request to achieve that.

Thus, I think we have neatly divided the problem about as well as you=20
possibly can.

-Jonathan R.


>=20
> Stastny Richard wrote:
>=20
>> I fully agree.
>>
>> I also was following this and previous discussions with interest,=20
>> because this issue
>> pops up periodicly over and over again and always dies away because no=
=20
>> solution
>> on the application layer is possible in mobile environments (at least=20
>> non has been found yet).
>> GPS does not work, user entry does not work, DHCP does not work=20
>> because of VPNs, User profile does not work, etc.
>>
>> So the only possiblity is a very simple basic protocol on layer 2, let=
s
>> call it SEP (Simple Emergency Protocol).
>>
>> If this protocol is simple enough, it may be mandated by regulators to=
=20
>> be implemented
>> in every IP access environment and also in any IP access device and it=
=20
>> should also
>> work like 112 in mobiles without login to the environment.
>>
>> The required SW could be made mandatory and part of all IP-enabled=20
>> operating systems.
>> In its simplest varity it could work with a simple click on a=20
>> (soft)button, it could also use
>> existing applications (e-mail, chat, SIP, etc.) if available, but this=
=20
>> is out of scope.
>>
>> To put the necessary parameters in the access device and get access=20
>> from any device cannot be too complicated.
>>
>> I propose to set up an own WG to deal with this asap.
>>
>> best regards
>> Richard
>>
>>
>>> -----Original Message-----
>>> From: Tyler Johnson [mailto:trjohns1@email.unc.edu] Sent: Friday,=20
>>> December 19, 2003 3:38 PM
>>> To: Rosen, Brian
>>> Cc: 'PROUVOST S=E9bastien FTRD/DAC/ISS'; Mpierce1@aol.com;=20
>>> mhammer@cisco.com; sipping@ietf.org; Henning Schulzrinne; Jonathan=20
>>> Rosenberg
>>> Subject: Re: RE : [sipping] comment on=20
>>> draft-polk-sipping-location-require ments -01.txt
>>>
>>>
>>> All,
>>>
>>> I have been following this discussion with some interest. It seems to=
=20
>>> me that in trying to create a 911 service for VoIP, we are applying=20
>>> an old paradigm to a new technology.
>>>
>>> I think that emergency services are important for many applications,=20
>>> and VoIP is just one. For example, I should be able to summon help=20
>>> from my email, IM device, Blackberry, etc. Further, I can see a 'Help=
=20
>>> I've fallen and I can't get up' 802.11b panic pendant for=20
>>> grandmothers. As IP is deployed, it will become increasingly=20
>>> important to provide these services, and municipalities will mandate =
it.
>>>
>>> Because of this, I very much agree with Brian's notion that the=20
>>> physical (or layer 2) network should provide the emergency service=20
>>> signalling. However, it strikes me that it is not appropriate to=20
>>> build this functionality into SIP or the VoIP application. Rather, it=
=20
>>> should be developed as a standalone generic service (outside of=20
>>> SIPPING) that can be accessed by any application. Then, SIPPING could=
=20
>>> point to it as the emergency services method of choice.
>>>
>>> I am concerned that if we build emergency services into VoIP, then=20
>>> VoIP emergency services will quickly become obsolete as the pace of=20
>>> other IP applications requiring emergency services quickens.
>>>
>>> Rosen, Brian wrote:
>>>
>>>> S=E9bastien
>>>>
>>>> There will HAVE to be a single worldwide set of requirements for=20
>>>> emergency services, because the Internet does not respect national=20
>>>> boundaries, and we ALREADY see the effect of this on calls to=20
>>>> emergency services.
>>>>
>>>> My usual example would be a patron of a Paris cafe using a WiFi
>>>> hotspot with a VPN tunnel open to her employers network, in which=20
>>>> she is running a sip softclient.  If an accident occurs outside the=20
>>>> cafe, and she uses her softclient to call for help, how does the=20
>>>> employer, which could be located in another continent, and using its=
=20
>>>> local VoIP carrier, be subject to any laws/specifications of=20
>>>> France?  It cannot.  And the hotspot operator, which might be=20
>>>> subject to some regulation, is unaware that there is a VoIP call,=20
>>>> let alone a call to the emergency system,
>>>> and in fact there is likely encryption on the tunnel making it
>>>> impossible for it to figure it out.
>>>>
>>>> However, if there is an international standard, such as we produce
>>>> here in the IETF, then it is VERY likely that the softclient, the=20
>>>> employer's PBX, and the VoIP carrier are able to correctly handle=20
>>>> the call, routing it to the correct emergency=20
>>>
>>>
>>> answering point,
>>>
>>>> and including call-back information as well as location=20
>>>
>>>
>>> information.=20
>>>
>>>> It is only an international standard that will work as the Internet=20
>>>> joins fixed, mobile and roaming users with a variety of devices,=20
>>>> proxies and carriers operating over multiple continents.
>>>>
>>>> The IETF has a history of not sanctioning regional=20
>>>
>>>
>>> variations in its
>>>
>>>> specifications, and, as the above example illustrates, it is not=20
>>>> feasible to implement regional or national variations.  The=20
>>>
>>>
>>> reality of
>>>
>>>> the situation is that regulating emergency calls is not=20
>>>
>>>
>>> possible with
>>>
>>>> VoIP (unless there was an international treaty that had universal=20
>>>> applicability), but a single, effective international=20
>>>
>>>
>>> standard is very
>>>
>>>> possible.
>>>>
>>>> Such a standard needs an agreed set of requirements, of course.
>>>>
>>>> I've stated my views on the proxy insertion of location.
>>>>
>>>> Brian
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: PROUVOST S=E9bastien FTRD/DAC/ISS=20
>>>> [mailto:sebastien.prouvost@francetelecom.com]
>>>> Sent: Friday, December 19, 2003 6:32 AM
>>>> To: Rosen, Brian; Mpierce1@aol.com; mhammer@cisco.com
>>>> Cc: sipping@ietf.org; Henning Schulzrinne; Jonathan Rosenberg
>>>> Subject: RE : [sipping] comment on=20
>>>> draft-polk-sipping-location-requirements -01.txt
>>>>
>>>>
>>>> Two points here :
>>>>
>>>> First I doubt that there will be a single world wide set of=20
>>>> requirements for emergency calls.
>>>>
>>>> Second, a requirement listed in the original draft was for=20
>>>
>>>
>>> a proxy to
>>>
>>>> be able to give its idea of the terminal location (originally by=20
>>>> asserting the location given by the terminal). However, it may be=20
>>>> easier for a proxy to insert its own info about the location of the=20
>>>> terminal rather than to assert the info given by the=20
>>>
>>>
>>> terminal. It also
>>>
>>>> let the possibility to the called party to get both pieces of=20
>>>> information which is useful information as pointed out by Jonathan.=20
>>>> Both pieces of information shall be passed on.
>>>>
>>>>
>>>> S=E9bastien Prouvost
>>>> France T=E9l=E9com R&D/DAC/CAR
>>>>
>>>>
>>>> -----Message d'origine-----
>>>> De : Rosen, Brian [mailto:Brian.Rosen@marconi.com]
>>>> Envoy=E9 : jeudi 18 d=E9cembre 2003 22:48
>>>> =C0 : 'Mpierce1@aol.com'; mhammer@cisco.com
>>>> Cc : sipping@ietf.org
>>>> Objet : RE: [sipping] comment on=20
>>>
>>>
>>> draft-polk-sipping-location-requirements
>>>
>>>> -01.txt
>>>>
>>>>
>>>> And NENA is working on such requirements, and is starting to engage=20
>>>> other
>>>> organizations in other parts of the world.  It has not been=20
>>>
>>>
>>> decided whether
>>>
>>>> there will be multiple, possibly conflicting requirements=20
>>>
>>>
>>> sent in from
>>>
>>>> different organizations, or whether an effort will be=20
>>>
>>>
>>> mounted to negotiate
>>>
>>>> a single set of requirements.  I favor the latter, because=20
>>>
>>>
>>> we don't have
>>>
>>>> the expertise in the IETF to deal with conflicts if they=20
>>>
>>>
>>> were to arise.=20
>>>
>>>> I'd ask that anyone who knows people who should be involved (NENA
>>>> equivalents in other parts of the world), please contact me.
>>>> Brian
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Mpierce1@aol.com [mailto:Mpierce1@aol.com]
>>>> Sent: Thursday, December 18, 2003 3:47 PM
>>>> To: mhammer@cisco.com
>>>> Cc: sipping@ietf.org
>>>> Subject: Re: [sipping] comment on=20
>>>> draft-polk-sipping-location-requirements
>>>> -01.txt
>>>>
>>>>
>>>> In a message dated 12/18/2003 3:05:36 PM Eastern Standard Time,=20
>>>> mhammer@cisco.com writes:
>>>>
>>>>
>>>>
>>>> It doesn't say you can't provide more than one type of measurement,=20
>>>> does it?
>>>>
>>>>
>>>> What liability would a carrier assume if the handset using GPS=20
>>>> provided a
>>>> location to 10 meters, and that got over-ridden by a=20
>>>
>>>
>>> carrier network using
>>>
>>>> TOA providing an accuracy of 100 meters, and the ambulance=20
>>>
>>>
>>> arrives too late?
>>>
>>>>
>>>>
>>>>
>>>>
>>>> More than one type of location is not the problem. I=20
>>>
>>>
>>> believe all the
>>>
>>>> past discussion was that the "handset" and the "carrier"=20
>>>
>>>
>>> came up with
>>>
>>>> conflicting information. If they were not conflicting, then=20
>>>
>>>
>>> why have
>>>
>>>> two. If they are conflicting, that is a problem. If the=20
>>>
>>>
>>> handset gives
>>>
>>>> a physical location to 10 meters, why would the carrier=20
>>>
>>>
>>> network bother
>>>
>>>> to include a value of 100 meters accuracy, if the value=20
>>>
>>>
>>> from the end
>>>
>>>> user were within that 100 meters? If it isn't, what should the PSAP=20
>>>> do, send an ambulance to both?
>>>>
>>>> If the handset gave a value within 10 meters and the=20
>>>
>>>
>>> carrier overwrote
>>>
>>>> it with a value accurate to only 100 meters, there would be serious=20
>>>> liability issues, especially if the requirement were for an=20
>>>
>>>
>>> accuracy
>>>
>>>> of 50 feet.
>>>>
>>>> Like I said, NENA (or some such organization) needs to say what the=20
>>>> requirements are (in the US). It is silly and hopeless for=20
>>>
>>>
>>> the IETF to
>>>
>>>> try to agree on "requirements".
>>>>
>>>> Mike
>>>>
>>>> _______________________________________________
>>>> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>>> This list is for NEW development of the application of SIP Use=20
>>>> sip-implementors@cs.columbia.edu for questions on current sip Use=20
>>>> sip@ietf.org for new developments of core SIP
>>>>
>>>> _______________________________________________
>>>> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>>> This list is for NEW development of the application of SIP Use=20
>>>> sip-implementors@cs.columbia.edu for questions on current sip Use=20
>>>> sip@ietf.org for new developments of core SIP
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>> This list is for NEW development of the application of SIP
>>> Use sip-implementors@cs.columbia.edu for questions on current sip Use=
=20
>>> sip@ietf.org for new developments of core SIP
>>>
>=20

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


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



From exim@www1.ietf.org  Mon Dec 22 01:54:36 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22075
	for <sipping-archive@odin.ietf.org>; Mon, 22 Dec 2003 01:54:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYJx9-0002P4-Pt
	for sipping-archive@odin.ietf.org; Mon, 22 Dec 2003 01:54:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBM6s7aI009238
	for sipping-archive@odin.ietf.org; Mon, 22 Dec 2003 01:54:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYJx9-0002Ov-Mm
	for sipping-web-archive@optimus.ietf.org; Mon, 22 Dec 2003 01:54:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22060
	for <sipping-web-archive@ietf.org>; Mon, 22 Dec 2003 01:54:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AYJx6-00003E-00
	for sipping-web-archive@ietf.org; Mon, 22 Dec 2003 01:54:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AYJx5-000036-00
	for sipping-web-archive@ietf.org; Mon, 22 Dec 2003 01:54:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AYJx5-000033-00
	for sipping-web-archive@ietf.org; Mon, 22 Dec 2003 01:54:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYJx4-0002Nl-KO; Mon, 22 Dec 2003 01:54:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYJwE-0002MO-Ez
	for sipping@optimus.ietf.org; Mon, 22 Dec 2003 01:53:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22048
	for <sipping@ietf.org>; Mon, 22 Dec 2003 01:53:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AYJwB-00002k-00
	for sipping@ietf.org; Mon, 22 Dec 2003 01:53:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AYJwA-00002c-00
	for sipping@ietf.org; Mon, 22 Dec 2003 01:53:06 -0500
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AYJw9-00000M-00
	for sipping@ietf.org; Mon, 22 Dec 2003 01:53:05 -0500
Received: from dynamicsoft.com ([63.113.46.51])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id hBM6qfmR004648;
	Mon, 22 Dec 2003 01:52:41 -0500 (EST)
Message-ID: <3FE694B4.6040101@dynamicsoft.com>
Date: Mon, 22 Dec 2003 01:52:36 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Pinal Jean-Pierre <jean-pierre.pinal@siemens.com>
CC: "'sipping@ietf.org'" <sipping@ietf.org>
Subject: Re: [Sipping] consecutive NOTIFY and automatic unsubscription upon
 500 error re sponse
References: <5B788FC2CAFBD6118BAE0030848B025C80F6A1@LNN201E>
In-Reply-To: <5B788FC2CAFBD6118BAE0030848B025C80F6A1@LNN201E>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

This is a good question. I believe it is an error in RFC 3265, as this 
case should not cause termination of the dialog. The essence of the 
problem is that RFC 3265 has much more strict rules for dialog 
termination than RFC 3261. In RFC 3261, it is only a 481 or 408 which 
causes dialog termination. RFC 3265 adds to that, extending it to any 
error response for which a remedy is not apparent. It is not obvious 
as to whether a 500 response fits into the category of "no further 
action can be taken to retry the request".

However, I would argue that, in the case of a 500, there is a clear 
action. According to RFC 3261, you should try again in a few seconds. 
As a result, a 500 response should not be a failure as defined by 
rfc3265 and not cause the dialog to terminate. However, this is far 
from clear in RFC 3265, and the spec ought to have been more clear 
about exactly which response codes really constitute a failure. We 
need to clarify that 500 does NOT.

I've added this to bugzilla. You can find the bug report at:
http://bugs.sipit.net/sipwg/show_bug.cgi?id=744

Thanks,
Jonathan R.



Pinal Jean-Pierre wrote:

> Hello
> 
>  
> 
> 1)
> 
> As described in RFC 3261, a UA may start a next transaction before the 
> previous is terminated
> 
> (except for INVITE)
> 
>  
> 
> 2)
> 
> After subscription, if notifier sends two consecutive NOTIFYs, the
> 
> subscriber may receive the second NOTIFY first and reject the first
> 
> with 500 in conformance with RFC 3261
> 
>  
> 
> RFC 3261
> 
> 12.2.2 UAS Behavior
> 
> "If the remote sequence number was not empty, but the sequence number
> 
>    of the request is lower than the remote sequence number, the request
> 
>    is out of order and MUST be rejected with a 500 (Server Internal
> 
>    Error) response."
> 
>  
> 
> 3)
> 
> And in RFC 3265
> 
>  
> 
> "A NOTIFY request is considered failed if the response times out, or a
> 
> non-200 class response code is received which has no "Retry-After"
> 
> header and no implied further action which can be taken to retry
> 
> therequest (e.g., "401 Authorization Required".)"
> 
> ...
> 
> "If the NOTIFY request fails (as defined above) due to an error
> 
> response, and the subscription was installed using a soft-state
> 
> mechanism, the notifier MUST remove the corresponding
> 
> subscription."
> 
>  
> 
> => In the case when second NOTIFY is received before first, the NOTIFIER 
> receives a 500 for the first NOTIFY and the subscription is removed!
> 
> But the subscriber does not want that its subscription is removed!
> 
>  
> 
> Here, what is wrong?
> 
>  
> 
> Must the subscriber sends a 500 with always a Retry-After header in 
> order to avoid subscription deletion?
> 
>  
> 
> In this case, must the NOTIFIER send a new NOTIFY with a full 
> description of subscribed state?
> 
>  
> 
> I found nothing in RFC3265 about consecutive NOTIFYs.
> 
>  
> 
> Or must the implied event package define in "Notifier generation of 
> NOTIFY requests" section that the notifier can not generate a new NOTIFY 
> before response of the previous NOTIFY has been received?
> 
> I think it is not the responsibility of event package
> 
>  
> 
> Is there a lack in RFC3265?
> 
>  
> 
>  
> 
> Best regards
> 
>  
> 
> Jean-Pierre
> 
>  
> 

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


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



From exim@www1.ietf.org  Mon Dec 22 08:56:40 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16663
	for <sipping-archive@odin.ietf.org>; Mon, 22 Dec 2003 08:56:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYQXc-0001ET-H4
	for sipping-archive@odin.ietf.org; Mon, 22 Dec 2003 08:56:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBMDuCPI004734
	for sipping-archive@odin.ietf.org; Mon, 22 Dec 2003 08:56:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYQXc-0001EH-Bo
	for sipping-web-archive@optimus.ietf.org; Mon, 22 Dec 2003 08:56:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16654
	for <sipping-web-archive@ietf.org>; Mon, 22 Dec 2003 08:56:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AYQXa-0003bo-00
	for sipping-web-archive@ietf.org; Mon, 22 Dec 2003 08:56:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AYQXY-0003bV-00
	for sipping-web-archive@ietf.org; Mon, 22 Dec 2003 08:56:10 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AYQXY-0003bS-00
	for sipping-web-archive@ietf.org; Mon, 22 Dec 2003 08:56:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYQXR-0001Cj-Ie; Mon, 22 Dec 2003 08:56:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYQWY-0001BW-56
	for sipping@optimus.ietf.org; Mon, 22 Dec 2003 08:55:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16613
	for <sipping@ietf.org>; Mon, 22 Dec 2003 08:54:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AYQWM-0003Yb-00
	for sipping@ietf.org; Mon, 22 Dec 2003 08:54:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AYQVw-0003YF-00
	for sipping@ietf.org; Mon, 22 Dec 2003 08:54:29 -0500
Received: from pooh.ulticom.com ([208.255.120.2] helo=chuckie.dgms.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AYQVv-0003Xl-00
	for sipping@ietf.org; Mon, 22 Dec 2003 08:54:28 -0500
Received: from pcasveren (localhost [127.0.0.1])
	by chuckie.dgms.com (8.9.3/8.9.3) with SMTP id IAA22571;
	Mon, 22 Dec 2003 08:53:57 -0500 (EST)
From: "Tolga Asveren" <asveren@ulticom.com>
To: "Jonathan Rosenberg" <jdrosen@dynamicsoft.com>,
        "Pinal Jean-Pierre" <jean-pierre.pinal@siemens.com>
Cc: <sipping@ietf.org>
Subject: RE: [Sipping] consecutive NOTIFY and automatic unsubscription upon 500 error re sponse
Date: Mon, 22 Dec 2003 08:52:58 -0500
Message-ID: <GBEBKGPKHGPAOFCLBNAMEEAECDAA.asveren@ulticom.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <3FE694B4.6040101@dynamicsoft.com>
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I believe the main problem is with 3261 rather than with 3265. Allowing
concurrent transactions and than rejecting them because of missequencing in
the network with an error code indicating "Server Internal Error" sounds
strange to me. One could argue, if the client is aware that there might be
missequencing in the network, it should not start concurrent transactions,
but even then I don't see something to be done on server side, so this error
code still sounds not very appropriate to me.
For example, for the specific case described below, one can change 3265 to
handle 500 error correctly. But what does it mean "correctly", what if it is
generated because of a real server internal error rather than missequencing
in the network?
So, I believe, it might be an idea to have a special error code for network
missequencing in 3261. Also an explanation about concurrent transaction with
networks not guaranteeing sequence prevention might help.

   Tolga


> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]On Behalf Of
> Jonathan Rosenberg
> Sent: Monday, December 22, 2003 1:53 AM
> To: Pinal Jean-Pierre
> Cc: 'sipping@ietf.org'
> Subject: Re: [Sipping] consecutive NOTIFY and automatic unsubscription
> upon 500 error re sponse
>
>
> This is a good question. I believe it is an error in RFC 3265, as this
> case should not cause termination of the dialog. The essence of the
> problem is that RFC 3265 has much more strict rules for dialog
> termination than RFC 3261. In RFC 3261, it is only a 481 or 408 which
> causes dialog termination. RFC 3265 adds to that, extending it to any
> error response for which a remedy is not apparent. It is not obvious
> as to whether a 500 response fits into the category of "no further
> action can be taken to retry the request".
>
> However, I would argue that, in the case of a 500, there is a clear
> action. According to RFC 3261, you should try again in a few seconds.
> As a result, a 500 response should not be a failure as defined by
> rfc3265 and not cause the dialog to terminate. However, this is far
> from clear in RFC 3265, and the spec ought to have been more clear
> about exactly which response codes really constitute a failure. We
> need to clarify that 500 does NOT.
>
> I've added this to bugzilla. You can find the bug report at:
> http://bugs.sipit.net/sipwg/show_bug.cgi?id=744
>
> Thanks,
> Jonathan R.
>
>
>
> Pinal Jean-Pierre wrote:
>
> > Hello
> >
> >
> >
> > 1)
> >
> > As described in RFC 3261, a UA may start a next transaction before the
> > previous is terminated
> >
> > (except for INVITE)
> >
> >
> >
> > 2)
> >
> > After subscription, if notifier sends two consecutive NOTIFYs, the
> >
> > subscriber may receive the second NOTIFY first and reject the first
> >
> > with 500 in conformance with RFC 3261
> >
> >
> >
> > RFC 3261
> >
> > 12.2.2 UAS Behavior
> >
> > "If the remote sequence number was not empty, but the sequence number
> >
> >    of the request is lower than the remote sequence number, the request
> >
> >    is out of order and MUST be rejected with a 500 (Server Internal
> >
> >    Error) response."
> >
> >
> >
> > 3)
> >
> > And in RFC 3265
> >
> >
> >
> > "A NOTIFY request is considered failed if the response times out, or a
> >
> > non-200 class response code is received which has no "Retry-After"
> >
> > header and no implied further action which can be taken to retry
> >
> > therequest (e.g., "401 Authorization Required".)"
> >
> > ...
> >
> > "If the NOTIFY request fails (as defined above) due to an error
> >
> > response, and the subscription was installed using a soft-state
> >
> > mechanism, the notifier MUST remove the corresponding
> >
> > subscription."
> >
> >
> >
> > => In the case when second NOTIFY is received before first, the
> NOTIFIER
> > receives a 500 for the first NOTIFY and the subscription is removed!
> >
> > But the subscriber does not want that its subscription is removed!
> >
> >
> >
> > Here, what is wrong?
> >
> >
> >
> > Must the subscriber sends a 500 with always a Retry-After header in
> > order to avoid subscription deletion?
> >
> >
> >
> > In this case, must the NOTIFIER send a new NOTIFY with a full
> > description of subscribed state?
> >
> >
> >
> > I found nothing in RFC3265 about consecutive NOTIFYs.
> >
> >
> >
> > Or must the implied event package define in "Notifier generation of
> > NOTIFY requests" section that the notifier can not generate a
> new NOTIFY
> > before response of the previous NOTIFY has been received?
> >
> > I think it is not the responsibility of event package
> >
> >
> >
> > Is there a lack in RFC3265?
> >
> >
> >
> >
> >
> > Best regards
> >
> >
> >
> > Jean-Pierre
> >
> >
> >
>
> --
> Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
> Chief Technology Officer                    Parsippany, NJ 07054-2711
> dynamicsoft
> jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
> http://www.jdrosen.net                      PHONE: (973) 952-5000
> http://www.dynamicsoft.com
>
>
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP


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



From exim@www1.ietf.org  Mon Dec 22 09:28:51 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17909
	for <sipping-archive@odin.ietf.org>; Mon, 22 Dec 2003 09:28:51 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYR2h-0002Vu-92
	for sipping-archive@odin.ietf.org; Mon, 22 Dec 2003 09:28:23 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBMESJPV009663
	for sipping-archive@odin.ietf.org; Mon, 22 Dec 2003 09:28:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYR2h-0002Vm-5a
	for sipping-web-archive@optimus.ietf.org; Mon, 22 Dec 2003 09:28:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17891
	for <sipping-web-archive@ietf.org>; Mon, 22 Dec 2003 09:28:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AYR2f-0004mt-00
	for sipping-web-archive@ietf.org; Mon, 22 Dec 2003 09:28:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AYR2e-0004mm-00
	for sipping-web-archive@ietf.org; Mon, 22 Dec 2003 09:28:17 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AYR2d-0004mj-00
	for sipping-web-archive@ietf.org; Mon, 22 Dec 2003 09:28:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYR2P-0002SH-J1; Mon, 22 Dec 2003 09:28:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYR1t-0002Ru-AC
	for sipping@optimus.ietf.org; Mon, 22 Dec 2003 09:27:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17882
	for <sipping@ietf.org>; Mon, 22 Dec 2003 09:27:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AYR1q-0004mE-00
	for sipping@ietf.org; Mon, 22 Dec 2003 09:27:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AYR1o-0004m7-00
	for sipping@ietf.org; Mon, 22 Dec 2003 09:27:25 -0500
Received: from albatross-ext.wise.edt.ericsson.se ([193.180.251.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AYR1o-0004m4-00
	for sipping@ietf.org; Mon, 22 Dec 2003 09:27:24 -0500
Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120])
	by albatross-ext.wise.edt.ericsson.se (8.12.10/8.12.10/WIREfire-1.8) with ESMTP id hBMERJI2022280;
	Mon, 22 Dec 2003 15:27:19 +0100 (MET)
Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72)
	id <ZJBM679T>; Mon, 22 Dec 2003 15:27:26 +0100
Message-ID: <F8EFC4B4A8C016428BC1F589296D4FBF05683E43@esealnt630.al.sw.ericsson.se>
From: "Christer Holmberg (JO/LMF)" <christer.holmberg@ericsson.com>
To: "'Francois Audet'" <audet@nortelnetworks.com>,
        "Gonzalo Camarillo (JO/LMF)" <gonzalo.camarillo@ericsson.com>
Cc: "'Dean Willis'" <dean.willis@softarmor.com>,
        "'sipping@ietf.org'"
	 <sipping@ietf.org>,
        "'rohan@cisco.com'" <rohan@cisco.com>
Subject: RE: [Sipping] WGLC on Early Media Drafts
Date: Mon, 22 Dec 2003 15:26:56 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3C897.A7047F21"
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=HTML_30_40,HTML_FONTCOLOR_BLUE,
	HTML_MESSAGE autolearn=no version=2.60

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

Hi,
 
NOT RECOMMENDED is fine with me too, as long as it's not forbidden :) My issue, which I have been talking with Gonzalo about, has been related with the gateway issue, where one probably doesn't want to reserve two ports for every session setup.
 
Regards,
 
Christer Holmberg
Ericsson Finland
 
 
 

-----Original Message-----
From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]On Behalf Of Francois Audet
Sent: 19. joulukuuta 2003 1:35
To: Gonzalo Camarillo (JO/LMF)
Cc: 'Dean Willis'; 'sipping@ietf.org'; 'rohan@cisco.com'
Subject: RE: [Sipping] WGLC on Early Media Drafts



> I am aware that some implementors, in particular gateway 
> vendors, will 
> use the same port anyway. That's why it is a NOT RECOMMENDED, 
> instead of 
> a MUST NOT. Nevertheless, from the standard point of view, you really 
> need to distinguish between early and regular media every 
> time, because 
> if you do not do it, and the INVITE forks, you may get media 
> clipping or 
> mixing of media (early and regular) from different sources. 
> 
> I believe that the NOT RECOMMENDED is a good compromise 
> between what the 
> standard should say about a general situation and what the 
> implementors 
> will do in controlled environments. 

I hadn't tought about gateways, but you are right that it would double 
the number of required ports. 

There are other issues as well, even for IP phones. 

Using 2 different ports will mean that if you are using STUN, you will need 
one more STUN query for the early media port. Same thing for ICE. 

Then if you are using RSVP or NSIS, it will mean that you have to double the procedures. 

It just makes the process heavier in those cases. 

Anyways, this is not a big issue to me, so I am OK with it. 


------_=_NextPart_001_01C3C897.A7047F21
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] WGLC on Early Media Drafts</TITLE>

<META content="MSHTML 6.00.2800.1276" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=781442114-22122003>Hi,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=781442114-22122003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=781442114-22122003>NOT 
RECOMMENDED is fine with me too, as long as it's not&nbsp;forbidden :)&nbsp;My 
issue, which I have been talking with Gonzalo about,&nbsp;has been&nbsp;related 
with the gateway issue, where one probably doesn't want to reserve two ports for 
every session setup.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=781442114-22122003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=781442114-22122003>Regards,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=781442114-22122003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=781442114-22122003>Christer Holmberg</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=781442114-22122003>Ericsson Finland</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</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> sipping-admin@ietf.org 
  [mailto:sipping-admin@ietf.org]<B>On Behalf Of </B>Francois 
  Audet<BR><B>Sent:</B> 19. joulukuuta 2003 1:35<BR><B>To:</B> Gonzalo Camarillo 
  (JO/LMF)<BR><B>Cc:</B> 'Dean Willis'; 'sipping@ietf.org'; 
  'rohan@cisco.com'<BR><B>Subject:</B> RE: [Sipping] WGLC on Early Media 
  Drafts<BR><BR></FONT></DIV>
  <P><FONT size=2>&gt; I am aware that some implementors, in particular gateway 
  </FONT><BR><FONT size=2>&gt; vendors, will </FONT><BR><FONT size=2>&gt; use 
  the same port anyway. That's why it is a NOT RECOMMENDED, </FONT><BR><FONT 
  size=2>&gt; instead of </FONT><BR><FONT size=2>&gt; a MUST NOT. Nevertheless, 
  from the standard point of view, you really </FONT><BR><FONT size=2>&gt; need 
  to distinguish between early and regular media every </FONT><BR><FONT 
  size=2>&gt; time, because </FONT><BR><FONT size=2>&gt; if you do not do it, 
  and the INVITE forks, you may get media </FONT><BR><FONT size=2>&gt; clipping 
  or </FONT><BR><FONT size=2>&gt; mixing of media (early and regular) from 
  different sources.</FONT> <BR><FONT size=2>&gt; </FONT><BR><FONT size=2>&gt; I 
  believe that the NOT RECOMMENDED is a good compromise </FONT><BR><FONT 
  size=2>&gt; between what the </FONT><BR><FONT size=2>&gt; standard should say 
  about a general situation and what the </FONT><BR><FONT size=2>&gt; 
  implementors </FONT><BR><FONT size=2>&gt; will do in controlled 
  environments.</FONT> </P>
  <P><FONT size=2>I hadn't tought about gateways, but you are right that it 
  would double</FONT> <BR><FONT size=2>the number of required ports.</FONT> </P>
  <P><FONT size=2>There are other issues as well, even for IP phones.</FONT> 
</P>
  <P><FONT size=2>Using 2 different ports will mean that if you are using STUN, 
  you will need</FONT> <BR><FONT size=2>one more STUN query for the early media 
  port. Same thing for ICE.</FONT> </P>
  <P><FONT size=2>Then if you are using RSVP or NSIS, it will mean that you have 
  to double the procedures.</FONT> </P>
  <P><FONT size=2>It just makes the process heavier in those cases.</FONT> </P>
  <P><FONT size=2>Anyways, this is not a big issue to me, so I am OK with 
  it.</FONT> </P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C3C897.A7047F21--

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



From exim@www1.ietf.org  Tue Dec 23 18:18:07 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18821
	for <sipping-archive@odin.ietf.org>; Tue, 23 Dec 2003 18:18:07 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYvmX-0006Cq-83
	for sipping-archive@odin.ietf.org; Tue, 23 Dec 2003 18:17:41 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBNNHfYw023852
	for sipping-archive@odin.ietf.org; Tue, 23 Dec 2003 18:17:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYvmW-0006CY-Us
	for sipping-web-archive@optimus.ietf.org; Tue, 23 Dec 2003 18:17:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18793
	for <sipping-web-archive@ietf.org>; Tue, 23 Dec 2003 18:17:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AYvmT-0003v5-00
	for sipping-web-archive@ietf.org; Tue, 23 Dec 2003 18:17:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AYvka-0003tM-00
	for sipping-web-archive@ietf.org; Tue, 23 Dec 2003 18:15:40 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AYvj4-0003sB-00
	for sipping-web-archive@ietf.org; Tue, 23 Dec 2003 18:14:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYviz-00061d-53; Tue, 23 Dec 2003 18:14:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AYvib-00061O-CS
	for sipping@optimus.ietf.org; Tue, 23 Dec 2003 18:13:37 -0500
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18348
	for <sipping@odin.ietf.org>; Tue, 23 Dec 2003 18:13:32 -0500 (EST)
Received: from apache by asgard.ietf.org with local (Exim 4.14)
	id 1AYvi7-0005cG-Fn; Tue, 23 Dec 2003 18:13:07 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Cc: Internet Architecture Board <iab@iab.org>,
        RFC Editor <rfc-editor@rfc-editor.org>, <sipping@ietf.org>
Message-Id: <E1AYvi7-0005cG-Fn@asgard.ietf.org>
Date: Tue, 23 Dec 2003 18:13:07 -0500
Subject: [Sipping] Protocol Action: 'A Message Summary and Message Waiting
 Indication Event Package for the Session Initiation Protocol (SIP)' to
 Proposed Standard
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60

The IESG has approved the following document:

- 'A Message Summary and Message Waiting Indication Event Package for the 
   Session Initiation Protocol (SIP) '
   <draft-ietf-sipping-mwi-04.txt> as a Proposed Standard

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

The IESG contact persons are Allison Mankin and Jon Peterson.

Technical Summary

   This document describes a SIP event package to carry message waiting
   status and message summaries from a messaging system to an interested
   User Agent.

    Using SIP-Specific Event Notification,  a Subscriber User Agent
   (typically an IP phone or SIP software User Agent) subscribes to the
   status of their messages.  A SIP User Agent acting on behalf of the
   user's messaging system then notifies the Subscriber whenever the
   messaging account's messages have changed.   The mime type
   application/simple-message-summary is defined for these notifications.

Working Group Summary

   The working group reviewed and supported advancing this specification.  

Protocol Quality

    The event package has been checked against RFC 3265.  The document was
     reviewed for the IESG by Allison Mankin.

RFC Editor Note:

Old:

   To: <alice@atlanta.com>
   From: <bob@biloxi.com>

New:

   To: <alice@atlanta.example.com>
   From: <bob@biloxi.example.com>

[one instance]


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



From exim@www1.ietf.org  Wed Dec 24 09:04:26 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10650
	for <sipping-archive@odin.ietf.org>; Wed, 24 Dec 2003 09:04:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AZ9cD-0004bQ-OE
	for sipping-archive@odin.ietf.org; Wed, 24 Dec 2003 09:03:57 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBOE3voE017686
	for sipping-archive@odin.ietf.org; Wed, 24 Dec 2003 09:03:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AZ9cD-0004bB-J0
	for sipping-web-archive@optimus.ietf.org; Wed, 24 Dec 2003 09:03:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10644
	for <sipping-web-archive@ietf.org>; Wed, 24 Dec 2003 09:03:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AZ9cC-00047R-00
	for sipping-web-archive@ietf.org; Wed, 24 Dec 2003 09:03:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AZ9aM-000465-00
	for sipping-web-archive@ietf.org; Wed, 24 Dec 2003 09:02:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AZ9Zb-00043x-00
	for sipping-web-archive@ietf.org; Wed, 24 Dec 2003 09:01:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AZ9ZO-0004QQ-G8; Wed, 24 Dec 2003 09:01:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AZ9Yu-0004Ps-1z
	for sipping@optimus.ietf.org; Wed, 24 Dec 2003 09:00:32 -0500
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10593
	for <sipping@odin.ietf.org>; Wed, 24 Dec 2003 09:00:29 -0500 (EST)
Received: from apache by asgard.ietf.org with local (Exim 4.14)
	id 1AZ9Yq-0003sw-7Y; Wed, 24 Dec 2003 09:00:28 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Cc: Internet Architecture Board <iab@iab.org>,
        RFC Editor <rfc-editor@rfc-editor.org>, <sipping@ietf.org>
Message-Id: <E1AZ9Yq-0003sw-7Y@asgard.ietf.org>
Date: Wed, 24 Dec 2003 09:00:28 -0500
Subject: [Sipping] Document Action: 'Authentication, Authorization and Accounting
 Requirements for the Session Initiation Protocol' to Informational
 RFC
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60

The IESG has approved the following document:

- 'Authentication, Authorization and Accounting Requirements for the 
   Session Initiation Protocol '
   <draft-ietf-sipping-aaa-req-04.txt> as an Informational RFC

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

The IESG contact persons are Allison Mankin and Jon Peterson.

RFC Editor Note

RFC Editor, please make the following clarifying change in Section 4,
Security Considerations.
Old:

   This document is informational in nature, so it does not directly
   affect the security of the Internet. However, security is a basic
   requirement of this work. Section 2.1.9 contains security
   requirements related to the SIP-AAA interface.

New:

   Security is a critical requirement of AAA for the Session Initiation
   Protocol.  Section 2.1.9 describes the threats and security 
   requirements.  Section 2.2 elaborates on the authentication and
   authorization requirements.


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



From exim@www1.ietf.org  Wed Dec 24 16:24:28 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23926
	for <sipping-archive@odin.ietf.org>; Wed, 24 Dec 2003 16:24:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AZGU4-0003Tt-1X
	for sipping-archive@odin.ietf.org; Wed, 24 Dec 2003 16:24:00 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBOLO0r5013375
	for sipping-archive@odin.ietf.org; Wed, 24 Dec 2003 16:24:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AZGU3-0003Te-Uf
	for sipping-web-archive@optimus.ietf.org; Wed, 24 Dec 2003 16:23:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23917
	for <sipping-web-archive@ietf.org>; Wed, 24 Dec 2003 16:23:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AZGU2-0001Ws-00
	for sipping-web-archive@ietf.org; Wed, 24 Dec 2003 16:23:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AZGS8-0001W7-00
	for sipping-web-archive@ietf.org; Wed, 24 Dec 2003 16:22:01 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AZGRJ-0001VK-00
	for sipping-web-archive@ietf.org; Wed, 24 Dec 2003 16:21:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AZGRB-0003EB-Ib; Wed, 24 Dec 2003 16:21:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AZGQD-0003B3-Kg
	for sipping@optimus.ietf.org; Wed, 24 Dec 2003 16:20:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23885
	for <sipping@ietf.org>; Wed, 24 Dec 2003 16:19:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AZGQB-0001UV-00
	for sipping@ietf.org; Wed, 24 Dec 2003 16:19:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AZGOM-0001TM-00
	for sipping@ietf.org; Wed, 24 Dec 2003 16:18:06 -0500
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AZGN0-0001Ml-00
	for sipping@ietf.org; Wed, 24 Dec 2003 16:16:42 -0500
Received: from dynamicsoft.com ([63.113.46.15])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id hBOLGHmR005999;
	Wed, 24 Dec 2003 16:16:17 -0500 (EST)
Message-ID: <3FEA021C.7060800@dynamicsoft.com>
Date: Wed, 24 Dec 2003 16:16:12 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Eric Burger <eburger@snowshore.com>
CC: "Sipping (E-mail)" <sipping@ietf.org>
Subject: Re: [Sipping] Comment on 3pcc-05
References: <4A3384433CE2AB46A63468CB207E209D4F6919@zoe.office.snowshore.com>
In-Reply-To: <4A3384433CE2AB46A63468CB207E209D4F6919@zoe.office.snowshore.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Old email; sorry for the late response.

Eric Burger wrote:
> The draft highlights that the message exchange with the UAS (B)
> happens on human terms, e.g., waiting for a person to answer before
> issuing an OK.
> 
> I think it is worth pointing that for all the flows not only does
> A's phone ring first, but they hear digital silence during the
> sequences with B's UAS.

Yup. I added a note to make sure that was clear. If it bothers you, 
you can always connect them to a music on hold source while the call 
to B occurs.

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

Yeah, I noticed that. It seems that the reference is broken at 
xml.resource.org. I fixed mine locally and will report the bug.

Thanks,
Jonathan R.


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


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



From exim@www1.ietf.org  Thu Dec 25 14:34:52 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06807
	for <sipping-archive@odin.ietf.org>; Thu, 25 Dec 2003 14:34:51 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AZbFY-000585-BR
	for sipping-archive@odin.ietf.org; Thu, 25 Dec 2003 14:34:24 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBPJYODl019710
	for sipping-archive@odin.ietf.org; Thu, 25 Dec 2003 14:34:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AZbFY-00057p-54
	for sipping-web-archive@optimus.ietf.org; Thu, 25 Dec 2003 14:34:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06793
	for <sipping-web-archive@ietf.org>; Thu, 25 Dec 2003 14:34:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AZbFV-0004i0-00
	for sipping-web-archive@ietf.org; Thu, 25 Dec 2003 14:34:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AZbDa-0004gi-00
	for sipping-web-archive@ietf.org; Thu, 25 Dec 2003 14:32:23 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AZbCZ-0004fz-00
	for sipping-web-archive@ietf.org; Thu, 25 Dec 2003 14:31:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AZbCJ-0004xJ-Gd; Thu, 25 Dec 2003 14:31:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AZbBf-0004wS-72
	for sipping@optimus.ietf.org; Thu, 25 Dec 2003 14:30:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06745
	for <sipping@ietf.org>; Thu, 25 Dec 2003 14:30:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AZbBc-0004f6-00
	for sipping@ietf.org; Thu, 25 Dec 2003 14:30:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AZb9k-0004eE-00
	for sipping@ietf.org; Thu, 25 Dec 2003 14:28:24 -0500
Received: from imr1.ericy.com ([198.24.6.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AZb83-0004bm-00
	for sipping@ietf.org; Thu, 25 Dec 2003 14:26:39 -0500
Received: from eamrcnt750.exu.ericsson.se (eamrcnt750.exu.ericsson.se [138.85.133.51])
	by imr1.ericy.com (8.12.10/8.12.10) with ESMTP id hBPJQ9Wm015889;
	Thu, 25 Dec 2003 13:26:09 -0600 (CST)
Received: from ericsson.com (rvi2-92-54.sw.ericsson.se [153.88.92.54]) by eamrcnt750.exu.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72)
	id YGLSG996; Thu, 25 Dec 2003 13:25:36 -0600
Message-ID: <3FEB39B7.6030902@ericsson.com>
Date: Thu, 25 Dec 2003 21:25:43 +0200
X-Sybari-Trust: 379ec12a 76be5e0c 125231cb 00000138
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
CC: allison Mankin <mankin@psg.com>, John Loughney <john.loughney@nokia.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] SIP-AAA reqs status
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

FYI: we have been working with some IESG and IAB members to address 
their comments on the SIP-AAA reqs draft. This is the result of our 
discussions:

http://www.ietf.org/internet-drafts/draft-ietf-sipping-aaa-req-04.txt

We have added a section about RADIUS. It clarifies the scope of the 
requirements in the document. We have also made a few clarifications to 
existing requirements. Now everything should be clearer in the draft. We 
have expanded the Security Considerations Section as well.

Now, it should be ready for publication as an RFC.

Thanks to all of you who provided comments.

Gonzalo


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



From exim@www1.ietf.org  Tue Dec 30 12:42:56 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00367
	for <sipping-archive@odin.ietf.org>; Tue, 30 Dec 2003 12:42:56 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbNsz-0005pF-K1
	for sipping-archive@odin.ietf.org; Tue, 30 Dec 2003 12:42:29 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBUHgTar022390
	for sipping-archive@odin.ietf.org; Tue, 30 Dec 2003 12:42:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbNsz-0005p3-AT
	for sipping-web-archive@optimus.ietf.org; Tue, 30 Dec 2003 12:42:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00351
	for <sipping-web-archive@ietf.org>; Tue, 30 Dec 2003 12:42:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbNsx-000776-00
	for sipping-web-archive@ietf.org; Tue, 30 Dec 2003 12:42:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbNr3-00071b-00
	for sipping-web-archive@ietf.org; Tue, 30 Dec 2003 12:40:30 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbNq3-0006zI-00
	for sipping-web-archive@ietf.org; Tue, 30 Dec 2003 12:39:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbNpd-0005bQ-FD; Tue, 30 Dec 2003 12:39:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbNox-0005aA-Sz
	for sipping@optimus.ietf.org; Tue, 30 Dec 2003 12:38:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00254
	for <sipping@ietf.org>; Tue, 30 Dec 2003 12:38:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbNow-0006wz-00
	for sipping@ietf.org; Tue, 30 Dec 2003 12:38:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbNn4-0006v3-00
	for sipping@ietf.org; Tue, 30 Dec 2003 12:36:23 -0500
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbNlK-0006r4-00
	for sipping@ietf.org; Tue, 30 Dec 2003 12:34:34 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-3.cisco.com with ESMTP; 30 Dec 2003 09:40:11 +0000
Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id hBUHY2VM024904;
	Tue, 30 Dec 2003 09:34:03 -0800 (PST)
Received: from [192.168.0.4] (sjc-vpn3-639.cisco.com [10.21.66.127])
	by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id ALB64363;
	Tue, 30 Dec 2003 09:34:01 -0800 (PST)
User-Agent: Microsoft-Entourage/10.1.4.030702.0
Date: Tue, 30 Dec 2003 09:34:01 -0800
Subject: Re: [Sipping] Problem with reg-event that needs immediate fix
From: Cullen Jennings <fluffy@cisco.com>
To: Jonathan Rosenberg <jdrosen@dynamicsoft.com>, sipping <sipping@ietf.org>
Message-ID: <BC16F709.2AD0D%fluffy@cisco.com>
In-Reply-To: <3FE1E027.2090305@dynamicsoft.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


I would prefer to change the Schema to be right for this things we know are
coming even if that broke backwards compatibility.

The more I look at the schema, I think the whole the things could be
structured a little better for extensibility. I had the same comment on some
of the other schema that have been in sipish drafts. We should probably make
this part of our NITS review.

Cullen

On 12/18/03 9:13 AM, "Jonathan Rosenberg" <jdrosen@dynamicsoft.com> wrote:

> While implementing the sipping reg-event draft, we ran into a serious
> technical problem.
> 
> The problem is that the specification has not left sufficient room for
> extensibility within the XML schema. It allows for new information to
> be added to the <registration> element (which describes the AOR), but
> does not allow any additional information to be provided about a
> contact. We ran into this problem because we needed to add path
> information (ala rfc 3327) to the notifications, but this information
> is per contact. There is no way to do this with the current specification.
> 
> The essence of the problem is that the contact element has, as
> content, the actual URI. This makes it difficult to add other
> information about the contact. A better approach would have been to
> make the contact element a complex type, which would include an
> element called <uri> that contains the uri.
> 
> For example, today we have:
> 
> <?xml version="1.0"?>
>   <reginfo xmlns="urn:ietf:params:xml:ns:reginfo"
>                version="1" state="partial">
>     <registration aor="sip:joe@bar.com" id="a7" state="active">
>       <contact id="76" state="active" event="registered"
>                duration-registered="0">sip:joe@pc34.bar.com</contact>
>     </registration>
>   </reginfo>
> 
> whereas it ought to have been:
> 
> <?xml version="1.0"?>
>   <reginfo xmlns="urn:ietf:params:xml:ns:reginfo"
>                version="1" state="partial">
>     <registration aor="sip:joe@bar.com" id="a7" state="active">
>       <contact id="76" state="active" event="registered"
>                duration-registered="0">
>                   <uri>sip:joe@pc34.bar.com</uri>
>       </contact>
>     </registration>
>   </reginfo>
> 
> 
> The schema for the contact element could then allow for other children
> in other namespaces, giving us the needed extensibility.
> 
> Unfortunately, there is other per-contact data we might want to add in
> the not-too-distant future, such as callee-caps information. That kind
> of data would be very useful for presence applications, where the
> presence server could obtain it from the registrar using reg-event.
> 
> I believe that this problem is significant enough that we should try
> and address it during auth48. For those of you not familiar with it,
> auth48 is a brief period just before publication of the actual RFC
> where the author can correct typos or minor other problems. It is
> possible, with AD approval, to make more substantive changes as I am
> suggesting (and indeed I already ran this by Allison and she is OK).
> Of course, I still need group consensus on any change. So, here is my
> proposal.
> 
> PROPOSAL
> 
> My proposal for fixing this, as outlined above, is to modify the XML
> schema. The <contact> element will instead become a complex type. It
> will have, as children, a sequence of <uri> followed by an optional
> element from any other namespace. The <uri> element will contain the
> actual contact URI.
> 
> Unfortunately, this proposed solution above is not backwards
> compatible with the current draft.
> 
> I considered other solutions as well:
> 
> 
> ALTERNATE 1
> 
> Modify the schema to allow attributes in the contact element from
> other namespaces. Adds some extensibility, but is very bad for more
> complex data, such as path or callee-cap data. Using attributes for
> that data will require us to define a lot of structure within each
> attribute. This approach is backwards compatible, but not forwards
> compatible. That is, an implementation compliant to the schema before
> this change would reject documents created by an implementation
> compliant to the schema after the change.
> 
> ALTERNATE 2
> 
> Modify the schema to contain a new element, child to the
> <registration> element. This element would be called "alt-contact",
> and would be defined as I suggest above for contact. Whenever new
> information is needed about a contact, the "alt-contact" element would
> be present, and contain that extension data. The document would also
> still contain a contact element, repeating the URI and other
> attributes. This would provide forwards and backwards compatibility,
> at the expense of a horrible hack that would repeat a lot of
> information in the document.
> 
> 
> I found neither of the two alternatives very palatable, which is why
> my proposal is to fix this now, and do it properly, while we still can.
> 
> Please provide input on the proposal ASAP. I'd like to come to
> consensus in the next week or so (before everyone disappears for
> vacations).
> 
> Thanks,
> Jonathan R.


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



From exim@www1.ietf.org  Wed Dec 31 16:16:08 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25799
	for <sipping-archive@odin.ietf.org>; Wed, 31 Dec 2003 16:16:08 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Abngp-0003jV-Qv
	for sipping-archive@odin.ietf.org; Wed, 31 Dec 2003 16:15:39 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBVLFdJX014345
	for sipping-archive@odin.ietf.org; Wed, 31 Dec 2003 16:15:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Abngp-0003jI-Nt
	for sipping-web-archive@optimus.ietf.org; Wed, 31 Dec 2003 16:15:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25787
	for <sipping-web-archive@ietf.org>; Wed, 31 Dec 2003 16:15:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Abngi-00016S-00
	for sipping-web-archive@ietf.org; Wed, 31 Dec 2003 16:15:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Abncl-000122-00
	for sipping-web-archive@ietf.org; Wed, 31 Dec 2003 16:11:30 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbnYr-0000x7-00
	for sipping-web-archive@ietf.org; Wed, 31 Dec 2003 16:07:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbnYU-0003Eu-7i; Wed, 31 Dec 2003 16:07:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbnXy-0003EP-Mf
	for sipping@optimus.ietf.org; Wed, 31 Dec 2003 16:06:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25609
	for <sipping@ietf.org>; Wed, 31 Dec 2003 16:06:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbnXs-0000wp-00
	for sipping@ietf.org; Wed, 31 Dec 2003 16:06:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbnVD-0000sn-00
	for sipping@ietf.org; Wed, 31 Dec 2003 16:03:42 -0500
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbnRX-0000oR-00
	for sipping@ietf.org; Wed, 31 Dec 2003 15:59:51 -0500
Received: from dynamicsoft.com ([63.113.46.68])
	by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id hBVKxImR007925;
	Wed, 31 Dec 2003 15:59:19 -0500 (EST)
Message-ID: <3FF338A2.1030105@dynamicsoft.com>
Date: Wed, 31 Dec 2003 15:59:14 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
CC: sipping <sipping@ietf.org>
Subject: Re: [Sipping] Problem with reg-event that needs immediate fix
References: <BC16F709.2AD0D%fluffy@cisco.com>
In-Reply-To: <BC16F709.2AD0D%fluffy@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>,
	<mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



Cullen Jennings wrote:

> I would prefer to change the Schema to be right for this things we know are
> coming even if that broke backwards compatibility.

Great. I think we have consensus at this point to make the change 
during auth48.

> 
> The more I look at the schema, I think the whole the things could be
> structured a little better for extensibility. I had the same comment on some
> of the other schema that have been in sipish drafts. We should probably make
> this part of our NITS review.

Can you be more specific? Generally, you want to allow almost any 
element to have children from other namespaces. What else did you have 
in mind?

-Jonathan R.


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


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



