From sip-bounces@ietf.org  Wed Oct  1 04:05:46 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 526C13A6C3E;
	Wed,  1 Oct 2008 04:05:46 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C54943A6C3E
	for <sip@core3.amsl.com>; Wed,  1 Oct 2008 04:05:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id M5QIdaYeMRPQ for <sip@core3.amsl.com>;
	Wed,  1 Oct 2008 04:05:42 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id F151C3A685A
	for <sip@ietf.org>; Wed,  1 Oct 2008 04:05:41 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K8200299461CC@siemenscomms.co.uk> for sip@ietf.org; Wed,
	01 Oct 2008 12:06:01 +0100 (BST)
Date: Wed, 01 Oct 2008 12:06:00 +0100
From: "Elwell, John" <john.elwell@siemens.com>
To: sip@ietf.org
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D0011FF917@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: draft-elwell-sip-identity-handling-ua-00  posted
Thread-Index: AckjtbAaEnjIedcIT0GUum2UDEsc7w==
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Subject: [Sip] draft-elwell-sip-identity-handling-ua-00  posted
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This draft arose out of suggestions during SIP Identity discussions in
the SIP WG in Dublin that we should consider UA handling of received
identity information.
http://www.ietf.org/internet-drafts/draft-elwell-sip-identity-handling-u
a-00.txt

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


From sip-bounces@ietf.org  Wed Oct  1 05:41:47 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF3F73A6CA3;
	Wed,  1 Oct 2008 05:41:47 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EB3413A6CA1
	for <sip@core3.amsl.com>; Wed,  1 Oct 2008 05:41:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tdCXyDtznNPO for <sip@core3.amsl.com>;
	Wed,  1 Oct 2008 05:41:44 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 537B128C20E
	for <sip@ietf.org>; Wed,  1 Oct 2008 05:40:22 -0700 (PDT)
Received: from [75.68.119.237] (port=63577 helo=[192.168.15.103])
	by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1Kl100-0001W5-NO for sip@ietf.org; Wed, 01 Oct 2008 05:40:13 -0700
Message-Id: <9BCA68EB-2AF2-4F88-A595-B4CE1ED6475B@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: SIP IETF <sip@ietf.org>
In-Reply-To: <200809300309.m8U39jFX37113365@shell01.TheWorld.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 1 Oct 2008 08:40:11 -0400
References: <5D1A7985295922448D5550C94DE2918002196DCC@DEEXC1U01.de.lucent.com>	<48898492.7010601@ericsson.com>	<5D1A7985295922448D5550C94DE2918002196FF7@DEEXC1U01.de.lucent.com>	<4889F09B.8050407@cisco.com>
	<200809262108.m8QL8fpj34800452@shell01.TheWorld.com>
	<48E0F79B.8090402@cisco.com>
	<200809300309.m8U39jFX37113365@shell01.TheWorld.com>
X-Mailer: Apple Mail (2.929.2)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: Re: [Sip] Comments on draft-ietf-sip-body-handling-02
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2005369940=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--===============2005369940==
Content-Type: multipart/signed; boundary=Apple-Mail-30--255524001; micalg=sha1; protocol="application/pkcs7-signature"


--Apple-Mail-30--255524001
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Agreed. And, echoing what Keith said, what Dale has done is prove  
(from a Computer Science perspective) that complete evaluation of  
unfettered MIME is *possible*. It is up to the implementor to figure  
out whether they want to take short-cuts (and risk barfing on  
legitimate messages) or do the whole thing.

The point is doing the Full Monte *is* practical on small, memory and  
CPU constrained devices. So the argument "We can't do the real thing  
because it hurts" is provably not legitimate.

On Sep 29, 2008, at 11:09 PM, Dale.Worley@comcast.net wrote:

>   From: Paul Kyzivat <pkyzivat@cisco.com>
>
>   I agree it would be straightforward to define a rule that says one  
> must
>   recursively unwrap all multipart/mixed bodies in order to find other
>   parts to process. But we ought to think if we really want to do  
> that.
>
> What alternative rule do you propose as the meaning of
> multipart/mixed?
>
>   Potentially this could introduce a lot of extra processing.
>
> That's sort of like saying that "x = 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0"
> involves a lot of extra processing.  Yes, it does.  But it meaning is
> clear, once we define what "+" means.  We could try to outlaw that
> expression and "expressions like it", but there's no sensible boundary
> to enforce -- Do we ban expressions with more than five addends?  How
> about more than one addend which is "0"?  Any possible solution to
> this problem is worse than the problem itself.
>
> What I am advocating is that we explicitly abandon the attempt to
> define only the situations that intuitively make sense, and instead
> define a set of simple, well-defined rules that make clear what is
> valid and what is not, and what the valid cases mean.  Just like we've
> done with arithmetic expressions.  Otherwise we'll never escape the
> swamp of trying to discern which ones make intuitive sense.
>
>   From: Paul Kyzivat <pkyzivat@cisco.com>
>
>> RFC 3459 uses multiparts in a somewhat different way that SIP does.
>> In SIP, the I-D suggests that components of a multipart/alternative
>> should have handling=optional and that the processor should ignore  
>> the
>> handling parameter:
>>
>> 	The UA SHOULD also set the 'handling' parameter of all the
>> 	body part within the 'multipart/alternative' to 'optional'
>> 	(the receiver will process the body parts based on the
>> 	handling parameter of the 'multipart/alternative' body; the
>> 	receiver will ignore the handling parameters of the body
>> 	parts).
>>
>> 	The receiver SHOULD ignore the handling parameters of the body
>> 	parts within the 'multipart/ alternative'.
>
>   Right. But the SHOULD without qualification suggests that somebody  
> might
>   do otherwise, and we don't know under what circumstances that might
>   happen. So if somebody sets all the parts to handling=required, it  
> seems
>   that the handling of the unselected parts will still be ignored.
>
> Yes, I see the problem there.  I'd replace that last SHOULD with MUST.
> Actually, I argue that MUST is implied, as the RFCs define how
> multipart/alternative is to be processed, and that algorithm does not
> look at the handling parameters of components of
> multipart/alternatives.
>
>   Suppose I want to send a MESSAGE, and I require that some form of  
> the
>   body be processed. I will offer it in two forms: text/enhanced and
>   text/html. How do I encode that?
>
> 	   C-T: multipart/alternative
> 	   C-D: render;handling=required
> 		   C-T: text/enhanced
> 		   C-D: render;handling=optional
> 		   ===
> 		   C-T: text/html
> 		   C-D: render;handling=optional
>   or
> 	   C-T: multipart/alternative
> 	   C-D: render;handling=required
> 		   C-T: text/enhanced
> 		   C-D: render;handling=required
> 		   ===
> 		   C-T: text/html
> 		   C-D: render;handling=required
>
> C-T: multipart/alternative
> C-D: render;handling=required
> 	C-T: text/enhanced
> 	===
> 	C-T: text/html
>
> 'render' is inherited from the parent, and the handling of the
> components is ignored.  We could also take it that MESSAGE implies
> that the body is 'required', so the handling specification of the
> parent is also optional.
>
>   And if I don't support either of those text types, what error do I
>   return? 415? In the first case it seems a little odd to return an  
> error
>   if I selected a part that is optional.
>
> 415.  The I-D is clear that 415 is how you respond to messages which
> are not processable due to a failure of these MIME tests.
>
>   And if I didn't require either part to be understood, would I just
>   change to handling=optional for the multipart/alternative itself?
>
> Intuitively, I'd say that MESSAGE demands that the entire body be
> processable, so handling=required is implicit for the entire body.
> But assuming that we did not make such a deduction from the SIP
> context of the message, if the body had handling=optional, it would
> have the effect that the request could succeed even if the requester
> did not understand the body.  (Hmmm...  That's another clause of the
> algorithm I overlooked.)
>
> (Note that there are cases where understanding the body is optional.
> E.g., a sipfrag of the request in a failure response.)
>
> Dale
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip


--Apple-Mail-30--255524001
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGPTCCBjkw
ggUhoAMCAQICEC+VK1RLWxrF8KJZDR9k8p8wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYTAlVT
MQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VS
VFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQD
Ey1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwwHhcNMDgwODEz
MDAwMDAwWhcNMDkwODEzMjM1OTU5WjCB4TE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsg
LSBQRVJTT05BIE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9m
IHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDMg
Q29tb2RvIExpbWl0ZWQxFDASBgNVBAMTC0VyaWMgQnVyZ2VyMSkwJwYJKoZIhvcNAQkBFhplYnVy
Z2VyQHN0YW5kYXJkc3RyYWNrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMTF
RRoA4LgOACMFph0aomRC/UpqoA5C/d6DUTOvTMrYSEqkjwnU4zxDtBcHlcB4AxKAov00MYsUvEU4
loz7BHjfDjv76AIkcwu33VYQbzGmarVnyaXsVb6f/cyRL3fPT0VOVO2tQAEEgwg//CX0jN8Kn2jH
uXD/HEvko7cmpL3Pwevf3+DwB61v7ca79PpEZfn/WhaqRKA4uVNPj/JbieeaLo2v/0RJzrEElZK0
pHCqxiD3mQ8ossPkA9fUCSxLlbdMcPU3be5x8vt8Q8mYTXF5Z3d9RZmYrmNkvTQtdzVpfYWr/hgV
Xqm9tByOOAR+hoN3FKbubR/OrAHL9yDAd4sCAwEAAaOCAhwwggIYMB8GA1UdIwQYMBaAFImCZ33E
nSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBRDWgutb7b8R/L7G3Y3D+molAA3VzAOBgNVHQ8BAf8E
BAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJ
YIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEW
HWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMIGlBgNVHR8EgZ0wgZowTKBKoEiGRmh0dHA6
Ly9jcmwuY29tb2RvY2EuY29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRF
bWFpbC5jcmwwSqBIoEaGRGh0dHA6Ly9jcmwuY29tb2RvLm5ldC9VVE4tVVNFUkZpcnN0LUNsaWVu
dEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMGwGCCsGAQUFBwEBBGAwXjA2BggrBgEFBQcwAoYq
aHR0cDovL2NydC5jb21vZG9jYS5jb20vVVROQUFBQ2xpZW50Q0EuY3J0MCQGCCsGAQUFBzABhhho
dHRwOi8vb2NzcC5jb21vZG9jYS5jb20wJQYDVR0RBB4wHIEaZWJ1cmdlckBzdGFuZGFyZHN0cmFj
ay5jb20wDQYJKoZIhvcNAQEFBQADggEBAGeBR7NPCvrY3GQoIi49JOuciatY2r4st905Jw1etp6J
umFFWlaCBl11tFSclk/3S45B+lUv3SEvG4CEjUByPScprVmCqHR+y8BAQaB/CV+N1y14x3MbhJ+Z
8XDGKeUXuuyGd9w0l3/t/QPid6TRXQjQFrLPFs1IALuNpNiFMHEF/xFbMG1Z2vznR/gSPlePekoZ
TqcExIDBNZTBebpZqwAXzPpedNNOclbMLFLWDMOAozVRpkfjI0eiFsk8SF1Ho1Gb9Bx8DeG4peE2
KRVOR9FFnZZgBpFjXYRcglsMOSKCY8HgE+NGvbbqbrMoBV/BlYyxRXwfti71RL9Zs2Cq1eQxggP8
MIID+AIBATCBwzCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExh
a2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8v
d3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkNH2TynzAJBgUrDgMCGgUAoIICDTAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wODEwMDExMjQwMTJaMCMGCSqGSIb3
DQEJBDEWBBQAn547fM4AgsfavXbhKllc/Rw6WTCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD
VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU
aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2
MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv
lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN
H2TynzANBgkqhkiG9w0BAQEFAASCAQCV/EQc8tuyP9jgiBBFzCvC7I1RlC+7lnDHM7jB1ggW070z
eb+G3KGh1Su/pQlqZAJ3FuosErbmQn52SlQ2IuLWky9BQCtFKCULZ0N4SdunIIcpnO6wtGj2loi8
b46lrzrsixlk3jZGoBQ8HA253ki/099RMbqKg+HQJ642biuSqqb3YKdvK2S+wrdGqqwQzDDKFGEV
I2KX4OGpVKwh/XjPN5WviAnlfLIwPckobij2irI5azxpsYBQM9e2tmOZV96ahc1Ok2vnmAMzITMv
t3cNIvmzjg2wxkJI6WVnwd/XJEPSblMgqPxhMHzRUs17J4Y/N184FHVDaQP5UvhvM3XXAAAAAAAA

--Apple-Mail-30--255524001--

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

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


From sip-bounces@ietf.org  Wed Oct  1 08:01:23 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 12F0528C1E6;
	Wed,  1 Oct 2008 08:01:23 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 68FD43A6C3B
	for <sip@core3.amsl.com>; Wed,  1 Oct 2008 08:01:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.38
X-Spam-Level: 
X-Spam-Status: No, score=-6.38 tagged_above=-999 required=5 tests=[AWL=0.219, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FlnMISHeum3u for <sip@core3.amsl.com>;
	Wed,  1 Oct 2008 08:01:20 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 1BC5A28C23E
	for <sip@ietf.org>; Wed,  1 Oct 2008 08:00:40 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,344,1220227200"; d="scan'208";a="22880900"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 01 Oct 2008 15:01:00 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m91F1073022298; 
	Wed, 1 Oct 2008 11:01:00 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m91F0wpe023125;
	Wed, 1 Oct 2008 15:01:00 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 11:00:58 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 11:00:58 -0400
Message-ID: <48E390AC.5080109@cisco.com>
Date: Wed, 01 Oct 2008 11:01:00 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens.com>
References: <0D5F89FAC29E2C41B98A6A762007F5D0011FF917@GBNTHT12009MSX.gb002.siemens.net>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D0011FF917@GBNTHT12009MSX.gb002.siemens.net>
X-OriginalArrivalTime: 01 Oct 2008 15:00:58.0834 (UTC)
	FILETIME=[8339B320:01C923D6]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3069; t=1222873260;
	x=1223737260; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-elwell-sip-identity-handl
	ing-ua-00=20=20posted |Sender:=20
	|To:=20=22Elwell,=20John=22=20<john.elwell@siemens.com>;
	bh=cZETTeirHDYsfuQzeyIIHSdfWgsuRm2spfUPXTVxbwU=;
	b=EO9kshdYoIvlRws8p0MME46wYnHTu8uI8wjWzdRKHFnAJbtJlvgBhPEytz
	9o79wFKXum4V6P2qgLS8ISioDf668nGq22cjJNqvPhpzPhzzh7GpPpufXXFp
	1k1JGD5vNs;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: sip@ietf.org
Subject: Re: [Sip] draft-elwell-sip-identity-handling-ua-00  posted
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

John,

I really like this document! I think it is important.

A few comments:

    Furthermore, although a P-Asserted-Identity header field can contain
    a display-name, the assertion strictly speaking covers only the URI,
    and therefore the display-name is even less trustworthy than the URI.
...
    If a display-name is received, the general advice is not to present
    it to the user.  Presenting an authenticated identifier along with an
    unauthenticated display-name would be misleading.  A preferred
    solution is to obtain a name by phone-book look-up, based on the
    received authenticated identifier, and present that.  If an
    unauthenticated identifier is presented (and indicated as not to be
    trusted), little additional harm would arise from also presenting the
    display-name.

In services that are providing traditional telephony services, 
calling-name is often an important feature. When the services are 
provided via sip, the display name seems to be the only obvious choice 
for conveying calling-name to the callee.

A provider that needs to do this *can* police the use of display-name in 
 From and/or manage its use of display-name in P-Asserted-Identity. In 
such an environment, the display-name could be trusted by the UAS to the 
same extent that the rest of the identity is.

If there is an alternative source of info, such as a local phone book 
with a matching entry, then it would seem good to prefer that. If there 
is no alternative source, and the display-name is not trusted, then it 
may still be better to display it than not. Especially if some 
indication of distrust can be rendered with it.

    When a UA receives more than one caller identifier, the choice of
    which one to present to the user will be influenced by
    trustworthiness.  Generally the most trustworthy should be chosen.
    When two of equal trust are received (e.g., a TEL URI and a SIP URI
    in the P-Asserted-Identity header field), there may be grounds for
    presenting each (or elements of each), if this is possible, because
    either or both could be of use to the user.

Another consideration is the context in which the identifier is 
displayed. In some cases the display is predicated on the identity being 
a number. In such a case there will be a bias towards displaying either 
a type 1 address or the user portion of a type 2 address.

	Thanks,
	Paul

Elwell, John wrote:
> This draft arose out of suggestions during SIP Identity discussions in
> the SIP WG in Dublin that we should consider UA handling of received
> identity information.
> http://www.ietf.org/internet-drafts/draft-elwell-sip-identity-handling-u
> a-00.txt
> 
> John
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct  1 08:29:17 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1B9A228C211;
	Wed,  1 Oct 2008 08:29:17 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 032C628C211
	for <sip@core3.amsl.com>; Wed,  1 Oct 2008 08:29:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vJ4Nmj6gNor8 for <sip@core3.amsl.com>;
	Wed,  1 Oct 2008 08:29:13 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id 705623A68E6
	for <sip@ietf.org>; Wed,  1 Oct 2008 08:29:13 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K8200IB7G5YDF@siemenscomms.co.uk> for sip@ietf.org; Wed,
	01 Oct 2008 16:28:58 +0100 (BST)
Date: Wed, 01 Oct 2008 16:28:15 +0100
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <48E390AC.5080109@cisco.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D00123031A@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] draft-elwell-sip-identity-handling-ua-00  posted
Thread-Index: Ackj1tigxY3Wol+XSYWrDfKuAKPr6QAA2COw
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <0D5F89FAC29E2C41B98A6A762007F5D0011FF917@GBNTHT12009MSX.gb002.siemens.net>
	<48E390AC.5080109@cisco.com>
Cc: sip@ietf.org
Subject: Re: [Sip] draft-elwell-sip-identity-handling-ua-00  posted
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Paul,

Thanks for your early read of this draft. Points taken.

John 

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Paul Kyzivat
> Sent: 01 October 2008 16:01
> To: Elwell, John
> Cc: sip@ietf.org
> Subject: Re: [Sip] draft-elwell-sip-identity-handling-ua-00 posted
> 
> John,
> 
> I really like this document! I think it is important.
> 
> A few comments:
> 
>     Furthermore, although a P-Asserted-Identity header field 
> can contain
>     a display-name, the assertion strictly speaking covers 
> only the URI,
>     and therefore the display-name is even less trustworthy 
> than the URI.
> ...
>     If a display-name is received, the general advice is not 
> to present
>     it to the user.  Presenting an authenticated identifier 
> along with an
>     unauthenticated display-name would be misleading.  A preferred
>     solution is to obtain a name by phone-book look-up, based on the
>     received authenticated identifier, and present that.  If an
>     unauthenticated identifier is presented (and indicated as 
> not to be
>     trusted), little additional harm would arise from also 
> presenting the
>     display-name.
> 
> In services that are providing traditional telephony services, 
> calling-name is often an important feature. When the services are 
> provided via sip, the display name seems to be the only 
> obvious choice 
> for conveying calling-name to the callee.
> 
> A provider that needs to do this *can* police the use of 
> display-name in 
>  From and/or manage its use of display-name in 
> P-Asserted-Identity. In 
> such an environment, the display-name could be trusted by the 
> UAS to the 
> same extent that the rest of the identity is.
> 
> If there is an alternative source of info, such as a local phone book 
> with a matching entry, then it would seem good to prefer 
> that. If there 
> is no alternative source, and the display-name is not 
> trusted, then it 
> may still be better to display it than not. Especially if some 
> indication of distrust can be rendered with it.
> 
>     When a UA receives more than one caller identifier, the choice of
>     which one to present to the user will be influenced by
>     trustworthiness.  Generally the most trustworthy should be chosen.
>     When two of equal trust are received (e.g., a TEL URI and 
> a SIP URI
>     in the P-Asserted-Identity header field), there may be grounds for
>     presenting each (or elements of each), if this is 
> possible, because
>     either or both could be of use to the user.
> 
> Another consideration is the context in which the identifier is 
> displayed. In some cases the display is predicated on the 
> identity being 
> a number. In such a case there will be a bias towards 
> displaying either 
> a type 1 address or the user portion of a type 2 address.
> 
> 	Thanks,
> 	Paul
> 
> Elwell, John wrote:
> > This draft arose out of suggestions during SIP Identity 
> discussions in
> > the SIP WG in Dublin that we should consider UA handling of received
> > identity information.
> > 
> http://www.ietf.org/internet-drafts/draft-elwell-sip-identity-
> handling-u
> > a-00.txt
> > 
> > John
> > _______________________________________________
> > Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sipping@ietf.org for new developments on the application of sip
> > 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct  1 09:42:21 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1E4593A6ABB;
	Wed,  1 Oct 2008 09:42:21 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 68B0E3A6ABB
	for <sip@core3.amsl.com>; Wed,  1 Oct 2008 09:42:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.805
X-Spam-Level: 
X-Spam-Status: No, score=-5.805 tagged_above=-999 required=5
	tests=[AWL=-0.406, BAYES_00=-2.599, J_CHICKENPOX_14=0.6,
	J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id e4y0ZuGS-S+r for <sip@core3.amsl.com>;
	Wed,  1 Oct 2008 09:42:18 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 1BBD23A6916
	for <sip@ietf.org>; Wed,  1 Oct 2008 09:42:17 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,344,1220227200"; d="scan'208";a="22892358"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 01 Oct 2008 16:42:35 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m91GgZ2e009762; 
	Wed, 1 Oct 2008 12:42:35 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m91GgZBg026589;
	Wed, 1 Oct 2008 16:42:35 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 12:42:35 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 12:42:34 -0400
Message-ID: <48E3A87E.9060201@cisco.com>
Date: Wed, 01 Oct 2008 12:42:38 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
References: <200809300309.m8U39wbI37097791@shell01.TheWorld.com>	<48E22F32.8050202@cisco.com>
	<5D1A7985295922448D5550C94DE2918002361364@DEEXC1U01.de.lucent.com>
In-Reply-To: <5D1A7985295922448D5550C94DE2918002361364@DEEXC1U01.de.lucent.com>
X-OriginalArrivalTime: 01 Oct 2008 16:42:34.0813 (UTC)
	FILETIME=[B4B646D0:01C923E4]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=15057; t=1222879355;
	x=1223743355; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Is=20body=20handling=20NP-compl
	ete? |Sender:=20
	|To:=20=22DRAGE,=20Keith=20\(Keith\)=22=20<drage@alcatel-lu
	cent.com>; bh=3bvE6rV3k4+3KUMKJ4NLroT0BIdpLsvhcNjm+U1CNhQ=;
	b=erpscKNx3omNmVqKtYLSruaPlmXAl1KlJ68yujYXJDbCMGDeaoXlSfE/se
	5YtUrN+gGpqst/7rtnmdzNEeftbH32BduN7zz7g4fkgUdd0YTWh6ugjeZs3d
	Sska16Or+I;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: sip@ietf.org
Subject: Re: [Sip] Is body handling NP-complete?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I think I would prefer a declarative specification of body handling as 
the normative part. But if we have a good processing algorithm to show, 
I would like to see it included, perhaps as a non-normative appendix. 
Its a good demonstration that the declarative spec is self consistent, 
and it gives developers a good starting point.

	Thanks,
	Paul

DRAGE, Keith (Keith) wrote:
> I would note that if this does end up in the specification, it can carry
> a rider that implementations should exhibit behaviour as demonstrated by
> the algorithm, not that they need to implement the algorithm itself. 
> 
> However I leave it to the working group to ascertain whether they prefer
> this as a means of specification.
> 
> Regards
> 
> Keith
> 
>> -----Original Message-----
>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
>> Behalf Of Paul Kyzivat
>> Sent: Tuesday, September 30, 2008 2:53 PM
>> To: Dale.Worley@comcast.net
>> Cc: sip@ietf.org
>> Subject: Re: [Sip] Is body handling NP-complete?
>>
>> Dale,
>>
>> I like the thorough treatment. It seems plausible to me.
>>
>> One implication of this is that body parts need to be 
>> processed twice in a content-type+content-disposition+context 
>> dependent way: once to extract references, and again for 
>> final effect. (Hmm - is extracting of references dependent on 
>> the disposition and context?)
>>
>> If you imagine that various content types are handled by 
>> plugins, then the plugins will each require two entry points 
>> - one for each of these processing modes. While that is 
>> certainly possible, it might mean that plugins that already 
>> exist for non-sip applications (e.g. email or html) may not 
>> be reusable for sip. (I am not familiar with the content-type 
>> plugins for other protocols such as email. But I presume that 
>> email plugins may be useful in some cases, at least for MESSAGE.)
>>
>> Do plugins for email have this complexity?
>>
>> An alternative is to do all the processing in one pass, and 
>> then at the end check if all body parts have been processed. 
>> BUT that means all the side effects of processing will have 
>> been realized before discovering that the message is in 
>> error. That is certainly not ideal.
>>
>>> This example also points out that the requirement that references 
>>> appear before the parts they reference is needed to make 
>> the problem 
>>> tractable.  Otherwise, there could be circular dependencies between 
>>> the choices for different multipart/alternatives, which might be 
>>> impossible to analyze by an algorithm as simple as a tree-walk.
>> This requirement is satisfied by lots of simple cases. But it 
>> means that it is impossible to describe any kind of circular 
>> structure. I'm not familiar enough with the use of 
>> multipart/related to know if it is a restriction that is 
>> tolerable there. Perhaps someone can comment on that.
>>
>> 	Thanks,
>> 	Paul
>>
>> Dale.Worley@comcast.net wrote:
>>> Referring back to last March, in
>>>
>> http://www.ietf.org/mail-archive/web/sip/current/msg22426.html, I was 
>>> contemplating whether the rules for testing a message body required 
>>> searching through combinations of choices regarding which 
>> alternatives 
>>> of multipart/alternatives are chosen.  As I then conceptualized the 
>>> problem, the question was "Is there a choice of 
>> alternatives such that 
>>> all the constraints for 'successful processing' can be 
>> met?"  It turns 
>>> out that if you phrase the question that way, the problem is 
>>> NP-complete, which means in practice that any algorithm to solve it 
>>> must do backtracking.
>>>
>>> The new formulation of the problem attempts to avoid this 
>> by dividing 
>>> the problem into three phases:  (1) assemble a tree which 
>> represents 
>>> the dependencies of super-parts' being processable upon that of 
>>> sub-parts, (2) walk the tree, tagging parts from the bottom 
>> up as to 
>>> whether they are processable, (3) if the overall tree is 
>> processable, 
>>> selecting for processing the correct subset of parts as directed by 
>>> the tags in the tree.  As long as the size of the tree is 
>> commensurate 
>>> with the number of body parts, the algorithm is inherently 
>> linear, and 
>>> clearly it doesn't involve backtracking.
>>>
>>> In regard to step (1), the tree is assembled:
>>>
>>> - the root node represents the message body
>>> - a node for a multipart/alternative part has one child for each
>>>   component
>>> - a node for a multipart/mixed part has one child for each
>>>   component
>>> - a note for a multipart/related part is not automatically given
>>>   children for its components
>>> - a header in a part that refers to another component generates a
>>>   child of that part that represents the referred-to component
>>> - similarly, a reference within a part that refers to another
>>>   component generates a child of that part that represents the
>>>   referred-to component (This is how multipart/related nodes get
>>>   children.)
>>>
>>> Of course, if a component is referred to multiple times, 
>> the component 
>>> is represented by multiple nodes in the tree, one node for 
>> each of its 
>>> roles.
>>>
>>> However, there are subtleties I might be overlooking, so I 
>> am going to 
>>> revisit the embedding of the NP-complete problem "3-satisfiability"
>>> into MIME to see what it reveals about my sketch of an algorithm.
>>>
>>> Referring to the previous message:
>>>
>>>     The reduction is as follows:
>>>
>>>     http://en.wikipedia.org/wiki/NP-complete
>>>     http://en.wikipedia.org/wiki/Reduction_%28complexity%29
>>>     http://en.wikipedia.org/wiki/3-satisfiability#3-satisfiability
>>>
>>>     Choose an instance of the 3-satisfiability problem, 
>> that is: a set of
>>>     boolean variables A, B, C, etc. and a formula composed of:
>>> 	    a series of "clauses" joined by AND, consisting of
>>> 		    a series of variables and their negations 
>> joined by OR.
>>>     The problem is to determine if there is any assignment 
>> of truth values
>>>     to the variables which makes the formula true, that is, 
>> which makes
>>>     true one of the variables or negations in each of the clauses.
>>>
>>>     For example, choose 4 variables A, B, C, and D, and the formula
>>>
>>>     (A OR B OR C) AND (B OR NOT-C OR D) AND (NOT-A OR NOT-B 
>> OR NOT-D)
>>>     This can be satisfied by setting A=TRUE, B=FALSE, 
>> C=TRUE, and D=FALSE.
>>>     Construct a multipart/mixed with each component labeled
>>>     handling=required.  Within that, for each variable, 
>> have a part which
>>>     is multipart/alternate with 2 parts.  If processing 
>> chooses the first
>>>     part of the part corresponding to a variable, that will 
>> model the
>>>     variable being TRUE.  If processing chooses the second 
>> part of the
>>>     part corresponding to a variable, that will model the 
>> variable being
>>>     FALSE.
>>>
>>>     For example, our body starts:
>>>
>>> 	    multipart/mixed
>>> 		    multipart/alternative;handling=required
>>> 			    first part corresponding to A (not 
>> yet specified)
>>> 			    second part corresponding to NOT-A
>>> 		    multipart/alternative;handling=required
>>> 			    first part corresponding to B
>>> 			    second part corresponding to NOT-B
>>> 		    multipart/alternative;handling=required
>>> 			    first part corresponding to C
>>> 			    second part corresponding to NOT-C
>>> 		    multipart/alternative;handling=required
>>> 			    first part corresponding to D
>>> 			    second part corresponding to NOT-D
>>>
>>>     For each clause of the formula, add an additional body 
>> part, marked
>>>     "Content-Disposition: by-reference; handling=required". 
>>  Give the part
>>>     a 'cid' URL.  The ability of the recipient to 
>> successfully process
>>>     this part will model making the corresponding clause TRUE.
>>>
>>>     For example, our body is now:
>>>
>>> 	    multipart/mixed
>>> 		    multipart/alternative;handling=required
>>> 			    first part corresponding to A (not 
>> yet specified)
>>> 			    second part corresponding to NOT-A
>>> 		    multipart/alternative;handling=required
>>> 			    first part corresponding to B
>>> 			    second part corresponding to NOT-B
>>> 		    multipart/alternative;handling=required
>>> 			    first part corresponding to C
>>> 			    second part corresponding to NOT-C
>>> 		    multipart/alternative;handling=required
>>> 			    first part corresponding to D
>>> 			    second part corresponding to NOT-D
>>> 		    part (not otherwise 
>> specified);by-reference;handling=required;cid=clause1
>>> 		    part (not otherwise 
>> specified);by-reference;handling=required;cid=clause2
>>> 		    part (not otherwise 
>>> specified);by-reference;handling=required;cid=clause3
>>>
>>>     We now want to arrange things so that one of the last 3 
>> parts can be
>>>     successfully processed only if we choose for processing 
>> one of the
>>>     earlier parts that corresponds to a variable value that 
>> will make the
>>>     corresponding clause true.  This is done by embedding forward
>>>     references in the variable-corresponding parts that refer to the
>>>     clause-corresponding parts.
>>>
>>>     For example:
>>>
>>>  1	    multipart/mixed
>>>  2		    multipart/alternative;handling=required
>>>  3			    first part corresponding to A
>>> 				    references cid:clause1
>>>  4			    second part corresponding to NOT-A
>>> 				    references cid:clause3
>>>  5		    multipart/alternative;handling=required
>>>  6			    first part corresponding to B
>>> 				    references cid:clause1
>>> 				    references cid:clause2
>>>  7			    second part corresponding to NOT-B
>>> 				    references cid:clause3
>>>  8		    multipart/alternative;handling=required
>>>  9			    first part corresponding to C
>>> 				    references cid:clause1
>>> 10			    second part corresponding to NOT-C
>>> 				    references cid:clause2
>>> 11		    multipart/alternative;handling=required
>>> 12			    first part corresponding to D
>>> 				    references cid:clause2
>>> 13			    second part corresponding to NOT-D
>>> 				    references cid:clause3
>>> 14		    part;by-reference;handling=required;cid=clause1
>>> 15		    part;by-reference;handling=required;cid=clause2
>>> 16		    part;by-reference;handling=required;cid=clause3
>>>
>>>     In order to process this body, the recipient must 
>> choose exactly one
>>>     of each pair of bodies in the multipart/alternative 
>> body parts.  This
>>>     choice is equivalent to choosing a set of values for 
>> the variables.
>>>     The references embedded in the chosen parts refer to 
>> the body parts
>>>     that correspond to the clauses which are made true by the
>>>     corresponding variable's value.  In order to 
>> successfully process the
>>>     final body parts, the recipient must have chosen a set 
>> of variable
>>>     values that makes all of the clauses true.
>>>
>>> The resulting tree is:
>>>
>>> 	1 -+- 2 --+- 3 ---- 14
>>> 	   |      |
>>> 	   |      +- 4 ---- 16
>>> 	   |
>>> 	   +- 5 --+- 6 --+- 14
>>> 	   |      |      |
>>> 	   |      |      +- 15
>>> 	   |      |
>>> 	   |      +- 7 ---- 16
>>> 	   |
>>> 	   +- 8 --+- 9 ---- 14
>>> 	   |      |
>>> 	   |      +- 10 --- 15
>>> 	   |
>>> 	   +- 11 -+- 12 --- 15
>>> 	   |      |
>>> 	   |      +- 13 --- 16
>>> 	   |
>>> 	   +- 14
>>> 	   |
>>> 	   +- 15
>>> 	   |
>>> 	   +- 16
>>>
>>> Though the number of nodes is greater than the number of 
>> body parts, 
>>> it's limited approximately by the number of appearances of 
>> variables 
>>> in the original boolean formula, so it's linear in the 
>> number of body 
>>> parts.  So in building the tree, we don't have exponential effort.
>>>
>>> In the new approach, we walk the tree, tagging each node as 
>> to whether 
>>> it is processable.  In the above model, we assume that all 
>> the simple 
>>> parts are processable, so all nodes labeled 2 through 16 are marked 
>>> processable.  And as we tag the nodes for processability, we choose 
>>> for each multipart/alternative node which child will be processed 
>>> (namely, the last child that is processable).  In this tree, the 
>>> choices are 2 -> 4, 5 -> 7, 8 -> 10, and 11 -> 13.
>>>
>>> Where things get interesting is deciding if node 1 is processable.
>>> All of its children are processable, of course.  But the 
>> crux of the 
>>> construction is how the "by-reference;handling=required" 
>> constraints 
>>> on nodes 14, 15, and 16 are handled.  In this algorithm, we check 
>>> whether each part is referenced by a part that will be processed.
>>> Fortunately, all references to these nodes must have been 
>> tree-walked 
>>> before node 1 is examined, so can determine unambiguously 
>> whether used 
>>> references point to those nodes.  In this case, we have chosen to 
>>> process 2, 4, 5, 7, 8, 10, 11, and 13, which means that 
>> there are used 
>>> references to 16, 16, 15, and 16.  This leaves 17 
>> unreferenced, and so 
>>> node 1 is determined to be unprocessable.
>>>
>>> Note that the new algorithm avoids being NP-complete essentially by 
>>> making choices as soon as they are seen.  In this model, 
>> values NOT-A, 
>>> NOT-B, NOT-C, and NOT-D are chosen outright.  Since the example 
>>> formula is not satisfied, the body that encodes it is not 
>> processable.
>>> This example also points out that the requirement that references 
>>> appear before the parts they reference is needed to make 
>> the problem 
>>> tractable.  Otherwise, there could be circular dependencies between 
>>> the choices for different multipart/alternatives, which might be 
>>> impossible to analyze by an algorithm as simple as a tree-walk.
>>>
>>> Dale
>>> _______________________________________________
>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>> This list is for NEW development of the core SIP Protocol Use 
>>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>>> sipping@ietf.org for new developments on the application of sip
>>>
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol Use 
>> sip-implementors@cs.columbia.edu for questions on current sip 
>> Use sipping@ietf.org for new developments on the application of sip
>>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct  1 09:51:00 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1CC8D3A6909;
	Wed,  1 Oct 2008 09:51:00 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B733E3A686C
	for <sip@core3.amsl.com>; Wed,  1 Oct 2008 09:50:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.364
X-Spam-Level: 
X-Spam-Status: No, score=-6.364 tagged_above=-999 required=5 tests=[AWL=0.235, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9za78MXy24bI for <sip@core3.amsl.com>;
	Wed,  1 Oct 2008 09:50:57 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 288833A6898
	for <sip@ietf.org>; Wed,  1 Oct 2008 09:50:57 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,344,1220227200"; d="scan'208";a="22893339"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 01 Oct 2008 16:51:12 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m91GpC1K014114; 
	Wed, 1 Oct 2008 12:51:12 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m91GpC0a029246;
	Wed, 1 Oct 2008 16:51:12 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 12:51:12 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 1 Oct 2008 12:51:11 -0400
Message-ID: <48E3AA84.6010808@cisco.com>
Date: Wed, 01 Oct 2008 12:51:16 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Eric Burger <eburger@standardstrack.com>
References: <5D1A7985295922448D5550C94DE2918002196DCC@DEEXC1U01.de.lucent.com>	<48898492.7010601@ericsson.com>	<5D1A7985295922448D5550C94DE2918002196FF7@DEEXC1U01.de.lucent.com>	<4889F09B.8050407@cisco.com>	<200809262108.m8QL8fpj34800452@shell01.TheWorld.com>	<48E0F79B.8090402@cisco.com>	<200809300309.m8U39jFX37113365@shell01.TheWorld.com>
	<9BCA68EB-2AF2-4F88-A595-B4CE1ED6475B@standardstrack.com>
In-Reply-To: <9BCA68EB-2AF2-4F88-A595-B4CE1ED6475B@standardstrack.com>
X-OriginalArrivalTime: 01 Oct 2008 16:51:11.0769 (UTC)
	FILETIME=[E8D78090:01C923E5]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=7040; t=1222879872;
	x=1223743872; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Comments=20on=20draft-ietf-sip-
	body-handling-02 |Sender:=20
	|To:=20Eric=20Burger=20<eburger@standardstrack.com>;
	bh=O8DV1iwYehC6OPOB8+PM1jxA5WFSwBJxGE3UpVLTYOI=;
	b=k8xl2ZptecntKreE+YPocC51s5ecqyfMEsonPD0TagFhBvADsiQINbKufH
	pnf+VMhYMOZREoYqdGwOp0GPlxVcK5eGRdK53/COfhf0f6Kg/i9RzHZQxJyS
	ry6yViL7Vc;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Comments on draft-ietf-sip-body-handling-02
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Ok, ok, UNCLE!!!

I'd still like to know if email clients need to do this two pass 
approach - first searching for all the references to determine if all 
the handling requirements can be met, and then actually doing the 
processing of the referenced parts?

Also, it *is* legal for proxies to process bodies. But its obviously not 
required (by the protocol) for them to do so. Do we have a clue how the 
handling parameter applies to proxies? I assume in effect they can just 
ignore it and consider handling to be optional for all parts. Also, I 
presume a proxy that cares about body parts might want to investigate 
all the alternatives of a multipart/alternative, since it can't know 
which one the recipient will choose.

	Thanks,
	Paul

Eric Burger wrote:
> Agreed. And, echoing what Keith said, what Dale has done is prove (from 
> a Computer Science perspective) that complete evaluation of unfettered 
> MIME is *possible*. It is up to the implementor to figure out whether 
> they want to take short-cuts (and risk barfing on legitimate messages) 
> or do the whole thing.
> 
> The point is doing the Full Monte *is* practical on small, memory and 
> CPU constrained devices. So the argument "We can't do the real thing 
> because it hurts" is provably not legitimate.
> 
> On Sep 29, 2008, at 11:09 PM, Dale.Worley@comcast.net wrote:
> 
>>   From: Paul Kyzivat <pkyzivat@cisco.com>
>>
>>   I agree it would be straightforward to define a rule that says one must
>>   recursively unwrap all multipart/mixed bodies in order to find other
>>   parts to process. But we ought to think if we really want to do that.
>>
>> What alternative rule do you propose as the meaning of
>> multipart/mixed?
>>
>>   Potentially this could introduce a lot of extra processing.
>>
>> That's sort of like saying that "x = 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0"
>> involves a lot of extra processing.  Yes, it does.  But it meaning is
>> clear, once we define what "+" means.  We could try to outlaw that
>> expression and "expressions like it", but there's no sensible boundary
>> to enforce -- Do we ban expressions with more than five addends?  How
>> about more than one addend which is "0"?  Any possible solution to
>> this problem is worse than the problem itself.
>>
>> What I am advocating is that we explicitly abandon the attempt to
>> define only the situations that intuitively make sense, and instead
>> define a set of simple, well-defined rules that make clear what is
>> valid and what is not, and what the valid cases mean.  Just like we've
>> done with arithmetic expressions.  Otherwise we'll never escape the
>> swamp of trying to discern which ones make intuitive sense.
>>
>>   From: Paul Kyzivat <pkyzivat@cisco.com>
>>
>>> RFC 3459 uses multiparts in a somewhat different way that SIP does.
>>> In SIP, the I-D suggests that components of a multipart/alternative
>>> should have handling=optional and that the processor should ignore the
>>> handling parameter:
>>>
>>>     The UA SHOULD also set the 'handling' parameter of all the
>>>     body part within the 'multipart/alternative' to 'optional'
>>>     (the receiver will process the body parts based on the
>>>     handling parameter of the 'multipart/alternative' body; the
>>>     receiver will ignore the handling parameters of the body
>>>     parts).
>>>
>>>     The receiver SHOULD ignore the handling parameters of the body
>>>     parts within the 'multipart/ alternative'.
>>
>>   Right. But the SHOULD without qualification suggests that somebody 
>> might
>>   do otherwise, and we don't know under what circumstances that might
>>   happen. So if somebody sets all the parts to handling=required, it 
>> seems
>>   that the handling of the unselected parts will still be ignored.
>>
>> Yes, I see the problem there.  I'd replace that last SHOULD with MUST.
>> Actually, I argue that MUST is implied, as the RFCs define how
>> multipart/alternative is to be processed, and that algorithm does not
>> look at the handling parameters of components of
>> multipart/alternatives.
>>
>>   Suppose I want to send a MESSAGE, and I require that some form of the
>>   body be processed. I will offer it in two forms: text/enhanced and
>>   text/html. How do I encode that?
>>
>>        C-T: multipart/alternative
>>        C-D: render;handling=required
>>            C-T: text/enhanced
>>            C-D: render;handling=optional
>>            ===
>>            C-T: text/html
>>            C-D: render;handling=optional
>>   or
>>        C-T: multipart/alternative
>>        C-D: render;handling=required
>>            C-T: text/enhanced
>>            C-D: render;handling=required
>>            ===
>>            C-T: text/html
>>            C-D: render;handling=required
>>
>> C-T: multipart/alternative
>> C-D: render;handling=required
>>     C-T: text/enhanced
>>     ===
>>     C-T: text/html
>>
>> 'render' is inherited from the parent, and the handling of the
>> components is ignored.  We could also take it that MESSAGE implies
>> that the body is 'required', so the handling specification of the
>> parent is also optional.
>>
>>   And if I don't support either of those text types, what error do I
>>   return? 415? In the first case it seems a little odd to return an error
>>   if I selected a part that is optional.
>>
>> 415.  The I-D is clear that 415 is how you respond to messages which
>> are not processable due to a failure of these MIME tests.
>>
>>   And if I didn't require either part to be understood, would I just
>>   change to handling=optional for the multipart/alternative itself?
>>
>> Intuitively, I'd say that MESSAGE demands that the entire body be
>> processable, so handling=required is implicit for the entire body.
>> But assuming that we did not make such a deduction from the SIP
>> context of the message, if the body had handling=optional, it would
>> have the effect that the request could succeed even if the requester
>> did not understand the body.  (Hmmm...  That's another clause of the
>> algorithm I overlooked.)
>>
>> (Note that there are cases where understanding the body is optional.
>> E.g., a sipfrag of the request in a failure response.)
>>
>> Dale
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sipping@ietf.org for new developments on the application of sip
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct  1 11:00:04 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E7EB628C14B;
	Wed,  1 Oct 2008 11:00:03 -0700 (PDT)
X-Original-To: sip@ietf.org
Delivered-To: sip@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 8F5063A681F; Wed,  1 Oct 2008 11:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081001180001.8F5063A681F@core3.amsl.com>
Date: Wed,  1 Oct 2008 11:00:01 -0700 (PDT)
Cc: sip@ietf.org
Subject: [Sip] I-D Action:draft-ietf-sip-dtls-srtp-framework-04.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--NextPart

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


	Title           : Framework for Establishing an SRTP Security Context using DTLS
	Author(s)       : J. Fischl, et al.
	Filename        : draft-ietf-sip-dtls-srtp-framework-04.txt
	Pages           : 34
	Date            : 2008-10-01

This document specifies how to use the Session Initiation Protocol
(SIP) to establish an Secure Real-time Transport Protocol (SRTP)
security context using the Datagram Transport Layer Security (DTLS)
protocol.  It describes a mechanism of transporting a fingerprint
attribute in the Session Description Protocol (SDP) that identifies
the key that will be presented during the DTLS handshake.  The key
exchange travels along the media path as opposed to the signaling
path.  The SIP Identity mechanism can be used to protect the
integrity of the fingerprint attribute from modification by
intermediate proxies.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sip-dtls-srtp-framework-04.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-sip-dtls-srtp-framework-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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


From sip-bounces@ietf.org  Thu Oct  2 06:49:55 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 69C953A6784;
	Thu,  2 Oct 2008 06:49:55 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1BC103A6784;
	Thu,  2 Oct 2008 06:49:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id mLmSNbThE6Ns; Thu,  2 Oct 2008 06:49:53 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net
	[IPv6:2001:470:1f03:267::2])
	by core3.amsl.com (Postfix) with ESMTP id 52B373A677D;
	Thu,  2 Oct 2008 06:49:52 -0700 (PDT)
Received: from dn3-232.estacado.net (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.14.3/8.14.1) with ESMTP id m92DoDZe005141
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 2 Oct 2008 08:50:13 -0500 (CDT)
	(envelope-from rjsparks@nostrum.com)
Message-Id: <6439E00A-B8BA-4B7C-84EC-8EEA07EE894A@nostrum.com>
From: Robert Sparks <rjsparks@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <E30A81B1-CB3F-4C19-9427-1AA4FE2194A3@nostrum.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Thu, 2 Oct 2008 08:50:11 -0500
References: <3A760625-C47C-4BEB-84B2-EB90C134F88D@nostrum.com>
	<E30A81B1-CB3F-4C19-9427-1AA4FE2194A3@nostrum.com>
X-Mailer: Apple Mail (2.926)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Virus-Scanned: ClamAV 0.94/8371/Thu Oct 2 05:15:33 2008 on shaman.nostrum.com
X-Virus-Status: Clean
Cc: "SIP@ietf.org List" <sip@ietf.org>, sipping LIST <sipping@ietf.org>,
	simple mailing list <simple@ietf.org>,
	"sip-implementors@lists.cs.columbia.edu Implementors"
	<sip-implementors@lists.cs.columbia.edu>
Subject: [Sip] SIPit registration closes tomorrow
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1053044081=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--===============1053044081==
Content-Type: multipart/alternative; boundary=Apple-Mail-122--164924064


--Apple-Mail-122--164924064
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

(This is the last reminder - thanks everyone on these lists for being  
so patient with the crossposts).


Registration for SIPit 23 closes TOMORROW Friday October 3.

Please register immediately if you haven't already done so.

Links to the registration and more information can be found at
http://www.sipit.net
and
http://www.etsi.org/plugtests/SIPit/SIPit.htm

Thanks, and see you in Lannion week after next!

RjS



--Apple-Mail-122--164924064
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">(This is the last reminder - =
thanks everyone on these lists for being so patient with the =
crossposts).<div><br><div><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><font =
class=3D"Apple-style-span" color=3D"#000000"><br></font>Registration for =
SIPit 23 closes TOMORROW Friday October =
3.&nbsp;</div><div><br></div><div>Please register immediately if you =
haven't already done so.</div><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br></div>Links to the registration and more information can be found =
at<br><a =
href=3D"http://www.sipit.net/">http://www.sipit.net</a><br>and<br><a =
href=3D"http://www.etsi.org/plugtests/SIPit/SIPit.htm">http://www.etsi.org=
/plugtests/SIPit/SIPit.htm</a><br><br>Thanks, and see you in Lannion =
week after =
next!<br><br>RjS</div></div><br></div></div><br></div></body></html>=

--Apple-Mail-122--164924064--

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

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


From sip-bounces@ietf.org  Thu Oct  2 08:25:27 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 87F8528C1F8;
	Thu,  2 Oct 2008 08:25:27 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 46E453A6AA5
	for <sip@core3.amsl.com>; Thu,  2 Oct 2008 08:25:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.478
X-Spam-Level: 
X-Spam-Status: No, score=-2.478 tagged_above=-999 required=5 tests=[AWL=0.121, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id wECvlnARetgI for <sip@core3.amsl.com>;
	Thu,  2 Oct 2008 08:25:14 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id EBE2028C230
	for <sip@ietf.org>; Thu,  2 Oct 2008 08:25:11 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m92FP3O7030191
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 2 Oct 2008 10:25:05 -0500
Message-Id: <CDF0F938-3B8C-442C-87E4-D9B319F939DB@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Juha Heinanen <jh@tutpro.com>
In-Reply-To: <18659.54337.452872.203497@taimen.test.fi>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 2 Oct 2008 10:24:52 -0500
References: <EE9B10212E22466DAE8D10EECAF11291@rildelhi.com>
	<5D1A7985295922448D5550C94DE291800236151C@DEEXC1U01.de.lucent.com>
	<18659.54337.452872.203497@taimen.test.fi>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] [Sipping] status of draft-ietf-sip-gruu-15
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Juha brought this up on SIPPING, and I'm moving it to SIP.

On Oct 1, 2008, at 2:49 PM, Juha Heinanen wrote:

> DRAGE, Keith \(Keith\) writes:
>
>> draft-ietf-sip-gruu is dependent on draft-ietf-sip-outbound (for  
>> which
>> publication has been requested but the AD has not yet moved it off  
>> the
>> starting grid).
>
> outbound going to be published?  i suggest that it is fixed first.
>

I'm going to regret this. I know. But I have to ask.

  I thought was fixed as you wanted by requiring multiple  
registrations if there are multiple configured proxies.

So what do you think is broken now?

--
Dean

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


From sip-bounces@ietf.org  Thu Oct  2 09:04:18 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 80E9F28C1A5;
	Thu,  2 Oct 2008 09:04:18 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3BCD428C1A5
	for <sip@core3.amsl.com>; Thu,  2 Oct 2008 09:04:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id m2mFavn-yiYu for <sip@core3.amsl.com>;
	Thu,  2 Oct 2008 09:04:16 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id 6A13E28C25E
	for <sip@ietf.org>; Thu,  2 Oct 2008 09:04:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 0A7EA1EC306;
	Thu,  2 Oct 2008 19:03:49 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id lX0EOy5-vp1l; Thu,  2 Oct 2008 19:03:47 +0300 (EEST)
Received: from taimen (h128142.gprs.dnafinland.fi [87.93.128.142])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Thu,  2 Oct 2008 19:03:47 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 9125A1C8105; Thu,  2 Oct 2008 19:03:43 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18660.61663.416336.165388@taimen.test.fi>
Date: Thu, 2 Oct 2008 19:03:43 +0300
To: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <CDF0F938-3B8C-442C-87E4-D9B319F939DB@softarmor.com>
References: <EE9B10212E22466DAE8D10EECAF11291@rildelhi.com>
	<5D1A7985295922448D5550C94DE291800236151C@DEEXC1U01.de.lucent.com>
	<18659.54337.452872.203497@taimen.test.fi>
	<CDF0F938-3B8C-442C-87E4-D9B319F939DB@softarmor.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] [Sipping] status of draft-ietf-sip-gruu-15
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Dean Willis writes:

 > So what do you think is broken now?

see my message a few days ago to the list.  i have read only a few
percent of outbound text and at least this paragraph is broken:

   If the UAC is sending a dialog-forming request, and wants all
   subsequent requests in the dialog to arrive over the same flow, the
   UAC adds an 'ob' parameter to its Contact header.  Typically this is
   desirable, but it is not necessary for example if the Contact is a
   GRUU [I-D.ietf-sip-gruu].  The flow used for the request is typically
   the same flow the UA registered over, but it could be a new flow, for
   example the initial subcription dialog for the configuration
   framework [I-D.ietf-sipping-config-framework] needs to exist before
   registration.

also, i'm questioning why outbound i-d does not provide a general
solution to "usage of the same flow for in-dialog requests" problem:

  outbound behavior is also needed in case of regular presence server.
  that is why i don't quite understand is why is this "usage of the same
  flow for in-dialog requests" feature tied to outbound proxy.  why is it
  not useful to have a generic capability for UAC to tell to the next hop
  (a proxy or UAS) in its dialog initiating request that "please use this
  flow for subsequent requests of this dialog"?

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


From sip-bounces@ietf.org  Thu Oct  2 15:55:34 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 896D63A6A8B;
	Thu,  2 Oct 2008 15:55:34 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 499233A6ABC
	for <sip@core3.amsl.com>; Thu,  2 Oct 2008 15:55:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.487
X-Spam-Level: 
X-Spam-Status: No, score=-2.487 tagged_above=-999 required=5 tests=[AWL=0.112, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id P8bh4I7CwHdY for <sip@core3.amsl.com>;
	Thu,  2 Oct 2008 15:55:32 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 75F413A6A8B
	for <sip@ietf.org>; Thu,  2 Oct 2008 15:55:32 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m92MtdC3000820
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 2 Oct 2008 17:55:41 -0500
Message-Id: <B8B2BE35-DBD7-4751-8EF2-A37F148B5C32@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
In-Reply-To: <48E139E9.4050008@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 2 Oct 2008 17:55:31 -0500
References: <18656.60044.302965.535846@harjus.tutpro.com>	<1ECE0EB50388174790F9694F77522CCF197351A7@zrc2hxm0.corp.nortel.com>	<18657.2518.651908.902884@harjus.tutpro.com>
	<1ECE0EB50388174790F9694F77522CCF197354D8@zrc2hxm0.corp.nortel.com>
	<48E139E9.4050008@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: Cullen Jennings <fluffy@cisco.com>, Rohan Mahy <rohan@ekabal.com>,
	Francois Audet <audet@nortel.com>, sip@ietf.org
Subject: Re: [Sip] configuration NOTIFY in example 9.1 of outbound i-d
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Sep 29, 2008, at 3:26 PM, Paul Kyzivat wrote:

>
>
> Francois Audet wrote:
>>> > Section 4.3 states (UA procedures):
>>> >    If the UAC is sending a dialog-forming request, and wants all
>>> >    subsequent requests in the dialog to arrive over the same  
>>> flow, the
>>> >    UAC adds an 'ob' parameter to its Contact header.  Typically  
>>> this is
>>> >    desirable, but it is not necessary for example if the Contact  
>>> is a
>>> >    GRUU [I-D.ietf-sip-gruu].
>>> if contact is gruu, does it mean that 'ob' param is implicitly  
>>> included?
>> I am not sure why this is worded like this. I was thinking that  
>> using a GRUU as a contact in a dialog-forming request would mandate  
>> that
>> requests sent to that Contact would be sent using the same flow, but
>> I see no such rule in draft-ietf-sip-gruu.
>
> Gruu isn't dependent on outbound.
>
>

So explain this one for me, please.

Is it that, if the gruu was formed using outbound (that is, the "real"  
contact for which the gruu is an alias has an "ob") use of the gruu  
will use the "ob" in the dereferencing at the gruu-provider?

So for the example referenced above may be correct, but incomplete --  
it should talk about whether or not the gruu was formed using  
outbound, not just whether or not the contact isa gruu.

--
Dean




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


From sip-bounces@ietf.org  Thu Oct  2 16:01:41 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 12D213A6896;
	Thu,  2 Oct 2008 16:01:41 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1D1E63A68E3
	for <sip@core3.amsl.com>; Thu,  2 Oct 2008 16:01:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.495
X-Spam-Level: 
X-Spam-Status: No, score=-2.495 tagged_above=-999 required=5 tests=[AWL=0.104, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1BPhbBOSY3-Y for <sip@core3.amsl.com>;
	Thu,  2 Oct 2008 16:01:38 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 2929A3A69F6
	for <sip@ietf.org>; Thu,  2 Oct 2008 16:00:29 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m92N0rkA000887
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 2 Oct 2008 18:00:55 -0500
Message-Id: <D6D8CEC6-6002-4654-B3EC-309BA8EA182E@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Juha Heinanen <jh@tutpro.com>
In-Reply-To: <18660.61663.416336.165388@taimen.test.fi>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 2 Oct 2008 18:00:45 -0500
References: <EE9B10212E22466DAE8D10EECAF11291@rildelhi.com>
	<5D1A7985295922448D5550C94DE291800236151C@DEEXC1U01.de.lucent.com>
	<18659.54337.452872.203497@taimen.test.fi>
	<CDF0F938-3B8C-442C-87E4-D9B319F939DB@softarmor.com>
	<18660.61663.416336.165388@taimen.test.fi>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] [Sipping] status of draft-ietf-sip-gruu-15
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 2, 2008, at 11:03 AM, Juha Heinanen wrote:

> Dean Willis writes:
>
>> So what do you think is broken now?
>
> see my message a few days ago to the list.  i have read only a few
> percent of outbound text and at least this paragraph is broken:
>
>   If the UAC is sending a dialog-forming request, and wants all
>   subsequent requests in the dialog to arrive over the same flow, the
>   UAC adds an 'ob' parameter to its Contact header.  Typically this is
>   desirable, but it is not necessary for example if the Contact is a
>   GRUU [I-D.ietf-sip-gruu].  The flow used for the request is  
> typically
>   the same flow the UA registered over, but it could be a new flow,  
> for
>   example the initial subcription dialog for the configuration
>   framework [I-D.ietf-sipping-config-framework] needs to exist before
>   registration.
>

Ah. Thanks.

I'll follow that one up on the list on the thread in which it was  
raised.

> also, i'm questioning why outbound i-d does not provide a general
> solution to "usage of the same flow for in-dialog requests" problem:
>
>  outbound behavior is also needed in case of regular presence server.
>  that is why i don't quite understand is why is this "usage of the  
> same
>  flow for in-dialog requests" feature tied to outbound proxy.  why  
> is it
>  not useful to have a generic capability for UAC to tell to the next  
> hop
>  (a proxy or UAS) in its dialog initiating request that "please use  
> this
>  flow for subsequent requests of this dialog"?

It probably is useful, just as having keepalive separate from outbound  
is probably useful. If we were designing outbound from scratch, we'd  
probably break those two functions out into separate drafts, and have  
outbound use them.

Given that we can, if we find it sufficiently useful, add a generic  
connect-reuse modifier apart from outbound, Is it worth derailing  
outbound in order to fix it at this stage?

--
Dean

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


From sip-bounces@ietf.org  Thu Oct  2 16:09:50 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9395428C0F1;
	Thu,  2 Oct 2008 16:09:50 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 80FF728C0F1
	for <sip@core3.amsl.com>; Thu,  2 Oct 2008 16:09:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id yv5nCWhpkulo for <sip@core3.amsl.com>;
	Thu,  2 Oct 2008 16:09:48 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56])
	by core3.amsl.com (Postfix) with ESMTP id 7B39C3A68FE
	for <sip@ietf.org>; Thu,  2 Oct 2008 16:09:48 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	m92N7MS22652; Thu, 2 Oct 2008 23:07:22 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 2 Oct 2008 18:09:37 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF198A6CF5@zrc2hxm0.corp.nortel.com>
In-Reply-To: <B8B2BE35-DBD7-4751-8EF2-A37F148B5C32@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] configuration NOTIFY in example 9.1 of outbound i-d
Thread-Index: Ackk4guULRc9t1QHRyidCgymkq1jtgAAQ8hA
References: <18656.60044.302965.535846@harjus.tutpro.com>
	<1ECE0EB50388174790F9694F77522CCF197351A7@zrc2hxm0.corp.nortel.com>
	<18657.2518.651908.902884@harjus.tutpro.com>
	<1ECE0EB50388174790F9694F77522CCF197354D8@zrc2hxm0.corp.nortel.com>
	<48E139E9.4050008@cisco.com>
	<B8B2BE35-DBD7-4751-8EF2-A37F148B5C32@softarmor.com>
From: "Francois Audet" <audet@nortel.com>
To: "Dean Willis" <dean.willis@softarmor.com>,
	"Paul Kyzivat" <pkyzivat@cisco.com>
Cc: Cullen Jennings <fluffy@cisco.com>, Rohan Mahy <rohan@ekabal.com>,
	sip@ietf.org
Subject: Re: [Sip] configuration NOTIFY in example 9.1 of outbound i-d
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

My take on this is that Juha is right and the document should really say:

	If the UAC is sending a dialog-forming request, and wants all
	subsequent requests in the dialog to arrive over the same
	flow, the UAC MUST add an 'ob' parameter to its Contact header.  
      [ DELETE NEXT SENTENCE ENTIRELY ]

In other words, GRUU is orthogonal and does NOT imply "ob" behavior.

Clean and simple, and I *think* this was our intent (i.e., I think
this is an historical oversight).

Cullen, can you confirm or clarify?

> -----Original Message-----
> From: Dean Willis [mailto:dean.willis@softarmor.com] 
> Sent: Thursday, October 02, 2008 15:56
> To: Paul Kyzivat
> Cc: Audet, Francois (SC100:3055); Cullen Jennings; Rohan 
> Mahy; sip@ietf.org
> Subject: Re: [Sip] configuration NOTIFY in example 9.1 of outbound i-d
> 
> 
> On Sep 29, 2008, at 3:26 PM, Paul Kyzivat wrote:
> 
> >
> >
> > Francois Audet wrote:
> >>> > Section 4.3 states (UA procedures):
> >>> >    If the UAC is sending a dialog-forming request, and wants all
> >>> >    subsequent requests in the dialog to arrive over the same
> >>> flow, the
> >>> >    UAC adds an 'ob' parameter to its Contact header.  Typically
> >>> this is
> >>> >    desirable, but it is not necessary for example if the Contact
> >>> is a
> >>> >    GRUU [I-D.ietf-sip-gruu].
> >>> if contact is gruu, does it mean that 'ob' param is implicitly 
> >>> included?
> >> I am not sure why this is worded like this. I was thinking 
> that using 
> >> a GRUU as a contact in a dialog-forming request would mandate that 
> >> requests sent to that Contact would be sent using the same 
> flow, but 
> >> I see no such rule in draft-ietf-sip-gruu.
> >
> > Gruu isn't dependent on outbound.
> >
> >
> 
> So explain this one for me, please.
> 
> Is it that, if the gruu was formed using outbound (that is, 
> the "real"  
> contact for which the gruu is an alias has an "ob") use of 
> the gruu will use the "ob" in the dereferencing at the gruu-provider?
> 
> So for the example referenced above may be correct, but 
> incomplete -- it should talk about whether or not the gruu 
> was formed using outbound, not just whether or not the 
> contact isa gruu.
> 
> --
> Dean
> 
> 
> 
> 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct  2 16:18:21 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ACB753A6A57;
	Thu,  2 Oct 2008 16:18:21 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2EB283A6ABC
	for <sip@core3.amsl.com>; Thu,  2 Oct 2008 16:18:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.431
X-Spam-Level: 
X-Spam-Status: No, score=-6.431 tagged_above=-999 required=5 tests=[AWL=0.168, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2-GhowDrIfPA for <sip@core3.amsl.com>;
	Thu,  2 Oct 2008 16:18:19 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 162B83A68FE
	for <sip@ietf.org>; Thu,  2 Oct 2008 16:18:19 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,353,1220227200"; d="scan'208";a="23033802"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 02 Oct 2008 23:18:03 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m92NI3Xf030688; 
	Thu, 2 Oct 2008 19:18:03 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m92NI338012835;
	Thu, 2 Oct 2008 23:18:03 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Oct 2008 19:18:02 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Oct 2008 19:18:02 -0400
Message-ID: <48E556A9.1090307@cisco.com>
Date: Thu, 02 Oct 2008 19:18:01 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
References: <18656.60044.302965.535846@harjus.tutpro.com>	<1ECE0EB50388174790F9694F77522CCF197351A7@zrc2hxm0.corp.nortel.com>	<18657.2518.651908.902884@harjus.tutpro.com>
	<1ECE0EB50388174790F9694F77522CCF197354D8@zrc2hxm0.corp.nortel.com>
	<48E139E9.4050008@cisco.com>
	<B8B2BE35-DBD7-4751-8EF2-A37F148B5C32@softarmor.com>
In-Reply-To: <B8B2BE35-DBD7-4751-8EF2-A37F148B5C32@softarmor.com>
X-OriginalArrivalTime: 02 Oct 2008 23:18:02.0702 (UTC)
	FILETIME=[1E0C8EE0:01C924E5]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1734; t=1222989483;
	x=1223853483; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20configuration=20NOTIFY=20in=20e
	xample=209.1=20of=20outbound=20i-d |Sender:=20
	|To:=20Dean=20Willis=20<dean.willis@softarmor.com>;
	bh=kNeJe3kS3tbwdH3U6808RmTU8/P4LCdhUzo0PAM5DLw=;
	b=hKSbEbGOO0wYfheQv2xfBKAcmHbytCc2yseck+DbsIBG3YRCsQhvVXHDLl
	WUE2bA79/I2QWoeaDAoOKSThMcYZDzToHpU488jdT1HUYfpAC+4pM+i91TYs
	OCaleUYOf/;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: Cullen Jennings <fluffy@cisco.com>, Rohan Mahy <rohan@ekabal.com>,
	Francois Audet <audet@nortel.com>, sip@ietf.org
Subject: Re: [Sip] configuration NOTIFY in example 9.1 of outbound i-d
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Dean Willis wrote:
> 
> On Sep 29, 2008, at 3:26 PM, Paul Kyzivat wrote:
> 
>>
>>
>> Francois Audet wrote:
>>>> > Section 4.3 states (UA procedures):
>>>> >    If the UAC is sending a dialog-forming request, and wants all
>>>> >    subsequent requests in the dialog to arrive over the same flow, 
>>>> the
>>>> >    UAC adds an 'ob' parameter to its Contact header.  Typically 
>>>> this is
>>>> >    desirable, but it is not necessary for example if the Contact is a
>>>> >    GRUU [I-D.ietf-sip-gruu].
>>>> if contact is gruu, does it mean that 'ob' param is implicitly 
>>>> included?
>>> I am not sure why this is worded like this. I was thinking that using 
>>> a GRUU as a contact in a dialog-forming request would mandate that
>>> requests sent to that Contact would be sent using the same flow, but
>>> I see no such rule in draft-ietf-sip-gruu.
>>
>> Gruu isn't dependent on outbound.
>>
>>
> 
> So explain this one for me, please.
> 
> Is it that, if the gruu was formed using outbound (that is, the "real" 
> contact for which the gruu is an alias has an "ob") use of the gruu will 
> use the "ob" in the dereferencing at the gruu-provider?

Sure. When the translation of the gruu takes place the contact, with the 
ob param, will go in the R-URI. And then of course that influences how 
it is routed.

> So for the example referenced above may be correct, but incomplete -- it 
> should talk about whether or not the gruu was formed using outbound, not 
> just whether or not the contact isa gruu.

Yes, I think you are right. The UA needs to either use a contact with 
'ob', or a gruu that maps to a contact with 'ob'.

	Thanks,
	Paul

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


From sip-bounces@ietf.org  Thu Oct  2 16:20:55 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8469A3A6922;
	Thu,  2 Oct 2008 16:20:55 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7A5323A6922
	for <sip@core3.amsl.com>; Thu,  2 Oct 2008 16:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.442
X-Spam-Level: 
X-Spam-Status: No, score=-6.442 tagged_above=-999 required=5 tests=[AWL=0.157, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zue27dkSTkxY for <sip@core3.amsl.com>;
	Thu,  2 Oct 2008 16:20:53 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 676323A6912
	for <sip@ietf.org>; Thu,  2 Oct 2008 16:20:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,353,1220227200"; d="scan'208";a="23033962"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 02 Oct 2008 23:20:43 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m92NKhAZ027466; 
	Thu, 2 Oct 2008 19:20:43 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m92NKh5T012171;
	Thu, 2 Oct 2008 23:20:43 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Oct 2008 19:20:43 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 2 Oct 2008 19:20:42 -0400
Message-ID: <48E55749.5050105@cisco.com>
Date: Thu, 02 Oct 2008 19:20:41 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Francois Audet <audet@nortel.com>
References: <18656.60044.302965.535846@harjus.tutpro.com>
	<1ECE0EB50388174790F9694F77522CCF197351A7@zrc2hxm0.corp.nortel.com>
	<18657.2518.651908.902884@harjus.tutpro.com>
	<1ECE0EB50388174790F9694F77522CCF197354D8@zrc2hxm0.corp.nortel.com>
	<48E139E9.4050008@cisco.com>
	<B8B2BE35-DBD7-4751-8EF2-A37F148B5C32@softarmor.com>
	<1ECE0EB50388174790F9694F77522CCF198A6CF5@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF198A6CF5@zrc2hxm0.corp.nortel.com>
X-OriginalArrivalTime: 02 Oct 2008 23:20:42.0861 (UTC)
	FILETIME=[7D82E1D0:01C924E5]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2606; t=1222989643;
	x=1223853643; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20configuration=20NOTIFY=20in=20e
	xample=209.1=20of=20outbound=20i-d |Sender:=20
	|To:=20Francois=20Audet=20<audet@nortel.com>;
	bh=lqZtzw+0Ha5WNMtrZJPlrEdVsSzxmS7F9YofQ+c9FL0=;
	b=POte54LGJZ9bfFglewyFF2Ru+k3KWFJOTCdPtUloLsv2rmmDwFdYmyU6Y6
	oNI7ylvPQZl/PPOtbMILscqHYYiin4eeRiZRvMi+KyjuZyjHpK48qgunj3kk
	ko2eSMKT+S;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: Cullen Jennings <fluffy@cisco.com>, Rohan Mahy <rohan@ekabal.com>,
	sip@ietf.org, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] configuration NOTIFY in example 9.1 of outbound i-d
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I guess our replies overlapped.

Francois Audet wrote:
> My take on this is that Juha is right and the document should really say:
> 
> 	If the UAC is sending a dialog-forming request, and wants all
> 	subsequent requests in the dialog to arrive over the same
> 	flow, the UAC MUST add an 'ob' parameter to its Contact header.  
>       [ DELETE NEXT SENTENCE ENTIRELY ]
> 
> In other words, GRUU is orthogonal and does NOT imply "ob" behavior.

Not quite. If you have obtained a gruu after registering a contact with 
outbound, you don't have to put "ob" on the gruu. It wouldn't help, 
since it would get lost in the process of translating the gruu.

	Thanks,
	Paul

> Clean and simple, and I *think* this was our intent (i.e., I think
> this is an historical oversight).
> 
> Cullen, can you confirm or clarify?
> 
>> -----Original Message-----
>> From: Dean Willis [mailto:dean.willis@softarmor.com] 
>> Sent: Thursday, October 02, 2008 15:56
>> To: Paul Kyzivat
>> Cc: Audet, Francois (SC100:3055); Cullen Jennings; Rohan 
>> Mahy; sip@ietf.org
>> Subject: Re: [Sip] configuration NOTIFY in example 9.1 of outbound i-d
>>
>>
>> On Sep 29, 2008, at 3:26 PM, Paul Kyzivat wrote:
>>
>>>
>>> Francois Audet wrote:
>>>>>> Section 4.3 states (UA procedures):
>>>>>>    If the UAC is sending a dialog-forming request, and wants all
>>>>>>    subsequent requests in the dialog to arrive over the same
>>>>> flow, the
>>>>>>    UAC adds an 'ob' parameter to its Contact header.  Typically
>>>>> this is
>>>>>>    desirable, but it is not necessary for example if the Contact
>>>>> is a
>>>>>>    GRUU [I-D.ietf-sip-gruu].
>>>>> if contact is gruu, does it mean that 'ob' param is implicitly 
>>>>> included?
>>>> I am not sure why this is worded like this. I was thinking 
>> that using 
>>>> a GRUU as a contact in a dialog-forming request would mandate that 
>>>> requests sent to that Contact would be sent using the same 
>> flow, but 
>>>> I see no such rule in draft-ietf-sip-gruu.
>>> Gruu isn't dependent on outbound.
>>>
>>>
>> So explain this one for me, please.
>>
>> Is it that, if the gruu was formed using outbound (that is, 
>> the "real"  
>> contact for which the gruu is an alias has an "ob") use of 
>> the gruu will use the "ob" in the dereferencing at the gruu-provider?
>>
>> So for the example referenced above may be correct, but 
>> incomplete -- it should talk about whether or not the gruu 
>> was formed using outbound, not just whether or not the 
>> contact isa gruu.
>>
>> --
>> Dean
>>
>>
>>
>>
>>
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct  2 16:37:56 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9C9B23A67F2;
	Thu,  2 Oct 2008 16:37:56 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8A7E93A67F2
	for <sip@core3.amsl.com>; Thu,  2 Oct 2008 16:37:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 750JZaK9hDGL for <sip@core3.amsl.com>;
	Thu,  2 Oct 2008 16:37:54 -0700 (PDT)
Received: from zcars04f.nortel.com (zcars04f.nortel.com [47.129.242.57])
	by core3.amsl.com (Postfix) with ESMTP id 7659D3A67A4
	for <sip@ietf.org>; Thu,  2 Oct 2008 16:37:54 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m92NcAc11793; Thu, 2 Oct 2008 23:38:10 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 2 Oct 2008 18:37:09 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF198A6D42@zrc2hxm0.corp.nortel.com>
In-Reply-To: <48E55749.5050105@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] configuration NOTIFY in example 9.1 of outbound i-d
Thread-Index: Ackk5X+whezMO1JuQ9+aeLtE7S6+yQAAjBsg
References: <18656.60044.302965.535846@harjus.tutpro.com>
	<1ECE0EB50388174790F9694F77522CCF197351A7@zrc2hxm0.corp.nortel.com>
	<18657.2518.651908.902884@harjus.tutpro.com>
	<1ECE0EB50388174790F9694F77522CCF197354D8@zrc2hxm0.corp.nortel.com>
	<48E139E9.4050008@cisco.com>
	<B8B2BE35-DBD7-4751-8EF2-A37F148B5C32@softarmor.com>
	<1ECE0EB50388174790F9694F77522CCF198A6CF5@zrc2hxm0.corp.nortel.com>
	<48E55749.5050105@cisco.com>
From: "Francois Audet" <audet@nortel.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
Cc: Cullen Jennings <fluffy@cisco.com>, Rohan Mahy <rohan@ekabal.com>,
	sip@ietf.org, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] configuration NOTIFY in example 9.1 of outbound i-d
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I see what you mean.

Can you propose replacement text? 

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
> Sent: Thursday, October 02, 2008 16:21
> To: Audet, Francois (SC100:3055)
> Cc: Dean Willis; Cullen Jennings; Rohan Mahy; sip@ietf.org
> Subject: Re: [Sip] configuration NOTIFY in example 9.1 of outbound i-d
> 
> I guess our replies overlapped.
> 
> Francois Audet wrote:
> > My take on this is that Juha is right and the document 
> should really say:
> > 
> > 	If the UAC is sending a dialog-forming request, and wants all
> > 	subsequent requests in the dialog to arrive over the same
> > 	flow, the UAC MUST add an 'ob' parameter to its Contact 
> header.  
> >       [ DELETE NEXT SENTENCE ENTIRELY ]
> > 
> > In other words, GRUU is orthogonal and does NOT imply "ob" behavior.
> 
> Not quite. If you have obtained a gruu after registering a 
> contact with outbound, you don't have to put "ob" on the 
> gruu. It wouldn't help, since it would get lost in the 
> process of translating the gruu.
> 
> 	Thanks,
> 	Paul
> 
> > Clean and simple, and I *think* this was our intent (i.e., I think 
> > this is an historical oversight).
> > 
> > Cullen, can you confirm or clarify?
> > 
> >> -----Original Message-----
> >> From: Dean Willis [mailto:dean.willis@softarmor.com]
> >> Sent: Thursday, October 02, 2008 15:56
> >> To: Paul Kyzivat
> >> Cc: Audet, Francois (SC100:3055); Cullen Jennings; Rohan Mahy; 
> >> sip@ietf.org
> >> Subject: Re: [Sip] configuration NOTIFY in example 9.1 of outbound 
> >> i-d
> >>
> >>
> >> On Sep 29, 2008, at 3:26 PM, Paul Kyzivat wrote:
> >>
> >>>
> >>> Francois Audet wrote:
> >>>>>> Section 4.3 states (UA procedures):
> >>>>>>    If the UAC is sending a dialog-forming request, and 
> wants all
> >>>>>>    subsequent requests in the dialog to arrive over the same
> >>>>> flow, the
> >>>>>>    UAC adds an 'ob' parameter to its Contact header.  Typically
> >>>>> this is
> >>>>>>    desirable, but it is not necessary for example if 
> the Contact
> >>>>> is a
> >>>>>>    GRUU [I-D.ietf-sip-gruu].
> >>>>> if contact is gruu, does it mean that 'ob' param is implicitly 
> >>>>> included?
> >>>> I am not sure why this is worded like this. I was thinking
> >> that using
> >>>> a GRUU as a contact in a dialog-forming request would 
> mandate that 
> >>>> requests sent to that Contact would be sent using the same
> >> flow, but
> >>>> I see no such rule in draft-ietf-sip-gruu.
> >>> Gruu isn't dependent on outbound.
> >>>
> >>>
> >> So explain this one for me, please.
> >>
> >> Is it that, if the gruu was formed using outbound (that is, the 
> >> "real"
> >> contact for which the gruu is an alias has an "ob") use of 
> the gruu 
> >> will use the "ob" in the dereferencing at the gruu-provider?
> >>
> >> So for the example referenced above may be correct, but 
> incomplete -- 
> >> it should talk about whether or not the gruu was formed using 
> >> outbound, not just whether or not the contact isa gruu.
> >>
> >> --
> >> Dean
> >>
> >>
> >>
> >>
> >>
> > 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct  2 16:58:51 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 80D1E3A6A77;
	Thu,  2 Oct 2008 16:58:51 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 398E13A6ABD
	for <sip@core3.amsl.com>; Thu,  2 Oct 2008 16:58:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.502
X-Spam-Level: 
X-Spam-Status: No, score=-2.502 tagged_above=-999 required=5 tests=[AWL=0.097, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KIvkXtzL8A-N for <sip@core3.amsl.com>;
	Thu,  2 Oct 2008 16:58:49 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 712243A682F
	for <sip@ietf.org>; Thu,  2 Oct 2008 16:58:49 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m92Nww6g001218
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 2 Oct 2008 18:59:00 -0500
Message-Id: <CB022A19-6DEF-4E12-A0DC-06D5628371F5@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Francois Audet <audet@nortel.com>
In-Reply-To: <D6D8CEC6-6002-4654-B3EC-309BA8EA182E@softarmor.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 2 Oct 2008 18:58:52 -0500
References: <EE9B10212E22466DAE8D10EECAF11291@rildelhi.com>
	<5D1A7985295922448D5550C94DE291800236151C@DEEXC1U01.de.lucent.com>
	<18659.54337.452872.203497@taimen.test.fi>
	<CDF0F938-3B8C-442C-87E4-D9B319F939DB@softarmor.com>
	<18660.61663.416336.165388@taimen.test.fi>
	<D6D8CEC6-6002-4654-B3EC-309BA8EA182E@softarmor.com>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>
Subject: [Sip] gruu in outbound-15 9.1
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

>

Original text:


>  If the UAC is sending a dialog-forming request, and wants all
>  subsequent requests in the dialog to arrive over the same flow, the
>  UAC adds an 'ob' parameter to its Contact header.  Typically this is
>  desirable, but it is not necessary for example if the Contact is a
>  GRUU [I-D.ietf-sip-gruu].  The flow used for the request is typically
>  the same flow the UA registered over, but it could be a new flow, for
>  example the initial subcription dialog for the configuration
>  framework [I-D.ietf-sipping-config-framework] needs to exist before
>  registration.


Proposed text:

Typically, a UAC using the procedures of this document and sending a
dialog-forming request will want all subsequent requests in the dialog
to arrive over the same flow. If the UAC is using a GRUU
[I-D.ietf-sip-gruu] that was instantiated using a Contact header field
value that included an "ob" parameter, the UAC sends teh request over
the flow used for registration and susequent requests will arrive over
that same flow. If the UAC is not using such a GRUU, then the UAC adds
an "ob" parameter to its Contact header field value.  This will cause
all subsequent requests in the dialog to arrive over the flow
instantiated by the dialog-forming request. This case is typical when
the request is sent prior to registration, such as in the the initial
subcription dialog for the configuration framework
[I-D.ietf-sipping-config-framework].


--
Dean

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


From sip-bounces@ietf.org  Thu Oct  2 22:42:17 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 677D03A6A72;
	Thu,  2 Oct 2008 22:42:17 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A40F63A6A72
	for <sip@core3.amsl.com>; Thu,  2 Oct 2008 22:42:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id H5VMmhmg1OuQ for <sip@core3.amsl.com>;
	Thu,  2 Oct 2008 22:42:16 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id B7D4E3A6A59
	for <sip@ietf.org>; Thu,  2 Oct 2008 22:42:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 237761EC306;
	Fri,  3 Oct 2008 08:42:32 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id O4KqB4jaludk; Fri,  3 Oct 2008 08:42:29 +0300 (EEST)
Received: from taimen (h137091.gprs.dnafinland.fi [87.93.137.91])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Fri,  3 Oct 2008 08:42:29 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id D3C1EAC1D5; Fri,  3 Oct 2008 08:42:24 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18661.45248.837206.877589@taimen.test.fi>
Date: Fri, 3 Oct 2008 08:42:24 +0300
To: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <D6D8CEC6-6002-4654-B3EC-309BA8EA182E@softarmor.com>
References: <EE9B10212E22466DAE8D10EECAF11291@rildelhi.com>
	<5D1A7985295922448D5550C94DE291800236151C@DEEXC1U01.de.lucent.com>
	<18659.54337.452872.203497@taimen.test.fi>
	<CDF0F938-3B8C-442C-87E4-D9B319F939DB@softarmor.com>
	<18660.61663.416336.165388@taimen.test.fi>
	<D6D8CEC6-6002-4654-B3EC-309BA8EA182E@softarmor.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] [Sipping] status of draft-ietf-sip-gruu-15
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Dean Willis writes:

 > It probably is useful, just as having keepalive separate from outbound  
 > is probably useful. If we were designing outbound from scratch, we'd  
 > probably break those two functions out into separate drafts, and have  
 > outbound use them.

my understanding is that there has never been a previous outbound
related rfc, i.e., we ARE designing outbound from scratch.

 > Given that we can, if we find it sufficiently useful, add a generic  
 > connect-reuse modifier apart from outbound, Is it worth derailing  
 > outbound in order to fix it at this stage?

it surely is.  real life fact is that many vendors have already
implemented keepalive as a standalone mechanism and (as my presence
example showed) there would be need to have a generic mechanism for
connection reuse too.

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


From sip-bounces@ietf.org  Fri Oct  3 03:15:03 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 63D953A69D6;
	Fri,  3 Oct 2008 03:15:03 -0700 (PDT)
X-Original-To: sip@ietf.org
Delivered-To: sip@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id A1C843A69D6; Fri,  3 Oct 2008 03:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081003101501.A1C843A69D6@core3.amsl.com>
Date: Fri,  3 Oct 2008 03:15:01 -0700 (PDT)
Cc: sip@ietf.org
Subject: [Sip] I-D Action:draft-ietf-sip-xcapevent-04.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--NextPart

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


	Title           : An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event Package
	Author(s)       : J. Urpalainen
	Filename        : draft-ietf-sip-xcapevent-04.txt
	Pages           : 28
	Date            : 2008-10-03

This document describes an "xcap-diff" SIP event package for the SIP
Event Notification Framework, which clients can use to receive
notifications of the partial changes of Extensible Markup Language
(XML) Configuration Access Protocol (XCAP) resources.  The initial
synchronization information exchange and document updates are based
on the XCAP-Diff format.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sip-xcapevent-04.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-sip-xcapevent-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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


From sip-bounces@ietf.org  Fri Oct  3 06:12:03 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 345743A6923;
	Fri,  3 Oct 2008 06:12:03 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EC1453A688C
	for <sip@core3.amsl.com>; Fri,  3 Oct 2008 06:12:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.452
X-Spam-Level: 
X-Spam-Status: No, score=-6.452 tagged_above=-999 required=5 tests=[AWL=0.147, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id islvbKmqzCai for <sip@core3.amsl.com>;
	Fri,  3 Oct 2008 06:11:57 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id A2C793A6923
	for <sip@ietf.org>; Fri,  3 Oct 2008 06:11:57 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,356,1220227200"; d="scan'208";a="23079830"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 03 Oct 2008 13:12:26 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m93DCPJh019061; 
	Fri, 3 Oct 2008 09:12:25 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m93DCO5b028014;
	Fri, 3 Oct 2008 13:12:25 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 3 Oct 2008 09:12:00 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 3 Oct 2008 09:12:00 -0400
Message-ID: <48E61A1F.3070107@cisco.com>
Date: Fri, 03 Oct 2008 09:11:59 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Francois Audet <audet@nortel.com>
References: <18656.60044.302965.535846@harjus.tutpro.com>
	<1ECE0EB50388174790F9694F77522CCF197351A7@zrc2hxm0.corp.nortel.com>
	<18657.2518.651908.902884@harjus.tutpro.com>
	<1ECE0EB50388174790F9694F77522CCF197354D8@zrc2hxm0.corp.nortel.com>
	<48E139E9.4050008@cisco.com>
	<B8B2BE35-DBD7-4751-8EF2-A37F148B5C32@softarmor.com>
	<1ECE0EB50388174790F9694F77522CCF198A6CF5@zrc2hxm0.corp.nortel.com>
	<48E55749.5050105@cisco.com>
	<1ECE0EB50388174790F9694F77522CCF198A6D42@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF198A6D42@zrc2hxm0.corp.nortel.com>
X-OriginalArrivalTime: 03 Oct 2008 13:12:00.0430 (UTC)
	FILETIME=[9EDBECE0:01C92559]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3275; t=1223039545;
	x=1223903545; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20configuration=20NOTIFY=20in=20e
	xample=209.1=20of=20outbound=20i-d |Sender:=20
	|To:=20Francois=20Audet=20<audet@nortel.com>;
	bh=v3v7zkDveyzq/5XWaRRF1R9y7AyjPc2TAJrWNrtXAqs=;
	b=0LbyiQYjblkeAC8Ekn5GOCEImOuOFJFFhvNWan4OokwKDJzP+wKsca4268
	EgW5G4MU/ApbK54jFiScQRD2R1S7Ee8ca4SxJuEOASqgcJOF1IMtT23/q1zf
	A+lNdf3vs7;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: Cullen Jennings <fluffy@cisco.com>, Rohan Mahy <rohan@ekabal.com>,
	sip@ietf.org, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] configuration NOTIFY in example 9.1 of outbound i-d
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Francois Audet wrote:
> I see what you mean.
> 
> Can you propose replacement text? 

Dean beat me to it. And his text is good - better than I would have done.

	Thanks,
	Paul

>> -----Original Message-----
>> From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
>> Sent: Thursday, October 02, 2008 16:21
>> To: Audet, Francois (SC100:3055)
>> Cc: Dean Willis; Cullen Jennings; Rohan Mahy; sip@ietf.org
>> Subject: Re: [Sip] configuration NOTIFY in example 9.1 of outbound i-d
>>
>> I guess our replies overlapped.
>>
>> Francois Audet wrote:
>>> My take on this is that Juha is right and the document 
>> should really say:
>>> 	If the UAC is sending a dialog-forming request, and wants all
>>> 	subsequent requests in the dialog to arrive over the same
>>> 	flow, the UAC MUST add an 'ob' parameter to its Contact 
>> header.  
>>>       [ DELETE NEXT SENTENCE ENTIRELY ]
>>>
>>> In other words, GRUU is orthogonal and does NOT imply "ob" behavior.
>> Not quite. If you have obtained a gruu after registering a 
>> contact with outbound, you don't have to put "ob" on the 
>> gruu. It wouldn't help, since it would get lost in the 
>> process of translating the gruu.
>>
>> 	Thanks,
>> 	Paul
>>
>>> Clean and simple, and I *think* this was our intent (i.e., I think 
>>> this is an historical oversight).
>>>
>>> Cullen, can you confirm or clarify?
>>>
>>>> -----Original Message-----
>>>> From: Dean Willis [mailto:dean.willis@softarmor.com]
>>>> Sent: Thursday, October 02, 2008 15:56
>>>> To: Paul Kyzivat
>>>> Cc: Audet, Francois (SC100:3055); Cullen Jennings; Rohan Mahy; 
>>>> sip@ietf.org
>>>> Subject: Re: [Sip] configuration NOTIFY in example 9.1 of outbound 
>>>> i-d
>>>>
>>>>
>>>> On Sep 29, 2008, at 3:26 PM, Paul Kyzivat wrote:
>>>>
>>>>> Francois Audet wrote:
>>>>>>>> Section 4.3 states (UA procedures):
>>>>>>>>    If the UAC is sending a dialog-forming request, and 
>> wants all
>>>>>>>>    subsequent requests in the dialog to arrive over the same
>>>>>>> flow, the
>>>>>>>>    UAC adds an 'ob' parameter to its Contact header.  Typically
>>>>>>> this is
>>>>>>>>    desirable, but it is not necessary for example if 
>> the Contact
>>>>>>> is a
>>>>>>>>    GRUU [I-D.ietf-sip-gruu].
>>>>>>> if contact is gruu, does it mean that 'ob' param is implicitly 
>>>>>>> included?
>>>>>> I am not sure why this is worded like this. I was thinking
>>>> that using
>>>>>> a GRUU as a contact in a dialog-forming request would 
>> mandate that 
>>>>>> requests sent to that Contact would be sent using the same
>>>> flow, but
>>>>>> I see no such rule in draft-ietf-sip-gruu.
>>>>> Gruu isn't dependent on outbound.
>>>>>
>>>>>
>>>> So explain this one for me, please.
>>>>
>>>> Is it that, if the gruu was formed using outbound (that is, the 
>>>> "real"
>>>> contact for which the gruu is an alias has an "ob") use of 
>> the gruu 
>>>> will use the "ob" in the dereferencing at the gruu-provider?
>>>>
>>>> So for the example referenced above may be correct, but 
>> incomplete -- 
>>>> it should talk about whether or not the gruu was formed using 
>>>> outbound, not just whether or not the contact isa gruu.
>>>>
>>>> --
>>>> Dean
>>>>
>>>>
>>>>
>>>>
>>>>
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct  3 08:30:03 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EC56328C252;
	Fri,  3 Oct 2008 08:30:02 -0700 (PDT)
X-Original-To: sip@ietf.org
Delivered-To: sip@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id CF04928C249; Fri,  3 Oct 2008 08:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081003153001.CF04928C249@core3.amsl.com>
Date: Fri,  3 Oct 2008 08:30:01 -0700 (PDT)
Cc: sip@ietf.org
Subject: [Sip] I-D Action:draft-ietf-sip-record-route-fix-04.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--NextPart

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


	Title           : Addressing Record-Route issues in the Session Initiation Protocol (SIP)
	Author(s)       : T. Froment, et al.
	Filename        : draft-ietf-sip-record-route-fix-04.txt
	Pages           : 25
	Date            : 2008-10-03

A typical function of a Session Initiation Protocol (SIP) Proxy is to
insert a Record-Route header into initial, dialog creating requests
in order to make subsequent, in-dialog requests pass through it.
This header contains a SIP Uniform Resource Identifier (URI)
indicating where and how the subsequent requests should be sent to
reach the proxy.  Like any SIP URI, it can contain sip or sips
schemes, IPv4 or IPv6 addresses, and URI parameters that could
influence the routing such as the transport parameter (for example
transport=tcp), or a compression indication like "comp=sigcomp".
When a proxy has to change some of those parameters between its
incoming and outgoing interfaces (multi-homed proxies, transport
protocol switching or IPv4 to IPv6 scenarios...), the question arises
on what should be put in Record-Route header(s).  It is just not
possible to make one header having the characteristics of both sides
at the same time.  This document aims to clarify these scenarios and
fix bugs already identified on this topic; it formally recommends the
use of the double Record-Route technique as an alternative to the
current RFC3261 text, which describes only a Record-Route rewriting
solution.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sip-record-route-fix-04.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-sip-record-route-fix-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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


From sip-bounces@ietf.org  Fri Oct  3 09:25:32 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7D1903A698E;
	Fri,  3 Oct 2008 09:25:32 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C1F783A698E
	for <sip@core3.amsl.com>; Fri,  3 Oct 2008 09:25:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.514
X-Spam-Level: 
X-Spam-Status: No, score=-2.514 tagged_above=-999 required=5 tests=[AWL=0.085, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BVlc63yiqgjb for <sip@core3.amsl.com>;
	Fri,  3 Oct 2008 09:25:25 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 4A1D53A68A7
	for <sip@ietf.org>; Fri,  3 Oct 2008 09:25:25 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m93GPp1b006549
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 3 Oct 2008 11:25:53 -0500
Message-Id: <FC1F4E08-4EFB-4829-B677-DA9A0E2F27BB@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Juha Heinanen <jh@tutpro.com>
In-Reply-To: <18661.45248.837206.877589@taimen.test.fi>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 3 Oct 2008 11:25:46 -0500
References: <EE9B10212E22466DAE8D10EECAF11291@rildelhi.com>
	<5D1A7985295922448D5550C94DE291800236151C@DEEXC1U01.de.lucent.com>
	<18659.54337.452872.203497@taimen.test.fi>
	<CDF0F938-3B8C-442C-87E4-D9B319F939DB@softarmor.com>
	<18660.61663.416336.165388@taimen.test.fi>
	<D6D8CEC6-6002-4654-B3EC-309BA8EA182E@softarmor.com>
	<18661.45248.837206.877589@taimen.test.fi>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] [Sipping] status of draft-ietf-sip-gruu-15
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 3, 2008, at 12:42 AM, Juha Heinanen wrote:

> Dean Willis writes:
>
>> It probably is useful, just as having keepalive separate from  
>> outbound
>> is probably useful. If we were designing outbound from scratch, we'd
>> probably break those two functions out into separate drafts, and have
>> outbound use them.
>
> my understanding is that there has never been a previous outbound
> related rfc, i.e., we ARE designing outbound from scratch.

Nope. We're designing outbound from where it is -- a document with  
years of effort in it, and quite a few implementations.

We always learn things while doing a document. Sometimes those things  
make their way into the document sometimes they don't.

My understanding of the WG's consensus position is that, while we  
could probably keep making Outbound better forever, the currently  
known weaknesses are not enough to force a fundamental redesign at  
this point.  We're still open to clarifications, and there's always  
the possibility that a real show-stopper could exist, but these two  
design limitations don't qualify as show-stoppers.

>
>
>> Given that we can, if we find it sufficiently useful, add a generic
>> connect-reuse modifier apart from outbound, Is it worth derailing
>> outbound in order to fix it at this stage?
>
> it surely is.  real life fact is that many vendors have already
> implemented keepalive as a standalone mechanism and (as my presence
> example showed) there would be need to have a generic mechanism for
> connection reuse too.
>

We're looking at a standalone keepalive, and Christer has been leading  
that work. We've also been stumbling over a connection-reuse mechanism  
for years; perhaps you have an insight that could lead that work  
towards some sort of meaningful conclusion.

--
Dean

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


From sip-bounces@ietf.org  Fri Oct  3 09:38:45 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5959B3A68E1;
	Fri,  3 Oct 2008 09:38:45 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 95A463A68E1
	for <sip@core3.amsl.com>; Fri,  3 Oct 2008 09:38:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.518
X-Spam-Level: 
X-Spam-Status: No, score=-2.518 tagged_above=-999 required=5 tests=[AWL=0.081, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id hL8MnmLi1ZYO for <sip@core3.amsl.com>;
	Fri,  3 Oct 2008 09:38:44 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id CD7143A68DB
	for <sip@ietf.org>; Fri,  3 Oct 2008 09:38:43 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m93GcNDL006641
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 3 Oct 2008 11:38:25 -0500
Message-Id: <91B7DF7A-8076-4589-8464-1422FCA1E44E@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: SIP IETF <sip@ietf.org>
In-Reply-To: <1222413851.8449.15.camel@little.research.nokia.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 3 Oct 2008 11:38:17 -0500
References: <1222413851.8449.15.camel@little.research.nokia.com>
X-Mailer: Apple Mail (2.929.2)
Cc: Keith Drage <drage@alcatel-lucent.com>, Aki Niemi <aki.niemi@nokia.com>
Subject: [Sip] Conclusion of WGLC on draft-ietf-sip-subnot-etags-03
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


The subnot-etags draft entered WGLC in August of 2007. It's been  
revised twice in that period.

The current version:

http://www.ietf.org/internet-drafts/draft-ietf-sip-subnot-etags-03.txt


seems to be pretty much ready to go (other than a few nits which can  
be cleaned up by RFCEd notes).


If you have any last comments on it, get them sent in Really Soon Now,  
as I plan to do the publication writeup shortly.



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


From sip-bounces@ietf.org  Fri Oct  3 09:45:08 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E7F303A6AC4;
	Fri,  3 Oct 2008 09:45:07 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 442EE3A69DD
	for <sip@core3.amsl.com>; Fri,  3 Oct 2008 09:45:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LYY3N1OUjedd for <sip@core3.amsl.com>;
	Fri,  3 Oct 2008 09:45:04 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id C19613A6AC4
	for <sip@ietf.org>; Fri,  3 Oct 2008 09:45:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 97CF41EC306;
	Fri,  3 Oct 2008 19:45:04 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id myBZ0+mFz6iI; Fri,  3 Oct 2008 19:45:02 +0300 (EEST)
Received: from taimen (h128061.gprs.dnafinland.fi [87.93.128.61])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Fri,  3 Oct 2008 19:45:02 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id D827CAC1D8; Fri,  3 Oct 2008 19:03:36 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18662.16984.781166.641624@taimen.test.fi>
Date: Fri, 3 Oct 2008 19:03:36 +0300
To: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <FC1F4E08-4EFB-4829-B677-DA9A0E2F27BB@softarmor.com>
References: <EE9B10212E22466DAE8D10EECAF11291@rildelhi.com>
	<5D1A7985295922448D5550C94DE291800236151C@DEEXC1U01.de.lucent.com>
	<18659.54337.452872.203497@taimen.test.fi>
	<CDF0F938-3B8C-442C-87E4-D9B319F939DB@softarmor.com>
	<18660.61663.416336.165388@taimen.test.fi>
	<D6D8CEC6-6002-4654-B3EC-309BA8EA182E@softarmor.com>
	<18661.45248.837206.877589@taimen.test.fi>
	<FC1F4E08-4EFB-4829-B677-DA9A0E2F27BB@softarmor.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] [Sipping] status of draft-ietf-sip-gruu-15
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Dean Willis writes:

 > My understanding of the WG's consensus position is that, while we  
 > could probably keep making Outbound better forever, the currently  
 > known weaknesses are not enough to force a fundamental redesign at  
 > this point.

i haven't suggested "fundamental redesign".  outbound should refer to
generic connection reuse and keepalive rfcs rather that include limited
solutions of its own that are likely to cause later backwards
compatibility issues or second solutions to the same problems.

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


From sip-bounces@ietf.org  Fri Oct  3 09:50:40 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DD3CE3A68A7;
	Fri,  3 Oct 2008 09:50:40 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0F6C13A68A7
	for <sip@core3.amsl.com>; Fri,  3 Oct 2008 09:50:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.523
X-Spam-Level: 
X-Spam-Status: No, score=-2.523 tagged_above=-999 required=5 tests=[AWL=0.076, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zdtKG0035l4p for <sip@core3.amsl.com>;
	Fri,  3 Oct 2008 09:50:38 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 89CFF3A67CF
	for <sip@ietf.org>; Fri,  3 Oct 2008 09:50:34 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m93Gp2wp006783
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT)
	for <sip@ietf.org>; Fri, 3 Oct 2008 11:51:03 -0500
Message-Id: <F37A79E3-19F5-45EE-A2BC-628E50D1309F@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: SIP IETF <sip@ietf.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 3 Oct 2008 11:50:56 -0500
X-Mailer: Apple Mail (2.929.2)
Subject: [Sip] Note on RFC 3330 Reserved  Example IP Addresses in Drafts
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


RFC 3330 defines reserved IP addresses for use in examples in internet  
drafts and RFCs.

The IESG has gotten very strict about publishing drafts that do not  
conform to RFC 3330's guidelines.

And, the idnits tool checks for these things.

An example of idnits output:

Found possible IPv4 address '10.1.1.2' in position 42; this doesn't  
match RFC3330's suggested 192.0.2.0/24

The idnits tool is online at:

http://tools.ietf.org/tools/idnits/
Idnits is easy to use. I strongly recommend all authors run every  
draft through idnits before submitting it, and clearing up all errors  
and as many warnings as reasonably possible. It will make my life   
easier!

--
Dean



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


From sip-bounces@ietf.org  Fri Oct  3 11:20:41 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 31BEF28C0DB;
	Fri,  3 Oct 2008 11:20:41 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C7FA43A6839
	for <sip@core3.amsl.com>; Fri,  3 Oct 2008 11:20:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level: 
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.043, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id NA2PyLhhvTIh for <sip@core3.amsl.com>;
	Fri,  3 Oct 2008 11:20:38 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 2675B3A6B29
	for <sip@ietf.org>; Fri,  3 Oct 2008 11:20:25 -0700 (PDT)
Received: from [75.68.119.237] (port=62358 helo=[192.168.15.100])
	by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1KlpG5-00046e-Hu; Fri, 03 Oct 2008 11:20:11 -0700
Message-Id: <9FF7202C-55A0-4635-84AC-1D7A8154C541@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
In-Reply-To: <48E3AA84.6010808@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 3 Oct 2008 14:20:11 -0400
References: <5D1A7985295922448D5550C94DE2918002196DCC@DEEXC1U01.de.lucent.com>	<48898492.7010601@ericsson.com>	<5D1A7985295922448D5550C94DE2918002196FF7@DEEXC1U01.de.lucent.com>	<4889F09B.8050407@cisco.com>	<200809262108.m8QL8fpj34800452@shell01.TheWorld.com>	<48E0F79B.8090402@cisco.com>	<200809300309.m8U39jFX37113365@shell01.TheWorld.com>
	<9BCA68EB-2AF2-4F88-A595-B4CE1ED6475B@standardstrack.com>
	<48E3AA84.6010808@cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Comments on draft-ietf-sip-body-handling-02
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1112415221=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--===============1112415221==
Content-Type: multipart/signed; boundary=Apple-Mail-45--62324645; micalg=sha1; protocol="application/pkcs7-signature"


--Apple-Mail-45--62324645
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

I'm trolling my e-mail contacts (pardon the pun) on how they do MIME  
decoding.

On the second paragraph: if you are a proxy that is actually doing  
something with the body, *and you are going to hack the body*, then I  
would offer you've created something that most likely will be some  
kind of B2BUA.

In the e-mail world, the ;handling property was created for gateways  
(B2BUA's), so the gateway could know whether dropping a body part,  
because the connected network/protocol could not handle that body  
part, would render the message useless. For example, if I am using an  
old version of Outlook, and I send you a Word file, the Word body part  
is required for the relay, but the application/tnef (proprietary  
Outlook stuff) is optional and the gateway can silently drop the part.

On Oct 1, 2008, at 12:51 PM, Paul Kyzivat wrote:

> Ok, ok, UNCLE!!!
>
> I'd still like to know if email clients need to do this two pass  
> approach - first searching for all the references to determine if  
> all the handling requirements can be met, and then actually doing  
> the processing of the referenced parts?
>
> Also, it *is* legal for proxies to process bodies. But its obviously  
> not required (by the protocol) for them to do so. Do we have a clue  
> how the handling parameter applies to proxies? I assume in effect  
> they can just ignore it and consider handling to be optional for all  
> parts. Also, I presume a proxy that cares about body parts might  
> want to investigate all the alternatives of a multipart/alternative,  
> since it can't know which one the recipient will choose.
>
> 	Thanks,
> 	Paul
>
> Eric Burger wrote:
>> Agreed. And, echoing what Keith said, what Dale has done is prove  
>> (from a Computer Science perspective) that complete evaluation of  
>> unfettered MIME is *possible*. It is up to the implementor to  
>> figure out whether they want to take short-cuts (and risk barfing  
>> on legitimate messages) or do the whole thing.
>> The point is doing the Full Monte *is* practical on small, memory  
>> and CPU constrained devices. So the argument "We can't do the real  
>> thing because it hurts" is provably not legitimate.
>> On Sep 29, 2008, at 11:09 PM, Dale.Worley@comcast.net wrote:
>>>  From: Paul Kyzivat <pkyzivat@cisco.com>
>>>
>>>  I agree it would be straightforward to define a rule that says  
>>> one must
>>>  recursively unwrap all multipart/mixed bodies in order to find  
>>> other
>>>  parts to process. But we ought to think if we really want to do  
>>> that.
>>>
>>> What alternative rule do you propose as the meaning of
>>> multipart/mixed?
>>>
>>>  Potentially this could introduce a lot of extra processing.
>>>
>>> That's sort of like saying that "x = 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0"
>>> involves a lot of extra processing.  Yes, it does.  But it meaning  
>>> is
>>> clear, once we define what "+" means.  We could try to outlaw that
>>> expression and "expressions like it", but there's no sensible  
>>> boundary
>>> to enforce -- Do we ban expressions with more than five addends?   
>>> How
>>> about more than one addend which is "0"?  Any possible solution to
>>> this problem is worse than the problem itself.
>>>
>>> What I am advocating is that we explicitly abandon the attempt to
>>> define only the situations that intuitively make sense, and instead
>>> define a set of simple, well-defined rules that make clear what is
>>> valid and what is not, and what the valid cases mean.  Just like  
>>> we've
>>> done with arithmetic expressions.  Otherwise we'll never escape the
>>> swamp of trying to discern which ones make intuitive sense.
>>>
>>>  From: Paul Kyzivat <pkyzivat@cisco.com>
>>>
>>>> RFC 3459 uses multiparts in a somewhat different way that SIP does.
>>>> In SIP, the I-D suggests that components of a multipart/alternative
>>>> should have handling=optional and that the processor should  
>>>> ignore the
>>>> handling parameter:
>>>>
>>>>    The UA SHOULD also set the 'handling' parameter of all the
>>>>    body part within the 'multipart/alternative' to 'optional'
>>>>    (the receiver will process the body parts based on the
>>>>    handling parameter of the 'multipart/alternative' body; the
>>>>    receiver will ignore the handling parameters of the body
>>>>    parts).
>>>>
>>>>    The receiver SHOULD ignore the handling parameters of the body
>>>>    parts within the 'multipart/ alternative'.
>>>
>>>  Right. But the SHOULD without qualification suggests that  
>>> somebody might
>>>  do otherwise, and we don't know under what circumstances that might
>>>  happen. So if somebody sets all the parts to handling=required,  
>>> it seems
>>>  that the handling of the unselected parts will still be ignored.
>>>
>>> Yes, I see the problem there.  I'd replace that last SHOULD with  
>>> MUST.
>>> Actually, I argue that MUST is implied, as the RFCs define how
>>> multipart/alternative is to be processed, and that algorithm does  
>>> not
>>> look at the handling parameters of components of
>>> multipart/alternatives.
>>>
>>>  Suppose I want to send a MESSAGE, and I require that some form of  
>>> the
>>>  body be processed. I will offer it in two forms: text/enhanced and
>>>  text/html. How do I encode that?
>>>
>>>       C-T: multipart/alternative
>>>       C-D: render;handling=required
>>>           C-T: text/enhanced
>>>           C-D: render;handling=optional
>>>           ===
>>>           C-T: text/html
>>>           C-D: render;handling=optional
>>>  or
>>>       C-T: multipart/alternative
>>>       C-D: render;handling=required
>>>           C-T: text/enhanced
>>>           C-D: render;handling=required
>>>           ===
>>>           C-T: text/html
>>>           C-D: render;handling=required
>>>
>>> C-T: multipart/alternative
>>> C-D: render;handling=required
>>>    C-T: text/enhanced
>>>    ===
>>>    C-T: text/html
>>>
>>> 'render' is inherited from the parent, and the handling of the
>>> components is ignored.  We could also take it that MESSAGE implies
>>> that the body is 'required', so the handling specification of the
>>> parent is also optional.
>>>
>>>  And if I don't support either of those text types, what error do I
>>>  return? 415? In the first case it seems a little odd to return an  
>>> error
>>>  if I selected a part that is optional.
>>>
>>> 415.  The I-D is clear that 415 is how you respond to messages which
>>> are not processable due to a failure of these MIME tests.
>>>
>>>  And if I didn't require either part to be understood, would I just
>>>  change to handling=optional for the multipart/alternative itself?
>>>
>>> Intuitively, I'd say that MESSAGE demands that the entire body be
>>> processable, so handling=required is implicit for the entire body.
>>> But assuming that we did not make such a deduction from the SIP
>>> context of the message, if the body had handling=optional, it would
>>> have the effect that the request could succeed even if the requester
>>> did not understand the body.  (Hmmm...  That's another clause of the
>>> algorithm I overlooked.)
>>>
>>> (Note that there are cases where understanding the body is optional.
>>> E.g., a sipfrag of the request in a failure response.)
>>>
>>> Dale
>>> _______________________________________________
>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>> This list is for NEW development of the core SIP Protocol
>>> Use sip-implementors@cs.columbia.edu for questions on current sip
>>> Use sipping@ietf.org for new developments on the application of sip
>> ------------------------------------------------------------------------
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sipping@ietf.org for new developments on the application of sip


--Apple-Mail-45--62324645
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGPTCCBjkw
ggUhoAMCAQICEC+VK1RLWxrF8KJZDR9k8p8wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYTAlVT
MQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VS
VFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQD
Ey1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwwHhcNMDgwODEz
MDAwMDAwWhcNMDkwODEzMjM1OTU5WjCB4TE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsg
LSBQRVJTT05BIE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9m
IHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDMg
Q29tb2RvIExpbWl0ZWQxFDASBgNVBAMTC0VyaWMgQnVyZ2VyMSkwJwYJKoZIhvcNAQkBFhplYnVy
Z2VyQHN0YW5kYXJkc3RyYWNrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMTF
RRoA4LgOACMFph0aomRC/UpqoA5C/d6DUTOvTMrYSEqkjwnU4zxDtBcHlcB4AxKAov00MYsUvEU4
loz7BHjfDjv76AIkcwu33VYQbzGmarVnyaXsVb6f/cyRL3fPT0VOVO2tQAEEgwg//CX0jN8Kn2jH
uXD/HEvko7cmpL3Pwevf3+DwB61v7ca79PpEZfn/WhaqRKA4uVNPj/JbieeaLo2v/0RJzrEElZK0
pHCqxiD3mQ8ossPkA9fUCSxLlbdMcPU3be5x8vt8Q8mYTXF5Z3d9RZmYrmNkvTQtdzVpfYWr/hgV
Xqm9tByOOAR+hoN3FKbubR/OrAHL9yDAd4sCAwEAAaOCAhwwggIYMB8GA1UdIwQYMBaAFImCZ33E
nSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBRDWgutb7b8R/L7G3Y3D+molAA3VzAOBgNVHQ8BAf8E
BAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJ
YIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEW
HWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMIGlBgNVHR8EgZ0wgZowTKBKoEiGRmh0dHA6
Ly9jcmwuY29tb2RvY2EuY29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRF
bWFpbC5jcmwwSqBIoEaGRGh0dHA6Ly9jcmwuY29tb2RvLm5ldC9VVE4tVVNFUkZpcnN0LUNsaWVu
dEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMGwGCCsGAQUFBwEBBGAwXjA2BggrBgEFBQcwAoYq
aHR0cDovL2NydC5jb21vZG9jYS5jb20vVVROQUFBQ2xpZW50Q0EuY3J0MCQGCCsGAQUFBzABhhho
dHRwOi8vb2NzcC5jb21vZG9jYS5jb20wJQYDVR0RBB4wHIEaZWJ1cmdlckBzdGFuZGFyZHN0cmFj
ay5jb20wDQYJKoZIhvcNAQEFBQADggEBAGeBR7NPCvrY3GQoIi49JOuciatY2r4st905Jw1etp6J
umFFWlaCBl11tFSclk/3S45B+lUv3SEvG4CEjUByPScprVmCqHR+y8BAQaB/CV+N1y14x3MbhJ+Z
8XDGKeUXuuyGd9w0l3/t/QPid6TRXQjQFrLPFs1IALuNpNiFMHEF/xFbMG1Z2vznR/gSPlePekoZ
TqcExIDBNZTBebpZqwAXzPpedNNOclbMLFLWDMOAozVRpkfjI0eiFsk8SF1Ho1Gb9Bx8DeG4peE2
KRVOR9FFnZZgBpFjXYRcglsMOSKCY8HgE+NGvbbqbrMoBV/BlYyxRXwfti71RL9Zs2Cq1eQxggP8
MIID+AIBATCBwzCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExh
a2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8v
d3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkNH2TynzAJBgUrDgMCGgUAoIICDTAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wODEwMDMxODIwMTFaMCMGCSqGSIb3
DQEJBDEWBBQWiZFoxi3duNYaQ007oLxDxNKu9DCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD
VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU
aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2
MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv
lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN
H2TynzANBgkqhkiG9w0BAQEFAASCAQB6crq76uDB7M3QOCFTUscob2C/E3IdE4Vw/AG0wB7zMj0A
usObKRP++O+HDZ+MxAg788/JaGqh6qORj8/eDP7zsa4Whzc0eLU1XQDZQs1+bYFJVdeRI9wqT3Zn
aVeXeKaNgCuGvDiLpLAUHpiiTnTjIXFR0l6DvR/MKurHmayiO21bbTSsNYaF/J6pTEoCVHYs/z2C
Ww3dYojLrZehazX2lGLjWMdWPV4gbslFo3JNLHCjKM9SqktGPc2BqVvxSGz47C6zb8CNAk72Sa7C
ZgIPkHACFskcyt+u7KxuJ9u/gnsl40WC9mQViMSySj0A+9U0LJMYuGyRoH2VZpNGv5jLAAAAAAAA

--Apple-Mail-45--62324645--

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

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


From sip-bounces@ietf.org  Fri Oct  3 11:42:41 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DB56D28C16B;
	Fri,  3 Oct 2008 11:42:41 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CC10128C0D8
	for <sip@core3.amsl.com>; Fri,  3 Oct 2008 11:42:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.475
X-Spam-Level: 
X-Spam-Status: No, score=-6.475 tagged_above=-999 required=5 tests=[AWL=0.124, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Z0hCUmru5no2 for <sip@core3.amsl.com>;
	Fri,  3 Oct 2008 11:42:39 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 2DE9728C18C
	for <sip@ietf.org>; Fri,  3 Oct 2008 11:42:39 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,358,1220227200"; d="scan'208";a="23123154"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 03 Oct 2008 18:43:02 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m93Ih0Aa026551; 
	Fri, 3 Oct 2008 14:43:00 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m93Ih0SK005958;
	Fri, 3 Oct 2008 18:43:00 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 3 Oct 2008 14:43:00 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 3 Oct 2008 14:43:00 -0400
Message-ID: <48E667B3.8090705@cisco.com>
Date: Fri, 03 Oct 2008 14:42:59 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Eric Burger <eburger@standardstrack.com>
References: <5D1A7985295922448D5550C94DE2918002196DCC@DEEXC1U01.de.lucent.com>	<48898492.7010601@ericsson.com>	<5D1A7985295922448D5550C94DE2918002196FF7@DEEXC1U01.de.lucent.com>	<4889F09B.8050407@cisco.com>	<200809262108.m8QL8fpj34800452@shell01.TheWorld.com>	<48E0F79B.8090402@cisco.com>	<200809300309.m8U39jFX37113365@shell01.TheWorld.com>
	<9BCA68EB-2AF2-4F88-A595-B4CE1ED6475B@standardstrack.com>
	<48E3AA84.6010808@cisco.com>
	<9FF7202C-55A0-4635-84AC-1D7A8154C541@standardstrack.com>
In-Reply-To: <9FF7202C-55A0-4635-84AC-1D7A8154C541@standardstrack.com>
X-OriginalArrivalTime: 03 Oct 2008 18:43:00.0142 (UTC)
	FILETIME=[DC2B7CE0:01C92587]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=9831; t=1223059380;
	x=1223923380; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Comments=20on=20draft-ietf-sip-
	body-handling-02 |Sender:=20
	|To:=20Eric=20Burger=20<eburger@standardstrack.com>;
	bh=0ktscA5yquvWnyrkynK505IRESR82/gZNKhU1/9VMD4=;
	b=SPnoFeoxXxBZ4Z4eZQ3HoENrXaP7noSh83SIs+e1R5KYm7lSzhYzAND58T
	4Dvzrdjv2Ejkmkl9veqCVXw+KLbnWJXTmfEYr4giPSLoHuYJR9bpuAZALjsM
	AAO8rNNDnx;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Comments on draft-ietf-sip-body-handling-02
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Eric Burger wrote:
> I'm trolling my e-mail contacts (pardon the pun) on how they do MIME 
> decoding.
> 
> On the second paragraph: if you are a proxy that is actually doing 
> something with the body, *and you are going to hack the body*, then I 
> would offer you've created something that most likely will be some kind 
> of B2BUA.

Thats a different case. A B2BUA *is* a UA, so I suppose these rules 
about handling apply to it. (But I know it will get more confusing when 
considering B2BUAs that are more "proxy-like" in their handling of the 
body - just passing it through and perhaps peeking into it.

I was concerned with true proxies. E.g. I know there are proxies that 
look for SDP bodies and use them as input to policy decisions for 
control of gates in the media path. Similarly, I can imagine a proxy 
that scans bodies of MESSAGE requests, recording them and perhaps 
alerting when certain keywords are noticed.

I'm not certain what relevance the handling parameter has to such a 
proxy. Perhaps none.

> In the e-mail world, the ;handling property was created for gateways 
> (B2BUA's), so the gateway could know whether dropping a body part, 
> because the connected network/protocol could not handle that body part, 
> would render the message useless. For example, if I am using an old 
> version of Outlook, and I send you a Word file, the Word body part is 
> required for the relay, but the application/tnef (proprietary Outlook 
> stuff) is optional and the gateway can silently drop the part.

That is quite different than what we are setting up here. We are in the 
process of saying that if there is some part with handling=required, and 
you don't know how to process it, then you should fail the request, 
before you have processed any of it.

That provides nice, clear, unambiguous semantics. But it may not be 
realistic. I don't have the sense that is how mail works. But then mail 
is different because there is typically no error message to the sender.

Its unclear to me whether there is much that can be shared of mime 
processing between a sip UA and a mail client/UI. Maybe not much, so 
that differences in processing logic are ok. But maybe some significant 
part can be shared, especially when exchanging info that is to be 
"rendered", such as with MESSAGE. If mime libraries can be shared, there 
is reason to keep the processing semantics the same.

	Thanks,
	Paul

> On Oct 1, 2008, at 12:51 PM, Paul Kyzivat wrote:
> 
>> Ok, ok, UNCLE!!!
>>
>> I'd still like to know if email clients need to do this two pass 
>> approach - first searching for all the references to determine if all 
>> the handling requirements can be met, and then actually doing the 
>> processing of the referenced parts?
>>
>> Also, it *is* legal for proxies to process bodies. But its obviously 
>> not required (by the protocol) for them to do so. Do we have a clue 
>> how the handling parameter applies to proxies? I assume in effect they 
>> can just ignore it and consider handling to be optional for all parts. 
>> Also, I presume a proxy that cares about body parts might want to 
>> investigate all the alternatives of a multipart/alternative, since it 
>> can't know which one the recipient will choose.
>>
>>     Thanks,
>>     Paul
>>
>> Eric Burger wrote:
>>> Agreed. And, echoing what Keith said, what Dale has done is prove 
>>> (from a Computer Science perspective) that complete evaluation of 
>>> unfettered MIME is *possible*. It is up to the implementor to figure 
>>> out whether they want to take short-cuts (and risk barfing on 
>>> legitimate messages) or do the whole thing.
>>> The point is doing the Full Monte *is* practical on small, memory and 
>>> CPU constrained devices. So the argument "We can't do the real thing 
>>> because it hurts" is provably not legitimate.
>>> On Sep 29, 2008, at 11:09 PM, Dale.Worley@comcast.net wrote:
>>>>  From: Paul Kyzivat <pkyzivat@cisco.com>
>>>>
>>>>  I agree it would be straightforward to define a rule that says one 
>>>> must
>>>>  recursively unwrap all multipart/mixed bodies in order to find other
>>>>  parts to process. But we ought to think if we really want to do that.
>>>>
>>>> What alternative rule do you propose as the meaning of
>>>> multipart/mixed?
>>>>
>>>>  Potentially this could introduce a lot of extra processing.
>>>>
>>>> That's sort of like saying that "x = 0 + 0 + 0 + 0 + 0 + 0 + 0 + 0"
>>>> involves a lot of extra processing.  Yes, it does.  But it meaning is
>>>> clear, once we define what "+" means.  We could try to outlaw that
>>>> expression and "expressions like it", but there's no sensible boundary
>>>> to enforce -- Do we ban expressions with more than five addends?  How
>>>> about more than one addend which is "0"?  Any possible solution to
>>>> this problem is worse than the problem itself.
>>>>
>>>> What I am advocating is that we explicitly abandon the attempt to
>>>> define only the situations that intuitively make sense, and instead
>>>> define a set of simple, well-defined rules that make clear what is
>>>> valid and what is not, and what the valid cases mean.  Just like we've
>>>> done with arithmetic expressions.  Otherwise we'll never escape the
>>>> swamp of trying to discern which ones make intuitive sense.
>>>>
>>>>  From: Paul Kyzivat <pkyzivat@cisco.com>
>>>>
>>>>> RFC 3459 uses multiparts in a somewhat different way that SIP does.
>>>>> In SIP, the I-D suggests that components of a multipart/alternative
>>>>> should have handling=optional and that the processor should ignore the
>>>>> handling parameter:
>>>>>
>>>>>    The UA SHOULD also set the 'handling' parameter of all the
>>>>>    body part within the 'multipart/alternative' to 'optional'
>>>>>    (the receiver will process the body parts based on the
>>>>>    handling parameter of the 'multipart/alternative' body; the
>>>>>    receiver will ignore the handling parameters of the body
>>>>>    parts).
>>>>>
>>>>>    The receiver SHOULD ignore the handling parameters of the body
>>>>>    parts within the 'multipart/ alternative'.
>>>>
>>>>  Right. But the SHOULD without qualification suggests that somebody 
>>>> might
>>>>  do otherwise, and we don't know under what circumstances that might
>>>>  happen. So if somebody sets all the parts to handling=required, it 
>>>> seems
>>>>  that the handling of the unselected parts will still be ignored.
>>>>
>>>> Yes, I see the problem there.  I'd replace that last SHOULD with MUST.
>>>> Actually, I argue that MUST is implied, as the RFCs define how
>>>> multipart/alternative is to be processed, and that algorithm does not
>>>> look at the handling parameters of components of
>>>> multipart/alternatives.
>>>>
>>>>  Suppose I want to send a MESSAGE, and I require that some form of the
>>>>  body be processed. I will offer it in two forms: text/enhanced and
>>>>  text/html. How do I encode that?
>>>>
>>>>       C-T: multipart/alternative
>>>>       C-D: render;handling=required
>>>>           C-T: text/enhanced
>>>>           C-D: render;handling=optional
>>>>           ===
>>>>           C-T: text/html
>>>>           C-D: render;handling=optional
>>>>  or
>>>>       C-T: multipart/alternative
>>>>       C-D: render;handling=required
>>>>           C-T: text/enhanced
>>>>           C-D: render;handling=required
>>>>           ===
>>>>           C-T: text/html
>>>>           C-D: render;handling=required
>>>>
>>>> C-T: multipart/alternative
>>>> C-D: render;handling=required
>>>>    C-T: text/enhanced
>>>>    ===
>>>>    C-T: text/html
>>>>
>>>> 'render' is inherited from the parent, and the handling of the
>>>> components is ignored.  We could also take it that MESSAGE implies
>>>> that the body is 'required', so the handling specification of the
>>>> parent is also optional.
>>>>
>>>>  And if I don't support either of those text types, what error do I
>>>>  return? 415? In the first case it seems a little odd to return an 
>>>> error
>>>>  if I selected a part that is optional.
>>>>
>>>> 415.  The I-D is clear that 415 is how you respond to messages which
>>>> are not processable due to a failure of these MIME tests.
>>>>
>>>>  And if I didn't require either part to be understood, would I just
>>>>  change to handling=optional for the multipart/alternative itself?
>>>>
>>>> Intuitively, I'd say that MESSAGE demands that the entire body be
>>>> processable, so handling=required is implicit for the entire body.
>>>> But assuming that we did not make such a deduction from the SIP
>>>> context of the message, if the body had handling=optional, it would
>>>> have the effect that the request could succeed even if the requester
>>>> did not understand the body.  (Hmmm...  That's another clause of the
>>>> algorithm I overlooked.)
>>>>
>>>> (Note that there are cases where understanding the body is optional.
>>>> E.g., a sipfrag of the request in a failure response.)
>>>>
>>>> Dale
>>>> _______________________________________________
>>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>>> This list is for NEW development of the core SIP Protocol
>>>> Use sip-implementors@cs.columbia.edu for questions on current sip
>>>> Use sipping@ietf.org for new developments on the application of sip
>>> ------------------------------------------------------------------------
>>> _______________________________________________
>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>> This list is for NEW development of the core SIP Protocol
>>> Use sip-implementors@cs.columbia.edu for questions on current sip
>>> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct  3 14:56:41 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5067C3A6986;
	Fri,  3 Oct 2008 14:56:41 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 839E73A6986
	for <sip@core3.amsl.com>; Fri,  3 Oct 2008 14:56:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id w9Jz7CNVsGoF for <sip@core3.amsl.com>;
	Fri,  3 Oct 2008 14:56:39 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56])
	by core3.amsl.com (Postfix) with ESMTP id 7EB783A6935
	for <sip@ietf.org>; Fri,  3 Oct 2008 14:56:39 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m93Lv5l17069; Fri, 3 Oct 2008 21:57:05 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 3 Oct 2008 16:56:54 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF198F2411@zrc2hxm0.corp.nortel.com>
In-Reply-To: <CB022A19-6DEF-4E12-A0DC-06D5628371F5@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: gruu in outbound-15 9.1
Thread-Index: Ackk6uLg+cF3ViEFQQuRhT3etDbcAQAuABoQ
References: <EE9B10212E22466DAE8D10EECAF11291@rildelhi.com>
	<5D1A7985295922448D5550C94DE291800236151C@DEEXC1U01.de.lucent.com>
	<18659.54337.452872.203497@taimen.test.fi>
	<CDF0F938-3B8C-442C-87E4-D9B319F939DB@softarmor.com>
	<18660.61663.416336.165388@taimen.test.fi>
	<D6D8CEC6-6002-4654-B3EC-309BA8EA182E@softarmor.com>
	<CB022A19-6DEF-4E12-A0DC-06D5628371F5@softarmor.com>
From: "Francois Audet" <audet@nortel.com>
To: "Dean Willis" <dean.willis@softarmor.com>
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] gruu in outbound-15 9.1
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Thanks Dean.

This text seems perfect to me. I'll deal with it in WGLC. 

> -----Original Message-----
> From: Dean Willis [mailto:dean.willis@softarmor.com] 
> Sent: Thursday, October 02, 2008 16:59
> To: Audet, Francois (SC100:3055)
> Cc: Juha Heinanen; SIP IETF
> Subject: gruu in outbound-15 9.1
> 
> >
> 
> Original text:
> 
> 
> >  If the UAC is sending a dialog-forming request, and wants all  
> > subsequent requests in the dialog to arrive over the same 
> flow, the  
> > UAC adds an 'ob' parameter to its Contact header.  
> Typically this is  
> > desirable, but it is not necessary for example if the Contact is a  
> > GRUU [I-D.ietf-sip-gruu].  The flow used for the request is 
> typically  
> > the same flow the UA registered over, but it could be a new 
> flow, for  
> > example the initial subcription dialog for the configuration  
> > framework [I-D.ietf-sipping-config-framework] needs to 
> exist before  
> > registration.
> 
> 
> Proposed text:
> 
> Typically, a UAC using the procedures of this document and 
> sending a dialog-forming request will want all subsequent 
> requests in the dialog to arrive over the same flow. If the 
> UAC is using a GRUU [I-D.ietf-sip-gruu] that was instantiated 
> using a Contact header field value that included an "ob" 
> parameter, the UAC sends teh request over the flow used for 
> registration and susequent requests will arrive over that 
> same flow. If the UAC is not using such a GRUU, then the UAC 
> adds an "ob" parameter to its Contact header field value.  
> This will cause all subsequent requests in the dialog to 
> arrive over the flow instantiated by the dialog-forming 
> request. This case is typical when the request is sent prior 
> to registration, such as in the the initial subcription 
> dialog for the configuration framework 
> [I-D.ietf-sipping-config-framework].
> 
> 
> --
> Dean
> 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Sun Oct  5 18:07:14 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 228113A687E;
	Sun,  5 Oct 2008 18:07:14 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7F2343A687E
	for <sip@core3.amsl.com>; Sun,  5 Oct 2008 18:07:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.526
X-Spam-Level: 
X-Spam-Status: No, score=-2.526 tagged_above=-999 required=5 tests=[AWL=0.073, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6WSmqvtukHdb for <sip@core3.amsl.com>;
	Sun,  5 Oct 2008 18:07:11 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id C1CB53A677D
	for <sip@ietf.org>; Sun,  5 Oct 2008 18:07:11 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9617i2Q026057
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT)
	for <sip@ietf.org>; Sun, 5 Oct 2008 20:07:45 -0500
Message-Id: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: SIP IETF <sip@ietf.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sun, 5 Oct 2008 20:07:39 -0500
X-Mailer: Apple Mail (2.929.2)
Subject: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


I'm hearing from some people that they're being forced to use Outbound  
even when there are no NATs to consider, because Outbound is the only  
way for a device to have dual registrations.

Personally, I seem to remember some systems that were doing multiple  
registrations long before Outbound, so I'm wondering who's missing  
what here, and what if anything we need to document or specify.

Thoughts?

--
Dean

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


From sip-bounces@ietf.org  Sun Oct  5 19:07:41 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1EA3D3A6837;
	Sun,  5 Oct 2008 19:07:41 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 46CDA3A677D
	for <sip@core3.amsl.com>; Sun,  5 Oct 2008 19:07:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.556
X-Spam-Level: 
X-Spam-Status: No, score=-3.556 tagged_above=-999 required=5 tests=[AWL=0.043, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Hl+eKR96Vafk for <sip@core3.amsl.com>;
	Sun,  5 Oct 2008 19:07:38 -0700 (PDT)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145])
	by core3.amsl.com (Postfix) with ESMTP id 718F73A6837
	for <sip@ietf.org>; Sun,  5 Oct 2008 19:07:38 -0700 (PDT)
Received: from shell.TheWorld.com (IDENT:105@shell01.theworld.com
	[192.74.137.71])
	by TheWorld.com (8.13.6/8.13.6) with ESMTP id m96279sI021943
	for <sip@ietf.org>; Sun, 5 Oct 2008 22:07:11 -0400
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1])
	by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id m96279CD40994212
	for <sip@ietf.org>; Sun, 5 Oct 2008 22:07:09 -0400 (EDT)
Received: (from worley@localhost)
	by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id m96279qQ41038047;
	Sun, 5 Oct 2008 22:07:09 -0400 (EDT)
Date: Sun, 5 Oct 2008 22:07:09 -0400 (EDT)
Message-Id: <200810060207.m96279qQ41038047@shell01.TheWorld.com>
To: sip@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <9BCA68EB-2AF2-4F88-A595-B4CE1ED6475B@standardstrack.com>
	(eburger@standardstrack.com)
References: <5D1A7985295922448D5550C94DE2918002196DCC@DEEXC1U01.de.lucent.com>	<48898492.7010601@ericsson.com>	<5D1A7985295922448D5550C94DE2918002196FF7@DEEXC1U01.de.lucent.com>	<4889F09B.8050407@cisco.com>
	<200809262108.m8QL8fpj34800452@shell01.TheWorld.com>
	<48E0F79B.8090402@cisco.com>
	<200809300309.m8U39jFX37113365@shell01.TheWorld.com>
	<9BCA68EB-2AF2-4F88-A595-B4CE1ED6475B@standardstrack.com>
Subject: Re: [Sip] Comments on draft-ietf-sip-body-handling-02
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

   From: Eric Burger <eburger@standardstrack.com>

   The point is doing the Full Monte *is* practical on small, memory and  
   CPU constrained devices. So the argument "We can't do the real thing  
   because it hurts" is provably not legitimate.

Though the real limitation to "doing the real thing" is programming
effort (or more exactly, finding good enough programming talent) than
the CPU/memory costs in the end-systems.  The downside of Moore's Law
is that it becomes increasingly uneconomical to pay a programmer to
spend the extra effort to write efficient code.

I once worked for a company that crammed a fully RFC 2616-compliant
HTTP server into a Z80.  Now embedded systems will give you many
megabytes without blinking.

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


From sip-bounces@ietf.org  Sun Oct  5 19:07:47 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E62BA3A69AD;
	Sun,  5 Oct 2008 19:07:46 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF65A3A69AD
	for <sip@core3.amsl.com>; Sun,  5 Oct 2008 19:07:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.559
X-Spam-Level: 
X-Spam-Status: No, score=-3.559 tagged_above=-999 required=5 tests=[AWL=0.040, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3s-A03MuvMW4 for <sip@core3.amsl.com>;
	Sun,  5 Oct 2008 19:07:45 -0700 (PDT)
Received: from TheWorld.com (pcls4.std.com [192.74.137.84])
	by core3.amsl.com (Postfix) with ESMTP id D1A623A69A9
	for <sip@ietf.org>; Sun,  5 Oct 2008 19:07:44 -0700 (PDT)
Received: from shell.TheWorld.com (IDENT:105@shell01.TheWorld.com
	[192.74.137.71])
	by TheWorld.com (8.13.6/8.13.6) with ESMTP id m9628Cho003217
	for <sip@ietf.org>; Sun, 5 Oct 2008 22:08:16 -0400
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1])
	by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id m9628CtK40847481
	for <sip@ietf.org>; Sun, 5 Oct 2008 22:08:12 -0400 (EDT)
Received: (from worley@localhost)
	by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id m9628CdL40918351;
	Sun, 5 Oct 2008 22:08:12 -0400 (EDT)
Date: Sun, 5 Oct 2008 22:08:12 -0400 (EDT)
Message-Id: <200810060208.m9628CdL40918351@shell01.TheWorld.com>
To: sip@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <48E3AA84.6010808@cisco.com> (pkyzivat@cisco.com)
References: <5D1A7985295922448D5550C94DE2918002196DCC@DEEXC1U01.de.lucent.com>	<48898492.7010601@ericsson.com>	<5D1A7985295922448D5550C94DE2918002196FF7@DEEXC1U01.de.lucent.com>	<4889F09B.8050407@cisco.com>	<200809262108.m8QL8fpj34800452@shell01.TheWorld.com>	<48E0F79B.8090402@cisco.com>	<200809300309.m8U39jFX37113365@shell01.TheWorld.com>
	<9BCA68EB-2AF2-4F88-A595-B4CE1ED6475B@standardstrack.com>
	<48E3AA84.6010808@cisco.com>
Subject: Re: [Sip] Comments on draft-ietf-sip-body-handling-02
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

   From: Paul Kyzivat <pkyzivat@cisco.com>

   I'd still like to know if email clients need to do this two pass 
   approach - first searching for all the references to determine if all 
   the handling requirements can be met, and then actually doing the 
   processing of the referenced parts?

Well, if you want to be able to process all valid MIME multipart
bodies, it seems to be unavoidable.  As far as I can tell, almost all
of the algorithm is prescribed by the RFCs.  The only specification
I've added is the subtle question of what strategy will be used to
choose from multipart/alternatives.  My first discussion some months
ago, I used the strategy "Can you choose so that the constraints are
satisfied?", which led to NP-completeness.  This version, which is
probably closer to what is intended by the RFCs, is "Make the choice
for each multipart/alternative without regard to whether it is adverse
to multiparts that contain you."

   Also, it *is* legal for proxies to process bodies. But its obviously not 
   required (by the protocol) for them to do so. Do we have a clue how the 
   handling parameter applies to proxies? I assume in effect they can just 
   ignore it and consider handling to be optional for all parts. Also, I 
   presume a proxy that cares about body parts might want to investigate 
   all the alternatives of a multipart/alternative, since it can't know 
   which one the recipient will choose.

As far as I can tell, proxies aren't allowed to reject messages
because they don't like their bodies, although I'm sure that in
specialized applications, they will.  But the interpretation of
handling parameters by such proxies will be determined by what the
"specialized application" is attempting to do; it's not in the scope
of RFCs.

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


From sip-bounces@ietf.org  Sun Oct  5 19:09:35 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0CD703A68F1;
	Sun,  5 Oct 2008 19:09:35 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E59593A68F1
	for <sip@core3.amsl.com>; Sun,  5 Oct 2008 19:09:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.562
X-Spam-Level: 
X-Spam-Status: No, score=-3.562 tagged_above=-999 required=5 tests=[AWL=0.038, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id bcpV1v2ic1GF for <sip@core3.amsl.com>;
	Sun,  5 Oct 2008 19:09:33 -0700 (PDT)
Received: from TheWorld.com (pcls1.std.com [192.74.137.141])
	by core3.amsl.com (Postfix) with ESMTP id EC4B83A677D
	for <sip@ietf.org>; Sun,  5 Oct 2008 19:09:32 -0700 (PDT)
Received: from shell.TheWorld.com (IDENT:105@shell01.theworld.com
	[192.74.137.71])
	by TheWorld.com (8.13.6/8.13.6) with ESMTP id m96292kT003638
	for <sip@ietf.org>; Sun, 5 Oct 2008 22:09:05 -0400
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1])
	by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id m96292Bp41020224
	for <sip@ietf.org>; Sun, 5 Oct 2008 22:09:02 -0400 (EDT)
Received: (from worley@localhost)
	by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id m962922l40982917;
	Sun, 5 Oct 2008 22:09:02 -0400 (EDT)
Date: Sun, 5 Oct 2008 22:09:02 -0400 (EDT)
Message-Id: <200810060209.m962922l40982917@shell01.TheWorld.com>
To: sip@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <48E22F32.8050202@cisco.com> (pkyzivat@cisco.com)
References: <200809300309.m8U39wbI37097791@shell01.TheWorld.com>
	<48E22F32.8050202@cisco.com>
Subject: Re: [Sip] Is body handling NP-complete?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

   From: Paul Kyzivat <pkyzivat@cisco.com>

   One implication of this is that body parts need to be processed twice in 
   a content-type+content-disposition+context dependent way: once to 
   extract references, and again for final effect.

That does seem to be unavoidable in the general case.  (Though every
practical case I know of can avoid two-pass processing.)

   (Hmm - is extracting of references dependent on the disposition and
   context?)

Presumably it could be, depending on the definition of how the simple
parts are to be processed.  In any case, it doesn't seem to add
complexity to the implementation to allow for it.

   If you imagine that various content types are handled by plugins, then 
   the plugins will each require two entry points - one for each of these 
   processing modes. While that is certainly possible, it might mean that 
   plugins that already exist for non-sip applications (e.g. email or html) 
   may not be reusable for sip. (I am not familiar with the content-type 
   plugins for other protocols such as email. But I presume that email 
   plugins may be useful in some cases, at least for MESSAGE.)

   Do plugins for email have this complexity?

Since two-pass processing is required for processing the full set of
MIME constructions, plugins for e-mail processing would theoretically
have to allow this.  I've never heard of any that do.

   An alternative is to do all the processing in one pass, and then at the 
   end check if all body parts have been processed. BUT that means all the 
   side effects of processing will have been realized before discovering 
   that the message is in error. That is certainly not ideal.

It wouldn't be correct, either.  How would you process a
multipart/alternative?

   > This example also points out that the requirement that references
   > appear before the parts they reference is needed to make the problem
   > tractable.  Otherwise, there could be circular dependencies between
   > the choices for different multipart/alternatives, which might be
   > impossible to analyze by an algorithm as simple as a tree-walk.

   This requirement is satisfied by lots of simple cases. But it means that 
   it is impossible to describe any kind of circular structure. I'm not 
   familiar enough with the use of multipart/related to know if it is a 
   restriction that is tolerable there. Perhaps someone can comment on that.

The requirement is in the current I-D:

   8.2.  UA Behavior to Generate References to Message Bodies

   UAs MUST only include forward references in the SIP messages they
   generate.

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


From sip-bounces@ietf.org  Sun Oct  5 22:40:32 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A43D03A68F3;
	Sun,  5 Oct 2008 22:40:32 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EF7013A68F3
	for <sip@core3.amsl.com>; Sun,  5 Oct 2008 22:40:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Trm6JjNFrkfr for <sip@core3.amsl.com>;
	Sun,  5 Oct 2008 22:40:31 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id B5C973A6885
	for <sip@ietf.org>; Sun,  5 Oct 2008 22:40:30 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m965exTL021015; Mon, 6 Oct 2008 08:41:01 +0300
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 6 Oct 2008 08:41:00 +0300
Received: from vaebe106.NOE.Nokia.com ([10.160.244.67]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 6 Oct 2008 08:41:00 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 08:40:59 +0300
Message-ID: <7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
In-Reply-To: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AcknT/49aMGLa8U4QKGYShAeQaIa2AAJAB6w
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
From: <Erkki.Koivusalo@nokia.com>
To: <dean.willis@softarmor.com>, <sip@ietf.org>
X-OriginalArrivalTime: 06 Oct 2008 05:41:00.0744 (UTC)
	FILETIME=[1D44C480:01C92776]
X-Nokia-AV: Clean
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi,

Problem with dual registrations without Outbound comes
with forking. When a device registers itself twice with
different Contact addresses, it will receive every request
destined to the AOR twice if the server implements parallel
forking or if the device rejects the first forked request.
 
On the other hand if the contact addresses are the same within
the dual registrations, without Outbound that is just a
registration refresh instead of dual registration, correct ?

Please tell if I miss some point of specified behaviour here.

For instance 3GPP is considering using Outbound to solve
this problem of multiple registrations even if there would 
not be any NATs in the access network.

---
A long time ago I posted a long email suggesting Outbound
to be split to two drafts, addressing two different problems:

- One that specifies the keepalive behaviour (needed for NATs)
- One that specifies multiple registration behaviour
  (needed for increased reliability) 

But it was not very popular suggestion and did not get
many responses. Perhaps the suggestion was raised too late,
at that time many were just waiting to get Outbound frozen
and published as RFC.

Regards,

Erkki

>-----Original Message-----
>From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
>Behalf Of ext Dean Willis
>Sent: 06.October.2008 04:08
>To: SIP IETF
>Subject: [Sip] Dual registration without Outbound
>
>
>I'm hearing from some people that they're being forced to use 
>Outbound  
>even when there are no NATs to consider, because Outbound is the only  
>way for a device to have dual registrations.
>
>Personally, I seem to remember some systems that were doing multiple  
>registrations long before Outbound, so I'm wondering who's missing  
>what here, and what if anything we need to document or specify.
>
>Thoughts?
>
>--
>Dean
>
>_______________________________________________
>Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>This list is for NEW development of the core SIP Protocol
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sipping@ietf.org for new developments on the application of sip
>
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Sun Oct  5 22:50:55 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 32C533A6910;
	Sun,  5 Oct 2008 22:50:55 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 72B773A67AD
	for <sip@core3.amsl.com>; Sun,  5 Oct 2008 22:50:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gUypuoBsqdhH for <sip@core3.amsl.com>;
	Sun,  5 Oct 2008 22:50:53 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id 8ABE03A63D3
	for <sip@ietf.org>; Sun,  5 Oct 2008 22:50:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 5C2F11EC2CE;
	Mon,  6 Oct 2008 08:51:28 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vbR7PH3W3OBF; Mon,  6 Oct 2008 08:51:26 +0300 (EEST)
Received: from taimen (h162192.gprs.dnafinland.fi [87.93.162.192])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Mon,  6 Oct 2008 08:51:26 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 79420AC054; Mon,  6 Oct 2008 08:51:19 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18665.42838.994529.377867@taimen.test.fi>
Date: Mon, 6 Oct 2008 08:51:18 +0300
To: <Erkki.Koivusalo@nokia.com>
In-Reply-To: <7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Erkki.Koivusalo@nokia.com writes:

 > Problem with dual registrations without Outbound comes
 > with forking. When a device registers itself twice with
 > different Contact addresses, it will receive every request
 > destined to the AOR twice if the server implements parallel
 > forking or if the device rejects the first forked request.

erkki,

i thought that dean meant with "dual registration" registering with two
different registrars (e.g. two srv records for the same domain).  in
that case, your problem does not occur if proxies are also paired with
the two registrars.

 > A long time ago I posted a long email suggesting Outbound
 > to be split to two drafts, addressing two different problems:
 > 
 > - One that specifies the keepalive behaviour (needed for NATs)
 > - One that specifies multiple registration behaviour
 >   (needed for increased reliability) 

and third draft should be about connection re-use.  

if iesg or whoever still exists whose task is to keep rfcs sane, it
should definitely bounce outbound i-d back to the working group so that
it can do the right thing rather that rushing outbound that only
includes application specific solution to these generic problems.

-- juha

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


From sip-bounces@ietf.org  Sun Oct  5 22:58:57 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5773028C0DE;
	Sun,  5 Oct 2008 22:58:57 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5FEBF3A6A30
	for <sip@core3.amsl.com>; Sun,  5 Oct 2008 22:58:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.299
X-Spam-Level: 
X-Spam-Status: No, score=-5.299 tagged_above=-999 required=5 tests=[AWL=1.300, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id oe5aUIAw97iL for <sip@core3.amsl.com>;
	Sun,  5 Oct 2008 22:58:55 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 96D873A6A2B
	for <sip@ietf.org>; Sun,  5 Oct 2008 22:58:55 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m965wr2N000963 for <sip@ietf.org>; Mon, 6 Oct 2008 00:59:28 -0500
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 6 Oct 2008 08:59:25 +0300
Received: from vaebe104.NOE.Nokia.com ([10.160.244.59]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 6 Oct 2008 08:59:25 +0300
Received: from [172.21.41.143] ([172.21.41.143]) by vaebe104.NOE.Nokia.com
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 6 Oct 2008 08:59:25 +0300
From: Jari Urpalainen <jari.urpalainen@nokia.com>
To: sip@ietf.org
In-Reply-To: <20081003101501.A1C843A69D6@core3.amsl.com>
References: <20081003101501.A1C843A69D6@core3.amsl.com>
Date: Mon, 06 Oct 2008 08:59:25 +0300
Message-Id: <1223272765.27467.8.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.3.1 
X-OriginalArrivalTime: 06 Oct 2008 05:59:25.0479 (UTC)
	FILETIME=[AFBDF370:01C92778]
X-Nokia-AV: Clean
Subject: Re: [Sip] I-D Action:draft-ietf-sip-xcapevent-04.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi !

Spencer Dawkins made an gen-ART review of this i-d during the ietf LC,
and those comments were addressed in this update. Details of what has
changed and why can be seen from
<http://www.ietf.org/mail-archive/web/ietf/current/msg53276.html>

br, Jari


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


From sip-bounces@ietf.org  Sun Oct  5 23:00:51 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2B27328C106;
	Sun,  5 Oct 2008 23:00:51 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AF4F628C0F0
	for <sip@core3.amsl.com>; Sun,  5 Oct 2008 23:00:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.186
X-Spam-Level: 
X-Spam-Status: No, score=-6.186 tagged_above=-999 required=5 tests=[AWL=0.063, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id cnmFcEej1-N4 for <sip@core3.amsl.com>;
	Sun,  5 Oct 2008 23:00:48 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 51FD228C0FA
	for <sip@ietf.org>; Sun,  5 Oct 2008 23:00:40 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	AA04520606; Mon,  6 Oct 2008 08:01:14 +0200 (CEST)
X-AuditID: c1b4fb3c-ae8cfbb0000015b5-6f-48e9a9aa228e
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	8B93220248; Mon,  6 Oct 2008 08:01:14 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 08:01:13 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 08:01:13 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se>
In-Reply-To: <18665.42838.994529.377867@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Acknd5q+xUhTeVWsR/awM/lvX3PoLQAAM9jA
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>,
	<Erkki.Koivusalo@nokia.com>
X-OriginalArrivalTime: 06 Oct 2008 06:01:13.0961 (UTC)
	FILETIME=[F066FD90:01C92778]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi,

The 3GPP case actually talks about multiple registrations with the SAME
registrar. 

But, I don't think there will be a forking problem, because I assume the
instance-id will still be the same for all registrations from the same
UA.

Regards,

Christer 

-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Juha Heinanen
Sent: Monday, October 06, 2008 8:51 AM
To: Erkki.Koivusalo@nokia.com
Cc: sip@ietf.org; dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound

Erkki.Koivusalo@nokia.com writes:

 > Problem with dual registrations without Outbound comes  > with
forking. When a device registers itself twice with  > different Contact
addresses, it will receive every request  > destined to the AOR twice if
the server implements parallel  > forking or if the device rejects the
first forked request.

erkki,

i thought that dean meant with "dual registration" registering with two
different registrars (e.g. two srv records for the same domain).  in
that case, your problem does not occur if proxies are also paired with
the two registrars.

 > A long time ago I posted a long email suggesting Outbound  > to be
split to two drafts, addressing two different problems:
 >
 > - One that specifies the keepalive behaviour (needed for NATs)  > -
One that specifies multiple registration behaviour
 >   (needed for increased reliability) 

and third draft should be about connection re-use.  

if iesg or whoever still exists whose task is to keep rfcs sane, it
should definitely bounce outbound i-d back to the working group so that
it can do the right thing rather that rushing outbound that only
includes application specific solution to these generic problems.

-- juha

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


From sip-bounces@ietf.org  Sun Oct  5 23:05:02 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 429B028C0F8;
	Sun,  5 Oct 2008 23:05:02 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A207828C0F8
	for <sip@core3.amsl.com>; Sun,  5 Oct 2008 23:05:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SvhKe166bxRX for <sip@core3.amsl.com>;
	Sun,  5 Oct 2008 23:05:00 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id CAAF928C0F1
	for <sip@ietf.org>; Sun,  5 Oct 2008 23:04:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 7DB951EC2CE;
	Mon,  6 Oct 2008 09:05:31 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0ff8k2x7P1VQ; Mon,  6 Oct 2008 09:05:29 +0300 (EEST)
Received: from taimen (h162192.gprs.dnafinland.fi [87.93.162.192])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Mon,  6 Oct 2008 09:05:29 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 3206FAC054; Mon,  6 Oct 2008 09:05:24 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18665.43684.176244.988653@taimen.test.fi>
Date: Mon, 6 Oct 2008 09:05:24 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > The 3GPP case actually talks about multiple registrations with the SAME
 > registrar. 

like registering over 3g and wlan?

 > But, I don't think there will be a forking problem, because I assume the
 > instance-id will still be the same for all registrations from the same
 > UA.

in the above case, i would definitely want inbound call to be forked.

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


From sip-bounces@ietf.org  Sun Oct  5 23:14:21 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B212D28C119;
	Sun,  5 Oct 2008 23:14:21 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E69E028C119
	for <sip@core3.amsl.com>; Sun,  5 Oct 2008 23:14:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id iX1BE-7dLdoN for <sip@core3.amsl.com>;
	Sun,  5 Oct 2008 23:14:19 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id C69B63A6A2B
	for <sip@ietf.org>; Sun,  5 Oct 2008 23:14:18 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com
	[10.160.244.31])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m966EYDx003541; Mon, 6 Oct 2008 09:14:51 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 6 Oct 2008 09:14:29 +0300
Received: from vaebe106.NOE.Nokia.com ([10.160.244.67]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 6 Oct 2008 09:14:29 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 09:14:27 +0300
Message-ID: <7A726F54F791494C8D8C87F13736E80EEC2237@vaebe106.NOE.Nokia.com>
In-Reply-To: <18665.42838.994529.377867@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Acknd5hKOXhKvpI6QRqIOrHVej+b6gAAYjng
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
From: <Erkki.Koivusalo@nokia.com>
To: <jh@tutpro.com>
X-OriginalArrivalTime: 06 Oct 2008 06:14:29.0225 (UTC)
	FILETIME=[CA6AA590:01C9277A]
X-Nokia-AV: Clean
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>i thought that dean meant with "dual registration" registering with two
>different registrars (e.g. two srv records for the same domain).

Not sure, perhaps. Hope that Dean will clarify what he meant and
whether I misunderstood his terminology.

>that case, your problem does not occur if proxies are also paired with
>the two registrars.

But even in that case I can not follow. Yes I see that is possible
without Outbound but on the other hand I fail to see Outbound providing
any added value for such a setup.

Or is the point exactly that :

- without Outbound you need multiple different registrars (having
different
  srv records for them) for such dual registration ?

- but with Outbound you could do similar thing with one single registrar
  while having multiple (or multihomed) proxies ?

Regards,

Erkki

>-----Original Message-----
>From: ext Juha Heinanen [mailto:jh@tutpro.com] 
>Sent: 06.October.2008 08:51
>To: Koivusalo Erkki (Nokia-D/Helsinki)
>Cc: dean.willis@softarmor.com; sip@ietf.org
>Subject: Re: [Sip] Dual registration without Outbound
>
>Erkki.Koivusalo@nokia.com writes:
>
> > Problem with dual registrations without Outbound comes
> > with forking. When a device registers itself twice with
> > different Contact addresses, it will receive every request
> > destined to the AOR twice if the server implements parallel
> > forking or if the device rejects the first forked request.
>
>erkki,
>
>i thought that dean meant with "dual registration" registering with two
>different registrars (e.g. two srv records for the same domain).  in
>that case, your problem does not occur if proxies are also paired with
>the two registrars.
>
> > A long time ago I posted a long email suggesting Outbound
> > to be split to two drafts, addressing two different problems:
> > 
> > - One that specifies the keepalive behaviour (needed for NATs)
> > - One that specifies multiple registration behaviour
> >   (needed for increased reliability) 
>
>and third draft should be about connection re-use.  
>
>if iesg or whoever still exists whose task is to keep rfcs sane, it
>should definitely bounce outbound i-d back to the working group so that
>it can do the right thing rather that rushing outbound that only
>includes application specific solution to these generic problems.
>
>-- juha
>
>
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Sun Oct  5 23:23:10 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B9AFB3A69EF;
	Sun,  5 Oct 2008 23:23:10 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8899E3A69BB
	for <sip@core3.amsl.com>; Sun,  5 Oct 2008 23:23:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 11QFJyM4GXiM for <sip@core3.amsl.com>;
	Sun,  5 Oct 2008 23:23:08 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id AF1B53A67ED
	for <sip@ietf.org>; Sun,  5 Oct 2008 23:23:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 59F0E1EC2CE;
	Mon,  6 Oct 2008 09:23:27 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id cWiewkASxyc3; Mon,  6 Oct 2008 09:23:25 +0300 (EEST)
Received: from taimen (h162192.gprs.dnafinland.fi [87.93.162.192])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Mon,  6 Oct 2008 09:23:25 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id C996BAC054; Mon,  6 Oct 2008 09:23:19 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18665.44759.799781.864060@taimen.test.fi>
Date: Mon, 6 Oct 2008 09:23:19 +0300
To: <Erkki.Koivusalo@nokia.com>
In-Reply-To: <7A726F54F791494C8D8C87F13736E80EEC2237@vaebe106.NOE.Nokia.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<7A726F54F791494C8D8C87F13736E80EEC2237@vaebe106.NOE.Nokia.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Erkki.Koivusalo@nokia.com writes:

 > But even in that case I can not follow. Yes I see that is possible
 > without Outbound but on the other hand I fail to see Outbound providing
 > any added value for such a setup.

i'm not claiming that outbound gives any additional value.  it would
have given if it had forced dual registration when there is two outbound
proxies in the set.

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


From sip-bounces@ietf.org  Sun Oct  5 23:35:16 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E5E0C3A6967;
	Sun,  5 Oct 2008 23:35:15 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0FF873A6903
	for <sip@core3.amsl.com>; Sun,  5 Oct 2008 23:35:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.191
X-Spam-Level: 
X-Spam-Status: No, score=-6.191 tagged_above=-999 required=5 tests=[AWL=0.058, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5WHM3-GHH9oB for <sip@core3.amsl.com>;
	Sun,  5 Oct 2008 23:35:14 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 2C3BE3A6967
	for <sip@ietf.org>; Sun,  5 Oct 2008 23:35:13 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	6E0B2205FC; Mon,  6 Oct 2008 08:35:48 +0200 (CEST)
X-AuditID: c1b4fb3c-ab0c8bb0000015b5-e3-48e9b1c4e862
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	4AF94205AE; Mon,  6 Oct 2008 08:35:48 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 08:35:47 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 08:35:47 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
In-Reply-To: <18665.43684.176244.988653@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckneYt+FGiLAeCnQz2ImchdoO+5dwAA7//Q
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com><18665.42838.994529.377867@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se>
	<18665.43684.176244.988653@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 06 Oct 2008 06:35:47.0644 (UTC)
	FILETIME=[C469E7C0:01C9277D]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>The 3GPP case actually talks about multiple registrations with the
SAME  > registrar. 
>
>like registering over 3g and wlan?

Yes, for example.

>>But, I don't think there will be a forking problem, because I assume
the instance-id will still be the same for all 
>>registrations from the same UA.
>
>in the above case, i would definitely want inbound call to be forked.

If you want to do that you simply register the same AoR twice using
basic 3261 registration, without Outbound, and the inbound call will be
forked. 

Regards,

Christer

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


From sip-bounces@ietf.org  Sun Oct  5 23:35:32 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AC4DF28C0F7;
	Sun,  5 Oct 2008 23:35:32 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 296CF3A69BB
	for <sip@core3.amsl.com>; Sun,  5 Oct 2008 23:35:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.53
X-Spam-Level: 
X-Spam-Status: No, score=-2.53 tagged_above=-999 required=5 tests=[AWL=0.069, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YTLWeWkTpfgy for <sip@core3.amsl.com>;
	Sun,  5 Oct 2008 23:35:31 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 415C23A6A35
	for <sip@ietf.org>; Sun,  5 Oct 2008 23:35:31 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m966a4Tw027579
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Mon, 6 Oct 2008 01:36:06 -0500
Message-Id: <D596900A-17A0-41CE-B675-35D327C21D83@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: <Erkki.Koivusalo@nokia.com>
In-Reply-To: <7A726F54F791494C8D8C87F13736E80EEC2237@vaebe106.NOE.Nokia.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 6 Oct 2008 01:35:59 -0500
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<7A726F54F791494C8D8C87F13736E80EEC2237@vaebe106.NOE.Nokia.com>
X-Mailer: Apple Mail (2.929.2)
Cc: sip@ietf.org
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 6, 2008, at 1:14 AM, <Erkki.Koivusalo@nokia.com> wrote:

>
> Hi,
>
>> i thought that dean meant with "dual registration" registering with  
>> two
>> different registrars (e.g. two srv records for the same domain).
>
> Not sure, perhaps. Hope that Dean will clarify what he meant and
> whether I misunderstood his terminology.

I wish I knew what I meant, actually.

The case I was asked about was in 3GPP-type networks. The one I'm  
familiar with is registering to two different proxies, as Juha  
described.

Apparently they are not the same.

Does IMS really need for a single UA to have two different  
registrations with one registrar, and for the requests to that UA to  
not be forked?

--
Dean

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


From sip-bounces@ietf.org  Sun Oct  5 23:40:23 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 05FA528C138;
	Sun,  5 Oct 2008 23:40:23 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9A0A33A6A46
	for <sip@core3.amsl.com>; Sun,  5 Oct 2008 23:40:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.533
X-Spam-Level: 
X-Spam-Status: No, score=-2.533 tagged_above=-999 required=5 tests=[AWL=0.066, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id sN7BK5wjegue for <sip@core3.amsl.com>;
	Sun,  5 Oct 2008 23:40:20 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 97B3E3A690B
	for <sip@ietf.org>; Sun,  5 Oct 2008 23:40:20 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m966esuf027646
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Mon, 6 Oct 2008 01:40:55 -0500
Message-Id: <30D3B985-E61D-45B1-8819-C82EC338E73D@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: jh@tutpro.com (Juha Heinanen)
In-Reply-To: <18665.44759.799781.864060@taimen.test.fi>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 6 Oct 2008 01:40:49 -0500
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<7A726F54F791494C8D8C87F13736E80EEC2237@vaebe106.NOE.Nokia.com>
	<18665.44759.799781.864060@taimen.test.fi>
X-Mailer: Apple Mail (2.929.2)
Cc: sip@ietf.org
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 6, 2008, at 1:23 AM, Juha Heinanen wrote:

> Erkki.Koivusalo@nokia.com writes:
>
>> But even in that case I can not follow. Yes I see that is possible
>> without Outbound but on the other hand I fail to see Outbound  
>> providing
>> any added value for such a setup.
>
> i'm not claiming that outbound gives any additional value.  it would
> have given if it had forced dual registration when there is two  
> outbound
> proxies in the set.
>

Outbound-15 4.2.1 says:

For each outbound proxy URI in the set, the UAC SHOULD send a REGISTER  
request using this URI as the default outbound proxy. (Alternatively,  
the UA could limit the number of flows formed to conserve battery  
power, for example). If the set has more than one URI, the UAC MUST  
send a REGISTER request to at least two of the default outbound  
proxies from the set.

As far as I can tell, that means that the UAC must dual register when  
there are two proxies.

Section 3.4 of Outbound, BTW, talks about how to dual-register with  
one registrar WITHOUT outbound.
--
Dean


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


From sip-bounces@ietf.org  Sun Oct  5 23:43:03 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B3C9128C148;
	Sun,  5 Oct 2008 23:43:03 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9A3E328C160
	for <sip@core3.amsl.com>; Sun,  5 Oct 2008 23:43:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id r1vEkXc2rqsO for <sip@core3.amsl.com>;
	Sun,  5 Oct 2008 23:43:00 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id A21DD28C13B
	for <sip@ietf.org>; Sun,  5 Oct 2008 23:43:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 04C141EC2CE;
	Mon,  6 Oct 2008 09:43:33 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id TYj-paKQDTOh; Mon,  6 Oct 2008 09:43:31 +0300 (EEST)
Received: from taimen (h162192.gprs.dnafinland.fi [87.93.162.192])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Mon,  6 Oct 2008 09:43:31 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id D1004AC054; Mon,  6 Oct 2008 09:43:25 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18665.45965.827982.821183@taimen.test.fi>
Date: Mon, 6 Oct 2008 09:43:25 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > If you want to do that you simply register the same AoR twice using
 > basic 3261 registration, without Outbound, and the inbound call will be
 > forked. 

are you saying that if i use outbound, then the inbound call will NOT get
forked (which would be very bad)?

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


From sip-bounces@ietf.org  Sun Oct  5 23:46:07 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0002A3A6A46;
	Sun,  5 Oct 2008 23:46:06 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 04DC83A69AB
	for <sip@core3.amsl.com>; Sun,  5 Oct 2008 23:46:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.196
X-Spam-Level: 
X-Spam-Status: No, score=-6.196 tagged_above=-999 required=5 tests=[AWL=0.053, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ss27bwgJ5QnV for <sip@core3.amsl.com>;
	Sun,  5 Oct 2008 23:46:05 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 28EAE3A6A46
	for <sip@ietf.org>; Sun,  5 Oct 2008 23:46:05 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	B4639207FD; Mon,  6 Oct 2008 08:46:39 +0200 (CEST)
X-AuditID: c1b4fb3c-ab0c8bb0000015b5-bf-48e9b44f8940
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	9A8CA20733; Mon,  6 Oct 2008 08:46:39 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 08:46:02 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 08:46:02 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F88E@esealmw113.eemea.ericsson.se>
In-Reply-To: <D596900A-17A0-41CE-B675-35D327C21D83@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Acknfeoon3UbegcbTr2F1FbVJj0BQAAAHQxQ
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com><18665.42838.994529.377867@taimen.test.fi><7A726F54F791494C8D8C87F13736E80EEC2237@vaebe106.NOE.Nokia.com>
	<D596900A-17A0-41CE-B675-35D327C21D83@softarmor.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Dean Willis" <dean.willis@softarmor.com>,
	<Erkki.Koivusalo@nokia.com>
X-OriginalArrivalTime: 06 Oct 2008 06:46:02.0328 (UTC)
	FILETIME=[32CB3D80:01C9277F]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>The case I was asked about was in 3GPP-type networks. The one I'm
familiar with is registering to two different proxies,
>as Juha described.
>
>Apparently they are not the same.
>
>Does IMS really need for a single UA to have two different
registrations with one registrar, and for the requests to that
>UA to not be forked?

I don't have the exact 3gpp requirement in front of me, but in my
understanding the answer is Yes. And, AFAIU it has been decided to use
the Outbound mechanism for that.

I will take a look whether it would require any changes to the Outbound
spec, but at the moment I can't think of any. 

Keep-alives will not be sent in non-NAT scenarios, so I guess one
question is whether the Outbound spec assumes there are always NATs, and
therefor always requires keep-alives for Outbound flows.

Regards,

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


From sip-bounces@ietf.org  Sun Oct  5 23:49:57 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7571528C18E;
	Sun,  5 Oct 2008 23:49:57 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0562128C14E
	for <sip@core3.amsl.com>; Sun,  5 Oct 2008 23:49:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.2
X-Spam-Level: 
X-Spam-Status: No, score=-6.2 tagged_above=-999 required=5 tests=[AWL=0.050,
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6kVFck3hIqpq for <sip@core3.amsl.com>;
	Sun,  5 Oct 2008 23:49:55 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 2DE5628C172
	for <sip@ietf.org>; Sun,  5 Oct 2008 23:49:55 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	BFCFB208C0; Mon,  6 Oct 2008 08:50:29 +0200 (CEST)
X-AuditID: c1b4fb3c-ab0c8bb0000015b5-1e-48e9b535f3cd
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	A68F12086E; Mon,  6 Oct 2008 08:50:29 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 08:50:28 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 08:50:28 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
In-Reply-To: <18665.45965.827982.821183@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AcknfuAM4TS2TF1vTb+WXHtYzHGSowAAHNrA
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com><18665.42838.994529.377867@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se><18665.43684.176244.988653@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 06 Oct 2008 06:50:28.0976 (UTC)
	FILETIME=[D1BA7F00:01C9277F]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>If you want to do that you simply register the same AoR twice using
basic 3261 registration, without Outbound, and the >>inbound call will
be forked. 
>
>are you saying that if i use outbound, then the inbound call will NOT
get forked (which would be very bad)?

I thought the whole idea of outbound was that the registrar chooses ONE
flow, and switches to another flow is the previous doesn't work. But, it
does not fork onto multiple flows.

Or, have I missunderstood everything???

Regards,

Christer

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


From sip-bounces@ietf.org  Sun Oct  5 23:54:03 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0F95028C1A0;
	Sun,  5 Oct 2008 23:54:03 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 282F728C1A7
	for <sip@core3.amsl.com>; Sun,  5 Oct 2008 23:54:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.203
X-Spam-Level: 
X-Spam-Status: No, score=-6.203 tagged_above=-999 required=5 tests=[AWL=0.046, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id kFcbLyiIH3TE for <sip@core3.amsl.com>;
	Sun,  5 Oct 2008 23:54:01 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id BE92E28C0F1
	for <sip@ietf.org>; Sun,  5 Oct 2008 23:54:00 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	4D9DA20336; Mon,  6 Oct 2008 08:54:35 +0200 (CEST)
X-AuditID: c1b4fb3e-a7e83bb000007a96-d7-48e9b62bdf49
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	3048D20541; Mon,  6 Oct 2008 08:54:35 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 08:54:34 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 08:54:34 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AcknfuAM4TS2TF1vTb+WXHtYzHGSowAAHNrAAAA0lFA=
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com><18665.42838.994529.377867@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se><18665.43684.176244.988653@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 06 Oct 2008 06:54:34.0515 (UTC)
	FILETIME=[6414C630:01C92780]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Subclause 3.1 says the following:

"When a proxy goes to route a message to a UA for which it has a
   binding, it can use any one of the flows on which a successful
   registration has been completed.  A failure to deliver a request on a
   particular flow can be tried again on an alternate flow.  Proxies can
   determine which flows go to the same UA by comparing the
instance-id."

Note that the text says "can use ONE of the flows". So, to me that
doesn't mean that the request will be forked on multiple flows.

Regards,

Christer 

-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Christer Holmberg
Sent: Monday, October 06, 2008 9:50 AM
To: Juha Heinanen
Cc: sip@ietf.org; dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound


Hi, 

>>If you want to do that you simply register the same AoR twice using
basic 3261 registration, without Outbound, and the >>inbound call will
be forked. 
>
>are you saying that if i use outbound, then the inbound call will NOT
get forked (which would be very bad)?

I thought the whole idea of outbound was that the registrar chooses ONE
flow, and switches to another flow is the previous doesn't work. But, it
does not fork onto multiple flows.

Or, have I missunderstood everything???

Regards,

Christer

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


From sip-bounces@ietf.org  Sun Oct  5 23:57:06 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D710F28C1B2;
	Sun,  5 Oct 2008 23:57:06 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6193628C1B2
	for <sip@core3.amsl.com>; Sun,  5 Oct 2008 23:57:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BiO693i1tFg3 for <sip@core3.amsl.com>;
	Sun,  5 Oct 2008 23:57:05 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id 76DB828C1A7
	for <sip@ietf.org>; Sun,  5 Oct 2008 23:57:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 99D471EC2CE;
	Mon,  6 Oct 2008 09:57:40 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Gana69WYSeBQ; Mon,  6 Oct 2008 09:57:38 +0300 (EEST)
Received: from taimen (h162192.gprs.dnafinland.fi [87.93.162.192])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Mon,  6 Oct 2008 09:57:38 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id A9CE1AC054; Mon,  6 Oct 2008 09:57:33 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18665.46813.666160.483955@taimen.test.fi>
Date: Mon, 6 Oct 2008 09:57:33 +0300
To: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <30D3B985-E61D-45B1-8819-C82EC338E73D@softarmor.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<7A726F54F791494C8D8C87F13736E80EEC2237@vaebe106.NOE.Nokia.com>
	<18665.44759.799781.864060@taimen.test.fi>
	<30D3B985-E61D-45B1-8819-C82EC338E73D@softarmor.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Dean Willis writes:

 > Outbound-15 4.2.1 says:
 > 
 > For each outbound proxy URI in the set, the UAC SHOULD send a REGISTER  
 > request using this URI as the default outbound proxy. (Alternatively,  
 > the UA could limit the number of flows formed to conserve battery  
 > power, for example). If the set has more than one URI, the UAC MUST  
 > send a REGISTER request to at least two of the default outbound  
 > proxies from the set.

i thought that i lost this battle, but it is a nice surprise that the
text has been changed and with two proxies in the set, ua MUST register
with both.

now if the ua has two network interfaces (3g and wlan, for example) and
the user want to use both of them simultaneously, is it so that inbound call
gets forked?

and further, is there any text anywhere forcing the ua to register both
of its contacts with both proxies?

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


From sip-bounces@ietf.org  Sun Oct  5 23:58:38 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B907928C1BF;
	Sun,  5 Oct 2008 23:58:38 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BCC8D28C1C7
	for <sip@core3.amsl.com>; Sun,  5 Oct 2008 23:58:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id iATH6iX467vj for <sip@core3.amsl.com>;
	Sun,  5 Oct 2008 23:58:36 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id E592028C1BF
	for <sip@ietf.org>; Sun,  5 Oct 2008 23:58:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 12D6C1EC2CE;
	Mon,  6 Oct 2008 09:59:11 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OJvAhGj6uNCq; Mon,  6 Oct 2008 09:59:09 +0300 (EEST)
Received: from taimen (h162192.gprs.dnafinland.fi [87.93.162.192])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Mon,  6 Oct 2008 09:59:09 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 85866AC054; Mon,  6 Oct 2008 09:59:03 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18665.46903.521238.719598@taimen.test.fi>
Date: Mon, 6 Oct 2008 09:59:03 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > I thought the whole idea of outbound was that the registrar chooses ONE
 > flow, and switches to another flow is the previous doesn't work. But, it
 > does not fork onto multiple flows.

yes, but if the UA has two contacts, e.g. wlan and 3g, as i asked in the
previous post?

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


From sip-bounces@ietf.org  Mon Oct  6 00:03:44 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C063D28C1D2;
	Mon,  6 Oct 2008 00:03:44 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6908128C1D2
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 00:03:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id cDFTH8sipkPl for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 00:03:42 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id 89E0A28C1CD
	for <sip@ietf.org>; Mon,  6 Oct 2008 00:03:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id AA7361EC2CE;
	Mon,  6 Oct 2008 10:04:17 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id u-ACAQ3KflLM; Mon,  6 Oct 2008 10:04:12 +0300 (EEST)
Received: from taimen (h162192.gprs.dnafinland.fi [87.93.162.192])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Mon,  6 Oct 2008 10:04:12 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 68A2EAC054; Mon,  6 Oct 2008 10:04:07 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18665.47207.397605.244480@taimen.test.fi>
Date: Mon, 6 Oct 2008 10:04:07 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > Subclause 3.1 says the following:
 > 
 > "When a proxy goes to route a message to a UA for which it has a
 >    binding, it can use any one of the flows on which a successful
 >    registration has been completed.  A failure to deliver a request on a
 >    particular flow can be tried again on an alternate flow.  Proxies can
 >    determine which flows go to the same UA by comparing the
 > instance-id."
 > 
 > Note that the text says "can use ONE of the flows". So, to me that
 > doesn't mean that the request will be forked on multiple flows.

christer,

that makes sense, if both registrations use the same contact, but not,
if UA registers with two different contacts.  in that case, there MUST
be four registrations, two via both ob proxies and inbound call MUST get
forked.

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


From sip-bounces@ietf.org  Mon Oct  6 00:06:23 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CA8DC28C1D6;
	Mon,  6 Oct 2008 00:06:23 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8ECE528C1CD
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 00:06:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.206
X-Spam-Level: 
X-Spam-Status: No, score=-6.206 tagged_above=-999 required=5 tests=[AWL=0.043, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id y+jyvYwDeYXg for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 00:06:21 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 856BF28C1D3
	for <sip@ietf.org>; Mon,  6 Oct 2008 00:06:21 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	DA6A12069C; Mon,  6 Oct 2008 09:06:55 +0200 (CEST)
X-AuditID: c1b4fb3e-a8684bb000007a96-f5-48e9b90f6b8c
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	BF29720569; Mon,  6 Oct 2008 09:06:55 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 09:06:54 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 09:06:54 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
In-Reply-To: <18665.47207.397605.244480@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckngcBxvMiWn9iKTAqnvd0LT6S1dwAABzpg
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com><18665.42838.994529.377867@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se><18665.43684.176244.988653@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 06 Oct 2008 07:06:54.0974 (UTC)
	FILETIME=[1D6DD9E0:01C92782]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 


 > Subclause 3.1 says the following:
 >
 > "When a proxy goes to route a message to a UA for which it has a
 >    binding, it can use any one of the flows on which a successful
 >    registration has been completed.  A failure to deliver a request
on a
 >    particular flow can be tried again on an alternate flow.  Proxies
can
 >    determine which flows go to the same UA by comparing the
 > instance-id."
 >
 > Note that the text says "can use ONE of the flows". So, to me that  >
doesn't mean that the request will be forked on multiple flows.
>
>christer,
>
>that makes sense, if both registrations use the same contact, but not,
if UA registers with two different contacts.  in 
>that case, there MUST be four registrations, two via both ob proxies
and inbound call MUST get forked.

I don't see any mentioning of the contact in the text above - it only
talks about instance-id.

Regards,

Christer

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


From sip-bounces@ietf.org  Mon Oct  6 00:18:27 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6258E28C1D3;
	Mon,  6 Oct 2008 00:18:27 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 697C428C1D3
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 00:18:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 92-0bZtQyDOx for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 00:18:22 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id 8AE0128C0E0
	for <sip@ietf.org>; Mon,  6 Oct 2008 00:18:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 6B5481EC2CE;
	Mon,  6 Oct 2008 10:18:47 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nQS27lGMSZ9I; Mon,  6 Oct 2008 10:18:45 +0300 (EEST)
Received: from taimen (h162192.gprs.dnafinland.fi [87.93.162.192])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Mon,  6 Oct 2008 10:18:45 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id D91C7AC054; Mon,  6 Oct 2008 10:18:40 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18665.48080.859460.802945@taimen.test.fi>
Date: Mon, 6 Oct 2008 10:18:40 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > I don't see any mentioning of the contact in the text above - it only
 > talks about instance-id.

then the ua must use two instance ids (one for each contact) or outbound
i-d must be changed to allow forking if contacts are not the same.

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


From sip-bounces@ietf.org  Mon Oct  6 00:22:11 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5697128C1F3;
	Mon,  6 Oct 2008 00:22:11 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 81F8F28C1F6
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 00:22:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.208
X-Spam-Level: 
X-Spam-Status: No, score=-6.208 tagged_above=-999 required=5 tests=[AWL=0.041, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1hiTobGZYi5W for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 00:22:09 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 2991928C1F3
	for <sip@ietf.org>; Mon,  6 Oct 2008 00:22:09 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	CBAA920244; Mon,  6 Oct 2008 09:22:26 +0200 (CEST)
X-AuditID: c1b4fb3e-a9e87bb000007a96-55-48e9bcb22925
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	9E48721154; Mon,  6 Oct 2008 09:22:26 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 09:22:25 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 09:22:25 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F893@esealmw113.eemea.ericsson.se>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF198F2411@zrc2hxm0.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] gruu in outbound-15 9.1
Thread-Index: Ackk6uLg+cF3ViEFQQuRhT3etDbcAQAuABoQAEBba8A=
References: <EE9B10212E22466DAE8D10EECAF11291@rildelhi.com><5D1A7985295922448D5550C94DE291800236151C@DEEXC1U01.de.lucent.com><18659.54337.452872.203497@taimen.test.fi><CDF0F938-3B8C-442C-87E4-D9B319F939DB@softarmor.com><18660.61663.416336.165388@taimen.test.fi><D6D8CEC6-6002-4654-B3EC-309BA8EA182E@softarmor.com><CB022A19-6DEF-4E12-A0DC-06D5628371F5@softarmor.com>
	<1ECE0EB50388174790F9694F77522CCF198F2411@zrc2hxm0.corp.nortel.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Francois Audet" <audet@nortel.com>,
	"Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 06 Oct 2008 07:22:25.0946 (UTC)
	FILETIME=[4854E7A0:01C92784]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] gruu in outbound-15 9.1
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi,

I have to admit that I have missed the addition of the possibiliy to
establish non-registration outbound flows using dialog-forming requests.

However, I unfortunately think that is going to require some more
editorial work to the spec, because parts of the documents talk about
the registation case, and some procedures seem to assume that
registrations are used, so maybe clarifications are needed that some
procedures only apply to the registration case.

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

Subclause 1 says:

"The key idea of this specification is that when a UA sends a REGISTER
request or a dialog-forming request, the proxy can later use this
same network "flow"--whether this is a bidirectional stream of UDP
datagrams, a TCP connection, or an analogous concept in another
transport protocol--to forward any incoming requests that need to go
to this UA in the context of the registration or dialog.

The text is a little confusing. It starts by talking about when a UA
sends a REGISTER, and at the end it talks about the context of a dialog.
You probably need to e.g. split the text into two parts - one talking
about the registration case, and one talking about the dialog case.

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

Subclauses 2.1 says:

"ob Parameter:  The 'ob' parameter is a SIP URI parameter which has
      different meaning depending on context.  In a Path header field
      value it is used by the first edge proxy to indicate that a flow
      token was added to the URI.  In a Contact or Route header field
      value it indicates that the UA would like other requests in the
      same dialog routed over the same flow."

First, I assume it refers to a Contact or Route header inserted by the
UAC in the dialog, so maybe that needs to be clarified. 

Second, I assume the only time the UAC will insert the parameter in a
Route header is when it was sent beck in a Path header?

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

Subclause 3.1 says:

 "When sending a dialog-forming request, a UA can also ask its first
   edge proxy to route subsequent requests in that dialog over the same
   flow.  This is necessary whether the UA has registered or not."

Why is this necessary when the UA is registered? Won't requests then
automatically be delivered over the registered flow?

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

Also, are keep-alives sent on dialog-forming requests? The text in the
last paragraph of subclause 1 seems to indiate so.

But, the non-registration flow examples don't show any keep-alives.

Also, subclause 3.5 says:

"When the UA detects that a flow has failed or that the flow definition
has changed, the UA needs to re-register..."

Is that true if the flow was established using a dialog-forming request?
What if the UA isn't registerded in the first place...? I guess
subclause 4.5 clarifies that this only applies to registation flows, but
it would also need to be claified here.


Also, subclause 3.5.1 says:

"If the client does not receive a pong in response to its ping, it
declares the flow dead and opens a new flow in its place."

How will that be done if the flow was established using a dialog-forming
request? Will the new flow be esablished by transfering the existing
dialog?


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

Subclause 4.2.1 talks about the case when the UAC recieves a 439
resposne for the REGISTER request. But, can't it receive 439 also if it
tries to estblish the flow using a dialog-establisment request?

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


Regards,

Christer







 

-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Francois Audet
Sent: Saturday, October 04, 2008 12:57 AM
To: Dean Willis
Cc: SIP IETF
Subject: Re: [Sip] gruu in outbound-15 9.1


Thanks Dean.

This text seems perfect to me. I'll deal with it in WGLC. 

> -----Original Message-----
> From: Dean Willis [mailto:dean.willis@softarmor.com]
> Sent: Thursday, October 02, 2008 16:59
> To: Audet, Francois (SC100:3055)
> Cc: Juha Heinanen; SIP IETF
> Subject: gruu in outbound-15 9.1
> 
> >
> 
> Original text:
> 
> 
> >  If the UAC is sending a dialog-forming request, and wants all 
> > subsequent requests in the dialog to arrive over the same
> flow, the
> > UAC adds an 'ob' parameter to its Contact header.  
> Typically this is
> > desirable, but it is not necessary for example if the Contact is a 
> > GRUU [I-D.ietf-sip-gruu].  The flow used for the request is
> typically
> > the same flow the UA registered over, but it could be a new
> flow, for
> > example the initial subcription dialog for the configuration 
> > framework [I-D.ietf-sipping-config-framework] needs to
> exist before
> > registration.
> 
> 
> Proposed text:
> 
> Typically, a UAC using the procedures of this document and sending a 
> dialog-forming request will want all subsequent requests in the dialog

> to arrive over the same flow. If the UAC is using a GRUU 
> [I-D.ietf-sip-gruu] that was instantiated using a Contact header field

> value that included an "ob"
> parameter, the UAC sends teh request over the flow used for 
> registration and susequent requests will arrive over that same flow. 
> If the UAC is not using such a GRUU, then the UAC adds an "ob" 
> parameter to its Contact header field value.
> This will cause all subsequent requests in the dialog to arrive over 
> the flow instantiated by the dialog-forming request. This case is 
> typical when the request is sent prior to registration, such as in the

> the initial subcription dialog for the configuration framework 
> [I-D.ietf-sipping-config-framework].
> 
> 
> --
> Dean
> 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol Use
sip-implementors@cs.columbia.edu for questions on current sip Use
sipping@ietf.org for new developments on the application of sip
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct  6 00:29:34 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E2A2428C1CB;
	Mon,  6 Oct 2008 00:29:34 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AD83028C1BB
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 00:29:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.211
X-Spam-Level: 
X-Spam-Status: No, score=-6.211 tagged_above=-999 required=5 tests=[AWL=0.038, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id x9BbESR7Ukmd for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 00:29:33 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id AF60728C19A
	for <sip@ietf.org>; Mon,  6 Oct 2008 00:29:32 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	160392068B; Mon,  6 Oct 2008 09:30:07 +0200 (CEST)
X-AuditID: c1b4fb3c-af0d0bb0000015b5-ac-48e9be7e9731
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	F36A620653; Mon,  6 Oct 2008 09:30:06 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 09:30:06 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 09:30:05 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
In-Reply-To: <18665.48080.859460.802945@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackng8iFbkGT3ob5RT29xq+1XuBAogAAJpzg
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com><18665.42838.994529.377867@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se><18665.43684.176244.988653@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 06 Oct 2008 07:30:06.0229 (UTC)
	FILETIME=[5AAE8450:01C92785]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>I don't see any mentioning of the contact in the text above - it only
talks about instance-id.
>
>then the ua must use two instance ids (one for each contact) or
outbound i-d must be changed to allow forking if contacts >are not the
same.

I guess we would need to check whether the spec FORBIDS forking, but my
point was that I don't see any text which would REQUIRE forking for
different contacts, if the instance-id is the same.

Can I ask you, why would you want to use Outbound in you want forking to
occur?

Of course, if you don't use Outbound, you may need anohter mechanism to
negotiate support of keep-alives: the sip-keep draft provides such
mechanism :)

But, since I know that you don't think that keep-alive indicators are
needed in the first place, I guess there much be another reason why you
want to use Outbound.


Regards,

Christer


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


From sip-bounces@ietf.org  Mon Oct  6 00:44:12 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E5A753A690B;
	Mon,  6 Oct 2008 00:44:11 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DBF263A690B
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 00:44:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QTE8jTgrXmcG for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 00:44:10 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id D100F3A677D
	for <sip@ietf.org>; Mon,  6 Oct 2008 00:44:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 655B51EC2CE;
	Mon,  6 Oct 2008 10:44:44 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UOJvNVEr8+Fo; Mon,  6 Oct 2008 10:44:42 +0300 (EEST)
Received: from taimen (h162192.gprs.dnafinland.fi [87.93.162.192])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Mon,  6 Oct 2008 10:44:42 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 12D73AC054; Mon,  6 Oct 2008 10:44:37 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18665.49637.47890.122973@taimen.test.fi>
Date: Mon, 6 Oct 2008 10:44:37 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > Can I ask you, why would you want to use Outbound in you want forking to
 > occur?

now that outbound text has been changed and it mandates UA to register
via two ob proxies if only two is given, it allows a very simple
implementation of redundancy, because the two proxies can operate
totally independent of each other.  

if UA has two different contacts and if outbound i-d does not mandate
the UA to register BOTH of them with BOTH ob proxies, then the above
(and only benefit) of outbound i-d goes away again, because we would
again be in the situation where redundancy is lost.

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


From sip-bounces@ietf.org  Mon Oct  6 00:45:03 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AC6133A69A9;
	Mon,  6 Oct 2008 00:45:03 -0700 (PDT)
X-Original-To: sip@ietf.org
Delivered-To: sip@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id D22B03A69D8; Mon,  6 Oct 2008 00:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081006074501.D22B03A69D8@core3.amsl.com>
Date: Mon,  6 Oct 2008 00:45:01 -0700 (PDT)
Cc: sip@ietf.org
Subject: [Sip] I-D Action:draft-ietf-sip-record-route-fix-05.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--NextPart

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


	Title           : Addressing Record-Route issues in the Session Initiation Protocol (SIP)
	Author(s)       : T. Froment, et al.
	Filename        : draft-ietf-sip-record-route-fix-05.txt
	Pages           : 25
	Date            : 2008-10-06

A typical function of a Session Initiation Protocol (SIP) Proxy is to
insert a Record-Route header into initial, dialog creating requests
in order to make subsequent, in-dialog requests pass through it.
This header contains a SIP Uniform Resource Identifier (URI)
indicating where and how the subsequent requests should be sent to
reach the proxy.  Like any SIP URI, it can contain sip or sips
schemes, IPv4 or IPv6 addresses, and URI parameters that could
influence the routing such as the transport parameter (for example
transport=tcp), or a compression indication like "comp=sigcomp".
When a proxy has to change some of those parameters between its
incoming and outgoing interfaces (multi-homed proxies, transport
protocol switching or IPv4 to IPv6 scenarios...), the question arises
on what should be put in Record-Route header(s).  It is just not
possible to make one header having the characteristics of both sides
at the same time.  This document aims to clarify these scenarios and
fix bugs already identified on this topic; it formally recommends the
use of the double Record-Route technique as an alternative to the
current RFC3261 text, which describes only a Record-Route rewriting
solution.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sip-record-route-fix-05.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-sip-record-route-fix-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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


From sip-bounces@ietf.org  Mon Oct  6 01:20:06 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9286928C13B;
	Mon,  6 Oct 2008 01:20:06 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 91AF228C10F
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 01:20:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id iFCC2UhY-ENJ for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 01:20:04 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id 9C72628C0F1
	for <sip@ietf.org>; Mon,  6 Oct 2008 01:20:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id BB25A1EC2CE;
	Mon,  6 Oct 2008 11:19:46 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id j--5+l7nQTvp; Mon,  6 Oct 2008 11:19:41 +0300 (EEST)
Received: from taimen (h162192.gprs.dnafinland.fi [87.93.162.192])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Mon,  6 Oct 2008 11:19:41 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 495F7AC054; Mon,  6 Oct 2008 11:19:36 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18665.51736.268071.502700@taimen.test.fi>
Date: Mon, 6 Oct 2008 11:19:36 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > That still dooesn't answer my question: why do you want forking? Why
 > can't the registrar simply choose ONE working flow?

forking increases changes that the call actually gets through, because
one of the access networks may not be reachable at the moment.  also, if
both 3g and wlan is reachable, call comes through many seconds earlier
through wlan and is usually also free.  i understand that mobile
operators don't have incentive to fork the call if one of the legs is
free and the other costs money.

 > And, the UA can make normal (non-outbound) registrations via each of the
 > two ob proxies. They will still operate indepenent of each other - and
 > you will get forking.

"can" but is not forced to, which breaks the whole thing.

 > Even the UA has two contacts, and registers each once (using normal reg
 > procedures), you will still have redundancy: if one contact doesn't work
 > then the registrar will try anohter.

yes, but then you have only one registrar, which breaks redundancy at
server side.

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


From sip-bounces@ietf.org  Mon Oct  6 01:28:19 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AE7C03A6A42;
	Mon,  6 Oct 2008 01:28:19 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 525C43A6A42
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 01:28:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.213
X-Spam-Level: 
X-Spam-Status: No, score=-6.213 tagged_above=-999 required=5 tests=[AWL=0.036, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id H6vrJjY3UgbN for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 01:28:17 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 394273A6A3B
	for <sip@ietf.org>; Mon,  6 Oct 2008 01:28:17 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	9D5D0211B1; Mon,  6 Oct 2008 10:06:10 +0200 (CEST)
X-AuditID: c1b4fb3e-a8e85bb000007a96-31-48e9c6f2902a
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	854BA20572; Mon,  6 Oct 2008 10:06:10 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 10:06:10 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 10:06:09 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
In-Reply-To: <18665.49637.47890.122973@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Acknh2c5FlOL1y5qSKKdWdqvUUrv6gAAbLlA
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com><18665.42838.994529.377867@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se><18665.43684.176244.988653@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 06 Oct 2008 08:06:10.0390 (UTC)
	FILETIME=[649F4760:01C9278A]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>Can I ask you, why would you want to use Outbound in you want forking
to occur?
>
>now that outbound text has been changed and it mandates UA to register
via two ob proxies if only two is given, it allows >a very simple
implementation of redundancy, because the two proxies can operate
totally independent of each other.  

That still dooesn't answer my question: why do you want forking? Why
can't the registrar simply choose ONE working flow?

And, the UA can make normal (non-outbound) registrations via each of the
two ob proxies. They will still operate indepenent of each other - and
you will get forking.

>if UA has two different contacts and if outbound i-d does not mandate
the UA to register BOTH of them with BOTH ob 
>proxies, then the above (and only benefit) of outbound i-d goes away
again, because we would again be in the situation 
>-where redundancy is lost.

Even the UA has two contacts, and registers each once (using normal reg
procedures), you will still have redundancy: if one contact doesn't work
then the registrar will try anohter.

Regards,

Christer




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


From sip-bounces@ietf.org  Mon Oct  6 03:08:05 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EF2823A6AAC;
	Mon,  6 Oct 2008 03:08:04 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5A3633A6AAC
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 03:08:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.214
X-Spam-Level: 
X-Spam-Status: No, score=-6.214 tagged_above=-999 required=5 tests=[AWL=0.035, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id L3ZhzmHZdsLF for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 03:08:02 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 52AE03A6A9A
	for <sip@ietf.org>; Mon,  6 Oct 2008 03:08:02 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	DFDF920599; Mon,  6 Oct 2008 12:08:36 +0200 (CEST)
X-AuditID: c1b4fb3e-aae89bb000007a96-19-48e9e3a4edb8
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	AAE7A20F26; Mon,  6 Oct 2008 12:08:36 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 12:07:35 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 12:07:35 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>
In-Reply-To: <18665.51736.268071.502700@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AcknjE1R3Cg7M7BjSfi+Vao+juSGEQADLsgg
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com><18665.42838.994529.377867@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se><18665.43684.176244.988653@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 06 Oct 2008 10:07:35.0688 (UTC)
	FILETIME=[5AFF8880:01C9279B]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>That still dooesn't answer my question: why do you want forking? Why
can't the registrar simply choose ONE working flow?
>
>forking increases changes that the call actually gets through, because
one of the access networks may not be reachable at >the moment.  also,
if both 3g and wlan is reachable, call comes through many seconds
earlier through wlan and is usually >also free.  i understand that
mobile operators don't have incentive to fork the call if one of the
legs is free and the 
>other costs money.

Yes, because earning money is simply wrong :)

>>And, the UA can make normal (non-outbound) registrations via each of
the two ob proxies. They will still operate 
>>indepenent of each other - and  > you will get forking.
>
>"can" but is not forced to, which breaks the whole thing.

Even if you allow (if it is even forbidden, that is) forking for
outbound it is still going to be a "can". No matter if you use outbound
or not, you would need to configure your registrar if to do forking,
whether  to do serial- or paralell forking, etc etc etc. 

>>Even the UA has two contacts, and registers each once (using normal
reg procedures), you will still have redundancy: if >>one contact
doesn't work then the registrar will try anohter.
>
>yes, but then you have only one registrar, which breaks redundancy at
server side.

So, you want to register both contacts to both registars, right?

Example:

UA_Contact_wlan ----- OB_1 ----- REG_1
UA_Contact_wlan ----- OB_1 ----- REG_2
UA_Contact_3g   ----- OB_2 ----- REG_1
UA_Contact_3g   ----- OB_2 ----- REG_2

Regards,

Christer




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


From sip-bounces@ietf.org  Mon Oct  6 03:24:51 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EBB2F3A6A5E;
	Mon,  6 Oct 2008 03:24:50 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E22C53A6A5E
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 03:24:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XHDLcL468IJf for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 03:24:49 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id F18753A68AD
	for <sip@ietf.org>; Mon,  6 Oct 2008 03:24:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 1EA741EC2CE;
	Mon,  6 Oct 2008 13:25:21 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gv5qxHpk0jaB; Mon,  6 Oct 2008 13:25:14 +0300 (EEST)
Received: from taimen (h162192.gprs.dnafinland.fi [87.93.162.192])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Mon,  6 Oct 2008 13:25:14 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id A47FAAC054; Mon,  6 Oct 2008 13:25:09 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18665.59269.640606.477292@taimen.test.fi>
Date: Mon, 6 Oct 2008 13:25:09 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > So, you want to register both contacts to both registars, right?
 > 
 > Example:
 > 
 > UA_Contact_wlan ----- OB_1 ----- REG_1
 > UA_Contact_wlan ----- OB_1 ----- REG_2
 > UA_Contact_3g   ----- OB_2 ----- REG_1
 > UA_Contact_3g   ----- OB_2 ----- REG_2

no, like this:

 > UA_Contact_wlan ----- OB_1 ----- REG_1
 > UA_Contact_wlan ----- OB_2 ----- REG_2
 > UA_Contact_3g   ----- OB_1 ----- REG_1
 > UA_Contact_3g   ----- OB_2 ----- REG_2

if outbound does not mandate that UA must register each contact with
both ob proxies, my pleasant surprise was a too early one and ob draft
falls back to the useless bin.

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


From sip-bounces@ietf.org  Mon Oct  6 03:36:10 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 36E443A6AB2;
	Mon,  6 Oct 2008 03:36:10 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D3D9A3A6AB2
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 03:36:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.216
X-Spam-Level: 
X-Spam-Status: No, score=-6.216 tagged_above=-999 required=5 tests=[AWL=0.033, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id MEx3Dne6nP78 for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 03:36:08 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 530C63A6AAD
	for <sip@ietf.org>; Mon,  6 Oct 2008 03:36:03 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	601B921192; Mon,  6 Oct 2008 12:36:38 +0200 (CEST)
X-AuditID: c1b4fb3e-a8e85bb000007a96-01-48e9ea36210d
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	4927321154; Mon,  6 Oct 2008 12:36:38 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 12:36:37 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 12:36:37 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
In-Reply-To: <18665.59269.640606.477292@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Acknndb9wTipKL1vRQ6r0c83ma4kUQAAFaMg
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com><18665.42838.994529.377867@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se><18665.43684.176244.988653@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>
	< 18665.59 269.640606.477292@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 06 Oct 2008 10:36:37.0987 (UTC)
	FILETIME=[697D4330:01C9279F]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

 > So, you want to register both contacts to both registars, right?
 >
 > Example:
 >
 > UA_Contact_wlan ----- OB_1 ----- REG_1 
 > UA_Contact_wlan ----- OB_1 ----- REG_2
 > UA_Contact_3g   ----- OB_2 ----- REG_1
 > UA_Contact_3g   ----- OB_2 ----- REG_2

>no, like this:

 > UA_Contact_wlan ----- OB_1 ----- REG_1  
 > UA_Contact_wlan ----- OB_2 ----- REG_2
 > UA_Contact_3g   ----- OB_1 ----- REG_1
 > UA_Contact_3g   ----- OB_2 ----- REG_2

Now, in your example, if OB_1 and REG_2 fail you don't still don't have
redundancy :)

>if outbound does not mandate that UA must register each contact with
both ob proxies, my pleasant surprise was a too
>early one and ob draft falls back to the useless bin.

I don't have the spec in front of me, but I don't think it currently
talks about multiple contacts.

I guess this all comes back to Dean's question whether we need some new
text into the draft.

In order to avoid delaying the Outbound spec even more, I guess it could
also be an extension draft:"Outbound with multiple contacts", or
something like that...

Regards,

Christer





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


From sip-bounces@ietf.org  Mon Oct  6 03:48:25 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 42E4C3A6A8D;
	Mon,  6 Oct 2008 03:48:25 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 591543A6A74
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 03:48:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Z2LYnC7bn4n7 for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 03:48:22 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id 717B13A69BB
	for <sip@ietf.org>; Mon,  6 Oct 2008 03:48:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id BCF441EC2CE;
	Mon,  6 Oct 2008 13:48:57 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id De4SynC0EMOB; Mon,  6 Oct 2008 13:48:55 +0300 (EEST)
Received: from taimen (h162192.gprs.dnafinland.fi [87.93.162.192])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Mon,  6 Oct 2008 13:48:55 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 9DE47AC054; Mon,  6 Oct 2008 13:48:51 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18665.60691.623346.723235@taimen.test.fi>
Date: Mon, 6 Oct 2008 13:48:51 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>
	< 18665.59 269.640606.477292@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > Now, in your example, if OB_1 and REG_2 fail you don't still don't have
 > redundancy :)

in the very common case that i have described earlier on this mailing
list, obx and regx are paired and run on the same host.  they are not
separate entities that can fail on their own.

 > I guess this all comes back to Dean's question whether we need some new
 > text into the draft.
 > 
 > In order to avoid delaying the Outbound spec even more, I guess it could
 > also be an extension draft:"Outbound with multiple contacts", or
 > something like that...

huh, once ob is out as rfc, it is way too late to do anything about it.
ob i-d must be got right the first shot.  another (better) alternative
is to publish the component rfcs that we have identified first and once
they are out, start working on ob i-d.

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


From sip-bounces@ietf.org  Mon Oct  6 09:27:32 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0D12C28C0DC;
	Mon,  6 Oct 2008 09:27:32 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D7A543A6811
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 09:27:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[AWL=0.063, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9apwjdZjCcdI for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 09:27:30 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 1951E3A67DD
	for <sip@ietf.org>; Mon,  6 Oct 2008 09:27:30 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m96GRpEP031983
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Mon, 6 Oct 2008 11:27:53 -0500
Message-Id: <5E472EB8-4A10-4279-9B70-AFD361CABBAE@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Juha Heinanen <jh@tutpro.com>
In-Reply-To: <18665.46813.666160.483955@taimen.test.fi>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 6 Oct 2008 11:27:46 -0500
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<7A726F54F791494C8D8C87F13736E80EEC2237@vaebe106.NOE.Nokia.com>
	<18665.44759.799781.864060@taimen.test.fi>
	<30D3B985-E61D-45B1-8819-C82EC338E73D@softarmor.com>
	<18665.46813.666160.483955@taimen.test.fi>
X-Mailer: Apple Mail (2.929.2)
Cc: sip@ietf.org
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 6, 2008, at 1:57 AM, Juha Heinanen wrote:

> Dean Willis writes:
>
>> Outbound-15 4.2.1 says:
>>
>> For each outbound proxy URI in the set, the UAC SHOULD send a  
>> REGISTER
>> request using this URI as the default outbound proxy. (Alternatively,
>> the UA could limit the number of flows formed to conserve battery
>> power, for example). If the set has more than one URI, the UAC MUST
>> send a REGISTER request to at least two of the default outbound
>> proxies from the set.
>
> i thought that i lost this battle, but it is a nice surprise that the
> text has been changed and with two proxies in the set, ua MUST  
> register
> with both.

That's why I kept saying we had fixed that part of outbound per your  
request.

>
>
> now if the ua has two network interfaces (3g and wlan, for example)  
> and
> the user want to use both of them simultaneously, is it so that  
> inbound call
> gets forked?

My understanding was that there is a contact prioritization. The proxy  
uses the first contact as long as the flow associated with that  
contact has keepalive. If that flow fails, then the proxy falls over  
to the second contact and flow.

> and further, is there any text anywhere forcing the ua to register  
> both
> of its contacts with both proxies?

Only in 3GPP specs, I believe.


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


From sip-bounces@ietf.org  Mon Oct  6 09:32:37 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F18083A693D;
	Mon,  6 Oct 2008 09:32:36 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C999D3A693D
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 09:32:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id lfN0eZbUpsr5 for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 09:32:32 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 1C7EE3A67DD
	for <sip@ietf.org>; Mon,  6 Oct 2008 09:32:32 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m96GWk0g032062
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Mon, 6 Oct 2008 11:32:48 -0500
Message-Id: <CDA30DAD-DE21-4A5D-BF67-9A49DF32B4EA@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Juha Heinanen <jh@tutpro.com>
In-Reply-To: <18665.59269.640606.477292@taimen.test.fi>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 6 Oct 2008 11:32:40 -0500
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eem!
	ea.ericsson.se> <18665.59269.640606.477292@taimen.test.fi>
X-Mailer: Apple Mail (2.929.2)
Cc: sip@ietf.org, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 6, 2008, at 5:25 AM, Juha Heinanen wrote:
>
> if outbound does not mandate that UA must register each contact with
> both ob proxies, my pleasant surprise was a too early one and ob draft
> falls back to the useless bin.

Assume a UA has two different interfaces, and it registers each of its  
interfaces with a different proxy/registrar. Further assume that those  
two proxy registrars collude with respect to mapping the user's AUR  
onto those contacts.

What's not redundant about this, and why is it useless?


--
Dean

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


From sip-bounces@ietf.org  Mon Oct  6 09:36:37 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 283D23A6AF2;
	Mon,  6 Oct 2008 09:36:37 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 52E363A67DD
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 09:36:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.218
X-Spam-Level: 
X-Spam-Status: No, score=-6.218 tagged_above=-999 required=5 tests=[AWL=0.031, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id StWYiBEqQIhk for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 09:36:35 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 692763A6AF2
	for <sip@ietf.org>; Mon,  6 Oct 2008 09:36:35 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	5C2C120F1B; Mon,  6 Oct 2008 18:36:21 +0200 (CEST)
X-AuditID: c1b4fb3e-ab68abb000007a96-5e-48ea3e8339de
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	E452B2049F; Mon,  6 Oct 2008 18:36:19 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 18:36:19 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 18:36:19 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F89E@esealmw113.eemea.ericsson.se>
In-Reply-To: <5E472EB8-4A10-4279-9B70-AFD361CABBAE@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackn0I0suLQggbuNSXyt3igX6cmXRAAAMcQQ
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com><18665.42838.994529.377867@taimen.test.fi><7A726F54F791494C8D8C87F13736E80EEC2237@vaebe106.NOE.Nokia.com><18665.44759.799781.864060@taimen.test.fi><30D3B985-E61D-45B1-8819-C82EC338E73D@softarmor.com><18665.46813.666160.483955@taimen.test.fi>
	<5E472EB8-4A10-4279-9B70-AFD361CABBAE@softarmor.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Dean Willis" <dean.willis@softarmor.com>, "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 06 Oct 2008 16:36:19.0375 (UTC)
	FILETIME=[A8FFBBF0:01C927D1]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>and further, is there any text anywhere forcing the ua to register
both of its contacts with both proxies?
>
>Only in 3GPP specs, I believe.

3GPP does not say anything about registering contacts with multiple
registrars - with or without outbound.

Regards,

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


From sip-bounces@ietf.org  Mon Oct  6 09:58:52 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 08D0E3A6AEE;
	Mon,  6 Oct 2008 09:58:52 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 180093A68F8
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 09:58:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0qNIiiUwN6nD for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 09:58:50 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id 2A2A73A6AFC
	for <sip@ietf.org>; Mon,  6 Oct 2008 09:58:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 90A671EC2CE;
	Mon,  6 Oct 2008 19:43:31 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Qxj7f46rGwqb; Mon,  6 Oct 2008 19:43:24 +0300 (EEST)
Received: from taimen (h180097.gprs.dnafinland.fi [87.93.180.97])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Mon,  6 Oct 2008 19:43:24 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 5250EAC054; Mon,  6 Oct 2008 19:43:18 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18666.16422.211242.766454@taimen.test.fi>
Date: Mon, 6 Oct 2008 19:43:18 +0300
To: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <CDA30DAD-DE21-4A5D-BF67-9A49DF32B4EA@softarmor.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eem!
	ea.ericsson.se> <18665.59269.640606.477292@taimen.test.fi>
	<CDA30DAD-DE21-4A5D-BF67-9A49DF32B4EA@softarmor.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Dean Willis writes:

 > Assume a UA has two different interfaces, and it registers each of its  
 > interfaces with a different proxy/registrar. Further assume that those  
 > two proxy registrars collude with respect to mapping the user's AUR  
 > onto those contacts.

that "collude" thing is exactly what i tried to avoid.  if ua is
required to register all of its contacts via both proxies, then
redundancy of the service can be implemented by running the
two proxy/registrars completely independent of each other thus greatly
simplifying the implementation.

if that requirement is not there, ob becomes totally useless again and
there was no advantage that the text was changed according to my
wishes.  you may as well go and change it back to what it was before.

 > What's not redundant about this, and why is it useless?

see above.  if we assume that ob set share common knowledge of the
registrations (e.g. via database), then registering via only some of the
ob proxies works fine.

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


From sip-bounces@ietf.org  Mon Oct  6 10:39:28 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C19153A698E;
	Mon,  6 Oct 2008 10:39:28 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6DC813A698E
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 10:39:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.541
X-Spam-Level: 
X-Spam-Status: No, score=-2.541 tagged_above=-999 required=5 tests=[AWL=0.058, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id MH4csGlIxpV3 for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 10:39:22 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 0FD293A69B8
	for <sip@ietf.org>; Mon,  6 Oct 2008 10:39:22 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m96Hd5uJ032544
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Mon, 6 Oct 2008 12:39:06 -0500
Message-Id: <0C624437-46DA-4FF8-BA5B-8E2F75E224B1@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F89E@esealmw113.eemea.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 6 Oct 2008 12:38:59 -0500
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com><18665.42838.994529.377867@taimen.test.fi><7A726F54F791494C8D8C87F13736E80EEC2237@vaebe106.NOE.Nokia.com><18665.44759.799781.864060@taimen.test.fi><30D3B985-E61D-45B1-8819-C82EC338E73D@softarmor.com><18665.46813.666160.483955@taimen.test.fi>
	<5E472EB8-4A10-4279-9B70-AFD361CABBAE@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F89E@esealmw113.eemea.ericsson.se>
X-Mailer: Apple Mail (2.929.2)
Cc: sip@ietf.org
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 6, 2008, at 11:36 AM, Christer Holmberg wrote:

>
> Hi,
>
>>> and further, is there any text anywhere forcing the ua to register
> both of its contacts with both proxies?
>>
>> Only in 3GPP specs, I believe.
>
> 3GPP does not say anything about registering contacts with multiple
> registrars - with or without outbound.
>

He said proxies, not registrars. Two different P-CSCFs, one for each  
radio. One S-CSCF.

--
Dean

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


From sip-bounces@ietf.org  Mon Oct  6 10:41:35 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8AD153A6AC4;
	Mon,  6 Oct 2008 10:41:35 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4ABEF3A6A27
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 10:41:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.543
X-Spam-Level: 
X-Spam-Status: No, score=-2.543 tagged_above=-999 required=5 tests=[AWL=0.056, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BNmBHGxM12ap for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 10:41:33 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 828FE3A69B8
	for <sip@ietf.org>; Mon,  6 Oct 2008 10:41:33 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m96HfCCN032583
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Mon, 6 Oct 2008 12:41:13 -0500
Message-Id: <ADB2E3A0-DAF6-432B-B269-A10E9D38E6EA@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Juha Heinanen <jh@tutpro.com>
In-Reply-To: <18666.16422.211242.766454@taimen.test.fi>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 6 Oct 2008 12:41:06 -0500
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eem!
	! ea.ericsson.se> <18665.59269.640606.477292@taimen.test.fi>
	<CDA30DAD-DE21-4A5D-BF67-9A49DF32B4EA@softarmor.com>
	<18666.16422.211242.766454@taimen.test.fi>
X-Mailer: Apple Mail (2.929.2)
Cc: sip@ietf.org, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Why do I get the feeling that you won't be happy even when every UA is  
forced to register every contact it has or might obtain have with  
every registrar that ever existed or will exist ;-)?

On Oct 6, 2008, at 11:43 AM, Juha Heinanen wrote:

> Dean Willis writes:
>
>> Assume a UA has two different interfaces, and it registers each of  
>> its
>> interfaces with a different proxy/registrar. Further assume that  
>> those
>> two proxy registrars collude with respect to mapping the user's AUR
>> onto those contacts.
>
> that "collude" thing is exactly what i tried to avoid.  if ua is
> required to register all of its contacts via both proxies, then
> redundancy of the service can be implemented by running the
> two proxy/registrars completely independent of each other thus greatly
> simplifying the implementation.
>
> if that requirement is not there, ob becomes totally useless again and
> there was no advantage that the text was changed according to my
> wishes.  you may as well go and change it back to what it was before.

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


From sip-bounces@ietf.org  Mon Oct  6 10:49:16 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7B2883A6AE6;
	Mon,  6 Oct 2008 10:49:16 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4E5D93A69FB
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 10:49:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id iBFfMQY6aS2c for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 10:49:14 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id 4E70D3A67FC
	for <sip@ietf.org>; Mon,  6 Oct 2008 10:49:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 4401B1EC2CE;
	Mon,  6 Oct 2008 20:49:07 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id pypBu-nxiZxp; Mon,  6 Oct 2008 20:49:05 +0300 (EEST)
Received: from taimen (h180097.gprs.dnafinland.fi [87.93.180.97])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Mon,  6 Oct 2008 20:49:05 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 6D764AC054; Mon,  6 Oct 2008 20:48:55 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18666.20359.413310.214443@taimen.test.fi>
Date: Mon, 6 Oct 2008 20:48:55 +0300
To: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <ADB2E3A0-DAF6-432B-B269-A10E9D38E6EA@softarmor.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eem!
	! ea.ericsson.se> <18665.59269.640606.477292@taimen.test.fi>
	<CDA30DAD-DE21-4A5D-BF67-9A49DF32B4EA@softarmor.com>
	<18666.16422.211242.766454@taimen.test.fi>
	<ADB2E3A0-DAF6-432B-B269-A10E9D38E6EA@softarmor.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Dean Willis writes:

 > Why do I get the feeling that you won't be happy even when every UA is  
 > forced to register every contact it has or might obtain have with  
 > every registrar that ever existed or will exist ;-)?

dean,

that is not true.  i sincerely hoped that outbound would help me to
implement redundant proxy/registrar without a need to for load
balancers, database clusters, or forwarding of requests between
proxies simply by being able to assume that if i have two ob proxies,
each ua would register all contacts that it has via both of them.  

this is a VERY simple, easy to understand and implement requirement
compared to anything else this working group has ever produced.

-- juha



 > 
 > On Oct 6, 2008, at 11:43 AM, Juha Heinanen wrote:
 > 
 > > Dean Willis writes:
 > >
 > >> Assume a UA has two different interfaces, and it registers each of  
 > >> its
 > >> interfaces with a different proxy/registrar. Further assume that  
 > >> those
 > >> two proxy registrars collude with respect to mapping the user's AUR
 > >> onto those contacts.
 > >
 > > that "collude" thing is exactly what i tried to avoid.  if ua is
 > > required to register all of its contacts via both proxies, then
 > > redundancy of the service can be implemented by running the
 > > two proxy/registrars completely independent of each other thus greatly
 > > simplifying the implementation.
 > >
 > > if that requirement is not there, ob becomes totally useless again and
 > > there was no advantage that the text was changed according to my
 > > wishes.  you may as well go and change it back to what it was before.
 > 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct  6 11:12:26 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 32B873A69FB;
	Mon,  6 Oct 2008 11:12:26 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7461B3A69FB
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 11:12:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.219
X-Spam-Level: 
X-Spam-Status: No, score=-6.219 tagged_above=-999 required=5 tests=[AWL=0.030, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Lpxjy3DeURn5 for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 11:12:24 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id A12863A6452
	for <sip@ietf.org>; Mon,  6 Oct 2008 11:12:24 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	95B702147C; Mon,  6 Oct 2008 20:12:26 +0200 (CEST)
X-AuditID: c1b4fb3e-ab68abb000007a96-b4-48ea550a0e1f
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	7FCC32147B; Mon,  6 Oct 2008 20:12:26 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 20:12:26 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 20:12:25 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8A2@esealmw113.eemea.ericsson.se>
In-Reply-To: <0C624437-46DA-4FF8-BA5B-8E2F75E224B1@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackn2nBzWB3BMLJWRm6gP8cTFVUrkgABF2Nw
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com><18665.42838.994529.377867@taimen.test.fi><7A726F54F791494C8D8C87F13736E80EEC2237@vaebe106.NOE.Nokia.com><18665.44759.799781.864060@taimen.test.fi><30D3B985-E61D-45B1-8819-C82EC338E73D@softarmor.com><18665.46813.666160.483955@taimen.test.fi>
	<5E472EB8-4A10-4279-9B70-AFD361CABBAE@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F89E@esealmw113.eemea.ericsson.se>
	<0C624437-46DA-4FF8-BA5B-8E2F75E224B1@softarmor.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 06 Oct 2008 18:12:26.0293 (UTC)
	FILETIME=[16599650:01C927DF]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>>and further, is there any text anywhere forcing the ua to register
both of its contacts with both proxies?
>>
>>Only in 3GPP specs, I believe.
>
>3GPP does not say anything about registering contacts with multiple 
>registrars - with or without outbound.
>
>
>He said proxies, not registrars. Two different P-CSCFs, one for each
radio. One S-CSCF.

I guess he can speak for himself, but the use-case he has presented
actaully talks about two different S-CSCFs.

Regards,

Christer


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


From sip-bounces@ietf.org  Mon Oct  6 11:19:52 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 698C53A69DD;
	Mon,  6 Oct 2008 11:19:52 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 57A943A6970
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 11:19:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.22
X-Spam-Level: 
X-Spam-Status: No, score=-6.22 tagged_above=-999 required=5 tests=[AWL=0.029, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fzHHBp2YXxCP for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 11:19:50 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id B17E328C10D
	for <sip@ietf.org>; Mon,  6 Oct 2008 11:19:49 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	B39C220D81; Mon,  6 Oct 2008 20:19:38 +0200 (CEST)
X-AuditID: c1b4fb3c-b00d2bb0000015b5-e6-48ea56ba5f3e
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	8BE7420B99; Mon,  6 Oct 2008 20:19:38 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 6 Oct 2008 20:19:38 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 6 Oct 2008 20:19:37 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8A3@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F893@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] gruu in outbound-15 9.1
Thread-Index: Ackk6uLg+cF3ViEFQQuRhT3etDbcAQAuABoQAEBba8AATscyMA==
References: <EE9B10212E22466DAE8D10EECAF11291@rildelhi.com><5D1A7985295922448D5550C94DE291800236151C@DEEXC1U01.de.lucent.com><18659.54337.452872.203497@taimen.test.fi><CDF0F938-3B8C-442C-87E4-D9B319F939DB@softarmor.com><18660.61663.416336.165388@taimen.test.fi><D6D8CEC6-6002-4654-B3EC-309BA8EA182E@softarmor.com><CB022A19-6DEF-4E12-A0DC-06D5628371F5@softarmor.com><1ECE0EB50388174790F9694F77522CCF198F2411@zrc2hxm0.corp.nortel.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F893@esealmw113.eemea.ericsson.se>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Christer Holmberg" <christer.holmberg@ericsson.com>,
	"Francois Audet" <audet@nortel.com>,
	"Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 06 Oct 2008 18:19:38.0304 (UTC)
	FILETIME=[17D93C00:01C927E0]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] gruu in outbound-15 9.1
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Some updates to my own previous comments. I have found answers to some
of the questions, so I have removed them.




Hi,

I have to admit that I have missed the addition of the possibiliy to
establish non-registration outbound flows using dialog-forming requests.

However, I unfortunately think that is going to require some more
editorial work to the spec, because parts of the documents talk about
the registation case, and some procedures seem to assume that
registrations are used, so maybe clarifications are needed that some
procedures only apply to the registration case.

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

Subclause 1 says:

"The key idea of this specification is that when a UA sends a REGISTER
request or a dialog-forming request, the proxy can later use this same
network "flow"--whether this is a bidirectional stream of UDP datagrams,
a TCP connection, or an analogous concept in another transport
protocol--to forward any incoming requests that need to go to this UA in
the context of the registration or dialog.

The text is a little confusing. It starts by talking about when a UA
sends a REGISTER, and at the end it talks about the context of a dialog.
You probably need to e.g. split the text into two parts - one talking
about the registration case, and one talking about the dialog case.

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

Also, are keep-alives sent on dialog-forming requests? The text in the
last paragraph of subclause 1 seems to indiate so.

But, the non-registration flow examples don't show any keep-alives.

Also, subclause 3.5 says:

"When the UA detects that a flow has failed or that the flow definition
has changed, the UA needs to re-register..."

Is that true if the flow was established using a dialog-forming request?
What if the UA isn't registerded in the first place...? I guess
subclause 4.5 clarifies that this only applies to registation flows, but
it would also need to be claified here.


Also, subclause 3.5.1 says:

"If the client does not receive a pong in response to its ping, it
declares the flow dead and opens a new flow in its place."

How will that be done if the flow was established using a dialog-forming
request? Will the new flow be esablished by transfering the existing
dialog?


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

Subclause 4.2.1 talks about the case when the UAC recieves a 439
resposne for the REGISTER request. But, can't it receive 439 also if it
tries to estblish the flow using a dialog-establisment request?

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


Regards,

Christer







 

-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Francois Audet
Sent: Saturday, October 04, 2008 12:57 AM
To: Dean Willis
Cc: SIP IETF
Subject: Re: [Sip] gruu in outbound-15 9.1


Thanks Dean.

This text seems perfect to me. I'll deal with it in WGLC. 

> -----Original Message-----
> From: Dean Willis [mailto:dean.willis@softarmor.com]
> Sent: Thursday, October 02, 2008 16:59
> To: Audet, Francois (SC100:3055)
> Cc: Juha Heinanen; SIP IETF
> Subject: gruu in outbound-15 9.1
> 
> >
> 
> Original text:
> 
> 
> >  If the UAC is sending a dialog-forming request, and wants all 
> > subsequent requests in the dialog to arrive over the same
> flow, the
> > UAC adds an 'ob' parameter to its Contact header.  
> Typically this is
> > desirable, but it is not necessary for example if the Contact is a 
> > GRUU [I-D.ietf-sip-gruu].  The flow used for the request is
> typically
> > the same flow the UA registered over, but it could be a new
> flow, for
> > example the initial subcription dialog for the configuration 
> > framework [I-D.ietf-sipping-config-framework] needs to
> exist before
> > registration.
> 
> 
> Proposed text:
> 
> Typically, a UAC using the procedures of this document and sending a 
> dialog-forming request will want all subsequent requests in the dialog

> to arrive over the same flow. If the UAC is using a GRUU 
> [I-D.ietf-sip-gruu] that was instantiated using a Contact header field

> value that included an "ob"
> parameter, the UAC sends teh request over the flow used for 
> registration and susequent requests will arrive over that same flow.
> If the UAC is not using such a GRUU, then the UAC adds an "ob" 
> parameter to its Contact header field value.
> This will cause all subsequent requests in the dialog to arrive over 
> the flow instantiated by the dialog-forming request. This case is 
> typical when the request is sent prior to registration, such as in the

> the initial subcription dialog for the configuration framework 
> [I-D.ietf-sipping-config-framework].
> 
> 
> --
> Dean
> 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol Use
sip-implementors@cs.columbia.edu for questions on current sip Use
sipping@ietf.org for new developments on the application of sip
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol Use
sip-implementors@cs.columbia.edu for questions on current sip Use
sipping@ietf.org for new developments on the application of sip
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct  6 12:15:04 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9CFDD28C20C;
	Mon,  6 Oct 2008 12:15:04 -0700 (PDT)
X-Original-To: sip@ietf.org
Delivered-To: sip@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 23BA428C201; Mon,  6 Oct 2008 12:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081006191502.23BA428C201@core3.amsl.com>
Date: Mon,  6 Oct 2008 12:15:02 -0700 (PDT)
Cc: sip@ietf.org
Subject: [Sip] I-D Action:draft-ietf-sip-domain-certs-02.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--NextPart

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


	Title           : Domain Certificates in the Session Initiation Protocol (SIP)
	Author(s)       : V. Gurbani, et al.
	Filename        : draft-ietf-sip-domain-certs-02.txt
	Pages           : 17
	Date            : 2008-10-06

This document describes how to interpret certain information in a
X.509 PKIX-compliant certificate used in a Session Initiation
Protocol (SIP) over Transport Layer Security (TLS) connection.  More
specifically, this document describes how to find the right identity
for authentication in such certificates and how to use that identity
for SIP domain authentication.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sip-domain-certs-02.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-sip-domain-certs-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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


From sip-bounces@ietf.org  Mon Oct  6 12:15:06 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5C94928C223;
	Mon,  6 Oct 2008 12:15:06 -0700 (PDT)
X-Original-To: sip@ietf.org
Delivered-To: sip@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 274B628C202; Mon,  6 Oct 2008 12:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081006191502.274B628C202@core3.amsl.com>
Date: Mon,  6 Oct 2008 12:15:02 -0700 (PDT)
Cc: sip@ietf.org
Subject: [Sip] I-D Action:draft-ietf-sip-eku-03.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--NextPart

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


	Title           : Using Extended Key Usage (EKU) for Session Initiation Protocol (SIP) X.509 Certificates
	Author(s)       : S. Lawrence, V. Gurbani
	Filename        : draft-ietf-sip-eku-03.txt
	Pages           : 10
	Date            : 2008-10-06

This memo documents an extended key usage (EKU) X.509 certificate
extension for identifying the holder of a certificate as
authoritative for a Session Initiation Protocol (SIP) service in the
domain named by the DNS name in the certificate.

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

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-sip-eku-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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


From sip-bounces@ietf.org  Mon Oct  6 12:16:02 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2D3DA28C21C;
	Mon,  6 Oct 2008 12:16:02 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7982B28C230
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 12:16:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id HBAezWGPyVRc for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 12:15:59 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37])
	by core3.amsl.com (Postfix) with ESMTP id 2C4C83A6AC5
	for <sip@ietf.org>; Mon,  6 Oct 2008 12:15:26 -0700 (PDT)
Received: from umail.lucent.com (h135-3-40-61.lucent.com [135.3.40.61])
	by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id m96JFVAW022969
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <sip@ietf.org>; Mon, 6 Oct 2008 14:15:31 -0500 (CDT)
Received: from [135.185.236.17] (il0015vkg1.ih.lucent.com [135.185.236.17])
	by umail.lucent.com (8.13.8/TPES) with ESMTP id m96JFV6F004389
	for <sip@ietf.org>; Mon, 6 Oct 2008 14:15:31 -0500 (CDT)
Message-ID: <48EA63D3.4040804@alcatel-lucent.com>
Date: Mon, 06 Oct 2008 14:15:31 -0500
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF SIP List <sip@ietf.org>
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Subject: [Sip] Post-WGLC version of domain-certs and sip-eku
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

All: A new version of domain-certs and sip-eku has just been
released.  This version includes the post-WGLC comments collected
during the Philadelphia and Dublin IETFs as well as the comments
by the chair (Keith Drage.)

sip-eku was also discussed extensively in the PKIX WG and
includes feedback from there as well.

This work is ready to be moved forward to the IESG.

Please let me and Scott know of any discrepancies or concerns.

Until the archive is updated, you can get a copy of the latest
versions from:

http://svn.resiprocate.org/rep/ietf-drafts/gurbani/domain-certs/draft-ietf-sip-domain-certs-02.txt
http://svn.resiprocate.org/rep/ietf-drafts/gurbani/domain-certs/draft-ietf-sip-domain-certs-02.html

http://svn.resiprocate.org/rep/ietf-drafts/gurbani/sip-eku/draft-ietf-sip-eku-03.txt
http://svn.resiprocate.org/rep/ietf-drafts/gurbani/sip-eku/draft-ietf-sip-eku-03.html

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://www.alcatel-lucent.com/bell-labs
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct  6 19:41:44 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 14B013A6B1B;
	Mon,  6 Oct 2008 19:41:44 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B66B63A6AD9
	for <sip@core3.amsl.com>; Mon,  6 Oct 2008 19:41:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.564
X-Spam-Level: 
X-Spam-Status: No, score=-3.564 tagged_above=-999 required=5 tests=[AWL=0.035, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2yY0KzelMF7E for <sip@core3.amsl.com>;
	Mon,  6 Oct 2008 19:41:42 -0700 (PDT)
Received: from TheWorld.com (pcls4.std.com [192.74.137.84])
	by core3.amsl.com (Postfix) with ESMTP id D47CB3A699E
	for <sip@ietf.org>; Mon,  6 Oct 2008 19:41:41 -0700 (PDT)
Received: from shell.TheWorld.com (IDENT:105@shell01.TheWorld.com
	[192.74.137.71])
	by TheWorld.com (8.13.6/8.13.6) with ESMTP id m972gAvd018553
	for <sip@ietf.org>; Mon, 6 Oct 2008 22:42:12 -0400
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1])
	by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id m972gAcI41636564
	for <sip@ietf.org>; Mon, 6 Oct 2008 22:42:10 -0400 (EDT)
Received: (from worley@localhost)
	by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id m972g7vC41474703;
	Mon, 6 Oct 2008 22:42:07 -0400 (EDT)
Date: Mon, 6 Oct 2008 22:42:07 -0400 (EDT)
Message-Id: <200810070242.m972g7vC41474703@shell01.TheWorld.com>
To: sip@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <9FF7202C-55A0-4635-84AC-1D7A8154C541@standardstrack.com>
	(eburger@standardstrack.com)
References: <5D1A7985295922448D5550C94DE2918002196DCC@DEEXC1U01.de.lucent.com>	<48898492.7010601@ericsson.com>	<5D1A7985295922448D5550C94DE2918002196FF7@DEEXC1U01.de.lucent.com>	<4889F09B.8050407@cisco.com>	<200809262108.m8QL8fpj34800452@shell01.TheWorld.com>	<48E0F79B.8090402@cisco.com>	<200809300309.m8U39jFX37113365@shell01.TheWorld.com>
	<9BCA68EB-2AF2-4F88-A595-B4CE1ED6475B@standardstrack.com>
	<48E3AA84.6010808@cisco.com>
	<9FF7202C-55A0-4635-84AC-1D7A8154C541@standardstrack.com>
Subject: Re: [Sip] Comments on draft-ietf-sip-body-handling-02
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

   From: Eric Burger <eburger@standardstrack.com>

   In the e-mail world, the ;handling property was created for gateways  
   (B2BUA's), so the gateway could know whether dropping a body part,  
   because the connected network/protocol could not handle that body  
   part, would render the message useless. For example, if I am using an  
   old version of Outlook, and I send you a Word file, the Word body part  
   is required for the relay, but the application/tnef (proprietary  
   Outlook stuff) is optional and the gateway can silently drop the part.

Ah!  This is an interesting difference, as the concept is that the
handling property is "global", that is, if a part labeled "required"
is necessary for successful processing of the entire message.  (As
opposed to the "local" concept, where it is only neccessary for the
successful processing of the containing multipart, whose processing
might not be necessary for processing the entire message.)

Of course, with one-level nesting, the two are equivalent.

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


From sip-bounces@ietf.org  Mon Oct  6 19:43:52 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8FB6E28C12E;
	Mon,  6 Oct 2008 19:43:52 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C170428C108;
	Mon,  6 Oct 2008 19:43:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.566
X-Spam-Level: 
X-Spam-Status: No, score=-3.566 tagged_above=-999 required=5 tests=[AWL=0.033, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id v2FF-n0jWDB9; Mon,  6 Oct 2008 19:43:50 -0700 (PDT)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146])
	by core3.amsl.com (Postfix) with ESMTP id DC07228C0F3;
	Mon,  6 Oct 2008 19:43:49 -0700 (PDT)
Received: from shell.TheWorld.com (IDENT:105@shell01.theworld.com
	[192.74.137.71])
	by TheWorld.com (8.13.6/8.13.6) with ESMTP id m972gs6V024228;
	Mon, 6 Oct 2008 22:42:56 -0400
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1])
	by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id m972gsh141383594;
	Mon, 6 Oct 2008 22:42:54 -0400 (EDT)
Received: (from worley@localhost)
	by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id m972grm741386799;
	Mon, 6 Oct 2008 22:42:53 -0400 (EDT)
Date: Mon, 6 Oct 2008 22:42:53 -0400 (EDT)
Message-Id: <200810070242.m972grm741386799@shell01.TheWorld.com>
To: pkyzivat@cisco.com
From: Dale.Worley@comcast.net
In-reply-to: <48E28DA2.5060708@cisco.com> (pkyzivat@cisco.com)
References: <5d688850809301209r6b43aeeaqa4c9f49fa2fa1706@mail.gmail.com>
	<48E28DA2.5060708@cisco.com>
Cc: sip@ietf.org, sipping@ietf.org, hasebe.miki@east.ntt.co.jp
Subject: Re: [Sip] INVITE dialogs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

   From: Paul Kyzivat <pkyzivat@cisco.com>

   I then looked at your notes. I found it very interesting that through 
   formal means you have identified a number of race conditions. I gather 
   you are not aware of:

   http://www.ietf.org/internet-drafts/draft-ietf-sipping-race-examples-06.txt

   That document has been done without benefit of formal models. But it 
   appears that there is substantial agreement about the set of race 
   conditions. (I wish you had been around when we did that work.) That 
   document is largely done, so it is likely impractical to get your input 
   into it. But take a look. It has resolutions to most of the races. If 
   you find any errors, please speak up.

It would be a very interesting "live fire demonstration" of the value
of the formalism if it discovered race conditions that we hadn't
identified by informal means.

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


From sip-bounces@ietf.org  Tue Oct  7 13:37:05 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BD0213A6B4A;
	Tue,  7 Oct 2008 13:37:05 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 868B73A6B4A
	for <sip@core3.amsl.com>; Tue,  7 Oct 2008 13:37:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.487
X-Spam-Level: 
X-Spam-Status: No, score=-6.487 tagged_above=-999 required=5 tests=[AWL=0.112, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id m2GQ-BZ5Icka for <sip@core3.amsl.com>;
	Tue,  7 Oct 2008 13:37:03 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 692253A67A7
	for <sip@ietf.org>; Tue,  7 Oct 2008 13:37:03 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,375,1220227200"; d="scan'208";a="23561124"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 07 Oct 2008 20:37:34 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m97KbXY6012192; 
	Tue, 7 Oct 2008 16:37:33 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m97KbTe2004480;
	Tue, 7 Oct 2008 20:37:33 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 7 Oct 2008 16:37:30 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 7 Oct 2008 16:37:30 -0400
Message-ID: <48EBC88B.2030300@cisco.com>
Date: Tue, 07 Oct 2008 16:37:31 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18665.43684.176244.988653@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>	<
	18665.59 269.640606.477292@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 07 Oct 2008 20:37:30.0507 (UTC)
	FILETIME=[84E0FDB0:01C928BC]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2494; t=1223411853;
	x=1224275853; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Dual=20registration=20without=2
	0Outbound |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=o+jaNX4GTxYQZQ7rUjtS6XabeEHYTBAMFUps2FENcLE=;
	b=LU+ldrQwhU3VmcuXifaGWydIOs6ucd4ht7yaQxiGP98tpalVT3bzWQ5JUR
	Ei6iBxCU1jUUy2rzz08vRsm3UPDpgOJgn6yCigj6l1VWgyBNIM6L5AyhoYRf
	+OqhecgraT;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I think I am missing something here. I presume that the knowledge of the 
UA is limited to:
- to proxy addresses
- an AOR to register

Presumably the address of the registrar is derived from the AOR to 
register by removing the user part. So the UA, when registering, doesn't 
specify two different registrars. Whether there are two or not is a 
function of how the proxy routes the register request. So whether the 
two registers for the same contact go to one registrar or two is unknown 
to the UA. In some configurations this would give you redundancy, and in 
others it would not.

Then, what causes the UA to register two different contacts? Are the 
wlan contact and the 3g contact registered to *different* AORs? If not I 
don't see the point. If anything, I would expect that 3g and wlan 
represent access networks and hence differing proxies, not AORs or 
registrars.

	Thanks,
	Paul

Christer Holmberg wrote:
> Hi, 
> 
>  > So, you want to register both contacts to both registars, right?
>  >
>  > Example:
>  >
>  > UA_Contact_wlan ----- OB_1 ----- REG_1 
>  > UA_Contact_wlan ----- OB_1 ----- REG_2
>  > UA_Contact_3g   ----- OB_2 ----- REG_1
>  > UA_Contact_3g   ----- OB_2 ----- REG_2
> 
>> no, like this:
> 
>  > UA_Contact_wlan ----- OB_1 ----- REG_1  
>  > UA_Contact_wlan ----- OB_2 ----- REG_2
>  > UA_Contact_3g   ----- OB_1 ----- REG_1
>  > UA_Contact_3g   ----- OB_2 ----- REG_2
> 
> Now, in your example, if OB_1 and REG_2 fail you don't still don't have
> redundancy :)
> 
>> if outbound does not mandate that UA must register each contact with
> both ob proxies, my pleasant surprise was a too
>> early one and ob draft falls back to the useless bin.
> 
> I don't have the spec in front of me, but I don't think it currently
> talks about multiple contacts.
> 
> I guess this all comes back to Dean's question whether we need some new
> text into the draft.
> 
> In order to avoid delaying the Outbound spec even more, I guess it could
> also be an extension draft:"Outbound with multiple contacts", or
> something like that...
> 
> Regards,
> 
> Christer
> 
> 
> 
> 
> 
> -- juha
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Tue Oct  7 14:27:15 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DC2443A69E2;
	Tue,  7 Oct 2008 14:27:15 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5EFBD3A689F
	for <sip@core3.amsl.com>; Tue,  7 Oct 2008 14:27:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.222
X-Spam-Level: 
X-Spam-Status: No, score=-6.222 tagged_above=-999 required=5 tests=[AWL=0.027, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id sbXCyeSauBSz for <sip@core3.amsl.com>;
	Tue,  7 Oct 2008 14:27:14 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 280C73A6768
	for <sip@ietf.org>; Tue,  7 Oct 2008 14:27:13 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	04F1420308; Tue,  7 Oct 2008 23:27:51 +0200 (CEST)
X-AuditID: c1b4fb3e-aa688bb000007a96-86-48ebd45610f7
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	C575F2001B; Tue,  7 Oct 2008 23:27:50 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 7 Oct 2008 23:27:50 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 7 Oct 2008 23:27:50 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8B5@esealmw113.eemea.ericsson.se>
In-Reply-To: <48EBC88B.2030300@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckovIjXnTlVjhh8QMadet9Sv5OYEgABK0sg
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18665.43684.176244.988653@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>	<
	18665.59 269.640606.477292@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
	<48EBC88B.2030300@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 07 Oct 2008 21:27:50.0553 (UTC)
	FILETIME=[8CF77090:01C928C3]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>I think I am missing something here. I presume that the knowledge of
the UA is limited to:
>- to proxy addresses
>- an AOR to register
>
>Presumably the address of the registrar is derived from the AOR to
register by removing the user part. So the UA, when 
>registering, doesn't specify two different registrars. Whether there
are two or not is a function of how the proxy routes 
>the register request. So whether the two registers for the same contact
go to one registrar or two is unknown to the UA. 
>In some configurations this would give you redundancy, and in others it
would not.
>
>Then, what causes the UA to register two different contacts? Are the
wlan contact and the 3g contact registered to 
>*different* AORs? If not I don't see the point. If anything, I would
expect that 3g and wlan represent access networks 
>and hence differing proxies, not AORs or registrars.

In the 3GPP case different contacts can be registered for the *SAME*
AOR. 

And, as you say, the edge proxies may be "access network dependent", so
it may not even be possible to e.g. register the wlan contact via the 3g
edge proxy, etc.


Regards,

Christer





	Thanks,
	Paul

Christer Holmberg wrote:
> Hi,
> 
>  > So, you want to register both contacts to both registars, right?
>  >
>  > Example:
>  >
>  > UA_Contact_wlan ----- OB_1 ----- REG_1  > UA_Contact_wlan ----- 
> OB_1 ----- REG_2
>  > UA_Contact_3g   ----- OB_2 ----- REG_1
>  > UA_Contact_3g   ----- OB_2 ----- REG_2
> 
>> no, like this:
> 
>  > UA_Contact_wlan ----- OB_1 ----- REG_1  > UA_Contact_wlan ----- 
> OB_2 ----- REG_2
>  > UA_Contact_3g   ----- OB_1 ----- REG_1
>  > UA_Contact_3g   ----- OB_2 ----- REG_2
> 
> Now, in your example, if OB_1 and REG_2 fail you don't still don't 
> have redundancy :)
> 
>> if outbound does not mandate that UA must register each contact with
> both ob proxies, my pleasant surprise was a too
>> early one and ob draft falls back to the useless bin.
> 
> I don't have the spec in front of me, but I don't think it currently 
> talks about multiple contacts.
> 
> I guess this all comes back to Dean's question whether we need some 
> new text into the draft.
> 
> In order to avoid delaying the Outbound spec even more, I guess it 
> could also be an extension draft:"Outbound with multiple contacts", or

> something like that...
> 
> Regards,
> 
> Christer
> 
> 
> 
> 
> 
> -- juha
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors@cs.columbia.edu for questions on current sip Use 
> sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Tue Oct  7 14:41:23 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 153BA3A6A2C;
	Tue,  7 Oct 2008 14:41:23 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0E14D3A684F
	for <sip@core3.amsl.com>; Tue,  7 Oct 2008 14:41:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.492
X-Spam-Level: 
X-Spam-Status: No, score=-6.492 tagged_above=-999 required=5 tests=[AWL=0.107, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QMvZtwwTibV1 for <sip@core3.amsl.com>;
	Tue,  7 Oct 2008 14:41:21 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id D8EAD3A689F
	for <sip@ietf.org>; Tue,  7 Oct 2008 14:41:20 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,375,1220227200"; d="scan'208";a="23529833"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 07 Oct 2008 21:41:30 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m97LfUk2014324; 
	Tue, 7 Oct 2008 17:41:30 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m97LfTAq026644;
	Tue, 7 Oct 2008 21:41:30 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 7 Oct 2008 17:41:30 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 7 Oct 2008 17:41:29 -0400
Message-ID: <48EBD789.5030005@cisco.com>
Date: Tue, 07 Oct 2008 17:41:29 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>	<	18665.59
	269.640606.477292@taimen.test.fi>	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>	<48EBC88B.2030300@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8B5@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F8B5@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 07 Oct 2008 21:41:29.0595 (UTC)
	FILETIME=[752754B0:01C928C5]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3704; t=1223415690;
	x=1224279690; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Dual=20registration=20without=2
	0Outbound |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=nKiAVpOIBK0T/sdhJlYKcCV3Bx0Lwa3HhPLsodWXENQ=;
	b=RoH2UDmdha+ygXn4W3XcQtrcrjrD3f2s6oo5SHiOR57YtT+f92NIyzwNV1
	HzlGq/CULo8OSTAiskimijKrZkuuGqGQU2AkP5HmI9D2HmKRa8FVVXxDGLOY
	E3i6YdUB1H;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Christer Holmberg wrote:
> Hi, 
> 
>> I think I am missing something here. I presume that the knowledge of
> the UA is limited to:
>> - to proxy addresses
>> - an AOR to register
>>
>> Presumably the address of the registrar is derived from the AOR to
> register by removing the user part. So the UA, when 
>> registering, doesn't specify two different registrars. Whether there
> are two or not is a function of how the proxy routes 
>> the register request. So whether the two registers for the same contact
> go to one registrar or two is unknown to the UA. 
>> In some configurations this would give you redundancy, and in others it
> would not.
>> Then, what causes the UA to register two different contacts? Are the
> wlan contact and the 3g contact registered to 
>> *different* AORs? If not I don't see the point. If anything, I would
> expect that 3g and wlan represent access networks 
>> and hence differing proxies, not AORs or registrars.
> 
> In the 3GPP case different contacts can be registered for the *SAME*
> AOR. 

Not just in 3gpp. That should be true most anywhere. Typically they 
represent different UAs.

The question is: why would a *single* UA establish two distinct contacts 
and register them for the same AOR?

> And, as you say, the edge proxies may be "access network dependent", so
> it may not even be possible to e.g. register the wlan contact via the 3g
> edge proxy, etc.

So you are saying that the contact addresses are themselves access 
network dependent??? So that the ip address of the contact is only 
accessible via a particular access network and proxy?

This *really* isn't the internet, is it!!!

	Paul

> Regards,
> 
> Christer
> 
> 
> 
> 
> 
> 	Thanks,
> 	Paul
> 
> Christer Holmberg wrote:
>> Hi,
>>
>>  > So, you want to register both contacts to both registars, right?
>>  >
>>  > Example:
>>  >
>>  > UA_Contact_wlan ----- OB_1 ----- REG_1  > UA_Contact_wlan ----- 
>> OB_1 ----- REG_2
>>  > UA_Contact_3g   ----- OB_2 ----- REG_1
>>  > UA_Contact_3g   ----- OB_2 ----- REG_2
>>
>>> no, like this:
>>  > UA_Contact_wlan ----- OB_1 ----- REG_1  > UA_Contact_wlan ----- 
>> OB_2 ----- REG_2
>>  > UA_Contact_3g   ----- OB_1 ----- REG_1
>>  > UA_Contact_3g   ----- OB_2 ----- REG_2
>>
>> Now, in your example, if OB_1 and REG_2 fail you don't still don't 
>> have redundancy :)
>>
>>> if outbound does not mandate that UA must register each contact with
>> both ob proxies, my pleasant surprise was a too
>>> early one and ob draft falls back to the useless bin.
>> I don't have the spec in front of me, but I don't think it currently 
>> talks about multiple contacts.
>>
>> I guess this all comes back to Dean's question whether we need some 
>> new text into the draft.
>>
>> In order to avoid delaying the Outbound spec even more, I guess it 
>> could also be an extension draft:"Outbound with multiple contacts", or
> 
>> something like that...
>>
>> Regards,
>>
>> Christer
>>
>>
>>
>>
>>
>> -- juha
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol Use 
>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>> sipping@ietf.org for new developments on the application of sip
>>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Tue Oct  7 14:52:43 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8FBEE3A6B70;
	Tue,  7 Oct 2008 14:52:43 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 46C693A695C
	for <sip@core3.amsl.com>; Tue,  7 Oct 2008 14:52:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QUP0RaTp8Xoq for <sip@core3.amsl.com>;
	Tue,  7 Oct 2008 14:52:41 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.24])
	by core3.amsl.com (Postfix) with ESMTP id 51E833A686C
	for <sip@ietf.org>; Tue,  7 Oct 2008 14:52:41 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 9so1208007eyd.31
	for <sip@ietf.org>; Tue, 07 Oct 2008 14:53:13 -0700 (PDT)
Received: by 10.210.90.8 with SMTP id n8mr3455657ebb.196.1223416393587;
	Tue, 07 Oct 2008 14:53:13 -0700 (PDT)
Received: from portatil.local (112.pool85-58-14.dynamic.orange.es
	[85.58.14.112])
	by mx.google.com with ESMTPS id q9sm16418330gve.5.2008.10.07.14.53.10
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Tue, 07 Oct 2008 14:53:12 -0700 (PDT)
From: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
To: sip@ietf.org
Date: Tue, 7 Oct 2008 23:53:07 +0200
User-Agent: KMail/1.9.9
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8B5@esealmw113.eemea.ericsson.se>
	<48EBD789.5030005@cisco.com>
In-Reply-To: <48EBD789.5030005@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810072353.07507.ibc@aliax.net>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

El Martes, 7 de Octubre de 2008, Paul Kyzivat escribi=F3:
> The question is: why would a *single* UA establish two distinct contacts
> and register them for the same AOR?

I don't know if the following is used, but I've been thinking about it:

A PBX (a UA with AoR sip:ua@domain.org) has two PSTN numbers asigned in its =

SIP provider/registrar:

1) +34111111
2) +34222222

Imagine it just creates a registration with:
  Contact: <sip:ua@UA_IP>

Then when the proxy receives a call for +34111111 or +34222222 it will =

transform the RURI into:
   INVITE sip:ua@UA_IP SIP/2.0

So how could the UA know which number was dialed? Note that reading the "To=
" =

header is not valid since the call could has been previously forwarded.


But now imagine that the UA uses two registrations, the first one with:
  Contact: <sip:+34111111@UP_IP>
and the second with:
  Contact: <sip:+34222222@UP_IP>

So if the proxy receives a call for +34111111 it could select the location =
of =

UA matching the username, and the UA would know which PSNT number was used.


Anyway I don't know how "llegal" is selecting an AoR location based on =

the "Contact" username.


-- =

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


From sip-bounces@ietf.org  Tue Oct  7 15:18:04 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 342CE28C12D;
	Tue,  7 Oct 2008 15:18:04 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 381EE3A6768
	for <sip@core3.amsl.com>; Tue,  7 Oct 2008 15:18:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.545
X-Spam-Level: 
X-Spam-Status: No, score=-2.545 tagged_above=-999 required=5 tests=[AWL=0.054, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id pKVWdAm6Rtz5 for <sip@core3.amsl.com>;
	Tue,  7 Oct 2008 15:18:02 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 5BE9E28C155
	for <sip@ietf.org>; Tue,  7 Oct 2008 15:18:02 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m97MHNJv010163
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Tue, 7 Oct 2008 17:17:25 -0500
Message-Id: <46101DEA-677B-4F28-AD1E-32F643858535@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
In-Reply-To: <48EBC88B.2030300@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 7 Oct 2008 17:17:18 -0500
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18665.43684.176244.988653@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>	<
	18665.59 269.640606.477292@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
	<48EBC88B.2030300@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: sip@ietf.org, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 7, 2008, at 3:37 PM, Paul Kyzivat wrote:

> I think I am missing something here. I presume that the knowledge of  
> the UA is limited to:
> - to proxy addresses
> - an AOR to register
>
> Presumably the address of the registrar is derived from the AOR to  
> register by removing the user part. So the UA, when registering,  
> doesn't specify two different registrars. Whether there are two or  
> not is a function of how the proxy routes the register request. So  
> whether the two registers for the same contact go to one registrar  
> or two is unknown to the UA. In some configurations this would give  
> you redundancy, and in others it would not.
>
> Then, what causes the UA to register two different contacts? Are the  
> wlan contact and the 3g contact registered to *different* AORs? If  
> not I don't see the point. If anything, I would expect that 3g and  
> wlan represent access networks and hence differing proxies, not AORs  
> or registrars.
>

Some IMS networks have mechanisms for discovering the  edge proxy  
based on the air interface. This, a UA might discover one proxy for  
its 3g interface, and another for its WLAN interface. In other words,  
one proxy for each Contact.

So, that's "proxy" discovery.

Registrar discovery is a separate process. With config-framework, the  
UA is configured with a set of proxies with which it may register.  
Under outbound-015, if there are two or more outbound proxies in the  
configured set, the UA must register through at least two of those  
proxies. This assumes a singular contact at the UA.

Juha has, IIRC, proposed that the UA must register with at least two  
of those proxies for each contact. This, I believe, has some merit.  
I'm not sure it's a MUST, but it certainly seems a reasonable SHOULD.

Of course, when the configuration mechanism is different and only one  
proxy is provided per contact, we have a different case.

It seems like we are developing two conflicted use cases here -- one  
for a singular contact with redundant registration paths, and another  
for redundant contacts, each with singular registration path.

Then there may be yet another case, multiple contacts, each with  
redundant registration paths.

--
Dean

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


From sip-bounces@ietf.org  Tue Oct  7 15:22:53 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1BEB23A6993;
	Tue,  7 Oct 2008 15:22:53 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B00873A6993
	for <sip@core3.amsl.com>; Tue,  7 Oct 2008 15:22:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.547
X-Spam-Level: 
X-Spam-Status: No, score=-2.547 tagged_above=-999 required=5 tests=[AWL=0.052, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1jSgYtbyjm8n for <sip@core3.amsl.com>;
	Tue,  7 Oct 2008 15:22:51 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id D7D493A6768
	for <sip@ietf.org>; Tue,  7 Oct 2008 15:22:50 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m97MNQgK010225
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Tue, 7 Oct 2008 17:23:27 -0500
Message-Id: <698DD02D-B015-414E-9CB3-7F8F9E64E2E8@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
In-Reply-To: <48EBD789.5030005@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 7 Oct 2008 17:23:20 -0500
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>	<	18665.59
	269.640606.477292@taimen.test.fi>	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>	<48EBC88B.2030300@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8B5@esealmw113.eemea.ericsson.se>
	! <48EBD789.5030005@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: sip@ietf.org, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 7, 2008, at 4:41 PM, Paul Kyzivat wrote:
>
>
> The question is: why would a *single* UA establish two distinct  
> contacts and register them for the same AOR?
>

Because it has two different network interfaces, with two separate IP  
addresses, and it wants to use them both in case one of those contacts  
fails. Keepalive is then used so that the proxy-registrar can note a  
failed Contact.

This is the classic dual-homed node use case, and it affects  
everything from DNS entries to BGP route advertisement. It's a general  
thorn in the sides of people who think of networks as acyclical graphs  
or trees. Sometimes, leaf nodes have multiple stems for good reasons.


>> And, as you say, the edge proxies may be "access network  
>> dependent", so
>> it may not even be possible to e.g. register the wlan contact via  
>> the 3g
>> edge proxy, etc.
>
> So you are saying that the contact addresses are themselves access  
> network dependent??? So that the ip address of the contact is only  
> accessible via a particular access network and proxy?
>
> This *really* isn't the internet, is it!!!


This isn't just a registration problem.

Imagine an enterprise that's connected to two ISPs. Each ISP provides  
an SBC for the enterprise.

Now you need two sets of telephone-routing tables to reach that  
enterprise.

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


From sip-bounces@ietf.org  Tue Oct  7 15:38:41 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6417028C0DC;
	Tue,  7 Oct 2008 15:38:41 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3CEC128C0DC
	for <sip@core3.amsl.com>; Tue,  7 Oct 2008 15:38:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.347
X-Spam-Level: 
X-Spam-Status: No, score=-6.347 tagged_above=-999 required=5
	tests=[AWL=-0.048, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Mxq3R3mLYrXS for <sip@core3.amsl.com>;
	Tue,  7 Oct 2008 15:38:39 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 29B433A685A
	for <sip@ietf.org>; Tue,  7 Oct 2008 15:38:39 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,375,1220227200"; d="scan'208";a="23539125"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 07 Oct 2008 22:38:49 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m97McnXh009539; 
	Tue, 7 Oct 2008 18:38:49 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m97Mcnag009062;
	Tue, 7 Oct 2008 22:38:49 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 7 Oct 2008 18:38:49 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 7 Oct 2008 18:38:49 -0400
Message-ID: <48EBE4F8.6080509@cisco.com>
Date: Tue, 07 Oct 2008 18:38:48 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF05C0F8B5@esealmw113.eemea.ericsson.se>	<48EBD789.5030005@cisco.com>
	<200810072353.07507.ibc@aliax.net>
In-Reply-To: <200810072353.07507.ibc@aliax.net>
X-OriginalArrivalTime: 07 Oct 2008 22:38:49.0237 (UTC)
	FILETIME=[77570C50:01C928CD]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2060; t=1223419129;
	x=1224283129; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Dual=20registration=20without=2
	0Outbound |Sender:=20
	|To:=20=3D?ISO-8859-1?Q?I=3DF1aki_Baz_Castillo?=3D=20<ibc@a
	liax.net>; bh=yE5l5dk1L4yznQqxYaoYRxuyigH2dkt3+6qVcyRdE+I=;
	b=FEn6R3ftMWFcN6abMTj4WQzuSYYrO820C7GXHZYMHI2YMennFxEAosGGxp
	TJvLNJypJN/yCp4ZcKdqu59qj1G13lrGj6GUZGPIHWvgJxMqrKAH0m8YXrj1
	1R2yoSwlSB;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: sip@ietf.org
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I=F1aki,

What you describe is perfectly fine, and is in fact the reasonable thing =

to do. You have distinct AORs corresponding to the two numbers, and a =

separate contact for each.

What I was asking about was creating multiple Contact addresses for the =

*same* AOR.

Christer has provided me with an explanation. Specifically that =

different access networks have unique ip addresses. If so, then I guess =

I would want to register them with the same AOR. And in fact, if I had =

multiple AORs to register I might want to fabricate a pair of unique =

contact addresses, each unique to the AOR but carrying the the two =

different IP addresses.

Then the question arises whether I want the registrations using the two =

contacts treated as a single flow.

	Thanks,
	Paul

I=F1aki Baz Castillo wrote:
> El Martes, 7 de Octubre de 2008, Paul Kyzivat escribi=F3:
>> The question is: why would a *single* UA establish two distinct contacts
>> and register them for the same AOR?
> =

> I don't know if the following is used, but I've been thinking about it:
> =

> A PBX (a UA with AoR sip:ua@domain.org) has two PSTN numbers asigned in i=
ts =

> SIP provider/registrar:
> =

> 1) +34111111
> 2) +34222222
> =

> Imagine it just creates a registration with:
>   Contact: <sip:ua@UA_IP>
> =

> Then when the proxy receives a call for +34111111 or +34222222 it will =

> transform the RURI into:
>    INVITE sip:ua@UA_IP SIP/2.0
> =

> So how could the UA know which number was dialed? Note that reading the "=
To" =

> header is not valid since the call could has been previously forwarded.
> =

> =

> But now imagine that the UA uses two registrations, the first one with:
>   Contact: <sip:+34111111@UP_IP>
> and the second with:
>   Contact: <sip:+34222222@UP_IP>
> =

> So if the proxy receives a call for +34111111 it could select the locatio=
n of =

> UA matching the username, and the UA would know which PSNT number was use=
d.
> =

> =

> Anyway I don't know how "llegal" is selecting an AoR location based on =

> the "Contact" username.
> =

> =

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


From sip-bounces@ietf.org  Tue Oct  7 16:33:51 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CC5CD3A67F9;
	Tue,  7 Oct 2008 16:33:51 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 12E193A67F9
	for <sip@core3.amsl.com>; Tue,  7 Oct 2008 16:33:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5
	tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_36=0.6,
	MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6Z2EpdmsjtSz for <sip@core3.amsl.com>;
	Tue,  7 Oct 2008 16:33:49 -0700 (PDT)
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184])
	by core3.amsl.com (Postfix) with ESMTP id 236053A6767
	for <sip@ietf.org>; Tue,  7 Oct 2008 16:33:48 -0700 (PDT)
Received: by nf-out-0910.google.com with SMTP id b11so1412990nfh.39
	for <sip@ietf.org>; Tue, 07 Oct 2008 16:34:15 -0700 (PDT)
Received: by 10.210.144.3 with SMTP id r3mr8874388ebd.56.1223422455632;
	Tue, 07 Oct 2008 16:34:15 -0700 (PDT)
Received: from portatil.local (112.pool85-58-14.dynamic.orange.es
	[85.58.14.112])
	by mx.google.com with ESMTPS id f13sm6467492gvd.4.2008.10.07.16.34.13
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Tue, 07 Oct 2008 16:34:14 -0700 (PDT)
From: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
To: sip@ietf.org
Date: Wed, 8 Oct 2008 01:34:09 +0200
User-Agent: KMail/1.9.9
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<200810072353.07507.ibc@aliax.net> <48EBE4F8.6080509@cisco.com>
In-Reply-To: <48EBE4F8.6080509@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810080134.10193.ibc@aliax.net>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

El Mi=E9rcoles, 8 de Octubre de 2008, Paul Kyzivat escribi=F3:
> I=F1aki,
>
> What you describe is perfectly fine, and is in fact the reasonable thing
> to do. You have distinct AORs corresponding to the two numbers, and a
> separate contact for each.
>
> What I was asking about was creating multiple Contact addresses for the
> *same* AOR.

Perpahs I didn't explain correctly:

I mean that UA (with name "a@doman.com") sends two REGISTER for the same Ao=
R:

1)
REGISTER sip:server
From: sip:a@domain.com
To: sip:a@domain.com
Contact: sip:+34111111@my_ip

1)
REGISTER sip:server
From: sip:a@domain.com
To: sip:a@domain.com
Contact: sip:+34222222@my_ip


When the proxy receives a call with RURI =3D +34111111, it ask the location =

sevice which returns "a@domain.com".
But the proxy, instead fo calling both locations in parallel (or =

sequentially), it just calls the location with the Contact username matchin=
g =

the incoming RURI (+34111111).

Not sure if it's a good idea.

Regards.



-- =

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


From sip-bounces@ietf.org  Tue Oct  7 16:45:01 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A4A3C3A689F;
	Tue,  7 Oct 2008 16:45:01 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E0B933A689F
	for <sip@core3.amsl.com>; Tue,  7 Oct 2008 16:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.532
X-Spam-Level: 
X-Spam-Status: No, score=-2.532 tagged_above=-999 required=5 tests=[AWL=0.067, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id VBJC8nafaF0N for <sip@core3.amsl.com>;
	Tue,  7 Oct 2008 16:45:00 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37])
	by core3.amsl.com (Postfix) with ESMTP id DC2D43A686C
	for <sip@ietf.org>; Tue,  7 Oct 2008 16:44:59 -0700 (PDT)
Received: from ilexp03.ndc.lucent.com (h135-3-39-50.lucent.com [135.3.39.50])
	by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id m97NjJfe019578; 
	Tue, 7 Oct 2008 18:45:34 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by
	ilexp03.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 7 Oct 2008 18:45:32 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.20]) by
	DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 8 Oct 2008 01:45:29 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 8 Oct 2008 01:45:22 +0200
Message-ID: <5D1A7985295922448D5550C94DE29180023B048B@DEEXC1U01.de.lucent.com>
In-Reply-To: <46101DEA-677B-4F28-AD1E-32F643858535@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckoyrBq+xKnvI0VSzm5Yp8d+Qx3NAAC3vEQ
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18665.43684.176244.988653@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>	<18665.59
	269.640606.477292@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se><48EBC88B.2030300@cisco.com>
	<46101DEA-677B-4F28-AD1E-32F64385! 8535@soft armor.com>
From: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: "Dean Willis" <dean.willis@softarmor.com>,
	"Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 07 Oct 2008 23:45:29.0638 (UTC)
	FILETIME=[C7C3CC60:01C928D6]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Cc: sip@ietf.org, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I am becoming concerned that we are now at this late stage going into
requirement inflation. This appears to be such.

I do not remember a requirement to provide redundant connections to
registrars as amongst the original requirements.

   1.  Must be able to detect that a UA supports these mechanisms.
   2.  Support UAs behind NATs.
   3.  Support TLS to a UA without a stable DNS name or IP address.
   4.  Detect failure of a connection and be able to correct for this.
   5.  Support many UAs simultaneously rebooting.
   6.  Support a NAT rebooting or resetting.
   7.  Minimize initial startup load on a proxy.
   8.  Support architectures with edge proxies.


Regards

Keith

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Dean Willis
> Sent: Tuesday, October 07, 2008 11:17 PM
> To: Paul Kyzivat
> Cc: sip@ietf.org; Christer Holmberg
> Subject: Re: [Sip] Dual registration without Outbound
> 
> 
> On Oct 7, 2008, at 3:37 PM, Paul Kyzivat wrote:
> 
> > I think I am missing something here. I presume that the 
> knowledge of 
> > the UA is limited to:
> > - to proxy addresses
> > - an AOR to register
> >
> > Presumably the address of the registrar is derived from the AOR to 
> > register by removing the user part. So the UA, when registering, 
> > doesn't specify two different registrars. Whether there are 
> two or not 
> > is a function of how the proxy routes the register request. 
> So whether 
> > the two registers for the same contact go to one registrar 
> or two is 
> > unknown to the UA. In some configurations this would give you 
> > redundancy, and in others it would not.
> >
> > Then, what causes the UA to register two different 
> contacts? Are the 
> > wlan contact and the 3g contact registered to *different* 
> AORs? If not 
> > I don't see the point. If anything, I would expect that 3g and wlan 
> > represent access networks and hence differing proxies, not AORs or 
> > registrars.
> >
> 
> Some IMS networks have mechanisms for discovering the  edge 
> proxy based on the air interface. This, a UA might discover 
> one proxy for its 3g interface, and another for its WLAN 
> interface. In other words, one proxy for each Contact.
> 
> So, that's "proxy" discovery.
> 
> Registrar discovery is a separate process. With 
> config-framework, the UA is configured with a set of proxies 
> with which it may register.  
> Under outbound-015, if there are two or more outbound proxies 
> in the configured set, the UA must register through at least 
> two of those proxies. This assumes a singular contact at the UA.
> 
> Juha has, IIRC, proposed that the UA must register with at 
> least two of those proxies for each contact. This, I believe, 
> has some merit.  
> I'm not sure it's a MUST, but it certainly seems a reasonable SHOULD.
> 
> Of course, when the configuration mechanism is different and 
> only one proxy is provided per contact, we have a different case.
> 
> It seems like we are developing two conflicted use cases here 
> -- one for a singular contact with redundant registration 
> paths, and another for redundant contacts, each with singular 
> registration path.
> 
> Then there may be yet another case, multiple contacts, each 
> with redundant registration paths.
> 
> --
> Dean
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors@cs.columbia.edu for questions on current sip 
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Tue Oct  7 18:04:18 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3E69528C0F8;
	Tue,  7 Oct 2008 18:04:18 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EF0B13A694C
	for <sip@core3.amsl.com>; Tue,  7 Oct 2008 18:04:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ZBHFaggb7p4D for <sip@core3.amsl.com>;
	Tue,  7 Oct 2008 18:04:16 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56])
	by core3.amsl.com (Postfix) with ESMTP id ABBFC3A6A9B
	for <sip@ietf.org>; Tue,  7 Oct 2008 18:04:15 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	m98127213850; Wed, 8 Oct 2008 01:02:07 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 7 Oct 2008 20:04:48 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF199DA2EB@zrc2hxm0.corp.nortel.com>
In-Reply-To: <5D1A7985295922448D5550C94DE29180023B048B@DEEXC1U01.de.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckoyrBq+xKnvI0VSzm5Yp8d+Qx3NAAC3vEQAAKxSbA=
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18665.43684.176244.988653@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>
	<18665.59
	269.640606.477292@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se><48EBC88B.2030300@cisco.com>
	<46101DEA-677B-4F28-AD1E-32F64385! ! 8535@so ft armor.com
	> <5D1A7985295922448D5550C94DE29180023B048B@DEEXC1U01.de.lucent.com>
From: "Francois Audet" <audet@nortel.com>
To: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>,
	"Dean Willis" <dean.willis@softarmor.com>,
	"Paul Kyzivat" <pkyzivat@cisco.com>
Cc: sip@ietf.org, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Right.

Outbound has a "redundancy" mechanism for the proxy embedded in the spec.

What is being asked is a redundancy mechanism for the UA (based on dual homing).

My reaction is that I don't see why a redundancy mechanism  for the UA should even
be tied to draft-ietf-sip-outbound. It seems to be attempting to use a small side effect
of outbound.

Rather, I think this should be a new draft, and it should be independent from outbound.
We already have a mechanism that allows for a q-value in a contact to indicate a desire for
different forking priorities.

I think another URI parameter for a Contact indicating that 2 different contacts are 
effectively the same (because of dual homing) would do the trick, and would not 
require outbound. Or maybe a parameter that says "alternative" to indicate that it's an
alternative to a specific contact (that has the advantage of telling the Registrar which
one is preferred which is apparently required).

Bottom line is I don't think Outbound is a good sledgehammer to use for this problem.

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of DRAGE, Keith (Keith)
> Sent: Tuesday, October 07, 2008 16:45
> To: Dean Willis; Paul Kyzivat
> Cc: sip@ietf.org; Christer Holmberg
> Subject: Re: [Sip] Dual registration without Outbound
> 
> I am becoming concerned that we are now at this late stage 
> going into requirement inflation. This appears to be such.
> 
> I do not remember a requirement to provide redundant 
> connections to registrars as amongst the original requirements.
> 
>    1.  Must be able to detect that a UA supports these mechanisms.
>    2.  Support UAs behind NATs.
>    3.  Support TLS to a UA without a stable DNS name or IP address.
>    4.  Detect failure of a connection and be able to correct for this.
>    5.  Support many UAs simultaneously rebooting.
>    6.  Support a NAT rebooting or resetting.
>    7.  Minimize initial startup load on a proxy.
>    8.  Support architectures with edge proxies.
> 
> 
> Regards
> 
> Keith
> 
> > -----Original Message-----
> > From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of 
> > Dean Willis
> > Sent: Tuesday, October 07, 2008 11:17 PM
> > To: Paul Kyzivat
> > Cc: sip@ietf.org; Christer Holmberg
> > Subject: Re: [Sip] Dual registration without Outbound
> > 
> > 
> > On Oct 7, 2008, at 3:37 PM, Paul Kyzivat wrote:
> > 
> > > I think I am missing something here. I presume that the
> > knowledge of
> > > the UA is limited to:
> > > - to proxy addresses
> > > - an AOR to register
> > >
> > > Presumably the address of the registrar is derived from 
> the AOR to 
> > > register by removing the user part. So the UA, when registering, 
> > > doesn't specify two different registrars. Whether there are
> > two or not
> > > is a function of how the proxy routes the register request. 
> > So whether
> > > the two registers for the same contact go to one registrar
> > or two is
> > > unknown to the UA. In some configurations this would give you 
> > > redundancy, and in others it would not.
> > >
> > > Then, what causes the UA to register two different
> > contacts? Are the
> > > wlan contact and the 3g contact registered to *different*
> > AORs? If not
> > > I don't see the point. If anything, I would expect that 
> 3g and wlan 
> > > represent access networks and hence differing proxies, 
> not AORs or 
> > > registrars.
> > >
> > 
> > Some IMS networks have mechanisms for discovering the  edge proxy 
> > based on the air interface. This, a UA might discover one proxy for 
> > its 3g interface, and another for its WLAN interface. In 
> other words, 
> > one proxy for each Contact.
> > 
> > So, that's "proxy" discovery.
> > 
> > Registrar discovery is a separate process. With 
> config-framework, the 
> > UA is configured with a set of proxies with which it may register.
> > Under outbound-015, if there are two or more outbound 
> proxies in the 
> > configured set, the UA must register through at least two of those 
> > proxies. This assumes a singular contact at the UA.
> > 
> > Juha has, IIRC, proposed that the UA must register with at 
> least two 
> > of those proxies for each contact. This, I believe, has some merit.
> > I'm not sure it's a MUST, but it certainly seems a 
> reasonable SHOULD.
> > 
> > Of course, when the configuration mechanism is different 
> and only one 
> > proxy is provided per contact, we have a different case.
> > 
> > It seems like we are developing two conflicted use cases here
> > -- one for a singular contact with redundant registration 
> paths, and 
> > another for redundant contacts, each with singular 
> registration path.
> > 
> > Then there may be yet another case, multiple contacts, each with 
> > redundant registration paths.
> > 
> > --
> > Dean
> > 
> > _______________________________________________
> > Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol Use 
> > sip-implementors@cs.columbia.edu for questions on current sip Use 
> > sipping@ietf.org for new developments on the application of sip
> > 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors@cs.columbia.edu for questions on current sip 
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Tue Oct  7 18:44:32 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 075D13A69BB;
	Tue,  7 Oct 2008 18:44:32 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 399B83A68A8
	for <sip@core3.amsl.com>; Tue,  7 Oct 2008 18:44:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.214
X-Spam-Level: 
X-Spam-Status: No, score=-6.214 tagged_above=-999 required=5 tests=[AWL=0.035, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id n-HDiDj3WzzS for <sip@core3.amsl.com>;
	Tue,  7 Oct 2008 18:44:29 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 0E4633A6837
	for <sip@ietf.org>; Tue,  7 Oct 2008 18:44:28 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	155DD20FCE; Wed,  8 Oct 2008 03:45:08 +0200 (CEST)
X-AuditID: c1b4fb3e-a6e81bb000007a96-65-48ec10a3e163
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	DE0B5200A5; Wed,  8 Oct 2008 03:45:07 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 8 Oct 2008 03:45:07 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 8 Oct 2008 03:45:06 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8B7@esealmw113.eemea.ericsson.se>
In-Reply-To: <48EBD789.5030005@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckoxXbd/DPfP8eUThS762xiaz9o5QAIX32Q
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>	<	18665.59
	269.640606.477292@taimen.test.fi>	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>	<48EBC88B.2030300@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8B5@esealmw113.eemea.ericsson.se>
	< 48EBD789 .5030005@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 08 Oct 2008 01:45:07.0403 (UTC)
	FILETIME=[7E0BD1B0:01C928E7]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>And, as you say, the edge proxies may be "access network dependent",
so it may not even be possible to e.g. register the 
>>wlan contact via the 3g edge proxy, etc.
>
>So you are saying that the contact addresses are themselves access
network dependent??? So that the ip address of the 
>contact is only accessible via a particular access network and proxy?
>
>This *really* isn't the internet, is it!!!

I am not sure I understand. Typically each access network assigns IP
addresses to the UA independent from each other. The wlan network has a
no idea what IP address the 3g network assigns to the UA, and vice
versa.

Regards,

Christer



> Regards,
> 
> Christer
> 
> 
> 
> 
> 
> 	Thanks,
> 	Paul
> 
> Christer Holmberg wrote:
>> Hi,
>>
>>  > So, you want to register both contacts to both registars, right?
>>  >
>>  > Example:
>>  >
>>  > UA_Contact_wlan ----- OB_1 ----- REG_1  > UA_Contact_wlan -----
>> OB_1 ----- REG_2
>>  > UA_Contact_3g   ----- OB_2 ----- REG_1
>>  > UA_Contact_3g   ----- OB_2 ----- REG_2
>>
>>> no, like this:
>>  > UA_Contact_wlan ----- OB_1 ----- REG_1  > UA_Contact_wlan -----
>> OB_2 ----- REG_2
>>  > UA_Contact_3g   ----- OB_1 ----- REG_1
>>  > UA_Contact_3g   ----- OB_2 ----- REG_2
>>
>> Now, in your example, if OB_1 and REG_2 fail you don't still don't 
>> have redundancy :)
>>
>>> if outbound does not mandate that UA must register each contact with
>> both ob proxies, my pleasant surprise was a too
>>> early one and ob draft falls back to the useless bin.
>> I don't have the spec in front of me, but I don't think it currently 
>> talks about multiple contacts.
>>
>> I guess this all comes back to Dean's question whether we need some 
>> new text into the draft.
>>
>> In order to avoid delaying the Outbound spec even more, I guess it 
>> could also be an extension draft:"Outbound with multiple contacts", 
>> or
> 
>> something like that...
>>
>> Regards,
>>
>> Christer
>>
>>
>>
>>
>>
>> -- juha
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol Use 
>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>> sipping@ietf.org for new developments on the application of sip
>>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors@cs.columbia.edu for questions on current sip Use 
> sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Tue Oct  7 18:48:08 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1469F3A6AFE;
	Tue,  7 Oct 2008 18:48:08 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CB9A73A6AEB
	for <sip@core3.amsl.com>; Tue,  7 Oct 2008 18:48:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.215
X-Spam-Level: 
X-Spam-Status: No, score=-6.215 tagged_above=-999 required=5 tests=[AWL=0.034, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4SBGxinS8ejF for <sip@core3.amsl.com>;
	Tue,  7 Oct 2008 18:48:06 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id B97C53A6AFE
	for <sip@ietf.org>; Tue,  7 Oct 2008 18:48:05 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	A85392079B; Wed,  8 Oct 2008 03:48:44 +0200 (CEST)
X-AuditID: c1b4fb3c-ad8cdbb0000015b5-02-48ec117c585f
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	878A72051B; Wed,  8 Oct 2008 03:48:44 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 8 Oct 2008 03:48:44 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 8 Oct 2008 03:48:43 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8B8@esealmw113.eemea.ericsson.se>
In-Reply-To: <46101DEA-677B-4F28-AD1E-32F643858535@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackoyqf4FWhgDgUuSIesB5NtpTNKuwAHPUhw
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18665.43684.176244.988653@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>	<
	18665.59 269.640606.477292@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
	<48EBC88B.2030300@cisco.com> <46101DEA-677B-4F28-AD1E-32F643
	858535@s oftarmor.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Dean Willis" <dean.willis@softarmor.com>,
	"Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 08 Oct 2008 01:48:44.0043 (UTC)
	FILETIME=[FF2C75B0:01C928E7]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 
>Registrar discovery is a separate process. With config-framework, the
UA is configured with a set of proxies with which 
>it may register.  
>Under outbound-015, if there are two or more outbound proxies in the
configured set, the UA must register through at 
>least two of those proxies. This assumes a singular contact at the UA.
>
>Juha has, IIRC, proposed that the UA must register with at least two of
those proxies for each contact. This, I believe, 
>has some merit.  
>I'm not sure it's a MUST, but it certainly seems a reasonable SHOULD.

I don't agree. In my opinion the important thing is the number of
registartions for the instance-id. Whether different contacts are used
or not is irrelevant.

Regards,

Christer

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


From sip-bounces@ietf.org  Tue Oct  7 19:54:56 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B09E53A6AF0;
	Tue,  7 Oct 2008 19:54:56 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8B0363A6AEA
	for <sip@core3.amsl.com>; Tue,  7 Oct 2008 19:54:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.766
X-Spam-Level: 
X-Spam-Status: No, score=-5.766 tagged_above=-999 required=5
	tests=[AWL=-0.417, BAYES_00=-2.599, HELO_EQ_SE=0.35,
	J_CHICKENPOX_36=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id xZVzJfs-WUWz for <sip@core3.amsl.com>;
	Tue,  7 Oct 2008 19:54:54 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 6A9923A6AF0
	for <sip@ietf.org>; Tue,  7 Oct 2008 19:54:54 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	A8A20203FE; Wed,  8 Oct 2008 04:55:33 +0200 (CEST)
X-AuditID: c1b4fb3c-ae8cfbb0000015b5-9d-48ec212540d4
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	8940520017; Wed,  8 Oct 2008 04:55:33 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 8 Oct 2008 04:55:32 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 8 Oct 2008 04:55:31 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8BC@esealmw113.eemea.ericsson.se>
In-Reply-To: <200810080134.10193.ibc@aliax.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Acko1UcIGZedeAQ4RzWQ0pICpo4C/wAGzNpg
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><200810072353.07507.ibc@aliax.net>
	<48EBE4F8.6080509@cisco.com> <200810080134.10193.ibc@aliax.net>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>,
	<sip@ietf.org>
X-OriginalArrivalTime: 08 Oct 2008 02:55:32.0987 (UTC)
	FILETIME=[54B0C4B0:01C928F1]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 =

Hi,

I am not sure I understand.

The location service does not return the AOR - it returns the contact assoc=
iated with the AOR.

So, the RURI should contain the AOR (a@domain.com), for which the location =
service then returns the two registered contacts.

Regards,

Christer

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On =

> Behalf Of I=F1aki Baz Castillo
> Sent: Wednesday, October 08, 2008 2:34 AM
> To: sip@ietf.org
> Subject: Re: [Sip] Dual registration without Outbound
> =

> El Mi=E9rcoles, 8 de Octubre de 2008, Paul Kyzivat escribi=F3:
> > I=F1aki,
> >
> > What you describe is perfectly fine, and is in fact the reasonable =

> > thing to do. You have distinct AORs corresponding to the =

> two numbers, =

> > and a separate contact for each.
> >
> > What I was asking about was creating multiple Contact addresses for =

> > the
> > *same* AOR.
> =

> Perpahs I didn't explain correctly:
> =

> I mean that UA (with name "a@doman.com") sends two REGISTER =

> for the same AoR:
> =

> 1)
> REGISTER sip:server
> From: sip:a@domain.com
> To: sip:a@domain.com
> Contact: sip:+34111111@my_ip
> =

> 1)
> REGISTER sip:server
> From: sip:a@domain.com
> To: sip:a@domain.com
> Contact: sip:+34222222@my_ip
> =

> =

> When the proxy receives a call with RURI =3D +34111111, it ask =

> the location sevice which returns "a@domain.com".
> But the proxy, instead fo calling both locations in parallel =

> (or sequentially), it just calls the location with the =

> Contact username matching the incoming RURI (+34111111).
> =

> Not sure if it's a good idea.
> =

> Regards.
> =

> =

> =

> --
> I=F1aki Baz Castillo
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use =

> sip-implementors@cs.columbia.edu for questions on current sip =

> Use sipping@ietf.org for new developments on the application of sip
> =

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


From sip-bounces@ietf.org  Tue Oct  7 20:29:02 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 56FDE3A6897;
	Tue,  7 Oct 2008 20:29:02 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 97F6A3A6897
	for <sip@core3.amsl.com>; Tue,  7 Oct 2008 20:29:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id qfu93SAxS6UB for <sip@core3.amsl.com>;
	Tue,  7 Oct 2008 20:28:59 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id 8152E3A6768
	for <sip@ietf.org>; Tue,  7 Oct 2008 20:28:58 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m983TaNk028264 for <sip@ietf.org>; Wed, 8 Oct 2008 06:29:37 +0300
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 8 Oct 2008 06:29:35 +0300
Received: from vaebe104.NOE.Nokia.com ([10.160.244.59]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 8 Oct 2008 06:29:35 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 8 Oct 2008 06:29:30 +0300
Message-ID: <C980492A76B70E4D9D5DE9299F333F1601181E4E@vaebe104.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Is GRUU generated in the case of registration with instance-ID
	and reg-ID
Thread-Index: Acko9g/3UqVCzekXRAG4ZhtoX146RA==
From: <georg.mayer@nokia.com>
To: <sip@ietf.org>
X-OriginalArrivalTime: 08 Oct 2008 03:29:35.0798 (UTC)
	FILETIME=[164CFD60:01C928F6]
X-Nokia-AV: Clean
Subject: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0332600651=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0332600651==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C928F6.15D11DF3"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C928F6.15D11DF3
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Hello,

Both Outbound and GRUU drafts make use of the instance-ID for different
purposes during SIP registration. In GRUU only the instance-ID is needed
to generate a GRUU. For Outbound both, instance-ID and reg-ID are
needed.

My question now is, whether a GRUU will be generated when a REGISTER is
received at the registrar, which indicates both reg-ID and instance-ID
in the Contact header. Reading outbound, it seems like instance-ID +
reg-ID are *only* used for outbound purposes.=20

Thanks a lot for your help.

Best regards
Georg

------_=_NextPart_001_01C928F6.15D11DF3
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.3">
<TITLE>Is GRUU generated in the case of registration with instance-ID =
and reg-ID</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">Hello,</FONT></SPAN>
</P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">Both Outbound and =
GRUU drafts make use of the instance-ID for different purposes during =
SIP registration. In GRUU only the instance-ID is needed to generate a =
GRUU. For Outbound both, instance-ID and reg-ID are =
needed.</FONT></SPAN></P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">My question now is, =
whether a GRUU will be generated when a REGISTER is received at the =
registrar, which indicates both reg-ID and instance-ID in the Contact =
header. Reading outbound, it seems like instance-ID + reg-ID are *only* =
used for outbound purposes. </FONT></SPAN></P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">Thanks a lot for your =
help.</FONT></SPAN>
</P>

<P><SPAN LANG=3D"de"><FONT SIZE=3D2 FACE=3D"Arial">Best =
regards</FONT></SPAN>

<BR><SPAN LANG=3D"de"><FONT SIZE=3D2 =
FACE=3D"Arial">Georg</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C928F6.15D11DF3--

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

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


From sip-bounces@ietf.org  Tue Oct  7 22:29:50 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 63F423A6900;
	Tue,  7 Oct 2008 22:29:50 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C3C933A6900
	for <sip@core3.amsl.com>; Tue,  7 Oct 2008 22:29:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.604
X-Spam-Level: 
X-Spam-Status: No, score=-1.604 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ygIQ1RkoaB5d for <sip@core3.amsl.com>;
	Tue,  7 Oct 2008 22:29:47 -0700 (PDT)
Received: from gws04.hcl.in (gws04.mail.hcl.in [203.105.186.20])
	by core3.amsl.com (Postfix) with ESMTP id 7D8C33A68DC
	for <sip@ietf.org>; Tue,  7 Oct 2008 22:29:47 -0700 (PDT)
Received: from gws04.hcl.in (gws04 [10.249.64.135])
	by localhost.hcl.in (Postfix) with ESMTP
	id E526D360118; Wed,  8 Oct 2008 11:00:24 +0530 (IST)
Received: from chn-egw02-out.corp.hcl.in (unknown [10.249.64.38])by 
	gws04.hcl.in (Postfix) with ESMTPid C6410360117;
	Wed,  8 Oct 2008 11:00:24 +0530 (IST)
Received: from CHN-HCLT-EVS02.HCLT.CORP.HCL.IN ([10.101.26.14]) by 
	chn-egw02-out.corp.hcl.in with Microsoft SMTPSVC(6.0.3790.3959);
	Wed, 8 Oct 2008 11:00:24 +0530
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 8 Oct 2008 11:00:00 +0530
Message-ID: <E971678290A1BA41BD96554DBA1211B6A4CF47@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: stateless proxy support Outbound ?
Thread-Index: AckpBuhC1RQZ2j7AQhqpyr+SxJKEYQ==
From: "Karthikeyan Gopal " <g_karthikeyan@hcl.in>
To: <sip-implementors@lists.cs.columbia.edu>, <sip@ietf.org>
X-OriginalArrivalTime: 08 Oct 2008 05:30:24.0474 (UTC) 
	FILETIME=[F6D92BA0:01C92906]
X-imss-version: 2.051
X-imss-result: Passed
X-imss-scanInfo: M:T L:E SM:1
X-imss-tmaseResult: TT:1 TS:-6.9747 TC:1F TRN:41 TV:5.5.1026(16204.003)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Subject: [Sip] stateless proxy support Outbound ?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0679572438=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0679572438==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C92906.E87E1279"

This is a multi-part message in MIME format.

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


Hi All,

   Can stateless proxy support Outbound?

If so why it was not mentioned clearly in draft? Where to store the flow
info?

Thanks & Regards,

Karthik

=20



DISCLAIMER:
---------------------------------------------------------------------------=
--------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and=
 intended for the named recipient(s) only=2E
It shall not attach any liability on the originator or HCL or its=
 affiliates=2E Any views or opinions presented in=20
this email are solely those of the author and may not necessarily reflect=
 the opinions of HCL or its affiliates=2E
Any form of reproduction, dissemination, copying, disclosure, modification,=
 distribution and / or publication of=20
this message without the prior written consent of the author of this e-mail=
 is strictly prohibited=2E If you have=20
received this email in error please delete it and notify the sender=
 immediately=2E Before opening any mail and=20
attachments please check them for viruses and defect=2E

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

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

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p=2EMsoNormal, li=2EMsoNormal, div=2EMsoNormal
	{margin:0in;
	margin-bottom:=2E0001pt;
	font-size:12=2E0pt;
	font-family:"Times New Roman";}
a:link, span=2EMsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span=2EMsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span=2EEmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8=2E5in 11=2E0in;
	margin:1=2E0in 1=2E25in 1=2E0in 1=2E25in;}
div=2ESection1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10=2E0pt;
font-family:Arial'>Hi All,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10=2E0pt;
font-family:Arial'>&nbsp;&nbsp; Can stateless proxy support=
 Outbound?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10=2E0pt;
font-family:Arial'>If so why it was not mentioned clearly in draft? Where=
 to store
the flow info?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10=2E0pt;
font-family:Arial'>Thanks &amp; Regards,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10=2E0pt;
font-family:Arial'>Karthik<o:p></o:p></span></font></p>

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

</div>

</body>

</html>

<table><tr><td bgcolor=3D#ffffff><font color=3D#000000>DISCLAIMER:<br>
---------------------------------------------------------------------------=
--------------------------------------------<br>
<br>
The contents of this e-mail and any attachment(s) are confidential and=
 intended for the named recipient(s) only=2E<br>
It shall not attach any liability on the originator or HCL or its=
 affiliates=2E Any views or opinions presented in <br>
this email are solely those of the author and may not necessarily reflect=
 the opinions of HCL or its affiliates=2E<br>
Any form of reproduction, dissemination, copying, disclosure, modification,=
 distribution and / or publication of <br>
this message without the prior written consent of the author of this e-mail=
 is strictly prohibited=2E If you have <br>
received this email in error please delete it and notify the sender=
 immediately=2E Before opening any mail and <br>
attachments please check them for viruses and defect=2E<br>
<br>
---------------------------------------------------------------------------=
--------------------------------------------<br>
</font></td></tr></table>
------_=_NextPart_001_01C92906.E87E1279--

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

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


From sip-bounces@ietf.org  Tue Oct  7 23:35:56 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3580D3A67FB;
	Tue,  7 Oct 2008 23:35:56 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A7B803A67A3
	for <sip@core3.amsl.com>; Tue,  7 Oct 2008 23:35:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0qCLnvMqzkNa for <sip@core3.amsl.com>;
	Tue,  7 Oct 2008 23:35:54 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id C31B23A67FB
	for <sip@ietf.org>; Tue,  7 Oct 2008 23:35:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 1CD841EC2CE;
	Wed,  8 Oct 2008 09:36:31 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id yrXsmBuhvjXl; Wed,  8 Oct 2008 09:36:28 +0300 (EEST)
Received: from taimen (h157165.gprs.dnafinland.fi [87.93.157.165])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Wed,  8 Oct 2008 09:36:28 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 04578AC061; Wed,  8 Oct 2008 09:36:22 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18668.21733.520868.113675@taimen.test.fi>
Date: Wed, 8 Oct 2008 09:36:21 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F8B8@esealmw113.eemea.ericsson.se>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>
	< 18665.59 269.640606.477292@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
	<48EBC88B.2030300@cisco.com> <46101DEA-677B-4F28-AD1E-32F643
	858535@s oftarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8B8@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > I don't agree. In my opinion the important thing is the number of
 > registartions for the instance-id. Whether different contacts are used
 > or not is irrelevant.

i don't know what instance-id is and i don't even care to know at this
point.  

the only thing that matters to me as a user is that if UA is connected
to IP networks and thus has two contacts, it must register both of them
via both of its two outbound proxies (either in a single register
request listing both contacts or in two separate register requests
listing one each).

this guarantees that if the two outbound proxies are implemented as
independent proxy/registrar pairs, inbound call to the UA via either
proxy is able to fork the call to both contacts.

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


From sip-bounces@ietf.org  Tue Oct  7 23:53:58 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6FD033A6AEB;
	Tue,  7 Oct 2008 23:53:58 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5AE0C3A68AB
	for <sip@core3.amsl.com>; Tue,  7 Oct 2008 23:53:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id yc8E4fgOkRja for <sip@core3.amsl.com>;
	Tue,  7 Oct 2008 23:53:56 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id 83B7B3A6AEB
	for <sip@ietf.org>; Tue,  7 Oct 2008 23:53:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 173011EC2CE;
	Wed,  8 Oct 2008 09:54:33 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id d2XfakQ67pD8; Wed,  8 Oct 2008 09:54:31 +0300 (EEST)
Received: from taimen (h157165.gprs.dnafinland.fi [87.93.157.165])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Wed,  8 Oct 2008 09:54:31 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id BAB34AC061; Wed,  8 Oct 2008 09:54:26 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18668.22818.736346.883984@taimen.test.fi>
Date: Wed, 8 Oct 2008 09:54:26 +0300
To: "Francois Audet" <audet@nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF199DA2EB@zrc2hxm0.corp.nortel.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>
	<18665.59 269.640606.477292@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
	<48EBC88B.2030300@cisco.com>
	<46101DEA-677B-4F28-AD1E-32F64385! ! 8535@so ft armor.com >
	<5D1A7985295922448D5550C94DE29180023B048B@DEEXC1U01.de.lucent.com>
	<1ECE0EB50388174790F9694F77522CCF199DA2EB@zrc2hxm0.corp.nortel.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Francois Audet writes:

 > Rather, I think this should be a new draft, and it should be
 > independent from outbound.

so do you now finally agree to base outbound drfat on two new drafts
that are also independent of outbound: dialog connection re-use and
keepalive?

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


From sip-bounces@ietf.org  Tue Oct  7 23:56:26 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 287EA3A6AD2;
	Tue,  7 Oct 2008 23:56:26 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ABD6728C106
	for <sip@core3.amsl.com>; Tue,  7 Oct 2008 23:56:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id qNvLTp5PfpRO for <sip@core3.amsl.com>;
	Tue,  7 Oct 2008 23:56:24 -0700 (PDT)
Received: from cluster-f.mailcontrol.com (cluster-f.mailcontrol.com
	[85.119.2.190]) by core3.amsl.com (Postfix) with ESMTP id 2F14A3A68A9
	for <sip@ietf.org>; Tue,  7 Oct 2008 23:56:23 -0700 (PDT)
Received: from rly02f.srv.mailcontrol.com (localhost.localdomain [127.0.0.1])
	by rly02f.srv.mailcontrol.com (MailControl) with ESMTP id
	m986us27022671 for <sip@ietf.org>; Wed, 8 Oct 2008 07:56:57 +0100
Received: from submission.mailcontrol.com (submission.mailcontrol.com
	[86.111.216.190])
	by rly02f.srv.mailcontrol.com (MailControl) id m986ula6022090
	for sip@ietf.org; Wed, 8 Oct 2008 07:56:47 +0100
Received: from exsmtp01.nasstar-t1.net (exsmtp01.nasstar-t1.net [89.28.233.12])
	by rly02f-eth0.srv.mailcontrol.com (envelope-sender
	attila.sipos@vegastream.com) (MIMEDefang) with ESMTP id
	m986uigB021502; Wed, 08 Oct 2008 07:56:47 +0100 (BST)
Received: from EXVS02.nasstar-t1.net ([10.2.10.104]) by
	exsmtp01.nasstar-t1.net with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 8 Oct 2008 07:57:45 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 8 Oct 2008 07:55:50 +0100
Message-ID: <680808427CF931459462C3D78CB5EC600354B48A@EXVS02.nasstar-t1.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] stateless proxy support Outbound ?
Thread-Index: AckpBuhC1RQZ2j7AQhqpyr+SxJKEYQACXHtg
From: "Attila Sipos" <attila.sipos@vegastream.com>
To: "Karthikeyan Gopal " <g_karthikeyan@hcl.in>,
	<sip-implementors@lists.cs.columbia.edu>, <sip@ietf.org>
X-OriginalArrivalTime: 08 Oct 2008 06:57:45.0434 (UTC)
	FILETIME=[2AB433A0:01C92913]
X-Scanned-By: MailControl A-08-50-15 (www.mailcontrol.com) on 10.70.1.112
Subject: Re: [Sip] stateless proxy support Outbound ?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1297849924=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1297849924==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C92913.2AE5C118"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C92913.2AE5C118
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

=20
It is possible - to do it you have to store the flow information in a
Via parameter
(or mix it into the branch, if you prefer).
=20
Unfortunately, the draft does not discuss stateless proxies
=20
=20
Regards,
=20
Attila
=20
PS I did have a discussion with someone about this but it might be
a bit confusing (it's just a big mess of e-mails).
if you want to look at some main points, here are some links:
http://www.ietf.org/mail-archive/web/sip/current/msg21238.html
http://www.ietf.org/mail-archive/web/sip/current/msg21245.html
http://www.ietf.org/mail-archive/web/sip/current/msg21249.html
http://www.ietf.org/mail-archive/web/sip/current/msg21331.html
http://www.ietf.org/mail-archive/web/sip/current/msg21344.html
=20
=20
=20
=20

________________________________

From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Karthikeyan Gopal=20
Sent: 08 October 2008 06:30
To: sip-implementors@lists.cs.columbia.edu; sip@ietf.org
Subject: [Sip] stateless proxy support Outbound ?



Hi All,

   Can stateless proxy support Outbound?

If so why it was not mentioned clearly in draft? Where to store the flow
info?

Thanks & Regards,

Karthik

DISCLAIMER:
------------------------------------------------------------------------
-----------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and
intended for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its
affiliates. Any views or opinions presented in=20
this email are solely those of the author and may not necessarily
reflect the opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure,
modification, distribution and / or publication of=20
this message without the prior written consent of the author of this
e-mail is strictly prohibited. If you have=20
received this email in error please delete it and notify the sender
immediately. Before opening any mail and=20
attachments please check them for viruses and defect.

------------------------------------------------------------------------
-----------------------------------------------
=09

------_=_NextPart_001_01C92913.2AE5C118
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML defanghtml_xmlns=3D"http://www.w3.org/TR/REC-html40"=20
defanghtml_xmlns:w=3D"urn:schemas-microsoft-com:office:word"=20
defanghtml_xmlns:o=3D"urn:schemas-microsoft-com:office:office"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.5730.13" name=3DGENERATOR>
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25i=
n; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal-compose
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D615363706-08102008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D615363706-08102008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>It is possible - to do it you have to store the fl=
ow=20
information in a Via parameter</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D615363706-08102008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>(or mix it into the branch, if you=20
prefer).</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D615363706-08102008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D615363706-08102008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Unfortunately, the draft does not discuss stateles=
s=20
proxies</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D615363706-08102008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D615363706-08102008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D615363706-08102008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D615363706-08102008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D615363706-08102008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Attila</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D615363706-08102008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D615363706-08102008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>PS I did have a discussion with someone about this=
 but it=20
might be</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D615363706-08102008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>a bit confusing (it's just a big mess of=20
e-mails).</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D615363706-08102008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>if you want to look at some main points, here are =
some=20
</FONT></SPAN><SPAN class=3D615363706-08102008><FONT face=3DArial color=3D#=
0000ff=20
size=3D2>links:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D615363706-08102008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2><A=20
href=3D"http://www.ietf.org/mail-archive/web/sip/current/msg21238.html">htt=
p://www.ietf.org/mail-archive/web/sip/current/msg21238.html</A></FONT></SPA=
N></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D615363706-08102008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2><A=20
href=3D"http://www.ietf.org/mail-archive/web/sip/current/msg21245.html">htt=
p://www.ietf.org/mail-archive/web/sip/current/msg21245.html</A></FONT></SPA=
N></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT><FONT face=3DArial color=3D#0000ff size=3D2></FONT><FONT fa=
ce=3DArial=20
color=3D#0000ff size=3D2><A=20
href=3D"http://www.ietf.org/mail-archive/web/sip/current/msg21249.html">htt=
p://www.ietf.org/mail-archive/web/sip/current/msg21249.html</A></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><A=20
href=3D"http://www.ietf.org/mail-archive/web/sip/current/msg21331.html">htt=
p://www.ietf.org/mail-archive/web/sip/current/msg21331.html</A></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><A=20
href=3D"http://www.ietf.org/mail-archive/web/sip/current/msg21344.html">htt=
p://www.ietf.org/mail-archive/web/sip/current/msg21344.html</A></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><BR></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> sip-bounces@ietf.org=20
[mailto:sip-bounces@ietf.org] <B>On Behalf Of </B>Karthikeyan Gopal=20
<BR><B>Sent:</B> 08 October 2008 06:30<BR><B>To:</B>=20
sip-implementors@lists.cs.columbia.edu; sip@ietf.org<BR><B>Subject:</B> [Si=
p]=20
stateless proxy support Outbound ?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi=20
All,<O:P></O:P></DEFANGHTML_SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; Can stateless pr=
oxy=20
support Outbound?<O:P></O:P></DEFANGHTML_SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">If so why it was not mentione=
d=20
clearly in draft? Where to store the flow=20
info?<O:P></O:P></DEFANGHTML_SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Thanks &amp;=20
Regards,<O:P></O:P></DEFANGHTML_SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Karthik<O:P></O:P></DEFANGHTM=
L_SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><O:P></O:P></DEFANGHTML_SPAN>=
</FONT></P></DIV>
<TABLE>
  <TBODY>
  <TR>
    <TD bgColor=3D#ffffff><FONT=20
      color=3D#000000>DISCLAIMER:<BR>--------------------------------------=
---------------------------------------------------------------------------=
------<BR><BR>The=20
      contents of this e-mail and any attachment(s) are confidential and=20
      intended for the named recipient(s) only.<BR>It shall not attach any=
=20
      liability on the originator or HCL or its affiliates. Any views or=20
      opinions presented in <BR>this email are solely those of the author a=
nd=20
      may not necessarily reflect the opinions of HCL or its affiliates.<BR=
>Any=20
      form of reproduction, dissemination, copying, disclosure, modificatio=
n,=20
      distribution and / or publication of <BR>this message without the pri=
or=20
      written consent of the author of this e-mail is strictly prohibited. =
If=20
      you have <BR>received this email in error please delete it and notify=
 the=20
      sender immediately. Before opening any mail and <BR>attachments pleas=
e=20
      check them for viruses and=20
      defect.<BR><BR>------------------------------------------------------=
-----------------------------------------------------------------<BR></FONT=
></TD></TR></TBODY></TABLE><br><br>
<P align=3Dleft><FONT style=3D"BACKGROUND-COLOR: #ffffff">.</FONT></P>
</body></HTML>

------_=_NextPart_001_01C92913.2AE5C118--

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

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


From sip-bounces@ietf.org  Tue Oct  7 23:56:29 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E988828C12C;
	Tue,  7 Oct 2008 23:56:28 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 405F228C135
	for <sip@core3.amsl.com>; Tue,  7 Oct 2008 23:56:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id uXrIjPeUK-CR for <sip@core3.amsl.com>;
	Tue,  7 Oct 2008 23:56:26 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id 5E11B28C130
	for <sip@ietf.org>; Tue,  7 Oct 2008 23:56:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 9B5051EC2CE;
	Wed,  8 Oct 2008 09:57:02 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id TNoMQ0IxxfMN; Wed,  8 Oct 2008 09:57:00 +0300 (EEST)
Received: from taimen (h157165.gprs.dnafinland.fi [87.93.157.165])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Wed,  8 Oct 2008 09:57:00 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id B8764AC061; Wed,  8 Oct 2008 09:56:54 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18668.22966.673918.296835@taimen.test.fi>
Date: Wed, 8 Oct 2008 09:56:54 +0300
To: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
In-Reply-To: <5D1A7985295922448D5550C94DE29180023B048B@DEEXC1U01.de.lucent.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>
	<18665.59 269.640606.477292@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
	<48EBC88B.2030300@cisco.com>
	<46101DEA-677B-4F28-AD1E-32F64385! 8535@soft armor.com>
	<5D1A7985295922448D5550C94DE29180023B048B@DEEXC1U01.de.lucent.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

DRAGE, Keith \(Keith\) writes:

 > I do not remember a requirement to provide redundant connections to
 > registrars as amongst the original requirements.

i have not asked for redundant connections to registrars.  the
connections are to outbound proxies.

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


From sip-bounces@ietf.org  Tue Oct  7 23:58:29 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C8B583A6B5E;
	Tue,  7 Oct 2008 23:58:29 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 22D3128C138
	for <sip@core3.amsl.com>; Tue,  7 Oct 2008 23:58:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.604
X-Spam-Level: 
X-Spam-Status: No, score=-1.604 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id oOfR4U2fYKxl for <sip@core3.amsl.com>;
	Tue,  7 Oct 2008 23:58:27 -0700 (PDT)
Received: from gws04.hcl.in (chn-hclin-gws02.hcl.in [203.105.186.20])
	by core3.amsl.com (Postfix) with ESMTP id E147E3A6B5E
	for <sip@ietf.org>; Tue,  7 Oct 2008 23:58:26 -0700 (PDT)
Received: from gws04.hcl.in (gws04 [10.249.64.135])
	by localhost.hcl.in (Postfix) with ESMTP
	id 18B3936008B; Wed,  8 Oct 2008 12:28:49 +0530 (IST)
Received: from chn-egw01-out.corp.hcl.in (unknown [10.249.64.37])by 
	gws04.hcl.in (Postfix) with ESMTPid F14AB36004A;
	Wed,  8 Oct 2008 12:28:48 +0530 (IST)
Received: from CHN-HCLT-EVS02.HCLT.CORP.HCL.IN ([10.101.26.14]) by 
	chn-egw01-out.corp.hcl.in with Microsoft SMTPSVC(6.0.3790.3959);
	Wed, 8 Oct 2008 12:28:48 +0530
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 8 Oct 2008 12:28:47 +0530
Message-ID: <E971678290A1BA41BD96554DBA1211B6A4D007@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Should SIP LoadBalancer add VIA header?
Thread-Index: AckpE0+7Bt7Ao7wHQZe1E2BNJyjWGg==
From: "Karthikeyan Gopal " <g_karthikeyan@hcl.in>
To: <sip-implementors@lists.cs.columbia.edu>, <sip@ietf.org>
X-OriginalArrivalTime: 08 Oct 2008 06:58:48.0673 (UTC) 
	FILETIME=[5065B510:01C92913]
X-imss-version: 2.051
X-imss-result: Passed
X-imss-scanInfo: M:T L:E SM:1
X-imss-tmaseResult: TT:1 TS:-12.2823 TC:1F TRN:43 TV:5.5.1026(16204.004)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Subject: [Sip] Should SIP LoadBalancer add VIA header?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0219178613=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0219178613==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C92913.5025DD8D"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C92913.5025DD8D
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Hi All,

  My Query:

     1=2E SIP-Load Balancer should add VIA header?

     2=2E SIP Response should traverse SIP-Loadbalancer or the SIP-Server
can send it directly to respective SIP-Client=2E

Thanks & Regards,

Karthikeyan=2EG



DISCLAIMER:
---------------------------------------------------------------------------=
--------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and=
 intended for the named recipient(s) only=2E
It shall not attach any liability on the originator or HCL or its=
 affiliates=2E Any views or opinions presented in=20
this email are solely those of the author and may not necessarily reflect=
 the opinions of HCL or its affiliates=2E
Any form of reproduction, dissemination, copying, disclosure, modification,=
 distribution and / or publication of=20
this message without the prior written consent of the author of this e-mail=
 is strictly prohibited=2E If you have=20
received this email in error please delete it and notify the sender=
 immediately=2E Before opening any mail and=20
attachments please check them for viruses and defect=2E

---------------------------------------------------------------------------=
--------------------------------------------
------_=_NextPart_001_01C92913.5025DD8D
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p=2EMsoNormal, li=2EMsoNormal, div=2EMsoNormal
	{margin:0in;
	margin-bottom:=2E0001pt;
	font-size:12=2E0pt;
	font-family:"Times New Roman";}
a:link, span=2EMsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span=2EMsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span=2EEmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8=2E5in 11=2E0in;
	margin:1=2E0in 1=2E25in 1=2E0in 1=2E25in;}
div=2ESection1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10=2E0pt;
font-family:Arial'>Hi All,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10=2E0pt;
font-family:Arial'>&nbsp; My Query:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10=2E0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp; 1=2E SIP-Load Balancer should=
 add VIA
header?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10=2E0pt;
font-family:Arial'>&nbsp;&nbsp;&nbsp;&nbsp; 2=2E SIP Response should=
 traverse
SIP-Loadbalancer or the SIP-Server can send it directly to respective
SIP-Client=2E<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10=2E0pt;
font-family:Arial'>Thanks &amp; Regards,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=
=3D'font-size:10=2E0pt;
font-family:Arial'>Karthikeyan=2EG<o:p></o:p></span></font></p>

</div>

</body>

</html>

<table><tr><td bgcolor=3D#ffffff><font color=3D#000000>DISCLAIMER:<br>
---------------------------------------------------------------------------=
--------------------------------------------<br>
<br>
The contents of this e-mail and any attachment(s) are confidential and=
 intended for the named recipient(s) only=2E<br>
It shall not attach any liability on the originator or HCL or its=
 affiliates=2E Any views or opinions presented in <br>
this email are solely those of the author and may not necessarily reflect=
 the opinions of HCL or its affiliates=2E<br>
Any form of reproduction, dissemination, copying, disclosure, modification,=
 distribution and / or publication of <br>
this message without the prior written consent of the author of this e-mail=
 is strictly prohibited=2E If you have <br>
received this email in error please delete it and notify the sender=
 immediately=2E Before opening any mail and <br>
attachments please check them for viruses and defect=2E<br>
<br>
---------------------------------------------------------------------------=
--------------------------------------------<br>
</font></td></tr></table>
------_=_NextPart_001_01C92913.5025DD8D--

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

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


From sip-bounces@ietf.org  Wed Oct  8 00:02:09 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1A43228C16D;
	Wed,  8 Oct 2008 00:02:09 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B624E28C155
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 00:02:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Y3rIxY3qphkm for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 00:02:07 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id DE2233A68AB
	for <sip@ietf.org>; Wed,  8 Oct 2008 00:02:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 0CF671EC2CE;
	Wed,  8 Oct 2008 10:02:47 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3oAr73oxR2Uo; Wed,  8 Oct 2008 10:02:44 +0300 (EEST)
Received: from taimen (h157165.gprs.dnafinland.fi [87.93.157.165])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Wed,  8 Oct 2008 10:02:44 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 0161DAC061; Wed,  8 Oct 2008 10:02:39 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18668.23311.970894.881744@taimen.test.fi>
Date: Wed, 8 Oct 2008 10:02:39 +0300
To: Paul Kyzivat <pkyzivat@cisco.com>
In-Reply-To: <48EBC88B.2030300@cisco.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>
	< 18665.59 269.640606.477292@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
	<48EBC88B.2030300@cisco.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, dean.willis@softarmor.com,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Paul Kyzivat writes:

 > Then, what causes the UA to register two different contacts? Are the 
 > wlan contact and the 3g contact registered to *different* AORs? If not I 
 > don't see the point. If anything, I would expect that 3g and wlan 
 > represent access networks and hence differing proxies, not AORs or 
 > registrars.

my sip uri is sip:jh@tutpro.com and the nokia phone on my desk is
currently registered to proxy of tutpro.com domain via both its wlan
interface and its 3g interface.  there is no need to have two different
proxies.

by the way, when my phone is on wlan and gprs network, the methods
supported by wlan contact and gprs contact are not the same (if that
matters anything to the instance-id business).

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


From sip-bounces@ietf.org  Wed Oct  8 00:47:34 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 80E6C3A6A86;
	Wed,  8 Oct 2008 00:47:34 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EB5833A6A86
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 00:47:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.579
X-Spam-Level: 
X-Spam-Status: No, score=-2.579 tagged_above=-999 required=5 tests=[AWL=0.020, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id aJpZSe1NxkNU for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 00:47:33 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id 164DC3A6B3B
	for <sip@ietf.org>; Wed,  8 Oct 2008 00:47:33 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K8E00C2STNSTS@siemenscomms.co.uk> for sip@ietf.org; Wed,
	08 Oct 2008 08:47:52 +0100 (BST)
Date: Wed, 08 Oct 2008 08:47:53 +0100
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <18668.21733.520868.113675@taimen.test.fi>
To: Juha Heinanen <jh@tutpro.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D0012686C6@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckpE2EVt0JUcuNsT+yerSppxzC+mAABkMRw
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>
	<" 18665.59 269.640606.477292"@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
	<48EBC88B.2030300@cisco.com> <"CA9998CD4A020D418654FCD EF4E707DF05C
	0F8B8"@esealmw113.eemea.ericsson.se>
	<18668.21733.520868.113675@taimen.test.fi>
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Juha Heinanen
> Sent: 08 October 2008 07:36
> To: Christer Holmberg
> Cc: sip@ietf.org; Paul Kyzivat; Dean Willis
> Subject: Re: [Sip] Dual registration without Outbound
> 
> Christer Holmberg writes:
> 
>  > I don't agree. In my opinion the important thing is the number of
>  > registartions for the instance-id. Whether different 
> contacts are used
>  > or not is irrelevant.
> 
> i don't know what instance-id is and i don't even care to know at this
> point.  
[JRE] I thought we were discussing sip-outbound. Instance-id is a
fundamental part of sip-outbound, so please read the draft. Christer is
correct - the important thing is whether the UA registers as one
instance-id or as two instance-ids (in the latter case, effectively
behaving as two UAs within the same device). This is a device decision,
and I don't believe we need normative statements in the draft to address
this. Some informative hints might be appropriate.

John



> 
> the only thing that matters to me as a user is that if UA is connected
> to IP networks and thus has two contacts, it must register 
> both of them
> via both of its two outbound proxies (either in a single register
> request listing both contacts or in two separate register requests
> listing one each).
> 
> this guarantees that if the two outbound proxies are implemented as
> independent proxy/registrar pairs, inbound call to the UA via either
> proxy is able to fork the call to both contacts.
> 
> -- juha
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct  8 00:49:06 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AC7293A6BC7;
	Wed,  8 Oct 2008 00:49:06 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 716123A6BC6
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 00:49:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.195
X-Spam-Level: 
X-Spam-Status: No, score=-6.195 tagged_above=-999 required=5 tests=[AWL=0.054, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zVcg8avpD5LN for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 00:49:04 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 3C9D63A6BA0
	for <sip@ietf.org>; Wed,  8 Oct 2008 00:49:04 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	59F9B20DAA; Wed,  8 Oct 2008 09:49:07 +0200 (CEST)
X-AuditID: c1b4fb3c-ad8cdbb0000015b5-8c-48ec65f329b1
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	205EE20816; Wed,  8 Oct 2008 09:49:07 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 8 Oct 2008 09:49:06 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 8 Oct 2008 09:49:05 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se>
In-Reply-To: <18668.21733.520868.113675@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckpEDPAGtDGAp3hRbef1d+Jd7z6IwACCvVw
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18665.43684.176244.988653@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se><18665.59
	269.640606.477292@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se><48EBC88B.2030300@cisco.com><46101DEA-677B-4F28-AD1E-32F64385853
	5@s ofta rmor.com><CA
	9998CD4A020D418654FCDEF4E707DF05C0F8B8@esealmw113.eemea.ericsson.se>
	<18668.21733.520868.113675@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 08 Oct 2008 07:49:06.0513 (UTC)
	FILETIME=[572B8C10:01C9291A]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>I don't agree. In my opinion the important thing is the number of
registartions for the instance-id. Whether 
>>different contacts are used  > or not is irrelevant.
> 
>i don't know what instance-id is and i don't even care to know at this
point. 

"instance-id:  This specification uses the word instance-id to refer
      to the value of the "sip.instance" media feature tag in the
      Contact header field.  This is a Uniform Resource Name (URN) that
      uniquely identifies this specific UA instance." 

While each registration flow gets an own reg-id, all registrations flows
from the UA shares the same instance-id.

>the only thing that matters to me as a user is that if UA is 
>connected to IP networks and thus has two contacts, it must 
>register both of them via both of its two outbound proxies 
>(either in a single register request listing both contacts or 
>in two separate register requests listing one each).
> 
>this guarantees that if the two outbound proxies are 
>implemented as independent proxy/registrar pairs, inbound 
>call to the UA via either proxy is able to fork the call to 
>both contacts.

They are still logically two separate functions, and I believe it has
been said that registrar redundancy is not within the scope.

Having said that, I don't think anything forbids you from doing what you
want. 

But, in scenarios where the outbound- and registrar proxies are NOT
co-located, and only one registrar is used, I see no reason why people
shall be forced to register both contacts to both outbound proxies. In
cases where the contact is access network dependent it may not even be
possible to do so.

Regards,

Christer

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


From sip-bounces@ietf.org  Wed Oct  8 00:52:50 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D8EA33A6B7E;
	Wed,  8 Oct 2008 00:52:50 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 173D73A6B7E
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 00:52:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.196
X-Spam-Level: 
X-Spam-Status: No, score=-6.196 tagged_above=-999 required=5 tests=[AWL=0.053, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 01x5BRxStEgt for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 00:52:49 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 49E0C3A6B47
	for <sip@ietf.org>; Wed,  8 Oct 2008 00:52:49 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	C667E21523; Wed,  8 Oct 2008 09:53:02 +0200 (CEST)
X-AuditID: c1b4fb3e-a5e7fbb000007a96-fc-48ec66a57acc
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	1561121A6F; Wed,  8 Oct 2008 09:52:05 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 8 Oct 2008 09:52:05 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 8 Oct 2008 09:52:04 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8C0@esealmw113.eemea.ericsson.se>
In-Reply-To: <18668.22966.673918.296835@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckpExJ8PaIN5GLhS46hElKWBwg6uwAB3BMQ
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18665.43684.176244.988653@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se><18665.59269.640606.477292@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se><48EBC88B.2030300@cisco.com><46101DEA-677B-4F28-AD1E-32F64385!
	85 35@soft armor.com><5
	D1A7985295922448D5550C94DE29180023B048B@DEEXC1U01.de.lucent.com>
	<18668.22966.673918.296835@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>,
	"DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
X-OriginalArrivalTime: 08 Oct 2008 07:52:05.0906 (UTC)
	FILETIME=[C218BF20:01C9291A]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 
>>I do not remember a requirement to provide redundant connections to
registrars as amongst the original requirements.
> 
>i have not asked for redundant connections to registrars. the
connections are to outbound proxies.

You talk about co-located outbound/registrar proxies, so you DO have
multiple registarars.

Regards,

Christer

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


From sip-bounces@ietf.org  Wed Oct  8 00:56:45 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 32DDB28C184;
	Wed,  8 Oct 2008 00:56:45 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7E9663A6B47
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 00:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.198
X-Spam-Level: 
X-Spam-Status: No, score=-6.198 tagged_above=-999 required=5 tests=[AWL=0.051, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QECgtwPP5J17 for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 00:56:43 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 5949A3A6B61
	for <sip@ietf.org>; Wed,  8 Oct 2008 00:56:43 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	34F1E2058E; Wed,  8 Oct 2008 09:57:10 +0200 (CEST)
X-AuditID: c1b4fb3c-ab8c9bb0000015b5-19-48ec67d6866d
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	11C402052E; Wed,  8 Oct 2008 09:57:10 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 8 Oct 2008 09:57:10 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 8 Oct 2008 09:57:08 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8C1@esealmw113.eemea.ericsson.se>
In-Reply-To: <18668.23311.970894.881744@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckpE9+UE2mtJ5wmQBC8hkfK9JukGAABukrg
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18665.43684.176244.988653@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se><
	18665.59
	269.640606.477292@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se><48EBC88B.2030300@cisco.com>
	<18668.23311.970894.881744@taimen. test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>,
	"Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 08 Oct 2008 07:57:10.0431 (UTC)
	FILETIME=[779B92F0:01C9291B]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 
>>Then, what causes the UA to register two different 
>>contacts? Are the wlan contact and the 3g contact 
>>registered to *different* AORs? If not I don't see the 
>>point. If anything, I would expect that 3g and wlan 
>>represent access networks and hence differing proxies, not 
>>AORs or registrars.
> 
>my sip uri is sip:jh@tutpro.com and the nokia phone on my 
>desk is currently registered to proxy of tutpro.com domain 
>via both its wlan interface and its 3g interface.  there is 
>no need to have two different proxies.
> 
>by the way, when my phone is on wlan and gprs network, the 
>methods supported by wlan contact and gprs contact are not 
>the same (if that matters anything to the instance-id business).

If the phone performs SIP outboun registrations over the different
accesses, I assume the instance-id value is the same for both
registrations.

And, yes, in many cases you probably will be able to reach the same
outbound/edge proxy via all accesses.

Regards,

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


From sip-bounces@ietf.org  Wed Oct  8 01:05:41 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 02DFE3A6BB9;
	Wed,  8 Oct 2008 01:05:41 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 385323A6B93
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 01:05:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.385
X-Spam-Level: 
X-Spam-Status: No, score=-0.385 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3,
	MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AOGpE-7mQ0TK for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 01:05:39 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.226])
	by core3.amsl.com (Postfix) with ESMTP id 285423A6B47
	for <sip@ietf.org>; Wed,  8 Oct 2008 01:05:15 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so3608670rvf.49
	for <sip@ietf.org>; Wed, 08 Oct 2008 01:05:34 -0700 (PDT)
Received: by 10.140.201.8 with SMTP id y8mr4690412rvf.28.1223453134432;
	Wed, 08 Oct 2008 01:05:34 -0700 (PDT)
Received: by 10.141.155.15 with HTTP; Wed, 8 Oct 2008 01:05:34 -0700 (PDT)
Message-ID: <cc1f582e0810080105j715a22c1j6bc271697c141c03@mail.gmail.com>
Date: Wed, 8 Oct 2008 10:05:34 +0200
From: "=?UTF-8?Q?I=C3=B1aki_Baz_Castillo?=" <ibc@aliax.net>
In-Reply-To: <E971678290A1BA41BD96554DBA1211B6A4D007@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
MIME-Version: 1.0
Content-Disposition: inline
References: <E971678290A1BA41BD96554DBA1211B6A4D007@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
Cc: sip@ietf.org, sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip] Should SIP LoadBalancer add VIA header?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

MjAwOC8xMC84IEthcnRoaWtleWFuIEdvcGFsIDxnX2thcnRoaWtleWFuQGhjbC5pbj46Cj4gSGkg
QWxsLAo+Cj4gICBNeSBRdWVyeToKPgo+ICAgICAgMS4gU0lQLUxvYWQgQmFsYW5jZXIgc2hvdWxk
IGFkZCBWSUEgaGVhZGVyPwoKQSBTSVAgbG9hZCBiYWxhbmRlciBpcyBpbiBmYWN0IGEgU0lQIHBy
b3h5IChnZW5lcmFsbHkgaW4gc3RhdGVsZXNzKSwKc28gaXQgbXVzdCBhZGQncyBhIFZpYSBoZWFk
ZXIuCgoKPiAgICAgIDIuIFNJUCBSZXNwb25zZSBzaG91bGQgdHJhdmVyc2UgU0lQLUxvYWRiYWxh
bmNlciBvciB0aGUgU0lQLVNlcnZlciBjYW4KPiBzZW5kIGl0IGRpcmVjdGx5IHRvIHJlc3BlY3Rp
dmUgU0lQLUNsaWVudC4KClRoZSByZXNvcG5zZSBzaG91bGQgdHJhdmVyc2UgdGhlIGxvYWQgYmFs
YW5jZXIuIFRoaXMgaXMgYnkgU0lQCmRlZmluaXRpb24uIEltYWdpbmUgdHdvIGNhc2VzOgoKMSkg
TG9hZCBiYWxhbmNlciAtLS0+IFNJUCBVRFAgLS0tPiBVQVMKSW4gdGhpcyBjYXNlIHRoZSBVQVMg
d291bGQgcmVwbHkgdG8gdGhlIFZpYSBzZW50LWJ5IGluIGNhc2UgaXQncyBlcXVhbAp0byB0aGUg
bG9hZCBiYWxhbmNlciBJUCBhZGRyZXNzLiBJbiBjYXNlIHRoZSBWaWEgc2VudC1ieSBhZGRlZCBi
eSB0aGUKbG9hZCBiYWxhbmNlciBpcyBhIGhvc3RuYW1lIHRoZW4gdGhlIFVBUyB3b3VsZCBhZGQK
InJlY2VpdmVkPVJFQUxfU09VUkNFX0lQX09GX0xPQURfQkFMQU5DRVIiIHRvIFZpYSBhbmQgc2Vu
dCByZXBsaWVzCnRoZXJlLAoKMikgTG9hZCBiYWxhbmNlciAtLS0+IFNJUCBUQ1AgLS0tPiBVQVMK
QnkgZGVmaW5pdGlvbiBhIFVBUyBtc3V0IHJlcGx5IHVzaW5nIHRoZSBpbmNvbWluZyBUQ1AgY29u
bmVjdGlvbi4KCgoKCgotLSAKScOxYWtpIEJheiBDYXN0aWxsbwo8aWJjQGFsaWF4Lm5ldD4KX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KU2lwIG1haWxpbmcg
bGlzdCAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zaXAKVGhpcyBsaXN0
IGlzIGZvciBORVcgZGV2ZWxvcG1lbnQgb2YgdGhlIGNvcmUgU0lQIFByb3RvY29sClVzZSBzaXAt
aW1wbGVtZW50b3JzQGNzLmNvbHVtYmlhLmVkdSBmb3IgcXVlc3Rpb25zIG9uIGN1cnJlbnQgc2lw
ClVzZSBzaXBwaW5nQGlldGYub3JnIGZvciBuZXcgZGV2ZWxvcG1lbnRzIG9uIHRoZSBhcHBsaWNh
dGlvbiBvZiBzaXA=


From sip-bounces@ietf.org  Wed Oct  8 01:53:54 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C97B03A6BA0;
	Wed,  8 Oct 2008 01:53:54 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 595F03A6BA0
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 01:53:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.455
X-Spam-Level: 
X-Spam-Status: No, score=-1.455 tagged_above=-999 required=5
	tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id EaN45khQABpW for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 01:53:52 -0700 (PDT)
Received: from gws03.hcl.in (chn-hclin-gws01.hcl.in [203.105.186.19])
	by core3.amsl.com (Postfix) with ESMTP id 0DC2F3A6809
	for <sip@ietf.org>; Wed,  8 Oct 2008 01:53:52 -0700 (PDT)
Received: from gws03.hcl.in (gws03 [10.249.64.134])
	by localhost.hcl.in (Postfix) with ESMTP
	id E9E8537C10A; Wed,  8 Oct 2008 14:23:30 +0530 (IST)
Received: from chn-egw02-out.corp.hcl.in (unknown [10.249.64.38])by 
	gws03.hcl.in (Postfix) with ESMTPid E03CA37C100;
	Wed,  8 Oct 2008 14:23:30 +0530 (IST)
Received: from CHN-HCLT-EVS02.HCLT.CORP.HCL.IN ([10.101.26.14]) by 
	chn-egw02-out.corp.hcl.in with Microsoft SMTPSVC(6.0.3790.3959);
	Wed, 8 Oct 2008 14:23:30 +0530
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 8 Oct 2008 14:23:16 +0530
Message-ID: <E971678290A1BA41BD96554DBA1211B6A4D0D7@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
In-Reply-To: <cc1f582e0810080105j715a22c1j6bc271697c141c03@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Should SIP LoadBalancer add VIA header?
Thread-Index: AckpHNMj52tZverfQpe4tlPsgmP4dgABfCXw
References: <E971678290A1BA41BD96554DBA1211B6A4D007@CHN-HCLT-EVS02.HCLT.CORP
	.HCL.IN> <cc1f582e0810080105j715a22c1j6bc271697c141c03@mail.gmail.com>
From: "Karthikeyan Gopal " <g_karthikeyan@hcl.in>
To: =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
X-OriginalArrivalTime: 08 Oct 2008 08:53:30.0690 (UTC) 
	FILETIME=[56662A20:01C92923]
X-imss-version: 2.051
X-imss-result: Passed
X-imss-scanInfo: M:T L:E SM:1
X-imss-tmaseResult: TT:1 TS:-17.1446 TC:1F TRN:38 TV:5.5.1026(16204.006)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: sip@ietf.org, sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip] Should SIP LoadBalancer add VIA header?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Is there any way to bypass SIP-Response?
Load on SIP-Loadbalancer gets increased when response traverse through it.

-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of I=F1a=
ki Baz Castillo
Sent: Wednesday, October 08, 2008 1:36 PM
Cc: sip@ietf.org; sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip] Should SIP LoadBalancer add VIA header?

2008/10/8 Karthikeyan Gopal <g_karthikeyan@hcl.in>:
> Hi All,
>
>   My Query:
>
>      1. SIP-Load Balancer should add VIA header?

A SIP load balander is in fact a SIP proxy (generally in stateless),
so it must add's a Via header.


>      2. SIP Response should traverse SIP-Loadbalancer or the SIP-Server c=
an
> send it directly to respective SIP-Client.

The resopnse should traverse the load balancer. This is by SIP
definition. Imagine two cases:

1) Load balancer ---> SIP UDP ---> UAS
In this case the UAS would reply to the Via sent-by in case it's equal
to the load balancer IP address. In case the Via sent-by added by the
load balancer is a hostname then the UAS would add
"received=3DREAL_SOURCE_IP_OF_LOAD_BALANCER" to Via and sent replies
there,

2) Load balancer ---> SIP TCP ---> UAS
By definition a UAS msut reply using the incoming TCP connection.





-- =

I=F1aki Baz Castillo
<ibc@aliax.net>
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip

DISCLAIMER:
---------------------------------------------------------------------------=
--------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and inte=
nded for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliate=
s. Any views or opinions presented in =

this email are solely those of the author and may not necessarily reflect t=
he opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification,=
 distribution and / or publication of =

this message without the prior written consent of the author of this e-mail=
 is strictly prohibited. If you have
received this email in error please delete it and notify the sender immedia=
tely. Before opening any mail and =

attachments please check them for viruses and defect.

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


From sip-bounces@ietf.org  Wed Oct  8 02:23:31 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 41E703A68A9;
	Wed,  8 Oct 2008 02:23:31 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BCB073A6918
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 02:23:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.554
X-Spam-Level: 
X-Spam-Status: No, score=-1.554 tagged_above=-999 required=5 tests=[AWL=0.050, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id n0yRiuMUR66F for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 02:23:28 -0700 (PDT)
Received: from gws03.hcl.in (gws03.hcl.in [203.105.186.19])
	by core3.amsl.com (Postfix) with ESMTP id 032C93A6889
	for <sip@ietf.org>; Wed,  8 Oct 2008 02:23:27 -0700 (PDT)
Received: from gws03.hcl.in (gws03 [10.249.64.134])
	by localhost.hcl.in (Postfix) with ESMTP
	id 4DD3037C121; Wed,  8 Oct 2008 14:53:16 +0530 (IST)
Received: from chn-egw01-out.corp.hcl.in (unknown [10.249.64.37])by 
	gws03.hcl.in (Postfix) with ESMTPid 11CED37C10C;
	Wed,  8 Oct 2008 14:53:15 +0530 (IST)
Received: from CHN-HCLT-EVS02.HCLT.CORP.HCL.IN ([10.101.26.14]) by 
	chn-egw01-out.corp.hcl.in with Microsoft SMTPSVC(6.0.3790.3959);
	Wed, 8 Oct 2008 14:53:14 +0530
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 8 Oct 2008 14:52:35 +0530
Message-ID: <E971678290A1BA41BD96554DBA1211B6A4D119@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
In-Reply-To: <680808427CF931459462C3D78CB5EC600354B593@EXVS02.nasstar-t1.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] stateless proxy support Outbound ?
Thread-Index: AckpBuhC1RQZ2j7AQhqpyr+SxJKEYQACXHtgAATdUrAAACki0AAAdFrg
References: <680808427CF931459462C3D78CB5EC600354B593@EXVS02.nasstar-t1.net>
From: "Karthikeyan Gopal " <g_karthikeyan@hcl.in>
To: "Attila Sipos" <attila.sipos@vegastream.com>
X-OriginalArrivalTime: 08 Oct 2008 09:23:14.0437 (UTC) 
	FILETIME=[7D985B50:01C92927]
X-imss-version: 2.051
X-imss-result: Passed
X-imss-scanInfo: M:T L:E SM:1
X-imss-tmaseResult: TT:1 TS:-29.7850 TC:1F TRN:96 TV:5.5.1026(16204.006)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Cc: sip@ietf.org, sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip] stateless proxy support Outbound ?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1393971860=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1393971860==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C92927.666A42D7"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C92927.666A42D7
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Is there any specific thing that has to be followed for UDP?

Where and what should be stored to maintain the same flow in case of
edge proxy and registrar in different node?

Why there was no discussion about mid-dialog and double record route in
outbound draft?

Regards,

Karthikeyan.G

=20

=20

________________________________

From: Attila Sipos [mailto:attila.sipos@vegastream.com]=20
Sent: Wednesday, October 08, 2008 2:32 PM
To: Karthikeyan Gopal=20
Subject: RE: [Sip] stateless proxy support Outbound ?

=20

=20

Yes, it can.

Regards,

Attila

=20

=20

________________________________

From: Karthikeyan Gopal [mailto:g_karthikeyan@hcl.in]=20
Sent: 08 October 2008 09:59
To: Attila Sipos
Subject: RE: [Sip] stateless proxy support Outbound ?

Thanks Attila.

I have one more query .Can Outbound be implemented with UDP transport?

Thanks & Regards,

Karthikeyan.G

________________________________

From: Attila Sipos [mailto:attila.sipos@vegastream.com]=20
Sent: Wednesday, October 08, 2008 12:26 PM
To: Karthikeyan Gopal ; sip-implementors@lists.cs.columbia.edu;
sip@ietf.org
Subject: RE: [Sip] stateless proxy support Outbound ?

It is possible - to do it you have to store the flow information in a
Via parameter

(or mix it into the branch, if you prefer).

Unfortunately, the draft does not discuss stateless proxies

Regards,

Attila

PS I did have a discussion with someone about this but it might be

a bit confusing (it's just a big mess of e-mails).

if you want to look at some main points, here are some links:

http://www.ietf.org/mail-archive/web/sip/current/msg21238.html

http://www.ietf.org/mail-archive/web/sip/current/msg21245.html

http://www.ietf.org/mail-archive/web/sip/current/msg21249.html

http://www.ietf.org/mail-archive/web/sip/current/msg21331.html

http://www.ietf.org/mail-archive/web/sip/current/msg21344.html

________________________________

size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>=20

From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Karthikeyan Gopal=20
Sent: 08 October 2008 06:30
To: sip-implementors@lists.cs.columbia.edu; sip@ietf.org
Subject: [Sip] stateless proxy support Outbound ?

Hi All,

   Can stateless proxy support Outbound?

If so why it was not mentioned clearly in draft? Where to store the flow
info?

Thanks & Regards,

Karthik

DISCLAIMER:
------------------------------------------------------------------------
-----------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and
intended for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its
affiliates. Any views or opinions presented in=20
this email are solely those of the author and may not necessarily
reflect the opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure,
modification, distribution and / or publication of=20
this message without the prior written consent of the author of this
e-mail is strictly prohibited. If you have=20
received this email in error please delete it and notify the sender
immediately. Before opening any mail and=20
attachments please check them for viruses and defect.

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

.

=20

.


------_=_NextPart_001_01C92927.666A42D7
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<DEFANGHTML_O:SMARTTAGTYPE name=3D"PersonName" =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"/>
</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Is there any specific thing that =
has to be
followed for UDP?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Where and what should be stored to =
maintain
the same flow in case of edge proxy and registrar in different =
node?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Why there was no discussion about =
mid-dialog
and double record route in outbound draft?<o:p></o:p></span></font></p>

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

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

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

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

<div>

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

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

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

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Attila Sipos
[mailto:attila.sipos@vegastream.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, October =
08, 2008
2:32 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> <st1:PersonName =
w:st=3D"on">Karthikeyan
 Gopal </st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [Sip] =
stateless proxy
support Outbound ?</span></font><o:p></o:p></p>

</div>

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

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

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Yes, it =
can.</span></font><o:p></o:p></p>

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

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

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

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

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

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

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

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> <st1:PersonName
w:st=3D"on">Karthikeyan Gopal =
</st1:PersonName>[mailto:g_karthikeyan@hcl.in] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 08 October 2008 =
09:59<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Attila Sipos<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [Sip] =
stateless proxy
support Outbound ?</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy =
face=3DArial><DEFANGHTML_SPAN  style=3D"FONT-SIZE: 10pt; COLOR: navy; =
FONT-FAMILY: Arial"><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Thanks =
Attila.</span><O:P></O:P></DEFANGHTML_SPAN></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy =
face=3DArial><DEFANGHTML_SPAN  style=3D"FONT-SIZE: 10pt; COLOR: navy; =
FONT-FAMILY: Arial"><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>I have one more =
query .<b><DEFANGHTML_SPAN style=3D"FONT-WEIGHT: bold"><span
style=3D'font-weight:bold'>Can Outbound be implemented with =
UDP</span></DEFANGHTML_SPAN></b>
transport?</span><O:P></O:P></DEFANGHTML_SPAN></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy =
face=3DArial><DEFANGHTML_SPAN  style=3D"FONT-SIZE: 10pt; COLOR: navy; =
FONT-FAMILY: Arial"><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Thanks &amp; =
Regards,</span><O:P></O:P></DEFANGHTML_SPAN></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy =
face=3DArial><DEFANGHTML_SPAN  style=3D"FONT-SIZE: 10pt; COLOR: navy; =
FONT-FAMILY: Arial"><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Karthikeyan.G</sp=
an><O:P></O:P></DEFANGHTML_SPAN></font><o:p></o:p></p>

<font size=3D3 face=3D"Times New Roman"><DEFANGHTML_SPAN  =
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><O:P></O:P></DEFANGHTML_SPAN></font>

<div>

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

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

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

<p class=3DMsoNormal><b><font size=3D2 =
face=3DTahoma></DEFANGHTML_SPAN><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'><DEFANGHTM=
L_SPAN  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</span></DEFANGHTML_SPAN></font></b><font
size=3D2 face=3DTahoma><DEFANGHTML_SPAN  style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma"><span
style=3D'font-size:10.0pt;font-family:Tahoma'> Attila Sipos
[mailto:attila.sipos@vegastream.com] <br>
<b><DEFANGHTML_SPAN  style=3D"FONT-WEIGHT: bold"><span =
style=3D'font-weight:bold'>Sent:</span></DEFANGHTML_SPAN></b>
Wednesday, October 08, 2008 12:26 PM<br>
<b><DEFANGHTML_SPAN  style=3D"FONT-WEIGHT: bold"><span =
style=3D'font-weight:bold'>To:</span></DEFANGHTML_SPAN></b>
<st1:PersonName w:st=3D"on"><DEFANGHTML_ST1:PERSONNAME =
u1:st=3D"on">Karthikeyan
 Gopal </st1:PersonName></DEFANGHTML_ST1:PERSONNAME>; =
sip-implementors@lists.cs.columbia.edu;
sip@ietf.org<br>
<b><DEFANGHTML_SPAN  style=3D"FONT-WEIGHT: bold"><span =
style=3D'font-weight:bold'>Subject:</span></DEFANGHTML_SPAN></b>
RE: [Sip] stateless proxy support Outbound =
?</span></DEFANGHTML_SPAN></font><O:P></O:P><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue =
face=3DArial><DEFANGHTML_SPAN  style=3D"FONT-SIZE: =
12pt"><O:P></O:P></DEFANGHTML_SPAN><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'><DEFANGHTML_SPAN =
 style=3D"FONT-SIZE: 12pt"><O:P></O:P></DEFANGHTML_SPAN><DEFANGHTML_SPAN =
 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">It
is possible - to do it you have to store the flow information in a Via =
parameter</span></DEFANGHTML_SPAN></font><O:P></O:P><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue =
face=3DArial><DEFANGHTML_SPAN  style=3D"FONT-SIZE: 10pt; COLOR: blue; =
FONT-FAMILY: Arial"><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>(or mix it into =
the
branch, if you =
prefer).</span></DEFANGHTML_SPAN></font><O:P></O:P><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue =
face=3DArial><DEFANGHTML_SPAN  style=3D"FONT-SIZE: =
12pt"><O:P></O:P></DEFANGHTML_SPAN><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'><DEFANGHTML_SPAN =
 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Unfortunately,
the draft does not discuss stateless =
proxies</span></DEFANGHTML_SPAN></font><O:P></O:P><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue =
face=3DArial><DEFANGHTML_SPAN  style=3D"FONT-SIZE: =
12pt"><O:P></O:P></DEFANGHTML_SPAN><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'><DEFANGHTML_SPAN =
 style=3D"FONT-SIZE: 12pt"><O:P></O:P></DEFANGHTML_SPAN><DEFANGHTML_SPAN =
 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Regards,</span></DEFANGHTML_SPAN></font><O:P></O:P><o:p></o:p></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dblue =
face=3DArial><DEFANGHTML_SPAN  style=3D"FONT-SIZE: =
12pt"><O:P></O:P></DEFANGHTML_SPAN><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'><DEFANGHTML_SPAN =
 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Attila</span></DEFANGHTML_SPAN></font><O:P></O:P><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue =
face=3DArial><DEFANGHTML_SPAN  style=3D"FONT-SIZE: =
12pt"><O:P></O:P></DEFANGHTML_SPAN><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'><DEFANGHTML_SPAN =
 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">PS
I did have a discussion with someone about this but it might =
be</span></DEFANGHTML_SPAN></font><O:P></O:P><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue =
face=3DArial><DEFANGHTML_SPAN  style=3D"FONT-SIZE: 10pt; COLOR: blue; =
FONT-FAMILY: Arial"><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>a bit confusing =
(it's
just a big mess of =
e-mails).</span></DEFANGHTML_SPAN></font><O:P></O:P><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue =
face=3DArial><DEFANGHTML_SPAN  style=3D"FONT-SIZE: 10pt; COLOR: blue; =
FONT-FAMILY: Arial"><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'>if you want to =
look at
some main points, here are some =
links:</span></DEFANGHTML_SPAN></font><O:P></O:P><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue =
face=3DArial><DEFANGHTML_SPAN  style=3D"FONT-SIZE: 10pt; COLOR: blue; =
FONT-FAMILY: Arial"><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'><a
href=3D"http://www.ietf.org/mail-archive/web/sip/current/msg21238.html">h=
ttp://www.ietf.org/mail-archive/web/sip/current/msg21238.html</a></span><=
/DEFANGHTML_SPAN></font><O:P></O:P><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue =
face=3DArial><DEFANGHTML_SPAN  style=3D"FONT-SIZE: 10pt; COLOR: blue; =
FONT-FAMILY: Arial"><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'><a
href=3D"http://www.ietf.org/mail-archive/web/sip/current/msg21245.html">h=
ttp://www.ietf.org/mail-archive/web/sip/current/msg21245.html</a></span><=
/DEFANGHTML_SPAN></font><O:P></O:P><o:p></o:p></p>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue =
face=3DArial><DEFANGHTML_SPAN  style=3D"FONT-SIZE: 10pt; COLOR: blue; =
FONT-FAMILY: Arial"><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'><a
href=3D"http://www.ietf.org/mail-archive/web/sip/current/msg21249.html">h=
ttp://www.ietf.org/mail-archive/web/sip/current/msg21249.html</a></span><=
/DEFANGHTML_SPAN></font><O:P></O:P><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue =
face=3DArial><DEFANGHTML_SPAN  style=3D"FONT-SIZE: 10pt; COLOR: blue; =
FONT-FAMILY: Arial"><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'><a
href=3D"http://www.ietf.org/mail-archive/web/sip/current/msg21331.html">h=
ttp://www.ietf.org/mail-archive/web/sip/current/msg21331.html</a></span><=
/DEFANGHTML_SPAN></font><O:P></O:P><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue =
face=3DArial><DEFANGHTML_SPAN  style=3D"FONT-SIZE: 10pt; COLOR: blue; =
FONT-FAMILY: Arial"><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'><a
href=3D"http://www.ietf.org/mail-archive/web/sip/current/msg21344.html">h=
ttp://www.ietf.org/mail-archive/web/sip/current/msg21344.html</a></span><=
/DEFANGHTML_SPAN></font><O:P></O:P><o:p></o:p></p>

</div>

<font size=3D3 face=3D"Times New Roman"><DEFANGHTML_SPAN  =
style=3D"FONT-SIZE: 12pt"><O:P></O:P></DEFANGHTML_SPAN></font>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><DEFANGHTML_SPAN  style=3D"FONT-SIZE: =
12pt"><O:P></O:P></DEFANGHTML_SPAN><span
style=3D'font-size:12.0pt'>

<hr<DEFANGHTML_SPAN  style=3D"FONT-SIZE: =
12pt"><O:P></O:P></DEFANGHTML_SPAN><DEFANGHTML_SPAN  style=3D"FONT-SIZE: =
12pt"><O:P></O:P></DEFANGHTML_SPAN><DEFANGHTML_SPAN  style=3D"FONT-SIZE: =
12pt"><O:P></O:P></DEFANGHTML_SPAN><DEFANGHTML_SPAN style=3D"FONT-SIZE: =
12pt">
size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

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

<p class=3DMsoNormal defanghtml_style=3D"margin-bottom:12.0pt"><b><font =
size=3D2
face=3DTahoma></DEFANGHTML_SPAN><span =
style=3D'font-size:10.0pt;font-family:Tahoma;
font-weight:bold'><DEFANGHTML_SPAN  style=3D"FONT-WEIGHT: bold; =
FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</span></DEFANGHTML_SPAN></font></b><font
size=3D2 face=3DTahoma><DEFANGHTML_SPAN  style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma"><span
style=3D'font-size:10.0pt;font-family:Tahoma'> sip-bounces@ietf.org
[mailto:sip-bounces@ietf.org] <b><DEFANGHTML_SPAN style=3D"FONT-WEIGHT: =
bold"><span
style=3D'font-weight:bold'>On Behalf Of =
</span></DEFANGHTML_SPAN></b><st1:PersonName
w:st=3D"on"><DEFANGHTML_ST1:PERSONNAME u1:st=3D"on">Karthikeyan Gopal =
</st1:PersonName><br>
</DEFANGHTML_ST1:PERSONNAME><b><DEFANGHTML_SPAN  style=3D"FONT-WEIGHT: =
bold"><span
style=3D'font-weight:bold'>Sent:</span></DEFANGHTML_SPAN></b> 08 October =
2008
06:30<br>
<b><DEFANGHTML_SPAN style=3D"FONT-WEIGHT: bold"><span =
style=3D'font-weight:bold'>To:</span></DEFANGHTML_SPAN></b>
sip-implementors@lists.cs.columbia.edu; sip@ietf.org<br>
<b><DEFANGHTML_SPAN  style=3D"FONT-WEIGHT: bold"><span =
style=3D'font-weight:bold'>Subject:</span></DEFANGHTML_SPAN></b>
[Sip] stateless proxy support Outbound =
?</span></DEFANGHTML_SPAN></font><O:P></O:P><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><DEFANGHTML_SPAN  =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><DEFANGHTML_SPAN  =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
style=3D'font-size:10.0pt;font-family:Arial'>Hi =
All,</span></DEFANGHTML_SPAN><O:P></O:P></DEFANGHTML_SPAN></font><O:P></O=
:P><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><DEFANGHTML_SPAN  =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><DEFANGHTML_SPAN  =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
style=3D'font-size:10.0pt;font-family:Arial'>&nbsp;&nbsp; Can stateless =
proxy
support =
Outbound?</span></DEFANGHTML_SPAN><O:P></O:P></DEFANGHTML_SPAN></font><O:=
P></O:P><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><DEFANGHTML_SPAN  =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><DEFANGHTML_SPAN  =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
style=3D'font-size:10.0pt;font-family:Arial'>If so why it was not =
mentioned
clearly in draft? Where to store the flow =
info?</span></DEFANGHTML_SPAN><O:P></O:P></DEFANGHTML_SPAN></font><O:P></=
O:P><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><DEFANGHTML_SPAN  =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><DEFANGHTML_SPAN  =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
style=3D'font-size:10.0pt;font-family:Arial'>Thanks &amp; =
Regards,</span></DEFANGHTML_SPAN><O:P></O:P></DEFANGHTML_SPAN></font><O:P=
></O:P><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><DEFANGHTML_SPAN  =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><DEFANGHTML_SPAN  =
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><span
style=3D'font-size:10.0pt;font-family:Arial'>Karthik</span></DEFANGHTML_S=
PAN><O:P></O:P></DEFANGHTML_SPAN></font><O:P></O:P><o:p></o:p></p>

<table class=3DMsoNormalTable border=3D0 cellpadding=3D0>
 <tr>
  <td bgcolor=3Dwhite style=3D'background:white;padding:0in 0in 0in 0in'
  defanghtml_style=3D"background:white;padding:.75pt .75pt .75pt .75pt">
  <p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New =
Roman"><DEFANGHTML_SPAN        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><O:P></O:P></DEFANGHTML_SPAN><DEFANGHTML_SPAN        =
style=3D"FONT-SIZE: 12pt; COLOR: black"><span
  style=3D'font-size:12.0pt;color:black'>DISCLAIMER:<br>
  =
-------------------------------------------------------------------------=
----------------------------------------------<br>
  <br>
  The contents of this e-mail and any attachment(s) are confidential and
  intended for the named recipient(s) only.<br>
  It shall not attach any liability on the originator or HCL or its =
affiliates.
  Any views or opinions presented in <br>
  this email are solely those of the author and may not necessarily =
reflect the
  opinions of HCL or its affiliates.<br>
  Any form of reproduction, dissemination, copying, disclosure, =
modification,
  distribution and / or publication of <br>
  this message without the prior written consent of the author of this =
e-mail
  is strictly prohibited. If you have <br>
  received this email in error please delete it and notify the sender
  immediately. Before opening any mail and <br>
  attachments please check them for viruses and defect.<br>
  <br>
  =
-------------------------------------------------------------------------=
----------------------------------------------</span></DEFANGHTML_SPAN></=
font><O:P></O:P><o:p></o:p></p>
  </td>
 </tr>
</table>

<p defanghtml_style=3D"margin-bottom:12.0pt"><font size=3D3 =
face=3D"Times New Roman"><DEFANGHTML_SPAN  style=3D"FONT-SIZE: =
12pt"><O:P></O:P></DEFANGHTML_SPAN><span
style=3D'font-size:12.0pt'><DEFANGHTML_SPAN  style=3D"FONT-SIZE: 12pt; =
BACKGROUND: =
white">.<o:p></o:p></span></DEFANGHTML_SPAN><O:P></O:P></font></p>

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

<p><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;
background:white'>.</span><o:p></o:p></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C92927.666A42D7--

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

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


From sip-bounces@ietf.org  Wed Oct  8 03:14:55 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7B38B3A69DB;
	Wed,  8 Oct 2008 03:14:55 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7D1BC3A69DB
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 03:14:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.385
X-Spam-Level: 
X-Spam-Status: No, score=-0.385 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3,
	MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rFaMf151WyVq for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 03:14:53 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.234])
	by core3.amsl.com (Postfix) with ESMTP id DD2133A677E
	for <sip@ietf.org>; Wed,  8 Oct 2008 03:14:53 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so3664165rvf.49
	for <sip@ietf.org>; Wed, 08 Oct 2008 03:14:57 -0700 (PDT)
Received: by 10.141.29.8 with SMTP id g8mr4764400rvj.62.1223460897773;
	Wed, 08 Oct 2008 03:14:57 -0700 (PDT)
Received: by 10.141.155.15 with HTTP; Wed, 8 Oct 2008 03:14:57 -0700 (PDT)
Message-ID: <cc1f582e0810080314x1be5d99ajb3ee53edbf189d8f@mail.gmail.com>
Date: Wed, 8 Oct 2008 12:14:57 +0200
From: "=?UTF-8?Q?I=C3=B1aki_Baz_Castillo?=" <ibc@aliax.net>
In-Reply-To: <E971678290A1BA41BD96554DBA1211B6A4D0D7@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
MIME-Version: 1.0
Content-Disposition: inline
References: <cc1f582e0810080105j715a22c1j6bc271697c141c03@mail.gmail.com>
	<E971678290A1BA41BD96554DBA1211B6A4D0D7@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
Cc: sip@ietf.org, sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip] Should SIP LoadBalancer add VIA header?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

MjAwOC8xMC84IEthcnRoaWtleWFuIEdvcGFsIDxnX2thcnRoaWtleWFuQGhjbC5pbj46Cj4KPiBJ
cyB0aGVyZSBhbnkgd2F5IHRvIGJ5cGFzcyBTSVAtUmVzcG9uc2U/Cj4gTG9hZCBvbiBTSVAtTG9h
ZGJhbGFuY2VyIGdldHMgaW5jcmVhc2VkIHdoZW4gcmVzcG9uc2UgdHJhdmVyc2UgdGhyb3VnaCBp
dC4KCk5vdCBBRkFJSy4gVGhpcyBpcyBob3cgU0lQIHdvcmtzLgoKQW55d2F5LCBub3RlIHRoYXQg
b25seSB0aGUgaW5pdGlhbCB0cmFuc2FjdGlvbiAocmVxdWVzdCArIHJlc3BvbnNlcykKd2lsbCB1
c2UgdGhlIGxvYWQgYmFsYW5jZXIuIFRoZSBmb2xsb3dpbmcgaW4tZGlhbG9nIHJlcXVlc3Qgd2ls
bCBnbwpkaXJlY3RseSBmcm9tIGFjbGxlciB0byBjYWxsZWUgKGlmIGxvYWQgYmFsYW5jaW5nIHBy
b3h5IGRvZXNuJ3QgYWRkClJlY29yZC1Sb3V0ZSkuCgoKCgotLSAKScOxYWtpIEJheiBDYXN0aWxs
bwo8aWJjQGFsaWF4Lm5ldD4KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18KU2lwIG1haWxpbmcgbGlzdCAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9zaXAKVGhpcyBsaXN0IGlzIGZvciBORVcgZGV2ZWxvcG1lbnQgb2YgdGhlIGNvcmUg
U0lQIFByb3RvY29sClVzZSBzaXAtaW1wbGVtZW50b3JzQGNzLmNvbHVtYmlhLmVkdSBmb3IgcXVl
c3Rpb25zIG9uIGN1cnJlbnQgc2lwClVzZSBzaXBwaW5nQGlldGYub3JnIGZvciBuZXcgZGV2ZWxv
cG1lbnRzIG9uIHRoZSBhcHBsaWNhdGlvbiBvZiBzaXA=


From sip-bounces@ietf.org  Wed Oct  8 04:05:35 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AD4C53A6A62;
	Wed,  8 Oct 2008 04:05:35 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BA9063A6A62
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 04:05:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RGBILISMLLLY for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 04:05:32 -0700 (PDT)
Received: from cluster-f.mailcontrol.com (cluster-f.mailcontrol.com
	[85.119.2.190]) by core3.amsl.com (Postfix) with ESMTP id 52BCC3A6846
	for <sip@ietf.org>; Wed,  8 Oct 2008 04:05:31 -0700 (PDT)
Received: from rly41f.srv.mailcontrol.com (localhost.localdomain [127.0.0.1])
	by rly41f.srv.mailcontrol.com (MailControl) with ESMTP id
	m98B5bhC012905 for <sip@ietf.org>; Wed, 8 Oct 2008 12:06:02 +0100
Received: from submission.mailcontrol.com (submission.mailcontrol.com
	[86.111.216.190])
	by rly41f.srv.mailcontrol.com (MailControl) id m98B5IUr010268
	for sip@ietf.org; Wed, 8 Oct 2008 12:05:18 +0100
Received: from exsmtp02.nasstar-t1.net (exsmtp02.nasstar-t1.net
	[89.28.233.152]) by rly41f-eth0.srv.mailcontrol.com (envelope-sender
	attila.sipos@vegastream.com) (MIMEDefang) with ESMTP id
	m98B4o0v006359; Wed, 08 Oct 2008 12:05:18 +0100 (BST)
Received: from EXVS02.nasstar-t1.net ([10.2.10.104]) by
	exsmtp02.nasstar-t1.net with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 8 Oct 2008 12:03:35 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 8 Oct 2008 12:01:41 +0100
Message-ID: <680808427CF931459462C3D78CB5EC600354B702@EXVS02.nasstar-t1.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] stateless proxy support Outbound ?
Thread-Index: AckpBuhC1RQZ2j7AQhqpyr+SxJKEYQACXHtgAATdUrAAACki0AAAdFrgAANx+LA=
From: "Attila Sipos" <attila.sipos@vegastream.com>
To: "Karthikeyan Gopal " <g_karthikeyan@hcl.in>
X-OriginalArrivalTime: 08 Oct 2008 11:03:35.0838 (UTC)
	FILETIME=[82A13BE0:01C92935]
X-Scanned-By: MailControl A-08-50-15 (www.mailcontrol.com) on 10.70.1.151
Cc: sip@ietf.org, sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip] stateless proxy support Outbound ?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1289728464=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1289728464==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C92935.8252A034"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C92935.8252A034
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

>>Is there any specific thing that has to be followed for UDP?

=20
Not really.  As long the as flow token stored in the Via records the
remote IP and port.
=20
For TCP, you need to record the socket number and make sure you don't
close
the socket (you can close it after the keepalive has expired)
=20
=20

>>Where and what should be stored to maintain the same flow in case of
edge proxy and registrar in different node?

This is a little bit harder.
If proxy and registrar are in the same node, it's quite easy.
=20
If not in the same node, then I'd recommend Sergio's comments from here:
http://www.ietf.org/mail-archive/web/sip/current/msg21331.html
=20
putting his comments together:
>>   Our approach tries to use the flow token also in responses: we just
>>put the flow token in the Via. As mentioned before:
>>   -the UA stores the flow token when it receives a 200 OK after
REGISTER;
>>   -then it puts it into every SIP request that is sent over a flow;
>>   -then the edge proxy copies the flow token to the URI part of the
Via
>>when it composes the Via before to forward the message.
>>   -Later, when the response arrives at the edge proxy, it tries to
>>decode the flow token in the Via, if it succeeds, it  forwards the
>>response over the flow indicated in the flow token.

=20
>>Why there was no discussion about mid-dialog and double record route
in outbound draft?

No idea.  Maybe it was considered too awkward.
=20
Regards,

Attila
=20
=20
=20
________________________________

From: Karthikeyan Gopal [mailto:g_karthikeyan@hcl.in]=20
Sent: 08 October 2008 10:23
To: Attila Sipos
Cc: sip@ietf.org; sip-implementors@lists.cs.columbia.edu
Subject: RE: [Sip] stateless proxy support Outbound ?



Is there any specific thing that has to be followed for UDP?

Where and what should be stored to maintain the same flow in case of
edge proxy and registrar in different node?

Why there was no discussion about mid-dialog and double record route in
outbound draft?

Regards,

Karthikeyan.G

________________________________

From: Attila Sipos [mailto:attila.sipos@vegastream.com]=20
Sent: Wednesday, October 08, 2008 2:32 PM
To: Karthikeyan Gopal=20
Subject: RE: [Sip] stateless proxy support Outbound ?

Yes, it can.

Regards,

Attila

________________________________

From: Karthikeyan Gopal [mailto:g_karthikeyan@hcl.in]=20
Sent: 08 October 2008 09:59
To: Attila Sipos
Subject: RE: [Sip] stateless proxy support Outbound ?

Thanks Attila.

I have one more query .Can Outbound be implemented with UDP transport?

Thanks & Regards,

Karthikeyan.G

________________________________

From: Attila Sipos [mailto:attila.sipos@vegastream.com]=20
Sent: Wednesday, October 08, 2008 12:26 PM
To: Karthikeyan Gopal ; sip-implementors@lists.cs.columbia.edu;
sip@ietf.org
Subject: RE: [Sip] stateless proxy support Outbound ?

It is possible - to do it you have to store the flow information in a
Via parameter

(or mix it into the branch, if you prefer).

Unfortunately, the draft does not discuss stateless proxies

Regards,

Attila

PS I did have a discussion with someone about this but it might be

a bit confusing (it's just a big mess of e-mails).

if you want to look at some main points, here are some links:

http://www.ietf.org/mail-archive/web/sip/current/msg21238.html

http://www.ietf.org/mail-archive/web/sip/current/msg21245.html

http://www.ietf.org/mail-archive/web/sip/current/msg21249.html

http://www.ietf.org/mail-archive/web/sip/current/msg21331.html

http://www.ietf.org/mail-archive/web/sip/current/msg21344.html

________________________________

size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>=20

From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Karthikeyan Gopal=20
Sent: 08 October 2008 06:30
To: sip-implementors@lists.cs.columbia.edu; sip@ietf.org
Subject: [Sip] stateless proxy support Outbound ?

Hi All,

   Can stateless proxy support Outbound?

If so why it was not mentioned clearly in draft? Where to store the flow
info?

Thanks & Regards,

Karthik

DISCLAIMER:
------------------------------------------------------------------------
-----------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and
intended for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its
affiliates. Any views or opinions presented in=20
this email are solely those of the author and may not necessarily
reflect the opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure,
modification, distribution and / or publication of=20
this message without the prior written consent of the author of this
e-mail is strictly prohibited. If you have=20
received this email in error please delete it and notify the sender
immediately. Before opening any mail and=20
attachments please check them for viruses and defect.

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

=2E

=2E


------_=_NextPart_001_01C92935.8252A034
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML defanghtml_xmlns:v=3D"urn:schemas-microsoft-com:vml"=20
defanghtml_xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags"=20
defanghtml_xmlns=3D"http://www.w3.org/TR/REC-html40"=20
defanghtml_xmlns:w=3D"urn:schemas-microsoft-com:office:word"=20
defanghtml_xmlns:o=3D"urn:schemas-microsoft-com:office:office"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.5730.13" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><DEFANGHTML_O:SMARTTAGTYPE name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" /><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times =
New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
	COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle19 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle20 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<DEFANGHTML_O:SMARTTAGTYPE name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" /></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff>
<P class=3DMsoNormal><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN=20
class=3D476095310-08102008>&gt;&gt;</SPAN>Is there any specific thing that =
has to=20
be followed for UDP?<?XML:NAMESPACE PREFIX =3D O=20
/><O:P></O:P></SPAN></P></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D476095310-08102008>Not really.&nbsp; As long the as flow token stor=
ed in=20
the Via records the </SPAN></FONT><FONT face=3DArial color=3D#0000ff size=
=3D2><SPAN=20
class=3D476095310-08102008>remote IP and port.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D476095310-08102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D476095310-08102008>For TCP, you need to record the socket number an=
d make=20
sure you don't close</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D476095310-08102008>the socket (you can close it after the keepalive=
 has=20
expired)</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft>
<P class=3DMsoNormal><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN=20
class=3D476095310-08102008>&gt;&gt;</SPAN>Where and what should be stored t=
o=20
maintain the same flow in case of edge proxy and registrar in different=20
node?<O:P></O:P></SPAN></P></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D476095310-08102008>This is a little bit harder.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D476095310-08102008>If proxy and registrar are in the same node, it'=
s quite=20
easy.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D476095310-08102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D476095310-08102008>If not in the same node, then I'd recommend Serg=
io's=20
comments from here:</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><A=
=20
href=3D"http://www.ietf.org/mail-archive/web/sip/current/msg21331.html">htt=
p://www.ietf.org/mail-archive/web/sip/current/msg21331.html</A></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D476095310-08102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D476095310-08102008>putting his comments together:</SPAN></FONT></DI=
V>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D476095310-08102008></SPAN></FONT><FONT face=3DArial color=3D#0000ff=
=20
size=3D2><SPAN class=3D476095310-08102008></SPAN></FONT><FONT face=3DArial=
=20
color=3D#0000ff size=3D2><SPAN class=3D476095310-08102008>&gt;&gt;&nbsp;&nb=
sp; Our=20
approach tries to use the flow token also in responses: we just<BR>&gt;&gt;=
put=20
the flow token in the Via. As mentioned before:<BR>&gt;&gt;&nbsp;&nbsp; -th=
e UA=20
stores the flow token when it receives a 200 OK after=20
REGISTER;<BR>&gt;&gt;&nbsp;&nbsp; -then it puts it into every SIP request t=
hat=20
is sent over a flow;<BR>&gt;&gt;&nbsp;&nbsp; -then the edge proxy copies th=
e=20
flow token to the URI part of the Via<BR>&gt;&gt;when it composes the Via b=
efore=20
to forward the message.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D476095310-08102008>&gt;&gt;&nbsp;&nbsp; -Later, when the response a=
rrives=20
at the edge proxy, it tries to<BR>&gt;&gt;decode the flow token in the Via,=
 if=20
it succeeds, it&nbsp; forwards the<BR>&gt;&gt;response over the flow indica=
ted=20
in the flow token.<BR></DIV></SPAN></FONT>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D476095310-08102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff><SPAN class=3D476095310-0=
8102008>
<P class=3DMsoNormal><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN=20
class=3D476095310-08102008>&gt;&gt;</SPAN>Why there was no discussion about=
=20
mid-dialog and double record route in outbound=20
draft?<O:P></O:P></SPAN></P></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D476095310-08102008>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D476095310-08102008>No idea.&nbsp; Maybe it was considered too=20
awkward.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D476095310-08102008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D476095310-08102008>Regards,</SPAN></FONT></DIV><FONT face=3DArial=
=20
color=3D#0000ff size=3D2><SPAN class=3D476095310-08102008>
<DIV dir=3Dltr align=3Dleft><BR>Attila</DIV>
<DIV dir=3Dltr align=3Dleft>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D476095310-08102008><FONT face=3DArial color=3D#0000ff size=3D2><SPA=
N=20
class=3D476095310-08102008><FONT face=3DArial color=3D#0000ff size=3D2><SPA=
N=20
class=3D476095310-08102008><FONT face=3DArial color=3D#0000ff size=3D2><SPA=
N=20
class=3D476095310-08102008>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><SP=
AN=20
class=3D476095310-08102008></SPAN></FONT>&nbsp;</DIV></SPAN></FONT></SPAN><=
/FONT></SPAN></FONT></SPAN></FONT></SPAN></FONT></SPAN></FONT></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Karthikeyan Gopal=20
[mailto:g_karthikeyan@hcl.in] <BR><B>Sent:</B> 08 October 2008=20
10:23<BR><B>To:</B> Attila Sipos<BR><B>Cc:</B> sip@ietf.org;=20
sip-implementors@lists.cs.columbia.edu<BR><B>Subject:</B> RE: [Sip] statele=
ss=20
proxy support Outbound ?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Is there any spe=
cific=20
thing that has to be followed for UDP?<O:P></O:P></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Where and what s=
hould=20
be stored to maintain the same flow in case of edge proxy and registrar in=
=20
different node?<O:P></O:P></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Why there was no=
=20
discussion about mid-dialog and double record route in outbound=20
draft?<O:P></O:P></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Regards,<O:P></O=
:P></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Karthikeyan.G<O:=
P></O:P></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><O:P></O:P></SPA=
N></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><O:P></O:P></SPA=
N></FONT></P>
<DIV>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT=20
face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SP=
AN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"=
> Attila=20
Sipos [mailto:attila.sipos@vegastream.com] <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, October 08, 2008 2:=
32=20
PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20
<DEFANGHTML_ST1:PERSONNAME w:st=3D"on">Karthikeyan Gopal=20
</DEFANGHTML_ST1:PERSONNAME><BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [Sip] stateless proxy s=
upport=20
Outbound ?</SPAN></FONT><O:P></O:P></P></DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT><O:P></O:P></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT><O:P></O:P></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Yes, it=20
can.</SPAN></FONT><O:P></O:P></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Regards,</SPAN><=
/FONT><O:P></O:P></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Attila</SPAN></F=
ONT><O:P></O:P></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><O:P></O:P></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><O:P></O:P></SPAN></FONT></P>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT=20
face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal defanghtml_style=3D"margin-bottom:12.0pt"><B><FONT fac=
e=3DTahoma=20
size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SP=
AN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"=
>=20
<DEFANGHTML_ST1:PERSONNAME w:st=3D"on">Karthikeyan Gopal=20
</DEFANGHTML_ST1:PERSONNAME>[mailto:g_karthikeyan@hcl.in] <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 08 October 2008 09:59<BR><B><S=
PAN=20
style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Attila Sipos<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [Sip] stateless proxy s=
upport=20
Outbound ?</SPAN></FONT><O:P></O:P></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><DEFANGHTML_S=
PAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Thanks=20
Attila.</SPAN><O:P></O:P></DEFANGHTML_SPAN></FONT><O:P></O:P></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><DEFANGHTML_S=
PAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I have one more =
query=20
.<B><DEFANGHTML_SPAN style=3D"FONT-WEIGHT: bold"><SPAN=20
style=3D"FONT-WEIGHT: bold">Can Outbound be implemented with=20
UDP</SPAN></DEFANGHTML_SPAN></B>=20
transport?</SPAN><O:P></O:P></DEFANGHTML_SPAN></FONT><O:P></O:P></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><DEFANGHTML_S=
PAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Thanks &amp;=20
Regards,</SPAN><O:P></O:P></DEFANGHTML_SPAN></FONT><O:P></O:P></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><DEFANGHTML_S=
PAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Karthikeyan.G</S=
PAN><O:P></O:P></DEFANGHTML_SPAN></FONT><O:P></O:P></P><FONT=20
face=3D"Times New Roman" size=3D3><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><O:P></O:P></DEF=
ANGHTML_SPAN></FONT>
<DIV>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT=20
face=3D"Times New Roman" size=3D3><DEFANGHTML_SPAN style=3D"FONT-SIZE: 12pt=
"><SPAN=20
style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2></DEFANGHTML_SPAN><SPA=
N=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"><DEFANGHT=
ML_SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SP=
AN></DEFANGHTML_SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> Attila Sipos=20
[mailto:attila.sipos@vegastream.com] <BR><B><DEFANGHTML_SPAN=20
style=3D"FONT-WEIGHT: bold"><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></DEFANGHTML_SPAN></B> Wednesday, O=
ctober=20
08, 2008 12:26 PM<BR><B><DEFANGHTML_SPAN style=3D"FONT-WEIGHT: bold"><SPAN=
=20
style=3D"FONT-WEIGHT: bold">To:</SPAN></DEFANGHTML_SPAN></B>=20
<DEFANGHTML_ST1:PERSONNAME w:st=3D"on"><DEFANGHTML_ST1:PERSONNAME=20
u1:st=3D"on">Karthikeyan Gopal=20
</DEFANGHTML_ST1:PERSONNAME></DEFANGHTML_ST1:PERSONNAME>;=20
sip-implementors@lists.cs.columbia.edu; sip@ietf.org<BR><B><DEFANGHTML_SPAN=
=20
style=3D"FONT-WEIGHT: bold"><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></DEFANGHTML_SPAN></B> RE: [Sip]=
=20
stateless proxy support Outbound=20
?</SPAN></DEFANGHTML_SPAN></FONT><O:P></O:P><O:P></O:P></P></DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><DEFANGHTML_S=
PAN=20
style=3D"FONT-SIZE: 12pt"><O:P></O:P></DEFANGHTML_SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><DEFANGHTML_SPAN=
=20
style=3D"FONT-SIZE: 12pt"><O:P></O:P></DEFANGHTML_SPAN><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">It is possible -=
 to do=20
it you have to store the flow information in a Via=20
parameter</SPAN></DEFANGHTML_SPAN></FONT><O:P></O:P><O:P></O:P></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><DEFANGHTML_S=
PAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">(or mix it into =
the=20
branch, if you=20
prefer).</SPAN></DEFANGHTML_SPAN></FONT><O:P></O:P><O:P></O:P></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><DEFANGHTML_S=
PAN=20
style=3D"FONT-SIZE: 12pt"><O:P></O:P></DEFANGHTML_SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><DEFANGHTML_SPAN=
=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Unfortunately, t=
he=20
draft does not discuss stateless=20
proxies</SPAN></DEFANGHTML_SPAN></FONT><O:P></O:P><O:P></O:P></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><DEFANGHTML_S=
PAN=20
style=3D"FONT-SIZE: 12pt"><O:P></O:P></DEFANGHTML_SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><DEFANGHTML_SPAN=
=20
style=3D"FONT-SIZE: 12pt"><O:P></O:P></DEFANGHTML_SPAN><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Regards,</SPAN><=
/DEFANGHTML_SPAN></FONT><O:P></O:P><O:P></O:P></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><DEFANGHTML_S=
PAN=20
style=3D"FONT-SIZE: 12pt"><O:P></O:P></DEFANGHTML_SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><DEFANGHTML_SPAN=
=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Attila</SPAN></D=
EFANGHTML_SPAN></FONT><O:P></O:P><O:P></O:P></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><DEFANGHTML_S=
PAN=20
style=3D"FONT-SIZE: 12pt"><O:P></O:P></DEFANGHTML_SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><DEFANGHTML_SPAN=
=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">PS I did have a=
=20
discussion with someone about this but it might=20
be</SPAN></DEFANGHTML_SPAN></FONT><O:P></O:P><O:P></O:P></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><DEFANGHTML_S=
PAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">a bit confusing =
(it's=20
just a big mess of=20
e-mails).</SPAN></DEFANGHTML_SPAN></FONT><O:P></O:P><O:P></O:P></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><DEFANGHTML_S=
PAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">if you want to l=
ook at=20
some main points, here are some=20
links:</SPAN></DEFANGHTML_SPAN></FONT><O:P></O:P><O:P></O:P></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><DEFANGHTML_S=
PAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><A=20
href=3D"http://www.ietf.org/mail-archive/web/sip/current/msg21238.html">htt=
p://www.ietf.org/mail-archive/web/sip/current/msg21238.html</A></SPAN></DEF=
ANGHTML_SPAN></FONT><O:P></O:P><O:P></O:P></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><DEFANGHTML_S=
PAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><A=20
href=3D"http://www.ietf.org/mail-archive/web/sip/current/msg21245.html">htt=
p://www.ietf.org/mail-archive/web/sip/current/msg21245.html</A></SPAN></DEF=
ANGHTML_SPAN></FONT><O:P></O:P><O:P></O:P></P>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><DEFANGHTML_S=
PAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><A=20
href=3D"http://www.ietf.org/mail-archive/web/sip/current/msg21249.html">htt=
p://www.ietf.org/mail-archive/web/sip/current/msg21249.html</A></SPAN></DEF=
ANGHTML_SPAN></FONT><O:P></O:P><O:P></O:P></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><DEFANGHTML_S=
PAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><A=20
href=3D"http://www.ietf.org/mail-archive/web/sip/current/msg21331.html">htt=
p://www.ietf.org/mail-archive/web/sip/current/msg21331.html</A></SPAN></DEF=
ANGHTML_SPAN></FONT><O:P></O:P><O:P></O:P></P></DIV>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><DEFANGHTML_S=
PAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><A=20
href=3D"http://www.ietf.org/mail-archive/web/sip/current/msg21344.html">htt=
p://www.ietf.org/mail-archive/web/sip/current/msg21344.html</A></SPAN></DEF=
ANGHTML_SPAN></FONT><O:P></O:P><O:P></O:P></P></DIV><FONT=20
face=3D"Times New Roman" size=3D3><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 12pt"><O:P></O:P></DEFANGHTML_SPAN></FONT>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT=20
face=3D"Times New Roman" size=3D3><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 12pt"><O:P></O:P></DEFANGHTML_SPAN><SPAN=20
style=3D"FONT-SIZE: 12pt"><HR<DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 12pt"><O:P></O:P></DEFANGHTML_SPAN><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 12pt"><O:P></O:P></DEFANGHTML_SPAN><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 12pt"><O:P></O:P></DEFANGHTML_SPAN><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 12pt">size=3D2 width=3D"100%" align=3Dcenter tabIndex=
=3D-1&gt;=20
</SPAN></FONT></DIV>
<P class=3DMsoNormal defanghtml_style=3D"margin-bottom:12.0pt"><B><FONT fac=
e=3DTahoma=20
size=3D2></DEFANGHTML_SPAN><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"><DEFANGHT=
ML_SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SP=
AN></DEFANGHTML_SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> sip-bounces@ietf.org=20
[mailto:sip-bounces@ietf.org] <B><DEFANGHTML_SPAN=20
style=3D"FONT-WEIGHT: bold"><SPAN style=3D"FONT-WEIGHT: bold">On Behalf Of=
=20
</SPAN></DEFANGHTML_SPAN></B><DEFANGHTML_ST1:PERSONNAME=20
w:st=3D"on"><DEFANGHTML_ST1:PERSONNAME u1:st=3D"on">Karthikeyan Gopal=20
</DEFANGHTML_ST1:PERSONNAME><BR></DEFANGHTML_ST1:PERSONNAME><B><DEFANGHTML_=
SPAN=20
style=3D"FONT-WEIGHT: bold"><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></DEFANGHTML_SPAN></B> 08 October 2=
008=20
06:30<BR><B><DEFANGHTML_SPAN style=3D"FONT-WEIGHT: bold"><SPAN=20
style=3D"FONT-WEIGHT: bold">To:</SPAN></DEFANGHTML_SPAN></B>=20
sip-implementors@lists.cs.columbia.edu; sip@ietf.org<BR><B><DEFANGHTML_SPAN=
=20
style=3D"FONT-WEIGHT: bold"><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></DEFANGHTML_SPAN></B> [Sip] sta=
teless=20
proxy support Outbound=20
?</SPAN></DEFANGHTML_SPAN></FONT><O:P></O:P><O:P></O:P></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi=20
All,</SPAN></DEFANGHTML_SPAN><O:P></O:P></DEFANGHTML_SPAN></FONT><O:P></O:P=
><O:P></O:P></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp;&nbsp; Can stateless pr=
oxy=20
support=20
Outbound?</SPAN></DEFANGHTML_SPAN><O:P></O:P></DEFANGHTML_SPAN></FONT><O:P>=
</O:P><O:P></O:P></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">If so why it was not mentione=
d=20
clearly in draft? Where to store the flow=20
info?</SPAN></DEFANGHTML_SPAN><O:P></O:P></DEFANGHTML_SPAN></FONT><O:P></O:=
P><O:P></O:P></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Thanks &amp;=20
Regards,</SPAN></DEFANGHTML_SPAN><O:P></O:P></DEFANGHTML_SPAN></FONT><O:P><=
/O:P><O:P></O:P></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Karthik</SPAN></DEFANGHTML_SP=
AN><O:P></O:P></DEFANGHTML_SPAN></FONT><O:P></O:P><O:P></O:P></P>
<TABLE class=3DMsoNormalTable cellPadding=3D0 border=3D0>
  <TBODY>
  <TR>
    <TD bgColor=3Dwhite=20
    defanghtml_style=3D"background:white;padding:0in 0in 0in 0in">
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dblack=20
      size=3D3><DEFANGHTML_SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><O:P></O:P></DEFANGHTML=
_SPAN><DEFANGHTML_SPAN=20
      style=3D"FONT-SIZE: 12pt; COLOR: black"><SPAN=20
      style=3D"FONT-SIZE: 12pt; COLOR: black">DISCLAIMER:<BR>--------------=
---------------------------------------------------------------------------=
------------------------------<BR><BR>The=20
      contents of this e-mail and any attachment(s) are confidential and=20
      intended for the named recipient(s) only.<BR>It shall not attach any=
=20
      liability on the originator or HCL or its affiliates. Any views or=20
      opinions presented in <BR>this email are solely those of the author a=
nd=20
      may not necessarily reflect the opinions of HCL or its affiliates.<BR=
>Any=20
      form of reproduction, dissemination, copying, disclosure, modificatio=
n,=20
      distribution and / or publication of <BR>this message without the pri=
or=20
      written consent of the author of this e-mail is strictly prohibited. =
If=20
      you have <BR>received this email in error please delete it and notify=
 the=20
      sender immediately. Before opening any mail and <BR>attachments pleas=
e=20
      check them for viruses and=20
      defect.<BR><BR>------------------------------------------------------=
-----------------------------------------------------------------</SPAN></D=
EFANGHTML_SPAN></FONT><O:P></O:P><O:P></O:P></P></TD></TR></TBODY></TABLE>
<P defanghtml_style=3D"margin-bottom:12.0pt"><FONT face=3D"Times New Roman"=
=20
size=3D3><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 12pt"><O:P></O:P></DEFANGHTML_SPAN><SPAN=20
style=3D"FONT-SIZE: 12pt"><DEFANGHTML_SPAN=20
style=3D"FONT-SIZE: 12pt; BACKGROUND: white">.<O:P></O:P></SPAN></DEFANGHTM=
L_SPAN><O:P></O:P></FONT></P>
<P class=3DMsoNormal defanghtml_style=3D"margin-bottom:12.0pt"><FONT=20
face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><O:P></O:P></SPAN></FONT></P>
<P><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt; BACKGROUND: white">.</SPAN><O:P></O:P></FONT></P>=
</DIV><br><br>
<P align=3Dleft><FONT style=3D"BACKGROUND-COLOR: #ffffff">.</FONT></P>
</body></HTML>

------_=_NextPart_001_01C92935.8252A034--

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

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


From sip-bounces@ietf.org  Wed Oct  8 06:33:54 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2D9993A6803;
	Wed,  8 Oct 2008 06:33:54 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F37223A686E
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 06:33:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.045
X-Spam-Level: 
X-Spam-Status: No, score=-6.045 tagged_above=-999 required=5
	tests=[AWL=-0.346, BAYES_00=-2.599, J_CHICKENPOX_36=0.6,
	MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rwRMjZYviSQ5 for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 06:33:52 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 673AC3A6803
	for <sip@ietf.org>; Wed,  8 Oct 2008 06:33:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,378,1220227200"; d="scan'208";a="23630373"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 08 Oct 2008 13:33:57 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m98DXvI1012166; 
	Wed, 8 Oct 2008 09:33:57 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m98DXvP6006563;
	Wed, 8 Oct 2008 13:33:57 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 8 Oct 2008 09:33:57 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 8 Oct 2008 09:33:56 -0400
Message-ID: <48ECB6C4.7020903@cisco.com>
Date: Wed, 08 Oct 2008 09:33:56 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>	<200810072353.07507.ibc@aliax.net>
	<48EBE4F8.6080509@cisco.com> <200810080134.10193.ibc@aliax.net>
In-Reply-To: <200810080134.10193.ibc@aliax.net>
X-OriginalArrivalTime: 08 Oct 2008 13:33:57.0026 (UTC)
	FILETIME=[83AD4820:01C9294A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2294; t=1223472837;
	x=1224336837; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Dual=20registration=20without=2
	0Outbound |Sender:=20
	|To:=20=3D?ISO-8859-1?Q?I=3DF1aki_Baz_Castillo?=3D=20<ibc@a
	liax.net>; bh=TZdXLXyt0pth0DlYx4nnBlhmDvarhYfz10uSgdvbtPE=;
	b=MARriVEdHQ33scRlnaQENKDCZ6hlCXKyF1TcjNrKZFeZpQ3q0DyHaSlH5l
	HEZr4FxikH5YCpG9tFRF0pN4djmvr8wTaKv+htOUxq5ynxjl/STliiHzuP5h
	2wrTO74hxb;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: sip@ietf.org
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



I=F1aki Baz Castillo wrote:
> El Mi=E9rcoles, 8 de Octubre de 2008, Paul Kyzivat escribi=F3:
>> I=F1aki,
>>
>> What you describe is perfectly fine, and is in fact the reasonable thing
>> to do. You have distinct AORs corresponding to the two numbers, and a
>> separate contact for each.
>>
>> What I was asking about was creating multiple Contact addresses for the
>> *same* AOR.
> =

> Perpahs I didn't explain correctly:
> =

> I mean that UA (with name "a@doman.com") sends two REGISTER for the same =
AoR:
> =

> 1)
> REGISTER sip:server
> From: sip:a@domain.com
> To: sip:a@domain.com
> Contact: sip:+34111111@my_ip
> =

> 1)
> REGISTER sip:server
> From: sip:a@domain.com
> To: sip:a@domain.com
> Contact: sip:+34222222@my_ip
> =

> =

> When the proxy receives a call with RURI =3D +34111111, it ask the locati=
on =

> sevice which returns "a@domain.com".
> But the proxy, instead fo calling both locations in parallel (or =

> sequentially), it just calls the location with the Contact username match=
ing =

> the incoming RURI (+34111111).
> =

> Not sure if it's a good idea.

Its certainly not an idea that appeals to me.

It requires an entirely non-standard routing algorithm within the proxy, =

selecting contact URI from among the available candidates in a very =

weird way.

Its an axiom of sip that UAs may choose their contact addresses as they =

wish. The encoding of any semantic information into that address is the =

business of the UA and not for any other server to second guess.

In your example, the same proxy is responsible for the following AORs:
- tel:+34111111
- tel:+34222222
- sip:a@domain.com

and probably:

- sip:+34111111@domain.com
- sip:+34222222@domain.com

Rather than have the UA register for a@domain.com and have the proxy do =

a weird mapping based on registered contact addresses, its much more =

straightforward to have the UA register as follows:

REGISTER sip:domain.com
From: sip:+34111111@domain.com
To: sip:+34111111@domain.com
Contact: sip:+34111111@my_ip

REGISTER sip:domain.com
From: sip:+34222222@domain.com
To: sip:+34222222@domain.com
Contact: sip:+34222222@my_ip

(Its required to use the sip form of the AOR rather than the tel form. =

Can't have a tel as the To of a REGISTER.)

	Thanks,
	Paul

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


From sip-bounces@ietf.org  Wed Oct  8 06:34:55 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DA42F3A6AB8;
	Wed,  8 Oct 2008 06:34:55 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 15E0C3A6AB8
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 06:34:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id O8qGZWivdYAF for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 06:34:54 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id 28F773A6774
	for <sip@ietf.org>; Wed,  8 Oct 2008 06:34:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 305461EC2CE;
	Wed,  8 Oct 2008 16:34:35 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XfhZINrhw6-x; Wed,  8 Oct 2008 16:34:33 +0300 (EEST)
Received: from taimen (h159126.gprs.dnafinland.fi [87.93.159.126])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Wed,  8 Oct 2008 16:34:33 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 51DADAC061; Wed,  8 Oct 2008 16:34:26 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18668.46818.312726.784259@taimen.test.fi>
Date: Wed, 8 Oct 2008 16:34:26 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>
	<18665.59 269.640606.477292@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
	<48EBC88B.2030300@cisco.com> <46101DEA-677B-4F28-AD1E-32F64385853
	5@s ofta rmor.com> <CA
	9998CD4A020D418654FCDEF4E707DF05C0F8B8@esealmw113.eemea.ericsson.se>
	<18668.21733.520868.113675@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > "instance-id:  This specification uses the word instance-id to refer
 >       to the value of the "sip.instance" media feature tag in the
 >       Contact header field.  This is a Uniform Resource Name (URN) that
 >       uniquely identifies this specific UA instance." 

what does "specific UA instance" mean?

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


From sip-bounces@ietf.org  Wed Oct  8 06:36:53 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0E1A63A6B83;
	Wed,  8 Oct 2008 06:36:53 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5424C3A6B7F
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 06:36:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id lBB7iUl896kp for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 06:36:47 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id 66E6F3A659A
	for <sip@ietf.org>; Wed,  8 Oct 2008 06:36:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 7F5F21EC2CE;
	Wed,  8 Oct 2008 16:37:00 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id kJEYIg2YfDiV; Wed,  8 Oct 2008 16:36:58 +0300 (EEST)
Received: from taimen (h159126.gprs.dnafinland.fi [87.93.159.126])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Wed,  8 Oct 2008 16:36:58 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 4211AAC061; Wed,  8 Oct 2008 16:36:52 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18668.46963.759610.665724@taimen.test.fi>
Date: Wed, 8 Oct 2008 16:36:51 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F8C0@esealmw113.eemea.ericsson.se>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>
	<18665.59269.640606.477292@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
	<48EBC88B.2030300@cisco.com> <46101DEA-677B-4F28-AD1E-32F64385! 85
	35@soft armor.com> <5
	D1A7985295922448D5550C94DE29180023B048B@DEEXC1U01.de.lucent.com>
	<18668.22966.673918.296835@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C0@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > >i have not asked for redundant connections to registrars. the
 > connections are to outbound proxies.
 > 
 > You talk about co-located outbound/registrar proxies, so you DO have
 > multiple registarars.

yes, but that is not relevant here.  someone else may have only one.
what matters are registrations via outbound proxies which may end up to
1 or 10 registrars.

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


From sip-bounces@ietf.org  Wed Oct  8 06:48:49 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7ACE33A6B63;
	Wed,  8 Oct 2008 06:48:49 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9E55C3A68F0
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 06:48:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.481
X-Spam-Level: 
X-Spam-Status: No, score=-6.481 tagged_above=-999 required=5 tests=[AWL=0.118, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id VGNzI6puxhiS for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 06:48:43 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 13B473A6BCF
	for <sip@ietf.org>; Wed,  8 Oct 2008 06:48:43 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,378,1220227200"; d="scan'208";a="23599458"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 08 Oct 2008 13:48:55 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m98DmsQH019087; 
	Wed, 8 Oct 2008 09:48:54 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m98Dmstp011100;
	Wed, 8 Oct 2008 13:48:54 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 8 Oct 2008 09:48:54 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 8 Oct 2008 09:48:54 -0400
Message-ID: <48ECBA45.1070109@cisco.com>
Date: Wed, 08 Oct 2008 09:48:53 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se><18665.59
	269.640606.477292@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se><48EBC88B.2030300@cisco.com><46101DEA-677B-4F28-AD1E-32F64385853
	5@s
	ofta	rmor.com><CA	9998CD4A020D418654FCDEF4E707DF05C0F8B8@esealmw113.eemea.ericsson.se>
	<18668.21733.520868.113675@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 08 Oct 2008 13:48:54.0172 (UTC)
	FILETIME=[9A6AE5C0:01C9294C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1103; t=1223473734;
	x=1224337734; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Dual=20registration=20without=2
	0Outbound |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=oNvItGewFUGPqrr/kr04CIRwcn9HVpEj0yQADqWLq70=;
	b=IhxL5xkWwiQp3prToUeN04+fbLwTZHaAn9A6jkr5n2YQ79OcBibDDWx6F4
	JSwXkDoFnx9I+jwUBpGNlkrYGKOYz+lKKsnD8VCsDm7bNxbacElxxhosPx/h
	eRSrMehL5Z;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: sip@ietf.org, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Christer Holmberg wrote:

> But, in scenarios where the outbound- and registrar proxies are NOT
> co-located, and only one registrar is used, I see no reason why people
> shall be forced to register both contacts to both outbound proxies. In
> cases where the contact is access network dependent it may not even be
> possible to do so.

I don't understand the last statement. You can put *any* syntactically 
valid URI in a Contact of a REGISTER.

Perhaps you mean it won't work once registered, when combined with the 
resulting Service-Route. In that case the edge proxy (P-CSCF) may be 
asked to route to a URI that is not on the access network that it is 
intended to use. But I guess that is just one aspect of the closed 
nature of 3gpp.

The problem I see developing here is the idea that the registration 
behavior of the UA is dependent on its understanding the topology of the 
network. Its one thing to expect it to know of a couple of attachment 
points. Its another thing to expect it to know more about what is behind 
those attachment points.

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


From sip-bounces@ietf.org  Wed Oct  8 06:55:46 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4A2153A6858;
	Wed,  8 Oct 2008 06:55:46 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0E0BD3A659A
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 06:55:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.486
X-Spam-Level: 
X-Spam-Status: No, score=-6.486 tagged_above=-999 required=5 tests=[AWL=0.113, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 16FxI37vLOM4 for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 06:55:44 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 223C33A6858
	for <sip@ietf.org>; Wed,  8 Oct 2008 06:55:44 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,378,1220227200"; d="scan'208";a="171121173"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 08 Oct 2008 13:55:28 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m98DtSGI002757; 
	Wed, 8 Oct 2008 06:55:28 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m98DtQKs025910;
	Wed, 8 Oct 2008 13:55:28 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 8 Oct 2008 09:54:49 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 8 Oct 2008 09:54:49 -0400
Message-ID: <48ECBBA8.8030505@cisco.com>
Date: Wed, 08 Oct 2008 09:54:48 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Juha Heinanen <jh@tutpro.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>	<18665.45965.827982.821183@taimen.test.fi>	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>	<18665.47207.397605.244480@taimen.test.fi>	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>	<18665.48080.859460.802945@taimen.test.fi>	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>	<18665.49637.47890.122973@taimen.test.fi>	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>	<18665.51736.268071.502700@taimen.test.fi>	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>	<
	18665.59
	269.640606.477292@taimen.test.fi>	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>	<48EBC88B.2030300@cisco.com>
	<18668.23311.970894.881744@taimen.test.fi>
In-Reply-To: <18668.23311.970894.881744@taimen.test.fi>
X-OriginalArrivalTime: 08 Oct 2008 13:54:49.0166 (UTC)
	FILETIME=[6E02AEE0:01C9294D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1622; t=1223474128;
	x=1224338128; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Dual=20registration=20without=2
	0Outbound |Sender:=20;
	bh=RdddL1ZiqdKl169DmWRLohGROoRJioWRKLfr8SKSvK0=;
	b=uccMTWWLZCaLA0Jq86kLt87apWxEW9CVLap7/xK1IBlHRmDg9LaomjzRdw
	eRTqxE4RwwQbXINm+z5/JoGE6HlviqxE/w+R24/pwgeexxMoG6VyggxaJtmd
	zIY2xyvlEJ;
Authentication-Results: sj-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: sip@ietf.org, dean.willis@softarmor.com,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Juha Heinanen wrote:
> Paul Kyzivat writes:
> 
>  > Then, what causes the UA to register two different contacts? Are the 
>  > wlan contact and the 3g contact registered to *different* AORs? If not I 
>  > don't see the point. If anything, I would expect that 3g and wlan 
>  > represent access networks and hence differing proxies, not AORs or 
>  > registrars.
> 
> my sip uri is sip:jh@tutpro.com and the nokia phone on my desk is
> currently registered to proxy of tutpro.com domain via both its wlan
> interface and its 3g interface.  there is no need to have two different
> proxies.

That's a sensible arrangement. I suppose the wlan and 3g interfaces have 
different IP addresses, and so you have a separate contact for each? So 
you register two contacts to the same AOR via the same proxy, right?

> by the way, when my phone is on wlan and gprs network, the methods
> supported by wlan contact and gprs contact are not the same (if that
> matters anything to the instance-id business).

In that case the choice of one instance id or two is a value judgment on 
your part. I would expect the default choice would be that they would 
have the same instance id. You might prefer distinct instance IDs if you 
want them considered independent devices. For instance, if one is 
IM-only and the other is voice-only then you might want them treated 
independently. But if they have overlapping capabilities, then you may 
have to then suffer having them both "ring" for the same call, which 
could be annoying. (But you might be able to program them to hide that.)

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


From sip-bounces@ietf.org  Wed Oct  8 07:00:36 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0A5333A6A35;
	Wed,  8 Oct 2008 07:00:36 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 273933A6774
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 07:00:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fwUnBO9UyQdx for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 07:00:28 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id 998763A6892
	for <sip@ietf.org>; Wed,  8 Oct 2008 07:00:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id BFE8D1EC2CE;
	Wed,  8 Oct 2008 17:01:03 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AiYKpJqLr-xr; Wed,  8 Oct 2008 17:01:01 +0300 (EEST)
Received: from taimen (h159126.gprs.dnafinland.fi [87.93.159.126])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Wed,  8 Oct 2008 17:01:01 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 227F3AC061; Wed,  8 Oct 2008 17:00:57 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18668.48409.76707.763960@taimen.test.fi>
Date: Wed, 8 Oct 2008 17:00:57 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F8C4@esealmw113.eemea.ericsson.se>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>
	<18665.59269.640606.477292@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
	<48EBC88B.2030300@cisco.com> <46101DEA-677B-4F28-AD1E-32F64385! 85
	35@soft armor.com> <
	5D1A7985295922448D5550C94DE29180023B048B@DEEXC1U01.de.lucent.com>
	<18668.22966.673918.296835@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C0@esealmw113.eemea.ericsson.se>
	<18668.46963.759610.665724@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C4@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > >yes, but that is not relevant here.  someone else may have only one.
 > >what matters are registrations via outbound proxies which may 
 > >end up to 1 or 10 registrars.
 > 
 > Well, then again I see no reason why the UA should have to register each
 > contact with all of the proxies.

some people may not care about simple implementation of redundancy.

 > Outbound says that the UE regiesters a number of flows. Whether all
 > those flows come from the same same contact is inrelevant. If one flow
 > fails, another fail is tried. It doesn't matter if that other flow
 > happens to be associated with another contact. So, you have redundancy.

could you please explain to me, how does that work for inbound calls to
the UA that need to get parallel forked to all contacts that the UA has
registered for its AoR?

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


From sip-bounces@ietf.org  Wed Oct  8 07:05:13 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F368228C14C;
	Wed,  8 Oct 2008 07:05:12 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 26F0B28C14C
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 07:05:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id W1+YpKkd95nK for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 07:05:11 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id 0130028C138
	for <sip@ietf.org>; Wed,  8 Oct 2008 07:05:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 652271EC2CE;
	Wed,  8 Oct 2008 17:05:25 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6HI9qOGTSOsx; Wed,  8 Oct 2008 17:05:23 +0300 (EEST)
Received: from taimen (h159126.gprs.dnafinland.fi [87.93.159.126])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Wed,  8 Oct 2008 17:05:23 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 9B350AC061; Wed,  8 Oct 2008 17:05:19 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18668.48671.615783.623174@taimen.test.fi>
Date: Wed, 8 Oct 2008 17:05:19 +0300
To: Paul Kyzivat <pkyzivat@cisco.com>
In-Reply-To: <48ECBBA8.8030505@cisco.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>
	< 18665.59 269.640606.477292@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
	<48EBC88B.2030300@cisco.com>
	<18668.23311.970894.881744@taimen.test.fi>
	<48ECBBA8.8030505@cisco.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, dean.willis@softarmor.com,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Paul Kyzivat writes:

 > That's a sensible arrangement. I suppose the wlan and 3g interfaces have 
 > different IP addresses, and so you have a separate contact for each? So 
 > you register two contacts to the same AOR via the same proxy, right?

exactly.  and if 3g connection is lost and replaced by 2g connection,
also the method list in the contacts will differ.

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


From sip-bounces@ietf.org  Wed Oct  8 07:18:53 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E18953A691F;
	Wed,  8 Oct 2008 07:18:53 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DD9F53A67BD
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 07:18:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.199
X-Spam-Level: 
X-Spam-Status: No, score=-6.199 tagged_above=-999 required=5 tests=[AWL=0.050, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OLTlCCrmMOjS for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 07:18:49 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id C770A3A691F
	for <sip@ietf.org>; Wed,  8 Oct 2008 07:18:48 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	07FAB20E53; Wed,  8 Oct 2008 16:18:12 +0200 (CEST)
X-AuditID: c1b4fb3c-ac0cabb0000015b5-07-48ecc12327b8
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	D333C20CB4; Wed,  8 Oct 2008 16:18:11 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 8 Oct 2008 16:18:11 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 8 Oct 2008 16:18:11 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8C6@esealmw113.eemea.ericsson.se>
In-Reply-To: <48ECBA45.1070109@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckpTJzQX4lxB1r2Rn2y3xz/wUJhEQAAyQlg
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se><18665.59
	269.640606.477292@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se><48EBC88B.2030300@cisco.com><46101DEA-677B-4F28-AD1E-32F64385853
	5@s
	ofta	rmor.com><CA	9998CD4A020D418654FCDEF4E707DF05C0F8B8@esealmw113.eemea.ericsson.se>
	<18668.21733.520868.113675@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se>
	<48ECBA45.1070109@c isco.com >
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 08 Oct 2008 14:18:11.0664 (UTC)
	FILETIME=[B1F6E500:01C92950]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>But, in scenarios where the outbound- and registrar proxies are NOT 
>>co-located, and only one registrar is used, I see no reason why people

>>shall be forced to register both contacts to both outbound 
>>proxies. In cases where the contact is access network dependent it may

>>not even be possible to do so.
> 
>I don't understand the last statement. You can put *any* 
>syntactically valid URI in a Contact of a REGISTER.

Yes, but syntactically valid does not necessarily mean globablly
reachable.

For example, the contacts could be part of private address domain, and
the edge proxy itself performs the NATting for that address domain. In
that case the contact can only be reached via those specific edge
proxy/proxies.

Another example is when different IP versions are used. An IPv6 contact
can't be registered with an IPv4 edge proxy (unless you have a IP
version converter in between, that is).


BUT, I don't think the main issue is whether a contact CAN be registerd
with all edge proxies, but WHY one would be mandated to do so.

Outbound provides you with multiple flows to reach a user. I doesn't
matter if each flow is not associated with the same contact, as long as
the user can be reached on any of the flows.

Regards,

Christer



> Perhaps you mean it won't work once registered, when combined 
> with the resulting Service-Route. In that case the edge proxy 
> (P-CSCF) may be asked to route to a URI that is not on the 
> access network that it is intended to use. But I guess that 
> is just one aspect of the closed nature of 3gpp.
> 
> The problem I see developing here is the idea that the 
> registration behavior of the UA is dependent on its 
> understanding the topology of the network. Its one thing to 
> expect it to know of a couple of attachment points. Its 
> another thing to expect it to know more about what is behind 
> those attachment points.
> 
> 	Thanks,
> 	Paul
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct  8 07:23:57 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CFDEF3A6BCE;
	Wed,  8 Oct 2008 07:23:57 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9D0083A6BD0
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 07:23:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id huN8gi3xwM5U for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 07:23:55 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id B4BE03A6BCE
	for <sip@ietf.org>; Wed,  8 Oct 2008 07:23:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 394381EC2CE;
	Wed,  8 Oct 2008 17:24:14 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WVy6GyaBG8eM; Wed,  8 Oct 2008 17:24:08 +0300 (EEST)
Received: from taimen (h159126.gprs.dnafinland.fi [87.93.159.126])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Wed,  8 Oct 2008 17:24:08 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 1BB3EAC061; Wed,  8 Oct 2008 17:24:04 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18668.49796.81109.206301@taimen.test.fi>
Date: Wed, 8 Oct 2008 17:24:04 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F8C5@esealmw113.eemea.ericsson.se>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>
	<18665.59269.640606.477292@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
	<48EBC88B.2030300@cisco.com> <46101DEA-677B-4F28-AD1E-32F64385! 85
	35@sof t armor.com>
	<5D1A7985295922448D5550C94DE29180023B048B@DEEXC1U01.de.lucent.com>
	<18668.22966.673918.296835@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C0@esealmw113.eemea.ericsson.se>
	<18668.46963.759610.665724@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C4@esealmw113.eemea.ericsson.se>
	<18668.48409.76707.763960@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C5@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > If you want to register multiple contacts, and you want the registrar to
 > fork to them, you use normal 3261 proceudres - and then you configure
 > the proxy to perform parallel forking.

this starts to go circles.  UA can do whatever it wants without any rfc.
proxy operator, however, has no way to know that UA does the right thing
if it is not mandated by an rfc and rfc3261 does not mandate registering
via multiple proxies.

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


From sip-bounces@ietf.org  Wed Oct  8 07:31:54 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C834A3A692E;
	Wed,  8 Oct 2008 07:31:54 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0133C3A68F0
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 07:31:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id xzkESixwVYyE for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 07:31:53 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id 07CF03A6BDF
	for <sip@ietf.org>; Wed,  8 Oct 2008 07:31:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 84C6A1EC2CE;
	Wed,  8 Oct 2008 17:31:44 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LloE8bfIvUiv; Wed,  8 Oct 2008 17:31:39 +0300 (EEST)
Received: from taimen (h159126.gprs.dnafinland.fi [87.93.159.126])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Wed,  8 Oct 2008 17:31:39 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 26AE6AC061; Wed,  8 Oct 2008 17:31:35 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18668.50247.121832.271341@taimen.test.fi>
Date: Wed, 8 Oct 2008 17:31:35 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F8C6@esealmw113.eemea.ericsson.se>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>
	<18665.59 269.640606.477292@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
	<48EBC88B.2030300@cisco.com>
	<46101DEA-677B-4F28-AD1E-32F64385853 5@s ofta	rmor.com>
	<CA	9998CD4A020D418654FCDEF4E707DF05C0F8B8@esealmw113.eemea.ericsson.se>
	<18668.21733.520868.113675@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se>
	<48ECBA45.1070109@c isco.com >
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C6@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > Outbound provides you with multiple flows to reach a user. I doesn't
 > matter if each flow is not associated with the same contact, as long as
 > the user can be reached on any of the flows.

this is all true, but then it makes no sense for ob draft to mandate
registering via at least two ob proxies.  the ua can register with one
and if that flow dies, register with another one.  your requirement is
satisfied and there is no need for ob draft to mandate two flows.

i'm sorry that i brought the "minimum two" issue up.  the current text
does not help me to achieve my goal and it can very well be removed.  as
side effect, it makes no sense to implement outbound, because it does
not add any value.  UAs are already using keepalives without outbound.

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


From sip-bounces@ietf.org  Wed Oct  8 07:39:22 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 12B8D3A6919;
	Wed,  8 Oct 2008 07:39:22 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 86B623A6887
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 07:39:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.201
X-Spam-Level: 
X-Spam-Status: No, score=-6.201 tagged_above=-999 required=5 tests=[AWL=0.048, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zKoYw6il7ewC for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 07:39:19 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 81B3B3A681D
	for <sip@ietf.org>; Wed,  8 Oct 2008 07:39:19 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	A11F7208C0; Wed,  8 Oct 2008 15:42:16 +0200 (CEST)
X-AuditID: c1b4fb3c-ad8cdbb0000015b5-bc-48ecb8b8811d
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	7C8A120473; Wed,  8 Oct 2008 15:42:16 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 8 Oct 2008 15:42:16 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 8 Oct 2008 15:42:15 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8C4@esealmw113.eemea.ericsson.se>
In-Reply-To: <18668.46963.759610.665724@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckpSvLFPB39sXfkTPyM7q3G6rdGwgAADX5g
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18665.43684.176244.988653@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se><18665.59269.640606.477292@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se><48EBC88B.2030300@cisco.com><46101DEA-677B-4F28-AD1E-32F64385!
	85 35@soft armor.com><
	5D1A7985295922448D5550C94DE29180023B048B@DEEXC1U01.de.lucent.com><18668.22966.673918.296835@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8C0@esealmw113.eemea.ericsson.se>
	<18668.46963.759610.665724@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 08 Oct 2008 13:42:16.0380 (UTC)
	FILETIME=[AD50A7C0:01C9294B]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 
>>>i have not asked for redundant connections to registrars. 
>>>connections are to outbound proxies.
>>
>>You talk about co-located outbound/registrar proxies, so you DO have
multiple registarars.
> 
>yes, but that is not relevant here.  someone else may have only one.
>what matters are registrations via outbound proxies which may 
>end up to 1 or 10 registrars.

Well, then again I see no reason why the UA should have to register each
contact with all of the proxies.

Outbound says that the UE regiesters a number of flows. Whether all
those flows come from the same same contact is inrelevant. If one flow
fails, another fail is tried. It doesn't matter if that other flow
happens to be associated with another contact. So, you have redundancy.

Regards,

Christer

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


From sip-bounces@ietf.org  Wed Oct  8 07:41:09 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C93E53A6B6A;
	Wed,  8 Oct 2008 07:41:09 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 38D653A6B6A
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 07:41:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.202
X-Spam-Level: 
X-Spam-Status: No, score=-6.202 tagged_above=-999 required=5 tests=[AWL=0.047, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id sQ91Q4OjYq4x for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 07:41:08 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 5D4E83A6B30
	for <sip@ietf.org>; Wed,  8 Oct 2008 07:41:08 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	8895F20E2A; Wed,  8 Oct 2008 16:40:26 +0200 (CEST)
X-AuditID: c1b4fb3c-af8d1bb0000015b5-95-48ecc65af7ee
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	7749D20E42; Wed,  8 Oct 2008 16:40:26 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 8 Oct 2008 16:40:20 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 8 Oct 2008 16:40:20 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
In-Reply-To: <18668.50247.121832.271341@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckpUpwGMmK+AazuRqmsd8XRTW0h9AAAIvmg
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se><18665.59
	269.640606.477292@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se><48EBC88B.2030300@cisco.com><46101DEA-677B-4F28-AD1E-32F64385853
	5@s
	ofta	rmor.com><CA	9998CD4A020D418654FCDEF4E707DF05C0F8B8@esealmw113.eemea.ericsson.se><18668.21733.520868.113675@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se><48ECBA45.1070109@c
	is co.com>< CA9998CD4A02
	0D418654FCDEF4E707DF05C0F8C6@esealmw113.eemea.ericsson.se>
	<18668.50247.121832.271341@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 08 Oct 2008 14:40:20.0784 (UTC)
	FILETIME=[CA2E8300:01C92953]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>Outbound provides you with multiple flows to reach a user. 
>>I doesn't  matter if each flow is not associated with the 
>>same contact, as long as the user can be reached on any of 
>>the flows.
> 
>this is all true, but then it makes no sense for ob draft to 
>mandate registering via at least two ob proxies.  the ua can 
>register with one and if that flow dies, register with 
>another one.  your requirement is satisfied and there is no 
>need for ob draft to mandate two flows.

I have never said that a user should only register with one ob proxy.

As specified, one should register with at least two ob proxies, but my
point is that it doesn't matter if those two registrations are bound to
the same contact, as long as the user can be reached on both of the
registrations.

Regards,

Christer



> 
> i'm sorry that i brought the "minimum two" issue up.  the 
> current text does not help me to achieve my goal and it can 
> very well be removed.  as side effect, it makes no sense to 
> implement outbound, because it does not add any value.  UAs 
> are already using keepalives without outbound.
> 
> -- juha
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct  8 07:50:41 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 614B43A68F0;
	Wed,  8 Oct 2008 07:50:41 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 30AAF3A68F0
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 07:50:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id aVO2apbw-AvB for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 07:50:34 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id AF6ED3A6890
	for <sip@ietf.org>; Wed,  8 Oct 2008 07:50:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 5781D1EC2CE;
	Wed,  8 Oct 2008 17:50:42 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jYAPIFcDpD52; Wed,  8 Oct 2008 17:50:36 +0300 (EEST)
Received: from taimen (h159126.gprs.dnafinland.fi [87.93.159.126])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Wed,  8 Oct 2008 17:50:36 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 83200AC061; Wed,  8 Oct 2008 17:50:31 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18668.51383.505850.963592@taimen.test.fi>
Date: Wed, 8 Oct 2008 17:50:31 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>
	<18665.59 269.640606.477292@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
	<48EBC88B.2030300@cisco.com>
	<46101DEA-677B-4F28-AD1E-32F64385853 5@s ofta	rmor.com>
	<CA	9998CD4A020D418654FCDEF4E707DF05C0F8B8@esealmw113.eemea.ericsson.se>
	<18668.21733.520868.113675@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se>
	<48ECBA45.1070109@c is co.com> < CA9998CD4A02
	0D418654FCDEF4E707DF05C0F8C6@esealmw113.eemea.ericsson.se>
	<18668.50247.121832.271341@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > As specified, one should register with at least two ob proxies, but my
 > point is that it doesn't matter if those two registrations are bound to
 > the same contact, as long as the user can be reached on both of the
 > registrations.

it DOES matter if you consider complexity of implementing redundant
proxy/registrar.

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


From sip-bounces@ietf.org  Wed Oct  8 08:22:48 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8A72F3A6822;
	Wed,  8 Oct 2008 08:22:48 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 196963A6822
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 08:22:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.203
X-Spam-Level: 
X-Spam-Status: No, score=-6.203 tagged_above=-999 required=5 tests=[AWL=0.046, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id G9p+nWlX22w2 for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 08:22:47 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 377D53A67DF
	for <sip@ietf.org>; Wed,  8 Oct 2008 08:22:46 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	8089A20752; Wed,  8 Oct 2008 16:11:15 +0200 (CEST)
X-AuditID: c1b4fb3c-ae0cebb0000015b5-2d-48ecbf83f74c
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	5703A206CF; Wed,  8 Oct 2008 16:11:15 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 8 Oct 2008 16:11:15 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 8 Oct 2008 16:11:14 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8C5@esealmw113.eemea.ericsson.se>
In-Reply-To: <18668.48409.76707.763960@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckpTk3Q8r2jactXT1Cci1dAYVkcogAAKGjw
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18665.43684.176244.988653@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se><18665.59269.640606.477292@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se><48EBC88B.2030300@cisco.com><46101DEA-677B-4F28-AD1E-32F64385!
	85 35@sof t armor.com>
	<5D1A7985295922448D5550C94DE29180023B048B@DEEXC1U01.de.lucent.com><18668.22966.673918.296835@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8C0@esealmw113.eemea.ericsson.se><18668.46963.759610.665724@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8C4@esealmw113.eemea.ericsson.se>
	<18668.48409.76707.763960@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 08 Oct 2008 14:11:15.0188 (UTC)
	FILETIME=[B9B9B340:01C9294F]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 
 
>>Outbound says that the UE regiesters a number of flows. 
>>Whether all those flows come from the same same contact is 
>>inrelevant. If one flow  fails, another fail is tried. It 
>>doesn't matter if that other flow happens to be associated 
>>with another contact. So, you have redundancy.
> 
>could you please explain to me, how does that work for 
>inbound calls to the UA that need to get parallel forked to 
>all contacts that the UA has registered for its AoR?

Again, that has nothing to do with Outbound. Outbound tries to ensure
that there is at least ONE flow on which you can be reached.

If you want to register multiple contacts, and you want the registrar to
fork to them, you use normal 3261 proceudres - and then you configure
the proxy to perform parallel forking.

OR, you use normal 3261 procedures combined with Outbound, but then you
would register each contact using independent outbound procedures for
each contact. You could register each contact via each outbound proxy,
but from a outbound perspective the contacts would not be related.

Regards,

Christer


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


From sip-bounces@ietf.org  Wed Oct  8 09:48:03 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C000C28C18C;
	Wed,  8 Oct 2008 09:48:03 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4CDC028C18C
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 09:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0-GhjnRbUVI0 for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 09:47:58 -0700 (PDT)
Received: from zcars04f.nortel.com (zcars04f.nortel.com [47.129.242.57])
	by core3.amsl.com (Postfix) with ESMTP id 427FA28C179
	for <sip@ietf.org>; Wed,  8 Oct 2008 09:47:54 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m98Gllo13054; Wed, 8 Oct 2008 16:47:48 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 8 Oct 2008 11:47:30 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF19A212A1@zrc2hxm0.corp.nortel.com>
In-Reply-To: <18668.22818.736346.883984@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckpErqAvb04oxeFTuK4/n1kThR9egATKlVw
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>
	<18665.59	269.640606.477292@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
	<48EBC88B.2030300@cisco.com>	<46101DEA-677B-4F2! 8-AD1E-32
	F64385! ! 85 35@so ft armor.com	>
	<5D1A7985295922448D5550C94DE29180023B048B@DEEXC1U01.de.lucent.com>
	<1ECE0EB50388174790F9694F77522CCF199DA2EB@zrc2hxm0.corp.nortel.com>
	<18668.22818.736346.883984@taimen.test.fi>
From: "Francois Audet" <audet@nortel.com>
To: "Juha Heinanen" <jh@tutpro.com>
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

No.

I'm saying a new draft on redundant registration is needed, and we can leave
outbound AS IS.

I thought about this more.

I think what it means, is NOT using "Supported: outbound", but using 
the +sip.instance and reg-id in the REGISTER. Perhaps with a different
"Support: redundant-registrations" or whatever.

The reg-ids will distinguish the multiple registrations. The +sip.instance
will correlate them.

This will be in line with what we did with GRUU which also can use the
+sip.instance.

A new draft describing this should be fairly simple to do, and we wouldn't
derail the process, and it would be very much in line with sip-outbound.

Makes sense?

> -----Original Message-----
> From: Juha Heinanen [mailto:jh@tutpro.com] 
> Sent: Tuesday, October 07, 2008 23:54
> To: Audet, Francois (SC100:3055)
> Cc: DRAGE, Keith (Keith); Dean Willis; Paul Kyzivat; 
> sip@ietf.org; Christer Holmberg
> Subject: Re: [Sip] Dual registration without Outbound
> 
> Francois Audet writes:
> 
>  > Rather, I think this should be a new draft, and it should 
> be  > independent from outbound.
> 
> so do you now finally agree to base outbound drfat on two new 
> drafts that are also independent of outbound: dialog 
> connection re-use and keepalive?
> 
> -- juha
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct  8 10:13:37 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B8E393A6BC3;
	Wed,  8 Oct 2008 10:13:37 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 817023A6BFC
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 10:13:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.204
X-Spam-Level: 
X-Spam-Status: No, score=-6.204 tagged_above=-999 required=5 tests=[AWL=0.044, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id kbAtL4A9JxTu for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 10:13:35 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id AC5F43A6BD6
	for <sip@ietf.org>; Wed,  8 Oct 2008 10:13:35 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	7E3C5203A7; Wed,  8 Oct 2008 17:17:28 +0200 (CEST)
X-AuditID: c1b4fb3e-a9686bb000007a96-87-48eccf08a8f2
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	5F48D20179; Wed,  8 Oct 2008 17:17:28 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 8 Oct 2008 17:17:28 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 8 Oct 2008 17:17:27 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8C9@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Outbound: keep-alives on dialog flows
Thread-Index: AckpWPlJ7iefydswRVaN7SAqinZOwA==
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: <sip@ietf.org>
X-OriginalArrivalTime: 08 Oct 2008 15:17:28.0170 (UTC)
	FILETIME=[F9CEA4A0:01C92958]
X-Brightmail-Tracker: AAAAAA==
Cc: Francois Audet <audet@nortel.com>
Subject: [Sip] Outbound: keep-alives on dialog flows
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1658224574=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1658224574==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C92958.F9930257"

This is a multi-part message in MIME format.

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


Hi,

As I asked in another e-mail, are keep-alives sent on dialog initated
Outbound flows?

I need to know, because in that case the non-registration use-case can
be removed from the sip-keep draft.

Regards,

Christer

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>Outbound: keep-alives on dialog flows</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>

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

<P><FONT SIZE=3D2 FACE=3D"Arial">As I asked in another e-mail, are =
keep-alives sent on dialog initated Outbound flows?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I need to know, because in that case =
the non-registration use-case can be removed from the sip-keep =
draft.</FONT>
</P>

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

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

</BODY>
</HTML>
------_=_NextPart_001_01C92958.F9930257--

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

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


From sip-bounces@ietf.org  Wed Oct  8 13:30:53 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C6E5B3A698A;
	Wed,  8 Oct 2008 13:30:53 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E46A13A698A
	for <sip@core3.amsl.com>; Wed,  8 Oct 2008 13:30:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level: 
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5
	tests=[AWL=-0.350, BAYES_00=-2.599, J_BACKHAIR_43=1,
	MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id q5Y6OVAcfLdV for <sip@core3.amsl.com>;
	Wed,  8 Oct 2008 13:30:52 -0700 (PDT)
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187])
	by core3.amsl.com (Postfix) with ESMTP id C64113A691D
	for <sip@ietf.org>; Wed,  8 Oct 2008 13:30:51 -0700 (PDT)
Received: by nf-out-0910.google.com with SMTP id b11so1634681nfh.39
	for <sip@ietf.org>; Wed, 08 Oct 2008 13:31:21 -0700 (PDT)
Received: by 10.210.20.17 with SMTP id 17mr10468540ebt.59.1223497881692;
	Wed, 08 Oct 2008 13:31:21 -0700 (PDT)
Received: from portatil.local (112.pool85-58-14.dynamic.orange.es
	[85.58.14.112])
	by mx.google.com with ESMTPS id g11sm74601gve.8.2008.10.08.13.31.19
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Wed, 08 Oct 2008 13:31:20 -0700 (PDT)
From: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
To: sip@ietf.org
Date: Wed, 8 Oct 2008 22:31:16 +0200
User-Agent: KMail/1.9.9
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<200810080134.10193.ibc@aliax.net> <48ECB6C4.7020903@cisco.com>
In-Reply-To: <48ECB6C4.7020903@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810082231.17038.ibc@aliax.net>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

El Mi=E9rcoles, 8 de Octubre de 2008, Paul Kyzivat escribi=F3:

> Its certainly not an idea that appeals to me.
>
> It requires an entirely non-standard routing algorithm within the proxy,
> selecting contact URI from among the available candidates in a very
> weird way.

Yes, true.


> Its an axiom of sip that UAs may choose their contact addresses as they
> wish. The encoding of any semantic information into that address is the
> business of the UA and not for any other server to second guess.

True again.


> In your example, the same proxy is responsible for the following AORs:
> - tel:+34111111
> - tel:+34222222
> - sip:a@domain.com
>
> and probably:
>
> - sip:+34111111@domain.com
> - sip:+34222222@domain.com
>
> Rather than have the UA register for a@domain.com and have the proxy do
> a weird mapping based on registered contact addresses, =


Why "weird"? it could be done based on a private ENUM that maps PSTN number=
s =

to SIP users without the need of having PSTN numbers as userinfo in the loc=
al =

SIP users.

I could allow a user sip:a@domain.org registering for the AoR sip:
+3411111@domain.org, but then I need to control in the registrar if the =

user "a@domain.org" has permissions to register that AoR. IMHO it's easier =
if =

the mapping PSTN<->SIP is done by the proxy instead of depending on the =

users, isn't?



> its much more =

> straightforward to have the UA register as follows:
>
> REGISTER sip:domain.com
> From: sip:+34111111@domain.com
> To: sip:+34111111@domain.com
> Contact: sip:+34111111@my_ip
>
> REGISTER sip:domain.com
> From: sip:+34222222@domain.com
> To: sip:+34222222@domain.com
> Contact: sip:+34222222@my_ip
>
> (Its required to use the sip form of the AOR rather than the tel form.
> Can't have a tel as the To of a REGISTER.)
>
> 	Thanks,
> 	Paul



-- =

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


From sip-bounces@ietf.org  Thu Oct  9 02:04:19 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EA34C3A68A6;
	Thu,  9 Oct 2008 02:04:18 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BE52C3A68A6
	for <sip@core3.amsl.com>; Thu,  9 Oct 2008 02:04:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.201
X-Spam-Level: *
X-Spam-Status: No, score=1.201 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, J_CHICKENPOX_12=0.6, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Uf5Blo9RWon0 for <sip@core3.amsl.com>;
	Thu,  9 Oct 2008 02:04:17 -0700 (PDT)
Received: from mx1.shearar.net (mx1.shearar.net [72.21.63.189])
	by core3.amsl.com (Postfix) with ESMTP id 163453A6893
	for <sip@ietf.org>; Thu,  9 Oct 2008 02:04:16 -0700 (PDT)
Received: from [41.241.57.163] (helo=bismuth)
	by mx1.shearar.net with smtp (Exim 4.63)
	(envelope-from <frank.shearar@angband.za.org>) id 1KnrSF-0006Jk-J9
	for sip@ietf.org; Thu, 09 Oct 2008 11:05:08 +0200
Message-ID: <000901c929ee$06cad080$0600000a@newtechnologies.org.uk>
From: "Frank Shearar" <frank.shearar@angband.za.org>
To: <sip@ietf.org>
Date: Thu, 9 Oct 2008 11:02:12 +0200
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1933
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1933
Subject: [Sip] (Minor) bug in RFC 3264 section 9?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Section 9 of RFC 3264 contains Figure 1:

   v=0
   o=carol 28908764872 28908764872 IN IP4 100.3.6.6
   s=-
   t=0 0
   c=IN IP4 192.0.2.4
   m=audio 0 RTP/AVP 0 1 3
   a=rtpmap:0 PCMU/8000
   a=rtpmap:1 1016/8000
   a=rtpmap:3 GSM/8000
   m=video 0 RTP/AVP 31 34
   a=rtpmap:31 H261/90000
   a=rtpmap:34 H263/90000

   Figure 1: SDP Indicating Capabilities

RFC 4566 (Section 5, page 8) says that t headers come AFTER connection
headers. Thus, should this figure not transpose the c & t headers?

frank

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


From sip-bounces@ietf.org  Thu Oct  9 02:13:28 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 45DFA3A6C5D;
	Thu,  9 Oct 2008 02:13:28 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 458783A6B40
	for <sip@core3.amsl.com>; Thu,  9 Oct 2008 02:13:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.399
X-Spam-Level: 
X-Spam-Status: No, score=-5.399 tagged_above=-999 required=5 tests=[AWL=0.001, 
	BAYES_00=-2.599, J_CHICKENPOX_12=0.6, J_CHICKENPOX_15=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id n-fLi499mDKF for <sip@core3.amsl.com>;
	Thu,  9 Oct 2008 02:13:26 -0700 (PDT)
Received: from ind-iport-1.cisco.com (ind-iport-1.cisco.com [64.104.129.195])
	by core3.amsl.com (Postfix) with ESMTP id A1E973A6904
	for <sip@ietf.org>; Thu,  9 Oct 2008 02:13:25 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,382,1220227200"; d="scan'208";a="30484111"
Received: from hkg-dkim-1.cisco.com ([10.75.231.161])
	by ind-iport-1.cisco.com with ESMTP; 09 Oct 2008 09:13:43 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94])
	by hkg-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m999Dghh004353; 
	Thu, 9 Oct 2008 17:13:42 +0800
Received: from xbh-hkg-412.apac.cisco.com (xbh-hkg-412.cisco.com
	[64.104.123.69])
	by hkg-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m999DaBQ004678;
	Thu, 9 Oct 2008 09:13:42 GMT
Received: from xmb-hkg-412.apac.cisco.com ([64.104.123.84]) by
	xbh-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 9 Oct 2008 17:13:33 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 9 Oct 2008 17:13:32 +0800
Message-ID: <F86B91A10B14744E88408E80B8A30EF3039F3535@xmb-hkg-412.apac.cisco.com>
In-Reply-To: <000901c929ee$06cad080$0600000a@newtechnologies.org.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] (Minor) bug in RFC 3264 section 9?
Thread-Index: Ackp7jDJXgqs4hROSiyHR+il9ESmgAAAQnUg
References: <000901c929ee$06cad080$0600000a@newtechnologies.org.uk>
From: "Rockson Li (zhengyli)" <zhengyli@cisco.com>
To: "Frank Shearar" <frank.shearar@angband.za.org>, <sip@ietf.org>
X-OriginalArrivalTime: 09 Oct 2008 09:13:33.0508 (UTC)
	FILETIME=[4DBF6040:01C929EF]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1156; t=1223543622;
	x=1224407622; c=relaxed/simple; s=hkgdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=zhengyli@cisco.com;
	z=From:=20=22Rockson=20Li=20(zhengyli)=22=20<zhengyli@cisco.
	com>
	|Subject:=20RE=3A=20[Sip]=20(Minor)=20bug=20in=20RFC=203264
	=20section=209? |Sender:=20;
	bh=o7mP5mxbA6NZTUjTj0unzs+8VmKAsqVjfEtWTRFXtSE=;
	b=FRIDOp9ZNH4IH35bC1zDJ44iR1+RzDii9sPjIW+DSkdwC1gFSJeIINVMwO
	ChdMM5n5J2zj7Q30GgxNluPVdQFi+AX9FOq+F3hevAGJFkdBBHpEa6jvP2hl
	CvroIVgcvqnd238MnbqGvMv28ax8yL8Jqrsn4p3lsQcp8/zWt+fRU=;
Authentication-Results: hkg-dkim-1; header.From=zhengyli@cisco.com; dkim=pass (
	sig from cisco.com/hkgdkim1002 verified; ); 
Subject: Re: [Sip] (Minor) bug in RFC 3264 section 9?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Frank,

I agree with you, it looks like a minor bug.

-Rockson 

-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Frank Shearar
Sent: Thursday, October 09, 2008 5:02 PM
To: sip@ietf.org
Subject: [Sip] (Minor) bug in RFC 3264 section 9?

Section 9 of RFC 3264 contains Figure 1:

   v=0
   o=carol 28908764872 28908764872 IN IP4 100.3.6.6
   s=-
   t=0 0
   c=IN IP4 192.0.2.4
   m=audio 0 RTP/AVP 0 1 3
   a=rtpmap:0 PCMU/8000
   a=rtpmap:1 1016/8000
   a=rtpmap:3 GSM/8000
   m=video 0 RTP/AVP 31 34
   a=rtpmap:31 H261/90000
   a=rtpmap:34 H263/90000

   Figure 1: SDP Indicating Capabilities

RFC 4566 (Section 5, page 8) says that t headers come AFTER connection
headers. Thus, should this figure not transpose the c & t headers?

frank

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


From sip-bounces@ietf.org  Thu Oct  9 14:00:44 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1B64B3A694E;
	Thu,  9 Oct 2008 14:00:44 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C17A43A694E
	for <sip@core3.amsl.com>; Thu,  9 Oct 2008 14:00:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gx7h5oYbGWCU for <sip@core3.amsl.com>;
	Thu,  9 Oct 2008 14:00:42 -0700 (PDT)
Received: from zrtps0kn.nortel.com (zrtps0kn.nortel.com [47.140.192.55])
	by core3.amsl.com (Postfix) with ESMTP id D06863A68DB
	for <sip@ietf.org>; Thu,  9 Oct 2008 14:00:41 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m99Kxps13032; Thu, 9 Oct 2008 20:59:51 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 9 Oct 2008 15:59:32 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF19AB3966@zrc2hxm0.corp.nortel.com>
In-Reply-To: <C980492A76B70E4D9D5DE9299F333F1601181E4E@vaebe104.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
Thread-Index: Acko9g/3UqVCzekXRAG4ZhtoX146RABW0poQ
References: <C980492A76B70E4D9D5DE9299F333F1601181E4E@vaebe104.NOE.Nokia.com>
From: "Francois Audet" <audet@nortel.com>
To: <georg.mayer@nokia.com>, <sip@ietf.org>
Subject: Re: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0771859115=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0771859115==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C92A51.EE009C60"

This is a multi-part message in MIME format.

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

I think you are correct.
=20
It doesn't mean we couldn't re-use reg-id for other purposes however.


________________________________

	From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of =
georg.mayer@nokia.com
	Sent: Tuesday, October 07, 2008 20:30
	To: sip@ietf.org
	Subject: [Sip] Is GRUU generated in the case of registration with =
instance-ID and reg-ID
=09
=09

	Hello,=20

	Both Outbound and GRUU drafts make use of the instance-ID for different =
purposes during SIP registration. In GRUU only the instance-ID is needed =
to generate a GRUU. For Outbound both, instance-ID and reg-ID are =
needed.

	My question now is, whether a GRUU will be generated when a REGISTER is =
received at the registrar, which indicates both reg-ID and instance-ID =
in the Contact header. Reading outbound, it seems like instance-ID + =
reg-ID are *only* used for outbound purposes.=20

	Thanks a lot for your help.=20

	Best regards=20
	Georg=20


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Is GRUU generated in the case of registration with =
instance-ID and reg-ID</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3395" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D390255520-09102008><FONT =
face=3DArial=20
color=3D#800000 size=3D2>I think you are correct.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D390255520-09102008><FONT =
face=3DArial=20
color=3D#800000 size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D390255520-09102008><FONT =
face=3DArial=20
color=3D#800000 size=3D2>It doesn't mean we couldn't re-use reg-id for =
other=20
purposes however.</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #800000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> sip-bounces@ietf.org=20
  [mailto:sip-bounces@ietf.org] <B>On Behalf Of=20
  </B>georg.mayer@nokia.com<BR><B>Sent:</B> Tuesday, October 07, 2008=20
  20:30<BR><B>To:</B> sip@ietf.org<BR><B>Subject:</B> [Sip] Is GRUU =
generated in=20
  the case of registration with instance-ID and =
reg-ID<BR></FONT><BR></DIV>
  <DIV></DIV><!-- Converted from text/rtf format -->
  <P><SPAN lang=3Dde><FONT face=3DArial size=3D2>Hello,</FONT></SPAN> =
</P>
  <P><SPAN lang=3Dde><FONT face=3DArial size=3D2>Both Outbound and GRUU =
drafts make=20
  use of the instance-ID for different purposes during SIP registration. =
In GRUU=20
  only the instance-ID is needed to generate a GRUU. For Outbound both,=20
  instance-ID and reg-ID are needed.</FONT></SPAN></P>
  <P><SPAN lang=3Dde><FONT face=3DArial size=3D2>My question now is, =
whether a GRUU=20
  will be generated when a REGISTER is received at the registrar, which=20
  indicates both reg-ID and instance-ID in the Contact header. Reading =
outbound,=20
  it seems like instance-ID + reg-ID are *only* used for outbound =
purposes.=20
  </FONT></SPAN></P>
  <P><SPAN lang=3Dde><FONT face=3DArial size=3D2>Thanks a lot for your=20
  help.</FONT></SPAN> </P>
  <P><SPAN lang=3Dde><FONT face=3DArial size=3D2>Best =
regards</FONT></SPAN> <BR><SPAN=20
  lang=3Dde><FONT face=3DArial size=3D2>Georg</FONT></SPAN><SPAN =
lang=3Den-us></SPAN>=20
  </P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C92A51.EE009C60--

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

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


From sip-bounces@ietf.org  Fri Oct 10 12:09:42 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7B13A3A68A9;
	Fri, 10 Oct 2008 12:09:42 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5F7533A6880
	for <sip@core3.amsl.com>; Fri, 10 Oct 2008 12:09:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Mmex6W+17U5k for <sip@core3.amsl.com>;
	Fri, 10 Oct 2008 12:09:40 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56])
	by core3.amsl.com (Postfix) with ESMTP id 612D93A635F
	for <sip@ietf.org>; Fri, 10 Oct 2008 12:09:40 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m9AJANk22047; Fri, 10 Oct 2008 19:10:23 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 10 Oct 2008 14:10:22 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF19B03514@zrc2hxm0.corp.nortel.com>
In-Reply-To: <18666.20359.413310.214443@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackn2/50PLWpXaPIRfiM7QVms7Z6cgDL35mQ
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eem! !	! ea.er
	icsson.se> < 18665.59269.640606.477292@taimen.test.fi>
	<CDA30DAD-DE21-4A5D-BF67-9A49DF32B4EA@softarmor.com>
	<18666.16422.211242.766454@taimen.test.fi>
	<ADB2E3A0-DAF6-432B-B269-A10E9D38E6EA@softarmor.com>
	<18666.20359.413310.214443@taimen.test.fi>
From: "Francois Audet" <audet@nortel.com>
To: "Juha Heinanen" <jh@tutpro.com>, "Dean Willis" <dean.willis@softarmor.com>
Cc: sip@ietf.org, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Juha,

I think outbound will help us to implement redundant proxy/registrar
without the need for load balancers/clusters/etc.

But it's not currently in the spec. I view it as something of high
priority that we should be looking at. But we'll never get there if we 
don't get outbound out the door first.
 

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Juha Heinanen
> Sent: Monday, October 06, 2008 10:49
> To: Dean Willis
> Cc: sip@ietf.org; Christer Holmberg
> Subject: Re: [Sip] Dual registration without Outbound
> 
> Dean Willis writes:
> 
>  > Why do I get the feeling that you won't be happy even when 
> every UA is  > forced to register every contact it has or 
> might obtain have with  > every registrar that ever existed 
> or will exist ;-)?
> 
> dean,
> 
> that is not true.  i sincerely hoped that outbound would help 
> me to implement redundant proxy/registrar without a need to 
> for load balancers, database clusters, or forwarding of 
> requests between proxies simply by being able to assume that 
> if i have two ob proxies, each ua would register all contacts 
> that it has via both of them.  
> 
> this is a VERY simple, easy to understand and implement 
> requirement compared to anything else this working group has 
> ever produced.
> 
> -- juha
> 
> 
> 
>  >
>  > On Oct 6, 2008, at 11:43 AM, Juha Heinanen wrote:
>  >
>  > > Dean Willis writes:
>  > >
>  > >> Assume a UA has two different interfaces, and it 
> registers each of  > >> its  > >> interfaces with a different 
> proxy/registrar. Further assume that  > >> those  > >> two 
> proxy registrars collude with respect to mapping the user's 
> AUR  > >> onto those contacts.
>  > >
>  > > that "collude" thing is exactly what i tried to avoid.  
> if ua is  > > required to register all of its contacts via 
> both proxies, then  > > redundancy of the service can be 
> implemented by running the  > > two proxy/registrars 
> completely independent of each other thus greatly  > > 
> simplifying the implementation.
>  > >
>  > > if that requirement is not there, ob becomes totally 
> useless again and  > > there was no advantage that the text 
> was changed according to my  > > wishes.  you may as well go 
> and change it back to what it was before.
>  >
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors@cs.columbia.edu for questions on current sip 
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 10 12:38:49 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 529C13A68F4;
	Fri, 10 Oct 2008 12:38:49 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1C1333A68F4
	for <sip@core3.amsl.com>; Fri, 10 Oct 2008 12:38:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YSJiyAwR4fxS for <sip@core3.amsl.com>;
	Fri, 10 Oct 2008 12:38:47 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id 403813A635F
	for <sip@ietf.org>; Fri, 10 Oct 2008 12:38:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id BAE2D1EC30B;
	Fri, 10 Oct 2008 22:39:32 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id NbRCCgpJwBfb; Fri, 10 Oct 2008 22:39:29 +0300 (EEST)
Received: from taimen (h138025.gprs.dnafinland.fi [87.93.138.25])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Fri, 10 Oct 2008 22:39:29 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id B955BAC0BF; Fri, 10 Oct 2008 22:39:25 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18671.44909.216290.711492@taimen.test.fi>
Date: Fri, 10 Oct 2008 22:39:25 +0300
To: "Francois Audet" <audet@nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF19B03514@zrc2hxm0.corp.nortel.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eem! !	! ea.er
	icsson.se> < 18665.59269.640606.477292@taimen.test.fi>
	<CDA30DAD-DE21-4A5D-BF67-9A49DF32B4EA@softarmor.com>
	<18666.16422.211242.766454@taimen.test.fi>
	<ADB2E3A0-DAF6-432B-B269-A10E9D38E6EA@softarmor.com>
	<18666.20359.413310.214443@taimen.test.fi>
	<1ECE0EB50388174790F9694F77522CCF19B03514@zrc2hxm0.corp.nortel.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Christer Holmberg <christer.holmberg@ericsson.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Francois Audet writes:

 > But it's not currently in the spec. I view it as something of high
 > priority that we should be looking at. But we'll never get there if we 
 > don't get outbound out the door first.

it takes years for UA vendors to implement outbound draft and more than
10 years the followup version.  by then, sip may be already replaced by
something else.  so if you want outbound to have any value, it needs to
be get right the first shot.

also, it was not clear to me (and looks like also some experts), what
instance-id means and what effect it has to forking to multiple
contacts.  if everything in outbound is not crystal clear, it makes no
sense to publish it.

-- juha

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


From sip-bounces@ietf.org  Fri Oct 10 13:35:28 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D71C53A68A6;
	Fri, 10 Oct 2008 13:35:28 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D175C3A68A6
	for <sip@core3.amsl.com>; Fri, 10 Oct 2008 13:35:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LDMFt-DHuDyE for <sip@core3.amsl.com>;
	Fri, 10 Oct 2008 13:35:27 -0700 (PDT)
Received: from zcars04f.nortel.com (zcars04f.nortel.com [47.129.242.57])
	by core3.amsl.com (Postfix) with ESMTP id C84313A68A0
	for <sip@ietf.org>; Fri, 10 Oct 2008 13:35:26 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m9AKa8400072; Fri, 10 Oct 2008 20:36:09 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 10 Oct 2008 15:35:56 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF19B0377A@zrc2hxm0.corp.nortel.com>
In-Reply-To: <18671.44909.216290.711492@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckrD+1cAGzcB/vpR8yLaYu4DCoIzQAB7PGw
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eem! ! !	! ea.
	er icsson.se >	<	18665.59269.640606.477292@taimen.test.fi>
	<CDA30DAD-DE21-4A5D-BF67-9A49DF32B4EA@softarmor.com>
	<18666.16422.211242.766454@taimen.test.fi>
	<ADB2E3A0-DAF6-432B-B269-A10E9D38E6EA@softarmor.com>
	<18666.20359.413310.214443@taimen.test.fi>
	<1ECE0EB50388174790F9694F77522CCF19B03514@zrc2hxm0.corp.nortel.com>
	<18671.44909.216290.711492@taimen.test.fi>
From: "Francois Audet" <audet@nortel.com>
To: "Juha Heinanen" <jh@tutpro.com>
Cc: sip@ietf.org, Christer Holmberg <christer.holmberg@ericsson.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Nobody is talking about a "second version" of outbound.

Somebody just need to write a draft on high-availability. 

> -----Original Message-----
> From: Juha Heinanen [mailto:jh@tutpro.com] 
> Sent: Friday, October 10, 2008 12:39
> To: Audet, Francois (SC100:3055)
> Cc: Dean Willis; sip@ietf.org; Christer Holmberg
> Subject: RE: [Sip] Dual registration without Outbound
> 
> Francois Audet writes:
> 
>  > But it's not currently in the spec. I view it as something 
> of high  > priority that we should be looking at. But we'll 
> never get there if we  > don't get outbound out the door first.
> 
> it takes years for UA vendors to implement outbound draft and 
> more than 10 years the followup version.  by then, sip may be 
> already replaced by something else.  so if you want outbound 
> to have any value, it needs to be get right the first shot.
> 
> also, it was not clear to me (and looks like also some 
> experts), what instance-id means and what effect it has to 
> forking to multiple contacts.  if everything in outbound is 
> not crystal clear, it makes no sense to publish it.
> 
> -- juha
> 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 10 16:11:04 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A375528C103;
	Fri, 10 Oct 2008 16:11:04 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B423728C103
	for <sip@core3.amsl.com>; Fri, 10 Oct 2008 16:11:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.205
X-Spam-Level: 
X-Spam-Status: No, score=-6.205 tagged_above=-999 required=5 tests=[AWL=0.043, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id DAY8IXu2VT4X for <sip@core3.amsl.com>;
	Fri, 10 Oct 2008 16:11:02 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 9D73628C0FD
	for <sip@ietf.org>; Fri, 10 Oct 2008 16:11:02 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	B102420711; Sat, 11 Oct 2008 01:11:48 +0200 (CEST)
X-AuditID: c1b4fb3e-a7e83bb000007a96-7a-48efe1341175
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	89F882006C; Sat, 11 Oct 2008 01:11:48 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 11 Oct 2008 01:11:48 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 11 Oct 2008 01:11:47 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
Thread-Index: AckrLZH1Tdf2a3GNSVKvr0LtBeKQ8Q==
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: <sip@ietf.org>
X-OriginalArrivalTime: 10 Oct 2008 23:11:48.0232 (UTC)
	FILETIME=[9226F880:01C92B2D]
X-Brightmail-Tracker: AAAAAA==
Cc: Francois Audet <audet@nortel.com>
Subject: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0616154028=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0616154028==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C92B2D.91D57ED4"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C92B2D.91D57ED4
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Hi Francoise,

So, how would the registrar know whether a GRUU is requested or not in
the case described by Georg? Based on whether the gruu option-tag is
present?

It would be good to clarify this in the outbound spec.

Regards,

Christer



>>I think you are correct.
>>=20
>>It doesn't mean we couldn't re-use reg-id for other purposes however.

>Hello,
>
>Both Outbound and GRUU drafts make use of the instance-ID for different
purposes during SIP registration. In GRUU only the instance-ID is needed
to generate a GRUU. >For Outbound both, instance-ID and reg-ID are
needed.
>
>My question now is, whether a GRUU will be generated when a REGISTER is
received at the registrar, which indicates both reg-ID and instance-ID
in the Contact=20
>header. Reading outbound, it seems like instance-ID + reg-ID are *only*
used for outbound purposes.
>
>Thanks a lot for your help.
>
>Best regards
>Georg

------_=_NextPart_001_01C92B2D.91D57ED4
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>[Sip] Is GRUU generated in the case of registration with =
instance-ID and reg-ID</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>

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

<P><FONT SIZE=3D2 FACE=3D"Arial">So, how would the registrar know =
whether a GRUU is requested or not in the case described by Georg? Based =
on whether the gruu option-tag is present?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">It would be good to clarify this in the =
outbound spec.</FONT>
</P>

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

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

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;I think you are correct.</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt; </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;It doesn't mean we couldn't =
re-use reg-id for other purposes however.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt;Hello,</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt;</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt;Both Outbound and GRUU drafts make =
use of the instance-ID for different purposes during SIP registration. =
In GRUU only the instance-ID is needed to generate a GRUU. &gt;For =
Outbound both, instance-ID and reg-ID are needed.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt;</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt;My question now is, whether a GRUU =
will be generated when a REGISTER is received at the registrar, which =
indicates both reg-ID and instance-ID in the Contact </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">&gt;header. Reading outbound, it seems =
like instance-ID + reg-ID are *only* used for outbound purposes.</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt;</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt;Thanks a lot for your help.</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt;</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt;Best regards</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&gt;Georg</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C92B2D.91D57ED4--

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

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


From sip-bounces@ietf.org  Fri Oct 10 17:49:36 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6CD7028C10F;
	Fri, 10 Oct 2008 17:49:36 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6AA7428C10F
	for <sip@core3.amsl.com>; Fri, 10 Oct 2008 17:49:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id xddqQCYadpxh for <sip@core3.amsl.com>;
	Fri, 10 Oct 2008 17:49:34 -0700 (PDT)
Received: from zrtps0kn.nortel.com (zrtps0kn.nortel.com [47.140.192.55])
	by core3.amsl.com (Postfix) with ESMTP id 607A028C0D8
	for <sip@ietf.org>; Fri, 10 Oct 2008 17:49:34 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m9B0oIw07310; Sat, 11 Oct 2008 00:50:18 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 10 Oct 2008 19:49:32 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
Thread-Index: AckrLZH1Tdf2a3GNSVKvr0LtBeKQ8QADaJLg
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>
From: "Francois Audet" <audet@nortel.com>
To: "Christer Holmberg" <christer.holmberg@ericsson.com>, <sip@ietf.org>
Subject: Re: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2041275714=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2041275714==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C92B3B.3A027D4C"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C92B3B.3A027D4C
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I think that's in the GRUU spec.


________________________________

	From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]=20
	Sent: Friday, October 10, 2008 16:12
	To: sip@ietf.org
	Cc: Audet, Francois (SC100:3055); georg.mayer@nokia.com
	Subject: [Sip] Is GRUU generated in the case of registration with =
instance-ID and reg-ID
=09
=09


	Hi Francoise,=20

	So, how would the registrar know whether a GRUU is requested or not in =
the case described by Georg? Based on whether the gruu option-tag is =
present?

	It would be good to clarify this in the outbound spec.=20

	Regards,=20

	Christer=20



	>>I think you are correct.=20
	>>=20
	>>It doesn't mean we couldn't re-use reg-id for other purposes however. =


	>Hello,=20
	>=20
	>Both Outbound and GRUU drafts make use of the instance-ID for =
different purposes during SIP registration. In GRUU only the instance-ID =
is needed to generate a GRUU. >For Outbound both, instance-ID and reg-ID =
are needed.

	>=20
	>My question now is, whether a GRUU will be generated when a REGISTER =
is received at the registrar, which indicates both reg-ID and =
instance-ID in the Contact=20

	>header. Reading outbound, it seems like instance-ID + reg-ID are =
*only* used for outbound purposes.=20
	>=20
	>Thanks a lot for your help.=20
	>=20
	>Best regards=20
	>Georg=20


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>[Sip] Is GRUU generated in the case of registration =
with instance-ID and reg-ID</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3395" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D659234900-11102008><FONT =
face=3DArial=20
color=3D#800000 size=3D2>I think that's in the GRUU =
spec.</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #800000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Christer Holmberg=20
  [mailto:christer.holmberg@ericsson.com] <BR><B>Sent:</B> Friday, =
October 10,=20
  2008 16:12<BR><B>To:</B> sip@ietf.org<BR><B>Cc:</B> Audet, Francois=20
  (SC100:3055); georg.mayer@nokia.com<BR><B>Subject:</B> [Sip] Is GRUU =
generated=20
  in the case of registration with instance-ID and =
reg-ID<BR></FONT><BR></DIV>
  <DIV></DIV><!-- Converted from text/rtf format --><BR>
  <P><FONT face=3DArial size=3D2>Hi Francoise,</FONT> </P>
  <P><FONT face=3DArial size=3D2>So, how would the registrar know =
whether a GRUU is=20
  requested or not in the case described by Georg? Based on whether the =
gruu=20
  option-tag is present?</FONT></P>
  <P><FONT face=3DArial size=3D2>It would be good to clarify this in the =
outbound=20
  spec.</FONT> </P>
  <P><FONT face=3DArial size=3D2>Regards,</FONT> </P>
  <P><FONT face=3DArial size=3D2>Christer</FONT> </P><BR><BR>
  <P><FONT face=3DArial size=3D2>&gt;&gt;I think you are correct.</FONT> =
<BR><FONT=20
  face=3DArial size=3D2>&gt;&gt; </FONT><BR><FONT face=3DArial =
size=3D2>&gt;&gt;It=20
  doesn't mean we couldn't re-use reg-id for other purposes =
however.</FONT> </P>
  <P><FONT face=3DArial size=3D2>&gt;Hello,</FONT> <BR><FONT =
face=3DArial=20
  size=3D2>&gt;</FONT> <BR><FONT face=3DArial size=3D2>&gt;Both Outbound =
and GRUU=20
  drafts make use of the instance-ID for different purposes during SIP=20
  registration. In GRUU only the instance-ID is needed to generate a =
GRUU.=20
  &gt;For Outbound both, instance-ID and reg-ID are needed.</FONT></P>
  <P><FONT face=3DArial size=3D2>&gt;</FONT> <BR><FONT face=3DArial =
size=3D2>&gt;My=20
  question now is, whether a GRUU will be generated when a REGISTER is =
received=20
  at the registrar, which indicates both reg-ID and instance-ID in the =
Contact=20
  </FONT></P>
  <P><FONT face=3DArial size=3D2>&gt;header. Reading outbound, it seems =
like=20
  instance-ID + reg-ID are *only* used for outbound purposes.</FONT> =
<BR><FONT=20
  face=3DArial size=3D2>&gt;</FONT> <BR><FONT face=3DArial =
size=3D2>&gt;Thanks a lot for=20
  your help.</FONT> <BR><FONT face=3DArial size=3D2>&gt;</FONT> =
<BR><FONT face=3DArial=20
  size=3D2>&gt;Best regards</FONT> <BR><FONT face=3DArial =
size=3D2>&gt;Georg</FONT>=20
  </P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C92B3B.3A027D4C--

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

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


From sip-bounces@ietf.org  Fri Oct 10 19:43:04 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5144E3A6935;
	Fri, 10 Oct 2008 19:43:04 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 74BDC3A6935
	for <sip@core3.amsl.com>; Fri, 10 Oct 2008 19:43:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.567
X-Spam-Level: 
X-Spam-Status: No, score=-3.567 tagged_above=-999 required=5 tests=[AWL=0.032, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id sTLq2-pjOvgP for <sip@core3.amsl.com>;
	Fri, 10 Oct 2008 19:43:01 -0700 (PDT)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146])
	by core3.amsl.com (Postfix) with ESMTP id 9FC9A3A68E0
	for <sip@ietf.org>; Fri, 10 Oct 2008 19:43:01 -0700 (PDT)
Received: from shell.TheWorld.com (monk@shell01.theworld.com [192.74.137.71])
	by TheWorld.com (8.13.6/8.13.6) with ESMTP id m9B2hiAX007459
	for <sip@ietf.org>; Fri, 10 Oct 2008 22:43:47 -0400
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1])
	by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id m9B2hi7X44222972
	for <sip@ietf.org>; Fri, 10 Oct 2008 22:43:44 -0400 (EDT)
Received: (from worley@localhost)
	by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id m9B2hdXh44296635;
	Fri, 10 Oct 2008 22:43:39 -0400 (EDT)
Date: Fri, 10 Oct 2008 22:43:39 -0400 (EDT)
Message-Id: <200810110243.m9B2hdXh44296635@shell01.TheWorld.com>
To: sip@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <C980492A76B70E4D9D5DE9299F333F1601181E4E@vaebe104.NOE.Nokia.com>
	(georg.mayer@nokia.com)
References: <C980492A76B70E4D9D5DE9299F333F1601181E4E@vaebe104.NOE.Nokia.com>
Subject: Re: [Sip] Is GRUU generated in the case of registration
	with	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

   From: <georg.mayer@nokia.com>

   Both Outbound and GRUU drafts make use of the instance-ID for different
   purposes during SIP registration. In GRUU only the instance-ID is needed
   to generate a GRUU. For Outbound both, instance-ID and reg-ID are
   needed.

   My question now is, whether a GRUU will be generated when a REGISTER is
   received at the registrar, which indicates both reg-ID and instance-ID
   in the Contact header. Reading outbound, it seems like instance-ID +
   reg-ID are *only* used for outbound purposes.

I'm not an expert on outbound, but looking at the uses of "GRUU" and
"instance" in the outbound draft there doesn't seem to be any
intention to forbid GRUU processing.  I would assume that GRUU
processing and outbound processing are independent, each triggered by
the appropriate conditions.

The diagram in section 5.4 of draft-ietf-sip-gruu-15.txt suggests that
multiple flows for a single UA would share the same GRUU.

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


From sip-bounces@ietf.org  Fri Oct 10 20:20:18 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D91A83A68FD;
	Fri, 10 Oct 2008 20:20:18 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C14CD3A6834
	for <sip@core3.amsl.com>; Fri, 10 Oct 2008 20:20:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.206
X-Spam-Level: 
X-Spam-Status: No, score=-6.206 tagged_above=-999 required=5 tests=[AWL=0.043, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id PEjbXwKW07VX for <sip@core3.amsl.com>;
	Fri, 10 Oct 2008 20:20:17 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id B88AA3A67E7
	for <sip@ietf.org>; Fri, 10 Oct 2008 20:20:15 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	9032E201E5; Sat, 11 Oct 2008 05:21:02 +0200 (CEST)
X-AuditID: c1b4fb3e-a9686bb000007a96-fd-48f01b9edd87
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	7429B20578; Sat, 11 Oct 2008 05:21:02 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 11 Oct 2008 05:21:01 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 11 Oct 2008 05:21:00 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
Thread-Index: AckrLZH1Tdf2a3GNSVKvr0LtBeKQ8QADaJLgAASHPY4=
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>
	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Francois Audet" <audet@nortel.com>,
	<sip@ietf.org>
X-OriginalArrivalTime: 11 Oct 2008 03:21:01.0894 (UTC)
	FILETIME=[633AB660:01C92B50]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


So, the following applies:


request                                        response
-------------------------------------------------------

instance-id AND Supported:gruu               =3D gruu
instance-id AND reg-id                       =3D outbound
instance-id AND reg-id AND Supported:gruu    =3D outbound AND gruu
instance-id                                  =3D n/a

Correct?

Regards,

Christer




-----Alkuper=E4inen viesti-----
L=E4hett=E4j=E4: Francois Audet [mailto:audet@nortel.com]
L=E4hetetty: la 11.10.2008 2:49
Vastaanottaja: Christer Holmberg; sip@ietf.org
Kopio: georg.mayer@nokia.com
Aihe: RE: [Sip] Is GRUU generated in the case of registration with instance=
-ID and reg-ID
 =

I think that's in the GRUU spec.


________________________________

	From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] =

	Sent: Friday, October 10, 2008 16:12
	To: sip@ietf.org
	Cc: Audet, Francois (SC100:3055); georg.mayer@nokia.com
	Subject: [Sip] Is GRUU generated in the case of registration with instance=
-ID and reg-ID
	=

	=



	Hi Francoise, =


	So, how would the registrar know whether a GRUU is requested or not in the=
 case described by Georg? Based on whether the gruu option-tag is present?

	It would be good to clarify this in the outbound spec. =


	Regards, =


	Christer =




	>>I think you are correct. =

	>> =

	>>It doesn't mean we couldn't re-use reg-id for other purposes however. =


	>Hello, =

	> =

	>Both Outbound and GRUU drafts make use of the instance-ID for different p=
urposes during SIP registration. In GRUU only the instance-ID is needed to =
generate a GRUU. >For Outbound both, instance-ID and reg-ID are needed.

	> =

	>My question now is, whether a GRUU will be generated when a REGISTER is r=
eceived at the registrar, which indicates both reg-ID and instance-ID in th=
e Contact =


	>header. Reading outbound, it seems like instance-ID + reg-ID are *only* u=
sed for outbound purposes. =

	> =

	>Thanks a lot for your help. =

	> =

	>Best regards =

	>Georg =



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


From sip-bounces@ietf.org  Fri Oct 10 21:08:49 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 468CD28C14B;
	Fri, 10 Oct 2008 21:08:49 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0F4FA3A68D7
	for <sip@core3.amsl.com>; Fri, 10 Oct 2008 21:08:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.207
X-Spam-Level: 
X-Spam-Status: No, score=-6.207 tagged_above=-999 required=5 tests=[AWL=0.042, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Cu0g2gPth7XW for <sip@core3.amsl.com>;
	Fri, 10 Oct 2008 21:08:47 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 092AA3A67A6
	for <sip@ietf.org>; Fri, 10 Oct 2008 21:08:45 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	73C1A20FD7; Sat, 11 Oct 2008 06:09:12 +0200 (CEST)
X-AuditID: c1b4fb3e-a8e85bb000007a96-99-48f026e84dfe
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	595A020FD6; Sat, 11 Oct 2008 06:09:12 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 11 Oct 2008 06:09:11 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 11 Oct 2008 06:09:11 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
In-Reply-To: <18668.51383.505850.963592@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckpVT4eWNK94IdGTZiC1ZOHcQ+AKACAEXKQ
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se><18665.59
	269.640606.477292@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se><48EBC88B.2030300@cisco.com><46101DEA-677B-4F28-AD1E-32F64385853
	5@s
	ofta	rmor.com><CA	9998CD4A020D418654FCDEF4E707DF05C0F8B8@esealmw113.eemea.ericsson.se><18668.21733.520868.113675@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se><48ECBA45.1070109@c
	is co.com> <CA9998CD4A0
	20D418654FCDEF4E707DF05C0F8C6@esealmw113.eemea.ericsson.se><18668.50247.121832.271341@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
	<18668.51383.505850.963592@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 11 Oct 2008 04:09:11.0739 (UTC)
	FILETIME=[1DB610B0:01C92B57]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Juha,

At one point you requested that a USER should establish at least two
register flows, and that was accepted.

That has NOT changed.

The only new thing is that the USER may use different contacts for
different flows. BUT, it is still the same USER, and that USER should
still register at least two register flows - either all flows from the
same contact, or from different contacts.

As far as I know, you have never before requested that the registrar,
for incoming requests, shall perform paralell forking on all registered
flows.

Regards,

Christer

 

> -----Original Message-----
> From: Juha Heinanen [mailto:jh@tutpro.com] 
> Sent: Wednesday, October 08, 2008 5:51 PM
> To: Christer Holmberg
> Cc: Paul Kyzivat; Dean Willis; sip@ietf.org
> Subject: RE: [Sip] Dual registration without Outbound
> 
> Christer Holmberg writes:
> 
>  > As specified, one should register with at least two ob 
> proxies, but my  > point is that it doesn't matter if those 
> two registrations are bound to  > the same contact, as long 
> as the user can be reached on both of the  > registrations.
> 
> it DOES matter if you consider complexity of implementing 
> redundant proxy/registrar.
> 
> -- juha
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 10 23:35:24 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D4E093A6A8D;
	Fri, 10 Oct 2008 23:35:24 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6F2953A69F7
	for <sip@core3.amsl.com>; Fri, 10 Oct 2008 23:35:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ttb7GCLzhIR9 for <sip@core3.amsl.com>;
	Fri, 10 Oct 2008 23:35:22 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id 96F763A6882
	for <sip@ietf.org>; Fri, 10 Oct 2008 23:35:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 612B81EC30B;
	Sat, 11 Oct 2008 09:36:03 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id C0aMmUvNd0WJ; Sat, 11 Oct 2008 09:35:53 +0300 (EEST)
Received: from taimen (h146058.gprs.dnafinland.fi [87.93.146.58])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Sat, 11 Oct 2008 09:35:53 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id A7D13AC0BF; Sat, 11 Oct 2008 09:35:46 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18672.18754.189767.996087@taimen.test.fi>
Date: Sat, 11 Oct 2008 09:35:46 +0300
To: "Francois Audet" <audet@nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF19B0377A@zrc2hxm0.corp.nortel.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eem! ! !	! ea.
	er icsson.se > <	18665.59269.640606.477292@taimen.test.fi>
	<CDA30DAD-DE21-4A5D-BF67-9A49DF32B4EA@softarmor.com>
	<18666.16422.211242.766454@taimen.test.fi>
	<ADB2E3A0-DAF6-432B-B269-A10E9D38E6EA@softarmor.com>
	<18666.20359.413310.214443@taimen.test.fi>
	<1ECE0EB50388174790F9694F77522CCF19B03514@zrc2hxm0.corp.nortel.com>
	<18671.44909.216290.711492@taimen.test.fi>
	<1ECE0EB50388174790F9694F77522CCF19B0377A@zrc2hxm0.corp.nortel.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Christer Holmberg <christer.holmberg@ericsson.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Francois Audet writes:

 > Nobody is talking about a "second version" of outbound.

it would be "second" version, because it would need to add to UA's
outbound behavior compared to ob rfc.

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


From sip-bounces@ietf.org  Fri Oct 10 23:53:58 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CD9243A67F8;
	Fri, 10 Oct 2008 23:53:58 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8B50A3A67F8
	for <sip@core3.amsl.com>; Fri, 10 Oct 2008 23:53:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Vw4xkGUiSnXf for <sip@core3.amsl.com>;
	Fri, 10 Oct 2008 23:53:56 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id 41AB33A67A3
	for <sip@ietf.org>; Fri, 10 Oct 2008 23:53:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id D64311EC310;
	Sat, 11 Oct 2008 09:54:05 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Ooo6SVz0Rp4G; Sat, 11 Oct 2008 09:54:02 +0300 (EEST)
Received: from taimen (h146058.gprs.dnafinland.fi [87.93.146.58])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Sat, 11 Oct 2008 09:54:02 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id A6E3AAC0BF; Sat, 11 Oct 2008 09:53:58 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18672.19846.621765.332209@taimen.test.fi>
Date: Sat, 11 Oct 2008 09:53:58 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>
	<18665.59 269.640606.477292@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
	<48EBC88B.2030300@cisco.com>
	<46101DEA-677B-4F28-AD1E-32F64385853 5@s ofta	rmor.com>
	<CA	9998CD4A020D418654FCDEF4E707DF05C0F8B8@esealmw113.eemea.ericsson.se>
	<18668.21733.520868.113675@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se>
	<48ECBA45.1070109@c is co.com> <CA9998CD4A0
	20D418654FCDEF4E707DF05C0F8C6@esealmw113.eemea.ericsson.se>
	<18668.50247.121832.271341@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
	<18668.51383.505850.963592@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > The only new thing is that the USER may use different contacts for
 > different flows. BUT, it is still the same USER, and that USER should
 > still register at least two register flows - either all flows from the
 > same contact, or from different contacts.
 > 
 > As far as I know, you have never before requested that the registrar,
 > for incoming requests, shall perform paralell forking on all registered
 > flows.

it is not SHALL, but it MUST BE POSSIBLE to do if the user wants that to
happen.

in my example the same UA instance registers AoR sip:jh@tutpro.com over
its gprs and 3g interfaces with different contact addresses (one from
ggsn and the other one from lan).

first, like today without outbound, it must be possible with outbound
that incoming call to sip:jh@tutpro.com gets parallel forked to the two
contacts of this UA instance.  now i tried to figure out what ob draft
says about it and found this:

7. Authoritative Proxy Procedures: Forwarding Requests

   When a proxy uses the location service to look up a registration
   binding and then proxies a request to a particular contact, it
   selects a contact to use normally, with a few additional rules:

   o  The proxy MUST NOT populate the target set with more than one
      contact with the same AOR and instance-id at a time.

to me this clearly means that parallel forking is not anymore possible
when UA implements outbound, which would be a VERY SEVERE restriction
and change of RFC3261 behavior.

second, if the UA instance may choose to register one of its two
contacts via ob proxy 1 and the other via ob proxy 2, it makes
simple implementation of redundancy with two proxy/registrar pairs
impossible.

these two issues currently make outbound useless to me (and i have not
read even half of the current version, so there may be many more in the
closet).

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


From sip-bounces@ietf.org  Sat Oct 11 14:09:19 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ABDF03A682C;
	Sat, 11 Oct 2008 14:09:19 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6EAC43A67D2
	for <sip@core3.amsl.com>; Sat, 11 Oct 2008 14:09:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id b0UA82Q0ZFqg for <sip@core3.amsl.com>;
	Sat, 11 Oct 2008 14:09:17 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id 717013A682C
	for <sip@ietf.org>; Sat, 11 Oct 2008 14:09:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 201681EC30B;
	Sun, 12 Oct 2008 00:10:03 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id uquO7MZtbIgK; Sun, 12 Oct 2008 00:10:00 +0300 (EEST)
Received: from taimen (h138061.gprs.dnafinland.fi [87.93.138.61])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Sun, 12 Oct 2008 00:10:00 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 8EF08AC0EE; Sun, 12 Oct 2008 00:09:53 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18673.5665.337048.880648@taimen.test.fi>
Date: Sun, 12 Oct 2008 00:09:53 +0300
To: "Dean Willis" <dean.willis@softarmor.com>
In-Reply-To: <2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
	<48EBC88B.2030300@cisco.com>
	<18668.21733.520868.113675@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se>
	<18668.50247.121832.271341@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
	<18668.51383.505850.963592@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Dean Willis writes:

 > Seems like what you are asking for is for a proxy to require parallel
 > forking to multiple contacts regsitered by a single UA. 

huh, i'm not asking anything beyond what is in rfc3261 and what is
currently working fine in practise.  or can you point to text in rfc3261
that prohibits a single UA registering several contacts for a single
AoR and that prohibits a proxy parallel forking to those contacts when
the contacts share the same q value?

 > That is not
 > only out of scope for outbound, it is also undesirable behaivior (as
 > in totally broken) for a great number of use cases. 

i didn't know that normal rfc3261 compliant behavior is outside of scope
of outbound.  was it listed in outbound requirements that outbound
should obsolete forking that has been there from the very beginning and
that many applications rely on?  could you quote the requirements text
on that?

also, what wrong or undesirable there is in the forking example that i
have described in earlier messages?
 
 > Consequently, this
 > means it would require a great deal of documentation around the use
 > cases for which it makes sense. I do not think this can be done
 > reasonably in the outbound draft.

outbound should not change current rfc3261 compliant forking behavior.
it has to support it and if more text is needed, then it is outbound
editors' problem.  forking is much more important than outbound
especially when many UAs have already implemented things like keepalives
without outbound.

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


From sip-bounces@ietf.org  Sat Oct 11 15:10:01 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5912F3A68CF;
	Sat, 11 Oct 2008 15:10:01 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E5C6C3A68B9
	for <sip@core3.amsl.com>; Sat, 11 Oct 2008 15:09:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.611
X-Spam-Level: **
X-Spam-Status: No, score=2.611 tagged_above=-999 required=5 tests=[AWL=0.610, 
	BAYES_80=2, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id roJC26rSmT-w for <sip@core3.amsl.com>;
	Sat, 11 Oct 2008 15:09:59 -0700 (PDT)
Received: from web52102.mail.re2.yahoo.com (web52102.mail.re2.yahoo.com
	[206.190.48.105])
	by core3.amsl.com (Postfix) with SMTP id 34B7D3A68CF
	for <sip@ietf.org>; Sat, 11 Oct 2008 15:09:59 -0700 (PDT)
Received: (qmail 47071 invoked by uid 60001); 11 Oct 2008 22:10:48 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Message-ID;
	b=w2AbkpoIzfF1vnS80S8hAC55guZkHsO/wKXOEk3GUd/zP6zsX7b1jaS1r6ht+5yTlYOBtxj4WXH7Bo8tJYUfn9kR9QQ1VBY4Jng2xcOKlVzB8qTf7NreZ7hG+XQFloqNfyu447mVQz6TVTVO6GneESlStI0UifoMpd3zHHLwmaw=;
X-YMail-OSG: 0fS02oIVM1lghqRP3KANywWX0gsF2yx2L0StEX1PmgwusrB03iMAGbMHhskvoOX5SPE2R4IPe.5XzCwYO4zqZEeZZe_mYiEcKVxwpdY48NGSQnEfLaIzCgp1kVHiEz1SYuis8CCkl8JuxtIAGmwIwIWdD.PyFkJ6sASHYLd5
Received: from [74.73.17.74] by web52102.mail.re2.yahoo.com via HTTP;
	Sat, 11 Oct 2008 15:10:48 PDT
X-Mailer: YahooMailWebService/0.7.218.2
Date: Sat, 11 Oct 2008 15:10:48 -0700 (PDT)
From: Ammar <ammar83_h@yahoo.com>
To: sip@ietf.org
MIME-Version: 1.0
Message-ID: <733948.45397.qm@web52102.mail.re2.yahoo.com>
Subject: [Sip] Conference policy and media policy
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ammar83_h@yahoo.com
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0519652760=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

--===============0519652760==
Content-Type: multipart/alternative; boundary="0-1812733133-1223763048=:45397"

--0-1812733133-1223763048=:45397
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Is there a difference between a conference policy and a media policy?
=A0
Thanks,
Ammar=0A=0A=0A      
--0-1812733133-1223763048=:45397
Content-Type: text/html; charset=us-ascii

<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><DIV>Is there a difference between a conference policy and a media policy?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks,</DIV>
<DIV><SPAN>Ammar</SPAN></DIV></td></tr></table><br>

      
--0-1812733133-1223763048=:45397--

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

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


From sip-bounces@ietf.org  Sun Oct 12 05:56:30 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C90443A6915;
	Sun, 12 Oct 2008 05:56:30 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 009503A6915
	for <sip@core3.amsl.com>; Sun, 12 Oct 2008 05:56:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rsDZYpqXnwM8 for <sip@core3.amsl.com>;
	Sun, 12 Oct 2008 05:56:29 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id 295C13A685E
	for <sip@ietf.org>; Sun, 12 Oct 2008 05:56:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id DE4731EC30A;
	Sun, 12 Oct 2008 15:57:01 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id b9uGz7Nh4eEd; Sun, 12 Oct 2008 15:56:57 +0300 (EEST)
Received: from taimen (h153192.gprs.dnafinland.fi [87.93.153.192])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Sun, 12 Oct 2008 15:56:57 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id BE6F9AC053; Sun, 12 Oct 2008 15:56:53 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18673.62485.295631.933830@taimen.test.fi>
Date: Sun, 12 Oct 2008 15:56:53 +0300
To: "Dean Willis" <dean.willis@softarmor.com>
In-Reply-To: <2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18668.21733.520868.113675@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se>
	<18668.50247.121832.271341@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
	<18668.51383.505850.963592@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
	<18673.5665.337048.880648@taimen.test.fi>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Dean Willis writes:

 > There is a big difference between not preventing behavior and
 > requiring behavior.

looks like you try on purpose to misunderstand what i have required.  i
have never said that proxy is REQUIRED to fork.  it just must be
POSSIBLE for the proxy to fork even when outbound is in use.

so if i upgrade my current phone that registers both of its contacts to
outbound capability, it must still be possible for this phone to
register both contacts and proxy to fork incoming calls to both of them.

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


From sip-bounces@ietf.org  Sun Oct 12 11:04:11 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A88423A69CF;
	Sun, 12 Oct 2008 11:04:11 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 79A433A69CF
	for <sip@core3.amsl.com>; Sun, 12 Oct 2008 11:04:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.208
X-Spam-Level: 
X-Spam-Status: No, score=-6.208 tagged_above=-999 required=5 tests=[AWL=0.041, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4D5ThpK0tKrw for <sip@core3.amsl.com>;
	Sun, 12 Oct 2008 11:04:09 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 7BD173A68F8
	for <sip@ietf.org>; Sun, 12 Oct 2008 11:04:09 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	B9EBF20229; Sun, 12 Oct 2008 20:04:42 +0200 (CEST)
X-AuditID: c1b4fb3e-a6680bb000007a96-c0-48f23c3aa53f
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	9D86D20077; Sun, 12 Oct 2008 20:04:42 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 12 Oct 2008 20:04:41 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 12 Oct 2008 20:04:20 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCF83@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AcksagWaIH/yUxC/QjKOE1ySP2puLAAKeY9/
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18668.21733.520868.113675@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se><18668.50247.121832.271341@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se><18668.51383.505850.963592@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se><18672.19846.621765.332209@taimen.test.fi><2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com><18673.5665.337048.880648@taimen.test.fi><2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>, "Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 12 Oct 2008 18:04:41.0931 (UTC)
	FILETIME=[000C11B0:01C92C95]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi Juha,

>>There is a big difference between not preventing behavior and requiring behavior.
>
>looks like you try on purpose to misunderstand what i have required.  i
>have never said that proxy is REQUIRED to fork.  it just must be
>POSSIBLE for the proxy to fork even when outbound is in use.
>
>so if i upgrade my current phone that registers both of its contacts to
>outbound capability, it must still be possible for this phone to
>register both contacts and proxy to fork incoming calls to both of them.

I think you once did say that forking shall be required, because otherwise the UA can't be sure that the proxy actually will fork. But, maybe I missunderstood.

So, eventhough my personal opinion is that parallel forking shouldn't occur for Outbound, I don't think it is prohibited. The outbound spec doesn't say much about how specific flows are chosen.

Regards,

Christer





-- juha

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


From sip-bounces@ietf.org  Sun Oct 12 11:07:58 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 791E23A6A01;
	Sun, 12 Oct 2008 11:07:58 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8464E3A69DE
	for <sip@core3.amsl.com>; Sun, 12 Oct 2008 11:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FQPtwaDMuPh0 for <sip@core3.amsl.com>;
	Sun, 12 Oct 2008 11:07:56 -0700 (PDT)
Received: from sov.voip.co.uk (smtp.sov.voip.co.uk [80.249.108.49])
	by core3.amsl.com (Postfix) with ESMTP id C9D863A69D9
	for <sip@ietf.org>; Sun, 12 Oct 2008 11:07:56 -0700 (PDT)
Message-ID: <48F23D27.8030305@voip.co.uk>
Date: Sun, 12 Oct 2008 19:08:39 +0100
From: Michael Procter <michael@voip.co.uk>
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>
Cc: sip@ietf.org, Francois Audet <audet@nortel.com>
Subject: Re: [Sip] Is GRUU generated in the case of registration
 with	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg wrote:
> So, the following applies:
>
>
> request                                        response
> -------------------------------------------------------
>
> instance-id AND Supported:gruu               = gruu
> instance-id AND reg-id                       = outbound
> instance-id AND reg-id AND Supported:gruu    = outbound AND gruu
> instance-id                                  = n/a
>
> Correct?
>
> Regards,
>
> Christer
>   
GRUU is a little more subtle than that.  If a UA provides an instance-id
to a GRUU-supporting registrar, then the registrar will create a GRUU
for that UA, whether it indicates support or not.

If it indicates support ('Supported: gruu') then it will receive the
GRUU in the 200 response to the REGISTER.  If it doesn't indicate
support, then it won't receive the GRUU.  See section 5.2 of the GRUU
draft for more details.

Note that the GRUU is still created for non-GRUU UAs, and that the GRUU
can be discovered by other devices using (for example)
draft-ietf-sipping-gruu-reg-event.

Regards,

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


From sip-bounces@ietf.org  Sun Oct 12 11:09:10 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 373F63A69ED;
	Sun, 12 Oct 2008 11:09:10 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9A7363A69ED
	for <sip@core3.amsl.com>; Sun, 12 Oct 2008 11:09:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id laGL-zCNA7qb for <sip@core3.amsl.com>;
	Sun, 12 Oct 2008 11:09:09 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id BA1E33A69DE
	for <sip@ietf.org>; Sun, 12 Oct 2008 11:09:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 784EF1EC30A;
	Sun, 12 Oct 2008 21:09:59 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id qnoZUMdOjMnI; Sun, 12 Oct 2008 21:09:57 +0300 (EEST)
Received: from taimen (h153192.gprs.dnafinland.fi [87.93.153.192])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Sun, 12 Oct 2008 21:09:57 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id B9724AC054; Sun, 12 Oct 2008 21:09:54 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18674.15730.594467.257803@taimen.test.fi>
Date: Sun, 12 Oct 2008 21:09:54 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF083CCF83@esealmw113.eemea.ericsson.se>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18668.21733.520868.113675@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se>
	<18668.50247.121832.271341@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
	<18668.51383.505850.963592@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
	<18673.5665.337048.880648@taimen.test.fi>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF83@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

  > So, eventhough my personal opinion is that parallel forking
  > shouldn't occur for Outbound, I don't think it is prohibited. The
  > outbound spec doesn't say much about how specific flows are chosen.

did you read the paragraph that i quoted?  to me it clearly makes
forking impossible when outbound is used.

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


From sip-bounces@ietf.org  Sun Oct 12 11:11:11 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0B80A3A6A09;
	Sun, 12 Oct 2008 11:11:11 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 229943A69DE
	for <sip@core3.amsl.com>; Sun, 12 Oct 2008 11:11:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.209
X-Spam-Level: 
X-Spam-Status: No, score=-6.209 tagged_above=-999 required=5 tests=[AWL=0.040, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YmDl0Y6u0V0U for <sip@core3.amsl.com>;
	Sun, 12 Oct 2008 11:11:08 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id EDD1A3A6A06
	for <sip@ietf.org>; Sun, 12 Oct 2008 11:11:07 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	A2F91205EC; Sun, 12 Oct 2008 20:11:57 +0200 (CEST)
X-AuditID: c1b4fb3c-b00d2bb0000015b5-e1-48f23ded472a
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	8385020023; Sun, 12 Oct 2008 20:11:57 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 12 Oct 2008 20:11:49 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 12 Oct 2008 20:11:48 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCF84@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackrbie0dgmUYEKfSvafJ9RixsKA/QBJu+/w
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se><18665.59
	269.640606.477292@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se><48EBC88B.2030300@cisco.com><46101DEA-677B-4F28-AD1E-32F64385853
	5@s
	ofta	rmor.com><CA	9998CD4A020D418654FCDEF4E707DF05C0F8B8@esealmw113.eemea.ericsson.se><18668.21733.520868.113675@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se><48ECBA45.1070109@c
	is co.com
	><CA9998CD4A020D418654FCDEF4E707DF05C0F8C6@esealmw113.eemea.ericsson.se><18668.50247.121832.271341@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se><18668.51383.505850.963592@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 12 Oct 2008 18:11:49.0152 (UTC)
	FILETIME=[FEB0D200:01C92C95]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi,

>>The only new thing is that the USER may use different contacts for
>>different flows. BUT, it is still the same USER, and that USER should
>>still register at least two register flows - either all flows from the
>>same contact, or from different contacts.
>> 
>>As far as I know, you have never before requested that the registrar,
>>for incoming requests, shall perform paralell forking on all registered
>>flows.
>
>it is not SHALL, but it MUST BE POSSIBLE to do if the user wants that to
>happen.
>
>in my example the same UA instance registers AoR sip:jh@tutpro.com over
>its gprs and 3g interfaces with different contact addresses (one from
>ggsn and the other one from lan).
>
>first, like today without outbound, it must be possible with outbound
>that incoming call to sip:jh@tutpro.com gets parallel forked to the two
>contacts of this UA instance.  now i tried to figure out what ob draft
>says about it and found this:
>
>7. Authoritative Proxy Procedures: Forwarding Requests
>
>   When a proxy uses the location service to look up a registration
>   binding and then proxies a request to a particular contact, it
>   selects a contact to use normally, with a few additional rules:
>
>   o  The proxy MUST NOT populate the target set with more than one
>      contact with the same AOR and instance-id at a time.
>
>to me this clearly means that parallel forking is not anymore possible
>when UA implements outbound,

Ok, I admit I forgot about that text.

>which would be a VERY SEVERE restriction and change of RFC3261 behavior.
>
>second, if the UA instance may choose to register one of its two
>contacts via ob proxy 1 and the other via ob proxy 2, it makes
>simple implementation of redundancy with two proxy/registrar pairs
>impossible.

So, does the outbound spec forbid registering each contact via two proxies? Or, do you want to mandate THAT?

Regards,

Christer


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


From sip-bounces@ietf.org  Sun Oct 12 11:33:53 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0F1E43A69C7;
	Sun, 12 Oct 2008 11:33:53 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF4713A69C7
	for <sip@core3.amsl.com>; Sun, 12 Oct 2008 11:33:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.91
X-Spam-Level: 
X-Spam-Status: No, score=-5.91 tagged_above=-999 required=5 tests=[AWL=-0.261, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_74=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KvM73tOZ9JIO for <sip@core3.amsl.com>;
	Sun, 12 Oct 2008 11:33:51 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id ADE903A68DF
	for <sip@ietf.org>; Sun, 12 Oct 2008 11:33:50 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	1151B200D3; Sun, 12 Oct 2008 20:33:45 +0200 (CEST)
X-AuditID: c1b4fb3e-a8684bb000007a96-2f-48f24308e4b3
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	E93A220070; Sun, 12 Oct 2008 20:33:44 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 12 Oct 2008 20:33:44 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 12 Oct 2008 20:33:44 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Is GRUU generated in the case of registration
	with	instance-ID and reg-ID
Thread-Index: AckslY6W7xpUzX8LQGKsjL6Z4QduVgAAMyWk
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>
	<48F23D27.8030305@voip.co.uk>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Michael Procter" <michael@voip.co.uk>
X-OriginalArrivalTime: 12 Oct 2008 18:33:44.0798 (UTC)
	FILETIME=[0EE077E0:01C92C99]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, Francois Audet <audet@nortel.com>
Subject: Re: [Sip] Is GRUU generated in the case of registration
	with	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi,

>> So, the following applies:
>>
>>
>> request                                        response
>> -------------------------------------------------------
>>
>> instance-id AND Supported:gruu               = gruu
>> instance-id AND reg-id                       = outbound
>> instance-id AND reg-id AND Supported:gruu    = outbound AND gruu
>> instance-id                                  = n/a
>>
>>Correct?
>GRUU is a little more subtle than that.  If a UA provides an instance-id
>to a GRUU-supporting registrar, then the registrar will create a GRUU
>for that UA, whether it indicates support or not.

Then the question is: if I only want to use outbound, is it always ok that the registrar creates a GRUU for me (no matter whether it returns it or not)?

>If it indicates support ('Supported: gruu') then it will receive the
>GRUU in the 200 response to the REGISTER.  If it doesn't indicate
>support, then it won't receive the GRUU.  See section 5.2 of the GRUU
>draft for more details.

Then the text in 5.1, about the Require header is a little confusing. It says that Require:gruu will NOT require the registrar to even generate a gruu - only that the registrar is required to support gruu.

OR, does the text refer to the case when the request ONLY contains Require:gruu, but no instance-id?

"A REGISTER request might contain a Require header field with the
"gruu" option tag; this indicates that the registrar has to
understand this extension in order to process the request.  It does
not require the registrar to create GRUUs, however."

>Note that the GRUU is still created for non-GRUU UAs, and that the GRUU
>can be discovered by other devices using (for example)
>draft-ietf-sipping-gruu-reg-event.

Maybe it would be good to clarify, in the outbound spec, that a gruu will be generated if the registrar supports gruu. Because, at least in 3GPP there has been some confusion about that, and I believe such clarification would prevent future interop problems.

Regards,

Christer 





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


From sip-bounces@ietf.org  Sun Oct 12 11:39:09 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AB7963A6A30;
	Sun, 12 Oct 2008 11:39:09 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 63F953A6A30
	for <sip@core3.amsl.com>; Sun, 12 Oct 2008 11:39:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nkBHziQMNmVO for <sip@core3.amsl.com>;
	Sun, 12 Oct 2008 11:39:07 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id 7DC543A69BA
	for <sip@ietf.org>; Sun, 12 Oct 2008 11:39:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id ACBC41EC30A;
	Sun, 12 Oct 2008 21:33:05 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id feEumUcElkcA; Sun, 12 Oct 2008 21:33:03 +0300 (EEST)
Received: from taimen (h153192.gprs.dnafinland.fi [87.93.153.192])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Sun, 12 Oct 2008 21:33:03 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 60911AC054; Sun, 12 Oct 2008 21:33:01 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18674.17117.366109.178620@taimen.test.fi>
Date: Sun, 12 Oct 2008 21:33:01 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF083CCF84@esealmw113.eemea.ericsson.se>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>
	<18665.59 269.640606.477292@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
	<48EBC88B.2030300@cisco.com>
	<46101DEA-677B-4F28-AD1E-32F64385853 5@s ofta	rmor.com>
	<CA	9998CD4A020D418654FCDEF4E707DF05C0F8B8@esealmw113.eemea.ericsson.se>
	<18668.21733.520868.113675@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se>
	<48ECBA45.1070109@c is co.com >
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C6@esealmw113.eemea.ericsson.se>
	<18668.50247.121832.271341@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
	<18668.51383.505850.963592@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF84@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > >second, if the UA instance may choose to register one of its two
 > >contacts via ob proxy 1 and the other via ob proxy 2, it makes
 > >simple implementation of redundancy with two proxy/registrar pairs
 > >impossible.
 > 
 > So, does the outbound spec forbid registering each contact via two
 > proxies? Or, do you want to mandate THAT?

i have told this already at least three times:

if it is not mandated that UA has to register all its contacts via at
least two ob proxies (if set has two or more), then simple
implementation of redundancy becomes impossible.  

also, reliability will necessarily suffer also in complex implementation
when one of the contacts would not be available via more than one proxy.

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


From sip-bounces@ietf.org  Sun Oct 12 11:40:46 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 564133A69D6;
	Sun, 12 Oct 2008 11:40:46 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9CE8D3A6A21
	for <sip@core3.amsl.com>; Sun, 12 Oct 2008 11:40:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.205
X-Spam-Level: 
X-Spam-Status: No, score=-6.205 tagged_above=-999 required=5 tests=[AWL=0.044, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2dYw07WFkS9B for <sip@core3.amsl.com>;
	Sun, 12 Oct 2008 11:40:43 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 9D3AB3A69D6
	for <sip@ietf.org>; Sun, 12 Oct 2008 11:40:43 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	6AF1B20347; Sun, 12 Oct 2008 20:41:20 +0200 (CEST)
X-AuditID: c1b4fb3e-a9686bb000007a96-e3-48f244d0deea
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	475E82019F; Sun, 12 Oct 2008 20:41:20 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 12 Oct 2008 20:41:20 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 12 Oct 2008 20:41:19 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCF86@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AcksmPgW1PEtj3UKRNmQSSiydp3fmAAADzPu
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se><18665.59
	269.640606.477292@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se><48EBC88B.2030300@cisco.com><46101DEA-677B-4F28-AD1E-32F64385853
	5@s
	ofta	rmor.com><CA	9998CD4A020D418654FCDEF4E707DF05C0F8B8@esealmw113.eemea.ericsson.se><18668.21733.520868.113675@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se><48ECBA45.1070109@c
	is co.co
	m><CA9998CD4A020D418654FCDEF4E707DF05C0F8C6@esealmw113.eemea.ericsson.se><18668.50247.121832.271341@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se><18668.51383.505850.963592@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se><18672.19846.621765.332209@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF083CCF84@esealmw113.eemea.ericsson.se>
	<18674.17117.366109.178620@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 12 Oct 2008 18:41:20.0117 (UTC)
	FILETIME=[1E44A250:01C92C9A]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi,

>>>second, if the UA instance may choose to register one of its two
>>>contacts via ob proxy 1 and the other via ob proxy 2, it makes
>>>simple implementation of redundancy with two proxy/registrar pairs
>>>impossible.
>> 
>>So, does the outbound spec forbid registering each contact via two
>>proxies? Or, do you want to mandate THAT?
>
>i have told this already at least three times:
>
>if it is not mandated that UA has to register all its contacts via at
>least two ob proxies (if set has two or more), then simple
>implementation of redundancy becomes impossible.  

The problem is that there are also cases where the ob proxies and registrars ARE separated, and what you propose may not be needed in such scenarios.

Why don't you simply configure your UA to register each contact with multiple ob/registrar proxies?

>also, reliability will necessarily suffer also in complex implementation
>when one of the contacts would not be available via more than one proxy.

If both contacts are "equal" I don't think that will be a problem. There will be two ways to reach the UA, as if a single contact was used.

Regards,

Christer



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


From sip-bounces@ietf.org  Sun Oct 12 12:10:41 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C79773A6934;
	Sun, 12 Oct 2008 12:10:41 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3B0283A6934
	for <sip@core3.amsl.com>; Sun, 12 Oct 2008 12:10:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WRw0WBcA9YAu for <sip@core3.amsl.com>;
	Sun, 12 Oct 2008 12:10:39 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id 1558F3A6941
	for <sip@ietf.org>; Sun, 12 Oct 2008 12:10:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 7C37F1EC30A;
	Sun, 12 Oct 2008 22:11:23 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id u2mrtGGUtXwg; Sun, 12 Oct 2008 22:11:21 +0300 (EEST)
Received: from taimen (h153192.gprs.dnafinland.fi [87.93.153.192])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Sun, 12 Oct 2008 22:11:21 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 9DEC4AC054; Sun, 12 Oct 2008 22:11:17 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18674.19413.615923.866164@taimen.test.fi>
Date: Sun, 12 Oct 2008 22:11:17 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF083CCF86@esealmw113.eemea.ericsson.se>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>
	<18665.59 269.640606.477292@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
	<48EBC88B.2030300@cisco.com>
	<46101DEA-677B-4F28-AD1E-32F64385853 5@s ofta	rmor.com>
	<CA	9998CD4A020D418654FCDEF4E707DF05C0F8B8@esealmw113.eemea.ericsson.se>
	<18668.21733.520868.113675@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se>
	<48ECBA45.1070109@c is co.co m>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C6@esealmw113.eemea.ericsson.se>
	<18668.50247.121832.271341@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
	<18668.51383.505850.963592@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF84@esealmw113.eemea.ericsson.se>
	<18674.17117.366109.178620@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF86@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > The problem is that there are also cases where the ob proxies and
 > registrars ARE separated, and what you propose may not be needed in
 > such scenarios.

i know that and i hoped that outbound would make a simple, redundant
implementation possible.  it was very close, when it was accepted that
at least two ob proxies must be used.  now this multiple contact thing
killed it.

 > Why don't you simply configure your UA to register each contact with
 > multiple ob/registrar proxies?

the problem is that many UAs don't support that kind of configuration,
because there has been no rfc that would mandate them to do so.  i was
hoping that ob would do it.

 > >also, reliability will necessarily suffer also in complex implementation
 > >when one of the contacts would not be available via more than one proxy.
 > 
 > If both contacts are "equal" I don't think that will be a
 > problem. There will be two ways to reach the UA, as if a single
 > contact was used.

they are NOT equal and you cannot assume it.  for example, gprs
connectivity might be much more reliable than wlan connectivity or vice
versa.  

but this is all theory anyhow, because ob draft is badly broken, because
it does not support forking at all and thus is in grave conflict
with rfc3261.

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


From sip-bounces@ietf.org  Mon Oct 13 00:43:46 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D778B3A6B89;
	Mon, 13 Oct 2008 00:43:46 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 45F513A6B89
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 00:43:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_74=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3Lk4E8+0i9eK for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 00:43:45 -0700 (PDT)
Received: from sov.voip.co.uk (smtp.sov.voip.co.uk [80.249.108.49])
	by core3.amsl.com (Postfix) with ESMTP id 4885F3A6B88
	for <sip@ietf.org>; Mon, 13 Oct 2008 00:43:44 -0700 (PDT)
Message-ID: <48F2FC13.1070308@voip.co.uk>
Date: Mon, 13 Oct 2008 08:43:15 +0100
From: Michael Procter <michael@voip.co.uk>
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>
	<48F23D27.8030305@voip.co.uk>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se>
Cc: sip@ietf.org, Francois Audet <audet@nortel.com>
Subject: Re: [Sip] Is GRUU generated in the case of registration with
 instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg wrote:
> Hi,
>
>   
>> GRUU is a little more subtle than that.  If a UA provides an instance-id
>> to a GRUU-supporting registrar, then the registrar will create a GRUU
>> for that UA, whether it indicates support or not.
>>     
>
> Then the question is: if I only want to use outbound, is it always ok that the registrar creates a GRUU for me (no matter whether it returns it or not)?
>   

I raised much the same question last year (March/April time), and I
think the conclusion was that creating the GRUU doesn't cause problems
and should be considered a Good Thing.

> Then the text in 5.1, about the Require header is a little confusing. It says that Require:gruu will NOT require the registrar to even generate a gruu - only that the registrar is required to support gruu.
>
> OR, does the text refer to the case when the request ONLY contains Require:gruu, but no instance-id?
>
> "A REGISTER request might contain a Require header field with the
> "gruu" option tag; this indicates that the registrar has to
> understand this extension in order to process the request.  It does
> not require the registrar to create GRUUs, however."
>   

I think this is the normal Require processing.  Putting 'Require: gruu'
in your REGISTER will ensure that it will only succeed on a GRUU-aware
registrar.  It doesn't control or enforce any particular GRUU-related
processing, only that the registrar understands GRUU.  This behaviour
(requiring understanding, not invoking) is common for many but not all
SIP options.

> Maybe it would be good to clarify, in the outbound spec, that a gruu will be generated if the registrar supports gruu. Because, at least in 3GPP there has been some confusion about that, and I believe such clarification would prevent future interop problems.
>   

I'm certainly in favour of reducing ambiguity, where it exists, but I'm
not sure outbound is the place to talk about GRUUs.  How did the
confusion arise?  The GRUU spec seems reasonably clear on this point.

Regards,

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


From sip-bounces@ietf.org  Mon Oct 13 01:20:05 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 55BF33A6827;
	Mon, 13 Oct 2008 01:20:05 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 45A193A67AF
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 01:20:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Level: 
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[AWL=0.032, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id pj8m8+DzKDOT for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 01:20:02 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id 38E0E3A6827
	for <sip@ietf.org>; Mon, 13 Oct 2008 01:20:02 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K8O003B04H4F4@siemenscomms.co.uk> for sip@ietf.org; Mon,
	13 Oct 2008 09:19:52 +0100 (BST)
Date: Mon, 13 Oct 2008 09:19:50 +0100
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <18673.5665.337048.880648@taimen.test.fi>
To: Juha Heinanen <jh@tutpro.com>, Dean Willis <dean.willis@softarmor.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D0012A1A18@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackr5ckBfoNhknS4Riu/U3PFwFlJcgBJWzuw
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
	<48EBC88B.2030300@cisco.com> <18668.21733.520868.113675@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se>
	<18668.50247.121832.271341@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
	<18668.51383.505850.963592@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
	<18673.5665.337048.880648@taimen.test.fi>
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Juha Heinanen
> Sent: 11 October 2008 22:10
> To: Dean Willis
> Cc: sip@ietf.org; Paul Kyzivat; Christer Holmberg
> Subject: Re: [Sip] Dual registration without Outbound
> 
> Dean Willis writes:
> 
>  > Seems like what you are asking for is for a proxy to 
> require parallel
>  > forking to multiple contacts regsitered by a single UA. 
> 
> huh, i'm not asking anything beyond what is in rfc3261 and what is
> currently working fine in practise.  or can you point to text 
> in rfc3261
> that prohibits a single UA registering several contacts for a single
> AoR and that prohibits a proxy parallel forking to those contacts when
> the contacts share the same q value?
> 
>  > That is not
>  > only out of scope for outbound, it is also undesirable 
> behaivior (as
>  > in totally broken) for a great number of use cases. 
> 
> i didn't know that normal rfc3261 compliant behavior is 
> outside of scope
> of outbound.  was it listed in outbound requirements that outbound
> should obsolete forking that has been there from the very 
> beginning and
> that many applications rely on?  could you quote the requirements text
> on that?
> 
> also, what wrong or undesirable there is in the forking example that i
> have described in earlier messages?
>  
>  > Consequently, this
>  > means it would require a great deal of documentation around the use
>  > cases for which it makes sense. I do not think this can be done
>  > reasonably in the outbound draft.
> 
> outbound should not change current rfc3261 compliant forking behavior.
> it has to support it and if more text is needed, then it is outbound
> editors' problem.  forking is much more important than outbound
> especially when many UAs have already implemented things like 
> keepalives
> without outbound.
[JRE] Yes, indeed, retention of forking is very important. With RFC
3261, multiple UAs can register and incoming requests will be forked to
them. With sip-outbound, this is still the case, provided these multiple
UAs choose different instance IDs. This still holds true if two UAs are
implemented in the same device, e.g., in your example, a dual mode
device would have a GPRS UA with one instance ID and a WLAN UA with a
second instance ID. If each registers, calls will be forked to both. To
be sip-outbound compliant, of course, each has to register at least
twice, so you will have at least two registrations (flows) with one
instance ID, and at least two registrations (flows) with the second
instance ID. An incoming request would be forked, such that it arrives
at the device twice (and only twice), once following one of the flows
for the first instance ID (GPRS) and once following one of the flows for
the second instance ID (WLAN).

Perhaps we need some informative text to describe this particular use
case.

John


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


From sip-bounces@ietf.org  Mon Oct 13 03:08:04 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2B57E3A6B7E;
	Mon, 13 Oct 2008 03:08:04 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3E4203A6B7E
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 03:08:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id khXCOiAoNMsn for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 03:08:02 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id 142643A659B
	for <sip@ietf.org>; Mon, 13 Oct 2008 03:08:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 6D4BA1EC30A;
	Mon, 13 Oct 2008 13:08:09 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jmSzz2mvAVKU; Mon, 13 Oct 2008 13:08:06 +0300 (EEST)
Received: from taimen (h142044.gprs.dnafinland.fi [87.93.142.44])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Mon, 13 Oct 2008 13:08:06 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 40F2AAC054; Mon, 13 Oct 2008 13:08:04 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18675.7684.207071.901832@taimen.test.fi>
Date: Mon, 13 Oct 2008 13:08:04 +0300
To: "Dean Willis" <dean.willis@softarmor.com>
In-Reply-To: <2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18668.50247.121832.271341@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
	<18668.51383.505850.963592@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
	<18673.5665.337048.880648@taimen.test.fi>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Dean Willis writes:

 > Um, perhaps I missed something. What is that prevents a UA from
 > registering two different interfaces with discrete instance IDs and
 > having a forking proxy fork to both instances?

i don't think nothing prevents that, but in my example, there is only
one sip ua and one instance of it.  both contacts of this instance belong
to the same ua:

   Proxies can
   determine which flows go to the same UA by comparing the instance-id.

if my phone would have two instance-ids, according to the above, i would
have too UAs, which is not the case today and i don't want that to be
the case when/if i one day upgrade its software to support outbound rfc.

it is amazing how hard it is to you to admit that outbound i-d as
currently written is badly broken.

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


From sip-bounces@ietf.org  Mon Oct 13 03:12:40 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 045423A6857;
	Mon, 13 Oct 2008 03:12:40 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 721683A6857
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 03:12:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id uAT5KLUJb-hh for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 03:12:38 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id 7EBB73A6800
	for <sip@ietf.org>; Mon, 13 Oct 2008 03:12:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 68B6C1EC30A;
	Mon, 13 Oct 2008 13:12:16 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id dhskJvgjF3aj; Mon, 13 Oct 2008 13:12:14 +0300 (EEST)
Received: from taimen (h142044.gprs.dnafinland.fi [87.93.142.44])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Mon, 13 Oct 2008 13:12:14 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 81C26AC054; Mon, 13 Oct 2008 13:12:10 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18675.7930.503396.458785@taimen.test.fi>
Date: Mon, 13 Oct 2008 13:12:10 +0300
To: "Elwell, John" <john.elwell@siemens.com>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D0012A1A18@GBNTHT12009MSX.gb002.siemens.net>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>
	<48EBC88B.2030300@cisco.com>
	<18668.21733.520868.113675@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se>
	<18668.50247.121832.271341@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
	<18668.51383.505850.963592@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
	<18673.5665.337048.880648@taimen.test.fi>
	<0D5F89FAC29E2C41B98A6A762007F5D0012A1A18@GBNTHT12009MSX.gb002.siemens.net>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Elwell, John writes:

 > [JRE] Yes, indeed, retention of forking is very important. With RFC
 > 3261, multiple UAs can register and incoming requests will be forked to
 > them. With sip-outbound, this is still the case, provided these multiple
 > UAs choose different instance IDs. This still holds true if two UAs are
 > implemented in the same device, e.g., in your example, a dual mode
 > device would have a GPRS UA with one instance ID and a WLAN UA with a
 > second instance ID. 

see my previous email.  i don't want two UAs, but like today, only one
that has two contacts.

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


From sip-bounces@ietf.org  Mon Oct 13 06:33:57 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6805628C10E;
	Mon, 13 Oct 2008 06:33:57 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BABBE28C0F9
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 06:33:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.207
X-Spam-Level: 
X-Spam-Status: No, score=-6.207 tagged_above=-999 required=5
	tests=[AWL=-0.208, BAYES_00=-2.599, J_CHICKENPOX_74=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WQE4DJc8nyIc for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 06:33:54 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 8F97328C10E
	for <sip@ietf.org>; Mon, 13 Oct 2008 06:33:54 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,403,1220227200"; d="scan'208";a="24042178"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 13 Oct 2008 13:33:48 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9DDXmgi010970; 
	Mon, 13 Oct 2008 09:33:48 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9DDXmp6002672;
	Mon, 13 Oct 2008 13:33:48 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 09:33:48 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 09:33:47 -0400
Message-ID: <48F34E3B.80106@cisco.com>
Date: Mon, 13 Oct 2008 09:33:47 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Michael Procter <michael@voip.co.uk>
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>	<48F23D27.8030305@voip.co.uk>	<CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se>
	<48F2FC13.1070308@voip.co.uk>
In-Reply-To: <48F2FC13.1070308@voip.co.uk>
X-OriginalArrivalTime: 13 Oct 2008 13:33:47.0683 (UTC)
	FILETIME=[522C6730:01C92D38]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2929; t=1223904828;
	x=1224768828; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Is=20GRUU=20generated=20in=20th
	e=20case=20of=20registration=20with=20instance-ID=0A=20and=2
	0reg-ID |Sender:=20
	|To:=20Michael=20Procter=20<michael@voip.co.uk>;
	bh=H381Na/LOkQSQ17aJZKBpV+wdK/2TF10seyGchDbhcM=;
	b=g/IhfPcccg8nb46WnQpVSV1iRxrZeBI2FmhqLLBn0q6vYx9L8puHk0+qmZ
	ImhQculm4BtUzdNf4jbRzwe8IGXMc0y8Ssx2S+yEAOTkxj2Cgl+Ei+ZcKENC
	UTv6E1gagQ;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: sip@ietf.org, Francois Audet <audet@nortel.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Is GRUU generated in the case of registration with
 instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Its been a long time, and the details are starting to get fuzzy in my 
mind. But I'm quite sure Michael is right here. The first registration 
with an instance id causes the creation of a permanent gruu, and every 
registration with an instance id results in creation of a temp gruu. 
This is regardless of whether the registering UA indicates support for 
gruu. If it does, then it receives a copy of the gruu in the response.

	Thanks,
	Paul

Michael Procter wrote:
> Christer Holmberg wrote:
>> Hi,
>>
>>   
>>> GRUU is a little more subtle than that.  If a UA provides an instance-id
>>> to a GRUU-supporting registrar, then the registrar will create a GRUU
>>> for that UA, whether it indicates support or not.
>>>     
>> Then the question is: if I only want to use outbound, is it always ok that the registrar creates a GRUU for me (no matter whether it returns it or not)?
>>   
> 
> I raised much the same question last year (March/April time), and I
> think the conclusion was that creating the GRUU doesn't cause problems
> and should be considered a Good Thing.
> 
>> Then the text in 5.1, about the Require header is a little confusing. It says that Require:gruu will NOT require the registrar to even generate a gruu - only that the registrar is required to support gruu.
>>
>> OR, does the text refer to the case when the request ONLY contains Require:gruu, but no instance-id?
>>
>> "A REGISTER request might contain a Require header field with the
>> "gruu" option tag; this indicates that the registrar has to
>> understand this extension in order to process the request.  It does
>> not require the registrar to create GRUUs, however."
>>   
> 
> I think this is the normal Require processing.  Putting 'Require: gruu'
> in your REGISTER will ensure that it will only succeed on a GRUU-aware
> registrar.  It doesn't control or enforce any particular GRUU-related
> processing, only that the registrar understands GRUU.  This behaviour
> (requiring understanding, not invoking) is common for many but not all
> SIP options.
> 
>> Maybe it would be good to clarify, in the outbound spec, that a gruu will be generated if the registrar supports gruu. Because, at least in 3GPP there has been some confusion about that, and I believe such clarification would prevent future interop problems.
>>   
> 
> I'm certainly in favour of reducing ambiguity, where it exists, but I'm
> not sure outbound is the place to talk about GRUUs.  How did the
> confusion arise?  The GRUU spec seems reasonably clear on this point.
> 
> Regards,
> 
> Michael
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct 13 09:11:17 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C14353A6AD1;
	Mon, 13 Oct 2008 09:11:17 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E015A3A68BA
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 09:11:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6oZLs2nCDhyL for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 09:11:13 -0700 (PDT)
Received: from zrtps0kn.nortel.com (zrtps0kn.nortel.com [47.140.192.55])
	by core3.amsl.com (Postfix) with ESMTP id D31593A6358
	for <sip@ietf.org>; Mon, 13 Oct 2008 09:11:12 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m9DGC2415311; Mon, 13 Oct 2008 16:12:02 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 13 Oct 2008 11:11:22 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF19B6B81F@zrc2hxm0.corp.nortel.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
Thread-Index: AckrLZH1Tdf2a3GNSVKvr0LtBeKQ8QADaJLgAASHPY4AgDHDoA==
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>
	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>
From: "Francois Audet" <audet@nortel.com>
To: "Christer Holmberg" <christer.holmberg@ericsson.com>, <sip@ietf.org>
Subject: Re: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Just to make sure I understand, what does your "response column" mean?
Are you talking about the Require option-tag?

> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] =

> Sent: Friday, October 10, 2008 20:21
> To: Audet, Francois (SC100:3055); sip@ietf.org
> Cc: georg.mayer@nokia.com
> Subject: VS: [Sip] Is GRUU generated in the case of =

> registration with instance-ID and reg-ID
> =

> =

> So, the following applies:
> =

> =

> request                                        response
> -------------------------------------------------------
> =

> instance-id AND Supported:gruu               =3D gruu
> instance-id AND reg-id                       =3D outbound
> instance-id AND reg-id AND Supported:gruu    =3D outbound AND gruu
> instance-id                                  =3D n/a
> =

> Correct?
> =

> Regards,
> =

> Christer
> =

> =

> =

> =

> -----Alkuper=E4inen viesti-----
> L=E4hett=E4j=E4: Francois Audet [mailto:audet@nortel.com]
> L=E4hetetty: la 11.10.2008 2:49
> Vastaanottaja: Christer Holmberg; sip@ietf.org
> Kopio: georg.mayer@nokia.com
> Aihe: RE: [Sip] Is GRUU generated in the case of registration =

> with instance-ID and reg-ID
>  =

> I think that's in the GRUU spec.
> =

> =

> ________________________________
> =

> 	From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] =

> 	Sent: Friday, October 10, 2008 16:12
> 	To: sip@ietf.org
> 	Cc: Audet, Francois (SC100:3055); georg.mayer@nokia.com
> 	Subject: [Sip] Is GRUU generated in the case of =

> registration with instance-ID and reg-ID
> 	=

> 	=

> =

> =

> 	Hi Francoise, =

> =

> 	So, how would the registrar know whether a GRUU is =

> requested or not in the case described by Georg? Based on =

> whether the gruu option-tag is present?
> =

> 	It would be good to clarify this in the outbound spec. =

> =

> 	Regards, =

> =

> 	Christer =

> =

> =

> =

> 	>>I think you are correct. =

> 	>> =

> 	>>It doesn't mean we couldn't re-use reg-id for other =

> purposes however. =

> =

> 	>Hello, =

> 	> =

> 	>Both Outbound and GRUU drafts make use of the =

> instance-ID for different purposes during SIP registration. =

> In GRUU only the instance-ID is needed to generate a GRUU. =

> >For Outbound both, instance-ID and reg-ID are needed.
> =

> 	> =

> 	>My question now is, whether a GRUU will be generated =

> when a REGISTER is received at the registrar, which indicates =

> both reg-ID and instance-ID in the Contact =

> =

> 	>header. Reading outbound, it seems like instance-ID + =

> reg-ID are *only* used for outbound purposes. =

> 	> =

> 	>Thanks a lot for your help. =

> 	> =

> 	>Best regards =

> 	>Georg =

> =

> =

> =

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


From sip-bounces@ietf.org  Mon Oct 13 09:11:51 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8500E3A693D;
	Mon, 13 Oct 2008 09:11:51 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 71CBF28C140
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 09:11:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id JAcsiGJBHPr6 for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 09:11:49 -0700 (PDT)
Received: from zcars04f.nortel.com (zcars04f.nortel.com [47.129.242.57])
	by core3.amsl.com (Postfix) with ESMTP id 6B70828C128
	for <sip@ietf.org>; Mon, 13 Oct 2008 09:11:49 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m9DGCV129616; Mon, 13 Oct 2008 16:12:31 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 13 Oct 2008 11:12:29 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF19B6B825@zrc2hxm0.corp.nortel.com>
In-Reply-To: <18672.18754.189767.996087@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackra6RWp2qrfHqZSFO+QO/TbLJa2gB4r71w
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<7A726F54F791494C8D8C87F13736E80EEC21DA@vaebe106.NOE.Nokia.com>
	<18665.42838.994529.377867@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88B@esealmw113.eemea.ericsson.se>
	<18665.43684.176244.988653@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se>
	<18665.45965.827982.821183@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se>
	<18665.47207.397605.244480@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se>
	<18665.48080.859460.802945@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se>
	<18665.49637.47890.122973@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se>
	<18665.51736.268071.502700@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eem! ! ! !	! e
	a.	er icsson .se	>	<	18665.59269.640606.477292@taimen.test.fi>
	<CDA30DAD-DE21-4A5D-BF67-9A49DF32B4EA@softarmor.com>
	<18666.16422.211242.766454@taimen.test.fi>
	<ADB2E3A0-DAF6-432B-B269-A10E9D38E6EA@softarmor.com>
	<18666.20359.413310.214443@taimen.test.fi>
	<1ECE0EB50388174790F9694F77522CCF19B03514@zrc2hxm0.corp.nortel.com>
	<18671.44909.216290.711492@taimen.test.fi>
	<1ECE0EB50388174790F9694F77522CCF19B0377A@zrc2hxm0.corp.nortel.com>
	<18672.18754.189767.996087@taimen.test.fi>
From: "Francois Audet" <audet@nortel.com>
To: "Juha Heinanen" <jh@tutpro.com>
Cc: sip@ietf.org, Christer Holmberg <christer.holmberg@ericsson.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

It would be a "high-availability" draft.

If we are lucky, maybe there is no impact on the UA (but I doubt it). 

> -----Original Message-----
> From: Juha Heinanen [mailto:jh@tutpro.com] 
> Sent: Friday, October 10, 2008 23:36
> To: Audet, Francois (SC100:3055)
> Cc: Dean Willis; sip@ietf.org; Christer Holmberg
> Subject: RE: [Sip] Dual registration without Outbound
> 
> Francois Audet writes:
> 
>  > Nobody is talking about a "second version" of outbound.
> 
> it would be "second" version, because it would need to add to 
> UA's outbound behavior compared to ob rfc.
> 
> -- juha
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct 13 10:46:11 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0DC5328C0FC;
	Mon, 13 Oct 2008 10:46:11 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DEA4028C118
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 10:46:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 04RSv75qIMov for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 10:46:09 -0700 (PDT)
Received: from zrtps0kn.nortel.com (zrtps0kn.nortel.com [47.140.192.55])
	by core3.amsl.com (Postfix) with ESMTP id DFDD03A67D4
	for <sip@ietf.org>; Mon, 13 Oct 2008 10:46:08 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m9DHk2423086; Mon, 13 Oct 2008 17:46:02 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 13 Oct 2008 12:45:44 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF19B6BAC6@zrc2hxm0.corp.nortel.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F8C9@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Outbound: keep-alives on dialog flows
Thread-Index: AckpWPlJ7iefydswRVaN7SAqinZOwAEAjN4A
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8C9@esealmw113.eemea.ericsson.se>
From: "Francois Audet" <audet@nortel.com>
To: "Christer Holmberg" <christer.holmberg@ericsson.com>, <sip@ietf.org>
Subject: Re: [Sip] Outbound: keep-alives on dialog flows
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2108892923=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2108892923==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C92D5B.8497F16C"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C92D5B.8497F16C
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

It can. Section 4.4., second and third paragraph.
=20
But it basically says that you need an explicit indication. I believe =
that the intent of this wording was to allow for sip-keep draft.
=20
In other words, I believe it says that the non-register case can only =
use keep-alive if there is an explicit mechanism (e.g., sip-keep).


________________________________

	From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]=20
	Sent: Wednesday, October 08, 2008 08:17
	To: sip@ietf.org
	Cc: Audet, Francois (SC100:3055)
	Subject: Outbound: keep-alives on dialog flows
=09
=09


	Hi,=20

	As I asked in another e-mail, are keep-alives sent on dialog initated =
Outbound flows?=20

	I need to know, because in that case the non-registration use-case can =
be removed from the sip-keep draft.=20

	Regards,=20

	Christer=20


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Outbound: keep-alives on dialog flows</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3395" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D330174317-13102008><FONT =
face=3DArial=20
color=3D#800000 size=3D2>It can. Section 4.4., second and third=20
paragraph.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D330174317-13102008><FONT =
face=3DArial=20
color=3D#800000 size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D330174317-13102008><FONT =
face=3DArial=20
color=3D#800000 size=3D2>But it basically says that you need an explicit =
indication.=20
I believe that the intent of this wording was to allow for sip-keep=20
draft.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D330174317-13102008><FONT =
face=3DArial=20
color=3D#800000 size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D330174317-13102008><FONT =
face=3DArial=20
color=3D#800000 size=3D2>In other words, I believe it says that the =
non-register=20
case can only use keep-alive if there is an explicit mechanism (e.g.,=20
sip-keep).</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #800000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Christer Holmberg=20
  [mailto:christer.holmberg@ericsson.com] <BR><B>Sent:</B> Wednesday, =
October=20
  08, 2008 08:17<BR><B>To:</B> sip@ietf.org<BR><B>Cc:</B> Audet, =
Francois=20
  (SC100:3055)<BR><B>Subject:</B> Outbound: keep-alives on dialog=20
  flows<BR></FONT><BR></DIV>
  <DIV></DIV><!-- Converted from text/rtf format --><BR>
  <P><FONT face=3DArial size=3D2>Hi,</FONT> </P>
  <P><FONT face=3DArial size=3D2>As I asked in another e-mail, are =
keep-alives sent=20
  on dialog initated Outbound flows?</FONT> </P>
  <P><FONT face=3DArial size=3D2>I need to know, because in that case =
the=20
  non-registration use-case can be removed from the sip-keep =
draft.</FONT> </P>
  <P><FONT face=3DArial size=3D2>Regards,</FONT> </P>
  <P><FONT face=3DArial size=3D2>Christer</FONT> =
</P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C92D5B.8497F16C--

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

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


From sip-bounces@ietf.org  Mon Oct 13 10:51:16 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A241628C118;
	Mon, 13 Oct 2008 10:51:16 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7EF893A6820
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 10:51:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.206
X-Spam-Level: 
X-Spam-Status: No, score=-6.206 tagged_above=-999 required=5 tests=[AWL=0.043, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ewdlRaBouNgx for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 10:51:13 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 2F4C33A67D4
	for <sip@ietf.org>; Mon, 13 Oct 2008 10:51:13 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	DFFA22011C; Mon, 13 Oct 2008 19:50:53 +0200 (CEST)
X-AuditID: c1b4fb3e-a8684bb000007a96-c0-48f38a7d61fb
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	BA616200C8; Mon, 13 Oct 2008 19:50:53 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 19:50:53 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 13 Oct 2008 19:50:51 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8EC@esealmw113.eemea.ericsson.se>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF19B6B81F@zrc2hxm0.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
Thread-Index: AckrLZH1Tdf2a3GNSVKvr0LtBeKQ8QADaJLgAASHPY4AgDHDoAADerLQ
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>
	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>
	<1ECE0EB50388174790F9694F77522CCF19B6B81F@zrc2hxm0.corp.nortel.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Francois Audet" <audet@nortel.com>,
	<sip@ietf.org>
X-OriginalArrivalTime: 13 Oct 2008 17:50:53.0283 (UTC)
	FILETIME=[3C8C2B30:01C92D5C]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, =


>Just to make sure I understand, what does your "response column" mean?
>Are you talking about the Require option-tag?

No, I am talking about the Supported option-tag.

But, I think the reply from Michael clarified, but now DO have a question r=
egarding the Require option-tag (see other mail).

Regards,

Christer

> =

> > -----Original Message-----
> > From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> > Sent: Friday, October 10, 2008 20:21
> > To: Audet, Francois (SC100:3055); sip@ietf.org
> > Cc: georg.mayer@nokia.com
> > Subject: VS: [Sip] Is GRUU generated in the case of =

> registration with =

> > instance-ID and reg-ID
> > =

> > =

> > So, the following applies:
> > =

> > =

> > request                                        response
> > -------------------------------------------------------
> > =

> > instance-id AND Supported:gruu               =3D gruu
> > instance-id AND reg-id                       =3D outbound
> > instance-id AND reg-id AND Supported:gruu    =3D outbound AND gruu
> > instance-id                                  =3D n/a
> > =

> > Correct?
> > =

> > Regards,
> > =

> > Christer
> > =

> > =

> > =

> > =

> > -----Alkuper=E4inen viesti-----
> > L=E4hett=E4j=E4: Francois Audet [mailto:audet@nortel.com]
> > L=E4hetetty: la 11.10.2008 2:49
> > Vastaanottaja: Christer Holmberg; sip@ietf.org
> > Kopio: georg.mayer@nokia.com
> > Aihe: RE: [Sip] Is GRUU generated in the case of registration with =

> > instance-ID and reg-ID
> >  =

> > I think that's in the GRUU spec.
> > =

> > =

> > ________________________________
> > =

> > 	From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] =

> > 	Sent: Friday, October 10, 2008 16:12
> > 	To: sip@ietf.org
> > 	Cc: Audet, Francois (SC100:3055); georg.mayer@nokia.com
> > 	Subject: [Sip] Is GRUU generated in the case of =

> registration with =

> > instance-ID and reg-ID
> > 	=

> > 	=

> > =

> > =

> > 	Hi Francoise,
> > =

> > 	So, how would the registrar know whether a GRUU is =

> requested or not =

> > in the case described by Georg? Based on whether the gruu =

> option-tag =

> > is present?
> > =

> > 	It would be good to clarify this in the outbound spec. =

> > =

> > 	Regards,
> > =

> > 	Christer
> > =

> > =

> > =

> > 	>>I think you are correct. =

> > 	>> =

> > 	>>It doesn't mean we couldn't re-use reg-id for other purposes =

> > however.
> > =

> > 	>Hello, =

> > 	> =

> > 	>Both Outbound and GRUU drafts make use of the instance-ID for =

> > different purposes during SIP registration.
> > In GRUU only the instance-ID is needed to generate a GRUU. =

> > >For Outbound both, instance-ID and reg-ID are needed.
> > =

> > 	> =

> > 	>My question now is, whether a GRUU will be generated =

> when a REGISTER =

> > is received at the registrar, which indicates both reg-ID and =

> > instance-ID in the Contact
> > =

> > 	>header. Reading outbound, it seems like instance-ID + =

> reg-ID are =

> > *only* used for outbound purposes.
> > 	> =

> > 	>Thanks a lot for your help. =

> > 	> =

> > 	>Best regards =

> > 	>Georg
> > =

> > =

> > =

> =

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


From sip-bounces@ietf.org  Mon Oct 13 12:01:59 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9C03128C126;
	Mon, 13 Oct 2008 12:01:59 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2055628C126
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 12:01:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.906
X-Spam-Level: 
X-Spam-Status: No, score=-5.906 tagged_above=-999 required=5
	tests=[AWL=-0.257, BAYES_00=-2.599, HELO_EQ_SE=0.35,
	J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Fy+9BN+epJhA for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 12:01:57 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 560B63A6A6C
	for <sip@ietf.org>; Mon, 13 Oct 2008 12:01:36 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	63AF220190; Mon, 13 Oct 2008 21:01:59 +0200 (CEST)
X-AuditID: c1b4fb3e-a7e83bb000007a96-4a-48f39b27b933
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	38C2F2005B; Mon, 13 Oct 2008 21:01:59 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 21:01:58 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 13 Oct 2008 21:01:57 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8ED@esealmw113.eemea.ericsson.se>
In-Reply-To: <48F2FC13.1070308@voip.co.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: VS: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
Thread-Index: AcktB1xjBie2koRPTuygIDgnFDKCHAAVOQXA
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>
	<48F23D27.8030305@voip.co.uk>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se>
	<48F2FC13.1070308@voip.co.uk>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Michael Procter" <michael@voip.co.uk>
X-OriginalArrivalTime: 13 Oct 2008 19:01:58.0678 (UTC)
	FILETIME=[2AEBCB60:01C92D66]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, Francois Audet <audet@nortel.com>
Subject: Re: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi Michael, 
   
>>>GRUU is a little more subtle than that.  If a UA provides an 
>>>instance-id to a GRUU-supporting registrar, then the 
>>>registrar will create a GRUU for that UA, whether it indicates
support or not.
>>>     
>>
>>Then the question is: if I only want to use outbound, is it 
>>always ok that the registrar creates a GRUU for me (no matter 
>>whether it returns it or not)?
>>   
> 
>I raised much the same question last year (March/April time), 
>and I think the conclusion was that creating the GRUU doesn't 
>cause problems and should be considered a Good Thing.

I think it is confusing that the 200 OK does not contain the gruu.
Shouldn't the 200 OK contain all currently registered contacts?

When a contact has been registered for an AOR (the RFC3680 statemachine
for the AOR is in "active" state), meaning that the AOR is reachable.

So, what is the justification for generating a gruu, but not returning
it (after all, the gruu will be sent to the UA if it registers to the
regevent package, so...)??? 


>>Then the text in 5.1, about the Require header is a little confusing.
It says that Require:gruu will NOT require the 
>>registrar to even generate a gruu - only that the registrar is
required to support gruu.
>>
>>OR, does the text refer to the case when the request ONLY contains
Require:gruu, but no instance-id?
>>
>>"A REGISTER request might contain a Require header field with the 
>>"gruu" option tag; this indicates that the registrar has to 
>>understand this extension in order to process the request.  It does 
>>not require the registrar to create GRUUs, however."
>>   
> 
>I think this is the normal Require processing.  Putting 'Require: gruu'
>in your REGISTER will ensure that it will only succeed on a 
>GRUU-aware registrar.  It doesn't control or enforce any 
>particular GRUU-related processing, only that the registrar 
>understands GRUU.  This behaviour (requiring understanding, 
>ot invoking) is common for many but not all SIP options.

My question is still: if the REGISTER contains instance-id AND
Require:gruu, is a gruu generated?

On one side the presence of instance-id always creates a gruu, but on
the other side the text says that the precense of Require:gruu does NOT
mandate the creation of a gruu.

OR, does the text simply mean that Require:gruu on its own (ie no
instance-id) does not mandate the creation of a gruu?



>>Maybe it would be good to clarify, in the outbound spec, 
>>that a gruu will be generated if the registrar supports gruu. 
>>Because, at least in 3GPP there has been some confusion about 
>>that, and I believe such clarification would prevent future 
>>interop problems.
> 
>I'm certainly in favour of reducing ambiguity, where it 
>exists, but I'm not sure outbound is the place to talk about 
>GRUUs.
>
>I think that the outbound spec should clarify that the instance-id,
when used with outbound, will also create a gruu, 
>according to the rules in the gruu-spec.
>
>How did the confusion arise?  The GRUU spec seems reasonably clear on
this point.

I don't remember the exact details, but: 3GPP uses gruu, and 3GPP has
adopted outbound for the multiple registration feature (previously it
was defined only for NAT traveral), so the question came up when the
procedures for the multiple registration feature was discussed: will a
gruu also be generated?

It may be obvious to people on this list, and of course we could clarify
it in the 3GPP specifications. But, I think this would be a useful
generic clarification in the outbound spec.

Regards,

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


From sip-bounces@ietf.org  Mon Oct 13 12:18:22 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8D9C83A6838;
	Mon, 13 Oct 2008 12:18:22 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 08C333A6838
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 12:18:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.201
X-Spam-Level: 
X-Spam-Status: No, score=-6.201 tagged_above=-999 required=5 tests=[AWL=0.048, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id bjAs2AjvK8Ad for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 12:18:18 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id F04133A67F7
	for <sip@ietf.org>; Mon, 13 Oct 2008 12:18:17 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	31A11203C3; Mon, 13 Oct 2008 21:18:42 +0200 (CEST)
X-AuditID: c1b4fb3e-a9686bb000007a96-83-48f39f1275c3
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	1E57B20FA5; Mon, 13 Oct 2008 21:18:42 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 21:18:38 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 13 Oct 2008 21:18:36 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
In-Reply-To: <18675.7684.207071.901832@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AcktG5kd5rs99AkMThCjJnNoQW6IKgAS0wKw
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18668.50247.121832.271341@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se><18668.51383.505850.963592@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se><18672.19846.621765.332209@taimen.test.fi><2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com><18673.5665.337048.880648@taimen.test.fi><2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com><18673.62485.295631.933830@taimen.test.fi><2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>, "Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 13 Oct 2008 19:18:38.0146 (UTC)
	FILETIME=[7EA68220:01C92D68]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi,

I don't think the spec is broken. I think the spec was written based on
the assumption that a UA instance is not interested in receiving an
INVITE multiple times in parallel (the UA will return 484 for all but
one INVITE) - which I don't think is desired even in normal forking
scenarios - but that it should be possible to, if one flow is down,
choose another flow to reach the UA (read: serial forking).

And, IF you would use two instance-ids (as proposed by Dean), why does
the forking proxy need to know whether they belong to the same UA or
not? Why doesn't it simply do paralell forking?

Regards,

Christer

 

> -----Original Message-----
> From: Juha Heinanen [mailto:jh@tutpro.com] 
> Sent: Monday, October 13, 2008 1:08 PM
> To: Dean Willis
> Cc: Christer Holmberg; Paul Kyzivat; sip@ietf.org
> Subject: Re: [Sip] Dual registration without Outbound
> 
> Dean Willis writes:
> 
>  > Um, perhaps I missed something. What is that prevents a UA 
> from  > registering two different interfaces with discrete 
> instance IDs and  > having a forking proxy fork to both instances?
> 
> i don't think nothing prevents that, but in my example, there 
> is only one sip ua and one instance of it.  both contacts of 
> this instance belong to the same ua:
> 
>    Proxies can
>    determine which flows go to the same UA by comparing the 
> instance-id.
> 
> if my phone would have two instance-ids, according to the 
> above, i would have too UAs, which is not the case today and 
> i don't want that to be the case when/if i one day upgrade 
> its software to support outbound rfc.
> 
> it is amazing how hard it is to you to admit that outbound 
> i-d as currently written is badly broken.
> 
> -- juha
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct 13 12:27:03 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 221EA3A6A50;
	Mon, 13 Oct 2008 12:27:03 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 613203A6A50
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 12:27:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FcDpBki0Qvyp for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 12:27:01 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id 6F69D3A6A00
	for <sip@ietf.org>; Mon, 13 Oct 2008 12:27:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 8D08C1EC30A;
	Mon, 13 Oct 2008 22:27:11 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id j5dvUFRF-gqd; Mon, 13 Oct 2008 22:27:09 +0300 (EEST)
Received: from taimen (h175008.gprs.dnafinland.fi [87.93.175.8])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Mon, 13 Oct 2008 22:27:09 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 9684CAC0BF; Mon, 13 Oct 2008 22:27:03 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18675.41223.587006.241312@taimen.test.fi>
Date: Mon, 13 Oct 2008 22:27:03 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18668.50247.121832.271341@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
	<18668.51383.505850.963592@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
	<18673.5665.337048.880648@taimen.test.fi>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > I don't think the spec is broken. I think the spec was written based on
 > the assumption that a UA instance is not interested in receiving an
 > INVITE multiple times in parallel (the UA will return 484 for all but
 > one INVITE) - which I don't think is desired even in normal forking
 > scenarios - 

the assumption and your conclusion is plain wrong.  in the example i
gave, it is very useful and desired that if wlan connectivity works,
phone gets the invite about 10 seconds faster than over gprs and the
call id free.  when second invite comes, my phone rejects it (i don't
remember the code, but that doesn't really matter to me).

 > but that it should be possible to, if one flow is down,
 > choose another flow to reach the UA (read: serial forking).

cannot do that it the other flow is not reachable through the proxy and
the other proxy to which the contact was registered is down.  this is
because the contact was not registered with both due to the brain damage
of ob draft and its instance-id business.

 > And, IF you would use two instance-ids (as proposed by Dean), why does
 > the forking proxy need to know whether they belong to the same UA or
 > not? Why doesn't it simply do paralell forking?

the proxy does not, but i don't want to complicate configuration of the
UA simply in order to cope with the brain damage of ob draft.  also,
don't want that the UA has to send two invites for one contact each.

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


From sip-bounces@ietf.org  Mon Oct 13 12:27:40 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DBE1F3A6B2A;
	Mon, 13 Oct 2008 12:27:40 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1E5613A6B5B
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 12:27:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.902
X-Spam-Level: 
X-Spam-Status: No, score=-5.902 tagged_above=-999 required=5
	tests=[AWL=-0.253, BAYES_00=-2.599, HELO_EQ_SE=0.35,
	J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id b8es11bXGC1f for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 12:27:39 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id DDADB3A69D2
	for <sip@ietf.org>; Mon, 13 Oct 2008 12:27:38 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	6FBFB2192A; Mon, 13 Oct 2008 21:06:54 +0200 (CEST)
X-AuditID: c1b4fb3e-a8684bb000007a96-46-48f39c4e9ff9
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	1237D20423; Mon, 13 Oct 2008 21:06:54 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 21:05:34 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 13 Oct 2008 21:05:34 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8EE@esealmw113.eemea.ericsson.se>
In-Reply-To: <48F34E3B.80106@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
Thread-Index: AcktOFPi4anv+TnYRGmmyHtP7bolNgALeABQ
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>	<48F23D27.8030305@voip.co.uk>	<CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se>
	<48F2FC13.1070308@voip.co.uk> <48F34E3B.80106@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>, "Michael Procter" <michael@voip.co.uk>
X-OriginalArrivalTime: 13 Oct 2008 19:05:34.0686 (UTC)
	FILETIME=[ABABFFE0:01C92D66]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, Francois Audet <audet@nortel.com>
Subject: Re: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>Its been a long time, and the details are starting to get fuzzy in my
mind.

One should not have to remember the details - they should be clear by
reading the specs :)

>But I'm quite sure Michael is right here. The first registration with
an instance id causes the 
>creation of a permanent gruu, and every registration with an instance
id results in creation of a temp gruu. 
>This is regardless of whether the registering UA indicates support for
gruu. If it does, then it receives a copy of the 
>gruu in the response.

Yes. The question was whether instance-id AND reg-id also create a gruu.
The answer seems to be yes, but I think it would be good to clarify that
somewhere.

So, either the outbound spec has a note saying that a gruu will always
be created.

...and/or, the gruu spec says that a gruu will always be created - even
when the instance-id is used as part of another feature (e.g. outbound).

Regards,

Christer









> Michael Procter wrote:
> > Christer Holmberg wrote:
> >> Hi,
> >>
> >>   
> >>> GRUU is a little more subtle than that.  If a UA provides an 
> >>> instance-id to a GRUU-supporting registrar, then the 
> registrar will 
> >>> create a GRUU for that UA, whether it indicates support or not.
> >>>     
> >> Then the question is: if I only want to use outbound, is 
> it always ok that the registrar creates a GRUU for me (no 
> matter whether it returns it or not)?
> >>   
> > 
> > I raised much the same question last year (March/April time), and I 
> > think the conclusion was that creating the GRUU doesn't 
> cause problems 
> > and should be considered a Good Thing.
> > 
> >> Then the text in 5.1, about the Require header is a little 
> confusing. It says that Require:gruu will NOT require the 
> registrar to even generate a gruu - only that the registrar 
> is required to support gruu.
> >>
> >> OR, does the text refer to the case when the request ONLY 
> contains Require:gruu, but no instance-id?
> >>
> >> "A REGISTER request might contain a Require header field with the 
> >> "gruu" option tag; this indicates that the registrar has to 
> >> understand this extension in order to process the request. 
>  It does 
> >> not require the registrar to create GRUUs, however."
> >>   
> > 
> > I think this is the normal Require processing.  Putting 
> 'Require: gruu'
> > in your REGISTER will ensure that it will only succeed on a 
> GRUU-aware 
> > registrar.  It doesn't control or enforce any particular 
> GRUU-related 
> > processing, only that the registrar understands GRUU.  This 
> behaviour 
> > (requiring understanding, not invoking) is common for many 
> but not all 
> > SIP options.
> > 
> >> Maybe it would be good to clarify, in the outbound spec, 
> that a gruu will be generated if the registrar supports gruu. 
> Because, at least in 3GPP there has been some confusion about 
> that, and I believe such clarification would prevent future 
> interop problems.
> >>   
> > 
> > I'm certainly in favour of reducing ambiguity, where it exists, but 
> > I'm not sure outbound is the place to talk about GRUUs.  
> How did the 
> > confusion arise?  The GRUU spec seems reasonably clear on 
> this point.
> > 
> > Regards,
> > 
> > Michael
> > _______________________________________________
> > Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol Use 
> > sip-implementors@cs.columbia.edu for questions on current sip Use 
> > sipping@ietf.org for new developments on the application of sip
> > 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct 13 12:31:26 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1CD613A6B14;
	Mon, 13 Oct 2008 12:31:26 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CA8A53A6B14
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 12:31:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.197
X-Spam-Level: 
X-Spam-Status: No, score=-6.197 tagged_above=-999 required=5 tests=[AWL=0.052, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id IqooIH8Fhx+Q for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 12:31:24 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id C43463A6B10
	for <sip@ietf.org>; Mon, 13 Oct 2008 12:31:23 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	7341D20066; Mon, 13 Oct 2008 21:31:29 +0200 (CEST)
X-AuditID: c1b4fb3e-a7682bb000007a96-b9-48f3a211cd00
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	54A8220064; Mon, 13 Oct 2008 21:31:29 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 21:31:28 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 13 Oct 2008 21:31:27 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8F0@esealmw113.eemea.ericsson.se>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF19B6BAC6@zrc2hxm0.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Outbound: keep-alives on dialog flows
Thread-Index: AckpWPlJ7iefydswRVaN7SAqinZOwAEAjN4AAANxrfA=
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8C9@esealmw113.eemea.ericsson.se>
	<1ECE0EB50388174790F9694F77522CCF19B6BAC6@zrc2hxm0.corp.nortel.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Francois Audet" <audet@nortel.com>,
	<sip@ietf.org>
X-OriginalArrivalTime: 13 Oct 2008 19:31:28.0777 (UTC)
	FILETIME=[49FB7790:01C92D6A]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] Outbound: keep-alives on dialog flows
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>It can. Section 4.4., second and third paragraph.
>	 
>But it basically says that you need an explicit indication. I believe
that the intent of this wording was to allow for 
>sip-keep draft.
>	 
>In other words, I believe it says that the non-register case can only
use keep-alive if there is an explicit mechanism 
>(e.g., sip-keep).

Ok, that clarifies.

But, do we then need to indicate that the procedures in chapter 3.5 and
3.5.1 only apply to registration flows?

Because, chapter 3.5 says:

"When the UA detects that a flow has failed or that the flow definition
has changed, the UA needs to re-register..."

...and chapter 3.5.1 says:

"If the client does not receive a pong in response to its ping, it
declares the flow dead and opens a new flow in its place."

OR, should chapter 3.5 say anything about what happens in a flow failure
in the first place? We have decided that the keep-alives is a separate
function, and in order for e.g. the keep-draft to refer to it I think it
should be described without any outbound procedures attached. Chapter 4
then describes how the keep-alives are used with outbound.


Finally, as I asked earlier, since an INVITE can establish a flow, can a
INVITE be rejectect with 439?


Regards,

Christer

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


From sip-bounces@ietf.org  Mon Oct 13 12:38:29 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 184C53A6B10;
	Mon, 13 Oct 2008 12:38:29 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0D53F3A6B07
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 12:38:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id IosOc6xh5Nbn for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 12:38:27 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id 2FF883A68B6
	for <sip@ietf.org>; Mon, 13 Oct 2008 12:38:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 9F1CE1EC30A;
	Mon, 13 Oct 2008 22:38:54 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Vgihi-AlhMjT; Mon, 13 Oct 2008 22:38:52 +0300 (EEST)
Received: from taimen (h175008.gprs.dnafinland.fi [87.93.175.8])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Mon, 13 Oct 2008 22:38:52 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 9699DAC0BF; Mon, 13 Oct 2008 22:38:46 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18675.41926.583512.912121@taimen.test.fi>
Date: Mon, 13 Oct 2008 22:38:46 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>, sip@ietf.org,
	Paul Kyzivat <pkyzivat@cisco.com>, Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <18675.41223.587006.241312@taimen.test.fi>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18668.50247.121832.271341@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
	<18668.51383.505850.963592@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
	<18673.5665.337048.880648@taimen.test.fi>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Juha Heinanen writes:

 > the proxy does not, but i don't want to complicate configuration of the
 > UA simply in order to cope with the brain damage of ob draft.  also,
 > don't want that the UA has to send two invites for one contact each.

typo: i don't want that the UA has to send two REGISTERs for one contact
each.  that is, UA must be able to register both of its contacts in a
single register request.

this is my last message about this topic (i need to save cycles to code
writing).  i have already learned many times that this working group
does not care about real world requirements or even rfc3261
compatibility unless something in 3gpp gets broken.

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


From sip-bounces@ietf.org  Mon Oct 13 12:39:04 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D454D3A69D2;
	Mon, 13 Oct 2008 12:39:04 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DB7683A6A3E
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 12:39:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level: 
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5
	tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_74=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FMkfjICp1D4k for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 12:39:02 -0700 (PDT)
Received: from sov.voip.co.uk (smtp.sov.voip.co.uk [80.249.108.49])
	by core3.amsl.com (Postfix) with ESMTP id 9A0AE3A68E7
	for <sip@ietf.org>; Mon, 13 Oct 2008 12:39:00 -0700 (PDT)
Message-ID: <48F3A3EA.4050307@voip.co.uk>
Date: Mon, 13 Oct 2008 20:39:22 +0100
From: Michael Procter <michael@voip.co.uk>
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>
	<48F23D27.8030305@voip.co.uk>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se>
	<48F2FC13.1070308@voip.co.uk>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8ED@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F8ED@esealmw113.eemea.ericsson.se>
Cc: sip@ietf.org, Francois Audet <audet@nortel.com>
Subject: Re: [Sip] Is GRUU generated in the case of registration with
 instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi Christer,

Christer Holmberg wrote:
> Hi Michael, 
> I think it is confusing that the 200 OK does not contain the gruu.
> Shouldn't the 200 OK contain all currently registered contacts?
>   

Yes, the 200 OK should contain all currently registered contacts, but a
GRUU isn't a registered contact.  When the UA indicates support, the
GRUUs are returned as header parameters to their associated contact, not
as separate contacts.

> When a contact has been registered for an AOR (the RFC3680 statemachine
> for the AOR is in "active" state), meaning that the AOR is reachable.
>
> So, what is the justification for generating a gruu, but not returning
> it (after all, the gruu will be sent to the UA if it registers to the
> regevent package, so...)??? 
>   

Sending a header parameter to a UA that doesn't declare it supports it
seems to be inviting interop issues.  I suspect this is the reason,
although I wasn't involved with that decision so I can't say
categorically what the reason was.

> My question is still: if the REGISTER contains instance-id AND
> Require:gruu, is a gruu generated?
>
> On one side the presence of instance-id always creates a gruu, but on
> the other side the text says that the precense of Require:gruu does NOT
> mandate the creation of a gruu.
>
> OR, does the text simply mean that Require:gruu on its own (ie no
> instance-id) does not mandate the creation of a gruu?
>   

I think it is this last one.  'Require: gruu' has no special meaning to
a gruu-supporting registrar - it only prevents non-supporting registrars
from handling the request. 

A gruu-supporting registrar will follow section 5, which contains the
phrase:
"If there is no valid public GRUU, the registrar SHOULD construct a
public GRUU"

Assuming the UA includes a +sip.instance, and doesn't try to do anything
silly (register the AoR as a contact, register a gruu as a contact),
then you SHOULD get a GRUU made for you.

> I don't remember the exact details, but: 3GPP uses gruu, and 3GPP has
> adopted outbound for the multiple registration feature (previously it
> was defined only for NAT traveral), so the question came up when the
> procedures for the multiple registration feature was discussed: will a
> gruu also be generated?
>
> It may be obvious to people on this list, and of course we could clarify
> it in the 3GPP specifications. But, I think this would be a useful
> generic clarification in the outbound spec.
>   

Maybe someone else would like to address this point.  Personally, I am
ambivalent.

> Regards,
>
> Christer
>   

Regards,

Michael

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


From sip-bounces@ietf.org  Mon Oct 13 12:39:39 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 939693A6BB1;
	Mon, 13 Oct 2008 12:39:39 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 00B133A6BB2
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 12:39:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.198
X-Spam-Level: 
X-Spam-Status: No, score=-6.198 tagged_above=-999 required=5 tests=[AWL=0.051, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SzNI-U2lsmAu for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 12:39:37 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id EBEF83A68AA
	for <sip@ietf.org>; Mon, 13 Oct 2008 12:39:36 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	F0B022046A; Mon, 13 Oct 2008 21:39:31 +0200 (CEST)
X-AuditID: c1b4fb3c-af8d1bb0000015b5-0d-48f3a3f3ea9a
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	D6EB2203D6; Mon, 13 Oct 2008 21:39:31 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 21:39:24 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 13 Oct 2008 21:39:23 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8F1@esealmw113.eemea.ericsson.se>
In-Reply-To: <18675.41223.587006.241312@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AcktabFA4ANQ+Y4cSF6cjK5/FVM7dQAARmag
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18668.50247.121832.271341@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se><18668.51383.505850.963592@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se><18672.19846.621765.332209@taimen.test.fi><2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com><18673.5665.337048.880648@taimen.test.fi><2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com><18673.62485.295631.933830@taimen.test.fi><2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com><18675.7684.207071.901832@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 13 Oct 2008 19:39:24.0887 (UTC)
	FILETIME=[65C41670:01C92D6B]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>I don't think the spec is broken. I think the spec was 
>>written based on the assumption that a UA instance is not 
>>interested in receiving an INVITE multiple times in 
>>parallel (the UA will return 484 for all but one INVITE) - 
>>which I don't think is desired even in normal forking scenarios - 
> 
>the assumption and your conclusion is plain wrong.  in the 
>example i gave, it is very useful and desired that if wlan 
>connectivity works, phone gets the invite about 10 seconds 
>faster than over gprs and the call id free.  when second 
>invite comes, my phone rejects it (i don't remember the code, 
>but that doesn't really matter to me).

484.

>>but that it should be possible to, if one flow is down, 
>>choose another flow to reach the UA (read: serial forking).
> 
>cannot do that it the other flow is not reachable through the 
>proxy and the other proxy to which the contact was registered 
>is down.  this is because the contact was not registered with 
>both due to the brain damage of ob draft and its instance-id business.

If specs had brains they would write themselves for us... :)
 
>>And, IF you would use two instance-ids (as proposed by 
>>Dean), why does the forking proxy need to know whether 
>>they belong to the same UA or not? Why doesn't it simply 
>>do paralell forking?
> 
>the proxy does not, but i don't want to complicate 
>configuration of the UA simply in order to cope with the 
>brain damage of ob draft.  also, don't want that the UA has 
>to send two invites for one contact each.

Why would the UA have to send two INVITEs just because it uses different
instance-ids?

Regards,

Christer

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


From sip-bounces@ietf.org  Mon Oct 13 12:44:18 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 63DEA3A6BB6;
	Mon, 13 Oct 2008 12:44:18 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C55753A6BB6
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 12:44:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.199
X-Spam-Level: 
X-Spam-Status: No, score=-6.199 tagged_above=-999 required=5 tests=[AWL=0.050, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Fv62AgMdAJ1S for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 12:44:17 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id C3B853A68B6
	for <sip@ietf.org>; Mon, 13 Oct 2008 12:44:16 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	408D920A3F; Mon, 13 Oct 2008 21:44:55 +0200 (CEST)
X-AuditID: c1b4fb3c-ac8cbbb0000015b5-7d-48f3a537dd39
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	2042F203DA; Mon, 13 Oct 2008 21:44:55 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 21:44:54 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 13 Oct 2008 21:44:52 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
In-Reply-To: <18675.41926.583512.912121@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackta1Q4oPZYeoZEQAiUqa8JyoYU4gAAB04g
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18668.50247.121832.271341@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se><18668.51383.505850.963592@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se><18672.19846.621765.332209@taimen.test.fi><2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com><18673.5665.337048.880648@taimen.test.fi><2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com><18673.62485.295631.933830@taimen.test.fi><2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com><18675.7684.207071.901832@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se><18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>, <sip@ietf.org>,
	"Paul Kyzivat" <pkyzivat@cisco.com>,
	"Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 13 Oct 2008 19:44:54.0533 (UTC)
	FILETIME=[2A401350:01C92D6C]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 
Hi,

>>the proxy does not, but i don't want to complicate 
>>configuration of the UA simply in order to cope with the 
>>brain damage of ob draft.  also, don't want that the UA 
>>has to send two invites for one contact each.
> 
>typo: i don't want that the UA has to send two REGISTERs for 
>one contact each.  that is, UA must be able to register both 
>of its contacts in a single register request.

You will still have to send a REGISTER for each flow that you establish
- no matter whether you use the same contact/instance-id or not.

Or, do you also want to change outbound so that you can establish
multiple flows with a single REGISTER?

Regards,

Christer

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


From sip-bounces@ietf.org  Mon Oct 13 12:53:38 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 641623A6888;
	Mon, 13 Oct 2008 12:53:38 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A82013A6888
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 12:53:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.9
X-Spam-Level: 
X-Spam-Status: No, score=-5.9 tagged_above=-999 required=5 tests=[AWL=-0.251, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_74=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rn+MM9PFHql9 for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 12:53:34 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id C94203A67AB
	for <sip@ietf.org>; Mon, 13 Oct 2008 12:53:33 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	48CCA2175A; Mon, 13 Oct 2008 21:53:51 +0200 (CEST)
X-AuditID: c1b4fb3e-a9e87bb000007a96-e5-48f3a74fd22d
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	2D93520222; Mon, 13 Oct 2008 21:53:51 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 21:53:50 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 13 Oct 2008 21:53:50 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8F3@esealmw113.eemea.ericsson.se>
In-Reply-To: <48F3A3EA.4050307@voip.co.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: VS: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
Thread-Index: Ackta2J9xTC7uTe9RTe4npORTDUQyAAAQz+A
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>
	<48F23D27.8030305@voip.co.uk>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se>
	<48F2FC13.1070308@voip.co.uk>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8ED@esealmw113.eemea.ericsson.se>
	<48F3A3EA.4050307@voip.co.uk>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Michael Procter" <michael@voip.co.uk>
X-OriginalArrivalTime: 13 Oct 2008 19:53:50.0578 (UTC)
	FILETIME=[69C20D20:01C92D6D]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, Francois Audet <audet@nortel.com>
Subject: Re: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>So, what is the justification for generating a gruu, but 
>>not returning it (after all, the gruu will be sent to the UA if it 
>>registers to the regevent package, so...)??? 
> 
>Sending a header parameter to a UA that doesn't declare it supports it
>seems to be inviting interop issues.  I suspect this is the reason,
>although I wasn't involved with that decision so I can't say
>categorically what the reason was.

Fair enough, but the UA is still going to get it if it subscribes to the
regevent package, isn't it?

>>My question is still: if the REGISTER contains instance-id AND
>>Require:gruu, is a gruu generated?
>>
>>On one side the presence of instance-id always creates a gruu, but on
>>the other side the text says that the precense of Require:gruu does
NOT
>>mandate the creation of a gruu.
>>
>>OR, does the text simply mean that Require:gruu on its own (ie no
>>instance-id) does not mandate the creation of a gruu?
>>    
>I think it is this last one.  'Require: gruu' has no special 
>meaning to a gruu-supporting registrar - it only prevents
non-supporting 
>registrars from handling the request.

That sounds reasonalble, but I think it should also be clarified.

Again, it may be clear to all of us now, but in order to avoid having
this same disucssion again in a couple of years....

>A gruu-supporting registrar will follow section 5, which contains the
>phrase:
>"If there is no valid public GRUU, the registrar SHOULD construct a
public GRUU"
> 
>Assuming the UA includes a +sip.instance, and doesn't try to 
>do anything silly (register the AoR as a contact, register a gruu as a
contact),
>then you SHOULD get a GRUU made for you.

Does instance-id AND Require:gruu also RETURN the gruu?

Or, if I want the gruu returned, and I want to mandate the registrar to
support gruu, do I have to send:

Instance-id AND Supported:gruu AND Require:gruu

Whatever the answer to my question is - clarification would be
appretiated :)

Regards,

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


From sip-bounces@ietf.org  Mon Oct 13 13:30:46 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 84A383A67A2;
	Mon, 13 Oct 2008 13:30:46 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2D2CE3A67A2
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 13:30:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5
	tests=[AWL=-0.100, BAYES_00=-2.599, J_CHICKENPOX_74=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RfTihOnXUj4W for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 13:30:45 -0700 (PDT)
Received: from sov.voip.co.uk (smtp.sov.voip.co.uk [80.249.108.49])
	by core3.amsl.com (Postfix) with ESMTP id AA3F63A67A1
	for <sip@ietf.org>; Mon, 13 Oct 2008 13:30:44 -0700 (PDT)
Message-ID: <48F3B002.6000201@voip.co.uk>
Date: Mon, 13 Oct 2008 21:30:58 +0100
From: Michael Procter <michael@voip.co.uk>
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>
	<48F23D27.8030305@voip.co.uk>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se>
	<48F2FC13.1070308@voip.co.uk>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8ED@esealmw113.eemea.ericsson.se>
	<48F3A3EA.4050307@voip.co.uk>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F3@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F8F3@esealmw113.eemea.ericsson.se>
Cc: sip@ietf.org, Francois Audet <audet@nortel.com>
Subject: Re: [Sip] Is GRUU generated in the case of registration with
 instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg wrote:
> Hi, 
>   
>>> So, what is the justification for generating a gruu, but 
>>> not returning it (after all, the gruu will be sent to the UA if it 
>>> registers to the regevent package, so...)??? 
>>>       
>> Sending a header parameter to a UA that doesn't declare it supports it
>> seems to be inviting interop issues.  I suspect this is the reason,
>> although I wasn't involved with that decision so I can't say
>> categorically what the reason was.
>>     
>
> Fair enough, but the UA is still going to get it if it subscribes to the
> regevent package, isn't it?
>   

Yes, it is.

> Does instance-id AND Require:gruu also RETURN the gruu?
>   

No. GRUU draft section 5.2 contains:
"If the REGISTER request contained a Supported header field that
included the "gruu" option..."
so the Supported header is needed (although you might get a pub-gruu if
you squint at the parenthetical 'and the client supports GRUUs' since
having a Require: gruu could be considered evidence of supporting gruus
- I don't think this follows the spirit of the draft though).

> Or, if I want the gruu returned, and I want to mandate the registrar to
> support gruu, do I have to send:
>
> Instance-id AND Supported:gruu AND Require:gruu
>   

GRUU draft, section 4.1 (extract from last paragraph):

"If a UA wishes to guarantee that the REGISTER request is not processed
unless the domain supports and uses this extension, it MAY include a
Require header field in the request with a value that contains the
"gruu" option tag. This is in addition to the presence of the Supported
header field also containing the "gruu" option tag."

So it looks like you need all three: +sip.instance, Require:gruu and
Supported: gruu.

> Whatever the answer to my question is - clarification would be
> appretiated :)
>   

I hope this helps!

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


From sip-bounces@ietf.org  Mon Oct 13 15:53:23 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 860B73A680B;
	Mon, 13 Oct 2008 15:53:23 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4E4653A680B
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 15:53:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.201
X-Spam-Level: 
X-Spam-Status: No, score=-6.201 tagged_above=-999 required=5
	tests=[AWL=-0.202, BAYES_00=-2.599, J_CHICKENPOX_74=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id DCMbTgGrdu3T for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 15:53:21 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 1758A3A6A44
	for <sip@ietf.org>; Mon, 13 Oct 2008 15:53:21 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,405,1220227200"; d="scan'208";a="24116136"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 13 Oct 2008 22:54:10 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9DMsA8c011100; 
	Mon, 13 Oct 2008 18:54:10 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9DMsAPX025640;
	Mon, 13 Oct 2008 22:54:10 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 18:54:10 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 18:54:09 -0400
Message-ID: <48F3D191.5000007@cisco.com>
Date: Mon, 13 Oct 2008 18:54:09 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>	<48F23D27.8030305@voip.co.uk>	<CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se>
	<48F2FC13.1070308@voip.co.uk> <48F34E3B.80106@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EE@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F8EE@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 13 Oct 2008 22:54:09.0856 (UTC)
	FILETIME=[9A8CDC00:01C92D86]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4044; t=1223938450;
	x=1224802450; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Is=20GRUU=20generated=20in=20th
	e=20case=20of=20registration=20with=20instance-ID=0A=20and=2
	0reg-ID |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=XrUT8ITgxuuq+h/nhvqh6l+iVYhSzIg5AFUnaz7/Z+k=;
	b=vGpXXBhJ3/FxPtGrT7d2TQOq3GIQXfpqNlk0Yv/DyWCx5mlreb/KKXN5eH
	Jn3rqTqce04a5wohrv/6Kt+Vtil1KLmdEgGNN/P8Fcq2WN4R0/2cJqC6Tm25
	UYIdXXdz5D;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: sip@ietf.org, Francois Audet <audet@nortel.com>
Subject: Re: [Sip] Is GRUU generated in the case of registration with
 instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Christer Holmberg wrote:
> Hi, 
> 
>> Its been a long time, and the details are starting to get fuzzy in my
> mind.
> 
> One should not have to remember the details - they should be clear by
> reading the specs :)

Right. But I was being lazy.

>> But I'm quite sure Michael is right here. The first registration with
> an instance id causes the 
>> creation of a permanent gruu, and every registration with an instance
> id results in creation of a temp gruu. 
>> This is regardless of whether the registering UA indicates support for
> gruu. If it does, then it receives a copy of the 
>> gruu in the response.
> 
> Yes. The question was whether instance-id AND reg-id also create a gruu.
> The answer seems to be yes, but I think it would be good to clarify that
> somewhere.

Since reg-id isn't mentioned in gruu, its irrelevant to the gruu spec, 
just as any other parameters are.

> So, either the outbound spec has a note saying that a gruu will always
> be created.
> 
> ...and/or, the gruu spec says that a gruu will always be created - even
> when the instance-id is used as part of another feature (e.g. outbound).

That would require it to be aware that it was part of another feature.
IMO That's an unreasonable assumption.

The spec says what it means.

	Thanks,
	Paul

> Regards,
> 
> Christer
> 
> 
> 
> 
> 
> 
> 
> 
> 
>> Michael Procter wrote:
>>> Christer Holmberg wrote:
>>>> Hi,
>>>>
>>>>   
>>>>> GRUU is a little more subtle than that.  If a UA provides an 
>>>>> instance-id to a GRUU-supporting registrar, then the 
>> registrar will 
>>>>> create a GRUU for that UA, whether it indicates support or not.
>>>>>     
>>>> Then the question is: if I only want to use outbound, is 
>> it always ok that the registrar creates a GRUU for me (no 
>> matter whether it returns it or not)?
>>>>   
>>> I raised much the same question last year (March/April time), and I 
>>> think the conclusion was that creating the GRUU doesn't 
>> cause problems 
>>> and should be considered a Good Thing.
>>>
>>>> Then the text in 5.1, about the Require header is a little 
>> confusing. It says that Require:gruu will NOT require the 
>> registrar to even generate a gruu - only that the registrar 
>> is required to support gruu.
>>>> OR, does the text refer to the case when the request ONLY 
>> contains Require:gruu, but no instance-id?
>>>> "A REGISTER request might contain a Require header field with the 
>>>> "gruu" option tag; this indicates that the registrar has to 
>>>> understand this extension in order to process the request. 
>>  It does 
>>>> not require the registrar to create GRUUs, however."
>>>>   
>>> I think this is the normal Require processing.  Putting 
>> 'Require: gruu'
>>> in your REGISTER will ensure that it will only succeed on a 
>> GRUU-aware 
>>> registrar.  It doesn't control or enforce any particular 
>> GRUU-related 
>>> processing, only that the registrar understands GRUU.  This 
>> behaviour 
>>> (requiring understanding, not invoking) is common for many 
>> but not all 
>>> SIP options.
>>>
>>>> Maybe it would be good to clarify, in the outbound spec, 
>> that a gruu will be generated if the registrar supports gruu. 
>> Because, at least in 3GPP there has been some confusion about 
>> that, and I believe such clarification would prevent future 
>> interop problems.
>>>>   
>>> I'm certainly in favour of reducing ambiguity, where it exists, but 
>>> I'm not sure outbound is the place to talk about GRUUs.  
>> How did the 
>>> confusion arise?  The GRUU spec seems reasonably clear on 
>> this point.
>>> Regards,
>>>
>>> Michael
>>> _______________________________________________
>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>> This list is for NEW development of the core SIP Protocol Use 
>>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>>> sipping@ietf.org for new developments on the application of sip
>>>
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct 13 16:07:03 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 54FF13A69C3;
	Mon, 13 Oct 2008 16:07:03 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 294243A69C3
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 16:07:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.195
X-Spam-Level: 
X-Spam-Status: No, score=-6.195 tagged_above=-999 required=5
	tests=[AWL=-0.196, BAYES_00=-2.599, J_CHICKENPOX_74=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ZWwgmEwfJPfb for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 16:07:00 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 21B5E3A66B4
	for <sip@ietf.org>; Mon, 13 Oct 2008 16:07:00 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,405,1220227200"; d="scan'208";a="174401790"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 13 Oct 2008 23:07:51 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9DN7pWl008140; 
	Mon, 13 Oct 2008 16:07:51 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m9DN7our006779;
	Mon, 13 Oct 2008 23:07:50 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 19:07:49 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Oct 2008 19:07:48 -0400
Message-ID: <48F3D4C4.2060006@cisco.com>
Date: Mon, 13 Oct 2008 19:07:48 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>	<48F23D27.8030305@voip.co.uk>	<CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se>	<48F2FC13.1070308@voip.co.uk>	<CA9998CD4A020D418654FCDEF4E707DF05C0F8ED@esealmw113.eemea.ericsson.se>	<48F3A3EA.4050307@voip.co.uk>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F3@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F8F3@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 13 Oct 2008 23:07:48.0752 (UTC)
	FILETIME=[82A67900:01C92D88]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3901; t=1223939271;
	x=1224803271; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Is=20GRUU=20generated=20in=20th
	e=20case=20of=20registration=20with=09instance-ID=0A=20and=2
	0reg-ID |Sender:=20;
	bh=Yfma4KpShHnSUFvPzZahsV+6/IvAeoeZUoMTIfPTP+Y=;
	b=bToNpAQFGUOCkA3Nqa+R00+bcr6t1iMhWEuATzhvP2N3DkdMex+6wjCRdK
	4nlkE7LV69idGICZ4dBctvHfFlJtVQDRTEp1lwe5ID3PuIt7hFQLSmFaUV53
	uchCLKBROf;
Authentication-Results: sj-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: sip@ietf.org, Francois Audet <audet@nortel.com>
Subject: Re: [Sip] Is GRUU generated in the case of registration
 with	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Christer Holmberg wrote:
> Hi, 
> 
>>> So, what is the justification for generating a gruu, but 
>>> not returning it (after all, the gruu will be sent to the UA if it 
>>> registers to the regevent package, so...)??? 
>> Sending a header parameter to a UA that doesn't declare it supports it
>> seems to be inviting interop issues.  I suspect this is the reason,
>> although I wasn't involved with that decision so I can't say
>> categorically what the reason was.

I also don't recall for certain what the reason was. I think perhaps 
initially it was thought that gruus would only been generated when 
requested. But that led to some logical inconsistencies around the 
permanent gruu when others might need to observe the gruu. So it was 
concluded that the presence of the gruu was coupled to the 
AOR/Contact/Instance-ID tuple. I can't remember the exact problem cases 
right now, though I think they did come from me. I can probably find 
them in my mail history if I look hard enough. But there was so much 
discussion on gruu it would take me a long time.

> Fair enough, but the UA is still going to get it if it subscribes to the
> regevent package, isn't it?

Yup. But ought to ignore any parts of the extension schema it doesn't 
understand.

>>> My question is still: if the REGISTER contains instance-id AND
>>> Require:gruu, is a gruu generated?
>>>
>>> On one side the presence of instance-id always creates a gruu, but on
>>> the other side the text says that the precense of Require:gruu does
> NOT
>>> mandate the creation of a gruu.
>>>
>>> OR, does the text simply mean that Require:gruu on its own (ie no
>>> instance-id) does not mandate the creation of a gruu?
>>>    
>> I think it is this last one.  'Require: gruu' has no special 
>> meaning to a gruu-supporting registrar - it only prevents
> non-supporting 
>> registrars from handling the request.
> 
> That sounds reasonalble, but I think it should also be clarified.

What are we clarifying? We know what the standard meaning of Require is. 
And we know that no additional meaning is provided. Why is more required?

> Again, it may be clear to all of us now, but in order to avoid having
> this same disucssion again in a couple of years....

If that is the point, the *maybe*. Given the state of the draft, it 
would probably have to be in Auth 48 if Jonathan wants to do it. Else it 
would be quite a pain.

>> A gruu-supporting registrar will follow section 5, which contains the
>> phrase:
>> "If there is no valid public GRUU, the registrar SHOULD construct a
> public GRUU"
>> Assuming the UA includes a +sip.instance, and doesn't try to 
>> do anything silly (register the AoR as a contact, register a gruu as a
> contact),
>> then you SHOULD get a GRUU made for you.
> 
> Does instance-id AND Require:gruu also RETURN the gruu?
> 
> Or, if I want the gruu returned, and I want to mandate the registrar to
> support gruu, do I have to send:
> 
> Instance-id AND Supported:gruu AND Require:gruu

I think the latter is correct. Require and Supported have different 
uses. As defined, Supported says "I am willing to have the GRUU returned 
to me, if it is available". My request still succeeds, but without 
getting the GRUU, if the registrar doesn't support gruu. "Require" says 
my request should fail if the registrar can't create the gruu.

This is all "SIP 101" stuff.

	Thanks,
	Paul

> Whatever the answer to my question is - clarification would be
> appretiated :)
> 
> Regards,
> 
> Christer
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct 13 22:12:28 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A66F03A6BBB;
	Mon, 13 Oct 2008 22:12:28 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 798113A63CB
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 22:12:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.195
X-Spam-Level: 
X-Spam-Status: No, score=-6.195 tagged_above=-999 required=5 tests=[AWL=0.054, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3mb8VHHwiSf5 for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 22:12:26 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 9014C3A6BA4
	for <sip@ietf.org>; Mon, 13 Oct 2008 22:12:26 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	1716C20197; Tue, 14 Oct 2008 07:13:05 +0200 (CEST)
X-AuditID: c1b4fb3e-a8684bb000007a96-ae-48f42a606c37
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	EF3B520059; Tue, 14 Oct 2008 07:13:04 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 14 Oct 2008 07:13:04 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 14 Oct 2008 07:13:03 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0864CEFC@esealmw113.eemea.ericsson.se>
In-Reply-To: <48F3D191.5000007@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
Thread-Index: Ackthpxe2j+IIv2ATNuWao7mqiLjvAANMqTQ
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>	<48F23D27.8030305@voip.co.uk>	<CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se>
	<48F2FC13.1070308@voip.co.uk> <48F34E3B.80106@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EE@esealmw113.eemea.ericsson.se>
	<48F3D191.5000007@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 14 Oct 2008 05:13:04.0373 (UTC)
	FILETIME=[8960DA50:01C92DBB]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, Francois Audet <audet@nortel.com>
Subject: Re: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>Yes. The question was whether instance-id AND reg-id also create a
gruu.
>>The answer seems to be yes, but I think it would be good to clarify 
>>that somewhere.
>
>Since reg-id isn't mentioned in gruu, its irrelevant to the gruu spec,
just as any other parameters are.

That is why I proposed it is clarified in the outbound spec :)

Regards,

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


From sip-bounces@ietf.org  Mon Oct 13 22:53:16 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 884CB28C10D;
	Mon, 13 Oct 2008 22:53:16 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5FF8228C10D
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 22:53:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KezW4JW7OZ9r for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 22:53:14 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id 156CA3A6BDA
	for <sip@ietf.org>; Mon, 13 Oct 2008 22:53:13 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m9E5rQot025741; Tue, 14 Oct 2008 08:53:49 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 14 Oct 2008 08:53:45 +0300
Received: from vaebe106.NOE.Nokia.com ([10.160.244.67]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 14 Oct 2008 08:53:45 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 14 Oct 2008 08:53:44 +0300
Message-ID: <7A726F54F791494C8D8C87F13736E80EF52279@vaebe106.NOE.Nokia.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F8ED@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Is GRUU generated in the case of registration
	withinstance-ID and reg-ID
Thread-Index: AcktB1xjBie2koRPTuygIDgnFDKCHAAVOQXAABh04SA=
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com><CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se><48F23D27.8030305@voip.co.uk><CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se><48F2FC13.1070308@voip.co.uk>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8ED@esealmw113.eemea.ericsson.se>
From: <Erkki.Koivusalo@nokia.com>
To: <christer.holmberg@ericsson.com>, <michael@voip.co.uk>
X-OriginalArrivalTime: 14 Oct 2008 05:53:45.0454 (UTC)
	FILETIME=[386040E0:01C92DC1]
X-Nokia-AV: Clean
Cc: sip@ietf.org, audet@nortel.com
Subject: Re: [Sip] Is GRUU generated in the case of registration
	withinstance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>Its been a long time, and the details are starting to get fuzzy in my
>mind.
>
>One should not have to remember the details - they should be clear by
>reading the specs :)

I agree, however the specs often lack the rationale behind
the agreed design choices. So even if you see something has
specified in a certain way, in some cases you will have hard
time understanding why, unless you dig into the email archives.

>>My question is still: if the REGISTER contains instance-id AND
>>Require:gruu, is a gruu generated?

>Since reg-id isn't mentioned in gruu, its irrelevant to the gruu spec,
>just as any other parameters are.

Right. Registrar compliant to the GRUU spec will create gruu
when it sees the Contact header field in the REGISTER message to
contain a "+sip.instance" header field parameter. The registrar
does not need to understand other parameters specified in Outbound
spec. I admit it is a bit confusing to use the same parameter in
two different specs that should be orthogonal, but it just happens
to be the specified behaviour.

>So, what is the justification for generating a gruu, but not returning
>it (after all, the gruu will be sent to the UA if it registers to the
>regevent package, so...)??? 

I also raised this question in march 2007 while reviewing GRUU spec
and received an answer from Paul Kyzivat, who had a point:

Erkki.Koivusalo@nokia.com wrote:
> Hi Jonathan,
> 
> GRUU draft tells the registrar to create a public GRUU and a
> temporary GRUU whenever it receives a REGISTER request with
> "+sip.instance" Contact header parameter but only return
> them is the REGISTER request contains Supported: gruu.
> 
> Does this make any sense ? Why would the registrar have to
> create those GRUUs if it would not return them to the UA ?
> 
> The use case I am thinking is:
> 
> - A registrar which supports both GRUU and Outbound 
> - An UA which supports Outbound but not GRUU
> 
> Such an UA would send its Contact header with "+sip.instance"
> parameter but it would not include Supported: gruu in its
> REGISTER. Strictly speaking GRUU draft currently tells
> the registrar to create GRUUs but not to return them to 
> the UA.
> 
> I would assume GRUU draft needs a small fix to tell the
> registrar to create the GRUUs only if the REGISTER
> request contains "gruu" option tag in Supported header.
> 
> Do you agree or have I missed something ?

This is partially one of those questions like "does a tree that falls 
make any noise if nobody is listening?"

If in fact nobody will learn about this gruu then there is no need to 
create it. But that is all about the difference between the conceptual 
model and the implementation, so it doesn't need to be stated.

The problem arises when there are multiple observers of registration 
state. There are at least two ways this can happen:
- other UAs that register
- subscribers to the reg event package

After you register, if others register they will get your contact back 
in the response to their register request, along with their own. If they

support gruu, then they will will see the permanent gruu and latest temp

gruu for your contact.

Similarly, when you register, any subscribers to the reg event package 
will get a notify telling of the change in registration state, including

your contact and the gruus that were "assigned" to you.

Everything hangs together better this way. Still, if nobody is looking 
you don't have to assign these, as long as you do assign them when 
somebody does start looking.

	Paul
--

Perhaps this could have been worth mentioning in the GRUU spec.

>I think that the outbound spec should clarify that the 
>instance-id, when used with outbound, will also create 
>a gruu, according to the rules in the gruu-spec.

I understand the point that Outbound spec should actually NOT
talk about creation of gruus, as that is the task of GRUU spec.
However Outbound refers to GRUU spec twice, so what about 
modifying the note within section 6 as like this:

   A Contact header field value with an instance-id media feature tag
   but no reg-id header field parameter is valid (this combination can
   be used in the GRUU [I-D.ietf-sip-gruu] specification as creation
   of gruu is not dependent on the presence or absence of reg-id 
   parameter), but one with a reg-id but no instance-id is not.  

Regards,

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


From sip-bounces@ietf.org  Mon Oct 13 23:16:43 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B22DF3A6BB2;
	Mon, 13 Oct 2008 23:16:43 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A9F9728C0EA
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 23:16:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.196
X-Spam-Level: 
X-Spam-Status: No, score=-6.196 tagged_above=-999 required=5 tests=[AWL=0.053, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id DOt2cA7obMQv for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 23:16:41 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 7C6283A6BB2
	for <sip@ietf.org>; Mon, 13 Oct 2008 23:16:41 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	CC81E20DAA; Tue, 14 Oct 2008 08:17:19 +0200 (CEST)
X-AuditID: c1b4fb3c-ad8cdbb0000015b5-85-48f4396ffa3c
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	A486620052; Tue, 14 Oct 2008 08:17:19 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 14 Oct 2008 08:17:08 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 14 Oct 2008 08:17:08 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0864D052@esealmw113.eemea.ericsson.se>
In-Reply-To: <7A726F54F791494C8D8C87F13736E80EF52279@vaebe106.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Is GRUU generated in the case of registration
	withinstance-ID and reg-ID
Thread-Index: AcktB1xjBie2koRPTuygIDgnFDKCHAAVOQXAABh04SAAATzCcA==
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com><CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se><48F23D27.8030305@voip.co.uk><CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se><48F2FC13.1070308@voip.co.uk>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8ED@esealmw113.eemea.ericsson.se>
	<7A726F54F791494C8D8C87F13736E80EF52279@vaebe106.NOE.Nokia.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: <Erkki.Koivusalo@nokia.com>,
	<michael@voip.co.uk>
X-OriginalArrivalTime: 14 Oct 2008 06:17:08.0750 (UTC)
	FILETIME=[7CCE3AE0:01C92DC4]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, audet@nortel.com
Subject: Re: [Sip] Is GRUU generated in the case of registration
	withinstance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi Erkki, 

>>>Its been a long time, and the details are starting to get fuzzy in my
mind.
>>
>>One should not have to remember the details - they should be clear by
reading the specs :)
>
>I agree, however the specs often lack the rationale behind the agreed
design choices. So even if you see something has specified in a certain 
>way, in some cases you will have hard time understanding why, unless
you dig into the email archives.

It is not about the rationale - but to understand the spec :)



>>So, what is the justification for generating a gruu, but not returning
it (after all, the gruu will be sent to the UA if it registers to the 
>>regevent package, so...)???
>
>I also raised this question in march 2007 while reviewing GRUU spec and
received an answer from Paul Kyzivat, who had a point:
>
> GRUU draft tells the registrar to create a public GRUU and a temporary

> GRUU whenever it receives a REGISTER request with "+sip.instance" 
> Contact header parameter but only return them is the REGISTER request 
> contains Supported: gruu.
> 
> Does this make any sense ? Why would the registrar have to create 
> those GRUUs if it would not return them to the UA ?
> 
> The use case I am thinking is:
> 
> - A registrar which supports both GRUU and Outbound
> - An UA which supports Outbound but not GRUU
> 
> Such an UA would send its Contact header with "+sip.instance"
> parameter but it would not include Supported: gruu in its REGISTER. 
> Strictly speaking GRUU draft currently tells the registrar to create 
> GRUUs but not to return them to the UA.
> 
> I would assume GRUU draft needs a small fix to tell the registrar to 
> create the GRUUs only if the REGISTER request contains "gruu" option 
> tag in Supported header.
> 
> Do you agree or have I missed something ?
>
>This is partially one of those questions like "does a tree that falls
make any noise if nobody is listening?"
>
>If in fact nobody will learn about this gruu then there is no need to
create it. But that is all about the difference between the conceptual 
>model and the implementation, so it doesn't need to be stated.
>
>The problem arises when there are multiple observers of registration
state. There are at least two ways this can happen:
>- other UAs that register
>- subscribers to the reg event package
>
>After you register, if others register they will get your contact back
in the response to their register request, along with their own. If 
>they support gruu, then they will will see the permanent gruu and
latest temp gruu for your contact.
>
>Similarly, when you register, any subscribers to the reg event package
will get a notify telling of the change in registration state, 
>including your contact and the gruus that were "assigned" to you.
>
>Everything hangs together better this way. Still, if nobody is looking
you don't have to assign these, as long as you do assign them when 
>somebody does start looking.

If I don't support gruu, but I register to the regevent package, I WILL
hear the tree falling, because I will receive the gruu in the NOTIFY :)

Regards,

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


From sip-bounces@ietf.org  Mon Oct 13 23:16:56 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 799F128C127;
	Mon, 13 Oct 2008 23:16:56 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F2A9628C139
	for <sip@core3.amsl.com>; Mon, 13 Oct 2008 23:16:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.897
X-Spam-Level: 
X-Spam-Status: No, score=-5.897 tagged_above=-999 required=5
	tests=[AWL=-0.248, BAYES_00=-2.599, HELO_EQ_SE=0.35,
	J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OCWANBlc4iMy for <sip@core3.amsl.com>;
	Mon, 13 Oct 2008 23:16:54 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id ED8DA3A6BE4
	for <sip@ietf.org>; Mon, 13 Oct 2008 23:16:53 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	E0EED21088; Tue, 14 Oct 2008 08:17:39 +0200 (CEST)
X-AuditID: c1b4fb3e-a8e85bb000007a96-a8-48f439834ef3
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	A4CFF2107F; Tue, 14 Oct 2008 08:17:39 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 14 Oct 2008 08:17:30 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 14 Oct 2008 08:17:30 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0864D054@esealmw113.eemea.ericsson.se>
In-Reply-To: <48F3B002.6000201@voip.co.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: VS: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
Thread-Index: AcktcpdSO2WUa+eWRP+K0PBBxsZVYQASnSKA
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>
	<48F23D27.8030305@voip.co.uk>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se>
	<48F2FC13.1070308@voip.co.uk>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8ED@esealmw113.eemea.ericsson.se>
	<48F3A3EA.4050307@voip.co.uk>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F3@esealmw113.eemea.ericsson.se>
	<48F3B002.6000201@voip.co.uk>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Michael Procter" <michael@voip.co.uk>
X-OriginalArrivalTime: 14 Oct 2008 06:17:30.0515 (UTC)
	FILETIME=[89C74E30:01C92DC4]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, Francois Audet <audet@nortel.com>
Subject: Re: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>>Or, if I want the gruu returned, and I want to mandate the registrar
to support gruu, do I have to send:
>>>
>>>Instance-id AND Supported:gruu AND Require:gruu
>>  
>>
>GRUU draft, section 4.1 (extract from last paragraph):
>
>"If a UA wishes to guarantee that the REGISTER request is not processed
unless the domain supports and uses this extension, it MAY include a 
>Require header field in the request with a value that contains the
"gruu" option tag. This is in addition to the presence of the Supported 
>header field also containing the "gruu" option tag."
>
>So it looks like you need all three: +sip.instance, Require:gruu and
Supported: gruu.

I guess the text could say that "This is in addition to the presence of
the Supported header IF THE UA WANTS THE REGISTRAR TO RETURN THE GRUU." 

Because, the gruu itself will be created even without the Supported
header.

I am not sure that we before have defined a mechanism where an
option-tag may have to be present in BOTH the Require and Supported
header, so that is why I think the text needs to be really clear.

Thanks!

Regards,

Christer

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


From sip-bounces@ietf.org  Tue Oct 14 05:17:53 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 152F828C132;
	Tue, 14 Oct 2008 05:17:53 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E558B3A6BBB
	for <sip@core3.amsl.com>; Tue, 14 Oct 2008 05:17:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5
	tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_74=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nJ12hUGEDmp4 for <sip@core3.amsl.com>;
	Tue, 14 Oct 2008 05:17:50 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 996CA3A6BB8
	for <sip@ietf.org>; Tue, 14 Oct 2008 05:17:50 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,409,1220227200"; d="scan'208";a="24170128"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 14 Oct 2008 12:18:02 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9ECI3RD022265; 
	Tue, 14 Oct 2008 08:18:03 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9ECI25A027694;
	Tue, 14 Oct 2008 12:18:02 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 14 Oct 2008 08:18:02 -0400
Received: from [10.86.251.129] ([10.86.251.129]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 14 Oct 2008 08:18:02 -0400
Message-ID: <48F48DF9.1000705@cisco.com>
Date: Tue, 14 Oct 2008 08:18:01 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Erkki.Koivusalo@nokia.com
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com><CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se><48F23D27.8030305@voip.co.uk><CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se><48F2FC13.1070308@voip.co.uk>	<CA9998CD4A020D418654FCDEF4E707DF05C0F8ED@esealmw113.eemea.ericsson.se>
	<7A726F54F791494C8D8C87F13736E80EF52279@vaebe106.NOE.Nokia.com>
In-Reply-To: <7A726F54F791494C8D8C87F13736E80EF52279@vaebe106.NOE.Nokia.com>
X-OriginalArrivalTime: 14 Oct 2008 12:18:02.0547 (UTC)
	FILETIME=[E7797030:01C92DF6]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5169; t=1223986683;
	x=1224850683; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Is=20GRUU=20generated=20in=20th
	e=20case=20of=20registration=09withinstance-ID=0A=20and=20re
	g-ID |Sender:=20 |To:=20Erkki.Koivusalo@nokia.com;
	bh=DXLpSbxo8bTOpRxoUDF+6TU6PqdteOd8DtDjwPy0/2s=;
	b=QmV9f9DTaj4PkmCePQ7VdyzCeFExx5daiNgFtDyEPybE8u0tetU3QL/RdE
	cGsIAIwu0WuzfWats2e9xu3kyG0dDBPaFdH1b1x2TZ9Vecc9sDkZEuhx8I4T
	pC4rghHB4f;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: sip@ietf.org, audet@nortel.com, christer.holmberg@ericsson.com
Subject: Re: [Sip] Is GRUU generated in the case of
 registration	withinstance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

The reason outbound and gruu are using the same instance-id is that both 
uses share the same definition of the concept of a UA instance.

	Thanks,
	Paul

Erkki.Koivusalo@nokia.com wrote:
> Hi, 
> 
>>> Its been a long time, and the details are starting to get fuzzy in my
>> mind.
>>
>> One should not have to remember the details - they should be clear by
>> reading the specs :)
> 
> I agree, however the specs often lack the rationale behind
> the agreed design choices. So even if you see something has
> specified in a certain way, in some cases you will have hard
> time understanding why, unless you dig into the email archives.
> 
>>> My question is still: if the REGISTER contains instance-id AND
>>> Require:gruu, is a gruu generated?
> 
>> Since reg-id isn't mentioned in gruu, its irrelevant to the gruu spec,
>> just as any other parameters are.
> 
> Right. Registrar compliant to the GRUU spec will create gruu
> when it sees the Contact header field in the REGISTER message to
> contain a "+sip.instance" header field parameter. The registrar
> does not need to understand other parameters specified in Outbound
> spec. I admit it is a bit confusing to use the same parameter in
> two different specs that should be orthogonal, but it just happens
> to be the specified behaviour.
> 
>> So, what is the justification for generating a gruu, but not returning
>> it (after all, the gruu will be sent to the UA if it registers to the
>> regevent package, so...)??? 
> 
> I also raised this question in march 2007 while reviewing GRUU spec
> and received an answer from Paul Kyzivat, who had a point:
> 
> Erkki.Koivusalo@nokia.com wrote:
>> Hi Jonathan,
>>
>> GRUU draft tells the registrar to create a public GRUU and a
>> temporary GRUU whenever it receives a REGISTER request with
>> "+sip.instance" Contact header parameter but only return
>> them is the REGISTER request contains Supported: gruu.
>>
>> Does this make any sense ? Why would the registrar have to
>> create those GRUUs if it would not return them to the UA ?
>>
>> The use case I am thinking is:
>>
>> - A registrar which supports both GRUU and Outbound 
>> - An UA which supports Outbound but not GRUU
>>
>> Such an UA would send its Contact header with "+sip.instance"
>> parameter but it would not include Supported: gruu in its
>> REGISTER. Strictly speaking GRUU draft currently tells
>> the registrar to create GRUUs but not to return them to 
>> the UA.
>>
>> I would assume GRUU draft needs a small fix to tell the
>> registrar to create the GRUUs only if the REGISTER
>> request contains "gruu" option tag in Supported header.
>>
>> Do you agree or have I missed something ?
> 
> This is partially one of those questions like "does a tree that falls 
> make any noise if nobody is listening?"
> 
> If in fact nobody will learn about this gruu then there is no need to 
> create it. But that is all about the difference between the conceptual 
> model and the implementation, so it doesn't need to be stated.
> 
> The problem arises when there are multiple observers of registration 
> state. There are at least two ways this can happen:
> - other UAs that register
> - subscribers to the reg event package
> 
> After you register, if others register they will get your contact back 
> in the response to their register request, along with their own. If they
> 
> support gruu, then they will will see the permanent gruu and latest temp
> 
> gruu for your contact.
> 
> Similarly, when you register, any subscribers to the reg event package 
> will get a notify telling of the change in registration state, including
> 
> your contact and the gruus that were "assigned" to you.
> 
> Everything hangs together better this way. Still, if nobody is looking 
> you don't have to assign these, as long as you do assign them when 
> somebody does start looking.
> 
> 	Paul
> --
> 
> Perhaps this could have been worth mentioning in the GRUU spec.
> 
>> I think that the outbound spec should clarify that the 
>> instance-id, when used with outbound, will also create 
>> a gruu, according to the rules in the gruu-spec.
> 
> I understand the point that Outbound spec should actually NOT
> talk about creation of gruus, as that is the task of GRUU spec.
> However Outbound refers to GRUU spec twice, so what about 
> modifying the note within section 6 as like this:
> 
>    A Contact header field value with an instance-id media feature tag
>    but no reg-id header field parameter is valid (this combination can
>    be used in the GRUU [I-D.ietf-sip-gruu] specification as creation
>    of gruu is not dependent on the presence or absence of reg-id 
>    parameter), but one with a reg-id but no instance-id is not.  
> 
> Regards,
> 
> Erkki
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Tue Oct 14 07:43:14 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 495333A6B2F;
	Tue, 14 Oct 2008 07:43:14 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 135793A6C01
	for <sip@core3.amsl.com>; Tue, 14 Oct 2008 07:43:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tCxM4eB7eZ-J for <sip@core3.amsl.com>;
	Tue, 14 Oct 2008 07:43:04 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6])
	by core3.amsl.com (Postfix) with ESMTP id D79673A6B2F
	for <sip@ietf.org>; Tue, 14 Oct 2008 07:43:03 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com
	(216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.291.1;
	Tue, 14 Oct 2008 10:40:48 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail.acmepacket.com
	([216.41.24.7]) with mapi; Tue, 14 Oct 2008 10:40:47 -0400
From: Bob Penfield <BPenfield@acmepacket.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Juha Heinanen
	<jh@tutpro.com>, "sip@ietf.org" <sip@ietf.org>, Paul Kyzivat
	<pkyzivat@cisco.com>, Dean Willis <dean.willis@softarmor.com>
Date: Tue, 14 Oct 2008 10:40:45 -0400
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackta1Q4oPZYeoZEQAiUqa8JyoYU4gAAB04gACPIDEA=
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18668.50247.121832.271341@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se><18668.51383.505850.963592@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se><18672.19846.621765.332209@taimen.test.fi><2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com><18673.5665.337048.880648@taimen.test.fi><2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com><18673.62485.295631.933830@taimen.test.fi><2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com><18675.7684.207071.901832@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se><18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

For both GRUU and Outbound a given instance-id (+sip-instance) actually represents a single UA contact instance rather than just a single User Agent. The basic idea behind GRUU is that a request addressed to a GRUU is forwarded by the proxy to a specific Contact address. The goal is the same with Outbound but it adds multiple flows/paths to that UA Contact. This is reflected in the proxy procedures in both GRUU and Outbound.

In both cases, the proxy does serial forking to Contacts with the same instance-id.

For GRUU it starts with the most-recently registered binding (according to section 6.1 of GRUU):

       The proxy MUST select the most recently refreshed
       contact.  As with draft-ietf-sip-outbound, if a request to this
       target fails with a 408 (Request Timeout) or 430 (Flow Failed)
       response, the proxy SHOULD retry with the next most recently
       refreshed contact.  Furthermore, if the request fails with any
       other response, the proxy MUST NOT retry on any other contacts
       for this instance.

For Outbound, it attempts the registered flows (according to section 7 of Outbound):

   When a proxy uses the location service to look up a registration
   binding and then proxies a request to a particular contact, it
   selects a contact to use normally, with a few additional rules:

   o  The proxy MUST NOT populate the target set with more than one
      contact with the same AOR and instance-id at a time.
   o  If a request for a particular AOR and instance-id fails with a 430
      (Flow Failed) response, the proxy SHOULD replace the failed branch
      with another target (if one is available) with the same AOR and
      instance-id, but a different reg-id.
   o  If the proxy receives a final response from a branch other than a
      408 (Request Timeout) or a 430 (Flow Failed) response, the proxy
      MUST NOT forward the same request to another target representing
      the same AOR and instance-id.  The targeted instance has already
      provided its response.

Therefore, a User Agent that is registering multiple Contacts to allow the possibility of parallel forking would need to have a separate instance-id for each Contact.

For User Agent's that have multiple interfaces, it could use the MAC address of each interface to create a unique UUID URN for each contact.

Thus, the following scenario is possible:

  UA_Contact_wlan;+sip-instance=ID_1;reg-id=1 ----- OB_1 ----- REG_1
  UA_Contact_wlan;+sip-instance=ID_1;reg-id=2 ----- OB_2 ----- REG_2
  UA_Contact_3g;+sip-instance=ID_2;reg-id=1   ----- OB_1 ----- REG_1
  UA_Contact_3g;+sip-instance=ID_2;reg-id=2   ----- OB_2 ----- REG_2

Unfortunately, the current text in section 4.1 says that a UA has "an Instance Identifier".

cheers,
(-:bob

-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of Christer Holmberg
Sent: Monday, October 13, 2008 3:45 PM
To: Juha Heinanen; sip@ietf.org; Paul Kyzivat; Dean Willis
Subject: Re: [Sip] Dual registration without Outbound


Hi,

>>the proxy does not, but i don't want to complicate
>>configuration of the UA simply in order to cope with the
>>brain damage of ob draft.  also, don't want that the UA
>>has to send two invites for one contact each.
>
>typo: i don't want that the UA has to send two REGISTERs for
>one contact each.  that is, UA must be able to register both
>of its contacts in a single register request.

You will still have to send a REGISTER for each flow that you establish
- no matter whether you use the same contact/instance-id or not.

Or, do you also want to change outbound so that you can establish
multiple flows with a single REGISTER?

Regards,

Christer

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


From sip-bounces@ietf.org  Tue Oct 14 08:05:42 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8165228C1DD;
	Tue, 14 Oct 2008 08:05:42 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9C8A83A6C06
	for <sip@core3.amsl.com>; Tue, 14 Oct 2008 08:05:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.572
X-Spam-Level: 
X-Spam-Status: No, score=-2.572 tagged_above=-999 required=5 tests=[AWL=0.027, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XtuCBEwUSlaM for <sip@core3.amsl.com>;
	Tue, 14 Oct 2008 08:05:35 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id DC6983A6C08
	for <sip@ietf.org>; Tue, 14 Oct 2008 08:05:34 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K8Q00L4PHRYS7@siemenscomms.co.uk> for sip@ietf.org; Tue,
	14 Oct 2008 16:02:22 +0100 (BST)
Date: Tue, 14 Oct 2008 16:02:23 +0100
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
To: Bob Penfield <BPenfield@acmepacket.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>,
	Juha Heinanen <jh@tutpro.com>, sip@ietf.org,
	Paul Kyzivat <pkyzivat@cisco.com>, Dean Willis <dean.willis@softarmor.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D0012A2353@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackta1Q4oPZYeoZEQAiUqa8JyoYU4gAAB04gACPIDEAABL7/QA==
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18668.50247.121832.271341@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
	<18668.51383.505850.963592@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
	<18673.5665.337048.880648@taimen.test.fi>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Bob Penfield
> Sent: 14 October 2008 15:41
> To: Christer Holmberg; Juha Heinanen; sip@ietf.org; Paul 
> Kyzivat; Dean Willis
> Subject: Re: [Sip] Dual registration without Outbound
> 
> For both GRUU and Outbound a given instance-id 
> (+sip-instance) actually represents a single UA contact 
> instance rather than just a single User Agent. The basic idea 
> behind GRUU is that a request addressed to a GRUU is 
> forwarded by the proxy to a specific Contact address. The 
> goal is the same with Outbound but it adds multiple 
> flows/paths to that UA Contact. This is reflected in the 
> proxy procedures in both GRUU and Outbound.
> 
> In both cases, the proxy does serial forking to Contacts with 
> the same instance-id.
> 
> For GRUU it starts with the most-recently registered binding 
> (according to section 6.1 of GRUU):
> 
>        The proxy MUST select the most recently refreshed
>        contact.  As with draft-ietf-sip-outbound, if a request to this
>        target fails with a 408 (Request Timeout) or 430 (Flow Failed)
>        response, the proxy SHOULD retry with the next most recently
>        refreshed contact.  Furthermore, if the request fails with any
>        other response, the proxy MUST NOT retry on any other contacts
>        for this instance.
> 
> For Outbound, it attempts the registered flows (according to 
> section 7 of Outbound):
> 
>    When a proxy uses the location service to look up a registration
>    binding and then proxies a request to a particular contact, it
>    selects a contact to use normally, with a few additional rules:
> 
>    o  The proxy MUST NOT populate the target set with more than one
>       contact with the same AOR and instance-id at a time.
>    o  If a request for a particular AOR and instance-id fails 
> with a 430
>       (Flow Failed) response, the proxy SHOULD replace the 
> failed branch
>       with another target (if one is available) with the same AOR and
>       instance-id, but a different reg-id.
>    o  If the proxy receives a final response from a branch 
> other than a
>       408 (Request Timeout) or a 430 (Flow Failed) response, the proxy
>       MUST NOT forward the same request to another target representing
>       the same AOR and instance-id.  The targeted instance has already
>       provided its response.
> 
> Therefore, a User Agent that is registering multiple Contacts 
> to allow the possibility of parallel forking would need to 
> have a separate instance-id for each Contact.
> 
> For User Agent's that have multiple interfaces, it could use 
> the MAC address of each interface to create a unique UUID URN 
> for each contact.
> 
> Thus, the following scenario is possible:
> 
>   UA_Contact_wlan;+sip-instance=ID_1;reg-id=1 ----- OB_1 ----- REG_1
>   UA_Contact_wlan;+sip-instance=ID_1;reg-id=2 ----- OB_2 ----- REG_2
>   UA_Contact_3g;+sip-instance=ID_2;reg-id=1   ----- OB_1 ----- REG_1
>   UA_Contact_3g;+sip-instance=ID_2;reg-id=2   ----- OB_2 ----- REG_2
> 
> Unfortunately, the current text in section 4.1 says that a UA 
> has "an Instance Identifier".
[JRE] In an earlier email I was trying to say roughly the same thing,
except the way I looked at it was that a device with multiple interfaces
would logically contain a UA for each interface, and each UA would than
have a single instance ID. In that case the text in section 4.1 still
works.

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


From sip-bounces@ietf.org  Tue Oct 14 10:19:40 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 200553A6849;
	Tue, 14 Oct 2008 10:19:40 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DA0333A6849
	for <sip@core3.amsl.com>; Tue, 14 Oct 2008 10:19:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id NZ-seyrtaCA1 for <sip@core3.amsl.com>;
	Tue, 14 Oct 2008 10:19:37 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56])
	by core3.amsl.com (Postfix) with ESMTP id A6B353A683A
	for <sip@ietf.org>; Tue, 14 Oct 2008 10:19:37 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	m9EHGaK00900; Tue, 14 Oct 2008 17:16:36 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 14 Oct 2008 12:19:00 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF19BAB943@zrc2hxm0.corp.nortel.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF0864CEFC@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
Thread-Index: Ackthpxe2j+IIv2ATNuWao7mqiLjvAANMqTQABlcJkA=
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>
	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>
	<48F23D27.8030305@voip.co.uk>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se>
	<48F2FC13.1070308@voip.co.uk> <48F34E3B.80106@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EE@esealmw113.eemea.ericsson.se>
	<48F3D191.5000007@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0864CEFC@esealmw113.eemea.ericsson.se>
From: "Francois Audet" <audet@nortel.com>
To: "Christer Holmberg" <christer.holmberg@ericsson.com>,
	"Paul Kyzivat" <pkyzivat@cisco.com>
Cc: sip@ietf.org
Subject: Re: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Can you propose actual text for a specific section. 

> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] 
> Sent: Monday, October 13, 2008 22:13
> To: Paul Kyzivat
> Cc: Michael Procter; sip@ietf.org; Audet, Francois (SC100:3055)
> Subject: RE: [Sip] Is GRUU generated in the case of 
> registration with instance-ID and reg-ID
> 
> 
> Hi, 
> 
> >>Yes. The question was whether instance-id AND reg-id also create a
> gruu.
> >>The answer seems to be yes, but I think it would be good to clarify 
> >>that somewhere.
> >
> >Since reg-id isn't mentioned in gruu, its irrelevant to the 
> gruu spec,
> just as any other parameters are.
> 
> That is why I proposed it is clarified in the outbound spec :)
> 
> Regards,
> 
> Christer
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Tue Oct 14 10:38:49 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8CA173A6BA6;
	Tue, 14 Oct 2008 10:38:49 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0399A3A6BA6
	for <sip@core3.amsl.com>; Tue, 14 Oct 2008 10:38:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2ap6vwNdU7u9 for <sip@core3.amsl.com>;
	Tue, 14 Oct 2008 10:38:44 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6])
	by core3.amsl.com (Postfix) with ESMTP id AF9FE3A6B51
	for <sip@ietf.org>; Tue, 14 Oct 2008 10:38:43 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com
	(216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.291.1;
	Tue, 14 Oct 2008 13:38:00 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail.acmepacket.com
	([216.41.24.7]) with mapi; Tue, 14 Oct 2008 13:37:59 -0400
From: Bob Penfield <BPenfield@acmepacket.com>
To: "Elwell, John" <john.elwell@siemens.com>, Christer Holmberg
	<christer.holmberg@ericsson.com>, Juha Heinanen <jh@tutpro.com>,
	"sip@ietf.org" <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Date: Tue, 14 Oct 2008 13:37:57 -0400
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackta1Q4oPZYeoZEQAiUqa8JyoYU4gAAB04gACPIDEAABL7/QAAE9WcQ
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC312843F60B4@mail.acmepacket.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18668.50247.121832.271341@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
	<18668.51383.505850.963592@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
	<18673.5665.337048.880648@taimen.test.fi>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0012A2353@GBNTHT12009MSX.gb002.siemens.net>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D0012A2353@GBNTHT12009MSX.gb002.siemens.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I guess the problem arises when you want to do a single REGISTER request for both instances. If I the use case correctly, the UA would send two REGISTER requests (one on each interface) and both REGISTERs would have the two Contacts (one for each instance-id). Something like this:

First REGISTER to Outbound-proxy #1

   REGISTER sip:example.com SIP/2.0
   Via: SIP/2.0/TCP 1.1.1.1;branch=z9hG4bKnashds7-1
   From: Bob <sip:bob@example.com>;tag=7F94778B653B-1
   To: Bob <sip:bob@example.com>
   Call-ID: 16CB75F21C70-1
   CSeq: 1 REGISTER
   Supported: path, outbound
   Route: <sip:ep1.example.com;lr>
   Contact: <sip:bob@1.1.1.1;transport=tcp>;reg-id=1
    ;+sip.instance="<urn:uuid:00000000-0000-1000-8000-AABBCCDDEEFF>"
   Contact: <sip:bob@2.2.2.2;transport=tcp>;reg-id=2
    ;+sip.instance="<urn:uuid:00000000-0000-1000-8000-BBCCDDEEFF00>"

Second REGISTER to Outbound-proxy #2

   REGISTER sip:example.com SIP/2.0
   Via: SIP/2.0/TCP 2.2.2.2;branch=z9hG4bKnashds7-2
   From: Bob <sip:bob@example.com>;tag=7F94778B653B-2
   To: Bob <sip:bob@example.com>
   Call-ID: 16CB75F21C70-2
   CSeq: 1 REGISTER
   Supported: path, outbound
   Route: <sip:ep2.example.com;lr>
   Contact: <sip:bob@2.2.2.2;transport=tcp>;reg-id=1
    ;+sip.instance="<urn:uuid:00000000-0000-1000-8000-BBCCDDEEFF00>"
   Contact: <sip:bob@1.1.1.1;transport=tcp>;reg-id=2
    ;+sip.instance="<urn:uuid:00000000-0000-1000-8000-AABBCCDDEEFF>"

Thus the UA could receive requests for either Contact on either of the two outbound flows.

Is having two UA instances in the same request legal with the current text?

cheers,
(-:bob

-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens.com]
Sent: Tuesday, October 14, 2008 11:02 AM
To: Bob Penfield; Christer Holmberg; Juha Heinanen; sip@ietf.org; Paul Kyzivat; Dean Willis
Subject: RE: [Sip] Dual registration without Outbound



> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
> Behalf Of Bob Penfield
> Sent: 14 October 2008 15:41
> To: Christer Holmberg; Juha Heinanen; sip@ietf.org; Paul
> Kyzivat; Dean Willis
> Subject: Re: [Sip] Dual registration without Outbound
>
> For both GRUU and Outbound a given instance-id
> (+sip-instance) actually represents a single UA contact
> instance rather than just a single User Agent. The basic idea
> behind GRUU is that a request addressed to a GRUU is
> forwarded by the proxy to a specific Contact address. The
> goal is the same with Outbound but it adds multiple
> flows/paths to that UA Contact. This is reflected in the
> proxy procedures in both GRUU and Outbound.
>
> In both cases, the proxy does serial forking to Contacts with
> the same instance-id.
>
> For GRUU it starts with the most-recently registered binding
> (according to section 6.1 of GRUU):
>
>        The proxy MUST select the most recently refreshed
>        contact.  As with draft-ietf-sip-outbound, if a request to this
>        target fails with a 408 (Request Timeout) or 430 (Flow Failed)
>        response, the proxy SHOULD retry with the next most recently
>        refreshed contact.  Furthermore, if the request fails with any
>        other response, the proxy MUST NOT retry on any other contacts
>        for this instance.
>
> For Outbound, it attempts the registered flows (according to
> section 7 of Outbound):
>
>    When a proxy uses the location service to look up a registration
>    binding and then proxies a request to a particular contact, it
>    selects a contact to use normally, with a few additional rules:
>
>    o  The proxy MUST NOT populate the target set with more than one
>       contact with the same AOR and instance-id at a time.
>    o  If a request for a particular AOR and instance-id fails
> with a 430
>       (Flow Failed) response, the proxy SHOULD replace the
> failed branch
>       with another target (if one is available) with the same AOR and
>       instance-id, but a different reg-id.
>    o  If the proxy receives a final response from a branch
> other than a
>       408 (Request Timeout) or a 430 (Flow Failed) response, the proxy
>       MUST NOT forward the same request to another target representing
>       the same AOR and instance-id.  The targeted instance has already
>       provided its response.
>
> Therefore, a User Agent that is registering multiple Contacts
> to allow the possibility of parallel forking would need to
> have a separate instance-id for each Contact.
>
> For User Agent's that have multiple interfaces, it could use
> the MAC address of each interface to create a unique UUID URN
> for each contact.
>
> Thus, the following scenario is possible:
>
>   UA_Contact_wlan;+sip-instance=ID_1;reg-id=1 ----- OB_1 ----- REG_1
>   UA_Contact_wlan;+sip-instance=ID_1;reg-id=2 ----- OB_2 ----- REG_2
>   UA_Contact_3g;+sip-instance=ID_2;reg-id=1   ----- OB_1 ----- REG_1
>   UA_Contact_3g;+sip-instance=ID_2;reg-id=2   ----- OB_2 ----- REG_2
>
> Unfortunately, the current text in section 4.1 says that a UA
> has "an Instance Identifier".
[JRE] In an earlier email I was trying to say roughly the same thing,
except the way I looked at it was that a device with multiple interfaces
would logically contain a UA for each interface, and each UA would than
have a single instance ID. In that case the text in section 4.1 still
works.

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


From sip-bounces@ietf.org  Tue Oct 14 10:46:22 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CC2BE3A6874;
	Tue, 14 Oct 2008 10:46:22 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DEC493A6874
	for <sip@core3.amsl.com>; Tue, 14 Oct 2008 10:46:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.299
X-Spam-Level: 
X-Spam-Status: No, score=-0.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MANGLED_SAVELE=2.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LVslYX2eEvCt for <sip@core3.amsl.com>;
	Tue, 14 Oct 2008 10:46:21 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.152])
	by core3.amsl.com (Postfix) with ESMTP id 7673C3A63EC
	for <sip@ietf.org>; Tue, 14 Oct 2008 10:46:21 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id d23so1578810fga.41
	for <sip@ietf.org>; Tue, 14 Oct 2008 10:46:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:mime-version
	:content-transfer-encoding:message-id:content-type:to:from:subject
	:date:x-mailer;
	bh=RqznbGLJJyVFkt0krewab2KOHE9Y6w3V6ga/F0AOlOM=;
	b=VJCrUMEQbOESt4j5yGh7U8fxdjTY19LpheIEzhAciIbnFY93NczQ3Z82dxhhB5Skt3
	Py9BWsE0uB12/e8z8C6ZOyGWNbLF/vEn5xkdvdJBnZGQAlGwWHjhB/gkKIWLbQX/FKc3
	bQKbg8m2dXht0GVGxh/EuI4FWA8jnQTYR4HzE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:content-transfer-encoding:message-id:content-type:to
	:from:subject:date:x-mailer;
	b=V2ZVD56Zc0fQC1c1AX6jYBNztJSGi41xoazdsZzd7qawJ5cOQe7n2gHshZr4cNEBOp
	jjRZByKD69vWIiFdi7FYXg706Em9QuPFR6rdQnnfI2lnRNu7IMSoNQhRlEii8TFqmVSz
	OfWigcN4i2EiPXgemRds4HM/N89WXZSGO8tsQ=
Received: by 10.181.56.3 with SMTP id i3mr6128009bkk.35.1224005780194;
	Tue, 14 Oct 2008 10:36:20 -0700 (PDT)
Received: from ?135.207.21.114? (H-135-207-21-114.research.att.com
	[135.207.21.114])
	by mx.google.com with ESMTPS id k5sm42575689nfh.0.2008.10.14.10.36.19
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Tue, 14 Oct 2008 10:36:19 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <47FFBA6A-AFE9-4894-9DF7-01F1557324FC@gmail.com>
To: sip@ietf.org,
 sipping@ietf.org
From: Pamela Zave <pamelazave@gmail.com>
Date: Tue, 14 Oct 2008 13:21:52 -0400
X-Mailer: Apple Mail (2.753.1)
Subject: [Sip] INVITE dialogs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

At the suggestion of Paul Kyzivat and Dale Worley, I compared

draft-ietf-sipping-race-examples-06.txt

to the basic Spin model of INVITE dialogs at

http://www.research.att.com/~pamela/sip.html.

Of the 13 race conditions in the sipping draft, 6 of them are out of  
the scope of the Spin model.  Most commonly, this is because they  
include retransmission of a lost message.  There are no transmission  
failures in the Spin model.

Of the remaining 7, all of them are in the Spin model, handled the  
same way.

In addition, the Spin model shows 42 additional race conditions.   
This count is subject to a lot of interpretation, so I estimate a  
possible error of about 20%.

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


From sip-bounces@ietf.org  Tue Oct 14 22:30:10 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8D2323A6BD7;
	Tue, 14 Oct 2008 22:30:10 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E638E3A6BD7
	for <sip@core3.amsl.com>; Tue, 14 Oct 2008 22:30:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.567
X-Spam-Level: 
X-Spam-Status: No, score=-1.567 tagged_above=-999 required=5 tests=[AWL=0.038, 
	BAYES_00=-2.599, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id f-tSxxc3Fcaj for <sip@core3.amsl.com>;
	Tue, 14 Oct 2008 22:30:07 -0700 (PDT)
Received: from gws03.hcl.in (chn-hclin-gws01.hcl.in [203.105.186.19])
	by core3.amsl.com (Postfix) with ESMTP id 383883A6B88
	for <sip@ietf.org>; Tue, 14 Oct 2008 22:30:07 -0700 (PDT)
Received: from gws03.hcl.in (gws03 [10.249.64.134])
	by localhost.hcl.in (Postfix) with ESMTP
	id 96F7E37C11A; Wed, 15 Oct 2008 11:01:02 +0530 (IST)
Received: from chn-egw01-out.corp.hcl.in (unknown [10.249.64.37])by 
	gws03.hcl.in (Postfix) with ESMTPid 6070E37C130;
	Wed, 15 Oct 2008 11:01:02 +0530 (IST)
Received: from CHN-HCLT-EVS02.HCLT.CORP.HCL.IN ([10.101.26.14]) by 
	chn-egw01-out.corp.hcl.in with Microsoft SMTPSVC(6.0.3790.3959);
	Wed, 15 Oct 2008 11:01:02 +0530
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 15 Oct 2008 11:01:01 +0530
Message-ID: <E971678290A1BA41BD96554DBA1211B6ABF788@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC312843F60B4@mail.acmepacket.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackta1Q4oPZYeoZEQAiUqa8JyoYU4gAAB04gACPIDEAABL7/QAAE9WcQABkzIjA=
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18668.50247
	.121832.271341@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@ese
	almw113.eemea.ericsson.se><18668.51383.505850.963592@taimen.test.fi><CA9998
	CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se><18672.1984
	6.621765.332209@taimen.test.fi><2210d2240810111235r5b786e94u7707730d8f1fa62
	7@mail.gmail.com><18673.5665.337048.880648@taimen.test.fi><2210d22408101201
	45o2297ac07v3487d014955bf0@mail.gmail.com><18673.62485.295631.933830@taimen
	.test.fi><2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com><1867
	5.7684.207071.901832@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8
	EF@esealmw113.eemea.ericsson.se><18675.41223.587006.241312@taimen.test.fi><
	18675.41926.583512.912121@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF0
	5C0F8F2@esealmw113.eemea.ericsson.se><E6C2E8958BA59A4FB960963D475F7AC312843
	5A4EA@mail.acmepacket.com><0D5F89FAC29E2C41B98A6A762007F5D0012A2353@GBNTHT1
	2009MSX.gb002.siemens.net> 
	<E6C2E8958BA59A4FB960963D475F7AC312843F60B4@mail.acmepacket.com>
From: "Karthikeyan Gopal " <g_karthikeyan@hcl.in>
To: "Bob Penfield" <BPenfield@acmepacket.com>,
	"Elwell, John" <john.elwell@siemens.com>,
	"Christer Holmberg" <christer.holmberg@ericsson.com>,
	"Juha Heinanen" <jh@tutpro.com>, <sip@ietf.org>,
	"Paul Kyzivat" <pkyzivat@cisco.com>,
	"Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 15 Oct 2008 05:31:02.0230 (UTC) 
	FILETIME=[363E8760:01C92E87]
X-imss-version: 2.051
X-imss-result: Passed
X-imss-scanInfo: M:T L:E SM:1
X-imss-tmaseResult: TT:1 TS:-23.3828 TC:1F TRN:65 TV:5.5.1026(16218.001)
X-imss-scores: Clean:100.00000 C:0 M:0 S:0 R:0
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Why two UA instance? What is the use case?
If UA want's to register with 2 flow say 2 proxies we can have same 
Instance-id and vary the reg-id value.
Regards,
Karthikeyan.G

-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Bob Penfield
Sent: Tuesday, October 14, 2008 11:08 PM
To: Elwell, John; Christer Holmberg; Juha Heinanen; sip@ietf.org; Paul
Kyzivat; Dean Willis
Subject: Re: [Sip] Dual registration without Outbound

I guess the problem arises when you want to do a single REGISTER request
for both instances. If I the use case correctly, the UA would send two
REGISTER requests (one on each interface) and both REGISTERs would have
the two Contacts (one for each instance-id). Something like this:

First REGISTER to Outbound-proxy #1

   REGISTER sip:example.com SIP/2.0
   Via: SIP/2.0/TCP 1.1.1.1;branch=z9hG4bKnashds7-1
   From: Bob <sip:bob@example.com>;tag=7F94778B653B-1
   To: Bob <sip:bob@example.com>
   Call-ID: 16CB75F21C70-1
   CSeq: 1 REGISTER
   Supported: path, outbound
   Route: <sip:ep1.example.com;lr>
   Contact: <sip:bob@1.1.1.1;transport=tcp>;reg-id=1
    ;+sip.instance="<urn:uuid:00000000-0000-1000-8000-AABBCCDDEEFF>"
   Contact: <sip:bob@2.2.2.2;transport=tcp>;reg-id=2
    ;+sip.instance="<urn:uuid:00000000-0000-1000-8000-BBCCDDEEFF00>"

Second REGISTER to Outbound-proxy #2

   REGISTER sip:example.com SIP/2.0
   Via: SIP/2.0/TCP 2.2.2.2;branch=z9hG4bKnashds7-2
   From: Bob <sip:bob@example.com>;tag=7F94778B653B-2
   To: Bob <sip:bob@example.com>
   Call-ID: 16CB75F21C70-2
   CSeq: 1 REGISTER
   Supported: path, outbound
   Route: <sip:ep2.example.com;lr>
   Contact: <sip:bob@2.2.2.2;transport=tcp>;reg-id=1
    ;+sip.instance="<urn:uuid:00000000-0000-1000-8000-BBCCDDEEFF00>"
   Contact: <sip:bob@1.1.1.1;transport=tcp>;reg-id=2
    ;+sip.instance="<urn:uuid:00000000-0000-1000-8000-AABBCCDDEEFF>"

Thus the UA could receive requests for either Contact on either of the
two outbound flows.

Is having two UA instances in the same request legal with the current
text?

cheers,
(-:bob

-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens.com]
Sent: Tuesday, October 14, 2008 11:02 AM
To: Bob Penfield; Christer Holmberg; Juha Heinanen; sip@ietf.org; Paul
Kyzivat; Dean Willis
Subject: RE: [Sip] Dual registration without Outbound



> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
> Behalf Of Bob Penfield
> Sent: 14 October 2008 15:41
> To: Christer Holmberg; Juha Heinanen; sip@ietf.org; Paul
> Kyzivat; Dean Willis
> Subject: Re: [Sip] Dual registration without Outbound
>
> For both GRUU and Outbound a given instance-id
> (+sip-instance) actually represents a single UA contact
> instance rather than just a single User Agent. The basic idea
> behind GRUU is that a request addressed to a GRUU is
> forwarded by the proxy to a specific Contact address. The
> goal is the same with Outbound but it adds multiple
> flows/paths to that UA Contact. This is reflected in the
> proxy procedures in both GRUU and Outbound.
>
> In both cases, the proxy does serial forking to Contacts with
> the same instance-id.
>
> For GRUU it starts with the most-recently registered binding
> (according to section 6.1 of GRUU):
>
>        The proxy MUST select the most recently refreshed
>        contact.  As with draft-ietf-sip-outbound, if a request to this
>        target fails with a 408 (Request Timeout) or 430 (Flow Failed)
>        response, the proxy SHOULD retry with the next most recently
>        refreshed contact.  Furthermore, if the request fails with any
>        other response, the proxy MUST NOT retry on any other contacts
>        for this instance.
>
> For Outbound, it attempts the registered flows (according to
> section 7 of Outbound):
>
>    When a proxy uses the location service to look up a registration
>    binding and then proxies a request to a particular contact, it
>    selects a contact to use normally, with a few additional rules:
>
>    o  The proxy MUST NOT populate the target set with more than one
>       contact with the same AOR and instance-id at a time.
>    o  If a request for a particular AOR and instance-id fails
> with a 430
>       (Flow Failed) response, the proxy SHOULD replace the
> failed branch
>       with another target (if one is available) with the same AOR and
>       instance-id, but a different reg-id.
>    o  If the proxy receives a final response from a branch
> other than a
>       408 (Request Timeout) or a 430 (Flow Failed) response, the proxy
>       MUST NOT forward the same request to another target representing
>       the same AOR and instance-id.  The targeted instance has already
>       provided its response.
>
> Therefore, a User Agent that is registering multiple Contacts
> to allow the possibility of parallel forking would need to
> have a separate instance-id for each Contact.
>
> For User Agent's that have multiple interfaces, it could use
> the MAC address of each interface to create a unique UUID URN
> for each contact.
>
> Thus, the following scenario is possible:
>
>   UA_Contact_wlan;+sip-instance=ID_1;reg-id=1 ----- OB_1 ----- REG_1
>   UA_Contact_wlan;+sip-instance=ID_1;reg-id=2 ----- OB_2 ----- REG_2
>   UA_Contact_3g;+sip-instance=ID_2;reg-id=1   ----- OB_1 ----- REG_1
>   UA_Contact_3g;+sip-instance=ID_2;reg-id=2   ----- OB_2 ----- REG_2
>
> Unfortunately, the current text in section 4.1 says that a UA
> has "an Instance Identifier".
[JRE] In an earlier email I was trying to say roughly the same thing,
except the way I looked at it was that a device with multiple interfaces
would logically contain a UA for each interface, and each UA would than
have a single instance ID. In that case the text in section 4.1 still
works.

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

DISCLAIMER:
-----------------------------------------------------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in 
this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of 
this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have
received this email in error please delete it and notify the sender immediately. Before opening any mail and 
attachments please check them for viruses and defect.

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


From sip-bounces@ietf.org  Tue Oct 14 22:33:00 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6716F3A6B88;
	Tue, 14 Oct 2008 22:33:00 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 26F553A6BF2
	for <sip@core3.amsl.com>; Tue, 14 Oct 2008 22:32:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.616
X-Spam-Level: 
X-Spam-Status: No, score=-2.616 tagged_above=-999 required=5
	tests=[AWL=-0.017, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zpubaewmboL7 for <sip@core3.amsl.com>;
	Tue, 14 Oct 2008 22:32:58 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 648063A6BF0
	for <sip@ietf.org>; Tue, 14 Oct 2008 22:32:58 -0700 (PDT)
Received: from [192.168.2.2] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9F5XqMn024908
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Wed, 15 Oct 2008 00:33:53 -0500
Message-ID: <48F580BA.9090001@softarmor.com>
Date: Wed, 15 Oct 2008 00:33:46 -0500
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Icedove 1.5.0.14eol (X11/20080724)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>
X-Enigmail-Version: 0.94.2.0
Cc: sip@ietf.org, Francois Audet <audet@nortel.com>
Subject: Re: [Sip] Is GRUU generated in the case of registration
 with	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg wrote:
> So, the following applies:
> 
> 
> request                                        response
> -------------------------------------------------------
> 
> instance-id AND Supported:gruu               = gruu
> instance-id AND reg-id                       = outbound
> instance-id AND reg-id AND Supported:gruu    = outbound AND gruu
> instance-id                                  = n/a
> 

It seems like instance-id by itself could be useful for detecting
expired registrations from the same node, outside of gruu or outbound.

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


From sip-bounces@ietf.org  Tue Oct 14 22:35:23 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 362DE3A6B81;
	Tue, 14 Oct 2008 22:35:23 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 85AC03A6BD7
	for <sip@core3.amsl.com>; Tue, 14 Oct 2008 22:35:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.616
X-Spam-Level: 
X-Spam-Status: No, score=-2.616 tagged_above=-999 required=5
	tests=[AWL=-0.017, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id TGmKhWKcAKla for <sip@core3.amsl.com>;
	Tue, 14 Oct 2008 22:35:20 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id BF0AA3A6B81
	for <sip@ietf.org>; Tue, 14 Oct 2008 22:35:20 -0700 (PDT)
Received: from [192.168.2.2] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9F5ZsWL024932
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Wed, 15 Oct 2008 00:35:55 -0500
Message-ID: <48F58135.2060403@softarmor.com>
Date: Wed, 15 Oct 2008 00:35:49 -0500
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Icedove 1.5.0.14eol (X11/20080724)
MIME-Version: 1.0
To: Juha Heinanen <jh@tutpro.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>	<18665.51736.268071.502700@taimen.test.fi>	<CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se>	<18665.59
	269.640606.477292@taimen.test.fi>	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>	<48EBC88B.2030300@cisco.com>	<46101DEA-677B-4F28-AD1E-32F64385853
	5@s
	ofta	rmor.com>	<CA	9998CD4A020D418654FCDEF4E707DF05C0F8B8@esealmw113.eemea.ericsson.se>	<18668.21733.520868.113675@taimen.test.fi>	<CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se>	<48ECBA45.1070109@c
	is
	co.com>	<CA9998CD4A0	20D418654FCDEF4E707DF05C0F8C6@esealmw113.eemea.ericsson.se>	<18668.50247.121832.271341@taimen.test.fi>	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>	<18668.51383.505850.963592@taimen.test.fi>	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
In-Reply-To: <18672.19846.621765.332209@taimen.test.fi>
X-Enigmail-Version: 0.94.2.0
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Juha Heinanen wrote:

> 7. Authoritative Proxy Procedures: Forwarding Requests
> 
>    When a proxy uses the location service to look up a registration
>    binding and then proxies a request to a particular contact, it
>    selects a contact to use normally, with a few additional rules:
> 
>    o  The proxy MUST NOT populate the target set with more than one
>       contact with the same AOR and instance-id at a time.
> 
> to me this clearly means that parallel forking is not anymore possible
> when UA implements outbound, which would be a VERY SEVERE restriction
> and change of RFC3261 behavior.

This seems to me to mean that if you have two interfaces on a given UA
and want them treated as separate instances (so that the requests can be
forked) that you do so by using different instance IDs for each interface.

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


From sip-bounces@ietf.org  Tue Oct 14 22:40:28 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0BF633A6B88;
	Tue, 14 Oct 2008 22:40:28 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5EDD23A6B88
	for <sip@core3.amsl.com>; Tue, 14 Oct 2008 22:40:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.615
X-Spam-Level: 
X-Spam-Status: No, score=-2.615 tagged_above=-999 required=5
	tests=[AWL=-0.016, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3LkEHvh5WCCg for <sip@core3.amsl.com>;
	Tue, 14 Oct 2008 22:40:25 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 9B2423A6960
	for <sip@ietf.org>; Tue, 14 Oct 2008 22:40:25 -0700 (PDT)
Received: from [192.168.2.2] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9F5fH5A024999
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Wed, 15 Oct 2008 00:41:18 -0500
Message-ID: <48F58278.50906@softarmor.com>
Date: Wed, 15 Oct 2008 00:41:12 -0500
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Icedove 1.5.0.14eol (X11/20080724)
MIME-Version: 1.0
To: Juha Heinanen <jh@tutpro.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se>	<48EBC88B.2030300@cisco.com>	<18668.21733.520868.113675@taimen.test.fi>	<CA9998CD4A020D418654FCDEF4E707DF05C0F8BF@esealmw113.eemea.ericsson.se>	<18668.50247.121832.271341@taimen.test.fi>	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>	<18668.51383.505850.963592@taimen.test.fi>	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>	<18672.19846.621765.332209@taimen.test.fi>	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>	<18673.5665.337048.880648@taimen.test.fi>	<0D5F89FAC29E2C41B98A6A762007F5D0012A1A18@GBNTHT12009MSX.gb002.siemens.net>
	<18675.7930.503396.458785@taimen.test.fi>
In-Reply-To: <18675.7930.503396.458785@taimen.test.fi>
X-Enigmail-Version: 0.94.2.0
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>, "Elwell,
	John" <john.elwell@siemens.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Juha Heinanen wrote:
> Elwell, John writes:
> 
>  > [JRE] Yes, indeed, retention of forking is very important. With RFC
>  > 3261, multiple UAs can register and incoming requests will be forked to
>  > them. With sip-outbound, this is still the case, provided these multiple
>  > UAs choose different instance IDs. This still holds true if two UAs are
>  > implemented in the same device, e.g., in your example, a dual mode
>  > device would have a GPRS UA with one instance ID and a WLAN UA with a
>  > second instance ID. 
> 
> see my previous email.  i don't want two UAs, but like today, only one
> that has two contacts.
> 

What requires there to be two "real" UAs to have two instance-id values?
A single UA with two interfaces and one instance-id per interface seems
reasonable to me.

It's also reasonable that that UA might have two different interfaces
that share an instance-id. It's really a choice between different
deployment scenarios.

--
Dean

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


From sip-bounces@ietf.org  Tue Oct 14 22:43:22 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D6AA33A6960;
	Tue, 14 Oct 2008 22:43:22 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 012DE3A6960
	for <sip@core3.amsl.com>; Tue, 14 Oct 2008 22:43:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.615
X-Spam-Level: 
X-Spam-Status: No, score=-2.615 tagged_above=-999 required=5
	tests=[AWL=-0.016, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id EcPjcVa9ZlFu for <sip@core3.amsl.com>;
	Tue, 14 Oct 2008 22:43:21 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 38E4D3A67EC
	for <sip@ietf.org>; Tue, 14 Oct 2008 22:43:21 -0700 (PDT)
Received: from [192.168.2.2] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9F5iEBt025023
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Wed, 15 Oct 2008 00:44:15 -0500
Message-ID: <48F58328.2080106@softarmor.com>
Date: Wed, 15 Oct 2008 00:44:08 -0500
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Icedove 1.5.0.14eol (X11/20080724)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18668.50247.121832.271341@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se><18668.51383.505850.963592@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se><18672.19846.621765.332209@taimen.test.fi><2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com><18673.5665.337048.880648@taimen.test.fi><2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com><18673.62485.295631.933830@taimen.test.fi><2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
X-Enigmail-Version: 0.94.2.0
Cc: sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg wrote:
> I don't think the spec is broken. I think the spec was written based on
> the assumption that a UA instance is not interested in receiving an
> INVITE multiple times in parallel (the UA will return 484 for all but
> one INVITE) - which I don't think is desired even in normal forking
> scenarios - but that it should be possible to, if one flow is down,
> choose another flow to reach the UA (read: serial forking).

IIRC, it was a deliberate choice (a feature of the spec) that it prevent
 redundant message delivery, as that would most likely screw up a UA.

The whole point of the instance-id is so that the proxy can know that
two contacts refer to the same UA, and therefore NOT fork request to
both contacts.

--
Dean


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


From sip-bounces@ietf.org  Tue Oct 14 22:57:42 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9BC8A3A6858;
	Tue, 14 Oct 2008 22:57:42 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7FB2A3A6858
	for <sip@core3.amsl.com>; Tue, 14 Oct 2008 22:57:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.19
X-Spam-Level: 
X-Spam-Status: No, score=-6.19 tagged_above=-999 required=5 tests=[AWL=0.059, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id R938tQIufv5L for <sip@core3.amsl.com>;
	Tue, 14 Oct 2008 22:57:40 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 3D1B83A67B4
	for <sip@ietf.org>; Tue, 14 Oct 2008 22:57:40 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	9858920D04; Wed, 15 Oct 2008 07:58:34 +0200 (CEST)
X-AuditID: c1b4fb3c-ae8cfbb0000015b5-8f-48f5868979f6
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	94C6B20D6B; Wed, 15 Oct 2008 07:58:33 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Oct 2008 07:57:48 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 15 Oct 2008 07:57:48 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF086A6463@esealmw113.eemea.ericsson.se>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF19BAB943@zrc2hxm0.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
Thread-Index: Ackthpxe2j+IIv2ATNuWao7mqiLjvAANMqTQABlcJkAAGm/XYA==
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>
	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>
	<48F23D27.8030305@voip.co.uk>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se>
	<48F2FC13.1070308@voip.co.uk> <48F34E3B.80106@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EE@esealmw113.eemea.ericsson.se>
	<48F3D191.5000007@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0864CEFC@esealmw113.eemea.ericsson.se>
	<1ECE0EB50388174790F9694F77522CCF19BAB943@zrc2hxm0.corp.nortel.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Francois Audet" <audet@nortel.com>,
	"Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 15 Oct 2008 05:57:48.0669 (UTC)
	FILETIME=[F3C1AAD0:01C92E8A]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org
Subject: Re: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi,

The text would be something like:

"NOTE: If the registrar supports gruu [reference-to-gruu-spec], the
presence of the instance-id in the REGISTER request will also trigger
the registrar to generate a gruu for the user, as described in
[reference-to-gruu-spec]."

I will look for a place in the outbound draft where to put it, but it
really isn't more complicated than that. Just a simple clarification
note :)

Regards,

Christer

 

-----Original Message-----
From: Francois Audet [mailto:audet@nortel.com] 
Sent: 14. lokakuuta 2008 20:19
To: Christer Holmberg; Paul Kyzivat
Cc: Michael Procter; sip@ietf.org
Subject: RE: [Sip] Is GRUU generated in the case of registration with
instance-ID and reg-ID

Can you propose actual text for a specific section. 

> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> Sent: Monday, October 13, 2008 22:13
> To: Paul Kyzivat
> Cc: Michael Procter; sip@ietf.org; Audet, Francois (SC100:3055)
> Subject: RE: [Sip] Is GRUU generated in the case of registration with 
> instance-ID and reg-ID
> 
> 
> Hi,
> 
> >>Yes. The question was whether instance-id AND reg-id also create a
> gruu.
> >>The answer seems to be yes, but I think it would be good to clarify 
> >>that somewhere.
> >
> >Since reg-id isn't mentioned in gruu, its irrelevant to the
> gruu spec,
> just as any other parameters are.
> 
> That is why I proposed it is clarified in the outbound spec :)
> 
> Regards,
> 
> Christer
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Tue Oct 14 23:01:59 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6F0B63A692D;
	Tue, 14 Oct 2008 23:01:59 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8C4943A692D
	for <sip@core3.amsl.com>; Tue, 14 Oct 2008 23:01:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.191
X-Spam-Level: 
X-Spam-Status: No, score=-6.191 tagged_above=-999 required=5 tests=[AWL=0.058, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id K5ZJHwi-0Q2T for <sip@core3.amsl.com>;
	Tue, 14 Oct 2008 23:01:57 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id B93663A6853
	for <sip@ietf.org>; Tue, 14 Oct 2008 23:01:57 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	5E7B1215BF; Wed, 15 Oct 2008 08:02:54 +0200 (CEST)
X-AuditID: c1b4fb3e-ab68abb000007a96-15-48f5878e3633
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	4052B214DB; Wed, 15 Oct 2008 08:02:54 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Oct 2008 08:02:53 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 15 Oct 2008 08:02:53 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF086D9D6C@esealmw113.eemea.ericsson.se>
In-Reply-To: <48F580BA.9090001@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Is GRUU generated in the case of registration
	with	instance-ID and reg-ID
Thread-Index: Ackuh54W9wjl39RlQOq+SCIKnM+E4AAA+QJA
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>
	<48F580BA.9090001@softarmor.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 15 Oct 2008 06:02:54.0068 (UTC)
	FILETIME=[A9C9DB40:01C92E8B]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, Francois Audet <audet@nortel.com>
Subject: Re: [Sip] Is GRUU generated in the case of registration
	with	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


>It seems like instance-id by itself could be useful for detecting
expired registrations from the same node, outside of gruu or outbound.

When SIP was born, it was all about the user, not the device...

Regards,

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


From sip-bounces@ietf.org  Tue Oct 14 23:52:20 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BD25D3A6B81;
	Tue, 14 Oct 2008 23:52:20 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C08DD3A6C44
	for <sip@core3.amsl.com>; Tue, 14 Oct 2008 23:52:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.614
X-Spam-Level: 
X-Spam-Status: No, score=-2.614 tagged_above=-999 required=5
	tests=[AWL=-0.015, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fwKJrwnqW4Ut for <sip@core3.amsl.com>;
	Tue, 14 Oct 2008 23:52:18 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 03F3E3A6B81
	for <sip@ietf.org>; Tue, 14 Oct 2008 23:52:17 -0700 (PDT)
Received: from [192.168.2.2] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9F6r9GT025776
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Wed, 15 Oct 2008 01:53:11 -0500
Message-ID: <48F5934F.7090706@softarmor.com>
Date: Wed, 15 Oct 2008 01:53:03 -0500
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Icedove 1.5.0.14eol (X11/20080724)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>	<48F580BA.9090001@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF086D9D6C@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF086D9D6C@esealmw113.eemea.ericsson.se>
X-Enigmail-Version: 0.94.2.0
Cc: sip@ietf.org, Francois Audet <audet@nortel.com>
Subject: Re: [Sip] Is GRUU generated in the case of
 registration	with	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg wrote:
>> It seems like instance-id by itself could be useful for detecting
> expired registrations from the same node, outside of gruu or outbound.
> 
> When SIP was born, it was all about the user, not the device...

That's because we didn't have all MacBooks, iPhones, and Google Androids
back then. Instead, we had to encode our REGISTER messages on tiny slips
of paper attached to the legs of carrier pigeons.

Seriously, IIRC back in 1998 UUNET honcho John Sidgemore made a speech
where he claimed it would not be long before the average person in the
developed world would have or more five internet-connected devices. We
all laughed at the silly man. Now I have dozens of Internet-connected
devices, including cell phones, music players, laptops, desktops,
microservers, WiFi routers, printers, voice mail, SIP phones, and so on.

He was right, and we should have thought about the implications to SIP a
little more carefully.

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


From sip-bounces@ietf.org  Wed Oct 15 00:52:23 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 410D93A6C5E;
	Wed, 15 Oct 2008 00:52:23 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EC2053A6C3E
	for <sip@core3.amsl.com>; Wed, 15 Oct 2008 00:52:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.192
X-Spam-Level: 
X-Spam-Status: No, score=-6.192 tagged_above=-999 required=5 tests=[AWL=0.057, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YJE86BPwLcFA for <sip@core3.amsl.com>;
	Wed, 15 Oct 2008 00:52:21 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 043353A6C50
	for <sip@ietf.org>; Wed, 15 Oct 2008 00:52:20 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	90E9B21468; Wed, 15 Oct 2008 09:51:52 +0200 (CEST)
X-AuditID: c1b4fb3e-ab68abb000007a96-35-48f5a1182f43
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	7127B2050E; Wed, 15 Oct 2008 09:51:52 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Oct 2008 09:51:52 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 15 Oct 2008 09:51:51 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF086DA228@esealmw113.eemea.ericsson.se>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D0012A2353@GBNTHT12009MSX.gb002.siemens.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackta1Q4oPZYeoZEQAiUqa8JyoYU4gAAB04gACPIDEAABL7/QAAjTT0w
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18668.50247.121832.271341@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
	<18668.51383.505850.963592@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
	<18673.5665.337048.880648@taimen.test.fi>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0012A2353@GBNT HT12009M
	SX.gb002.siemens.net>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Elwell, John" <john.elwell@siemens.com>,
	"Bob Penfield" <BPenfield@acmepacket.com>, "Juha Heinanen" <jh@tutpro.com>,
	<sip@ietf.org>, "Paul Kyzivat" <pkyzivat@cisco.com>,
	"Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 15 Oct 2008 07:51:52.0236 (UTC)
	FILETIME=[E2D71EC0:01C92E9A]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>[JRE] In an earlier email I was trying to say roughly the same thing,
except the way I looked at it was that a device with multiple interfaces
would logically contain a UA for each interface, 
>and each UA would than have a single instance ID. In that case the text
in section 4.1 still works.

I think the use-cases we are talking about still only has a single UA
(if you refer to actual application software).

Regards,

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


From sip-bounces@ietf.org  Wed Oct 15 00:57:49 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0F1983A6972;
	Wed, 15 Oct 2008 00:57:49 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AE9E53A6972
	for <sip@core3.amsl.com>; Wed, 15 Oct 2008 00:57:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.193
X-Spam-Level: 
X-Spam-Status: No, score=-6.193 tagged_above=-999 required=5 tests=[AWL=0.056, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id g00BGYL19YUf for <sip@core3.amsl.com>;
	Wed, 15 Oct 2008 00:57:46 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 146773A68D3
	for <sip@ietf.org>; Wed, 15 Oct 2008 00:57:45 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	15882203DC; Wed, 15 Oct 2008 09:58:41 +0200 (CEST)
X-AuditID: c1b4fb3c-af0d0bb0000015b5-0e-48f5a2b029c5
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	C76E020C3A; Wed, 15 Oct 2008 09:58:40 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Oct 2008 09:58:22 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 15 Oct 2008 09:58:22 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF086DA294@esealmw113.eemea.ericsson.se>
In-Reply-To: <E971678290A1BA41BD96554DBA1211B6ABF788@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackta1Q4oPZYeoZEQAiUqa8JyoYU4gAAB04gACPIDEAABL7/QAAE9WcQABkzIjAABU/TgA==
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18668.50247.121832.271341@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se><18668.51383.505850.963592@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se><18672.19846.621765.332209@taimen.test.fi><2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com><18673.5665.337048.880648@taimen.test.fi><2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com><18673.62485.295631.933830@taimen.test.fi><2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com><18675.7684.207071.901832@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se><18675.41223.587006.241312@taimen.test.fi><18675.41926.583512.912121@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se><E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com><0D5F89FAC29E2C41B98A6A762007F5D0012A2353@GBNTHT12009MSX.gb002.
	siemens. net> <E6C2E8
	958BA59A4FB960963D475F7AC312843F60B4@mail.acmepacket.com>
	<E971678290A1BA41BD96554DBA1211B6ABF788@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Karthikeyan Gopal " <g_karthikeyan@hcl.in>,
	"Bob Penfield" <BPenfield@acmepacket.com>,
	"Elwell, John" <john.elwell@siemens.com>, "Juha Heinanen" <jh@tutpro.com>,
	<sip@ietf.org>, "Paul Kyzivat" <pkyzivat@cisco.com>,
	"Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 15 Oct 2008 07:58:22.0611 (UTC)
	FILETIME=[CB859E30:01C92E9B]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>Why two UA instance? What is the use case?
>If UA want's to register with 2 flow say 2 proxies we can have same
Instance-id and vary the reg-id value.

The issue is that Juha wants incoming INVITEs to be paralelly forked to
both contacts. Outbound does not do paralell forking - it tries one
flow, and if that doesn't work it tries another one.

Regards,

Christer


-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Bob Penfield
Sent: Tuesday, October 14, 2008 11:08 PM
To: Elwell, John; Christer Holmberg; Juha Heinanen; sip@ietf.org; Paul
Kyzivat; Dean Willis
Subject: Re: [Sip] Dual registration without Outbound

I guess the problem arises when you want to do a single REGISTER request
for both instances. If I the use case correctly, the UA would send two
REGISTER requests (one on each interface) and both REGISTERs would have
the two Contacts (one for each instance-id). Something like this:

First REGISTER to Outbound-proxy #1

   REGISTER sip:example.com SIP/2.0
   Via: SIP/2.0/TCP 1.1.1.1;branch=z9hG4bKnashds7-1
   From: Bob <sip:bob@example.com>;tag=7F94778B653B-1
   To: Bob <sip:bob@example.com>
   Call-ID: 16CB75F21C70-1
   CSeq: 1 REGISTER
   Supported: path, outbound
   Route: <sip:ep1.example.com;lr>
   Contact: <sip:bob@1.1.1.1;transport=tcp>;reg-id=1
    ;+sip.instance="<urn:uuid:00000000-0000-1000-8000-AABBCCDDEEFF>"
   Contact: <sip:bob@2.2.2.2;transport=tcp>;reg-id=2
    ;+sip.instance="<urn:uuid:00000000-0000-1000-8000-BBCCDDEEFF00>"

Second REGISTER to Outbound-proxy #2

   REGISTER sip:example.com SIP/2.0
   Via: SIP/2.0/TCP 2.2.2.2;branch=z9hG4bKnashds7-2
   From: Bob <sip:bob@example.com>;tag=7F94778B653B-2
   To: Bob <sip:bob@example.com>
   Call-ID: 16CB75F21C70-2
   CSeq: 1 REGISTER
   Supported: path, outbound
   Route: <sip:ep2.example.com;lr>
   Contact: <sip:bob@2.2.2.2;transport=tcp>;reg-id=1
    ;+sip.instance="<urn:uuid:00000000-0000-1000-8000-BBCCDDEEFF00>"
   Contact: <sip:bob@1.1.1.1;transport=tcp>;reg-id=2
    ;+sip.instance="<urn:uuid:00000000-0000-1000-8000-AABBCCDDEEFF>"

Thus the UA could receive requests for either Contact on either of the
two outbound flows.

Is having two UA instances in the same request legal with the current
text?

cheers,
(-:bob

-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens.com]
Sent: Tuesday, October 14, 2008 11:02 AM
To: Bob Penfield; Christer Holmberg; Juha Heinanen; sip@ietf.org; Paul
Kyzivat; Dean Willis
Subject: RE: [Sip] Dual registration without Outbound



> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of 
> Bob Penfield
> Sent: 14 October 2008 15:41
> To: Christer Holmberg; Juha Heinanen; sip@ietf.org; Paul Kyzivat; Dean

> Willis
> Subject: Re: [Sip] Dual registration without Outbound
>
> For both GRUU and Outbound a given instance-id
> (+sip-instance) actually represents a single UA contact instance 
> rather than just a single User Agent. The basic idea behind GRUU is 
> that a request addressed to a GRUU is forwarded by the proxy to a 
> specific Contact address. The goal is the same with Outbound but it 
> adds multiple flows/paths to that UA Contact. This is reflected in the

> proxy procedures in both GRUU and Outbound.
>
> In both cases, the proxy does serial forking to Contacts with the same

> instance-id.
>
> For GRUU it starts with the most-recently registered binding 
> (according to section 6.1 of GRUU):
>
>        The proxy MUST select the most recently refreshed
>        contact.  As with draft-ietf-sip-outbound, if a request to this
>        target fails with a 408 (Request Timeout) or 430 (Flow Failed)
>        response, the proxy SHOULD retry with the next most recently
>        refreshed contact.  Furthermore, if the request fails with any
>        other response, the proxy MUST NOT retry on any other contacts
>        for this instance.
>
> For Outbound, it attempts the registered flows (according to section 7

> of Outbound):
>
>    When a proxy uses the location service to look up a registration
>    binding and then proxies a request to a particular contact, it
>    selects a contact to use normally, with a few additional rules:
>
>    o  The proxy MUST NOT populate the target set with more than one
>       contact with the same AOR and instance-id at a time.
>    o  If a request for a particular AOR and instance-id fails with a 
> 430
>       (Flow Failed) response, the proxy SHOULD replace the failed 
> branch
>       with another target (if one is available) with the same AOR and
>       instance-id, but a different reg-id.
>    o  If the proxy receives a final response from a branch other than 
> a
>       408 (Request Timeout) or a 430 (Flow Failed) response, the proxy
>       MUST NOT forward the same request to another target representing
>       the same AOR and instance-id.  The targeted instance has already
>       provided its response.
>
> Therefore, a User Agent that is registering multiple Contacts to allow

> the possibility of parallel forking would need to have a separate 
> instance-id for each Contact.
>
> For User Agent's that have multiple interfaces, it could use the MAC 
> address of each interface to create a unique UUID URN for each 
> contact.
>
> Thus, the following scenario is possible:
>
>   UA_Contact_wlan;+sip-instance=ID_1;reg-id=1 ----- OB_1 ----- REG_1
>   UA_Contact_wlan;+sip-instance=ID_1;reg-id=2 ----- OB_2 ----- REG_2
>   UA_Contact_3g;+sip-instance=ID_2;reg-id=1   ----- OB_1 ----- REG_1
>   UA_Contact_3g;+sip-instance=ID_2;reg-id=2   ----- OB_2 ----- REG_2
>
> Unfortunately, the current text in section 4.1 says that a UA has "an 
> Instance Identifier".
[JRE] In an earlier email I was trying to say roughly the same thing,
except the way I looked at it was that a device with multiple interfaces
would logically contain a UA for each interface, and each UA would than
have a single instance ID. In that case the text in section 4.1 still
works.

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

DISCLAIMER:
------------------------------------------------------------------------
-----------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and
intended for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its
affiliates. Any views or opinions presented in this email are solely
those of the author and may not necessarily reflect the opinions of HCL
or its affiliates.
Any form of reproduction, dissemination, copying, disclosure,
modification, distribution and / or publication of this message without
the prior written consent of the author of this e-mail is strictly
prohibited. If you have received this email in error please delete it
and notify the sender immediately. Before opening any mail and
attachments please check them for viruses and defect.

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


From sip-bounces@ietf.org  Wed Oct 15 01:03:21 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 10ED83A68DE;
	Wed, 15 Oct 2008 01:03:21 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3E2ED3A68DE
	for <sip@core3.amsl.com>; Wed, 15 Oct 2008 01:03:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.194
X-Spam-Level: 
X-Spam-Status: No, score=-6.194 tagged_above=-999 required=5 tests=[AWL=0.055, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Cccg5kx3lPHg for <sip@core3.amsl.com>;
	Wed, 15 Oct 2008 01:03:18 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id A733F3A68D4
	for <sip@ietf.org>; Wed, 15 Oct 2008 01:03:17 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	DBA6C21269; Wed, 15 Oct 2008 10:03:45 +0200 (CEST)
X-AuditID: c1b4fb3e-a9e87bb000007a96-18-48f5a3e126fd
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	9DF6B211A6; Wed, 15 Oct 2008 10:03:45 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Oct 2008 10:03:45 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 15 Oct 2008 10:03:44 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF086DA2E3@esealmw113.eemea.ericsson.se>
In-Reply-To: <E971678290A1BA41BD96554DBA1211B6ABF788@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackta1Q4oPZYeoZEQAiUqa8JyoYU4gAAB04gACPIDEAABL7/QAAE9WcQABkzIjAABW7X8A==
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18668.50247.121832.271341@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se><18668.51383.505850.963592@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se><18672.19846.621765.332209@taimen.test.fi><2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com><18673.5665.337048.880648@taimen.test.fi><2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com><18673.62485.295631.933830@taimen.test.fi><2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com><18675.7684.207071.901832@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se><18675.41223.587006.241312@taimen.test.fi><18675.41926.583512.912121@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se><E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com><0D5F89FAC29E2C41B98A6A762007F5D0012A2353@GBNTHT12009MSX.gb002.
	siemens. net> <E6C2E8
	958BA59A4FB960963D475F7AC312843F60B4@mail.acmepacket.com>
	<E971678290A1BA41BD96554DBA1211B6ABF788@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Karthikeyan Gopal " <g_karthikeyan@hcl.in>,
	"Bob Penfield" <BPenfield@acmepacket.com>,
	"Elwell, John" <john.elwell@siemens.com>, "Juha Heinanen" <jh@tutpro.com>,
	<sip@ietf.org>, "Paul Kyzivat" <pkyzivat@cisco.com>,
	"Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 15 Oct 2008 08:03:45.0460 (UTC)
	FILETIME=[8BF47740:01C92E9C]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>I guess the problem arises when you want to do a single REGISTER
request for both instances. If I the use case correctly, the UA would
send two REGISTER requests (one on each interface) and 
>both REGISTERs would have the two Contacts (one for each instance-id).
Something like this:
>
>First REGISTER to Outbound-proxy #1
>
>   REGISTER sip:example.com SIP/2.0
>   Via: SIP/2.0/TCP 1.1.1.1;branch=z9hG4bKnashds7-1
>   From: Bob <sip:bob@example.com>;tag=7F94778B653B-1
>   To: Bob <sip:bob@example.com>
>   Call-ID: 16CB75F21C70-1
>   CSeq: 1 REGISTER
>   Supported: path, outbound
>   Route: <sip:ep1.example.com;lr>
>   Contact: <sip:bob@1.1.1.1;transport=tcp>;reg-id=1
>    ;+sip.instance="<urn:uuid:00000000-0000-1000-8000-AABBCCDDEEFF>"
>   Contact: <sip:bob@2.2.2.2;transport=tcp>;reg-id=2
>    ;+sip.instance="<urn:uuid:00000000-0000-1000-8000-BBCCDDEEFF00>"
>
>Second REGISTER to Outbound-proxy #2
>
>   REGISTER sip:example.com SIP/2.0
>   Via: SIP/2.0/TCP 2.2.2.2;branch=z9hG4bKnashds7-2
>   From: Bob <sip:bob@example.com>;tag=7F94778B653B-2
>   To: Bob <sip:bob@example.com>
>   Call-ID: 16CB75F21C70-2
>   CSeq: 1 REGISTER
>   Supported: path, outbound
>   Route: <sip:ep2.example.com;lr>
>   Contact: <sip:bob@2.2.2.2;transport=tcp>;reg-id=1
>    ;+sip.instance="<urn:uuid:00000000-0000-1000-8000-BBCCDDEEFF00>"
>   Contact: <sip:bob@1.1.1.1;transport=tcp>;reg-id=2
>    ;+sip.instance="<urn:uuid:00000000-0000-1000-8000-AABBCCDDEEFF>"
>
>Thus the UA could receive requests for either Contact on either of the
two outbound flows.
>
>Is having two UA instances in the same request legal with the current
text?

Isn't the edge proxy always going to send incoming request (towards the
UA) to the address/port where the REGISTER came from, in order for the
request to traverse the NAT? 

So, I don't think you can perform the kind of "third party registration"
which your example shows.

Regards,

Christer






-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens.com]
Sent: Tuesday, October 14, 2008 11:02 AM
To: Bob Penfield; Christer Holmberg; Juha Heinanen; sip@ietf.org; Paul
Kyzivat; Dean Willis
Subject: RE: [Sip] Dual registration without Outbound



> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of 
> Bob Penfield
> Sent: 14 October 2008 15:41
> To: Christer Holmberg; Juha Heinanen; sip@ietf.org; Paul Kyzivat; Dean

> Willis
> Subject: Re: [Sip] Dual registration without Outbound
>
> For both GRUU and Outbound a given instance-id
> (+sip-instance) actually represents a single UA contact instance 
> rather than just a single User Agent. The basic idea behind GRUU is 
> that a request addressed to a GRUU is forwarded by the proxy to a 
> specific Contact address. The goal is the same with Outbound but it 
> adds multiple flows/paths to that UA Contact. This is reflected in the

> proxy procedures in both GRUU and Outbound.
>
> In both cases, the proxy does serial forking to Contacts with the same

> instance-id.
>
> For GRUU it starts with the most-recently registered binding 
> (according to section 6.1 of GRUU):
>
>        The proxy MUST select the most recently refreshed
>        contact.  As with draft-ietf-sip-outbound, if a request to this
>        target fails with a 408 (Request Timeout) or 430 (Flow Failed)
>        response, the proxy SHOULD retry with the next most recently
>        refreshed contact.  Furthermore, if the request fails with any
>        other response, the proxy MUST NOT retry on any other contacts
>        for this instance.
>
> For Outbound, it attempts the registered flows (according to section 7

> of Outbound):
>
>    When a proxy uses the location service to look up a registration
>    binding and then proxies a request to a particular contact, it
>    selects a contact to use normally, with a few additional rules:
>
>    o  The proxy MUST NOT populate the target set with more than one
>       contact with the same AOR and instance-id at a time.
>    o  If a request for a particular AOR and instance-id fails with a 
> 430
>       (Flow Failed) response, the proxy SHOULD replace the failed 
> branch
>       with another target (if one is available) with the same AOR and
>       instance-id, but a different reg-id.
>    o  If the proxy receives a final response from a branch other than 
> a
>       408 (Request Timeout) or a 430 (Flow Failed) response, the proxy
>       MUST NOT forward the same request to another target representing
>       the same AOR and instance-id.  The targeted instance has already
>       provided its response.
>
> Therefore, a User Agent that is registering multiple Contacts to allow

> the possibility of parallel forking would need to have a separate 
> instance-id for each Contact.
>
> For User Agent's that have multiple interfaces, it could use the MAC 
> address of each interface to create a unique UUID URN for each 
> contact.
>
> Thus, the following scenario is possible:
>
>   UA_Contact_wlan;+sip-instance=ID_1;reg-id=1 ----- OB_1 ----- REG_1
>   UA_Contact_wlan;+sip-instance=ID_1;reg-id=2 ----- OB_2 ----- REG_2
>   UA_Contact_3g;+sip-instance=ID_2;reg-id=1   ----- OB_1 ----- REG_1
>   UA_Contact_3g;+sip-instance=ID_2;reg-id=2   ----- OB_2 ----- REG_2
>
> Unfortunately, the current text in section 4.1 says that a UA has "an 
> Instance Identifier".
[JRE] In an earlier email I was trying to say roughly the same thing,
except the way I looked at it was that a device with multiple interfaces
would logically contain a UA for each interface, and each UA would than
have a single instance ID. In that case the text in section 4.1 still
works.

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

DISCLAIMER:
------------------------------------------------------------------------
-----------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and
intended for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its
affiliates. Any views or opinions presented in this email are solely
those of the author and may not necessarily reflect the opinions of HCL
or its affiliates.
Any form of reproduction, dissemination, copying, disclosure,
modification, distribution and / or publication of this message without
the prior written consent of the author of this e-mail is strictly
prohibited. If you have received this email in error please delete it
and notify the sender immediately. Before opening any mail and
attachments please check them for viruses and defect.

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


From sip-bounces@ietf.org  Wed Oct 15 01:27:31 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 149983A68D6;
	Wed, 15 Oct 2008 01:27:31 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3F4CD3A68B1
	for <sip@core3.amsl.com>; Wed, 15 Oct 2008 01:27:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.573
X-Spam-Level: 
X-Spam-Status: No, score=-2.573 tagged_above=-999 required=5 tests=[AWL=0.026, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Yw-++kL3241e for <sip@core3.amsl.com>;
	Wed, 15 Oct 2008 01:27:29 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id 61D053A67A6
	for <sip@ietf.org>; Wed, 15 Oct 2008 01:27:29 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K8R00E6XU6U28@siemenscomms.co.uk> for sip@ietf.org; Wed,
	15 Oct 2008 09:28:06 +0100 (BST)
Date: Wed, 15 Oct 2008 09:28:11 +0100
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: A
	<CA9998CD4A020D418654FCDEF4E707DF086DA228@esealmw113.eemea.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>,
	Bob Penfield <BPenfield@acmepacket.com>, Juha Heinanen <jh@tutpro.com>, 
	sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D0012DB11E@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackta1Q4oPZYeoZEQAiUqa8JyoYU4gAAB04gACPIDEAABL7/QAAjTT0wAAEXIbA=
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18668.50247.121832.271341@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
	<18668.51383.505850.963592@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
	<18673.5665.337048.880648@taimen.test.fi>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com> A
	<CA9998CD4A020D418654FCDEF4E707DF086DA228@esealmw113.eemea.ericsson.se>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer,

It might well be the same software stack from the IP layer or the
transport layer upwards, but logically it acts as two UAs (with some
application software at the top to bind the two together). At least from
the proxy perspective it looks like two UAs. Viewing it your way is
perhaps also valid (but requires a minor change to sip-outbound).

John

> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] 
> Sent: 15 October 2008 08:52
> To: Elwell, John; Bob Penfield; Juha Heinanen; sip@ietf.org; 
> Paul Kyzivat; Dean Willis
> Subject: RE: [Sip] Dual registration without Outbound
> 
> 
> Hi, 
> 
> >[JRE] In an earlier email I was trying to say roughly the same thing,
> except the way I looked at it was that a device with multiple 
> interfaces
> would logically contain a UA for each interface, 
> >and each UA would than have a single instance ID. In that 
> case the text
> in section 4.1 still works.
> 
> I think the use-cases we are talking about still only has a single UA
> (if you refer to actual application software).
> 
> Regards,
> 
> Christer
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct 15 01:30:38 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D301128C1C1;
	Wed, 15 Oct 2008 01:30:38 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4DD653A67A6
	for <sip@core3.amsl.com>; Wed, 15 Oct 2008 01:30:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.195
X-Spam-Level: 
X-Spam-Status: No, score=-6.195 tagged_above=-999 required=5 tests=[AWL=0.054, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BjdTpnPv4Gp5 for <sip@core3.amsl.com>;
	Wed, 15 Oct 2008 01:30:37 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id B6FE33A68CC
	for <sip@ietf.org>; Wed, 15 Oct 2008 01:30:36 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	BD033204D7; Wed, 15 Oct 2008 10:31:32 +0200 (CEST)
X-AuditID: c1b4fb3c-ac8cbbb0000015b5-aa-48f5aa64f533
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	9DB5D20CD5; Wed, 15 Oct 2008 10:31:32 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Oct 2008 10:31:31 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 15 Oct 2008 10:31:30 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF086DA432@esealmw113.eemea.ericsson.se>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D0012DB11E@GBNTHT12009MSX.gb002.siemens.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackta1Q4oPZYeoZEQAiUqa8JyoYU4gAAB04gACPIDEAABL7/QAAjTT0wAAEXIbAAAE5eEA==
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18668.50247.121832.271341@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
	<18668.51383.505850.963592@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
	<18673.5665.337048.880648@taimen.test.fi>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
	A <CA9998CD4A020D418654FCDEF4E707DF086DA228@es ealmw113
	.eemea.erics son.se>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DB11E@GBNTHT12009MSX.gb002.siemens.net>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Elwell, John" <john.elwell@siemens.com>,
	"Bob Penfield" <BPenfield@acmepacket.com>, "Juha Heinanen" <jh@tutpro.com>,
	<sip@ietf.org>, "Paul Kyzivat" <pkyzivat@cisco.com>,
	"Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 15 Oct 2008 08:31:31.0323 (UTC)
	FILETIME=[6CE2FCB0:01C92EA0]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>It might well be the same software stack from the IP layer or the
transport layer upwards, but logically it acts as two UAs (with some
application software at the top to bind the two together). 
>At least from the proxy perspective it looks like two UAs. Viewing it
your way is perhaps also valid (but requires a minor change to
sip-outbound).

And, if I understood correctly, that is the change Juha has been asking
for :)

Regards,

Christer

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


From sip-bounces@ietf.org  Wed Oct 15 01:50:49 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 29D063A67F2;
	Wed, 15 Oct 2008 01:50:49 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 60A073A67F2
	for <sip@core3.amsl.com>; Wed, 15 Oct 2008 01:50:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.563
X-Spam-Level: 
X-Spam-Status: No, score=-2.563 tagged_above=-999 required=5 tests=[AWL=0.036, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 70iwWNWTpjxy for <sip@core3.amsl.com>;
	Wed, 15 Oct 2008 01:50:47 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id 967803A67A6
	for <sip@ietf.org>; Wed, 15 Oct 2008 01:50:47 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K8R00F3SVA9KH@siemenscomms.co.uk> for sip@ietf.org; Wed,
	15 Oct 2008 09:51:45 +0100 (BST)
Date: Wed, 15 Oct 2008 09:51:54 +0100
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: A
	<CA9998CD4A020D418654FCDEF4E707DF086DA432@esealmw113.eemea.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>,
	Bob Penfield <BPenfield@acmepacket.com>, Juha Heinanen <jh@tutpro.com>, 
	sip@ietf.org, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackta1Q4oPZYeoZEQAiUqa8JyoYU4gAAB04gACPIDEAABL7/QAAjTT0wAAEXIbAAAE5eEAAAG/tQ
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18668.50247.121832.271341@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
	<18668.51383.505850.963592@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
	<18673.5665.337048.880648@taimen.test.fi>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com> A
	<CA9998CD4A020D418654FCDEF4E707DF086DA432@esealmw113.eemea.ericsson.se>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 

> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] 
> Sent: 15 October 2008 09:32
> To: Elwell, John; Bob Penfield; Juha Heinanen; sip@ietf.org; 
> Paul Kyzivat; Dean Willis
> Subject: RE: [Sip] Dual registration without Outbound
> 
> 
> Hi, 
> 
> >It might well be the same software stack from the IP layer or the
> transport layer upwards, but logically it acts as two UAs (with some
> application software at the top to bind the two together). 
> >At least from the proxy perspective it looks like two UAs. Viewing it
> your way is perhaps also valid (but requires a minor change to
> sip-outbound).
> 
> And, if I understood correctly, that is the change Juha has 
> been asking
> for :)
[JRE] Exactly. But viewing it my way possibly requires less change to
sip-outbound, since much of it talks about one instance ID per UA (e.g.,
section 3.1).

Whichever way we view it, the following statement in 4.1 seems to be
problematic:
"Instance ID MUST NOT change as the device moves from one network to
   another."

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


From sip-bounces@ietf.org  Wed Oct 15 02:07:42 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A4A4F3A6B81;
	Wed, 15 Oct 2008 02:07:42 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7040E28C210
	for <sip@core3.amsl.com>; Wed, 15 Oct 2008 02:07:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KF5ETLkdFGHR for <sip@core3.amsl.com>;
	Wed, 15 Oct 2008 02:07:40 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id 4C93D3A688D
	for <sip@ietf.org>; Wed, 15 Oct 2008 02:07:40 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m9F98IDj012061; Wed, 15 Oct 2008 12:08:19 +0300
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 15 Oct 2008 12:08:18 +0300
Received: from vaebe106.NOE.Nokia.com ([10.160.244.67]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 15 Oct 2008 12:08:17 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 15 Oct 2008 12:08:15 +0300
Message-ID: <7A726F54F791494C8D8C87F13736E80EF82AC5@vaebe106.NOE.Nokia.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF19BAB943@zrc2hxm0.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Is GRUU generated in the case of registration
	withinstance-ID and reg-ID
Thread-Index: Ackthpxe2j+IIv2ATNuWao7mqiLjvAANMqTQABlcJkAAIRzsIA==
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se><1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com><CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se><48F23D27.8030305@voip.co.uk><CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se><48F2FC13.1070308@voip.co.uk>
	<48F34E3B.80106@cisco.com><CA9998CD4A020D418654FCDEF4E707DF05C0F8EE@esealmw113.eemea.ericsson.se><48F3D191.5000007@cisco.com><CA9998CD4A020D418654FCDEF4E707DF0864CEFC@esealmw113.eemea.ericsson.se>
	<1ECE0EB50388174790F9694F77522CCF19BAB943@zrc2hxm0.corp.nortel.com>
From: <Erkki.Koivusalo@nokia.com>
To: <audet@nortel.com>, <christer.holmberg@ericsson.com>, <pkyzivat@cisco.com>
X-OriginalArrivalTime: 15 Oct 2008 09:08:17.0226 (UTC)
	FILETIME=[8FB512A0:01C92EA5]
X-Nokia-AV: Clean
Cc: sip@ietf.org
Subject: Re: [Sip] Is GRUU generated in the case of registration
	withinstance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi Francois,

Just in case you missed it, I repeat my proposal from
yesterday. The clarification could be added to the note 
within section 6 of Outbound like this:

   A Contact header field value with an instance-id media feature tag
   but no reg-id header field parameter is valid (this combination can
   be used in the GRUU [I-D.ietf-sip-gruu] specification as creation
   of gruu is not dependent on the presence or absence of reg-id 
   parameter), but one with a reg-id but no instance-id is not.   

Regards,

Erkki

>-----Original Message-----
>From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
>Behalf Of ext Francois Audet
>Sent: 14.October.2008 20:19
>To: Christer Holmberg; Paul Kyzivat
>Cc: sip@ietf.org
>Subject: Re: [Sip] Is GRUU generated in the case of 
>registration withinstance-ID and reg-ID
>
>Can you propose actual text for a specific section. 
>
>> -----Original Message-----
>> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] 
>> Sent: Monday, October 13, 2008 22:13
>> To: Paul Kyzivat
>> Cc: Michael Procter; sip@ietf.org; Audet, Francois (SC100:3055)
>> Subject: RE: [Sip] Is GRUU generated in the case of 
>> registration with instance-ID and reg-ID
>> 
>> 
>> Hi, 
>> 
>> >>Yes. The question was whether instance-id AND reg-id also create a
>> gruu.
>> >>The answer seems to be yes, but I think it would be good 
>to clarify 
>> >>that somewhere.
>> >
>> >Since reg-id isn't mentioned in gruu, its irrelevant to the 
>> gruu spec,
>> just as any other parameters are.
>> 
>> That is why I proposed it is clarified in the outbound spec :)
>> 
>> Regards,
>> 
>> Christer
>> 
>_______________________________________________
>Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>This list is for NEW development of the core SIP Protocol
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sipping@ietf.org for new developments on the application of sip
>
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct 15 08:08:32 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 255C428C23F;
	Wed, 15 Oct 2008 08:08:32 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7CFE728C23F
	for <sip@core3.amsl.com>; Wed, 15 Oct 2008 08:08:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id wZO0IusNza6y for <sip@core3.amsl.com>;
	Wed, 15 Oct 2008 08:08:24 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6])
	by core3.amsl.com (Postfix) with ESMTP id 6EE0728C22A
	for <sip@ietf.org>; Wed, 15 Oct 2008 08:08:24 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com
	(216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.291.1;
	Wed, 15 Oct 2008 11:08:02 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with
	mapi; Wed, 15 Oct 2008 11:08:02 -0400
From: Bob Penfield <BPenfield@acmepacket.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "Karthikeyan Gopal "
	<g_karthikeyan@hcl.in>, "Elwell, John" <john.elwell@siemens.com>, Juha
	Heinanen <jh@tutpro.com>, "sip@ietf.org" <sip@ietf.org>, Paul Kyzivat
	<pkyzivat@cisco.com>, Dean Willis <dean.willis@softarmor.com>
Date: Wed, 15 Oct 2008 11:07:56 -0400
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackta1Q4oPZYeoZEQAiUqa8JyoYU4gAAB04gACPIDEAABL7/QAAE9WcQABkzIjAABW7X8AAOZVdw
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC3128899B4FC@mail>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18668.50247.121832.271341@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se><18668.51383.505850.963592@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se><18672.19846.621765.332209@taimen.test.fi><2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com><18673.5665.337048.880648@taimen.test.fi><2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com><18673.62485.295631.933830@taimen.test.fi><2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com><18675.7684.207071.901832@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se><18675.41223.587006.241312@taimen.test.fi><18675.41926.583512.912121@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se><E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com><0D5F89FAC29E2C41B98A6A762007F5D0012A2353@GBNTHT12009MSX.gb002.
	siemens.	net> <E6C2E8
	958BA59A4FB960963D475F7AC312843F60B4@mail.acmepacket.com>
	<E971678290A1BA41BD96554DBA1211B6ABF788@CHN-HCLT-EVS02.HCLT.CORP.HCL.IN>
	<CA9998CD4A020D418654FCDEF4E707DF086DA2E3@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF086DA2E3@esealmw113.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



>-----Original Message-----
>From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
>Sent: Wednesday, October 15, 2008 4:04 AM
>To: Karthikeyan Gopal ; Bob Penfield; Elwell, John; Juha Heinanen; sip@ietf.org; Paul Kyzivat; Dean Willis
>Subject: RE: [Sip] Dual registration without Outbound
>
>
>Hi,
>
>>I guess the problem arises when you want to do a single REGISTER
>>request for both instances. If I the use case correctly, the UA would
>>send two REGISTER requests (one on each interface) and
>>both REGISTERs would have the two Contacts (one for each instance-id).
>>Something like this:
>>
>>First REGISTER to Outbound-proxy #1
>>
>>   REGISTER sip:example.com SIP/2.0
>>   Via: SIP/2.0/TCP 1.1.1.1;branch=z9hG4bKnashds7-1
>>   From: Bob <sip:bob@example.com>;tag=7F94778B653B-1
>>   To: Bob <sip:bob@example.com>
>>   Call-ID: 16CB75F21C70-1
>>   CSeq: 1 REGISTER
>>   Supported: path, outbound
>>   Route: <sip:ep1.example.com;lr>
>>   Contact: <sip:bob@1.1.1.1;transport=tcp>;reg-id=1
>>    ;+sip.instance="<urn:uuid:00000000-0000-1000-8000-AABBCCDDEEFF>"
>>   Contact: <sip:bob@2.2.2.2;transport=tcp>;reg-id=2
>>    ;+sip.instance="<urn:uuid:00000000-0000-1000-8000-BBCCDDEEFF00>"
>>
>>Second REGISTER to Outbound-proxy #2
>>
>>   REGISTER sip:example.com SIP/2.0
>>   Via: SIP/2.0/TCP 2.2.2.2;branch=z9hG4bKnashds7-2
>>   From: Bob <sip:bob@example.com>;tag=7F94778B653B-2
>>   To: Bob <sip:bob@example.com>
>>   Call-ID: 16CB75F21C70-2
>>   CSeq: 1 REGISTER
>>   Supported: path, outbound
>>   Route: <sip:ep2.example.com;lr>
>>   Contact: <sip:bob@2.2.2.2;transport=tcp>;reg-id=1
>>    ;+sip.instance="<urn:uuid:00000000-0000-1000-8000-BBCCDDEEFF00>"
>>   Contact: <sip:bob@1.1.1.1;transport=tcp>;reg-id=2
>>    ;+sip.instance="<urn:uuid:00000000-0000-1000-8000-AABBCCDDEEFF>"
>>
>>Thus the UA could receive requests for either Contact on either of the
>>two outbound flows.
>>
>>Is having two UA instances in the same request legal with the current
>>text?
>
>Isn't the edge proxy always going to send incoming request (towards the
>UA) to the address/port where the REGISTER came from, in order for the
>request to traverse the NAT?
>

That is exactly the desired effect. Since outbound ignores the Contact's address and sends it over the existing connection and it arrives over the interface that the REGISTER was sent on.

I did not see anything in Outbound that defines how the Authoritative Proxy chooses between the flows for a given contact, but, if it always tried reg-id=1 (i.e. the lowest reg-id) first, then if both flows were still up, two request would be forked (one on each flow) and the one for 1.1.1.1 would arrive on the interface for 1.1.1.1 and the other for 2.2.2.2 would arrive on the interface for 2.2.2.2.

If one of the flows was down, both requests would arrive on the other flow.

>So, I don't think you can perform the kind of "third party registration"
>which your example shows.

This is not really 3rd party registration since both requests arrive at the single User Agent that happens to have two Contact Instances.

>
>Regards,
>
>Christer
>





-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens.com]
Sent: Tuesday, October 14, 2008 11:02 AM
To: Bob Penfield; Christer Holmberg; Juha Heinanen; sip@ietf.org; Paul
Kyzivat; Dean Willis
Subject: RE: [Sip] Dual registration without Outbound



> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
> Bob Penfield
> Sent: 14 October 2008 15:41
> To: Christer Holmberg; Juha Heinanen; sip@ietf.org; Paul Kyzivat; Dean

> Willis
> Subject: Re: [Sip] Dual registration without Outbound
>
> For both GRUU and Outbound a given instance-id
> (+sip-instance) actually represents a single UA contact instance
> rather than just a single User Agent. The basic idea behind GRUU is
> that a request addressed to a GRUU is forwarded by the proxy to a
> specific Contact address. The goal is the same with Outbound but it
> adds multiple flows/paths to that UA Contact. This is reflected in the

> proxy procedures in both GRUU and Outbound.
>
> In both cases, the proxy does serial forking to Contacts with the same

> instance-id.
>
> For GRUU it starts with the most-recently registered binding
> (according to section 6.1 of GRUU):
>
>        The proxy MUST select the most recently refreshed
>        contact.  As with draft-ietf-sip-outbound, if a request to this
>        target fails with a 408 (Request Timeout) or 430 (Flow Failed)
>        response, the proxy SHOULD retry with the next most recently
>        refreshed contact.  Furthermore, if the request fails with any
>        other response, the proxy MUST NOT retry on any other contacts
>        for this instance.
>
> For Outbound, it attempts the registered flows (according to section 7

> of Outbound):
>
>    When a proxy uses the location service to look up a registration
>    binding and then proxies a request to a particular contact, it
>    selects a contact to use normally, with a few additional rules:
>
>    o  The proxy MUST NOT populate the target set with more than one
>       contact with the same AOR and instance-id at a time.
>    o  If a request for a particular AOR and instance-id fails with a
> 430
>       (Flow Failed) response, the proxy SHOULD replace the failed
> branch
>       with another target (if one is available) with the same AOR and
>       instance-id, but a different reg-id.
>    o  If the proxy receives a final response from a branch other than
> a
>       408 (Request Timeout) or a 430 (Flow Failed) response, the proxy
>       MUST NOT forward the same request to another target representing
>       the same AOR and instance-id.  The targeted instance has already
>       provided its response.
>
> Therefore, a User Agent that is registering multiple Contacts to allow

> the possibility of parallel forking would need to have a separate
> instance-id for each Contact.
>
> For User Agent's that have multiple interfaces, it could use the MAC
> address of each interface to create a unique UUID URN for each
> contact.
>
> Thus, the following scenario is possible:
>
>   UA_Contact_wlan;+sip-instance=ID_1;reg-id=1 ----- OB_1 ----- REG_1
>   UA_Contact_wlan;+sip-instance=ID_1;reg-id=2 ----- OB_2 ----- REG_2
>   UA_Contact_3g;+sip-instance=ID_2;reg-id=1   ----- OB_1 ----- REG_1
>   UA_Contact_3g;+sip-instance=ID_2;reg-id=2   ----- OB_2 ----- REG_2
>
> Unfortunately, the current text in section 4.1 says that a UA has "an
> Instance Identifier".
[JRE] In an earlier email I was trying to say roughly the same thing,
except the way I looked at it was that a device with multiple interfaces
would logically contain a UA for each interface, and each UA would than
have a single instance ID. In that case the text in section 4.1 still
works.

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

DISCLAIMER:
------------------------------------------------------------------------
-----------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and
intended for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its
affiliates. Any views or opinions presented in this email are solely
those of the author and may not necessarily reflect the opinions of HCL
or its affiliates.
Any form of reproduction, dissemination, copying, disclosure,
modification, distribution and / or publication of this message without
the prior written consent of the author of this e-mail is strictly
prohibited. If you have received this email in error please delete it
and notify the sender immediately. Before opening any mail and
attachments please check them for viruses and defect.

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


From sip-bounces@ietf.org  Wed Oct 15 08:12:14 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 597A83A69A2;
	Wed, 15 Oct 2008 08:12:14 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C4CCF3A6981
	for <sip@core3.amsl.com>; Wed, 15 Oct 2008 08:12:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id udUYpwCYhjyj for <sip@core3.amsl.com>;
	Wed, 15 Oct 2008 08:12:13 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6])
	by core3.amsl.com (Postfix) with ESMTP id D82453A69A2
	for <sip@ietf.org>; Wed, 15 Oct 2008 08:12:12 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com
	(216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.291.1;
	Wed, 15 Oct 2008 11:11:50 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with
	mapi; Wed, 15 Oct 2008 11:11:50 -0400
From: Bob Penfield <BPenfield@acmepacket.com>
To: "Elwell, John" <john.elwell@siemens.com>, Christer Holmberg
	<christer.holmberg@ericsson.com>, Juha Heinanen <jh@tutpro.com>,
	"sip@ietf.org" <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Date: Wed, 15 Oct 2008 11:11:47 -0400
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackta1Q4oPZYeoZEQAiUqa8JyoYU4gAAB04gACPIDEAABL7/QAAjTT0wAAEXIbAAAE5eEAAAG/tQAA3MBgA=
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC3128899B51F@mail>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18668.50247.121832.271341@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
	<18668.51383.505850.963592@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
	<18673.5665.337048.880648@taimen.test.fi>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com> A
	<CA9998CD4A020D418654FCDEF4E707DF086DA432@esealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBNTHT12009MSX.gb002.siemens.net>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBNTHT12009MSX.gb002.siemens.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



>-----Original Message-----
>From: Elwell, John [mailto:john.elwell@siemens.com]
>Sent: Wednesday, October 15, 2008 4:52 AM
>To: Christer Holmberg; Bob Penfield; Juha Heinanen; sip@ietf.org; Paul Kyzivat; Dean Willis
>Subject: RE: [Sip] Dual registration without Outbound
>
>
>> -----Original Message-----
>> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
>> Sent: 15 October 2008 09:32
>> To: Elwell, John; Bob Penfield; Juha Heinanen; sip@ietf.org;
>> Paul Kyzivat; Dean Willis
>> Subject: RE: [Sip] Dual registration without Outbound
>>
>>
>> Hi,
>>
>>>It might well be the same software stack from the IP layer or the
>>>transport layer upwards, but logically it acts as two UAs (with some
>>>application software at the top to bind the two together).
>>>At least from the proxy perspective it looks like two UAs. Viewing it
>>>your way is perhaps also valid (but requires a minor change to
>>>sip-outbound).
>>
>> And, if I understood correctly, that is the change Juha has
>> been asking
>> for :)
>[JRE] Exactly. But viewing it my way possibly requires less change to
>sip-outbound, since much of it talks about one instance ID per UA (e.g.,
>section 3.1).
>
>Whichever way we view it, the following statement in 4.1 seems to be
>problematic:
>"Instance ID MUST NOT change as the device moves from one network to
>   another."

If the UA uses the interface's MAC address to generate the instance-id, it would not change when you move between networks.

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


From sip-bounces@ietf.org  Wed Oct 15 08:58:48 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C9E9E28C158;
	Wed, 15 Oct 2008 08:58:48 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CDE8F28C253
	for <sip@core3.amsl.com>; Wed, 15 Oct 2008 08:58:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Z75XofyBPGZA for <sip@core3.amsl.com>;
	Wed, 15 Oct 2008 08:58:43 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56])
	by core3.amsl.com (Postfix) with ESMTP id DDD8F28C24E
	for <sip@ietf.org>; Wed, 15 Oct 2008 08:58:42 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	m9FFuHq04959; Wed, 15 Oct 2008 15:56:17 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 15 Oct 2008 10:58:53 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF19BFCF4E@zrc2hxm0.corp.nortel.com>
In-Reply-To: <48F580BA.9090001@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
Thread-Index: Ackuh6Joak8qt4eARYi38hw1ywpsgQAVz+6w
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>
	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>
	<48F580BA.9090001@softarmor.com>
From: "Francois Audet" <audet@nortel.com>
To: "Dean Willis" <dean.willis@softarmor.com>,
	"Christer Holmberg" <christer.holmberg@ericsson.com>
Cc: sip@ietf.org
Subject: Re: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Agree. Using instance-id by itself has lots of usages. 

> -----Original Message-----
> From: Dean Willis [mailto:dean.willis@softarmor.com] 
> Sent: Tuesday, October 14, 2008 22:34
> To: Christer Holmberg
> Cc: Audet, Francois (SC100:3055); sip@ietf.org
> Subject: Re: [Sip] Is GRUU generated in the case of 
> registration with instance-ID and reg-ID
> 
> Christer Holmberg wrote:
> > So, the following applies:
> > 
> > 
> > request                                        response
> > -------------------------------------------------------
> > 
> > instance-id AND Supported:gruu               = gruu
> > instance-id AND reg-id                       = outbound
> > instance-id AND reg-id AND Supported:gruu    = outbound AND gruu
> > instance-id                                  = n/a
> > 
> 
> It seems like instance-id by itself could be useful for 
> detecting expired registrations from the same node, outside 
> of gruu or outbound.
> 
> --
> Dean
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct 15 09:01:33 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2970A28C21F;
	Wed, 15 Oct 2008 09:01:33 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 662E63A6923
	for <sip@core3.amsl.com>; Wed, 15 Oct 2008 09:01:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id eQ5x5dewqvTP for <sip@core3.amsl.com>;
	Wed, 15 Oct 2008 09:01:30 -0700 (PDT)
Received: from zcars04f.nortel.com (zcars04f.nortel.com [47.129.242.57])
	by core3.amsl.com (Postfix) with ESMTP id 577BE3A677C
	for <sip@ietf.org>; Wed, 15 Oct 2008 09:01:30 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m9FG1sK26058; Wed, 15 Oct 2008 16:01:54 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 15 Oct 2008 11:01:49 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF19BFCF64@zrc2hxm0.corp.nortel.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF086A6463@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
Thread-Index: Ackthpxe2j+IIv2ATNuWao7mqiLjvAANMqTQABlcJkAAGm/XYAAVLEcg
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>
	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>
	<48F23D27.8030305@voip.co.uk>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se>
	<48F2FC13.1070308@voip.co.uk> <48F34E3B.80106@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EE@esealmw113.eemea.ericsson.se>
	<48F3D191.5000007@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0864CEFC@esealmw113.eemea.ericsson.se>
	<1ECE0EB50388174790F9694F77522CCF19BAB943@zrc2hxm0.corp.nortel.com>
	<CA9998CD4A020D418654FCDEF4E707DF086A6463@esealmw113.eemea.ericsson.se>
From: "Francois Audet" <audet@nortel.com>
To: "Christer Holmberg" <christer.holmberg@ericsson.com>,
	"Paul Kyzivat" <pkyzivat@cisco.com>
Cc: sip@ietf.org
Subject: Re: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I'm ok with this and unless there are complaints, I'll add it to the text. 

> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] 
> Sent: Tuesday, October 14, 2008 22:58
> To: Audet, Francois (SC100:3055); Paul Kyzivat
> Cc: Michael Procter; sip@ietf.org
> Subject: RE: [Sip] Is GRUU generated in the case of 
> registration with instance-ID and reg-ID
> 
> 
> Hi,
> 
> The text would be something like:
> 
> "NOTE: If the registrar supports gruu 
> [reference-to-gruu-spec], the presence of the instance-id in 
> the REGISTER request will also trigger the registrar to 
> generate a gruu for the user, as described in 
> [reference-to-gruu-spec]."
> 
> I will look for a place in the outbound draft where to put 
> it, but it really isn't more complicated than that. Just a 
> simple clarification note :)
> 
> Regards,
> 
> Christer
> 
>  
> 
> -----Original Message-----
> From: Francois Audet [mailto:audet@nortel.com]
> Sent: 14. lokakuuta 2008 20:19
> To: Christer Holmberg; Paul Kyzivat
> Cc: Michael Procter; sip@ietf.org
> Subject: RE: [Sip] Is GRUU generated in the case of 
> registration with instance-ID and reg-ID
> 
> Can you propose actual text for a specific section. 
> 
> > -----Original Message-----
> > From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> > Sent: Monday, October 13, 2008 22:13
> > To: Paul Kyzivat
> > Cc: Michael Procter; sip@ietf.org; Audet, Francois (SC100:3055)
> > Subject: RE: [Sip] Is GRUU generated in the case of 
> registration with 
> > instance-ID and reg-ID
> > 
> > 
> > Hi,
> > 
> > >>Yes. The question was whether instance-id AND reg-id also create a
> > gruu.
> > >>The answer seems to be yes, but I think it would be good 
> to clarify 
> > >>that somewhere.
> > >
> > >Since reg-id isn't mentioned in gruu, its irrelevant to the
> > gruu spec,
> > just as any other parameters are.
> > 
> > That is why I proposed it is clarified in the outbound spec :)
> > 
> > Regards,
> > 
> > Christer
> > 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct 15 09:03:57 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F002C3A6923;
	Wed, 15 Oct 2008 09:03:56 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6770E3A6923
	for <sip@core3.amsl.com>; Wed, 15 Oct 2008 09:03:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id P8ET78Lrjuqt for <sip@core3.amsl.com>;
	Wed, 15 Oct 2008 09:03:54 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56])
	by core3.amsl.com (Postfix) with ESMTP id 646B23A68C0
	for <sip@ietf.org>; Wed, 15 Oct 2008 09:03:54 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m9FG3XV22995; Wed, 15 Oct 2008 16:03:34 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 15 Oct 2008 11:02:13 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF19BFCF67@zrc2hxm0.corp.nortel.com>
In-Reply-To: <7A726F54F791494C8D8C87F13736E80EF82AC5@vaebe106.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Is GRUU generated in the case of registration
	withinstance-ID and reg-ID
Thread-Index: Ackthpxe2j+IIv2ATNuWao7mqiLjvAANMqTQABlcJkAAIRzsIAAOgrwQ
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se><1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com><CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se><48F23D27.8030305@voip.co.uk><CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se><48F2FC13.1070308@voip.co.uk>
	<48F34E3B.80106@cisco.com><CA9998CD4A020D418654FCDEF4E707DF05C0F8EE@esealmw113.eemea.ericsson.se><48F3D191.5000007@cisco.com><CA9998CD4A020D418654FCDEF4E707DF0864CEFC@esealmw113.eemea.ericsson.se>
	<1ECE0EB50388174790F9694F77522CCF19BAB943@zrc2hxm0.corp.nortel.com>
	<7A726F54F791494C8D8C87F13736E80EF82AC5@vaebe106.NOE.Nokia.com>
From: "Francois Audet" <audet@nortel.com>
To: <Erkki.Koivusalo@nokia.com>, <christer.holmberg@ericsson.com>,
	<pkyzivat@cisco.com>
Cc: sip@ietf.org
Subject: Re: [Sip] Is GRUU generated in the case of registration
	withinstance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I'm ok with this, and unless there are complaints, I'll add it to the text. 

> -----Original Message-----
> From: Erkki.Koivusalo@nokia.com [mailto:Erkki.Koivusalo@nokia.com] 
> Sent: Wednesday, October 15, 2008 02:08
> To: Audet, Francois (SC100:3055); 
> christer.holmberg@ericsson.com; pkyzivat@cisco.com
> Cc: sip@ietf.org
> Subject: RE: [Sip] Is GRUU generated in the case of 
> registration withinstance-ID and reg-ID
> 
> 
> Hi Francois,
> 
> Just in case you missed it, I repeat my proposal from 
> yesterday. The clarification could be added to the note 
> within section 6 of Outbound like this:
> 
>    A Contact header field value with an instance-id media feature tag
>    but no reg-id header field parameter is valid (this combination can
>    be used in the GRUU [I-D.ietf-sip-gruu] specification as creation
>    of gruu is not dependent on the presence or absence of reg-id 
>    parameter), but one with a reg-id but no instance-id is not.   
> 
> Regards,
> 
> Erkki
> 
> >-----Original Message-----
> >From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of 
> >ext Francois Audet
> >Sent: 14.October.2008 20:19
> >To: Christer Holmberg; Paul Kyzivat
> >Cc: sip@ietf.org
> >Subject: Re: [Sip] Is GRUU generated in the case of registration 
> >withinstance-ID and reg-ID
> >
> >Can you propose actual text for a specific section. 
> >
> >> -----Original Message-----
> >> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> >> Sent: Monday, October 13, 2008 22:13
> >> To: Paul Kyzivat
> >> Cc: Michael Procter; sip@ietf.org; Audet, Francois (SC100:3055)
> >> Subject: RE: [Sip] Is GRUU generated in the case of 
> registration with 
> >> instance-ID and reg-ID
> >> 
> >> 
> >> Hi,
> >> 
> >> >>Yes. The question was whether instance-id AND reg-id 
> also create a
> >> gruu.
> >> >>The answer seems to be yes, but I think it would be good
> >to clarify
> >> >>that somewhere.
> >> >
> >> >Since reg-id isn't mentioned in gruu, its irrelevant to the
> >> gruu spec,
> >> just as any other parameters are.
> >> 
> >> That is why I proposed it is clarified in the outbound spec :)
> >> 
> >> Regards,
> >> 
> >> Christer
> >> 
> >_______________________________________________
> >Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> >This list is for NEW development of the core SIP Protocol Use 
> >sip-implementors@cs.columbia.edu for questions on current sip Use 
> >sipping@ietf.org for new developments on the application of sip
> >
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct 15 10:13:14 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E544528C20B;
	Wed, 15 Oct 2008 10:13:13 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D4CDC28C20B
	for <sip@core3.amsl.com>; Wed, 15 Oct 2008 10:13:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id txMOxzkehy2P for <sip@core3.amsl.com>;
	Wed, 15 Oct 2008 10:13:12 -0700 (PDT)
Received: from smtp1.versatel.nl (smtp1.versatel.nl [62.58.50.88])
	by core3.amsl.com (Postfix) with ESMTP id E2F153A6B81
	for <sip@ietf.org>; Wed, 15 Oct 2008 10:13:11 -0700 (PDT)
Received: (qmail 28666 invoked by uid 0); 15 Oct 2008 17:14:03 -0000
Received: from ip198-11-212-87.adsl2.static.versatel.nl (HELO [192.168.2.155])
	([87.212.11.198]) (envelope-sender <jbemmel@zonnet.nl>)
	by smtp1.versatel.nl (qmail-ldap-1.03) with SMTP
	for < >; 15 Oct 2008 17:14:03 -0000
Message-ID: <48F624D8.7070000@zonnet.nl>
Date: Wed, 15 Oct 2008 19:14:00 +0200
From: Jeroen van Bemmel <jbemmel@zonnet.nl>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: IETF SIP List <sip@ietf.org>
Subject: [Sip] minor editorial outbound comment
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

All,

Just a minor remark: outbound-15 references 
draft-ietf-behave-rfc3489bis-15, there is now a -18 version.
Not sure if the WGLC process includes an automatic check for the latest 
versions of references?

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


From sip-bounces@ietf.org  Wed Oct 15 10:42:12 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 62B703A6C54;
	Wed, 15 Oct 2008 10:42:12 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5CF4D3A6922
	for <sip@core3.amsl.com>; Wed, 15 Oct 2008 10:42:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.197
X-Spam-Level: 
X-Spam-Status: No, score=-6.197 tagged_above=-999 required=5 tests=[AWL=0.052, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XHlyitEuOImj for <sip@core3.amsl.com>;
	Wed, 15 Oct 2008 10:42:09 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 6855B3A6768
	for <sip@ietf.org>; Wed, 15 Oct 2008 10:42:09 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	3258D212C3; Wed, 15 Oct 2008 19:42:43 +0200 (CEST)
X-AuditID: c1b4fb3e-a6e81bb000007a96-f4-48f62b93fd50
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	1136F200C2; Wed, 15 Oct 2008 19:42:43 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Oct 2008 19:42:42 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 15 Oct 2008 19:41:35 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCF8E@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
Thread-Index: Ackuh6Joak8qt4eARYi38hw1ywpsgQAVz+6wAAOYuQI=
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>
	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>
	<48F580BA.9090001@softarmor.com>
	<1ECE0EB50388174790F9694F77522CCF19BFCF4E@zrc2hxm0.corp.nortel.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Francois Audet" <audet@nortel.com>,
	"Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 15 Oct 2008 17:42:42.0867 (UTC)
	FILETIME=[6D102030:01C92EED]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org
Subject: Re: [Sip] Is GRUU generated in the case of registration with
	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi,

>Agree. Using instance-id by itself has lots of usages.

Yes. The "n/a" in the table was only from a pure gruu- and outbound perspective.

Regards,

Christer

 

 



> -----Original Message-----
> From: Dean Willis [mailto:dean.willis@softarmor.com]
> Sent: Tuesday, October 14, 2008 22:34
> To: Christer Holmberg
> Cc: Audet, Francois (SC100:3055); sip@ietf.org
> Subject: Re: [Sip] Is GRUU generated in the case of
> registration with instance-ID and reg-ID
>
> Christer Holmberg wrote:
> > So, the following applies:
> >
> >
> > request                                        response
> > -------------------------------------------------------
> >
> > instance-id AND Supported:gruu               = gruu
> > instance-id AND reg-id                       = outbound
> > instance-id AND reg-id AND Supported:gruu    = outbound AND gruu
> > instance-id                                  = n/a
> >
>
> It seems like instance-id by itself could be useful for
> detecting expired registrations from the same node, outside
> of gruu or outbound.
>
> --
> Dean
>

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


From sip-bounces@ietf.org  Wed Oct 15 10:55:02 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 29F2B28C229;
	Wed, 15 Oct 2008 10:55:02 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9204F3A6A0C
	for <sip@core3.amsl.com>; Wed, 15 Oct 2008 10:55:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.492
X-Spam-Level: 
X-Spam-Status: No, score=-6.492 tagged_above=-999 required=5 tests=[AWL=0.107, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id PlFHTjnx6CKe for <sip@core3.amsl.com>;
	Wed, 15 Oct 2008 10:55:00 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 71D7D3A6C80
	for <sip@ietf.org>; Wed, 15 Oct 2008 10:55:00 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,417,1220227200"; d="scan'208";a="24388064"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 15 Oct 2008 17:55:31 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9FHtVEn004609; 
	Wed, 15 Oct 2008 13:55:31 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9FHtVZB007279;
	Wed, 15 Oct 2008 17:55:31 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Oct 2008 13:55:31 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Oct 2008 13:55:30 -0400
Message-ID: <48F62E90.5090905@cisco.com>
Date: Wed, 15 Oct 2008 13:55:28 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Francois Audet <audet@nortel.com>
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>	<48F23D27.8030305@voip.co.uk>	<CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se>	<48F2FC13.1070308@voip.co.uk>
	<48F34E3B.80106@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EE@esealmw113.eemea.ericsson.se>	<48F3D191.5000007@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0864CEFC@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19BAB943@zrc2hxm0.corp.nortel.com>	<CA9998CD4A020D418654FCDEF4E707DF086A6463@esealmw113.eemea.ericsson.se>
	<1ECE0EB50388174790F9694F77522CCF19BFCF64@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF19BFCF64@zrc2hxm0.corp.nortel.com>
X-OriginalArrivalTime: 15 Oct 2008 17:55:30.0789 (UTC)
	FILETIME=[36C7B950:01C92EEF]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2671; t=1224093331;
	x=1224957331; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Is=20GRUU=20generated=20in=20th
	e=20case=20of=20registration=20with=09instance-ID=0A=20and=2
	0reg-ID |Sender:=20
	|To:=20Francois=20Audet=20<audet@nortel.com>;
	bh=5auICi2OHQKDSGH505Jbw4A2ByAOck/kHhVzID3Ndl0=;
	b=rnxZpJ5Q3R5RnuUQzO/ifmmnnL1KTtgfGGnIUXAM/56wWZ5ZFWY5D+zH3/
	F3VHbI3twWbH9rvkCoEjPbKEccDoVdDwpaRcDxwyvx7cSxzF9rgbag237yh4
	8zwGO2jZHA;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: sip@ietf.org, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Is GRUU generated in the case of registration
 with	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Francois Audet wrote:
> I'm ok with this and unless there are complaints, I'll add it to the text. 

This will cause a two way dependency between gruu and outbound.
Maybe that is ok, since gruu has been stable for months (years?) and has 
been stalled awaiting the clearance of its dependency on outbound.

	Thanks,
	Paul

>> -----Original Message-----
>> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] 
>> Sent: Tuesday, October 14, 2008 22:58
>> To: Audet, Francois (SC100:3055); Paul Kyzivat
>> Cc: Michael Procter; sip@ietf.org
>> Subject: RE: [Sip] Is GRUU generated in the case of 
>> registration with instance-ID and reg-ID
>>
>>
>> Hi,
>>
>> The text would be something like:
>>
>> "NOTE: If the registrar supports gruu 
>> [reference-to-gruu-spec], the presence of the instance-id in 
>> the REGISTER request will also trigger the registrar to 
>> generate a gruu for the user, as described in 
>> [reference-to-gruu-spec]."
>>
>> I will look for a place in the outbound draft where to put 
>> it, but it really isn't more complicated than that. Just a 
>> simple clarification note :)
>>
>> Regards,
>>
>> Christer
>>
>>  
>>
>> -----Original Message-----
>> From: Francois Audet [mailto:audet@nortel.com]
>> Sent: 14. lokakuuta 2008 20:19
>> To: Christer Holmberg; Paul Kyzivat
>> Cc: Michael Procter; sip@ietf.org
>> Subject: RE: [Sip] Is GRUU generated in the case of 
>> registration with instance-ID and reg-ID
>>
>> Can you propose actual text for a specific section. 
>>
>>> -----Original Message-----
>>> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
>>> Sent: Monday, October 13, 2008 22:13
>>> To: Paul Kyzivat
>>> Cc: Michael Procter; sip@ietf.org; Audet, Francois (SC100:3055)
>>> Subject: RE: [Sip] Is GRUU generated in the case of 
>> registration with 
>>> instance-ID and reg-ID
>>>
>>>
>>> Hi,
>>>
>>>>> Yes. The question was whether instance-id AND reg-id also create a
>>> gruu.
>>>>> The answer seems to be yes, but I think it would be good 
>> to clarify 
>>>>> that somewhere.
>>>> Since reg-id isn't mentioned in gruu, its irrelevant to the
>>> gruu spec,
>>> just as any other parameters are.
>>>
>>> That is why I proposed it is clarified in the outbound spec :)
>>>
>>> Regards,
>>>
>>> Christer
>>>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct 15 15:28:45 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CD9D23A6A3F;
	Wed, 15 Oct 2008 15:28:45 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1C1383A6A3F
	for <sip@core3.amsl.com>; Wed, 15 Oct 2008 15:28:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.613
X-Spam-Level: 
X-Spam-Status: No, score=-2.613 tagged_above=-999 required=5
	tests=[AWL=-0.014, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id mMCKo4c2DCDc for <sip@core3.amsl.com>;
	Wed, 15 Oct 2008 15:28:43 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 5C1023A687A
	for <sip@ietf.org>; Wed, 15 Oct 2008 15:28:43 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9FMTZtt001759
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Wed, 15 Oct 2008 17:29:37 -0500
Message-Id: <068483D2-2A92-4DA0-A177-F8CACACA72A7@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: "Elwell, John" <john.elwell@siemens.com>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBNTHT12009MSX.gb002.siemens.net>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 15 Oct 2008 17:29:30 -0500
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18668.50247.121832.271341@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
	<18668.51383.505850.963592@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
	<18673.5665.337048.880648@taimen.test.fi>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
	A <CA9998CD4A020D418654FCDEF4E707DF086DA432@e!
	sealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBNTHT12009MSX.gb002.siemens.net>
X-Mailer: Apple Mail (2.929.2)
Cc: Bob Penfield <BPenfield@acmepacket.com>, sip@ietf.org,
	Paul Kyzivat <pkyzivat@cisco.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 15, 2008, at 3:51 AM, Elwell, John wrote:

>
> "Instance ID MUST NOT change as the device moves from one network to
>   another."

If the instance ID is derived from the MAC address, then clearly the  
instance will change depending on the type of network being used.

--
Dean

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


From sip-bounces@ietf.org  Wed Oct 15 15:38:17 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3422C3A683D;
	Wed, 15 Oct 2008 15:38:17 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6A47A3A683D
	for <sip@core3.amsl.com>; Wed, 15 Oct 2008 15:38:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.613
X-Spam-Level: 
X-Spam-Status: No, score=-2.613 tagged_above=-999 required=5
	tests=[AWL=-0.014, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id S8h-MtGn06wi for <sip@core3.amsl.com>;
	Wed, 15 Oct 2008 15:38:14 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id B4F263A679C
	for <sip@ietf.org>; Wed, 15 Oct 2008 15:38:14 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9FMcT4O001822
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT)
	for <sip@ietf.org>; Wed, 15 Oct 2008 17:38:30 -0500
Message-Id: <06CE0CC4-957A-4F77-8A00-C83A2A06BA2D@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: SIP IETF <sip@ietf.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 15 Oct 2008 17:38:23 -0500
X-Mailer: Apple Mail (2.929.2)
Subject: [Sip] Attendance poll for Minneapolis
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


I'm wondering how badly we'll be impacted by the ongoing economic panic.

If you would normally be in-attendance at the Minneapolis IETF, but  
aren't going to be due to travel or budget constraints peculiar to the  
current environment, please let me know.

--
Dean

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


From sip-bounces@ietf.org  Wed Oct 15 15:52:17 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8C63A3A688F;
	Wed, 15 Oct 2008 15:52:17 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 84D513A688F
	for <sip@core3.amsl.com>; Wed, 15 Oct 2008 15:52:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.495
X-Spam-Level: 
X-Spam-Status: No, score=-6.495 tagged_above=-999 required=5 tests=[AWL=0.104, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id m3yQUicRiy08 for <sip@core3.amsl.com>;
	Wed, 15 Oct 2008 15:52:15 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 8EC453A6807
	for <sip@ietf.org>; Wed, 15 Oct 2008 15:52:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,418,1220227200"; d="scan'208";a="24425784"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 15 Oct 2008 22:52:47 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9FMqlNr010569; 
	Wed, 15 Oct 2008 18:52:47 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9FMqlRp028836;
	Wed, 15 Oct 2008 22:52:47 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Oct 2008 18:52:47 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Oct 2008 18:52:46 -0400
Message-ID: <48F6743A.4060006@cisco.com>
Date: Wed, 15 Oct 2008 18:52:42 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
	<18673.5665.337048.880648@taimen.test.fi>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
	A <CA9998CD4A020D418654FCDEF4E707DF086DA432@e!
	sealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBNTHT12009MSX.gb002.siemens.net>
	<068483D2-2A92-4DA0-A177-F8CACACA72A7@softarmor.com>
In-Reply-To: <068483D2-2A92-4DA0-A177-F8CACACA72A7@softarmor.com>
X-OriginalArrivalTime: 15 Oct 2008 22:52:46.0896 (UTC)
	FILETIME=[BDEDAB00:01C92F18]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1494; t=1224111167;
	x=1224975167; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Dual=20registration=20without=2
	0Outbound |Sender:=20
	|To:=20Dean=20Willis=20<dean.willis@softarmor.com>;
	bh=APaAPHDkCzgpANWOosmcFsr/6b72hGinuJ0uLYEKuPQ=;
	b=eWyMW3fgqMPaUOLvkgPUDvs6F9B3GUWMckFD3qLvicC6OBB21igZBy4P3D
	x/nyhkrFHeSPH6yFAd7MDc3ka0hjmGpTgS2O2CT8Xd35FXqEGTm7L4elSZhH
	atIY7LwS4A;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: Bob Penfield <BPenfield@acmepacket.com>, sip@ietf.org, "Elwell,
	John" <john.elwell@siemens.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Dean Willis wrote:
> 
> On Oct 15, 2008, at 3:51 AM, Elwell, John wrote:
> 
>>
>> "Instance ID MUST NOT change as the device moves from one network to
>>   another."

I've always viewed this as one worthwhile objective, but that there may 
be conflicting objectives that lead to multiple instance ids.

For instance, if I sell my device to Dean, he may not want it to have 
the same instance id it had when it was mine.

Or I may want to change ids so that it appears to others that I have two 
devices rather than one. (Maybe someone will try to correlate my 
location to the device I am using, and I want to throw them off.)

And with soft devices it is very subjective when what I have is one 
logical device or several.

I think all we can do is hope that the same instance id is used when the 
user is willing for some continuity of device identity to be perceived.

Trying to register the "same UA" concurrently with two different 
instance ids in an attempt to get parallel forked call attempts via 
different networks is creative but a bit ugly. For one thing its hard in 
general to guarantee that the two will be parallel forked. And the UA 
will have to attempt to correlate the two in order to realize they are 
the same and so process correctly. An SBC between the forking proxy and 
the UA is likely to disturb the CallID, the From, and the caller's 
Contact address. With those messed up the correlation will get difficult.

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


From sip-bounces@ietf.org  Wed Oct 15 23:02:45 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B3EEC3A6B45;
	Wed, 15 Oct 2008 23:02:45 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 37C983A6B48
	for <sip@core3.amsl.com>; Wed, 15 Oct 2008 23:02:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.198
X-Spam-Level: 
X-Spam-Status: No, score=-6.198 tagged_above=-999 required=5 tests=[AWL=0.051, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Nj83GiEKdaMT for <sip@core3.amsl.com>;
	Wed, 15 Oct 2008 23:02:43 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 32EA43A6B46
	for <sip@ietf.org>; Wed, 15 Oct 2008 23:02:43 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	57745218EC; Thu, 16 Oct 2008 08:03:32 +0200 (CEST)
X-AuditID: c1b4fb3e-a8e85bb000007a96-c2-48f6d92dda38
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	6727921672; Thu, 16 Oct 2008 08:03:25 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Oct 2008 08:02:40 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 16 Oct 2008 08:02:40 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF087246CE@esealmw113.eemea.ericsson.se>
In-Reply-To: <48F6743A.4060006@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckvGL+GMebrwH5ZQoKZad3USNhefAAO76Xg
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
	<18673.5665.337048.880648@taimen.test.fi>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
	A <CA9998CD4A020D418654FCDEF4E707DF086DA432@e!
	sealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBNTHT12009MSX.gb002.siemens.net>
	<068483D2-2A92-4DA0-A177-F8CACACA72A7@softarmor.com> <48F674
	3A.4060006@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>,
	"Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 16 Oct 2008 06:02:40.0881 (UTC)
	FILETIME=[CC576E10:01C92F54]
X-Brightmail-Tracker: AAAAAA==
Cc: Bob Penfield <BPenfield@acmepacket.com>, sip@ietf.org, "Elwell,
	John" <john.elwell@siemens.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>Trying to register the "same UA" concurrently with two different
instance ids in an attempt to get parallel forked call attempts via
different networks is creative but a bit ugly. For one thing 
>its hard in general to guarantee that the two will be parallel forked.
And the UA will have to attempt to correlate the two in order to realize
they are the same and so process correctly. An 
>SBC between the forking proxy and the UA is likely to disturb the
CallID, the From, and the caller's Contact address. With those messed up
the correlation will get difficult.

IF there is a need to do parallell forking to the "same UA", I think
it's better to simply allow it in Outbound - instead of trying to find
hacks on how to get around the current restrictions.

However, parallell forking in outbound should not be the default
behavior, because I strongly think that in most cases people only want
to receive the initial request on a SINGLE flow - no matter if they use
one or more contacts.

Regards,

Christer

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


From sip-bounces@ietf.org  Thu Oct 16 01:14:41 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A59F23A6B37;
	Thu, 16 Oct 2008 01:14:41 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 840A83A6ABB
	for <sip@core3.amsl.com>; Thu, 16 Oct 2008 01:14:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.564
X-Spam-Level: 
X-Spam-Status: No, score=-2.564 tagged_above=-999 required=5 tests=[AWL=0.035, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FGu4fyMEXaIz for <sip@core3.amsl.com>;
	Thu, 16 Oct 2008 01:14:39 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id 9FCD73A6AA9
	for <sip@ietf.org>; Thu, 16 Oct 2008 01:14:39 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K8T006D0O8ZC4@siemenscomms.co.uk> for sip@ietf.org; Thu,
	16 Oct 2008 09:14:59 +0100 (BST)
Date: Thu, 16 Oct 2008 09:14:57 +0100
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <E6C2E8958BA59A4FB960963D475F7AC3128899B51F@mail>
To: Bob Penfield <BPenfield@acmepacket.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>,
	Juha Heinanen <jh@tutpro.com>, sip@ietf.org,
	Paul Kyzivat <pkyzivat@cisco.com>, Dean Willis <dean.willis@softarmor.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D0012DB621@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackta1Q4oPZYeoZEQAiUqa8JyoYU4gAAB04gACPIDEAABL7/QAAjTT0wAAEXIbAAAE5eEAAAG/tQAA3MBgAAI8AvQA==
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18668.50247.121832.271341@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
	<18668.51383.505850.963592@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
	<18673.5665.337048.880648@taimen.test.fi>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBNTHT12009MSX.gb002.siemens.net>
	<E6C2E8958BA59A4FB960963D475F7AC3128899B51F@mail>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 

> -----Original Message-----
> From: Bob Penfield [mailto:BPenfield@acmepacket.com] 
> Sent: 15 October 2008 16:12
> To: Elwell, John; Christer Holmberg; Juha Heinanen; 
> sip@ietf.org; Paul Kyzivat; Dean Willis
> Subject: RE: [Sip] Dual registration without Outbound
> 
> 
> 
> >-----Original Message-----
> >From: Elwell, John [mailto:john.elwell@siemens.com]
> >Sent: Wednesday, October 15, 2008 4:52 AM
> >To: Christer Holmberg; Bob Penfield; Juha Heinanen; 
> sip@ietf.org; Paul Kyzivat; Dean Willis
> >Subject: RE: [Sip] Dual registration without Outbound
> >
> >
> >> -----Original Message-----
> >> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> >> Sent: 15 October 2008 09:32
> >> To: Elwell, John; Bob Penfield; Juha Heinanen; sip@ietf.org;
> >> Paul Kyzivat; Dean Willis
> >> Subject: RE: [Sip] Dual registration without Outbound
> >>
> >>
> >> Hi,
> >>
> >>>It might well be the same software stack from the IP layer or the
> >>>transport layer upwards, but logically it acts as two UAs 
> (with some
> >>>application software at the top to bind the two together).
> >>>At least from the proxy perspective it looks like two UAs. 
> Viewing it
> >>>your way is perhaps also valid (but requires a minor change to
> >>>sip-outbound).
> >>
> >> And, if I understood correctly, that is the change Juha has
> >> been asking
> >> for :)
> >[JRE] Exactly. But viewing it my way possibly requires less change to
> >sip-outbound, since much of it talks about one instance ID 
> per UA (e.g.,
> >section 3.1).
> >
> >Whichever way we view it, the following statement in 4.1 seems to be
> >problematic:
> >"Instance ID MUST NOT change as the device moves from one network to
> >   another."
> 
> If the UA uses the interface's MAC address to generate the 
> instance-id, it would not change when you move between networks.
[JRE] I think Dean already answered this. If the instance ID is derived
from the MAC address, then when moving between networks employing a
different MAC technology, by definition the instance ID will change.

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


From sip-bounces@ietf.org  Thu Oct 16 05:05:30 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EAEDE3A6B56;
	Thu, 16 Oct 2008 05:05:29 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3D8A83A6B4A
	for <sip@core3.amsl.com>; Thu, 16 Oct 2008 05:05:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5
	tests=[AWL=-0.100, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gV1BeRI+9l4R for <sip@core3.amsl.com>;
	Thu, 16 Oct 2008 05:05:27 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39])
	by core3.amsl.com (Postfix) with ESMTP id 42C143A67D8
	for <sip@ietf.org>; Thu, 16 Oct 2008 05:05:27 -0700 (PDT)
Received: from ilexp03.ndc.lucent.com (h135-3-39-50.lucent.com [135.3.39.50])
	by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id m9GC5V9X025739; 
	Thu, 16 Oct 2008 07:06:11 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by
	ilexp03.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Oct 2008 07:05:40 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.20]) by
	DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Oct 2008 14:05:36 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 16 Oct 2008 14:05:35 +0200
Message-ID: <5D1A7985295922448D5550C94DE29180023E9D43@DEEXC1U01.de.lucent.com>
In-Reply-To: <48F62E90.5090905@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Is GRUU generated in the case of registration
	with	instance-ID and reg-ID
Thread-Index: Acku71Mod5eXc2qnTMqrdeudX7DeVwAmACpA
References: <CA9998CD4A020D418654FCDEF4E707DF05C0F8DF@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19B03A76@zrc2hxm0.corp.nortel.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF7E@esealmw113.eemea.ericsson.se>	<48F23D27.8030305@voip.co.uk>	<CA9998CD4A020D418654FCDEF4E707DF083CCF85@esealmw113.eemea.ericsson.se>	<48F2FC13.1070308@voip.co.uk><48F34E3B.80106@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EE@esealmw113.eemea.ericsson.se>	<48F3D191.5000007@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0864CEFC@esealmw113.eemea.ericsson.se>	<1ECE0EB50388174790F9694F77522CCF19BAB943@zrc2hxm0.corp.nortel.com>	<CA9998CD4A020D418654FCDEF4E707DF086A6463@esealmw113.eemea.ericsson.se><1ECE0EB50388174790F9694F77522CCF19BFCF64@zrc2hxm0.corp.nortel.com>
	<48F62E90.5090905@cisco.com>
From: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>, "Francois Audet" <audet@nortel.com>
X-OriginalArrivalTime: 16 Oct 2008 12:05:36.0525 (UTC)
	FILETIME=[7FA303D0:01C92F87]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: sip@ietf.org, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Is GRUU generated in the case of registration
	with	instance-ID and reg-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

It should not do because in my understanding this is an informative
reference, and we do not hold documents waiting for completion of
informative references.

In any case I guess we will get gruu and outbound published within days
of each other due to the reverse dependency.

Regards

Keith 

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Paul Kyzivat
> Sent: Wednesday, October 15, 2008 6:55 PM
> To: Francois Audet
> Cc: sip@ietf.org; Christer Holmberg
> Subject: Re: [Sip] Is GRUU generated in the case of 
> registration with instance-ID and reg-ID
> 
> 
> 
> Francois Audet wrote:
> > I'm ok with this and unless there are complaints, I'll add 
> it to the text. 
> 
> This will cause a two way dependency between gruu and outbound.
> Maybe that is ok, since gruu has been stable for months 
> (years?) and has been stalled awaiting the clearance of its 
> dependency on outbound.
> 
> 	Thanks,
> 	Paul
> 
> >> -----Original Message-----
> >> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> >> Sent: Tuesday, October 14, 2008 22:58
> >> To: Audet, Francois (SC100:3055); Paul Kyzivat
> >> Cc: Michael Procter; sip@ietf.org
> >> Subject: RE: [Sip] Is GRUU generated in the case of 
> registration with 
> >> instance-ID and reg-ID
> >>
> >>
> >> Hi,
> >>
> >> The text would be something like:
> >>
> >> "NOTE: If the registrar supports gruu 
> [reference-to-gruu-spec], the 
> >> presence of the instance-id in the REGISTER request will 
> also trigger 
> >> the registrar to generate a gruu for the user, as described in 
> >> [reference-to-gruu-spec]."
> >>
> >> I will look for a place in the outbound draft where to put 
> it, but it 
> >> really isn't more complicated than that. Just a simple 
> clarification 
> >> note :)
> >>
> >> Regards,
> >>
> >> Christer
> >>
> >>  
> >>
> >> -----Original Message-----
> >> From: Francois Audet [mailto:audet@nortel.com]
> >> Sent: 14. lokakuuta 2008 20:19
> >> To: Christer Holmberg; Paul Kyzivat
> >> Cc: Michael Procter; sip@ietf.org
> >> Subject: RE: [Sip] Is GRUU generated in the case of 
> registration with 
> >> instance-ID and reg-ID
> >>
> >> Can you propose actual text for a specific section. 
> >>
> >>> -----Original Message-----
> >>> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> >>> Sent: Monday, October 13, 2008 22:13
> >>> To: Paul Kyzivat
> >>> Cc: Michael Procter; sip@ietf.org; Audet, Francois (SC100:3055)
> >>> Subject: RE: [Sip] Is GRUU generated in the case of
> >> registration with
> >>> instance-ID and reg-ID
> >>>
> >>>
> >>> Hi,
> >>>
> >>>>> Yes. The question was whether instance-id AND reg-id 
> also create a
> >>> gruu.
> >>>>> The answer seems to be yes, but I think it would be good
> >> to clarify
> >>>>> that somewhere.
> >>>> Since reg-id isn't mentioned in gruu, its irrelevant to the
> >>> gruu spec,
> >>> just as any other parameters are.
> >>>
> >>> That is why I proposed it is clarified in the outbound spec :)
> >>>
> >>> Regards,
> >>>
> >>> Christer
> >>>
> > _______________________________________________
> > Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol Use 
> > sip-implementors@cs.columbia.edu for questions on current sip Use 
> > sipping@ietf.org for new developments on the application of sip
> > 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors@cs.columbia.edu for questions on current sip 
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 16 06:29:35 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DA0953A6C8A;
	Thu, 16 Oct 2008 06:29:35 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4F42828B56A
	for <sip@core3.amsl.com>; Thu, 16 Oct 2008 06:29:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.498
X-Spam-Level: 
X-Spam-Status: No, score=-6.498 tagged_above=-999 required=5 tests=[AWL=0.101, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ioZXsttXL2M0 for <sip@core3.amsl.com>;
	Thu, 16 Oct 2008 06:29:34 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 4F7983A6C23
	for <sip@ietf.org>; Thu, 16 Oct 2008 06:29:34 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,423,1220227200"; d="scan'208";a="24496961"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 16 Oct 2008 13:30:26 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9GDUQma021648; 
	Thu, 16 Oct 2008 09:30:26 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9GDUQP9017077;
	Thu, 16 Oct 2008 13:30:26 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Oct 2008 09:30:26 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Oct 2008 09:30:25 -0400
Message-ID: <48F741F1.8050809@cisco.com>
Date: Thu, 16 Oct 2008 09:30:25 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
	<18673.5665.337048.880648@taimen.test.fi>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
	A <CA9998CD4A020D418654FCDEF4E707DF086DA432@e!
	sealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBNTHT12009MSX.gb002.siemens.net>
	<068483D2-2A92-4DA0-A177-F8CACACA72A7@softarmor.com>
	<48F674	3A.4060006@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF087246CE@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF087246CE@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 16 Oct 2008 13:30:25.0863 (UTC)
	FILETIME=[591E5D70:01C92F93]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1678; t=1224163826;
	x=1225027826; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Dual=20registration=20without=2
	0Outbound |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=ZLQBO2HHoPDmdL3W67iSDnwtbIYS82km3Nl+4/+lVxs=;
	b=MOSz2RKrvP8x8U5G1VF6wuriqCOv0IoZAmkfzWrWSmeIfKOkEJadGrOoBA
	H/EtARG1jv/nFA7+lQ4BPXuAjaRlrRQqQjYAdtk8ArNulY3pe9KNks/jcKsD
	9MV+nRlxjC;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: Bob Penfield <BPenfield@acmepacket.com>, sip@ietf.org, "Elwell,
	John" <john.elwell@siemens.com>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Christer Holmberg wrote:
> Hi, 
> 
>> Trying to register the "same UA" concurrently with two different
> instance ids in an attempt to get parallel forked call attempts via
> different networks is creative but a bit ugly. For one thing 
>> its hard in general to guarantee that the two will be parallel forked.
> And the UA will have to attempt to correlate the two in order to realize
> they are the same and so process correctly. An 
>> SBC between the forking proxy and the UA is likely to disturb the
> CallID, the From, and the caller's Contact address. With those messed up
> the correlation will get difficult.
> 
> IF there is a need to do parallell forking to the "same UA", I think
> it's better to simply allow it in Outbound - instead of trying to find
> hacks on how to get around the current restrictions.
> 
> However, parallell forking in outbound should not be the default
> behavior, because I strongly think that in most cases people only want
> to receive the initial request on a SINGLE flow - no matter if they use
> one or more contacts.

Making this behavior "possible but not default" means that there must be 
two options: "do it", and "don't do it". The choice of which to do would 
need to be encoded somewhere. This matters a lot to the UA, so I think 
this option would have to be encoded as part of the registration 
request. Thus outbound would have to change to accommodate it.

In any case, changing the mechanism for requesting this behavior 
wouldn't really change the issues I raised about detecting when the same 
call is delivered via both paths.

	Thanks,
	Paul

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


From sip-bounces@ietf.org  Thu Oct 16 16:14:53 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 868883A6924;
	Thu, 16 Oct 2008 16:14:53 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A5ED53A659B
	for <sip@core3.amsl.com>; Thu, 16 Oct 2008 16:14:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id eiArSrtEswmz for <sip@core3.amsl.com>;
	Thu, 16 Oct 2008 16:14:51 -0700 (PDT)
Received: from zrtps0kn.nortel.com (zrtps0kn.nortel.com [47.140.192.55])
	by core3.amsl.com (Postfix) with ESMTP id C5C873A691A
	for <sip@ietf.org>; Thu, 16 Oct 2008 16:14:50 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m9GNFhS06566; Thu, 16 Oct 2008 23:15:44 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 16 Oct 2008 18:15:42 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF19CD56C1@zrc2hxm0.corp.nortel.com>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D0012DB621@GBNTHT12009MSX.gb002.siemens.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackta1Q4oPZYeoZEQAiUqa8JyoYU4gAAB04gACPIDEAABL7/QAAjTT0wAAEXIbAAAE5eEAAAG/tQAA3MBgAAI8AvQAAfexUw
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<18668.50247.121832.271341@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8C8@esealmw113.eemea.ericsson.se>
	<18668.51383.505850.963592@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8E3@esealmw113.eemea.ericsson.se>
	<18672.19846.621765.332209@taimen.test.fi>
	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
	<18673.5665.337048.880648@taimen.test.fi>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBN! THT12009M
	SX.gb002.sie
	mens.net> <E6C2E8958BA59A4FB960963D475F7AC3128899B51F@mail>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DB621@GBNTHT12009MSX.gb002.siemens.net>
From: "Francois Audet" <audet@nortel.com>
To: "Elwell, John" <john.elwell@siemens.com>,
	"Bob Penfield" <BPenfield@acmepacket.com>,
	"Christer Holmberg" <christer.holmberg@ericsson.com>,
	"Juha Heinanen" <jh@tutpro.com>, <sip@ietf.org>,
	"Paul Kyzivat" <pkyzivat@cisco.com>,
	"Dean Willis" <dean.willis@softarmor.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 
Did we reach a conclusion on this thread?

I think it has always been clear that forking is possible, and you do it by
using different +sip.instance.

I don't see any reason to change the spec.
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 16 16:49:44 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E3B1C3A698E;
	Thu, 16 Oct 2008 16:49:44 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9A4623A693D
	for <sip@core3.amsl.com>; Thu, 16 Oct 2008 16:49:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.613
X-Spam-Level: 
X-Spam-Status: No, score=-2.613 tagged_above=-999 required=5
	tests=[AWL=-0.014, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rlfFf03c7pG5 for <sip@core3.amsl.com>;
	Thu, 16 Oct 2008 16:49:42 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id D37853A698E
	for <sip@ietf.org>; Thu, 16 Oct 2008 16:49:42 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9GNoVDp012727
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 16 Oct 2008 18:50:33 -0500
Message-Id: <A95EB2F7-66F4-41CF-AC2A-2783532332C0@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
In-Reply-To: <48F741F1.8050809@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 16 Oct 2008 18:50:26 -0500
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<2210d2240810111235r5b786e94u7707730d8f1fa627@mail.gmail.com>
	<18673.5665.337048.880648@taimen.test.fi>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
	A <CA9998CD4A020D418654FCDEF4E707DF086DA432@e!
	sealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBNTHT12009MSX.gb002.siemens.net>
	<068483D2-2A92-4DA0-A177-F8CACACA72A7@softarmor.com>
	<48F674	3A.4060006@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF087246CE@esealmw113.eemea.ericsson.se>
	<48F741F1.! 8050809@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: Bob Penfield <BPenfield@acmepacket.com>, sip@ietf.org, "Elwell,
	John" <john.elwell@siemens.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 16, 2008, at 8:30 AM, Paul Kyzivat wrote:
>
> Making this behavior "possible but not default" means that there  
> must be two options: "do it", and "don't do it". The choice of which  
> to do would need to be encoded somewhere. This matters a lot to the  
> UA, so I think this option would have to be encoded as part of the  
> registration request. Thus outbound would have to change to  
> accommodate it.


If you want outbound's redundant-flow functionality, which is  
dependent on requests NOT forking to each flow to a UA, use outbound  
as specified.

If instead you want your two contacts treated as two different  
instances so that requests will fork to them, use two different  
instance-id values. Essentially, you're using single-contact/single  
flow Outbound (i.e., keepalive and reverse-routing of requests without  
redundant-flow) simultaneously on two different contacts (which may  
well be two different interfaces).

If you want both outbound's features simultaneously on multiple  
instances (or use virtual interfaces by having multiple instances on  
the same interface), then apply outbound as specified on each  
instance, where there are at least two proxies configured for each  
instance.

About the only thing I can see needing to document somewhere is the  
concept of using multiple instance-ids to make virtual interfaces, and  
that's pretty simple.

--
Dean

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


From sip-bounces@ietf.org  Thu Oct 16 16:53:23 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AAC943A69AB;
	Thu, 16 Oct 2008 16:53:23 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F1DA83A6924
	for <sip@core3.amsl.com>; Thu, 16 Oct 2008 16:53:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.612
X-Spam-Level: 
X-Spam-Status: No, score=-2.612 tagged_above=-999 required=5
	tests=[AWL=-0.013, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id oT1bVLuknlxu for <sip@core3.amsl.com>;
	Thu, 16 Oct 2008 16:53:22 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 41C623A69AB
	for <sip@ietf.org>; Thu, 16 Oct 2008 16:53:22 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9GNs7wb012750
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT)
	for <sip@ietf.org>; Thu, 16 Oct 2008 18:54:08 -0500
Message-Id: <BF4D24CF-D537-4476-87D2-8E30B8462B95@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: SIP IETF <sip@ietf.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 16 Oct 2008 18:54:01 -0500
X-Mailer: Apple Mail (2.929.2)
Subject: [Sip] So where are we at with WGLC of draft-ietf-sip-body-handling?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


There was a lot of discussion around the first of the month.

Where are we now?

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


From sip-bounces@ietf.org  Thu Oct 16 17:07:15 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8D4A83A698C;
	Thu, 16 Oct 2008 17:07:15 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 91FA63A698C
	for <sip@core3.amsl.com>; Thu, 16 Oct 2008 17:07:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.5
X-Spam-Level: 
X-Spam-Status: No, score=-6.5 tagged_above=-999 required=5 tests=[AWL=0.099,
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3g7fJPAc3itn for <sip@core3.amsl.com>;
	Thu, 16 Oct 2008 17:07:13 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 69B763A6852
	for <sip@ietf.org>; Thu, 16 Oct 2008 17:07:13 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,427,1220227200"; d="scan'208";a="24570839"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 17 Oct 2008 00:08:15 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9H08F0K023179; 
	Thu, 16 Oct 2008 20:08:15 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9H08FG8020844;
	Fri, 17 Oct 2008 00:08:15 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Oct 2008 20:08:15 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Oct 2008 20:08:14 -0400
Message-ID: <48F7D76F.1090808@cisco.com>
Date: Thu, 16 Oct 2008 20:08:15 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
	A <CA9998CD4A020D418654FCDEF4E707DF086DA432@e!
	sealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBNTHT12009MSX.gb002.siemens.net>
	<068483D2-2A92-4DA0-A177-F8CACACA72A7@softarmor.com>
	<48F674	3A.4060006@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF087246CE@esealmw113.eemea.ericsson.se>
	<48F741F1.! 8050809@cisco.com>
	<A95EB2F7-66F4-41CF-AC2A-2783532332C0@softarmor.com>
In-Reply-To: <A95EB2F7-66F4-41CF-AC2A-2783532332C0@softarmor.com>
X-OriginalArrivalTime: 17 Oct 2008 00:08:14.0962 (UTC)
	FILETIME=[73477520:01C92FEC]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1520; t=1224202095;
	x=1225066095; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Dual=20registration=20without=2
	0Outbound |Sender:=20
	|To:=20Dean=20Willis=20<dean.willis@softarmor.com>;
	bh=UObdiKDXMIBV+f2AQvBuKVc/BOA/+UA1b8bLQJg4i68=;
	b=WqzhH656SbXT1HQWYZdTV7XXkfvm8YzvvzxkWxucViwZJgD+BwkMwWZGHh
	WwalHDSD8PVi1xpcOKZUIc+1NBL8QZBpYXXeditP4lcjJhGRb+eNmQ9UeR1L
	ikf4R7pObv;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: Bob Penfield <BPenfield@acmepacket.com>, sip@ietf.org, "Elwell,
	John" <john.elwell@siemens.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I agree.

	Paul

Dean Willis wrote:
> 
> On Oct 16, 2008, at 8:30 AM, Paul Kyzivat wrote:
>>
>> Making this behavior "possible but not default" means that there must 
>> be two options: "do it", and "don't do it". The choice of which to do 
>> would need to be encoded somewhere. This matters a lot to the UA, so I 
>> think this option would have to be encoded as part of the registration 
>> request. Thus outbound would have to change to accommodate it.
> 
> 
> If you want outbound's redundant-flow functionality, which is dependent 
> on requests NOT forking to each flow to a UA, use outbound as specified.
> 
> If instead you want your two contacts treated as two different instances 
> so that requests will fork to them, use two different instance-id 
> values. Essentially, you're using single-contact/single flow Outbound 
> (i.e., keepalive and reverse-routing of requests without redundant-flow) 
> simultaneously on two different contacts (which may well be two 
> different interfaces).
> 
> If you want both outbound's features simultaneously on multiple 
> instances (or use virtual interfaces by having multiple instances on the 
> same interface), then apply outbound as specified on each instance, 
> where there are at least two proxies configured for each instance.
> 
> About the only thing I can see needing to document somewhere is the 
> concept of using multiple instance-ids to make virtual interfaces, and 
> that's pretty simple.
> 
> -- 
> Dean
> 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 17 00:43:17 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7EC8F3A6924;
	Fri, 17 Oct 2008 00:43:17 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4D0513A63CB
	for <sip@core3.amsl.com>; Fri, 17 Oct 2008 00:43:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.565
X-Spam-Level: 
X-Spam-Status: No, score=-2.565 tagged_above=-999 required=5 tests=[AWL=0.034, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 7JMdeQ0FIPTv for <sip@core3.amsl.com>;
	Fri, 17 Oct 2008 00:43:15 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id 540B33A67D0
	for <sip@ietf.org>; Fri, 17 Oct 2008 00:43:15 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K8V00L71HHOFM@siemenscomms.co.uk> for sip@ietf.org; Fri,
	17 Oct 2008 08:44:12 +0100 (BST)
Date: Fri, 17 Oct 2008 08:44:11 +0100
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <48F7D76F.1090808@cisco.com>
To: Paul Kyzivat <pkyzivat@cisco.com>, Dean Willis <dean.willis@softarmor.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D0012DBACA@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackv79xMUr/Qqlh5Q/eajulnuL518wAPEKsg
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBNTHT12009MSX.gb002.siemens.net>
	<068483D2-2A92-4DA0-A177-F8CACACA72A7@softarmor.com>
	<"48F674 3A.4060006"@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF087246CE@esealmw113.eemea.ericsson.se>
	<A95EB2F7-66F4-41CF-AC2A-2783532332C0@softarmor.com>
	<48F7D76F.1090808@cisco.com>
Cc: Bob Penfield <BPenfield@acmepacket.com>, sip@ietf.org,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

+1

John 

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
> Sent: 17 October 2008 01:08
> To: Dean Willis
> Cc: Christer Holmberg; Elwell, John; Bob Penfield; Juha 
> Heinanen; sip@ietf.org
> Subject: Re: [Sip] Dual registration without Outbound
> 
> I agree.
> 
> 	Paul
> 
> Dean Willis wrote:
> > 
> > On Oct 16, 2008, at 8:30 AM, Paul Kyzivat wrote:
> >>
> >> Making this behavior "possible but not default" means that 
> there must 
> >> be two options: "do it", and "don't do it". The choice of 
> which to do 
> >> would need to be encoded somewhere. This matters a lot to 
> the UA, so I 
> >> think this option would have to be encoded as part of the 
> registration 
> >> request. Thus outbound would have to change to accommodate it.
> > 
> > 
> > If you want outbound's redundant-flow functionality, which 
> is dependent 
> > on requests NOT forking to each flow to a UA, use outbound 
> as specified.
> > 
> > If instead you want your two contacts treated as two 
> different instances 
> > so that requests will fork to them, use two different instance-id 
> > values. Essentially, you're using single-contact/single 
> flow Outbound 
> > (i.e., keepalive and reverse-routing of requests without 
> redundant-flow) 
> > simultaneously on two different contacts (which may well be two 
> > different interfaces).
> > 
> > If you want both outbound's features simultaneously on multiple 
> > instances (or use virtual interfaces by having multiple 
> instances on the 
> > same interface), then apply outbound as specified on each instance, 
> > where there are at least two proxies configured for each instance.
> > 
> > About the only thing I can see needing to document somewhere is the 
> > concept of using multiple instance-ids to make virtual 
> interfaces, and 
> > that's pretty simple.
> > 
> > -- 
> > Dean
> > 
> > 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 17 01:08:19 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 105113A69DD;
	Fri, 17 Oct 2008 01:08:19 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8ADD33A69DD
	for <sip@core3.amsl.com>; Fri, 17 Oct 2008 01:08:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.198
X-Spam-Level: 
X-Spam-Status: No, score=-6.198 tagged_above=-999 required=5 tests=[AWL=0.051, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 7BbThiwME7r0 for <sip@core3.amsl.com>;
	Fri, 17 Oct 2008 01:08:16 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 655443A682C
	for <sip@ietf.org>; Fri, 17 Oct 2008 01:08:16 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	20D4920EC5; Fri, 17 Oct 2008 10:08:10 +0200 (CEST)
X-AuditID: c1b4fb3c-ad8cdbb0000015b5-32-48f847e9ba4a
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	F384B20D65; Fri, 17 Oct 2008 10:08:09 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Oct 2008 10:08:09 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 17 Oct 2008 10:08:08 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0877429A@esealmw113.eemea.ericsson.se>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D0012DBACA@GBNTHT12009MSX.gb002.siemens.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackv79xMUr/Qqlh5Q/eajulnuL518wAPEKsgAADBhVA=
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBNTHT12009MSX.gb002.siemens.net>
	<068483D2-2A92-4DA0-A177-F8CACACA72A7@softarmor.com> <"48F674
	3A.4060006"@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF087246CE@esealmw113.eemea.ericsson.se>
	<A95EB2F7-66F4-41CF-AC2A-2783532332C0@softarmor.com>
	<48F7D76F.1090808@cisco.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DBACA@GBNTHT12009MSX.gb002.siemens.net>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Elwell, John" <john.elwell@siemens.com>,
	"Paul Kyzivat" <pkyzivat@cisco.com>,
	"Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 17 Oct 2008 08:08:09.0834 (UTC)
	FILETIME=[7E5C3CA0:01C9302F]
X-Brightmail-Tracker: AAAAAA==
Cc: Bob Penfield <BPenfield@acmepacket.com>, sip@ietf.org
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi,

The please-perform-parallel-forking-to-the-same-intance-id extension
indication would then be brought as a separate draft.

Regards,

Christer

-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens.com] 
Sent: 17. lokakuuta 2008 10:44
To: Paul Kyzivat; Dean Willis
Cc: Christer Holmberg; Bob Penfield; Juha Heinanen; sip@ietf.org
Subject: RE: [Sip] Dual registration without Outbound

+1

John 

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> Sent: 17 October 2008 01:08
> To: Dean Willis
> Cc: Christer Holmberg; Elwell, John; Bob Penfield; Juha Heinanen; 
> sip@ietf.org
> Subject: Re: [Sip] Dual registration without Outbound
> 
> I agree.
> 
> 	Paul
> 
> Dean Willis wrote:
> > 
> > On Oct 16, 2008, at 8:30 AM, Paul Kyzivat wrote:
> >>
> >> Making this behavior "possible but not default" means that
> there must
> >> be two options: "do it", and "don't do it". The choice of
> which to do
> >> would need to be encoded somewhere. This matters a lot to
> the UA, so I
> >> think this option would have to be encoded as part of the
> registration
> >> request. Thus outbound would have to change to accommodate it.
> > 
> > 
> > If you want outbound's redundant-flow functionality, which
> is dependent
> > on requests NOT forking to each flow to a UA, use outbound
> as specified.
> > 
> > If instead you want your two contacts treated as two
> different instances
> > so that requests will fork to them, use two different instance-id 
> > values. Essentially, you're using single-contact/single
> flow Outbound
> > (i.e., keepalive and reverse-routing of requests without
> redundant-flow)
> > simultaneously on two different contacts (which may well be two 
> > different interfaces).
> > 
> > If you want both outbound's features simultaneously on multiple 
> > instances (or use virtual interfaces by having multiple
> instances on the
> > same interface), then apply outbound as specified on each instance, 
> > where there are at least two proxies configured for each instance.
> > 
> > About the only thing I can see needing to document somewhere is the 
> > concept of using multiple instance-ids to make virtual
> interfaces, and
> > that's pretty simple.
> > 
> > --
> > Dean
> > 
> > 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 17 02:29:34 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 007873A68A2;
	Fri, 17 Oct 2008 02:29:33 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1EEA33A68A2
	for <sip@core3.amsl.com>; Fri, 17 Oct 2008 02:29:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Level: 
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[AWL=0.032, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id n09bu0H3klqx for <sip@core3.amsl.com>;
	Fri, 17 Oct 2008 02:29:32 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id 2D7573A63D2
	for <sip@ietf.org>; Fri, 17 Oct 2008 02:29:32 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K8V0047YMAOM4@siemenscomms.co.uk> for sip@ietf.org; Fri,
	17 Oct 2008 10:28:00 +0100 (BST)
Date: Fri, 17 Oct 2008 10:26:53 +0100
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: A
	<CA9998CD4A020D418654FCDEF4E707DF0877429A@esealmw113.eemea.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>,
	Paul Kyzivat <pkyzivat@cisco.com>, Dean Willis <dean.willis@softarmor.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D0012DBBC2@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackv79xMUr/Qqlh5Q/eajulnuL518wAPEKsgAADBhVAAAss74A==
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBNTHT12009MSX.gb002.siemens.net>
	<068483D2-2A92-4DA0-A177-F8CACACA72A7@softarmor.com>
	<"48F674 3A.4060006"@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF087246CE@esealmw113.eemea.ericsson.se>
	<A95EB2F7-66F4-41CF-AC2A-2783532332C0@softarmor.com>
	<48F7D76F.1090808@cisco.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DBACA@GBNTHT12009MSX.gb002.siemens.net>
	A <"CA9998CD4A020D418654FCDEF4E707DF087742
	9A"@esealmw113.eemea.ericsson.se>
Cc: Bob Penfield <BPenfield@acmepacket.com>, sip@ietf.org
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer,

It is not clear why would need anything else. Why would you need to
parallel fork to the same instance ID, when you can use different
instance IDs?

John 

> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] 
> Sent: 17 October 2008 09:08
> To: Elwell, John; Paul Kyzivat; Dean Willis
> Cc: Bob Penfield; Juha Heinanen; sip@ietf.org
> Subject: RE: [Sip] Dual registration without Outbound
> 
> 
> Hi,
> 
> The please-perform-parallel-forking-to-the-same-intance-id extension
> indication would then be brought as a separate draft.
> 
> Regards,
> 
> Christer
> 
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens.com] 
> Sent: 17. lokakuuta 2008 10:44
> To: Paul Kyzivat; Dean Willis
> Cc: Christer Holmberg; Bob Penfield; Juha Heinanen; sip@ietf.org
> Subject: RE: [Sip] Dual registration without Outbound
> 
> +1
> 
> John 
> 
> > -----Original Message-----
> > From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> > Sent: 17 October 2008 01:08
> > To: Dean Willis
> > Cc: Christer Holmberg; Elwell, John; Bob Penfield; Juha Heinanen; 
> > sip@ietf.org
> > Subject: Re: [Sip] Dual registration without Outbound
> > 
> > I agree.
> > 
> > 	Paul
> > 
> > Dean Willis wrote:
> > > 
> > > On Oct 16, 2008, at 8:30 AM, Paul Kyzivat wrote:
> > >>
> > >> Making this behavior "possible but not default" means that
> > there must
> > >> be two options: "do it", and "don't do it". The choice of
> > which to do
> > >> would need to be encoded somewhere. This matters a lot to
> > the UA, so I
> > >> think this option would have to be encoded as part of the
> > registration
> > >> request. Thus outbound would have to change to accommodate it.
> > > 
> > > 
> > > If you want outbound's redundant-flow functionality, which
> > is dependent
> > > on requests NOT forking to each flow to a UA, use outbound
> > as specified.
> > > 
> > > If instead you want your two contacts treated as two
> > different instances
> > > so that requests will fork to them, use two different instance-id 
> > > values. Essentially, you're using single-contact/single
> > flow Outbound
> > > (i.e., keepalive and reverse-routing of requests without
> > redundant-flow)
> > > simultaneously on two different contacts (which may well be two 
> > > different interfaces).
> > > 
> > > If you want both outbound's features simultaneously on multiple 
> > > instances (or use virtual interfaces by having multiple
> > instances on the
> > > same interface), then apply outbound as specified on each 
> instance, 
> > > where there are at least two proxies configured for each instance.
> > > 
> > > About the only thing I can see needing to document 
> somewhere is the 
> > > concept of using multiple instance-ids to make virtual
> > interfaces, and
> > > that's pretty simple.
> > > 
> > > --
> > > Dean
> > > 
> > > 
> > 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 17 02:32:19 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DAAFF28C0F9;
	Fri, 17 Oct 2008 02:32:19 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E89FC28C0F9
	for <sip@core3.amsl.com>; Fri, 17 Oct 2008 02:32:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.199
X-Spam-Level: 
X-Spam-Status: No, score=-6.199 tagged_above=-999 required=5 tests=[AWL=0.050, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2Z5JQtPg2TPp for <sip@core3.amsl.com>;
	Fri, 17 Oct 2008 02:32:17 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id D56BB28C0F6
	for <sip@ietf.org>; Fri, 17 Oct 2008 02:32:16 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	8A2C5204CD; Fri, 17 Oct 2008 11:33:19 +0200 (CEST)
X-AuditID: c1b4fb3e-a8e85bb000007a96-66-48f85bdf0508
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	6DF1E21492; Fri, 17 Oct 2008 11:33:19 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Oct 2008 11:33:18 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 17 Oct 2008 11:33:18 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF087746A7@esealmw113.eemea.ericsson.se>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D0012DBBC2@GBNTHT12009MSX.gb002.siemens.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackv79xMUr/Qqlh5Q/eajulnuL518wAPEKsgAADBhVAAAss74AAAQQgA
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBNTHT12009MSX.gb002.siemens.net>
	<068483D2-2A92-4DA0-A177-F8CACACA72A7@softarmor.com> <"48F674
	3A.4060006"@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF087246CE@esealmw113.eemea.ericsson.se>
	<A95EB2F7-66F4-41CF-AC2A-2783532332C0@softarmor.com>
	<48F7D76F.1090808@cisco.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DBACA@GBNTHT12009MSX.gb002.siemens.net>
	A <"CA9998CD4A020D418654FCDEF4E7 07DF0877 42 9A"@eseal
	mw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DBBC2@GBNTHT12009MSX.gb002.siemens.net>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Elwell, John" <john.elwell@siemens.com>,
	"Paul Kyzivat" <pkyzivat@cisco.com>,
	"Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 17 Oct 2008 09:33:18.0298 (UTC)
	FILETIME=[633DFBA0:01C9303B]
X-Brightmail-Tracker: AAAAAA==
Cc: Bob Penfield <BPenfield@acmepacket.com>, sip@ietf.org
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>It is not clear why would need anything else. Why would you need to
parallel fork to the same instance ID, when you can use different
instance IDs?

I don't need it, but Juha does :)

Regards,

Christer




> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> Sent: 17 October 2008 09:08
> To: Elwell, John; Paul Kyzivat; Dean Willis
> Cc: Bob Penfield; Juha Heinanen; sip@ietf.org
> Subject: RE: [Sip] Dual registration without Outbound
> 
> 
> Hi,
> 
> The please-perform-parallel-forking-to-the-same-intance-id extension 
> indication would then be brought as a separate draft.
> 
> Regards,
> 
> Christer
> 
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens.com]
> Sent: 17. lokakuuta 2008 10:44
> To: Paul Kyzivat; Dean Willis
> Cc: Christer Holmberg; Bob Penfield; Juha Heinanen; sip@ietf.org
> Subject: RE: [Sip] Dual registration without Outbound
> 
> +1
> 
> John
> 
> > -----Original Message-----
> > From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> > Sent: 17 October 2008 01:08
> > To: Dean Willis
> > Cc: Christer Holmberg; Elwell, John; Bob Penfield; Juha Heinanen; 
> > sip@ietf.org
> > Subject: Re: [Sip] Dual registration without Outbound
> > 
> > I agree.
> > 
> > 	Paul
> > 
> > Dean Willis wrote:
> > > 
> > > On Oct 16, 2008, at 8:30 AM, Paul Kyzivat wrote:
> > >>
> > >> Making this behavior "possible but not default" means that
> > there must
> > >> be two options: "do it", and "don't do it". The choice of
> > which to do
> > >> would need to be encoded somewhere. This matters a lot to
> > the UA, so I
> > >> think this option would have to be encoded as part of the
> > registration
> > >> request. Thus outbound would have to change to accommodate it.
> > > 
> > > 
> > > If you want outbound's redundant-flow functionality, which
> > is dependent
> > > on requests NOT forking to each flow to a UA, use outbound
> > as specified.
> > > 
> > > If instead you want your two contacts treated as two
> > different instances
> > > so that requests will fork to them, use two different instance-id 
> > > values. Essentially, you're using single-contact/single
> > flow Outbound
> > > (i.e., keepalive and reverse-routing of requests without
> > redundant-flow)
> > > simultaneously on two different contacts (which may well be two 
> > > different interfaces).
> > > 
> > > If you want both outbound's features simultaneously on multiple 
> > > instances (or use virtual interfaces by having multiple
> > instances on the
> > > same interface), then apply outbound as specified on each
> instance,
> > > where there are at least two proxies configured for each instance.
> > > 
> > > About the only thing I can see needing to document
> somewhere is the
> > > concept of using multiple instance-ids to make virtual
> > interfaces, and
> > > that's pretty simple.
> > > 
> > > --
> > > Dean
> > > 
> > > 
> > 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 17 02:39:47 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 008EE3A69EF;
	Fri, 17 Oct 2008 02:39:47 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C12453A69EF
	for <sip@core3.amsl.com>; Fri, 17 Oct 2008 02:39:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1j4NJyNCkE6X for <sip@core3.amsl.com>;
	Fri, 17 Oct 2008 02:39:45 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id D44BE3A69DD
	for <sip@ietf.org>; Fri, 17 Oct 2008 02:39:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 64C991EC2CE;
	Fri, 17 Oct 2008 12:40:44 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id i7h4msEvzaSc; Fri, 17 Oct 2008 12:40:42 +0300 (EEST)
Received: from taimen (h160108.gprs.dnafinland.fi [87.93.160.108])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Fri, 17 Oct 2008 12:40:42 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 438DBAC0EB; Fri, 17 Oct 2008 12:40:38 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18680.23958.246188.814477@taimen.test.fi>
Date: Fri, 17 Oct 2008 12:40:38 +0300
To: "Elwell, John" <john.elwell@siemens.com>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D0012DBBC2@GBNTHT12009MSX.gb002.siemens.net>
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBNTHT12009MSX.gb002.siemens.net>
	<068483D2-2A92-4DA0-A177-F8CACACA72A7@softarmor.com>
	<"48F674 3A.4060006"@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF087246CE@esealmw113.eemea.ericsson.se>
	<A95EB2F7-66F4-41CF-AC2A-2783532332C0@softarmor.com>
	<48F7D76F.1090808@cisco.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DBACA@GBNTHT12009MSX.gb002.siemens.net>
	<"CA9998CD4A020D418654FCDEF4E707DF087742
	9A"@esealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DBBC2@GBNTHT12009MSX.gb002.siemens.net>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: Bob Penfield <BPenfield@acmepacket.com>, sip@ietf.org,
	Paul Kyzivat <pkyzivat@cisco.com>, Dean Willis <dean.willis@softarmor.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Elwell, John writes:

 > It is not clear why would need anything else. Why would you need to
 > parallel fork to the same instance ID, when you can use different
 > instance IDs?

just one clarifying question:

it was not clear to me if separate instance ids need to be used for
different contacts of the same ua, can a single register request contain
both contacts and their instance ids?  for example, if my ua has two
contacts and ob set has two proxies, does my ua need to send two or four
register requests?

if four, i cannot accept a draft which causes such a mess.

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


From sip-bounces@ietf.org  Fri Oct 17 04:59:01 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3E7763A68D0;
	Fri, 17 Oct 2008 04:59:01 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 714CA3A6A4A
	for <sip@core3.amsl.com>; Fri, 17 Oct 2008 04:58:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.568
X-Spam-Level: 
X-Spam-Status: No, score=-2.568 tagged_above=-999 required=5 tests=[AWL=0.031, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id GFdhZMIrvBNC for <sip@core3.amsl.com>;
	Fri, 17 Oct 2008 04:58:58 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id 9C7CD3A68D0
	for <sip@ietf.org>; Fri, 17 Oct 2008 04:58:58 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K8V00D5MTBWWU@siemenscomms.co.uk> for sip@ietf.org; Fri,
	17 Oct 2008 12:59:58 +0100 (BST)
Date: Fri, 17 Oct 2008 12:59:53 +0100
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <18680.23958.246188.814477@taimen.test.fi>
To: Juha Heinanen <jh@tutpro.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D0012DBD1C@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckwPG5Wh6FrWEkgRtKCUz4Qnhof+wACvbSg
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBNTHT12009MSX.gb002.siemens.net>
	<068483D2-2A92-4DA0-A177-F8CACACA72A7@softarmor.com>
	<"48F674 3A.4060006"@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF087246CE@esealmw113.eemea.ericsson.se>
	<A95EB2F7-66F4-41CF-AC2A-2783532332C0@softarmor.com>
	<48F7D76F.1090808@cisco.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DBACA@GBNTHT12009MSX.gb002.siemens.net>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DBBC2@GBNTHT12009MSX.gb002.siemens.net>
	<18680.23958.246188.814477@taimen.test.fi>
Cc: Bob Penfield <BPenfield@acmepacket.com>, sip@ietf.org,
	Paul Kyzivat <pkyzivat@cisco.com>, Dean Willis <dean.willis@softarmor.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I believe that Dean's description in his most recent posting described
the situation well. I think in that case you do indeed need to register
4 times, but I don't regard that as a mess. I just think we need a small
amount of clarifying text in the present draft.

John 

> -----Original Message-----
> From: Juha Heinanen [mailto:jh@tutpro.com] 
> Sent: 17 October 2008 10:41
> To: Elwell, John
> Cc: Christer Holmberg; Paul Kyzivat; Dean Willis; Bob 
> Penfield; sip@ietf.org
> Subject: RE: [Sip] Dual registration without Outbound
> 
> Elwell, John writes:
> 
>  > It is not clear why would need anything else. Why would you need to
>  > parallel fork to the same instance ID, when you can use different
>  > instance IDs?
> 
> just one clarifying question:
> 
> it was not clear to me if separate instance ids need to be used for
> different contacts of the same ua, can a single register 
> request contain
> both contacts and their instance ids?  for example, if my ua has two
> contacts and ob set has two proxies, does my ua need to send 
> two or four
> register requests?
> 
> if four, i cannot accept a draft which causes such a mess.
> 
> -- juha
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 17 05:17:23 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C4BB428C0EA;
	Fri, 17 Oct 2008 05:17:23 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 497553A6AB8
	for <sip@core3.amsl.com>; Fri, 17 Oct 2008 05:17:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.578
X-Spam-Level: 
X-Spam-Status: No, score=-6.578 tagged_above=-999 required=5 tests=[AWL=0.022, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id sZoMUWd+S3ER for <sip@core3.amsl.com>;
	Fri, 17 Oct 2008 05:17:22 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id AF11C3A6AB6
	for <sip@ietf.org>; Fri, 17 Oct 2008 05:17:21 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com
	[10.160.244.31])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m9HCI7Ke012894; Fri, 17 Oct 2008 15:18:17 +0300
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 17 Oct 2008 15:18:14 +0300
Received: from esebe101.NOE.Nokia.com ([172.21.138.215]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 17 Oct 2008 15:17:55 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 17 Oct 2008 15:17:54 +0300
Message-ID: <C84E0A4ABA6DD74DA5221E0833A35DF30AF19D2B@esebe101.NOE.Nokia.com>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D0012DBACA@GBNTHT12009MSX.gb002.siemens.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: Ackv79xMUr/Qqlh5Q/eajulnuL518wAPEKsgAAkTetA=
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com><18673.62485.295631.933830@taimen.test.fi><2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com><18675.7684.207071.901832@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se><18675.41223.587006.241312@taimen.test.fi><18675.41926.583512.912121@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se><E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com><0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBNTHT12009MSX.gb002.siemens.net><068483D2-2A92-4DA0-A177-F8CACACA72A7@softarmor.com><"48F674
	3A.4060006"@cisco.com><CA9998CD4A020D418654FCDEF4E707DF087246CE@esealmw113.eemea.ericsson.se><A95EB2F7-66F4-41CF-AC2A-2783532332C0@softarmor.com><48F7D76F.1090808@cisco.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DBACA@GBNTHT12009MSX.gb002.siemens.net>
From: <Markus.Isomaki@nokia.com>
To: <john.elwell@siemens.com>, <pkyzivat@cisco.com>,
	<dean.willis@softarmor.com>
X-OriginalArrivalTime: 17 Oct 2008 12:17:55.0652 (UTC)
	FILETIME=[629A9840:01C93052]
X-Nokia-AV: Clean
Cc: BPenfield@acmepacket.com, sip@ietf.org, christer.holmberg@ericsson.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi,

Agreed.

I've been trying to follow this thread here and there and finally got
some clarity by reading Dean's mail below. In general high availability
and also parallel forking are nice, but I'm definitely against any
normative statements on how many flows UA needs to use. For instace the
case Juha is describing, i.e. parallel registrations over GPRS and WLAN
with parallel forking would have a trade off that the device battery
would run out much sooner with a single GPRS- *or* WLAN-bound
registration. So, for that reason I don't think that would be the best
default choice for an UA in a battery powered wireless device.

What Dean is describing below seems good as it is up to the UA to decide
what to do while everything seems possible and there shouldn't be
serious IOP issues even if UAs preferred different strategies. And above
all we don't need to agree beforehand on what would be the best way.

Markus 
 

>-----Original Message-----
>From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
>Behalf Of ext Elwell, John
>Sent: 17 October, 2008 10:44
>To: Paul Kyzivat; Dean Willis
>Cc: Bob Penfield; sip@ietf.org; Christer Holmberg
>Subject: Re: [Sip] Dual registration without Outbound
>
>+1
>
>John 
>
>> -----Original Message-----
>> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
>> Sent: 17 October 2008 01:08
>> To: Dean Willis
>> Cc: Christer Holmberg; Elwell, John; Bob Penfield; Juha Heinanen; 
>> sip@ietf.org
>> Subject: Re: [Sip] Dual registration without Outbound
>> 
>> I agree.
>> 
>> 	Paul
>> 
>> Dean Willis wrote:
>> > 
>> > On Oct 16, 2008, at 8:30 AM, Paul Kyzivat wrote:
>> >>
>> >> Making this behavior "possible but not default" means that
>> there must
>> >> be two options: "do it", and "don't do it". The choice of
>> which to do
>> >> would need to be encoded somewhere. This matters a lot to
>> the UA, so I
>> >> think this option would have to be encoded as part of the
>> registration
>> >> request. Thus outbound would have to change to accommodate it.
>> > 
>> > 
>> > If you want outbound's redundant-flow functionality, which
>> is dependent
>> > on requests NOT forking to each flow to a UA, use outbound
>> as specified.
>> > 
>> > If instead you want your two contacts treated as two
>> different instances
>> > so that requests will fork to them, use two different instance-id 
>> > values. Essentially, you're using single-contact/single
>> flow Outbound
>> > (i.e., keepalive and reverse-routing of requests without
>> redundant-flow)
>> > simultaneously on two different contacts (which may well be two 
>> > different interfaces).
>> > 
>> > If you want both outbound's features simultaneously on multiple 
>> > instances (or use virtual interfaces by having multiple
>> instances on the
>> > same interface), then apply outbound as specified on each 
>instance, 
>> > where there are at least two proxies configured for each instance.
>> > 
>> > About the only thing I can see needing to document 
>somewhere is the 
>> > concept of using multiple instance-ids to make virtual
>> interfaces, and
>> > that's pretty simple.
>> > 
>> > --
>> > Dean
>> > 
>> > 
>> 
>_______________________________________________
>Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>This list is for NEW development of the core SIP Protocol Use 
>sip-implementors@cs.columbia.edu for questions on current sip 
>Use sipping@ietf.org for new developments on the application of sip
>
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 17 07:09:03 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 115863A6897;
	Fri, 17 Oct 2008 07:09:03 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 986643A6897
	for <sip@core3.amsl.com>; Fri, 17 Oct 2008 07:09:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.612
X-Spam-Level: 
X-Spam-Status: No, score=-2.612 tagged_above=-999 required=5
	tests=[AWL=-0.012, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6czb7Ae356zI for <sip@core3.amsl.com>;
	Fri, 17 Oct 2008 07:09:01 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id DEB5D3A6826
	for <sip@ietf.org>; Fri, 17 Oct 2008 07:09:00 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9HE9riA018921
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 17 Oct 2008 09:09:55 -0500
Message-Id: <B3DE6853-21AA-4FF5-B1E9-96236DA0748C@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF0877429A@esealmw113.eemea.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 17 Oct 2008 09:09:48 -0500
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBNTHT12009MSX.gb002.siemens.net>
	<068483D2-2A92-4DA0-A177-F8CACACA72A7@softarmor.com> <"48F674
	3A.4060006"@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF087246CE@esealmw113.eemea.ericsson.se>
	<A95EB2F7-66F4-41CF-AC2A-2783532332C0@softarmor.com>
	<48F7D76F.1090808@cisco.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DBACA@GBNTHT12009MSX.gb002.siemens.net>
	<CA9998CD4A020D418654FCDEF4E707!
	DF0877429A@esealmw113.eemea.ericsson.se>
X-Mailer: Apple Mail (2.929.2)
Cc: Bob Penfield <BPenfield@acmepacket.com>, sip@ietf.org,
	Paul Kyzivat <pkyzivat@cisco.com>, "Elwell, John" <john.elwell@siemens.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 17, 2008, at 3:08 AM, Christer Holmberg wrote:

>
> Hi,
>
> The please-perform-parallel-forking-to-the-same-intance-id extension
> indication would then be brought as a separate draft.
>

Do we need such an extension when there is a workaround -- using  
different instance-id?

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


From sip-bounces@ietf.org  Fri Oct 17 07:35:06 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 90AE53A6A97;
	Fri, 17 Oct 2008 07:35:06 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DE8FF3A6A97
	for <sip@core3.amsl.com>; Fri, 17 Oct 2008 07:35:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level: 
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5
	tests=[AWL=-0.012, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YMX2MQx0o-ao for <sip@core3.amsl.com>;
	Fri, 17 Oct 2008 07:35:05 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id E40B93A6AA4
	for <sip@ietf.org>; Fri, 17 Oct 2008 07:35:04 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9HEa4BH019230
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT)
	for <sip@ietf.org>; Fri, 17 Oct 2008 09:36:05 -0500
Message-Id: <5CFE7D5D-BCA0-49A7-A58C-1291A8F416F6@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: SIP IETF <sip@ietf.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 17 Oct 2008 09:35:58 -0500
X-Mailer: Apple Mail (2.929.2)
Subject: [Sip] Question on non-outbound registrations in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

The current draft says:
4.2.3.  Non Outbound Registrations

    In an initial registration, a User Agent MUST NOT include a reg-id
    header parameter in the Contact header field if the registering UA  
is
    not the same instance as the UA referred to by the target Contact
    header field.  (This practice is occasionally used to install
    forwarding policy into registrars.)

    A UAC also MUST NOT include an instance-id feature taf or reg-id
    Contact header field parameter in a request to un-register all
    Contacts (a single Contact header field value with the value of  
"*").

This strikes me as odd in several ways.

The reg-id lets us know "which registration we are talking about". The  
instance-id lets us know "which specific UA-appearance we are talking  
about".
So for a 3rd-party registration, it might be useful to have reg-id or  
instance-id values. Assume for example a voice-mail server that  
registers a low q-value contact for an AOR, so that calls will  
eventually reach it in a no-answer scenario. Withdrawing just those  
specific registrations would seem to require a selection mechanism  
from the set of registrations, and reg-id would appear to satisfy this  
need.


In a different use case, assume a 3rd party registration is used to  
install forwarding policy. The use of an instance-id in such a  
registration would seem to allow the forwarding policy to target one  
specific instance of the set of contacts registered to the target. In  
other words, not "forward the call to sip:bob@example.com", but  
"forward the call to sip:bob@example.com's cell phone".

Now it's entirely possible that neither of these scenarios actually  
work. But I don't see in the discussion of outbound anything about WHY  
they wouldn't work, which means that the requirements language (the  
MUST in outbound) is unsupported. I don't like unsupported  
requirements in a specification.
--
Dean

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


From sip-bounces@ietf.org  Fri Oct 17 07:55:17 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 967C43A69E3;
	Fri, 17 Oct 2008 07:55:17 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4CC3F3A697F
	for <sip@core3.amsl.com>; Fri, 17 Oct 2008 07:55:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level: 
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5
	tests=[AWL=-0.012, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gVBeIt7vD1VW for <sip@core3.amsl.com>;
	Fri, 17 Oct 2008 07:55:15 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 53CC13A69E3
	for <sip@ietf.org>; Fri, 17 Oct 2008 07:55:15 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9HEtiJr019320
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 17 Oct 2008 09:55:48 -0500
Message-Id: <AF99D145-C09C-4DC2-892C-EFA90F1726C6@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Juha Heinanen <jh@tutpro.com>
In-Reply-To: <18680.23958.246188.814477@taimen.test.fi>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 17 Oct 2008 09:55:39 -0500
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBNTHT12009MSX.gb002.siemens.net>
	<068483D2-2A92-4DA0-A177-F8CACACA72A7@softarmor.com> <"48F674
	3A.4060006"@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF087246CE@esealmw113.eemea.ericsson.se>
	<A95EB2F7-66F4-41CF-AC2A-2783532332C0@softarmor.com>
	<48F7D76F.1090808@cisco.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DBACA@GBNTHT12009MSX.gb002.siemens.net>
	<"CA9998CD4A020D418654FCDEF4E70!
	7DF087742 9A"@esealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DBBC2@GBNTHT12009MSX.gb002.siemens.net>
	<18680.23958.246188.814477@taimen.test.fi>
X-Mailer: Apple Mail (2.929.2)
Cc: Bob Penfield <BPenfield@acmepacket.com>, sip@ietf.org,
	Paul Kyzivat <pkyzivat@cisco.com>, "Elwell,
	John" <john.elwell@siemens.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 17, 2008, at 4:40 AM, Juha Heinanen wrote:

> Elwell, John writes:
>
>> It is not clear why would need anything else. Why would you need to
>> parallel fork to the same instance ID, when you can use different
>> instance IDs?
>
> just one clarifying question:
>
> it was not clear to me if separate instance ids need to be used for
> different contacts of the same ua, can a single register request  
> contain
> both contacts and their instance ids?  for example, if my ua has two
> contacts and ob set has two proxies, does my ua need to send two or  
> four
> register requests?
>
> if four, i cannot accept a draft which causes such a mess.
>

Keep in mind that the processing of the REGISTER request forms the  
flow-path. As the request and response traverse the proxies, the  
information needed for service-route and path are discovered and stored.

Let us first think about registrations from different physical  
interfaces. Since the edge proxy on each interface is likely to be  
different, the flow-path needed for each registration is different.  
Clearly each outbound registration from a different interface requires  
a separate REGISTER request in order to assure formation of a correct  
flow-path.

In the typical outbound case, the edge proxy is also different for  
each reg-id. That's the goal of the redundancy function of outbound --  
allowing multiple edge proxy bindings. Since the edge proxy is  
recorded into the flow-path by the passage of the REGISTER request and  
response through that proxy, separate REGISTER requests would appear  
to be needed for each edge proxy (and consequently for each reg-ID  
from a given instance).

So the general solution for two instances, each of which has two  
registration flows through different edge proxies, would appear to  
require for REGISTER requests. This model provides full single-failure  
interface redundancy, flow redundancy, edge-proxy redundancy,  
transport redundancy, and possibly (depending on the registrar design)  
registrar redundancy, and provides multiple-failure redundancy in a  
number of scenarios. More importantly, it allows survivability for a  
dialog in the event of any single failure (except perhaps a total  
registrar failure).

Now it is entirely possible, Juha, that you have in mind some sort of  
reduced case-case use for Outbound. I think what you want requires two  
instances, each of which has a single flow-path to the registrar.  
Thus, only two registrations would be required. This provides a weaker  
survival model in-dialog than the two-instance/two-flow (2x2)  model,  
but has a different recovery model than the one-instance/two-flow base  
model of Outbound. There might be cases where this is seen as more  
suitable, although I can't identify one off-hand.

--
Dean

--
Dean

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


From sip-bounces@ietf.org  Fri Oct 17 08:08:13 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 076843A6A8F;
	Fri, 17 Oct 2008 08:08:13 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B8B793A6A8F
	for <sip@core3.amsl.com>; Fri, 17 Oct 2008 08:08:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level: 
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5
	tests=[AWL=-0.012, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vvjPD71HBp4P for <sip@core3.amsl.com>;
	Fri, 17 Oct 2008 08:08:11 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id F033A3A6A4C
	for <sip@ietf.org>; Fri, 17 Oct 2008 08:08:10 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9HF4vmV019417
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT)
	for <sip@ietf.org>; Fri, 17 Oct 2008 10:04:58 -0500
Message-Id: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: SIP IETF <sip@ietf.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 17 Oct 2008 10:04:52 -0500
X-Mailer: Apple Mail (2.929.2)
Subject: [Sip] Stupid question on flow use in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Assume Bob's UA is using outbound and is registered with two flows.  
Both flows use the same instance-id. The first flow goes through edge- 
proxy 1 and has reg-id 1. The second flow goes through proxy 2 and has  
reg-id 2.

Both flows are "live" from a keepalive perspective.

Alice calls Bob.

Which flow gets exercised?

Where in Outbound is this described? If it is not in Outbound, is it  
described somewhere else? If it is simply left-to-the-implementation,  
does this need to be explained somewhere?

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


From sip-bounces@ietf.org  Fri Oct 17 08:12:20 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF3D63A6A9C;
	Fri, 17 Oct 2008 08:12:20 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1BEA93A67AC
	for <sip@core3.amsl.com>; Fri, 17 Oct 2008 08:12:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[AWL=-0.011, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id hGwH5HuHqNXS for <sip@core3.amsl.com>;
	Fri, 17 Oct 2008 08:12:19 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 4E59A3A6A9C
	for <sip@ietf.org>; Fri, 17 Oct 2008 08:12:19 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9HFCep8019510
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT)
	for <sip@ietf.org>; Fri, 17 Oct 2008 10:12:41 -0500
Message-Id: <0DE08EA6-0B60-4C13-A398-17A7C4C6B46C@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: SIP IETF <sip@ietf.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 17 Oct 2008 10:12:34 -0500
X-Mailer: Apple Mail (2.929.2)
Subject: [Sip] Thoughts on how gruu, outbound,
	etc. should have been documented
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


In retrospect, our world might be tidier had we used a document  
structure something like this:

1) Instance identification for SIP user agents, and the use of  
instance identification in SIP registration.

2) Global aliasing for user-agent-instance/AOR tuples (making/using a  
GRUU for an instance)

3) Keepalive for SIP message sequences.

4) Persistence and reuse of registration flows (core Outbound).

5) Enhanced availability architecture using the preceding design  
elements.


--
Dean



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


From sip-bounces@ietf.org  Fri Oct 17 08:18:43 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 965DB3A6A6C;
	Fri, 17 Oct 2008 08:18:43 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8C46E3A6A6C
	for <sip@core3.amsl.com>; Fri, 17 Oct 2008 08:18:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[AWL=-0.011, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AZqkWaAonItO for <sip@core3.amsl.com>;
	Fri, 17 Oct 2008 08:18:41 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id B68DE3A6A16
	for <sip@ietf.org>; Fri, 17 Oct 2008 08:18:41 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9HFJVnu019597
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 17 Oct 2008 10:19:33 -0500
Message-Id: <2C8744D2-4856-4035-94BD-0B5B858AE6BC@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <AF99D145-C09C-4DC2-892C-EFA90F1726C6@softarmor.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 17 Oct 2008 10:19:26 -0500
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com>
	<2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com>
	<18673.62485.295631.933830@taimen.test.fi>
	<2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com>
	<18675.7684.207071.901832@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se>
	<18675.41223.587006.241312@taimen.test.fi>
	<18675.41926.583512.912121@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se>
	<E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBNTHT12009MSX.gb002.siemens.net>
	<068483D2-2A92-4DA0-A177-F8CACACA72A7@softarmor.com> <"48F674
	3A.4060006"@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF087246CE@esealmw113.eemea.ericsson.se>
	<A95EB2F7-66F4-41CF-AC2A-2783532332C0@softarmor.com>
	<48F7D76F.1090808@cisco.com>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DBACA@GBNTHT12009MSX.gb002.siemens.net>
	<"CA9998CD4A020D418654FCDEF4E70!
	! 7DF087742 9A"@esealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D0012DBBC2@GBNTHT12009MSX.gb002.siemens.net>
	<18680.23958.246188.814477@taimen.test.fi>
	<AF99D145-C09C-4DC2-892C-EFA90F1726C6@softarmor.com>
X-Mailer: Apple Mail (2.929.2)
Cc: Bob Penfield <BPenfield@acmepacket.com>, sip@ietf.org,
	Paul Kyzivat <pkyzivat@cisco.com>, "Elwell,
	John" <john.elwell@siemens.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 17, 2008, at 9:55 AM, Dean Willis wrote:

>
> So the general solution for two instances, each of which has two  
> registration flows through different edge proxies, would appear to  
> require for REGISTER requests. This model provides full single- 
> failure interface redundancy, flow redundancy, edge-proxy  
> redundancy, transport redundancy, and possibly (depending on the  
> registrar design) registrar redundancy, and provides multiple- 
> failure redundancy in a number of scenarios. More importantly, it  
> allows survivability for a dialog in the event of any single failure  
> (except perhaps a total registrar failure).

That should have been a "four register requests", not  "for register  
requests":

So the general solution for two instances, each of which has two  
registration flows through different edge proxies, would appear to  
require four REGISTER requests. This model provides full single- 
failure interface redundancy, flow redundancy, edge-proxy redundancy,  
transport redundancy, and possibly (depending on the registrar design)  
registrar redundancy, and provides multiple-failure redundancy in a  
number of scenarios. More importantly, it allows survivability for a  
dialog in the event of any single failure (except perhaps a total  
registrar failure).



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


From sip-bounces@ietf.org  Fri Oct 17 09:45:57 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 30C3F3A6A2B;
	Fri, 17 Oct 2008 09:45:57 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 19AC63A67EA
	for <sip@core3.amsl.com>; Fri, 17 Oct 2008 09:45:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[AWL=-0.011, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id PbL4xgZhld7Y for <sip@core3.amsl.com>;
	Fri, 17 Oct 2008 09:45:55 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 4F87A3A6A2B
	for <sip@ietf.org>; Fri, 17 Oct 2008 09:45:55 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9HGkvCI020448
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT)
	for <sip@ietf.org>; Fri, 17 Oct 2008 11:46:59 -0500
Message-Id: <C2FE0C2E-4EDA-4CCD-AAA1-D1122654665C@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: SIP IETF <sip@ietf.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 17 Oct 2008 11:46:52 -0500
X-Mailer: Apple Mail (2.929.2)
Subject: [Sip] Outbound and mid-dialog requests with GRUU
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Here's a question:

A UA has registered two flows to one instance. It has one gruu. The UA  
uses the gruu as the contact in a dialog-forming request.

An in-dialog request (for example, BYE) is sent back  to the UA. On  
which flow does it get routed?

I believe: It gets routed on the flow that formed the dialog, as long  
as that flow exists. The proxy has stored dialog state and knows which  
flow the dialog-forming request used.

The GRUU spec assumes one contact per gruu. Outbound transforms this  
to multiple contacts and multiple flows per gruu. I think this  
requires further specification as to flow selection, possibly for out- 
of-dialog messages and almost definitely for in-dialog messages.  
Perhaps this is documented somewhere and I've just missed it.

Any clues?

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


From sip-bounces@ietf.org  Fri Oct 17 09:59:44 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 00DF23A6781;
	Fri, 17 Oct 2008 09:59:44 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7C35F3A6781
	for <sip@core3.amsl.com>; Fri, 17 Oct 2008 09:59:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id sy4zgkDdvUVD for <sip@core3.amsl.com>;
	Fri, 17 Oct 2008 09:59:41 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id 9A8933A6780
	for <sip@ietf.org>; Fri, 17 Oct 2008 09:59:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 43C1F1EC2CE;
	Fri, 17 Oct 2008 20:00:10 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SVN-L9EM0uL5; Fri, 17 Oct 2008 20:00:08 +0300 (EEST)
Received: from taimen (h171120.gprs.dnafinland.fi [87.93.171.120])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Fri, 17 Oct 2008 20:00:08 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id F0D88AC0EF; Fri, 17 Oct 2008 20:00:03 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18680.50323.497877.834548@taimen.test.fi>
Date: Fri, 17 Oct 2008 20:00:03 +0300
To: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <C2FE0C2E-4EDA-4CCD-AAA1-D1122654665C@softarmor.com>
References: <C2FE0C2E-4EDA-4CCD-AAA1-D1122654665C@softarmor.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: SIP IETF <sip@ietf.org>
Subject: [Sip]  Outbound and mid-dialog requests with GRUU
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Dean Willis writes:

 > Any clues?

it is very revealing that at the stage when these i-d are about to go to
rfc editors for publishing, there is lots of all kind of issues that
even the experts are not sure about.

even if these issues finally get sorted out on the list, there is
absolutely no chance whatsoever that an average implementer who has not
participated in these discussions could even get his/her implementation
correct.  these specifications are far too complicated for that.

it should be a high time to take a timeout and go back to the basics.

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


From sip-bounces@ietf.org  Fri Oct 17 10:20:07 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B91163A6AD5;
	Fri, 17 Oct 2008 10:20:07 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EC2093A6AD5
	for <sip@core3.amsl.com>; Fri, 17 Oct 2008 10:20:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.503
X-Spam-Level: 
X-Spam-Status: No, score=-6.503 tagged_above=-999 required=5 tests=[AWL=0.096, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6k2PnYtbtiM8 for <sip@core3.amsl.com>;
	Fri, 17 Oct 2008 10:20:04 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id ADD933A6936
	for <sip@ietf.org>; Fri, 17 Oct 2008 10:20:04 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,432,1220227200"; d="scan'208";a="24658322"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 17 Oct 2008 17:21:08 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9HHL8BL024704; 
	Fri, 17 Oct 2008 13:21:08 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9HHL8c1001145;
	Fri, 17 Oct 2008 17:21:08 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Oct 2008 13:21:07 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Oct 2008 13:21:07 -0400
Message-ID: <48F8C97C.6010603@cisco.com>
Date: Fri, 17 Oct 2008 13:21:00 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
References: <C2FE0C2E-4EDA-4CCD-AAA1-D1122654665C@softarmor.com>
In-Reply-To: <C2FE0C2E-4EDA-4CCD-AAA1-D1122654665C@softarmor.com>
X-OriginalArrivalTime: 17 Oct 2008 17:21:07.0728 (UTC)
	FILETIME=[BDED1900:01C9307C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2499; t=1224264068;
	x=1225128068; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Outbound=20and=20mid-dialog=20r
	equests=20with=20GRUU |Sender:=20
	|To:=20Dean=20Willis=20<dean.willis@softarmor.com>;
	bh=2oLina1B0vNd3ZLLOSMG16qGNASKAQ5svMXlA6Jik9E=;
	b=q474Iz6+wskMHlXVOATFpwec0ZkrODU+gGqMKRR3u3PjkvociFjcejUCVL
	JY0ZkEclVdC3U8Ic+MzUE52gCNFR+eT+FK/VsCKr/jDG6waEiIW+YlcAZx5R
	DmPKRGAPrG;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Outbound and mid-dialog requests with GRUU
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Dean Willis wrote:
> 
> Here's a question:
> 
> A UA has registered two flows to one instance. It has one gruu. The UA 
> uses the gruu as the contact in a dialog-forming request.
> 
> An in-dialog request (for example, BYE) is sent back  to the UA. On 
> which flow does it get routed?

 From gruu-15:

    If there are no registered contacts bound to the GRUU, the server
    MUST return a 480 (Temporarily Unavailable) response.  If there are
    more than one, there are two cases:

    1.  The client is using draft-ietf-sip-outbound [13] and registering
        multiple contacts for redundancy.  In that case, these contacts
        contain reg-id Contact header field parameters, and the rules
        described in Section 7 of draft-ietf-sip-outbound [13] for
        selecting a single registered contact apply.

    2.  The client was not using SIP outbound, in which case there would
        only be multiple contacts with the same instance ID if the client
        had rebooted, restarted and re-registered.  In this case, these
        contacts would not contain the reg-id Contact header field
        parameter.  The proxy MUST select the most recently refreshed
        contact.  As with draft-ietf-sip-outbound, if a request to this
        target fails with a 408 (Request Timeout) or 430 (Flow Failed)
        response, the proxy SHOULD retry with the next most recently
        refreshed contact.  Furthermore, if the request fails with any
        other response, the proxy MUST NOT retry on any other contacts
        for this instance.


> I believe: It gets routed on the flow that formed the dialog, as long as 
> that flow exists. The proxy has stored dialog state and knows which flow 
> the dialog-forming request used.
> 
> The GRUU spec assumes one contact per gruu. Outbound transforms this to 
> multiple contacts and multiple flows per gruu. I think this requires 
> further specification as to flow selection, possibly for out-of-dialog 
> messages and almost definitely for in-dialog messages. Perhaps this is 
> documented somewhere and I've just missed it.
> 
> Any clues?
> 
> -- 
> Dean
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 17 12:55:50 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9A5D428C10A;
	Fri, 17 Oct 2008 12:55:50 -0700 (PDT)
X-Original-To: sip@ietf.org
Delivered-To: sip@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30)
	id B199F3A6A87; Fri, 17 Oct 2008 12:55:47 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20081017195547.B199F3A6A87@core3.amsl.com>
Date: Fri, 17 Oct 2008 12:55:47 -0700 (PDT)
Cc: sip@ietf.org
Subject: [Sip] Last Call: draft-ietf-sip-dtls-srtp-framework (Framework for
 Establishing an SRTP Security Context using DTLS) to Proposed Standard
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

The IESG has received a request from the Session Initiation Protocol WG 
(sip) to consider the following document:

- 'Framework for Establishing an SRTP Security Context using DTLS '
   <draft-ietf-sip-dtls-srtp-framework-04.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2008-10-31. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-sip-dtls-srtp-framework-04.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=16647&rfc_flag=0

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


From sip-bounces@ietf.org  Fri Oct 17 15:30:56 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 768DC3A6B25;
	Fri, 17 Oct 2008 15:30:56 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 921DD28C0FD
	for <sip@core3.amsl.com>; Fri, 17 Oct 2008 15:30:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.673
X-Spam-Level: 
X-Spam-Status: No, score=-2.673 tagged_above=-999 required=5
	tests=[AWL=-0.074, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id J32YJXBjDns9 for <sip@core3.amsl.com>;
	Fri, 17 Oct 2008 15:30:53 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39])
	by core3.amsl.com (Postfix) with ESMTP id A59333A65A5
	for <sip@ietf.org>; Fri, 17 Oct 2008 15:30:53 -0700 (PDT)
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1])
	by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id m9HMUMG6023524;
	Fri, 17 Oct 2008 17:31:55 -0500 (CDT)
Received: from DEEXP02.DE.lucent.com ([135.248.187.66]) by
	ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Oct 2008 17:31:47 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.20]) by
	DEEXP02.DE.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 18 Oct 2008 00:31:45 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 18 Oct 2008 00:31:44 +0200
Message-ID: <5D1A7985295922448D5550C94DE29180023EA133@DEEXC1U01.de.lucent.com>
In-Reply-To: <18680.50323.497877.834548@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip]  Outbound and mid-dialog requests with GRUU
Thread-Index: Ackwee36TVaXojS4QCq6tCh11eB2PQALMDgg
References: <C2FE0C2E-4EDA-4CCD-AAA1-D1122654665C@softarmor.com>
	<18680.50323.497877.834548@taimen.test.fi>
From: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: "Juha Heinanen" <jh@tutpro.com>, "Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 17 Oct 2008 22:31:45.0330 (UTC)
	FILETIME=[22CD7920:01C930A8]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Outbound and mid-dialog requests with GRUU
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

(An informational note from one of the WG co-chairs)

This document is not about to go to the RFC editor's for publishing.

It is about to go to the IETF to see if they agree it, i.e. the SIP WG
have submitted a publication request.

That means it still gets reviewed by:

Our AD
The security directorate
The GEN ART review team
Any other review teams that think they have a hand in this
IANA
The IETF as a whole (and that definitely does include you unless you
explicitly exclude yourself)
The IESG as a whole

Once that has happened, the world just may let the RFC editors get their
hands on it.

I am sure somewhere in that process you can get to make any comments you
think relevant - as I believe I have said before.

And I would note that at the moment I have see any proposal that adds
more than about 4 lines of text to outbound, and no other issues that
are so far looking like they achieve consensus that there is an issue.
On that basis there are many many more documents that score lower in
their readiness for publication request - and I note that none of this
current discussion got raised by you until we had completed at least two
WGLC and at least two requests to see if we were ready for the
publication request. 

So yes carry on making comments, but lets look to start building some
consensus from the responses.

Regards

Keith

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Juha Heinanen
> Sent: Friday, October 17, 2008 6:00 PM
> To: Dean Willis
> Cc: SIP IETF
> Subject: [Sip] Outbound and mid-dialog requests with GRUU
> 
> Dean Willis writes:
> 
>  > Any clues?
> 
> it is very revealing that at the stage when these i-d are 
> about to go to rfc editors for publishing, there is lots of 
> all kind of issues that even the experts are not sure about.
> 
> even if these issues finally get sorted out on the list, 
> there is absolutely no chance whatsoever that an average 
> implementer who has not participated in these discussions 
> could even get his/her implementation correct.  these 
> specifications are far too complicated for that.
> 
> it should be a high time to take a timeout and go back to the basics.
> 
> -- juha
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors@cs.columbia.edu for questions on current sip 
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 17 16:45:38 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 563B33A6AA9;
	Fri, 17 Oct 2008 16:45:38 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E0EB33A6AA9
	for <sip@core3.amsl.com>; Fri, 17 Oct 2008 16:45:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[AWL=-0.011, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8+C-5Ay4XX0z for <sip@core3.amsl.com>;
	Fri, 17 Oct 2008 16:45:35 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 6E57A3A6B20
	for <sip@ietf.org>; Fri, 17 Oct 2008 16:45:35 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9HNkc0A023539
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 17 Oct 2008 18:46:39 -0500
Message-Id: <0F49EA03-A8EE-41CE-AF56-4281B5881FEF@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Juha Heinanen <jh@tutpro.com>
In-Reply-To: <18680.50323.497877.834548@taimen.test.fi>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 17 Oct 2008 18:46:32 -0500
References: <C2FE0C2E-4EDA-4CCD-AAA1-D1122654665C@softarmor.com>
	<18680.50323.497877.834548@taimen.test.fi>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Outbound and mid-dialog requests with GRUU
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 17, 2008, at 12:00 PM, Juha Heinanen wrote:

> Dean Willis writes:
>
>> Any clues?
>
> it is very revealing that at the stage when these i-d are about to  
> go to
> rfc editors for publishing, there is lots of all kind of issues that
> even the experts are not sure about.

Huh. I figure that I'm usually the last to understand something; by  
the time I understand it, it should be obvious to everybody. I still  
don't understand SDP.

> even if these issues finally get sorted out on the list, there is
> absolutely no chance whatsoever that an average implementer who has  
> not
> participated in these discussions could even get his/her  
> implementation
> correct.  these specifications are far too complicated for that.

You're right. I think we should close the working group and ban all  
authors from publishing for  a year. That'll teach us!

--
Dean


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


From sip-bounces@ietf.org  Fri Oct 17 17:02:00 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5A75D3A68A1;
	Fri, 17 Oct 2008 17:02:00 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5CB323A68A1
	for <sip@core3.amsl.com>; Fri, 17 Oct 2008 17:01:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[AWL=-0.011, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OBjmIHJjU1g3 for <sip@core3.amsl.com>;
	Fri, 17 Oct 2008 17:01:57 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 8AE1A3A67DB
	for <sip@ietf.org>; Fri, 17 Oct 2008 17:01:57 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9I02rGp023650
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 17 Oct 2008 19:02:55 -0500
Message-Id: <72946674-BEAB-4E2B-87B7-543DD13CA0B7@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
In-Reply-To: <48F8C97C.6010603@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 17 Oct 2008 19:02:48 -0500
References: <C2FE0C2E-4EDA-4CCD-AAA1-D1122654665C@softarmor.com>
	<48F8C97C.6010603@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Outbound and mid-dialog requests with GRUU
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 17, 2008, at 12:21 PM, Paul Kyzivat wrote:

>
>
> Dean Willis wrote:
>> Here's a question:
>> A UA has registered two flows to one instance. It has one gruu. The  
>> UA uses the gruu as the contact in a dialog-forming request.
>> An in-dialog request (for example, BYE) is sent back  to the UA. On  
>> which flow does it get routed?
>
> From gruu-15:
>
>
>   1.  The client is using draft-ietf-sip-outbound [13] and registering
>       multiple contacts for redundancy.  In that case, these contacts
>       contain reg-id Contact header field parameters, and the rules
>       described in Section 7 of draft-ietf-sip-outbound [13] for
>       selecting a single registered contact apply.



Not helpful; section 7 refers to out-of-dialog request forwarding.

What happens to in-dialog requests?

The request references a gruu.

A pre-outbound gruu is bound to one and only one contact, so the  
request-URI transformation rule is obvious; transform the request-URI  
using the contact associated with the gruu. This behavior is specified  
in 6.1 of the gruu draft. Oddly enough, that text in gruu-6.1 replaces  
the request-URI with "the registered contacts" (note the plural). Not  
sure that makes sense. Somebody tell me if that's a bug in gruu.

An outbound-compliant gruu is bound to one and only instance, but an  
instance can have multiple contacts.

I think what has to happen to make it work is fairly obvious, but it  
isn't documented anywhere I can find.

There's some hinting at it in outbound-5.3.2, but inly from the  
perspective of the edge proxy. What has to happen at the home proxy to  
make this work?

--
Dean


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


From sip-bounces@ietf.org  Fri Oct 17 17:49:27 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D55403A69CF;
	Fri, 17 Oct 2008 17:49:27 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C324A3A69CF
	for <sip@core3.amsl.com>; Fri, 17 Oct 2008 17:49:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.508
X-Spam-Level: 
X-Spam-Status: No, score=-6.508 tagged_above=-999 required=5 tests=[AWL=0.091, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tHL10J3P3Sut for <sip@core3.amsl.com>;
	Fri, 17 Oct 2008 17:49:25 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 9B6EF3A67DB
	for <sip@ietf.org>; Fri, 17 Oct 2008 17:49:25 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,435,1220227200"; d="scan'208";a="24674387"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 18 Oct 2008 00:50:30 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9I0oUev013227; 
	Fri, 17 Oct 2008 20:50:30 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9I0oUUm013950;
	Sat, 18 Oct 2008 00:50:30 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Oct 2008 20:50:30 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Oct 2008 20:50:30 -0400
Message-ID: <48F932D1.3070401@cisco.com>
Date: Fri, 17 Oct 2008 20:50:25 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
References: <C2FE0C2E-4EDA-4CCD-AAA1-D1122654665C@softarmor.com>
	<48F8C97C.6010603@cisco.com>
	<72946674-BEAB-4E2B-87B7-543DD13CA0B7@softarmor.com>
In-Reply-To: <72946674-BEAB-4E2B-87B7-543DD13CA0B7@softarmor.com>
X-OriginalArrivalTime: 18 Oct 2008 00:50:30.0209 (UTC)
	FILETIME=[84D13310:01C930BB]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2192; t=1224291030;
	x=1225155030; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Outbound=20and=20mid-dialog=20r
	equests=20with=20GRUU |Sender:=20
	|To:=20Dean=20Willis=20<dean.willis@softarmor.com>;
	bh=XC81zC83G5Wds/iCyXIm24Opfd6xQnZjdMAF4HRjMtw=;
	b=DxEG+KEUomgfYzITOEKNWf2eMXPeXAU2DQuLCQnzbcA2fqKXLbmJ36t9Hc
	TZDyxYZjuAg+0Oe4d2aB3SCQL3gGdSffZ2psJcppeKZ82417onPVLciP+BoA
	KDVgi6QAZi;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Outbound and mid-dialog requests with GRUU
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Dean Willis wrote:
> 
> On Oct 17, 2008, at 12:21 PM, Paul Kyzivat wrote:
> 
>>
>>
>> Dean Willis wrote:
>>> Here's a question:
>>> A UA has registered two flows to one instance. It has one gruu. The 
>>> UA uses the gruu as the contact in a dialog-forming request.
>>> An in-dialog request (for example, BYE) is sent back  to the UA. On 
>>> which flow does it get routed?
>>
>> From gruu-15:
>>
>>
>>   1.  The client is using draft-ietf-sip-outbound [13] and registering
>>       multiple contacts for redundancy.  In that case, these contacts
>>       contain reg-id Contact header field parameters, and the rules
>>       described in Section 7 of draft-ietf-sip-outbound [13] for
>>       selecting a single registered contact apply.
> 
> 
> 
> Not helpful; section 7 refers to out-of-dialog request forwarding.

Why do you say that. That section of outbound doesn't even mention dialogs.

> What happens to in-dialog requests?

> The request references a gruu.
> 
> A pre-outbound gruu is bound to one and only one contact, so the 
> request-URI transformation rule is obvious; transform the request-URI 
> using the contact associated with the gruu. This behavior is specified 
> in 6.1 of the gruu draft. Oddly enough, that text in gruu-6.1 replaces 
> the request-URI with "the registered contacts" (note the plural). Not 
> sure that makes sense. Somebody tell me if that's a bug in gruu.
> 
> An outbound-compliant gruu is bound to one and only instance, but an 
> instance can have multiple contacts.
> 
> I think what has to happen to make it work is fairly obvious, but it 
> isn't documented anywhere I can find.
> 
> There's some hinting at it in outbound-5.3.2, but inly from the 
> perspective of the edge proxy. What has to happen at the home proxy to 
> make this work?

I assume the same thing as for out of dialog requests. Out of dialog 
requests that reference a gruu need just as much to get to the proper 
instance as in-dialog requests do.

Why does it matter if both flows are functional? Presumably if one of 
the flows has had problems the proxy ought to choose the other one first.

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


From sip-bounces@ietf.org  Fri Oct 17 18:17:29 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A325F3A67F8;
	Fri, 17 Oct 2008 18:17:29 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9EDF43A67F8
	for <sip@core3.amsl.com>; Fri, 17 Oct 2008 18:17:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.609
X-Spam-Level: 
X-Spam-Status: No, score=-2.609 tagged_above=-999 required=5
	tests=[AWL=-0.010, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ldJBKzGZqo15 for <sip@core3.amsl.com>;
	Fri, 17 Oct 2008 18:17:27 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id BF3C23A67C0
	for <sip@ietf.org>; Fri, 17 Oct 2008 18:17:27 -0700 (PDT)
Received: from [192.168.2.103] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9I1IU4g024034
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 17 Oct 2008 20:18:31 -0500
Message-Id: <A8D4EED1-4C7A-447E-AA1B-F077EB03B434@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
In-Reply-To: <48F932D1.3070401@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 17 Oct 2008 20:18:24 -0500
References: <C2FE0C2E-4EDA-4CCD-AAA1-D1122654665C@softarmor.com>
	<48F8C97C.6010603@cisco.com>
	<72946674-BEAB-4E2B-87B7-543DD13CA0B7@softarmor.com>
	<48F932D1.3070401@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Outbound and mid-dialog requests with GRUU
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 17, 2008, at 7:50 PM, Paul Kyzivat wrote:
>>>
>> Not helpful; section 7 refers to out-of-dialog request forwarding.
>
> Why do you say that. That section of outbound doesn't even mention  
> dialogs.
>

It also doesn't mention multiple contacts per GRUU.

>> What happens to in-dialog requests?
>
>> The request references a gruu.
>> A pre-outbound gruu is bound to one and only one contact, so the  
>> request-URI transformation rule is obvious; transform the request- 
>> URI using the contact associated with the gruu. This behavior is  
>> specified in 6.1 of the gruu draft. Oddly enough, that text in  
>> gruu-6.1 replaces the request-URI with "the registered  
>> contacts" (note the plural). Not sure that makes sense. Somebody  
>> tell me if that's a bug in gruu.
>> An outbound-compliant gruu is bound to one and only instance, but  
>> an instance can have multiple contacts.
>> I think what has to happen to make it work is fairly obvious, but  
>> it isn't documented anywhere I can find.
>> There's some hinting at it in outbound-5.3.2, but inly from the  
>> perspective of the edge proxy. What has to happen at the home proxy  
>> to make this work?
>
> I assume the same thing as for out of dialog requests. Out of dialog  
> requests that reference a gruu need just as much to get to the  
> proper instance as in-dialog requests do.

Not really; for out-of-dialog requests, any contact is equally valid.  
But for in-dialog requests, I think there's a need to use the flow  
that was used by the earlier requests in the dialog, if that's possible.

>
>
> Why does it matter if both flows are functional? Presumably if one  
> of the flows has had problems the proxy ought to choose the other  
> one first.

Are there any SIP devices that get confused when they see an  
unexpected request URI on a request, for example, when the request URI  
spontaneously changes mid-dialog without a reINVITE?

Are there other elements that might get confused by NOT seeing some  
messages in a dialog?

For example: what happens if there is an off-the-shelf SBC squatting  
on each flow?

--
Dean

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


From sip-bounces@ietf.org  Fri Oct 17 23:14:03 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3EBBF3A6928;
	Fri, 17 Oct 2008 23:14:03 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6279C3A6928
	for <sip@core3.amsl.com>; Fri, 17 Oct 2008 23:14:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FVpD9SlELFd9 for <sip@core3.amsl.com>;
	Fri, 17 Oct 2008 23:14:01 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id 8C9013A67D9
	for <sip@ietf.org>; Fri, 17 Oct 2008 23:14:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 318181EC2CE;
	Sat, 18 Oct 2008 09:15:04 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 39uiRvGMtB3P; Sat, 18 Oct 2008 09:15:02 +0300 (EEST)
Received: from taimen (h151042.gprs.dnafinland.fi [87.93.151.42])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Sat, 18 Oct 2008 09:15:02 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id E59CDAC0EB; Sat, 18 Oct 2008 09:14:54 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18681.32478.874497.179953@taimen.test.fi>
Date: Sat, 18 Oct 2008 09:14:54 +0300
To: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <0F49EA03-A8EE-41CE-AF56-4281B5881FEF@softarmor.com>
References: <C2FE0C2E-4EDA-4CCD-AAA1-D1122654665C@softarmor.com>
	<18680.50323.497877.834548@taimen.test.fi>
	<0F49EA03-A8EE-41CE-AF56-4281B5881FEF@softarmor.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Outbound and mid-dialog requests with GRUU
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Dean Willis writes:

 > You're right. I think we should close the working group and ban all  
 > authors from publishing for  a year. That'll teach us!

exactly and better yet, start implementing what has been published or
about to be published.  when all specs have been implemented by the
authors and interoperability has been verified, the gw can resume its
work.

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


From sip-bounces@ietf.org  Sat Oct 18 05:54:08 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D0FB73A6913;
	Sat, 18 Oct 2008 05:54:08 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CF7CA3A6913
	for <sip@core3.amsl.com>; Sat, 18 Oct 2008 05:54:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.747
X-Spam-Level: 
X-Spam-Status: No, score=-2.747 tagged_above=-999 required=5
	tests=[AWL=-0.148, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id iKim3GOr3hHc for <sip@core3.amsl.com>;
	Sat, 18 Oct 2008 05:54:06 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37])
	by core3.amsl.com (Postfix) with ESMTP id EB5B83A68EB
	for <sip@ietf.org>; Sat, 18 Oct 2008 05:54:05 -0700 (PDT)
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1])
	by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id m9ICt53m020482;
	Sat, 18 Oct 2008 07:55:05 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by
	ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 18 Oct 2008 07:55:05 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.20]) by
	DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 18 Oct 2008 14:55:02 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 18 Oct 2008 14:55:01 +0200
Message-ID: <5D1A7985295922448D5550C94DE29180023EA139@DEEXC1U01.de.lucent.com>
In-Reply-To: <B3DE6853-21AA-4FF5-B1E9-96236DA0748C@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckwYhuhqUiEVI/EQtG3iqPZUFuNjQAvlX0A
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><2210d2240810120145o2297ac07v3487d014955bf0@mail.gmail.com><18673.62485.295631.933830@taimen.test.fi><2210d2240810130000i30c61aaei8a7f88f2069e46c0@mail.gmail.com><18675.7684.207071.901832@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8EF@esealmw113.eemea.ericsson.se><18675.41223.587006.241312@taimen.test.fi><18675.41926.583512.912121@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F8F2@esealmw113.eemea.ericsson.se><E6C2E8958BA59A4FB960963D475F7AC3128435A4EA@mail.acmepacket.com><0D5F89FAC29E2C41B98A6A762007F5D0012DB166@GBNTHT12009MSX.gb002.siemens.net><068483D2-2A92-4DA0-A177-F8CACACA72A7@softarmor.com>
	<"48F6743A.4060006"@cisco.com><CA9998CD4A020D418654FCDEF4E707DF087246CE@esealmw113.eemea.ericsson.se><A95EB2F7-66F4-41CF-AC2A-2783532332C0@softarmor.com><48F7D76F.1090808@cisco.com><0D5F89FAC29E2C41B98A6A762007F5D0012DBACA@GBNTHT12009MSX.gb002.siemens.net><CA9998CD4A020D418654FCDEF4E707!DF0877429A@eseal!
	mw113.eem ea.ericsson.
	se> <B3DE6853-21AA-4FF5-B1E9-96236DA0748C@softarmor.com>
From: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: "Dean Willis" <dean.willis@softarmor.com>,
	"Christer Holmberg" <christer.holmberg@ericsson.com>
X-OriginalArrivalTime: 18 Oct 2008 12:55:02.0399 (UTC)
	FILETIME=[BC42F8F0:01C93120]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Cc: Bob Penfield <BPenfield@acmepacket.com>, sip@ietf.org,
	Paul Kyzivat <pkyzivat@cisco.com>, "Elwell, John" <john.elwell@siemens.com>
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

(As individual)

At the moment, it may be that there is a useful information or BCP that
could back the existing mechansisms up, but I am not seeing in this
thread at the moment a significant justification for a new extension.

And of course such an informational or BCP would only exist if someone
volunteered to draft one.

Regards

Keith 

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Dean Willis
> Sent: Friday, October 17, 2008 3:10 PM
> To: Christer Holmberg
> Cc: Bob Penfield; sip@ietf.org; Paul Kyzivat; Elwell, John
> Subject: Re: [Sip] Dual registration without Outbound
> 
> 
> On Oct 17, 2008, at 3:08 AM, Christer Holmberg wrote:
> 
> >
> > Hi,
> >
> > The please-perform-parallel-forking-to-the-same-intance-id 
> extension 
> > indication would then be brought as a separate draft.
> >
> 
> Do we need such an extension when there is a workaround -- 
> using different instance-id?
> 
> --
> Dean
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors@cs.columbia.edu for questions on current sip 
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Sat Oct 18 07:50:31 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2EF213A68A4;
	Sat, 18 Oct 2008 07:50:31 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7C94B3A67F2
	for <sip@core3.amsl.com>; Sat, 18 Oct 2008 07:50:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rHqnmpng9siW for <sip@core3.amsl.com>;
	Sat, 18 Oct 2008 07:50:28 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 3DC403A68E5
	for <sip@ietf.org>; Sat, 18 Oct 2008 07:50:28 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,438,1220227200"; d="scan'208";a="24708723"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 18 Oct 2008 14:51:32 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9IEpWQa019690; 
	Sat, 18 Oct 2008 10:51:32 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9IEpWiG001312;
	Sat, 18 Oct 2008 14:51:32 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 18 Oct 2008 10:51:32 -0400
Received: from [10.86.251.214] ([10.86.251.214]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 18 Oct 2008 10:51:31 -0400
Message-ID: <48F9F7F0.2020705@cisco.com>
Date: Sat, 18 Oct 2008 10:51:28 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
References: <C2FE0C2E-4EDA-4CCD-AAA1-D1122654665C@softarmor.com>
	<48F8C97C.6010603@cisco.com>
	<72946674-BEAB-4E2B-87B7-543DD13CA0B7@softarmor.com>
	<48F932D1.3070401@cisco.com>
	<A8D4EED1-4C7A-447E-AA1B-F077EB03B434@softarmor.com>
In-Reply-To: <A8D4EED1-4C7A-447E-AA1B-F077EB03B434@softarmor.com>
X-OriginalArrivalTime: 18 Oct 2008 14:51:32.0042 (UTC)
	FILETIME=[0269DAA0:01C93131]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2509; t=1224341492;
	x=1225205492; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Outbound=20and=20mid-dialog=20r
	equests=20with=20GRUU |Sender:=20
	|To:=20Dean=20Willis=20<dean.willis@softarmor.com>;
	bh=Y2FIMSsJUnnpPymqSZt1C41levddMtLm13aq94nnnRw=;
	b=qeIGxg+5dUuJv2lu45y2PjsKoBsi9efCjQYKadnLVKcoIfWxnVXtByx5fn
	mV19psV+w6wsRsuQloU1smXdphEgn5NMGHIgeMr4DUj2QlLceMGyGG8ayuTS
	UpghL20b5/;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Outbound and mid-dialog requests with GRUU
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

comment at end.

Dean Willis wrote:
> 
> On Oct 17, 2008, at 7:50 PM, Paul Kyzivat wrote:
>>>>
>>> Not helpful; section 7 refers to out-of-dialog request forwarding.
>>
>> Why do you say that. That section of outbound doesn't even mention 
>> dialogs.
>>
> 
> It also doesn't mention multiple contacts per GRUU.
> 
>>> What happens to in-dialog requests?
>>
>>> The request references a gruu.
>>> A pre-outbound gruu is bound to one and only one contact, so the 
>>> request-URI transformation rule is obvious; transform the request-URI 
>>> using the contact associated with the gruu. This behavior is 
>>> specified in 6.1 of the gruu draft. Oddly enough, that text in 
>>> gruu-6.1 replaces the request-URI with "the registered contacts" 
>>> (note the plural). Not sure that makes sense. Somebody tell me if 
>>> that's a bug in gruu.
>>> An outbound-compliant gruu is bound to one and only instance, but an 
>>> instance can have multiple contacts.
>>> I think what has to happen to make it work is fairly obvious, but it 
>>> isn't documented anywhere I can find.
>>> There's some hinting at it in outbound-5.3.2, but inly from the 
>>> perspective of the edge proxy. What has to happen at the home proxy 
>>> to make this work?
>>
>> I assume the same thing as for out of dialog requests. Out of dialog 
>> requests that reference a gruu need just as much to get to the proper 
>> instance as in-dialog requests do.
> 
> Not really; for out-of-dialog requests, any contact is equally valid. 
> But for in-dialog requests, I think there's a need to use the flow that 
> was used by the earlier requests in the dialog, if that's possible.
> 
>>
>>
>> Why does it matter if both flows are functional? Presumably if one of 
>> the flows has had problems the proxy ought to choose the other one first.
> 
> Are there any SIP devices that get confused when they see an unexpected 
> request URI on a request, for example, when the request URI 
> spontaneously changes mid-dialog without a reINVITE?
> 
> Are there other elements that might get confused by NOT seeing some 
> messages in a dialog?
> 
> For example: what happens if there is an off-the-shelf SBC squatting on 
> each flow?

Well, the multiple flows are there for redundancy, right?
If one of the flows failsl, the whole point is that things should 
continue. If the UA gets upset receiving in-dialog messages on a 
different flow, then things aren't working right.

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


From sip-bounces@ietf.org  Sat Oct 18 10:16:15 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C874F3A67D2;
	Sat, 18 Oct 2008 10:16:15 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 666E63A67D2
	for <sip@core3.amsl.com>; Sat, 18 Oct 2008 10:16:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id uyH2iS0507go for <sip@core3.amsl.com>;
	Sat, 18 Oct 2008 10:16:13 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35])
	by core3.amsl.com (Postfix) with ESMTP id 167983A6783
	for <sip@ietf.org>; Sat, 18 Oct 2008 10:16:13 -0700 (PDT)
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1])
	by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id m9IHGacg008454;
	Sat, 18 Oct 2008 12:17:17 -0500 (CDT)
Received: from ILEXC2U03.ndc.lucent.com ([135.3.39.9]) by
	ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 18 Oct 2008 12:17:15 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 18 Oct 2008 12:17:14 -0500
Message-ID: <1FD3C0CCB36AAA4AAAB874C3898C0B2701AD706B@ILEXC2U03.ndc.lucent.com>
In-Reply-To: <48F9F7F0.2020705@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Outbound and mid-dialog requests with GRUU
Thread-Index: AckxMQ5+EkwhsZp4TH2LeLr8zi4j5QAE/14Q
References: <C2FE0C2E-4EDA-4CCD-AAA1-D1122654665C@softarmor.com><48F8C97C.6010603@cisco.com><72946674-BEAB-4E2B-87B7-543DD13CA0B7@softarmor.com><48F932D1.3070401@cisco.com><A8D4EED1-4C7A-447E-AA1B-F077EB03B434@softarmor.com>
	<48F9F7F0.2020705@cisco.com>
From: "Orsic, Milo \(Milo\)" <orsic@alcatel-lucent.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>,
	"Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 18 Oct 2008 17:17:15.0664 (UTC)
	FILETIME=[5E04B100:01C93145]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Outbound and mid-dialog requests with GRUU
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0899684050=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0899684050==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C93145.5D8A52AD"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C93145.5D8A52AD
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Dean,
Pertaining to Paul's posting below:
------------------------------=20
Well, the multiple flows are there for redundancy, right?
If one of the flows fails, the whole point is that things should
continue. If the UA gets upset receiving in-dialog messages on a
different flow, then things aren't working right.

Thanks,
Paul
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The UA will not get upset, since it may not receive the message. Assume:


1. First registration between (UA's address) IP#1 via edge proxy#1
establishes the binding in the NAT/reflexive-firewall (and flow#1) - as
required by the draft.

2. Second registration between (UA's address) IP#2 via edge proxy#2 is
used for redundancy, establishes the binding in the
NAT/reflexive-firewall (and flow#2) - as required by the draft.

3. Dialog is established using this flow#1 (and Route for this dialog
includes the edge proxy#1).

There was never a registration between IP#2 via proxy#1. Hence, any
in-dialog request (destined for the UA) sent from edge proxy#1 (since it
is in the Route) to IP#2 will be filtered by the NAT/reflexive-firewall.


As you can see by this example, the second registration - as required by
the draft - doesn't really creates a redundant flow. =20
IMHO, the draft should restrict the "redundancy" to a single contact
address (reached via different edge proxies).

Cheers,
Milo=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D=3D=3D
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D=3D=20

-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Paul Kyzivat
Sent: Saturday, October 18, 2008 9:51 AM
To: Dean Willis
Cc: SIP IETF
Subject: Re: [Sip] Outbound and mid-dialog requests with GRUU

comment at end.

Dean Willis wrote:
>=20
> On Oct 17, 2008, at 7:50 PM, Paul Kyzivat wrote:
>>>>
>>> Not helpful; section 7 refers to out-of-dialog request forwarding.
>>
>> Why do you say that. That section of outbound doesn't even mention=20
>> dialogs.
>>
>=20
> It also doesn't mention multiple contacts per GRUU.
>=20
>>> What happens to in-dialog requests?
>>
>>> The request references a gruu.
>>> A pre-outbound gruu is bound to one and only one contact, so the=20
>>> request-URI transformation rule is obvious; transform the=20
>>> request-URI using the contact associated with the gruu. This=20
>>> behavior is specified in 6.1 of the gruu draft. Oddly enough, that=20
>>> text in
>>> gruu-6.1 replaces the request-URI with "the registered contacts"=20
>>> (note the plural). Not sure that makes sense. Somebody tell me if=20
>>> that's a bug in gruu.
>>> An outbound-compliant gruu is bound to one and only instance, but an

>>> instance can have multiple contacts.
>>> I think what has to happen to make it work is fairly obvious, but it

>>> isn't documented anywhere I can find.
>>> There's some hinting at it in outbound-5.3.2, but inly from the=20
>>> perspective of the edge proxy. What has to happen at the home proxy=20
>>> to make this work?
>>
>> I assume the same thing as for out of dialog requests. Out of dialog=20
>> requests that reference a gruu need just as much to get to the proper

>> instance as in-dialog requests do.
>=20
> Not really; for out-of-dialog requests, any contact is equally valid.=20
> But for in-dialog requests, I think there's a need to use the flow=20
> that was used by the earlier requests in the dialog, if that's
possible.
>=20
>>
>>
>> Why does it matter if both flows are functional? Presumably if one of

>> the flows has had problems the proxy ought to choose the other one
first.
>=20
> Are there any SIP devices that get confused when they see an=20
> unexpected request URI on a request, for example, when the request URI

> spontaneously changes mid-dialog without a reINVITE?
>=20
> Are there other elements that might get confused by NOT seeing some=20
> messages in a dialog?
>=20
> For example: what happens if there is an off-the-shelf SBC squatting=20
> on each flow?

Well, the multiple flows are there for redundancy, right?
If one of the flows failsl, the whole point is that things should
continue. If the UA gets upset receiving in-dialog messages on a
different flow, then things aren't working right.

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

------_=_NextPart_001_01C93145.5D8A52AD
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7651.59">
<TITLE>RE: [Sip] Outbound and mid-dialog requests with GRUU</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New Roman">Hi =
Dean,</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">Pertaining to Paul's posting below:</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">------------------------------ </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Well, the =
multiple flows are there for redundancy, right?</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">If one of the =
flows fails, the whole point is that things should continue. If the<U> =
UA gets upset</U> receiving in-dialog messages on a different flow, then =
things aren't working right.</FONT></SPAN></P>

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

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Paul</FONT></SPAN>

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

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New Roman">The UA =
will not get upset, since it may not receive the message. Assume: =
</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New Roman">1. First =
registration between (UA's address) IP#1 via edge proxy#1 establishes =
the binding in the NAT/reflexive-firewall (and flow#1) - as required by =
the draft.</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New Roman">2. =
Second registration between (UA's address) IP#2 via edge =
proxy#2</FONT><U> <FONT SIZE=3D2 FACE=3D"Times New Roman">is used for =
redundancy</FONT></U><FONT SIZE=3D2 FACE=3D"Times New Roman">, =
establishes the binding in the NAT/reflexive-firewall (and flow#2) - as =
required by the draft.</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New Roman">3. =
Dialog is established using this flow#1 (and</FONT><U> <FONT SIZE=3D2 =
FACE=3D"Times New Roman">Route</FONT></U><FONT SIZE=3D2 FACE=3D"Times =
New Roman"> for this dialog includes the</FONT><U><FONT SIZE=3D2 =
FACE=3D"Times New Roman"> edge proxy#1</FONT></U><FONT SIZE=3D2 =
FACE=3D"Times New Roman">).</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New Roman">There =
was never a registration between IP#2 via proxy#1. Hence, any in-dialog =
request (destined for the UA) sent from edge proxy#1 (since it is in =
the</FONT><U> <FONT SIZE=3D2 FACE=3D"Times New Roman">Route)</FONT></U> =
<FONT SIZE=3D2 FACE=3D"Times New Roman">to IP#2 will be filtered by the =
NAT/reflexive-firewall. </FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New Roman">As you =
can see by this example, the second registration - as required by the =
draft -</FONT><U> <FONT SIZE=3D2 FACE=3D"Times New Roman">doesn't really =
creates a redundant flow</FONT></U><FONT SIZE=3D2 FACE=3D"Times New =
Roman">.&nbsp; </FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New Roman">IMHO, =
the draft should restrict the &quot;redundancy&quot; to a single contact =
address (reached via different edge proxies).</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">Cheers,</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New Roman">Milo =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Times New =
Roman">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D</FONT><FONT SIZE=3D2 FACE=3D"Arial"> </FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">-----Original =
Message-----</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">From: =
sip-bounces@ietf.org [</FONT></SPAN><A =
HREF=3D"mailto:sip-bounces@ietf.org"><SPAN LANG=3D"en-us"><U><FONT =
COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">mailto:sip-bounces@ietf.org</FONT></U></SPAN></A><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">] On Behalf Of Paul =
Kyzivat</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Sent: Saturday, =
October 18, 2008 9:51 AM</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">To: Dean =
Willis</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Cc: SIP =
IETF</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Subject: Re: =
[Sip] Outbound and mid-dialog requests with GRUU</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">comment at =
end.</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Dean Willis =
wrote:</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; On Oct 17, =
2008, at 7:50 PM, Paul Kyzivat wrote:</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;&gt;&gt;&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; Not =
helpful; section 7 refers to out-of-dialog request =
forwarding.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt; Why do =
you say that. That section of outbound doesn't even mention =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt; =
dialogs.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; It also =
doesn't mention multiple contacts per GRUU.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; What =
happens to in-dialog requests?</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; The =
request references a gruu.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; A =
pre-outbound gruu is bound to one and only one contact, so the =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; =
request-URI transformation rule is obvious; transform the </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; =
request-URI using the contact associated with the gruu. This =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; =
behavior is specified in 6.1 of the gruu draft. Oddly enough, that =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; text =
in</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; =
gruu-6.1 replaces the request-URI with &quot;the registered =
contacts&quot; </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; =
(note the plural). Not sure that makes sense. Somebody tell me if =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; =
that's a bug in gruu.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; An =
outbound-compliant gruu is bound to one and only instance, but an =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; =
instance can have multiple contacts.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; I =
think what has to happen to make it work is fairly obvious, but it =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; =
isn't documented anywhere I can find.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; =
There's some hinting at it in outbound-5.3.2, but inly from the =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; =
perspective of the edge proxy. What has to happen at the home proxy =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt;&gt; to =
make this work?</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt; I assume =
the same thing as for out of dialog requests. Out of dialog =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt; requests =
that reference a gruu need just as much to get to the proper =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt; instance =
as in-dialog requests do.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; Not really; =
for out-of-dialog requests, any contact is equally valid. </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; But for =
in-dialog requests, I think there's a need to use the flow =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; that was =
used by the earlier requests in the dialog, if that's =
possible.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt; Why does =
it matter if both flows are functional? Presumably if one of =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;&gt; the =
flows has had problems the proxy ought to choose the other one =
first.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; Are there =
any SIP devices that get confused when they see an </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; unexpected =
request URI on a request, for example, when the request URI =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; =
spontaneously changes mid-dialog without a reINVITE?</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; Are there =
other elements that might get confused by NOT seeing some </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; messages in =
a dialog?</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; For example: =
what happens if there is an off-the-shelf SBC squatting </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; on each =
flow?</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Well, the multiple =
flows are there for redundancy, right?</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">If one of the =
flows failsl, the whole point is that things should continue. If the UA =
gets upset receiving in-dialog messages on a different flow, then things =
aren't working right.</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2 FACE=3D"Arial">Thanks,</FONT></SPAN>

<BR><SPAN LANG=3D"en-us">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<FONT SIZE=3D2 FACE=3D"Arial">Paul</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">_______________________________________________</FONT></SP=
AN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Sip mailing =
list&nbsp; </FONT></SPAN><A =
HREF=3D"https://www.ietf.org/mailman/listinfo/sip"><SPAN =
LANG=3D"en-us"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">https://www.ietf.org/mailman/listinfo/sip</FONT></U></SPAN=
></A><SPAN LANG=3D"en-us"></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">This list is for =
NEW development of the core SIP Protocol Use =
sip-implementors@cs.columbia.edu for questions on current sip Use =
sipping@ietf.org for new developments on the application of =
sip</FONT></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C93145.5D8A52AD--

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

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


From sip-bounces@ietf.org  Sun Oct 19 10:36:34 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 197633A6828;
	Sun, 19 Oct 2008 10:36:34 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 637BE3A6805
	for <sip@core3.amsl.com>; Sun, 19 Oct 2008 10:36:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.609
X-Spam-Level: 
X-Spam-Status: No, score=-2.609 tagged_above=-999 required=5
	tests=[AWL=-0.010, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jCMQ6k+ZXENp for <sip@core3.amsl.com>;
	Sun, 19 Oct 2008 10:36:31 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 8140A3A67B2
	for <sip@ietf.org>; Sun, 19 Oct 2008 10:36:31 -0700 (PDT)
Received: from [192.168.15.100] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9JHac5B004958
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT)
	for <sip@ietf.org>; Sun, 19 Oct 2008 12:36:41 -0500
Message-Id: <1A80883E-AB46-4776-92C0-798C7E662D21@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: SIP IETF <sip@ietf.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sun, 19 Oct 2008 12:36:32 -0500
References: <20081016203334.229803A68EC@core3.amsl.com>
X-Mailer: Apple Mail (2.929.2)
Subject: [Sip] WG Interim Meeting Opportunity in January 2009
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


The IETF is planning to host a large-scale interim meeting in Malta in  
January. I'm not sure I can be there, but I don't suppose that will  
stop the WG from meeting.

I'm sure we'll discuss this further on-list, but I wanted to give you  
a "heads up" on the possible meeting now.

--
Dean



Begin forwarded message:

> From: IETF Chair <chair@ietf.org>
> Date: October 16, 2008 3:33:34 PM CDT
> To: Working Group Chairs <wgchairs@ietf.org>
> Cc: chair@ietf.org
> Subject: WG Interim Meeting Opportunity in January 2009
>
> In our continuing effort to ensure that IETF WGs are getting enough
> meeting time to progress their work, we are conducting another  
> experiment.
>  Many WGs have found interim meetings an effective way to tackle  
> thorny
> technical issues, resolve contentious technical issues, accelerate
> standards development, and provide traction for new work.  As  
> always, an
> interim WG meeting is not a substitute for a regular session at the
> traditional IETF meeting.  Since some WG Chairs and ADs have found the
> amount of time necessary to put together an interim meeting can be
> excessive, we are trying to reduce the effort necessary to conduct an
> interim meeting to determine whether reducing this burden will  
> expedite
> IETF standards development.  To this end, the Secretariat will  
> facilitate
> a large interim meeting from 20-22 January 2009 in Malta.  If you are
> interested in participating in this experiment, please contact your  
> Area
> Director for approval.  All face-to-face interim meetings require AD
> approval, and this is no exception.  The IETF Secretariat is putting
> together a program with three full days and four tracks on each  
> day.  Each
> WG interim meeting is expected to consume at least one full day on  
> one of
> the tracks.
>
> ADs will schedule the sessions.  A URL for the schedule will be  
> announced
> shortly.  Once it is available, if you detect a scheduling conflict,
> please raise the concern with your AD for resolution.  Session time is
> limited, and sessions will be allocated first come, first served.
>
> The Secretariat will provide registration, food and beverage, audio
> visual facilities, and on site registration support.  VeriLAN will  
> provide
> network and audio streaming support.  It is expected that the  
> meeting fee
> will be $375 for early registration and $475 for late registration.
>
> The Internet Society is looking for meeting sponsors for this event.
> Anyone interested please contact Drew Dvorshak <dvorshak@isoc.org>.
>
> Russ
>

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


From sip-bounces@ietf.org  Sun Oct 19 10:38:32 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D9A943A6A95;
	Sun, 19 Oct 2008 10:38:32 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 31EB03A6A95
	for <sip@core3.amsl.com>; Sun, 19 Oct 2008 10:38:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.609
X-Spam-Level: 
X-Spam-Status: No, score=-2.609 tagged_above=-999 required=5
	tests=[AWL=-0.010, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3EfZQcv0m2Mq for <sip@core3.amsl.com>;
	Sun, 19 Oct 2008 10:38:31 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 752323A682F
	for <sip@ietf.org>; Sun, 19 Oct 2008 10:38:31 -0700 (PDT)
Received: from [192.168.15.100] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9JHcriS004980
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Sun, 19 Oct 2008 12:38:54 -0500
Message-Id: <9AFE9D6F-FE78-440F-AF2C-6F871C3BF089@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
In-Reply-To: <48F9F7F0.2020705@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sun, 19 Oct 2008 12:38:48 -0500
References: <C2FE0C2E-4EDA-4CCD-AAA1-D1122654665C@softarmor.com>
	<48F8C97C.6010603@cisco.com>
	<72946674-BEAB-4E2B-87B7-543DD13CA0B7@softarmor.com>
	<48F932D1.3070401@cisco.com>
	<A8D4EED1-4C7A-447E-AA1B-F077EB03B434@softarmor.com>
	<48F9F7F0.2020705@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>, Francois Audet <audet@nortel.com>
Subject: Re: [Sip] Outbound and mid-dialog requests with GRUU
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 18, 2008, at 9:51 AM, Paul Kyzivat wrote:

>
> Well, the multiple flows are there for redundancy, right?
> If one of the flows failsl, the whole point is that things should  
> continue. If the UA gets upset receiving in-dialog messages on a  
> different flow, then things aren't working right.


Fair enough. Perhaps a simple statement of this potential, and a  
requirement for supporting this eventuality as a consequence of  
supporting the outbound extension, could be added to the Outbound spec?

--
Dean

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


From sip-bounces@ietf.org  Sun Oct 19 10:46:27 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C2CA63A682F;
	Sun, 19 Oct 2008 10:46:27 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7617D3A680A
	for <sip@core3.amsl.com>; Sun, 19 Oct 2008 10:46:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.609
X-Spam-Level: 
X-Spam-Status: No, score=-2.609 tagged_above=-999 required=5
	tests=[AWL=-0.010, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id eWVOSKIUoiRk for <sip@core3.amsl.com>;
	Sun, 19 Oct 2008 10:46:25 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 966713A67B2
	for <sip@ietf.org>; Sun, 19 Oct 2008 10:46:25 -0700 (PDT)
Received: from [192.168.15.100] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9JHlQST005059
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Sun, 19 Oct 2008 12:47:28 -0500
Message-Id: <2F1FBD97-85C3-482C-996E-5D5B5BCC3B9D@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: "Orsic, Milo (Milo)" <orsic@ALCATEL-LUCENT.COM>
In-Reply-To: <1FD3C0CCB36AAA4AAAB874C3898C0B2701AD706B@ILEXC2U03.ndc.lucent.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sun, 19 Oct 2008 12:47:21 -0500
References: <C2FE0C2E-4EDA-4CCD-AAA1-D1122654665C@softarmor.com><48F8C97C.6010603@cisco.com><72946674-BEAB-4E2B-87B7-543DD13CA0B7@softarmor.com><48F932D1.3070401@cisco.com><A8D4EED1-4C7A-447E-AA1B-F077EB03B434@softarmor.com>
	<48F9F7F0.2020705@cisco.com>
	<1FD3C0CCB36AAA4AAAB874C3898C0B2701AD706B@ILEXC2U03.ndc.lucent.com>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] Outbound and mid-dialog requests with GRUU
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 18, 2008, at 12:17 PM, Orsic, Milo (Milo) wrote:

> Hi Dean,
> Pertaining to Paul's posting below:
> ------------------------------
> Well, the multiple flows are there for redundancy, right?
> If one of the flows fails, the whole point is that things should  
> continue. If the UA gets upset receiving in-dialog messages on a  
> different flow, then things aren't working right.
>
> Thanks,
> Paul
> ======================
>
> The UA will not get upset, since it may not receive the message.  
> Assume:
>
> 1. First registration between (UA's address) IP#1 via edge proxy#1  
> establishes the binding in the NAT/reflexive-firewall (and flow#1) -  
> as required by the draft.
>
> 2. Second registration between (UA's address) IP#2 via edge proxy#2  
> is used for redundancy, establishes the binding in the NAT/reflexive- 
> firewall (and flow#2) - as required by the draft.
>
> 3. Dialog is established using this flow#1 (and Route for this  
> dialog includes the edge proxy#1).
>
> There was never a registration between IP#2 via proxy#1. Hence, any  
> in-dialog request (destined for the UA) sent from edge proxy#1  
> (since it is in the Route) to IP#2 will be filtered by the NAT/ 
> reflexive-firewall.
>
> As you can see by this example, the second registration - as  
> required by the draft - doesn't really creates a redundant flow.
>
> IMHO, the draft should restrict the "redundancy" to a single contact  
> address (reached via different edge proxies).
>

Flow 1 goes from contact 1 through edge proxy 1, flow 2 goes from  
contact 2 through edge proxy 2. Both flows are attached to a single  
instance-id. The home proxy/registrar  keeps track of the keepalive  
status of each flow, and the keepalives keep the NAT binding open for  
each flow.

Presume flow 1 is in-use for a dialog, and the flow fails. The home  
proxy must then re-route the dialog to flow 2. This requires a fair  
bit of mechanism in the proxy, mechanism that is not completely  
defined in the outbound draft, but that can be readily inferred.

Another way to look at it is that Outbound routes to the "instance",  
not to the "contact".

I think there is a little bit of confusion about gruu. Without  
Outbound, the gruu is an alias for the conact. With Outbound, Is the  
gruu an alias for the contact or the instance ?  From a semantic- 
clarity model, I think gruu needs to be an alias for the instance.  
This however, is not completely clear to me in the current spec set.

--
Dean

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


From sip-bounces@ietf.org  Sun Oct 19 16:23:29 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C62B63A68E4;
	Sun, 19 Oct 2008 16:23:29 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2D1273A67B6
	for <sip@core3.amsl.com>; Sun, 19 Oct 2008 16:23:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id PSwwgr-5wc8p for <sip@core3.amsl.com>;
	Sun, 19 Oct 2008 16:23:27 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39])
	by core3.amsl.com (Postfix) with ESMTP id E0D4A3A6810
	for <sip@ietf.org>; Sun, 19 Oct 2008 16:23:26 -0700 (PDT)
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1])
	by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id m9JNOQCm028066;
	Sun, 19 Oct 2008 18:24:26 -0500 (CDT)
Received: from ILEXC2U03.ndc.lucent.com ([135.3.39.9]) by
	ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 19 Oct 2008 18:24:26 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 19 Oct 2008 18:24:24 -0500
Message-ID: <1FD3C0CCB36AAA4AAAB874C3898C0B2701AD70B2@ILEXC2U03.ndc.lucent.com>
In-Reply-To: <2F1FBD97-85C3-482C-996E-5D5B5BCC3B9D@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Outbound and mid-dialog requests with GRUU
Thread-Index: AckyEsFw0FEc+0EMRn6s9IIpN0bRnwAKgwxg
References: <C2FE0C2E-4EDA-4CCD-AAA1-D1122654665C@softarmor.com><48F8C97C.6010603@cisco.com><72946674-BEAB-4E2B-87B7-543DD13CA0B7@softarmor.com><48F932D1.3070401@cisco.com><A8D4EED1-4C7A-447E-AA1B-F077EB03B434@softarmor.com>
	<48F9F7F0.2020705@cisco.com>
	<1FD3C0CCB36AAA4AAAB874C3898C0B2701AD706B@ILEXC2U03.ndc.lucent.com>
	<2F1FBD97-85C3-482C-996E-5D5B5BCC3B9D@softarmor.com>
From: "Orsic, Milo \(Milo\)" <orsic@alcatel-lucent.com>
To: "Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 19 Oct 2008 23:24:26.0245 (UTC)
	FILETIME=[D3AE5350:01C93241]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: SIP IETF <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] Outbound and mid-dialog requests with GRUU
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1025291386=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1025291386==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C93241.D366FBE7"

This is a multi-part message in MIME format.

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

Hi Dean,
Thank you for your response. In the text below, I am not referring to
GRUU, i.e. I am referring to outbound. IMHO there are two cases, i.e.:

1. The initial dialog-forming request, destined to the UA. When this
request arrives at the authorative proxy, the outbound mechanism works
OK (i.e. there are two-or-more alternative routes to the target UA which
will be tried sequentially); and

2. The case when the dialog has been established. In this case the
far-end UA builds the Route header that it will include in its
subsequent in-dialog requests. Unfortunately, this Route header includes
the edge-proxy#1 and flow#1 (flow-token#1). The failure of the flow#1
can not be tried again via flow#2. For the the authorative proxy, to
re-write the Route header (to replace the edge-proxy#1 with
edge-proxy#2) for this request and all subsequent in-dialog requests
(destined for the UA) violate the SIP proxy function. Hence, I have my
doubts that the outbound "alternative flow mechanism" will work for the
in-dialog requests - as I have stated in my email.

Cheers,
Milo=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D=3D=3D=3D

-----Original Message-----
From: Dean Willis [mailto:dean.willis@softarmor.com]=20
Sent: Sunday, October 19, 2008 12:47 PM
To: Orsic, Milo (Milo)
Cc: Paul Kyzivat; SIP IETF
Subject: Re: [Sip] Outbound and mid-dialog requests with GRUU


On Oct 18, 2008, at 12:17 PM, Orsic, Milo (Milo) wrote:

> Hi Dean,
> Pertaining to Paul's posting below:
> ------------------------------
> Well, the multiple flows are there for redundancy, right?
> If one of the flows fails, the whole point is that things should=20
> continue. If the UA gets upset receiving in-dialog messages on a=20
> different flow, then things aren't working right.
>
> Thanks,
> Paul
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> The UA will not get upset, since it may not receive the message. =20
> Assume:
>
> 1. First registration between (UA's address) IP#1 via edge proxy#1=20
> establishes the binding in the NAT/reflexive-firewall (and flow#1) -=20
> as required by the draft.
>
> 2. Second registration between (UA's address) IP#2 via edge proxy#2 is

> used for redundancy, establishes the binding in the NAT/reflexive-=20
> firewall (and flow#2) - as required by the draft.
>
> 3. Dialog is established using this flow#1 (and Route for this dialog=20
> includes the edge proxy#1).
>
> There was never a registration between IP#2 via proxy#1. Hence, any=20
> in-dialog request (destined for the UA) sent from edge proxy#1 (since=20
> it is in the Route) to IP#2 will be filtered by the NAT/=20
> reflexive-firewall.
>
> As you can see by this example, the second registration - as required=20
> by the draft - doesn't really creates a redundant flow.
>
> IMHO, the draft should restrict the "redundancy" to a single contact=20
> address (reached via different edge proxies).
>

Flow 1 goes from contact 1 through edge proxy 1, flow 2 goes from =20
contact 2 through edge proxy 2. Both flows are attached to a single =20
instance-id. The home proxy/registrar  keeps track of the keepalive =20
status of each flow, and the keepalives keep the NAT binding open for =20
each flow.

Presume flow 1 is in-use for a dialog, and the flow fails. The home =20
proxy must then re-route the dialog to flow 2. This requires a fair =20
bit of mechanism in the proxy, mechanism that is not completely =20
defined in the outbound draft, but that can be readily inferred.

Another way to look at it is that Outbound routes to the "instance", =20
not to the "contact".

I think there is a little bit of confusion about gruu. Without =20
Outbound, the gruu is an alias for the conact. With Outbound, Is the =20
gruu an alias for the contact or the instance ?  From a semantic-=20
clarity model, I think gruu needs to be an alias for the instance. =20
This however, is not completely clear to me in the current spec set.

--
Dean


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7651.59">
<TITLE>RE: [Sip] Outbound and mid-dialog requests with GRUU</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman">Hi Dean,</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman">Thank you for your response. In the text below, I am not =
referring to GRUU, i.e. I am referring to outbound. IMHO there are two =
cases, i.e.:</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman">1. The initial dialog-forming request, destined to the UA. =
When this request arrives at the authorative<U> proxy</U>, the outbound =
mechanism works OK (i.e. there are two-or-more alternative routes to the =
target UA which will be tried sequentially); and</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman">2. The case when the dialog has been established. In this =
case the far-end UA builds the Route header that it will include in its =
subsequent in-dialog requests. Unfortunately, this Route header includes =
the edge-proxy#1 and flow#1 (flow-token#1). The failure of the flow#1 =
can not be tried again via flow#2. For the the authorative</FONT><U> =
<FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times New =
Roman">proxy,</FONT></U><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman"> to re-write the Route header (to replace the edge-proxy#1 =
with edge-proxy#2) for this request and all subsequent in-dialog =
requests (destined for the UA) violate the SIP</FONT><U><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times New Roman"> =
proxy</FONT></U><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times New =
Roman"> function. Hence, I have my doubts that the outbound =
&quot;alternative flow mechanism&quot; will work for the in-dialog =
requests - as I have stated in my email.</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman">Cheers,</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman">Milo</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial"> =
</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">-----Original =
Message-----</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">From: Dean Willis =
[</FONT></SPAN><A HREF=3D"mailto:dean.willis@softarmor.com"><SPAN =
LANG=3D"en-us"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">mailto:dean.willis@softarmor.com</FONT></U></SPAN></A><SPA=
N LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">] </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Sent: Sunday, =
October 19, 2008 12:47 PM</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">To: Orsic, Milo =
(Milo)</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Cc: Paul Kyzivat; =
SIP IETF</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Subject: Re: =
[Sip] Outbound and mid-dialog requests with GRUU</FONT></SPAN>
</P>
<BR>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">On Oct 18, 2008, =
at 12:17 PM, Orsic, Milo (Milo) wrote:</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; Hi =
Dean,</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; Pertaining =
to Paul's posting below:</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; =
------------------------------</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; Well, the =
multiple flows are there for redundancy, right?</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; If one of =
the flows fails, the whole point is that things should </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; continue. If =
the UA gets upset receiving in-dialog messages on a </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; different =
flow, then things aren't working right.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; =
Thanks,</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; =
Paul</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>=
</SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; The UA will =
not get upset, since it may not receive the message.&nbsp; =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; =
Assume:</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; 1. First =
registration between (UA's address) IP#1 via edge proxy#1 </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; establishes =
the binding in the NAT/reflexive-firewall (and flow#1) - </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; as required =
by the draft.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; 2. Second =
registration between (UA's address) IP#2 via edge proxy#2 is =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; used for =
redundancy, establishes the binding in the NAT/reflexive- </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; firewall =
(and flow#2) - as required by the draft.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; 3. Dialog is =
established using this flow#1 (and Route for this dialog </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; includes the =
edge proxy#1).</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; There was =
never a registration between IP#2 via proxy#1. Hence, any </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; in-dialog =
request (destined for the UA) sent from edge proxy#1 (since =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; it is in the =
Route) to IP#2 will be filtered by the NAT/ </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; =
reflexive-firewall.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; As you can =
see by this example, the second registration - as required =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; by the draft =
- doesn't really creates a redundant flow.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; IMHO, the =
draft should restrict the &quot;redundancy&quot; to a single contact =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; address =
(reached via different edge proxies).</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Flow 1 goes from =
contact 1 through edge proxy 1, flow 2 goes from&nbsp; </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">contact 2 through =
edge proxy 2. Both flows are attached to a single&nbsp; </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">instance-id. The =
home proxy/registrar&nbsp; keeps track of the keepalive&nbsp; =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">status of each =
flow, and the keepalives keep the NAT binding open for&nbsp; =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">each =
flow.</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Presume flow 1 is =
in-use for a dialog, and the flow fails. The home&nbsp; </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">proxy must then =
re-route the dialog to flow 2. This requires a fair&nbsp; </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">bit of mechanism =
in the proxy, mechanism that is not completely&nbsp; </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">defined in the =
outbound draft, but that can be readily inferred.</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Another way to =
look at it is that Outbound routes to the &quot;instance&quot;,&nbsp; =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">not to the =
&quot;contact&quot;.</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">I think there is a =
little bit of confusion about gruu. Without&nbsp; </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Outbound, the =
gruu is an alias for the conact. With Outbound, Is the&nbsp; =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">gruu an alias for =
the contact or the instance ?&nbsp; From a semantic- </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">clarity model, I =
think gruu needs to be an alias for the instance.&nbsp; </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">This however, is =
not completely clear to me in the current spec set.</FONT></SPAN>
</P>

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

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Dean</FONT></SPAN>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C93241.D366FBE7--

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

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


From sip-bounces@ietf.org  Sun Oct 19 19:51:02 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2BD8E3A6803;
	Sun, 19 Oct 2008 19:51:02 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9A71E3A68C0
	for <sip@core3.amsl.com>; Sun, 19 Oct 2008 19:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.569
X-Spam-Level: 
X-Spam-Status: No, score=-3.569 tagged_above=-999 required=5 tests=[AWL=0.030, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8QLhcy35hGw9 for <sip@core3.amsl.com>;
	Sun, 19 Oct 2008 19:51:00 -0700 (PDT)
Received: from TheWorld.com (pcls1.std.com [192.74.137.141])
	by core3.amsl.com (Postfix) with ESMTP id D4C6F3A6803
	for <sip@ietf.org>; Sun, 19 Oct 2008 19:50:59 -0700 (PDT)
Received: from shell.TheWorld.com (IDENT:105@shell01.theworld.com
	[192.74.137.71])
	by TheWorld.com (8.13.6/8.13.6) with ESMTP id m9K2oljc007561
	for <sip@ietf.org>; Sun, 19 Oct 2008 22:50:49 -0400
Received: from shell01.TheWorld.com (localhost [127.0.0.1])
	by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id m9K2oicD50195393
	for <sip@ietf.org>; Sun, 19 Oct 2008 22:50:47 -0400 (EDT)
Received: (from worley@localhost)
	by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id m9K2oifX50014113;
	Sun, 19 Oct 2008 22:50:44 -0400 (EDT)
Date: Sun, 19 Oct 2008 22:50:44 -0400 (EDT)
Message-Id: <200810200250.m9K2oifX50014113@shell01.TheWorld.com>
To: sip@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <BF4D24CF-D537-4476-87D2-8E30B8462B95@softarmor.com>
	(dean.willis@softarmor.com)
References: <BF4D24CF-D537-4476-87D2-8E30B8462B95@softarmor.com>
Subject: Re: [Sip] So where are we at with WGLC of
	draft-ietf-sip-body-handling?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

   From: Dean Willis <dean.willis@softarmor.com>

   There was a lot of discussion around the first of the month.

   Where are we now?

There is an open discussion point on the precise semantics of
'required' -- in the SIP context, it is probably more convenient to
mean "required for processing of the containing body part", but in the
e-mail gateway context, it is used to mean "required for the overall
message to be processed".  (The two are equivalent for non-nested
multiparts.)

My elaborate algorithm is, IMHO, a direct expression of the rules in
the I-D, although I've probably added some "it could only mean this"
assumptions which should be made explicit.  Whether the algorithm
itself is given in the I-D is a presentation issue.

If the algorithm it too complex to implement, we must simplify the
I-D.

I think we should make some statement that multipart/related should
not be used unless it is "protected" by some extension-requirement
that ensures the recipient can process multipart/related.

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


From sip-bounces@ietf.org  Sun Oct 19 22:54:38 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 68DEE3A6A05;
	Sun, 19 Oct 2008 22:54:38 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E08F13A68DA
	for <sip@core3.amsl.com>; Sun, 19 Oct 2008 22:54:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.2
X-Spam-Level: 
X-Spam-Status: No, score=-6.2 tagged_above=-999 required=5 tests=[AWL=0.049,
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id bemIaM5uFh8C for <sip@core3.amsl.com>;
	Sun, 19 Oct 2008 22:54:36 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id D80A83A6A05
	for <sip@ietf.org>; Sun, 19 Oct 2008 22:54:35 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	DA5BD2065B; Mon, 20 Oct 2008 07:55:44 +0200 (CEST)
X-AuditID: c1b4fb3e-aae89bb000007a96-34-48fc1d60989c
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	BC550200B6; Mon, 20 Oct 2008 07:55:44 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 07:55:44 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 20 Oct 2008 07:55:43 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se>
In-Reply-To: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Stupid question on flow use in outbound
Thread-Index: AckwalpNrXwgtdvJS02TBwUFX2qSZwCDNpgQ
References: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Dean Willis" <dean.willis@softarmor.com>,
	"SIP IETF" <sip@ietf.org>
X-OriginalArrivalTime: 20 Oct 2008 05:55:44.0369 (UTC)
	FILETIME=[7DBBBE10:01C93278]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] Stupid question on flow use in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>Assume Bob's UA is using outbound and is registered with two flows.  
>Both flows use the same instance-id. The first flow goes through edge-
proxy 1 and has reg-id 1. The second flow goes through proxy 2 and has
reg-id 2.
>
>Both flows are "live" from a keepalive perspective.
>
>Alice calls Bob.
>
>Which flow gets exercised?
>
>Where in Outbound is this described? If it is not in Outbound, is it
described somewhere else? If it is simply left-to-the-implementation,
does this need to be explained somewhere?

I guess it is (for good or bad) left-to-the-implementation.

HOWEVER, one thing which has been discussed, and which I think we SHOULD
say something about, is whether it's allowed to use a different set of
user capabilities for each flow.

Personally I think it would be useful. For example, I could indicate
that I want to receive incoming video calls over my super-fast-broadband
access, instead of my slow jungle-drum access.

I don't think we would need very much text for this either. Maybe a note
saying something like:

"NOTE: A user MAY register different set of user capabilities (using the
mechanism in [ref-to-RFC3840] on each flow, if the user wishes the
registrar to choose a particular flow based on caller preferences
[ref-to-RFC3841]."

...or something like that.

Regards,

Christer

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


From sip-bounces@ietf.org  Sun Oct 19 23:38:05 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E96F73A68FD;
	Sun, 19 Oct 2008 23:38:04 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7B60B3A6883
	for <sip@core3.amsl.com>; Sun, 19 Oct 2008 23:38:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.201
X-Spam-Level: 
X-Spam-Status: No, score=-6.201 tagged_above=-999 required=5 tests=[AWL=0.048, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0NS61rdZuQY1 for <sip@core3.amsl.com>;
	Sun, 19 Oct 2008 23:38:02 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 64C4E3A68FD
	for <sip@ietf.org>; Sun, 19 Oct 2008 23:38:01 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	CA02921343; Mon, 20 Oct 2008 08:39:09 +0200 (CEST)
X-AuditID: c1b4fb3e-a7e83bb000007a96-5e-48fc27624e35
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	446A6203D5; Mon, 20 Oct 2008 08:38:26 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 08:38:09 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 20 Oct 2008 08:38:08 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF087C4763@esealmw113.eemea.ericsson.se>
In-Reply-To: <5CFE7D5D-BCA0-49A7-A58C-1291A8F416F6@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Question on non-outbound registrations in outbound
Thread-Index: AckwZbrDEsvK9OABRl6TGguzpKj+rgCGGbYA
References: <5CFE7D5D-BCA0-49A7-A58C-1291A8F416F6@softarmor.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Dean Willis" <dean.willis@softarmor.com>,
	"SIP IETF" <sip@ietf.org>
X-OriginalArrivalTime: 20 Oct 2008 06:38:09.0353 (UTC)
	FILETIME=[6AA97B90:01C9327E]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] Question on non-outbound registrations in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi Dean,

How would the keep-alives work for 3rd party registration? How would I
know that you have registered me, and that I now have to send
keep-alives (and where I would have to send the keep-alives)? 

And, how would you know if the flow that you have registered for me
fails, in which case you should establish a new flow for me?

Regards,

Christer


-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Dean Willis
Sent: 17. lokakuuta 2008 17:36
To: SIP IETF
Subject: [Sip] Question on non-outbound registrations in outbound

The current draft says:
4.2.3.  Non Outbound Registrations

    In an initial registration, a User Agent MUST NOT include a reg-id
    header parameter in the Contact header field if the registering UA
is
    not the same instance as the UA referred to by the target Contact
    header field.  (This practice is occasionally used to install
    forwarding policy into registrars.)

    A UAC also MUST NOT include an instance-id feature taf or reg-id
    Contact header field parameter in a request to un-register all
    Contacts (a single Contact header field value with the value of
"*").

This strikes me as odd in several ways.

The reg-id lets us know "which registration we are talking about". The
instance-id lets us know "which specific UA-appearance we are talking
about".
So for a 3rd-party registration, it might be useful to have reg-id or
instance-id values. Assume for example a voice-mail server that
registers a low q-value contact for an AOR, so that calls will
eventually reach it in a no-answer scenario. Withdrawing just those
specific registrations would seem to require a selection mechanism from
the set of registrations, and reg-id would appear to satisfy this need.


In a different use case, assume a 3rd party registration is used to
install forwarding policy. The use of an instance-id in such a
registration would seem to allow the forwarding policy to target one
specific instance of the set of contacts registered to the target. In
other words, not "forward the call to sip:bob@example.com", but "forward
the call to sip:bob@example.com's cell phone".

Now it's entirely possible that neither of these scenarios actually
work. But I don't see in the discussion of outbound anything about WHY
they wouldn't work, which means that the requirements language (the MUST
in outbound) is unsupported. I don't like unsupported requirements in a
specification.
--
Dean

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


From sip-bounces@ietf.org  Mon Oct 20 05:20:17 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 25B873A6A1D;
	Mon, 20 Oct 2008 05:20:17 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C39563A692C
	for <sip@core3.amsl.com>; Mon, 20 Oct 2008 05:20:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zdg24ZvbtFTx for <sip@core3.amsl.com>;
	Mon, 20 Oct 2008 05:20:14 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 8C9863A681C
	for <sip@ietf.org>; Mon, 20 Oct 2008 05:20:14 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,451,1220227200"; d="scan'208";a="24946290"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 20 Oct 2008 12:21:25 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9KCLP9F010548; 
	Mon, 20 Oct 2008 08:21:25 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9KCLPS9026574;
	Mon, 20 Oct 2008 12:21:25 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 08:21:25 -0400
Received: from [10.86.251.214] ([10.86.251.214]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 08:21:25 -0400
Message-ID: <48FC77C4.2090502@cisco.com>
Date: Mon, 20 Oct 2008 08:21:24 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <5CFE7D5D-BCA0-49A7-A58C-1291A8F416F6@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF087C4763@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF087C4763@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 20 Oct 2008 12:21:25.0111 (UTC)
	FILETIME=[5EB0C070:01C932AE]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3992; t=1224505285;
	x=1225369285; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Question=20on=20non-outbound=20
	registrations=20in=20outbound |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=pAjl/pgRxUwRgqXdXJ2A+tKQfiiYi1rrTYI2WB+tJ94=;
	b=CLnOdWkiGdRa7IZ+Ns70h1qfol4KhKqaL6Ixq9XySfYn5UrzkuERTWQKUO
	rDwn51uEgO4g4Zxf1grTrnmM/kOaz8DA7j9udldFpKq1RPZTqkntAvFQcaZ2
	PllDCtT5WJ;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Question on non-outbound registrations in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Can we be careful about terminology here?
I don't think this has anything to do with third party registration.
Third party registration is when identity of the UA performing the 
registration differs from the To-URI of the REGISTER request.

I think what this was intended to be about is when a Contact address 
used in a REGISTER terminates at a different place from the device 
sending the REGISTER request.

Now I guess the Contact address itself is irrelevant in outbound, to the 
extent that its never resolved via 3263. We normally expect it to be 
consistent with the source of the register request, but does it really 
matter?

	Thanks,
	Paul

Christer Holmberg wrote:
> Hi Dean,
> 
> How would the keep-alives work for 3rd party registration? How would I
> know that you have registered me, and that I now have to send
> keep-alives (and where I would have to send the keep-alives)? 
> 
> And, how would you know if the flow that you have registered for me
> fails, in which case you should establish a new flow for me?
> 
> Regards,
> 
> Christer
> 
> 
> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
> Dean Willis
> Sent: 17. lokakuuta 2008 17:36
> To: SIP IETF
> Subject: [Sip] Question on non-outbound registrations in outbound
> 
> The current draft says:
> 4.2.3.  Non Outbound Registrations
> 
>     In an initial registration, a User Agent MUST NOT include a reg-id
>     header parameter in the Contact header field if the registering UA
> is
>     not the same instance as the UA referred to by the target Contact
>     header field.  (This practice is occasionally used to install
>     forwarding policy into registrars.)
> 
>     A UAC also MUST NOT include an instance-id feature taf or reg-id
>     Contact header field parameter in a request to un-register all
>     Contacts (a single Contact header field value with the value of
> "*").
> 
> This strikes me as odd in several ways.
> 
> The reg-id lets us know "which registration we are talking about". The
> instance-id lets us know "which specific UA-appearance we are talking
> about".
> So for a 3rd-party registration, it might be useful to have reg-id or
> instance-id values. Assume for example a voice-mail server that
> registers a low q-value contact for an AOR, so that calls will
> eventually reach it in a no-answer scenario. Withdrawing just those
> specific registrations would seem to require a selection mechanism from
> the set of registrations, and reg-id would appear to satisfy this need.
> 
> 
> In a different use case, assume a 3rd party registration is used to
> install forwarding policy. The use of an instance-id in such a
> registration would seem to allow the forwarding policy to target one
> specific instance of the set of contacts registered to the target. In
> other words, not "forward the call to sip:bob@example.com", but "forward
> the call to sip:bob@example.com's cell phone".
> 
> Now it's entirely possible that neither of these scenarios actually
> work. But I don't see in the discussion of outbound anything about WHY
> they wouldn't work, which means that the requirements language (the MUST
> in outbound) is unsupported. I don't like unsupported requirements in a
> specification.
> --
> Dean
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use
> sip-implementors@cs.columbia.edu for questions on current sip Use
> sipping@ietf.org for new developments on the application of sip
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct 20 05:23:15 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 00B713A6A5E;
	Mon, 20 Oct 2008 05:23:15 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D043C3A6A55
	for <sip@core3.amsl.com>; Mon, 20 Oct 2008 05:23:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.202
X-Spam-Level: 
X-Spam-Status: No, score=-6.202 tagged_above=-999 required=5 tests=[AWL=0.047, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nvBrjFmZPoRU for <sip@core3.amsl.com>;
	Mon, 20 Oct 2008 05:23:13 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id A3F433A692C
	for <sip@ietf.org>; Mon, 20 Oct 2008 05:23:12 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	DED1820C64; Mon, 20 Oct 2008 14:23:53 +0200 (CEST)
X-AuditID: c1b4fb3c-ac0cabb0000015b5-73-48fc7859ba01
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	C614A20E12; Mon, 20 Oct 2008 14:23:53 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 14:23:53 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 20 Oct 2008 14:23:52 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF087FEF7B@esealmw113.eemea.ericsson.se>
In-Reply-To: <48FC77C4.2090502@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Question on non-outbound registrations in outbound
Thread-Index: AckyrmHBJ09BpRnkQCuY0e67aQJmUAAADmCg
References: <5CFE7D5D-BCA0-49A7-A58C-1291A8F416F6@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF087C4763@esealmw113.eemea.ericsson.se>
	<48FC77C4.2090502@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 20 Oct 2008 12:23:53.0228 (UTC)
	FILETIME=[B6F99CC0:01C932AE]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Question on non-outbound registrations in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>Can we be careful about terminology here?
>I don't think this has anything to do with third party registration.
>Third party registration is when identity of the UA performing the
registration differs from the To-URI of the REGISTER request.
>
>I think what this was intended to be about is when a Contact address
used in a REGISTER terminates at a different place from the device
sending the REGISTER request.
>
>Now I guess the Contact address itself is irrelevant in outbound, to
the extent that its never resolved via 3263. We normally expect it to be
consistent with the source of the register request, 
>but does it really matter?

I don't think so. Incoming requests will be sent to where the REGISTER
came from, no matter what's in the Contact.

Regards,

Christer





Christer Holmberg wrote:
> Hi Dean,
> 
> How would the keep-alives work for 3rd party registration? How would I

> know that you have registered me, and that I now have to send 
> keep-alives (and where I would have to send the keep-alives)?
> 
> And, how would you know if the flow that you have registered for me 
> fails, in which case you should establish a new flow for me?
> 
> Regards,
> 
> Christer
> 
> 
> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of 
> Dean Willis
> Sent: 17. lokakuuta 2008 17:36
> To: SIP IETF
> Subject: [Sip] Question on non-outbound registrations in outbound
> 
> The current draft says:
> 4.2.3.  Non Outbound Registrations
> 
>     In an initial registration, a User Agent MUST NOT include a reg-id
>     header parameter in the Contact header field if the registering UA

> is
>     not the same instance as the UA referred to by the target Contact
>     header field.  (This practice is occasionally used to install
>     forwarding policy into registrars.)
> 
>     A UAC also MUST NOT include an instance-id feature taf or reg-id
>     Contact header field parameter in a request to un-register all
>     Contacts (a single Contact header field value with the value of 
> "*").
> 
> This strikes me as odd in several ways.
> 
> The reg-id lets us know "which registration we are talking about". The

> instance-id lets us know "which specific UA-appearance we are talking 
> about".
> So for a 3rd-party registration, it might be useful to have reg-id or 
> instance-id values. Assume for example a voice-mail server that 
> registers a low q-value contact for an AOR, so that calls will 
> eventually reach it in a no-answer scenario. Withdrawing just those 
> specific registrations would seem to require a selection mechanism 
> from the set of registrations, and reg-id would appear to satisfy this
need.
> 
> 
> In a different use case, assume a 3rd party registration is used to 
> install forwarding policy. The use of an instance-id in such a 
> registration would seem to allow the forwarding policy to target one 
> specific instance of the set of contacts registered to the target. In 
> other words, not "forward the call to sip:bob@example.com", but 
> "forward the call to sip:bob@example.com's cell phone".
> 
> Now it's entirely possible that neither of these scenarios actually 
> work. But I don't see in the discussion of outbound anything about WHY

> they wouldn't work, which means that the requirements language (the 
> MUST in outbound) is unsupported. I don't like unsupported 
> requirements in a specification.
> --
> Dean
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors@cs.columbia.edu for questions on current sip Use 
> sipping@ietf.org for new developments on the application of sip 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors@cs.columbia.edu for questions on current sip Use 
> sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct 20 05:38:07 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1FDA428C0F2;
	Mon, 20 Oct 2008 05:38:07 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CAAC03A6AB1
	for <sip@core3.amsl.com>; Mon, 20 Oct 2008 05:38:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.202
X-Spam-Level: 
X-Spam-Status: No, score=-6.202 tagged_above=-999 required=5 tests=[AWL=0.046, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id TJKHX5hMGzuW for <sip@core3.amsl.com>;
	Mon, 20 Oct 2008 05:38:05 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id B23EB3A6A2D
	for <sip@ietf.org>; Mon, 20 Oct 2008 05:38:04 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	3F31320C78 for <sip@ietf.org>; Mon, 20 Oct 2008 14:39:08 +0200 (CEST)
X-AuditID: c1b4fb3c-ab8c9bb0000015b5-a5-48fc7bec0be8
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	265E420C36 for <sip@ietf.org>; Mon, 20 Oct 2008 14:39:08 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 14:39:07 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 20 Oct 2008 14:39:07 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF087FF086@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New version (-02) of draft-ietf-sip-199
Thread-Index: AckysNfJpc9q0xPEQDSKY8KjQKktBg==
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "SIP IETF" <sip@ietf.org>
X-OriginalArrivalTime: 20 Oct 2008 12:39:07.0876 (UTC)
	FILETIME=[D825D240:01C932B0]
X-Brightmail-Tracker: AAAAAA==
Subject: [Sip] New version (-02) of draft-ietf-sip-199
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1400578070=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1400578070==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C932B0.D7E25B6C"

This is a multi-part message in MIME format.

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


Hi,

I've submitted a new version of the 199 draft.=20

I tried to take all comments into consideration, and I appologize if I
have forgotten something.

The main open issue at the moment is when/if a UAS would send a 199
response to terminate an early dialog.

One idea that has been presented would be to define an 199 indicator,
which a forking proxy can insert to indicate to the UASs that it
supports 199, so that the UASs don't have to send 199. Of course, this
works only if the forking proxy closest to the UASs supports 199.

The document can also be found at:

http://users.piuha.net/cholmber/drafts/draft-ietf-sip-199-02.txt

Regards,

Christer

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>New version (-02) of draft-ietf-sip-199</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>

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

<P><FONT SIZE=3D2 FACE=3D"Arial">I've submitted a new version of the 199 =
draft. </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I tried to take all comments into =
consideration, and I appologize if I have forgotten something.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The main open issue at the moment is =
when/if a UAS would send a 199 response to terminate an early =
dialog.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">One idea that has been presented would =
be to define an 199 indicator, which a forking proxy can insert to =
indicate to the UASs that it supports 199, so that the UASs don't have =
to send 199. Of course, this works only if the forking proxy closest to =
the UASs supports 199.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The document can also be found =
at:</FONT>
</P>

<P><A =
HREF=3D"http://users.piuha.net/cholmber/drafts/draft-ietf-sip-199-02.txt"=
><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">http://users.piuha.net/cholmber/drafts/draft-ietf-sip-199-=
02.txt</FONT></U></A>
</P>

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

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

</BODY>
</HTML>
------_=_NextPart_001_01C932B0.D7E25B6C--

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

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


From sip-bounces@ietf.org  Mon Oct 20 05:45:03 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 559AF3A68CE;
	Mon, 20 Oct 2008 05:45:03 -0700 (PDT)
X-Original-To: sip@ietf.org
Delivered-To: sip@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 0F7A23A6891; Mon, 20 Oct 2008 05:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081020124502.0F7A23A6891@core3.amsl.com>
Date: Mon, 20 Oct 2008 05:45:02 -0700 (PDT)
Cc: sip@ietf.org
Subject: [Sip] I-D Action:draft-ietf-sip-199-02.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--NextPart

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


	Title           : Response Code for Indication of Terminated Dialog
	Author(s)       : C. Holmberg
	Filename        : draft-ietf-sip-199-02.txt
	Pages           : 11
	Date            : 2008-10-20

This specification defines a new SIP response code, 199 Early Dialog
Terminated, which a SIP entity can use to indicate upstream that an
early dialog has been terminated.  The response code can be used by a
SIP entity to indicate to the UAC that an early dialog has been
terminated, before a final response is sent to the UAC.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sip-199-02.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-sip-199-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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


From sip-bounces@ietf.org  Mon Oct 20 06:33:45 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 806B63A69D7;
	Mon, 20 Oct 2008 06:33:45 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CDE7C3A699A
	for <sip@core3.amsl.com>; Mon, 20 Oct 2008 06:33:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.51
X-Spam-Level: 
X-Spam-Status: No, score=-6.51 tagged_above=-999 required=5 tests=[AWL=0.089, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vIEua1W6Pp-V for <sip@core3.amsl.com>;
	Mon, 20 Oct 2008 06:33:39 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 72B103A68E6
	for <sip@ietf.org>; Mon, 20 Oct 2008 06:33:39 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,451,1220227200"; d="scan'208";a="24994152"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 20 Oct 2008 13:34:48 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9KDYm3L016568; 
	Mon, 20 Oct 2008 09:34:48 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9KDYmAe018199;
	Mon, 20 Oct 2008 13:34:48 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 09:34:48 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 09:34:48 -0400
Message-ID: <48FC88F7.1050501@cisco.com>
Date: Mon, 20 Oct 2008 09:34:47 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <5CFE7D5D-BCA0-49A7-A58C-1291A8F416F6@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF087C4763@esealmw113.eemea.ericsson.se>	<48FC77C4.2090502@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF087FEF7B@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF087FEF7B@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 20 Oct 2008 13:34:48.0157 (UTC)
	FILETIME=[9F1C40D0:01C932B8]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4860; t=1224509688;
	x=1225373688; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Question=20on=20non-outbound=20
	registrations=20in=20outbound |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=gs7COEksVMp4JmxsMtuM4FCp+vpgIMVJUEYdqDOKT2Q=;
	b=drml5bM3oui112l4Ip6m6qsn2Od5u69HRX21O9qoKLZX6Ekt+zO+fTUV8b
	2SIF7fYVm3U43bUMDcdRc6PeXV8zOppog5Igd2LBUn+xI2eMW6spI901K0Rr
	LQP2Ha3KAB;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Question on non-outbound registrations in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Perhaps it would be better if outbound specified a special form of 
contact address that was clearly bogus for routing in its own right, to 
avoid any confusion that its value is significant when outbound is used.

	Thanks,
	Paul

Christer Holmberg wrote:
> Hi, 
> 
>> Can we be careful about terminology here?
>> I don't think this has anything to do with third party registration.
>> Third party registration is when identity of the UA performing the
> registration differs from the To-URI of the REGISTER request.
>> I think what this was intended to be about is when a Contact address
> used in a REGISTER terminates at a different place from the device
> sending the REGISTER request.
>> Now I guess the Contact address itself is irrelevant in outbound, to
> the extent that its never resolved via 3263. We normally expect it to be
> consistent with the source of the register request, 
>> but does it really matter?
> 
> I don't think so. Incoming requests will be sent to where the REGISTER
> came from, no matter what's in the Contact.
> 
> Regards,
> 
> Christer
> 
> 
> 
> 
> 
> Christer Holmberg wrote:
>> Hi Dean,
>>
>> How would the keep-alives work for 3rd party registration? How would I
> 
>> know that you have registered me, and that I now have to send 
>> keep-alives (and where I would have to send the keep-alives)?
>>
>> And, how would you know if the flow that you have registered for me 
>> fails, in which case you should establish a new flow for me?
>>
>> Regards,
>>
>> Christer
>>
>>
>> -----Original Message-----
>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of 
>> Dean Willis
>> Sent: 17. lokakuuta 2008 17:36
>> To: SIP IETF
>> Subject: [Sip] Question on non-outbound registrations in outbound
>>
>> The current draft says:
>> 4.2.3.  Non Outbound Registrations
>>
>>     In an initial registration, a User Agent MUST NOT include a reg-id
>>     header parameter in the Contact header field if the registering UA
> 
>> is
>>     not the same instance as the UA referred to by the target Contact
>>     header field.  (This practice is occasionally used to install
>>     forwarding policy into registrars.)
>>
>>     A UAC also MUST NOT include an instance-id feature taf or reg-id
>>     Contact header field parameter in a request to un-register all
>>     Contacts (a single Contact header field value with the value of 
>> "*").
>>
>> This strikes me as odd in several ways.
>>
>> The reg-id lets us know "which registration we are talking about". The
> 
>> instance-id lets us know "which specific UA-appearance we are talking 
>> about".
>> So for a 3rd-party registration, it might be useful to have reg-id or 
>> instance-id values. Assume for example a voice-mail server that 
>> registers a low q-value contact for an AOR, so that calls will 
>> eventually reach it in a no-answer scenario. Withdrawing just those 
>> specific registrations would seem to require a selection mechanism 
>> from the set of registrations, and reg-id would appear to satisfy this
> need.
>>
>> In a different use case, assume a 3rd party registration is used to 
>> install forwarding policy. The use of an instance-id in such a 
>> registration would seem to allow the forwarding policy to target one 
>> specific instance of the set of contacts registered to the target. In 
>> other words, not "forward the call to sip:bob@example.com", but 
>> "forward the call to sip:bob@example.com's cell phone".
>>
>> Now it's entirely possible that neither of these scenarios actually 
>> work. But I don't see in the discussion of outbound anything about WHY
> 
>> they wouldn't work, which means that the requirements language (the 
>> MUST in outbound) is unsupported. I don't like unsupported 
>> requirements in a specification.
>> --
>> Dean
>>
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol Use 
>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>> sipping@ietf.org for new developments on the application of sip 
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol Use 
>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>> sipping@ietf.org for new developments on the application of sip
>>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct 20 07:36:49 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5E8793A692E;
	Mon, 20 Oct 2008 07:36:49 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BE0773A68D0
	for <sip@core3.amsl.com>; Mon, 20 Oct 2008 07:36:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XLtfslcjPvv5 for <sip@core3.amsl.com>;
	Mon, 20 Oct 2008 07:36:46 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33])
	by core3.amsl.com (Postfix) with ESMTP id 7A0263A67A5
	for <sip@ietf.org>; Mon, 20 Oct 2008 07:36:46 -0700 (PDT)
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id m9KEcJw5010455;
	Mon, 20 Oct 2008 09:38:23 -0500 (CDT)
Received: from ILEXC2U03.ndc.lucent.com ([135.3.39.9]) by
	ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 09:37:27 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 20 Oct 2008 09:37:26 -0500
Message-ID: <1FD3C0CCB36AAA4AAAB874C3898C0B2701AD7249@ILEXC2U03.ndc.lucent.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Stupid question on flow use in outbound
Thread-Index: AckwalpNrXwgtdvJS02TBwUFX2qSZwCDNpgQABJq3lA=
References: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se>
From: "Orsic, Milo \(Milo\)" <orsic@alcatel-lucent.com>
To: "Christer Holmberg" <christer.holmberg@ericsson.com>,
	"SIP IETF" <sip@ietf.org>
X-OriginalArrivalTime: 20 Oct 2008 14:37:27.0767 (UTC)
	FILETIME=[60033670:01C932C1]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Subject: Re: [Sip] Stupid question on flow use in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1053946608=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1053946608==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C932C1.5FA17ED8"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C932C1.5FA17ED8
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Christer,
IMHO outbound should specifies "alternative paths". Here is what I mean
by "alternative paths".
=20
Assume that China Airline has two counters (contacts), one only English
speaking the other only Chinese spiking. It doesn't matter if you took
either the escalator or the elevator to the English speaking counter
(the elevator and escalator are alternatives paths).  However, if the
elevator gets you to English speaking counter and the escalator gets you
to Chinese speaking counter - they are not alternatives.=20
Hence, you have two choices, i.e. either
1. the two alternatives get you to the same counter, or=20
2. make the second counter also English speaking.
My choices is 1. (e.g. I don't want to be constrained that the
alternative contact addresses must be registered with the same feature
tags).=20

Milo

-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Christer Holmberg
Sent: Monday, October 20, 2008 12:56 AM
To: Dean Willis; SIP IETF
Subject: Re: [Sip] Stupid question on flow use in outbound


Hi,=20

>Assume Bob's UA is using outbound and is registered with two flows. =20
>Both flows use the same instance-id. The first flow goes through edge-
proxy 1 and has reg-id 1. The second flow goes through proxy 2 and has
reg-id 2.
>
>Both flows are "live" from a keepalive perspective.
>
>Alice calls Bob.
>
>Which flow gets exercised?
>
>Where in Outbound is this described? If it is not in Outbound, is it
described somewhere else? If it is simply left-to-the-implementation,
does this need to be explained somewhere?

I guess it is (for good or bad) left-to-the-implementation.

HOWEVER, one thing which has been discussed, and which I think we SHOULD
say something about, is whether it's allowed to use a different set of
user capabilities for each flow.

Personally I think it would be useful. For example, I could indicate
that I want to receive incoming video calls over my super-fast-broadband
access, instead of my slow jungle-drum access.

I don't think we would need very much text for this either. Maybe a note
saying something like:

"NOTE: A user MAY register different set of user capabilities (using the
mechanism in [ref-to-RFC3840] on each flow, if the user wishes the
registrar to choose a particular flow based on caller preferences
[ref-to-RFC3841]."

...or something like that.

Regards,

Christer

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

------_=_NextPart_001_01C932C1.5FA17ED8
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7651.59">
<TITLE>RE: [Sip] Stupid question on flow use in outbound</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman">Hi Christer,</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman">IMHO outbound should specifies &quot;alternative paths&quot;. =
Here is what I mean by &quot;alternative paths&quot;.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman">&nbsp;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman">Assume that China Airline has two counters (contacts), one =
only English speaking the other only Chinese spiking. It doesn't matter =
if you took either the escalator or the elevator to the English speaking =
counter (the elevator and escalator are alternatives paths).&nbsp; =
However, if the elevator gets you to English speaking counter and the =
escalator gets you to Chinese speaking counter - they are not =
alternatives. </FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman">Hence, you have two choices, i.e. either</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman">1. the two alternatives get you to the same counter, or =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman">2. make the second counter also English =
speaking.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman">My choices is 1. (e.g. I don't want to be constrained that =
the alternative contact addresses must be registered with the same =
feature tags). </FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman">Milo</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">-----Original =
Message-----</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">From: =
sip-bounces@ietf.org [</FONT></SPAN><A =
HREF=3D"mailto:sip-bounces@ietf.org"><SPAN LANG=3D"en-us"><U><FONT =
COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">mailto:sip-bounces@ietf.org</FONT></U></SPAN></A><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">] On Behalf Of Christer =
Holmberg</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Sent: Monday, =
October 20, 2008 12:56 AM</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">To: Dean Willis; =
SIP IETF</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Subject: Re: =
[Sip] Stupid question on flow use in outbound</FONT></SPAN>
</P>
<BR>

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

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;Assume Bob's =
UA is using outbound and is registered with two flows.&nbsp; =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;Both flows =
use the same instance-id. The first flow goes through =
edge-</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">proxy 1 and has =
reg-id 1. The second flow goes through proxy 2 and has reg-id =
2.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;Both flows =
are &quot;live&quot; from a keepalive perspective.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;Alice calls =
Bob.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;Which flow =
gets exercised?</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;Where in =
Outbound is this described? If it is not in Outbound, is =
it</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">described =
somewhere else? If it is simply left-to-the-implementation, does this =
need to be explained somewhere?</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">I guess it is (for =
good or bad) left-to-the-implementation.</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">HOWEVER, one thing =
which has been discussed, and which I think we SHOULD say something =
about, is whether it's allowed to use a different set of user =
capabilities for each flow.</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Personally I think =
it would be useful. For example, I could indicate that I want to receive =
incoming video calls over my super-fast-broadband access, instead of my =
slow jungle-drum access.</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">I don't think we =
would need very much text for this either. Maybe a note saying something =
like:</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&quot;NOTE: A user =
MAY register different set of user capabilities (using the mechanism in =
[ref-to-RFC3840] on each flow, if the user wishes the registrar to =
choose a particular flow based on caller preferences =
[ref-to-RFC3841].&quot;</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">...or something =
like that.</FONT></SPAN>
</P>

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

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

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">_______________________________________________</FONT></SP=
AN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Sip mailing =
list&nbsp; </FONT></SPAN><A =
HREF=3D"https://www.ietf.org/mailman/listinfo/sip"><SPAN =
LANG=3D"en-us"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">https://www.ietf.org/mailman/listinfo/sip</FONT></U></SPAN=
></A><SPAN LANG=3D"en-us"></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">This list is for =
NEW development of the core SIP Protocol Use =
sip-implementors@cs.columbia.edu for questions on current sip Use =
sipping@ietf.org for new developments on the application of =
sip</FONT></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C932C1.5FA17ED8--

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

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


From sip-bounces@ietf.org  Mon Oct 20 11:52:51 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3B48A3A69B3;
	Mon, 20 Oct 2008 11:52:51 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CB1C73A6A2A
	for <sip@core3.amsl.com>; Mon, 20 Oct 2008 11:52:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.203
X-Spam-Level: 
X-Spam-Status: No, score=-6.203 tagged_above=-999 required=5 tests=[AWL=0.046, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Do3pdZuh+fOA for <sip@core3.amsl.com>;
	Mon, 20 Oct 2008 11:52:48 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 87D2F3A68D0
	for <sip@ietf.org>; Mon, 20 Oct 2008 11:52:48 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	24B90208EE; Mon, 20 Oct 2008 20:53:58 +0200 (CEST)
X-AuditID: c1b4fb3c-b00d2bb0000015b5-a2-48fcd3c50ba9
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	F3657206BE; Mon, 20 Oct 2008 20:53:57 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 20:53:57 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 20 Oct 2008 20:50:14 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCF8F@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Question on non-outbound registrations in outbound
Thread-Index: AckyuKF27r4qdXk1S6at36HKABSgXQALA7g1
References: <5CFE7D5D-BCA0-49A7-A58C-1291A8F416F6@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF087C4763@esealmw113.eemea.ericsson.se>	<48FC77C4.2090502@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF087FEF7B@esealmw113.eemea.ericsson.se>
	<48FC88F7.1050501@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 20 Oct 2008 18:53:57.0347 (UTC)
	FILETIME=[34EAC330:01C932E5]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Question on non-outbound registrations in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi,
 
>Perhaps it would be better if outbound specified a special form of 
>contact address that was clearly bogus for routing in its own right, to 
>avoid any confusion that its value is significant when outbound is used.

When sending the REGISTER, the UAC doesn't know whether the registrar supports outbound in the first place, so whatever "special form" it used it must work also in those cases.

I guess it depends on if/how much the registrar cares about the contact, since it is going to route based on the Path.

Regards,

Christer





	Thanks,
	Paul

Christer Holmberg wrote:
> Hi, 
> 
>> Can we be careful about terminology here?
>> I don't think this has anything to do with third party registration.
>> Third party registration is when identity of the UA performing the
> registration differs from the To-URI of the REGISTER request.
>> I think what this was intended to be about is when a Contact address
> used in a REGISTER terminates at a different place from the device
> sending the REGISTER request.
>> Now I guess the Contact address itself is irrelevant in outbound, to
> the extent that its never resolved via 3263. We normally expect it to be
> consistent with the source of the register request, 
>> but does it really matter?
> 
> I don't think so. Incoming requests will be sent to where the REGISTER
> came from, no matter what's in the Contact.
> 
> Regards,
> 
> Christer
> 
> 
> 
> 
> 
> Christer Holmberg wrote:
>> Hi Dean,
>>
>> How would the keep-alives work for 3rd party registration? How would I
> 
>> know that you have registered me, and that I now have to send 
>> keep-alives (and where I would have to send the keep-alives)?
>>
>> And, how would you know if the flow that you have registered for me 
>> fails, in which case you should establish a new flow for me?
>>
>> Regards,
>>
>> Christer
>>
>>
>> -----Original Message-----
>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of 
>> Dean Willis
>> Sent: 17. lokakuuta 2008 17:36
>> To: SIP IETF
>> Subject: [Sip] Question on non-outbound registrations in outbound
>>
>> The current draft says:
>> 4.2.3.  Non Outbound Registrations
>>
>>     In an initial registration, a User Agent MUST NOT include a reg-id
>>     header parameter in the Contact header field if the registering UA
> 
>> is
>>     not the same instance as the UA referred to by the target Contact
>>     header field.  (This practice is occasionally used to install
>>     forwarding policy into registrars.)
>>
>>     A UAC also MUST NOT include an instance-id feature taf or reg-id
>>     Contact header field parameter in a request to un-register all
>>     Contacts (a single Contact header field value with the value of 
>> "*").
>>
>> This strikes me as odd in several ways.
>>
>> The reg-id lets us know "which registration we are talking about". The
> 
>> instance-id lets us know "which specific UA-appearance we are talking 
>> about".
>> So for a 3rd-party registration, it might be useful to have reg-id or 
>> instance-id values. Assume for example a voice-mail server that 
>> registers a low q-value contact for an AOR, so that calls will 
>> eventually reach it in a no-answer scenario. Withdrawing just those 
>> specific registrations would seem to require a selection mechanism 
>> from the set of registrations, and reg-id would appear to satisfy this
> need.
>>
>> In a different use case, assume a 3rd party registration is used to 
>> install forwarding policy. The use of an instance-id in such a 
>> registration would seem to allow the forwarding policy to target one 
>> specific instance of the set of contacts registered to the target. In 
>> other words, not "forward the call to sip:bob@example.com", but 
>> "forward the call to sip:bob@example.com's cell phone".
>>
>> Now it's entirely possible that neither of these scenarios actually 
>> work. But I don't see in the discussion of outbound anything about WHY
> 
>> they wouldn't work, which means that the requirements language (the 
>> MUST in outbound) is unsupported. I don't like unsupported 
>> requirements in a specification.
>> --
>> Dean
>>
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol Use 
>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>> sipping@ietf.org for new developments on the application of sip 
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol Use 
>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>> sipping@ietf.org for new developments on the application of sip
>>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 

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


From sip-bounces@ietf.org  Mon Oct 20 11:59:24 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A597F3A6A11;
	Mon, 20 Oct 2008 11:59:24 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C28163A6AE7
	for <sip@core3.amsl.com>; Mon, 20 Oct 2008 11:59:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.204
X-Spam-Level: 
X-Spam-Status: No, score=-6.204 tagged_above=-999 required=5 tests=[AWL=0.045, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nWM9BkeB-2iJ for <sip@core3.amsl.com>;
	Mon, 20 Oct 2008 11:59:21 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 9D1413A6A9E
	for <sip@ietf.org>; Mon, 20 Oct 2008 11:59:21 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	5768920E8B; Mon, 20 Oct 2008 21:00:32 +0200 (CEST)
X-AuditID: c1b4fb3c-aa8c7bb0000015b5-b1-48fcd55071f5
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	31A5520E88; Mon, 20 Oct 2008 21:00:32 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 21:00:31 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 20 Oct 2008 21:00:31 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCF90@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Stupid question on flow use in outbound
Thread-Index: AckwalpNrXwgtdvJS02TBwUFX2qSZwCDNpgQABJq3lAACSJG/w==
References: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se>
	<1FD3C0CCB36AAA4AAAB874C3898C0B2701AD7249@ILEXC2U03.ndc.lucent.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Orsic, Milo (Milo)" <orsic@alcatel-lucent.com>, "SIP IETF" <sip@ietf.org>
X-OriginalArrivalTime: 20 Oct 2008 19:00:31.0963 (UTC)
	FILETIME=[202062B0:01C932E6]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] Stupid question on flow use in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi Milo,

>IMHO outbound should specifies "alternative paths". Here is what I mean
>by "alternative paths".
> 
>Assume that China Airline has two counters (contacts), one only English
>speaking the other only Chinese spiking. It doesn't matter if you took
>either the escalator or the elevator to the English speaking counter
>(the elevator and escalator are alternatives paths).  However, if the
>elevator gets you to English speaking counter and the escalator gets you
>to Chinese speaking counter - they are not alternatives. 
>Hence, you have two choices, i.e. either
>1. the two alternatives get you to the same counter, or 
>2. make the second counter also English speaking.
>My choices is 1. (e.g. I don't want to be constrained that the
>alternative contact addresses must be registered with the same feature
>tags). 

So, I assume you AGREE with me: it shall be possible to register different capabilities on different flows?

...eventhough you objected when I brought it up in 3GPP ;)

Regards,

Christer



-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Christer Holmberg
Sent: Monday, October 20, 2008 12:56 AM
To: Dean Willis; SIP IETF
Subject: Re: [Sip] Stupid question on flow use in outbound


Hi, 

>Assume Bob's UA is using outbound and is registered with two flows.  
>Both flows use the same instance-id. The first flow goes through edge-
proxy 1 and has reg-id 1. The second flow goes through proxy 2 and has
reg-id 2.
>
>Both flows are "live" from a keepalive perspective.
>
>Alice calls Bob.
>
>Which flow gets exercised?
>
>Where in Outbound is this described? If it is not in Outbound, is it
described somewhere else? If it is simply left-to-the-implementation,
does this need to be explained somewhere?

I guess it is (for good or bad) left-to-the-implementation.

HOWEVER, one thing which has been discussed, and which I think we SHOULD
say something about, is whether it's allowed to use a different set of
user capabilities for each flow.

Personally I think it would be useful. For example, I could indicate
that I want to receive incoming video calls over my super-fast-broadband
access, instead of my slow jungle-drum access.

I don't think we would need very much text for this either. Maybe a note
saying something like:

"NOTE: A user MAY register different set of user capabilities (using the
mechanism in [ref-to-RFC3840] on each flow, if the user wishes the
registrar to choose a particular flow based on caller preferences
[ref-to-RFC3841]."

...or something like that.

Regards,

Christer

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

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


From sip-bounces@ietf.org  Mon Oct 20 12:52:38 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E48173A695F;
	Mon, 20 Oct 2008 12:52:38 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D426E3A695F
	for <sip@core3.amsl.com>; Mon, 20 Oct 2008 12:52:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.412
X-Spam-Level: 
X-Spam-Status: No, score=-6.412 tagged_above=-999 required=5 tests=[AWL=0.187, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id pw79zJXpIYoC for <sip@core3.amsl.com>;
	Mon, 20 Oct 2008 12:52:37 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id B125B3A68F7
	for <sip@ietf.org>; Mon, 20 Oct 2008 12:52:36 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com
	[10.160.244.31])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m9KJrR7H016741; Mon, 20 Oct 2008 22:53:43 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 20 Oct 2008 22:53:37 +0300
Received: from esebe101.NOE.Nokia.com ([172.21.138.215]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 20 Oct 2008 22:53:36 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 20 Oct 2008 22:53:36 +0300
Message-ID: <C84E0A4ABA6DD74DA5221E0833A35DF30AF1A058@esebe101.NOE.Nokia.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Stupid question on flow use in outbound
Thread-Index: AckwalpNrXwgtdvJS02TBwUFX2qSZwCDNpgQAAw4HeA=
References: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se>
From: <Markus.Isomaki@nokia.com>
To: <christer.holmberg@ericsson.com>, <dean.willis@softarmor.com>,
	<sip@ietf.org>
X-OriginalArrivalTime: 20 Oct 2008 19:53:36.0800 (UTC)
	FILETIME=[8A6FF200:01C932ED]
X-Nokia-AV: Clean
Subject: Re: [Sip] Stupid question on flow use in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer,

In what you describe below, you are assuming that in order to use your
super-fast-broadband access for video, you would also have to do your
related SIP transactions over the same interface. In general this is not
true, as you could as well run SIP over your jungle-drum interface while
putting the broadband interface addresses in your SDP. 

But I suppose we are talking about networks where some B2BUAs will get
confused if you try the media from a different IP address from where you
do SIP (although if you have something like a carrier grade NAT between
the UA and the B2BUA there is no guarantee that SIP and RTP would come
from the same IP). Perhaps it would be good enough to use two different
instance id's?
 
Markus


>-----Original Message-----
>From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
>Behalf Of ext Christer Holmberg
>Sent: 20 October, 2008 08:56
>To: Dean Willis; SIP IETF
>Subject: Re: [Sip] Stupid question on flow use in outbound
>
>
>Hi, 
>
>>Assume Bob's UA is using outbound and is registered with two flows.  
>>Both flows use the same instance-id. The first flow goes through edge-
>proxy 1 and has reg-id 1. The second flow goes through proxy 2 
>and has reg-id 2.
>>
>>Both flows are "live" from a keepalive perspective.
>>
>>Alice calls Bob.
>>
>>Which flow gets exercised?
>>
>>Where in Outbound is this described? If it is not in Outbound, is it
>described somewhere else? If it is simply 
>left-to-the-implementation, does this need to be explained somewhere?
>
>I guess it is (for good or bad) left-to-the-implementation.
>
>HOWEVER, one thing which has been discussed, and which I think 
>we SHOULD say something about, is whether it's allowed to use 
>a different set of user capabilities for each flow.
>
>Personally I think it would be useful. For example, I could 
>indicate that I want to receive incoming video calls over my 
>super-fast-broadband access, instead of my slow jungle-drum access.
>
>I don't think we would need very much text for this either. 
>Maybe a note saying something like:
>
>"NOTE: A user MAY register different set of user capabilities 
>(using the mechanism in [ref-to-RFC3840] on each flow, if the 
>user wishes the registrar to choose a particular flow based on 
>caller preferences [ref-to-RFC3841]."
>
>...or something like that.
>
>Regards,
>
>Christer
>
>_______________________________________________
>Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>This list is for NEW development of the core SIP Protocol Use 
>sip-implementors@cs.columbia.edu for questions on current sip 
>Use sipping@ietf.org for new developments on the application of sip
>
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct 20 13:14:02 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7E5F63A6ACE;
	Mon, 20 Oct 2008 13:14:02 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CF34B3A6ACE
	for <sip@core3.amsl.com>; Mon, 20 Oct 2008 13:14:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Q9NRQjaDUKP9 for <sip@core3.amsl.com>;
	Mon, 20 Oct 2008 13:14:00 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39])
	by core3.amsl.com (Postfix) with ESMTP id 892BD3A6AC1
	for <sip@ietf.org>; Mon, 20 Oct 2008 13:13:59 -0700 (PDT)
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1])
	by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id m9KKEDhI015244;
	Mon, 20 Oct 2008 15:15:04 -0500 (CDT)
Received: from ILEXC2U03.ndc.lucent.com ([135.3.39.9]) by
	ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 15:14:39 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 20 Oct 2008 15:14:37 -0500
Message-ID: <1FD3C0CCB36AAA4AAAB874C3898C0B2701AD7515@ILEXC2U03.ndc.lucent.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF083CCF90@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Stupid question on flow use in outbound
Thread-Index: AckwalpNrXwgtdvJS02TBwUFX2qSZwCDNpgQABJq3lAACSJG/wACcL6Q
References: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se>
	<1FD3C0CCB36AAA4AAAB874C3898C0B2701AD7249@ILEXC2U03.ndc.lucent.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF90@esealmw113.eemea.ericsson.se>
From: "Orsic, Milo \(Milo\)" <orsic@alcatel-lucent.com>
To: "Christer Holmberg" <christer.holmberg@ericsson.com>,
	"SIP IETF" <sip@ietf.org>
X-OriginalArrivalTime: 20 Oct 2008 20:14:39.0577 (UTC)
	FILETIME=[7B1C6C90:01C932F0]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Subject: Re: [Sip] Stupid question on flow use in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0537037119=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0537037119==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C932F0.7AA425C3"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C932F0.7AA425C3
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Christer,

No, you didn't follow my text below, i.e.:

Choice 1. says that "the alternative flows always terminate at the
single contact," or

Choice 2. says that "if the alternative flows terminate on different
contacts, then the contacts must have the same features."

The third case (yours) is "two alternative flows terminate at different
contacts, and the contacts have different features" by definition the
flows are not alternatives. Why would you call it an alternative - when
it gets you to a wrong place? (e.g. you used the RFC 3841 to select the
proper contact - and you ended up someplace else).
Cheers,
Milo=20

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

-----Original Message-----
From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]=20
Sent: Monday, October 20, 2008 2:01 PM
To: Orsic, Milo (Milo); SIP IETF
Subject: VS: [Sip] Stupid question on flow use in outbound


Hi Milo,

>IMHO outbound should specifies "alternative paths". Here is what I mean

>by "alternative paths".
>=20
>Assume that China Airline has two counters (contacts), one only English

>speaking the other only Chinese spiking. It doesn't matter if you took=20
>either the escalator or the elevator to the English speaking counter=20
>(the elevator and escalator are alternatives paths).  However, if the=20
>elevator gets you to English speaking counter and the escalator gets=20
>you to Chinese speaking counter - they are not alternatives.
>Hence, you have two choices, i.e. either 1. the two alternatives get=20
>you to the same counter, or 2. make the second counter also English=20
>speaking.
>My choices is 1. (e.g. I don't want to be constrained that the=20
>alternative contact addresses must be registered with the same feature=20
>tags).

So, I assume you AGREE with me: it shall be possible to register
different capabilities on different flows?

...eventhough you objected when I brought it up in 3GPP ;)

Regards,

Christer



-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Christer Holmberg
Sent: Monday, October 20, 2008 12:56 AM
To: Dean Willis; SIP IETF
Subject: Re: [Sip] Stupid question on flow use in outbound


Hi,=20

>Assume Bob's UA is using outbound and is registered with two flows. =20
>Both flows use the same instance-id. The first flow goes through edge-
proxy 1 and has reg-id 1. The second flow goes through proxy 2 and has
reg-id 2.
>
>Both flows are "live" from a keepalive perspective.
>
>Alice calls Bob.
>
>Which flow gets exercised?
>
>Where in Outbound is this described? If it is not in Outbound, is it
described somewhere else? If it is simply left-to-the-implementation,
does this need to be explained somewhere?

I guess it is (for good or bad) left-to-the-implementation.

HOWEVER, one thing which has been discussed, and which I think we SHOULD
say something about, is whether it's allowed to use a different set of
user capabilities for each flow.

Personally I think it would be useful. For example, I could indicate
that I want to receive incoming video calls over my super-fast-broadband
access, instead of my slow jungle-drum access.

I don't think we would need very much text for this either. Maybe a note
saying something like:

"NOTE: A user MAY register different set of user capabilities (using the
mechanism in [ref-to-RFC3840] on each flow, if the user wishes the
registrar to choose a particular flow based on caller preferences
[ref-to-RFC3841]."

...or something like that.

Regards,

Christer

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


------_=_NextPart_001_01C932F0.7AA425C3
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7651.59">
<TITLE>RE: [Sip] Stupid question on flow use in outbound</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman">Hi Christer,</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman">No, you didn't follow my text below, i.e.:</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman">Choice 1. says that &quot;the alternative flows always =
terminate at the<U> single contact,</U>&quot; or</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman">Choice 2. says that &quot;if the alternative flows terminate =
on different contacts, then the contacts must have the same =
features.&quot;</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman">The third case (yours) is &quot;two alternative flows =
terminate at different contacts, and the contacts have different =
features&quot; by definition</FONT><U> <FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Times New Roman">the flows are not alternatives</FONT></U><FONT =
COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times New Roman">. Why would you call =
it an alternative - when it gets you to a wrong place? (e.g. you used =
the RFC 3841 to select the proper contact - and you ended up someplace =
else).</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman">Cheers,</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Times =
New Roman">Milo</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial"> =
</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">----------------------------------------------------------=
---------------------------------------------</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">-----Original =
Message-----</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">From: Christer =
Holmberg [</FONT></SPAN><A =
HREF=3D"mailto:christer.holmberg@ericsson.com"><SPAN =
LANG=3D"en-us"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">mailto:christer.holmberg@ericsson.com</FONT></U></SPAN></A=
><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">] </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Sent: Monday, =
October 20, 2008 2:01 PM</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">To: Orsic, Milo =
(Milo); SIP IETF</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Subject: VS: =
[Sip] Stupid question on flow use in outbound</FONT></SPAN>
</P>
<BR>

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

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;IMHO outbound =
should specifies &quot;alternative paths&quot;. Here is what I mean =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;by =
&quot;alternative paths&quot;.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt; =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;Assume that =
China Airline has two counters (contacts), one only English =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;speaking the =
other only Chinese spiking. It doesn't matter if you took </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;either the =
escalator or the elevator to the English speaking counter </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;(the elevator =
and escalator are alternatives paths).&nbsp; However, if the =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;elevator gets =
you to English speaking counter and the escalator gets </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;you to =
Chinese speaking counter - they are not alternatives.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;Hence, you =
have two choices, i.e. either 1. the two alternatives get </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;you to the =
same counter, or 2. make the second counter also English </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;speaking.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;My choices is =
1. (e.g. I don't want to be constrained that the </FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;alternative =
contact addresses must be registered with the same feature =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;tags).</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">So, I assume you =
AGREE with me: it shall be possible to register different capabilities =
on different flows?</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">...eventhough you =
objected when I brought it up in 3GPP ;)</FONT></SPAN>
</P>

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

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Christer</FONT></SPAN>
</P>
<BR>
<BR>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">-----Original =
Message-----</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">From: =
sip-bounces@ietf.org [</FONT></SPAN><A =
HREF=3D"mailto:sip-bounces@ietf.org"><SPAN LANG=3D"en-us"><U><FONT =
COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">mailto:sip-bounces@ietf.org</FONT></U></SPAN></A><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">] On Behalf Of Christer =
Holmberg</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Sent: Monday, =
October 20, 2008 12:56 AM</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">To: Dean Willis; =
SIP IETF</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Subject: Re: =
[Sip] Stupid question on flow use in outbound</FONT></SPAN>
</P>
<BR>

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

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;Assume Bob's =
UA is using outbound and is registered with two flows.&nbsp; =
</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;Both flows =
use the same instance-id. The first flow goes through =
edge-</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">proxy 1 and has =
reg-id 1. The second flow goes through proxy 2 and has reg-id =
2.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;Both flows =
are &quot;live&quot; from a keepalive perspective.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;Alice calls =
Bob.</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;Which flow =
gets exercised?</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">&gt;</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&gt;Where in =
Outbound is this described? If it is not in Outbound, is =
it</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">described =
somewhere else? If it is simply left-to-the-implementation, does this =
need to be explained somewhere?</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">I guess it is (for =
good or bad) left-to-the-implementation.</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">HOWEVER, one thing =
which has been discussed, and which I think we SHOULD say something =
about, is whether it's allowed to use a different set of user =
capabilities for each flow.</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Personally I think =
it would be useful. For example, I could indicate that I want to receive =
incoming video calls over my super-fast-broadband access, instead of my =
slow jungle-drum access.</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">I don't think we =
would need very much text for this either. Maybe a note saying something =
like:</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">&quot;NOTE: A user =
MAY register different set of user capabilities (using the mechanism in =
[ref-to-RFC3840] on each flow, if the user wishes the registrar to =
choose a particular flow based on caller preferences =
[ref-to-RFC3841].&quot;</FONT></SPAN></P>

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">...or something =
like that.</FONT></SPAN>
</P>

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

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

<P><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">_______________________________________________</FONT></SP=
AN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">Sip mailing =
list&nbsp; </FONT></SPAN><A =
HREF=3D"https://www.ietf.org/mailman/listinfo/sip"><SPAN =
LANG=3D"en-us"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">https://www.ietf.org/mailman/listinfo/sip</FONT></U></SPAN=
></A><SPAN LANG=3D"en-us"></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">This list is for =
NEW development of the core SIP Protocol Use =
sip-implementors@cs.columbia.edu for questions on current sip Use =
sipping@ietf.org for new developments on the application of =
sip</FONT></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01C932F0.7AA425C3--

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

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


From sip-bounces@ietf.org  Mon Oct 20 16:15:03 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8A1963A69FF;
	Mon, 20 Oct 2008 16:15:03 -0700 (PDT)
X-Original-To: sip@ietf.org
Delivered-To: sip@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 43DCA3A69EF; Mon, 20 Oct 2008 16:15:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081020231502.43DCA3A69EF@core3.amsl.com>
Date: Mon, 20 Oct 2008 16:15:02 -0700 (PDT)
Cc: sip@ietf.org
Subject: [Sip] I-D Action:draft-ietf-sip-info-events-00.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--NextPart

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


	Title           : Session Initiation Protocol (SIP) INFO Method and Package Framework
	Author(s)       : E. Burger, et al.
	Filename        : draft-ietf-sip-info-events-00.txt
	Pages           : 29
	Date            : 2008-10-20

This document defines the new INFO method and a mechanism for
defining, negotiating and exchanging Info Packages that use the INFO
method.  Applications which need to exchange session-related
information within a SIP INVITE-created dialog use these INFO
requests.  This draft addresses issues and open items from RFC 2976,
and replaces it.Conventions Used in this Document

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sip-info-events-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-sip-info-events-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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


From sip-bounces@ietf.org  Mon Oct 20 16:38:05 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F07BA3A6847;
	Mon, 20 Oct 2008 16:38:04 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CD3703A692C
	for <sip@core3.amsl.com>; Mon, 20 Oct 2008 16:38:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[AWL=-0.121, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LRl58dtVMkMw for <sip@core3.amsl.com>;
	Mon, 20 Oct 2008 16:38:03 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33])
	by core3.amsl.com (Postfix) with ESMTP id EC7EE3A67E9
	for <sip@ietf.org>; Mon, 20 Oct 2008 16:38:02 -0700 (PDT)
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id m9KNe8BB027879
	for <sip@ietf.org>; Mon, 20 Oct 2008 18:40:08 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by
	ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Oct 2008 18:39:13 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.30]) by
	DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 01:39:11 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 21 Oct 2008 01:39:10 +0200
Message-ID: <5D1A7985295922448D5550C94DE29180024254D8@DEEXC1U01.de.lucent.com>
In-Reply-To: <20081020231502.43DCA3A69EF@core3.amsl.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] I-D Action:draft-ietf-sip-info-events-00.txt
Thread-Index: AckzCeI5b8p+rS2oRRaGHJzyI9WhlQAAnc4g
References: <20081020231502.43DCA3A69EF@core3.amsl.com>
From: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: <sip@ietf.org>
X-OriginalArrivalTime: 20 Oct 2008 23:39:11.0167 (UTC)
	FILETIME=[0D8C74F0:01C9330D]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Subject: Re: [Sip] I-D Action:draft-ietf-sip-info-events-00.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

(As WG chair)

This is the draft that is supposed to solve all the INFO problems we
ever had and ever will have in future.

Note that the current version of the draft obsoletes (replaces) RFC
2976, i.e. the existing INFO method documentation.

There are a couple of open issues in the document where I believe the
editor's will be initiating discussion shortly - so you may want to wait
for those on the TBD.

Otherwise, let the discussion commence. You may want to try and raise
different issues in different emails, in order to allow these to be kept
track of.

Regards

Keith

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Internet-Drafts@ietf.org
> Sent: Tuesday, October 21, 2008 12:15 AM
> To: i-d-announce@ietf.org
> Cc: sip@ietf.org
> Subject: [Sip] I-D Action:draft-ietf-sip-info-events-00.txt
> 
> A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> This draft is a work item of the Session Initiation Protocol 
> Working Group of the IETF.
> 
> 
> 	Title           : Session Initiation Protocol (SIP) 
> INFO Method and Package Framework
> 	Author(s)       : E. Burger, et al.
> 	Filename        : draft-ietf-sip-info-events-00.txt
> 	Pages           : 29
> 	Date            : 2008-10-20
> 
> This document defines the new INFO method and a mechanism for 
> defining, negotiating and exchanging Info Packages that use 
> the INFO method.  Applications which need to exchange 
> session-related information within a SIP INVITE-created 
> dialog use these INFO requests.  This draft addresses issues 
> and open items from RFC 2976, and replaces it.Conventions 
> Used in this Document
> 
> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 
> NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 
> "OPTIONAL" in this document are to be interpreted as 
> described in RFC 2119 [RFC2119].
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-sip-info-events-00.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail 
> reader implementation to automatically retrieve the ASCII 
> version of the Internet-Draft.
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct 20 22:37:43 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EFBD53A659A;
	Mon, 20 Oct 2008 22:37:42 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E2CFD3A659A
	for <sip@core3.amsl.com>; Mon, 20 Oct 2008 22:37:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.204
X-Spam-Level: 
X-Spam-Status: No, score=-6.204 tagged_above=-999 required=5 tests=[AWL=0.044, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id DV3u0xY62fPa for <sip@core3.amsl.com>;
	Mon, 20 Oct 2008 22:37:40 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 38F9B3A63EC
	for <sip@ietf.org>; Mon, 20 Oct 2008 22:37:40 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	BEDC3210E1; Tue, 21 Oct 2008 07:38:48 +0200 (CEST)
X-AuditID: c1b4fb3e-a7682bb000007a96-45-48fd6ad02453
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	5CAA421088; Tue, 21 Oct 2008 07:38:24 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 07:38:12 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 21 Oct 2008 07:38:12 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF088222A2@esealmw113.eemea.ericsson.se>
In-Reply-To: <1FD3C0CCB36AAA4AAAB874C3898C0B2701AD7515@ILEXC2U03.ndc.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Stupid question on flow use in outbound
Thread-Index: AckwalpNrXwgtdvJS02TBwUFX2qSZwCDNpgQABJq3lAACSJG/wACcL6QABPu53A=
References: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se>
	<1FD3C0CCB36AAA4AAAB874C3898C0B2701AD7249@ILEXC2U03.ndc.lucent.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF90@esealmw113.eemea.ericsson.se>
	<1FD3C0CCB36AAA4AAAB874C3898C0B2701AD7515@ILEXC2U03.ndc.lucent.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Orsic, Milo (Milo)" <orsic@alcatel-lucent.com>, "SIP IETF" <sip@ietf.org>
X-OriginalArrivalTime: 21 Oct 2008 05:38:12.0930 (UTC)
	FILETIME=[3570A220:01C9333F]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] Stupid question on flow use in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0380884258=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0380884258==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C9333F.351D28EE"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9333F.351D28EE
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Milo,
=20
The contact does not represent the China Airline counter. The USER
represent the China Airline counter. The contacts just represent two
ways of entering the China Airline offices, but once you've done that
you will still reach the same user.
=20
Converting into SIP language: you are establishing a session with the
USER. The contact is simply the "door" for the SIP messages to reach the
SIP stack.
=20
Regards,
=20
Christer

________________________________

From: Orsic, Milo (Milo) [mailto:orsic@alcatel-lucent.com]=20
Sent: 20. lokakuuta 2008 23:15
To: Christer Holmberg; SIP IETF
Subject: RE: [Sip] Stupid question on flow use in outbound



Hi Christer,=20

No, you didn't follow my text below, i.e.:=20

Choice 1. says that "the alternative flows always terminate at the
single contact," or=20

Choice 2. says that "if the alternative flows terminate on different
contacts, then the contacts must have the same features."

The third case (yours) is "two alternative flows terminate at different
contacts, and the contacts have different features" by definition the
flows are not alternatives. Why would you call it an alternative - when
it gets you to a wrong place? (e.g. you used the RFC 3841 to select the
proper contact - and you ended up someplace else).

Cheers,=20
Milo=20

------------------------------------------------------------------------
-------------------------------=20

-----Original Message-----=20
From: Christer Holmberg [mailto:christer.holmberg@ericsson.com
<mailto:christer.holmberg@ericsson.com> ]=20
Sent: Monday, October 20, 2008 2:01 PM=20
To: Orsic, Milo (Milo); SIP IETF=20
Subject: VS: [Sip] Stupid question on flow use in outbound=20


Hi Milo,=20

>IMHO outbound should specifies "alternative paths". Here is what I mean

>by "alternative paths".=20
>=20
>Assume that China Airline has two counters (contacts), one only English

>speaking the other only Chinese spiking. It doesn't matter if you took=20
>either the escalator or the elevator to the English speaking counter=20
>(the elevator and escalator are alternatives paths).  However, if the=20
>elevator gets you to English speaking counter and the escalator gets=20
>you to Chinese speaking counter - they are not alternatives.=20
>Hence, you have two choices, i.e. either 1. the two alternatives get=20
>you to the same counter, or 2. make the second counter also English=20
>speaking.=20
>My choices is 1. (e.g. I don't want to be constrained that the=20
>alternative contact addresses must be registered with the same feature=20
>tags).=20

So, I assume you AGREE with me: it shall be possible to register
different capabilities on different flows?=20

...eventhough you objected when I brought it up in 3GPP ;)=20

Regards,=20

Christer=20



-----Original Message-----=20
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org
<mailto:sip-bounces@ietf.org> ] On Behalf Of Christer Holmberg=20
Sent: Monday, October 20, 2008 12:56 AM=20
To: Dean Willis; SIP IETF=20
Subject: Re: [Sip] Stupid question on flow use in outbound=20


Hi,=20

>Assume Bob's UA is using outbound and is registered with two flows. =20
>Both flows use the same instance-id. The first flow goes through edge-=20
proxy 1 and has reg-id 1. The second flow goes through proxy 2 and has
reg-id 2.=20
>=20
>Both flows are "live" from a keepalive perspective.=20
>=20
>Alice calls Bob.=20
>=20
>Which flow gets exercised?=20
>=20
>Where in Outbound is this described? If it is not in Outbound, is it=20
described somewhere else? If it is simply left-to-the-implementation,
does this need to be explained somewhere?=20

I guess it is (for good or bad) left-to-the-implementation.=20

HOWEVER, one thing which has been discussed, and which I think we SHOULD
say something about, is whether it's allowed to use a different set of
user capabilities for each flow.

Personally I think it would be useful. For example, I could indicate
that I want to receive incoming video calls over my super-fast-broadband
access, instead of my slow jungle-drum access.

I don't think we would need very much text for this either. Maybe a note
saying something like:=20

"NOTE: A user MAY register different set of user capabilities (using the
mechanism in [ref-to-RFC3840] on each flow, if the user wishes the
registrar to choose a particular flow based on caller preferences
[ref-to-RFC3841]."

...or something like that.=20

Regards,=20

Christer=20

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


------_=_NextPart_001_01C9333F.351D28EE
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>RE: [Sip] Stupid question on flow use in =
outbound</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16711" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D716023605-21102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Milo,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D716023605-21102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D716023605-21102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>The contact does not represent the China =
Airline counter.=20
The USER represent the China Airline counter. The contacts just =
represent two=20
ways of entering the China Airline offices, but once you've done that=20
you&nbsp;will still reach the same user.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D716023605-21102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D716023605-21102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Converting into SIP language: you are =
establishing a=20
session with the USER. The contact is simply the "door" for the SIP=20
messages&nbsp;to reach the SIP stack.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D716023605-21102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D716023605-21102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D716023605-21102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D716023605-21102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Christer</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Orsic, Milo (Milo)=20
[mailto:orsic@alcatel-lucent.com] <BR><B>Sent:</B> 20. lokakuuta 2008=20
23:15<BR><B>To:</B> Christer Holmberg; SIP IETF<BR><B>Subject:</B> RE: =
[Sip]=20
Stupid question on flow use in outbound<BR></FONT><BR></DIV>
<DIV></DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=3Den-us><FONT face=3D"Times New Roman" color=3D#000080 =
size=3D2>Hi=20
Christer,</FONT></SPAN> </P>
<P><SPAN lang=3Den-us><FONT face=3D"Times New Roman" color=3D#000080 =
size=3D2>No, you=20
didn't follow my text below, i.e.:</FONT></SPAN> </P>
<P><SPAN lang=3Den-us><FONT face=3D"Times New Roman" color=3D#000080 =
size=3D2>Choice 1.=20
says that "the alternative flows always terminate at the<U> single =
contact,</U>"=20
or</FONT></SPAN> </P>
<P><SPAN lang=3Den-us><FONT face=3D"Times New Roman" color=3D#000080 =
size=3D2>Choice 2.=20
says that "if the alternative flows terminate on different contacts, =
then the=20
contacts must have the same features."</FONT></SPAN></P>
<P><SPAN lang=3Den-us><FONT face=3D"Times New Roman" color=3D#000080 =
size=3D2>The third=20
case (yours) is "two alternative flows terminate at different contacts, =
and the=20
contacts have different features" by definition</FONT><U> <FONT=20
face=3D"Times New Roman" color=3D#000080 size=3D2>the flows are not=20
alternatives</FONT></U><FONT face=3D"Times New Roman" color=3D#000080 =
size=3D2>. Why=20
would you call it an alternative - when it gets you to a wrong place? =
(e.g. you=20
used the RFC 3841 to select the proper contact - and you ended up =
someplace=20
else).</FONT></SPAN></P>
<P><SPAN lang=3Den-us><FONT face=3D"Times New Roman" color=3D#000080=20
size=3D2>Cheers,</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT =
face=3D"Times New Roman"=20
color=3D#000080 size=3D2>Milo</FONT><FONT face=3DArial color=3D#000080 =
size=3D2>=20
</FONT></SPAN></P>
<P><SPAN lang=3Den-us><FONT face=3DArial color=3D#000080=20
size=3D2>----------------------------------------------------------------=
---------------------------------------</FONT></SPAN>=20
</P>
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>-----Original=20
Message-----</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>From:=20
Christer Holmberg [</FONT></SPAN><A=20
href=3D"mailto:christer.holmberg@ericsson.com"><SPAN =
lang=3Den-us><U><FONT=20
face=3DArial color=3D#0000ff=20
size=3D2>mailto:christer.holmberg@ericsson.com</FONT></U></SPAN></A><SPAN=
=20
lang=3Den-us><FONT face=3DArial size=3D2>] </FONT></SPAN><BR><SPAN =
lang=3Den-us><FONT=20
face=3DArial size=3D2>Sent: Monday, October 20, 2008 2:01 =
PM</FONT></SPAN> <BR><SPAN=20
lang=3Den-us><FONT face=3DArial size=3D2>To: Orsic, Milo (Milo); SIP=20
IETF</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>Subject: VS:=20
[Sip] Stupid question on flow use in outbound</FONT></SPAN> </P><BR>
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>Hi Milo,</FONT></SPAN> =
</P>
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>&gt;IMHO outbound =
should specifies=20
"alternative paths". Here is what I mean </FONT></SPAN><BR><SPAN=20
lang=3Den-us><FONT face=3DArial size=3D2>&gt;by "alternative =
paths".</FONT></SPAN>=20
<BR><SPAN lang=3Den-us><FONT face=3DArial size=3D2>&gt; =
</FONT></SPAN><BR><SPAN=20
lang=3Den-us><FONT face=3DArial size=3D2>&gt;Assume that China Airline =
has two=20
counters (contacts), one only English </FONT></SPAN><BR><SPAN =
lang=3Den-us><FONT=20
face=3DArial size=3D2>&gt;speaking the other only Chinese spiking. It =
doesn't matter=20
if you took </FONT></SPAN><BR><SPAN lang=3Den-us><FONT face=3DArial=20
size=3D2>&gt;either the escalator or the elevator to the English =
speaking counter=20
</FONT></SPAN><BR><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>&gt;(the elevator and=20
escalator are alternatives paths).&nbsp; However, if the =
</FONT></SPAN><BR><SPAN=20
lang=3Den-us><FONT face=3DArial size=3D2>&gt;elevator gets you to =
English speaking=20
counter and the escalator gets </FONT></SPAN><BR><SPAN =
lang=3Den-us><FONT=20
face=3DArial size=3D2>&gt;you to Chinese speaking counter - they are not =

alternatives.</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT face=3DArial=20
size=3D2>&gt;Hence, you have two choices, i.e. either 1. the two =
alternatives get=20
</FONT></SPAN><BR><SPAN lang=3Den-us><FONT face=3DArial size=3D2>&gt;you =
to the same=20
counter, or 2. make the second counter also English =
</FONT></SPAN><BR><SPAN=20
lang=3Den-us><FONT face=3DArial size=3D2>&gt;speaking.</FONT></SPAN> =
<BR><SPAN=20
lang=3Den-us><FONT face=3DArial size=3D2>&gt;My choices is 1. (e.g. I =
don't want to be=20
constrained that the </FONT></SPAN><BR><SPAN lang=3Den-us><FONT =
face=3DArial=20
size=3D2>&gt;alternative contact addresses must be registered with the =
same=20
feature </FONT></SPAN><BR><SPAN lang=3Den-us><FONT face=3DArial=20
size=3D2>&gt;tags).</FONT></SPAN> </P>
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>So, I assume you AGREE =
with me: it=20
shall be possible to register different capabilities on different=20
flows?</FONT></SPAN> </P>
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>...eventhough you =
objected when I=20
brought it up in 3GPP ;)</FONT></SPAN> </P>
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>Regards,</FONT></SPAN> =
</P>
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>Christer</FONT></SPAN> =
</P><BR><BR>
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>-----Original=20
Message-----</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>From:=20
sip-bounces@ietf.org [</FONT></SPAN><A =
href=3D"mailto:sip-bounces@ietf.org"><SPAN=20
lang=3Den-us><U><FONT face=3DArial color=3D#0000ff=20
size=3D2>mailto:sip-bounces@ietf.org</FONT></U></SPAN></A><SPAN =
lang=3Den-us><FONT=20
face=3DArial size=3D2>] On Behalf Of Christer Holmberg</FONT></SPAN> =
<BR><SPAN=20
lang=3Den-us><FONT face=3DArial size=3D2>Sent: Monday, October 20, 2008 =
12:56=20
AM</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT face=3DArial size=3D2>To: =
Dean Willis;=20
SIP IETF</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>Subject: Re:=20
[Sip] Stupid question on flow use in outbound</FONT></SPAN> </P><BR>
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>Hi, </FONT></SPAN></P>
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>&gt;Assume Bob's UA is =
using=20
outbound and is registered with two flows.&nbsp; </FONT></SPAN><BR><SPAN =

lang=3Den-us><FONT face=3DArial size=3D2>&gt;Both flows use the same =
instance-id. The=20
first flow goes through edge-</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT =

face=3DArial size=3D2>proxy 1 and has reg-id 1. The second flow goes =
through proxy 2=20
and has reg-id 2.</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT =
face=3DArial=20
size=3D2>&gt;</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>&gt;Both=20
flows are "live" from a keepalive perspective.</FONT></SPAN> <BR><SPAN=20
lang=3Den-us><FONT face=3DArial size=3D2>&gt;</FONT></SPAN> <BR><SPAN =
lang=3Den-us><FONT=20
face=3DArial size=3D2>&gt;Alice calls Bob.</FONT></SPAN> <BR><SPAN =
lang=3Den-us><FONT=20
face=3DArial size=3D2>&gt;</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT =
face=3DArial=20
size=3D2>&gt;Which flow gets exercised?</FONT></SPAN> <BR><SPAN =
lang=3Den-us><FONT=20
face=3DArial size=3D2>&gt;</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT =
face=3DArial=20
size=3D2>&gt;Where in Outbound is this described? If it is not in =
Outbound, is=20
it</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>described=20
somewhere else? If it is simply left-to-the-implementation, does this =
need to be=20
explained somewhere?</FONT></SPAN> </P>
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>I guess it is (for =
good or bad)=20
left-to-the-implementation.</FONT></SPAN> </P>
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>HOWEVER, one thing =
which has been=20
discussed, and which I think we SHOULD say something about, is whether =
it's=20
allowed to use a different set of user capabilities for each=20
flow.</FONT></SPAN></P>
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>Personally I think it =
would be=20
useful. For example, I could indicate that I want to receive incoming =
video=20
calls over my super-fast-broadband access, instead of my slow =
jungle-drum=20
access.</FONT></SPAN></P>
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>I don't think we would =
need very=20
much text for this either. Maybe a note saying something =
like:</FONT></SPAN>=20
</P>
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>"NOTE: A user MAY =
register different=20
set of user capabilities (using the mechanism in [ref-to-RFC3840] on =
each flow,=20
if the user wishes the registrar to choose a particular flow based on =
caller=20
preferences [ref-to-RFC3841]."</FONT></SPAN></P>
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>...or something like=20
that.</FONT></SPAN> </P>
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>Regards,</FONT></SPAN> =
</P>
<P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>Christer</FONT></SPAN> =
</P>
<P><SPAN lang=3Den-us><FONT face=3DArial=20
size=3D2>_______________________________________________</FONT></SPAN> =
<BR><SPAN=20
lang=3Den-us><FONT face=3DArial size=3D2>Sip mailing list&nbsp; =
</FONT></SPAN><A=20
href=3D"https://www.ietf.org/mailman/listinfo/sip"><SPAN =
lang=3Den-us><U><FONT=20
face=3DArial color=3D#0000ff=20
size=3D2>https://www.ietf.org/mailman/listinfo/sip</FONT></U></SPAN></A><=
SPAN=20
lang=3Den-us></SPAN> <BR><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>This list is for=20
NEW development of the core SIP Protocol Use =
sip-implementors@cs.columbia.edu=20
for questions on current sip Use sipping@ietf.org for new developments =
on the=20
application of sip</FONT></SPAN></P></BODY></HTML>

------_=_NextPart_001_01C9333F.351D28EE--

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

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


From sip-bounces@ietf.org  Mon Oct 20 22:50:18 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7E3323A67E5;
	Mon, 20 Oct 2008 22:50:18 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B0CEB3A67E5
	for <sip@core3.amsl.com>; Mon, 20 Oct 2008 22:50:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5
	tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_55=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6gad2fVamY4M for <sip@core3.amsl.com>;
	Mon, 20 Oct 2008 22:50:16 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id 1C5553A63EC
	for <sip@ietf.org>; Mon, 20 Oct 2008 22:50:15 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com
	[10.160.244.31])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m9L5otwV017071; Tue, 21 Oct 2008 08:51:19 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 21 Oct 2008 08:51:17 +0300
Received: from vaebe106.NOE.Nokia.com ([10.160.244.67]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 21 Oct 2008 08:51:16 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 21 Oct 2008 08:51:14 +0300
Message-ID: <7A726F54F791494C8D8C87F13736E80EFF95C8@vaebe106.NOE.Nokia.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF19A212A1@zrc2hxm0.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckpErqAvb04oxeFTuK4/n1kThR9egATKlVwAnew/bA=
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18665.43684.176244.988653@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se><18665.59	269.640606.477292@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se><48EBC88B.2030300@cisco.com>	<46101DEA-677B-4F2!
	8-AD1E-32F6438! 5! ! 85 3 5@so ft armo
	r.com	><5D1A7985295922448D5550C94DE29180023B048B@DEEXC1U01.de.lucent.com><1ECE0EB50388174790F9694F77522CCF199DA2EB@zrc2hxm0.corp.nortel.com><18668.22818.736346.883984@taimen.test.fi>
	<1ECE0EB50388174790F9694F77522CCF19A212A1@zrc2hxm0.corp.nortel.com>
From: <Erkki.Koivusalo@nokia.com>
To: <audet@nortel.com>, <jh@tutpro.com>
X-OriginalArrivalTime: 21 Oct 2008 05:51:16.0859 (UTC)
	FILETIME=[08B2B4B0:01C93341]
X-Nokia-AV: Clean
Cc: sip@ietf.org, pkyzivat@cisco.com, dean.willis@softarmor.com,
	drage@alcatel-lucent.com, christer.holmberg@ericsson.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi Francois,

>I'm saying a new draft on redundant registration is needed, 
>and we can leave outbound AS IS.
>
>I thought about this more.
>
>I think what it means, is NOT using "Supported: outbound", but using 
>the +sip.instance and reg-id in the REGISTER. Perhaps with a different
>"Support: redundant-registrations" or whatever.
>
>The reg-ids will distinguish the multiple registrations. The 
>+sip.instance will correlate them.

Funny, but your proposal reminds me about the email which
I sent to sip mailing list in Nov 2006:

http://www.ietf.org/mail-archive/web/sip/current/msg17495.html

What I proposed that time was essentially this:
----
Outbound draft has bundled together two different things
that actually are orthogonal, both as problems and as
solutions too. The only reason to keep them together in
one single spec is that in some environments it makes
sense to use them together, but the problem is that in
some other environments separation would be desirable.

Those two items could be described like this:

- A mechanism with which an UA would be able to maintain a
  persistent flow through a NAT/firewall towards an outbound 
  proxy, keep the flow alive and monitor its state. The
  mechanism would also define how the authoritative and edge 
  proxies would use the persistent flow and Path header for 
  forwarding incoming requests to the UA.

- A mechanism with which an UA instance would be able to achieve
  high availability towards its home domain, by maintaining
  multiple simultaneous registrations without the need to
  receive multiple forked copies of a single incoming request.
  This resiliency would enable the UA to protect its connectivity
  against edge proxy failures or access network connectivity 
  failures. This mechanism would introduce the reg-id parameter
  to Contact and allow the authoritative proxy to forward
  requests to the UA using the set of registered Contacts
  and corresponding Paths.
----

I proposed to split Outbound to two drafts along with those
lines:
a) flow keepalive draft
b) multiple registration draft

Interestingly enough I find the proposed flow keepalive draft
to highly correlate to the Outbound original requirements
(from Keith's recent email):

   1.  Must be able to detect that a UA supports these mechanisms.
   2.  Support UAs behind NATs.
   3.  Support TLS to a UA without a stable DNS name or IP address.
   4.  Detect failure of a connection and be able to correct for this.
   5.  Support many UAs simultaneously rebooting.
   6.  Support a NAT rebooting or resetting.
   7.  Minimize initial startup load on a proxy.
   8.  Support architectures with edge proxies.

On the other hand, the multiple reg draft does not have any direct
relation to these requirements, even if you could argue multiple
registrations would be needed to make the solution more robust
against NAT reboots (item 6). To me it really attacks SIP proxy
reboots or any network failures for multihomed UAs, something
_not_ within the original requirements of Outbound.

>I think what it means, is NOT using "Supported: outbound", but using 
>the +sip.instance and reg-id in the REGISTER. Perhaps with a different
>"Support: redundant-registrations" or whatever.
>
>The reg-ids will distinguish the multiple registrations. The 
>+sip.instance will correlate them.

The only real difference between our proposals is that you
suggest usage of +sip.instance and reg-id to be defined in
a rather similar way in two drafts: Outbound and a new one.
I was proposing to move all that stuff to another draft so
that implementations could implement support for keepalives
and multiple registration either separately or combined,
depending on the problems they try to solve.

P.S. Personally I believe all this discussion is just too late,
decisions have been taken years ago and most of the WG members
are probably too tired with this subject to do any work for it.

Regards,

Erkki

>-----Original Message-----
>From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
>Behalf Of ext Francois Audet
>Sent: 08.October.2008 19:48
>To: Juha Heinanen
>Cc: sip@ietf.org; Paul Kyzivat; Christer Holmberg; DRAGE,Keith 
>(Keith); Dean Willis
>Subject: Re: [Sip] Dual registration without Outbound
>
>No.
>
>I'm saying a new draft on redundant registration is needed, 
>and we can leave
>outbound AS IS.
>
>I thought about this more.
>
>I think what it means, is NOT using "Supported: outbound", but using 
>the +sip.instance and reg-id in the REGISTER. Perhaps with a different
>"Support: redundant-registrations" or whatever.
>
>The reg-ids will distinguish the multiple registrations. The 
>+sip.instance
>will correlate them.
>
>This will be in line with what we did with GRUU which also can use the
>+sip.instance.
>
>A new draft describing this should be fairly simple to do, and 
>we wouldn't
>derail the process, and it would be very much in line with 
>sip-outbound.
>
>Makes sense?
>
>> -----Original Message-----
>> From: Juha Heinanen [mailto:jh@tutpro.com] 
>> Sent: Tuesday, October 07, 2008 23:54
>> To: Audet, Francois (SC100:3055)
>> Cc: DRAGE, Keith (Keith); Dean Willis; Paul Kyzivat; 
>> sip@ietf.org; Christer Holmberg
>> Subject: Re: [Sip] Dual registration without Outbound
>> 
>> Francois Audet writes:
>> 
>>  > Rather, I think this should be a new draft, and it should 
>> be  > independent from outbound.
>> 
>> so do you now finally agree to base outbound drfat on two new 
>> drafts that are also independent of outbound: dialog 
>> connection re-use and keepalive?
>> 
>> -- juha
>> 
>_______________________________________________
>Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>This list is for NEW development of the core SIP Protocol
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sipping@ietf.org for new developments on the application of sip
>
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct 20 23:00:23 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CF6EA3A6822;
	Mon, 20 Oct 2008 23:00:23 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BD3703A6822
	for <sip@core3.amsl.com>; Mon, 20 Oct 2008 23:00:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.845
X-Spam-Level: 
X-Spam-Status: No, score=-4.845 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id uthelqq9nFIB for <sip@core3.amsl.com>;
	Mon, 20 Oct 2008 23:00:22 -0700 (PDT)
Received: from ahmler8.mail.eds.com (ahmler8.mail.eds.com [192.85.154.82])
	by core3.amsl.com (Postfix) with ESMTP id EC3223A659A
	for <sip@ietf.org>; Mon, 20 Oct 2008 23:00:21 -0700 (PDT)
Received: from ahmlir1.mail.eds.com (ahmlir1-2.mail.eds.com [192.85.154.152])
	by ahmler8.mail.eds.com (8.14.2/8.13.8) with ESMTP id m9L61RNJ002124;
	Tue, 21 Oct 2008 02:01:28 -0400
Received: from ahmlir1.mail.eds.com (localhost.localdomain [127.0.0.1])
	by ahmlir1.mail.eds.com (8.14.2/8.12.10) with ESMTP id m9L61MDX011664; 
	Tue, 21 Oct 2008 02:01:22 -0400
Received: from usut001.3Com.com ([205.142.126.149])
	by ahmlir1.mail.eds.com (8.14.2/8.12.10) with ESMTP id m9L61MGb011653; 
	Tue, 21 Oct 2008 02:01:22 -0400
X-EDSINT-Source-Ip: 205.142.126.149
From: Udit_Goyal@3com.com
To: sip-implementors@cs.columbia.edu, sip@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.2 June 01, 2004
Message-ID: <OF204F420F.568E20D7-ON652574E9.00212F67-652574E9.002131E2@3com.com>
Date: Tue, 21 Oct 2008 11:33:06 +0530
X-MIMETrack: Serialize by Router on USUT001/US/3Com(Release 6.5.5FP2|October
	23, 2006) at 10/20/2008 11:01:22 PM,
	Serialize complete at 10/20/2008 11:01:22 PM
Subject: [Sip] Sip query
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1156098512=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multipart message in MIME format.
--===============1156098512==
Content-Type: multipart/alternative; boundary="=_alternative 002131D7652574E9_="

This is a multipart message in MIME format.
--=_alternative 002131D7652574E9_=
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: base64

LQ0KQSBxdWVyeSBvbiBTaXAgY2FsbCBmbG93IC0NCg0KUGFydHkgc2VuZHMgb3V0IElOVklURSB3
aXRoIFNEUCBpbmZvIHRvIHBhcnR5IEIgdG8gbWFrZSBhIGNhbGwuIA0KUGFydHkgQiByZWNlaXZl
cyB0aGUgbWVzc2FnZSBhbmQgc2VuZHMgYmFjayAxODMgU2Vzc2lvbiBwcm9ncmVzcyB3aXRoIFNE
UCANCmluZm8gdG8gcGFydHkgQS4gSW4gdGhlIDE4MyBtZXNzYWdlLCBpdCBkb2VzIGhhdmUgQ29u
dGFjdCBpbmZvcm1hdGlvbi4NCk5vdywgcGFydHkgQSBzZW5kcyBvdXQgQ0FOQ0VMIG1lc3NhZ2Ug
dG8gcGFydHkgQiB1c2luZyBjb250YWN0IGhlYWRlciANCmluZm9ybWF0aW9uIHJlY2VpdmVkIGlu
IDE4MyBtZXNzYWdlLg0KDQpXaWxsIGl0IGJlIHZhbGlkIGluIFNJUCB0byB1c2UgQ29udGFjdCBp
bmZvcm1hdGlvbiBiZWZvcmUgcmVjZWl2aW5nIDIwMCBPSyANCm1lc3NhZ2Ugb3Igbm90ID8NCg0K
Q09ORklERU5USUFMSVRZIE5PVElDRTogVGhpcyBlLW1haWwgbWVzc2FnZSwgaW5jbHVkaW5nIGFu
eSBhdHRhY2htZW50cywNCmlzIGJlaW5nIHNlbnQgYnkgM0NvbSBmb3IgdGhlIHNvbGUgdXNlIG9m
IHRoZSBpbnRlbmRlZCByZWNpcGllbnQocykgYW5kDQptYXkgY29udGFpbiBjb25maWRlbnRpYWws
IHByb3ByaWV0YXJ5IGFuZC9vciBwcml2aWxlZ2VkIGluZm9ybWF0aW9uLg0KQW55IHVuYXV0aG9y
aXplZCByZXZpZXcsIHVzZSwgZGlzY2xvc3VyZSBhbmQvb3IgZGlzdHJpYnV0aW9uIGJ5IGFueSAN
CnJlY2lwaWVudCBpcyBwcm9oaWJpdGVkLiAgSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkIHJl
Y2lwaWVudCwgcGxlYXNlDQpkZWxldGUgYW5kL29yIGRlc3Ryb3kgYWxsIGNvcGllcyBvZiB0aGlz
IG1lc3NhZ2UgcmVnYXJkbGVzcyBvZiBmb3JtIGFuZA0KYW55IGluY2x1ZGVkIGF0dGFjaG1lbnRz
IGFuZCBub3RpZnkgM0NvbSBpbW1lZGlhdGVseSBieSBjb250YWN0aW5nIHRoZQ0Kc2VuZGVyIHZp
YSByZXBseSBlLW1haWwgb3IgZm9yd2FyZGluZyB0byAzQ29tIGF0IHBvc3RtYXN0ZXJAM2NvbS5j
b20uIA0K
--=_alternative 002131D7652574E9_=
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0xIGNvbG9yPSM4MDAwODAgZmFjZT0ic2Fucy1zZXJpZiI+LTwvZm9u
dD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+QSBxdWVyeSBvbiBTaXAgY2Fs
bCBmbG93IC08L2ZvbnQ+DQo8YnI+DQo8dWw+DQo8bGk+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMt
c2VyaWYiPlBhcnR5IHNlbmRzIG91dCBJTlZJVEUgd2l0aCBTRFAgaW5mbw0KdG8gcGFydHkgQiB0
byBtYWtlIGEgY2FsbC4gPC9mb250Pg0KPGxpPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlm
Ij5QYXJ0eSBCIHJlY2VpdmVzIHRoZSBtZXNzYWdlIGFuZCBzZW5kcw0KYmFjayAxODMgU2Vzc2lv
biBwcm9ncmVzcyB3aXRoIFNEUCBpbmZvIHRvIHBhcnR5IEEuIEluIHRoZSAxODMgbWVzc2FnZSwN
Cml0IGRvZXMgaGF2ZSBDb250YWN0IGluZm9ybWF0aW9uLjwvZm9udD4NCjxsaT48Zm9udCBzaXpl
PTIgZmFjZT0ic2Fucy1zZXJpZiI+Tm93LCBwYXJ0eSBBIHNlbmRzIG91dCBDQU5DRUwgbWVzc2Fn
ZQ0KdG8gcGFydHkgQiB1c2luZyBjb250YWN0IGhlYWRlciBpbmZvcm1hdGlvbiByZWNlaXZlZCBp
biAxODMgbWVzc2FnZS48L2ZvbnQ+PC91bD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1z
ZXJpZiI+V2lsbCBpdCBiZSB2YWxpZCBpbiBTSVAgdG8gdXNlIENvbnRhY3QNCmluZm9ybWF0aW9u
IGJlZm9yZSByZWNlaXZpbmcgMjAwIE9LIG1lc3NhZ2Ugb3Igbm90ID88L2ZvbnQ+DQoNCjx0YWJs
ZT48dHI+PHRkIGJnY29sb3I9I2ZmZmZmZj48Zm9udCBjb2xvcj0jMDAwMDAwPjxwcmU+Q09ORklE
RU5USUFMSVRZIE5PVElDRTogVGhpcyBlLW1haWwgbWVzc2FnZSwgaW5jbHVkaW5nIGFueSBhdHRh
Y2htZW50cywNCmlzIGJlaW5nIHNlbnQgYnkgM0NvbSBmb3IgdGhlIHNvbGUgdXNlIG9mIHRoZSBp
bnRlbmRlZCByZWNpcGllbnQocykgYW5kDQptYXkgY29udGFpbiBjb25maWRlbnRpYWwsIHByb3By
aWV0YXJ5IGFuZC9vciBwcml2aWxlZ2VkIGluZm9ybWF0aW9uLg0KQW55IHVuYXV0aG9yaXplZCBy
ZXZpZXcsIHVzZSwgZGlzY2xvc3VyZSBhbmQvb3IgZGlzdHJpYnV0aW9uIGJ5IGFueSANCnJlY2lw
aWVudCBpcyBwcm9oaWJpdGVkLiAgSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVu
dCwgcGxlYXNlDQpkZWxldGUgYW5kL29yIGRlc3Ryb3kgYWxsIGNvcGllcyBvZiB0aGlzIG1lc3Nh
Z2UgcmVnYXJkbGVzcyBvZiBmb3JtIGFuZA0KYW55IGluY2x1ZGVkIGF0dGFjaG1lbnRzIGFuZCBu
b3RpZnkgM0NvbSBpbW1lZGlhdGVseSBieSBjb250YWN0aW5nIHRoZQ0Kc2VuZGVyIHZpYSByZXBs
eSBlLW1haWwgb3IgZm9yd2FyZGluZyB0byAzQ29tIGF0IHBvc3RtYXN0ZXJAM2NvbS5jb20uIA0K
PC9wcmU+PC9mb250PjwvdGQ+PC90cj48L3RhYmxlPg==
--=_alternative 002131D7652574E9_=--

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

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


From sip-bounces@ietf.org  Mon Oct 20 23:08:15 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 72F0E3A6869;
	Mon, 20 Oct 2008 23:08:15 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E0A573A6869
	for <sip@core3.amsl.com>; Mon, 20 Oct 2008 23:08:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.204
X-Spam-Level: 
X-Spam-Status: No, score=-6.204 tagged_above=-999 required=5 tests=[AWL=0.044, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id JHUgNcPBDReX for <sip@core3.amsl.com>;
	Mon, 20 Oct 2008 23:08:12 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 9993B3A6822
	for <sip@ietf.org>; Mon, 20 Oct 2008 23:08:12 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	B232B2112A; Tue, 21 Oct 2008 08:09:22 +0200 (CEST)
X-AuditID: c1b4fb3c-aa8c7bb0000015b5-5d-48fd720e2411
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	39FE5210FC; Tue, 21 Oct 2008 08:09:18 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 08:09:17 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 21 Oct 2008 08:09:17 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF08822352@esealmw113.eemea.ericsson.se>
In-Reply-To: <OF204F420F.568E20D7-ON652574E9.00212F67-652574E9.002131E2@3com.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Sip query
Thread-Index: AckzQoaQbJi8y7i6QMq/BOfZNCLJBgAAOSqA
References: <OF204F420F.568E20D7-ON652574E9.00212F67-652574E9.002131E2@3com.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: <Udit_Goyal@3com.com>, <sip-implementors@cs.columbia.edu>, <sip@ietf.org>
X-OriginalArrivalTime: 21 Oct 2008 06:09:17.0712 (UTC)
	FILETIME=[8CEFC900:01C93343]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] Sip query
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0377557526=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0377557526==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C93343.8C9DE2F1"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C93343.8C9DE2F1
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,
=20
If the UAC is sending non-CANCEL requests (INFO, PRACK, UPDATE,
re-INVITE etc) before 200 OK it would use the Contact information.
=20
Regards,
=20
Christer

________________________________

From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Udit_Goyal@3com.com
Sent: 21. lokakuuta 2008 9:03
To: sip-implementors@cs.columbia.edu; sip@ietf.org
Subject: [Sip] Sip query



-=20
A query on Sip call flow -=20


*	Party sends out INVITE with SDP info to party B to make a call.=20
*	Party B receives the message and sends back 183 Session progress
with SDP info to party A. In the 183 message, it does have Contact
information.=20
*	Now, party A sends out CANCEL message to party B using contact
header information received in 183 message.


Will it be valid in SIP to use Contact information before receiving 200
OK message or not ?=20
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is being sent by 3Com for the sole use of the intended recipient(s) and
may contain confidential, proprietary and/or privileged information.
Any unauthorized review, use, disclosure and/or distribution by any=20
recipient is prohibited.  If you are not the intended recipient, please
delete and/or destroy all copies of this message regardless of form and
any included attachments and notify 3Com immediately by contacting the
sender via reply e-mail or forwarding to 3Com at postmaster@3com.com.=20


------_=_NextPart_001_01C93343.8C9DE2F1
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16711" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D151210806-21102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D151210806-21102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D151210806-21102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>If the UAC is sending non-CANCEL requests =
(INFO, PRACK,=20
UPDATE, re-INVITE etc) before 200 OK it would use the Contact=20
information.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D151210806-21102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D151210806-21102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D151210806-21102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D151210806-21102008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Christer</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> sip-bounces@ietf.org=20
[mailto:sip-bounces@ietf.org] <B>On Behalf Of=20
</B>Udit_Goyal@3com.com<BR><B>Sent:</B> 21. lokakuuta 2008 =
9:03<BR><B>To:</B>=20
sip-implementors@cs.columbia.edu; sip@ietf.org<BR><B>Subject:</B> [Sip] =
Sip=20
query<BR></FONT><BR></DIV>
<DIV></DIV><BR><FONT face=3Dsans-serif color=3D#800080 size=3D1>-</FONT> =
<BR><FONT=20
face=3Dsans-serif size=3D2>A query on Sip call flow -</FONT> <BR>
<UL>
  <LI><FONT face=3Dsans-serif size=3D2>Party sends out INVITE with SDP =
info to party=20
  B to make a call. </FONT>
  <LI><FONT face=3Dsans-serif size=3D2>Party B receives the message and =
sends back=20
  183 Session progress with SDP info to party A. In the 183 message, it =
does=20
  have Contact information.</FONT>=20
  <LI><FONT face=3Dsans-serif size=3D2>Now, party A sends out CANCEL =
message to=20
  party B using contact header information received in 183=20
message.</FONT></LI></UL><BR><FONT face=3Dsans-serif size=3D2>Will it be =
valid in=20
SIP to use Contact information before receiving 200 OK message or not =
?</FONT>=20
<TABLE>
  <TBODY>
  <TR>
    <TD bgColor=3D#ffffff><FONT color=3D#000000><PRE>CONFIDENTIALITY =
NOTICE: This e-mail message, including any attachments,
is being sent by 3Com for the sole use of the intended recipient(s) and
may contain confidential, proprietary and/or privileged information.
Any unauthorized review, use, disclosure and/or distribution by any=20
recipient is prohibited.  If you are not the intended recipient, please
delete and/or destroy all copies of this message regardless of form and
any included attachments and notify 3Com immediately by contacting the
sender via reply e-mail or forwarding to 3Com at postmaster@3com.com.=20
</PRE></FONT></TD></TR></TBODY></TABLE></BODY></HTML>

------_=_NextPart_001_01C93343.8C9DE2F1--

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

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


From sip-bounces@ietf.org  Mon Oct 20 23:28:31 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 62ECA3A6869;
	Mon, 20 Oct 2008 23:28:31 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D133A3A6822
	for <sip@core3.amsl.com>; Mon, 20 Oct 2008 23:28:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5
	tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	J_CHICKENPOX_56=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id j8-y41bo7+la for <sip@core3.amsl.com>;
	Mon, 20 Oct 2008 23:28:24 -0700 (PDT)
Received: from jaguar.aricent.com (jaguar.aricent.com [121.241.96.11])
	by core3.amsl.com (Postfix) with ESMTP id C82C43A67E5
	for <sip@ietf.org>; Mon, 20 Oct 2008 23:28:22 -0700 (PDT)
Received: from jaguar.aricent.com (localhost [127.0.0.1])
	by jaguar.aricent.com (8.13.8/8.13.8) with ESMTP id m9L6INRS006665
	for <sip@ietf.org>; Tue, 21 Oct 2008 11:48:23 +0530
Received: from GUREXHT02.ASIAN.AD.ARICENT.COM (gurexht02.asian.ad.aricent.com
	[10.203.171.138])
	by jaguar.aricent.com (8.13.8/8.13.8) with ESMTP id m9L6INtI006622
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL);
	Tue, 21 Oct 2008 11:48:23 +0530
Received: from GUREXMB01.asian.ad.aricent.com ([10.203.171.130]) by
	GUREXHT02.ASIAN.AD.ARICENT.COM ([10.203.171.138]) with mapi;
	Tue, 21 Oct 2008 11:52:52 +0530
From: Tarun2 Gupta <tarun2.gupta@aricent.com>
To: "Udit_Goyal@3com.com" <Udit_Goyal@3com.com>,
	"sip-implementors@cs.columbia.edu" <sip-implementors@cs.columbia.edu>, 
	"sip@ietf.org" <sip@ietf.org>
Date: Tue, 21 Oct 2008 11:53:30 +0530
Thread-Topic: [Sip] Sip query
Thread-Index: AckzQoYuagrNm5JgQvyeIiP4C2GD3wAAuO9A
Message-ID: <63CB5B3FE7915949AC981D0309B35A9809AF9F5009@GUREXMB01.ASIAN.AD.ARICENT.COM>
References: <OF204F420F.568E20D7-ON652574E9.00212F67-652574E9.002131E2@3com.com>
In-Reply-To: <OF204F420F.568E20D7-ON652574E9.00212F67-652574E9.002131E2@3com.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Subject: Re: [Sip] Sip query
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1648087746=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

--===============1648087746==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_63CB5B3FE7915949AC981D0309B35A9809AF9F5009GUREXMB01ASIA_"

--_000_63CB5B3FE7915949AC981D0309B35A9809AF9F5009GUREXMB01ASIA_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Udit

Pls refer Section 9.1 Client Behavior of RFC 3261

"Once the CANCEL is constructed, the client SHOULD check whether it has rec=
eived any response (provisional
or final) for the request being cancelled (herein referred to as the "origi=
nal request").
If no provisional response has been received, the CANCEL request MUST NOT b=
e sent; rather, the client
MUST wait for the arrival of a provisional response before sending the requ=
est. If the original request has
generated a final response, the CANCEL SHOULD NOT be sent, as it is an effe=
ctive no-op, since CANCEL
has no effect on requests that have already generated a final response. Whe=
n the client decides to send the
CANCEL, it creates a client transaction for the CANCEL and passes it the CA=
NCEL request along with
the destination address, port, and transport. The destination address, port=
, and transport for the CANCEL
MUST be identical to those used to send the original request."

Regards,
Tarun

________________________________
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of Udit_=
Goyal@3com.com
Sent: Tuesday, October 21, 2008 11:33 AM
To: sip-implementors@cs.columbia.edu; sip@ietf.org
Subject: [Sip] Sip query


-
A query on Sip call flow -

 *   Party sends out INVITE with SDP info to party B to make a call.
 *   Party B receives the message and sends back 183 Session progress with =
SDP info to party A. In the 183 message, it does have Contact information.
 *   Now, party A sends out CANCEL message to party B using contact header =
information received in 183 message.

Will it be valid in SIP to use Contact information before receiving 200 OK =
message or not ?

CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,

is being sent by 3Com for the sole use of the intended recipient(s) and

may contain confidential, proprietary and/or privileged information.

Any unauthorized review, use, disclosure and/or distribution by any

recipient is prohibited.  If you are not the intended recipient, please

delete and/or destroy all copies of this message regardless of form and

any included attachments and notify 3Com immediately by contacting the

sender via reply e-mail or forwarding to 3Com at postmaster@3com.com.



________________________________
"DISCLAIMER: This message is proprietary to Aricent and is intended solely =
for the use of the individual to whom it is addressed. It may contain privi=
leged or confidential information and should not be circulated or used for =
any purpose other than for what it is intended. If you have received this m=
essage in error,please notify the originator immediately. If you are not th=
e intended recipient, you are notified that you are strictly prohibited fro=
m using, copying, altering, or disclosing the contents of this message. Ari=
cent accepts no responsibility for loss or damage arising from the use of t=
he information transmitted by this email including damage from virus."

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:oa=3D"urn:schemas-microsoft-com:office:activation" xmlns:html=3D"http://ww=
w.w3.org/TR/REC-html40" xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope=
/" xmlns:D=3D"DAV:" xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2=
003/xml" xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xm=
lns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:d=
s=3D"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.micros=
oft.com/sharepoint/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc"=
 xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas=
.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.or=
g/2001/04/xmlenc#" xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xm=
lns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http=
://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf=3D"http://schemas.micros=
oft.com/data/udc/xmlfile" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:sans-serif;
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1854109741;
	mso-list-template-ids:973271434;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"Section1">
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">Hi Udit<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">Pls refer
<b><span style=3D"font-weight:bold">Section 9.1 Client Behavior of RFC 3261=
<o:p></o:p></span></b></span></font></p>
<p class=3D"MsoNormal"><b><font size=3D"2" face=3D"Arial"><span style=3D"fo=
nt-size:10.0pt;
font-family:Arial;font-weight:bold"><o:p>&nbsp;</o:p></span></font></b></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">&#8220;Once the CANCEL is constructed, the client SHOULD=
 check whether it has received any response (provisional<o:p></o:p></span><=
/font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">or final) for the request being cancelled (herein referr=
ed to as the &#8220;original request&#8221;).<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">If no provisional response has been received, the CANCEL=
 request MUST NOT be sent; rather, the client<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">MUST wait for the arrival of a provisional response befo=
re sending the request. If the original request has<o:p></o:p></span></font=
></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">generated a final response, the CANCEL SHOULD NOT be sen=
t, as it is an effective no-op, since CANCEL<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">has no effect on requests that have already generated a =
final response. When the client decides to send the<o:p></o:p></span></font=
></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">CANCEL, it creates a client transaction for the CANCEL a=
nd passes it the CANCEL request along with<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">the destination address, port, and transport.
<font color=3D"blue"><span style=3D"color:blue">The destination address, po=
rt, and transport for the CANCEL<o:p></o:p></span></font></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"blue" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:blue">MUST be identical to those used to sen=
d the original request</span></font><font size=3D"2" face=3D"Arial"><span s=
tyle=3D"font-size:10.0pt;font-family:Arial">.&#8221;<o:p></o:p></span></fon=
t></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">Regards,<o:p></o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"2" face=3D"Arial"><span style=3D"font-=
size:10.0pt;
font-family:Arial">Tarun</span></font><o:p></o:p></p>
<p class=3D"MsoNormal"><font size=3D"2" color=3D"navy" face=3D"Arial"><span=
 style=3D"font-size:
10.0pt;font-family:Arial;color:navy"><o:p>&nbsp;</o:p></span></font></p>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><font=
 size=3D"3" face=3D"Times New Roman"><span style=3D"font-size:12.0pt">
<hr size=3D"2" width=3D"100%" align=3D"center" tabindex=3D"-1">
</span></font></div>
<p class=3D"MsoNormal"><b><font size=3D"2" face=3D"Tahoma"><span style=3D"f=
ont-size:10.0pt;
font-family:Tahoma;font-weight:bold">From:</span></font></b><font size=3D"2=
" face=3D"Tahoma"><span style=3D"font-size:10.0pt;font-family:Tahoma"> sip-=
bounces@ietf.org [mailto:sip-bounces@ietf.org]
<b><span style=3D"font-weight:
bold">On Behalf Of </span></b>Udit_Goyal@3com.com<br>
<b><span style=3D"font-weight:bold">Sent:</span></b> Tuesday, October 21, 2=
008 11:33 AM<br>
<b><span style=3D"font-weight:bold">To:</span></b> sip-implementors@cs.colu=
mbia.edu; sip@ietf.org<br>
<b><span style=3D"font-weight:bold">Subject:</span></b> [Sip] Sip query</sp=
an></font><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><br>
</span></font><font size=3D"1" color=3D"purple" face=3D"sans-serif"><span s=
tyle=3D"font-size:
7.5pt;font-family:sans-serif;color:purple">-</span></font>
<br>
<font size=3D"2" face=3D"sans-serif"><span style=3D"font-size:10.0pt;font-f=
amily:sans-serif">A query on Sip call flow -</span></font>
<o:p></o:p></p>
<ul type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;
     mso-list:l0 level1 lfo1">
<font size=3D"2" face=3D"sans-serif"><span style=3D"font-size:10.0pt;font-f=
amily:sans-serif">Party sends out INVITE with SDP info to party B to make a=
 call.
</span></font><o:p></o:p></li><li class=3D"MsoNormal" style=3D"mso-margin-t=
op-alt:auto;mso-margin-bottom-alt:auto;
     mso-list:l0 level1 lfo1">
<font size=3D"2" face=3D"sans-serif"><span style=3D"font-size:10.0pt;font-f=
amily:sans-serif">Party B receives the message and sends back 183 Session p=
rogress with SDP info to party A. In the 183 message, it does have Contact =
information.</span></font>
<o:p></o:p></li><li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;ms=
o-margin-bottom-alt:auto;
     mso-list:l0 level1 lfo1">
<font size=3D"2" face=3D"sans-serif"><span style=3D"font-size:10.0pt;font-f=
amily:sans-serif">Now, party A sends out CANCEL message to party B using co=
ntact header information received in 183 message.</span></font><o:p></o:p>
</li></ul>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><br>
</span></font><font size=3D"2" face=3D"sans-serif"><span style=3D"font-size=
:10.0pt;
font-family:sans-serif">Will it be valid in SIP to use Contact information =
before receiving 200 OK message or not ?</span></font>
<o:p></o:p></p>
<table class=3D"MsoNormalTable" border=3D"0" cellpadding=3D"0">
<tbody>
<tr>
<td bgcolor=3D"white" style=3D"background:white;padding:.75pt .75pt .75pt .=
75pt">
<pre><font size=3D"2" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:10.0pt;
  color:black">CONFIDENTIALITY NOTICE: This e-mail message, including any a=
ttachments,<o:p></o:p></span></font></pre>
<pre><font size=3D"2" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:10.0pt;
  color:black">is being sent by 3Com for the sole use of the intended recip=
ient(s) and<o:p></o:p></span></font></pre>
<pre><font size=3D"2" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:10.0pt;
  color:black">may contain confidential, proprietary and/or privileged info=
rmation.<o:p></o:p></span></font></pre>
<pre><font size=3D"2" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:10.0pt;
  color:black">Any unauthorized review, use, disclosure and/or distribution=
 by any <o:p></o:p></span></font></pre>
<pre><font size=3D"2" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:10.0pt;
  color:black">recipient is prohibited.&nbsp; If you are not the intended r=
ecipient, please<o:p></o:p></span></font></pre>
<pre><font size=3D"2" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:10.0pt;
  color:black">delete and/or destroy all copies of this message regardless =
of form and<o:p></o:p></span></font></pre>
<pre><font size=3D"2" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:10.0pt;
  color:black">any included attachments and notify 3Com immediately by cont=
acting the<o:p></o:p></span></font></pre>
<pre><font size=3D"2" color=3D"black" face=3D"Courier New"><span style=3D"f=
ont-size:10.0pt;
  color:black">sender via reply e-mail or forwarding to 3Com at postmaster@=
3com.com. <o:p></o:p></span></font></pre>
</td>
</tr>
</tbody>
</table>
<p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span styl=
e=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"3">&quot;DISCLAIMER: This messa=
ge is proprietary to Aricent and is intended solely for the use of the indi=
vidual to whom it is addressed. It may contain privileged or confidential i=
nformation and should not be circulated or
 used for any purpose other than for what it is intended. If you have recei=
ved this message in error,please notify the originator immediately. If you =
are not the intended recipient, you are notified that you are strictly proh=
ibited from using, copying, altering,
 or disclosing the contents of this message. Aricent accepts no responsibil=
ity for loss or damage arising from the use of the information transmitted =
by this email including damage from virus.&quot;<br>
</font>
</body>
</html>

--_000_63CB5B3FE7915949AC981D0309B35A9809AF9F5009GUREXMB01ASIA_--

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

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


From sip-bounces@ietf.org  Tue Oct 21 00:44:02 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 961F13A6A04;
	Tue, 21 Oct 2008 00:44:02 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 852F23A6A04
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 00:44:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.205
X-Spam-Level: 
X-Spam-Status: No, score=-6.205 tagged_above=-999 required=5 tests=[AWL=0.044, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id TWr0MYPOmkIL for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 00:44:00 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 479D83A68E1
	for <sip@ietf.org>; Tue, 21 Oct 2008 00:44:00 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	F381621031; Tue, 21 Oct 2008 09:45:10 +0200 (CEST)
X-AuditID: c1b4fb3c-ae8cfbb0000015b5-88-48fd88864270
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	6395120022; Tue, 21 Oct 2008 09:45:10 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 09:43:58 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 21 Oct 2008 09:43:57 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0884C04F@esealmw113.eemea.ericsson.se>
In-Reply-To: <C84E0A4ABA6DD74DA5221E0833A35DF30AF1A058@esebe101.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Stupid question on flow use in outbound
Thread-Index: AckwalpNrXwgtdvJS02TBwUFX2qSZwCDNpgQAAw4HeAAKhrrQA==
References: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se>
	<C84E0A4ABA6DD74DA5221E0833A35DF30AF1A058@esebe101.NOE.Nokia.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: <Markus.Isomaki@nokia.com>,
	<dean.willis@softarmor.com>,
	<sip@ietf.org>
X-OriginalArrivalTime: 21 Oct 2008 07:43:58.0237 (UTC)
	FILETIME=[C6CB1CD0:01C93350]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] Stupid question on flow use in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>In what you describe below, you are assuming that in order to use your
super-fast-broadband access for video, you would also have to do your
related SIP transactions over the same interface. In 
>general this is not true, as you could as well run SIP over your
jungle-drum interface while putting the broadband interface addresses in
your SDP. 
>
>But I suppose we are talking about networks where some B2BUAs will get
confused if you try the media from a different IP address from where you
do SIP (although if you have something like a 
>carrier grade NAT between the UA and the B2BUA there is no guarantee
that SIP and RTP would come from the same IP). Perhaps it would be good
enough to use two different instance id's?

It doesn't have to be a B2BUA. It can be any kind of "gate control node"
which will not allow media to pass unless there is an associated SIP
session. 

Regards,

Christer



>-----Original Message-----
>From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of 
>ext Christer Holmberg
>Sent: 20 October, 2008 08:56
>To: Dean Willis; SIP IETF
>Subject: Re: [Sip] Stupid question on flow use in outbound
>
>
>Hi,
>
>>Assume Bob's UA is using outbound and is registered with two flows.  
>>Both flows use the same instance-id. The first flow goes through edge-
>proxy 1 and has reg-id 1. The second flow goes through proxy 2 and has 
>reg-id 2.
>>
>>Both flows are "live" from a keepalive perspective.
>>
>>Alice calls Bob.
>>
>>Which flow gets exercised?
>>
>>Where in Outbound is this described? If it is not in Outbound, is it
>described somewhere else? If it is simply left-to-the-implementation, 
>does this need to be explained somewhere?
>
>I guess it is (for good or bad) left-to-the-implementation.
>
>HOWEVER, one thing which has been discussed, and which I think we 
>SHOULD say something about, is whether it's allowed to use a different 
>set of user capabilities for each flow.
>
>Personally I think it would be useful. For example, I could indicate 
>that I want to receive incoming video calls over my 
>super-fast-broadband access, instead of my slow jungle-drum access.
>
>I don't think we would need very much text for this either. 
>Maybe a note saying something like:
>
>"NOTE: A user MAY register different set of user capabilities (using 
>the mechanism in [ref-to-RFC3840] on each flow, if the user wishes the 
>registrar to choose a particular flow based on caller preferences 
>[ref-to-RFC3841]."
>
>...or something like that.
>
>Regards,
>
>Christer
>
>_______________________________________________
>Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>This list is for NEW development of the core SIP Protocol Use 
>sip-implementors@cs.columbia.edu for questions on current sip Use 
>sipping@ietf.org for new developments on the application of sip
>
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Tue Oct 21 00:51:08 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9A68E3A69D0;
	Tue, 21 Oct 2008 00:51:08 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 137CB3A69D0
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 00:51:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 693otfwyR4BD for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 00:51:07 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id 2E2453A6879
	for <sip@ietf.org>; Tue, 21 Oct 2008 00:51:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 1549524001;
	Tue, 21 Oct 2008 10:52:20 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id GanTKDMyFxeV; Tue, 21 Oct 2008 10:52:18 +0300 (EEST)
Received: from taimen (h157094.gprs.dnafinland.fi [87.93.157.94])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Tue, 21 Oct 2008 10:52:18 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id D50DFAC04F; Tue, 21 Oct 2008 10:52:13 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18685.35373.838455.289828@taimen.test.fi>
Date: Tue, 21 Oct 2008 10:52:13 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF0884C04F@esealmw113.eemea.ericsson.se>
References: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se>
	<C84E0A4ABA6DD74DA5221E0833A35DF30AF1A058@esebe101.NOE.Nokia.com>
	<CA9998CD4A020D418654FCDEF4E707DF0884C04F@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, dean.willis@softarmor.com, Markus.Isomaki@nokia.com
Subject: Re: [Sip] Stupid question on flow use in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > It doesn't have to be a B2BUA. It can be any kind of "gate control node"
 > which will not allow media to pass unless there is an associated SIP
 > session.

then it is the problem with that "gate control node".  of course, it
must be possible to use different ip address for sip and media.

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


From sip-bounces@ietf.org  Tue Oct 21 00:54:09 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0DD0128C103;
	Tue, 21 Oct 2008 00:54:09 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1CA6C28C0FC
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 00:54:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.421
X-Spam-Level: 
X-Spam-Status: No, score=-6.421 tagged_above=-999 required=5 tests=[AWL=0.178, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0iiLDCQ1dqim for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 00:54:07 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 47C8D28C103
	for <sip@ietf.org>; Tue, 21 Oct 2008 00:54:07 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com
	[10.160.244.31])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m9L7sWil017938; Tue, 21 Oct 2008 02:55:16 -0500
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 21 Oct 2008 10:54:49 +0300
Received: from esebe101.NOE.Nokia.com ([172.21.138.215]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 21 Oct 2008 10:54:48 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 21 Oct 2008 10:54:46 +0300
Message-ID: <C84E0A4ABA6DD74DA5221E0833A35DF30AF1A137@esebe101.NOE.Nokia.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF0884C04F@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Stupid question on flow use in outbound
Thread-Index: AckwalpNrXwgtdvJS02TBwUFX2qSZwCDNpgQAAw4HeAAKhrrQAAAJL2g
References: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se>
	<C84E0A4ABA6DD74DA5221E0833A35DF30AF1A058@esebe101.NOE.Nokia.com>
	<CA9998CD4A020D418654FCDEF4E707DF0884C04F@esealmw113.eemea.ericsson.se>
From: <Markus.Isomaki@nokia.com>
To: <christer.holmberg@ericsson.com>, <dean.willis@softarmor.com>,
	<sip@ietf.org>
X-OriginalArrivalTime: 21 Oct 2008 07:54:48.0940 (UTC)
	FILETIME=[4AA482C0:01C93352]
X-Nokia-AV: Clean
Subject: Re: [Sip] Stupid question on flow use in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi,

Christer Holmberg wrote:
>>
>>But I suppose we are talking about networks where some B2BUAs will get
>confused if you try the media from a different IP address from 
>where you do SIP (although if you have something like a 
>>carrier grade NAT between the UA and the B2BUA there is no guarantee
>that SIP and RTP would come from the same IP). Perhaps it 
>would be good enough to use two different instance id's?
>
>It doesn't have to be a B2BUA. It can be any kind of "gate 
>control node"
>which will not allow media to pass unless there is an 
>associated SIP session. 
>

Yes, but I think such a node will need some information about SIP
sessions and that is given by a B2BUA-ish element (since it needs to dig
into SDP). But OK, the bottom line is that some folks claim they want to
deploy SIP in such a way that media and signaling are strongly
associated like that. Do you know if a lot of them are *really* doing it
too?

>Regards,
>
>Christer
>

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


From sip-bounces@ietf.org  Tue Oct 21 00:56:12 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B884C3A6ABF;
	Tue, 21 Oct 2008 00:56:12 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 76C313A6A04
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 00:56:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.906
X-Spam-Level: 
X-Spam-Status: No, score=-5.906 tagged_above=-999 required=5
	tests=[AWL=-0.257, BAYES_00=-2.599, HELO_EQ_SE=0.35,
	J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nH7ANUnv0JYp for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 00:56:10 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 344BD3A69E7
	for <sip@ietf.org>; Tue, 21 Oct 2008 00:56:10 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	0797B2245C; Tue, 21 Oct 2008 09:57:20 +0200 (CEST)
X-AuditID: c1b4fb3e-ab68abb000007a96-27-48fd8a6a7498
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	6F203224D6; Tue, 21 Oct 2008 09:53:14 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 09:53:06 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 21 Oct 2008 09:53:04 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0884C0EC@esealmw113.eemea.ericsson.se>
In-Reply-To: <7A726F54F791494C8D8C87F13736E80EFF95C8@vaebe106.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckpErqAvb04oxeFTuK4/n1kThR9egATKlVwAnew/bAABMZkoA==
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18665.43684.176244.988653@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se><18665.59	269.640606.477292@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se><48EBC88B.2030300@cisco.com>	<46101DEA-677B-4F2!
	8-AD1E-32F6438! 5! ! 85 35@so ft ar
	mor.com	><5D1A7985295922448D5550C94DE29180023B048B@DEEXC1U01.de.lucent.com><1ECE0EB50388174790F9694F77522CCF199DA2EB@zrc2hxm0.corp.nortel.com><18668.22818.736346.883984@taimen.test.fi>
	<1ECE0EB50388174790F9694F77522CCF19A212A1@zrc2hxm0.corp.nortel.com>
	<7A726F54F791494C8D8C87F13736E80EFF95C8@vaebe106.NOE.Nokia.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: <Erkki.Koivusalo@nokia.com>,
	<audet@nortel.com>,
	<jh@tutpro.com>
X-OriginalArrivalTime: 21 Oct 2008 07:53:06.0138 (UTC)
	FILETIME=[0D5E2BA0:01C93352]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, pkyzivat@cisco.com, drage@alcatel-lucent.com,
	dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>I proposed to split Outbound to two drafts along with those
>lines:
>a) flow keepalive draft
>b) multiple registration draft
>
>Interestingly enough I find the proposed flow keepalive draft
>to highly correlate to the Outbound original requirements
>(from Keith's recent email):
>
>   1.  Must be able to detect that a UA supports these mechanisms.
>   2.  Support UAs behind NATs.
>   3.  Support TLS to a UA without a stable DNS name or IP address.
>   4.  Detect failure of a connection and be able to correct for this.
>   5.  Support many UAs simultaneously rebooting.
>   6.  Support a NAT rebooting or resetting.
>   7.  Minimize initial startup load on a proxy.
>   8.  Support architectures with edge proxies.
>
>On the other hand, the multiple reg draft does not have any direct
>relation to these requirements, even if you could argue multiple
>registrations would be needed to make the solution more robust
>against NAT reboots (item 6). To me it really attacks SIP proxy
>reboots or any network failures for multihomed UAs, something
>_not_ within the original requirements of Outbound.

Isn't the second part ("be able to correct for this") of item 4 related
to Outbound?


>>I think what it means, is NOT using "Supported: outbound", but using 
>>the +sip.instance and reg-id in the REGISTER. Perhaps with a different
>>"Support: redundant-registrations" or whatever.
>>
>>The reg-ids will distinguish the multiple registrations. The 
>>+sip.instance will correlate them.
>
>The only real difference between our proposals is that you
>suggest usage of +sip.instance and reg-id to be defined in
>a rather similar way in two drafts: Outbound and a new one.

I personally think that the definition of instance-id belongs to the
gruu spec.

But, I assume that has been discussed before, so...

>I was proposing to move all that stuff to another draft so
>that implementations could implement support for keepalives
>and multiple registration either separately or combined,
>depending on the problems they try to solve.

To me the main problem is not that the keepalives are defined in
Outbound, but that it is currently not possible to negotiate the usage
of them without Outbound. But, the intention of the keep draft is to
solve that.

Regards,

Christer













>-----Original Message-----
>From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
>Behalf Of ext Francois Audet
>Sent: 08.October.2008 19:48
>To: Juha Heinanen
>Cc: sip@ietf.org; Paul Kyzivat; Christer Holmberg; DRAGE,Keith 
>(Keith); Dean Willis
>Subject: Re: [Sip] Dual registration without Outbound
>
>No.
>
>I'm saying a new draft on redundant registration is needed, 
>and we can leave
>outbound AS IS.
>
>I thought about this more.
>
>I think what it means, is NOT using "Supported: outbound", but using 
>the +sip.instance and reg-id in the REGISTER. Perhaps with a different
>"Support: redundant-registrations" or whatever.
>
>The reg-ids will distinguish the multiple registrations. The 
>+sip.instance
>will correlate them.
>
>This will be in line with what we did with GRUU which also can use the
>+sip.instance.
>
>A new draft describing this should be fairly simple to do, and 
>we wouldn't
>derail the process, and it would be very much in line with 
>sip-outbound.
>
>Makes sense?
>
>> -----Original Message-----
>> From: Juha Heinanen [mailto:jh@tutpro.com] 
>> Sent: Tuesday, October 07, 2008 23:54
>> To: Audet, Francois (SC100:3055)
>> Cc: DRAGE, Keith (Keith); Dean Willis; Paul Kyzivat; 
>> sip@ietf.org; Christer Holmberg
>> Subject: Re: [Sip] Dual registration without Outbound
>> 
>> Francois Audet writes:
>> 
>>  > Rather, I think this should be a new draft, and it should 
>> be  > independent from outbound.
>> 
>> so do you now finally agree to base outbound drfat on two new 
>> drafts that are also independent of outbound: dialog 
>> connection re-use and keepalive?
>> 
>> -- juha
>> 
>_______________________________________________
>Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>This list is for NEW development of the core SIP Protocol
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sipping@ietf.org for new developments on the application of sip
>
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Tue Oct 21 01:06:10 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 089F23A6B36;
	Tue, 21 Oct 2008 01:06:10 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D93463A6B3C
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 01:06:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.203
X-Spam-Level: 
X-Spam-Status: No, score=-6.203 tagged_above=-999 required=5 tests=[AWL=0.046, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5WG2DrbZU4CR for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 01:06:07 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 0D4EE3A6B36
	for <sip@ietf.org>; Tue, 21 Oct 2008 01:06:06 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	1409122732; Tue, 21 Oct 2008 10:05:10 +0200 (CEST)
X-AuditID: c1b4fb3e-aae89bb000007a96-26-48fd8c3ebb5c
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	BE73C22453; Tue, 21 Oct 2008 10:01:02 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 09:59:48 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 21 Oct 2008 09:59:48 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0884C141@esealmw113.eemea.ericsson.se>
In-Reply-To: <18685.35373.838455.289828@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Stupid question on flow use in outbound
Thread-Index: AckzUfLNCY0W84DzQtquZR6DdyxF5QAANEkg
References: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se><C84E0A4ABA6DD74DA5221E0833A35DF30AF1A058@esebe101.NOE.Nokia.com><CA9998CD4A020D418654FCDEF4E707DF0884C04F@esealmw113.eemea.ericsson.se>
	<18685.35373.838455.289828@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 21 Oct 2008 07:59:48.0750 (UTC)
	FILETIME=[FD57E2E0:01C93352]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, dean.willis@softarmor.com, Markus.Isomaki@nokia.com
Subject: Re: [Sip] Stupid question on flow use in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>It doesn't have to be a B2BUA. It can be any kind of "gate control
node"
>>which will not allow media to pass unless there is an associated SIP
session.
>
>then it is the problem with that "gate control node".  of course, it
must be possible to use different ip address for sip and media.

I was referring to the case when signalling and media is transported on
completely different access networks, via different B2BUA/gates/etc.

If signalling and media is transported on the same access networks, they
can in many cases have different IP address and/or port.

Regards,

Christer

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


From sip-bounces@ietf.org  Tue Oct 21 01:14:40 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6ACFE3A6B4B;
	Tue, 21 Oct 2008 01:14:40 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AE1FE3A6B44
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 01:14:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Q09cogxAbESb for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 01:14:30 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id D44133A6B52
	for <sip@ietf.org>; Tue, 21 Oct 2008 01:14:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 3A0B51EC01B;
	Tue, 21 Oct 2008 11:15:32 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LD9btZ90-+Bk; Tue, 21 Oct 2008 11:15:29 +0300 (EEST)
Received: from taimen (h157094.gprs.dnafinland.fi [87.93.157.94])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Tue, 21 Oct 2008 11:15:29 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 80446AC04C; Tue, 21 Oct 2008 11:15:25 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18685.36765.490403.95747@taimen.test.fi>
Date: Tue, 21 Oct 2008 11:15:25 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF0884C141@esealmw113.eemea.ericsson.se>
References: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se>
	<C84E0A4ABA6DD74DA5221E0833A35DF30AF1A058@esebe101.NOE.Nokia.com>
	<CA9998CD4A020D418654FCDEF4E707DF0884C04F@esealmw113.eemea.ericsson.se>
	<18685.35373.838455.289828@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF0884C141@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, dean.willis@softarmor.com, Markus.Isomaki@nokia.com
Subject: Re: [Sip] Stupid question on flow use in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > I was referring to the case when signalling and media is transported on
 > completely different access networks, via different B2BUA/gates/etc.
 > 
 > If signalling and media is transported on the same access networks, they
 > can in many cases have different IP address and/or port.

they should be able to use different access networks too.  that kind of
restriction cannot be placed on any sip protocol component.  if someone
wants to deploy such gates, they better buy ones that talk to each
other.  there is nothing new in this.

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


From sip-bounces@ietf.org  Tue Oct 21 01:48:21 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DC06A3A6AB4;
	Tue, 21 Oct 2008 01:48:21 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7D93A3A6AB4
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 01:48:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.239
X-Spam-Level: 
X-Spam-Status: No, score=-6.239 tagged_above=-999 required=5
	tests=[AWL=-0.240, BAYES_00=-2.599, J_CHICKENPOX_55=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id d1YlGMvOQx3E for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 01:48:19 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 584053A69CC
	for <sip@ietf.org>; Tue, 21 Oct 2008 01:48:19 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com
	[10.160.244.31])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m9L8nLiA005300; Tue, 21 Oct 2008 03:49:22 -0500
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 21 Oct 2008 11:48:50 +0300
Received: from vaebe106.NOE.Nokia.com ([10.160.244.67]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 21 Oct 2008 11:48:36 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 21 Oct 2008 11:48:30 +0300
Message-ID: <7A726F54F791494C8D8C87F13736E80EFF9822@vaebe106.NOE.Nokia.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF0884C0EC@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Dual registration without Outbound
Thread-Index: AckpErqAvb04oxeFTuK4/n1kThR9egATKlVwAnew/bAABMZkoAAB5ydg
References: <7C532034-8511-4191-9ABA-02D5C42AC74D@softarmor.com><18665.43684.176244.988653@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88C@esealmw113.eemea.ericsson.se><18665.45965.827982.821183@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F88F@esealmw113.eemea.ericsson.se><CA9998CD4A020D418654FCDEF4E707DF05C0F890@esealmw113.eemea.ericsson.se><18665.47207.397605.244480@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F892@esealmw113.eemea.ericsson.se><18665.48080.859460.802945@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F894@esealmw113.eemea.ericsson.se><18665.49637.47890.122973@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F895@esealmw113.eemea.ericsson.se><18665.51736.268071.502700@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F896@esealmw113.eemea.ericsson.se><18665.59	269.640606.477292@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF05C0F899@esealmw113.eemea.ericsson.se><48EBC88B.2030300@cisco.com>	<46101DEA-677B-4F2!
	8-AD1E-32F6438! !  5! ! 8 5 35@so ft a
	rmor.com	><5D1A7985295922448D5550C94DE29180023B048B@DEEXC1U01.de.lucent.com><1ECE0EB50388174790F9694F77522CCF199DA2EB@zrc2hxm0.corp.nortel.com><18668.22818.736346.883984@taimen.test.fi>
	<1ECE0EB50388174790F9694F77522CCF19A212A1@zrc2hxm0.corp.nortel.com>
	<7A726F54F791494C8D8C87F13736E80EFF95C8@vaebe106.NOE.Nokia.com>
	<CA9998CD4A020D418654FCDEF4E707DF0884C0EC@esealmw113.eemea.ericsson.se>
From: <Erkki.Koivusalo@nokia.com>
To: <christer.holmberg@ericsson.com>, <audet@nortel.com>, <jh@tutpro.com>
X-OriginalArrivalTime: 21 Oct 2008 08:48:36.0565 (UTC)
	FILETIME=[CE750050:01C93359]
X-Nokia-AV: Clean
Cc: sip@ietf.org, pkyzivat@cisco.com, drage@alcatel-lucent.com,
	dean.willis@softarmor.com
Subject: Re: [Sip] Dual registration without Outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi, 

>>On the other hand, the multiple reg draft does not have any direct
>>relation to these requirements, even if you could argue multiple
>>registrations would be needed to make the solution more robust
>>against NAT reboots (item 6). To me it really attacks SIP proxy
>>reboots or any network failures for multihomed UAs, something
>>_not_ within the original requirements of Outbound.
>
>Isn't the second part ("be able to correct for this") of item 4 related
>to Outbound?

>>   4.  Detect failure of a connection and be able to correct for this.

I can read that as a requirement for the UA to re-establish 
flows which the UA detects as failed. The requirement itself
does not say anything about how quickly all that should be
done, but nevertheless the design decision in Outbound was
to add support for multiple flows for redundancy and elimination
of blackout periods for a single flow failure. 

As pointed out earlier, I would have been happier to see that 
solution defined in a separate draft as there is a demand for
a separate multi-registration draft without keepalive support.

Regards,

Erkki

>-----Original Message-----
>From: ext Christer Holmberg [mailto:christer.holmberg@ericsson.com] 
>Sent: 21.October.2008 10:53
>To: Koivusalo Erkki (Nokia-D/Helsinki); audet@nortel.com; jh@tutpro.com
>Cc: sip@ietf.org; pkyzivat@cisco.com; 
>drage@alcatel-lucent.com; dean.willis@softarmor.com
>Subject: RE: [Sip] Dual registration without Outbound
>
>
>Hi, 
>
>>I proposed to split Outbound to two drafts along with those
>>lines:
>>a) flow keepalive draft
>>b) multiple registration draft
>>
>>Interestingly enough I find the proposed flow keepalive draft
>>to highly correlate to the Outbound original requirements
>>(from Keith's recent email):
>>
>>   1.  Must be able to detect that a UA supports these mechanisms.
>>   2.  Support UAs behind NATs.
>>   3.  Support TLS to a UA without a stable DNS name or IP address.
>>   4.  Detect failure of a connection and be able to correct for this.
>>   5.  Support many UAs simultaneously rebooting.
>>   6.  Support a NAT rebooting or resetting.
>>   7.  Minimize initial startup load on a proxy.
>>   8.  Support architectures with edge proxies.
>>
>>On the other hand, the multiple reg draft does not have any direct
>>relation to these requirements, even if you could argue multiple
>>registrations would be needed to make the solution more robust
>>against NAT reboots (item 6). To me it really attacks SIP proxy
>>reboots or any network failures for multihomed UAs, something
>>_not_ within the original requirements of Outbound.
>
>Isn't the second part ("be able to correct for this") of item 4 related
>to Outbound?
>
>
>>>I think what it means, is NOT using "Supported: outbound", but using 
>>>the +sip.instance and reg-id in the REGISTER. Perhaps with a 
>different
>>>"Support: redundant-registrations" or whatever.
>>>
>>>The reg-ids will distinguish the multiple registrations. The 
>>>+sip.instance will correlate them.
>>
>>The only real difference between our proposals is that you
>>suggest usage of +sip.instance and reg-id to be defined in
>>a rather similar way in two drafts: Outbound and a new one.
>
>I personally think that the definition of instance-id belongs to the
>gruu spec.
>
>But, I assume that has been discussed before, so...
>
>>I was proposing to move all that stuff to another draft so
>>that implementations could implement support for keepalives
>>and multiple registration either separately or combined,
>>depending on the problems they try to solve.
>
>To me the main problem is not that the keepalives are defined in
>Outbound, but that it is currently not possible to negotiate the usage
>of them without Outbound. But, the intention of the keep draft is to
>solve that.
>
>Regards,
>
>Christer
>
>
>
>
>
>
>
>
>
>
>
>
>
>>-----Original Message-----
>>From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
>>Behalf Of ext Francois Audet
>>Sent: 08.October.2008 19:48
>>To: Juha Heinanen
>>Cc: sip@ietf.org; Paul Kyzivat; Christer Holmberg; DRAGE,Keith 
>>(Keith); Dean Willis
>>Subject: Re: [Sip] Dual registration without Outbound
>>
>>No.
>>
>>I'm saying a new draft on redundant registration is needed, 
>>and we can leave
>>outbound AS IS.
>>
>>I thought about this more.
>>
>>I think what it means, is NOT using "Supported: outbound", but using 
>>the +sip.instance and reg-id in the REGISTER. Perhaps with a different
>>"Support: redundant-registrations" or whatever.
>>
>>The reg-ids will distinguish the multiple registrations. The 
>>+sip.instance
>>will correlate them.
>>
>>This will be in line with what we did with GRUU which also can use the
>>+sip.instance.
>>
>>A new draft describing this should be fairly simple to do, and 
>>we wouldn't
>>derail the process, and it would be very much in line with 
>>sip-outbound.
>>
>>Makes sense?
>>
>>> -----Original Message-----
>>> From: Juha Heinanen [mailto:jh@tutpro.com] 
>>> Sent: Tuesday, October 07, 2008 23:54
>>> To: Audet, Francois (SC100:3055)
>>> Cc: DRAGE, Keith (Keith); Dean Willis; Paul Kyzivat; 
>>> sip@ietf.org; Christer Holmberg
>>> Subject: Re: [Sip] Dual registration without Outbound
>>> 
>>> Francois Audet writes:
>>> 
>>>  > Rather, I think this should be a new draft, and it should 
>>> be  > independent from outbound.
>>> 
>>> so do you now finally agree to base outbound drfat on two new 
>>> drafts that are also independent of outbound: dialog 
>>> connection re-use and keepalive?
>>> 
>>> -- juha
>>> 
>>_______________________________________________
>>Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>This list is for NEW development of the core SIP Protocol
>>Use sip-implementors@cs.columbia.edu for questions on current sip
>>Use sipping@ietf.org for new developments on the application of sip
>>
>
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Tue Oct 21 04:32:07 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 691623A6B06;
	Tue, 21 Oct 2008 04:32:07 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 547B43A6943
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 04:32:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.203
X-Spam-Level: 
X-Spam-Status: No, score=-6.203 tagged_above=-999 required=5 tests=[AWL=0.046, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id I51MO8gXV60M for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 04:32:04 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 88E973A6909
	for <sip@ietf.org>; Tue, 21 Oct 2008 04:32:04 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	CB58A21435; Tue, 21 Oct 2008 13:33:15 +0200 (CEST)
X-AuditID: c1b4fb3c-ab8c9bb0000015b5-31-48fdbd2c0208
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	BA51721552; Tue, 21 Oct 2008 13:29:48 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 13:28:57 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 21 Oct 2008 13:28:57 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0884CB69@esealmw113.eemea.ericsson.se>
In-Reply-To: <18685.36765.490403.95747@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Stupid question on flow use in outbound
Thread-Index: AckzVTB1rnypjKx+RuySVkmEHwt38wAGuh/Q
References: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se><C84E0A4ABA6DD74DA5221E0833A35DF30AF1A058@esebe101.NOE.Nokia.com><CA9998CD4A020D418654FCDEF4E707DF0884C04F@esealmw113.eemea.ericsson.se><18685.35373.838455.289828@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF0884C141@esealmw113.eemea.ericsson.se>
	<18685.36765.490403.95747@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 21 Oct 2008 11:28:57.0192 (UTC)
	FILETIME=[34CC2E80:01C93370]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, dean.willis@softarmor.com, Markus.Isomaki@nokia.com
Subject: Re: [Sip] Stupid question on flow use in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 

>>I was referring to the case when signalling and media is transported
on  > completely different access networks, via different
B2BUA/gates/etc.
>>
>>If signalling and media is transported on the same access networks,
they  > can in many cases have different IP address and/or port.
>
>they should be able to use different access networks too.  that kind of
restriction cannot be placed on any sip protocol component. 

Yes, it can :)

Regards,

Christer

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


From sip-bounces@ietf.org  Tue Oct 21 04:42:32 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 177533A6B4E;
	Tue, 21 Oct 2008 04:42:32 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F10D63A6B4F
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 04:42:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.204
X-Spam-Level: 
X-Spam-Status: No, score=-6.204 tagged_above=-999 required=5 tests=[AWL=0.045, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vkU58+SxiQ1d for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 04:42:30 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id DD53F3A6B0B
	for <sip@ietf.org>; Tue, 21 Oct 2008 04:42:29 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	69259214B8; Tue, 21 Oct 2008 13:42:47 +0200 (CEST)
X-AuditID: c1b4fb3c-aa8c7bb0000015b5-10-48fdbfeade24
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	44304217E2; Tue, 21 Oct 2008 13:41:30 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 13:41:29 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 21 Oct 2008 13:41:29 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0884CBF2@esealmw113.eemea.ericsson.se>
In-Reply-To: <C84E0A4ABA6DD74DA5221E0833A35DF30AF1A137@esebe101.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Stupid question on flow use in outbound
Thread-Index: AckwalpNrXwgtdvJS02TBwUFX2qSZwCDNpgQAAw4HeAAKhrrQAAAJL2gAAgDcxA=
References: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se>
	<C84E0A4ABA6DD74DA5221E0833A35DF30AF1A058@esebe101.NOE.Nokia.com>
	<CA9998CD4A020D418654FCDEF4E707DF0884C04F@esealmw113.eemea.ericsson.se>
	<C84E0A4ABA6DD74DA5221E0833A35DF30AF1A137@esebe101.NOE.Nokia.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: <Markus.Isomaki@nokia.com>,
	<dean.willis@softarmor.com>,
	<sip@ietf.org>
X-OriginalArrivalTime: 21 Oct 2008 11:41:29.0403 (UTC)
	FILETIME=[F52678B0:01C93371]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] Stupid question on flow use in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>>But I suppose we are talking about networks where some B2BUAs will
get
>>>confused if you try the media from a different IP address from where 
>>>you do SIP (although if you have something like a
>>>carrier grade NAT between the UA and the B2BUA there is no guarantee
>>>that SIP and RTP would come from the same IP). Perhaps it would be
good 
>>>enough to use two different instance id's?
>>
>>It doesn't have to be a B2BUA. It can be any kind of "gate control 
>>node" which will not allow media to pass unless there is an associated
SIP 
>>session.
>
>
>Yes, but I think such a node will need some information about SIP
>sessions and that is given by a B2BUA-ish element (since it needs to
dig
>into SDP).

That is what I meant: the node controlling the gate need the SIP/SDP
information in order to open the gates.

But, if the signalling traverses some other node, in another network,
which has no control over the gate where the media is sent, the gates
won't be opened.

So, you need to make sure that the signalling traverses the node which
controls the gates where the media is to be sent.

>But OK, the bottom line is that some folks claim they want to deploy
SIP in such a way that media and signaling are strongly
>associated like that. Do you know if a lot of them are *really* doing
it too?

I don't know. I am just saying that the signalling needs to traverse the
entities which control the gates where the media is to be sent trough.

Regards,

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


From sip-bounces@ietf.org  Tue Oct 21 04:47:52 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1D6823A6909;
	Tue, 21 Oct 2008 04:47:52 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 880783A6953
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 04:47:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BCTfAkUkOl9e for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 04:47:49 -0700 (PDT)
Received: from tutpro.com (lohi.tutpro.com [192.98.100.2])
	by core3.amsl.com (Postfix) with ESMTP id 8284F3A6B3C
	for <sip@ietf.org>; Tue, 21 Oct 2008 04:47:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 9FE9F1EC30A;
	Tue, 21 Oct 2008 14:49:02 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fmvhaHPklmSk; Tue, 21 Oct 2008 14:49:00 +0300 (EEST)
Received: from taimen (h157094.gprs.dnafinland.fi [87.93.157.94])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Tue, 21 Oct 2008 14:49:00 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 57B4AAC04C; Tue, 21 Oct 2008 14:48:57 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18685.49577.331938.340003@taimen.test.fi>
Date: Tue, 21 Oct 2008 14:48:57 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF0884CBF2@esealmw113.eemea.ericsson.se>
References: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se>
	<C84E0A4ABA6DD74DA5221E0833A35DF30AF1A058@esebe101.NOE.Nokia.com>
	<CA9998CD4A020D418654FCDEF4E707DF0884C04F@esealmw113.eemea.ericsson.se>
	<C84E0A4ABA6DD74DA5221E0833A35DF30AF1A137@esebe101.NOE.Nokia.com>
	<CA9998CD4A020D418654FCDEF4E707DF0884CBF2@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, dean.willis@softarmor.com, Markus.Isomaki@nokia.com
Subject: Re: [Sip] Stupid question on flow use in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > So, you need to make sure that the signalling traverses the node which
 > controls the gates where the media is to be sent.

which does not mean that media needs to travel the same path or use the
same ip address as signalling.

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


From sip-bounces@ietf.org  Tue Oct 21 04:51:54 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 44D2C3A6B4F;
	Tue, 21 Oct 2008 04:51:54 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D28BD3A6B0F
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 04:51:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.204
X-Spam-Level: 
X-Spam-Status: No, score=-6.204 tagged_above=-999 required=5 tests=[AWL=0.045, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jkATl82KTwGa for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 04:51:51 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 00D2F3A6B4B
	for <sip@ietf.org>; Tue, 21 Oct 2008 04:51:50 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	8E05920A4F; Tue, 21 Oct 2008 13:52:33 +0200 (CEST)
X-AuditID: c1b4fb3c-ad0ccbb0000015b5-2d-48fdc281dfa7
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	6B2A32053D; Tue, 21 Oct 2008 13:52:33 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 13:52:33 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 21 Oct 2008 13:52:33 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0884CC9F@esealmw113.eemea.ericsson.se>
In-Reply-To: <18685.49577.331938.340003@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Stupid question on flow use in outbound
Thread-Index: AckzcwQ+EfsHjsr9TZ+iFYX91gYgegAACtSw
References: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se><C84E0A4ABA6DD74DA5221E0833A35DF30AF1A058@esebe101.NOE.Nokia.com><CA9998CD4A020D418654FCDEF4E707DF0884C04F@esealmw113.eemea.ericsson.se><C84E0A4ABA6DD74DA5221E0833A35DF30AF1A137@esebe101.NOE.Nokia.com><CA9998CD4A020D418654FCDEF4E707DF0884CBF2@esealmw113.eemea.ericsson.se>
	<18685.49577.331938.340003@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 21 Oct 2008 11:52:33.0281 (UTC)
	FILETIME=[80DA3710:01C93373]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, dean.willis@softarmor.com, Markus.Isomaki@nokia.com
Subject: Re: [Sip] Stupid question on flow use in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 

>>So, you need to make sure that the signalling traverses the node which
> controls the gates where the media is to be sent.
>
>which does not mean that media needs to travel the same path or use the
same ip address as signalling.

I never said that.

But: if B2BUA-X controls gate-X, and B2BUA-Y controls gate-Y, you need
to make sure both signalling and media reaches X - OR that both media
and signalling reaches Y. 

Regards,

Christer

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


From sip-bounces@ietf.org  Tue Oct 21 04:59:53 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2AFE228C0E8;
	Tue, 21 Oct 2008 04:59:53 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5C8453A6B4B
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 04:59:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1Iz7i5SMQYWZ for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 04:59:50 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id 82B433A6B2F
	for <sip@ietf.org>; Tue, 21 Oct 2008 04:59:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id B95521EC01B;
	Tue, 21 Oct 2008 15:00:43 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 37nRKY5U5xck; Tue, 21 Oct 2008 15:00:41 +0300 (EEST)
Received: from taimen (h157094.gprs.dnafinland.fi [87.93.157.94])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Tue, 21 Oct 2008 15:00:41 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id 47283AC04C; Tue, 21 Oct 2008 15:00:38 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18685.50278.262733.559617@taimen.test.fi>
Date: Tue, 21 Oct 2008 15:00:38 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF0884CC9F@esealmw113.eemea.ericsson.se>
References: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se>
	<C84E0A4ABA6DD74DA5221E0833A35DF30AF1A058@esebe101.NOE.Nokia.com>
	<CA9998CD4A020D418654FCDEF4E707DF0884C04F@esealmw113.eemea.ericsson.se>
	<C84E0A4ABA6DD74DA5221E0833A35DF30AF1A137@esebe101.NOE.Nokia.com>
	<CA9998CD4A020D418654FCDEF4E707DF0884CBF2@esealmw113.eemea.ericsson.se>
	<18685.49577.331938.340003@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF0884CC9F@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, dean.willis@softarmor.com, Markus.Isomaki@nokia.com
Subject: Re: [Sip] Stupid question on flow use in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > But: if B2BUA-X controls gate-X, and B2BUA-Y controls gate-Y, you need
 > to make sure both signalling and media reaches X - OR that both media
 > and signalling reaches Y. 

yes, unless B2BUA-X and B2BUA-Y talk to each other.  my point is that
you cannot write a sip spec that prohibits signalling and media from
using different paths/ip addresses.

if your environment is such that it will not work, then you have to
configure your UA in such a way that it always uses same path/ip
address.  i don't see how this would be a protocol issue.

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


From sip-bounces@ietf.org  Tue Oct 21 05:09:09 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 817D33A6B3C;
	Tue, 21 Oct 2008 05:09:09 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EAE983A6B3C
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 05:09:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.205
X-Spam-Level: 
X-Spam-Status: No, score=-6.205 tagged_above=-999 required=5 tests=[AWL=0.044, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id smNI4G2btUMA for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 05:09:07 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 277C53A6914
	for <sip@ietf.org>; Tue, 21 Oct 2008 05:09:07 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	7FADA20A3F; Tue, 21 Oct 2008 14:09:04 +0200 (CEST)
X-AuditID: c1b4fb3c-ab8c9bb0000015b5-7e-48fdc660d962
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	60231209F1; Tue, 21 Oct 2008 14:09:04 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 14:09:03 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 21 Oct 2008 14:09:03 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0884CD5E@esealmw113.eemea.ericsson.se>
In-Reply-To: <18685.50278.262733.559617@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Stupid question on flow use in outbound
Thread-Index: AckzdKd/A+2r5JdfQU6BzqQ2JIZNhwAANEkw
References: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se><C84E0A4ABA6DD74DA5221E0833A35DF30AF1A058@esebe101.NOE.Nokia.com><CA9998CD4A020D418654FCDEF4E707DF0884C04F@esealmw113.eemea.ericsson.se><C84E0A4ABA6DD74DA5221E0833A35DF30AF1A137@esebe101.NOE.Nokia.com><CA9998CD4A020D418654FCDEF4E707DF0884CBF2@esealmw113.eemea.ericsson.se><18685.49577.331938.340003@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF0884CC9F@esealmw113.eemea.ericsson.se>
	<18685.50278.262733.559617@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 21 Oct 2008 12:09:03.0798 (UTC)
	FILETIME=[CF3F1D60:01C93375]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, dean.willis@softarmor.com, Markus.Isomaki@nokia.com
Subject: Re: [Sip] Stupid question on flow use in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 
>>But: if B2BUA-X controls gate-X, and B2BUA-Y controls gate-Y, you need
to make sure both signalling and media reaches X - OR that both media
and signalling reaches Y. 
>
>yes, unless B2BUA-X and B2BUA-Y talk to each other.

Sure.

>my point is that you cannot write a sip spec that prohibits signalling
and media from using different paths/ip addresses.
>
>if your environment is such that it will not work, then you have to
configure your UA in such a way that it always uses same path/ip
address.  i don't see how this would be a protocol issue.

The initial point was that it should be allowed to register different
capabilities per flow - in case there are use-cases and architectures
where it could be useful.

Regards,

Christer

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


From sip-bounces@ietf.org  Tue Oct 21 05:25:10 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 10AEA3A67A4;
	Tue, 21 Oct 2008 05:25:09 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4DDD03A6958
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 05:25:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 40fLFyJ-wfh4 for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 05:25:06 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id CB7543A67A4
	for <sip@ietf.org>; Tue, 21 Oct 2008 05:25:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 4356C1EC01B;
	Tue, 21 Oct 2008 15:26:11 +0300 (EEST)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id yX1RFZCUbX-X; Tue, 21 Oct 2008 15:26:04 +0300 (EEST)
Received: from taimen (h157094.gprs.dnafinland.fi [87.93.157.94])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Tue, 21 Oct 2008 15:26:04 +0300 (EEST)
Received: by taimen (Postfix, from userid 1000)
	id B5F86AC04C; Tue, 21 Oct 2008 15:26:00 +0300 (EEST)
MIME-Version: 1.0
Message-ID: <18685.51800.710995.365684@taimen.test.fi>
Date: Tue, 21 Oct 2008 15:26:00 +0300
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF0884CD5E@esealmw113.eemea.ericsson.se>
References: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se>
	<C84E0A4ABA6DD74DA5221E0833A35DF30AF1A058@esebe101.NOE.Nokia.com>
	<CA9998CD4A020D418654FCDEF4E707DF0884C04F@esealmw113.eemea.ericsson.se>
	<C84E0A4ABA6DD74DA5221E0833A35DF30AF1A137@esebe101.NOE.Nokia.com>
	<CA9998CD4A020D418654FCDEF4E707DF0884CBF2@esealmw113.eemea.ericsson.se>
	<18685.49577.331938.340003@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF0884CC9F@esealmw113.eemea.ericsson.se>
	<18685.50278.262733.559617@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF0884CD5E@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, dean.willis@softarmor.com, Markus.Isomaki@nokia.com
Subject: Re: [Sip] Stupid question on flow use in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > The initial point was that it should be allowed to register different
 > capabilities per flow - in case there are use-cases and architectures
 > where it could be useful.

and how does that relate to which ip addresses UA uses for signaling and
media?  isn't its UAs internal business?

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


From sip-bounces@ietf.org  Tue Oct 21 05:28:27 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 04D543A69B9;
	Tue, 21 Oct 2008 05:28:27 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1AFE73A6A39
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 05:28:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.205
X-Spam-Level: 
X-Spam-Status: No, score=-6.205 tagged_above=-999 required=5 tests=[AWL=0.044, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id U-Z9ZVEs3tx3 for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 05:28:25 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 499013A69B9
	for <sip@ietf.org>; Tue, 21 Oct 2008 05:28:25 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	2EDC4209D4; Tue, 21 Oct 2008 14:29:37 +0200 (CEST)
X-AuditID: c1b4fb3c-ae8cfbb0000015b5-0c-48fdcb31454c
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	1155F207AF; Tue, 21 Oct 2008 14:29:37 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 14:29:36 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 21 Oct 2008 14:29:36 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0884CE65@esealmw113.eemea.ericsson.se>
In-Reply-To: <18685.51800.710995.365684@taimen.test.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Stupid question on flow use in outbound
Thread-Index: AckzeDScRc7yZUWJSDaXWQRM9N0UIgAAGEKQ
References: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se><C84E0A4ABA6DD74DA5221E0833A35DF30AF1A058@esebe101.NOE.Nokia.com><CA9998CD4A020D418654FCDEF4E707DF0884C04F@esealmw113.eemea.ericsson.se><C84E0A4ABA6DD74DA5221E0833A35DF30AF1A137@esebe101.NOE.Nokia.com><CA9998CD4A020D418654FCDEF4E707DF0884CBF2@esealmw113.eemea.ericsson.se><18685.49577.331938.340003@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF0884CC9F@esealmw113.eemea.ericsson.se><18685.50278.262733.559617@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF0884CD5E@esealmw113.eemea.ericsson.se>
	<18685.51800.710995.365684@taimen.test.fi>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 21 Oct 2008 12:29:36.0204 (UTC)
	FILETIME=[ADD158C0:01C93378]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org, dean.willis@softarmor.com, Markus.Isomaki@nokia.com
Subject: Re: [Sip] Stupid question on flow use in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>The initial point was that it should be allowed to register different
capabilities per flow - in case there are use-cases and architectures
where it could be useful.
>
>and how does that relate to which ip addresses UA uses for signaling
and media? 

I don't know - it wasn't me who brought that up :)

Regards,

Christer

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


From sip-bounces@ietf.org  Tue Oct 21 06:11:43 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2EE173A6979;
	Tue, 21 Oct 2008 06:11:43 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CEF843A6943
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 06:11:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.537
X-Spam-Level: 
X-Spam-Status: No, score=-6.537 tagged_above=-999 required=5 tests=[AWL=0.062, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 30lZYheW8WRW for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 06:11:41 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id DC5383A6A0D
	for <sip@ietf.org>; Tue, 21 Oct 2008 06:11:40 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,457,1220227200"; d="scan'208";a="25145613"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 21 Oct 2008 13:12:07 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9LDC70b025305; 
	Tue, 21 Oct 2008 09:12:07 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9LDC6lh004688;
	Tue, 21 Oct 2008 13:12:07 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 09:12:02 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 09:12:02 -0400
Message-ID: <48FDD521.1020606@cisco.com>
Date: Tue, 21 Oct 2008 09:12:01 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se><C84E0A4ABA6DD74DA5221E0833A35DF30AF1A058@esebe101.NOE.Nokia.com><CA9998CD4A020D418654FCDEF4E707DF0884C04F@esealmw113.eemea.ericsson.se><18685.35373.838455.289828@taimen.test.fi><CA9998CD4A020D418654FCDEF4E707DF0884C141@esealmw113.eemea.ericsson.se>	<18685.36765.490403.95747@taimen.test.fi>
	<CA9998CD4A020D418654FCDEF4E707DF0884CB69@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF0884CB69@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 21 Oct 2008 13:12:02.0215 (UTC)
	FILETIME=[9B5BCB70:01C9337E]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=883; t=1224594727; x=1225458727;
	c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Stupid=20question=20on=20flow=2
	0use=20in=20outbound |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=Gh+xevS7tXEoIb/pS7Akfze5w/ldPHDrbjvl4Qw7Pvw=;
	b=SA8Ugj70z10t4npZNxBwm9/aI4oO9Xi9i9qlj1gql2IlFhRLP3TkctYEBd
	xO9M5Ghxh5tc0qAzobHO9oROfN6aYyVnBJ2V9MJgwsRlvfolFNgz7ChkV822
	6OaeoSDs5I;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: sip@ietf.org, Markus.Isomaki@nokia.com, dean.willis@softarmor.com
Subject: Re: [Sip] Stupid question on flow use in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Christer Holmberg wrote:
>  
> 
>>> I was referring to the case when signalling and media is transported
> on  > completely different access networks, via different
> B2BUA/gates/etc.
>>> If signalling and media is transported on the same access networks,
> they  > can in many cases have different IP address and/or port.
>> they should be able to use different access networks too.  that kind of
> restriction cannot be placed on any sip protocol component. 
> 
> Yes, it can :)

Its hard to argue with that, since there are so many existence proofs. :-(

But I would say "that kind of restriction SHOULD NOT be placed ...".

The end result of that is people with narrow ideas of what they care 
about break the possibility of many interesting and valuable new 
features. Its the "if I can't control it then you can't have it" mentality.

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


From sip-bounces@ietf.org  Tue Oct 21 07:39:15 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 15B353A6AA1;
	Tue, 21 Oct 2008 07:39:15 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CBB153A6AA1
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 07:39:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.538
X-Spam-Level: 
X-Spam-Status: No, score=-6.538 tagged_above=-999 required=5 tests=[AWL=0.061, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OrSNSjO2y8GK for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 07:39:13 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id E19613A6A59
	for <sip@ietf.org>; Tue, 21 Oct 2008 07:39:12 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,458,1220227200"; d="scan'208";a="25159716"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 21 Oct 2008 14:40:23 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9LEeNDO018704; 
	Tue, 21 Oct 2008 10:40:23 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9LEeNS3023914;
	Tue, 21 Oct 2008 14:40:23 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 10:40:23 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 10:40:22 -0400
Message-ID: <48FDE9D6.9020304@cisco.com>
Date: Tue, 21 Oct 2008 10:40:22 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>
X-OriginalArrivalTime: 21 Oct 2008 14:40:22.0825 (UTC)
	FILETIME=[F2C4B190:01C9338A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=591; t=1224600023; x=1225464023;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20draft-ietf-sip-info-events-00=3A=20small=20stuf f
	|Sender:=20
	|To:=20SIP=20IETF=20<sip@ietf.org>,=20Eric=20Burger=20<ebur
	ger@bea.com>; bh=N/hVw0JuayCuDmKlYEd05/LFpD2X6bmzrW7BtHvAUE8=;
	b=k4CSdxwxNGlz+A/ZHx3+6SeWvr3ZQNHtIJZ9+z5lWel6h2SWbr/r0hhH0S
	APREbRIXfR9Tt20YqOibpdRnTmkB4gVY0HiGT4qgyOBSdhLLsphZ2PP9DoGA
	plwGZmy40y;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Subject: [Sip] draft-ietf-sip-info-events-00: small stuff
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Eric,

I like how this is shaping up. But I do see some places where I think 
the specification needs to be tightened up, and some other comments as 
well. I will send separate messages for things that are likely to 
generate conversation. Here is the little stuff that probably won't.

There is an error in the following ABNF. Need to s/"Send/"Recv"/

    Recv-Info           =  "Send-Info" HCOLON Info-package-type
                           *( COMMA Info-package-type )



NIT: There are two places where Package-Info is used rather than 
Info-Package.

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


From sip-bounces@ietf.org  Tue Oct 21 07:41:23 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B1F2A3A6909;
	Tue, 21 Oct 2008 07:41:23 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 445F93A6909
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 07:41:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id wliuKXEOgU8i for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 07:41:22 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id DC8533A68DE
	for <sip@ietf.org>; Tue, 21 Oct 2008 07:41:20 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K9300J0ZFHAUZ@siemenscomms.co.uk> for sip@ietf.org; Tue,
	21 Oct 2008 15:42:33 +0100 (BST)
Date: Tue, 21 Oct 2008 15:41:30 +0100
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <5D1A7985295922448D5550C94DE29180024254D8@DEEXC1U01.de.lucent.com>
To: sip@ietf.org
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D001316999@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] I-D Action:draft-ietf-sip-info-events-00.txt
Thread-Index: AckzCeI5b8p+rS2oRRaGHJzyI9WhlQAAnc4gAB5rJKA=
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <20081020231502.43DCA3A69EF@core3.amsl.com>
	<5D1A7985295922448D5550C94DE29180024254D8@DEEXC1U01.de.lucent.com>
Subject: Re: [Sip] I-D Action:draft-ietf-sip-info-events-00.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Some comments:

"Info Package negotiation is similar, but not the same, as negotiating
   SDP [RFC3264].  It is similar, in that the UAC may offer a set of
   Send-Info and Recv-Info packages in the initial INVITE, the UAS
   offers its set of Send-Info and Recv-Info pacakges in provisional 1xx
   and final 2xx responses, and the UAC may offer a final set of Send-
   Info and Recv-Info packages in the ACK."
This sounds like a 3-way exchange, which is not the same as for SDP. I
believe a 2-way exchange, as for SDP, is intended. This interpretation
seems to be in line with 4.2 and 4.3, but 4.1 seems to suggest a 3-way
handshake. Clarification is needed in several places.

"The
   general rule is before a UA may begin sending INFO methods with a
   given Info Package, the UAC must have first indicated it wants to
   send the Info Package by listing it in a Send-Info header in the most
   recent dialog negotiation and the UAS must have positively indicated
   it is willing to receive the Info Package by listing it in a Recv-
   Info header in the most recent dialog negotiation."
Not necessarily. This only applies before a UAC can begin sending.
Before a UAS can begin sending, the opposite must have happened, i.e.,
the UAS must have indicated willingness to send and the UAC must have
indicated willingness to received.

"Once the UAC and UAS establish an early dialog through a 1xx
   provisional response with To-tags, and the UAC has received a Recv-
   Info header field values from the UAS in the response, the UAC MAY
   send any Info Packages supported by the UAS in an INFO message.  The
   2xx final response updates the state of the supported Info Packages,
   such that the 2xx contains the full and final list of Send-Info and
   Recv-Info Info Packages."
This text does not seem to allow for receipt of a 2xx response without
having received a 1xx provisional response.

"Any proposal to have INFO change
   the state of a SIP call is an architectural error and one MUST NOT
   allow it."
Who or what is "one"? For any normative statement, we have to be clear
to whom or what it applies.

John


> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of DRAGE, Keith (Keith)
> Sent: 21 October 2008 00:39
> To: sip@ietf.org
> Subject: Re: [Sip] I-D Action:draft-ietf-sip-info-events-00.txt
> 
> (As WG chair)
> 
> This is the draft that is supposed to solve all the INFO problems we
> ever had and ever will have in future.
> 
> Note that the current version of the draft obsoletes (replaces) RFC
> 2976, i.e. the existing INFO method documentation.
> 
> There are a couple of open issues in the document where I believe the
> editor's will be initiating discussion shortly - so you may 
> want to wait
> for those on the TBD.
> 
> Otherwise, let the discussion commence. You may want to try and raise
> different issues in different emails, in order to allow these 
> to be kept
> track of.
> 
> Regards
> 
> Keith
> 
> > -----Original Message-----
> > From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> > Behalf Of Internet-Drafts@ietf.org
> > Sent: Tuesday, October 21, 2008 12:15 AM
> > To: i-d-announce@ietf.org
> > Cc: sip@ietf.org
> > Subject: [Sip] I-D Action:draft-ietf-sip-info-events-00.txt
> > 
> > A New Internet-Draft is available from the on-line 
> > Internet-Drafts directories.
> > This draft is a work item of the Session Initiation Protocol 
> > Working Group of the IETF.
> > 
> > 
> > 	Title           : Session Initiation Protocol (SIP) 
> > INFO Method and Package Framework
> > 	Author(s)       : E. Burger, et al.
> > 	Filename        : draft-ietf-sip-info-events-00.txt
> > 	Pages           : 29
> > 	Date            : 2008-10-20
> > 
> > This document defines the new INFO method and a mechanism for 
> > defining, negotiating and exchanging Info Packages that use 
> > the INFO method.  Applications which need to exchange 
> > session-related information within a SIP INVITE-created 
> > dialog use these INFO requests.  This draft addresses issues 
> > and open items from RFC 2976, and replaces it.Conventions 
> > Used in this Document
> > 
> > The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 
> > NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 
> > "OPTIONAL" in this document are to be interpreted as 
> > described in RFC 2119 [RFC2119].
> > 
> > A URL for this Internet-Draft is:
> > 
> http://www.ietf.org/internet-drafts/draft-ietf-sip-info-events-00.txt
> > 
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> > 
> > Below is the data which will enable a MIME compliant mail 
> > reader implementation to automatically retrieve the ASCII 
> > version of the Internet-Draft.
> > 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Tue Oct 21 07:41:29 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 658773A6AA1;
	Tue, 21 Oct 2008 07:41:29 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A37EC3A6AA1
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 07:41:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.539
X-Spam-Level: 
X-Spam-Status: No, score=-6.539 tagged_above=-999 required=5 tests=[AWL=0.060, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9mlz4PSr-C6r for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 07:41:26 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id A4CF13A6A99
	for <sip@ietf.org>; Tue, 21 Oct 2008 07:41:26 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,458,1220227200"; d="scan'208";a="25160128"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 21 Oct 2008 14:42:40 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9LEgeE4020430; 
	Tue, 21 Oct 2008 10:42:40 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9LEghMN024948;
	Tue, 21 Oct 2008 14:42:43 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 10:42:40 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 10:42:39 -0400
Message-ID: <48FDEA5F.5070905@cisco.com>
Date: Tue, 21 Oct 2008 10:42:39 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>
X-OriginalArrivalTime: 21 Oct 2008 14:42:39.0966 (UTC)
	FILETIME=[4482BFE0:01C9338B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1216; t=1224600160;
	x=1225464160; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20draft-ietf-sip-info-events-00=3A=20Your=20Quest
	ions |Sender:=20
	|To:=20SIP=20IETF=20<sip@ietf.org>,=20Eric=20Burger=20<ebur
	ger@bea.com>; bh=SALa9CACf9Dn+4o8S5hb3g4Sd3DLhwJSxy3sg4iYlwc=;
	b=LFxMxs7as+9aGaAGeOBxnWJzbjLV5a6M1VQYoLdDba9VF7acZ9gDxBviyD
	ki2XWJxMSwfcQCvadzpmMsQ/zH425+a4x9AaZDrPpAxE31nz8A2PgKEVntIC
	jLslkJawWm;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Subject: [Sip] draft-ietf-sip-info-events-00: Your Questions
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Eric,

The following are a couple of the questions in the document, with my 
response. I'm saving another one for a separate thread.

       [EDITOR'S NOTE: is not waiting for a dialog to fully establish a
       problem?  Personally, I doubt it.  Even the corner cases, like
       forking, do not bother me.]

Well, you definitely must have an early dialog, even if it was 
established via an unreliable response. But I agree this is not a 
problem. If the UA doesn't want to exchange some package until the call 
is answered, then it can renegotiate that afterwards.

       [EDITOR'S NOTE: I chose 489 as 405 implies a media mis-match and
       501 implies INFO is not supported.  This protocol failure is
       identical to a NOTIFY with an event package the UAS did not
       subscribe to.  We could create a new response code if you have
       problems with "Bad Event" implying there is some link between INFO
       and NOTIFY.  However, I would offer what we are doing is refining
       489 to mean, "received some package in some context that I do not
       understand," where today the possible contexts are INFO and
       NOTIFY.  Work for you?]

Yes.

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


From sip-bounces@ietf.org  Tue Oct 21 07:43:57 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2C2953A6A44;
	Tue, 21 Oct 2008 07:43:57 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 525A33A6AF0
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 07:43:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.54
X-Spam-Level: 
X-Spam-Status: No, score=-6.54 tagged_above=-999 required=5 tests=[AWL=0.059, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id k-dDt4mPm-Hv for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 07:43:50 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id AD6703A6A44
	for <sip@ietf.org>; Tue, 21 Oct 2008 07:43:50 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,458,1220227200"; d="scan'208";a="25128782"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 21 Oct 2008 14:44:41 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9LEie2B021806; 
	Tue, 21 Oct 2008 10:44:41 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9LEielF015145;
	Tue, 21 Oct 2008 14:44:41 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 10:44:40 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 10:44:40 -0400
Message-ID: <48FDEAD8.8010803@cisco.com>
Date: Tue, 21 Oct 2008 10:44:40 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>
X-OriginalArrivalTime: 21 Oct 2008 14:44:40.0575 (UTC)
	FILETIME=[8C6638F0:01C9338B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1367; t=1224600281;
	x=1225464281; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20draft-ietf-sip-info-events-00=3A=20multiple=20p
	ackages=20per=20INFO |Sender:=20
	|To:=20SIP=20IETF=20<sip@ietf.org>,=20Eric=20Burger=20<ebur
	ger@bea.com>; bh=9S8AWRGKjyZGwUSjfCsvSQ7OfzGR8vG3w9ZpjzQMRaA=;
	b=jxo/r+Ne19DZAj2mOZ/di4xrDxAGhZdghIslukx0G2r0FwiOsB6a+iN0Is
	zHQ8GGgaLSe6cU5H3tLiR9rX4QPNy4ksaNFMNFthsaxrE03elfl+ZXW8X2zj
	9cNCHq7eNm;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Subject: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Re the question about multiple packages per INFO:

    There MUST be exactly one Info Package type listed per Info-Package
    header.  Multiple Info-Packages per INFO message are disallowed.

    [EDITOR NOTE: Really?  Why not multiple Info-Packages, in a
    multipart/mime?  Well, I thought of one: it is hard to disambiguate.
    For example, take an INFO message with an Info-Package: key_image,
    caller_picture.  I then have a multipart/mime with, you guessed it,
    an image/jpeg and an image/jpeg.  I would offer we do allow this and
    require the MIME parse order of the body match the order of the Info-
    Package enumerations; if you have too many packages or body parts or
    they do not align, you barf.  However, I timed out on this and thus
    we will have to wait for the next version for me to flesh this out.
    If we do do this, then we'll reference RFC 3261 as updated by
    draft-ietf-sip-body-handling to require multipart MIME handling.]

How about defining an initial package type of "multipart". It allows 
only content-type multipart/mixed. Then each contained type must have 
its own Info-Package header. If you want to allow multiple packages per 
INFO then you need to negotiate support for "multipart". Or maybe we 
require support of multipart if you support any other package type.

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


From sip-bounces@ietf.org  Tue Oct 21 07:44:52 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F1A3A3A6A44;
	Tue, 21 Oct 2008 07:44:51 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7C8393A6A44
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 07:44:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.541
X-Spam-Level: 
X-Spam-Status: No, score=-6.541 tagged_above=-999 required=5 tests=[AWL=0.058, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0SY-COvZch-T for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 07:44:50 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 890763A68DE
	for <sip@ietf.org>; Tue, 21 Oct 2008 07:44:50 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,458,1220227200"; d="scan'208";a="25128987"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 21 Oct 2008 14:46:04 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9LEk4SB025551; 
	Tue, 21 Oct 2008 10:46:04 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9LEk4EG015756;
	Tue, 21 Oct 2008 14:46:04 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 10:45:53 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 10:45:53 -0400
Message-ID: <48FDEB20.9040109@cisco.com>
Date: Tue, 21 Oct 2008 10:45:52 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>
X-OriginalArrivalTime: 21 Oct 2008 14:45:53.0153 (UTC)
	FILETIME=[B7A8BF10:01C9338B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=388; t=1224600364; x=1225464364;
	c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20draft-ietf-sip-info-events-00=3A=20CANCEL???
	|Sender:=20
	|To:=20SIP=20IETF=20<sip@ietf.org>,=20Eric=20Burger=20<ebur
	ger@bea.com>; bh=ADmcHHnaASd0WHszRY6XRNQ4QcyDhamX9ORyeapuB4U=;
	b=a4Fb7Q7WrteY49fKQkYVhIvD0FoZnYUcDFQ5CFboQuIvLtbKvDFy+XPQW9
	5IhV4eoQ6zfMrcmYkX4Q8iHanA10MIVX43i3ymEW3cuXcvRDaHXtf/vbIp0C
	2f512jKK03;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Subject: [Sip] draft-ietf-sip-info-events-00: CANCEL???
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I have a question regarding the following paragraph:

    A UAC MAY CANCEL an INFO request.  A UAS receiving a CANCEL for an
    INFO request SHOULD respond to the INFO with a "487 Request
    Cancelled" response unless the UAC has already sent a final response.
    The UAS then MUST ignore future INFO requests.

Why would the CANCEL affect *future* info requests???


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


From sip-bounces@ietf.org  Tue Oct 21 07:50:17 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2DD283A6916;
	Tue, 21 Oct 2008 07:50:17 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 20F873A6916
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 07:50:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.542
X-Spam-Level: 
X-Spam-Status: No, score=-6.542 tagged_above=-999 required=5 tests=[AWL=0.057, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9A5fan4q3SPs for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 07:50:14 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id F0AAB3A687D
	for <sip@ietf.org>; Tue, 21 Oct 2008 07:50:13 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,458,1220227200"; d="scan'208";a="25129929"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 21 Oct 2008 14:51:23 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9LEpOma029460; 
	Tue, 21 Oct 2008 10:51:24 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9LEpNgD018004;
	Tue, 21 Oct 2008 14:51:24 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 10:51:24 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 10:51:23 -0400
Message-ID: <48FDEC6B.8090006@cisco.com>
Date: Tue, 21 Oct 2008 10:51:23 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>
X-OriginalArrivalTime: 21 Oct 2008 14:51:23.0575 (UTC)
	FILETIME=[7C9B2470:01C9338C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3011; t=1224600685;
	x=1225464685; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20draft-ietf-sip-info-events-00=3A=20package=20ne
	gotiation |Sender:=20
	|To:=20SIP=20IETF=20<sip@ietf.org>,=20Eric=20Burger=20<ebur
	ger@bea.com>; bh=ypxSgImtp9OLB8Vovzk0rkDuFEVoDoBMzJ6P2W4frXI=;
	b=mX+WvSb+JpVeXJmOt8aIMjmSuyN+TELq/HuKxBIdZkAM+Q6u6gG/ACOKwf
	7JXtumvCf/gaMNxaqbYjpnCRyfjkmhwmUIJgyJwDQdJUjg2wDGRH03FZqQhJ
	WmaLt1IctT;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Subject: [Sip] draft-ietf-sip-info-events-00: package negotiation
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

General issues with the negotiation mechanism:

What happens if the initial INVITE by a UAC includes only Send-Info or 
Recv-Info? Does that indicate a "half-legacy" device??? Or does it delay 
negotiation for one but not the other? Or does the presence of one mean 
the absence of the other is equivalent to an empty one?

As I think about it, I don't think its really necessary to treat the 
absence of these headers as meaning "legacy". Treating the absence of 
these headers as equivalent to their presence without any packages is 
sufficient to get the proper legacy behavior. The tricky part is 
figuring out out when their absence *doesn't* mean that, which is 
significant only in the non-legacy case. In particular, when they aren't 
present in INVITE it means deferral of the "offer" to the UAS. And 
possibly absence in an UPDATE means "don't renegotiate"???

I'm confused by the three way negotiation of info packages in 
INVITE/2xx/ACK. Its allowed when the Send-Info/Recv-Info are in the 
INVITE, but not when they are deferred to the INVITE response, or when 
they are conveyed in UPDATE and its response. If the three way handshake 
is needed to seal the deal, then those other options should be off the 
table. But the "deferred offer" of these is really needed, so it can't 
be off the table. Or is this just an extra benefit that can be exploited 
when possible?

Also, I don't see any provision for additional round(s) of negotiation 
before 2xx via PRACK and UPDATE, though there is provision for 
additional "half-negotiations" via provisional responses and the final 
response. Given the parallels with O/A, I'd prefer to see them more 
aligned in this regard, though I can be talked out of that with a good 
argument.

I'd also like to take advantage of the lessons that have been learned 
with O/A and nail down more of the semantics now. One issue that leaps 
to mind in that regard is what happens if we start to negotiate info 
packages in a reINVITE and then the reINVITE fails?

IMO what is needed is a state model for this stuff, added to the state 
for an invite-dialog-usage. This state should determine which packages 
may be sent, and which should be received without error. We should be 
very clear about exactly which events cause changes to this state.

Even then there are race conditions that need to be clarified. For 
instance: Suppose, as a result of an INVITE/1xx exchange between Alice 
and Bob, that packages P & Q are allowed to be sent from Alice to Bob. 
Alice then sends an INFO with package Q, and at the same time Bob sends 
a 2xx that only allows the receipt of package P. Then Bob receives the 
INFO with package Q. What should happen?

Another issue is that if the Send-Info/Recv-Info contents change in 
subsequent 1xx responses to the same INVITE, the UAS has no guarantee 
that they are received. So any reduction in what can be received cannot 
be counted upon until the 2xx/ACK.

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


From sip-bounces@ietf.org  Tue Oct 21 07:51:34 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 415053A6AB4;
	Tue, 21 Oct 2008 07:51:34 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4CD7A3A6A99
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 07:51:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.543
X-Spam-Level: 
X-Spam-Status: No, score=-6.543 tagged_above=-999 required=5 tests=[AWL=0.056, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id O1zPS3RpJQSd for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 07:51:28 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 3FA133A6A70
	for <sip@ietf.org>; Tue, 21 Oct 2008 07:51:28 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,458,1220227200"; d="scan'208";a="25130149"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 21 Oct 2008 14:52:37 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9LEqdfB027627; 
	Tue, 21 Oct 2008 10:52:39 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9LEqfmf028999;
	Tue, 21 Oct 2008 14:52:42 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 10:52:37 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 10:52:37 -0400
Message-ID: <48FDECB5.3030607@cisco.com>
Date: Tue, 21 Oct 2008 10:52:37 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>
References: <20081020231502.43DCA3A69EF@core3.amsl.com>
In-Reply-To: <20081020231502.43DCA3A69EF@core3.amsl.com>
X-OriginalArrivalTime: 21 Oct 2008 14:52:37.0529 (UTC)
	FILETIME=[A8AFA090:01C9338C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1310; t=1224600759;
	x=1225464759; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20draft-ietf-sip-info-events-00=3A=20Legacy=20usa
	ge=20of=20INFO |Sender:=20
	|To:=20SIP=20IETF=20<sip@ietf.org>,=20Eric=20Burger=20<ebur
	ger@bea.com>; bh=tcG7S/5ad0Q67t4jGGK2uGKg1/VWx7+PkIjlcRQMZAI=;
	b=dakYQVmYtOhu3SaIToKtjbx2cprJBd94IjTPPwjFnCwnXc0S59faT/dty1
	Gu/uGFbVI3dRLtu29mu0y1O+qi9oQsvupKmS87AKIVU8dx04b6vPiKrLeowS
	dKa7LiQVoW;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Subject: [Sip] draft-ietf-sip-info-events-00: Legacy usage of INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

While I see rules in 5.1 and 6 that permit use of legacy packages at the 
INFO UAS, I find no rules that permit sending a legacy INFO. I guess it 
must be possible to use legacy INFO even when both sides support this 
new info package mechanism. And I guess the evidence that a UA *doesn't* 
support this new mechanism (by the absence of the headers in 
request/response) is just equivalent to one that explicitly negotiates 
support of no packages.

Regarding registration if INFO packages - I thought we also wanted to 
introduce a registry for legacy usages of INFO, to encourage them to 
come out into the daylight. I guess maybe that would be a separate 
registry, since the key for it will have to be Content-Type. So it 
*could* be established from a different document. But I think this is 
the likely place to do it, since its the place where all the eyeballs 
will be. I think the rule for registering those needs to be that one can 
only be registered if the Content-Type has not already been registered, 
and it was in *use* with INFO prior to this document becoming an RFC. 
(The registration itself could be done later. I guess it would be the 
honor system.) Any usages being deployed after this becomes an RFC would 
be required to use the new mechanism.

	Thanks,
	Paul













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


From sip-bounces@ietf.org  Tue Oct 21 14:30:02 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8BB163A685D;
	Tue, 21 Oct 2008 14:30:02 -0700 (PDT)
X-Original-To: sip@ietf.org
Delivered-To: sip@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 86C293A6804; Tue, 21 Oct 2008 14:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081021213001.86C293A6804@core3.amsl.com>
Date: Tue, 21 Oct 2008 14:30:01 -0700 (PDT)
Cc: sip@ietf.org
Subject: [Sip] I-D Action:draft-ietf-sip-rph-new-namespaces-04.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--NextPart

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


	Title           : IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespaces
	Author(s)       : J. Polk
	Filename        : draft-ietf-sip-rph-new-namespaces-04.txt
	Pages           : 7
	Date            : 2008-10-21

This document creates additional Session Initiation Protocol (SIP)
Resource-Priority namespaces to meet the requirements of the US 
Defense Information Systems Agency, and places these namespaces in 
the IANA registry.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sip-rph-new-namespaces-04.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-sip-rph-new-namespaces-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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


From sip-bounces@ietf.org  Tue Oct 21 14:58:12 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 062083A6BC0;
	Tue, 21 Oct 2008 14:58:12 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 16E3A3A6BBF
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 14:58:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.566
X-Spam-Level: 
X-Spam-Status: No, score=-6.566 tagged_above=-999 required=5 tests=[AWL=0.033, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1mpZm5364QBg for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 14:58:10 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 154023A6BBA
	for <sip@ietf.org>; Tue, 21 Oct 2008 14:58:10 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,460,1220227200"; d="scan'208";a="25216227"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 21 Oct 2008 21:59:11 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9LLxB8U025081; 
	Tue, 21 Oct 2008 17:59:11 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9LLxBVD029484;
	Tue, 21 Oct 2008 21:59:11 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 17:59:11 -0400
Received: from jmpolk-wxp01.cisco.com ([10.82.255.197]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Oct 2008 17:59:10 -0400
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 21 Oct 2008 16:59:09 -0500
To: sip@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Mime-Version: 1.0
Message-ID: <XFE-RTP-201EB4HGXAw0000072c@xfe-rtp-201.amer.cisco.com>
X-OriginalArrivalTime: 21 Oct 2008 21:59:10.0962 (UTC)
	FILETIME=[3F8F9520:01C933C8]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=541; t=1224626351; x=1225490351;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jmpolk@cisco.com;
	z=From:=20=22James=20M.=20Polk=22=20<jmpolk@cisco.com>
	|Subject:=20Rev=20of=20draft-ietf-sip-rph-new-namespaces-04
	|Sender:=20 |To:=20sip@ietf.org;
	bh=9u8L6zcv5LMhn+2DuSketTUEc9iHA6gFmjb4ZIH30Bo=;
	b=ICM0udWDCCNHMUP7WrFw85IMNrEq5N7AVnweHG46EhOMpC01J9OtDJnNbk
	4HZseVlZ2+t7vtUW8NCAe3oU7kRxftT0AGqjd73HAwbyT6/fJWk+GYLAmxfd
	Jhy8ybtKni;
Authentication-Results: rtp-dkim-1; header.From=jmpolk@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
Subject: [Sip] Rev of draft-ietf-sip-rph-new-namespaces-04
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

SIP WG

I've just revved
http://www.ietf.org/internet-drafts/draft-ietf-sip-rph-new-namespaces-04.txt

I made some small fixes that shouldn't have made it through the last 
version, and corrected a larger mistaken - a poorly written 
paraphrase of section 8 of RFC 4412 (dealing with the relative 
priority order defined in that RFC).  I simply deleted that 
paraphrasing, instead referring specifically to section 8 of RFC 4412.

This ID is getting reviewed by the IESG on this Thursday's call.

Comments are welcome

James

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


From sip-bounces@ietf.org  Tue Oct 21 19:16:19 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F26E23A695C;
	Tue, 21 Oct 2008 19:16:18 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BCCC23A690E
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 19:16:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CsZc+TaxjFwr for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 19:16:17 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id C15603A68DC
	for <sip@ietf.org>; Tue, 21 Oct 2008 19:16:16 -0700 (PDT)
Received: from [192.168.1.3] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9M2HSOD025447
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Tue, 21 Oct 2008 21:17:29 -0500
Message-Id: <D9E05E07-FB6A-4C52-A2B8-01ADF96720C5@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF087C4763@esealmw113.eemea.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 21 Oct 2008 21:17:22 -0500
References: <5CFE7D5D-BCA0-49A7-A58C-1291A8F416F6@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF087C4763@esealmw113.eemea.ericsson.se>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Question on non-outbound registrations in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Thank you! That is exactly the sort of "Why this is a MUST" discussion  
I'm talking about.

--
dean


On Oct 20, 2008, at 1:38 AM, Christer Holmberg wrote:

>
> Hi Dean,
>
> How would the keep-alives work for 3rd party registration? How would I
> know that you have registered me, and that I now have to send
> keep-alives (and where I would have to send the keep-alives)?
>
> And, how would you know if the flow that you have registered for me
> fails, in which case you should establish a new flow for me?
>
> Regards,
>
> Christer
>
>
> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
> Dean Willis
> Sent: 17. lokakuuta 2008 17:36
> To: SIP IETF
> Subject: [Sip] Question on non-outbound registrations in outbound
>
> The current draft says:
> 4.2.3.  Non Outbound Registrations
>
>    In an initial registration, a User Agent MUST NOT include a reg-id
>    header parameter in the Contact header field if the registering UA
> is
>    not the same instance as the UA referred to by the target Contact
>    header field.  (This practice is occasionally used to install
>    forwarding policy into registrars.)
>
>    A UAC also MUST NOT include an instance-id feature taf or reg-id
>    Contact header field parameter in a request to un-register all
>    Contacts (a single Contact header field value with the value of
> "*").
>
> This strikes me as odd in several ways.
>
> The reg-id lets us know "which registration we are talking about". The
> instance-id lets us know "which specific UA-appearance we are talking
> about".
> So for a 3rd-party registration, it might be useful to have reg-id or
> instance-id values. Assume for example a voice-mail server that
> registers a low q-value contact for an AOR, so that calls will
> eventually reach it in a no-answer scenario. Withdrawing just those
> specific registrations would seem to require a selection mechanism  
> from
> the set of registrations, and reg-id would appear to satisfy this  
> need.
>
>
> In a different use case, assume a 3rd party registration is used to
> install forwarding policy. The use of an instance-id in such a
> registration would seem to allow the forwarding policy to target one
> specific instance of the set of contacts registered to the target. In
> other words, not "forward the call to sip:bob@example.com", but  
> "forward
> the call to sip:bob@example.com's cell phone".
>
> Now it's entirely possible that neither of these scenarios actually
> work. But I don't see in the discussion of outbound anything about WHY
> they wouldn't work, which means that the requirements language (the  
> MUST
> in outbound) is unsupported. I don't like unsupported requirements  
> in a
> specification.
> --
> Dean
>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use
> sip-implementors@cs.columbia.edu for questions on current sip Use
> sipping@ietf.org for new developments on the application of sip
>

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


From sip-bounces@ietf.org  Tue Oct 21 19:20:21 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5303B3A69DF;
	Tue, 21 Oct 2008 19:20:21 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 94F1F3A69DF
	for <sip@core3.amsl.com>; Tue, 21 Oct 2008 19:20:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id p1QMhmr1+y79 for <sip@core3.amsl.com>;
	Tue, 21 Oct 2008 19:20:19 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id C62893A6906
	for <sip@ietf.org>; Tue, 21 Oct 2008 19:20:10 -0700 (PDT)
Received: from [192.168.1.3] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9M2LDnb025488
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Tue, 21 Oct 2008 21:21:15 -0500
Message-Id: <F9E72953-9068-49F9-A34A-2E50977DC746@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: "Orsic, Milo (Milo)" <orsic@ALCATEL-LUCENT.COM>
In-Reply-To: <1FD3C0CCB36AAA4AAAB874C3898C0B2701AD7249@ILEXC2U03.ndc.lucent.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 21 Oct 2008 21:21:08 -0500
References: <7308C701-904B-450B-81AA-C8E285EAAF09@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF087C463A@esealmw113.eemea.ericsson.se>
	<1FD3C0CCB36AAA4AAAB874C3898C0B2701AD7249@ILEXC2U03.ndc.lucent.com>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Stupid question on flow use in outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 20, 2008, at 9:37 AM, Orsic, Milo (Milo) wrote:

> Hi Christer,
> IMHO outbound should specifies "alternative paths". Here is what I  
> mean by "alternative paths".
>
> Assume that China Airline has two counters (contacts), one only  
> English speaking the other only Chinese spiking. It doesn't matter  
> if you took either the escalator or the elevator to the English  
> speaking counter (the elevator and escalator are alternatives  
> paths).  However, if the elevator gets you to English speaking  
> counter and the escalator gets you to Chinese speaking counter -  
> they are not alternatives.
>
> Hence, you have two choices, i.e. either
> 1. the two alternatives get you to the same counter, or
> 2. make the second counter also English speaking.
> My choices is 1. (e.g. I don't want to be constrained that the  
> alternative contact addresses must be registered with the same  
> feature tags).
>

The English and Chinese counters are different instances, with  
different capabilities tags. They are not the sort of things that  
Outbound considers alternate flows.

Of course, with SIP, you'd be cloned for each counter, with one clone  
put on the elevator, one clone put on on the escalator, and the  
original you discarded into the bit void.

--
Dean

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


From sip-bounces@ietf.org  Wed Oct 22 00:53:04 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 745FD3A6A19;
	Wed, 22 Oct 2008 00:53:04 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F1EED3A6A4D
	for <sip@core3.amsl.com>; Wed, 22 Oct 2008 00:53:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.206
X-Spam-Level: 
X-Spam-Status: No, score=-6.206 tagged_above=-999 required=5 tests=[AWL=0.043, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id MxNOEbEmkZ1e for <sip@core3.amsl.com>;
	Wed, 22 Oct 2008 00:53:02 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id DA64D3A6A19
	for <sip@ietf.org>; Wed, 22 Oct 2008 00:53:01 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	B3BB3215D6; Wed, 22 Oct 2008 09:54:10 +0200 (CEST)
X-AuditID: c1b4fb3e-aef86bb00000537b-f9-48fedc22ef61
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	A18C220109; Wed, 22 Oct 2008 09:54:10 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 09:54:09 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 22 Oct 2008 09:54:09 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
In-Reply-To: <48FDEAD8.8010803@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
Thread-Index: Ackzi6XrNIT2zGxYSj2+GSTrqqgYJAAj0PhQ
References: <48FDEAD8.8010803@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>, "SIP IETF" <sip@ietf.org>,
	"Eric Burger" <eburger@bea.com>
X-OriginalArrivalTime: 22 Oct 2008 07:54:09.0941 (UTC)
	FILETIME=[5DCF7C50:01C9341B]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi,

Doesn't the body handling draft say that one MUST be able to parse
multipart message bodies?

So, I don't think we should forbid the usage of multiple packages. There
MAY be use-cases where it is useful, so...

I also think that the negotiation of multipart support is more generic,
so such mechanism should not be bound to INFO packages.

Regards,

Christer



 

-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Paul Kyzivat
Sent: 21. lokakuuta 2008 17:45
To: SIP IETF; Eric Burger
Subject: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO

Re the question about multiple packages per INFO:

    There MUST be exactly one Info Package type listed per Info-Package
    header.  Multiple Info-Packages per INFO message are disallowed.

    [EDITOR NOTE: Really?  Why not multiple Info-Packages, in a
    multipart/mime?  Well, I thought of one: it is hard to disambiguate.
    For example, take an INFO message with an Info-Package: key_image,
    caller_picture.  I then have a multipart/mime with, you guessed it,
    an image/jpeg and an image/jpeg.  I would offer we do allow this and
    require the MIME parse order of the body match the order of the
Info-
    Package enumerations; if you have too many packages or body parts or
    they do not align, you barf.  However, I timed out on this and thus
    we will have to wait for the next version for me to flesh this out.
    If we do do this, then we'll reference RFC 3261 as updated by
    draft-ietf-sip-body-handling to require multipart MIME handling.]

How about defining an initial package type of "multipart". It allows
only content-type multipart/mixed. Then each contained type must have
its own Info-Package header. If you want to allow multiple packages per
INFO then you need to negotiate support for "multipart". Or maybe we
require support of multipart if you support any other package type.

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


From sip-bounces@ietf.org  Wed Oct 22 00:54:57 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7FF8F3A6A08;
	Wed, 22 Oct 2008 00:54:57 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BAE4C3A6B45
	for <sip@core3.amsl.com>; Wed, 22 Oct 2008 00:54:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.206
X-Spam-Level: 
X-Spam-Status: No, score=-6.206 tagged_above=-999 required=5 tests=[AWL=0.043, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id GwbsaT8+3r-g for <sip@core3.amsl.com>;
	Wed, 22 Oct 2008 00:54:56 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id DBEA63A6A08
	for <sip@ietf.org>; Wed, 22 Oct 2008 00:54:55 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	B344620A0E; Wed, 22 Oct 2008 09:56:10 +0200 (CEST)
X-AuditID: c1b4fb3c-ab8c9bb0000015b5-81-48fedc9aed92
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	98051203C1; Wed, 22 Oct 2008 09:56:10 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 09:56:09 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 22 Oct 2008 09:56:09 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0889E4B3@esealmw113.eemea.ericsson.se>
In-Reply-To: <48FDEB20.9040109@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: CANCEL???
Thread-Index: Ackzi8bLi12MJGK6RJ+KriKm2bNDsQAj6y1Q
References: <48FDEB20.9040109@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>, "SIP IETF" <sip@ietf.org>,
	"Eric Burger" <eburger@bea.com>
X-OriginalArrivalTime: 22 Oct 2008 07:56:09.0922 (UTC)
	FILETIME=[A5532220:01C9341B]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] draft-ietf-sip-info-events-00: CANCEL???
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi,

I have the same question as Paul.

Also, I wonder whether the paragraph is needed in the first place. I
think INFO should follow the normal 3261 procedures as far as CANCEL is
concerned.

I also doubt that a UAS would send a 1xx response for an INFO, and
without that you can't CANCEL, right?

Regards,

Christer

 

-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Paul Kyzivat
Sent: 21. lokakuuta 2008 17:46
To: SIP IETF; Eric Burger
Subject: [Sip] draft-ietf-sip-info-events-00: CANCEL???

I have a question regarding the following paragraph:

    A UAC MAY CANCEL an INFO request.  A UAS receiving a CANCEL for an
    INFO request SHOULD respond to the INFO with a "487 Request
    Cancelled" response unless the UAC has already sent a final
response.
    The UAS then MUST ignore future INFO requests.

Why would the CANCEL affect *future* info requests???


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


From sip-bounces@ietf.org  Wed Oct 22 01:11:31 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8EF903A6B42;
	Wed, 22 Oct 2008 01:11:31 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6C57028C12C
	for <sip@core3.amsl.com>; Wed, 22 Oct 2008 01:11:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.187
X-Spam-Level: 
X-Spam-Status: No, score=-6.187 tagged_above=-999 required=5 tests=[AWL=0.062, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fc5aQw80l2hH for <sip@core3.amsl.com>;
	Wed, 22 Oct 2008 01:11:29 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 2873F3A6A43
	for <sip@ietf.org>; Wed, 22 Oct 2008 01:11:28 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	AD821220C9; Wed, 22 Oct 2008 10:11:07 +0200 (CEST)
X-AuditID: c1b4fb3e-af787bb00000537b-1c-48fee01b4779
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	81039220C3; Wed, 22 Oct 2008 10:11:07 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 10:11:06 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 10:11:06 +0200
Received: from [131.160.37.21] (E000FB0F665DD.lmf.ericsson.se [131.160.37.21])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 4CC012687;
	Wed, 22 Oct 2008 11:11:06 +0300 (EEST)
Message-ID: <48FEE01A.90305@ericsson.com>
Date: Wed, 22 Oct 2008 11:11:06 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Dale.Worley@comcast.net
References: <BF4D24CF-D537-4476-87D2-8E30B8462B95@softarmor.com>
	<200810200250.m9K2oifX50014113@shell01.TheWorld.com>
In-Reply-To: <200810200250.m9K2oifX50014113@shell01.TheWorld.com>
X-OriginalArrivalTime: 22 Oct 2008 08:11:06.0404 (UTC)
	FILETIME=[BBAB6E40:01C9341D]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org
Subject: Re: [Sip] So where are we at with WGLC of
	draft-ietf-sip-body-handling?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi Dale,

thanks for all your comments and for putting your time on analyzing
these issues. Let's agree on how to resolve the open issues, which you
list below in your summary:

> There is an open discussion point on the precise semantics of 
> 'required' -- in the SIP context, it is probably more convenient to 
> mean "required for processing of the containing body part", but in
> the e-mail gateway context, it is used to mean "required for the
> overall message to be processed".  (The two are equivalent for
> non-nested multiparts.)

yes, the current I-D specifies the latter; what has been called "global"
in the email threads. The idea was to be consistent with email. However,
I agree with the conclusions of the email discussions. That is, using
the "local" approach probably makes more sense in a SIP context.

So, if nobody objects, I suggest we specify the following:

multipart/mixed:

o the handling of a multipart/mixed is 'required' if its processing as a
whole is required.

o the handling parameter of a given component inside the multipart/mixed
is set regardless of the handling parameter of the multipart/mixed.

   This rules means that we can have an optional multipart/mixed that has
   required parts in it. *If* and only if the processor decides to
   process the multipart/mixed, then it needs to process the required
   parts.

   It can also happen that we have a required multipart/mixed with all
   its components being optional. This is not a big deal. The only thing
   that could happen is that the processor decides to process the
   multipart/mixed and then it decides not to process any of its parts.
   This of course relates to Paul's point on what it takes to process a
   body part.


multipart/alternative:

o the handling of a multipart/alternative is 'required' if its
processing as a whole is required.

o the handling parameter of a given component inside the
multipart/alternative is irrelevant. We can still recommend that it is
set to optional.

   This rules means that now the multipart/alternative can contain
   multipart/mixed parts that contain required components. This was not
   possible with the rules in the current I-D.

multipart/related:

o the handling of a multipart/related is 'required' if its processing as
   a whole is required.

o the handling of the root element within a multipart/related should
   probably always be required. However, since we support required
   multipart/mixed bodies with only optional components, I suggest we do
   not bother specifying anything here.


> My elaborate algorithm is, IMHO, a direct expression of the rules in 
> the I-D, although I've probably added some "it could only mean this" 
> assumptions which should be made explicit.  Whether the algorithm 
> itself is given in the I-D is a presentation issue.

I tend to agree with others in that I prefer a declarative
specification. My suggestion would be not to include the algorithm in
the draft.

> If the algorithm it too complex to implement, we must simplify the 
> I-D.
> 
> I think we should make some statement that multipart/related should 
> not be used unless it is "protected" by some extension-requirement 
> that ensures the recipient can process multipart/related.

the draft already states that. In any case, in one of your previous
emails, you suggested to strengthen the text. I suggest we do this:

OLD:
    Authors wishing
    to make use of 'multipart/related' bodies should keep in mind that
    UAs that do not understand 'multipart/related' will treat it as
    'multipart/mixed'.


NEW:
    Authors wishing
    to make use of 'multipart/related' bodies should keep in mind that
    UAs that do not understand 'multipart/related' will treat it as
    'multipart/mixed'. If such treatment by a recipient is not acceptable
    for a particular extension, the authors of such extension would need
    to make sure (e.g., by using an option-tag or by other means) that
    entities receiving the 'multipart/related' body were able to
    correctly process them.


Cheers,

Gonzalo

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


From sip-bounces@ietf.org  Wed Oct 22 02:35:18 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5E9A63A6941;
	Wed, 22 Oct 2008 02:35:18 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EAC783A6904
	for <sip@core3.amsl.com>; Wed, 22 Oct 2008 02:35:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.207
X-Spam-Level: 
X-Spam-Status: No, score=-6.207 tagged_above=-999 required=5 tests=[AWL=0.042, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id C+AjSCBHPQuG for <sip@core3.amsl.com>;
	Wed, 22 Oct 2008 02:35:15 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 992A828C10D
	for <sip@ietf.org>; Wed, 22 Oct 2008 02:35:15 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	5805A21939; Wed, 22 Oct 2008 11:36:28 +0200 (CEST)
X-AuditID: c1b4fb3e-af787bb00000537b-22-48fef41cbf1d
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	31DA3203A3; Wed, 22 Oct 2008 11:36:28 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 11:36:27 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 22 Oct 2008 11:36:26 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0889EAE5@esealmw113.eemea.ericsson.se>
In-Reply-To: <48FDEC6B.8090006@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: package negotiation
Thread-Index: AckzjJNP49uCz7AXST2p9zseGFUriQAm4eFw
References: <48FDEC6B.8090006@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>, "SIP IETF" <sip@ietf.org>,
	"Eric Burger" <eburger@bea.com>
X-OriginalArrivalTime: 22 Oct 2008 09:36:27.0834 (UTC)
	FILETIME=[A847A1A0:01C93429]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] draft-ietf-sip-info-events-00: package negotiation
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>General issues with the negotiation mechanism:
>
>What happens if the initial INVITE by a UAC includes only Send-Info or
Recv-Info? Does that indicate a "half-legacy" device??? Or does it delay
negotiation for one but not the other? Or does 
>the presence of one mean the absence of the other is equivalent to an
empty one?
>
>As I think about it, I don't think its really necessary to treat the
absence of these headers as meaning "legacy". Treating the absence of
these headers as equivalent to their presence without 
>any packages is sufficient to get the proper legacy behavior. The
tricky part is figuring out out when their absence *doesn't* mean that,
which is significant only in the non-legacy case. In 
>particular, when they aren't present in INVITE it means deferral of the
"offer" to the UAS. And possibly absence in an UPDATE means "don't
renegotiate"???

I don't think the presence, or absence, of the S/R-Info headers should
in any way be connected to legacy in any way. A UA can be legacy no
matter if the headers are present, or not present, but that is all done
based on "configuration", as described in the draft.

So, if a UAC only included Send-Info, it means that it only supports
sending of Info packages. Then, it may, or may not, also support legacy
INFO usages, but that is completely separated.


>I'm confused by the three way negotiation of info packages in
INVITE/2xx/ACK. Its allowed when the Send-Info/Recv-Info are in the
INVITE, but not when they are deferred to the INVITE response, 
>or when they are conveyed in UPDATE and its response. If the three way
handshake is needed to seal the deal, then those other options should be
off the table. But the "deferred offer" of these 
>is really needed, so it can't be off the table. Or is this just an
extra benefit that can be exploited when possible?
>
>Also, I don't see any provision for additional round(s) of negotiation
before 2xx via PRACK and UPDATE, though there is provision for
additional "half-negotiations" via provisional responses 
>and the final response. Given the parallels with O/A, I'd prefer to see
them more aligned in this regard, though I can be talked out of that
with a good argument.

I agree (I think :). The negotiation whould be 2-way. Then, based on
what the UAC gets from the UAS, it may send a PRACK/UPDATE/re-INVITE
with a new set of supported Info packages, but that is a new 2-way
negotiation transaction.


>I'd also like to take advantage of the lessons that have been learned
with O/A and nail down more of the semantics now. One issue that leaps
to mind in that regard is what happens if we start 
>to negotiate info packages in a reINVITE and then the reINVITE fails?

That's a good point.

I think we should use the same rule as for offer/answer. Because, assume
I send you a new set of packages in a re-INVITE, and you send me back a
set in a 18x. Then we may start using info packages based on that
negotiation long before the re-INVITE is rejected.

>IMO what is needed is a state model for this stuff, added to the state
for an invite-dialog-usage. This state should determine which packages
may be sent, and which should be received without 
>error. We should be very clear about exactly which events cause changes
to this state.
>
>Even then there are race conditions that need to be clarified. For
>instance: Suppose, as a result of an INVITE/1xx exchange between Alice
and Bob, that packages P & Q are allowed to be sent from Alice to Bob. 
>Alice then sends an INFO with package Q, and at the same time Bob sends
a 2xx that only allows the receipt of package P. Then Bob receives the
INFO with package Q. What should happen?
>
>Another issue is that if the Send-Info/Recv-Info contents change in
subsequent 1xx responses to the same INVITE, the UAS has no guarantee
that they are received. So any reduction in what can be 
>received cannot be counted upon until the 2xx/ACK.

True. But, I wonder whether this will really be a real-life problem.

And, we could a response code (4xx Info package not supported), which is
used by the UAS if it receives an info package which it doesn't support.
Then the UAC knows.

Regards.

Christer

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


From sip-bounces@ietf.org  Wed Oct 22 06:35:10 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 481613A6B08;
	Wed, 22 Oct 2008 06:35:10 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D41A13A6B08
	for <sip@core3.amsl.com>; Wed, 22 Oct 2008 06:35:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.542
X-Spam-Level: 
X-Spam-Status: No, score=-6.542 tagged_above=-999 required=5 tests=[AWL=0.057, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SgoC6Yli6xhj for <sip@core3.amsl.com>;
	Wed, 22 Oct 2008 06:35:07 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 8AE503A6B02
	for <sip@ietf.org>; Wed, 22 Oct 2008 06:35:07 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,464,1220227200"; d="scan'208";a="25281032"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 22 Oct 2008 13:36:06 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9MDa653024630; 
	Wed, 22 Oct 2008 09:36:06 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9MDa6J8004458;
	Wed, 22 Oct 2008 13:36:06 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 09:36:06 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 09:36:05 -0400
Message-ID: <48FF2C45.7010204@cisco.com>
Date: Wed, 22 Oct 2008 09:36:05 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 22 Oct 2008 13:36:05.0928 (UTC)
	FILETIME=[224AAA80:01C9344B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3351; t=1224682566;
	x=1225546566; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20multiple=20packages=20per=20INFO |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=ii+y4UeuNrh1S5uAUvSqcgNCDUNBfhD6eFGZp2Nj9U8=;
	b=wPSlcvEGrFDdj53kBz693fCuHo4aHs1SqOXV9MY8gXyVurkApE+Ul/2o8/
	OZDUBfZ0zaYSum5quLVp7zjto9EsHggYSJGm8MZTB+NPrcU4ych6YYbP9kri
	J0d6rLL36l;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Christer Holmberg wrote:
> Hi,
> 
> Doesn't the body handling draft say that one MUST be able to parse
> multipart message bodies?
> 
> So, I don't think we should forbid the usage of multiple packages. There
> MAY be use-cases where it is useful, so...
> 
> I also think that the negotiation of multipart support is more generic,
> so such mechanism should not be bound to INFO packages.

My thinking was:

If multipart is used to convey multiple info packages, then each part 
that contains an info package should contain an Info-Package header 
stating which package it is. That was an alternative to Eric's proposal 
that all the packages be listed at the outer level.

Then the question remained: in this case should there be an Info-Package 
header at the outer level, and if so, what should it contain?

Answering that question is what led to my proposing the "multipart" package.

I guess an alternative would be for the Info-Package header at the outer 
level to list all the packages contained, in no particular order, and 
then for the individual parts to contain an Info-Package describing that 
part.

I do think it is necessary for there to be an Info-Package header at the 
outer level, to distinguish this from a legacy use of Info.

	Thanks,
	Paul

> Regards,
> 
> Christer
> 
> 
> 
>  
> 
> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
> Paul Kyzivat
> Sent: 21. lokakuuta 2008 17:45
> To: SIP IETF; Eric Burger
> Subject: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
> 
> Re the question about multiple packages per INFO:
> 
>     There MUST be exactly one Info Package type listed per Info-Package
>     header.  Multiple Info-Packages per INFO message are disallowed.
> 
>     [EDITOR NOTE: Really?  Why not multiple Info-Packages, in a
>     multipart/mime?  Well, I thought of one: it is hard to disambiguate.
>     For example, take an INFO message with an Info-Package: key_image,
>     caller_picture.  I then have a multipart/mime with, you guessed it,
>     an image/jpeg and an image/jpeg.  I would offer we do allow this and
>     require the MIME parse order of the body match the order of the
> Info-
>     Package enumerations; if you have too many packages or body parts or
>     they do not align, you barf.  However, I timed out on this and thus
>     we will have to wait for the next version for me to flesh this out.
>     If we do do this, then we'll reference RFC 3261 as updated by
>     draft-ietf-sip-body-handling to require multipart MIME handling.]
> 
> How about defining an initial package type of "multipart". It allows
> only content-type multipart/mixed. Then each contained type must have
> its own Info-Package header. If you want to allow multiple packages per
> INFO then you need to negotiate support for "multipart". Or maybe we
> require support of multipart if you support any other package type.
> 
> 	Thanks,
> 	Paul
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use
> sip-implementors@cs.columbia.edu for questions on current sip Use
> sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct 22 06:52:47 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C577D3A6B46;
	Wed, 22 Oct 2008 06:52:47 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CD61B3A6B4E
	for <sip@core3.amsl.com>; Wed, 22 Oct 2008 06:52:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.736
X-Spam-Level: 
X-Spam-Status: No, score=-2.736 tagged_above=-999 required=5
	tests=[AWL=-0.137, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id T4WdXmSWS3Z6 for <sip@core3.amsl.com>;
	Wed, 22 Oct 2008 06:52:44 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33])
	by core3.amsl.com (Postfix) with ESMTP id C643A3A6B08
	for <sip@ietf.org>; Wed, 22 Oct 2008 06:52:44 -0700 (PDT)
Received: from ilexp03.ndc.lucent.com (h135-3-39-50.lucent.com [135.3.39.50])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id m9MDe8RI011710; 
	Wed, 22 Oct 2008 08:42:26 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by
	ilexp03.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 08:41:15 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.30]) by
	DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 15:41:05 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Wed, 22 Oct 2008 15:41:05 +0200
Message-ID: <5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
Thread-Index: Ackzi6XrNIT2zGxYSj2+GSTrqqgYJAAj0PhQAAwDrPA=
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
From: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: "Christer Holmberg" <christer.holmberg@ericsson.com>,
	"Paul Kyzivat" <pkyzivat@cisco.com>, "SIP IETF" <sip@ietf.org>,
	"Eric Burger" <eburger@bea.com>
X-OriginalArrivalTime: 22 Oct 2008 13:41:05.0832 (UTC)
	FILETIME=[D50C6280:01C9344B]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

There is is disconnect in the argument here.

Just because SIP requires (or now nearly requires) multipart body
handling doesn't mean that we have to define the meaning of multiple
bodies of the same type for every usage.

And surely there are wider things bound up here. For example is it not
still up to the application using INFO to ensure in order delivery if
that is what it requires. One way of doing this is to constrain the
transport mechanism to not send another INFO until the previous has been
acknowledged. If so, then different applications may have different
requirements in this respect that interact.

Why does putting two different packages in the same INFO work better
than two different INFO messages each with their own package usage? Is
there a desirable relationship that can be implemented between the two
that we would otherwise lose?

Regards

Keith

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Christer Holmberg
> Sent: Wednesday, October 22, 2008 8:54 AM
> To: Paul Kyzivat; SIP IETF; Eric Burger
> Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple 
> packages per INFO
> 
> 
> Hi,
> 
> Doesn't the body handling draft say that one MUST be able to 
> parse multipart message bodies?
> 
> So, I don't think we should forbid the usage of multiple 
> packages. There MAY be use-cases where it is useful, so...
> 
> I also think that the negotiation of multipart support is 
> more generic, so such mechanism should not be bound to INFO packages.
> 
> Regards,
> 
> Christer
> 
> 
> 
>  
> 
> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Paul Kyzivat
> Sent: 21. lokakuuta 2008 17:45
> To: SIP IETF; Eric Burger
> Subject: [Sip] draft-ietf-sip-info-events-00: multiple 
> packages per INFO
> 
> Re the question about multiple packages per INFO:
> 
>     There MUST be exactly one Info Package type listed per 
> Info-Package
>     header.  Multiple Info-Packages per INFO message are disallowed.
> 
>     [EDITOR NOTE: Really?  Why not multiple Info-Packages, in a
>     multipart/mime?  Well, I thought of one: it is hard to 
> disambiguate.
>     For example, take an INFO message with an Info-Package: key_image,
>     caller_picture.  I then have a multipart/mime with, you 
> guessed it,
>     an image/jpeg and an image/jpeg.  I would offer we do 
> allow this and
>     require the MIME parse order of the body match the order of the
> Info-
>     Package enumerations; if you have too many packages or 
> body parts or
>     they do not align, you barf.  However, I timed out on 
> this and thus
>     we will have to wait for the next version for me to flesh 
> this out.
>     If we do do this, then we'll reference RFC 3261 as updated by
>     draft-ietf-sip-body-handling to require multipart MIME handling.]
> 
> How about defining an initial package type of "multipart". It 
> allows only content-type multipart/mixed. Then each contained 
> type must have its own Info-Package header. If you want to 
> allow multiple packages per INFO then you need to negotiate 
> support for "multipart". Or maybe we require support of 
> multipart if you support any other package type.
> 
> 	Thanks,
> 	Paul
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors@cs.columbia.edu for questions on current sip 
> Use sipping@ietf.org for new developments on the application 
> of sip _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors@cs.columbia.edu for questions on current sip 
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct 22 06:56:35 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D492A3A6823;
	Wed, 22 Oct 2008 06:56:35 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 461693A67DB
	for <sip@core3.amsl.com>; Wed, 22 Oct 2008 06:56:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.574
X-Spam-Level: 
X-Spam-Status: No, score=-2.574 tagged_above=-999 required=5 tests=[AWL=0.025, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id S26xGM5SEwow for <sip@core3.amsl.com>;
	Wed, 22 Oct 2008 06:56:30 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 77C3B3A6823
	for <sip@ietf.org>; Wed, 22 Oct 2008 06:56:30 -0700 (PDT)
Received: from [75.68.119.237] (port=62287 helo=[192.168.15.103])
	by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1KseDF-0006QK-68; Wed, 22 Oct 2008 06:57:25 -0700
Message-Id: <D1CF9810-4025-45F4-86FF-C2D4D5132538@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>,
	Paul Kyzivat <pkyzivat@cisco.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF0889E4B3@esealmw113.eemea.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 22 Oct 2008 09:57:24 -0400
References: <48FDEB20.9040109@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E4B3@esealmw113.eemea.ericsson.se>
X-Mailer: Apple Mail (2.929.2)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: CANCEL???
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0821166486=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--===============0821166486==
Content-Type: multipart/signed; boundary=Apple-Mail-32--583974894; micalg=sha1; protocol="application/pkcs7-signature"


--Apple-Mail-32--583974894
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Cut-and-paste error.

On Oct 22, 2008, at 3:56 AM, Christer Holmberg wrote:

>
> Hi,
>
> I have the same question as Paul.
>
> Also, I wonder whether the paragraph is needed in the first place. I
> think INFO should follow the normal 3261 procedures as far as CANCEL  
> is
> concerned.
>
> I also doubt that a UAS would send a 1xx response for an INFO, and
> without that you can't CANCEL, right?
>
> Regards,
>
> Christer
>
>
>
> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
> Paul Kyzivat
> Sent: 21. lokakuuta 2008 17:46
> To: SIP IETF; Eric Burger
> Subject: [Sip] draft-ietf-sip-info-events-00: CANCEL???
>
> I have a question regarding the following paragraph:
>
>    A UAC MAY CANCEL an INFO request.  A UAS receiving a CANCEL for an
>    INFO request SHOULD respond to the INFO with a "487 Request
>    Cancelled" response unless the UAC has already sent a final
> response.
>    The UAS then MUST ignore future INFO requests.
>
> Why would the CANCEL affect *future* info requests???
>
>
> 	Paul
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use
> sip-implementors@cs.columbia.edu for questions on current sip Use
> sipping@ietf.org for new developments on the application of sip
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip


--Apple-Mail-32--583974894
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGPTCCBjkw
ggUhoAMCAQICEC+VK1RLWxrF8KJZDR9k8p8wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYTAlVT
MQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VS
VFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQD
Ey1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwwHhcNMDgwODEz
MDAwMDAwWhcNMDkwODEzMjM1OTU5WjCB4TE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsg
LSBQRVJTT05BIE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9m
IHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDMg
Q29tb2RvIExpbWl0ZWQxFDASBgNVBAMTC0VyaWMgQnVyZ2VyMSkwJwYJKoZIhvcNAQkBFhplYnVy
Z2VyQHN0YW5kYXJkc3RyYWNrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMTF
RRoA4LgOACMFph0aomRC/UpqoA5C/d6DUTOvTMrYSEqkjwnU4zxDtBcHlcB4AxKAov00MYsUvEU4
loz7BHjfDjv76AIkcwu33VYQbzGmarVnyaXsVb6f/cyRL3fPT0VOVO2tQAEEgwg//CX0jN8Kn2jH
uXD/HEvko7cmpL3Pwevf3+DwB61v7ca79PpEZfn/WhaqRKA4uVNPj/JbieeaLo2v/0RJzrEElZK0
pHCqxiD3mQ8ossPkA9fUCSxLlbdMcPU3be5x8vt8Q8mYTXF5Z3d9RZmYrmNkvTQtdzVpfYWr/hgV
Xqm9tByOOAR+hoN3FKbubR/OrAHL9yDAd4sCAwEAAaOCAhwwggIYMB8GA1UdIwQYMBaAFImCZ33E
nSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBRDWgutb7b8R/L7G3Y3D+molAA3VzAOBgNVHQ8BAf8E
BAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJ
YIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEW
HWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMIGlBgNVHR8EgZ0wgZowTKBKoEiGRmh0dHA6
Ly9jcmwuY29tb2RvY2EuY29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRF
bWFpbC5jcmwwSqBIoEaGRGh0dHA6Ly9jcmwuY29tb2RvLm5ldC9VVE4tVVNFUkZpcnN0LUNsaWVu
dEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMGwGCCsGAQUFBwEBBGAwXjA2BggrBgEFBQcwAoYq
aHR0cDovL2NydC5jb21vZG9jYS5jb20vVVROQUFBQ2xpZW50Q0EuY3J0MCQGCCsGAQUFBzABhhho
dHRwOi8vb2NzcC5jb21vZG9jYS5jb20wJQYDVR0RBB4wHIEaZWJ1cmdlckBzdGFuZGFyZHN0cmFj
ay5jb20wDQYJKoZIhvcNAQEFBQADggEBAGeBR7NPCvrY3GQoIi49JOuciatY2r4st905Jw1etp6J
umFFWlaCBl11tFSclk/3S45B+lUv3SEvG4CEjUByPScprVmCqHR+y8BAQaB/CV+N1y14x3MbhJ+Z
8XDGKeUXuuyGd9w0l3/t/QPid6TRXQjQFrLPFs1IALuNpNiFMHEF/xFbMG1Z2vznR/gSPlePekoZ
TqcExIDBNZTBebpZqwAXzPpedNNOclbMLFLWDMOAozVRpkfjI0eiFsk8SF1Ho1Gb9Bx8DeG4peE2
KRVOR9FFnZZgBpFjXYRcglsMOSKCY8HgE+NGvbbqbrMoBV/BlYyxRXwfti71RL9Zs2Cq1eQxggP8
MIID+AIBATCBwzCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExh
a2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8v
d3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkNH2TynzAJBgUrDgMCGgUAoIICDTAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wODEwMjIxMzU3MjRaMCMGCSqGSIb3
DQEJBDEWBBROzH2bL/F1buk0rtd9E6jv8rk5UjCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD
VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU
aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2
MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv
lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN
H2TynzANBgkqhkiG9w0BAQEFAASCAQBjFLvXq3rvmRIC1HxkDTPk8xXqJZnjGwIMawjTbZqH1zJg
vG4C2nI6wNVEs0OSf+nB6GnOEEJgOjv24Enuok3Qj80EIxbzzamLVziP3ReSOCMjhGJNwQbOmsrU
YzFAFFHB9dsJQLabwjEWT2kdgx7VcS9T3rfZ0iyH/uQhBmVHDKGGSgKzQHC3eaDuIg3RYiZmtNvh
hNNc8cwJ0Yoq3PzXqDqY+4+TXXYNB7R1NtyCQ89jmivhaodTObZKQr69+b1QpMw2mZQFI45awvp8
wvSZZaZ0Ht8otbo0MBlJ4rB3r9F9hp/IdhHPmbG4XW6y4qzrRnq+z6KcBUkltd/CPc56AAAAAAAA

--Apple-Mail-32--583974894--

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

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


From sip-bounces@ietf.org  Wed Oct 22 08:30:07 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 512A53A6B46;
	Wed, 22 Oct 2008 08:30:07 -0700 (PDT)
X-Original-To: sip@ietf.org
Delivered-To: sip@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 99A823A697A; Wed, 22 Oct 2008 08:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081022153001.99A823A697A@core3.amsl.com>
Date: Wed, 22 Oct 2008 08:30:01 -0700 (PDT)
Cc: sip@ietf.org
Subject: [Sip] I-D Action:draft-ietf-sip-connect-reuse-12.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--NextPart

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


	Title           : Connection Reuse in the Session Initiation Protocol (SIP)
	Author(s)       : V. Gurbani, et al.
	Filename        : draft-ietf-sip-connect-reuse-12.txt
	Pages           : 20
	Date            : 2008-10-22

This document enables a pair of communicating proxies to reuse a
congestion-controlled connection between themselves for sending
requests in the forward and backwards direction.  Because the
connection is essentially aliased for requests going in the backwards
direction, reuse is predicated upon both the communicating endpoints
authenticating themselves using X.509 certificates through TLS.  For
this reason, we only consider connection reuse for TLS over TCP and
TLS over SCTP.  From the security perspective, it is bad practice to
reuse a single connection for the TCP or SCTP transport between two
peers, and this document provides specific insights into why this is
the case.  As a remedy, it suggests using two TCP connections (or two
SCTP associations), each opened pro-actively towards the recipient by
the sender.  Finally, this document also provides guidelines on
connection reuse and virtual SIP servers and the interaction of
connection reuse and DNS SRV lookups in SIP.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sip-connect-reuse-12.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-sip-connect-reuse-12.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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


From sip-bounces@ietf.org  Wed Oct 22 10:23:32 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7AF603A6A73;
	Wed, 22 Oct 2008 10:23:32 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D290A3A6A66
	for <sip@core3.amsl.com>; Wed, 22 Oct 2008 10:23:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.208
X-Spam-Level: 
X-Spam-Status: No, score=-6.208 tagged_above=-999 required=5 tests=[AWL=0.041, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KHgBrD1GAjYg for <sip@core3.amsl.com>;
	Wed, 22 Oct 2008 10:23:30 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 937563A6A73
	for <sip@ietf.org>; Wed, 22 Oct 2008 10:23:30 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	83F6E204BA; Wed, 22 Oct 2008 19:24:23 +0200 (CEST)
X-AuditID: c1b4fb3c-ad8cdbb0000015b5-4c-48ff61c79c5f
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	57B9F204A9; Wed, 22 Oct 2008 19:24:23 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 19:24:23 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 22 Oct 2008 19:20:10 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCF93@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
Thread-Index: Ackzi6XrNIT2zGxYSj2+GSTrqqgYJAAj0PhQAAwDrPAAB93STA==
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>,
	"Paul Kyzivat" <pkyzivat@cisco.com>, "SIP IETF" <sip@ietf.org>,
	"Eric Burger" <eburger@bea.com>
X-OriginalArrivalTime: 22 Oct 2008 17:24:23.0158 (UTC)
	FILETIME=[067A1960:01C9346B]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi,

>Just because SIP requires (or now nearly requires) multipart body
>handling doesn't mean that we have to define the meaning of multiple
>bodies of the same type for every usage.

Of course not. But, unless there are good reasons I don't think we should forbid it - in case there will be future use-cases where it could be useful.

>And surely there are wider things bound up here. For example is it not
>still up to the application using INFO to ensure in order delivery if
>that is what it requires. One way of doing this is to constrain the
>transport mechanism to not send another INFO until the previous has been
>acknowledged. If so, then different applications may have different
>requirements in this respect that interact.

Correct. So, this would only be used if it fulfills all those requirements.

>Why does putting two different packages in the same INFO work better
>than two different INFO messages each with their own package usage? Is
>there a desirable relationship that can be implemented between the two
>that we would otherwise lose?

Well, that brings up a good question: assuming it is allowed to send multiple info packages in a single INFO, does that automatically mean that there must be a desirable relationship? I don't think so.
 
If there is a relationship that should be described in the application logic itself.
 
Regards,
 
Christer
 
 
 

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
> Behalf Of Christer Holmberg
> Sent: Wednesday, October 22, 2008 8:54 AM
> To: Paul Kyzivat; SIP IETF; Eric Burger
> Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple
> packages per INFO
>
>
> Hi,
>
> Doesn't the body handling draft say that one MUST be able to
> parse multipart message bodies?
>
> So, I don't think we should forbid the usage of multiple
> packages. There MAY be use-cases where it is useful, so...
>
> I also think that the negotiation of multipart support is
> more generic, so such mechanism should not be bound to INFO packages.
>
> Regards,
>
> Christer
>
>
>
> 
>
> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
> Behalf Of Paul Kyzivat
> Sent: 21. lokakuuta 2008 17:45
> To: SIP IETF; Eric Burger
> Subject: [Sip] draft-ietf-sip-info-events-00: multiple
> packages per INFO
>
> Re the question about multiple packages per INFO:
>
>     There MUST be exactly one Info Package type listed per
> Info-Package
>     header.  Multiple Info-Packages per INFO message are disallowed.
>
>     [EDITOR NOTE: Really?  Why not multiple Info-Packages, in a
>     multipart/mime?  Well, I thought of one: it is hard to
> disambiguate.
>     For example, take an INFO message with an Info-Package: key_image,
>     caller_picture.  I then have a multipart/mime with, you
> guessed it,
>     an image/jpeg and an image/jpeg.  I would offer we do
> allow this and
>     require the MIME parse order of the body match the order of the
> Info-
>     Package enumerations; if you have too many packages or
> body parts or
>     they do not align, you barf.  However, I timed out on
> this and thus
>     we will have to wait for the next version for me to flesh
> this out.
>     If we do do this, then we'll reference RFC 3261 as updated by
>     draft-ietf-sip-body-handling to require multipart MIME handling.]
>
> How about defining an initial package type of "multipart". It
> allows only content-type multipart/mixed. Then each contained
> type must have its own Info-Package header. If you want to
> allow multiple packages per INFO then you need to negotiate
> support for "multipart". Or maybe we require support of
> multipart if you support any other package type.
>
>       Thanks,
>       Paul
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use
> sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application
> of sip _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use
> sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>

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


From sip-bounces@ietf.org  Wed Oct 22 10:36:00 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 44D073A697E;
	Wed, 22 Oct 2008 10:36:00 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F00613A683B
	for <sip@core3.amsl.com>; Wed, 22 Oct 2008 10:35:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.725
X-Spam-Level: 
X-Spam-Status: No, score=-2.725 tagged_above=-999 required=5
	tests=[AWL=-0.126, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ispo0HaBZudo for <sip@core3.amsl.com>;
	Wed, 22 Oct 2008 10:35:54 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35])
	by core3.amsl.com (Postfix) with ESMTP id 349043A697E
	for <sip@ietf.org>; Wed, 22 Oct 2008 10:35:53 -0700 (PDT)
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1])
	by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id m9MHXkQi022987;
	Wed, 22 Oct 2008 12:33:54 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by
	ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 12:33:43 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.30]) by
	DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 19:33:40 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Wed, 22 Oct 2008 19:33:39 +0200
Message-ID: <5D1A7985295922448D5550C94DE2918002425AC4@DEEXC1U01.de.lucent.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF083CCF93@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
Thread-Index: Ackzi6XrNIT2zGxYSj2+GSTrqqgYJAAj0PhQAAwDrPAAB93STAAAQ/Ew
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF93@esealmw113.eemea.ericsson.se>
From: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: "Christer Holmberg" <christer.holmberg@ericsson.com>,
	"Paul Kyzivat" <pkyzivat@cisco.com>, "SIP IETF" <sip@ietf.org>,
	"Eric Burger" <eburger@bea.com>
X-OriginalArrivalTime: 22 Oct 2008 17:33:40.0073 (UTC)
	FILETIME=[526C9590:01C9346C]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer said in reply to me:

> >Why does putting two different packages in the same INFO work better 
> >than two different INFO messages each with their own package 
> usage? Is 
> >there a desirable relationship that can be implemented 
> between the two 
> >that we would otherwise lose?
> 
> Well, that brings up a good question: assuming it is allowed 
> to send multiple info packages in a single INFO, does that 
> automatically mean that there must be a desirable 
> relationship? I don't think so.
>  
> If there is a relationship that should be described in the 
> application logic itself.

That was not an answer to my question.

What I was trying to get to was whether providing two INFOs each containing one package provided the same solution as one INFO containing two packages  (and assuming anyone has a use case for two packages on the same dialog - something I don't believe I have yet seen presented to the list - did I miss it somewhere). 

If the answer is yes, then it becomes a matter of deciding whether we want one solution or two to be documented, and if one, then which one. 

If the answer is no, then we need to understand the why and wherefore of those differences before deciding what documentation to provide.

Regards

Keith 

> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] 
> Sent: Wednesday, October 22, 2008 6:20 PM
> To: DRAGE, Keith (Keith); Paul Kyzivat; SIP IETF; Eric Burger
> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple 
> packages per INFO
> 
> Hi,
> 
> >Just because SIP requires (or now nearly requires) multipart body 
> >handling doesn't mean that we have to define the meaning of multiple 
> >bodies of the same type for every usage.
> 
> Of course not. But, unless there are good reasons I don't 
> think we should forbid it - in case there will be future 
> use-cases where it could be useful.
> 
> >And surely there are wider things bound up here. For example 
> is it not 
> >still up to the application using INFO to ensure in order 
> delivery if 
> >that is what it requires. One way of doing this is to constrain the 
> >transport mechanism to not send another INFO until the previous has 
> >been acknowledged. If so, then different applications may have 
> >different requirements in this respect that interact.
> 
> Correct. So, this would only be used if it fulfills all those 
> requirements.
> 
> >Why does putting two different packages in the same INFO work better 
> >than two different INFO messages each with their own package 
> usage? Is 
> >there a desirable relationship that can be implemented 
> between the two 
> >that we would otherwise lose?
> 
> Well, that brings up a good question: assuming it is allowed 
> to send multiple info packages in a single INFO, does that 
> automatically mean that there must be a desirable 
> relationship? I don't think so.
>  
> If there is a relationship that should be described in the 
> application logic itself.
>  
> Regards,
>  
> Christer
>  
>  
>  
> 
> > -----Original Message-----
> > From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of 
> > Christer Holmberg
> > Sent: Wednesday, October 22, 2008 8:54 AM
> > To: Paul Kyzivat; SIP IETF; Eric Burger
> > Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages 
> > per INFO
> >
> >
> > Hi,
> >
> > Doesn't the body handling draft say that one MUST be able to parse 
> > multipart message bodies?
> >
> > So, I don't think we should forbid the usage of multiple packages. 
> > There MAY be use-cases where it is useful, so...
> >
> > I also think that the negotiation of multipart support is more 
> > generic, so such mechanism should not be bound to INFO packages.
> >
> > Regards,
> >
> > Christer
> >
> >
> >
> > 
> >
> > -----Original Message-----
> > From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of 
> > Paul Kyzivat
> > Sent: 21. lokakuuta 2008 17:45
> > To: SIP IETF; Eric Burger
> > Subject: [Sip] draft-ietf-sip-info-events-00: multiple packages per 
> > INFO
> >
> > Re the question about multiple packages per INFO:
> >
> >     There MUST be exactly one Info Package type listed per 
> > Info-Package
> >     header.  Multiple Info-Packages per INFO message are disallowed.
> >
> >     [EDITOR NOTE: Really?  Why not multiple Info-Packages, in a
> >     multipart/mime?  Well, I thought of one: it is hard to 
> > disambiguate.
> >     For example, take an INFO message with an Info-Package: 
> key_image,
> >     caller_picture.  I then have a multipart/mime with, you guessed 
> > it,
> >     an image/jpeg and an image/jpeg.  I would offer we do 
> allow this 
> > and
> >     require the MIME parse order of the body match the order of the
> > Info-
> >     Package enumerations; if you have too many packages or 
> body parts 
> > or
> >     they do not align, you barf.  However, I timed out on this and 
> > thus
> >     we will have to wait for the next version for me to flesh this 
> > out.
> >     If we do do this, then we'll reference RFC 3261 as updated by
> >     draft-ietf-sip-body-handling to require multipart MIME 
> handling.]
> >
> > How about defining an initial package type of "multipart". 
> It allows 
> > only content-type multipart/mixed. Then each contained type 
> must have 
> > its own Info-Package header. If you want to allow multiple packages 
> > per INFO then you need to negotiate support for 
> "multipart". Or maybe 
> > we require support of multipart if you support any other 
> package type.
> >
> >       Thanks,
> >       Paul
> > _______________________________________________
> > Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol Use 
> > sip-implementors@cs.columbia.edu for questions on current sip Use 
> > sipping@ietf.org for new developments on the application of sip 
> > _______________________________________________
> > Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol Use 
> > sip-implementors@cs.columbia.edu for questions on current sip Use 
> > sipping@ietf.org for new developments on the application of sip
> >
> 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct 22 11:18:20 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3A73D3A6A62;
	Wed, 22 Oct 2008 11:18:20 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8939A3A6A62
	for <sip@core3.amsl.com>; Wed, 22 Oct 2008 11:18:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.56
X-Spam-Level: 
X-Spam-Status: No, score=-6.56 tagged_above=-999 required=5 tests=[AWL=0.039, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id EYz4WzyHIcLa for <sip@core3.amsl.com>;
	Wed, 22 Oct 2008 11:18:18 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id F32133A69D0
	for <sip@ietf.org>; Wed, 22 Oct 2008 11:18:17 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,465,1220227200"; d="scan'208";a="25322845"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 22 Oct 2008 18:19:30 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9MIJUiE007382; 
	Wed, 22 Oct 2008 14:19:30 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9MIJT3V025356;
	Wed, 22 Oct 2008 18:19:30 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 14:19:29 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 14:19:29 -0400
Message-ID: <48FF6EB1.4000407@cisco.com>
Date: Wed, 22 Oct 2008 14:19:29 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF93@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425AC4@DEEXC1U01.de.lucent.com>
In-Reply-To: <5D1A7985295922448D5550C94DE2918002425AC4@DEEXC1U01.de.lucent.com>
X-OriginalArrivalTime: 22 Oct 2008 18:19:29.0456 (UTC)
	FILETIME=[B92F2300:01C93472]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=7619; t=1224699570;
	x=1225563570; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20multiple=20packages=20per=20INFO |Sender:=20
	|To:=20=22DRAGE,=20Keith=20\(Keith\)=22=20<drage@alcatel-lu
	cent.com>; bh=GNohEiWXV8zzh2Rj/DVm6ABfZIVCvJEFbGTG24ZXs+0=;
	b=xrLHyeQlkc46MUbTv4mmPiwWeHUZ8XXJt5338EWzqQ3VDdE2Z/4S3jmPYV
	K1FcuOZBUdz5iKaqxj4O0ehGwnShdveGkE9w0PeEp4qkI/fyd+UBKlFS11zB
	f+I9D8eHy6;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Keith,

IMO sending two info packages in separate INFO messages should produce 
the same behavior as sending them in one. Except perhaps for order of 
processing. If we choose to define sending two in one INFO, then I think 
we need to specify how the ordering is supposed to work. (E.g. that they 
should be processed in the same order as they appear in the multipart, 
and that in such case the behavior MUST be the same as if they were sent 
in separate messages in that order.)

The one advantage that comes to mind is that if you can't do this, then 
you really need to wait for the round trip of one info before sending 
another, which could be inconvenient and delay inducing if you get the 
data for more than one at the same time.

But we could certainly just decide not to define that now, and leave it 
till later to decide if sending multiple packages is useful.

An problem with defining this is that it introduces another sort of 
error to handle if one package can be dealt with but another cannot.

I guess I'd be inclined not to define it for now.

	Thanks,
	Paul



DRAGE, Keith (Keith) wrote:
> Christer said in reply to me:
> 
>>> Why does putting two different packages in the same INFO work better 
>>> than two different INFO messages each with their own package 
>> usage? Is 
>>> there a desirable relationship that can be implemented 
>> between the two 
>>> that we would otherwise lose?
>> Well, that brings up a good question: assuming it is allowed 
>> to send multiple info packages in a single INFO, does that 
>> automatically mean that there must be a desirable 
>> relationship? I don't think so.
>>  
>> If there is a relationship that should be described in the 
>> application logic itself.
> 
> That was not an answer to my question.
> 
> What I was trying to get to was whether providing two INFOs each containing one package provided the same solution as one INFO containing two packages  (and assuming anyone has a use case for two packages on the same dialog - something I don't believe I have yet seen presented to the list - did I miss it somewhere). 
> 
> If the answer is yes, then it becomes a matter of deciding whether we want one solution or two to be documented, and if one, then which one. 
> 
> If the answer is no, then we need to understand the why and wherefore of those differences before deciding what documentation to provide.
> 
> Regards
> 
> Keith 
> 
>> -----Original Message-----
>> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] 
>> Sent: Wednesday, October 22, 2008 6:20 PM
>> To: DRAGE, Keith (Keith); Paul Kyzivat; SIP IETF; Eric Burger
>> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple 
>> packages per INFO
>>
>> Hi,
>>
>>> Just because SIP requires (or now nearly requires) multipart body 
>>> handling doesn't mean that we have to define the meaning of multiple 
>>> bodies of the same type for every usage.
>> Of course not. But, unless there are good reasons I don't 
>> think we should forbid it - in case there will be future 
>> use-cases where it could be useful.
>>
>>> And surely there are wider things bound up here. For example 
>> is it not 
>>> still up to the application using INFO to ensure in order 
>> delivery if 
>>> that is what it requires. One way of doing this is to constrain the 
>>> transport mechanism to not send another INFO until the previous has 
>>> been acknowledged. If so, then different applications may have 
>>> different requirements in this respect that interact.
>> Correct. So, this would only be used if it fulfills all those 
>> requirements.
>>
>>> Why does putting two different packages in the same INFO work better 
>>> than two different INFO messages each with their own package 
>> usage? Is 
>>> there a desirable relationship that can be implemented 
>> between the two 
>>> that we would otherwise lose?
>> Well, that brings up a good question: assuming it is allowed 
>> to send multiple info packages in a single INFO, does that 
>> automatically mean that there must be a desirable 
>> relationship? I don't think so.
>>  
>> If there is a relationship that should be described in the 
>> application logic itself.
>>  
>> Regards,
>>  
>> Christer
>>  
>>  
>>  
>>
>>> -----Original Message-----
>>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
>> Behalf Of 
>>> Christer Holmberg
>>> Sent: Wednesday, October 22, 2008 8:54 AM
>>> To: Paul Kyzivat; SIP IETF; Eric Burger
>>> Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages 
>>> per INFO
>>>
>>>
>>> Hi,
>>>
>>> Doesn't the body handling draft say that one MUST be able to parse 
>>> multipart message bodies?
>>>
>>> So, I don't think we should forbid the usage of multiple packages. 
>>> There MAY be use-cases where it is useful, so...
>>>
>>> I also think that the negotiation of multipart support is more 
>>> generic, so such mechanism should not be bound to INFO packages.
>>>
>>> Regards,
>>>
>>> Christer
>>>
>>>
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
>> Behalf Of 
>>> Paul Kyzivat
>>> Sent: 21. lokakuuta 2008 17:45
>>> To: SIP IETF; Eric Burger
>>> Subject: [Sip] draft-ietf-sip-info-events-00: multiple packages per 
>>> INFO
>>>
>>> Re the question about multiple packages per INFO:
>>>
>>>     There MUST be exactly one Info Package type listed per 
>>> Info-Package
>>>     header.  Multiple Info-Packages per INFO message are disallowed.
>>>
>>>     [EDITOR NOTE: Really?  Why not multiple Info-Packages, in a
>>>     multipart/mime?  Well, I thought of one: it is hard to 
>>> disambiguate.
>>>     For example, take an INFO message with an Info-Package: 
>> key_image,
>>>     caller_picture.  I then have a multipart/mime with, you guessed 
>>> it,
>>>     an image/jpeg and an image/jpeg.  I would offer we do 
>> allow this 
>>> and
>>>     require the MIME parse order of the body match the order of the
>>> Info-
>>>     Package enumerations; if you have too many packages or 
>> body parts 
>>> or
>>>     they do not align, you barf.  However, I timed out on this and 
>>> thus
>>>     we will have to wait for the next version for me to flesh this 
>>> out.
>>>     If we do do this, then we'll reference RFC 3261 as updated by
>>>     draft-ietf-sip-body-handling to require multipart MIME 
>> handling.]
>>> How about defining an initial package type of "multipart". 
>> It allows 
>>> only content-type multipart/mixed. Then each contained type 
>> must have 
>>> its own Info-Package header. If you want to allow multiple packages 
>>> per INFO then you need to negotiate support for 
>> "multipart". Or maybe 
>>> we require support of multipart if you support any other 
>> package type.
>>>       Thanks,
>>>       Paul
>>> _______________________________________________
>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>> This list is for NEW development of the core SIP Protocol Use 
>>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>>> sipping@ietf.org for new developments on the application of sip 
>>> _______________________________________________
>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>> This list is for NEW development of the core SIP Protocol Use 
>>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>>> sipping@ietf.org for new developments on the application of sip
>>>
>>
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct 22 14:46:25 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E5ACB3A6B87;
	Wed, 22 Oct 2008 14:46:25 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D3C3928C1B9
	for <sip@core3.amsl.com>; Wed, 22 Oct 2008 14:46:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.716
X-Spam-Level: 
X-Spam-Status: No, score=-2.716 tagged_above=-999 required=5
	tests=[AWL=-0.117, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1SfYSRJjM-ap for <sip@core3.amsl.com>;
	Wed, 22 Oct 2008 14:46:23 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35])
	by core3.amsl.com (Postfix) with ESMTP id ED85C3A6853
	for <sip@ietf.org>; Wed, 22 Oct 2008 14:46:18 -0700 (PDT)
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2])
	by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id m9MLjicA012078;
	Wed, 22 Oct 2008 16:45:44 -0500 (CDT)
Received: from DEEXP02.DE.lucent.com ([135.248.187.66]) by
	ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 16:45:44 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.30]) by
	DEEXP02.DE.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 23:45:41 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Wed, 22 Oct 2008 23:45:40 +0200
Message-ID: <5D1A7985295922448D5550C94DE2918002425ADD@DEEXC1U01.de.lucent.com>
In-Reply-To: <48FF6EB1.4000407@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
Thread-Index: Ack0cryxPINIzsANRGyXA7Zi2Gh2FwAG1y8A
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF93@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425AC4@DEEXC1U01.de.lucent.com>
	<48FF6EB1.4000407@cisco.com>
From: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 22 Oct 2008 21:45:41.0256 (UTC)
	FILETIME=[875A0080:01C9348F]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Thanks for the direct answer to my question.

> IMO sending two info packages in separate INFO messages 
> should produce the same behavior as sending them in one. 
> Except perhaps for order of processing. If we choose to 
> define sending two in one INFO, then I think we need to 
> specify how the ordering is supposed to work. (E.g. that they 
> should be processed in the same order as they appear in the 
> multipart, and that in such case the behavior MUST be the 
> same as if they were sent in separate messages in that order.)

Surely here you are implying that the two packages have a dependency. That's two steps of use cases, i.e. that there is a requirement for more than one use case in the first place, and then the use case for the two packages being interdependent in terms of data content.

If there is not such dependency, but the two packages both require in order delivery for their own data, then surely each package not sending the next INFO until it has received the response for the previous one within its package is a sufficient mechanism at the level of INFO and the body packaging.

Regards

Keith

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
> Sent: Wednesday, October 22, 2008 7:19 PM
> To: DRAGE, Keith (Keith)
> Cc: Christer Holmberg; SIP IETF; Eric Burger
> Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple 
> packages per INFO
> 
> Keith,
> 
> IMO sending two info packages in separate INFO messages 
> should produce the same behavior as sending them in one. 
> Except perhaps for order of processing. If we choose to 
> define sending two in one INFO, then I think we need to 
> specify how the ordering is supposed to work. (E.g. that they 
> should be processed in the same order as they appear in the 
> multipart, and that in such case the behavior MUST be the 
> same as if they were sent in separate messages in that order.)
> 
> The one advantage that comes to mind is that if you can't do 
> this, then you really need to wait for the round trip of one 
> info before sending another, which could be inconvenient and 
> delay inducing if you get the data for more than one at the same time.
> 
> But we could certainly just decide not to define that now, 
> and leave it till later to decide if sending multiple 
> packages is useful.
> 
> An problem with defining this is that it introduces another 
> sort of error to handle if one package can be dealt with but 
> another cannot.
> 
> I guess I'd be inclined not to define it for now.
> 
> 	Thanks,
> 	Paul
> 
> 
> 
> DRAGE, Keith (Keith) wrote:
> > Christer said in reply to me:
> > 
> >>> Why does putting two different packages in the same INFO 
> work better 
> >>> than two different INFO messages each with their own package
> >> usage? Is
> >>> there a desirable relationship that can be implemented
> >> between the two
> >>> that we would otherwise lose?
> >> Well, that brings up a good question: assuming it is 
> allowed to send 
> >> multiple info packages in a single INFO, does that 
> automatically mean 
> >> that there must be a desirable relationship? I don't think so.
> >>  
> >> If there is a relationship that should be described in the 
> >> application logic itself.
> > 
> > That was not an answer to my question.
> > 
> > What I was trying to get to was whether providing two INFOs 
> each containing one package provided the same solution as one 
> INFO containing two packages  (and assuming anyone has a use 
> case for two packages on the same dialog - something I don't 
> believe I have yet seen presented to the list - did I miss it 
> somewhere). 
> > 
> > If the answer is yes, then it becomes a matter of deciding 
> whether we want one solution or two to be documented, and if 
> one, then which one. 
> > 
> > If the answer is no, then we need to understand the why and 
> wherefore of those differences before deciding what 
> documentation to provide.
> > 
> > Regards
> > 
> > Keith
> > 
> >> -----Original Message-----
> >> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> >> Sent: Wednesday, October 22, 2008 6:20 PM
> >> To: DRAGE, Keith (Keith); Paul Kyzivat; SIP IETF; Eric Burger
> >> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple 
> packages 
> >> per INFO
> >>
> >> Hi,
> >>
> >>> Just because SIP requires (or now nearly requires) multipart body 
> >>> handling doesn't mean that we have to define the meaning 
> of multiple 
> >>> bodies of the same type for every usage.
> >> Of course not. But, unless there are good reasons I don't think we 
> >> should forbid it - in case there will be future use-cases where it 
> >> could be useful.
> >>
> >>> And surely there are wider things bound up here. For example
> >> is it not
> >>> still up to the application using INFO to ensure in order
> >> delivery if
> >>> that is what it requires. One way of doing this is to 
> constrain the 
> >>> transport mechanism to not send another INFO until the 
> previous has 
> >>> been acknowledged. If so, then different applications may have 
> >>> different requirements in this respect that interact.
> >> Correct. So, this would only be used if it fulfills all those 
> >> requirements.
> >>
> >>> Why does putting two different packages in the same INFO 
> work better 
> >>> than two different INFO messages each with their own package
> >> usage? Is
> >>> there a desirable relationship that can be implemented
> >> between the two
> >>> that we would otherwise lose?
> >> Well, that brings up a good question: assuming it is 
> allowed to send 
> >> multiple info packages in a single INFO, does that 
> automatically mean 
> >> that there must be a desirable relationship? I don't think so.
> >>  
> >> If there is a relationship that should be described in the 
> >> application logic itself.
> >>  
> >> Regards,
> >>  
> >> Christer
> >>  
> >>  
> >>  
> >>
> >>> -----Original Message-----
> >>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
> >> Behalf Of
> >>> Christer Holmberg
> >>> Sent: Wednesday, October 22, 2008 8:54 AM
> >>> To: Paul Kyzivat; SIP IETF; Eric Burger
> >>> Subject: Re: [Sip] draft-ietf-sip-info-events-00: 
> multiple packages 
> >>> per INFO
> >>>
> >>>
> >>> Hi,
> >>>
> >>> Doesn't the body handling draft say that one MUST be able 
> to parse 
> >>> multipart message bodies?
> >>>
> >>> So, I don't think we should forbid the usage of multiple 
> packages. 
> >>> There MAY be use-cases where it is useful, so...
> >>>
> >>> I also think that the negotiation of multipart support is more 
> >>> generic, so such mechanism should not be bound to INFO packages.
> >>>
> >>> Regards,
> >>>
> >>> Christer
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> -----Original Message-----
> >>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
> >> Behalf Of
> >>> Paul Kyzivat
> >>> Sent: 21. lokakuuta 2008 17:45
> >>> To: SIP IETF; Eric Burger
> >>> Subject: [Sip] draft-ietf-sip-info-events-00: multiple 
> packages per 
> >>> INFO
> >>>
> >>> Re the question about multiple packages per INFO:
> >>>
> >>>     There MUST be exactly one Info Package type listed per 
> >>> Info-Package
> >>>     header.  Multiple Info-Packages per INFO message are 
> disallowed.
> >>>
> >>>     [EDITOR NOTE: Really?  Why not multiple Info-Packages, in a
> >>>     multipart/mime?  Well, I thought of one: it is hard to 
> >>> disambiguate.
> >>>     For example, take an INFO message with an Info-Package: 
> >> key_image,
> >>>     caller_picture.  I then have a multipart/mime with, 
> you guessed 
> >>> it,
> >>>     an image/jpeg and an image/jpeg.  I would offer we do
> >> allow this
> >>> and
> >>>     require the MIME parse order of the body match the 
> order of the
> >>> Info-
> >>>     Package enumerations; if you have too many packages or
> >> body parts
> >>> or
> >>>     they do not align, you barf.  However, I timed out on 
> this and 
> >>> thus
> >>>     we will have to wait for the next version for me to 
> flesh this 
> >>> out.
> >>>     If we do do this, then we'll reference RFC 3261 as updated by
> >>>     draft-ietf-sip-body-handling to require multipart MIME
> >> handling.]
> >>> How about defining an initial package type of "multipart". 
> >> It allows
> >>> only content-type multipart/mixed. Then each contained type
> >> must have
> >>> its own Info-Package header. If you want to allow 
> multiple packages 
> >>> per INFO then you need to negotiate support for
> >> "multipart". Or maybe
> >>> we require support of multipart if you support any other
> >> package type.
> >>>       Thanks,
> >>>       Paul
> >>> _______________________________________________
> >>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> >>> This list is for NEW development of the core SIP Protocol Use 
> >>> sip-implementors@cs.columbia.edu for questions on current sip Use 
> >>> sipping@ietf.org for new developments on the application of sip 
> >>> _______________________________________________
> >>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> >>> This list is for NEW development of the core SIP Protocol Use 
> >>> sip-implementors@cs.columbia.edu for questions on current sip Use 
> >>> sipping@ietf.org for new developments on the application of sip
> >>>
> >>
> > 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct 22 15:03:32 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A7ABD3A6B73;
	Wed, 22 Oct 2008 15:03:32 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9DA3E28C1A6
	for <sip@core3.amsl.com>; Wed, 22 Oct 2008 15:03:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.562
X-Spam-Level: 
X-Spam-Status: No, score=-6.562 tagged_above=-999 required=5 tests=[AWL=0.037, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vn0yWfa-9j8B for <sip@core3.amsl.com>;
	Wed, 22 Oct 2008 15:03:30 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id CA44A3A6A9B
	for <sip@ietf.org>; Wed, 22 Oct 2008 15:03:29 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,466,1220227200"; d="scan'208";a="25321088"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 22 Oct 2008 22:04:47 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9MM4kPn010834; 
	Wed, 22 Oct 2008 18:04:46 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9MM4k8g020996;
	Wed, 22 Oct 2008 22:04:46 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 18:04:46 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 18:04:46 -0400
Message-ID: <48FFA373.5090508@cisco.com>
Date: Wed, 22 Oct 2008 18:04:35 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF93@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425AC4@DEEXC1U01.de.lucent.com>
	<48FF6EB1.4000407@cisco.com>
	<5D1A7985295922448D5550C94DE2918002425ADD@DEEXC1U01.de.lucent.com>
In-Reply-To: <5D1A7985295922448D5550C94DE2918002425ADD@DEEXC1U01.de.lucent.com>
X-OriginalArrivalTime: 22 Oct 2008 22:04:46.0404 (UTC)
	FILETIME=[31E9B840:01C93492]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=10038; t=1224713087;
	x=1225577087; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20multiple=20packages=20per=20INFO |Sender:=20
	|To:=20=22DRAGE,=20Keith=20\(Keith\)=22=20<drage@alcatel-lu
	cent.com>; bh=TtHKprOQDZ4Vy01PNnneCbBjjBYs1VB4CrXNQa/rFac=;
	b=wF8Vx39RH88Z9efs56U6y5xDvvAYkjXS4Ildlwy8n53Oa0hqXAjBoSN9Oc
	XI3Yr1vNL2vjvxQogcv4PUTGBUaiBjWLRH8jqjrL2+plDtjdzy+xgiFL/EEL
	ExAI88pYFn;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Keith,

The reason for awaiting a reply before sending another INFO is because 
if you don't do that, and the messages get reordered, then the last one 
to arrive will fail due to CSeq ordering. That's not a good thing, 
though I guess it would be simple enough to retry it in that case.

I would assume that in most cases the actual order of processing would 
not matter for different package types.

	Thanks,
	Paul

DRAGE, Keith (Keith) wrote:
> Thanks for the direct answer to my question.
> 
>> IMO sending two info packages in separate INFO messages 
>> should produce the same behavior as sending them in one. 
>> Except perhaps for order of processing. If we choose to 
>> define sending two in one INFO, then I think we need to 
>> specify how the ordering is supposed to work. (E.g. that they 
>> should be processed in the same order as they appear in the 
>> multipart, and that in such case the behavior MUST be the 
>> same as if they were sent in separate messages in that order.)
> 
> Surely here you are implying that the two packages have a dependency. That's two steps of use cases, i.e. that there is a requirement for more than one use case in the first place, and then the use case for the two packages being interdependent in terms of data content.
> 
> If there is not such dependency, but the two packages both require in order delivery for their own data, then surely each package not sending the next INFO until it has received the response for the previous one within its package is a sufficient mechanism at the level of INFO and the body packaging.
> 
> Regards
> 
> Keith
> 
>> -----Original Message-----
>> From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
>> Sent: Wednesday, October 22, 2008 7:19 PM
>> To: DRAGE, Keith (Keith)
>> Cc: Christer Holmberg; SIP IETF; Eric Burger
>> Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple 
>> packages per INFO
>>
>> Keith,
>>
>> IMO sending two info packages in separate INFO messages 
>> should produce the same behavior as sending them in one. 
>> Except perhaps for order of processing. If we choose to 
>> define sending two in one INFO, then I think we need to 
>> specify how the ordering is supposed to work. (E.g. that they 
>> should be processed in the same order as they appear in the 
>> multipart, and that in such case the behavior MUST be the 
>> same as if they were sent in separate messages in that order.)
>>
>> The one advantage that comes to mind is that if you can't do 
>> this, then you really need to wait for the round trip of one 
>> info before sending another, which could be inconvenient and 
>> delay inducing if you get the data for more than one at the same time.
>>
>> But we could certainly just decide not to define that now, 
>> and leave it till later to decide if sending multiple 
>> packages is useful.
>>
>> An problem with defining this is that it introduces another 
>> sort of error to handle if one package can be dealt with but 
>> another cannot.
>>
>> I guess I'd be inclined not to define it for now.
>>
>> 	Thanks,
>> 	Paul
>>
>>
>>
>> DRAGE, Keith (Keith) wrote:
>>> Christer said in reply to me:
>>>
>>>>> Why does putting two different packages in the same INFO 
>> work better 
>>>>> than two different INFO messages each with their own package
>>>> usage? Is
>>>>> there a desirable relationship that can be implemented
>>>> between the two
>>>>> that we would otherwise lose?
>>>> Well, that brings up a good question: assuming it is 
>> allowed to send 
>>>> multiple info packages in a single INFO, does that 
>> automatically mean 
>>>> that there must be a desirable relationship? I don't think so.
>>>>  
>>>> If there is a relationship that should be described in the 
>>>> application logic itself.
>>> That was not an answer to my question.
>>>
>>> What I was trying to get to was whether providing two INFOs 
>> each containing one package provided the same solution as one 
>> INFO containing two packages  (and assuming anyone has a use 
>> case for two packages on the same dialog - something I don't 
>> believe I have yet seen presented to the list - did I miss it 
>> somewhere). 
>>> If the answer is yes, then it becomes a matter of deciding 
>> whether we want one solution or two to be documented, and if 
>> one, then which one. 
>>> If the answer is no, then we need to understand the why and 
>> wherefore of those differences before deciding what 
>> documentation to provide.
>>> Regards
>>>
>>> Keith
>>>
>>>> -----Original Message-----
>>>> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
>>>> Sent: Wednesday, October 22, 2008 6:20 PM
>>>> To: DRAGE, Keith (Keith); Paul Kyzivat; SIP IETF; Eric Burger
>>>> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple 
>> packages 
>>>> per INFO
>>>>
>>>> Hi,
>>>>
>>>>> Just because SIP requires (or now nearly requires) multipart body 
>>>>> handling doesn't mean that we have to define the meaning 
>> of multiple 
>>>>> bodies of the same type for every usage.
>>>> Of course not. But, unless there are good reasons I don't think we 
>>>> should forbid it - in case there will be future use-cases where it 
>>>> could be useful.
>>>>
>>>>> And surely there are wider things bound up here. For example
>>>> is it not
>>>>> still up to the application using INFO to ensure in order
>>>> delivery if
>>>>> that is what it requires. One way of doing this is to 
>> constrain the 
>>>>> transport mechanism to not send another INFO until the 
>> previous has 
>>>>> been acknowledged. If so, then different applications may have 
>>>>> different requirements in this respect that interact.
>>>> Correct. So, this would only be used if it fulfills all those 
>>>> requirements.
>>>>
>>>>> Why does putting two different packages in the same INFO 
>> work better 
>>>>> than two different INFO messages each with their own package
>>>> usage? Is
>>>>> there a desirable relationship that can be implemented
>>>> between the two
>>>>> that we would otherwise lose?
>>>> Well, that brings up a good question: assuming it is 
>> allowed to send 
>>>> multiple info packages in a single INFO, does that 
>> automatically mean 
>>>> that there must be a desirable relationship? I don't think so.
>>>>  
>>>> If there is a relationship that should be described in the 
>>>> application logic itself.
>>>>  
>>>> Regards,
>>>>  
>>>> Christer
>>>>  
>>>>  
>>>>  
>>>>
>>>>> -----Original Message-----
>>>>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
>>>> Behalf Of
>>>>> Christer Holmberg
>>>>> Sent: Wednesday, October 22, 2008 8:54 AM
>>>>> To: Paul Kyzivat; SIP IETF; Eric Burger
>>>>> Subject: Re: [Sip] draft-ietf-sip-info-events-00: 
>> multiple packages 
>>>>> per INFO
>>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> Doesn't the body handling draft say that one MUST be able 
>> to parse 
>>>>> multipart message bodies?
>>>>>
>>>>> So, I don't think we should forbid the usage of multiple 
>> packages. 
>>>>> There MAY be use-cases where it is useful, so...
>>>>>
>>>>> I also think that the negotiation of multipart support is more 
>>>>> generic, so such mechanism should not be bound to INFO packages.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Christer
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
>>>> Behalf Of
>>>>> Paul Kyzivat
>>>>> Sent: 21. lokakuuta 2008 17:45
>>>>> To: SIP IETF; Eric Burger
>>>>> Subject: [Sip] draft-ietf-sip-info-events-00: multiple 
>> packages per 
>>>>> INFO
>>>>>
>>>>> Re the question about multiple packages per INFO:
>>>>>
>>>>>     There MUST be exactly one Info Package type listed per 
>>>>> Info-Package
>>>>>     header.  Multiple Info-Packages per INFO message are 
>> disallowed.
>>>>>     [EDITOR NOTE: Really?  Why not multiple Info-Packages, in a
>>>>>     multipart/mime?  Well, I thought of one: it is hard to 
>>>>> disambiguate.
>>>>>     For example, take an INFO message with an Info-Package: 
>>>> key_image,
>>>>>     caller_picture.  I then have a multipart/mime with, 
>> you guessed 
>>>>> it,
>>>>>     an image/jpeg and an image/jpeg.  I would offer we do
>>>> allow this
>>>>> and
>>>>>     require the MIME parse order of the body match the 
>> order of the
>>>>> Info-
>>>>>     Package enumerations; if you have too many packages or
>>>> body parts
>>>>> or
>>>>>     they do not align, you barf.  However, I timed out on 
>> this and 
>>>>> thus
>>>>>     we will have to wait for the next version for me to 
>> flesh this 
>>>>> out.
>>>>>     If we do do this, then we'll reference RFC 3261 as updated by
>>>>>     draft-ietf-sip-body-handling to require multipart MIME
>>>> handling.]
>>>>> How about defining an initial package type of "multipart". 
>>>> It allows
>>>>> only content-type multipart/mixed. Then each contained type
>>>> must have
>>>>> its own Info-Package header. If you want to allow 
>> multiple packages 
>>>>> per INFO then you need to negotiate support for
>>>> "multipart". Or maybe
>>>>> we require support of multipart if you support any other
>>>> package type.
>>>>>       Thanks,
>>>>>       Paul
>>>>> _______________________________________________
>>>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>>>> This list is for NEW development of the core SIP Protocol Use 
>>>>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>>>>> sipping@ietf.org for new developments on the application of sip 
>>>>> _______________________________________________
>>>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>>>> This list is for NEW development of the core SIP Protocol Use 
>>>>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>>>>> sipping@ietf.org for new developments on the application of sip
>>>>>
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct 22 15:32:22 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C7A2C3A698F;
	Wed, 22 Oct 2008 15:32:22 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 973D63A698F
	for <sip@core3.amsl.com>; Wed, 22 Oct 2008 15:32:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.713
X-Spam-Level: 
X-Spam-Status: No, score=-2.713 tagged_above=-999 required=5
	tests=[AWL=-0.114, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3be-XID51VIT for <sip@core3.amsl.com>;
	Wed, 22 Oct 2008 15:32:20 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37])
	by core3.amsl.com (Postfix) with ESMTP id EDECA3A68ED
	for <sip@ietf.org>; Wed, 22 Oct 2008 15:32:19 -0700 (PDT)
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2])
	by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id m9MMXabs017341
	for <sip@ietf.org>; Wed, 22 Oct 2008 17:33:36 -0500 (CDT)
Received: from DEEXP02.DE.lucent.com ([135.248.187.66]) by
	ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 17:33:36 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.30]) by
	DEEXP02.DE.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 00:33:33 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Thu, 23 Oct 2008 00:33:06 +0200
Message-ID: <5D1A7985295922448D5550C94DE2918002425AE1@DEEXC1U01.de.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Publication request for draft-ietf-sip-connect-reuse-12
Thread-Index: Ack0lic6as8akCdkQWGpr/INxJrKOw==
From: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: "SIP IETF" <sip@ietf.org>
X-OriginalArrivalTime: 22 Oct 2008 22:33:33.0951 (UTC)
	FILETIME=[379C78F0:01C93496]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Subject: [Sip] Publication request for draft-ietf-sip-connect-reuse-12
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

(As WG cochair)

A new version of this document has just been issued, which makes no
technical change but does tidy up some editorial issues that I
discovered while doing the publication request.

I intend to submit the publication request in 24 hours time with the
following PROTO writeup unless any further issues are discovered.

If anyone has any further implementation experience they would like to
share in particular, that would be useful information.

I am also currently preparing domain-certs, eku and session policy.
Information on implementation experience would be useful on those
documents.

Regards

Keith

------------------------------------------------------------------------
-
PROTO writeup for
http://www.ietf.org/internet-drafts/draft-ietf-sip-connect-reuse-12: 
"Connection Reuse in the Session Initiation Protocol (SIP)"

   (1.a)  Who is the Document Shepherd for this document?  Has the
          Document Shepherd personally reviewed this version of the
          document and, in particular, does he or she believe this
          version is ready for forwarding to the IESG for publication?

Keith Drage

The document has been reviewed and is ready for forwarding to IESG for
publication.

Document history:

-	draft-mahy-sip-connect-reuse-00 was submitted 1st June 2003 and
expired 30th 
November 2003.
-	draft-ietf-sip-connect-reuse-00 was submitted 1st August 2003
and expired 30th 
January 2004.
-	draft-ietf-sip-connect-reuse-01 was submitted 1st February 2004
and expired 1st 
August 2004.
-	draft-ietf-sip-connect-reuse-02 was submitted 17th July 2004 and
expired 15th 
January 2005.
-	draft-ietf-sip-connect-reuse-03 was submitted 22nd October 2004
and expired 22nd 
April 2005.
-	draft-ietf-sip-connect-reuse-04 was submitted 14th July 2005 and
expired 15th 
January 2006.
-	draft-ietf-sip-connect-reuse-05 was submitted 5th February 2006
and expired 5th 
August 2006.
-	draft-ietf-sip-connect-reuse-06 was submitted 21st August 2006
and expired 22nd 
February 2007.
-	draft-ietf-sip-connect-reuse-07 was submitted 6th October 2006
and expired 9th 
April 2007.
-	draft-ietf-sip-connect-reuse-08 was submitted 16th October 2007
and expired 18th 
April 2008.
-	draft-ietf-sip-connect-reuse-09 was submitted 8th February 2008
and expires 11th 
August 2008.
-	draft-ietf-sip-connect-reuse-10 was submitted 13th May 2008 and
expires 14th 
November 2008.
-	draft-ietf-sip-connect-reuse-11 was submitted 14th July 2008 and
expires 15th 
January 2009.
-	draft-ietf-sip-connect-reuse-12 was submitted 22nd October 2008
and expires 25th 
April 2009.

There was a requirements phase of the work that was covered in:

-	draft-mahy-sipping-connect-reuse-reqs-00 was submitted 19th June
2002 and expired 
18th December 2002.
-	draft-ietf-sipping-connect-reuse-reqs-00 was submitted 1st
October 2002 and 
expired 1st April 2003.

These requirements were handed over to SIP without being published by
SIPPING. The 
requirements also formed the basis for progressing
draft-ietf-sip-outbound, the scope of 
which is separate from this document.

WGLC announced in the SIP WG on 26th October 2005 to complete 18th
November 2005 on -04 
version. WGLC continuation announced 23rd October 2007 to complete 6th
November 2007 on 
-08 version. Extended until 24th November 2007.

Review was made and comments were received from: Dale Worley, Hadriel
Kaplan, Jerry Yin. 
Paul Kyzivat participated in the discussion on the resolution of these
comments. Earlier 
reviews were made by Paul Kyzivat, Jonathan Rosenberg, Cullen Jennings,
Benny Prijono, 
Matthew Gardiner.

   (1.b)  Has the document had adequate review both from key WG members
          and from key non-WG members?  Does the Document Shepherd have
          any concerns about the depth or breadth of the reviews that
          have been performed?

The document has had adequate review from working group members. The
main issue with the 
extended timescale of this document has been separating the scope from
that of outbound, 
and identifying whether there was still a sufficient use case for
continuing with this 
document. While the community of use is small compared to outbound, it
is still 
significant and it was therefore agreed to proceed with the draft.

   (1.c)  Does the Document Shepherd have concerns that the document
          needs more review from a particular or broader perspective,
          e.g., security, operational complexity, someone familiar with
          AAA, internationalization, or XML?

The document defines mechanisms that are entirely internal to the
Session Initiation 
Protocol (SIP). The document shepherd considers that no external review
from an external 
specialist is necessary, apart from as follows.

The document has not had a separate security review, and that should
therefore occur.

   (1.d)  Does the Document Shepherd have any specific concerns or
          issues with this document that the Responsible Area Director
          and/or the IESG should be aware of?  For example, perhaps he
          or she is uncomfortable with certain parts of the document, or
          has concerns whether there really is a need for it.  In any
          event, if the WG has discussed those issues and has indicated
          that it still wishes to advance the document, detail those
          concerns here.  Has an IPR disclosure related to this document
          been filed?  If so, please include a reference to the
          disclosure and summarize the WG discussion and conclusion on
          this issue.

The document defines a new SIP protocol extension for a particular
purpose in a form 
that has been used for many other extensions. The document shepherd has
no concerns with 
the document.

There have been no IPR disclosures on this document.

   (1.e)  How solid is the WG consensus behind this document?  Does it
          represent the strong concurrence of a few individuals, with
          others being silent, or does the WG as a whole understand and
          agree with it?

As already indicated, there are two solutions in this area fulfilling
two different use 
cases. draft-ietf-sip-outbound covers the majority of these use cases,
with a more 
limited community of support of the remaining use cases covered by this
draft. However a 
poll of the SIP WG showed that there was still a significant community
of interest to 
justify proceeding with the document.

   (1.f)  Has anyone threatened an appeal or otherwise indicated extreme
          discontent?  If so, please summarize the areas of conflict in
          separate email messages to the Responsible Area Director.  (It
          should be in a separate email because this questionnaire is
          entered into the ID Tracker.)

None indicated.

   (1.g)  Has the Document Shepherd personally verified that the
          document satisfies all ID nits?  (See
          http://www.ietf.org/ID-Checklist.html and
          http://tools.ietf.org/tools/idnits/.)  Boilerplate checks are
          not enough; this check needs to be thorough.  Has the document
          met all formal review criteria it needs to, such as the MIB
          Doctor, media type, and URI type reviews?  If the document
          does not already indicate its intended status at the top of
          the first page, please indicate the intended status here.

The document has been reviewed against the guidelines in RFC 4485 and it
is believed 
that the document is conformant with those guidelines.

While the document defines a Via header field parameter, this has been
performed as a 
SIP working group item, and therefore this draft is in conformance with
RFC 3968.

For ID-NITS the checks against idnits 2.09.01 report no NITS found.


   (1.h)  Has the document split its references into normative and
          informative?  Are there normative references to documents that
          are not ready for advancement or are otherwise in an unclear
          state?  If such normative references exist, what is the
          strategy for their completion?  Are there normative references
          that are downward references, as described in [RFC3967]?  If
          so, list these downward references to support the Area
          Director in the Last Call procedure for them [RFC3967].

The document has separate sections for normative and informative
references. The 
normative references have been checked and found to be normative.

   (1.i)  Has the Document Shepherd verified that the document's IANA
          Considerations section exists and is consistent with the body
          of the document?  If the document specifies protocol
          extensions, are reservations requested in appropriate IANA
          registries?  Are the IANA registries clearly identified?  If
          the document creates a new registry, does it define the
          proposed initial contents of the registry and an allocation
          procedure for future registrations?  Does it suggest a
          reasonable name for the new registry?  See [RFC2434].  If the
          document describes an Expert Review process, has the Document
          Shepherd conferred with the Responsible Area Director so that
          the IESG can appoint the needed Expert during IESG Evaluation?

The document defines the following value that requires registration:

*	alias header field parameter to the Via header field.

Section 12 of the document provides the IANA considerations section, and
this defines 
the above.

   (1.j)  Has the Document Shepherd verified that sections of the
          document that are written in a formal language, such as XML
          code, BNF rules, MIB definitions, etc., validate correctly in
          an automated checker?

The document defines one items in ABNF in section 7. These augment the
ABNF defined in 
RFC 3261.

The contents of this ABNF is have been checked in conjunction with the
ABNF defined in 
RFC 3261 by use of the checker defined in
http://www.apps.ietf.org/abnf.html and no 
faults have been found. 

   (1.k)  The IESG approval announcement includes a Document
          Announcement Write-Up.  Please provide such a Document
          Announcement Write-Up.  Recent examples can be found in the
          "Action" announcements for approved documents.  The approval
          announcement contains the following sections:

          Technical Summary
             Relevant content can frequently be found in the abstract
             and/or introduction of the document.  If not, this may be
             an indication that there are deficiencies in the abstract
             or introduction.

          Working Group Summary
             Was there anything in the WG process that is worth noting?
             For example, was there controversy about particular points
             or were there decisions where the consensus was
             particularly rough?

          Document Quality
             Are there existing implementations of the protocol?  Have a
             significant number of vendors indicated their plan to
             implement the specification?  Are there any reviewers that
             merit special mention as having done a thorough review,
             e.g., one that resulted in important changes or a
             conclusion that the document had no substantive issues?  If
             there was a MIB Doctor, Media Type, or other Expert Review,
             what was its course (briefly)?  In the case of a Media Type
             Review, on what date was the request posted?

          Personnel
             Who is the Document Shepherd for this document?  Who is the
             Responsible Area Director?  If the document requires IANA
             experts(s), insert 'The IANA Expert(s) for the registries
             in this document are <TO BE ADDED BY THE AD>.'

Technical summary.

This document enables a pair of communicating proxies to reuse a
congestion-controlled 
connection between themselves for sending requests in the forward and
backwards 
direction.  Because the connection is essentially aliased for requests
going in the 
backwards direction, reuse should be predicated upon both the
communicating endpoints 
authenticating themselves using X.509 certificates through TLS.  For
this reason, we 
only consider connection reuse for TLS over TCP and TLS over SCTP.  A
single connection 
should not be reused for the TCP or SCTP transport between two peers,
and this document 
provides insight into why this is the case.  As a remedy, it suggests
using two TCP 
connections (or two SCTP associations), each opened pro-actively towards
the recipient 
by the sender.  Finally, this document also provides guidelines on
connection reuse and 
virtual SIP servers and the interaction of connection reuse and DNS SRV
lookups in SIP.

Working group summary.

There is consensus in the working group to publish this document. 

Document Quality

At SIPiT 18 there were recorded 6 implementations of connect-reuse. At
SIPiT 19 
there were recorded 27 implementations of connect-reuse (30% of 90 
implementations). This was the last SIPiT apparently polled for numbers
of 
implementations of this extension.

Personnel

The document shepherd for this document was Keith Drage. The responsible
Area Director 
was Cullen Jennings. The IANA Expert(s) for the registries in this
document are <TO BE 
ADDED BY THE AD>.
----------------------------------------------------------------------
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct 22 17:48:09 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9AB543A68FB;
	Wed, 22 Oct 2008 17:48:09 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2FC8E3A68FB
	for <sip@core3.amsl.com>; Wed, 22 Oct 2008 17:48:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id L3KME5lTWTyR for <sip@core3.amsl.com>;
	Wed, 22 Oct 2008 17:48:07 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 78BD23A685E
	for <sip@ietf.org>; Wed, 22 Oct 2008 17:48:07 -0700 (PDT)
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9N0krYT002232
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Wed, 22 Oct 2008 19:46:55 -0500
Message-Id: <D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
In-Reply-To: <5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 22 Oct 2008 19:46:47 -0500
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>,
	Paul Kyzivat <pkyzivat@cisco.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 22, 2008, at 8:41 AM, DRAGE, Keith (Keith) wrote:
>
>
> Why does putting two different packages in the same INFO work better
> than two different INFO messages each with their own package usage? Is
> there a desirable relationship that can be implemented between the two
> that we would otherwise lose?

We have one package per NOTIFY. Let's stick with one package per INFO,  
unless we want to go back to using mime-types as the only  
distinguisher of packages.

--
Dean

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


From sip-bounces@ietf.org  Wed Oct 22 18:04:17 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B474A28C170;
	Wed, 22 Oct 2008 18:04:17 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E263C28C161
	for <sip@core3.amsl.com>; Wed, 22 Oct 2008 18:04:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.678
X-Spam-Level: 
X-Spam-Status: No, score=-2.678 tagged_above=-999 required=5
	tests=[AWL=-0.079, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nm3Qp7ZHpHN8 for <sip@core3.amsl.com>;
	Wed, 22 Oct 2008 18:04:14 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35])
	by core3.amsl.com (Postfix) with ESMTP id 671BA28C153
	for <sip@ietf.org>; Wed, 22 Oct 2008 18:04:14 -0700 (PDT)
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2])
	by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id m9N13oSa026487;
	Wed, 22 Oct 2008 20:03:51 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by
	ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Oct 2008 20:03:50 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.30]) by
	DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 03:03:47 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Thu, 23 Oct 2008 03:03:46 +0200
Message-ID: <5D1A7985295922448D5550C94DE2918002425AE6@DEEXC1U01.de.lucent.com>
In-Reply-To: <48FFA373.5090508@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
Thread-Index: Ack0kjVBUgvzrsIRSc6XyxMy5zxN9wABtaVQ
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF93@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425AC4@DEEXC1U01.de.lucent.com>
	<48FF6EB1.4000407@cisco.com>
	<5D1A7985295922448D5550C94DE2918002425ADD@DEEXC1U01.de.lucent.com>
	<48FFA373.5090508@cisco.com>
From: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 23 Oct 2008 01:03:47.0531 (UTC)
	FILETIME=[341FA1B0:01C934AB]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

In order delivery and reliable delivery are different things but in many cases they are linked. I suspect that if an application is prepared to accept out of order delivery it is also prepared to accept unreliable delivery. 

This may be because the application provides its own sequencing and retransmission mechanisms, or because it just plain does not matter to the application.

I believe that the original INFO RFC allowed outstanding INFO transactions to exist before initiating another. This carried the implications you mention. It was up to the application to decide whether that was acceptable, or whether it relied on waiting for the response to a previous INFO transaction before commencing another as its protection mechanism.

I believe where we have a single package in a dialog, this flexibility should still exist.

Where we have multiple packages in a dialog, and one package is reliant on the receipt of a response before generating a new INFO, then based on your comment about loss of an out of sequence request in a dialog, then all packages in that dialog will have to share that restriction.

Regards

Keith

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
> Sent: Wednesday, October 22, 2008 11:05 PM
> To: DRAGE, Keith (Keith)
> Cc: Christer Holmberg; SIP IETF; Eric Burger
> Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple 
> packages per INFO
> 
> Keith,
> 
> The reason for awaiting a reply before sending another INFO 
> is because if you don't do that, and the messages get 
> reordered, then the last one to arrive will fail due to CSeq 
> ordering. That's not a good thing, though I guess it would be 
> simple enough to retry it in that case.
> 
> I would assume that in most cases the actual order of 
> processing would not matter for different package types.
> 
> 	Thanks,
> 	Paul
> 
> DRAGE, Keith (Keith) wrote:
> > Thanks for the direct answer to my question.
> > 
> >> IMO sending two info packages in separate INFO messages should 
> >> produce the same behavior as sending them in one.
> >> Except perhaps for order of processing. If we choose to define 
> >> sending two in one INFO, then I think we need to specify how the 
> >> ordering is supposed to work. (E.g. that they should be 
> processed in 
> >> the same order as they appear in the multipart, and that 
> in such case 
> >> the behavior MUST be the same as if they were sent in separate 
> >> messages in that order.)
> > 
> > Surely here you are implying that the two packages have a 
> dependency. That's two steps of use cases, i.e. that there is 
> a requirement for more than one use case in the first place, 
> and then the use case for the two packages being 
> interdependent in terms of data content.
> > 
> > If there is not such dependency, but the two packages both 
> require in order delivery for their own data, then surely 
> each package not sending the next INFO until it has received 
> the response for the previous one within its package is a 
> sufficient mechanism at the level of INFO and the body packaging.
> > 
> > Regards
> > 
> > Keith
> > 
> >> -----Original Message-----
> >> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> >> Sent: Wednesday, October 22, 2008 7:19 PM
> >> To: DRAGE, Keith (Keith)
> >> Cc: Christer Holmberg; SIP IETF; Eric Burger
> >> Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple 
> packages 
> >> per INFO
> >>
> >> Keith,
> >>
> >> IMO sending two info packages in separate INFO messages should 
> >> produce the same behavior as sending them in one.
> >> Except perhaps for order of processing. If we choose to define 
> >> sending two in one INFO, then I think we need to specify how the 
> >> ordering is supposed to work. (E.g. that they should be 
> processed in 
> >> the same order as they appear in the multipart, and that 
> in such case 
> >> the behavior MUST be the same as if they were sent in separate 
> >> messages in that order.)
> >>
> >> The one advantage that comes to mind is that if you can't do this, 
> >> then you really need to wait for the round trip of one info before 
> >> sending another, which could be inconvenient and delay inducing if 
> >> you get the data for more than one at the same time.
> >>
> >> But we could certainly just decide not to define that now, 
> and leave 
> >> it till later to decide if sending multiple packages is useful.
> >>
> >> An problem with defining this is that it introduces 
> another sort of 
> >> error to handle if one package can be dealt with but 
> another cannot.
> >>
> >> I guess I'd be inclined not to define it for now.
> >>
> >> 	Thanks,
> >> 	Paul
> >>
> >>
> >>
> >> DRAGE, Keith (Keith) wrote:
> >>> Christer said in reply to me:
> >>>
> >>>>> Why does putting two different packages in the same INFO
> >> work better
> >>>>> than two different INFO messages each with their own package
> >>>> usage? Is
> >>>>> there a desirable relationship that can be implemented
> >>>> between the two
> >>>>> that we would otherwise lose?
> >>>> Well, that brings up a good question: assuming it is
> >> allowed to send
> >>>> multiple info packages in a single INFO, does that
> >> automatically mean
> >>>> that there must be a desirable relationship? I don't think so.
> >>>>  
> >>>> If there is a relationship that should be described in the 
> >>>> application logic itself.
> >>> That was not an answer to my question.
> >>>
> >>> What I was trying to get to was whether providing two INFOs
> >> each containing one package provided the same solution as one INFO 
> >> containing two packages  (and assuming anyone has a use 
> case for two 
> >> packages on the same dialog - something I don't believe I have yet 
> >> seen presented to the list - did I miss it somewhere).
> >>> If the answer is yes, then it becomes a matter of deciding
> >> whether we want one solution or two to be documented, and if one, 
> >> then which one.
> >>> If the answer is no, then we need to understand the why and
> >> wherefore of those differences before deciding what 
> documentation to 
> >> provide.
> >>> Regards
> >>>
> >>> Keith
> >>>
> >>>> -----Original Message-----
> >>>> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> >>>> Sent: Wednesday, October 22, 2008 6:20 PM
> >>>> To: DRAGE, Keith (Keith); Paul Kyzivat; SIP IETF; Eric Burger
> >>>> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple
> >> packages
> >>>> per INFO
> >>>>
> >>>> Hi,
> >>>>
> >>>>> Just because SIP requires (or now nearly requires) 
> multipart body 
> >>>>> handling doesn't mean that we have to define the meaning
> >> of multiple
> >>>>> bodies of the same type for every usage.
> >>>> Of course not. But, unless there are good reasons I 
> don't think we 
> >>>> should forbid it - in case there will be future 
> use-cases where it 
> >>>> could be useful.
> >>>>
> >>>>> And surely there are wider things bound up here. For example
> >>>> is it not
> >>>>> still up to the application using INFO to ensure in order
> >>>> delivery if
> >>>>> that is what it requires. One way of doing this is to
> >> constrain the
> >>>>> transport mechanism to not send another INFO until the
> >> previous has
> >>>>> been acknowledged. If so, then different applications may have 
> >>>>> different requirements in this respect that interact.
> >>>> Correct. So, this would only be used if it fulfills all those 
> >>>> requirements.
> >>>>
> >>>>> Why does putting two different packages in the same INFO
> >> work better
> >>>>> than two different INFO messages each with their own package
> >>>> usage? Is
> >>>>> there a desirable relationship that can be implemented
> >>>> between the two
> >>>>> that we would otherwise lose?
> >>>> Well, that brings up a good question: assuming it is
> >> allowed to send
> >>>> multiple info packages in a single INFO, does that
> >> automatically mean
> >>>> that there must be a desirable relationship? I don't think so.
> >>>>  
> >>>> If there is a relationship that should be described in the 
> >>>> application logic itself.
> >>>>  
> >>>> Regards,
> >>>>  
> >>>> Christer
> >>>>  
> >>>>  
> >>>>  
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
> >>>> Behalf Of
> >>>>> Christer Holmberg
> >>>>> Sent: Wednesday, October 22, 2008 8:54 AM
> >>>>> To: Paul Kyzivat; SIP IETF; Eric Burger
> >>>>> Subject: Re: [Sip] draft-ietf-sip-info-events-00: 
> >> multiple packages
> >>>>> per INFO
> >>>>>
> >>>>>
> >>>>> Hi,
> >>>>>
> >>>>> Doesn't the body handling draft say that one MUST be able
> >> to parse
> >>>>> multipart message bodies?
> >>>>>
> >>>>> So, I don't think we should forbid the usage of multiple
> >> packages. 
> >>>>> There MAY be use-cases where it is useful, so...
> >>>>>
> >>>>> I also think that the negotiation of multipart support is more 
> >>>>> generic, so such mechanism should not be bound to INFO packages.
> >>>>>
> >>>>> Regards,
> >>>>>
> >>>>> Christer
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> -----Original Message-----
> >>>>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
> >>>> Behalf Of
> >>>>> Paul Kyzivat
> >>>>> Sent: 21. lokakuuta 2008 17:45
> >>>>> To: SIP IETF; Eric Burger
> >>>>> Subject: [Sip] draft-ietf-sip-info-events-00: multiple
> >> packages per
> >>>>> INFO
> >>>>>
> >>>>> Re the question about multiple packages per INFO:
> >>>>>
> >>>>>     There MUST be exactly one Info Package type listed per 
> >>>>> Info-Package
> >>>>>     header.  Multiple Info-Packages per INFO message are
> >> disallowed.
> >>>>>     [EDITOR NOTE: Really?  Why not multiple Info-Packages, in a
> >>>>>     multipart/mime?  Well, I thought of one: it is hard to 
> >>>>> disambiguate.
> >>>>>     For example, take an INFO message with an Info-Package: 
> >>>> key_image,
> >>>>>     caller_picture.  I then have a multipart/mime with,
> >> you guessed
> >>>>> it,
> >>>>>     an image/jpeg and an image/jpeg.  I would offer we do
> >>>> allow this
> >>>>> and
> >>>>>     require the MIME parse order of the body match the
> >> order of the
> >>>>> Info-
> >>>>>     Package enumerations; if you have too many packages or
> >>>> body parts
> >>>>> or
> >>>>>     they do not align, you barf.  However, I timed out on
> >> this and
> >>>>> thus
> >>>>>     we will have to wait for the next version for me to
> >> flesh this
> >>>>> out.
> >>>>>     If we do do this, then we'll reference RFC 3261 as 
> updated by
> >>>>>     draft-ietf-sip-body-handling to require multipart MIME
> >>>> handling.]
> >>>>> How about defining an initial package type of "multipart". 
> >>>> It allows
> >>>>> only content-type multipart/mixed. Then each contained type
> >>>> must have
> >>>>> its own Info-Package header. If you want to allow
> >> multiple packages
> >>>>> per INFO then you need to negotiate support for
> >>>> "multipart". Or maybe
> >>>>> we require support of multipart if you support any other
> >>>> package type.
> >>>>>       Thanks,
> >>>>>       Paul
> >>>>> _______________________________________________
> >>>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> >>>>> This list is for NEW development of the core SIP Protocol Use 
> >>>>> sip-implementors@cs.columbia.edu for questions on 
> current sip Use 
> >>>>> sipping@ietf.org for new developments on the application of sip 
> >>>>> _______________________________________________
> >>>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> >>>>> This list is for NEW development of the core SIP Protocol Use 
> >>>>> sip-implementors@cs.columbia.edu for questions on 
> current sip Use 
> >>>>> sipping@ietf.org for new developments on the application of sip
> >>>>>
> > 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 23 00:10:32 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AAE973A69C9;
	Thu, 23 Oct 2008 00:10:31 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CE62A3A6BFC
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 00:10:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.209
X-Spam-Level: 
X-Spam-Status: No, score=-6.209 tagged_above=-999 required=5 tests=[AWL=0.040, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id xX2yQPi3nOjk for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 00:10:28 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 84FE33A6BF0
	for <sip@ietf.org>; Thu, 23 Oct 2008 00:10:28 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	D2E0E220EC; Thu, 23 Oct 2008 09:11:32 +0200 (CEST)
X-AuditID: c1b4fb3e-adf84bb00000537b-5c-490023a4a492
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	A86A320430; Thu, 23 Oct 2008 09:11:32 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 09:10:29 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 23 Oct 2008 09:10:28 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
In-Reply-To: <48FF2C45.7010204@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-sip-info-events-00: Content-Type vs Info-Package [was
	RE: [Sip] draft-ietf-sip-info-events-00: multiple packages per
	INFO]
Thread-Index: Ack0SyaoOgdkhL/bQvyCd1E6OQiCXwAkqkyA
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 23 Oct 2008 07:10:29.0330 (UTC)
	FILETIME=[6E37BB20:01C934DE]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>
Subject: [Sip] draft-ietf-sip-info-events-00: Content-Type vs Info-Package
	[was RE: draft-ietf-sip-info-events-00: multiple packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi Paul,

Now I understand what you mean - I mixed up things a little.

The question is: shall we really use the Info-Package header. And, if
so, shall we use it in the way as currently described by the draft?


Shouldn't we use Content-Type to indicate what is in the message body?
After all, we may need Content-Length etc.

So, there would be two options:


1. Use Content-Type to indicate info-package, and within the package
itself then indicate the exact package type

Example: Content-Type: application/info-package


2. Use Content-Type to indicate info-package AND exact package type

Example: Content-Type: application/info-package.foo


...or something like that.


Then, if you have multiple packages, you would use Content-Type:
multipart/mixed on the SIP level, and Content-Type
application/info-package within the mimes (normal multipart handling).

Regards,

Christer






 

-----Original Message-----
From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
Sent: 22. lokakuuta 2008 16:36
To: Christer Holmberg
Cc: SIP IETF; Eric Burger
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per
INFO



Christer Holmberg wrote:
> Hi,
> 
> Doesn't the body handling draft say that one MUST be able to parse 
> multipart message bodies?
> 
> So, I don't think we should forbid the usage of multiple packages. 
> There MAY be use-cases where it is useful, so...
> 
> I also think that the negotiation of multipart support is more 
> generic, so such mechanism should not be bound to INFO packages.

My thinking was:

If multipart is used to convey multiple info packages, then each part
that contains an info package should contain an Info-Package header
stating which package it is. That was an alternative to Eric's proposal
that all the packages be listed at the outer level.

Then the question remained: in this case should there be an Info-Package
header at the outer level, and if so, what should it contain?

Answering that question is what led to my proposing the "multipart"
package.

I guess an alternative would be for the Info-Package header at the outer
level to list all the packages contained, in no particular order, and
then for the individual parts to contain an Info-Package describing that
part.

I do think it is necessary for there to be an Info-Package header at the
outer level, to distinguish this from a legacy use of Info.

	Thanks,
	Paul

> Regards,
> 
> Christer
> 
> 
> 
>  
> 
> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of 
> Paul Kyzivat
> Sent: 21. lokakuuta 2008 17:45
> To: SIP IETF; Eric Burger
> Subject: [Sip] draft-ietf-sip-info-events-00: multiple packages per 
> INFO
> 
> Re the question about multiple packages per INFO:
> 
>     There MUST be exactly one Info Package type listed per
Info-Package
>     header.  Multiple Info-Packages per INFO message are disallowed.
> 
>     [EDITOR NOTE: Really?  Why not multiple Info-Packages, in a
>     multipart/mime?  Well, I thought of one: it is hard to
disambiguate.
>     For example, take an INFO message with an Info-Package: key_image,
>     caller_picture.  I then have a multipart/mime with, you guessed
it,
>     an image/jpeg and an image/jpeg.  I would offer we do allow this
and
>     require the MIME parse order of the body match the order of the
> Info-
>     Package enumerations; if you have too many packages or body parts
or
>     they do not align, you barf.  However, I timed out on this and
thus
>     we will have to wait for the next version for me to flesh this
out.
>     If we do do this, then we'll reference RFC 3261 as updated by
>     draft-ietf-sip-body-handling to require multipart MIME handling.]
> 
> How about defining an initial package type of "multipart". It allows 
> only content-type multipart/mixed. Then each contained type must have 
> its own Info-Package header. If you want to allow multiple packages 
> per INFO then you need to negotiate support for "multipart". Or maybe 
> we require support of multipart if you support any other package type.
> 
> 	Thanks,
> 	Paul
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors@cs.columbia.edu for questions on current sip Use 
> sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 23 00:13:39 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 469793A6930;
	Thu, 23 Oct 2008 00:13:39 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 825A43A6930
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 00:13:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.209
X-Spam-Level: 
X-Spam-Status: No, score=-6.209 tagged_above=-999 required=5 tests=[AWL=0.040, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Fkz+khsi9dy7 for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 00:13:37 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id B85353A68AA
	for <sip@ietf.org>; Thu, 23 Oct 2008 00:13:36 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	20B4F2047F; Thu, 23 Oct 2008 09:14:33 +0200 (CEST)
X-AuditID: c1b4fb3e-ae785bb00000537b-31-49002458fd7f
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	E8E2420362; Thu, 23 Oct 2008 09:14:32 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 09:14:32 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 23 Oct 2008 09:14:31 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF088F10C6@esealmw113.eemea.ericsson.se>
In-Reply-To: <5D1A7985295922448D5550C94DE2918002425ADD@DEEXC1U01.de.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
Thread-Index: Ack0cryxPINIzsANRGyXA7Zi2Gh2FwAG1y8AABQiq5A=
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF93@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425AC4@DEEXC1U01.de.lucent.com>
	<48FF6EB1.4000407@cisco.com>
	<5D1A7985295922448D5550C94DE2918002425ADD@DEEXC1U01.de.lucent.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>,
	"Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 23 Oct 2008 07:14:32.0354 (UTC)
	FILETIME=[FF124020:01C934DE]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi,

I think that the packages should have no dependency at all - and it's an
implementation issue in which order they are processed, etc.

So, IF the UAC really wants to ensure that package X is processed before
package Y, the UAC should send them in SEPARATE INFOs, and wait for the
X package INFO response before sending the Y package INFO.

Regards,

Christer






-----Original Message-----
From: DRAGE, Keith (Keith) [mailto:drage@alcatel-lucent.com] 
Sent: 23. lokakuuta 2008 0:46
To: Paul Kyzivat
Cc: Christer Holmberg; SIP IETF; Eric Burger
Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple packages per
INFO

Thanks for the direct answer to my question.

> IMO sending two info packages in separate INFO messages should produce

> the same behavior as sending them in one.
> Except perhaps for order of processing. If we choose to define sending

> two in one INFO, then I think we need to specify how the ordering is 
> supposed to work. (E.g. that they should be processed in the same 
> order as they appear in the multipart, and that in such case the 
> behavior MUST be the same as if they were sent in separate messages in

> that order.)

Surely here you are implying that the two packages have a dependency.
That's two steps of use cases, i.e. that there is a requirement for more
than one use case in the first place, and then the use case for the two
packages being interdependent in terms of data content.

If there is not such dependency, but the two packages both require in
order delivery for their own data, then surely each package not sending
the next INFO until it has received the response for the previous one
within its package is a sufficient mechanism at the level of INFO and
the body packaging.

Regards

Keith

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> Sent: Wednesday, October 22, 2008 7:19 PM
> To: DRAGE, Keith (Keith)
> Cc: Christer Holmberg; SIP IETF; Eric Burger
> Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages 
> per INFO
> 
> Keith,
> 
> IMO sending two info packages in separate INFO messages should produce

> the same behavior as sending them in one.
> Except perhaps for order of processing. If we choose to define sending

> two in one INFO, then I think we need to specify how the ordering is 
> supposed to work. (E.g. that they should be processed in the same 
> order as they appear in the multipart, and that in such case the 
> behavior MUST be the same as if they were sent in separate messages in

> that order.)
> 
> The one advantage that comes to mind is that if you can't do this, 
> then you really need to wait for the round trip of one info before 
> sending another, which could be inconvenient and delay inducing if you

> get the data for more than one at the same time.
> 
> But we could certainly just decide not to define that now, and leave 
> it till later to decide if sending multiple packages is useful.
> 
> An problem with defining this is that it introduces another sort of 
> error to handle if one package can be dealt with but another cannot.
> 
> I guess I'd be inclined not to define it for now.
> 
> 	Thanks,
> 	Paul
> 
> 
> 
> DRAGE, Keith (Keith) wrote:
> > Christer said in reply to me:
> > 
> >>> Why does putting two different packages in the same INFO
> work better
> >>> than two different INFO messages each with their own package
> >> usage? Is
> >>> there a desirable relationship that can be implemented
> >> between the two
> >>> that we would otherwise lose?
> >> Well, that brings up a good question: assuming it is
> allowed to send
> >> multiple info packages in a single INFO, does that
> automatically mean
> >> that there must be a desirable relationship? I don't think so.
> >>  
> >> If there is a relationship that should be described in the 
> >> application logic itself.
> > 
> > That was not an answer to my question.
> > 
> > What I was trying to get to was whether providing two INFOs
> each containing one package provided the same solution as one INFO 
> containing two packages  (and assuming anyone has a use case for two 
> packages on the same dialog - something I don't believe I have yet 
> seen presented to the list - did I miss it somewhere).
> > 
> > If the answer is yes, then it becomes a matter of deciding
> whether we want one solution or two to be documented, and if one, then

> which one.
> > 
> > If the answer is no, then we need to understand the why and
> wherefore of those differences before deciding what documentation to 
> provide.
> > 
> > Regards
> > 
> > Keith
> > 
> >> -----Original Message-----
> >> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> >> Sent: Wednesday, October 22, 2008 6:20 PM
> >> To: DRAGE, Keith (Keith); Paul Kyzivat; SIP IETF; Eric Burger
> >> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple
> packages
> >> per INFO
> >>
> >> Hi,
> >>
> >>> Just because SIP requires (or now nearly requires) multipart body 
> >>> handling doesn't mean that we have to define the meaning
> of multiple
> >>> bodies of the same type for every usage.
> >> Of course not. But, unless there are good reasons I don't think we 
> >> should forbid it - in case there will be future use-cases where it 
> >> could be useful.
> >>
> >>> And surely there are wider things bound up here. For example
> >> is it not
> >>> still up to the application using INFO to ensure in order
> >> delivery if
> >>> that is what it requires. One way of doing this is to
> constrain the
> >>> transport mechanism to not send another INFO until the
> previous has
> >>> been acknowledged. If so, then different applications may have 
> >>> different requirements in this respect that interact.
> >> Correct. So, this would only be used if it fulfills all those 
> >> requirements.
> >>
> >>> Why does putting two different packages in the same INFO
> work better
> >>> than two different INFO messages each with their own package
> >> usage? Is
> >>> there a desirable relationship that can be implemented
> >> between the two
> >>> that we would otherwise lose?
> >> Well, that brings up a good question: assuming it is
> allowed to send
> >> multiple info packages in a single INFO, does that
> automatically mean
> >> that there must be a desirable relationship? I don't think so.
> >>  
> >> If there is a relationship that should be described in the 
> >> application logic itself.
> >>  
> >> Regards,
> >>  
> >> Christer
> >>  
> >>  
> >>  
> >>
> >>> -----Original Message-----
> >>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
> >> Behalf Of
> >>> Christer Holmberg
> >>> Sent: Wednesday, October 22, 2008 8:54 AM
> >>> To: Paul Kyzivat; SIP IETF; Eric Burger
> >>> Subject: Re: [Sip] draft-ietf-sip-info-events-00: 
> multiple packages
> >>> per INFO
> >>>
> >>>
> >>> Hi,
> >>>
> >>> Doesn't the body handling draft say that one MUST be able
> to parse
> >>> multipart message bodies?
> >>>
> >>> So, I don't think we should forbid the usage of multiple
> packages. 
> >>> There MAY be use-cases where it is useful, so...
> >>>
> >>> I also think that the negotiation of multipart support is more 
> >>> generic, so such mechanism should not be bound to INFO packages.
> >>>
> >>> Regards,
> >>>
> >>> Christer
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> -----Original Message-----
> >>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
> >> Behalf Of
> >>> Paul Kyzivat
> >>> Sent: 21. lokakuuta 2008 17:45
> >>> To: SIP IETF; Eric Burger
> >>> Subject: [Sip] draft-ietf-sip-info-events-00: multiple
> packages per
> >>> INFO
> >>>
> >>> Re the question about multiple packages per INFO:
> >>>
> >>>     There MUST be exactly one Info Package type listed per 
> >>> Info-Package
> >>>     header.  Multiple Info-Packages per INFO message are
> disallowed.
> >>>
> >>>     [EDITOR NOTE: Really?  Why not multiple Info-Packages, in a
> >>>     multipart/mime?  Well, I thought of one: it is hard to 
> >>> disambiguate.
> >>>     For example, take an INFO message with an Info-Package: 
> >> key_image,
> >>>     caller_picture.  I then have a multipart/mime with,
> you guessed
> >>> it,
> >>>     an image/jpeg and an image/jpeg.  I would offer we do
> >> allow this
> >>> and
> >>>     require the MIME parse order of the body match the
> order of the
> >>> Info-
> >>>     Package enumerations; if you have too many packages or
> >> body parts
> >>> or
> >>>     they do not align, you barf.  However, I timed out on
> this and
> >>> thus
> >>>     we will have to wait for the next version for me to
> flesh this
> >>> out.
> >>>     If we do do this, then we'll reference RFC 3261 as updated by
> >>>     draft-ietf-sip-body-handling to require multipart MIME
> >> handling.]
> >>> How about defining an initial package type of "multipart". 
> >> It allows
> >>> only content-type multipart/mixed. Then each contained type
> >> must have
> >>> its own Info-Package header. If you want to allow
> multiple packages
> >>> per INFO then you need to negotiate support for
> >> "multipart". Or maybe
> >>> we require support of multipart if you support any other
> >> package type.
> >>>       Thanks,
> >>>       Paul
> >>> _______________________________________________
> >>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> >>> This list is for NEW development of the core SIP Protocol Use 
> >>> sip-implementors@cs.columbia.edu for questions on current sip Use 
> >>> sipping@ietf.org for new developments on the application of sip 
> >>> _______________________________________________
> >>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> >>> This list is for NEW development of the core SIP Protocol Use 
> >>> sip-implementors@cs.columbia.edu for questions on current sip Use 
> >>> sipping@ietf.org for new developments on the application of sip
> >>>
> >>
> > 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 23 00:16:43 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0DFCA3A6BE5;
	Thu, 23 Oct 2008 00:16:43 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7C6913A6BE5
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 00:16:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.209
X-Spam-Level: 
X-Spam-Status: No, score=-6.209 tagged_above=-999 required=5 tests=[AWL=0.040, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id p0hRLrjfhcoE for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 00:16:40 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id AFCA13A68AA
	for <sip@ietf.org>; Thu, 23 Oct 2008 00:16:40 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	B874A2058A; Thu, 23 Oct 2008 09:17:10 +0200 (CEST)
X-AuditID: c1b4fb3e-ac781bb00000537b-e9-490024f6b615
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	A4F6C211CA; Thu, 23 Oct 2008 09:17:10 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 09:17:10 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 23 Oct 2008 09:17:09 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>
In-Reply-To: <D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
Thread-Index: Ack0qTKM+IYZmRSGSa699sptsTBiEAANfbXA
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Dean Willis" <dean.willis@softarmor.com>,
	"DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
X-OriginalArrivalTime: 23 Oct 2008 07:17:10.0225 (UTC)
	FILETIME=[5D2B7410:01C934DF]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>,
	Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>Why does putting two different packages in the same INFO work better 
>>than two different INFO messages each with their own package usage? Is

>>there a desirable relationship that can be implemented between the two

>>that we would otherwise lose?
>
>We have one package per NOTIFY. Let's stick with one package per INFO,
unless we want to go back to using mime-types as the only distinguisher
of packages.

I raised that issue in another e-mail.

But, never the less, I have no strong feelings on the single versus
multiple package issue.

Regards,

Christer


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


From sip-bounces@ietf.org  Thu Oct 23 02:29:57 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DB9533A6C2D;
	Thu, 23 Oct 2008 02:29:57 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4F1953A691A
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 02:29:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level: 
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[AWL=0.049, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id icAVGkgJqU0V for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 02:29:51 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id 8E9C23A6C2D
	for <sip@ietf.org>; Thu, 23 Oct 2008 02:29:51 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K9600A2CQDKOA@siemenscomms.co.uk> for sip@ietf.org; Thu,
	23 Oct 2008 10:29:44 +0100 (BST)
Date: Thu, 23 Oct 2008 10:29:42 +0100
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: A
	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>,
	Dean Willis <dean.willis@softarmor.com>,
	"DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
Thread-Index: Ack0qTKM+IYZmRSGSa699sptsTBiEAANfbXAAAR/FbA=
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com> A
	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>,
	Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

In reply to this whole thread, please bear in mind that we had lots of
discussion about whether it would be worthwhile defining this new INFO
mechanism, since existing applications are unlikely to change and the
best we can hope for is that new applications will exploit the new
mechanism. Therefore we want to keep the mechanism as simple as
possible. The complexities of matching body parts to header fields,
dealing with cases where only some of the packages are understood, etc.
are hardly likely to persuade people to implement the mechanism. Please
keep it simple.

John


> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Christer Holmberg
> Sent: 23 October 2008 08:17
> To: Dean Willis; DRAGE, Keith (Keith)
> Cc: SIP IETF; Eric Burger; Paul Kyzivat
> Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple 
> packages per INFO
> 
> 
> Hi, 
> 
> >>Why does putting two different packages in the same INFO 
> work better 
> >>than two different INFO messages each with their own 
> package usage? Is
> 
> >>there a desirable relationship that can be implemented 
> between the two
> 
> >>that we would otherwise lose?
> >
> >We have one package per NOTIFY. Let's stick with one package 
> per INFO,
> unless we want to go back to using mime-types as the only 
> distinguisher
> of packages.
> 
> I raised that issue in another e-mail.
> 
> But, never the less, I have no strong feelings on the single versus
> multiple package issue.
> 
> Regards,
> 
> Christer
> 
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 23 02:50:40 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BFC8F3A6C34;
	Thu, 23 Oct 2008 02:50:40 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 695573A693D
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 02:50:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.21
X-Spam-Level: 
X-Spam-Status: No, score=-6.21 tagged_above=-999 required=5 tests=[AWL=0.039, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YbY4Zl3T9xAi for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 02:50:38 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id F2FA93A6C34
	for <sip@ietf.org>; Thu, 23 Oct 2008 02:50:37 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	6F07A21E6F; Thu, 23 Oct 2008 11:51:21 +0200 (CEST)
X-AuditID: c1b4fb3e-ae785bb00000537b-3e-49004919920c
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	45CEC21848; Thu, 23 Oct 2008 11:51:21 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 11:51:20 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 23 Oct 2008 11:51:20 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF088F17D5@esealmw113.eemea.ericsson.se>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
Thread-Index: Ack0qTKM+IYZmRSGSa699sptsTBiEAANfbXAAAR/FbAAAOJCYA==
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com> A
	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Elwell, John" <john.elwell@siemens.com>,
	"Dean Willis" <dean.willis@softarmor.com>,
	"DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
X-OriginalArrivalTime: 23 Oct 2008 09:51:20.0644 (UTC)
	FILETIME=[E6D96040:01C934F4]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>,
	Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi,

I agree with John. Let's keep it simple. If allowing multiple packages
in a single INFO causes issues, let's forget about it.

The whole idea with this is to allow people using INFO to do so in an
easy and standardized way, so let's not shoot ourselves in the foot with
complexity.

Regards,

Christer 

-----Original Message-----
From: Elwell, John [mailto:john.elwell@siemens.com] 
Sent: 23. lokakuuta 2008 12:30
To: Christer Holmberg; Dean Willis; DRAGE, Keith (Keith)
Cc: SIP IETF; Eric Burger; Paul Kyzivat
Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple packages per
INFO

In reply to this whole thread, please bear in mind that we had lots of
discussion about whether it would be worthwhile defining this new INFO
mechanism, since existing applications are unlikely to change and the
best we can hope for is that new applications will exploit the new
mechanism. Therefore we want to keep the mechanism as simple as
possible. The complexities of matching body parts to header fields,
dealing with cases where only some of the packages are understood, etc.
are hardly likely to persuade people to implement the mechanism. Please
keep it simple.

John


> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of 
> Christer Holmberg
> Sent: 23 October 2008 08:17
> To: Dean Willis; DRAGE, Keith (Keith)
> Cc: SIP IETF; Eric Burger; Paul Kyzivat
> Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages 
> per INFO
> 
> 
> Hi,
> 
> >>Why does putting two different packages in the same INFO
> work better
> >>than two different INFO messages each with their own
> package usage? Is
> 
> >>there a desirable relationship that can be implemented
> between the two
> 
> >>that we would otherwise lose?
> >
> >We have one package per NOTIFY. Let's stick with one package
> per INFO,
> unless we want to go back to using mime-types as the only 
> distinguisher of packages.
> 
> I raised that issue in another e-mail.
> 
> But, never the less, I have no strong feelings on the single versus 
> multiple package issue.
> 
> Regards,
> 
> Christer
> 
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors@cs.columbia.edu for questions on current sip Use 
> sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 23 02:54:52 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AA58E28C178;
	Thu, 23 Oct 2008 02:54:52 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9BA1028C178
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 02:54:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[AWL=0.047, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ec11v76dSfaY for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 02:54:43 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id 9B5BA3A6C2C
	for <sip@ietf.org>; Thu, 23 Oct 2008 02:54:42 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K9600C4WRIC5J@siemenscomms.co.uk> for sip@ietf.org; Thu,
	23 Oct 2008 10:54:36 +0100 (BST)
Date: Thu, 23 Oct 2008 10:54:30 +0100
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: A
	<CA9998CD4A020D418654FCDEF4E707DF0889EAE5@esealmw113.eemea.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>,
	Paul Kyzivat <pkyzivat@cisco.com>, SIP IETF <sip@ietf.org>,
	Eric Burger <eburger@bea.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D0013491A7@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: package negotiation
Thread-Index: AckzjJNP49uCz7AXST2p9zseGFUriQAm4eFwADLtkHA=
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <48FDEC6B.8090006@cisco.com> A
	<CA9998CD4A020D418654FCDEF4E707DF0889EAE5@esealmw113.eemea.ericsson.se>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: package negotiation
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I can't help wondering whether treating this like offer-answer is the
wrong approach. With offer-answer, an offer has a different semantic
meaning to an answer, particularly when it comes to more advanced
features such as SDP capability negotiation. Since offers and answers
are not explicitly indicated as such (unfortunately), we have to have
very precise rules for which messages contain offers and which contain
answers, so that there is no confusion.

I don't think Send-Info and Recv-Info have quite the same
characteristics. What problems would be introduced if we just said that
any request or any response can contain Send-Info and/or Recv-Info, and
that the latest one you send or receive is the one that applies? There
might be some scope for getting out of step, but I am having difficult
identifying really convincing concerns. It seems a lot cleaner than
introducing a whole lot of new state machinery similar to offer-answer.

John

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Christer Holmberg
> Sent: 22 October 2008 10:36
> To: Paul Kyzivat; SIP IETF; Eric Burger
> Subject: Re: [Sip] draft-ietf-sip-info-events-00: package negotiation
> 
> 
> Hi, 
> 
> >General issues with the negotiation mechanism:
> >
> >What happens if the initial INVITE by a UAC includes only 
> Send-Info or
> Recv-Info? Does that indicate a "half-legacy" device??? Or 
> does it delay
> negotiation for one but not the other? Or does 
> >the presence of one mean the absence of the other is equivalent to an
> empty one?
> >
> >As I think about it, I don't think its really necessary to treat the
> absence of these headers as meaning "legacy". Treating the absence of
> these headers as equivalent to their presence without 
> >any packages is sufficient to get the proper legacy behavior. The
> tricky part is figuring out out when their absence *doesn't* 
> mean that,
> which is significant only in the non-legacy case. In 
> >particular, when they aren't present in INVITE it means 
> deferral of the
> "offer" to the UAS. And possibly absence in an UPDATE means "don't
> renegotiate"???
> 
> I don't think the presence, or absence, of the S/R-Info headers should
> in any way be connected to legacy in any way. A UA can be legacy no
> matter if the headers are present, or not present, but that 
> is all done
> based on "configuration", as described in the draft.
> 
> So, if a UAC only included Send-Info, it means that it only supports
> sending of Info packages. Then, it may, or may not, also 
> support legacy
> INFO usages, but that is completely separated.
> 
> 
> >I'm confused by the three way negotiation of info packages in
> INVITE/2xx/ACK. Its allowed when the Send-Info/Recv-Info are in the
> INVITE, but not when they are deferred to the INVITE response, 
> >or when they are conveyed in UPDATE and its response. If the 
> three way
> handshake is needed to seal the deal, then those other 
> options should be
> off the table. But the "deferred offer" of these 
> >is really needed, so it can't be off the table. Or is this just an
> extra benefit that can be exploited when possible?
> >
> >Also, I don't see any provision for additional round(s) of 
> negotiation
> before 2xx via PRACK and UPDATE, though there is provision for
> additional "half-negotiations" via provisional responses 
> >and the final response. Given the parallels with O/A, I'd 
> prefer to see
> them more aligned in this regard, though I can be talked out of that
> with a good argument.
> 
> I agree (I think :). The negotiation whould be 2-way. Then, based on
> what the UAC gets from the UAS, it may send a PRACK/UPDATE/re-INVITE
> with a new set of supported Info packages, but that is a new 2-way
> negotiation transaction.
> 
> 
> >I'd also like to take advantage of the lessons that have been learned
> with O/A and nail down more of the semantics now. One issue that leaps
> to mind in that regard is what happens if we start 
> >to negotiate info packages in a reINVITE and then the reINVITE fails?
> 
> That's a good point.
> 
> I think we should use the same rule as for offer/answer. 
> Because, assume
> I send you a new set of packages in a re-INVITE, and you send 
> me back a
> set in a 18x. Then we may start using info packages based on that
> negotiation long before the re-INVITE is rejected.
> 
> >IMO what is needed is a state model for this stuff, added to 
> the state
> for an invite-dialog-usage. This state should determine which packages
> may be sent, and which should be received without 
> >error. We should be very clear about exactly which events 
> cause changes
> to this state.
> >
> >Even then there are race conditions that need to be clarified. For
> >instance: Suppose, as a result of an INVITE/1xx exchange 
> between Alice
> and Bob, that packages P & Q are allowed to be sent from 
> Alice to Bob. 
> >Alice then sends an INFO with package Q, and at the same 
> time Bob sends
> a 2xx that only allows the receipt of package P. Then Bob receives the
> INFO with package Q. What should happen?
> >
> >Another issue is that if the Send-Info/Recv-Info contents change in
> subsequent 1xx responses to the same INVITE, the UAS has no guarantee
> that they are received. So any reduction in what can be 
> >received cannot be counted upon until the 2xx/ACK.
> 
> True. But, I wonder whether this will really be a real-life problem.
> 
> And, we could a response code (4xx Info package not 
> supported), which is
> used by the UAS if it receives an info package which it 
> doesn't support.
> Then the UAC knows.
> 
> Regards.
> 
> Christer
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 23 03:31:06 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7E3673A69A3;
	Thu, 23 Oct 2008 03:31:06 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4A79C3A69A3
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 03:31:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.676
X-Spam-Level: 
X-Spam-Status: No, score=-2.676 tagged_above=-999 required=5
	tests=[AWL=-0.077, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Nl9Zqx5ZwwO8 for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 03:30:56 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37])
	by core3.amsl.com (Postfix) with ESMTP id 72F083A684D
	for <sip@ietf.org>; Thu, 23 Oct 2008 03:30:53 -0700 (PDT)
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1])
	by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id m9NAT2lY011652;
	Thu, 23 Oct 2008 05:29:08 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by
	ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 05:29:04 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.30]) by
	DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 12:29:02 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Thu, 23 Oct 2008 12:29:00 +0200
Message-ID: <5D1A7985295922448D5550C94DE2918002425C2C@DEEXC1U01.de.lucent.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF088F17D5@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
Thread-Index: Ack0qTKM+IYZmRSGSa699sptsTBiEAANfbXAAAR/FbAAAOJCYAABVQTQ
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com> A
	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>
	<CA9998CD4A020D418654FCDEF4E707DF088F17D5@esealmw113.eemea.ericsson.se>
From: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: "Christer Holmberg" <christer.holmberg@ericsson.com>,
	"Elwell, John" <john.elwell@siemens.com>,
	"Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 23 Oct 2008 10:29:02.0378 (UTC)
	FILETIME=[2AF298A0:01C934FA]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>,
	Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I don't have a problem agreeing with that.

Note that buried somewhere in this thread was a question of whether we
had a use case for multiple packages per dialog, or can we simplify even
further.

Keith 

> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] 
> Sent: Thursday, October 23, 2008 10:51 AM
> To: Elwell, John; Dean Willis; DRAGE, Keith (Keith)
> Cc: SIP IETF; Eric Burger; Paul Kyzivat
> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple 
> packages per INFO
> 
> 
> Hi,
> 
> I agree with John. Let's keep it simple. If allowing multiple 
> packages in a single INFO causes issues, let's forget about it.
> 
> The whole idea with this is to allow people using INFO to do 
> so in an easy and standardized way, so let's not shoot 
> ourselves in the foot with complexity.
> 
> Regards,
> 
> Christer 
> 
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens.com]
> Sent: 23. lokakuuta 2008 12:30
> To: Christer Holmberg; Dean Willis; DRAGE, Keith (Keith)
> Cc: SIP IETF; Eric Burger; Paul Kyzivat
> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple 
> packages per INFO
> 
> In reply to this whole thread, please bear in mind that we 
> had lots of discussion about whether it would be worthwhile 
> defining this new INFO mechanism, since existing applications 
> are unlikely to change and the best we can hope for is that 
> new applications will exploit the new mechanism. Therefore we 
> want to keep the mechanism as simple as possible. The 
> complexities of matching body parts to header fields, dealing 
> with cases where only some of the packages are understood, etc.
> are hardly likely to persuade people to implement the 
> mechanism. Please keep it simple.
> 
> John
> 
> 
> > -----Original Message-----
> > From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of 
> > Christer Holmberg
> > Sent: 23 October 2008 08:17
> > To: Dean Willis; DRAGE, Keith (Keith)
> > Cc: SIP IETF; Eric Burger; Paul Kyzivat
> > Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages 
> > per INFO
> > 
> > 
> > Hi,
> > 
> > >>Why does putting two different packages in the same INFO
> > work better
> > >>than two different INFO messages each with their own
> > package usage? Is
> > 
> > >>there a desirable relationship that can be implemented
> > between the two
> > 
> > >>that we would otherwise lose?
> > >
> > >We have one package per NOTIFY. Let's stick with one package
> > per INFO,
> > unless we want to go back to using mime-types as the only 
> > distinguisher of packages.
> > 
> > I raised that issue in another e-mail.
> > 
> > But, never the less, I have no strong feelings on the single versus 
> > multiple package issue.
> > 
> > Regards,
> > 
> > Christer
> > 
> > 
> > _______________________________________________
> > Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol Use 
> > sip-implementors@cs.columbia.edu for questions on current sip Use 
> > sipping@ietf.org for new developments on the application of sip
> > 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 23 03:41:01 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AD2BD28C11C;
	Thu, 23 Oct 2008 03:41:01 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 257CB3A6959
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 03:41:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.21
X-Spam-Level: 
X-Spam-Status: No, score=-6.21 tagged_above=-999 required=5 tests=[AWL=0.039, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ZEm9lbql-VJJ for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 03:40:51 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 292EE3A6C32
	for <sip@ietf.org>; Thu, 23 Oct 2008 03:40:50 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	8693C20B07; Thu, 23 Oct 2008 12:41:14 +0200 (CEST)
X-AuditID: c1b4fb3c-ac8cbbb0000015b5-95-490054ca912d
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	6297720EED; Thu, 23 Oct 2008 12:41:14 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 12:41:14 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 23 Oct 2008 12:41:13 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF088F19BA@esealmw113.eemea.ericsson.se>
In-Reply-To: <5D1A7985295922448D5550C94DE2918002425C2C@DEEXC1U01.de.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
Thread-Index: Ack0qTKM+IYZmRSGSa699sptsTBiEAANfbXAAAR/FbAAAOJCYAABVQTQAABjsqA=
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com> A
	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>
	<CA9998CD4A020D418654FCDEF4E707DF088F17D5@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425C2C@DEEXC1U01.de.lucent.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>,
	"Elwell, John" <john.elwell@siemens.com>,
	"Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 23 Oct 2008 10:41:14.0137 (UTC)
	FILETIME=[DF1C2890:01C934FB]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>,
	Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>I don't have a problem agreeing with that.
>
>Note that buried somewhere in this thread was a question of whether we
had a use case for multiple packages per dialog, or can we simplify even
further.

I don't think we should go that far, because that could become very
restrictive.

For example, assume I want to use INFO packages e.g. for DTMF during the
call setup, and then other INFO package(s) for something else during the
call.

Regards,

Christer


> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> Sent: Thursday, October 23, 2008 10:51 AM
> To: Elwell, John; Dean Willis; DRAGE, Keith (Keith)
> Cc: SIP IETF; Eric Burger; Paul Kyzivat
> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple packages 
> per INFO
> 
> 
> Hi,
> 
> I agree with John. Let's keep it simple. If allowing multiple packages

> in a single INFO causes issues, let's forget about it.
> 
> The whole idea with this is to allow people using INFO to do so in an 
> easy and standardized way, so let's not shoot ourselves in the foot 
> with complexity.
> 
> Regards,
> 
> Christer
> 
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens.com]
> Sent: 23. lokakuuta 2008 12:30
> To: Christer Holmberg; Dean Willis; DRAGE, Keith (Keith)
> Cc: SIP IETF; Eric Burger; Paul Kyzivat
> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple packages 
> per INFO
> 
> In reply to this whole thread, please bear in mind that we had lots of

> discussion about whether it would be worthwhile defining this new INFO

> mechanism, since existing applications are unlikely to change and the 
> best we can hope for is that new applications will exploit the new 
> mechanism. Therefore we want to keep the mechanism as simple as 
> possible. The complexities of matching body parts to header fields, 
> dealing with cases where only some of the packages are understood, 
> etc.
> are hardly likely to persuade people to implement the mechanism. 
> Please keep it simple.
> 
> John
> 
> 
> > -----Original Message-----
> > From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
> Behalf Of
> > Christer Holmberg
> > Sent: 23 October 2008 08:17
> > To: Dean Willis; DRAGE, Keith (Keith)
> > Cc: SIP IETF; Eric Burger; Paul Kyzivat
> > Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages 
> > per INFO
> > 
> > 
> > Hi,
> > 
> > >>Why does putting two different packages in the same INFO
> > work better
> > >>than two different INFO messages each with their own
> > package usage? Is
> > 
> > >>there a desirable relationship that can be implemented
> > between the two
> > 
> > >>that we would otherwise lose?
> > >
> > >We have one package per NOTIFY. Let's stick with one package
> > per INFO,
> > unless we want to go back to using mime-types as the only 
> > distinguisher of packages.
> > 
> > I raised that issue in another e-mail.
> > 
> > But, never the less, I have no strong feelings on the single versus 
> > multiple package issue.
> > 
> > Regards,
> > 
> > Christer
> > 
> > 
> > _______________________________________________
> > Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol Use 
> > sip-implementors@cs.columbia.edu for questions on current sip Use 
> > sipping@ietf.org for new developments on the application of sip
> > 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 23 04:09:16 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2AD4A3A6C5C;
	Thu, 23 Oct 2008 04:09:16 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 132B43A6C5C
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 04:09:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.675
X-Spam-Level: 
X-Spam-Status: No, score=-2.675 tagged_above=-999 required=5
	tests=[AWL=-0.076, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id G+sb9rb8jJyt for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 04:09:05 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33])
	by core3.amsl.com (Postfix) with ESMTP id F39A73A6C50
	for <sip@ietf.org>; Thu, 23 Oct 2008 04:09:04 -0700 (PDT)
Received: from ilexp03.ndc.lucent.com (h135-3-39-50.lucent.com [135.3.39.50])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id m9NB8YIQ009356; 
	Thu, 23 Oct 2008 06:08:57 -0500 (CDT)
Received: from DEEXP02.DE.lucent.com ([135.248.187.66]) by
	ilexp03.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 06:07:59 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.30]) by
	DEEXP02.DE.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 13:07:45 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Thu, 23 Oct 2008 13:07:44 +0200
Message-ID: <5D1A7985295922448D5550C94DE2918002425C50@DEEXC1U01.de.lucent.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF088F19BA@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
Thread-Index: Ack0qTKM+IYZmRSGSa699sptsTBiEAANfbXAAAR/FbAAAOJCYAABVQTQAABjsqAAAO/WsA==
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com> A
	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>
	<CA9998CD4A020D418654FCDEF4E707DF088F17D5@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425C2C@DEEXC1U01.de.lucent.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F19BA@esealmw113.eemea.ericsson.se>
From: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: "Christer Holmberg" <christer.holmberg@ericsson.com>,
	"Elwell, John" <john.elwell@siemens.com>,
	"Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 23 Oct 2008 11:07:45.0427 (UTC)
	FILETIME=[9397BE30:01C934FF]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>,
	Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

It may be restrictive, but will anyone notice the restriction?

Is there anyone out there who has a current use case for two packages
per dialog - rather than "I've definitely used one therefore want to
reserve my options in case I need a second"?

Keith



> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] 
> Sent: Thursday, October 23, 2008 11:41 AM
> To: DRAGE, Keith (Keith); Elwell, John; Dean Willis
> Cc: SIP IETF; Eric Burger; Paul Kyzivat
> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple 
> packages per INFO
> 
> 
> Hi, 
> 
> >I don't have a problem agreeing with that.
> >
> >Note that buried somewhere in this thread was a question of 
> whether we
> had a use case for multiple packages per dialog, or can we 
> simplify even further.
> 
> I don't think we should go that far, because that could 
> become very restrictive.
> 
> For example, assume I want to use INFO packages e.g. for DTMF 
> during the call setup, and then other INFO package(s) for 
> something else during the call.
> 
> Regards,
> 
> Christer
> 
> 
> > -----Original Message-----
> > From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> > Sent: Thursday, October 23, 2008 10:51 AM
> > To: Elwell, John; Dean Willis; DRAGE, Keith (Keith)
> > Cc: SIP IETF; Eric Burger; Paul Kyzivat
> > Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple packages 
> > per INFO
> > 
> > 
> > Hi,
> > 
> > I agree with John. Let's keep it simple. If allowing 
> multiple packages
> 
> > in a single INFO causes issues, let's forget about it.
> > 
> > The whole idea with this is to allow people using INFO to 
> do so in an 
> > easy and standardized way, so let's not shoot ourselves in the foot 
> > with complexity.
> > 
> > Regards,
> > 
> > Christer
> > 
> > -----Original Message-----
> > From: Elwell, John [mailto:john.elwell@siemens.com]
> > Sent: 23. lokakuuta 2008 12:30
> > To: Christer Holmberg; Dean Willis; DRAGE, Keith (Keith)
> > Cc: SIP IETF; Eric Burger; Paul Kyzivat
> > Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple packages 
> > per INFO
> > 
> > In reply to this whole thread, please bear in mind that we 
> had lots of
> 
> > discussion about whether it would be worthwhile defining 
> this new INFO
> 
> > mechanism, since existing applications are unlikely to 
> change and the 
> > best we can hope for is that new applications will exploit the new 
> > mechanism. Therefore we want to keep the mechanism as simple as 
> > possible. The complexities of matching body parts to header fields, 
> > dealing with cases where only some of the packages are understood, 
> > etc.
> > are hardly likely to persuade people to implement the mechanism. 
> > Please keep it simple.
> > 
> > John
> > 
> > 
> > > -----Original Message-----
> > > From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
> > Behalf Of
> > > Christer Holmberg
> > > Sent: 23 October 2008 08:17
> > > To: Dean Willis; DRAGE, Keith (Keith)
> > > Cc: SIP IETF; Eric Burger; Paul Kyzivat
> > > Subject: Re: [Sip] draft-ietf-sip-info-events-00: 
> multiple packages 
> > > per INFO
> > > 
> > > 
> > > Hi,
> > > 
> > > >>Why does putting two different packages in the same INFO
> > > work better
> > > >>than two different INFO messages each with their own
> > > package usage? Is
> > > 
> > > >>there a desirable relationship that can be implemented
> > > between the two
> > > 
> > > >>that we would otherwise lose?
> > > >
> > > >We have one package per NOTIFY. Let's stick with one package
> > > per INFO,
> > > unless we want to go back to using mime-types as the only 
> > > distinguisher of packages.
> > > 
> > > I raised that issue in another e-mail.
> > > 
> > > But, never the less, I have no strong feelings on the 
> single versus 
> > > multiple package issue.
> > > 
> > > Regards,
> > > 
> > > Christer
> > > 
> > > 
> > > _______________________________________________
> > > Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> > > This list is for NEW development of the core SIP Protocol Use 
> > > sip-implementors@cs.columbia.edu for questions on current sip Use 
> > > sipping@ietf.org for new developments on the application of sip
> > > 
> > 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 23 04:14:35 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 042CC28C0EA;
	Thu, 23 Oct 2008 04:14:35 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 183AA3A6C70
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 04:14:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.211
X-Spam-Level: 
X-Spam-Status: No, score=-6.211 tagged_above=-999 required=5 tests=[AWL=0.038, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UEktHMVX+VKw for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 04:14:26 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 69ED83A6C5A
	for <sip@ietf.org>; Thu, 23 Oct 2008 04:14:26 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	5E59C20F44; Thu, 23 Oct 2008 13:15:28 +0200 (CEST)
X-AuditID: c1b4fb3c-af0d0bb0000015b5-c7-49005cd04a86
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	3274F208AE; Thu, 23 Oct 2008 13:15:28 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 13:15:27 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 23 Oct 2008 13:15:27 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF088F1B10@esealmw113.eemea.ericsson.se>
In-Reply-To: <5D1A7985295922448D5550C94DE2918002425C50@DEEXC1U01.de.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
Thread-Index: Ack0qTKM+IYZmRSGSa699sptsTBiEAANfbXAAAR/FbAAAOJCYAABVQTQAABjsqAAAO/WsAAAMjWQ
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com> A
	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>
	<CA9998CD4A020D418654FCDEF4E707DF088F17D5@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425C2C@DEEXC1U01.de.lucent.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F19BA@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425C50@DEEXC1U01.de.lucent.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>,
	"Elwell, John" <john.elwell@siemens.com>,
	"Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 23 Oct 2008 11:15:27.0930 (UTC)
	FILETIME=[A74419A0:01C93500]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>,
	Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>It may be restrictive, but will anyone notice the restriction?

Maybe not today, but who knows about tomorrow.

>Is there anyone out there who has a current use case for two packages
per dialog - rather than "I've definitely used one therefore want to
reserve my options in case I need a second"?

I send DTMFs during call setup, and then you and me use some application
which use INFO during the call.

I don't have a more detailed use-case than that at the moment. But, I
don't think allowing many packages makes it more complex, and I really
think it is restrictive. Then, IF someone needs it, they will go on with
"legacy" usage, since they can't use info packages...

Regards,

Christer




> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> Sent: Thursday, October 23, 2008 11:41 AM
> To: DRAGE, Keith (Keith); Elwell, John; Dean Willis
> Cc: SIP IETF; Eric Burger; Paul Kyzivat
> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple packages 
> per INFO
> 
> 
> Hi,
> 
> >I don't have a problem agreeing with that.
> >
> >Note that buried somewhere in this thread was a question of
> whether we
> had a use case for multiple packages per dialog, or can we simplify 
> even further.
> 
> I don't think we should go that far, because that could become very 
> restrictive.
> 
> For example, assume I want to use INFO packages e.g. for DTMF during 
> the call setup, and then other INFO package(s) for something else 
> during the call.
> 
> Regards,
> 
> Christer
> 
> 
> > -----Original Message-----
> > From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> > Sent: Thursday, October 23, 2008 10:51 AM
> > To: Elwell, John; Dean Willis; DRAGE, Keith (Keith)
> > Cc: SIP IETF; Eric Burger; Paul Kyzivat
> > Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple packages 
> > per INFO
> > 
> > 
> > Hi,
> > 
> > I agree with John. Let's keep it simple. If allowing
> multiple packages
> 
> > in a single INFO causes issues, let's forget about it.
> > 
> > The whole idea with this is to allow people using INFO to
> do so in an
> > easy and standardized way, so let's not shoot ourselves in the foot 
> > with complexity.
> > 
> > Regards,
> > 
> > Christer
> > 
> > -----Original Message-----
> > From: Elwell, John [mailto:john.elwell@siemens.com]
> > Sent: 23. lokakuuta 2008 12:30
> > To: Christer Holmberg; Dean Willis; DRAGE, Keith (Keith)
> > Cc: SIP IETF; Eric Burger; Paul Kyzivat
> > Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple packages 
> > per INFO
> > 
> > In reply to this whole thread, please bear in mind that we
> had lots of
> 
> > discussion about whether it would be worthwhile defining
> this new INFO
> 
> > mechanism, since existing applications are unlikely to
> change and the
> > best we can hope for is that new applications will exploit the new 
> > mechanism. Therefore we want to keep the mechanism as simple as 
> > possible. The complexities of matching body parts to header fields, 
> > dealing with cases where only some of the packages are understood, 
> > etc.
> > are hardly likely to persuade people to implement the mechanism. 
> > Please keep it simple.
> > 
> > John
> > 
> > 
> > > -----Original Message-----
> > > From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
> > Behalf Of
> > > Christer Holmberg
> > > Sent: 23 October 2008 08:17
> > > To: Dean Willis; DRAGE, Keith (Keith)
> > > Cc: SIP IETF; Eric Burger; Paul Kyzivat
> > > Subject: Re: [Sip] draft-ietf-sip-info-events-00: 
> multiple packages
> > > per INFO
> > > 
> > > 
> > > Hi,
> > > 
> > > >>Why does putting two different packages in the same INFO
> > > work better
> > > >>than two different INFO messages each with their own
> > > package usage? Is
> > > 
> > > >>there a desirable relationship that can be implemented
> > > between the two
> > > 
> > > >>that we would otherwise lose?
> > > >
> > > >We have one package per NOTIFY. Let's stick with one package
> > > per INFO,
> > > unless we want to go back to using mime-types as the only 
> > > distinguisher of packages.
> > > 
> > > I raised that issue in another e-mail.
> > > 
> > > But, never the less, I have no strong feelings on the
> single versus
> > > multiple package issue.
> > > 
> > > Regards,
> > > 
> > > Christer
> > > 
> > > 
> > > _______________________________________________
> > > Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> > > This list is for NEW development of the core SIP Protocol Use 
> > > sip-implementors@cs.columbia.edu for questions on current sip Use 
> > > sipping@ietf.org for new developments on the application of sip
> > > 
> > 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 23 05:09:44 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 983CD3A6B17;
	Thu, 23 Oct 2008 05:09:44 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BDC273A6B17
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 05:09:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level: 
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fHRfyzD7377T for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 05:09:30 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 44B7A3A6A6B
	for <sip@ietf.org>; Thu, 23 Oct 2008 05:09:30 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,470,1220227200"; d="scan'208";a="25386259"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 23 Oct 2008 12:10:48 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9NCAmXQ007699; 
	Thu, 23 Oct 2008 08:10:48 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9NCAmP7024150;
	Thu, 23 Oct 2008 12:10:48 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 08:06:41 -0400
Received: from [10.86.242.189] ([10.86.242.189]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 08:06:40 -0400
Message-ID: <490068D0.6000605@cisco.com>
Date: Thu, 23 Oct 2008 08:06:40 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 23 Oct 2008 12:06:41.0004 (UTC)
	FILETIME=[CEF5FAC0:01C93507]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5049; t=1224763849;
	x=1225627849; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20draft-ietf-sip-info-events-00=3A=20Cont
	ent-Type=20vs=20Info-Package=20[was=0A=20RE=3A=20[Sip]=20dra
	ft-ietf-sip-info-events-00=3A=20multiple=20packages=20per=20
	INFO] |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=TF6CwY8Wbl5gpJfx1F3pjJZxAJEpm1TaNRmIH5Mor9s=;
	b=MihLHMOIZjbHbpHzcH6ASU7A8/XnrGP38XEGMexZIcFDFfj6Icqg+F8tnb
	yszo96pX+nV7543z6OABLInu+zNeO5+RB2Y1zfDSH+LLRuQTLGTOebNQPcGP
	ejtHflR7rX;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
 Info-Package [was RE: draft-ietf-sip-info-events-00: multiple packages per
 INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Its not a matter of Info-Package *vs* Content-Type - Its Info-Package 
*plus* Content-Type. Previously there was an assumption that C-T would 
uniquely distinguish the "package". Read what Eric wrote about why that 
is a bad assumption.

	Thanks,
	Paul

Christer Holmberg wrote:
> Hi Paul,
> 
> Now I understand what you mean - I mixed up things a little.
> 
> The question is: shall we really use the Info-Package header. And, if
> so, shall we use it in the way as currently described by the draft?
> 
> 
> Shouldn't we use Content-Type to indicate what is in the message body?
> After all, we may need Content-Length etc.
> 
> So, there would be two options:
> 
> 
> 1. Use Content-Type to indicate info-package, and within the package
> itself then indicate the exact package type
> 
> Example: Content-Type: application/info-package
> 
> 
> 2. Use Content-Type to indicate info-package AND exact package type
> 
> Example: Content-Type: application/info-package.foo
> 
> 
> ...or something like that.
> 
> 
> Then, if you have multiple packages, you would use Content-Type:
> multipart/mixed on the SIP level, and Content-Type
> application/info-package within the mimes (normal multipart handling).
> 
> Regards,
> 
> Christer
> 
> 
> 
> 
> 
> 
>  
> 
> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
> Sent: 22. lokakuuta 2008 16:36
> To: Christer Holmberg
> Cc: SIP IETF; Eric Burger
> Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per
> INFO
> 
> 
> 
> Christer Holmberg wrote:
>> Hi,
>>
>> Doesn't the body handling draft say that one MUST be able to parse 
>> multipart message bodies?
>>
>> So, I don't think we should forbid the usage of multiple packages. 
>> There MAY be use-cases where it is useful, so...
>>
>> I also think that the negotiation of multipart support is more 
>> generic, so such mechanism should not be bound to INFO packages.
> 
> My thinking was:
> 
> If multipart is used to convey multiple info packages, then each part
> that contains an info package should contain an Info-Package header
> stating which package it is. That was an alternative to Eric's proposal
> that all the packages be listed at the outer level.
> 
> Then the question remained: in this case should there be an Info-Package
> header at the outer level, and if so, what should it contain?
> 
> Answering that question is what led to my proposing the "multipart"
> package.
> 
> I guess an alternative would be for the Info-Package header at the outer
> level to list all the packages contained, in no particular order, and
> then for the individual parts to contain an Info-Package describing that
> part.
> 
> I do think it is necessary for there to be an Info-Package header at the
> outer level, to distinguish this from a legacy use of Info.
> 
> 	Thanks,
> 	Paul
> 
>> Regards,
>>
>> Christer
>>
>>
>>
>>  
>>
>> -----Original Message-----
>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of 
>> Paul Kyzivat
>> Sent: 21. lokakuuta 2008 17:45
>> To: SIP IETF; Eric Burger
>> Subject: [Sip] draft-ietf-sip-info-events-00: multiple packages per 
>> INFO
>>
>> Re the question about multiple packages per INFO:
>>
>>     There MUST be exactly one Info Package type listed per
> Info-Package
>>     header.  Multiple Info-Packages per INFO message are disallowed.
>>
>>     [EDITOR NOTE: Really?  Why not multiple Info-Packages, in a
>>     multipart/mime?  Well, I thought of one: it is hard to
> disambiguate.
>>     For example, take an INFO message with an Info-Package: key_image,
>>     caller_picture.  I then have a multipart/mime with, you guessed
> it,
>>     an image/jpeg and an image/jpeg.  I would offer we do allow this
> and
>>     require the MIME parse order of the body match the order of the
>> Info-
>>     Package enumerations; if you have too many packages or body parts
> or
>>     they do not align, you barf.  However, I timed out on this and
> thus
>>     we will have to wait for the next version for me to flesh this
> out.
>>     If we do do this, then we'll reference RFC 3261 as updated by
>>     draft-ietf-sip-body-handling to require multipart MIME handling.]
>>
>> How about defining an initial package type of "multipart". It allows 
>> only content-type multipart/mixed. Then each contained type must have 
>> its own Info-Package header. If you want to allow multiple packages 
>> per INFO then you need to negotiate support for "multipart". Or maybe 
>> we require support of multipart if you support any other package type.
>>
>> 	Thanks,
>> 	Paul
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol Use 
>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>> sipping@ietf.org for new developments on the application of sip
>>
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 23 05:12:48 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 69F263A6C10;
	Thu, 23 Oct 2008 05:12:48 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 08AB53A684D
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 05:12:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.539
X-Spam-Level: 
X-Spam-Status: No, score=-6.539 tagged_above=-999 required=5 tests=[AWL=0.060, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XY5cIIPet1+u for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 05:12:38 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id CF5A73A6C10
	for <sip@ietf.org>; Thu, 23 Oct 2008 05:12:37 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,470,1220227200"; d="scan'208";a="25419279"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 23 Oct 2008 12:13:56 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9NCDugu011078; 
	Thu, 23 Oct 2008 08:13:56 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9NCDuw5019623;
	Thu, 23 Oct 2008 12:13:56 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 08:13:13 -0400
Received: from [10.86.242.189] ([10.86.242.189]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 08:13:13 -0400
Message-ID: <49006A58.3090106@cisco.com>
Date: Thu, 23 Oct 2008 08:13:12 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com> A
	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>
	<CA9998CD4A020D418654FCDEF4E707DF088F17D5@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425C2C@DEEXC1U01.de.lucent.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F19BA@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF088F19BA@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 23 Oct 2008 12:13:13.0473 (UTC)
	FILETIME=[B8E3FF10:01C93508]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3749; t=1224764036;
	x=1225628036; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20multiple=20packages=20per=20INFO |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=joygUpsp1LxMTLWnSLtiO8tp9lmAATWZmK96AZ7ngik=;
	b=yXHgfbdFp5TInhT5LnwvRG1sB0W8TCPMPdVXgeB1ia/S+UEmEw3kLOqRrK
	DPfGFk5WVPTCoPMYeuQ62tedpbSB2lSA+zbYQbaxbTYTJ4g+kmghlj1C0lSu
	WzWDve4P/3;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, "Elwell, John" <john.elwell@siemens.com>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>, Eric Burger <eburger@bea.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I also agree it is too extreme to restrict to one package per dialog.
But as I stated earlier, I'm fine not defining multiple packages per INFO.

	Paul

Christer Holmberg wrote:
> Hi, 
> 
>> I don't have a problem agreeing with that.
>>
>> Note that buried somewhere in this thread was a question of whether we
> had a use case for multiple packages per dialog, or can we simplify even
> further.
> 
> I don't think we should go that far, because that could become very
> restrictive.
> 
> For example, assume I want to use INFO packages e.g. for DTMF during the
> call setup, and then other INFO package(s) for something else during the
> call.
> 
> Regards,
> 
> Christer
> 
> 
>> -----Original Message-----
>> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
>> Sent: Thursday, October 23, 2008 10:51 AM
>> To: Elwell, John; Dean Willis; DRAGE, Keith (Keith)
>> Cc: SIP IETF; Eric Burger; Paul Kyzivat
>> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple packages 
>> per INFO
>>
>>
>> Hi,
>>
>> I agree with John. Let's keep it simple. If allowing multiple packages
> 
>> in a single INFO causes issues, let's forget about it.
>>
>> The whole idea with this is to allow people using INFO to do so in an 
>> easy and standardized way, so let's not shoot ourselves in the foot 
>> with complexity.
>>
>> Regards,
>>
>> Christer
>>
>> -----Original Message-----
>> From: Elwell, John [mailto:john.elwell@siemens.com]
>> Sent: 23. lokakuuta 2008 12:30
>> To: Christer Holmberg; Dean Willis; DRAGE, Keith (Keith)
>> Cc: SIP IETF; Eric Burger; Paul Kyzivat
>> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple packages 
>> per INFO
>>
>> In reply to this whole thread, please bear in mind that we had lots of
> 
>> discussion about whether it would be worthwhile defining this new INFO
> 
>> mechanism, since existing applications are unlikely to change and the 
>> best we can hope for is that new applications will exploit the new 
>> mechanism. Therefore we want to keep the mechanism as simple as 
>> possible. The complexities of matching body parts to header fields, 
>> dealing with cases where only some of the packages are understood, 
>> etc.
>> are hardly likely to persuade people to implement the mechanism. 
>> Please keep it simple.
>>
>> John
>>
>>
>>> -----Original Message-----
>>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
>> Behalf Of
>>> Christer Holmberg
>>> Sent: 23 October 2008 08:17
>>> To: Dean Willis; DRAGE, Keith (Keith)
>>> Cc: SIP IETF; Eric Burger; Paul Kyzivat
>>> Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages 
>>> per INFO
>>>
>>>
>>> Hi,
>>>
>>>>> Why does putting two different packages in the same INFO
>>> work better
>>>>> than two different INFO messages each with their own
>>> package usage? Is
>>>
>>>>> there a desirable relationship that can be implemented
>>> between the two
>>>
>>>>> that we would otherwise lose?
>>>> We have one package per NOTIFY. Let's stick with one package
>>> per INFO,
>>> unless we want to go back to using mime-types as the only 
>>> distinguisher of packages.
>>>
>>> I raised that issue in another e-mail.
>>>
>>> But, never the less, I have no strong feelings on the single versus 
>>> multiple package issue.
>>>
>>> Regards,
>>>
>>> Christer
>>>
>>>
>>> _______________________________________________
>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>> This list is for NEW development of the core SIP Protocol Use 
>>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>>> sipping@ietf.org for new developments on the application of sip
>>>
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 23 05:14:14 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 27FA528C0EE;
	Thu, 23 Oct 2008 05:14:14 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 357D43A68F3
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 05:14:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.549
X-Spam-Level: 
X-Spam-Status: No, score=-6.549 tagged_above=-999 required=5 tests=[AWL=0.050, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id HgaxAWgcHXsY for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 05:14:03 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id A7AE23A6C2E
	for <sip@ietf.org>; Thu, 23 Oct 2008 05:14:02 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,470,1220227200"; d="scan'208";a="25419762"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 23 Oct 2008 12:15:20 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9NCFK7r010592; 
	Thu, 23 Oct 2008 08:15:20 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9NCFG6V020597;
	Thu, 23 Oct 2008 12:15:20 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 08:15:20 -0400
Received: from [10.86.242.189] ([10.86.242.189]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 08:15:19 -0400
Message-ID: <49006AD6.6020003@cisco.com>
Date: Thu, 23 Oct 2008 08:15:18 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com> A
	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>
	<CA9998CD4A020D418654FCDEF4E707DF088F17D5@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425C2C@DEEXC1U01.de.lucent.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F19BA@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425C50@DEEXC1U01.de.lucent.com>
In-Reply-To: <5D1A7985295922448D5550C94DE2918002425C50@DEEXC1U01.de.lucent.com>
X-OriginalArrivalTime: 23 Oct 2008 12:15:19.0754 (UTC)
	FILETIME=[0428F2A0:01C93509]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4433; t=1224764120;
	x=1225628120; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20multiple=20packages=20per=20INFO |Sender:=20
	|To:=20=22DRAGE,=20Keith=20\(Keith\)=22=20<drage@alcatel-lu
	cent.com>; bh=RtXwXporccDe8vQJeUVK9SyZlM5tSX2VYt0HKErAGDo=;
	b=ZXShJ9TurbB0k9uTRjcMqQt14cTn9Q8iwxTQch7hx8i5V35L6SibVNnfz5
	bdLqV08PPHNxT162halatiNnVK/M8lE9DxVElx6VFhlPCCRQxegL0O+MHijo
	ILe2OteQ88;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>,
	Dean Willis <dean.willis@softarmor.com>, "Elwell,
	John" <john.elwell@siemens.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



DRAGE, Keith (Keith) wrote:
> It may be restrictive, but will anyone notice the restriction?
> 
> Is there anyone out there who has a current use case for two packages
> per dialog - rather than "I've definitely used one therefore want to
> reserve my options in case I need a second"?

ISUP + DTMF

Of course DTMF can be done other ways, but ...

> Keith
> 
> 
> 
>> -----Original Message-----
>> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] 
>> Sent: Thursday, October 23, 2008 11:41 AM
>> To: DRAGE, Keith (Keith); Elwell, John; Dean Willis
>> Cc: SIP IETF; Eric Burger; Paul Kyzivat
>> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple 
>> packages per INFO
>>
>>
>> Hi, 
>>
>>> I don't have a problem agreeing with that.
>>>
>>> Note that buried somewhere in this thread was a question of 
>> whether we
>> had a use case for multiple packages per dialog, or can we 
>> simplify even further.
>>
>> I don't think we should go that far, because that could 
>> become very restrictive.
>>
>> For example, assume I want to use INFO packages e.g. for DTMF 
>> during the call setup, and then other INFO package(s) for 
>> something else during the call.
>>
>> Regards,
>>
>> Christer
>>
>>
>>> -----Original Message-----
>>> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
>>> Sent: Thursday, October 23, 2008 10:51 AM
>>> To: Elwell, John; Dean Willis; DRAGE, Keith (Keith)
>>> Cc: SIP IETF; Eric Burger; Paul Kyzivat
>>> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple packages 
>>> per INFO
>>>
>>>
>>> Hi,
>>>
>>> I agree with John. Let's keep it simple. If allowing 
>> multiple packages
>>
>>> in a single INFO causes issues, let's forget about it.
>>>
>>> The whole idea with this is to allow people using INFO to 
>> do so in an 
>>> easy and standardized way, so let's not shoot ourselves in the foot 
>>> with complexity.
>>>
>>> Regards,
>>>
>>> Christer
>>>
>>> -----Original Message-----
>>> From: Elwell, John [mailto:john.elwell@siemens.com]
>>> Sent: 23. lokakuuta 2008 12:30
>>> To: Christer Holmberg; Dean Willis; DRAGE, Keith (Keith)
>>> Cc: SIP IETF; Eric Burger; Paul Kyzivat
>>> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple packages 
>>> per INFO
>>>
>>> In reply to this whole thread, please bear in mind that we 
>> had lots of
>>
>>> discussion about whether it would be worthwhile defining 
>> this new INFO
>>
>>> mechanism, since existing applications are unlikely to 
>> change and the 
>>> best we can hope for is that new applications will exploit the new 
>>> mechanism. Therefore we want to keep the mechanism as simple as 
>>> possible. The complexities of matching body parts to header fields, 
>>> dealing with cases where only some of the packages are understood, 
>>> etc.
>>> are hardly likely to persuade people to implement the mechanism. 
>>> Please keep it simple.
>>>
>>> John
>>>
>>>
>>>> -----Original Message-----
>>>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
>>> Behalf Of
>>>> Christer Holmberg
>>>> Sent: 23 October 2008 08:17
>>>> To: Dean Willis; DRAGE, Keith (Keith)
>>>> Cc: SIP IETF; Eric Burger; Paul Kyzivat
>>>> Subject: Re: [Sip] draft-ietf-sip-info-events-00: 
>> multiple packages 
>>>> per INFO
>>>>
>>>>
>>>> Hi,
>>>>
>>>>>> Why does putting two different packages in the same INFO
>>>> work better
>>>>>> than two different INFO messages each with their own
>>>> package usage? Is
>>>>
>>>>>> there a desirable relationship that can be implemented
>>>> between the two
>>>>
>>>>>> that we would otherwise lose?
>>>>> We have one package per NOTIFY. Let's stick with one package
>>>> per INFO,
>>>> unless we want to go back to using mime-types as the only 
>>>> distinguisher of packages.
>>>>
>>>> I raised that issue in another e-mail.
>>>>
>>>> But, never the less, I have no strong feelings on the 
>> single versus 
>>>> multiple package issue.
>>>>
>>>> Regards,
>>>>
>>>> Christer
>>>>
>>>>
>>>> _______________________________________________
>>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>>> This list is for NEW development of the core SIP Protocol Use 
>>>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>>>> sipping@ietf.org for new developments on the application of sip
>>>>
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 23 05:17:10 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4FB7E3A6BC8;
	Thu, 23 Oct 2008 05:17:10 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2B3BA3A6948
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 05:17:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.211
X-Spam-Level: 
X-Spam-Status: No, score=-6.211 tagged_above=-999 required=5 tests=[AWL=0.038, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id PRAtFQthvO5V for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 05:17:00 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 74A453A6C1F
	for <sip@ietf.org>; Thu, 23 Oct 2008 05:16:59 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	59E4C210E3; Thu, 23 Oct 2008 14:18:17 +0200 (CEST)
X-AuditID: c1b4fb3c-ad0ccbb0000015b5-e5-49006b89c8c5
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	2859020F57; Thu, 23 Oct 2008 14:18:17 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 14:18:16 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 23 Oct 2008 14:18:16 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF08924955@esealmw113.eemea.ericsson.se>
In-Reply-To: <490068D0.6000605@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-sip-info-events-00: Content-Type vs Info-Package [was
	RE: [Sip] draft-ietf-sip-info-events-00: multiple packages per
	INFO]
Thread-Index: Ack1CGRDSomI4TtnTgyfiw+pN7BqNwAAMHeA
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<490068D0.6000605@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 23 Oct 2008 12:18:16.0968 (UTC)
	FILETIME=[6DC9A880:01C93509]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>Its not a matter of Info-Package *vs* Content-Type - Its Info-Package
>*plus* Content-Type. Previously there was an assumption that C-T would
uniquely distinguish the "package". Read what Eric wrote about why that
is a bad assumption.

Fine.

But, what will the Content-Type value be, then? We need a value, and the
draft doesn't specify one.

OR, shall each info package define the Content-Type value, in addition
to the package name itself???

Regards,

Christer



Christer Holmberg wrote:
> Hi Paul,
> 
> Now I understand what you mean - I mixed up things a little.
> 
> The question is: shall we really use the Info-Package header. And, if 
> so, shall we use it in the way as currently described by the draft?
> 
> 
> Shouldn't we use Content-Type to indicate what is in the message body?
> After all, we may need Content-Length etc.
> 
> So, there would be two options:
> 
> 
> 1. Use Content-Type to indicate info-package, and within the package 
> itself then indicate the exact package type
> 
> Example: Content-Type: application/info-package
> 
> 
> 2. Use Content-Type to indicate info-package AND exact package type
> 
> Example: Content-Type: application/info-package.foo
> 
> 
> ...or something like that.
> 
> 
> Then, if you have multiple packages, you would use Content-Type:
> multipart/mixed on the SIP level, and Content-Type 
> application/info-package within the mimes (normal multipart handling).
> 
> Regards,
> 
> Christer
> 
> 
> 
> 
> 
> 
>  
> 
> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> Sent: 22. lokakuuta 2008 16:36
> To: Christer Holmberg
> Cc: SIP IETF; Eric Burger
> Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages 
> per INFO
> 
> 
> 
> Christer Holmberg wrote:
>> Hi,
>>
>> Doesn't the body handling draft say that one MUST be able to parse 
>> multipart message bodies?
>>
>> So, I don't think we should forbid the usage of multiple packages. 
>> There MAY be use-cases where it is useful, so...
>>
>> I also think that the negotiation of multipart support is more 
>> generic, so such mechanism should not be bound to INFO packages.
> 
> My thinking was:
> 
> If multipart is used to convey multiple info packages, then each part 
> that contains an info package should contain an Info-Package header 
> stating which package it is. That was an alternative to Eric's 
> proposal that all the packages be listed at the outer level.
> 
> Then the question remained: in this case should there be an 
> Info-Package header at the outer level, and if so, what should it
contain?
> 
> Answering that question is what led to my proposing the "multipart"
> package.
> 
> I guess an alternative would be for the Info-Package header at the 
> outer level to list all the packages contained, in no particular 
> order, and then for the individual parts to contain an Info-Package 
> describing that part.
> 
> I do think it is necessary for there to be an Info-Package header at 
> the outer level, to distinguish this from a legacy use of Info.
> 
> 	Thanks,
> 	Paul
> 
>> Regards,
>>
>> Christer
>>
>>
>>
>>  
>>
>> -----Original Message-----
>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of

>> Paul Kyzivat
>> Sent: 21. lokakuuta 2008 17:45
>> To: SIP IETF; Eric Burger
>> Subject: [Sip] draft-ietf-sip-info-events-00: multiple packages per 
>> INFO
>>
>> Re the question about multiple packages per INFO:
>>
>>     There MUST be exactly one Info Package type listed per
> Info-Package
>>     header.  Multiple Info-Packages per INFO message are disallowed.
>>
>>     [EDITOR NOTE: Really?  Why not multiple Info-Packages, in a
>>     multipart/mime?  Well, I thought of one: it is hard to
> disambiguate.
>>     For example, take an INFO message with an Info-Package:
key_image,
>>     caller_picture.  I then have a multipart/mime with, you guessed
> it,
>>     an image/jpeg and an image/jpeg.  I would offer we do allow this
> and
>>     require the MIME parse order of the body match the order of the
>> Info-
>>     Package enumerations; if you have too many packages or body parts
> or
>>     they do not align, you barf.  However, I timed out on this and
> thus
>>     we will have to wait for the next version for me to flesh this
> out.
>>     If we do do this, then we'll reference RFC 3261 as updated by
>>     draft-ietf-sip-body-handling to require multipart MIME handling.]
>>
>> How about defining an initial package type of "multipart". It allows 
>> only content-type multipart/mixed. Then each contained type must have

>> its own Info-Package header. If you want to allow multiple packages 
>> per INFO then you need to negotiate support for "multipart". Or maybe

>> we require support of multipart if you support any other package
type.
>>
>> 	Thanks,
>> 	Paul
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol Use 
>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>> sipping@ietf.org for new developments on the application of sip
>>
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 23 06:47:44 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 886C43A68E6;
	Thu, 23 Oct 2008 06:47:44 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 21C853A687E
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 06:47:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level: 
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[AWL=0.046, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ImFWdoyTm2Gl for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 06:47:34 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id C32373A6883
	for <sip@ietf.org>; Thu, 23 Oct 2008 06:47:33 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K970041J2DG98@siemenscomms.co.uk> for sip@ietf.org; Thu,
	23 Oct 2008 14:48:52 +0100 (BST)
Date: Thu, 23 Oct 2008 14:48:59 +0100
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <49006A58.3090106@cisco.com>
To: Paul Kyzivat <pkyzivat@cisco.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D00134941B@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
Thread-Index: Ack1CObtr79rbudNSAqG1MkyUhFB7AADONQA
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com> A
	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>
	<CA9998CD4A020D418654FCDEF4E707DF088F17D5@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425C2C@DEEXC1U01.de.lucent.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F19BA@esealmw113.eemea.ericsson.se>
	<49006A58.3090106@cisco.com>
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I agree with Paul and Christer concerning multiple packages per dialog.
It seems a very reasonable thing to do and doesn't cost anything in
complexity.

John 

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
> Sent: 23 October 2008 13:13
> To: Christer Holmberg
> Cc: DRAGE, Keith (Keith); Elwell, John; Dean Willis; SIP 
> IETF; Eric Burger
> Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple 
> packages per INFO
> 
> I also agree it is too extreme to restrict to one package per dialog.
> But as I stated earlier, I'm fine not defining multiple 
> packages per INFO.
> 
> 	Paul
> 
> Christer Holmberg wrote:
> > Hi, 
> > 
> >> I don't have a problem agreeing with that.
> >>
> >> Note that buried somewhere in this thread was a question 
> of whether we
> > had a use case for multiple packages per dialog, or can we 
> simplify even
> > further.
> > 
> > I don't think we should go that far, because that could become very
> > restrictive.
> > 
> > For example, assume I want to use INFO packages e.g. for 
> DTMF during the
> > call setup, and then other INFO package(s) for something 
> else during the
> > call.
> > 
> > Regards,
> > 
> > Christer
> > 
> > 
> >> -----Original Message-----
> >> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> >> Sent: Thursday, October 23, 2008 10:51 AM
> >> To: Elwell, John; Dean Willis; DRAGE, Keith (Keith)
> >> Cc: SIP IETF; Eric Burger; Paul Kyzivat
> >> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple 
> packages 
> >> per INFO
> >>
> >>
> >> Hi,
> >>
> >> I agree with John. Let's keep it simple. If allowing 
> multiple packages
> > 
> >> in a single INFO causes issues, let's forget about it.
> >>
> >> The whole idea with this is to allow people using INFO to 
> do so in an 
> >> easy and standardized way, so let's not shoot ourselves in 
> the foot 
> >> with complexity.
> >>
> >> Regards,
> >>
> >> Christer
> >>
> >> -----Original Message-----
> >> From: Elwell, John [mailto:john.elwell@siemens.com]
> >> Sent: 23. lokakuuta 2008 12:30
> >> To: Christer Holmberg; Dean Willis; DRAGE, Keith (Keith)
> >> Cc: SIP IETF; Eric Burger; Paul Kyzivat
> >> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple 
> packages 
> >> per INFO
> >>
> >> In reply to this whole thread, please bear in mind that we 
> had lots of
> > 
> >> discussion about whether it would be worthwhile defining 
> this new INFO
> > 
> >> mechanism, since existing applications are unlikely to 
> change and the 
> >> best we can hope for is that new applications will exploit the new 
> >> mechanism. Therefore we want to keep the mechanism as simple as 
> >> possible. The complexities of matching body parts to 
> header fields, 
> >> dealing with cases where only some of the packages are understood, 
> >> etc.
> >> are hardly likely to persuade people to implement the mechanism. 
> >> Please keep it simple.
> >>
> >> John
> >>
> >>
> >>> -----Original Message-----
> >>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
> >> Behalf Of
> >>> Christer Holmberg
> >>> Sent: 23 October 2008 08:17
> >>> To: Dean Willis; DRAGE, Keith (Keith)
> >>> Cc: SIP IETF; Eric Burger; Paul Kyzivat
> >>> Subject: Re: [Sip] draft-ietf-sip-info-events-00: 
> multiple packages 
> >>> per INFO
> >>>
> >>>
> >>> Hi,
> >>>
> >>>>> Why does putting two different packages in the same INFO
> >>> work better
> >>>>> than two different INFO messages each with their own
> >>> package usage? Is
> >>>
> >>>>> there a desirable relationship that can be implemented
> >>> between the two
> >>>
> >>>>> that we would otherwise lose?
> >>>> We have one package per NOTIFY. Let's stick with one package
> >>> per INFO,
> >>> unless we want to go back to using mime-types as the only 
> >>> distinguisher of packages.
> >>>
> >>> I raised that issue in another e-mail.
> >>>
> >>> But, never the less, I have no strong feelings on the 
> single versus 
> >>> multiple package issue.
> >>>
> >>> Regards,
> >>>
> >>> Christer
> >>>
> >>>
> >>> _______________________________________________
> >>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> >>> This list is for NEW development of the core SIP Protocol Use 
> >>> sip-implementors@cs.columbia.edu for questions on current sip Use 
> >>> sipping@ietf.org for new developments on the application of sip
> >>>
> > 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 23 07:15:37 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C9CAC3A696E;
	Thu, 23 Oct 2008 07:15:37 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D71BD3A6A2D
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 07:15:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AtFpgfZIarcG for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 07:15:28 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 752583A696E
	for <sip@ietf.org>; Thu, 23 Oct 2008 07:15:28 -0700 (PDT)
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9NEFNAr007752
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 23 Oct 2008 09:15:25 -0500
Message-Id: <093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 23 Oct 2008 09:15:18 -0500
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>,
	Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 23, 2008, at 2:10 AM, Christer Holmberg wrote:

>
> Shouldn't we use Content-Type to indicate what is in the message body?
> After all, we may need Content-Length etc.

Ah, no.

We had extended conversations on this earlier.  Content-Type tells you  
what's in the body; it just doesn't tell you what to DO with the body.

What, for example, is the purpose of an image/jpeg in an INFO?

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


From sip-bounces@ietf.org  Thu Oct 23 07:18:43 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E1FFC3A6BE5;
	Thu, 23 Oct 2008 07:18:43 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CBEE73A698C
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 07:18:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id sIlY1Y2AQIZW for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 07:18:34 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 152603A6BE5
	for <sip@ietf.org>; Thu, 23 Oct 2008 07:18:34 -0700 (PDT)
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9NEJc4C007788
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 23 Oct 2008 09:19:40 -0500
Message-Id: <A11BA33F-6F5B-425A-9D76-17C5894A86C9@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
In-Reply-To: <5D1A7985295922448D5550C94DE2918002425C50@DEEXC1U01.de.lucent.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 23 Oct 2008 09:19:32 -0500
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com> A
	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>
	<CA9998CD4A020D418654FCDEF4E707DF088F17D5@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425C2C@DEEXC1U01.de.lucent.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F19BA@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425C50@DEEXC1U01.de.lucent.com>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>,
	Paul Kyzivat <pkyzivat@cisco.com>, "Elwell,
	John" <john.elwell@siemens.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 23, 2008, at 6:07 AM, DRAGE, Keith (Keith) wrote:

> It may be restrictive, but will anyone notice the restriction?
>
> Is there anyone out there who has a current use case for two packages
> per dialog - rather than "I've definitely used one therefore want to
> reserve my options in case I need a second"?

Two packages in the same dialog makes sense.  For example, one might  
want to use location-push and image-push during a call..

Different sets of packages allowed at different times during the  
lifespan of the dialog doesn't make nearly as much sense. The simplest  
model is to agree one set of packages "up front", and use only that  
set during the dialog.

--
Dean

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


From sip-bounces@ietf.org  Thu Oct 23 07:19:28 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 929053A6C1A;
	Thu, 23 Oct 2008 07:19:28 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 804BB3A698C
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 07:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.556
X-Spam-Level: 
X-Spam-Status: No, score=-6.556 tagged_above=-999 required=5 tests=[AWL=0.043, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4elbLb5r-aHl for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 07:19:17 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 3C74F3A6C24
	for <sip@ietf.org>; Thu, 23 Oct 2008 07:19:17 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,470,1220227200"; d="scan'208";a="25439701"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 23 Oct 2008 14:20:28 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9NEKRoK030320; 
	Thu, 23 Oct 2008 10:20:27 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9NEKQtf013407;
	Thu, 23 Oct 2008 14:20:27 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 10:20:26 -0400
Received: from [10.86.242.189] ([10.86.242.189]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 10:20:26 -0400
Message-ID: <49008829.4050507@cisco.com>
Date: Thu, 23 Oct 2008 10:20:25 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<490068D0.6000605@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF08924955@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF08924955@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 23 Oct 2008 14:20:26.0395 (UTC)
	FILETIME=[7E7776B0:01C9351A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=921; t=1224771627; x=1225635627;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20draft-ietf-sip-info-events-00=3A=20Cont
	ent-Type=20vs=20Info-Package=20[was=0A=20RE=3A=20[Sip]=20dra
	ft-ietf-sip-info-events-00=3A=20multiple=20packages=20per=20
	INFO] |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=YI0Mma+6L8e/ZywZ4JguuzvRVBvzShxXuOt9jOKAg+Y=;
	b=XR4xIa5mRZ7kS9mLC0E81iOMn55JmgItlyNUNtB5gcQj5ZFCW8/UprSsfm
	CJ+eXhXiJrgD2lCpIAmhkwgeCPs18usoYNA13VVu7NLAMB+iaQgRyT1mJSTS
	gwFKwm8X3D;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
 Info-Package [was RE: draft-ietf-sip-info-events-00: multiple packages per
 INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Christer Holmberg wrote:
> Hi, 
> 
>> Its not a matter of Info-Package *vs* Content-Type - Its Info-Package
>> *plus* Content-Type. Previously there was an assumption that C-T would
> uniquely distinguish the "package". Read what Eric wrote about why that
> is a bad assumption.
> 
> Fine.
> 
> But, what will the Content-Type value be, then? We need a value, and the
> draft doesn't specify one.
> 
> OR, shall each info package define the Content-Type value, in addition
> to the package name itself???

    7.2.4.  INFO Bodies

    Each Info Package MUST define what type or types of bodies are
    expected in INFO requests.  Such packages MUST specify or cite
    detailed specifications for the syntax and semantics associated with
    such a body.

    Info Packages also MUST define a default MIME type if the "Accept"
    header fails to define any MIME types in the INVITE request.
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 23 07:32:51 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 639563A6A27;
	Thu, 23 Oct 2008 07:32:51 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6A7DF3A6971
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 07:32:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.562
X-Spam-Level: 
X-Spam-Status: No, score=-6.562 tagged_above=-999 required=5 tests=[AWL=0.038, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id kkkfmUOpgOfb for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 07:32:41 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 4208C3A68D7
	for <sip@ietf.org>; Thu, 23 Oct 2008 07:32:41 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,470,1220227200"; d="scan'208";a="25441920"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 23 Oct 2008 14:34:00 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9NEY0Y6012627; 
	Thu, 23 Oct 2008 10:34:00 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9NEY081019117;
	Thu, 23 Oct 2008 14:34:00 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 10:34:00 -0400
Received: from [10.86.242.189] ([10.86.242.189]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 10:33:59 -0400
Message-ID: <49008B56.2010900@cisco.com>
Date: Thu, 23 Oct 2008 10:33:58 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com> A
	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>
	<CA9998CD4A020D418654FCDEF4E707DF088F17D5@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425C2C@DEEXC1U01.de.lucent.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F19BA@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425C50@DEEXC1U01.de.lucent.com>
	<A11BA33F-6F5B-425A-9D76-17C5894A86C9@softarmor.com>
In-Reply-To: <A11BA33F-6F5B-425A-9D76-17C5894A86C9@softarmor.com>
X-OriginalArrivalTime: 23 Oct 2008 14:33:59.0676 (UTC)
	FILETIME=[63384BC0:01C9351C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=874; t=1224772440; x=1225636440;
	c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20multiple=20packages=20per=20INFO |Sender:=20
	|To:=20Dean=20Willis=20<dean.willis@softarmor.com>;
	bh=DXE9k9ppN0A5gr31Boyc/4KXZY1j6P3F3CCQQuL27KU=;
	b=C/CogOL1O83Twvd1lQJ1Lp53jvx3GomjsHYzjbExo+bMC58NeK6JlyWKbx
	25smd8m4NgGJBRDrjZmXq8J5VtXHBFnx67WDMscLEqRBdyVb88CnPfCSPLKJ
	GA9x3ewZ4+;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, "Elwell, John" <john.elwell@siemens.com>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>, Eric Burger <eburger@bea.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Dean Willis wrote:
> 
> On Oct 23, 2008, at 6:07 AM, DRAGE, Keith (Keith) wrote:
> 
>> It may be restrictive, but will anyone notice the restriction?
>>
>> Is there anyone out there who has a current use case for two packages
>> per dialog - rather than "I've definitely used one therefore want to
>> reserve my options in case I need a second"?
> 
> Two packages in the same dialog makes sense.  For example, one might 
> want to use location-push and image-push during a call..
> 
> Different sets of packages allowed at different times during the 
> lifespan of the dialog doesn't make nearly as much sense. The simplest 
> model is to agree one set of packages "up front", and use only that set 
> during the dialog.

No. I always have to remind people:

a 3pcc transfer can result in needing to renegotiate things in the 
dialog that remains.


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


From sip-bounces@ietf.org  Thu Oct 23 08:15:44 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 49F4D3A684D;
	Thu, 23 Oct 2008 08:15:44 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 53D943A684D
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 08:15:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.374
X-Spam-Level: 
X-Spam-Status: No, score=-2.374 tagged_above=-999 required=5
	tests=[AWL=-0.374, BAYES_00=-2.599, J_CHICKENPOX_93=0.6,
	SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id F+fw9foXtkMP for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 08:15:30 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net
	[IPv6:2001:470:1f03:267::2])
	by core3.amsl.com (Postfix) with ESMTP id 009523A67A5
	for <sip@ietf.org>; Thu, 23 Oct 2008 08:15:29 -0700 (PDT)
Received: from dn3-232.estacado.net (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.14.3/8.14.1) with ESMTP id m9NFGjDM021332
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO)
	for <sip@ietf.org>; Thu, 23 Oct 2008 10:16:45 -0500 (CDT)
	(envelope-from rjsparks@nostrum.com)
Message-Id: <13208C5A-4105-4F77-842B-DD434EBE403A@nostrum.com>
From: Robert Sparks <rjsparks@nostrum.com>
To: "SIP@ietf.org List" <sip@ietf.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 23 Oct 2008 10:16:45 -0500
X-Mailer: Apple Mail (2.929.2)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Virus-Scanned: ClamAV 0.94/8476/Thu Oct 23 09:46:06 2008 on
	shaman.nostrum.com
X-Virus-Status: Clean
Subject: [Sip] SIPit23 Survey Notes
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Also available at https://www.sipit.net/SIPit23_Summary :

SIPit 23 was hosted by ETSI with technical support from Orange
the week of October 13-17, 2008 in Lannion, France

There were 97 attendees from 37 companies visiting from 19 countries.

I manually surveyed the teams at this event to avoid some of the  
sampling error
we've seen with the use of an automated survey tool at the last few  
SIPits.
Please take care to remember this change in the measurement tool when  
trying to
read trends comparing this report to previous events. In particular, I  
was
careful to avoid counting two products that were essentially the same
implementation as different. With that in mind:

We had over 50 distinct implementations.

There were a higher than usual proportion of implementations attending  
SIPit
for the first time at this SIPit. As a result, there was more testing  
of basic
interoperability than we've seen for the last several events. There  
were still
several advanced teams demonstrating interoperability of more  
complicated
scenarios.

62% of the UAs present both sent RTCP and paid attention to RTCP they  
recieved
     this is the first sipit where this has been true for the majority  
of the UAs.

This event saw a (mostly) successful test of ICE between three  
implementations
at the multiparty tests.

There were no implementations of the sip-config, sip-consent, or  
session-policy
frameworks. The only people in the room who had even read the sip-config
framework documents are regular IETF participants. Even fewer had read
sip-consent or session-policy. There is currently a huge gap between
specification and implementation for these concepts. (Note - there  
have been
sip-config implemantations at previous events, but the teams that  
brought them
were not able to attend this time).

The roles represented (some implementations act in more than one role):
  29 endpoints
  13 proxy/registrars
   8 event servers
   7 gateways
   2 automaton UAs (voicemail, conference, appserver, etc)
  14 b2bua/sbcs
   3 UAs with signaling, but without media
   5 test/monitoring tool

The set of things considered UAs below (the union of the
endpoints/b2buas/gateways/etc) consisted of 42 implementations.

Implementations using each transport for SIP messages:
   UDP    100%
   TCP     93%
   TLS     48% server-auth, 28% mutual-auth
   SCTP    11%
   DTLS   none

30% of the implementations supported SIP over IPv6 (This was  
significantly down
from the last few events - I think it is mostly due to the number of  
very young
implementations present.)

19% supported SIP over IPSec

For DNS we had support for:
    Full RFC3263		: 65% (continuing to climb)
    SRV only		: 15%
    A records only	: 13%
    no DNS support	:  7%

Support for various items:
   72% rport
   15% sigcomp
   36% enum
   13% RFC4320 fixes
   13% invfix
   63% session-timer
   9% outbound (various versions)
   9% gruu-15

There were only 2 implementations claiming support for Identity. 2 for  
the
dial-string URI (RFC4967), and none for Service URNs (RFC5031). These  
are all
lower than what was reported at previous events - a result of the  
opportunity
to double-check answers during the manual survey.

Many teams expressed intent to implement outbound and gruu once  
something was
published as an RFC, and a strong unwillingness to even try until that  
happens.


36% of the implementations indicated support for anonymous calling.

24% reported using the Diversion header field.

76% of the implementations made some use of SIP Events.
There was a huge upswing in support for the message-summary event.

The UAs implemented these methods:
   95% INVITE, CANCEL, ACK, BYE (some endponts did messaging/presence  
only)
   93% REGISTER
   95% NOTIFY <- still a lot of unsolicted NOTIFYs
   95% SUBSCRIBE
   86% OPTIONS
   83% PRACK
   77% INFO
   72% REFER
   72% UPDATE
   64% MESSAGE
   43% PUBLISH (Note that several of these are b2buas
                that are not really processing the PUBLISH
                - the next survey will split those out)

Support for various extensions in the endpoints:
   98%   RFC3262 100rel
   50%   RFC3323 privacy
   36%   RFC3327 path
    7%   RFC3840/RFC3841 pref/caller-prefs
   79%   RFC3891 replaces
    9%   RFC4488 norefersub
    7%   RFC4538 target-dialog

There were 6 ICE implementations (and 1 ICE-TCP implementation)
There were 6 TURN clients and one TURN server present
There were 19 STUN clients (6 were stun-bis)

88% of the UAs supported symmetric RTP
16% supported SRTP - only one had code based on the dtls-srtp work

Support for multipart/mime increased (38% of the UAs would do  
something with it
on receipt). There were no implementations present testing S/MIME.

Of the SIP-Events implementations, the following packages were  
supported:
   82%	message-summary
   72%	refer
   59%	presence
    8%	reg
   16%	dialog
   12%	conf

There were two RLS servers and 6 clients supporting
the event-lists extension present. There were two xcap servers present.

There were 8 SIP-Events implementations present supporting winfo.

7 of the proxies present implemented some form of loop detection (only  
3 have
implemented the loop-detection part of fork-loop fix)

There were 5 MSRP clients and one MSRP relay present.  All of the  
clients
supported file transfer (3 used file-transfer-mech).  Several clients  
were able
to exchange files.  Two of the clients were able to exchange instant  
messages.
(Only one had been created with the intent to send instant messages -  
the rest
were file transfer centric.) The embedded-device implementers noted  
that the
decision to not allow a negotiated maximum chunk size (not maximum  
message
size) is causing them significant difficulty.

The multiparty STUN/TURN/ICE test saw successful calls using ICE after
correcting some implementation issues around authenticating a binding  
and
becoming less strict on parsing SDP (specifically the rtcp attribute).
There was some argument over what inputs to use for candidate pairs when
one stream (of many) in an offer was rejected in the answer.

I asked where people were taking bits from messages to display as  
caller-id.
There were many different kinds of answers, including
  P-Asserted-Identity if present, then From
  From display name
  username part of From uri
  P-Asserted-Identity only
  Contact uri
  Remote IP address
  P-Asserted-Identity, then Remote-Party-ID, then From
  From, then Remote-Party-ID, then P-Asserted-Identity
  Remote-Party-ID then From
  From then P-Assertid-Identity
  P-Asserted-Identity, then Reply-To, then From
  entire From URI
Of these, using the From display name occurred most frequently,
but not much more than any of the other responses

After removing some minor rough edges, the presence multiparty test
exercised xcap successfully, modifying resource lists and presence  
rules.
There are still many questions around how to discover the xcap root uri.

The TLS multiparty test had several new participants and did not go as  
smoothly
as it has in past events. Most of the issues were with configuration  
of individual
implementations, but there was quite a bit of confusion around the use  
of sips:
and transport=tls. We will hold a longer and more rigourous multiparty  
session
focusing on TLS at the next SIPit.

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


From sip-bounces@ietf.org  Thu Oct 23 10:56:50 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F160E3A69DA;
	Thu, 23 Oct 2008 10:56:49 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5DDE73A69DA
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 10:56:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.211
X-Spam-Level: 
X-Spam-Status: No, score=-6.211 tagged_above=-999 required=5 tests=[AWL=0.038, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id sdjCyFnCMENV for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 10:56:48 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 6C2BD3A684D
	for <sip@ietf.org>; Thu, 23 Oct 2008 10:56:48 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	2DB9920235; Thu, 23 Oct 2008 19:58:07 +0200 (CEST)
X-AuditID: c1b4fb3e-aa77dbb00000537b-3f-4900bb2fc029
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	15A63201B5; Thu, 23 Oct 2008 19:58:07 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 19:58:03 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 23 Oct 2008 19:58:00 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCF9C@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-sip-info-events-00: Content-Type vs Info-Package [was
	RE: [Sip] draft-ietf-sip-info-events-00: multiple packages per
	INFO]
Thread-Index: Ack1GoaWO0nDLNLPSbW6+4lCRcvotgAHZhVj
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<490068D0.6000605@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF08924955@esealmw113.eemea.ericsson.se>
	<49008829.4050507@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 23 Oct 2008 17:58:03.0211 (UTC)
	FILETIME=[E4EF79B0:01C93538]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Wouldn't it be much simplier to define a generic mime, e.g. application/info-package, and then each info package only needs to define the Info-Package header value for that particular package?
 
Regards,
 
Christer

________________________________

From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
Sent: Thu 23/10/2008 16:20
To: Christer Holmberg
Cc: SIP IETF; eric burger
Subject: Re: draft-ietf-sip-info-events-00: Content-Type vs Info-Package [was RE: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO]





Christer Holmberg wrote:
> Hi,
>
>> Its not a matter of Info-Package *vs* Content-Type - Its Info-Package
>> *plus* Content-Type. Previously there was an assumption that C-T would
> uniquely distinguish the "package". Read what Eric wrote about why that
> is a bad assumption.
>
> Fine.
>
> But, what will the Content-Type value be, then? We need a value, and the
> draft doesn't specify one.
>
> OR, shall each info package define the Content-Type value, in addition
> to the package name itself???

    7.2.4.  INFO Bodies

    Each Info Package MUST define what type or types of bodies are
    expected in INFO requests.  Such packages MUST specify or cite
    detailed specifications for the syntax and semantics associated with
    such a body.

    Info Packages also MUST define a default MIME type if the "Accept"
    header fails to define any MIME types in the INVITE request.


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


From sip-bounces@ietf.org  Thu Oct 23 10:57:56 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B0EED3A688D;
	Thu, 23 Oct 2008 10:57:56 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3151B3A688D
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 10:57:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.212
X-Spam-Level: 
X-Spam-Status: No, score=-6.212 tagged_above=-999 required=5 tests=[AWL=0.037, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ILkw1jiXxpuN for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 10:57:54 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 5E5BB3A6838
	for <sip@ietf.org>; Thu, 23 Oct 2008 10:57:54 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	01F30201B5; Thu, 23 Oct 2008 19:59:13 +0200 (CEST)
X-AuditID: c1b4fb3e-adf84bb00000537b-68-4900bb70b72f
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	D82C12015F; Thu, 23 Oct 2008 19:59:12 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 19:59:12 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 23 Oct 2008 19:59:12 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
Thread-Index: Ack1GfeA/H9NGvZJR9KYGkllbJc4FQAHYCcw
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 23 Oct 2008 17:59:12.0335 (UTC)
	FILETIME=[0E22F5F0:01C93539]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>,
	Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi,
 
>>Shouldn't we use Content-Type to indicate what is in the message body?
>>After all, we may need Content-Length etc.
>
>Ah, no.
>
>We had extended conversations on this earlier.  Content-Type tells you 
>what's in the body; it just doesn't tell you what to DO with the body.
>
>What, for example, is the purpose of an image/jpeg in an INFO?

That is not what I meant. 
 
We can use the Info-Package header, but can't we use a generic mime value - which tells us that there is an info package in the body.
 
Regards,
 
Christer

 

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


From sip-bounces@ietf.org  Thu Oct 23 10:58:07 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7B5833A6A99;
	Thu, 23 Oct 2008 10:58:07 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2302A28C0F3
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 10:58:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ZDeGLSX1bcgg for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 10:58:04 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id AE47B3A684D
	for <sip@ietf.org>; Thu, 23 Oct 2008 10:58:04 -0700 (PDT)
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9NHw0v0009119
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 23 Oct 2008 12:58:02 -0500
Message-Id: <1777ACAB-FC6A-4DC0-BF67-21058B3F5F58@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
In-Reply-To: <49008B56.2010900@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 23 Oct 2008 12:57:55 -0500
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com> A
	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>
	<CA9998CD4A020D418654FCDEF4E707DF088F17D5@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425C2C@DEEXC1U01.de.lucent.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F19BA@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425C50@DEEXC1U01.de.lucent.com>
	<A11BA33F-6F5B-425A-9D76-17C5894A86C9@softarmor.com>
	<49008B56.2010900@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>, "Elwell, John" <john.elwell@siemens.com>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>, Eric Burger <eburger@bea.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 23, 2008, at 9:33 AM, Paul Kyzivat wrote:

>
>
> Dean Willis wrote:
>> On Oct 23, 2008, at 6:07 AM, DRAGE, Keith (Keith) wrote:
>>> It may be restrictive, but will anyone notice the restriction?
>>>
>>> Is there anyone out there who has a current use case for two  
>>> packages
>>> per dialog - rather than "I've definitely used one therefore want to
>>> reserve my options in case I need a second"?
>> Two packages in the same dialog makes sense.  For example, one  
>> might want to use location-push and image-push during a call..
>> Different sets of packages allowed at different times during the  
>> lifespan of the dialog doesn't make nearly as much sense. The  
>> simplest model is to agree one set of packages "up front", and use  
>> only that set during the dialog.
>
> No. I always have to remind people:
>
> a 3pcc transfer can result in needing to renegotiate things in the  
> dialog that remains.
>
>


That's a dialog renegotiation, for all practical purposes a new dialog.

You're also negotiating new codecs, etc.

Doing INFO package renegotiation is just a part of it.

OTOH, I think we messed up with 3PCC, too. It's just another  
bottomless pit of complexity that we should have avoided.

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


From sip-bounces@ietf.org  Thu Oct 23 11:02:50 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DD1353A6824;
	Thu, 23 Oct 2008 11:02:50 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1DDCF3A68CC
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 11:02:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.212
X-Spam-Level: 
X-Spam-Status: No, score=-6.212 tagged_above=-999 required=5 tests=[AWL=0.037, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id C-uJGDjeTZ16 for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 11:02:48 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 0A9973A67E4
	for <sip@ietf.org>; Thu, 23 Oct 2008 11:02:47 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	A7FF8206A6; Thu, 23 Oct 2008 20:04:05 +0200 (CEST)
X-AuditID: c1b4fb3e-aef86bb00000537b-6f-4900bc950713
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	90E56203D4; Thu, 23 Oct 2008 20:04:05 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 20:04:05 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 23 Oct 2008 20:00:05 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCF9D@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
Thread-Index: Ack1HGcv1fRbfLreQ6aUoC921fVoxQAHMZ6u
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com> A
	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>
	<CA9998CD4A020D418654FCDEF4E707DF088F17D5@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425C2C@DEEXC1U01.de.lucent.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F19BA@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425C50@DEEXC1U01.de.lucent.com>
	<A11BA33F-6F5B-425A-9D76-17C5894A86C9@softarmor.com>
	<49008B56.2010900@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>,
	"Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 23 Oct 2008 18:04:05.0030 (UTC)
	FILETIME=[BC98AC60:01C93539]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, "Elwell, John" <john.elwell@siemens.com>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>, Eric Burger <eburger@bea.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi,
 
Not only 3pcc, I think it could be useful to re-negotiate the packages during the session. For example, I may want DTMFs only during a certain period of the call, so for the rest of the call you would not be able to generate INFOs by pressing digit buttons.
 
Also, we may enable some application during the call, so the UAs need to re-negotiate the packages. For example, I may tell you that I have a vcard which I want to send you, but we may not have negotiated that "by defualt" when the call was established.
 
Regards,
 
Christer
 

________________________________

From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
Sent: Thu 23/10/2008 16:33
To: Dean Willis
Cc: DRAGE, Keith (Keith); Christer Holmberg; Elwell, John; SIP IETF; Eric Burger
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO





Dean Willis wrote:
>
> On Oct 23, 2008, at 6:07 AM, DRAGE, Keith (Keith) wrote:
>
>> It may be restrictive, but will anyone notice the restriction?
>>
>> Is there anyone out there who has a current use case for two packages
>> per dialog - rather than "I've definitely used one therefore want to
>> reserve my options in case I need a second"?
>
> Two packages in the same dialog makes sense.  For example, one might
> want to use location-push and image-push during a call..
>
> Different sets of packages allowed at different times during the
> lifespan of the dialog doesn't make nearly as much sense. The simplest
> model is to agree one set of packages "up front", and use only that set
> during the dialog.

No. I always have to remind people:

a 3pcc transfer can result in needing to renegotiate things in the
dialog that remains.




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


From sip-bounces@ietf.org  Thu Oct 23 11:19:59 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7FB173A6AC5;
	Thu, 23 Oct 2008 11:19:59 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C89E53A6823
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 11:19:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.566
X-Spam-Level: 
X-Spam-Status: No, score=-6.566 tagged_above=-999 required=5 tests=[AWL=0.033, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4RzuHtPwxtkt for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 11:19:56 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id AC17A3A6AC3
	for <sip@ietf.org>; Thu, 23 Oct 2008 11:19:56 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,471,1220227200"; d="scan'208";a="25473404"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 23 Oct 2008 18:21:15 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9NILGTS020003; 
	Thu, 23 Oct 2008 14:21:16 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9NILF4g016023;
	Thu, 23 Oct 2008 18:21:16 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 14:21:15 -0400
Received: from [10.86.242.189] ([10.86.242.189]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 14:21:15 -0400
Message-ID: <4900C09A.9060104@cisco.com>
Date: Thu, 23 Oct 2008 14:21:14 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 23 Oct 2008 18:21:15.0434 (UTC)
	FILETIME=[22C3D8A0:01C9353C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1434; t=1224786076;
	x=1225650076; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20Content-Type=20vs=20Info-Package=0A=20[was=20RE=3A=20dra
	ft-ietf-sip-info-events-00=3A=20multiple=20packages=20per=20
	INFO] |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=pSWSAXeI099Ysl6/AD/a9NYLjE6KpqTLtSSfdvZ8ca8=;
	b=BWK04+2jLTYgdu9dr4hfJw8XAgMzY66dyk+fwHfPygKufLq0zXw6ITWFq8
	gwtJVvSsabDioRMiqawxaOcYBxf+TQxEzEpZOXYiy79wG2CkkXlnwFBNiujJ
	mOIvHAfMl+;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
 Info-Package [was RE: draft-ietf-sip-info-events-00: multiple packages per
 INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer,

I don't understand where you are heading with this?

If I want to send an INFO with a jpeg, then what is this other mime type 
doing other than getting in my way.

OTOH, we haven't discussed Content-Disposition wrt INFO. In the absence 
of any mention, I assume that "render" will be used for info packages, 
and the detailed processing defined by the Info-Package value.

In some sense, the Info-Package value is serving the same purpose as 
Content-Disposition. We could *consider* using the C-D *instead* of the 
Info-Package header, so that what we would be negotiating would be the 
acceptable C-D values. The downside of that is that we would then need 
to open up the registration of new C-D values. I think that might be 
opposed by a lot of people.

	Thanks,
	Paul

Christer Holmberg wrote:
> Hi,
>  
>>> Shouldn't we use Content-Type to indicate what is in the message body?
>>> After all, we may need Content-Length etc.
>> Ah, no.
>>
>> We had extended conversations on this earlier.  Content-Type tells you 
>> what's in the body; it just doesn't tell you what to DO with the body.
>>
>> What, for example, is the purpose of an image/jpeg in an INFO?
> 
> That is not what I meant. 
>  
> We can use the Info-Package header, but can't we use a generic mime value - which tells us that there is an info package in the body.
>  
> Regards,
>  
> Christer
> 
>  
> 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 23 11:23:30 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3F2873A6ACB;
	Thu, 23 Oct 2008 11:23:30 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 039BE3A69CA
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 11:23:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.569
X-Spam-Level: 
X-Spam-Status: No, score=-6.569 tagged_above=-999 required=5 tests=[AWL=0.030, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LinMf1VGCtmb for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 11:23:28 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 061A13A6975
	for <sip@ietf.org>; Thu, 23 Oct 2008 11:23:27 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,471,1220227200"; d="scan'208";a="25473936"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 23 Oct 2008 18:24:46 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9NIOlTm022299; 
	Thu, 23 Oct 2008 14:24:47 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9NIOlTQ017309;
	Thu, 23 Oct 2008 18:24:47 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 14:24:47 -0400
Received: from [10.86.242.189] ([10.86.242.189]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 14:24:46 -0400
Message-ID: <4900C16E.9030701@cisco.com>
Date: Thu, 23 Oct 2008 14:24:46 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com> A
	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>
	<CA9998CD4A020D418654FCDEF4E707DF088F17D5@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425C2C@DEEXC1U01.de.lucent.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F19BA@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425C50@DEEXC1U01.de.lucent.com>
	<A11BA33F-6F5B-425A-9D76-17C5894A86C9@softarmor.com>
	<49008B56.2010900@cisco.com>
	<1777ACAB-FC6A-4DC0-BF67-21058B3F5F58@softarmor.com>
In-Reply-To: <1777ACAB-FC6A-4DC0-BF67-21058B3F5F58@softarmor.com>
X-OriginalArrivalTime: 23 Oct 2008 18:24:46.0868 (UTC)
	FILETIME=[A0CA1D40:01C9353C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1652; t=1224786287;
	x=1225650287; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20multiple=20packages=20per=20INFO |Sender:=20
	|To:=20Dean=20Willis=20<dean.willis@softarmor.com>;
	bh=a1IWFinupdoCpz2W4k31OBBcxe6+C/dewS3Zoroi1xQ=;
	b=F17ogwi34LTGUY8ep6zHMUmD7JBC9HQWRyuyBrSXJXEp3nIKguPo5xRMbf
	ymCak2PvUicUA4Ls3AASio/1mtvks63vZNue1ktH03vOhtXtOaXlvrs3STi7
	sYfoyaJADH;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, "Elwell, John" <john.elwell@siemens.com>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>, Eric Burger <eburger@bea.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Dean Willis wrote:
> 
> On Oct 23, 2008, at 9:33 AM, Paul Kyzivat wrote:
> 
>>
>>
>> Dean Willis wrote:
>>> On Oct 23, 2008, at 6:07 AM, DRAGE, Keith (Keith) wrote:
>>>> It may be restrictive, but will anyone notice the restriction?
>>>>
>>>> Is there anyone out there who has a current use case for two packages
>>>> per dialog - rather than "I've definitely used one therefore want to
>>>> reserve my options in case I need a second"?
>>> Two packages in the same dialog makes sense.  For example, one might 
>>> want to use location-push and image-push during a call..
>>> Different sets of packages allowed at different times during the 
>>> lifespan of the dialog doesn't make nearly as much sense. The 
>>> simplest model is to agree one set of packages "up front", and use 
>>> only that set during the dialog.
>>
>> No. I always have to remind people:
>>
>> a 3pcc transfer can result in needing to renegotiate things in the 
>> dialog that remains.
>>
>>
> 
> 
> That's a dialog renegotiation, for all practical purposes a new dialog.
> 
> You're also negotiating new codecs, etc.
> 
> Doing INFO package renegotiation is just a part of it.

That does not create a new dialog, it just updates the existing dialog. 
Its done using reINVITE or UPDATE. And that is exactly the currently 
proposed means of changing the set of packages in mid dialog.

> OTOH, I think we messed up with 3PCC, too. It's just another bottomless 
> pit of complexity that we should have avoided.

If we had invented Invite/Replaces early enough it could have replaced 
reINVITE. But that is water over the dam.

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


From sip-bounces@ietf.org  Thu Oct 23 12:24:21 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 94F3D3A6AB1;
	Thu, 23 Oct 2008 12:24:21 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 853153A6820
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 12:24:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.212
X-Spam-Level: 
X-Spam-Status: No, score=-6.212 tagged_above=-999 required=5 tests=[AWL=0.037, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6vGokKBvknPo for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 12:24:19 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 6B2E43A6891
	for <sip@ietf.org>; Thu, 23 Oct 2008 12:24:19 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	EC8C420B99; Thu, 23 Oct 2008 21:25:37 +0200 (CEST)
X-AuditID: c1b4fb3e-ae785bb00000537b-90-4900cfb18b86
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	CD8062040A; Thu, 23 Oct 2008 21:25:37 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 21:25:37 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 23 Oct 2008 21:23:59 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCF9F@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
Thread-Index: Ack1PCW9GBWOZljDSF2zxAYYGvpiBwACMB+Z
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
	<4900C09A.9060104@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 23 Oct 2008 19:25:37.0217 (UTC)
	FILETIME=[20912B10:01C93545]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi,
 
Let's assume I want to send an INFO with package foo.
 
The value of the Info-Package header is "foo", right?
 
Now, what is the value of the Content-Type header?
 
Is it something which is generic for all info packages (e.g. application/info), OR is it something which is specified in the foo package description?
 
Regards,
 
Christer

________________________________

From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
Sent: Thu 23/10/2008 20:21
To: Christer Holmberg
Cc: Dean Willis; SIP IETF; Eric Burger
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs Info-Package [was RE: draft-ietf-sip-info-events-00: multiple packages per INFO]



Christer,

I don't understand where you are heading with this?

If I want to send an INFO with a jpeg, then what is this other mime type
doing other than getting in my way.

OTOH, we haven't discussed Content-Disposition wrt INFO. In the absence
of any mention, I assume that "render" will be used for info packages,
and the detailed processing defined by the Info-Package value.

In some sense, the Info-Package value is serving the same purpose as
Content-Disposition. We could *consider* using the C-D *instead* of the
Info-Package header, so that what we would be negotiating would be the
acceptable C-D values. The downside of that is that we would then need
to open up the registration of new C-D values. I think that might be
opposed by a lot of people.

        Thanks,
        Paul

Christer Holmberg wrote:
> Hi,
> 
>>> Shouldn't we use Content-Type to indicate what is in the message body?
>>> After all, we may need Content-Length etc.
>> Ah, no.
>>
>> We had extended conversations on this earlier.  Content-Type tells you
>> what's in the body; it just doesn't tell you what to DO with the body.
>>
>> What, for example, is the purpose of an image/jpeg in an INFO?
>
> That is not what I meant.
> 
> We can use the Info-Package header, but can't we use a generic mime value - which tells us that there is an info package in the body.
> 
> Regards,
> 
> Christer
>
> 
>
>


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


From sip-bounces@ietf.org  Thu Oct 23 13:06:14 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 382523A691B;
	Thu, 23 Oct 2008 13:06:14 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3C9A03A691B
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 13:06:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.572
X-Spam-Level: 
X-Spam-Status: No, score=-6.572 tagged_above=-999 required=5 tests=[AWL=0.027, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id y0KrfYT8BFXX for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 13:06:12 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 176513A67D6
	for <sip@ietf.org>; Thu, 23 Oct 2008 13:06:12 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,472,1220227200"; d="scan'208";a="25457671"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 23 Oct 2008 20:07:31 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9NK7VJF017569; 
	Thu, 23 Oct 2008 16:07:31 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9NK7V6I012886;
	Thu, 23 Oct 2008 20:07:31 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 16:07:31 -0400
Received: from [10.86.242.189] ([10.86.242.189]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Oct 2008 16:07:31 -0400
Message-ID: <4900D982.4050007@cisco.com>
Date: Thu, 23 Oct 2008 16:07:30 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
	<4900C09A.9060104@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9F@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF083CCF9F@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 23 Oct 2008 20:07:31.0055 (UTC)
	FILETIME=[FAEE67F0:01C9354A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2492; t=1224792451;
	x=1225656451; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20Content-Type=20vs=20Info-Package=0A=20[was=20RE=3A=20dra
	ft-ietf-sip-info-events-00=3A=20multiple=20packages=20per=20
	INFO] |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=qmSqB4P2xAGoyeVp396bT4MRwWNr2P2QSmwsVFqiJyw=;
	b=bH4p6eaBOBg8H6Uwlo3ODjyyF5YgrONspQRXhQOjDsllLm3gOU2G8bCZU6
	sP7PIWJIMx9+97/odfJI4ZfXocKoLdjtSxOgp6mINBoU2r21nnuRhXi305w7
	fDw9z5uR+K;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
 Info-Package [was RE: draft-ietf-sip-info-events-00: multiple packages per
 INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Christer Holmberg wrote:
> Hi,
>  
> Let's assume I want to send an INFO with package foo.
>  
> The value of the Info-Package header is "foo", right?
>  
> Now, what is the value of the Content-Type header?

The package could support a number of content types: image/jpeg, 
text/plain, multipart/related, ...
Anything that the definition of the package says is allowed.

At least that is how I think Eric intended to to be.

	Paul

> Is it something which is generic for all info packages (e.g. application/info), OR is it something which is specified in the foo package description?
>  
> Regards,
>  
> Christer
> 
> ________________________________
> 
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
> Sent: Thu 23/10/2008 20:21
> To: Christer Holmberg
> Cc: Dean Willis; SIP IETF; Eric Burger
> Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs Info-Package [was RE: draft-ietf-sip-info-events-00: multiple packages per INFO]
> 
> 
> 
> Christer,
> 
> I don't understand where you are heading with this?
> 
> If I want to send an INFO with a jpeg, then what is this other mime type
> doing other than getting in my way.
> 
> OTOH, we haven't discussed Content-Disposition wrt INFO. In the absence
> of any mention, I assume that "render" will be used for info packages,
> and the detailed processing defined by the Info-Package value.
> 
> In some sense, the Info-Package value is serving the same purpose as
> Content-Disposition. We could *consider* using the C-D *instead* of the
> Info-Package header, so that what we would be negotiating would be the
> acceptable C-D values. The downside of that is that we would then need
> to open up the registration of new C-D values. I think that might be
> opposed by a lot of people.
> 
>         Thanks,
>         Paul
> 
> Christer Holmberg wrote:
>> Hi,
>>
>>>> Shouldn't we use Content-Type to indicate what is in the message body?
>>>> After all, we may need Content-Length etc.
>>> Ah, no.
>>>
>>> We had extended conversations on this earlier.  Content-Type tells you
>>> what's in the body; it just doesn't tell you what to DO with the body.
>>>
>>> What, for example, is the purpose of an image/jpeg in an INFO?
>> That is not what I meant.
>>
>> We can use the Info-Package header, but can't we use a generic mime value - which tells us that there is an info package in the body.
>>
>> Regards,
>>
>> Christer
>>
>>
>>
>>
> 
> 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 23 18:47:29 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 01ED03A6ACB;
	Thu, 23 Oct 2008 18:47:29 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E2DBD3A6AC8
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 18:47:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4njUVCuzZUd0 for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 18:47:27 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 2503A3A6848
	for <sip@ietf.org>; Thu, 23 Oct 2008 18:47:27 -0700 (PDT)
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9O1mci3011305
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 23 Oct 2008 20:48:40 -0500
Message-Id: <04FA10C5-B3BD-4368-BE66-A88DBD6EB2C8@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF083CCF9C@esealmw113.eemea.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 23 Oct 2008 20:48:33 -0500
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<490068D0.6000605@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF08924955@esealmw113.eemea.ericsson.se>
	<49008829.4050507@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9C@esealmw113.eemea.ericsson.se>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 23, 2008, at 12:58 PM, Christer Holmberg wrote:

> Wouldn't it be much simplier to define a generic mime, e.g.  
> application/info-package, and then each info package only needs to  
> define the Info-Package header value for that particular package?

No, as some packages might well send two bodies in a single INFO.

For example, envision a location-enabled image push: It sends an image/ 
jpeg and a pidf/lo that are correlated.

You need the Info-Package header to tell you what two bodies to look  
for and what they mean, and the MIME markup to know which is which.

--
Dean

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


From sip-bounces@ietf.org  Thu Oct 23 18:50:35 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CFD693A6AC5;
	Thu, 23 Oct 2008 18:50:35 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6C8A23A6AC5
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 18:50:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id th+h5NFomz7u for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 18:50:33 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id B5EEA3A6A6A
	for <sip@ietf.org>; Thu, 23 Oct 2008 18:50:33 -0700 (PDT)
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9O1oQFP011313
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 23 Oct 2008 20:51:00 -0500
Message-Id: <357F6D04-0BAE-47C1-8BAB-5E0FE4DA76B7@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF083CCF9D@esealmw113.eemea.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 23 Oct 2008 20:50:59 -0500
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com> A
	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>
	<CA9998CD4A020D418654FCDEF4E707DF088F17D5@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425C2C@DEEXC1U01.de.lucent.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F19BA@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425C50@DEEXC1U01.de.lucent.com>
	<A11BA33F-6F5B-425A-9D76-17C5894A86C9@softarmor.com>
	<49008B56.2010900@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9D@esealmw113.eemea.ericsson.se>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>,
	Paul Kyzivat <pkyzivat@cisco.com>, "Elwell,
	John" <john.elwell@siemens.com>, Eric Burger <eburger@bea.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 23, 2008, at 1:00 PM, Christer Holmberg wrote:

> Hi,
>
> Not only 3pcc, I think it could be useful to re-negotiate the  
> packages during the session. For example, I may want DTMFs only  
> during a certain period of the call, so for the rest of the call you  
> would not be able to generate INFOs by pressing digit buttons.
>
> Also, we may enable some application during the call, so the UAs  
> need to re-negotiate the packages. For example, I may tell you that  
> I have a vcard which I want to send you, but we may not have  
> negotiated that "by defualt" when the call was established.
>

then re-INVITE.

--
Dean

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


From sip-bounces@ietf.org  Thu Oct 23 18:57:12 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E0F8728C0D0;
	Thu, 23 Oct 2008 18:57:12 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 967883A6848
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 18:57:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3rN7cfUeZEs1 for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 18:57:10 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id BEDD63A6AC8
	for <sip@ietf.org>; Thu, 23 Oct 2008 18:57:10 -0700 (PDT)
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9O1oQFO011313
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 23 Oct 2008 20:50:27 -0500
Message-Id: <5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 23 Oct 2008 20:50:20 -0500
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>, Eric Burger <eburger@bea.com>,
	Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 23, 2008, at 12:59 PM, Christer Holmberg wrote:

> Hi,
>
>>> Shouldn't we use Content-Type to indicate what is in the message  
>>> body?
>>> After all, we may need Content-Length etc.
>>
>> Ah, no.
>>
>> We had extended conversations on this earlier.  Content-Type tells  
>> you
>> what's in the body; it just doesn't tell you what to DO with the  
>> body.
>>
>> What, for example, is the purpose of an image/jpeg in an INFO?
>
> That is not what I meant.
>
> We can use the Info-Package header, but can't we use a generic mime  
> value - which tells us that there is an info package in the body.
>

Nope. Not only might you have multiple bodies per INFO, you might have  
several different MIME types that might be usable with a given info- 
package.

For example, an image push app might use image/jpeg, image/gif, image/ 
raw, etc. The package defines which type or types are allowed.

--
Dean


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


From sip-bounces@ietf.org  Thu Oct 23 21:01:32 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8BFDB3A67A2;
	Thu, 23 Oct 2008 21:01:32 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4B62A3A67A2
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 21:01:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.574
X-Spam-Level: 
X-Spam-Status: No, score=-6.574 tagged_above=-999 required=5 tests=[AWL=0.025, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id EDbc3XjQ-YwM for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 21:01:31 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 4B07C3A65A5
	for <sip@ietf.org>; Thu, 23 Oct 2008 21:01:31 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,474,1220227200"; d="scan'208";a="25528316"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 24 Oct 2008 04:02:51 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9O42puq009934; 
	Fri, 24 Oct 2008 00:02:51 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9O42pKb017375;
	Fri, 24 Oct 2008 04:02:51 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 00:02:51 -0400
Received: from [10.86.242.189] ([10.86.242.189]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 00:02:50 -0400
Message-ID: <490148E9.6070300@cisco.com>
Date: Fri, 24 Oct 2008 00:02:49 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
References: <48FDEAD8.8010803@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com>
	A	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>	<0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>	<CA9998CD4A020D418654FCDEF4E707DF088F17D5@esealmw113.eemea.ericsson.se>	<5D1A7985295922448D5550C94DE2918002425C2C@DEEXC1U01.de.lucent.com>	<CA9998CD4A020D418654FCDEF4E707DF088F19BA@esealmw113.eemea.ericsson.se>	<5D1A7985295922448D5550C94DE2918002425C50@DEEXC1U01.de.lucent.com>	<A11BA33F-6F5B-425A-9D76-17C5894A86C9@softarmor.com>	<49008B56.2010900@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF9D@esealmw113.eemea.ericsson.se>
	<357F6D04-0BAE-47C1-8BAB-5E0FE4DA76B7@softarmor.com>
In-Reply-To: <357F6D04-0BAE-47C1-8BAB-5E0FE4DA76B7@softarmor.com>
X-OriginalArrivalTime: 24 Oct 2008 04:02:50.0904 (UTC)
	FILETIME=[62160180:01C9358D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1314; t=1224820971;
	x=1225684971; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20multiple=20packages=20per=20INFO |Sender:=20
	|To:=20Dean=20Willis=20<dean.willis@softarmor.com>;
	bh=B4rbA+pXu/vcwgzFKwnK8AfdTqOnHnbQAr5F1fBux9k=;
	b=r/p8qZq8deM2qJH4ZSitiUId+sOL/boQSva9xWUsYCSOigLGab6yWQ/GsR
	PfbO7GPGTZCrI6so925AyF7RT4Z5sFwJAQ/d/M74Jd/He/Ojh16CIE9cadgz
	1Z8zGylPaI;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, "Elwell, John" <john.elwell@siemens.com>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>, Eric Burger <eburger@bea.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Dean,

I'm now confused on what you are advocating.

As its currently written, you can negotiate which packages you want to 
use. The later in the call you can renegotiate to use different ones. 
That seems consistent with what you are saying. So what is the issue?

	Thanks,
	Paul

Dean Willis wrote:
> 
> On Oct 23, 2008, at 1:00 PM, Christer Holmberg wrote:
> 
>> Hi,
>>
>> Not only 3pcc, I think it could be useful to re-negotiate the packages 
>> during the session. For example, I may want DTMFs only during a 
>> certain period of the call, so for the rest of the call you would not 
>> be able to generate INFOs by pressing digit buttons.
>>
>> Also, we may enable some application during the call, so the UAs need 
>> to re-negotiate the packages. For example, I may tell you that I have 
>> a vcard which I want to send you, but we may not have negotiated that 
>> "by defualt" when the call was established.
>>
> 
> then re-INVITE.
> 
> -- 
> Dean
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 23 21:22:04 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 91C7C3A689D;
	Thu, 23 Oct 2008 21:22:04 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E026F3A689D
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 21:22:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.213
X-Spam-Level: 
X-Spam-Status: No, score=-6.213 tagged_above=-999 required=5 tests=[AWL=0.036, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5xqry6AdyWLi for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 21:22:02 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id BCEEF3A6358
	for <sip@ietf.org>; Thu, 23 Oct 2008 21:22:01 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	25F2121422; Fri, 24 Oct 2008 06:23:21 +0200 (CEST)
X-AuditID: c1b4fb3e-aef86bb00000537b-16-49014db9250e
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	0944621428; Fri, 24 Oct 2008 06:23:21 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 06:23:20 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 24 Oct 2008 06:22:15 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCFA8@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
Thread-Index: Ack1exdRh0eFtlRMTTeffJYNC7Ez9wAFQEHs
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>
	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com> A
	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>
	<0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>
	<CA9998CD4A020D418654FCDEF4E707DF088F17D5@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425C2C@DEEXC1U01.de.lucent.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F19BA@esealmw113.eemea.ericsson.se>
	<5D1A7985295922448D5550C94DE2918002425C50@DEEXC1U01.de.lucent.com>
	<A11BA33F-6F5B-425A-9D76-17C5894A86C9@softarmor.com>
	<49008B56.2010900@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9D@esealmw113.eemea.ericsson.se>
	<357F6D04-0BAE-47C1-8BAB-5E0FE4DA76B7@softarmor.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 24 Oct 2008 04:23:20.0824 (UTC)
	FILETIME=[3F2CE780:01C93590]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>,
	Paul Kyzivat <pkyzivat@cisco.com>, "Elwell,
	John" <john.elwell@siemens.com>, Eric Burger <eburger@bea.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi,

>> Not only 3pcc, I think it could be useful to re-negotiate the 
>> packages during the session. For example, I may want DTMFs only 
>> during a certain period of the call, so for the rest of the call you 
>> would not be able to generate INFOs by pressing digit buttons.
>>
>> Also, we may enable some application during the call, so the UAs 
>> need to re-negotiate the packages. For example, I may tell you that 
>> I have a vcard which I want to send you, but we may not have 
>> negotiated that "by defualt" when the call was established.
>>
>
>then re-INVITE.

Yes.
 
Where you thinking of something else?
 
Regards,
 
Christer

 

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


From sip-bounces@ietf.org  Thu Oct 23 23:19:51 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E02DB3A68AA;
	Thu, 23 Oct 2008 23:19:51 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A2E753A6358
	for <sip@core3.amsl.com>; Thu, 23 Oct 2008 23:19:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.213
X-Spam-Level: 
X-Spam-Status: No, score=-6.213 tagged_above=-999 required=5 tests=[AWL=0.036, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YooEkbgm7EeG for <sip@core3.amsl.com>;
	Thu, 23 Oct 2008 23:19:49 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 90FA03A690E
	for <sip@ietf.org>; Thu, 23 Oct 2008 23:19:49 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	226D520C88; Fri, 24 Oct 2008 08:21:09 +0200 (CEST)
X-AuditID: c1b4fb3c-ab8c9bb0000015b5-2d-490169545364
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	F0B602074D; Fri, 24 Oct 2008 08:21:08 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 08:21:08 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 24 Oct 2008 08:21:07 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>
In-Reply-To: <5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
Thread-Index: Ack1exikY5eWTSdlRGeTTBK8RkCtEwAJGuxw
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Dean Willis" <dean.willis@softarmor.com>,
	"Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 24 Oct 2008 06:21:08.0793 (UTC)
	FILETIME=[B4036290:01C935A0]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 
Hi,

(I've put all text about this into a single reply)

Dean:
=====

>>>>Shouldn't we use Content-Type to indicate what is in the message
body?
>>>>After all, we may need Content-Length etc.
>>>
>>>Ah, no.
>>>
>>>We had extended conversations on this earlier.  Content-Type tells 
>>>you what's in the body; it just doesn't tell you what to DO with the 
>>>body.
>>>
>>>What, for example, is the purpose of an image/jpeg in an INFO?
>>
>>That is not what I meant.
>>
>>We can use the Info-Package header, but can't we use a generic mime 
>>value - which tells us that there is an info package in the body.
>
>Nope. Not only might you have multiple bodies per INFO, you might have

>several different MIME types that might be usable with a given info- 
>package.
>
>For example, an image push app might use image/jpeg, image/gif, image/ 
>raw, etc. The package defines which type or types are allowed.
>>Wouldn't it be much simplier to define a generic mime, e.g.  
>>application/info-package, and then each info package only needs to 
>>define the Info-Package header value for that particular package?
>
>No, as some packages might well send two bodies in a single INFO.
>
>For example, envision a location-enabled image push: It sends an image/
jpeg and a pidf/lo that are correlated.
>
>You need the Info-Package header to tell you what two bodies to look
for and what they mean, and the MIME markup to know which is which.

[Christer] If we assume that we are NOT going to allow multiple packages
per INFO (nobody has objected to that restriction) we wouldn't have that
problem.



Paul:
=====

>>Let's assume I want to send an INFO with package foo.
>>  
>>The value of the Info-Package header is "foo", right?
>>  
>>Now, what is the value of the Content-Type header?
>
>The package could support a number of content types: image/jpeg,
text/plain, multipart/related, ...
>Anything that the definition of the package says is allowed.
>
>At least that is how I think Eric intended to to be.

[Christer] I agree that a package could be associated with a number of
content types. But, since the Info-Package header shows which package is
included, I just wonder why we can't use a common C-T mime.


Regards,

Christer




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


From sip-bounces@ietf.org  Fri Oct 24 03:13:29 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 370C53A6A16;
	Fri, 24 Oct 2008 03:13:29 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9998A3A6A16
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 03:13:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.657
X-Spam-Level: 
X-Spam-Status: No, score=-2.657 tagged_above=-999 required=5
	tests=[AWL=-0.058, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6CJmy+MffE6Y for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 03:13:27 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39])
	by core3.amsl.com (Postfix) with ESMTP id BA16D3A68E0
	for <sip@ietf.org>; Fri, 24 Oct 2008 03:13:27 -0700 (PDT)
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1])
	by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id m9OAEjt1013825;
	Fri, 24 Oct 2008 05:14:45 -0500 (CDT)
Received: from DEEXP02.DE.lucent.com ([135.248.187.66]) by
	ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 05:14:45 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.30]) by
	DEEXP02.DE.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 12:14:42 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 24 Oct 2008 12:14:40 +0200
Message-ID: <5D1A7985295922448D5550C94DE2918002425F1E@DEEXC1U01.de.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Requirements for INFO work
Thread-Index: Ack1wVONYjzXMlexQOKlxHGwKIAEJg==
From: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: "SIP IETF" <sip@ietf.org>
X-OriginalArrivalTime: 24 Oct 2008 10:14:42.0360 (UTC)
	FILETIME=[54C00380:01C935C1]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: draft-ietf-sip-info-events@tools.ietf.org
Subject: [Sip] Requirements for INFO work
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

(As WG chair)

I believe that the original starting point for INFO was to regularise
the existing position with INFO usage, and that the decision we made to
charter this work was based on developing a more valid basis for meeting
the existing INFO requirements. I believe previous discussion related
around overriding such constraints as:

1)	identification of INFO usages to the remote entity so that both
could agree that INFO was in use for the same purpose

2)	registration of usages so that there could be some
interoperability between two INFO usages from different vendors.

(I am not trying to create a complete list here and now)

Much of the discussion seems to be now on "We have this new capability
so it must now be capable of doing these things as well". I do not
believe many of these things were possible with legacy INFO usage.

If we are not careful, I would think that the SIP chairs are going to
have to insist on a requirements phase to make sure we have a robust and
complete set of requirements before proceeding further. Too many
previous SIP deliverables have been derailed because we get to the end
of the work, and then find we don't understand why we were doing the
work in the first place.

I would direct that the editors start compiling a list of what they
consider this work is meant to do, in terms independent of the actual
implementation, as this discussion proceeds, and we will embed that in
the document at some time. Treat this as the requirements list we are
trying to work to. Moreover, if we have the need to add or amend that
list, we will do a consensus call on that change. 

If in the review of the document by the working group - we find
something that is not in the requirements, and the document would be
simpler by not doing it, then we will take it out. That should be
stimulation enough for making sure we keep this list up to date.

Regards

Keith

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


From sip-bounces@ietf.org  Fri Oct 24 05:05:44 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0C3393A6AAF;
	Fri, 24 Oct 2008 05:05:44 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 657063A6AAF
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 05:05:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.576
X-Spam-Level: 
X-Spam-Status: No, score=-6.576 tagged_above=-999 required=5 tests=[AWL=0.023, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jEpc9EVcaY68 for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 05:05:41 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 3256C3A691F
	for <sip@ietf.org>; Fri, 24 Oct 2008 05:05:41 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,477,1220227200"; d="scan'208";a="181856518"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by sj-iport-6.cisco.com with ESMTP; 24 Oct 2008 12:07:02 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9OC72sb004099; 
	Fri, 24 Oct 2008 08:07:02 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9OC71on010851;
	Fri, 24 Oct 2008 12:07:02 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 08:06:56 -0400
Received: from [10.86.242.189] ([10.86.242.189]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 08:06:56 -0400
Message-ID: <4901BA73.1010700@cisco.com>
Date: Fri, 24 Oct 2008 08:07:15 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 24 Oct 2008 12:06:56.0639 (UTC)
	FILETIME=[02B170F0:01C935D1]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2085; t=1224850022;
	x=1225714022; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20Content-Type=20vs=20Info-Package=0A=20[was=20RE=3A=20dra
	ft-ietf-sip-info-events-00=3A=20multiple=20packages=20per=20
	INFO] |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=HZUehWNfv7g1xdfq6waiLLmKEXbjFz95oHB+fDwmFMU=;
	b=OdsgzsQUzpbPlOk44hYY4IhmnTwU3aG0z31+9huloelgudBUSumi/5EYFl
	76Yu7YQgwDABmvCRaaI5vxh9A0a2X8I9trSayIgwke/A/R2JG0WW3zsXF3bo
	sQ5Hn6uV0t;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
 Info-Package [was RE: draft-ietf-sip-info-events-00: multiple packages per
 INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Pruned. Comments inline.

Christer Holmberg wrote:
>  
> Hi,
> 
> (I've put all text about this into a single reply)

>> For example, envision a location-enabled image push: It sends an image/
> jpeg and a pidf/lo that are correlated.
>> You need the Info-Package header to tell you what two bodies to look
> for and what they mean, and the MIME markup to know which is which.
> 
> [Christer] If we assume that we are NOT going to allow multiple packages
> per INFO (nobody has objected to that restriction) we wouldn't have that
> problem.


> Paul:
> =====
> 
>>> Let's assume I want to send an INFO with package foo.
>>>  
>>> The value of the Info-Package header is "foo", right?
>>>  
>>> Now, what is the value of the Content-Type header?
>> The package could support a number of content types: image/jpeg,
> text/plain, multipart/related, ...
>> Anything that the definition of the package says is allowed.
>>
>> At least that is how I think Eric intended to to be.
> 
> [Christer] I agree that a package could be associated with a number of
> content types. But, since the Info-Package header shows which package is
> included, I just wonder why we can't use a common C-T mime.

Just because there is only one package per info, there still could be 
*alternative* C-Ts for a given package. If you use one C-T for all INFOs 
then you can't do this. And its an abuse of the C-T, since then it won't 
describe the format of the content.

I do think there is something we haven't discussed: how do we figure out 
what part of the overall body is the part that carries the package? 
Normally this is no issue, since it is the entire body of the INFO 
message. But there are cases where it might not be. For instance if 
S/MIME is used, or if there is some header in the message the needs to 
reference a body part from a CID URI.

The answer to this goes back to Content-Disposition. The body part that 
contains the info package should have a unique C-D. That can be 
"render", or we could pick some other one.

	Thanks,
	Paul

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


From sip-bounces@ietf.org  Fri Oct 24 05:08:58 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1E5BE28C0E9;
	Fri, 24 Oct 2008 05:08:58 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CFD163A6A92;
	Fri, 24 Oct 2008 05:08:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.578
X-Spam-Level: 
X-Spam-Status: No, score=-6.578 tagged_above=-999 required=5 tests=[AWL=0.021, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id n2IEUiMOYVyV; Fri, 24 Oct 2008 05:08:55 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71])
	by core3.amsl.com (Postfix) with ESMTP id 18CF43A6A41;
	Fri, 24 Oct 2008 05:08:55 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,477,1220227200"; d="scan'208";a="98484448"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by sj-iport-2.cisco.com with ESMTP; 24 Oct 2008 12:10:06 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9OCA6oh005088; 
	Fri, 24 Oct 2008 08:10:06 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9OCA5Au027043;
	Fri, 24 Oct 2008 12:10:05 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 08:10:02 -0400
Received: from [10.86.242.189] ([10.86.242.189]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 08:10:02 -0400
Message-ID: <4901BB2D.3030908@cisco.com>
Date: Fri, 24 Oct 2008 08:10:21 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Saverio Niccolini <Saverio.Niccolini@nw.neclab.eu>
References: <5d688850809301209r6b43aeeaqa4c9f49fa2fa1706@mail.gmail.com><48E28DA2.5060708@cisco.com>	<200810070242.m972grm741386799@shell01.TheWorld.com>
	<547F018265F92642B577B986577D671C3E0612@VENUS.office>
In-Reply-To: <547F018265F92642B577B986577D671C3E0612@VENUS.office>
X-OriginalArrivalTime: 24 Oct 2008 12:10:02.0213 (UTC)
	FILETIME=[714DC950:01C935D1]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1405; t=1224850206;
	x=1225714206; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20[Sip]=20INVITE=20dialogs
	|Sender:=20
	|To:=20Saverio=20Niccolini=20<Saverio.Niccolini@nw.neclab.e u>;
	bh=j1P5DP0VYuCTp3f8X7RIngDD/fx2hJQcik0GgC0kynA=;
	b=COtYpgeNKjUdsE4J45pshGQsGLGYanJNQStY27vEPEXokk+rCQ5XHx4Msl
	OpIEsBQj9c+8AVI6zv1WhIDSfMXUsHCpnzHuOXCe1X+tA9Jwi/KIdpE+rDEl
	YuvERdQA+h;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: sip@ietf.org, sipping@ietf.org, hasebe.miki@east.ntt.co.jp
Subject: Re: [Sip] [Sipping]  INVITE dialogs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I think it is up to the wg and the chairs whether the draft is opened up 
for inclusion of more races. I haven't had time to examine Pamela's 
document in detail, so I can't speak to the specific races she has found 
right now. I would not be terribly surprised if there are more. But I am 
surprised if there are 40 more. Perhaps many of those are variants on a 
theme and might be viewed by others as some smaller number.

	Thanks,
	Paul

Saverio Niccolini wrote:
>> It would be a very interesting "live fire demonstration" of 
>> the value of the formalism if it discovered race conditions 
>> that we hadn't identified by informal means.
> 
> I would not be surprise to discover that race conditions identified by
> informal means are much less than the ones identified using a formalism
> (even if one using simplifications).
> 
> Paul was saying there is not chance to touch the
> draft-ietf-sipping-race-examples
> 
> is there any plan to address the identified new race conditions
> in another draft then? (Pamela was speaking of about 40 more...)
> 
> Saverio
> _______________________________________________
> Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 24 05:14:50 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 408BE28C166;
	Fri, 24 Oct 2008 05:14:50 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1BD6A28C166
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 05:14:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.213
X-Spam-Level: 
X-Spam-Status: No, score=-6.213 tagged_above=-999 required=5 tests=[AWL=0.036, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id HkNltDFBWTOq for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 05:14:48 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 1B37F28C11A
	for <sip@ietf.org>; Fri, 24 Oct 2008 05:14:48 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	468E4204FF; Fri, 24 Oct 2008 14:16:00 +0200 (CEST)
X-AuditID: c1b4fb3e-ad783bb00000537b-1b-4901bc801445
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	2CDB120122; Fri, 24 Oct 2008 14:16:00 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 14:15:59 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 24 Oct 2008 14:15:59 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>
In-Reply-To: <4901BA73.1010700@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
Thread-Index: Ack10Qj/dTYJJCShTJS/8IEHTF/1oQAAJQwQ
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>
	<4901BA73.1010700@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 24 Oct 2008 12:15:59.0464 (UTC)
	FILETIME=[463DF680:01C935D2]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>I do think there is something we haven't discussed: how do we 
>figure out what part of the overall body is the part that 
>carries the package? 
>Normally this is no issue, since it is the entire body of the 
>INFO message. But there are cases where it might not be. For 
>instance if S/MIME is used, or if there is some header in the 
>message the needs to reference a body part from a CID URI.
> 
>The answer to this goes back to Content-Disposition. The body 
>part that contains the info package should have a unique C-D. 
>That can be "render", or we could pick some other one.

I believe the mime rules are something like:

--boundary
Mime-headers
Empy-line
Content (SDP, info packet, etc)
--boundary--


For SIP, the ruleas are:

SIP-part
Empty-line
Message body (SDP, info packet - or one of more mimes).


I guess the question is whether we should define some generic syntax for
the info packages, e.g. Something which identifies the beginning of an
info package.

For SDP, you find the beginning by looking for the v= parameter.

Regards,

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


From sip-bounces@ietf.org  Fri Oct 24 05:30:46 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 381DD3A69F5;
	Fri, 24 Oct 2008 05:30:46 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 35D543A69F5
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 05:30:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.579
X-Spam-Level: 
X-Spam-Status: No, score=-6.579 tagged_above=-999 required=5 tests=[AWL=0.020, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FeStCWdawyMp for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 05:30:43 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id ED5EF3A6829
	for <sip@ietf.org>; Fri, 24 Oct 2008 05:30:42 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,477,1220227200"; d="scan'208";a="25525169"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 24 Oct 2008 12:31:48 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9OCVmYv007812; 
	Fri, 24 Oct 2008 08:31:48 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9OCVmvT016330;
	Fri, 24 Oct 2008 12:31:48 GMT
Received: from xfe-rtp-211.amer.cisco.com ([64.102.31.113]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 08:31:48 -0400
Received: from [10.86.242.189] ([10.86.242.189]) by xfe-rtp-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 08:31:22 -0400
Message-ID: <4901C02C.1000305@cisco.com>
Date: Fri, 24 Oct 2008 08:31:40 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
References: <5D1A7985295922448D5550C94DE2918002425F1E@DEEXC1U01.de.lucent.com>
In-Reply-To: <5D1A7985295922448D5550C94DE2918002425F1E@DEEXC1U01.de.lucent.com>
X-OriginalArrivalTime: 24 Oct 2008 12:31:22.0545 (UTC)
	FILETIME=[6C70F210:01C935D4]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3004; t=1224851508;
	x=1225715508; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Requirements=20for=20INFO=20wor k
	|Sender:=20
	|To:=20=22DRAGE,=20Keith=20\(Keith\)=22=20<drage@alcatel-lu
	cent.com>; bh=lIhEdpMl2soVG3qqqWvBb4HenIPGctN0cG8JL0o6SeA=;
	b=kRDKxWxZDmSqw8LomYPDgqnA+GOdzc8f5CTrck6r1hcKfP++PJ/GXxQoDb
	SVqz+eDIzpXKI/xk1v/CkHctZfPybuXEWeqhsI3T5Xn8jRiNDfQ/hlfQX3Hl
	quYq418tE0;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, draft-ietf-sip-info-events@tools.ietf.org
Subject: Re: [Sip] Requirements for INFO work
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Keith,

I can see why you would send this out, but IMO the status is not as far 
in the weeds as you seem to think.

AFAIK the only real scope creep that has come up is around multiple info 
packages per INFO. And I think we have all largely agreed to exclude that.

There has been a lot of discussion of how the negotiation of packages 
works, but that is intrinsic to what we are doing. And once you agree 
that you must negotiate this (which I think we did) then renegotiation 
must be addressed.

The rest of the discussion has been on clarifying ambiguities, and so is 
a good thing.

	Thanks,
	Paul

DRAGE, Keith (Keith) wrote:
> (As WG chair)
> 
> I believe that the original starting point for INFO was to regularise
> the existing position with INFO usage, and that the decision we made to
> charter this work was based on developing a more valid basis for meeting
> the existing INFO requirements. I believe previous discussion related
> around overriding such constraints as:
> 
> 1)	identification of INFO usages to the remote entity so that both
> could agree that INFO was in use for the same purpose
> 
> 2)	registration of usages so that there could be some
> interoperability between two INFO usages from different vendors.
> 
> (I am not trying to create a complete list here and now)
> 
> Much of the discussion seems to be now on "We have this new capability
> so it must now be capable of doing these things as well". I do not
> believe many of these things were possible with legacy INFO usage.
> 
> If we are not careful, I would think that the SIP chairs are going to
> have to insist on a requirements phase to make sure we have a robust and
> complete set of requirements before proceeding further. Too many
> previous SIP deliverables have been derailed because we get to the end
> of the work, and then find we don't understand why we were doing the
> work in the first place.
> 
> I would direct that the editors start compiling a list of what they
> consider this work is meant to do, in terms independent of the actual
> implementation, as this discussion proceeds, and we will embed that in
> the document at some time. Treat this as the requirements list we are
> trying to work to. Moreover, if we have the need to add or amend that
> list, we will do a consensus call on that change. 
> 
> If in the review of the document by the working group - we find
> something that is not in the requirements, and the document would be
> simpler by not doing it, then we will take it out. That should be
> stimulation enough for making sure we keep this list up to date.
> 
> Regards
> 
> Keith
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 24 05:40:52 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AF9533A6A58;
	Fri, 24 Oct 2008 05:40:52 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E301F3A6A58
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 05:40:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.58
X-Spam-Level: 
X-Spam-Status: No, score=-6.58 tagged_above=-999 required=5 tests=[AWL=0.019, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CPcVDEplT05C for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 05:40:50 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 275613A6AA3
	for <sip@ietf.org>; Fri, 24 Oct 2008 05:40:50 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,477,1220227200"; d="scan'208";a="181874879"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by sj-iport-6.cisco.com with ESMTP; 24 Oct 2008 12:42:06 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9OCg5nw017378; 
	Fri, 24 Oct 2008 08:42:05 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9OCg5c4018886;
	Fri, 24 Oct 2008 12:42:05 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 08:42:04 -0400
Received: from [10.86.242.189] ([10.86.242.189]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 08:42:06 -0400
Message-ID: <4901C2B1.1050209@cisco.com>
Date: Fri, 24 Oct 2008 08:42:25 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>
	<4901BA73.1010700@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 24 Oct 2008 12:42:06.0162 (UTC)
	FILETIME=[EC111B20:01C935D5]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1449; t=1224852125;
	x=1225716125; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20Content-Type=20vs=20Info-Package=0A=20[was=20RE=3A=20dra
	ft-ietf-sip-info-events-00=3A=20multiple=20packages=20per=20
	INFO] |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=MXYTWI7TwK9PmVb37Fpec843/rtzsgnPZ/utQ4M92NE=;
	b=rfG7JpXcwSG0hSlUbLobrhU+d5eVq7Eg/BSegY+/tpyt2ZYdQlR9W7/xZj
	yRmuSoJVulDe8qNvuO4nkT/cvWkAh1HWGyrkQt5s9VGuym5iFqsJL+7dOYAE
	2hoEniBpAt;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
 Info-Package [was RE: draft-ietf-sip-info-events-00: multiple packages per
 INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer,

For SDP, you find the part by looking for the one with 
Content-Disposition:session. If there is a part with no C-D header then 
one with a C-T of application/sdp defaults to "session". So its all 
about C-D.

	Paul

Christer Holmberg wrote:
> Hi, 
> 
>> I do think there is something we haven't discussed: how do we 
>> figure out what part of the overall body is the part that 
>> carries the package? 
>> Normally this is no issue, since it is the entire body of the 
>> INFO message. But there are cases where it might not be. For 
>> instance if S/MIME is used, or if there is some header in the 
>> message the needs to reference a body part from a CID URI.
>>
>> The answer to this goes back to Content-Disposition. The body 
>> part that contains the info package should have a unique C-D. 
>> That can be "render", or we could pick some other one.
> 
> I believe the mime rules are something like:
> 
> --boundary
> Mime-headers
> Empy-line
> Content (SDP, info packet, etc)
> --boundary--
> 
> 
> For SIP, the ruleas are:
> 
> SIP-part
> Empty-line
> Message body (SDP, info packet - or one of more mimes).
> 
> 
> I guess the question is whether we should define some generic syntax for
> the info packages, e.g. Something which identifies the beginning of an
> info package.
> 
> For SDP, you find the beginning by looking for the v= parameter.
> 
> Regards,
> 
> Christer
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 24 05:45:55 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8079C3A6A92;
	Fri, 24 Oct 2008 05:45:55 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1BE0C3A6AD0
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 05:45:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.214
X-Spam-Level: 
X-Spam-Status: No, score=-6.214 tagged_above=-999 required=5 tests=[AWL=0.035, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id d7DJNMcNIiJo for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 05:45:53 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 0FF4D3A6A92
	for <sip@ietf.org>; Fri, 24 Oct 2008 05:45:53 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	B3FCC210E3; Fri, 24 Oct 2008 14:47:13 +0200 (CEST)
X-AuditID: c1b4fb3e-aef86bb00000537b-21-4901c3d121cf
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	9DABE2155B; Fri, 24 Oct 2008 14:47:13 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 14:47:13 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 24 Oct 2008 14:47:12 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>
In-Reply-To: <4901C2B1.1050209@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
Thread-Index: Ack11fNBtz7nyz2WSOmjnXS7oqf9UAAAHT3w
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>
	<4901BA73.1010700@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>
	<4901C2B1.1050209@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 24 Oct 2008 12:47:13.0059 (UTC)
	FILETIME=[A2FDDF30:01C935D6]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>For SDP, you find the part by looking for the one with 
>Content-Disposition:session. If there is a part with no C-D 
>header then one with a C-T of application/sdp defaults to 
>"session". So its all about C-D.

The C-D header gives you information about the body, yes, but I don't
think it helps you to FIND the body.

That's what the SIP and MIME ABNFs are for.

Regards,

Christer





> 
> 	Paul
> 
> Christer Holmberg wrote:
> > Hi,
> > 
> >> I do think there is something we haven't discussed: how do 
> we figure 
> >> out what part of the overall body is the part that carries the 
> >> package?
> >> Normally this is no issue, since it is the entire body of the INFO 
> >> message. But there are cases where it might not be. For 
> instance if 
> >> S/MIME is used, or if there is some header in the message 
> the needs 
> >> to reference a body part from a CID URI.
> >>
> >> The answer to this goes back to Content-Disposition. The body part 
> >> that contains the info package should have a unique C-D.
> >> That can be "render", or we could pick some other one.
> > 
> > I believe the mime rules are something like:
> > 
> > --boundary
> > Mime-headers
> > Empy-line
> > Content (SDP, info packet, etc)
> > --boundary--
> > 
> > 
> > For SIP, the ruleas are:
> > 
> > SIP-part
> > Empty-line
> > Message body (SDP, info packet - or one of more mimes).
> > 
> > 
> > I guess the question is whether we should define some 
> generic syntax 
> > for the info packages, e.g. Something which identifies the 
> beginning 
> > of an info package.
> > 
> > For SDP, you find the beginning by looking for the v= parameter.
> > 
> > Regards,
> > 
> > Christer
> > 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 24 06:10:52 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6AD073A6914;
	Fri, 24 Oct 2008 06:10:52 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2F8EC3A6B20
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 06:10:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.564
X-Spam-Level: 
X-Spam-Status: No, score=-6.564 tagged_above=-999 required=5 tests=[AWL=0.035, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id k8x6T+6XKDIB for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 06:10:50 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 3D4463A6B2E
	for <sip@ietf.org>; Fri, 24 Oct 2008 06:10:37 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,477,1220227200"; d="scan'208";a="181896686"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 24 Oct 2008 13:11:59 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m9ODBx2H032755; 
	Fri, 24 Oct 2008 06:11:59 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m9ODBtsf027050;
	Fri, 24 Oct 2008 13:11:59 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 09:11:56 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 09:11:56 -0400
Message-ID: <4901C9B1.3070404@cisco.com>
Date: Fri, 24 Oct 2008 09:12:17 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>
	<4901BA73.1010700@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>
	<4901C2B1.1050209@cisco.com>
In-Reply-To: <4901C2B1.1050209@cisco.com>
X-OriginalArrivalTime: 24 Oct 2008 13:11:56.0549 (UTC)
	FILETIME=[17387B50:01C935DA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1913; t=1224853919;
	x=1225717919; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20Content-Type=20vs=20Info-Package=0A=20[was=20RE=3A=20dra
	ft-ietf-sip-info-events-00=3A=20multiple=20packages=20per=20
	INFO] |Sender:=20;
	bh=VQLVO2GKQLsMBkkb+7Vaj++stXpHoRSa/vUGj7hMgI8=;
	b=HHRUG9qK9W7wvvM5bcU42Q0D/8W3hDQgZNZaQY0oGlzN7cQvO7pz1EjsOP
	M553i7dv1yu9OGuyOWgwiJ3QAq9O/dwPV3FT/2QBG0tFXb/Zs2HrIM0CKt8J
	l+Uda1ystj;
Authentication-Results: sj-dkim-4; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
 Info-Package [was RE: draft-ietf-sip-info-events-00: multiple packages per
 INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Oops, I just realized I didn't state this the way I meant...

Paul Kyzivat wrote:
> Christer,
> 
> For SDP, you find the part by looking for the one with 
> Content-Disposition:session. If there is a part with no C-D header then 
> one with a C-T of application/sdp defaults to "session". So its all 
> about C-D.

For *offers and answers* you find the part by looking for the one with 
Content-Disposition:session. If there is a part with no C-D header then 
  one with a C-T of application/sdp defaults to "session". So its all 
about C-D. (In theory, application/sdp is just one of the C-Ts that 
might be used to encode offers and answers.)

>     Paul
> 
> Christer Holmberg wrote:
>> Hi,
>>> I do think there is something we haven't discussed: how do we figure 
>>> out what part of the overall body is the part that carries the 
>>> package? Normally this is no issue, since it is the entire body of 
>>> the INFO message. But there are cases where it might not be. For 
>>> instance if S/MIME is used, or if there is some header in the message 
>>> the needs to reference a body part from a CID URI.
>>>
>>> The answer to this goes back to Content-Disposition. The body part 
>>> that contains the info package should have a unique C-D. That can be 
>>> "render", or we could pick some other one.
>>
>> I believe the mime rules are something like:
>>
>> --boundary
>> Mime-headers
>> Empy-line
>> Content (SDP, info packet, etc)
>> --boundary--
>>
>>
>> For SIP, the ruleas are:
>>
>> SIP-part
>> Empty-line
>> Message body (SDP, info packet - or one of more mimes).
>>
>>
>> I guess the question is whether we should define some generic syntax for
>> the info packages, e.g. Something which identifies the beginning of an
>> info package.
>>
>> For SDP, you find the beginning by looking for the v= parameter.
>>
>> Regards,
>>
>> Christer
>>
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 24 06:38:33 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BC37928C0EF;
	Fri, 24 Oct 2008 06:38:33 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 546AF28C0EF
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 06:38:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.565
X-Spam-Level: 
X-Spam-Status: No, score=-6.565 tagged_above=-999 required=5 tests=[AWL=0.034, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8vAGYXyB2TMZ for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 06:38:26 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id ABA793A6A75
	for <sip@ietf.org>; Fri, 24 Oct 2008 06:38:26 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,477,1220227200"; d="scan'208";a="25564881"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 24 Oct 2008 13:39:48 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9ODdmOo011789; 
	Fri, 24 Oct 2008 09:39:48 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9ODdmCe008512;
	Fri, 24 Oct 2008 13:39:48 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 09:39:47 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 09:39:47 -0400
Message-ID: <4901D025.6060302@cisco.com>
Date: Fri, 24 Oct 2008 09:39:49 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>
	<4901BA73.1010700@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>
	<4901C2B1.1050209@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 24 Oct 2008 13:39:47.0512 (UTC)
	FILETIME=[FB313380:01C935DD]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1901; t=1224855588;
	x=1225719588; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20Content-Type=20vs=20Info-Package=0A=20[was=20RE=3A=20dra
	ft-ietf-sip-info-events-00=3A=20multiple=20packages=20per=20
	INFO] |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=MonGaF3D9Dw6cSLq5FjM4/MfbXTSN6dLdDyqu3NFws4=;
	b=H+QOkQaBW/z5Gd1iLeMYE+2D/Vs1xxFtGbVsMS8+zMswce5KtAfRVuEo/u
	ucnnZU6MtVyndYCql1msf7twrRDYeHY3oxfYavazRWT/h83bpiXIt9bkN+if
	qYxHRA8Z3a;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
 Info-Package [was RE: draft-ietf-sip-info-events-00: multiple packages per
 INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Oh, sorry. I didn't really mean "find". I meant "choose the appropriate 
body part".

	Paul

Christer Holmberg wrote:
> Hi, 
> 
>> For SDP, you find the part by looking for the one with 
>> Content-Disposition:session. If there is a part with no C-D 
>> header then one with a C-T of application/sdp defaults to 
>> "session". So its all about C-D.
> 
> The C-D header gives you information about the body, yes, but I don't
> think it helps you to FIND the body.
> 
> That's what the SIP and MIME ABNFs are for.
> 
> Regards,
> 
> Christer
> 
> 
> 
> 
> 
>> 	Paul
>>
>> Christer Holmberg wrote:
>>> Hi,
>>>
>>>> I do think there is something we haven't discussed: how do 
>> we figure 
>>>> out what part of the overall body is the part that carries the 
>>>> package?
>>>> Normally this is no issue, since it is the entire body of the INFO 
>>>> message. But there are cases where it might not be. For 
>> instance if 
>>>> S/MIME is used, or if there is some header in the message 
>> the needs 
>>>> to reference a body part from a CID URI.
>>>>
>>>> The answer to this goes back to Content-Disposition. The body part 
>>>> that contains the info package should have a unique C-D.
>>>> That can be "render", or we could pick some other one.
>>> I believe the mime rules are something like:
>>>
>>> --boundary
>>> Mime-headers
>>> Empy-line
>>> Content (SDP, info packet, etc)
>>> --boundary--
>>>
>>>
>>> For SIP, the ruleas are:
>>>
>>> SIP-part
>>> Empty-line
>>> Message body (SDP, info packet - or one of more mimes).
>>>
>>>
>>> I guess the question is whether we should define some 
>> generic syntax 
>>> for the info packages, e.g. Something which identifies the 
>> beginning 
>>> of an info package.
>>>
>>> For SDP, you find the beginning by looking for the v= parameter.
>>>
>>> Regards,
>>>
>>> Christer
>>>
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 24 06:43:36 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 82FCC28C16F;
	Fri, 24 Oct 2008 06:43:36 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 499DC28C0F1
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 06:43:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1SiOUF-NQk9y for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 06:43:31 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 90A6B28C16F
	for <SIP@ietf.org>; Fri, 24 Oct 2008 06:43:28 -0700 (PDT)
Received: from [216.47.140.112] (port=53254 helo=[10.10.11.148])
	by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1KtMy6-0005OQ-5i for SIP@ietf.org; Fri, 24 Oct 2008 06:44:47 -0700
Message-Id: <4E1528CB-8D2B-4C9B-A16C-33DF6847EB71@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: SIP IETF <SIP@ietf.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 24 Oct 2008 07:52:45 -0500
X-Mailer: Apple Mail (2.929.2)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: [Sip] INFO Events Replacing or Updating INFO?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0112755120=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--===============0112755120==
Content-Type: multipart/signed; boundary=Apple-Mail-2--415053799; micalg=sha1; protocol="application/pkcs7-signature"


--Apple-Mail-2--415053799
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

You may or may not recall there was discussion in Dublin (but not on  
the list or in the minutes) about whether the new INFO Events document  
should Update or Obsolete the old INFO specification, RFC 2976.  Upon  
reflection, and what you see in the current draft, the editors went  
with Obsolete. The reasons are:

o  This mechanism substantially replaces the old mechanism; it is not  
an incremental change or correction.

o  There are already way too many documents in SIP; it would be easy  
for an implementor to not bother checking what the Update is when they  
look at RFC 2976.

o   We want the RFC 2976 mechanism to go away. Keeping RFC 2976 active  
is begging for implementors to build the wrong thing. An Update sort  
of implies "new and improved, but old is still good."  Old, in this  
case, is NOT good.


The editors made this decision and it is what the current document  
reflects.  However, we would like to make sure this represents the  
work group consensus.  Therefore, it would be helpful if you could  
chime in with your thoughts:

[ ] INFO Events should Obsolete RFC 2976
[ ] INFO Events should Update RFC 2796, because ____________
[ ] I do not care what you do


--Apple-Mail-2--415053799
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGPTCCBjkw
ggUhoAMCAQICEC+VK1RLWxrF8KJZDR9k8p8wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYTAlVT
MQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VS
VFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQD
Ey1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwwHhcNMDgwODEz
MDAwMDAwWhcNMDkwODEzMjM1OTU5WjCB4TE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsg
LSBQRVJTT05BIE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9m
IHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDMg
Q29tb2RvIExpbWl0ZWQxFDASBgNVBAMTC0VyaWMgQnVyZ2VyMSkwJwYJKoZIhvcNAQkBFhplYnVy
Z2VyQHN0YW5kYXJkc3RyYWNrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMTF
RRoA4LgOACMFph0aomRC/UpqoA5C/d6DUTOvTMrYSEqkjwnU4zxDtBcHlcB4AxKAov00MYsUvEU4
loz7BHjfDjv76AIkcwu33VYQbzGmarVnyaXsVb6f/cyRL3fPT0VOVO2tQAEEgwg//CX0jN8Kn2jH
uXD/HEvko7cmpL3Pwevf3+DwB61v7ca79PpEZfn/WhaqRKA4uVNPj/JbieeaLo2v/0RJzrEElZK0
pHCqxiD3mQ8ossPkA9fUCSxLlbdMcPU3be5x8vt8Q8mYTXF5Z3d9RZmYrmNkvTQtdzVpfYWr/hgV
Xqm9tByOOAR+hoN3FKbubR/OrAHL9yDAd4sCAwEAAaOCAhwwggIYMB8GA1UdIwQYMBaAFImCZ33E
nSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBRDWgutb7b8R/L7G3Y3D+molAA3VzAOBgNVHQ8BAf8E
BAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJ
YIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEW
HWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMIGlBgNVHR8EgZ0wgZowTKBKoEiGRmh0dHA6
Ly9jcmwuY29tb2RvY2EuY29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRF
bWFpbC5jcmwwSqBIoEaGRGh0dHA6Ly9jcmwuY29tb2RvLm5ldC9VVE4tVVNFUkZpcnN0LUNsaWVu
dEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMGwGCCsGAQUFBwEBBGAwXjA2BggrBgEFBQcwAoYq
aHR0cDovL2NydC5jb21vZG9jYS5jb20vVVROQUFBQ2xpZW50Q0EuY3J0MCQGCCsGAQUFBzABhhho
dHRwOi8vb2NzcC5jb21vZG9jYS5jb20wJQYDVR0RBB4wHIEaZWJ1cmdlckBzdGFuZGFyZHN0cmFj
ay5jb20wDQYJKoZIhvcNAQEFBQADggEBAGeBR7NPCvrY3GQoIi49JOuciatY2r4st905Jw1etp6J
umFFWlaCBl11tFSclk/3S45B+lUv3SEvG4CEjUByPScprVmCqHR+y8BAQaB/CV+N1y14x3MbhJ+Z
8XDGKeUXuuyGd9w0l3/t/QPid6TRXQjQFrLPFs1IALuNpNiFMHEF/xFbMG1Z2vznR/gSPlePekoZ
TqcExIDBNZTBebpZqwAXzPpedNNOclbMLFLWDMOAozVRpkfjI0eiFsk8SF1Ho1Gb9Bx8DeG4peE2
KRVOR9FFnZZgBpFjXYRcglsMOSKCY8HgE+NGvbbqbrMoBV/BlYyxRXwfti71RL9Zs2Cq1eQxggP8
MIID+AIBATCBwzCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExh
a2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8v
d3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkNH2TynzAJBgUrDgMCGgUAoIICDTAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wODEwMjQxMjUyNDZaMCMGCSqGSIb3
DQEJBDEWBBSgMgA9aWqAmhrSNlyu27/bnAsEnzCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD
VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU
aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2
MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv
lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN
H2TynzANBgkqhkiG9w0BAQEFAASCAQDBnpNfVUPIoWKUbaOEQ6N98IVr11XHNVXVWUp/wrUSavz6
b0nDoTCtwfbaADd0s5GppoP5A+wFliYMOHy+e2hlhL/e9mWIUGZpfBToMBQl3jOfQwX4A+MPf4un
5bNZS/m8eMWJAdbukvJlSrqBJHkKLwLWef/xZX0yK2RzHK7iej18jj7pjNNJqctG5AB4EcY1ADvm
klmZs9UiqII8PJh6h54hgLYByRQe2KJf2Sr3IjquPkLPiV6jxrGzlgxRutGAPOto+tiKE0asjDXp
2PbKFsuaLyOA9nrwRlCf0RTkEAPCt6tsViwBTjWZHnzHTduiTYGD+94tCvr6wpcF2c7NAAAAAAAA

--Apple-Mail-2--415053799--

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

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


From sip-bounces@ietf.org  Fri Oct 24 06:43:40 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4609128C17F;
	Fri, 24 Oct 2008 06:43:40 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5E90628C17F
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 06:43:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0aIdr7i7yQkq for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 06:43:37 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 9FBD928C175
	for <SIP@ietf.org>; Fri, 24 Oct 2008 06:43:37 -0700 (PDT)
Received: from cpds.rice.iit.edu ([216.47.140.112]:53254 helo=[10.10.11.148])
	by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1KtMyF-0005OQ-Si for SIP@ietf.org; Fri, 24 Oct 2008 06:44:56 -0700
Message-Id: <C9685920-CA2B-435A-9FA9-767BE5085AB6@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: SIP IETF <SIP@ietf.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 24 Oct 2008 08:44:58 -0500
X-Mailer: Apple Mail (2.929.2)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: [Sip] INFO Events Replacing or Updating INFO?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0234219863=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--===============0234219863==
Content-Type: multipart/signed; boundary=Apple-Mail-4--411920942; micalg=sha1; protocol="application/pkcs7-signature"


--Apple-Mail-4--411920942
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

You may or may not recall there was discussion in Dublin (but not on  
the list or in the minutes) about whether the new INFO Events document  
should Update or Obsolete the old INFO specification, RFC 2976.  Upon  
reflection, and what you see in the current draft, the editors went  
with Obsolete. The reasons are:

o  This mechanism substantially replaces the old mechanism; it is not  
an incremental change or correction.

o  There are already way too many documents in SIP; it would be easy  
for an implementor to not bother checking what the Update is when they  
look at RFC 2976.

o   We want the RFC 2976 mechanism to go away. Keeping RFC 2976 active  
is begging for implementors to build the wrong thing. An Update sort  
of implies "new and improved, but old is still good."  Old, in this  
case, is NOT good.


The editors made this decision and it is what the current document  
reflects.  However, we would like to make sure this represents the  
work group consensus.  Therefore, it would be helpful if you could  
chime in with your thoughts:

[ ] INFO Events should Obsolete RFC 2976
[ ] INFO Events should Update RFC 2796, because ____________
[ ] I do not care what you do


--Apple-Mail-4--411920942
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGPTCCBjkw
ggUhoAMCAQICEC+VK1RLWxrF8KJZDR9k8p8wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYTAlVT
MQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VS
VFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQD
Ey1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwwHhcNMDgwODEz
MDAwMDAwWhcNMDkwODEzMjM1OTU5WjCB4TE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsg
LSBQRVJTT05BIE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9m
IHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDMg
Q29tb2RvIExpbWl0ZWQxFDASBgNVBAMTC0VyaWMgQnVyZ2VyMSkwJwYJKoZIhvcNAQkBFhplYnVy
Z2VyQHN0YW5kYXJkc3RyYWNrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMTF
RRoA4LgOACMFph0aomRC/UpqoA5C/d6DUTOvTMrYSEqkjwnU4zxDtBcHlcB4AxKAov00MYsUvEU4
loz7BHjfDjv76AIkcwu33VYQbzGmarVnyaXsVb6f/cyRL3fPT0VOVO2tQAEEgwg//CX0jN8Kn2jH
uXD/HEvko7cmpL3Pwevf3+DwB61v7ca79PpEZfn/WhaqRKA4uVNPj/JbieeaLo2v/0RJzrEElZK0
pHCqxiD3mQ8ossPkA9fUCSxLlbdMcPU3be5x8vt8Q8mYTXF5Z3d9RZmYrmNkvTQtdzVpfYWr/hgV
Xqm9tByOOAR+hoN3FKbubR/OrAHL9yDAd4sCAwEAAaOCAhwwggIYMB8GA1UdIwQYMBaAFImCZ33E
nSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBRDWgutb7b8R/L7G3Y3D+molAA3VzAOBgNVHQ8BAf8E
BAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJ
YIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEW
HWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMIGlBgNVHR8EgZ0wgZowTKBKoEiGRmh0dHA6
Ly9jcmwuY29tb2RvY2EuY29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRF
bWFpbC5jcmwwSqBIoEaGRGh0dHA6Ly9jcmwuY29tb2RvLm5ldC9VVE4tVVNFUkZpcnN0LUNsaWVu
dEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMGwGCCsGAQUFBwEBBGAwXjA2BggrBgEFBQcwAoYq
aHR0cDovL2NydC5jb21vZG9jYS5jb20vVVROQUFBQ2xpZW50Q0EuY3J0MCQGCCsGAQUFBzABhhho
dHRwOi8vb2NzcC5jb21vZG9jYS5jb20wJQYDVR0RBB4wHIEaZWJ1cmdlckBzdGFuZGFyZHN0cmFj
ay5jb20wDQYJKoZIhvcNAQEFBQADggEBAGeBR7NPCvrY3GQoIi49JOuciatY2r4st905Jw1etp6J
umFFWlaCBl11tFSclk/3S45B+lUv3SEvG4CEjUByPScprVmCqHR+y8BAQaB/CV+N1y14x3MbhJ+Z
8XDGKeUXuuyGd9w0l3/t/QPid6TRXQjQFrLPFs1IALuNpNiFMHEF/xFbMG1Z2vznR/gSPlePekoZ
TqcExIDBNZTBebpZqwAXzPpedNNOclbMLFLWDMOAozVRpkfjI0eiFsk8SF1Ho1Gb9Bx8DeG4peE2
KRVOR9FFnZZgBpFjXYRcglsMOSKCY8HgE+NGvbbqbrMoBV/BlYyxRXwfti71RL9Zs2Cq1eQxggP8
MIID+AIBATCBwzCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExh
a2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8v
d3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkNH2TynzAJBgUrDgMCGgUAoIICDTAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wODEwMjQxMzQ0NThaMCMGCSqGSIb3
DQEJBDEWBBSgMgA9aWqAmhrSNlyu27/bnAsEnzCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD
VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU
aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2
MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv
lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN
H2TynzANBgkqhkiG9w0BAQEFAASCAQCKe9IxhA5MIJn4j2u9sekkucvdCtQDfLEIppR4goDZWI1v
vtYvcSeX6yzrSDxjqS2ciseoZHLLgQ1aR2GW4DOtwhx4gBoI2C6xlI+1x3gp1VQJPm4Ogg7Xd5ct
D35C4SkVF1ICiXWLxHm8l/K8hTvkEVcyFwBIEAiWs0Qe/Cwb0KHHrT6MLpZlh469LYb+xctRODM4
89P9edxvRyemTa+Wy4fHKqudN4QlD2vrWVJLKXCo3dnOTlCb4SHVnRavVnkPVBKBhurUq/eci64a
nlpgE5nV7s+3+Ja+VJFbVao4KZtcShon3aCJKNwDnLwIiRIwBwGu1tvlLfcIo44041qsAAAAAAAA

--Apple-Mail-4--411920942--

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

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


From sip-bounces@ietf.org  Fri Oct 24 06:56:55 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ED77B28C0F4;
	Fri, 24 Oct 2008 06:56:54 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C6DCA3A6B3F
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 06:56:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.565
X-Spam-Level: 
X-Spam-Status: No, score=-6.565 tagged_above=-999 required=5 tests=[AWL=0.034, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QEWsZHuGSNbz for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 06:56:53 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id CB26B3A6B34
	for <SIP@ietf.org>; Fri, 24 Oct 2008 06:56:52 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,477,1220227200"; d="scan'208";a="25535199"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 24 Oct 2008 13:58:14 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9ODwEN7027783; 
	Fri, 24 Oct 2008 09:58:14 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9ODwEV9014932;
	Fri, 24 Oct 2008 13:58:14 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 09:58:13 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 09:58:13 -0400
Message-ID: <4901D477.5010209@cisco.com>
Date: Fri, 24 Oct 2008 09:58:15 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Eric Burger <eburger@standardstrack.com>
References: <C9685920-CA2B-435A-9FA9-767BE5085AB6@standardstrack.com>
In-Reply-To: <C9685920-CA2B-435A-9FA9-767BE5085AB6@standardstrack.com>
X-OriginalArrivalTime: 24 Oct 2008 13:58:13.0660 (UTC)
	FILETIME=[8E81FDC0:01C935E0]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=349; t=1224856694; x=1225720694;
	c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20INFO=20Events=20Replacing=20or=
	20Updating=20INFO? |Sender:=20
	|To:=20Eric=20Burger=20<eburger@standardstrack.com>;
	bh=cO/rnDlbvkS8FhcO+PhXveeMwgJSXtWuwdBbM7lBRxU=;
	b=ph42wLCHqJUGiChfraxbtzebAIYWG3kMqNIx8YiNHnvB1yDc+5xRSf4XM/
	jJ8jca0QUIYV616eKUFwp7PriHj1vHIGn0tRnMtXAIskvNx+ognruShoPnIG
	cyzGaJ7exI;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: SIP IETF <SIP@ietf.org>
Subject: Re: [Sip] INFO Events Replacing or Updating INFO?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Eric Burger wrote:

> [X] INFO Events should Obsolete RFC 2976
> [ ] INFO Events should Update RFC 2796, because ____________
> [ ] I do not care what you do

But of course the new document must carefully define backward compatible 
behavior. Its made a stab at that, and I expect it to be complete before 
approval.

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


From sip-bounces@ietf.org  Fri Oct 24 07:03:30 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9B35928C178;
	Fri, 24 Oct 2008 07:03:30 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 51D573A6B43;
	Fri, 24 Oct 2008 07:03:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.537
X-Spam-Level: 
X-Spam-Status: No, score=-6.537 tagged_above=-999 required=5 tests=[AWL=0.062, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id oY3BUCv-2V2J; Fri, 24 Oct 2008 07:03:28 -0700 (PDT)
Received: from zcars04f.nortel.com (zcars04f.nortel.com [47.129.242.57])
	by core3.amsl.com (Postfix) with ESMTP id 203023A6B34;
	Fri, 24 Oct 2008 07:03:28 -0700 (PDT)
Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com
	[47.103.123.72])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m9OE4DU19332; Fri, 24 Oct 2008 14:04:14 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 24 Oct 2008 09:00:39 -0500
Message-ID: <F66D7286825402429571678A16C2F5EE05F40DB9@zrc2hxm1.corp.nortel.com>
In-Reply-To: <4901BB2D.3030908@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] [Sip] INVITE dialogs
Thread-Index: Ack10YOEMLDH1q1VQg2sOP7TXJJWUgADyVOg
References: <5d688850809301209r6b43aeeaqa4c9f49fa2fa1706@mail.gmail.com><48E28DA2.5060708@cisco.com>
	<200810070242.m972grm741386799@shell01.TheWorld.com>
	<547F018265F92642B577B986577D671C3E0612@VENUS.office>
	<4901BB2D.3030908@cisco.com>
From: "Mary Barnes" <mary.barnes@nortel.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>,
	"Saverio Niccolini" <Saverio.Niccolini@nw.neclab.eu>
Cc: sip@ietf.org, sipping@ietf.org, hasebe.miki@east.ntt.co.jp
Subject: Re: [Sip] [Sipping]  INVITE dialogs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I think we also need to consider that some of these may be corner cases.
The idea of the doc in SIPPING was to document the most common race
conditions and the ones that had plagued folks in the past. If we can
get feedback from folks that these other cases occur "in the wild" and
are not rare cases (and not when there's buggy SW), then it might be
quite reasonable to bring this doc back to the WG.

Regards,
Mary. 

-----Original Message-----
From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
Behalf Of Paul Kyzivat
Sent: Friday, October 24, 2008 7:10 AM
To: Saverio Niccolini
Cc: sip@ietf.org; sipping@ietf.org; hasebe.miki@east.ntt.co.jp
Subject: Re: [Sipping] [Sip] INVITE dialogs

I think it is up to the wg and the chairs whether the draft is opened up
for inclusion of more races. I haven't had time to examine Pamela's
document in detail, so I can't speak to the specific races she has found
right now. I would not be terribly surprised if there are more. But I am
surprised if there are 40 more. Perhaps many of those are variants on a
theme and might be viewed by others as some smaller number.

	Thanks,
	Paul

Saverio Niccolini wrote:
>> It would be a very interesting "live fire demonstration" of the value

>> of the formalism if it discovered race conditions that we hadn't 
>> identified by informal means.
> 
> I would not be surprise to discover that race conditions identified by

> informal means are much less than the ones identified using a 
> formalism (even if one using simplifications).
> 
> Paul was saying there is not chance to touch the 
> draft-ietf-sipping-race-examples
> 
> is there any plan to address the identified new race conditions in 
> another draft then? (Pamela was speaking of about 40 more...)
> 
> Saverio
> _______________________________________________
> Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the 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://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP Use
sip-implementors@cs.columbia.edu for questions on current sip Use
sip@ietf.org for new developments of core SIP
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 24 07:32:30 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EF4E43A6B43;
	Fri, 24 Oct 2008 07:32:29 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 96AEC3A6B2E
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 07:32:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.43
X-Spam-Level: 
X-Spam-Status: No, score=-1.43 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ZbHTSqiH0cWi for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 07:32:28 -0700 (PDT)
Received: from ds3000.pernau.at (ds3000.pernau.at [88.198.53.113])
	by core3.amsl.com (Postfix) with ESMTP id A619D3A6B43
	for <sip@ietf.org>; Fri, 24 Oct 2008 07:32:28 -0700 (PDT)
Received: from [10.10.0.51] (nat.labs.nic.at [83.136.33.3])
	by ds3000.pernau.at (Postfix) with ESMTP id 43BD01080005;
	Fri, 24 Oct 2008 16:33:49 +0200 (CEST)
Message-ID: <4901DCCB.7010607@pernau.at>
Date: Fri, 24 Oct 2008 16:33:47 +0200
From: Klaus Darilion <klaus.mailinglists@pernau.at>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Robert Sparks <rjsparks@nostrum.com>
References: <13208C5A-4105-4F77-842B-DD434EBE403A@nostrum.com>
In-Reply-To: <13208C5A-4105-4F77-842B-DD434EBE403A@nostrum.com>
Cc: "SIP@ietf.org List" <sip@ietf.org>
Subject: Re: [Sip] SIPit23 Survey Notes
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi Robert!

Robert Sparks schrieb:
> 
> 19% supported SIP over IPSec

What do you mean with "SIP over IPSec"? Every protocol runs over IPSec 
as it is transparent to the application.

> I asked where people were taking bits from messages to display as 
> caller-id.
> There were many different kinds of answers, including
>  P-Asserted-Identity if present, then From
>  From display name
>  username part of From uri
>  P-Asserted-Identity only
>  Contact uri
>  Remote IP address
>  P-Asserted-Identity, then Remote-Party-ID, then From
>  From, then Remote-Party-ID, then P-Asserted-Identity

So, if the From header is missing ???, the other headers are used?

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


From sip-bounces@ietf.org  Fri Oct 24 07:51:11 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 03AFE28C1D1;
	Fri, 24 Oct 2008 07:51:11 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9D27928C1D1
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 07:51:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id bg1r-VFHvHU3 for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 07:51:08 -0700 (PDT)
Received: from smail6.alcatel.fr (colt-na5.alcatel.fr [62.23.212.5])
	by core3.amsl.com (Postfix) with ESMTP id 86E0328C156
	for <sip@ietf.org>; Fri, 24 Oct 2008 07:51:08 -0700 (PDT)
Received: from FRVELSBHS05.ad2.ad.alcatel.com (frvelsbhs05.ad2.ad.alcatel.com
	[155.132.6.77])
	by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m9OEqSsE002497; 
	Fri, 24 Oct 2008 16:52:28 +0200
Received: from [139.54.131.75] ([139.54.131.75]) by
	FRVELSBHS05.ad2.ad.alcatel.com over TLS secured channel with
	Microsoft SMTPSVC(6.0.3790.2499); Fri, 24 Oct 2008 16:52:28 +0200
Message-ID: <4901E12B.8050109@alcatel-lucent.fr>
Date: Fri, 24 Oct 2008 16:52:27 +0200
From: Thomas Froment <Thomas.Froment@alcatel-lucent.fr>
User-Agent: Thunderbird 2.0.0.17 (X11/20080914)
MIME-Version: 1.0
To: Klaus Darilion <klaus.mailinglists@pernau.at>
References: <13208C5A-4105-4F77-842B-DD434EBE403A@nostrum.com>
	<4901DCCB.7010607@pernau.at>
In-Reply-To: <4901DCCB.7010607@pernau.at>
X-OriginalArrivalTime: 24 Oct 2008 14:52:28.0059 (UTC)
	FILETIME=[2247DEB0:01C935E8]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
Cc: "SIP@ietf.org List" <sip@ietf.org>
Subject: Re: [Sip] SIPit23 Survey Notes
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Klaus Darilion wrote:
> Hi Robert!
>
> Robert Sparks schrieb:
>>
>> 19% supported SIP over IPSec
>
> What do you mean with "SIP over IPSec"? Every protocol runs over IPSec 
> as it is transparent to the application.
Well, SIP over IPsec is not really "transparent" to the SIP implementation:
when you want to send a request over an IPSec SA, you MUST be able to 
choose what is the source interface / source port and destination 
interface / destination port. This is not something so easy to implement 
at SIP transport level.
Thomas


>
>> I asked where people were taking bits from messages to display as 
>> caller-id.
>> There were many different kinds of answers, including
>>  P-Asserted-Identity if present, then From
>>  From display name
>>  username part of From uri
>>  P-Asserted-Identity only
>>  Contact uri
>>  Remote IP address
>>  P-Asserted-Identity, then Remote-Party-ID, then From
>>  From, then Remote-Party-ID, then P-Asserted-Identity
>
> So, if the From header is missing ???, the other headers are used?
>
> thanks for the summary
> Klaus
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip

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


From sip-bounces@ietf.org  Fri Oct 24 08:50:35 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 091A828C20B;
	Fri, 24 Oct 2008 08:50:35 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E02ED28C209
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 08:50:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.43
X-Spam-Level: 
X-Spam-Status: No, score=-1.43 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id u9GwQuv8enhP for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 08:50:33 -0700 (PDT)
Received: from ds3000.pernau.at (ds3000.pernau.at [88.198.53.113])
	by core3.amsl.com (Postfix) with ESMTP id F144728C205
	for <sip@ietf.org>; Fri, 24 Oct 2008 08:50:32 -0700 (PDT)
Received: from [10.10.0.51] (nat.labs.nic.at [83.136.33.3])
	by ds3000.pernau.at (Postfix) with ESMTP id 0C8361080005;
	Fri, 24 Oct 2008 17:51:52 +0200 (CEST)
Message-ID: <4901EF16.7020703@pernau.at>
Date: Fri, 24 Oct 2008 17:51:50 +0200
From: Klaus Darilion <klaus.mailinglists@pernau.at>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Thomas Froment <Thomas.Froment@alcatel-lucent.fr>
References: <13208C5A-4105-4F77-842B-DD434EBE403A@nostrum.com>	<4901DCCB.7010607@pernau.at>
	<4901E12B.8050109@alcatel-lucent.fr>
In-Reply-To: <4901E12B.8050109@alcatel-lucent.fr>
Cc: "SIP@ietf.org List" <sip@ietf.org>
Subject: Re: [Sip] SIPit23 Survey Notes
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Thomas Froment schrieb:
> Klaus Darilion wrote:
>> Hi Robert!
>>
>> Robert Sparks schrieb:
>>>
>>> 19% supported SIP over IPSec
>>
>> What do you mean with "SIP over IPSec"? Every protocol runs over IPSec 
>> as it is transparent to the application.
> Well, SIP over IPsec is not really "transparent" to the SIP implementation:
> when you want to send a request over an IPSec SA, you MUST be able to 
> choose what is the source interface / source port and destination 
> interface / destination port. This is not something so easy to implement 
> at SIP transport level.

I still do not get it. You can use IPSec without any additional 
interfaces. If the IPSec implementation creates tunnel interfaces, that 
may cause problems to SIP client. But then the problem is due to tunnel 
interfaces (which can be anything, not only IPsec), not due to IPSec.

So if the SIP client does not care if the communication is secured with 
IPsec, then every client should work over IPsec too.

So the question is still - what means "supported SIP over IPSec"?

Does it mean, "Is the SIP client capable of retrieving IPsec information 
from the kernel to find out if a message will be sent via IPsec secured way?

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


From sip-bounces@ietf.org  Fri Oct 24 09:59:29 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 84DC63A6BE1;
	Fri, 24 Oct 2008 09:59:29 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B52E33A6B51;
	Fri, 24 Oct 2008 09:59:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.566
X-Spam-Level: 
X-Spam-Status: No, score=-6.566 tagged_above=-999 required=5 tests=[AWL=0.033, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BUo6NlMY0wUc; Fri, 24 Oct 2008 09:59:26 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 67E703A6BCD;
	Fri, 24 Oct 2008 09:59:26 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,479,1220227200"; d="scan'208";a="25589266"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 24 Oct 2008 17:00:43 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9OH0hcg031646; 
	Fri, 24 Oct 2008 13:00:43 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9OH0hvh021065;
	Fri, 24 Oct 2008 17:00:43 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 13:00:43 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 13:00:43 -0400
Message-ID: <4901FF36.1060002@cisco.com>
Date: Fri, 24 Oct 2008 13:00:38 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Mary Barnes <mary.barnes@nortel.com>
References: <5d688850809301209r6b43aeeaqa4c9f49fa2fa1706@mail.gmail.com><48E28DA2.5060708@cisco.com>
	<200810070242.m972grm741386799@shell01.TheWorld.com>
	<547F018265F92642B577B986577D671C3E0612@VENUS.office>
	<4901BB2D.3030908@cisco.com>
	<F66D7286825402429571678A16C2F5EE05F40DB9@zrc2hxm1.corp.nortel.com>
In-Reply-To: <F66D7286825402429571678A16C2F5EE05F40DB9@zrc2hxm1.corp.nortel.com>
X-OriginalArrivalTime: 24 Oct 2008 17:00:43.0240 (UTC)
	FILETIME=[0CF74E80:01C935FA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3576; t=1224867643;
	x=1225731643; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20[Sip]=20INVITE=20dialogs
	|Sender:=20 |To:=20Mary=20Barnes=20<mary.barnes@nortel.com>;
	bh=08S8KFPRnrGUMILIdKa0EbA4uxWH875OP88Gpfg4qpg=;
	b=QiMhm8kpV30K+Dk3tsdeXuEcPmzuwIM1DwpDDydGdm7TWGo+KQd8I8aKqg
	/C8raWYjfq7B46p0q3vkKXVVNUPXgFJYo+Q0DFixfRzPkfgdqZ1kWSybE3uo
	nbDKIV59mL;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: sip@ietf.org, Saverio Niccolini <Saverio.Niccolini@nw.neclab.eu>,
	hasebe.miki@east.ntt.co.jp,
	=?ISO-8859-1?Q?I=F1aki_B?=@core3.amsl.com, sipping@ietf.org
Subject: Re: [Sip] [Sipping]  INVITE dialogs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Mary,

I suppose there may be someplace to draw a line, but these race =

conditions are mostly corner cases. In my experience, any corner case =

you can find, as improbable as it might seem, will be observed in =

practice, probably much more often than you think.

If these things are real, and are not just variants of the ones we have =

already identified, and covered by them, then it *may* be worth revisiting.

I have exchanged several messages with Pamela on this, but have not =

examined her work in detail. She has made a number of simplifying =

assumptions that IMO are not realistic ones to make in practice. But I =

*think* that if she is finding races under those simplifying assumptions =

then they presumably should continue to be real under looser conditions.

But I haven't had the time to understand her formalisms to make a =

meaningful judgment on what she has found. Maybe somebody else has time?
(Perhaps someone like I=F1aki (hint hint) who seems to have an interest in =

arcane things.)

	Thanks,
	Paul

Mary Barnes wrote:
> I think we also need to consider that some of these may be corner cases.
> The idea of the doc in SIPPING was to document the most common race
> conditions and the ones that had plagued folks in the past. If we can
> get feedback from folks that these other cases occur "in the wild" and
> are not rare cases (and not when there's buggy SW), then it might be
> quite reasonable to bring this doc back to the WG.
> =

> Regards,
> Mary. =

> =

> -----Original Message-----
> From: sipping-bounces@ietf.org [mailto:sipping-bounces@ietf.org] On
> Behalf Of Paul Kyzivat
> Sent: Friday, October 24, 2008 7:10 AM
> To: Saverio Niccolini
> Cc: sip@ietf.org; sipping@ietf.org; hasebe.miki@east.ntt.co.jp
> Subject: Re: [Sipping] [Sip] INVITE dialogs
> =

> I think it is up to the wg and the chairs whether the draft is opened up
> for inclusion of more races. I haven't had time to examine Pamela's
> document in detail, so I can't speak to the specific races she has found
> right now. I would not be terribly surprised if there are more. But I am
> surprised if there are 40 more. Perhaps many of those are variants on a
> theme and might be viewed by others as some smaller number.
> =

> 	Thanks,
> 	Paul
> =

> Saverio Niccolini wrote:
>>> It would be a very interesting "live fire demonstration" of the value
> =

>>> of the formalism if it discovered race conditions that we hadn't =

>>> identified by informal means.
>> I would not be surprise to discover that race conditions identified by
> =

>> informal means are much less than the ones identified using a =

>> formalism (even if one using simplifications).
>>
>> Paul was saying there is not chance to touch the =

>> draft-ietf-sipping-race-examples
>>
>> is there any plan to address the identified new race conditions in =

>> another draft then? (Pamela was speaking of about 40 more...)
>>
>> Saverio
>> _______________________________________________
>> Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
>> This list is for NEW development of the 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://www.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP Use
> sip-implementors@cs.columbia.edu for questions on current sip Use
> sip@ietf.org for new developments of core SIP
> =

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


From sip-bounces@ietf.org  Fri Oct 24 10:32:51 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A75C03A6979;
	Fri, 24 Oct 2008 10:32:51 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 179A73A67F8
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 10:32:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.57
X-Spam-Level: 
X-Spam-Status: No, score=-3.57 tagged_above=-999 required=5 tests=[AWL=0.029, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id cEFxPZRyh6xt for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 10:32:49 -0700 (PDT)
Received: from TheWorld.com (pcls4.std.com [192.74.137.84])
	by core3.amsl.com (Postfix) with ESMTP id 2E3583A687D
	for <sip@ietf.org>; Fri, 24 Oct 2008 10:32:48 -0700 (PDT)
Received: from shell.TheWorld.com (root@shell01.TheWorld.com [192.74.137.71])
	by TheWorld.com (8.13.6/8.13.6) with ESMTP id m9OHWtrB000960
	for <sip@ietf.org>; Fri, 24 Oct 2008 13:32:57 -0400
Received: from shell01.TheWorld.com (localhost [127.0.0.1])
	by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id m9OHWsOW52914003
	for <sip@ietf.org>; Fri, 24 Oct 2008 13:32:55 -0400 (EDT)
Received: (from worley@localhost)
	by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id m9OHWs8u52941053;
	Fri, 24 Oct 2008 13:32:54 -0400 (EDT)
Date: Fri, 24 Oct 2008 13:32:54 -0400 (EDT)
Message-Id: <200810241732.m9OHWs8u52941053@shell01.TheWorld.com>
To: sip@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <4901DCCB.7010607@pernau.at> (klaus.mailinglists@pernau.at)
References: <13208C5A-4105-4F77-842B-DD434EBE403A@nostrum.com>
	<4901DCCB.7010607@pernau.at>
Subject: Re: [Sip] SIPit23 Survey Notes
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

   From: Klaus Darilion <klaus.mailinglists@pernau.at>

   >  From, then Remote-Party-ID, then P-Asserted-Identity

   So, if the From header is missing ???, the other headers are used?

Probably "If the From header is missing a display-name, the other
headers are examined."

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


From sip-bounces@ietf.org  Fri Oct 24 10:32:52 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 62CF13A6B51;
	Fri, 24 Oct 2008 10:32:52 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 35F393A67F8
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 10:32:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.572
X-Spam-Level: 
X-Spam-Status: No, score=-3.572 tagged_above=-999 required=5 tests=[AWL=0.027, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id HARbk+AWHrgu for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 10:32:49 -0700 (PDT)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146])
	by core3.amsl.com (Postfix) with ESMTP id 2E3373A682A
	for <sip@ietf.org>; Fri, 24 Oct 2008 10:32:48 -0700 (PDT)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71])
	by TheWorld.com (8.13.6/8.13.6) with ESMTP id m9OHWev1005798
	for <sip@ietf.org>; Fri, 24 Oct 2008 13:32:43 -0400
Received: from shell01.TheWorld.com (localhost [127.0.0.1])
	by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id m9OHWeEb52996313
	for <sip@ietf.org>; Fri, 24 Oct 2008 13:32:40 -0400 (EDT)
Received: (from worley@localhost)
	by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id m9OHWbxv52636270;
	Fri, 24 Oct 2008 13:32:37 -0400 (EDT)
Date: Fri, 24 Oct 2008 13:32:37 -0400 (EDT)
Message-Id: <200810241732.m9OHWbxv52636270@shell01.TheWorld.com>
To: sip@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <48FDEB20.9040109@cisco.com> (pkyzivat@cisco.com)
References: <48FDEB20.9040109@cisco.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: CANCEL???
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

   From: Paul Kyzivat <pkyzivat@cisco.com>

   I have a question regarding the following paragraph:

       A UAC MAY CANCEL an INFO request.  A UAS receiving a CANCEL for an
       INFO request SHOULD respond to the INFO with a "487 Request
       Cancelled" response unless the UAC has already sent a final response.
       The UAS then MUST ignore future INFO requests.

   Why would the CANCEL affect *future* info requests???

I'm sure we *don't* want CANCEL to affect future INFO requests.  That
adds another bit of state that has to be remembered, and I'm sure it
will cause some weird complications.  (Among other things, what is it
to "ignore" an INFO request?  What response code is that?)

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


From sip-bounces@ietf.org  Fri Oct 24 12:41:11 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7892228C0E7;
	Fri, 24 Oct 2008 12:41:11 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0C9C73A6A49
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 12:41:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.299
X-Spam-Level: 
X-Spam-Status: No, score=-0.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MANGLED_SAVELE=2.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vp35dkF-yDLL for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 12:41:09 -0700 (PDT)
Received: from mail-gx0-f16.google.com (mail-gx0-f16.google.com
	[209.85.217.16])
	by core3.amsl.com (Postfix) with ESMTP id B3AC43A6938
	for <sip@ietf.org>; Fri, 24 Oct 2008 12:41:08 -0700 (PDT)
Received: by gxk9 with SMTP id 9so116932gxk.13
	for <sip@ietf.org>; Fri, 24 Oct 2008 12:42:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:in-reply-to:references
	:mime-version:content-type:message-id:cc:content-transfer-encoding
	:from:subject:date:to:x-mailer;
	bh=cK33sR8Xz5s7CmjFsATwmZd/aUUAXu+knPkqQnHBL/8=;
	b=tpkyGhzx9jnaiy7dq8hTTV73ykY3xL2QXiub/6TI9Kl77nuwhn/a8i8nT5uHBefpzi
	97XnxD8566qfARwrvwLdNeh3y6D7qrS+Ox8mlNLQ1vmMoRTpu/BZZY0M6RqIIU2S9RDi
	sHwqP/4L2aJOP2+DZZ6z56GmvuN9bCUw8W6xc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=in-reply-to:references:mime-version:content-type:message-id:cc
	:content-transfer-encoding:from:subject:date:to:x-mailer;
	b=aVw07B5a4iLLO83nppV7hk42Rrp3aep7LKKPhiUZpJVtCEDhBBWSe3jU5Yrc3oVQng
	8mQlsXXaRQzPymiWIXpVWCYzDVkOMV6unwJm5beMvLNnMPYkt4LiUDKg+ZPTBwjhRzqj
	a9ANxgQSP14Egc94wF5ACvVsowPFyBES9x2p4=
Received: by 10.100.105.15 with SMTP id d15mr3276741anc.31.1224877347302;
	Fri, 24 Oct 2008 12:42:27 -0700 (PDT)
Received: from ?135.207.21.114? (H-135-207-21-114.research.att.com
	[135.207.21.114])
	by mx.google.com with ESMTPS id c37sm1673074ana.11.2008.10.24.12.42.25
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Fri, 24 Oct 2008 12:42:26 -0700 (PDT)
In-Reply-To: <490206BD.8020701@cisco.com>
References: <47FFBA6A-AFE9-4894-9DF7-01F1557324FC@gmail.com>
	<490206BD.8020701@cisco.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <92A1F222-80D6-4534-A604-C898F1DEE3F3@gmail.com>
From: Pamela Zave <pamelazave@gmail.com>
Date: Fri, 24 Oct 2008 15:27:18 -0400
To: Paul Kyzivat <pkyzivat@cisco.com>
X-Mailer: Apple Mail (2.753.1)
Cc: sip@ietf.org, sipping@ietf.org
Subject: Re: [Sip] [Sipping] INVITE dialogs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

The count of new races is rather arbitrary, of course, but some are  
serious ones requiring significant programming effort to work  
around.  As Paul says, removing my simplifying assumptions can only  
make the problem worse, not better.

I realize that it is not easy for someone new to delve into the model  
quickly.  I propose to extract a few cases that I find interesting,  
check them with experts for validity to avoid wasting everyone's  
time,  and post a readable summary.  Then everyone should be able to  
assess the substance.

I am about to leave for a week of vacation, so ETA is the first week  
of November.

I hope this is helpful.
Cheers,
Pamela


On Oct 24, 2008, at 1:32 PM, Paul Kyzivat wrote:

> Pamela,
>
> Will you perchance be attending IETF73 in Minneapolis this Nov?
>
> There is some interest in having you talk about the race conditions  
> you say you have found.
>
> 	Thanks,
> 	Paul
>
> Pamela Zave wrote:
>> At the suggestion of Paul Kyzivat and Dale Worley, I compared
>> draft-ietf-sipping-race-examples-06.txt
>> to the basic Spin model of INVITE dialogs at
>> http://www.research.att.com/~pamela/sip.html.
>> Of the 13 race conditions in the sipping draft, 6 of them are out  
>> of the scope of the Spin model.  Most commonly, this is because  
>> they include retransmission of a lost message.  There are no  
>> transmission failures in the Spin model.
>> Of the remaining 7, all of them are in the Spin model, handled the  
>> same way.
>> In addition, the Spin model shows 42 additional race conditions.   
>> This count is subject to a lot of interpretation, so I estimate a  
>> possible error of about 20%.
>> Pamela Zave
>> _______________________________________________
>> Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
>> This list is for NEW development of the application of SIP
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sip@ietf.org for new developments of core SIP

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


From sip-bounces@ietf.org  Fri Oct 24 13:24:04 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E85873A67AD;
	Fri, 24 Oct 2008 13:24:03 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A05ED3A67AD
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 13:24:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.647
X-Spam-Level: 
X-Spam-Status: No, score=-2.647 tagged_above=-999 required=5
	tests=[AWL=-0.047, BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id W0hlxQHKiyBO for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 13:24:02 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net
	[IPv6:2001:470:1f03:267::2])
	by core3.amsl.com (Postfix) with ESMTP id 4992C3A6783
	for <sip@ietf.org>; Fri, 24 Oct 2008 13:24:01 -0700 (PDT)
Received: from dn3-232.estacado.net (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.14.3/8.14.1) with ESMTP id m9OKPLva096577
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Fri, 24 Oct 2008 15:25:22 -0500 (CDT)
	(envelope-from rjsparks@nostrum.com)
Message-Id: <680687F5-C601-4FF7-BE5B-D09F93C2E69C@nostrum.com>
From: Robert Sparks <rjsparks@nostrum.com>
To: Klaus Darilion <klaus.mailinglists@pernau.at>
In-Reply-To: <4901DCCB.7010607@pernau.at>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 24 Oct 2008 15:25:21 -0500
References: <13208C5A-4105-4F77-842B-DD434EBE403A@nostrum.com>
	<4901DCCB.7010607@pernau.at>
X-Mailer: Apple Mail (2.929.2)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Virus-Scanned: ClamAV 0.94/8485/Fri Oct 24 08:38:51 2008 on
	shaman.nostrum.com
X-Virus-Status: Clean
Cc: "SIP@ietf.org List" <sip@ietf.org>
Subject: Re: [Sip] SIPit23 Survey Notes
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 24, 2008, at 9:33 AM, Klaus Darilion wrote:

> Hi Robert!
>
> Robert Sparks schrieb:
>> 19% supported SIP over IPSec
>
> What do you mean with "SIP over IPSec"? Every protocol runs over  
> IPSec as it is transparent to the application.
Thomas answered this already.
>
>
>> I asked where people were taking bits from messages to display as  
>> caller-id.
>> There were many different kinds of answers, including
>> P-Asserted-Identity if present, then From
>> From display name
>> username part of From uri
>> P-Asserted-Identity only
>> Contact uri
>> Remote IP address
>> P-Asserted-Identity, then Remote-Party-ID, then From
>> From, then Remote-Party-ID, then P-Asserted-Identity
>
> So, if the From header is missing ???, the other headers are used?
Yeah - each row represented an ordered set - if the first thing in the  
row was present, it was used, otherwise, the next thing was looked  
for, and so on...
>
>
> thanks for the summary
> Klaus

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


From sip-bounces@ietf.org  Fri Oct 24 13:24:25 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6B8DD28C11C;
	Fri, 24 Oct 2008 13:24:25 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A122C3A68E4;
	Fri, 24 Oct 2008 13:24:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.417
X-Spam-Level: 
X-Spam-Status: No, score=-5.417 tagged_above=-999 required=5
	tests=[AWL=-1.118, BAYES_00=-2.599, MANGLED_SAVELE=2.3,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0Q5mhejCSyEs; Fri, 24 Oct 2008 13:24:22 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 374C53A6841;
	Fri, 24 Oct 2008 13:24:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,480,1220227200"; d="scan'208";a="25616524"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 24 Oct 2008 20:25:44 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9OKPivj022685; 
	Fri, 24 Oct 2008 16:25:44 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9OKPipn004176;
	Fri, 24 Oct 2008 20:25:44 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 16:25:44 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 16:25:43 -0400
Message-ID: <49022F47.4060707@cisco.com>
Date: Fri, 24 Oct 2008 16:25:43 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Pamela Zave <pamelazave@gmail.com>
References: <47FFBA6A-AFE9-4894-9DF7-01F1557324FC@gmail.com>
	<490206BD.8020701@cisco.com>
	<92A1F222-80D6-4534-A604-C898F1DEE3F3@gmail.com>
In-Reply-To: <92A1F222-80D6-4534-A604-C898F1DEE3F3@gmail.com>
X-OriginalArrivalTime: 24 Oct 2008 20:25:43.0840 (UTC)
	FILETIME=[B0B1EA00:01C93616]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2167; t=1224879944;
	x=1225743944; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sipping]=20INVITE=20dialogs |Sender:=20
	|To:=20Pamela=20Zave=20<pamelazave@gmail.com>;
	bh=Bfw7lWWiCFGU8T7G5YzwpJKn1iSvlQ029M4ScUaVHK4=;
	b=MTNdMskcn3B4BHaKlVHzX2VXU9JKOkb9Re8ICII7Xlt2sjt7qt83M3D8TE
	kR0OJH0BH6e7qad3lfsH/4sRKnGdgsB4th/6nlg5WA810WG+tGZ3kRbggI1a
	G0tvknvaOM;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: sip@ietf.org, sipping@ietf.org
Subject: Re: [Sip] [Sipping] INVITE dialogs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Pamela Zave wrote:
> The count of new races is rather arbitrary, of course, but some are 
> serious ones requiring significant programming effort to work around.  
> As Paul says, removing my simplifying assumptions can only make the 
> problem worse, not better.
> 
> I realize that it is not easy for someone new to delve into the model 
> quickly.  I propose to extract a few cases that I find interesting, 
> check them with experts for validity to avoid wasting everyone's time,  
> and post a readable summary.  Then everyone should be able to assess the 
> substance.

I like that idea a lot!

	Thanks,
	Paul

> I am about to leave for a week of vacation, so ETA is the first week of 
> November.
> 
> I hope this is helpful.
> Cheers,
> Pamela
> 
> 
> On Oct 24, 2008, at 1:32 PM, Paul Kyzivat wrote:
> 
>> Pamela,
>>
>> Will you perchance be attending IETF73 in Minneapolis this Nov?
>>
>> There is some interest in having you talk about the race conditions 
>> you say you have found.
>>
>>     Thanks,
>>     Paul
>>
>> Pamela Zave wrote:
>>> At the suggestion of Paul Kyzivat and Dale Worley, I compared
>>> draft-ietf-sipping-race-examples-06.txt
>>> to the basic Spin model of INVITE dialogs at
>>> http://www.research.att.com/~pamela/sip.html.
>>> Of the 13 race conditions in the sipping draft, 6 of them are out of 
>>> the scope of the Spin model.  Most commonly, this is because they 
>>> include retransmission of a lost message.  There are no transmission 
>>> failures in the Spin model.
>>> Of the remaining 7, all of them are in the Spin model, handled the 
>>> same way.
>>> In addition, the Spin model shows 42 additional race conditions.  
>>> This count is subject to a lot of interpretation, so I estimate a 
>>> possible error of about 20%.
>>> Pamela Zave
>>> _______________________________________________
>>> Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
>>> This list is for NEW development of the application of SIP
>>> Use sip-implementors@cs.columbia.edu for questions on current sip
>>> Use sip@ietf.org for new developments of core SIP
> 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 24 13:33:07 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A06053A6783;
	Fri, 24 Oct 2008 13:33:07 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5C3DE3A6783
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 13:33:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.644
X-Spam-Level: 
X-Spam-Status: No, score=-2.644 tagged_above=-999 required=5
	tests=[AWL=-0.044, BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id kr-6QvWnlvfg for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 13:33:05 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net
	[IPv6:2001:470:1f03:267::2])
	by core3.amsl.com (Postfix) with ESMTP id D2B0B3A677D
	for <sip@ietf.org>; Fri, 24 Oct 2008 13:33:04 -0700 (PDT)
Received: from dn3-232.estacado.net (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.14.3/8.14.1) with ESMTP id m9OKYKdL097210
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Fri, 24 Oct 2008 15:34:21 -0500 (CDT)
	(envelope-from rjsparks@nostrum.com)
Message-Id: <F0A08997-9FD8-4EAB-AFAE-CF1099E2A2A1@nostrum.com>
From: Robert Sparks <rjsparks@nostrum.com>
To: Klaus Darilion <klaus.mailinglists@pernau.at>
In-Reply-To: <4901EF16.7020703@pernau.at>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 24 Oct 2008 15:34:20 -0500
References: <13208C5A-4105-4F77-842B-DD434EBE403A@nostrum.com>	<4901DCCB.7010607@pernau.at>
	<4901E12B.8050109@alcatel-lucent.fr> <4901EF16.7020703@pernau.at>
X-Mailer: Apple Mail (2.929.2)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Virus-Scanned: ClamAV 0.94/8485/Fri Oct 24 08:38:51 2008 on
	shaman.nostrum.com
X-Virus-Status: Clean
Cc: "SIP@ietf.org List" <sip@ietf.org>
Subject: Re: [Sip] SIPit23 Survey Notes
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi Klaus -

The number represents endpoints that could actually emit a SIP message  
over IPSec at the event, not just ones that would work if IPSec  
happened to be the part of the transport. Its a measure of what the  
available implementations can be configured to do.

What it doesn't capture is the tight-coupling w/ the IPSec  
implementation that's required to support, for instance, Digest-AKA as  
used in IMS. I don't have that statistic from this event, but based on  
conversations and observations at past events, the number would be non- 
zero but small.

RjS


On Oct 24, 2008, at 10:51 AM, Klaus Darilion wrote:

>
>
> Thomas Froment schrieb:
>> Klaus Darilion wrote:
>>> Hi Robert!
>>>
>>> Robert Sparks schrieb:
>>>>
>>>> 19% supported SIP over IPSec
>>>
>>> What do you mean with "SIP over IPSec"? Every protocol runs over  
>>> IPSec as it is transparent to the application.
>> Well, SIP over IPsec is not really "transparent" to the SIP  
>> implementation:
>> when you want to send a request over an IPSec SA, you MUST be able  
>> to choose what is the source interface / source port and  
>> destination interface / destination port. This is not something so  
>> easy to implement at SIP transport level.
>
> I still do not get it. You can use IPSec without any additional  
> interfaces. If the IPSec implementation creates tunnel interfaces,  
> that may cause problems to SIP client. But then the problem is due  
> to tunnel interfaces (which can be anything, not only IPsec), not  
> due to IPSec.
>
> So if the SIP client does not care if the communication is secured  
> with IPsec, then every client should work over IPsec too.
>
> So the question is still - what means "supported SIP over IPSec"?
>
> Does it mean, "Is the SIP client capable of retrieving IPsec  
> information from the kernel to find out if a message will be sent  
> via IPsec secured way?
>
> regards
> klaus
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip

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


From sip-bounces@ietf.org  Fri Oct 24 13:52:03 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B0D883A69B4;
	Fri, 24 Oct 2008 13:52:03 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EA2CE3A69B4
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 13:52:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.214
X-Spam-Level: 
X-Spam-Status: No, score=-6.214 tagged_above=-999 required=5 tests=[AWL=0.035, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id al7NG+wpqzjG for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 13:52:01 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id E64983A6856
	for <sip@ietf.org>; Fri, 24 Oct 2008 13:52:00 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	7CA4920434; Fri, 24 Oct 2008 22:53:22 +0200 (CEST)
X-AuditID: c1b4fb3e-af787bb00000537b-50-490235c267ee
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	608A520314; Fri, 24 Oct 2008 22:53:22 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 22:53:21 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 24 Oct 2008 22:53:21 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
Thread-Index: Ack13gE4ueu/SFwNTx+Fl9RrHZD3LwAO6D8+
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>
	<4901BA73.1010700@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>
	<4901C2B1.1050209@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>
	<4901D025.6060302@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 24 Oct 2008 20:53:21.0877 (UTC)
	FILETIME=[8CF64850:01C9361A]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi,
 
(Combining e-mails again)
   

Paul:
====

>>>For SDP, you find the part by looking for the one with
>>>Content-Disposition:session. If there is a part with no C-D
>>>header then one with a C-T of application/sdp defaults to
>>>"session". So its all about C-D.
>>
>>The C-D header gives you information about the body, yes, but I don't
>>think it helps you to FIND the body.
>>
>>That's what the SIP and MIME ABNFs are for.
>>
>Oh, sorry. I didn't really mean "find". I meant "choose the appropriate body part".

 
>>For SDP, you find the part by looking for the one with
>>Content-Disposition:session. If there is a part with no C-D header then
>>one with a C-T of application/sdp defaults to "session". So its all
>>about C-D.
> 
>Oops, I just realized I didn't state this the way I meant...
>
>For *offers and answers* you find the part by looking for the one with
>Content-Disposition:session. If there is a part with no C-D header then
>one with a C-T of application/sdp defaults to "session". So its all
>about C-D. (In theory, application/sdp is just one of the C-Ts that
>might be used to encode offers and answers.)
 
I am not sure what you mean by "body part". Is this a problem if we only allow a single info-package per message?
 
Regards,
 
Christer
 



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


From sip-bounces@ietf.org  Fri Oct 24 14:09:13 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A4B8C3A6841;
	Fri, 24 Oct 2008 14:09:13 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 99DF33A6841
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 14:09:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.554
X-Spam-Level: 
X-Spam-Status: No, score=-6.554 tagged_above=-999 required=5 tests=[AWL=0.045, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id DhGMv8jA2Ex5 for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 14:09:11 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 83A233A677D
	for <sip@ietf.org>; Fri, 24 Oct 2008 14:09:11 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,480,1220227200"; d="scan'208";a="25589008"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 24 Oct 2008 21:10:33 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9OLAXVf016190; 
	Fri, 24 Oct 2008 17:10:33 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9OLAXSx019602;
	Fri, 24 Oct 2008 21:10:33 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 17:10:33 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 17:10:32 -0400
Message-ID: <490239C8.3020808@cisco.com>
Date: Fri, 24 Oct 2008 17:10:32 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>
	<4901BA73.1010700@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>
	<4901C2B1.1050209@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>
	<4901D025.6060302@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 24 Oct 2008 21:10:32.0989 (UTC)
	FILETIME=[F38D7CD0:01C9361C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1232; t=1224882633;
	x=1225746633; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20Content-Type=20vs=20Info-Package=0A=20[was=20RE=3A=20dra
	ft-ietf-sip-info-events-00=3A=20multiple=20packages=20per=20
	INFO] |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=VtKWsrdqKyvU0NHDVJDGb9hKC8zIhE2hIdb9AcNy+yo=;
	b=E09xj4uNGoYwrVYaKFeOBRjBeawVbuTlW9h9kXD99Y97Th9/qi83K7pcnh
	dumH7QeJ4BOh4+26qmZX6is90MPvdWuTOjEoDL3ld7AHiJHT3OqpjlCNZbLr
	9AVuJ4Akh0;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
 Info-Package [was RE: draft-ietf-sip-info-events-00: multiple packages per
 INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Christer Holmberg wrote:

>> For *offers and answers* you find the part by looking for the one with
>> Content-Disposition:session. If there is a part with no C-D header then
>> one with a C-T of application/sdp defaults to "session". So its all
>> about C-D. (In theory, application/sdp is just one of the C-Ts that
>> might be used to encode offers and answers.)
>  
> I am not sure what you mean by "body part". Is this a problem if we only allow a single info-package per message?

I mean, even with INFO the body may contain more than the info package, 
or it may contain something that is not the info package and contain 
*no* info package. For instance, it might contain a body that is 
referenced via a CID: URI in some header in the message, that serves 
some incidental purpose.

The body could be a multipart/mixed, and one part could contain the info 
package, and some other part could contain the info package.

Thinking that the body must contain only the info package is failing to 
remember the lessons we have already learned with INVITE and other messages.

So no, this has nothing to do with multiple info packages per message. I 
have stopped talking about that.

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


From sip-bounces@ietf.org  Fri Oct 24 14:26:39 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 20BEA28C0D6;
	Fri, 24 Oct 2008 14:26:39 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B26223A67D2
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 14:26:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id B8mtPrW5Mo3z for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 14:26:37 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id DAF293A677C
	for <sip@ietf.org>; Fri, 24 Oct 2008 14:26:36 -0700 (PDT)
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9OLQiVP017276
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 24 Oct 2008 16:26:46 -0500
Message-Id: <01D9D13D-F6EE-43E8-8EC9-38801D0B5B8F@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
In-Reply-To: <490148E9.6070300@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 24 Oct 2008 16:26:39 -0500
References: <48FDEAD8.8010803@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com>
	A	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>	<0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>	<CA9998CD4A020D418654FCDEF4E707DF088F17D5@esealmw113.eemea.ericsson.se>	<5D1A7985295922448D5550C94DE2918002425C2C@DEEXC1U01.de.lucent.com>	<CA9998CD4A020D418654FCDEF4E707DF088F19BA@esealmw113.eemea.ericsson.se>	<5D1A7985295922448D5550C94DE2918002425C50@DEEXC1U01.de.lucent.com>	<A11BA33F-6F5B-425A-9D76-17C5894A86C9@softarmor.com>	<49008B56.2010900@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF9D@esealmw113.eemea.ericsson.se>
	<357F6D04-0BAE-47C1-8BAB-5E0FE4DA76B7@softarmor.com>
	<490148E9.6070300@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>, "Elwell, John" <john.elwell@siemens.com>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>, Eric Burger <eburger@bea.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


One might renegotiate on a re-INVITE, or on any transaction. I believe  
Christer was proposing the latter. I think restricting INFO package  
negotiation to dialog-forming and dialog-reforming transactions is  
reasonable.

--
Dean


On Oct 23, 2008, at 11:02 PM, Paul Kyzivat wrote:

> Dean,
>
> I'm now confused on what you are advocating.
>
> As its currently written, you can negotiate which packages you want  
> to use. The later in the call you can renegotiate to use different  
> ones. That seems consistent with what you are saying. So what is the  
> issue?
>
> 	Thanks,
> 	Paul
>
> Dean Willis wrote:
>> On Oct 23, 2008, at 1:00 PM, Christer Holmberg wrote:
>>> Hi,
>>>
>>> Not only 3pcc, I think it could be useful to re-negotiate the  
>>> packages during the session. For example, I may want DTMFs only  
>>> during a certain period of the call, so for the rest of the call  
>>> you would not be able to generate INFOs by pressing digit buttons.
>>>
>>> Also, we may enable some application during the call, so the UAs  
>>> need to re-negotiate the packages. For example, I may tell you  
>>> that I have a vcard which I want to send you, but we may not have  
>>> negotiated that "by defualt" when the call was established.
>>>
>> then re-INVITE.
>> -- 
>> Dean
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sipping@ietf.org for new developments on the application of sip
>

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


From sip-bounces@ietf.org  Fri Oct 24 14:27:01 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BBF3D28C15C;
	Fri, 24 Oct 2008 14:27:01 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A345228C157
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 14:27:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id JLpVrdPcCRQA for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 14:27:00 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id D027B28C154
	for <sip@ietf.org>; Fri, 24 Oct 2008 14:26:59 -0700 (PDT)
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9OLS8c2017280
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 24 Oct 2008 16:28:10 -0500
Message-Id: <07AD9FC7-C9D2-4229-B364-BD051728BF37@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 24 Oct 2008 16:28:03 -0500
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 24, 2008, at 1:21 AM, Christer Holmberg wrote:
>
> [Christer] I agree that a package could be associated with a number of
> content types. But, since the Info-Package header shows which  
> package is
> included, I just wonder why we can't use a common C-T mime.
>

Then which of the multiple bodies, each of which carries the same C-T  
mime marking, is which? Are you relying on ordering?

--
Dean

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


From sip-bounces@ietf.org  Fri Oct 24 14:29:08 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7A10828C154;
	Fri, 24 Oct 2008 14:29:08 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 18DEB28C154
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 14:29:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.215
X-Spam-Level: 
X-Spam-Status: No, score=-6.215 tagged_above=-999 required=5 tests=[AWL=0.034, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vR-fSIlp+kSD for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 14:29:06 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 2B0FE28C144
	for <sip@ietf.org>; Fri, 24 Oct 2008 14:29:06 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	15AEE20675; Fri, 24 Oct 2008 23:29:01 +0200 (CEST)
X-AuditID: c1b4fb3e-ae785bb00000537b-d2-49023e1c3fee
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	ED46D20176; Fri, 24 Oct 2008 23:29:00 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 23:29:00 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 24 Oct 2008 23:24:43 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
Thread-Index: Ack2HPUcDq4eCZBxTISf9flU990NrgAAfl+W
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>
	<4901BA73.1010700@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>
	<4901C2B1.1050209@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>
	<4901D025.6060302@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>
	<490239C8.3020808@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 24 Oct 2008 21:29:00.0285 (UTC)
	FILETIME=[878D72D0:01C9361F]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 
Hi,

>>> For *offers and answers* you find the part by looking for the one with
>>> Content-Disposition:session. If there is a part with no C-D header then
>>> one with a C-T of application/sdp defaults to "session". So its all
>>> about C-D. (In theory, application/sdp is just one of the C-Ts that
>>> might be used to encode offers and answers.)
>> 
>> I am not sure what you mean by "body part". Is this a problem if we only allow a single info-package per message?
>
>I mean, even with INFO the body may contain more than the info package,
>or it may contain something that is not the info package and contain
>*no* info package. For instance, it might contain a body that is
>referenced via a CID: URI in some header in the message, that serves
>some incidental purpose.
>
>The body could be a multipart/mixed, and one part could contain the info
>package, and some other part could contain the info package.
>
>Thinking that the body must contain only the info package is failing to
>remember the lessons we have already learned with INVITE and other messages.
>
>So no, this has nothing to do with multiple info packages per message. I
>have stopped talking about that.

So, just to make sure I understand: you are talking about a case where the INFO does contain a multipart message body, but only one of the mimes contains an actual info-package (the other mime(s) contains something else)?
 
Example:
 
Content-Type:multipart/mixed
Info-Package: foo
 
--boundary
 
foo data
 
--boundary
 
some other (non-info package) data
 
--boundary--
 
 
Regards,
 
Christer
 
 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 24 14:31:36 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3EAAA28C144;
	Fri, 24 Oct 2008 14:31:36 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 93F733A6856
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 14:31:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id baqnZGDPwwnS for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 14:31:34 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id BC84C3A67EF
	for <sip@ietf.org>; Fri, 24 Oct 2008 14:31:34 -0700 (PDT)
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9OLWpbe017347
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 24 Oct 2008 16:32:53 -0500
Message-Id: <86A1F277-3D1B-4CA4-9672-4092A51BCDCC@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Thomas Froment <Thomas.Froment@alcatel-lucent.fr>
In-Reply-To: <4901E12B.8050109@alcatel-lucent.fr>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 24 Oct 2008 16:32:45 -0500
References: <13208C5A-4105-4F77-842B-DD434EBE403A@nostrum.com>
	<4901DCCB.7010607@pernau.at> <4901E12B.8050109@alcatel-lucent.fr>
X-Mailer: Apple Mail (2.929.2)
Cc: "SIP@ietf.org List" <sip@ietf.org>,
	Klaus Darilion <klaus.mailinglists@pernau.at>
Subject: Re: [Sip] SIPit23 Survey Notes
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 24, 2008, at 9:52 AM, Thomas Froment wrote:

> Klaus Darilion wrote:
>> Hi Robert!
>>
>> Robert Sparks schrieb:
>>>
>>> 19% supported SIP over IPSec
>>
>> What do you mean with "SIP over IPSec"? Every protocol runs over  
>> IPSec as it is transparent to the application.
> Well, SIP over IPsec is not really "transparent" to the SIP  
> implementation:
> when you want to send a request over an IPSec SA, you MUST be able  
> to choose what is the source interface / source port and destination  
> interface / destination port. This is not something so easy to  
> implement at SIP transport level.

That depends. For example, if you're running SIP over tunnel-mode  
IPSec, there is no impact at all to SIP.

So clearly, you mean something else by "SIP over IPSec". What do you  
mean? Is this something that we need an RFC to define so that we can  
say "RFC XXXX" instead of "SIP over IPSec"?

--
Dean

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


From sip-bounces@ietf.org  Fri Oct 24 14:32:50 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 110363A6856;
	Fri, 24 Oct 2008 14:32:50 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E37EF28C14F
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 14:32:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.215
X-Spam-Level: 
X-Spam-Status: No, score=-6.215 tagged_above=-999 required=5 tests=[AWL=0.034, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AZFUg6kAeVvn for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 14:32:48 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 2F2593A677C
	for <sip@ietf.org>; Fri, 24 Oct 2008 14:32:48 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	9D15D20685; Fri, 24 Oct 2008 23:34:09 +0200 (CEST)
X-AuditID: c1b4fb3c-ae0cebb0000015b5-95-49023f519ba2
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	7E06B2004B; Fri, 24 Oct 2008 23:34:09 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 23:34:08 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 24 Oct 2008 23:32:42 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCFB6@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
Thread-Index: Ack2H2785r6pG1KYTS6lbE+cxqu6nwAAJ0ns
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>
	<07AD9FC7-C9D2-4229-B364-BD051728BF37@softarmor.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 24 Oct 2008 21:34:08.0970 (UTC)
	FILETIME=[3F8B0AA0:01C93620]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi,
 
>> [Christer] I agree that a package could be associated with a number of
>> content types. But, since the Info-Package header shows which 
>> package is included, I just wonder why we can't use a common C-T mime.
>>
>
>Then which of the multiple bodies, each of which carries the same C-T 
>mime marking, is which? Are you relying on ordering?

Let's assume BOTH bodies contain C-T: image/jpeg. How do you know which is associated with the info package?
 
Regards,
 
Christer


 

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


From sip-bounces@ietf.org  Fri Oct 24 14:35:17 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BEF0C28C173;
	Fri, 24 Oct 2008 14:35:17 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D392528C14F
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 14:35:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 15j7plS+QLst for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 14:35:16 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 0DEAA28C155
	for <sip@ietf.org>; Fri, 24 Oct 2008 14:35:15 -0700 (PDT)
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9OLaYbH017365
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 24 Oct 2008 16:36:35 -0500
Message-Id: <5736B897-8C58-4923-AB2B-8AE1BA9B2747@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF083CCFB6@esealmw113.eemea.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 24 Oct 2008 16:36:28 -0500
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>
	<07AD9FC7-C9D2-4229-B364-BD051728BF37@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFB6@esealmw113.eemea.ericsson.se>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 24, 2008, at 4:32 PM, Christer Holmberg wrote:

> Hi,
>
>>> [Christer] I agree that a package could be associated with a  
>>> number of
>>> content types. But, since the Info-Package header shows which
>>> package is included, I just wonder why we can't use a common C-T  
>>> mime.
>>>
>>
>> Then which of the multiple bodies, each of which carries the same C-T
>> mime marking, is which? Are you relying on ordering?
>
> Let's assume BOTH bodies contain C-T: image/jpeg. How do you know  
> which is associated with the info package?
>

So you have a multipart body, with one or more parts related to an  
INFO package, and other parts related to something else, such as AIB,  
E2M, etc. Right?

The content-disposition of the body parts related to INFO packages  
needs to differentiate them from the other body parts.

--
Dean

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


From sip-bounces@ietf.org  Fri Oct 24 14:39:28 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 853163A6A15;
	Fri, 24 Oct 2008 14:39:28 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 35C693A677C
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 14:39:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AHytquR8L-ZY for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 14:39:26 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 564F628C14F
	for <sip@ietf.org>; Fri, 24 Oct 2008 14:39:26 -0700 (PDT)
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9OLelSc017431
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT)
	for <sip@ietf.org>; Fri, 24 Oct 2008 16:40:48 -0500
Message-Id: <41397D90-A4BD-4AC0-8598-3B10783612C4@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: SIP IETF <sip@ietf.org>
In-Reply-To: <1A80883E-AB46-4776-92C0-798C7E662D21@softarmor.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 24 Oct 2008 16:40:41 -0500
References: <20081016203334.229803A68EC@core3.amsl.com>
	<1A80883E-AB46-4776-92C0-798C7E662D21@softarmor.com>
X-Mailer: Apple Mail (2.929.2)
Subject: [Sip] Does SIP want to participate in the Interim Meeting
	Opportunity in January 2009
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

IETF is hosting a large-scale interim meeting in Malta, Jan 22-22 2009.

Do we want to have an interim meeting? The AD's assumption is "yes",  
so please reply if you think otherwise.

--
Dean

Begin forwarded message:

> From: IETF Chair <chair@ietf.org>
> Date: October 16, 2008 3:33:34 PM CDT
> To: Working Group Chairs <wgchairs@ietf.org>
> Cc: chair@ietf.org
> Subject: WG Interim Meeting Opportunity in January 2009
>
> In our continuing effort to ensure that IETF WGs are getting enough
> meeting time to progress their work, we are conducting another  
> experiment.
> Many WGs have found interim meetings an effective way to tackle thorny
> technical issues, resolve contentious technical issues, accelerate
> standards development, and provide traction for new work.  As  
> always, an
> interim WG meeting is not a substitute for a regular session at the
> traditional IETF meeting.  Since some WG Chairs and ADs have found the
> amount of time necessary to put together an interim meeting can be
> excessive, we are trying to reduce the effort necessary to conduct an
> interim meeting to determine whether reducing this burden will  
> expedite
> IETF standards development.  To this end, the Secretariat will  
> facilitate
> a large interim meeting from 20-22 January 2009 in Malta.  If you are
> interested in participating in this experiment, please contact your  
> Area
> Director for approval.  All face-to-face interim meetings require AD
> approval, and this is no exception.  The IETF Secretariat is putting
> together a program with three full days and four tracks on each  
> day.  Each
> WG interim meeting is expected to consume at least one full day on  
> one of
> the tracks.
>
> ADs will schedule the sessions.  A URL for the schedule will be  
> announced
> shortly.  Once it is available, if you detect a scheduling conflict,
> please raise the concern with your AD for resolution.  Session time is
> limited, and sessions will be allocated first come, first served.
>
> The Secretariat will provide registration, food and beverage, audio
> visual facilities, and on site registration support.  VeriLAN will  
> provide
> network and audio streaming support.  It is expected that the  
> meeting fee
> will be $375 for early registration and $475 for late registration.
>
> The Internet Society is looking for meeting sponsors for this event.
> Anyone interested please contact Drew Dvorshak <dvorshak@isoc.org>.
>
> Russ
>

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


From sip-bounces@ietf.org  Fri Oct 24 15:03:37 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5DCAB28C157;
	Fri, 24 Oct 2008 15:03:37 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D6E243A6774
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 15:03:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.254
X-Spam-Level: 
X-Spam-Status: No, score=-6.254 tagged_above=-999 required=5
	tests=[AWL=-0.255, BAYES_00=-2.599, J_CHICKENPOX_37=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XsZYi68cBHLe for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 15:03:34 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id A626F3A657C
	for <sip@ietf.org>; Fri, 24 Oct 2008 15:03:34 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,480,1220227200"; d="scan'208";a="25593940"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 24 Oct 2008 22:04:47 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9OM4kcn013290; 
	Fri, 24 Oct 2008 18:04:46 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9OM4knd004165;
	Fri, 24 Oct 2008 22:04:46 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 18:04:46 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 18:04:46 -0400
Message-ID: <4902467E.3010603@cisco.com>
Date: Fri, 24 Oct 2008 18:04:46 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>
	<4901BA73.1010700@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>
	<4901C2B1.1050209@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>
	<4901D025.6060302@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>
	<490239C8.3020808@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 24 Oct 2008 22:04:46.0493 (UTC)
	FILETIME=[86CACCD0:01C93624]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1367; t=1224885886;
	x=1225749886; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20Content-Type=20vs=20Info-Package=0A=20[was=20RE=3A=20dra
	ft-ietf-sip-info-events-00=3A=20multiple=20packages=20per=20
	INFO] |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=p/8at/pEeSQcX3GKnnQnXP6nZ0wZlYQTLjeRhwEnHUo=;
	b=MsycPY+GHpUvLjfyLOAs3S6kbe8GOBwmesLf5zV8QmjTC1BnQT2IdyYD/3
	aVttFCnqV3kd2FopbJEWhTu+kocjrxXNUHoqdVlpkWxUUQ00iGeSGwdjpGtS
	RRf3g6lMw8;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
 Info-Package [was RE: draft-ietf-sip-info-events-00: multiple packages per
 INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Christer Holmberg wrote:

> So, just to make sure I understand: you are talking about a case where the INFO does contain a multipart message body, but only one of the mimes contains an actual info-package (the other mime(s) contains something else)?

pretty much. And to distinguish those, you need more than C-T.
But I think as we have been discussing, if we only allow one info 
package per INFO, then the Info-Package header belongs in the message, 
not in the body part.

I'll revise your example a bit:


INFO sip:foo@bar.com
To:...
From:...
Some-Header: CID:abcdefg
Info-Package: foo
Content-Type:multipart/mixed
Content-Length:...

--boundary
Content-Type: application/foo-data
Content-Disposition: package;handling=required

foo data
--boundary
Content-ID: abcdefg
Content-Type: application/some-header-data
Content-Disposition: by-reference;handling=optional

some other (non-info package) data
--boundary--


In the above I have used C-D of "package" to identify the part that 
contains the info package. That is yet to be determined, but I think it 
needs to be well defined, even if it is "render".

A more straightforward case would be:

INFO sip:foo@bar.com
To:...
From:...
Info-Package: foo
Content-Type: application/foo-data
Content-Disposition: package;handling=required
Content-Length:10

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


From sip-bounces@ietf.org  Fri Oct 24 15:35:32 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EF59D3A68D5;
	Fri, 24 Oct 2008 15:35:31 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1420C3A68D5
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 15:35:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id EnxBsLrtZ6J7 for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 15:35:30 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 4C5D63A6806
	for <sip@ietf.org>; Fri, 24 Oct 2008 15:35:30 -0700 (PDT)
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9OMaf9d017678
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 24 Oct 2008 17:36:43 -0500
Message-Id: <F05558E6-AF75-41BC-9691-8A7E14748C8B@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
In-Reply-To: <4902467E.3010603@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 24 Oct 2008 17:36:35 -0500
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>
	<4901BA73.1010700@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>
	<4901C2B1.1050209@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>
	<4901D025.6060302@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>
	<490239C8.3020808@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>
	<4902467E.3010603@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 24, 2008, at 5:04 PM, Paul Kyzivat wrote:

>
> Christer Holmberg wrote:
>
>> So, just to make sure I understand: you are talking about a case  
>> where the INFO does contain a multipart message body, but only one  
>> of the mimes contains an actual info-package (the other mime(s)  
>> contains something else)?
>
> pretty much. And to distinguish those, you need more than C-T.
> But I think as we have been discussing, if we only allow one info  
> package per INFO, then the Info-Package header belongs in the  
> message, not in the body part.
>

So the error condition is you have two body parts of types allowed for  
the INFO package, but only one of them is the "real" info, and the  
other part is from some other extension.

If it hurts, don't do it?

Seriously, a Content-Disposition would sort this out.

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


From sip-bounces@ietf.org  Fri Oct 24 16:27:31 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 46D973A6A8C;
	Fri, 24 Oct 2008 16:27:31 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9C7B73A6A8C
	for <sip@core3.amsl.com>; Fri, 24 Oct 2008 16:27:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.551
X-Spam-Level: 
X-Spam-Status: No, score=-6.551 tagged_above=-999 required=5 tests=[AWL=0.048, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id um6yhfWbcgnO for <sip@core3.amsl.com>;
	Fri, 24 Oct 2008 16:27:29 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 9FDFE3A6A76
	for <sip@ietf.org>; Fri, 24 Oct 2008 16:27:29 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,481,1220227200"; d="scan'208";a="25600317"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 24 Oct 2008 23:28:47 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9ONSlm1005976; 
	Fri, 24 Oct 2008 19:28:47 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9ONSllX003460;
	Fri, 24 Oct 2008 23:28:47 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 19:28:47 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Oct 2008 19:28:47 -0400
Message-ID: <49025A2E.4050801@cisco.com>
Date: Fri, 24 Oct 2008 19:28:46 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
References: <48FDEAD8.8010803@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>	<48FF2C45.7010204@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>	<4901BA73.1010700@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>	<4901C2B1.1050209@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>	<4901D025.6060302@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>	<490239C8.3020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>	<4902467E.3010603@cisco.com>
	<F05558E6-AF75-41BC-9691-8A7E14748C8B@softarmor.com>
In-Reply-To: <F05558E6-AF75-41BC-9691-8A7E14748C8B@softarmor.com>
X-OriginalArrivalTime: 24 Oct 2008 23:28:47.0082 (UTC)
	FILETIME=[4337A4A0:01C93630]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1398; t=1224890927;
	x=1225754927; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20Content-Type=20vs=09Info-Package=0A=20[was=20RE=3A=20dra
	ft-ietf-sip-info-events-00=3A=20multiple=09packages=20per=20
	INFO] |Sender:=20
	|To:=20Dean=20Willis=20<dean.willis@softarmor.com>;
	bh=RTZT0jMdqXepdxd4z58I95bo+4xnOGylVstGofr9bW0=;
	b=hDJwfsBMegiArryBneFNYdMa1RkexwvyWvjKvtmxsI7Ikw1sHXnMu+3Qzz
	gvolJKViz8/jNAQ9hmANhgVN4bV6gFIJHxACalVtR03xlH4r20AVbencN7xc
	qryKl3jb3S;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type
 vs	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple	packages
 per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Dean Willis wrote:
> 
> On Oct 24, 2008, at 5:04 PM, Paul Kyzivat wrote:
> 
>>
>> Christer Holmberg wrote:
>>
>>> So, just to make sure I understand: you are talking about a case 
>>> where the INFO does contain a multipart message body, but only one of 
>>> the mimes contains an actual info-package (the other mime(s) contains 
>>> something else)?
>>
>> pretty much. And to distinguish those, you need more than C-T.
>> But I think as we have been discussing, if we only allow one info 
>> package per INFO, then the Info-Package header belongs in the message, 
>> not in the body part.
>>
> 
> So the error condition is you have two body parts of types allowed for 
> the INFO package, but only one of them is the "real" info, and the other 
> part is from some other extension.
> 
> If it hurts, don't do it?
> 
> Seriously, a Content-Disposition would sort this out.

Yes. We need a C-D.

It can be "render" if we want it to be. But I think that brings some 
baggage that we could do without. In particular, "render" is the default 
C-D for any C-T that isn't defined to have some other C-D as its default.

I am really now thinking that the info package type is really a 
"sub-disposition-type" - an extension to the disposition type namespace 
that is independently managed. And then we provide the means to 
negotiate use of those in INFO.

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


From sip-bounces@ietf.org  Sat Oct 25 03:41:47 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AFC0828C12A;
	Sat, 25 Oct 2008 03:41:47 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1874228C12A
	for <sip@core3.amsl.com>; Sat, 25 Oct 2008 03:41:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2x3dd3o+Rh7D for <sip@core3.amsl.com>;
	Sat, 25 Oct 2008 03:41:46 -0700 (PDT)
Received: from smtp1.versatel.nl (smtp1.versatel.nl [62.58.50.88])
	by core3.amsl.com (Postfix) with ESMTP id 0FCCC28C0F6
	for <sip@ietf.org>; Sat, 25 Oct 2008 03:41:45 -0700 (PDT)
Received: (qmail 14810 invoked by uid 0); 25 Oct 2008 10:43:07 -0000
Received: from ip198-11-212-87.adsl2.static.versatel.nl (HELO [192.168.2.155])
	([87.212.11.198]) (envelope-sender <jbemmel@zonnet.nl>)
	by smtp1.versatel.nl (qmail-ldap-1.03) with SMTP
	for < >; 25 Oct 2008 10:43:07 -0000
Message-ID: <4902F82E.5050105@zonnet.nl>
Date: Sat, 25 Oct 2008 12:42:54 +0200
From: Jeroen van Bemmel <jbemmel@zonnet.nl>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: IETF SIP List <sip@ietf.org>
Subject: [Sip] info-events and callee capabilities / caller prefs
	(RFC3840/3841)
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

All,

In analogy with RFC3265-based events and caller prefs / callee 
capabilities, I believe there may be value in having something similar 
for info-events.

Since the current info-events draft does not define a tag for use in 
Supported/Require, a UAC currently has no way to signal that it prefers 
to communicate with a UAS that supports INFO events, let alone  specific 
INFO events (e.g. key strokes, caller ID pictures, etc.). Such a 
capability could be valuable in upgrade scenarios (i.e. moving from a 
network that does not support INFO packages).

My suggestion is therefore to let the new info-events draft update 
RFC3840/RFC3841 with e.g. "info-events=....", and to also define a tag 
for use with Supported/Require to support capability indication

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


From sip-bounces@ietf.org  Sat Oct 25 03:59:36 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B87B63A69DF;
	Sat, 25 Oct 2008 03:59:36 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 56ABF28C131
	for <sip@core3.amsl.com>; Sat, 25 Oct 2008 03:59:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level: 
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id MTIRGiY3iiGc for <sip@core3.amsl.com>;
	Sat, 25 Oct 2008 03:59:34 -0700 (PDT)
Received: from smtp2.versatel.nl (smtp2.versatel.nl [62.58.50.89])
	by core3.amsl.com (Postfix) with ESMTP id EFB123A6966
	for <sip@ietf.org>; Sat, 25 Oct 2008 03:59:33 -0700 (PDT)
Received: (qmail 27845 invoked by uid 0); 25 Oct 2008 11:00:54 -0000
Received: from ip198-11-212-87.adsl2.static.versatel.nl (HELO [192.168.2.155])
	([87.212.11.198]) (envelope-sender <jbemmel@zonnet.nl>)
	by smtp2.versatel.nl (qmail-ldap-1.03) with SMTP
	for < >; 25 Oct 2008 11:00:54 -0000
Message-ID: <4902FC59.3000303@zonnet.nl>
Date: Sat, 25 Oct 2008 13:00:41 +0200
From: Jeroen van Bemmel <jbemmel@zonnet.nl>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Dale.Worley@comcast.net
References: <48FDEB20.9040109@cisco.com>
	<200810241732.m9OHWbxv52636270@shell01.TheWorld.com>
In-Reply-To: <200810241732.m9OHWbxv52636270@shell01.TheWorld.com>
Cc: sip@ietf.org
Subject: Re: [Sip] draft-ietf-sip-info-events-00: CANCEL???
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

All,

IMHO allowing CANCEL of INFO requests is a bad idea, it introduces a 
RACE condition that any CANCEL will generally loose. It also introduces 
semantic issues: what does it mean to cancel a given INFO event? For 
INVITE it somewhat intuitively means stop ringing the phone and signal 
to the callee that the call was aborted, it is not generally clear what 
CANCEL for a generic INFO event would mean. For example, an INFO event 
might trigger some action that is not "undoable" (e.g. a gaming move in 
a multiplayer game, the final digit of a 4-digit access code, ... )

I do have a question regarding the - somewhat hypothetical - scenario of 
a mid-dialog INVITE being CANCELed: How does that affect the INFO 
negotiation mechanism state? I guess from a UAS perspective the 
UAC-provided Send-Info and Recv-Info in the INVITE should be reverted 
back to the last known values, and for the UAC the 487 response should 
cause it to revert to the previous state?

Regards,
Jeroen

Dale.Worley@comcast.net wrote:
>    From: Paul Kyzivat <pkyzivat@cisco.com>
>
>    I have a question regarding the following paragraph:
>
>        A UAC MAY CANCEL an INFO request.  A UAS receiving a CANCEL for an
>        INFO request SHOULD respond to the INFO with a "487 Request
>        Cancelled" response unless the UAC has already sent a final response.
>        The UAS then MUST ignore future INFO requests.
>
>    Why would the CANCEL affect *future* info requests???
>
> I'm sure we *don't* want CANCEL to affect future INFO requests.  That
> adds another bit of state that has to be remembered, and I'm sure it
> will cause some weird complications.  (Among other things, what is it
> to "ignore" an INFO request?  What response code is that?)
>
> Dale
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>
>   
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Sat Oct 25 04:21:14 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A1D8F3A6966;
	Sat, 25 Oct 2008 04:21:14 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B4D983A6807
	for <sip@core3.amsl.com>; Sat, 25 Oct 2008 04:21:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.004
X-Spam-Level: 
X-Spam-Status: No, score=-1.004 tagged_above=-999 required=5 tests=[AWL=0.500, 
	BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545,
	RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zqumILKOyOUN for <sip@core3.amsl.com>;
	Sat, 25 Oct 2008 04:21:13 -0700 (PDT)
Received: from smtp6.versatel.nl (smtp6.versatel.nl [62.58.50.97])
	by core3.amsl.com (Postfix) with ESMTP id A4DB53A6966
	for <sip@ietf.org>; Sat, 25 Oct 2008 04:21:12 -0700 (PDT)
Received: (qmail 29418 invoked by uid 0); 25 Oct 2008 11:22:34 -0000
Received: from ip198-11-212-87.adsl2.static.versatel.nl (HELO [192.168.2.155])
	([87.212.11.198]) (envelope-sender <jbemmel@zonnet.nl>)
	by smtp6.versatel.nl (qmail-ldap-1.03) with SMTP
	for < >; 25 Oct 2008 11:22:34 -0000
Message-ID: <4903016D.2030106@zonnet.nl>
Date: Sat, 25 Oct 2008 13:22:21 +0200
From: Jeroen van Bemmel <jbemmel@zonnet.nl>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: IETF SIP List <sip@ietf.org>
Subject: [Sip] info-events and "in-order delivery"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

    The current info-events text says (section 5.6):

"In addition, the INFO method does not define mechanisms for ensuring
   in-order delivery.  While the UAC will increment the CSeq header upon
   the transmission of new INFO messages, the UAS cannot use the CSeq to
   determine the sequence of INFO information.  This is due to the fact
   that there could be gaps in the INFO message CSeq count caused by a
   user agent sending re-INVITES or other SIP messages."


This is not entirely accurate: SIP guarantees that INFO messages are never delivered out-of-sequence. 
Only in case of *overlapping INFO requests* (i.e. sending a next one before having received a final 
response for the previous one) it cannot be guaranteed that all are received.

The partial event mechanism (RFC5263) includes a 'version' attribute to detect such gaps. In case of INFO events, 
I think it is better to simply say: the UAC MUST NOT send an INFO request with a given event type when a previous 
INFO request containing that event type has not yet received a final response.

Regards,
Jeroen


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


From sip-bounces@ietf.org  Sat Oct 25 04:49:46 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B70F228C15E;
	Sat, 25 Oct 2008 04:49:46 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 22DD128C15E
	for <sip@core3.amsl.com>; Sat, 25 Oct 2008 04:49:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.629
X-Spam-Level: 
X-Spam-Status: No, score=-0.629 tagged_above=-999 required=5
	tests=[AWL=-0.125, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id hWuVlN8a4I6S for <sip@core3.amsl.com>;
	Sat, 25 Oct 2008 04:49:45 -0700 (PDT)
Received: from smtp2.versatel.nl (smtp2.versatel.nl [62.58.50.89])
	by core3.amsl.com (Postfix) with ESMTP id 1A6FA28C0F6
	for <sip@ietf.org>; Sat, 25 Oct 2008 04:49:44 -0700 (PDT)
Received: (qmail 19215 invoked by uid 0); 25 Oct 2008 11:51:07 -0000
Received: from ip198-11-212-87.adsl2.static.versatel.nl (HELO [192.168.2.155])
	([87.212.11.198]) (envelope-sender <jbemmel@zonnet.nl>)
	by smtp2.versatel.nl (qmail-ldap-1.03) with SMTP
	for < >; 25 Oct 2008 11:51:07 -0000
Message-ID: <4903081E.4090002@zonnet.nl>
Date: Sat, 25 Oct 2008 13:50:54 +0200
From: Jeroen van Bemmel <jbemmel@zonnet.nl>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: IETF SIP List <sip@ietf.org>
Subject: [Sip] info-event: syntax simplification
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Current draft (with Recv fix):

Info-Package        =  "Info-Package" HCOLON Info-package-type
   Send-Info           =  "Send-Info" HCOLON Info-package-type
                          *( COMMA Info-package-type )
   Recv-Info           =  "Recv-Info" HCOLON Info-package-type
                          *( COMMA Info-package-type )
   Info-package-type   =  Info-package-name *( "." Info-package-param)
   Info-package-name   =  token-nodot
   token-nodot         =  1*( alphanum / "-"  / "!" / "%" / "*"
                              / "_" / "+" / "`" / "'" / "~" ) ;rfc3265
   Info-package-param  =  generic-param  ;this doesn't work due to dot!


 From an implementation perspective, this is unnecessarily complex and 
verbose: if a UA can both send and receive the same INFO package, it 
must list it twice.

As an alternative, I would propose something similar to SDP media streams:

Supported-Info      = "Supported-Info" HCOLON Info-package-type *(COMMA Info-package-type)
Info-package-type   = token *( SEMI Info-package-param )
Info-package-param  = "sendonly" / "recvonly" / generic-param ; only one of "sendonly" or "recvonly" may be present

Usage would be to include 1 "Supported-Info" header in requests/responses, instead of 2 separate "Send-Info" / "Recv-Info". 
By default a package is "sendrecv" (i.e. UA may send it, and can receive it), unless overridden by "sendonly" or "recvonly" flags

Regards,
Jeroen


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


From sip-bounces@ietf.org  Sat Oct 25 05:08:46 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C044828C0F4;
	Sat, 25 Oct 2008 05:08:46 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 190913A69FC
	for <sip@core3.amsl.com>; Sat, 25 Oct 2008 05:08:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.104
X-Spam-Level: 
X-Spam-Status: No, score=-1.104 tagged_above=-999 required=5 tests=[AWL=0.399, 
	BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545,
	HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UF8AAvUQNOXz for <sip@core3.amsl.com>;
	Sat, 25 Oct 2008 05:08:44 -0700 (PDT)
Received: from smtp6.versatel.nl (smtp6.versatel.nl [62.58.50.97])
	by core3.amsl.com (Postfix) with ESMTP id EFEDA3A69A1
	for <sip@ietf.org>; Sat, 25 Oct 2008 05:08:43 -0700 (PDT)
Received: (qmail 17946 invoked by uid 0); 25 Oct 2008 12:10:06 -0000
Received: from ip198-11-212-87.adsl2.static.versatel.nl (HELO [192.168.2.155])
	([87.212.11.198]) (envelope-sender <jbemmel@zonnet.nl>)
	by smtp6.versatel.nl (qmail-ldap-1.03) with SMTP
	for < >; 25 Oct 2008 12:10:06 -0000
Message-ID: <49030C91.3070900@zonnet.nl>
Date: Sat, 25 Oct 2008 14:09:53 +0200
From: Jeroen van Bemmel <jbemmel@zonnet.nl>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens.com>
References: <48FDEAD8.8010803@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com>
	A	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>	<0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>	<CA9998CD4A020D418654FCDEF4E707DF088F17D5@esealmw113.eemea.ericsson.se>	<5D1A7985295922448D5550C94DE2918002425C2C@DEEXC1U01.de.lucent.com>	<CA9998CD4A020D418654FCDEF4E707DF088F19BA@esealmw113.eemea.ericsson.se>	<49006A58.3090106@cisco.com>
	<0D5F89FAC29E2C41B98A6A762007F5D00134941B@GBNTHT12009MSX.gb002.siemens.net>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D00134941B@GBNTHT12009MSX.gb002.siemens.net>
Cc: SIP IETF <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>,
	Dean Willis <dean.willis@softarmor.com>, Eric Burger <eburger@bea.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2097505843=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.
--===============2097505843==
Content-Type: multipart/alternative;
 boundary="------------020905060300010208040309"

This is a multi-part message in MIME format.
--------------020905060300010208040309
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Multiple packages per INFO can trivially be supported by defining a 
Content-Type parameter to indicate the INFO event package being used, 
instead of the "Info-Package" header

So:

INFO sip:foo@bar.com
To:...
From:...
Content-Type:multipart/mixed
Content-Length:...

--boundary
Content-Type: application/foo-data*;info-package=foo*

foo data
--boundary
Content-ID: abcdefg
Content-Type: application/some-header-data

some other (non-info package) data
--boundary--

I believe this models things better, as the INFO event package being 
used is really just an attribute of the Content-Type to help 
interpretation of the contents, just like Content-Type helps interpret 
the format

Regards,
Jeroen

Elwell, John wrote:
> I agree with Paul and Christer concerning multiple packages per dialog.
> It seems a very reasonable thing to do and doesn't cost anything in
> complexity.
>
> John 
>
>   
>> -----Original Message-----
>> From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
>> Sent: 23 October 2008 13:13
>> To: Christer Holmberg
>> Cc: DRAGE, Keith (Keith); Elwell, John; Dean Willis; SIP 
>> IETF; Eric Burger
>> Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple 
>> packages per INFO
>>
>> I also agree it is too extreme to restrict to one package per dialog.
>> But as I stated earlier, I'm fine not defining multiple 
>> packages per INFO.
>>
>> 	Paul
>>
>> Christer Holmberg wrote:
>>     
>>> Hi, 
>>>
>>>       
>>>> I don't have a problem agreeing with that.
>>>>
>>>> Note that buried somewhere in this thread was a question 
>>>>         
>> of whether we
>>     
>>> had a use case for multiple packages per dialog, or can we 
>>>       
>> simplify even
>>     
>>> further.
>>>
>>> I don't think we should go that far, because that could become very
>>> restrictive.
>>>
>>> For example, assume I want to use INFO packages e.g. for 
>>>       
>> DTMF during the
>>     
>>> call setup, and then other INFO package(s) for something 
>>>       
>> else during the
>>     
>>> call.
>>>
>>> Regards,
>>>
>>> Christer
>>>
>>>
>>>       
>>>> -----Original Message-----
>>>> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
>>>> Sent: Thursday, October 23, 2008 10:51 AM
>>>> To: Elwell, John; Dean Willis; DRAGE, Keith (Keith)
>>>> Cc: SIP IETF; Eric Burger; Paul Kyzivat
>>>> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple 
>>>>         
>> packages 
>>     
>>>> per INFO
>>>>
>>>>
>>>> Hi,
>>>>
>>>> I agree with John. Let's keep it simple. If allowing 
>>>>         
>> multiple packages
>>     
>>>> in a single INFO causes issues, let's forget about it.
>>>>
>>>> The whole idea with this is to allow people using INFO to 
>>>>         
>> do so in an 
>>     
>>>> easy and standardized way, so let's not shoot ourselves in 
>>>>         
>> the foot 
>>     
>>>> with complexity.
>>>>
>>>> Regards,
>>>>
>>>> Christer
>>>>
>>>> -----Original Message-----
>>>> From: Elwell, John [mailto:john.elwell@siemens.com]
>>>> Sent: 23. lokakuuta 2008 12:30
>>>> To: Christer Holmberg; Dean Willis; DRAGE, Keith (Keith)
>>>> Cc: SIP IETF; Eric Burger; Paul Kyzivat
>>>> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple 
>>>>         
>> packages 
>>     
>>>> per INFO
>>>>
>>>> In reply to this whole thread, please bear in mind that we 
>>>>         
>> had lots of
>>     
>>>> discussion about whether it would be worthwhile defining 
>>>>         
>> this new INFO
>>     
>>>> mechanism, since existing applications are unlikely to 
>>>>         
>> change and the 
>>     
>>>> best we can hope for is that new applications will exploit the new 
>>>> mechanism. Therefore we want to keep the mechanism as simple as 
>>>> possible. The complexities of matching body parts to 
>>>>         
>> header fields, 
>>     
>>>> dealing with cases where only some of the packages are understood, 
>>>> etc.
>>>> are hardly likely to persuade people to implement the mechanism. 
>>>> Please keep it simple.
>>>>
>>>> John
>>>>
>>>>
>>>>         
>>>>> -----Original Message-----
>>>>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
>>>>>           
>>>> Behalf Of
>>>>         
>>>>> Christer Holmberg
>>>>> Sent: 23 October 2008 08:17
>>>>> To: Dean Willis; DRAGE, Keith (Keith)
>>>>> Cc: SIP IETF; Eric Burger; Paul Kyzivat
>>>>> Subject: Re: [Sip] draft-ietf-sip-info-events-00: 
>>>>>           
>> multiple packages 
>>     
>>>>> per INFO
>>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>>           
>>>>>>> Why does putting two different packages in the same INFO
>>>>>>>               
>>>>> work better
>>>>>           
>>>>>>> than two different INFO messages each with their own
>>>>>>>               
>>>>> package usage? Is
>>>>>
>>>>>           
>>>>>>> there a desirable relationship that can be implemented
>>>>>>>               
>>>>> between the two
>>>>>
>>>>>           
>>>>>>> that we would otherwise lose?
>>>>>>>               
>>>>>> We have one package per NOTIFY. Let's stick with one package
>>>>>>             
>>>>> per INFO,
>>>>> unless we want to go back to using mime-types as the only 
>>>>> distinguisher of packages.
>>>>>
>>>>> I raised that issue in another e-mail.
>>>>>
>>>>> But, never the less, I have no strong feelings on the 
>>>>>           
>> single versus 
>>     
>>>>> multiple package issue.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Christer
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>>>> This list is for NEW development of the core SIP Protocol Use 
>>>>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>>>>> sipping@ietf.org for new developments on the application of sip
>>>>>
>>>>>           
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>
>   

--------------020905060300010208040309
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Multiple packages per INFO can trivially be supported by defining a
Content-Type parameter to indicate the INFO event package being used,
instead of the "Info-Package" header<br>
<br>
So:<br>
<br>
INFO <a class="moz-txt-link-abbreviated" href="mailto:sip:foo@bar.com">sip:foo@bar.com</a>
<br>
To:...
<br>
From:...
<br>
Content-Type:multipart/mixed
<br>
Content-Length:...
<br>
<br>
--boundary
<br>
Content-Type: application/foo-data<b>;info-package=foo</b>
<br>
<br>
foo data
<br>
--boundary
<br>
Content-ID: abcdefg
<br>
Content-Type: application/some-header-data
<br>
<br>
some other (non-info package) data
<br>
--boundary--
<br>
<br>
I believe this models things better, as the INFO event package being
used is really just an attribute of the Content-Type to help
interpretation of the contents, just like Content-Type helps interpret
the format<br>
<br>
Regards,<br>
Jeroen<br>
<br>
Elwell, John wrote:
<blockquote
 cite="mid:0D5F89FAC29E2C41B98A6A762007F5D00134941B@GBNTHT12009MSX.gb002.siemens.net"
 type="cite">
  <pre wrap="">I agree with Paul and Christer concerning multiple packages per dialog.
It seems a very reasonable thing to do and doesn't cost anything in
complexity.

John 

  </pre>
  <blockquote type="cite">
    <pre wrap="">-----Original Message-----
From: Paul Kyzivat [<a class="moz-txt-link-freetext" href="mailto:pkyzivat@cisco.com">mailto:pkyzivat@cisco.com</a>] 
Sent: 23 October 2008 13:13
To: Christer Holmberg
Cc: DRAGE, Keith (Keith); Elwell, John; Dean Willis; SIP 
IETF; Eric Burger
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple 
packages per INFO

I also agree it is too extreme to restrict to one package per dialog.
But as I stated earlier, I'm fine not defining multiple 
packages per INFO.

	Paul

Christer Holmberg wrote:
    </pre>
    <blockquote type="cite">
      <pre wrap="">Hi, 

      </pre>
      <blockquote type="cite">
        <pre wrap="">I don't have a problem agreeing with that.

Note that buried somewhere in this thread was a question 
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">of whether we
    </pre>
    <blockquote type="cite">
      <pre wrap="">had a use case for multiple packages per dialog, or can we 
      </pre>
    </blockquote>
    <pre wrap="">simplify even
    </pre>
    <blockquote type="cite">
      <pre wrap="">further.

I don't think we should go that far, because that could become very
restrictive.

For example, assume I want to use INFO packages e.g. for 
      </pre>
    </blockquote>
    <pre wrap="">DTMF during the
    </pre>
    <blockquote type="cite">
      <pre wrap="">call setup, and then other INFO package(s) for something 
      </pre>
    </blockquote>
    <pre wrap="">else during the
    </pre>
    <blockquote type="cite">
      <pre wrap="">call.

Regards,

Christer


      </pre>
      <blockquote type="cite">
        <pre wrap="">-----Original Message-----
From: Christer Holmberg [<a class="moz-txt-link-freetext" href="mailto:christer.holmberg@ericsson.com">mailto:christer.holmberg@ericsson.com</a>]
Sent: Thursday, October 23, 2008 10:51 AM
To: Elwell, John; Dean Willis; DRAGE, Keith (Keith)
Cc: SIP IETF; Eric Burger; Paul Kyzivat
Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple 
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">packages 
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">per INFO


Hi,

I agree with John. Let's keep it simple. If allowing 
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">multiple packages
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">in a single INFO causes issues, let's forget about it.

The whole idea with this is to allow people using INFO to 
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">do so in an 
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">easy and standardized way, so let's not shoot ourselves in 
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">the foot 
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">with complexity.

Regards,

Christer

-----Original Message-----
From: Elwell, John [<a class="moz-txt-link-freetext" href="mailto:john.elwell@siemens.com">mailto:john.elwell@siemens.com</a>]
Sent: 23. lokakuuta 2008 12:30
To: Christer Holmberg; Dean Willis; DRAGE, Keith (Keith)
Cc: SIP IETF; Eric Burger; Paul Kyzivat
Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple 
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">packages 
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">per INFO

In reply to this whole thread, please bear in mind that we 
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">had lots of
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">discussion about whether it would be worthwhile defining 
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">this new INFO
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">mechanism, since existing applications are unlikely to 
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">change and the 
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">best we can hope for is that new applications will exploit the new 
mechanism. Therefore we want to keep the mechanism as simple as 
possible. The complexities of matching body parts to 
        </pre>
      </blockquote>
    </blockquote>
    <pre wrap="">header fields, 
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap="">dealing with cases where only some of the packages are understood, 
etc.
are hardly likely to persuade people to implement the mechanism. 
Please keep it simple.

John


        </pre>
        <blockquote type="cite">
          <pre wrap="">-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:sip-bounces@ietf.org">sip-bounces@ietf.org</a> [<a class="moz-txt-link-freetext" href="mailto:sip-bounces@ietf.org">mailto:sip-bounces@ietf.org</a>] On
          </pre>
        </blockquote>
        <pre wrap="">Behalf Of
        </pre>
        <blockquote type="cite">
          <pre wrap="">Christer Holmberg
Sent: 23 October 2008 08:17
To: Dean Willis; DRAGE, Keith (Keith)
Cc: SIP IETF; Eric Burger; Paul Kyzivat
Subject: Re: [Sip] draft-ietf-sip-info-events-00: 
          </pre>
        </blockquote>
      </blockquote>
    </blockquote>
    <pre wrap="">multiple packages 
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">per INFO


Hi,

          </pre>
          <blockquote type="cite">
            <blockquote type="cite">
              <pre wrap="">Why does putting two different packages in the same INFO
              </pre>
            </blockquote>
          </blockquote>
          <pre wrap="">work better
          </pre>
          <blockquote type="cite">
            <blockquote type="cite">
              <pre wrap="">than two different INFO messages each with their own
              </pre>
            </blockquote>
          </blockquote>
          <pre wrap="">package usage? Is

          </pre>
          <blockquote type="cite">
            <blockquote type="cite">
              <pre wrap="">there a desirable relationship that can be implemented
              </pre>
            </blockquote>
          </blockquote>
          <pre wrap="">between the two

          </pre>
          <blockquote type="cite">
            <blockquote type="cite">
              <pre wrap="">that we would otherwise lose?
              </pre>
            </blockquote>
            <pre wrap="">We have one package per NOTIFY. Let's stick with one package
            </pre>
          </blockquote>
          <pre wrap="">per INFO,
unless we want to go back to using mime-types as the only 
distinguisher of packages.

I raised that issue in another e-mail.

But, never the less, I have no strong feelings on the 
          </pre>
        </blockquote>
      </blockquote>
    </blockquote>
    <pre wrap="">single versus 
    </pre>
    <blockquote type="cite">
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">multiple package issue.

Regards,

Christer


_______________________________________________
Sip mailing list  <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/sip">https://www.ietf.org/mailman/listinfo/sip</a>
This list is for NEW development of the core SIP Protocol Use 
<a class="moz-txt-link-abbreviated" href="mailto:sip-implementors@cs.columbia.edu">sip-implementors@cs.columbia.edu</a> for questions on current sip Use 
<a class="moz-txt-link-abbreviated" href="mailto:sipping@ietf.org">sipping@ietf.org</a> for new developments on the application of sip

          </pre>
        </blockquote>
      </blockquote>
    </blockquote>
  </blockquote>
  <pre wrap=""><!---->_______________________________________________
Sip mailing list  <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/sip">https://www.ietf.org/mailman/listinfo/sip</a>
This list is for NEW development of the core SIP Protocol
Use <a class="moz-txt-link-abbreviated" href="mailto:sip-implementors@cs.columbia.edu">sip-implementors@cs.columbia.edu</a> for questions on current sip
Use <a class="moz-txt-link-abbreviated" href="mailto:sipping@ietf.org">sipping@ietf.org</a> for new developments on the application of sip

  </pre>
</blockquote>
</body>
</html>

--------------020905060300010208040309--

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

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


From sip-bounces@ietf.org  Sat Oct 25 05:30:43 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5AD4C3A69B0;
	Sat, 25 Oct 2008 05:30:43 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D191A3A6827
	for <sip@core3.amsl.com>; Sat, 25 Oct 2008 05:30:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.671
X-Spam-Level: 
X-Spam-Status: No, score=-0.671 tagged_above=-999 required=5
	tests=[AWL=-0.167, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KJkxT7gFE1nA for <sip@core3.amsl.com>;
	Sat, 25 Oct 2008 05:30:42 -0700 (PDT)
Received: from smtp2.versatel.nl (smtp2.versatel.nl [62.58.50.89])
	by core3.amsl.com (Postfix) with ESMTP id C6FE03A69B0
	for <sip@ietf.org>; Sat, 25 Oct 2008 05:30:25 -0700 (PDT)
Received: (qmail 4636 invoked by uid 0); 25 Oct 2008 12:31:47 -0000
Received: from ip198-11-212-87.adsl2.static.versatel.nl (HELO [192.168.2.155])
	([87.212.11.198]) (envelope-sender <jbemmel@zonnet.nl>)
	by smtp2.versatel.nl (qmail-ldap-1.03) with SMTP
	for < >; 25 Oct 2008 12:31:47 -0000
Message-ID: <490311A6.3090801@zonnet.nl>
Date: Sat, 25 Oct 2008 14:31:34 +0200
From: Jeroen van Bemmel <jbemmel@zonnet.nl>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
References: <48FDEAD8.8010803@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com>
	A	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>	<0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>	<CA9998CD4A020D418654FCDEF4E707DF088F17D5@esealmw113.eemea.ericsson.se>	<5D1A7985295922448D5550C94DE2918002425C2C@DEEXC1U01.de.lucent.com>	<CA9998CD4A020D418654FCDEF4E707DF088F19BA@esealmw113.eemea.ericsson.se>
	<49006A58.3090106@cisco.com>
In-Reply-To: <49006A58.3090106@cisco.com>
Cc: SIP IETF <sip@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>,
	"DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>, "Elwell,
	John" <john.elwell@siemens.com>, Dean Willis <dean.willis@softarmor.com>,
	Eric Burger <eburger@bea.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

A possible reason to want multiple packages per INFO request, is that it 
allows one to construct applications that rely on "all or nothing" 
semantics for correlated events.

For example, if one would use SIP to implement an application that lets 
one post a small icon on a blog, and requires an authorization token to 
do that, both would have to arrive together. Another example could be an 
electronic variant of a postage stamp (i.e. some token representing some 
monetary value), when using two different INFOs one might fail to arrive 
where the other would (i.e. content without payment, or payment without 
content).

It has to do with certain atomic, transactional behavior and consistency 
of the user experience

Regards,
Jeroen

Paul Kyzivat wrote:
> I also agree it is too extreme to restrict to one package per dialog.
> But as I stated earlier, I'm fine not defining multiple packages per 
> INFO.
>
>     Paul
>
> Christer Holmberg wrote:
>> Hi,
>>> I don't have a problem agreeing with that.
>>>
>>> Note that buried somewhere in this thread was a question of whether we
>> had a use case for multiple packages per dialog, or can we simplify even
>> further.
>>
>> I don't think we should go that far, because that could become very
>> restrictive.
>>
>> For example, assume I want to use INFO packages e.g. for DTMF during the
>> call setup, and then other INFO package(s) for something else during the
>> call.
>>
>> Regards,
>>
>> Christer
>>
>>
>>> -----Original Message-----
>>> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
>>> Sent: Thursday, October 23, 2008 10:51 AM
>>> To: Elwell, John; Dean Willis; DRAGE, Keith (Keith)
>>> Cc: SIP IETF; Eric Burger; Paul Kyzivat
>>> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple packages 
>>> per INFO
>>>
>>>
>>> Hi,
>>>
>>> I agree with John. Let's keep it simple. If allowing multiple packages
>>
>>> in a single INFO causes issues, let's forget about it.
>>>
>>> The whole idea with this is to allow people using INFO to do so in 
>>> an easy and standardized way, so let's not shoot ourselves in the 
>>> foot with complexity.
>>>
>>> Regards,
>>>
>>> Christer
>>>
>>> -----Original Message-----
>>> From: Elwell, John [mailto:john.elwell@siemens.com]
>>> Sent: 23. lokakuuta 2008 12:30
>>> To: Christer Holmberg; Dean Willis; DRAGE, Keith (Keith)
>>> Cc: SIP IETF; Eric Burger; Paul Kyzivat
>>> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple packages 
>>> per INFO
>>>
>>> In reply to this whole thread, please bear in mind that we had lots of
>>
>>> discussion about whether it would be worthwhile defining this new INFO
>>
>>> mechanism, since existing applications are unlikely to change and 
>>> the best we can hope for is that new applications will exploit the 
>>> new mechanism. Therefore we want to keep the mechanism as simple as 
>>> possible. The complexities of matching body parts to header fields, 
>>> dealing with cases where only some of the packages are understood, etc.
>>> are hardly likely to persuade people to implement the mechanism. 
>>> Please keep it simple.
>>>
>>> John
>>>
>>>
>>>> -----Original Message-----
>>>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
>>> Behalf Of
>>>> Christer Holmberg
>>>> Sent: 23 October 2008 08:17
>>>> To: Dean Willis; DRAGE, Keith (Keith)
>>>> Cc: SIP IETF; Eric Burger; Paul Kyzivat
>>>> Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages 
>>>> per INFO
>>>>
>>>>
>>>> Hi,
>>>>
>>>>>> Why does putting two different packages in the same INFO
>>>> work better
>>>>>> than two different INFO messages each with their own
>>>> package usage? Is
>>>>
>>>>>> there a desirable relationship that can be implemented
>>>> between the two
>>>>
>>>>>> that we would otherwise lose?
>>>>> We have one package per NOTIFY. Let's stick with one package
>>>> per INFO,
>>>> unless we want to go back to using mime-types as the only 
>>>> distinguisher of packages.
>>>>
>>>> I raised that issue in another e-mail.
>>>>
>>>> But, never the less, I have no strong feelings on the single versus 
>>>> multiple package issue.
>>>>
>>>> Regards,
>>>>
>>>> Christer
>>>>
>>>>
>>>> _______________________________________________
>>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>>> This list is for NEW development of the core SIP Protocol Use 
>>>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>>>> sipping@ietf.org for new developments on the application of sip
>>>>
>>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Sat Oct 25 07:01:00 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 587C03A6A15;
	Sat, 25 Oct 2008 07:01:00 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2D3253A69E9
	for <sip@core3.amsl.com>; Sat, 25 Oct 2008 07:00:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.581
X-Spam-Level: 
X-Spam-Status: No, score=-6.581 tagged_above=-999 required=5 tests=[AWL=0.018, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id NH1wUp3m2frR for <sip@core3.amsl.com>;
	Sat, 25 Oct 2008 07:00:57 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id D47D83A6A70
	for <sip@ietf.org>; Sat, 25 Oct 2008 07:00:20 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,483,1220227200"; d="scan'208";a="25636925"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 25 Oct 2008 14:01:44 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9PE1iDA018615; 
	Sat, 25 Oct 2008 10:01:44 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9PE1iR3011046;
	Sat, 25 Oct 2008 14:01:44 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 25 Oct 2008 10:01:44 -0400
Received: from [10.86.249.64] ([10.86.249.64]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 25 Oct 2008 10:01:44 -0400
Message-ID: <490326C7.5010601@cisco.com>
Date: Sat, 25 Oct 2008 10:01:43 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Jeroen van Bemmel <jbemmel@zonnet.nl>
References: <48FDEB20.9040109@cisco.com>	<200810241732.m9OHWbxv52636270@shell01.TheWorld.com>
	<4902FC59.3000303@zonnet.nl>
In-Reply-To: <4902FC59.3000303@zonnet.nl>
X-OriginalArrivalTime: 25 Oct 2008 14:01:44.0392 (UTC)
	FILETIME=[3686E480:01C936AA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3045; t=1224943304;
	x=1225807304; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20CANCEL??? |Sender:=20
	|To:=20Jeroen=20van=20Bemmel=20<jbemmel@zonnet.nl>;
	bh=7DzmUsrYjHUb4ZmsxcAZ4pvuDiSCmz6csRFw9ncf4Lk=;
	b=I13xSC+Pi3stbYn+xj8mQjXc0sm0SsxgxBV5WsU5hZiWeAZaXbiBIjJNRl
	+qhdiwSslj0F+JppZWW+V6hiA4YKtP8lwdQL7q/DceAkOczMYSKFhy0DLfmg
	qPUN92yXE7;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: sip@ietf.org
Subject: Re: [Sip] draft-ietf-sip-info-events-00: CANCEL???
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Jeroen,

Re CANCEL of INFO, I don't see this any different than CANCEL of any 
other non-INVITE transaction: you are free to ask, but don't get your 
hopes up, because it probably won't work.

Re CANCEL of reINVITE: I already raised the issue of the need to define 
what happens to the negotiated info package state when a reINVITE fails. 
This is just an instance of that. (The issue is around the resulting 487 
response to the INVITE, not the CANCEL itself that is the issue.)

	Thanks,
	Paul

Jeroen van Bemmel wrote:
> All,
> 
> IMHO allowing CANCEL of INFO requests is a bad idea, it introduces a 
> RACE condition that any CANCEL will generally loose. It also introduces 
> semantic issues: what does it mean to cancel a given INFO event? For 
> INVITE it somewhat intuitively means stop ringing the phone and signal 
> to the callee that the call was aborted, it is not generally clear what 
> CANCEL for a generic INFO event would mean. For example, an INFO event 
> might trigger some action that is not "undoable" (e.g. a gaming move in 
> a multiplayer game, the final digit of a 4-digit access code, ... )
> 
> I do have a question regarding the - somewhat hypothetical - scenario of 
> a mid-dialog INVITE being CANCELed: How does that affect the INFO 
> negotiation mechanism state? I guess from a UAS perspective the 
> UAC-provided Send-Info and Recv-Info in the INVITE should be reverted 
> back to the last known values, and for the UAC the 487 response should 
> cause it to revert to the previous state?
> 
> Regards,
> Jeroen
> 
> Dale.Worley@comcast.net wrote:
>>    From: Paul Kyzivat <pkyzivat@cisco.com>
>>
>>    I have a question regarding the following paragraph:
>>
>>        A UAC MAY CANCEL an INFO request.  A UAS receiving a CANCEL for an
>>        INFO request SHOULD respond to the INFO with a "487 Request
>>        Cancelled" response unless the UAC has already sent a final 
>> response.
>>        The UAS then MUST ignore future INFO requests.
>>
>>    Why would the CANCEL affect *future* info requests???
>>
>> I'm sure we *don't* want CANCEL to affect future INFO requests.  That
>> adds another bit of state that has to be remembered, and I'm sure it
>> will cause some weird complications.  (Among other things, what is it
>> to "ignore" an INFO request?  What response code is that?)
>>
>> Dale
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sipping@ietf.org for new developments on the application of sip
>>
>>   
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Sat Oct 25 07:08:23 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7AF793A68A4;
	Sat, 25 Oct 2008 07:08:23 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9CAA13A68A4
	for <sip@core3.amsl.com>; Sat, 25 Oct 2008 07:08:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.582
X-Spam-Level: 
X-Spam-Status: No, score=-6.582 tagged_above=-999 required=5 tests=[AWL=0.017, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BqXryoOZ2Gh3 for <sip@core3.amsl.com>;
	Sat, 25 Oct 2008 07:08:20 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 90D323A6841
	for <sip@ietf.org>; Sat, 25 Oct 2008 07:08:20 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,483,1220227200"; d="scan'208";a="25669333"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 25 Oct 2008 14:09:44 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9PE9iO3020469; 
	Sat, 25 Oct 2008 10:09:44 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9PE9iV4012107;
	Sat, 25 Oct 2008 14:09:44 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 25 Oct 2008 10:09:44 -0400
Received: from [10.86.249.64] ([10.86.249.64]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 25 Oct 2008 10:09:44 -0400
Message-ID: <490328A7.1080604@cisco.com>
Date: Sat, 25 Oct 2008 10:09:43 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Jeroen van Bemmel <jbemmel@zonnet.nl>
References: <4903016D.2030106@zonnet.nl>
In-Reply-To: <4903016D.2030106@zonnet.nl>
X-OriginalArrivalTime: 25 Oct 2008 14:09:44.0067 (UTC)
	FILETIME=[546F7D30:01C936AB]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2028; t=1224943784;
	x=1225807784; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20info-events=20and=20=22in-order
	=20delivery=22 |Sender:=20
	|To:=20Jeroen=20van=20Bemmel=20<jbemmel@zonnet.nl>;
	bh=83ZMIH/n8y8hWQ9N8G/JS0RfgrBSbi8MB/xBkO4NM5c=;
	b=YdmRiQ278r8Kl2rMuRM4SgC7Q1p6LlG4ZO3s9zFVgvuKYSQ6eTuBtm6aya
	c8ms+9CjxSbs/aRrjBrTDevvq85EnW8ai6yhYV57HiiZcg+qQSRYxTu1n0Wr
	/C/69IAFaN;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: IETF SIP List <sip@ietf.org>
Subject: Re: [Sip] info-events and "in-order delivery"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Jeroen,

There may be some utility to overlapping info packages of the *same* 
package type. This can work if subsequent messages *supersede* the 
preceding one, so if a later one is processed first then the loss of the 
earlier one is irrelevant. But this is much less likely to be the case 
for packages of *different* types.

I think this simply needs to be highlighted as an issue - especially the 
cross-package-type issue. The details need to be addressed on a 
per-package-type basis.

	Thanks,
	Paul

Jeroen van Bemmel wrote:
>    The current info-events text says (section 5.6):
> 
> "In addition, the INFO method does not define mechanisms for ensuring
>   in-order delivery.  While the UAC will increment the CSeq header upon
>   the transmission of new INFO messages, the UAS cannot use the CSeq to
>   determine the sequence of INFO information.  This is due to the fact
>   that there could be gaps in the INFO message CSeq count caused by a
>   user agent sending re-INVITES or other SIP messages."
> 
> 
> This is not entirely accurate: SIP guarantees that INFO messages are 
> never delivered out-of-sequence. Only in case of *overlapping INFO 
> requests* (i.e. sending a next one before having received a final 
> response for the previous one) it cannot be guaranteed that all are 
> received.
> 
> The partial event mechanism (RFC5263) includes a 'version' attribute to 
> detect such gaps. In case of INFO events, I think it is better to simply 
> say: the UAC MUST NOT send an INFO request with a given event type when 
> a previous INFO request containing that event type has not yet received 
> a final response.
> 
> Regards,
> Jeroen
> 
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Sat Oct 25 08:08:10 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 352A83A689D;
	Sat, 25 Oct 2008 08:08:10 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D4B523A689D
	for <sip@core3.amsl.com>; Sat, 25 Oct 2008 08:08:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XehJdoaaKqgM for <sip@core3.amsl.com>;
	Sat, 25 Oct 2008 08:08:05 -0700 (PDT)
Received: from mail-gx0-f16.google.com (mail-gx0-f16.google.com
	[209.85.217.16])
	by core3.amsl.com (Postfix) with ESMTP id 0196A3A67FB
	for <sip@ietf.org>; Sat, 25 Oct 2008 08:08:04 -0700 (PDT)
Received: by gxk9 with SMTP id 9so838770gxk.13
	for <sip@ietf.org>; Sat, 25 Oct 2008 08:09:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:mime-version:content-type:content-transfer-encoding
	:content-disposition;
	bh=Fl8CqqdTbvSe24HUMAaBjllgXQRF8Drxi/p6ImvMHs8=;
	b=Uvs9aL7Xl16Op5fUmc4UnqWGdtfBhGR8+EoRvT8xKXpN1TMQUSGeCeRxGpnhD19SZi
	FnHt79sTGhWihPuCbnBz45EGk0VNF/jedqo/8b9g2uL08OWQwXSCOtIi1mC+BluF8sYH
	hZYIR4hVfsS4lGCBfBKNOT5p+Aw3rt5Ws3Iqg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:mime-version:content-type
	:content-transfer-encoding:content-disposition;
	b=MXXDsD+No0fJmJrSX636BKH/jkWXhGpWLCAdCQc5fEohX6UHXVaaTp8NMIWTCslox+
	2H4sc7l6rJkV7rEaMY6aR7qGh4XXzDFO6De4SRIzoz1spwyS/PNYJPei6LCIlSyBYNO5
	pUCpOK/38Ek6ciVzdGRQY3UQbNqxiBDMvPb8g=
Received: by 10.90.49.3 with SMTP id w3mr2407802agw.80.1224947368819;
	Sat, 25 Oct 2008 08:09:28 -0700 (PDT)
Received: by 10.90.114.2 with HTTP; Sat, 25 Oct 2008 08:09:28 -0700 (PDT)
Message-ID: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
Date: Sat, 25 Oct 2008 17:09:28 +0200
From: "=?UTF-8?Q?Victor_Pascual_=C3=81vila?=" <victor.pascual.avila@gmail.com>
To: sip@ietf.org
MIME-Version: 1.0
Content-Disposition: inline
Subject: [Sip] submission of a new I-D: "Dialog Event foR Identity
	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

SGkgYWxsLAoKQSBuZXcgSS1ELCBkcmFmdC1rdXRoYW4tc2lwLWRlcml2ZS0wMCwgd2FzIGp1c3Qg
c3VibWl0dGVkLiBZb3VyCmNvbW1lbnRzIGFyZSBhbHdheXMgd2VsY29tZS4KCkZpbGVuYW1lOiAg
ICAgICAgICBkcmFmdC1rdXRoYW4tc2lwLWRlcml2ZQpWZXJzaW9uOiAgICAgICAgICAgMDAKU3Rh
Z2luZyBVUkw6Cmh0dHA6Ly93d3czLmlldGYub3JnL3Byb2NlZWRpbmdzL3N0YWdpbmcvZHJhZnQt
a3V0aGFuLXNpcC1kZXJpdmUtMDAudHh0ClRpdGxlOiAgICAgICAgICAgICBEaWFsb2cgRXZlbnQg
Zm9SIElkZW50aXR5IFZFcmlmaWNhdGlvbgpDcmVhdGlvbl9kYXRlOiAgICAgMjAwOC0xMC0yNQpX
RyBJRDogICAgICAgICAgICAgSW5kdmlkdWFsIFN1Ym1pc3Npb24KTnVtYmVyX29mX3BhZ2VzOiAy
NApBYnN0cmFjdDoKVGhpcyBkb2N1bWVudCBwcm92aWRlcyBhIHNpbXBsZSBtZWNoYW5pc20gdG8g
cHJldmVudCBhbiBhdHRhY2tlciBmcm9tCnByZXNlbnRpbmcgYSBmb3JnZWQgIkZyb20iIGhlYWRl
ciBmaWVsZC4gIEl0IG9mZmVycyBhbiBlbmQtdG8tZW5kCmlkZW50aXR5IGFzc3VtcHRpb24gd2hp
Y2ggZG9lcyBub3QgcmVxdWlyZSBhbnkgcHJldmlvdXMgYXNzb2NpYXRpb24Kb3IgdHJ1c3QgcmVs
YXRpb25zaGlwIGJldHdlZW4gYWRtaW5pc3RyYXRpdmUgZG9tYWlucyBvciB0aGUgVUFzLiAgVGhl
ClVBUyB2ZXJpZmllcyB0aGUgIkZyb20iIGhlYWRlciBieSBzdWJzY3JpYmluZyB0byB0aGUgRGlh
bG9nIEV2ZW50CnBhY2thZ2UgW1JGQyA0MjM1XSBhdCB0aGUgQU9SIGluIHRoZSAiRnJvbSIgaGVh
ZGVyIGZpZWxkLiAgSWYgdGhlCmVudGl0eSBjYWxsaW5nIGlzIHJlZ2lzdGVyZWQgdW5kZXIgdGhp
cyBBT1IsIGl0IHdpbGwgY29uZmlybSB0aGF0IGl0CmlzIGNhbGxpbmcgYnkgc2VuZGluZyBzb21l
IHZhbGlkIGRpYWxvZyBzdGF0ZS4gIEluIHRoaXMgY2FzZSwgdGhlCmlkZW50aXR5IG9mIHRoZSBj
YWxsZXIgaXMgY29uc2lkZXJlZCB0byBiZSB2ZXJpZmllZC4KClN1Ym1pdHRlcjogVmljdG9yIFBh
c2N1YWwgKHZpY3RvckBpcHRlbC5vcmcpCgpBdXRob3Iocyk6CkppcmkgS3V0aGFuLCBKaXJpLkt1
dGhhbkB0ZWtlbGVjLmNvbQpEb3JnaGFtIFNpc2FsZW0sIERvcmdoYW0uU2lzYWxlbUB0ZWtlbGVj
LmNvbQpSYXBoYWVsIENvZWZmaWMsIFJhcGhhZWwuQ29lZmZpY0B0ZWtlbGVjLmNvbQpWaWN0b3Ig
UGFzY3VhbCwgVmljdG9yLlBhc2N1YWxAdGVrZWxlYy5jb20KCgpUaGFua3MsCi0tIApWaWN0b3Ig
UGFzY3VhbCDDgXZpbGEKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18KU2lwIG1haWxpbmcgbGlzdCAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9zaXAKVGhpcyBsaXN0IGlzIGZvciBORVcgZGV2ZWxvcG1lbnQgb2YgdGhlIGNvcmUgU0lQ
IFByb3RvY29sClVzZSBzaXAtaW1wbGVtZW50b3JzQGNzLmNvbHVtYmlhLmVkdSBmb3IgcXVlc3Rp
b25zIG9uIGN1cnJlbnQgc2lwClVzZSBzaXBwaW5nQGlldGYub3JnIGZvciBuZXcgZGV2ZWxvcG1l
bnRzIG9uIHRoZSBhcHBsaWNhdGlvbiBvZiBzaXA=


From sip-bounces@ietf.org  Sat Oct 25 08:56:49 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D82D43A69A0;
	Sat, 25 Oct 2008 08:56:49 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1400C3A6807
	for <sip@core3.amsl.com>; Sat, 25 Oct 2008 08:56:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5
	tests=[AWL=-0.050, BAYES_00=-2.599, HELO_EQ_SE=0.35,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id g9RHHEJbfBzf for <sip@core3.amsl.com>;
	Sat, 25 Oct 2008 08:56:48 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id BCF9E3A693A
	for <sip@ietf.org>; Sat, 25 Oct 2008 08:56:47 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	60ACF20ED2; Sat, 25 Oct 2008 17:58:10 +0200 (CEST)
X-AuditID: c1b4fb3e-aef86bb00000537b-ca-49034211443e
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	F1DFA20ECF; Sat, 25 Oct 2008 17:58:09 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 25 Oct 2008 17:58:09 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 25 Oct 2008 17:58:09 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se
	[131.160.33.3])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 365E62321;
	Sat, 25 Oct 2008 18:58:09 +0300 (EEST)
Received: from localhost.localdomain (localhost [IPv6:::1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id C43344DC85;
	Sat, 25 Oct 2008 18:58:08 +0300 (EEST)
Message-ID: <49034210.5060803@ericsson.com>
Date: Sat, 25 Oct 2008 18:58:08 +0300
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (X11/20080914)
MIME-Version: 1.0
To: Jeroen van Bemmel <jbemmel@zonnet.nl>
References: <48FDEAD8.8010803@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com>	A	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>	<0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>	<CA9998CD4A020D418654FCDEF4E707DF088F17D5@esealmw113.eemea.ericsson.se>	<5D1A7985295922448D5550C94DE2918002425C2C@DEEXC1U01.de.lucent.com>	<CA9998CD4A020D418654FCDEF4E707DF088F19BA@esealmw113.eemea.ericsson.se>	<49006A58.3090106@cisco.com>
	<490311A6.3090801@zonnet.nl>
In-Reply-To: <490311A6.3090801@zonnet.nl>
X-OriginalArrivalTime: 25 Oct 2008 15:58:09.0423 (UTC)
	FILETIME=[79EE09F0:01C936BA]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>, "Elwell,
	John" <john.elwell@siemens.com>, Dean Willis <dean.willis@softarmor.com>,
	Eric Burger <eburger@bea.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

what happens if an application includes in a multiple packaged INFO 
request a body part the Sever does not understand?
how is the server able to indicate that only a part of the INFO request 
was not understood ?

regards
Sal

Jeroen van Bemmel wrote:
> A possible reason to want multiple packages per INFO request, is that 
> it allows one to construct applications that rely on "all or nothing" 
> semantics for correlated events.
>
> For example, if one would use SIP to implement an application that 
> lets one post a small icon on a blog, and requires an authorization 
> token to do that, both would have to arrive together. Another example 
> could be an electronic variant of a postage stamp (i.e. some token 
> representing some monetary value), when using two different INFOs one 
> might fail to arrive where the other would (i.e. content without 
> payment, or payment without content).
>
> It has to do with certain atomic, transactional behavior and 
> consistency of the user experience
>
> Regards,
> Jeroen
>
> Paul Kyzivat wrote:
>> I also agree it is too extreme to restrict to one package per dialog.
>> But as I stated earlier, I'm fine not defining multiple packages per 
>> INFO.
>>
>>     Paul
>>
>> Christer Holmberg wrote:
>>> Hi,
>>>> I don't have a problem agreeing with that.
>>>>
>>>> Note that buried somewhere in this thread was a question of whether we
>>> had a use case for multiple packages per dialog, or can we simplify 
>>> even
>>> further.
>>>
>>> I don't think we should go that far, because that could become very
>>> restrictive.
>>>
>>> For example, assume I want to use INFO packages e.g. for DTMF during 
>>> the
>>> call setup, and then other INFO package(s) for something else during 
>>> the
>>> call.
>>>
>>> Regards,
>>>
>>> Christer
>>>
>>>
>>>> -----Original Message-----
>>>> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
>>>> Sent: Thursday, October 23, 2008 10:51 AM
>>>> To: Elwell, John; Dean Willis; DRAGE, Keith (Keith)
>>>> Cc: SIP IETF; Eric Burger; Paul Kyzivat
>>>> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple packages 
>>>> per INFO
>>>>
>>>>
>>>> Hi,
>>>>
>>>> I agree with John. Let's keep it simple. If allowing multiple packages
>>>
>>>> in a single INFO causes issues, let's forget about it.
>>>>
>>>> The whole idea with this is to allow people using INFO to do so in 
>>>> an easy and standardized way, so let's not shoot ourselves in the 
>>>> foot with complexity.
>>>>
>>>> Regards,
>>>>
>>>> Christer
>>>>
>>>> -----Original Message-----
>>>> From: Elwell, John [mailto:john.elwell@siemens.com]
>>>> Sent: 23. lokakuuta 2008 12:30
>>>> To: Christer Holmberg; Dean Willis; DRAGE, Keith (Keith)
>>>> Cc: SIP IETF; Eric Burger; Paul Kyzivat
>>>> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple packages 
>>>> per INFO
>>>>
>>>> In reply to this whole thread, please bear in mind that we had lots of
>>>
>>>> discussion about whether it would be worthwhile defining this new INFO
>>>
>>>> mechanism, since existing applications are unlikely to change and 
>>>> the best we can hope for is that new applications will exploit the 
>>>> new mechanism. Therefore we want to keep the mechanism as simple as 
>>>> possible. The complexities of matching body parts to header fields, 
>>>> dealing with cases where only some of the packages are understood, 
>>>> etc.
>>>> are hardly likely to persuade people to implement the mechanism. 
>>>> Please keep it simple.
>>>>
>>>> John
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
>>>> Behalf Of
>>>>> Christer Holmberg
>>>>> Sent: 23 October 2008 08:17
>>>>> To: Dean Willis; DRAGE, Keith (Keith)
>>>>> Cc: SIP IETF; Eric Burger; Paul Kyzivat
>>>>> Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple 
>>>>> packages per INFO
>>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>>>> Why does putting two different packages in the same INFO
>>>>> work better
>>>>>>> than two different INFO messages each with their own
>>>>> package usage? Is
>>>>>
>>>>>>> there a desirable relationship that can be implemented
>>>>> between the two
>>>>>
>>>>>>> that we would otherwise lose?
>>>>>> We have one package per NOTIFY. Let's stick with one package
>>>>> per INFO,
>>>>> unless we want to go back to using mime-types as the only 
>>>>> distinguisher of packages.
>>>>>
>>>>> I raised that issue in another e-mail.
>>>>>
>>>>> But, never the less, I have no strong feelings on the single 
>>>>> versus multiple package issue.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Christer
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>>>> This list is for NEW development of the core SIP Protocol Use 
>>>>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>>>>> sipping@ietf.org for new developments on the application of sip
>>>>>
>>>
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sipping@ietf.org for new developments on the application of sip
>>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>

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


From sip-bounces@ietf.org  Sat Oct 25 09:17:31 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AE44E28C15E;
	Sat, 25 Oct 2008 09:17:31 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 34A5A28C1E5
	for <sip@core3.amsl.com>; Sat, 25 Oct 2008 09:17:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.564
X-Spam-Level: 
X-Spam-Status: No, score=-2.564 tagged_above=-999 required=5 tests=[AWL=0.035, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AA9g3rqYLS94 for <sip@core3.amsl.com>;
	Sat, 25 Oct 2008 09:17:29 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id 0441D28C1AF
	for <sip@ietf.org>; Sat, 25 Oct 2008 09:17:28 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K9A00M6SYND5L@siemenscomms.co.uk> for sip@ietf.org; Sat,
	25 Oct 2008 17:18:49 +0100 (BST)
Date: Sat, 25 Oct 2008 17:18:47 +0100
From: "Elwell, John" <john.elwell@siemens.com>
To: SIP IETF <sip@ietf.org>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D001349A65@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: More on SIP Identity
Thread-Index: Ack2vVvyBZZTDq83RV6rAthGRy4+XA==
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Subject: [Sip] More on SIP Identity
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

First, I have revised the E.164 problem statement draft, which had
expired. The only changes are a clarification to the introduction
concerning E.164 number formats and an addition to the sentence on
number portability in 2.1:
http://www.ietf.org/internet-drafts/draft-elwell-sip-e164-problem-statem
ent-01.txt

Second, I have revised the e2e identity important draft, just to capture
(near the end of section 2.4), a set of arguments Hadriel gave for not
re-signing at intermediaries:
http://www.ietf.org/internet-drafts/draft-elwell-sip-e2e-identity-import
ant-01.txt

Third, a reminder that there were thoughts expressed in Dublin that we
should capture in a draft considerations about how a UA should handle
received identity information. A first attempt at this is in:
http://www.ietf.org/internet-drafts/draft-elwell-sip-identity-handling-u
a-00.txt

Also there are other drafts on the subject from Hadriel Kaplan, Kai
Fischer, Dan Wing and others, mostly expired.

Finally, where do we stand on this whole topic? It is known that certain
SIP intermediaries (B2BUAs, SBCs) break RFC 4474 signatures. In some
cases the reasons for such modification are considered doubtful, but in
other cases there may be justification.

During the Dublin session we focused on a particular problem caused by
B2BUAs/SBCs, that of media steering. This is known to break RFC 4474
signatures (since it involves changing IP addresses and ports in SDP).
There was no conclusion as to whether this is indeed a justified
modification, whether it is a problem that needs solving, and what to do
about it.

It was also asked whether there are other potentially justified
behaviours of intermediaries that break RFC 4474 signatures.

One possible candidate is codec selection, whereby an intermediary
removes from an SDP offer those codecs that fall outside policy or for
which bandwidth is not currently available.

Another possible candidate is topology hiding, by changing Call-Id
values to hide information.

Yet another possible candidate is changing Cseq values, to compensate
for 3PCC actions.

I think we need to get a complete list of such behaviours and assess to
what extent they are justified (and therefore the importance of finding
a solution to the problems that arise). So I would welcome more
discussion on the subject prior to Minneapolis.

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


From sip-bounces@ietf.org  Sat Oct 25 09:20:14 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 77E3C28C145;
	Sat, 25 Oct 2008 09:20:14 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E6A1C28C1AB
	for <sip@core3.amsl.com>; Sat, 25 Oct 2008 09:20:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.293
X-Spam-Level: 
X-Spam-Status: No, score=-6.293 tagged_above=-999 required=5
	tests=[AWL=-0.044, BAYES_00=-2.599, HELO_EQ_SE=0.35,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YMXvi4VRj4eR for <sip@core3.amsl.com>;
	Sat, 25 Oct 2008 09:20:13 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id BB91C28C12B
	for <sip@ietf.org>; Sat, 25 Oct 2008 09:20:12 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	33EA6206FD; Sat, 25 Oct 2008 18:21:36 +0200 (CEST)
X-AuditID: c1b4fb3c-ae0cebb0000015b5-91-490347901805
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	13CDC203D6; Sat, 25 Oct 2008 18:21:36 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 25 Oct 2008 18:21:35 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 25 Oct 2008 18:21:35 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se
	[131.160.33.3])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id A63952321;
	Sat, 25 Oct 2008 19:21:35 +0300 (EEST)
Received: from localhost.localdomain (localhost [IPv6:::1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 779814DC85;
	Sat, 25 Oct 2008 19:21:35 +0300 (EEST)
Message-ID: <4903478E.9040402@ericsson.com>
Date: Sat, 25 Oct 2008 19:21:34 +0300
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (X11/20080914)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
References: <20081020231502.43DCA3A69EF@core3.amsl.com>
	<48FDECB5.3030607@cisco.com>
In-Reply-To: <48FDECB5.3030607@cisco.com>
X-OriginalArrivalTime: 25 Oct 2008 16:21:35.0816 (UTC)
	FILETIME=[C0349480:01C936BD]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Legacy usage of INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

the following paragraph of Section 5.2 puzzles me:

   If a server receives an INFO request with a body it understands, but
   it has no Info-Package header, the UAS MAY render the body.  Note the
   semantics of "rendering" is up to the Info Package definition.  The
   UAS MUST respond to the INFO request with a 200 OK.  This enables
   legacy use of INFO.


Now it states that is to enable legacy use of INFO, but at same time 
refer to the Info Package definition
that is something only for the new usage.

IMO with this text it would be possible send also an INFO request the 
other end is not willing to receive,
it is enough not include the Info-Package header. Is this can be seen as 
a possible security problem?

Thanks
Sal


Paul Kyzivat wrote:
> While I see rules in 5.1 and 6 that permit use of legacy packages at 
> the INFO UAS, I find no rules that permit sending a legacy INFO. I 
> guess it must be possible to use legacy INFO even when both sides 
> support this new info package mechanism. And I guess the evidence that 
> a UA *doesn't* support this new mechanism (by the absence of the 
> headers in request/response) is just equivalent to one that explicitly 
> negotiates support of no packages.
>
> Regarding registration if INFO packages - I thought we also wanted to 
> introduce a registry for legacy usages of INFO, to encourage them to 
> come out into the daylight. I guess maybe that would be a separate 
> registry, since the key for it will have to be Content-Type. So it 
> *could* be established from a different document. But I think this is 
> the likely place to do it, since its the place where all the eyeballs 
> will be. I think the rule for registering those needs to be that one 
> can only be registered if the Content-Type has not already been 
> registered, and it was in *use* with INFO prior to this document 
> becoming an RFC. (The registration itself could be done later. I guess 
> it would be the honor system.) Any usages being deployed after this 
> becomes an RFC would be required to use the new mechanism.
>
> Thanks,
> Paul
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Sip mailing list https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>

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


From sip-bounces@ietf.org  Sat Oct 25 09:23:58 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 51C7828C1D4;
	Sat, 25 Oct 2008 09:23:58 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A83EB28C1AF
	for <sip@core3.amsl.com>; Sat, 25 Oct 2008 09:23:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.289
X-Spam-Level: 
X-Spam-Status: No, score=-6.289 tagged_above=-999 required=5
	tests=[AWL=-0.040, BAYES_00=-2.599, HELO_EQ_SE=0.35,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id cOV3CU1WON95 for <sip@core3.amsl.com>;
	Sat, 25 Oct 2008 09:23:57 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id D80F128C1AB
	for <SIP@ietf.org>; Sat, 25 Oct 2008 09:23:56 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	7C5B4204DC; Sat, 25 Oct 2008 18:25:20 +0200 (CEST)
X-AuditID: c1b4fb3c-ac0cabb0000015b5-b3-49034870576d
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	59969203D6; Sat, 25 Oct 2008 18:25:20 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 25 Oct 2008 18:25:20 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 25 Oct 2008 18:25:19 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se
	[131.160.33.3])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id 865772321;
	Sat, 25 Oct 2008 19:25:18 +0300 (EEST)
Received: from localhost.localdomain (localhost [IPv6:::1])
	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 46C634DC85;
	Sat, 25 Oct 2008 19:25:16 +0300 (EEST)
Message-ID: <4903486B.6050502@ericsson.com>
Date: Sat, 25 Oct 2008 19:25:15 +0300
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (X11/20080914)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
References: <C9685920-CA2B-435A-9FA9-767BE5085AB6@standardstrack.com>
	<4901D477.5010209@cisco.com>
In-Reply-To: <4901D477.5010209@cisco.com>
X-OriginalArrivalTime: 25 Oct 2008 16:25:19.0430 (UTC)
	FILETIME=[457D5E60:01C936BE]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <SIP@ietf.org>
Subject: Re: [Sip] INFO Events Replacing or Updating INFO?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I agree with Paul

Sal

Paul Kyzivat wrote:
>
>
> Eric Burger wrote:
>
>> [X] INFO Events should Obsolete RFC 2976
>> [ ] INFO Events should Update RFC 2796, because ____________
>> [ ] I do not care what you do
>
> But of course the new document must carefully define backward 
> compatible behavior. Its made a stab at that, and I expect it to be 
> complete before approval.
>
>     Thanks,
>     Paul
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>

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


From sip-bounces@ietf.org  Sat Oct 25 10:02:05 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2F77928C20B;
	Sat, 25 Oct 2008 10:02:05 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5DD2D28C20B
	for <sip@core3.amsl.com>; Sat, 25 Oct 2008 10:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.572
X-Spam-Level: 
X-Spam-Status: No, score=-5.572 tagged_above=-999 required=5
	tests=[AWL=-0.370, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QFEUwUYNrCHb for <sip@core3.amsl.com>;
	Sat, 25 Oct 2008 10:01:54 -0700 (PDT)
Received: from exprod6og112.obsmtp.com (exprod6og112.obsmtp.com [64.18.1.29])
	by core3.amsl.com (Postfix) with ESMTP id 1B9AD28C1DB
	for <sip@ietf.org>; Sat, 25 Oct 2008 10:01:52 -0700 (PDT)
Received: from source ([192.150.8.22]) by exprod6ob112.postini.com
	([64.18.5.12]) with SMTP; Sat, 25 Oct 2008 10:03:16 PDT
Received: from inner-relay-3.eur.adobe.com (inner-relay-3b [10.128.4.236])
	by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	m9PH3DE0003006; Sat, 25 Oct 2008 10:03:14 -0700 (PDT)
Received: from apacmail.pac.adobe.com (apacmail.pac.adobe.com [130.248.36.99])
	by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id
	m9PH34EL027831; Sat, 25 Oct 2008 10:03:11 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by
	apacmail.pac.adobe.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 26 Oct 2008 02:03:03 +0900
Received: from 10.7.240.145 ([10.7.240.145]) by namail5.corp.adobe.com
	([10.8.192.88]) with Microsoft Exchange Server HTTP-DAV ; 
	Sat, 25 Oct 2008 17:03:00 +0000
User-Agent: Microsoft-Entourage/12.13.0.080930
Date: Sat, 25 Oct 2008 12:02:59 -0500
From: Henry Sinnreich <hsinnrei@adobe.com>
To: <Jiri.Kuthan@tekelec.com>, <Dorgham.Sisalem@tekelec.com>,
	<Raphael.Coeffic@tekelec.com>, <Victor.Pascual@tekelec.com>,
	SIP IETF <sip@ietf.org>
Message-ID: <C528BB73.9465%hsinnrei@adobe.com>
Thread-Topic: draft-kuthan-sip-derive
Thread-Index: Ack2w4hM/9fAhyb0xEiu+9CpPTWQdg==
Mime-version: 1.0
X-OriginalArrivalTime: 25 Oct 2008 17:03:03.0058 (UTC)
	FILETIME=[8AB79720:01C936C3]
Subject: [Sip] draft-kuthan-sip-derive
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2118580983=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

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

--===============2118580983==
Content-type: multipart/alternative;
	boundary="B_3307780980_929907"

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

--B_3307780980_929907
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

The =8CDialog Event foR Identity Verification=B9 is meeting IMO the real need
for preventing forged =B3From=B2 names and has the virtue of simplicity as well=
.
It is analog to the email verification which is  successfully deployed
throughout the Internet at present.

 http://www3.ietf.org/proceedings/staging/draft-kuthan-sip-derive-00.txt

Thanks, Henry


--B_3307780980_929907
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>draft-kuthan-sip-derive</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:14pt=
'>The &#8216;</SPAN></FONT><SPAN STYLE=3D'font-size:14pt'><FONT FACE=3D"Consolas=
, Courier New, Courier">Dialog Event foR Identity Verification&#8217; is mee=
ting IMO the real need for preventing forged &#8220;From&#8221; names and ha=
s the virtue of simplicity as well. <BR>
It is analog to the email verification which is &nbsp;successfully deployed=
 throughout the Internet at present.<BR>
<BR>
&nbsp;<FONT COLOR=3D"#0000FF"><U><a href=3D"http://www3.ietf.org/proceedings/st=
aging/draft-kuthan-sip-derive-00.txt">http://www3.ietf.org/proceedings/stagi=
ng/draft-kuthan-sip-derive-00.txt</a><BR>
<BR>
</U></FONT>Thanks, Henry<FONT COLOR=3D"#0000FF"><U><BR>
</U></FONT></FONT></SPAN>
</BODY>
</HTML>


--B_3307780980_929907--


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

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



From sip-bounces@ietf.org  Sat Oct 25 10:24:58 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8C9983A69FC;
	Sat, 25 Oct 2008 10:24:58 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 472DE28B797
	for <sip@core3.amsl.com>; Sat, 25 Oct 2008 10:24:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.032
X-Spam-Level: 
X-Spam-Status: No, score=-2.032 tagged_above=-999 required=5 tests=[AWL=0.267, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id cZ1SDxeZn9DV for <sip@core3.amsl.com>;
	Sat, 25 Oct 2008 10:24:56 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.24])
	by core3.amsl.com (Postfix) with ESMTP id D1BD63A68A4
	for <sip@ietf.org>; Sat, 25 Oct 2008 10:24:55 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 9so634039eyd.31
	for <sip@ietf.org>; Sat, 25 Oct 2008 10:26:18 -0700 (PDT)
Received: by 10.210.45.14 with SMTP id s14mr4080090ebs.72.1224955577618;
	Sat, 25 Oct 2008 10:26:17 -0700 (PDT)
Received: from portatil.local (240.pool85-58-8.dynamic.orange.es [85.58.8.240])
	by mx.google.com with ESMTPS id 7sm2502042eyg.0.2008.10.25.10.26.15
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Sat, 25 Oct 2008 10:26:16 -0700 (PDT)
From: =?utf-8?q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: sip@ietf.org
Date: Sat, 25 Oct 2008 19:26:17 +0200
User-Agent: KMail/1.9.9
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810251926.17644.ibc@aliax.net>
Subject: [Sip] [RFC 4235 & draft-kuthan-sip-derive] 481 "Call doesn't exist"
	for initial SUBSCRIBE ?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

SGksIEkndmUgYSBkb3VidCBhYm91dCB3aGF0IHNob3VsZCBiZSB0aGUgY29ycmVjdCByZXNwb25z
ZSBmb3IgYW4gaW5pdGlhbCAKU1VCU0NSSUJFIChFdmVudDogZGlhbG9nKSBpZiB0aGUgaW5kaWNh
dGVkIGRpYWxvZyBkb2Vzbid0IGV4aXN0IGluIHRoZSAKcmVjaXBpZW50IG9mIHRoZSBTVUJTQ1JJ
QkUuCgpUaGlzIGRvdWJ0IGNvbWVzIGFmdGVyIHJlYWRpbmcgdGhlIHRvZGF5IHN1Ym1pdHRlZCBk
cmFmdCAiRGlhbG9nIEV2ZW50IGZvUiAKSWRlbnRpdHkgVkVyaWZpY2F0aW9uIjoKICBodHRwOi8v
d3d3My5pZXRmLm9yZy9wcm9jZWVkaW5ncy9zdGFnaW5nL2RyYWZ0LWt1dGhhbi1zaXAtZGVyaXZl
LTAwLnR4dAoKSW4gcGFnZSAxNCBvZiB0aGlzIGRyYWZ0IHRoZXJlIGlzIGEgZmxvdyBhYm91dCBh
IHN1c3BpY2lvdXMgY2FsbCAoc3Bvb2ZlZCAKRnJvbSkuIFRoZSBmbG93IGlzIGNvcnJlY3RseSBk
aXNwbGF5ZWQgdXNpbmcgZml4ZWQgbGVuZ3RoIHR5cG9ncmFwaHksIGlmIGl0J3MgCm5vdCB5b3Vy
IGNhc2UgcmVmZXIgdG8gcGFnZSAxNCBvZiB0aGUgZHJhZnQuCgoKICAgIEF0dGFja2VyICAgICAg
ICBBbGljZSAgIFByb3h5IDEgKGF0bGFudGEuY29tKSBQcm94eSAyIChiaWxveGkuY29tKSBCb2IK
ICAgIHwgICAgICAgICAgICAgICB8IElOVklURSBGNSAgICAgIHwgICAgICAgICAgICAgICAgfCAg
ICAgICAgICAgICAgICB8CiAgICB8LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tPnwgICAgICAgICAgICAgICAgfAogICAgfCAgICAgICAgICAgICAgIHwgMTAw
IEY2ICAgICAgICAgfCAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgIHwKICAgIHw8LS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tfCBJTlZJVEUgRjcg
ICAgICB8CiAgICB8ICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICB8ICAgICAgICAgICAg
ICAgIHwtLS0tLS0tLS0tLS0tLS0+fAogICAgfCAgICAgICAgICAgICAgIHwgICAgICAgICAgICAg
ICAgfCAgICAgICAgICAgICAgICB8IDEwMCBGOCAgICAgICAgIHwKICAgIHwgICAgICAgICAgICAg
ICB8ICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgfDwtLS0tLS0tLS0tLS0tLS18CiAg
ICB8ICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgIHwgU1VC
U0NSSUJFIEY5ICAgfAogICAgfCAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgfCBTVUJT
Q1JJQkUgRjEwICB8PC0tLS0tLS0tLS0tLS0tLXwKICAgIHwgICAgICAgICAgICAgICB8IFNVQlND
UklCRSBGMTEgIHw8LS0tLS0tLS0tLS0tLS0tfCAgICAgICAgICAgICAgICB8CiAgICB8ICAgICAg
ICAgICAgICAgfDwtLS0tLS0tLS0tLS0tLS18ICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAg
ICAgfAogICAgfCAgICAgICAgICAgICAgIHwgNDgxIEYxMiAgICAgICAgfCAgICAgICAgICAgICAg
ICB8ICAgICAgICAgICAgICAgIHwKICAgIHwgICAgICAgICAgICAgICB8LS0tLS0tLS0tLS0tLS0t
PnwgNDgxIEYxMyAgICAgICAgfCAgICAgICAgICAgICAgICB8CiAgICB8ICAgICAgICAgICAgICAg
fCAgICAgICAgICAgICAgICB8LS0tLS0tLS0tLS0tLS0tPnwgNDgxIEYxNCAgICAgICAgfAogICAg
fCAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICB8LS0tLS0t
LS0tLS0tLS0tPnwKCgpTbywgQm9iIHNlbmRzIGFuIGluaXRpYWwgU1VCU0NSSUJFIHRvIEFsaWNl
IEFvUiAodGhlIHJlY2VpdmVkIEZyb20gdXJpIGluIHRoZSAKSU5WSVRFIEY1L0Y3KSB3aXRoIHRo
ZSBoYWxmLWRpYWxvZyBkYXRhOgoKICAgU1VCU0NSSUJFIHNpcDphbGljZUBhdGxhbnRhLmNvbSBT
SVAvMi4wCiAgIEZyb206IEJvYiA8c2lwOkJvYkBiaWxveGkuY29tPjt0YWc9ODY3MjM0OQogICBU
bzogPHNpcDphbGljZUBhdGxhbnRhLmNvbT4KICAgQ2FsbC1JRDogeHQ0NjUzZ3MyaGFtQGJpbG94
aS5jb20KICAgQ29udGFjdDogPHNpcDpib2JAY2xpZW50LmJpbG94eS5jb20+CiAgIEV2ZW50OiBk
aWFsb2c7Y2FsbC1pZD0zODQ4Mjc2Mjk4MjIwMTg4NTExQGF0bGFudGEuY29tO3RvLXRhZz05Znhj
ZWQ3NnNsCiAgIEV4cGlyZXM9MAogICBBY2NlcHQ6IGFwcGxpY2F0aW9uL2RpYWxvZy1pbmZvK3ht
bAogICBDb250ZW50LUxlbmd0aDogMAoKTm90ZSB0aGF0ICJFdmVudCIgaGVhZGVyIGNvbnRhaW5z
IHNwZWNpZmljIGhhbGYtZGlhbG9nIGluZm9ybWF0aW9uLgoKVGhpcyBTVUJTQ1JJQkUgYXJyaXZl
cyB0byBBbGljZSdzIFVBIHdoaWNoIGlzIG5vdCBhd2FyZSBvZiB0aGF0IGRpYWxvZy4gV2hpY2gg
CnJlc3BvbnNlIHNob3VsZCBpdCByZXBseT8gVGhlIGZsb3cgc3VnZ2VzdHMgIjQ4MSBDYWxsL1Ry
YW5zYWN0aW9uIGRvZXNuJ3QgCmV4aXN0IiwgYnV0Li4uIGlzIGl0IGNvcnJlY3Q/CgpBRkFJSywg
YSA0ODEgc2hvdWxkIGJlIHJlcGxpZWQgd2hlbiBhbiAqaW4tZGlhbG9nKiByZXF1ZXN0IGFycml2
ZXMgdG8gYW4gVUFTIAp3aGljaCBpcyBub3QgYXdhcmUgb2YgdGhhdCBkaWFsb2cuIEJ1dCBpbiB0
aGUgYWJvdmUgY2FzZSB3ZSBoYXZlIGFuICppbml0aWFsKiAKcmVxdWVzdCBhbmQgdGhlIDQ4MSBy
ZWZlcnMgdG8gdGhlIHNwZWNpZmljIGRpYWxvZyBpbiB0aGUgIkV2ZW50IiBoZWFkZXIuCgoKV2Vs
bCwgSSBzdWdnZXN0IGEgcG9zc2libGUgaXNzdWUgd2l0aCB0aGUgYWJvdmUgYmVoYXZpb3VyOgoK
LSBBbGljZSBpbnZpdGVzIEJvYi4KLSBCZWZvcmUgc2VuZGluZyBhIHByb3Zpc2lvbmFsIHJlc3Bv
bnNlLCBCb2Igc2VuZHMgYW4gKmluaXRpYWwqIFNVQlNDUklCRSB0byAKQWxpY2Ugd2l0aCB0aGUg
Y3VycmVudCBoYWxmLWRpYWxvZyBpbmZvcm1hdGlvbiBpbiB0aGUgIkV2ZW50IiBoZWFkZXIuCi0g
QWxpY2UgYWNjZXB0cyB0aGUgU1VCU0NSSUJFLCByZXBsaWVzIDIwMCBhbmQgbGF0ZXIgYSBOT1RJ
Rlkgd2l0aCB0aGUgCnNwZWNpZmljIGRpYWxvZyBzdGF0dXMuCgphKQotIEFmdGVyIDQwIHNlY29u
ZHMgQWxpY2UncyBVQSBjcmFzaGVzIGFuZCBpcyByZXN0YXJ0ZWQgKGRpYWxvZyBpbmZvIGxvc3Qp
LgotIEJvYiBzZW5kcyBhIFNVQlNDUklCRSByZWZyZXNoIChhbiBpbi1kaWFsb2cgcmVxdWVzdCku
Ci0gVGhhdCBkaWFsb2cgKHRoZSBTVUJTQ1JJQkUgZGlhbG9nKSBkb2Vzbid0IGV4aXN0IGluIEFs
aWNlIGFueW1vcmUsIHNvIEFsaWNlIApyZXBsaWVzIDQ4MS4KCmIpCi0gRGlhbG9nIGJldHdlZW4g
QWxpY2UgYW5kIEJvYiBlbmRzIGJlY2F1c2UgQWxpY2Ugc2VuZHMgYSBCWUUsIGJ1dCBiZWZvcmUg
CkFsaWNlIHJlY2VpdmVzIHRoZSBCWUUgYW5kIHRoZSBkaWFsb2cgTk9USUZZIHVwZGF0ZSwgQm9i
IHNlbmRzIGEgU1VCU0NSSUJFIApyZWZyZXNoIChhbiBpbi1kaWFsb2cgcmVxdWVzdCkgZm9yIHRo
YXQgZGlhbG9nLgotIFRoaXMgU1VCU0NSSUJFIGFycml2ZXMgdG8gQWxpY2UsIHRoZSBTVUJTQ1JJ
QkUgcmVxdWVzdCBkaWFsb2cgZXhpc3RzIGJ1dCB0aGUgCmRpYWxvZyBpbmRpY2F0ZWQgaW4gIkV2
ZW50IiBoZWFkZXIgZG9lc24ndCBleGlzdCBhbnltb3JlLgotIEFzIHRoZSBhYm92ZSBmbG93IHN1
Z2dlc3RzLCBBbGljZSByZXBsaWVzIDQ4MS4KCkluIGJvdGggY2FzZXMgYSkgYW5kIGIpLCBBbGlj
ZSByZXBsaWVzIDQ4MSBidXQgdGhlIHNjZW5hcmlvIGlzIGNvbXBsZXRlbHkgCmRpZmZlcmVudC4g
VGhlIDQ4MSBpbiBhKSBtZWFucyB0aGF0IHRoZSBpbi1kaWFsb2cgU1VCU0NSSUJFIGJlbG9uZ3Mg
dG8gYSBub24gCmV4aXN0aW5nIGRpYWxvZyBpbiBBbGljZSwgd2hpbGUgdGhlIDQ4MSBpbiBiKSBt
ZWFucyB0aGF0IGEgZGlhbG9nIGluZGljYXRlZCAKaW4gdGhlIEV2ZW50IGhlYWRlciBkb2Vzbid0
IGV4aXN0LgpCdXQgdGhlcmUgaXMgbm8gd2F5IGZvciBCb2IgdG8gcmVhbGl6ZSB3aGljaCBpcyB0
aGUgY2FzZSBhKSBvciBiKS4KCgpUaGUgbWFpbiBxdWVzdGlvbiBpczogaXMgNDgxIHRoZSBhcHBy
b2lhdGUgKGFuZCB2YWxpZCkgcmVwbHkgaW4gdGhlIGFib3ZlIGZsb3cgCihjYXNlIGIpPyBJcyA0
ODEgcmVhbGx5IHZhbGlkIGFzIGEgcmVwbHkgZm9yIGFuIGluaXRpYWwgcmVxdWVzdD8KCgoKCi0t
IApJw7Fha2kgQmF6IENhc3RpbGxvCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fClNpcCBtYWlsaW5nIGxpc3QgIGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vc2lwClRoaXMgbGlzdCBpcyBmb3IgTkVXIGRldmVsb3BtZW50IG9mIHRoZSBj
b3JlIFNJUCBQcm90b2NvbApVc2Ugc2lwLWltcGxlbWVudG9yc0Bjcy5jb2x1bWJpYS5lZHUgZm9y
IHF1ZXN0aW9ucyBvbiBjdXJyZW50IHNpcApVc2Ugc2lwcGluZ0BpZXRmLm9yZyBmb3IgbmV3IGRl
dmVsb3BtZW50cyBvbiB0aGUgYXBwbGljYXRpb24gb2Ygc2lw


From sip-bounces@ietf.org  Sat Oct 25 13:32:38 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7ABEC3A6810;
	Sat, 25 Oct 2008 13:32:38 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ABC353A6810
	for <sip@core3.amsl.com>; Sat, 25 Oct 2008 13:32:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.433
X-Spam-Level: 
X-Spam-Status: No, score=-6.433 tagged_above=-999 required=5
	tests=[AWL=-0.134, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id hNnd+AKjIolN for <sip@core3.amsl.com>;
	Sat, 25 Oct 2008 13:32:35 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 2950B3A67AD
	for <sip@ietf.org>; Sat, 25 Oct 2008 13:32:35 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,484,1220227200"; d="scan'208";a="182614482"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 25 Oct 2008 20:34:00 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9PKY0Td015940; 
	Sat, 25 Oct 2008 13:34:00 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9PKXxx5004993;
	Sat, 25 Oct 2008 20:34:00 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 25 Oct 2008 16:33:59 -0400
Received: from [10.86.249.64] ([10.86.249.64]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 25 Oct 2008 16:33:59 -0400
Message-ID: <490382B6.1090400@cisco.com>
Date: Sat, 25 Oct 2008 16:33:58 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: =?UTF-8?B?ScOxYWtpIEJheiBDYXN0aWxsbw==?= <ibc@aliax.net>
References: <200810251926.17644.ibc@aliax.net>
In-Reply-To: <200810251926.17644.ibc@aliax.net>
X-OriginalArrivalTime: 25 Oct 2008 20:33:59.0248 (UTC)
	FILETIME=[0264ED00:01C936E1]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4553; t=1224966840;
	x=1225830840; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20[RFC=204235=20&=20draft-kuthan-
	sip-derive]=20481=20=22Call=20doesn't=0A=20exist=22=09for=20
	initial=20SUBSCRIBE=20? |Sender:=20;
	bh=jaEaSIKAmHAV5ygzSPARMz1vW6aYV8i0sNxXLQATgrc=;
	b=NLwUJN9Lf00Vb1jWZZRXmFfIC8PkkEMyFNO3eR+CBstjSgxqS0Vk6u2lUd
	lwWMIL2ctip72mC2q+vBFTh50ZoXYzZ7xeb123A7q970d5khHG8oIkQk4GTe
	daaOVzickJhrBLS4Zv9Pc0dWHgp+dbuHX2sL+9qF5MA/W5tMiJeGI=;
Authentication-Results: sj-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: sip@ietf.org
Subject: Re: [Sip] [RFC 4235 & draft-kuthan-sip-derive] 481 "Call doesn't
 exist"	for initial SUBSCRIBE ?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

SSBhZ3JlZSB0aGF0IDQ4MSBzZWVtcyBhbiB1bnN1aXRhYmxlIHJlc3BvbnNlIGluIHRoaXMgY2Fz
ZS4KSXRzIG5vdCBjbGVhciB0byBtZSB3aGF0IHJlc3BvbnNlIGlzIGJlc3Qgc3VpdGVkLiBQZXJo
YXBzIDQwMyBvciA2MDMuCgoJVGhhbmtzLAoJUGF1bAoKScOxYWtpIEJheiBDYXN0aWxsbyB3cm90
ZToKPiBIaSwgSSd2ZSBhIGRvdWJ0IGFib3V0IHdoYXQgc2hvdWxkIGJlIHRoZSBjb3JyZWN0IHJl
c3BvbnNlIGZvciBhbiBpbml0aWFsIAo+IFNVQlNDUklCRSAoRXZlbnQ6IGRpYWxvZykgaWYgdGhl
IGluZGljYXRlZCBkaWFsb2cgZG9lc24ndCBleGlzdCBpbiB0aGUgCj4gcmVjaXBpZW50IG9mIHRo
ZSBTVUJTQ1JJQkUuCj4gCj4gVGhpcyBkb3VidCBjb21lcyBhZnRlciByZWFkaW5nIHRoZSB0b2Rh
eSBzdWJtaXR0ZWQgZHJhZnQgIkRpYWxvZyBFdmVudCBmb1IgCj4gSWRlbnRpdHkgVkVyaWZpY2F0
aW9uIjoKPiAgIGh0dHA6Ly93d3czLmlldGYub3JnL3Byb2NlZWRpbmdzL3N0YWdpbmcvZHJhZnQt
a3V0aGFuLXNpcC1kZXJpdmUtMDAudHh0Cj4gCj4gSW4gcGFnZSAxNCBvZiB0aGlzIGRyYWZ0IHRo
ZXJlIGlzIGEgZmxvdyBhYm91dCBhIHN1c3BpY2lvdXMgY2FsbCAoc3Bvb2ZlZCAKPiBGcm9tKS4g
VGhlIGZsb3cgaXMgY29ycmVjdGx5IGRpc3BsYXllZCB1c2luZyBmaXhlZCBsZW5ndGggdHlwb2dy
YXBoeSwgaWYgaXQncyAKPiBub3QgeW91ciBjYXNlIHJlZmVyIHRvIHBhZ2UgMTQgb2YgdGhlIGRy
YWZ0Lgo+IAo+IAo+ICAgICBBdHRhY2tlciAgICAgICAgQWxpY2UgICBQcm94eSAxIChhdGxhbnRh
LmNvbSkgUHJveHkgMiAoYmlsb3hpLmNvbSkgQm9iCj4gICAgIHwgICAgICAgICAgICAgICB8IElO
VklURSBGNSAgICAgIHwgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICB8Cj4gICAgIHwt
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0+fCAgICAgICAg
ICAgICAgICB8Cj4gICAgIHwgICAgICAgICAgICAgICB8IDEwMCBGNiAgICAgICAgIHwgICAgICAg
ICAgICAgICAgfCAgICAgICAgICAgICAgICB8Cj4gICAgIHw8LS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tfCBJTlZJVEUgRjcgICAgICB8Cj4gICAgIHwgICAg
ICAgICAgICAgICB8ICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgfC0tLS0tLS0tLS0t
LS0tLT58Cj4gICAgIHwgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgIHwgICAgICAgICAg
ICAgICAgfCAxMDAgRjggICAgICAgICB8Cj4gICAgIHwgICAgICAgICAgICAgICB8ICAgICAgICAg
ICAgICAgIHwgICAgICAgICAgICAgICAgfDwtLS0tLS0tLS0tLS0tLS18Cj4gICAgIHwgICAgICAg
ICAgICAgICB8ICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgfCBTVUJTQ1JJQkUgRjkg
ICB8Cj4gICAgIHwgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgIHwgU1VCU0NSSUJFIEYx
MCAgfDwtLS0tLS0tLS0tLS0tLS18Cj4gICAgIHwgICAgICAgICAgICAgICB8IFNVQlNDUklCRSBG
MTEgIHw8LS0tLS0tLS0tLS0tLS0tfCAgICAgICAgICAgICAgICB8Cj4gICAgIHwgICAgICAgICAg
ICAgICB8PC0tLS0tLS0tLS0tLS0tLXwgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICB8
Cj4gICAgIHwgICAgICAgICAgICAgICB8IDQ4MSBGMTIgICAgICAgIHwgICAgICAgICAgICAgICAg
fCAgICAgICAgICAgICAgICB8Cj4gICAgIHwgICAgICAgICAgICAgICB8LS0tLS0tLS0tLS0tLS0t
PnwgNDgxIEYxMyAgICAgICAgfCAgICAgICAgICAgICAgICB8Cj4gICAgIHwgICAgICAgICAgICAg
ICB8ICAgICAgICAgICAgICAgIHwtLS0tLS0tLS0tLS0tLS0+fCA0ODEgRjE0ICAgICAgICB8Cj4g
ICAgIHwgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgfC0t
LS0tLS0tLS0tLS0tLT58Cj4gCj4gCj4gU28sIEJvYiBzZW5kcyBhbiBpbml0aWFsIFNVQlNDUklC
RSB0byBBbGljZSBBb1IgKHRoZSByZWNlaXZlZCBGcm9tIHVyaSBpbiB0aGUgCj4gSU5WSVRFIEY1
L0Y3KSB3aXRoIHRoZSBoYWxmLWRpYWxvZyBkYXRhOgo+IAo+ICAgIFNVQlNDUklCRSBzaXA6YWxp
Y2VAYXRsYW50YS5jb20gU0lQLzIuMAo+ICAgIEZyb206IEJvYiA8c2lwOkJvYkBiaWxveGkuY29t
Pjt0YWc9ODY3MjM0OQo+ICAgIFRvOiA8c2lwOmFsaWNlQGF0bGFudGEuY29tPgo+ICAgIENhbGwt
SUQ6IHh0NDY1M2dzMmhhbUBiaWxveGkuY29tCj4gICAgQ29udGFjdDogPHNpcDpib2JAY2xpZW50
LmJpbG94eS5jb20+Cj4gICAgRXZlbnQ6IGRpYWxvZztjYWxsLWlkPTM4NDgyNzYyOTgyMjAxODg1
MTFAYXRsYW50YS5jb207dG8tdGFnPTlmeGNlZDc2c2wKPiAgICBFeHBpcmVzPTAKPiAgICBBY2Nl
cHQ6IGFwcGxpY2F0aW9uL2RpYWxvZy1pbmZvK3htbAo+ICAgIENvbnRlbnQtTGVuZ3RoOiAwCj4g
Cj4gTm90ZSB0aGF0ICJFdmVudCIgaGVhZGVyIGNvbnRhaW5zIHNwZWNpZmljIGhhbGYtZGlhbG9n
IGluZm9ybWF0aW9uLgo+IAo+IFRoaXMgU1VCU0NSSUJFIGFycml2ZXMgdG8gQWxpY2UncyBVQSB3
aGljaCBpcyBub3QgYXdhcmUgb2YgdGhhdCBkaWFsb2cuIFdoaWNoIAo+IHJlc3BvbnNlIHNob3Vs
ZCBpdCByZXBseT8gVGhlIGZsb3cgc3VnZ2VzdHMgIjQ4MSBDYWxsL1RyYW5zYWN0aW9uIGRvZXNu
J3QgCj4gZXhpc3QiLCBidXQuLi4gaXMgaXQgY29ycmVjdD8KPiAKPiBBRkFJSywgYSA0ODEgc2hv
dWxkIGJlIHJlcGxpZWQgd2hlbiBhbiAqaW4tZGlhbG9nKiByZXF1ZXN0IGFycml2ZXMgdG8gYW4g
VUFTIAo+IHdoaWNoIGlzIG5vdCBhd2FyZSBvZiB0aGF0IGRpYWxvZy4gQnV0IGluIHRoZSBhYm92
ZSBjYXNlIHdlIGhhdmUgYW4gKmluaXRpYWwqIAo+IHJlcXVlc3QgYW5kIHRoZSA0ODEgcmVmZXJz
IHRvIHRoZSBzcGVjaWZpYyBkaWFsb2cgaW4gdGhlICJFdmVudCIgaGVhZGVyLgo+IAo+IAo+IFdl
bGwsIEkgc3VnZ2VzdCBhIHBvc3NpYmxlIGlzc3VlIHdpdGggdGhlIGFib3ZlIGJlaGF2aW91cjoK
PiAKPiAtIEFsaWNlIGludml0ZXMgQm9iLgo+IC0gQmVmb3JlIHNlbmRpbmcgYSBwcm92aXNpb25h
bCByZXNwb25zZSwgQm9iIHNlbmRzIGFuICppbml0aWFsKiBTVUJTQ1JJQkUgdG8gCj4gQWxpY2Ug
d2l0aCB0aGUgY3VycmVudCBoYWxmLWRpYWxvZyBpbmZvcm1hdGlvbiBpbiB0aGUgIkV2ZW50IiBo
ZWFkZXIuCj4gLSBBbGljZSBhY2NlcHRzIHRoZSBTVUJTQ1JJQkUsIHJlcGxpZXMgMjAwIGFuZCBs
YXRlciBhIE5PVElGWSB3aXRoIHRoZSAKPiBzcGVjaWZpYyBkaWFsb2cgc3RhdHVzLgo+IAo+IGEp
Cj4gLSBBZnRlciA0MCBzZWNvbmRzIEFsaWNlJ3MgVUEgY3Jhc2hlcyBhbmQgaXMgcmVzdGFydGVk
IChkaWFsb2cgaW5mbyBsb3N0KS4KPiAtIEJvYiBzZW5kcyBhIFNVQlNDUklCRSByZWZyZXNoIChh
biBpbi1kaWFsb2cgcmVxdWVzdCkuCj4gLSBUaGF0IGRpYWxvZyAodGhlIFNVQlNDUklCRSBkaWFs
b2cpIGRvZXNuJ3QgZXhpc3QgaW4gQWxpY2UgYW55bW9yZSwgc28gQWxpY2UgCj4gcmVwbGllcyA0
ODEuCj4gCj4gYikKPiAtIERpYWxvZyBiZXR3ZWVuIEFsaWNlIGFuZCBCb2IgZW5kcyBiZWNhdXNl
IEFsaWNlIHNlbmRzIGEgQllFLCBidXQgYmVmb3JlIAo+IEFsaWNlIHJlY2VpdmVzIHRoZSBCWUUg
YW5kIHRoZSBkaWFsb2cgTk9USUZZIHVwZGF0ZSwgQm9iIHNlbmRzIGEgU1VCU0NSSUJFIAo+IHJl
ZnJlc2ggKGFuIGluLWRpYWxvZyByZXF1ZXN0KSBmb3IgdGhhdCBkaWFsb2cuCj4gLSBUaGlzIFNV
QlNDUklCRSBhcnJpdmVzIHRvIEFsaWNlLCB0aGUgU1VCU0NSSUJFIHJlcXVlc3QgZGlhbG9nIGV4
aXN0cyBidXQgdGhlIAo+IGRpYWxvZyBpbmRpY2F0ZWQgaW4gIkV2ZW50IiBoZWFkZXIgZG9lc24n
dCBleGlzdCBhbnltb3JlLgo+IC0gQXMgdGhlIGFib3ZlIGZsb3cgc3VnZ2VzdHMsIEFsaWNlIHJl
cGxpZXMgNDgxLgo+IAo+IEluIGJvdGggY2FzZXMgYSkgYW5kIGIpLCBBbGljZSByZXBsaWVzIDQ4
MSBidXQgdGhlIHNjZW5hcmlvIGlzIGNvbXBsZXRlbHkgCj4gZGlmZmVyZW50LiBUaGUgNDgxIGlu
IGEpIG1lYW5zIHRoYXQgdGhlIGluLWRpYWxvZyBTVUJTQ1JJQkUgYmVsb25ncyB0byBhIG5vbiAK
PiBleGlzdGluZyBkaWFsb2cgaW4gQWxpY2UsIHdoaWxlIHRoZSA0ODEgaW4gYikgbWVhbnMgdGhh
dCBhIGRpYWxvZyBpbmRpY2F0ZWQgCj4gaW4gdGhlIEV2ZW50IGhlYWRlciBkb2Vzbid0IGV4aXN0
Lgo+IEJ1dCB0aGVyZSBpcyBubyB3YXkgZm9yIEJvYiB0byByZWFsaXplIHdoaWNoIGlzIHRoZSBj
YXNlIGEpIG9yIGIpLgo+IAo+IAo+IFRoZSBtYWluIHF1ZXN0aW9uIGlzOiBpcyA0ODEgdGhlIGFw
cHJvaWF0ZSAoYW5kIHZhbGlkKSByZXBseSBpbiB0aGUgYWJvdmUgZmxvdyAKPiAoY2FzZSBiKT8g
SXMgNDgxIHJlYWxseSB2YWxpZCBhcyBhIHJlcGx5IGZvciBhbiBpbml0aWFsIHJlcXVlc3Q/Cj4g
Cj4gCj4gCj4gCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
ClNpcCBtYWlsaW5nIGxpc3QgIGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v
c2lwClRoaXMgbGlzdCBpcyBmb3IgTkVXIGRldmVsb3BtZW50IG9mIHRoZSBjb3JlIFNJUCBQcm90
b2NvbApVc2Ugc2lwLWltcGxlbWVudG9yc0Bjcy5jb2x1bWJpYS5lZHUgZm9yIHF1ZXN0aW9ucyBv
biBjdXJyZW50IHNpcApVc2Ugc2lwcGluZ0BpZXRmLm9yZyBmb3IgbmV3IGRldmVsb3BtZW50cyBv
biB0aGUgYXBwbGljYXRpb24gb2Ygc2lw


From sip-bounces@ietf.org  Sat Oct 25 14:03:59 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AB2DC3A6886;
	Sat, 25 Oct 2008 14:03:59 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 707CA3A6810
	for <sip@core3.amsl.com>; Sat, 25 Oct 2008 14:03:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.023
X-Spam-Level: 
X-Spam-Status: No, score=-2.023 tagged_above=-999 required=5 tests=[AWL=0.124, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, SARE_SUB_ENC_UTF8=0.152]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 72-BKT2Y589C for <sip@core3.amsl.com>;
	Sat, 25 Oct 2008 14:03:57 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27])
	by core3.amsl.com (Postfix) with ESMTP id CD0DC3A67FB
	for <sip@ietf.org>; Sat, 25 Oct 2008 14:03:55 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 9so681978eyd.31
	for <sip@ietf.org>; Sat, 25 Oct 2008 14:05:19 -0700 (PDT)
Received: by 10.210.117.1 with SMTP id p1mr4293832ebc.95.1224968719266;
	Sat, 25 Oct 2008 14:05:19 -0700 (PDT)
Received: from portatil.local (240.pool85-58-8.dynamic.orange.es [85.58.8.240])
	by mx.google.com with ESMTPS id 3sm2895931eyi.5.2008.10.25.14.05.17
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Sat, 25 Oct 2008 14:05:18 -0700 (PDT)
From: =?utf-8?q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: sip@ietf.org
Date: Sat, 25 Oct 2008 23:05:19 +0200
User-Agent: KMail/1.9.9
References: <200810251926.17644.ibc@aliax.net> <490382B6.1090400@cisco.com>
In-Reply-To: <490382B6.1090400@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810252305.20030.ibc@aliax.net>
Subject: Re: [Sip]
	=?utf-8?q?=5BRFC_4235_=26_draft-kuthan-sip-derive=5D_481_?=
	=?utf-8?q?=22Call_doesn=27t_exist=22_=09for_initial_SUBSCRIBE_=3F?=
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

RWwgU8OhYmFkbywgMjUgZGUgT2N0dWJyZSBkZSAyMDA4LCBQYXVsIEt5eml2YXQgZXNjcmliacOz
Ogo+IEkgYWdyZWUgdGhhdCA0ODEgc2VlbXMgYW4gdW5zdWl0YWJsZSByZXNwb25zZSBpbiB0aGlz
IGNhc2UuCj4gSXRzIG5vdCBjbGVhciB0byBtZSB3aGF0IHJlc3BvbnNlIGlzIGJlc3Qgc3VpdGVk
LiBQZXJoYXBzIDQwMyBvciA2MDMuCgpJIHN1cHBvc2UgNDA0IGlzIGFsc28gdW5hcHByb3BpYXRl
LCBpc24ndD8KCi0tIApJw7Fha2kgQmF6IENhc3RpbGxvCl9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fClNpcCBtYWlsaW5nIGxpc3QgIGh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vc2lwClRoaXMgbGlzdCBpcyBmb3IgTkVXIGRldmVsb3Bt
ZW50IG9mIHRoZSBjb3JlIFNJUCBQcm90b2NvbApVc2Ugc2lwLWltcGxlbWVudG9yc0Bjcy5jb2x1
bWJpYS5lZHUgZm9yIHF1ZXN0aW9ucyBvbiBjdXJyZW50IHNpcApVc2Ugc2lwcGluZ0BpZXRmLm9y
ZyBmb3IgbmV3IGRldmVsb3BtZW50cyBvbiB0aGUgYXBwbGljYXRpb24gb2Ygc2lw


From sip-bounces@ietf.org  Sat Oct 25 14:54:11 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 89CCB3A6929;
	Sat, 25 Oct 2008 14:54:11 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C238A3A67AD
	for <sip@core3.amsl.com>; Sat, 25 Oct 2008 14:54:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id H6QBxGdeHjZ9 for <sip@core3.amsl.com>;
	Sat, 25 Oct 2008 14:54:08 -0700 (PDT)
Received: from mail.iptel.org (smtp.iptel.org [213.192.59.67])
	by core3.amsl.com (Postfix) with ESMTP id 43B8F3A689D
	for <sip@ietf.org>; Sat, 25 Oct 2008 14:54:08 -0700 (PDT)
Received: from jiri-kuthans-macbook-pro-8.local (shell.iptel.org
	[213.192.59.74])
	by mail.iptel.org (Postfix) with ESMTP id 0A00B1810C14;
	Sat, 25 Oct 2008 23:55:32 +0200 (CEST)
Message-ID: <490395D3.2010303@iptel.org>
Date: Sat, 25 Oct 2008 23:55:31 +0200
From: Jiri Kuthan <jiri@iptel.org>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Henry Sinnreich <hsinnrei@adobe.com>
References: <C528BB73.9465%hsinnrei@adobe.com>
In-Reply-To: <C528BB73.9465%hsinnrei@adobe.com>
Cc: SIP IETF <sip@ietf.org>, Raphael.Coeffic@tekelec.com,
	Victor.Pascual@tekelec.com, Dorgham.Sisalem@tekelec.com,
	Jiri.Kuthan@tekelec.com
Subject: Re: [Sip] draft-kuthan-sip-derive
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="windows-1252"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

well, first of all, thank you very much for the positive comments.

secondly -- real is becoming really real :) In Germany, there has been
recently an attack that could have been better absorbed using such
a method, probably at best in combination with others. The attack
is shortly described at http://www.ipcom.at/index.php?id=3D565. It
was as simple as sending annoying INVITEs around, it is not clear
really what could have been the attack purpose.

In fact, the attack is really trivial: it doesn't try to make
messages appear credible, and any reasonably-configured SIP
server would drop them right away. (none of the domains belongs
to the server, the messages have little variance among them)

The victims' phones would not have been ringing at 3AM if they
tried to verify who is calling them. (even though with so
trivially formed requests a proxy server would drop them even
before reaching the UAS).

-jiri


Henry Sinnreich wrote:
>   The =91  Dialog Event foR Identity Verification=92 is meeting IMO the r=
eal =

> need for preventing forged =93From=94 names and has the virtue of simplic=
ity =

> as well.
> It is analog to the email verification which is  successfully deployed =

> throughout the Internet at present.
> =

>   http://www3.ietf.org/proceedings/staging/draft-kuthan-sip-derive-00.txt
> =

> Thanks, Henry
> =

> =

> ------------------------------------------------------------------------
> =

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


From sip-bounces@ietf.org  Sat Oct 25 15:11:14 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 84ED43A67D8;
	Sat, 25 Oct 2008 15:11:14 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8858F3A67D8
	for <sip@core3.amsl.com>; Sat, 25 Oct 2008 15:11:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tzP4-HOyWqqp for <sip@core3.amsl.com>;
	Sat, 25 Oct 2008 15:11:12 -0700 (PDT)
Received: from mail.iptel.org (smtp.iptel.org [213.192.59.67])
	by core3.amsl.com (Postfix) with ESMTP id 176903A67AD
	for <sip@ietf.org>; Sat, 25 Oct 2008 15:11:12 -0700 (PDT)
Received: from jiri-kuthans-macbook-pro-8.local (shell.iptel.org
	[213.192.59.74])
	by mail.iptel.org (Postfix) with ESMTP id 31CA91810C14;
	Sun, 26 Oct 2008 00:12:36 +0200 (CEST)
Message-ID: <490399D3.800@iptel.org>
Date: Sun, 26 Oct 2008 00:12:35 +0200
From: Jiri Kuthan <jiri@iptel.org>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
References: <200810251926.17644.ibc@aliax.net> <490382B6.1090400@cisco.com>
In-Reply-To: <490382B6.1090400@cisco.com>
Cc: sip@ietf.org
Subject: Re: [Sip] [RFC 4235 & draft-kuthan-sip-derive] 481 "Call doesn't
 exist"	for initial SUBSCRIBE ?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

SW4gZmFjdCBJIGFncmVlIHRoYXQncyBhIGJ1ZyAtLSB0aGUgU1VCU0NSSUJFIGlzIHN1cHBvc2Vk
IHRvIGNyZWF0ZSBhIGRpYWxvZwpvbiBpdHMgb3duIGFuZCBpdCBpcyBub3QgZGVuaWVkIGJlY2F1
c2Ugb2YgYW4gYWJzZW50IGRpYWxvZyBjb250ZXh0LCBidXQKYmVjYXVzZSBBbGljZSBoYXMgbm8g
cmVhc29uIHRvIGFjY2VwdCB1bnNvbGljaXRlZCBzdWJzY3JpYmVzLgoKV2hpY2ggdG91Y2hlcyB0
aGUgZGVsaWNhdGUgcHJpdmFjeSBhc3BlY3QgLS0gaG93IGRvIHdlIG1ha2Ugc3VyZSB0aGF0CnRo
ZSBOT1RJRlkgcmVxdWVzdHMgZGlzY2xvc2Ugb25seSBzdGF0dXMgdG8gYSByaWdodGZ1bCByZWNl
cGllbnQKKGkuZS4sIHRoZSBjYWxsZWUpLgoKLWppcmkKCgpQYXVsIEt5eml2YXQgd3JvdGU6Cj4g
SSBhZ3JlZSB0aGF0IDQ4MSBzZWVtcyBhbiB1bnN1aXRhYmxlIHJlc3BvbnNlIGluIHRoaXMgY2Fz
ZS4KPiBJdHMgbm90IGNsZWFyIHRvIG1lIHdoYXQgcmVzcG9uc2UgaXMgYmVzdCBzdWl0ZWQuIFBl
cmhhcHMgNDAzIG9yIDYwMy4KPiAKPiAgICAgVGhhbmtzLAo+ICAgICBQYXVsCj4gCj4gScOxYWtp
IEJheiBDYXN0aWxsbyB3cm90ZToKPj4gSGksIEkndmUgYSBkb3VidCBhYm91dCB3aGF0IHNob3Vs
ZCBiZSB0aGUgY29ycmVjdCByZXNwb25zZSBmb3IgYW4gCj4+IGluaXRpYWwgU1VCU0NSSUJFIChF
dmVudDogZGlhbG9nKSBpZiB0aGUgaW5kaWNhdGVkIGRpYWxvZyBkb2Vzbid0IAo+PiBleGlzdCBp
biB0aGUgcmVjaXBpZW50IG9mIHRoZSBTVUJTQ1JJQkUuCj4+Cj4+IFRoaXMgZG91YnQgY29tZXMg
YWZ0ZXIgcmVhZGluZyB0aGUgdG9kYXkgc3VibWl0dGVkIGRyYWZ0ICJEaWFsb2cgRXZlbnQgCj4+
IGZvUiBJZGVudGl0eSBWRXJpZmljYXRpb24iOgo+PiAgIGh0dHA6Ly93d3czLmlldGYub3JnL3By
b2NlZWRpbmdzL3N0YWdpbmcvZHJhZnQta3V0aGFuLXNpcC1kZXJpdmUtMDAudHh0Cj4+Cj4+IElu
IHBhZ2UgMTQgb2YgdGhpcyBkcmFmdCB0aGVyZSBpcyBhIGZsb3cgYWJvdXQgYSBzdXNwaWNpb3Vz
IGNhbGwgCj4+IChzcG9vZmVkIEZyb20pLiBUaGUgZmxvdyBpcyBjb3JyZWN0bHkgZGlzcGxheWVk
IHVzaW5nIGZpeGVkIGxlbmd0aCAKPj4gdHlwb2dyYXBoeSwgaWYgaXQncyBub3QgeW91ciBjYXNl
IHJlZmVyIHRvIHBhZ2UgMTQgb2YgdGhlIGRyYWZ0Lgo+Pgo+Pgo+PiAgICAgQXR0YWNrZXIgICAg
ICAgIEFsaWNlICAgUHJveHkgMSAoYXRsYW50YS5jb20pIFByb3h5IDIgKGJpbG94aS5jb20pIAo+
PiBCb2IKPj4gICAgIHwgICAgICAgICAgICAgICB8IElOVklURSBGNSAgICAgIHwgICAgICAgICAg
ICAgICAgfCAgICAgICAgICAgICAgICB8Cj4+ICAgICB8LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPnwgICAgICAgICAgICAgICAgfAo+PiAgICAgfCAgICAg
ICAgICAgICAgIHwgMTAwIEY2ICAgICAgICAgfCAgICAgICAgICAgICAgICB8ICAgICAgICAgICAg
ICAgIHwKPj4gICAgIHw8LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tfCBJTlZJVEUgRjcgICAgICB8Cj4+ICAgICB8ICAgICAgICAgICAgICAgfCAgICAgICAg
ICAgICAgICB8ICAgICAgICAgICAgICAgIHwtLS0tLS0tLS0tLS0tLS0+fAo+PiAgICAgfCAgICAg
ICAgICAgICAgIHwgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICB8IDEwMCBGOCAgICAg
ICAgIHwKPj4gICAgIHwgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgIHwgICAgICAgICAg
ICAgICAgfDwtLS0tLS0tLS0tLS0tLS18Cj4+ICAgICB8ICAgICAgICAgICAgICAgfCAgICAgICAg
ICAgICAgICB8ICAgICAgICAgICAgICAgIHwgU1VCU0NSSUJFIEY5ICAgfAo+PiAgICAgfCAgICAg
ICAgICAgICAgIHwgICAgICAgICAgICAgICAgfCBTVUJTQ1JJQkUgRjEwICB8PC0tLS0tLS0tLS0t
LS0tLXwKPj4gICAgIHwgICAgICAgICAgICAgICB8IFNVQlNDUklCRSBGMTEgIHw8LS0tLS0tLS0t
LS0tLS0tfCAgICAgICAgICAgICAgICB8Cj4+ICAgICB8ICAgICAgICAgICAgICAgfDwtLS0tLS0t
LS0tLS0tLS18ICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgfAo+PiAgICAgfCAgICAg
ICAgICAgICAgIHwgNDgxIEYxMiAgICAgICAgfCAgICAgICAgICAgICAgICB8ICAgICAgICAgICAg
ICAgIHwKPj4gICAgIHwgICAgICAgICAgICAgICB8LS0tLS0tLS0tLS0tLS0tPnwgNDgxIEYxMyAg
ICAgICAgfCAgICAgICAgICAgICAgICB8Cj4+ICAgICB8ICAgICAgICAgICAgICAgfCAgICAgICAg
ICAgICAgICB8LS0tLS0tLS0tLS0tLS0tPnwgNDgxIEYxNCAgICAgICAgfAo+PiAgICAgfCAgICAg
ICAgICAgICAgIHwgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICB8LS0tLS0tLS0tLS0t
LS0tPnwKPj4KPj4KPj4gU28sIEJvYiBzZW5kcyBhbiBpbml0aWFsIFNVQlNDUklCRSB0byBBbGlj
ZSBBb1IgKHRoZSByZWNlaXZlZCBGcm9tIHVyaSAKPj4gaW4gdGhlIElOVklURSBGNS9GNykgd2l0
aCB0aGUgaGFsZi1kaWFsb2cgZGF0YToKPj4KPj4gICAgU1VCU0NSSUJFIHNpcDphbGljZUBhdGxh
bnRhLmNvbSBTSVAvMi4wCj4+ICAgIEZyb206IEJvYiA8c2lwOkJvYkBiaWxveGkuY29tPjt0YWc9
ODY3MjM0OQo+PiAgICBUbzogPHNpcDphbGljZUBhdGxhbnRhLmNvbT4KPj4gICAgQ2FsbC1JRDog
eHQ0NjUzZ3MyaGFtQGJpbG94aS5jb20KPj4gICAgQ29udGFjdDogPHNpcDpib2JAY2xpZW50LmJp
bG94eS5jb20+Cj4+ICAgIEV2ZW50OiAKPj4gZGlhbG9nO2NhbGwtaWQ9Mzg0ODI3NjI5ODIyMDE4
ODUxMUBhdGxhbnRhLmNvbTt0by10YWc9OWZ4Y2VkNzZzbAo+PiAgICBFeHBpcmVzPTAKPj4gICAg
QWNjZXB0OiBhcHBsaWNhdGlvbi9kaWFsb2ctaW5mbyt4bWwKPj4gICAgQ29udGVudC1MZW5ndGg6
IDAKPj4KPj4gTm90ZSB0aGF0ICJFdmVudCIgaGVhZGVyIGNvbnRhaW5zIHNwZWNpZmljIGhhbGYt
ZGlhbG9nIGluZm9ybWF0aW9uLgo+Pgo+PiBUaGlzIFNVQlNDUklCRSBhcnJpdmVzIHRvIEFsaWNl
J3MgVUEgd2hpY2ggaXMgbm90IGF3YXJlIG9mIHRoYXQgCj4+IGRpYWxvZy4gV2hpY2ggcmVzcG9u
c2Ugc2hvdWxkIGl0IHJlcGx5PyBUaGUgZmxvdyBzdWdnZXN0cyAiNDgxIAo+PiBDYWxsL1RyYW5z
YWN0aW9uIGRvZXNuJ3QgZXhpc3QiLCBidXQuLi4gaXMgaXQgY29ycmVjdD8KPj4KPj4gQUZBSUss
IGEgNDgxIHNob3VsZCBiZSByZXBsaWVkIHdoZW4gYW4gKmluLWRpYWxvZyogcmVxdWVzdCBhcnJp
dmVzIHRvIAo+PiBhbiBVQVMgd2hpY2ggaXMgbm90IGF3YXJlIG9mIHRoYXQgZGlhbG9nLiBCdXQg
aW4gdGhlIGFib3ZlIGNhc2Ugd2UgCj4+IGhhdmUgYW4gKmluaXRpYWwqIHJlcXVlc3QgYW5kIHRo
ZSA0ODEgcmVmZXJzIHRvIHRoZSBzcGVjaWZpYyBkaWFsb2cgaW4gCj4+IHRoZSAiRXZlbnQiIGhl
YWRlci4KPj4KPj4KPj4gV2VsbCwgSSBzdWdnZXN0IGEgcG9zc2libGUgaXNzdWUgd2l0aCB0aGUg
YWJvdmUgYmVoYXZpb3VyOgo+Pgo+PiAtIEFsaWNlIGludml0ZXMgQm9iLgo+PiAtIEJlZm9yZSBz
ZW5kaW5nIGEgcHJvdmlzaW9uYWwgcmVzcG9uc2UsIEJvYiBzZW5kcyBhbiAqaW5pdGlhbCogCj4+
IFNVQlNDUklCRSB0byBBbGljZSB3aXRoIHRoZSBjdXJyZW50IGhhbGYtZGlhbG9nIGluZm9ybWF0
aW9uIGluIHRoZSAKPj4gIkV2ZW50IiBoZWFkZXIuCj4+IC0gQWxpY2UgYWNjZXB0cyB0aGUgU1VC
U0NSSUJFLCByZXBsaWVzIDIwMCBhbmQgbGF0ZXIgYSBOT1RJRlkgd2l0aCB0aGUgCj4+IHNwZWNp
ZmljIGRpYWxvZyBzdGF0dXMuCj4+Cj4+IGEpCj4+IC0gQWZ0ZXIgNDAgc2Vjb25kcyBBbGljZSdz
IFVBIGNyYXNoZXMgYW5kIGlzIHJlc3RhcnRlZCAoZGlhbG9nIGluZm8gCj4+IGxvc3QpLgo+PiAt
IEJvYiBzZW5kcyBhIFNVQlNDUklCRSByZWZyZXNoIChhbiBpbi1kaWFsb2cgcmVxdWVzdCkuCj4+
IC0gVGhhdCBkaWFsb2cgKHRoZSBTVUJTQ1JJQkUgZGlhbG9nKSBkb2Vzbid0IGV4aXN0IGluIEFs
aWNlIGFueW1vcmUsIAo+PiBzbyBBbGljZSByZXBsaWVzIDQ4MS4KPj4KPj4gYikKPj4gLSBEaWFs
b2cgYmV0d2VlbiBBbGljZSBhbmQgQm9iIGVuZHMgYmVjYXVzZSBBbGljZSBzZW5kcyBhIEJZRSwg
YnV0IAo+PiBiZWZvcmUgQWxpY2UgcmVjZWl2ZXMgdGhlIEJZRSBhbmQgdGhlIGRpYWxvZyBOT1RJ
RlkgdXBkYXRlLCBCb2Igc2VuZHMgCj4+IGEgU1VCU0NSSUJFIHJlZnJlc2ggKGFuIGluLWRpYWxv
ZyByZXF1ZXN0KSBmb3IgdGhhdCBkaWFsb2cuCj4+IC0gVGhpcyBTVUJTQ1JJQkUgYXJyaXZlcyB0
byBBbGljZSwgdGhlIFNVQlNDUklCRSByZXF1ZXN0IGRpYWxvZyBleGlzdHMgCj4+IGJ1dCB0aGUg
ZGlhbG9nIGluZGljYXRlZCBpbiAiRXZlbnQiIGhlYWRlciBkb2Vzbid0IGV4aXN0IGFueW1vcmUu
Cj4+IC0gQXMgdGhlIGFib3ZlIGZsb3cgc3VnZ2VzdHMsIEFsaWNlIHJlcGxpZXMgNDgxLgo+Pgo+
PiBJbiBib3RoIGNhc2VzIGEpIGFuZCBiKSwgQWxpY2UgcmVwbGllcyA0ODEgYnV0IHRoZSBzY2Vu
YXJpbyBpcyAKPj4gY29tcGxldGVseSBkaWZmZXJlbnQuIFRoZSA0ODEgaW4gYSkgbWVhbnMgdGhh
dCB0aGUgaW4tZGlhbG9nIFNVQlNDUklCRSAKPj4gYmVsb25ncyB0byBhIG5vbiBleGlzdGluZyBk
aWFsb2cgaW4gQWxpY2UsIHdoaWxlIHRoZSA0ODEgaW4gYikgbWVhbnMgCj4+IHRoYXQgYSBkaWFs
b2cgaW5kaWNhdGVkIGluIHRoZSBFdmVudCBoZWFkZXIgZG9lc24ndCBleGlzdC4KPj4gQnV0IHRo
ZXJlIGlzIG5vIHdheSBmb3IgQm9iIHRvIHJlYWxpemUgd2hpY2ggaXMgdGhlIGNhc2UgYSkgb3Ig
YikuCj4+Cj4+Cj4+IFRoZSBtYWluIHF1ZXN0aW9uIGlzOiBpcyA0ODEgdGhlIGFwcHJvaWF0ZSAo
YW5kIHZhbGlkKSByZXBseSBpbiB0aGUgCj4+IGFib3ZlIGZsb3cgKGNhc2UgYik/IElzIDQ4MSBy
ZWFsbHkgdmFsaWQgYXMgYSByZXBseSBmb3IgYW4gaW5pdGlhbCAKPj4gcmVxdWVzdD8KPj4KPj4K
Pj4KPj4KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+
IFNpcCBtYWlsaW5nIGxpc3QgIGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v
c2lwCj4gVGhpcyBsaXN0IGlzIGZvciBORVcgZGV2ZWxvcG1lbnQgb2YgdGhlIGNvcmUgU0lQIFBy
b3RvY29sCj4gVXNlIHNpcC1pbXBsZW1lbnRvcnNAY3MuY29sdW1iaWEuZWR1IGZvciBxdWVzdGlv
bnMgb24gY3VycmVudCBzaXAKPiBVc2Ugc2lwcGluZ0BpZXRmLm9yZyBmb3IgbmV3IGRldmVsb3Bt
ZW50cyBvbiB0aGUgYXBwbGljYXRpb24gb2Ygc2lwCl9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fClNpcCBtYWlsaW5nIGxpc3QgIGh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vc2lwClRoaXMgbGlzdCBpcyBmb3IgTkVXIGRldmVsb3BtZW50
IG9mIHRoZSBjb3JlIFNJUCBQcm90b2NvbApVc2Ugc2lwLWltcGxlbWVudG9yc0Bjcy5jb2x1bWJp
YS5lZHUgZm9yIHF1ZXN0aW9ucyBvbiBjdXJyZW50IHNpcApVc2Ugc2lwcGluZ0BpZXRmLm9yZyBm
b3IgbmV3IGRldmVsb3BtZW50cyBvbiB0aGUgYXBwbGljYXRpb24gb2Ygc2lw


From sip-bounces@ietf.org  Sat Oct 25 15:59:16 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BE8633A691D;
	Sat, 25 Oct 2008 15:59:16 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2F18A3A6878
	for <sip@core3.amsl.com>; Sat, 25 Oct 2008 15:59:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.124
X-Spam-Level: 
X-Spam-Status: No, score=-2.124 tagged_above=-999 required=5 tests=[AWL=0.175, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id uLD0AkKpYntW for <sip@core3.amsl.com>;
	Sat, 25 Oct 2008 15:59:14 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.24])
	by core3.amsl.com (Postfix) with ESMTP id 05A333A67AD
	for <sip@ietf.org>; Sat, 25 Oct 2008 15:59:13 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 9so704619eyd.31
	for <sip@ietf.org>; Sat, 25 Oct 2008 16:00:37 -0700 (PDT)
Received: by 10.210.79.14 with SMTP id c14mr4359661ebb.194.1224975637142;
	Sat, 25 Oct 2008 16:00:37 -0700 (PDT)
Received: from portatil.lan (240.pool85-58-8.dynamic.orange.es [85.58.8.240])
	by mx.google.com with ESMTPS id m5sm4410605gve.3.2008.10.25.16.00.35
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Sat, 25 Oct 2008 16:00:35 -0700 (PDT)
From: =?utf-8?q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: sip@ietf.org
Date: Sun, 26 Oct 2008 01:00:38 +0200
User-Agent: KMail/1.9.9
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
In-Reply-To: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810260100.38716.ibc@aliax.net>
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR Identity
	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

RWwgU8OhYmFkbywgMjUgZGUgT2N0dWJyZSBkZSAyMDA4LCBWaWN0b3IgUGFzY3VhbCDDgXZpbGEg
ZXNjcmliacOzOgoKPiBUaGUKPiBVQVMgdmVyaWZpZXMgdGhlICJGcm9tIiBoZWFkZXIgYnkgc3Vi
c2NyaWJpbmcgdG8gdGhlIERpYWxvZyBFdmVudAo+IHBhY2thZ2UgW1JGQyA0MjM1XSBhdCB0aGUg
QU9SIGluIHRoZSAiRnJvbSIgaGVhZGVyIGZpZWxkLiAgSWYgdGhlCj4gZW50aXR5IGNhbGxpbmcg
aXMgcmVnaXN0ZXJlZCB1bmRlciB0aGlzIEFPUiwgaXQgd2lsbCBjb25maXJtIHRoYXQgaXQKPiBp
cyBjYWxsaW5nIGJ5IHNlbmRpbmcgc29tZSB2YWxpZCBkaWFsb2cgc3RhdGUuICBJbiB0aGlzIGNh
c2UsIHRoZQo+IGlkZW50aXR5IG9mIHRoZSBjYWxsZXIgaXMgY29uc2lkZXJlZCB0byBiZSB2ZXJp
ZmllZC4KCkEgcXVlc3Rpb24gYWJvdXQgY2FsbGVyIHByaXZhY3k6CgpJIGhvcGUgdGhpcyBtZWNo
YW5pbXMgZG9lc24ndCByZXF1aWVyZSB0aGF0ICdhbnlvbmUnIGNhbiBzdWJzY3JpYmUgdG8gdGhl
IGNhbGwgCnN0YXR1cyBvZiAnYW55b25lJy4gVGhpcyBpczoKCiAgIEFsaWNlICAgIFByb3h5IDEg
KGF0bGFudGEuY29tKSAgICBQcm94eSAyIChiaWxveGkuY29tKSAgICBCb2IKCkluIG9yZGVyIHRo
aXMgZHJhZnQgdG8gd29yaywgQWxpY2UgbXVzdCBhbGxvdyBhIFNVQlNDUklCRSAoRXZlbnQ6IGRp
YWxvZykgZnJvbSAKQm9iLCBidXQgd2h5IHNob3VsZCBBbGljZSBhbGxvdyBCb2IgbW9uaXRvcml6
aW5nICphbGwqIGhlciBjYWxscz8KClNvLCBBbGljZSBvciBQcm94eSAxIHNob3VsZCBqdXN0IGFs
bG93IFNVQlNDUklCRSAoRXZlbnQ6IGRpYWxvZykgZnJvbSBCb2IgaWYgCnRoZSBFdmVudCBoZWFk
ZXIgaW5jbHVkZXMgJ2NhbGwtaWQnIGFuZCAndG8tdGFnJyBwYXJhbWV0ZXJzLCBpLmU6CgogIEV2
ZW50OiBkaWFsb2c7Y2FsbC1pZD0zODQ4Mjc2Mjk4MjIwMTg4NTExQGF0bGFudGEuY29tO3RvLXRh
Zz05ZnhjZWQ3NnNsCgpJZiBub3QsIEFsaWNlIG9yIFByb3h5IDEgc2hvdWxkIGRlbnkgdGhlIHJl
cXVlc3Qgd2l0aCAiNDAzIEZvcmJpZGRlbiIuCgpJIGtub3cgdGhhdCB0aGlzIGRyYWZ0IGRvZXNu
J3QgaW52b2x2ZSBhdXRob3JpemF0aW9uIHJlcXVlcmltZW50cywgYnV0IGluIGEgCnJlYWwgd29y
bGQgaG93IHdvdWxkIHRoZSBwcml2YWN5IG1lY2hhbmlzbSBiZSBhY2hpZXZlZD8gSSBzdWdnZXN0
IHRoYXQgYSAKcHJveHkgc2hvdWxkIGFsbG93IFNVQlNDUklCRSAoRXZlbnQ6IGRpYWxvZykgZm9y
IGl0cyBsb2NhbCB1c2VycyBqdXN0IGlmIHRoZSAKRXZlbnQgaGVhZGVyIGluY2x1ZGVzICdjYWxs
LWlkJyBhbmQgJ3RvLXRhZycgcGFyYW1ldGVycy4gQWxzbywgZGlhbG9nIGV2ZW50IApwYWNrYWdl
IGlzIGNvbW1vbmx5IGltcGxlbWVudGVkIGF0IHByb3h5IGxldmVsIHdpdGggYSBwcmVzZW5jZSBh
Z2VudCBpbnN0ZWFkIApvZiBmb3J3YXJkaW5nIHRoZSBTVUJTQ1JJQkUncyB0byB0aGUgVUEncy4K
CkluIHRoaXMgbWFubmVyLCBhIGRlZmF1bHQgcG9saWN5IGluIGEgcHJveHkgd291bGQgYWxsb3cg
dGhpcyBkcmFmdCBtZWNoYW5pc20gCndvcmtpbmcgd2l0aG91dCBleHBvc2luZyBsb2NhbCB1c2Vy
cyBwcml2YWN5LiBXb3VsZCBpdCBiZSB0aGUgY29ycmVjdCB3YXk/CgoKUEQ6IFRoYW5rcyBmb3Ig
cHJvcG9zaW5nIGEgZmVhc2libGUgc29sdXRpb24gaW5zdGVhZCBvZiBwcm9wb3NpbmcgZXhvdGlj
IApzcGVjaWZpY2F0aW9ucyB0aGF0IGRlcGVuZCBvbiBvdGhlciBzcGVjaWZpY2F0aW9ucyB3aGlj
aCBub2JvZHkgaW1wbGVtZW50LgoKCi0tIApJw7Fha2kgQmF6IENhc3RpbGxvCl9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClNpcCBtYWlsaW5nIGxpc3QgIGh0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2lwClRoaXMgbGlzdCBpcyBmb3Ig
TkVXIGRldmVsb3BtZW50IG9mIHRoZSBjb3JlIFNJUCBQcm90b2NvbApVc2Ugc2lwLWltcGxlbWVu
dG9yc0Bjcy5jb2x1bWJpYS5lZHUgZm9yIHF1ZXN0aW9ucyBvbiBjdXJyZW50IHNpcApVc2Ugc2lw
cGluZ0BpZXRmLm9yZyBmb3IgbmV3IGRldmVsb3BtZW50cyBvbiB0aGUgYXBwbGljYXRpb24gb2Yg
c2lw


From sip-bounces@ietf.org  Sat Oct 25 19:58:41 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D274C3A6AD2;
	Sat, 25 Oct 2008 19:58:41 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 022203A6AD2
	for <sip@core3.amsl.com>; Sat, 25 Oct 2008 19:58:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5
	tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YnqrZSvVFZ8w for <sip@core3.amsl.com>;
	Sat, 25 Oct 2008 19:58:40 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 07DC53A695E
	for <sip@ietf.org>; Sat, 25 Oct 2008 19:58:39 -0700 (PDT)
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9Q300Mh024488
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Sat, 25 Oct 2008 22:00:03 -0500
Message-Id: <D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: =?ISO-8859-1?Q?Victor_Pascual_=C1vila?= <victor.pascual.avila@gmail.com>
In-Reply-To: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sat, 25 Oct 2008 21:59:54 -0500
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
X-Mailer: Apple Mail (2.929.2)
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR Identity
	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 25, 2008, at 10:09 AM, Victor Pascual =C1vila wrote:

> Hi all,
>
> A new I-D, draft-kuthan-sip-derive-00, was just submitted. Your
> comments are always welcome.

Sounds like you have reinvented identd, which has pretty much vanished  =

from the Internet because it was found to not really add any useful  =

authentication.

See: http://en.wikipedia.org/wiki/Ident

So tell me, how is this operationally different from IDENT?

--
Dean

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


From sip-bounces@ietf.org  Sat Oct 25 20:08:24 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 386CC28C0E8;
	Sat, 25 Oct 2008 20:08:24 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CC73A3A6830;
	Fri, 24 Oct 2008 00:06:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YEzUILV2DofB; Fri, 24 Oct 2008 00:06:50 -0700 (PDT)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41])
	by core3.amsl.com (Postfix) with ESMTP id 0830A3A67E5;
	Fri, 24 Oct 2008 00:06:50 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id CC6B62C000359;
	Fri, 24 Oct 2008 09:08:10 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office)
Received: from smtp0.neclab.eu ([127.0.0.1])
	by localhost (atlas2.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CD3+7U5z505R; Fri, 24 Oct 2008 09:08:10 +0200 (CEST)
Received: from VENUS.office (mx2.office [192.168.24.15])
	by smtp0.neclab.eu (Postfix) with ESMTP id A7F722C000305;
	Fri, 24 Oct 2008 09:07:45 +0200 (CEST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 24 Oct 2008 09:07:45 +0200
Message-ID: <547F018265F92642B577B986577D671C3E0612@VENUS.office>
In-Reply-To: <200810070242.m972grm741386799@shell01.TheWorld.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sipping] [Sip] INVITE dialogs
Thread-Index: AckoJsNxzrdCYdJ0Qj+IyJe2d19GvQNgB6lg
References: <5d688850809301209r6b43aeeaqa4c9f49fa2fa1706@mail.gmail.com><48E28DA2.5060708@cisco.com>
	<200810070242.m972grm741386799@shell01.TheWorld.com>
From: "Saverio Niccolini" <Saverio.Niccolini@nw.neclab.eu>
To: <Dale.Worley@comcast.net>,
	<pkyzivat@cisco.com>
X-Mailman-Approved-At: Sat, 25 Oct 2008 20:08:23 -0700
Cc: sip@ietf.org, sipping@ietf.org, hasebe.miki@east.ntt.co.jp
Subject: Re: [Sip] [Sipping]  INVITE dialogs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

> It would be a very interesting "live fire demonstration" of 
> the value of the formalism if it discovered race conditions 
> that we hadn't identified by informal means.

I would not be surprise to discover that race conditions identified by
informal means are much less than the ones identified using a formalism
(even if one using simplifications).

Paul was saying there is not chance to touch the
draft-ietf-sipping-race-examples

is there any plan to address the identified new race conditions
in another draft then? (Pamela was speaking of about 40 more...)

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


From sip-bounces@ietf.org  Sat Oct 25 20:35:37 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1C70B3A6ADE;
	Sat, 25 Oct 2008 20:35:37 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3CDA63A6AE9
	for <sip@core3.amsl.com>; Sat, 25 Oct 2008 20:35:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id VIDiYUQiWMtg for <sip@core3.amsl.com>;
	Sat, 25 Oct 2008 20:35:34 -0700 (PDT)
Received: from mail.iptel.org (smtp.iptel.org [213.192.59.67])
	by core3.amsl.com (Postfix) with ESMTP id 34F053A67F1
	for <sip@ietf.org>; Sat, 25 Oct 2008 20:35:34 -0700 (PDT)
Received: from jiri-kuthans-macbook-pro-8.local (shell.iptel.org
	[213.192.59.74])
	by mail.iptel.org (Postfix) with ESMTP id 10A7A1810C10;
	Sun, 26 Oct 2008 04:36:59 +0100 (CET)
Message-ID: <4903E5DA.6030201@iptel.org>
Date: Sun, 26 Oct 2008 04:36:58 +0100
From: Jiri Kuthan <jiri@iptel.org>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>
In-Reply-To: <D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR
	Identity	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Dean Willis wrote:
> =

> On Oct 25, 2008, at 10:09 AM, Victor Pascual =C1vila wrote:
> =

>> Hi all,
>>
>> A new I-D, draft-kuthan-sip-derive-00, was just submitted. Your
>> comments are always welcome.
> =

> Sounds like you have reinvented identd, which has pretty much vanished =

> from the Internet because it was found to not really add any useful =

> authentication.
> =

> See: http://en.wikipedia.org/wiki/Ident
> =

> So tell me, how is this operationally different from IDENT?

I'm actually not sure how this comparison holds, perhaps because IDENT
vanished from the Internet before I noticed it was there. I think the
email verification is a better example in that a) it works b) it is
massively used c) it is protocol-specific as opposed to being
a universal instance.

-jiri


> =

> -- =

> Dean
> =

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

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


From sip-bounces@ietf.org  Sun Oct 26 01:54:40 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9B93C3A6A9C;
	Sun, 26 Oct 2008 01:54:40 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A797D3A6A9C
	for <sip@core3.amsl.com>; Sun, 26 Oct 2008 01:54:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5
	tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id C1AXfz5NZdyn for <sip@core3.amsl.com>;
	Sun, 26 Oct 2008 01:54:39 -0700 (PDT)
Received: from taimen.tutpro.com (harjus.tutpro.com [192.98.100.3])
	by core3.amsl.com (Postfix) with ESMTP id CE2FD3A69F7
	for <sip@ietf.org>; Sun, 26 Oct 2008 01:54:38 -0700 (PDT)
Received: by taimen.tutpro.com (Postfix, from userid 1000)
	id 612F033ABBF; Sun, 26 Oct 2008 10:56:02 +0200 (EET)
MIME-Version: 1.0
Message-ID: <18692.12450.342904.645834@harjus.tutpro.com>
Date: Sun, 26 Oct 2008 10:56:02 +0200
To: =?utf-8?q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
In-Reply-To: <200810260100.38716.ibc@aliax.net>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<200810260100.38716.ibc@aliax.net>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR
	Identity	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I=F1aki Baz Castillo writes:

 > PD: Thanks for proposing a feasible solution instead of proposing exotic =

 > specifications that depend on other specifications which nobody
 > implement.

i agree with this and long time ago (before presence existed) proposed a
similar (if not even simpler) solution:

- my phone receives a call from sip:foo@bar

- my phone sends a query to sip:foo@bar asking if foo@bar is trying to
  call me

in order for this to work, the phone from which sip:foo@bar is calling,
needs to be registered.

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


From sip-bounces@ietf.org  Sun Oct 26 03:44:04 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 532C83A691A;
	Sun, 26 Oct 2008 03:44:04 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BDB3C3A691A
	for <sip@core3.amsl.com>; Sun, 26 Oct 2008 03:44:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.153
X-Spam-Level: 
X-Spam-Status: No, score=-2.153 tagged_above=-999 required=5 tests=[AWL=0.146, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3kv8pJrF5Ah0 for <sip@core3.amsl.com>;
	Sun, 26 Oct 2008 03:44:03 -0700 (PDT)
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187])
	by core3.amsl.com (Postfix) with ESMTP id D82363A684F
	for <sip@ietf.org>; Sun, 26 Oct 2008 03:44:02 -0700 (PDT)
Received: by nf-out-0910.google.com with SMTP id b11so534796nfh.39
	for <sip@ietf.org>; Sun, 26 Oct 2008 03:45:24 -0700 (PDT)
Received: by 10.210.54.19 with SMTP id c19mr4959852eba.116.1225017924722;
	Sun, 26 Oct 2008 03:45:24 -0700 (PDT)
Received: from portatil.local (240.pool85-58-8.dynamic.orange.es [85.58.8.240])
	by mx.google.com with ESMTPS id y37sm232426iky.9.2008.10.26.03.45.22
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Sun, 26 Oct 2008 03:45:23 -0700 (PDT)
From: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
To: sip@ietf.org
Date: Sun, 26 Oct 2008 11:45:19 +0100
User-Agent: KMail/1.9.9
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>
In-Reply-To: <D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810261145.19745.ibc@aliax.net>
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR Identity
	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

El Domingo, 26 de Octubre de 2008, Dean Willis escribi=F3:
> > A new I-D, draft-kuthan-sip-derive-00, was just submitted. Your
> > comments are always welcome.
>
> Sounds like you have reinvented identd, which has pretty much vanished =
=A0
> from the Internet because it was found to not really add any useful =A0
> authentication.

draft-kuthan-sip-derive-00 proposal is 100% SIP based instead of depending =
on =

other protocols. IMHO it has *nothing* to do with Identd mechanism.

-- =

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


From sip-bounces@ietf.org  Sun Oct 26 03:51:38 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 41FEF3A68AC;
	Sun, 26 Oct 2008 03:51:38 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A04653A682E
	for <sip@core3.amsl.com>; Sun, 26 Oct 2008 03:51:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.215
X-Spam-Level: 
X-Spam-Status: No, score=-6.215 tagged_above=-999 required=5 tests=[AWL=0.034, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id VddQwOlMp5o0 for <sip@core3.amsl.com>;
	Sun, 26 Oct 2008 03:51:35 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 69D563A68AC
	for <sip@ietf.org>; Sun, 26 Oct 2008 03:51:35 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	BE1ED2023D; Sun, 26 Oct 2008 11:52:59 +0100 (CET)
X-AuditID: c1b4fb3c-ad8cdbb0000015b5-47-49044c0b96ca
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	91D2720015; Sun, 26 Oct 2008 11:52:59 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 26 Oct 2008 11:52:59 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 26 Oct 2008 11:52:57 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCFB8@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: Content-Type
	vs	Info-Package [was RE: draft-ietf-sip-info-events-00:
	multiple	packages per INFO]
Thread-Index: Ack2MET96PgRNNvDTgqe7QzrcuTVwABJ8Ni4
References: <48FDEAD8.8010803@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>	<48FF2C45.7010204@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>	<4901BA73.1010700@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>	<4901C2B1.1050209@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>	<4901D025.6060302@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>	<490239C8.3020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>	<4902467E.3010603@cisco.com>
	<F05558E6-AF75-41BC-9691-8A7E14748C8B@softarmor.com>
	<49025A2E.4050801@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>,
	"Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 26 Oct 2008 10:52:59.0399 (UTC)
	FILETIME=[02B7D970:01C93759]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type
	vs	Info-Package [was RE: draft-ietf-sip-info-events-00:
	multiple	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi,
 
I don't understand why we should have to make an assumption that the C-D value will be different, and that it will always be possible to pick out the info package based on it. 
 
We don't know what info packages there will be, and we don't have a clear picture of other usages, so I think making such restrictive assumption is really bad. In that case I would rather prefer that we don't even allow multipart in INFO, which may also be another shooting in the feet thing...
 
I would still like to understand why the proposed usage of C-T by Jeroem and myself (eventhough I may not have made myself clear) wouldn't work:
 
example: Content-Type: application/foo-data;info-package=foo 
 
I don't think the C-T usage, as in the example above, fits into Eric's why-content-type-is-bad description.
 
image/jpge is BAD, I agree
 
image/jpeg; info-package=foo is not bad, in my opinion.
 
Of course, there may still be a need for C-D, per mime, but I don't think we should use C-D in order to figure out which mime is associated with the info package (unelss we have a C-D value of "info-package", that is).
 
Regards,
 
Christer

________________________________

From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
Sent: Sat 25/10/2008 01:28
To: Dean Willis
Cc: SIP IETF; Christer Holmberg
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs Info-Package [was RE: draft-ietf-sip-info-events-00: multiple packages per INFO]





Dean Willis wrote:
>
> On Oct 24, 2008, at 5:04 PM, Paul Kyzivat wrote:
>
>>
>> Christer Holmberg wrote:
>>
>>> So, just to make sure I understand: you are talking about a case
>>> where the INFO does contain a multipart message body, but only one of
>>> the mimes contains an actual info-package (the other mime(s) contains
>>> something else)?
>>
>> pretty much. And to distinguish those, you need more than C-T.
>> But I think as we have been discussing, if we only allow one info
>> package per INFO, then the Info-Package header belongs in the message,
>> not in the body part.
>>
>
> So the error condition is you have two body parts of types allowed for
> the INFO package, but only one of them is the "real" info, and the other
> part is from some other extension.
>
> If it hurts, don't do it?
>
> Seriously, a Content-Disposition would sort this out.

Yes. We need a C-D.

It can be "render" if we want it to be. But I think that brings some
baggage that we could do without. In particular, "render" is the default
C-D for any C-T that isn't defined to have some other C-D as its default.

I am really now thinking that the info package type is really a
"sub-disposition-type" - an extension to the disposition type namespace
that is independently managed. And then we provide the means to
negotiate use of those in INFO.

        Paul


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


From sip-bounces@ietf.org  Sun Oct 26 03:53:02 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 082B23A6AE1;
	Sun, 26 Oct 2008 03:53:02 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E59473A68FD
	for <sip@core3.amsl.com>; Sun, 26 Oct 2008 03:53:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.571
X-Spam-Level: 
X-Spam-Status: No, score=-4.571 tagged_above=-999 required=5
	tests=[AWL=-1.612, BAYES_00=-2.599, FRT_OPPORTUN1=1.893,
	FRT_OPPORTUN2=1.397, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 92ba6gwTY-b4 for <sip@core3.amsl.com>;
	Sun, 26 Oct 2008 03:52:59 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 3073F3A6ADE
	for <sip@ietf.org>; Sun, 26 Oct 2008 03:52:59 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	741AA20FDA; Sun, 26 Oct 2008 11:54:24 +0100 (CET)
X-AuditID: c1b4fb3e-ae785bb00000537b-1a-49044c60a00a
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	549AA20FDB; Sun, 26 Oct 2008 11:54:24 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 26 Oct 2008 11:54:24 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 26 Oct 2008 11:53:20 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCFB9@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Does SIP want to participate in the Interim
	MeetingOpportunity in January 2009
Thread-Index: Ack2ITSDlIEVMl/hQIm7j1LieWBdrgBN9rY6
References: <20081016203334.229803A68EC@core3.amsl.com><1A80883E-AB46-4776-92C0-798C7E662D21@softarmor.com>
	<41397D90-A4BD-4AC0-8598-3B10783612C4@softarmor.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Dean Willis" <dean.willis@softarmor.com>,
	"SIP IETF" <sip@ietf.org>
X-OriginalArrivalTime: 26 Oct 2008 10:54:24.0162 (UTC)
	FILETIME=[353DA820:01C93759]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] Does SIP want to participate in the Interim
	MeetingOpportunity in January 2009
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I guess there is something wrong with the dates, or is there going to be a ONE-day large-scale meeting?

________________________________

From: sip-bounces@ietf.org on behalf of Dean Willis
Sent: Fri 24/10/2008 23:40
To: SIP IETF
Subject: [Sip] Does SIP want to participate in the Interim MeetingOpportunity in January 2009



IETF is hosting a large-scale interim meeting in Malta, Jan 22-22 2009.

Do we want to have an interim meeting? The AD's assumption is "yes", 
so please reply if you think otherwise.

--
Dean

Begin forwarded message:

> From: IETF Chair <chair@ietf.org>
> Date: October 16, 2008 3:33:34 PM CDT
> To: Working Group Chairs <wgchairs@ietf.org>
> Cc: chair@ietf.org
> Subject: WG Interim Meeting Opportunity in January 2009
>
> In our continuing effort to ensure that IETF WGs are getting enough
> meeting time to progress their work, we are conducting another 
> experiment.
> Many WGs have found interim meetings an effective way to tackle thorny
> technical issues, resolve contentious technical issues, accelerate
> standards development, and provide traction for new work.  As 
> always, an
> interim WG meeting is not a substitute for a regular session at the
> traditional IETF meeting.  Since some WG Chairs and ADs have found the
> amount of time necessary to put together an interim meeting can be
> excessive, we are trying to reduce the effort necessary to conduct an
> interim meeting to determine whether reducing this burden will 
> expedite
> IETF standards development.  To this end, the Secretariat will 
> facilitate
> a large interim meeting from 20-22 January 2009 in Malta.  If you are
> interested in participating in this experiment, please contact your 
> Area
> Director for approval.  All face-to-face interim meetings require AD
> approval, and this is no exception.  The IETF Secretariat is putting
> together a program with three full days and four tracks on each 
> day.  Each
> WG interim meeting is expected to consume at least one full day on 
> one of
> the tracks.
>
> ADs will schedule the sessions.  A URL for the schedule will be 
> announced
> shortly.  Once it is available, if you detect a scheduling conflict,
> please raise the concern with your AD for resolution.  Session time is
> limited, and sessions will be allocated first come, first served.
>
> The Secretariat will provide registration, food and beverage, audio
> visual facilities, and on site registration support.  VeriLAN will 
> provide
> network and audio streaming support.  It is expected that the 
> meeting fee
> will be $375 for early registration and $475 for late registration.
>
> The Internet Society is looking for meeting sponsors for this event.
> Anyone interested please contact Drew Dvorshak <dvorshak@isoc.org>.
>
> Russ
>

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


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


From sip-bounces@ietf.org  Sun Oct 26 04:00:02 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B69753A6AF3;
	Sun, 26 Oct 2008 04:00:02 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3704A3A6AEB
	for <sip@core3.amsl.com>; Sun, 26 Oct 2008 04:00:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.902
X-Spam-Level: 
X-Spam-Status: No, score=-5.902 tagged_above=-999 required=5
	tests=[AWL=-0.253, BAYES_00=-2.599, HELO_EQ_SE=0.35,
	J_CHICKENPOX_37=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FnsvMao0QpmO for <sip@core3.amsl.com>;
	Sun, 26 Oct 2008 04:00:01 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 1746B3A6AEE
	for <sip@ietf.org>; Sun, 26 Oct 2008 04:00:01 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	8603520633; Sun, 26 Oct 2008 12:01:26 +0100 (CET)
X-AuditID: c1b4fb3c-af0d0bb0000015b5-e5-49044e06fa25
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	66E2B20611; Sun, 26 Oct 2008 12:01:26 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 26 Oct 2008 12:01:26 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 26 Oct 2008 12:01:24 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCFBA@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
Thread-Index: Ack2JIi/YnmGy6W9RImww5G4tJNnegBNNCTp
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>
	<4901BA73.1010700@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>
	<4901C2B1.1050209@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>
	<4901D025.6060302@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>
	<490239C8.3020808@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>
	<4902467E.3010603@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 26 Oct 2008 11:01:26.0227 (UTC)
	FILETIME=[30CFAA30:01C9375A]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi,

>>So, just to make sure I understand: you are talking about a case where the INFO does contain a multipart message body, but only one of the mimes contains an actual info-package (the other mime(s) contains something else)?
>
>pretty much. And to distinguish those, you need more than C-T.
>But I think as we have been discussing, if we only allow one info
>package per INFO, then the Info-Package header belongs in the message,
>not in the body part.
 
I don't think that defining Info-Package as a mime header would even be within the scope of the SIP WG, would it?
 
My assumption has been that the I-P header is in the SIP message part, and that causes the problem: in the case of multipart, how to associate the correct mime with the I-P header? I still think making assumptions on C-D is very dangerous, considering the very little experience we have of the C-D header in the first place.

>I'll revise your example a bit:
>
>INFO sip:foo@bar.com
>To:...
>From:...
>Some-Header: CID:abcdefg
>Info-Package: foo
>Content-Type:multipart/mixed
>Content-Length:...
>
>--boundary
>Content-Type: application/foo-data
>Content-Disposition: package;handling=required
>
>foo data
>--boundary
>Content-ID: abcdefg
>Content-Type: application/some-header-data
>Content-Disposition: by-reference;handling=optional
>
>some other (non-info package) data
>--boundary--
>
>In the above I have used C-D of "package" to identify the part that
>contains the info package. That is yet to be determined, but I think it
>needs to be well defined, even if it is "render".

Again, I don't think using C-D for the "association" is a good idea.
 

>A more straightforward case would be:
>
>INFO sip:foo@bar.com
>To:...
>From:...
>Info-Package: foo
>Content-Type: application/foo-data
>Content-Disposition: package;handling=required
>Content-Length:10
>
>foo data

...assuming that we don't allow multipart in INFOs, yes.
 
Regards,
 
Christer
 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Sun Oct 26 04:03:52 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 71F713A6B03;
	Sun, 26 Oct 2008 04:03:52 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3FD7F3A6B07
	for <sip@core3.amsl.com>; Sun, 26 Oct 2008 04:03:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.2
X-Spam-Level: 
X-Spam-Status: No, score=-6.2 tagged_above=-999 required=5 tests=[AWL=0.049,
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QgDJkgQesvyn for <sip@core3.amsl.com>;
	Sun, 26 Oct 2008 04:03:50 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 258A93A6AFC
	for <sip@ietf.org>; Sun, 26 Oct 2008 04:03:50 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	051CF20FC8; Sun, 26 Oct 2008 12:05:12 +0100 (CET)
X-AuditID: c1b4fb3e-abf80bb00000537b-49-49044ee747ce
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	E6E1D20154; Sun, 26 Oct 2008 12:05:11 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 26 Oct 2008 12:05:11 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 26 Oct 2008 12:02:12 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCFBB@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] info-events and callee capabilities / caller
	prefs(RFC3840/3841)
Thread-Index: Ack2joM8D7ekwX5RRsSy+CB5EczEpgAy8j/j
References: <4902F82E.5050105@zonnet.nl>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Jeroen van Bemmel" <jbemmel@zonnet.nl>,
	"IETF SIP List" <sip@ietf.org>
X-OriginalArrivalTime: 26 Oct 2008 11:05:11.0751 (UTC)
	FILETIME=[B73BE570:01C9375A]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] info-events and callee capabilities / caller
	prefs(RFC3840/3841)
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi,
 
I agree. I think it would be very useful, for forking cases, if a UA can register the info packages it supports.
 
Regards,
 
Christer
 
 

________________________________

From: sip-bounces@ietf.org on behalf of Jeroen van Bemmel
Sent: Sat 25/10/2008 12:42
To: IETF SIP List
Subject: [Sip] info-events and callee capabilities / caller prefs(RFC3840/3841)



All,

In analogy with RFC3265-based events and caller prefs / callee
capabilities, I believe there may be value in having something similar
for info-events.

Since the current info-events draft does not define a tag for use in
Supported/Require, a UAC currently has no way to signal that it prefers
to communicate with a UAS that supports INFO events, let alone  specific
INFO events (e.g. key strokes, caller ID pictures, etc.). Such a
capability could be valuable in upgrade scenarios (i.e. moving from a
network that does not support INFO packages).

My suggestion is therefore to let the new info-events draft update
RFC3840/RFC3841 with e.g. "info-events=....", and to also define a tag
for use with Supported/Require to support capability indication

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


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


From sip-bounces@ietf.org  Sun Oct 26 04:07:43 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8409B3A697D;
	Sun, 26 Oct 2008 04:07:43 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 470693A6AE3
	for <sip@core3.amsl.com>; Sun, 26 Oct 2008 04:07:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.2
X-Spam-Level: 
X-Spam-Status: No, score=-6.2 tagged_above=-999 required=5 tests=[AWL=0.049,
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id xUSvmWDMqXjc for <sip@core3.amsl.com>;
	Sun, 26 Oct 2008 04:07:41 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id DF26F3A697D
	for <sip@ietf.org>; Sun, 26 Oct 2008 04:07:40 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	5086D21001; Sun, 26 Oct 2008 12:09:06 +0100 (CET)
X-AuditID: c1b4fb3e-aff88bb00000537b-c9-49044fd2ff9f
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	1FADD20269; Sun, 26 Oct 2008 12:09:06 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 26 Oct 2008 12:09:05 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 26 Oct 2008 12:07:48 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCFBC@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
Thread-Index: Ack2unoI+qq6cbhdSt2GK1gMR6OoYQAoJrlC
References: <48FDEAD8.8010803@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>	<5D1A7985295922448D5550C94DE2918002425A08@DEEXC1U01.de.lucent.com>	<D85A991A-AEE8-4A12-AFE6-F999C2DD4058@softarmor.com>	A	<CA9998CD4A020D418654FCDEF4E707DF088F10DB@esealmw113.eemea.ericsson.se>	<0D5F89FAC29E2C41B98A6A762007F5D00134915C@GBNTHT12009MSX.gb002.siemens.net>	<CA9998CD4A020D418654FCDEF4E707DF088F17D5@esealmw113.eemea.ericsson.se>	<5D1A7985295922448D5550C94DE2918002425C2C@DEEXC1U01.de.lucent.com>	<CA9998CD4A020D418654FCDEF4E707DF088F19BA@esealmw113.eemea.ericsson.se>	<49006A58.3090106@cisco.com>
	<490311A6.3090801@zonnet.nl> <49034210.5060803@ericsson.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Salvatore Loreto" <salvatore.loreto@ericsson.com>,
	"Jeroen van Bemmel" <jbemmel@zonnet.nl>
X-OriginalArrivalTime: 26 Oct 2008 11:09:05.0931 (UTC)
	FILETIME=[42D0EDB0:01C9375B]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>, "Elwell,
	John" <john.elwell@siemens.com>, Dean Willis <dean.willis@softarmor.com>,
	Eric Burger <eburger@bea.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple packages per INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


>what happens if an application includes in a multiple packaged INFO
>request a body part the Sever does not understand?
>how is the server able to indicate that only a part of the INFO request
>was not understood ?

THAT is what you ARE supposed to use the C-D header for. If handling=required, and the receiver doesn't understand it, rejected the message shall be...
 
Regards,
 
Christer
 


Jeroen van Bemmel wrote:
> A possible reason to want multiple packages per INFO request, is that
> it allows one to construct applications that rely on "all or nothing"
> semantics for correlated events.
>
> For example, if one would use SIP to implement an application that
> lets one post a small icon on a blog, and requires an authorization
> token to do that, both would have to arrive together. Another example
> could be an electronic variant of a postage stamp (i.e. some token
> representing some monetary value), when using two different INFOs one
> might fail to arrive where the other would (i.e. content without
> payment, or payment without content).
>
> It has to do with certain atomic, transactional behavior and
> consistency of the user experience
>
> Regards,
> Jeroen
>
> Paul Kyzivat wrote:
>> I also agree it is too extreme to restrict to one package per dialog.
>> But as I stated earlier, I'm fine not defining multiple packages per
>> INFO.
>>
>>     Paul
>>
>> Christer Holmberg wrote:
>>> Hi,
>>>> I don't have a problem agreeing with that.
>>>>
>>>> Note that buried somewhere in this thread was a question of whether we
>>> had a use case for multiple packages per dialog, or can we simplify
>>> even
>>> further.
>>>
>>> I don't think we should go that far, because that could become very
>>> restrictive.
>>>
>>> For example, assume I want to use INFO packages e.g. for DTMF during
>>> the
>>> call setup, and then other INFO package(s) for something else during
>>> the
>>> call.
>>>
>>> Regards,
>>>
>>> Christer
>>>
>>>
>>>> -----Original Message-----
>>>> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
>>>> Sent: Thursday, October 23, 2008 10:51 AM
>>>> To: Elwell, John; Dean Willis; DRAGE, Keith (Keith)
>>>> Cc: SIP IETF; Eric Burger; Paul Kyzivat
>>>> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple packages
>>>> per INFO
>>>>
>>>>
>>>> Hi,
>>>>
>>>> I agree with John. Let's keep it simple. If allowing multiple packages
>>>
>>>> in a single INFO causes issues, let's forget about it.
>>>>
>>>> The whole idea with this is to allow people using INFO to do so in
>>>> an easy and standardized way, so let's not shoot ourselves in the
>>>> foot with complexity.
>>>>
>>>> Regards,
>>>>
>>>> Christer
>>>>
>>>> -----Original Message-----
>>>> From: Elwell, John [mailto:john.elwell@siemens.com]
>>>> Sent: 23. lokakuuta 2008 12:30
>>>> To: Christer Holmberg; Dean Willis; DRAGE, Keith (Keith)
>>>> Cc: SIP IETF; Eric Burger; Paul Kyzivat
>>>> Subject: RE: [Sip] draft-ietf-sip-info-events-00: multiple packages
>>>> per INFO
>>>>
>>>> In reply to this whole thread, please bear in mind that we had lots of
>>>
>>>> discussion about whether it would be worthwhile defining this new INFO
>>>
>>>> mechanism, since existing applications are unlikely to change and
>>>> the best we can hope for is that new applications will exploit the
>>>> new mechanism. Therefore we want to keep the mechanism as simple as
>>>> possible. The complexities of matching body parts to header fields,
>>>> dealing with cases where only some of the packages are understood,
>>>> etc.
>>>> are hardly likely to persuade people to implement the mechanism.
>>>> Please keep it simple.
>>>>
>>>> John
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
>>>> Behalf Of
>>>>> Christer Holmberg
>>>>> Sent: 23 October 2008 08:17
>>>>> To: Dean Willis; DRAGE, Keith (Keith)
>>>>> Cc: SIP IETF; Eric Burger; Paul Kyzivat
>>>>> Subject: Re: [Sip] draft-ietf-sip-info-events-00: multiple
>>>>> packages per INFO
>>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>>>> Why does putting two different packages in the same INFO
>>>>> work better
>>>>>>> than two different INFO messages each with their own
>>>>> package usage? Is
>>>>>
>>>>>>> there a desirable relationship that can be implemented
>>>>> between the two
>>>>>
>>>>>>> that we would otherwise lose?
>>>>>> We have one package per NOTIFY. Let's stick with one package
>>>>> per INFO,
>>>>> unless we want to go back to using mime-types as the only
>>>>> distinguisher of packages.
>>>>>
>>>>> I raised that issue in another e-mail.
>>>>>
>>>>> But, never the less, I have no strong feelings on the single
>>>>> versus multiple package issue.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Christer
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>>>> This list is for NEW development of the core SIP Protocol Use
>>>>> sip-implementors@cs.columbia.edu for questions on current sip Use
>>>>> sipping@ietf.org for new developments on the application of sip
>>>>>
>>>
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sipping@ietf.org for new developments on the application of sip
>>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>



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


From sip-bounces@ietf.org  Sun Oct 26 04:37:09 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 895FA28C114;
	Sun, 26 Oct 2008 04:37:09 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7DCB43A6AF5
	for <sip@core3.amsl.com>; Sun, 26 Oct 2008 04:37:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.347
X-Spam-Level: 
X-Spam-Status: No, score=-0.347 tagged_above=-999 required=5
	tests=[AWL=-0.443, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, 
	J_CHICKENPOX_37=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QmKs0SusiZIl for <sip@core3.amsl.com>;
	Sun, 26 Oct 2008 04:37:07 -0700 (PDT)
Received: from smtp2.versatel.nl (smtp2.versatel.nl [62.58.50.89])
	by core3.amsl.com (Postfix) with ESMTP id 3ABC13A6AE3
	for <sip@ietf.org>; Sun, 26 Oct 2008 04:37:07 -0700 (PDT)
Received: (qmail 6252 invoked by uid 0); 26 Oct 2008 11:38:31 -0000
Received: from ip198-11-212-87.adsl2.static.versatel.nl (HELO [192.168.2.155])
	([87.212.11.198]) (envelope-sender <jbemmel@zonnet.nl>)
	by smtp2.versatel.nl (qmail-ldap-1.03) with SMTP
	for < >; 26 Oct 2008 11:38:31 -0000
Message-ID: <490456A8.6090109@zonnet.nl>
Date: Sun, 26 Oct 2008 12:38:16 +0100
From: Jeroen van Bemmel <jbemmel@zonnet.nl>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <48FDEAD8.8010803@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>	<48FF2C45.7010204@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>	<4901BA73.1010700@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>	<4901C2B1.1050209@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>	<4901D025.6060302@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>	<490239C8.3020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>	<4902467E.3010603@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFBA@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF083CCFBA@esealmw113.eemea.ericsson.se>
Cc: SIP IETF <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type
 vs	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple	packages
 per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer,

Like I wrote before: adding the INFO package as a parameter to 
Content-Type solves all this. I don't think C-D is the right header, 
because the "disposition" would depend on the semantics of the event 
package. We simply need an additional qualifier to disambiguate the 
interpretation of the body

Regards,
Jeroen

Christer Holmberg wrote:
> Hi,
>
>   
>>> So, just to make sure I understand: you are talking about a case where the INFO does contain a multipart message body, but only one of the mimes contains an actual info-package (the other mime(s) contains something else)?
>>>       
>> pretty much. And to distinguish those, you need more than C-T.
>> But I think as we have been discussing, if we only allow one info
>> package per INFO, then the Info-Package header belongs in the message,
>> not in the body part.
>>     
>  
> I don't think that defining Info-Package as a mime header would even be within the scope of the SIP WG, would it?
>  
> My assumption has been that the I-P header is in the SIP message part, and that causes the problem: in the case of multipart, how to associate the correct mime with the I-P header? I still think making assumptions on C-D is very dangerous, considering the very little experience we have of the C-D header in the first place.
>
>   
>> I'll revise your example a bit:
>>
>> INFO sip:foo@bar.com
>> To:...
>> From:...
>> Some-Header: CID:abcdefg
>> Info-Package: foo
>> Content-Type:multipart/mixed
>> Content-Length:...
>>
>> --boundary
>> Content-Type: application/foo-data
>> Content-Disposition: package;handling=required
>>
>> foo data
>> --boundary
>> Content-ID: abcdefg
>> Content-Type: application/some-header-data
>> Content-Disposition: by-reference;handling=optional
>>
>> some other (non-info package) data
>> --boundary--
>>
>> In the above I have used C-D of "package" to identify the part that
>> contains the info package. That is yet to be determined, but I think it
>> needs to be well defined, even if it is "render".
>>     
>
> Again, I don't think using C-D for the "association" is a good idea.
>  
>
>   
>> A more straightforward case would be:
>>
>> INFO sip:foo@bar.com
>> To:...
>> From:...
>> Info-Package: foo
>> Content-Type: application/foo-data
>> Content-Disposition: package;handling=required
>> Content-Length:10
>>
>> foo data
>>     
>
> ...assuming that we don't allow multipart in INFOs, yes.
>  
> Regards,
>  
> Christer
>  
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>
>   
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Sun Oct 26 04:50:48 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 96F373A698D;
	Sun, 26 Oct 2008 04:50:48 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2F9383A6A05
	for <sip@core3.amsl.com>; Sun, 26 Oct 2008 04:50:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.9
X-Spam-Level: 
X-Spam-Status: No, score=-5.9 tagged_above=-999 required=5 tests=[AWL=-0.251, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_37=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nTHEPRSUFNt1 for <sip@core3.amsl.com>;
	Sun, 26 Oct 2008 04:50:46 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id D63DE3A68AC
	for <sip@ietf.org>; Sun, 26 Oct 2008 04:50:45 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	926A9206F4; Sun, 26 Oct 2008 12:52:10 +0100 (CET)
X-AuditID: c1b4fb3e-af787bb00000537b-ac-490459ea51e4
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	6A5C620479; Sun, 26 Oct 2008 12:52:10 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 26 Oct 2008 12:52:10 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 26 Oct 2008 12:51:32 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCFC2@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: Content-Type
	vs	Info-Package [was RE: draft-ietf-sip-info-events-00:
	multiple	packages per INFO]
Thread-Index: Ack3X2AJSUmQ/ZXkStGQ0iGg3fV45gAAdCrL
References: <48FDEAD8.8010803@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>	<48FF2C45.7010204@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>	<4901BA73.1010700@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>	<4901C2B1.1050209@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>	<4901D025.6060302@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>	<490239C8.3020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>	<4902467E.3010603@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFBA@esealmw113.eemea.ericsson.se>
	<490456A8.6090109@zon net.nl>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Jeroen van Bemmel" <jbemmel@zonnet.nl>
X-OriginalArrivalTime: 26 Oct 2008 11:52:10.0176 (UTC)
	FILETIME=[47256C00:01C93761]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type
	vs	Info-Package [was RE: draft-ietf-sip-info-events-00:
	multiple	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi,

>Like I wrote before: adding the INFO package as a parameter to
>Content-Type solves all this. I don't think C-D is the right header,
>because the "disposition" would depend on the semantics of the event
>package. We simply need an additional qualifier to disambiguate the
>interpretation of the body

Dude, I agree with you :)
 
Regards,
 
Christer
 

Christer Holmberg wrote:
> Hi,
>
>  
>>> So, just to make sure I understand: you are talking about a case where the INFO does contain a multipart message body, but only one of the mimes contains an actual info-package (the other mime(s) contains something else)?
>>>      
>> pretty much. And to distinguish those, you need more than C-T.
>> But I think as we have been discussing, if we only allow one info
>> package per INFO, then the Info-Package header belongs in the message,
>> not in the body part.
>>    
> 
> I don't think that defining Info-Package as a mime header would even be within the scope of the SIP WG, would it?
> 
> My assumption has been that the I-P header is in the SIP message part, and that causes the problem: in the case of multipart, how to associate the correct mime with the I-P header? I still think making assumptions on C-D is very dangerous, considering the very little experience we have of the C-D header in the first place.
>
>  
>> I'll revise your example a bit:
>>
>> INFO sip:foo@bar.com
>> To:...
>> From:...
>> Some-Header: CID:abcdefg
>> Info-Package: foo
>> Content-Type:multipart/mixed
>> Content-Length:...
>>
>> --boundary
>> Content-Type: application/foo-data
>> Content-Disposition: package;handling=required
>>
>> foo data
>> --boundary
>> Content-ID: abcdefg
>> Content-Type: application/some-header-data
>> Content-Disposition: by-reference;handling=optional
>>
>> some other (non-info package) data
>> --boundary--
>>
>> In the above I have used C-D of "package" to identify the part that
>> contains the info package. That is yet to be determined, but I think it
>> needs to be well defined, even if it is "render".
>>    
>
> Again, I don't think using C-D for the "association" is a good idea.
> 
>
>  
>> A more straightforward case would be:
>>
>> INFO sip:foo@bar.com
>> To:...
>> From:...
>> Info-Package: foo
>> Content-Type: application/foo-data
>> Content-Disposition: package;handling=required
>> Content-Length:10
>>
>> foo data
>>    
>
> ...assuming that we don't allow multipart in INFOs, yes.
> 
> Regards,
> 
> Christer
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>
>  

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


From sip-bounces@ietf.org  Sun Oct 26 05:39:57 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D75FC3A6894;
	Sun, 26 Oct 2008 05:39:57 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4A04F3A67F4
	for <sip@core3.amsl.com>; Sun, 26 Oct 2008 05:39:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.639
X-Spam-Level: 
X-Spam-Status: No, score=-2.639 tagged_above=-999 required=5
	tests=[AWL=-0.040, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id s9f7sOLnBpin for <sip@core3.amsl.com>;
	Sun, 26 Oct 2008 05:39:55 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39])
	by core3.amsl.com (Postfix) with ESMTP id 6DA873A6894
	for <SIP@ietf.org>; Sun, 26 Oct 2008 05:39:54 -0700 (PDT)
Received: from ilexp01.ndc.lucent.com (h135-3-39-1.lucent.com [135.3.39.1])
	by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id m9QCfFLd021239;
	Sun, 26 Oct 2008 07:41:16 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by
	ilexp01.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 26 Oct 2008 07:41:15 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.28]) by
	DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 26 Oct 2008 13:41:13 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Sun, 26 Oct 2008 13:41:12 +0100
Message-ID: <5D1A7985295922448D5550C94DE29180024260BD@DEEXC1U01.de.lucent.com>
In-Reply-To: <4901D477.5010209@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] INFO Events Replacing or Updating INFO?
Thread-Index: Ack14JnRiguc0TggRZ65R9PLgM/dTwBhwgtw
References: <C9685920-CA2B-435A-9FA9-767BE5085AB6@standardstrack.com>
	<4901D477.5010209@cisco.com>
From: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>,
	"Eric Burger" <eburger@standardstrack.com>
X-OriginalArrivalTime: 26 Oct 2008 12:41:13.0432 (UTC)
	FILETIME=[2176A580:01C93768]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: SIP IETF <SIP@ietf.org>
Subject: Re: [Sip] INFO Events Replacing or Updating INFO?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I believe we can take that as a given condition.

Please validate the results of your comments so far in any new version,
and of course, it is open for all to make comments on this issue.

Note that there are some things that are not well defined in RFC 2796,
so primarily the WG will be looking for compatibility with what RFC 2976
actually says, rather than what one implementation may have interpreted.
So please back up any comments on compatibility issues with existing RFC
2976 text.


Regards

Keith 

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Paul Kyzivat
> Sent: Friday, October 24, 2008 2:58 PM
> To: Eric Burger
> Cc: SIP IETF
> Subject: Re: [Sip] INFO Events Replacing or Updating INFO?
> 
> 
> 
> Eric Burger wrote:
> 
> > [X] INFO Events should Obsolete RFC 2976 [ ] INFO Events 
> should Update 
> > RFC 2796, because ____________ [ ] I do not care what you do
> 
> But of course the new document must carefully define backward 
> compatible behavior. Its made a stab at that, and I expect it 
> to be complete before approval.
> 
> 	Thanks,
> 	Paul
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors@cs.columbia.edu for questions on current sip 
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Sun Oct 26 07:39:14 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 829F13A68CD;
	Sun, 26 Oct 2008 07:39:14 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C59983A68CD
	for <sip@core3.amsl.com>; Sun, 26 Oct 2008 07:39:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.576
X-Spam-Level: 
X-Spam-Status: No, score=-5.576 tagged_above=-999 required=5
	tests=[AWL=-0.373, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id za9rT00RHHeS for <sip@core3.amsl.com>;
	Sun, 26 Oct 2008 07:39:12 -0700 (PDT)
Received: from exprod6og102.obsmtp.com (exprod6og102.obsmtp.com [64.18.1.183])
	by core3.amsl.com (Postfix) with ESMTP id 10DBD3A686C
	for <sip@ietf.org>; Sun, 26 Oct 2008 07:39:08 -0700 (PDT)
Received: from source ([192.150.8.22]) by exprod6ob102.postini.com
	([64.18.5.12]) with SMTP; Sun, 26 Oct 2008 07:40:34 PDT
Received: from inner-relay-1.corp.adobe.com ([153.32.1.51])
	by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	m9QEeUE0017646; Sun, 26 Oct 2008 07:40:31 -0700 (PDT)
Received: from fe2.corp.adobe.com (fe2.corp.adobe.com [10.8.192.72])
	by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	m9QEeQiq026509; Sun, 26 Oct 2008 07:40:30 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by fe2.corp.adobe.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 26 Oct 2008 07:40:26 -0700
Received: from 10.7.240.126 ([10.7.240.126]) by namail5.corp.adobe.com
	([10.8.192.88]) with Microsoft Exchange Server HTTP-DAV ; 
	Sun, 26 Oct 2008 14:40:25 +0000
User-Agent: Microsoft-Entourage/12.13.0.080930
Date: Sun, 26 Oct 2008 09:40:24 -0500
From: Henry Sinnreich <hsinnrei@adobe.com>
To: Jiri Kuthan <jiri@iptel.org>
Message-ID: <C529EB88.949C%hsinnrei@adobe.com>
Thread-Topic: [Sip] draft-kuthan-sip-derive
Thread-Index: Ack3eMeIEs0MEplwl0eHvPDR+bGWBg==
In-Reply-To: <490395D3.2010303@iptel.org>
Mime-version: 1.0
X-OriginalArrivalTime: 26 Oct 2008 14:40:26.0299 (UTC)
	FILETIME=[C8E788B0:01C93778]
Cc: SIP IETF <sip@ietf.org>, Raphael.Coeffic@tekelec.com,
	Victor.Pascual@tekelec.com, Dorgham.Sisalem@tekelec.com,
	Jiri.Kuthan@tekelec.com
Subject: Re: [Sip] draft-kuthan-sip-derive
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Reading all those papers about VoIP attacks, including VoIP spam:
Why is nobody addressing the most obvious reason to give up phones, both
VoIP and TDM: Telemarketing and political campaign, polling calls?

Getting annoyed by telemarketers outweighs the benefits of having a landline
phone in the first place. For some reason, the mobile phone seems much safer
and the only worthwhile to keep.

Or just use our personal SIP services, such as the SIP server in my
residential (Intertex) gateway and giving our SIP URI only to friends...

Henry


On 10/25/08 4:55 PM, "Jiri Kuthan" <jiri@iptel.org> wrote:

> well, first of all, thank you very much for the positive comments.
> =

> secondly -- real is becoming really real :) In Germany, there has been
> recently an attack that could have been better absorbed using such
> a method, probably at best in combination with others. The attack
> is shortly described at http://www.ipcom.at/index.php?id=3D565. It
> was as simple as sending annoying INVITEs around, it is not clear
> really what could have been the attack purpose.
> =

> In fact, the attack is really trivial: it doesn't try to make
> messages appear credible, and any reasonably-configured SIP
> server would drop them right away. (none of the domains belongs
> to the server, the messages have little variance among them)
> =

> The victims' phones would not have been ringing at 3AM if they
> tried to verify who is calling them. (even though with so
> trivially formed requests a proxy server would drop them even
> before reaching the UAS).
> =

> -jiri
> =

> =

> Henry Sinnreich wrote:
>>   The =8C  Dialog Event foR Identity Verification=B9 is meeting IMO the =
real
>> need for preventing forged =B3From=B2 names and has the virtue of simpli=
city
>> as well.
>> It is analog to the email verification which is  successfully deployed
>> throughout the Internet at present.
>> =

>>   http://www3.ietf.org/proceedings/staging/draft-kuthan-sip-derive-00.txt
>> =

>> Thanks, Henry
>> =

>> =

>> ------------------------------------------------------------------------
>> =

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

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


From sip-bounces@ietf.org  Sun Oct 26 07:50:22 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 762DF3A6942;
	Sun, 26 Oct 2008 07:50:22 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8EED83A68C1
	for <sip@core3.amsl.com>; Sun, 26 Oct 2008 07:50:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.23
X-Spam-Level: 
X-Spam-Status: No, score=-6.23 tagged_above=-999 required=5 tests=[AWL=0.369, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zPTDST+Svqz5 for <sip@core3.amsl.com>;
	Sun, 26 Oct 2008 07:50:20 -0700 (PDT)
Received: from psmtp.com (exprod6ob111.obsmtp.com [64.18.1.26])
	by core3.amsl.com (Postfix) with ESMTP id D95DE3A681B
	for <sip@ietf.org>; Sun, 26 Oct 2008 07:50:19 -0700 (PDT)
Received: from source ([192.150.11.134]) by exprod6ob111.postini.com
	([64.18.5.12]) with SMTP; Sun, 26 Oct 2008 07:51:46 PDT
Received: from inner-relay-3.eur.adobe.com ([192.150.8.236])
	by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	m9QElQG3022334; Sun, 26 Oct 2008 07:47:27 -0700 (PDT)
Received: from apacmail.pac.adobe.com (apacmail.pac.adobe.com [130.248.36.99])
	by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id
	m9QEpeEL000550; Sun, 26 Oct 2008 07:51:41 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by
	apacmail.pac.adobe.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 26 Oct 2008 23:51:38 +0900
Received: from 10.7.240.126 ([10.7.240.126]) by namail5.corp.adobe.com
	([10.8.192.88]) with Microsoft Exchange Server HTTP-DAV ; 
	Sun, 26 Oct 2008 14:51:35 +0000
User-Agent: Microsoft-Entourage/12.13.0.080930
Date: Sun, 26 Oct 2008 09:51:35 -0500
From: Henry Sinnreich <hsinnrei@adobe.com>
To: Henry Sinnreich <henry@henrysinnreich.net>
Message-ID: <C529EE27.94A0%hsinnrei@adobe.com>
Thread-Topic: [Sip] draft-kuthan-sip-derive
Thread-Index: Ack3eld7GC65iknMB0OPYnFoQyNP5g==
In-Reply-To: <DF5D02DC-2C57-4A41-B3F3-EA6B2933D4CD@henrysinnreich.net>
Mime-version: 1.0
X-OriginalArrivalTime: 26 Oct 2008 14:51:38.0084 (UTC)
	FILETIME=[5951CA40:01C9377A]
Cc: SIP IETF <sip@ietf.org>, Raphael.Coeffic@tekelec.com,
	Victor.Pascual@tekelec.com, Dorgham.Sisalem@tekelec.com,
	Jiri.Kuthan@tekelec.com
Subject: Re: [Sip] draft-kuthan-sip-derive
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Folks,

To prove me wrong, someone just sent this forged email

> email verification successfully deployed throughout the internet?
> really?
> =

> Yes, this is a demonstration of forged From addresses. Very sloppily
> done, so you can see who sent it.

It was not me for sure.
Then how come some many web sites include the email in their verification?

Henry

On 10/25/08 10:08 PM, "Henry Sinnreich" <henry@henrysinnreich.net> wrote:

> =

> email verification successfully deployed throughout the internet?
> really?
> =

> Yes, this is a demonstration of forged From addresses. Very sloppily
> done, so you can see who sent it.
> =

> On Oct 25, 2008, at 12:02 PM, Henry Sinnreich wrote:
> =

>> The =8CDialog Event foR Identity Verification=B9 is meeting IMO the real
>> need for preventing forged =B3From=B2 names and has the virtue of
>> simplicity as well.
>> It is analog to the email verification which is  successfully
>> deployed throughout the Internet at present.
>> =

>>  http://www3.ietf.org/proceedings/staging/draft-kuthan-sip-derive-00.txt
>> =

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


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


From sip-bounces@ietf.org  Sun Oct 26 11:07:35 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 671B93A681A;
	Sun, 26 Oct 2008 11:07:35 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 166FD3A68CD
	for <sip@core3.amsl.com>; Sun, 26 Oct 2008 11:07:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id u65yldh1OoL5 for <sip@core3.amsl.com>;
	Sun, 26 Oct 2008 11:07:33 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20])
	by core3.amsl.com (Postfix) with SMTP id 3535E3A681A
	for <sip@ietf.org>; Sun, 26 Oct 2008 11:07:31 -0700 (PDT)
Received: (qmail invoked by alias); 26 Oct 2008 18:08:54 -0000
Received: from a91-154-101-110.elisa-laajakaista.fi (EHLO 4FIL42860)
	[91.154.101.110]
	by mail.gmx.net (mp024) with SMTP; 26 Oct 2008 19:08:54 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+TpgARDdCTviELMdDQQHE8muDAR1/K9lDKrrYNPO
	NwKFC2kTGFGYKz
From: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>
To: "'Henry Sinnreich'" <hsinnrei@adobe.com>, <Jiri.Kuthan@tekelec.com>,
	<Dorgham.Sisalem@tekelec.com>, <Raphael.Coeffic@tekelec.com>,
	<Victor.Pascual@tekelec.com>, "'SIP IETF'" <sip@ietf.org>
References: <C528BB73.9465%hsinnrei@adobe.com>
Date: Sun, 26 Oct 2008 20:08:57 +0200
Message-ID: <01b301c93795$ed79ff60$04ffa8c0@nsnintra.net>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Ack2w4hM/9fAhyb0xEiu+9CpPTWQdgA0V+Mg
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <C528BB73.9465%hsinnrei@adobe.com>
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.73
Subject: Re: [Sip] draft-kuthan-sip-derive
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Given that only 2 out of 50 implementations had support for SIP Identity at
SIPit#23 I wonder how urgent the need for anything beyond P-Asserted-ID
actually is: 
https://www.sipit.net/SIPit23_Summary
 
Ciao
Hannes
 
PS: Btw, how is your document different from
http://tools.ietf.org/html/draft-wing-sip-e164-rrc-01


________________________________

	From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf
Of Henry Sinnreich
	Sent: 25 October, 2008 20:03
	To: Jiri.Kuthan@tekelec.com; Dorgham.Sisalem@tekelec.com;
Raphael.Coeffic@tekelec.com; Victor.Pascual@tekelec.com; SIP IETF
	Subject: [Sip] draft-kuthan-sip-derive
	
	
	The 'Dialog Event foR Identity Verification' is meeting IMO the real
need for preventing forged "From" names and has the virtue of simplicity as
well. 
	It is analog to the email verification which is  successfully
deployed throughout the Internet at present.
	
	
http://www3.ietf.org/proceedings/staging/draft-kuthan-sip-derive-00.txt
	
	Thanks, Henry
	


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


From sip-bounces@ietf.org  Sun Oct 26 11:44:46 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 98F263A6B16;
	Sun, 26 Oct 2008 11:44:46 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 269D13A6A1D
	for <sip@core3.amsl.com>; Sun, 26 Oct 2008 11:44:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.513
X-Spam-Level: 
X-Spam-Status: No, score=-2.513 tagged_above=-999 required=5 tests=[AWL=0.086, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Js6g71CzllvP for <sip@core3.amsl.com>;
	Sun, 26 Oct 2008 11:44:44 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20])
	by core3.amsl.com (Postfix) with SMTP id 932AB3A6821
	for <sip@ietf.org>; Sun, 26 Oct 2008 11:44:42 -0700 (PDT)
Received: (qmail invoked by alias); 26 Oct 2008 18:46:07 -0000
Received: from a91-154-101-110.elisa-laajakaista.fi (EHLO 4FIL42860)
	[91.154.101.110]
	by mail.gmx.net (mp061) with SMTP; 26 Oct 2008 19:46:07 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19W+yE92tZWhzeUB6e2lc7W+Hfp4VSjTnpWayQ8NE
	9eKNNQhPQ18iHn
From: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>
To: "'Henry Sinnreich'" <hsinnrei@adobe.com>, "'Jiri Kuthan'" <jiri@iptel.org>
References: <490395D3.2010303@iptel.org> <C529EB88.949C%hsinnrei@adobe.com>
Date: Sun, 26 Oct 2008 20:45:59 +0200
Message-ID: <01c101c9379b$20967680$04ffa8c0@nsnintra.net>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Ack3eMeIEs0MEplwl0eHvPDR+bGWBgAIfQqA
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <C529EB88.949C%hsinnrei@adobe.com>
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.74
Cc: 'SIP IETF' <sip@ietf.org>, Raphael.Coeffic@tekelec.com,
	Victor.Pascual@tekelec.com, Dorgham.Sisalem@tekelec.com,
	Jiri.Kuthan@tekelec.com
Subject: Re: [Sip] draft-kuthan-sip-derive
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

> In Germany, 
>there has been 
>> recently an attack that could have been better absorbed using such a 
>> method, probably at best in combination with others. The attack is 
>> shortly described at http://www.ipcom.at/index.php?id=565. It was as 
>> simple as sending annoying INVITEs around, it is not clear 
>really what 
>> could have been the attack purpose.

I don't see how the attack in Germany (that by some has even been put in the
context of SPIT; I believe wrongly) has anything todo with any of the drafts
discussed in this group on SIP Identity.  


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


From sip-bounces@ietf.org  Sun Oct 26 11:59:14 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7470C3A6B45;
	Sun, 26 Oct 2008 11:59:14 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 602FB3A6B43
	for <sip@core3.amsl.com>; Sun, 26 Oct 2008 11:59:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.277
X-Spam-Level: 
X-Spam-Status: No, score=-6.277 tagged_above=-999 required=5
	tests=[AWL=-0.278, BAYES_00=-2.599, J_CHICKENPOX_37=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id NlHizQj-VgzT for <sip@core3.amsl.com>;
	Sun, 26 Oct 2008 11:59:12 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 2CDE63A6A27
	for <sip@ietf.org>; Sun, 26 Oct 2008 11:59:12 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,489,1220227200"; d="scan'208";a="25725641"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 26 Oct 2008 19:00:39 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9QJ0dJD022658; 
	Sun, 26 Oct 2008 15:00:39 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9QJ0d3h000488;
	Sun, 26 Oct 2008 19:00:39 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 26 Oct 2008 15:00:38 -0400
Received: from [10.86.249.64] ([10.86.249.64]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 26 Oct 2008 15:00:38 -0400
Message-ID: <4904BE56.7050704@cisco.com>
Date: Sun, 26 Oct 2008 15:00:38 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Jeroen van Bemmel <jbemmel@zonnet.nl>
References: <48FDEAD8.8010803@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>	<48FF2C45.7010204@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>	<4901BA73.1010700@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>	<4901C2B1.1050209@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>	<4901D025.6060302@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>	<490239C8.3020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>	<4902467E.3010603@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFBA@esealmw113.eemea.ericsson.se>
	<490456A8.6090109@zon net.nl>
In-Reply-To: <490456A8.6090109@zonnet.nl>
X-OriginalArrivalTime: 26 Oct 2008 19:00:38.0514 (UTC)
	FILETIME=[22827D20:01C9379D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3663; t=1225047639;
	x=1225911639; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20Content-Type=20vs=09Info-Package=0A=20[was=20RE=3A=20dra
	ft-ietf-sip-info-events-00=3A=20multiple=09packages=20per=20
	INFO] |Sender:=20
	|To:=20Jeroen=20van=20Bemmel=20<jbemmel@zonnet.nl>;
	bh=6Wx9LbOQm8sq0r5ZTjymVOakbIFav90DBsDN/8804i8=;
	b=UDx4l2qlH0TY1okQXJbEb3b2Jsm2w57vZc+SOAQpxtd3553K8LYErRnPmb
	q0eXaOjQKeUAOWnlAAnYUtXTI9JNPLIT/wMKWC1w4yS/RbmWvc42c0tFDK6S
	3Gi+R6Ojk6;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type
 vs	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple	packages
 per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Jeroen van Bemmel wrote:
> Christer,
> 
> Like I wrote before: adding the INFO package as a parameter to 
> Content-Type solves all this. I don't think C-D is the right header, 
> because the "disposition" would depend on the semantics of the event 
> package. We simply need an additional qualifier to disambiguate the 
> interpretation of the body

If you mentioned this before I missed it.

Its an interesting idea. But I don't think it is technicallyh feasible.
AFAIK the parameters to a C-T must be defined as part of the definition 
of the C-T. That wold mean that only yet-to-be-defined C-Ts could be 
used for info packages.

Whether C-D is suitable to identifhy the info package depends on whether 
it makes any sense to use C-D as an independent control over processing 
of the package, in addition to the definition of the package itself. I 
certainly haven't seen it that way. I would need a good use case to 
convince me that it is a useful thing to do.

	Thanks,
	Paul

> 
> Regards,
> Jeroen
> 
> Christer Holmberg wrote:
>> Hi,
>>
>>  
>>>> So, just to make sure I understand: you are talking about a case 
>>>> where the INFO does contain a multipart message body, but only one 
>>>> of the mimes contains an actual info-package (the other mime(s) 
>>>> contains something else)?
>>>>       
>>> pretty much. And to distinguish those, you need more than C-T.
>>> But I think as we have been discussing, if we only allow one info
>>> package per INFO, then the Info-Package header belongs in the message,
>>> not in the body part.
>>>     
>>  
>> I don't think that defining Info-Package as a mime header would even 
>> be within the scope of the SIP WG, would it?
>>  
>> My assumption has been that the I-P header is in the SIP message part, 
>> and that causes the problem: in the case of multipart, how to 
>> associate the correct mime with the I-P header? I still think making 
>> assumptions on C-D is very dangerous, considering the very little 
>> experience we have of the C-D header in the first place.
>>
>>  
>>> I'll revise your example a bit:
>>>
>>> INFO sip:foo@bar.com
>>> To:...
>>> From:...
>>> Some-Header: CID:abcdefg
>>> Info-Package: foo
>>> Content-Type:multipart/mixed
>>> Content-Length:...
>>>
>>> --boundary
>>> Content-Type: application/foo-data
>>> Content-Disposition: package;handling=required
>>>
>>> foo data
>>> --boundary
>>> Content-ID: abcdefg
>>> Content-Type: application/some-header-data
>>> Content-Disposition: by-reference;handling=optional
>>>
>>> some other (non-info package) data
>>> --boundary--
>>>
>>> In the above I have used C-D of "package" to identify the part that
>>> contains the info package. That is yet to be determined, but I think it
>>> needs to be well defined, even if it is "render".
>>>     
>>
>> Again, I don't think using C-D for the "association" is a good idea.
>>  
>>
>>  
>>> A more straightforward case would be:
>>>
>>> INFO sip:foo@bar.com
>>> To:...
>>> From:...
>>> Info-Package: foo
>>> Content-Type: application/foo-data
>>> Content-Disposition: package;handling=required
>>> Content-Length:10
>>>
>>> foo data
>>>     
>>
>> ...assuming that we don't allow multipart in INFOs, yes.
>>  
>> Regards,
>>  
>> Christer
>>  
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sipping@ietf.org for new developments on the application of sip
>>
>>   
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Sun Oct 26 13:03:40 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E955D3A6B6A;
	Sun, 26 Oct 2008 13:03:39 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 90CFE3A6B66
	for <sip@core3.amsl.com>; Sun, 26 Oct 2008 13:03:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level: 
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id lSleHPmP3FDY for <sip@core3.amsl.com>;
	Sun, 26 Oct 2008 13:03:37 -0700 (PDT)
Received: from taimen.tutpro.com (harjus.tutpro.com [192.98.100.3])
	by core3.amsl.com (Postfix) with ESMTP id 7FED23A6820
	for <sip@ietf.org>; Sun, 26 Oct 2008 13:03:36 -0700 (PDT)
Received: by taimen.tutpro.com (Postfix, from userid 1000)
	id 77EC433ABC2; Sun, 26 Oct 2008 22:05:07 +0200 (EET)
MIME-Version: 1.0
Message-ID: <18692.52595.364526.196499@harjus.tutpro.com>
Date: Sun, 26 Oct 2008 22:05:07 +0200
To: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>
In-Reply-To: <01b301c93795$ed79ff60$04ffa8c0@nsnintra.net>
References: <C528BB73.9465%hsinnrei@adobe.com>
	<01b301c93795$ed79ff60$04ffa8c0@nsnintra.net>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: Dorgham.Sisalem@tekelec.com, 'SIP IETF' <sip@ietf.org>,
	Raphael.Coeffic@tekelec.com,
	'Henry Sinnreich' <hsinnrei@adobe.com>, Jiri.Kuthan@tekelec.com,
	Victor.Pascual@tekelec.com
Subject: Re: [Sip] draft-kuthan-sip-derive
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hannes Tschofenig writes:

 > Given that only 2 out of 50 implementations had support for SIP Identity at
 > SIPit#23 I wonder how urgent the need for anything beyond P-Asserted-ID
 > actually is: 
 > https://www.sipit.net/SIPit23_Summary

pai does not help if you receive a request from anywhere on the
internet.

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


From sip-bounces@ietf.org  Sun Oct 26 13:08:24 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B3D6E3A685C;
	Sun, 26 Oct 2008 13:08:24 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 530683A685C
	for <sip@core3.amsl.com>; Sun, 26 Oct 2008 13:08:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KM45Oit0cEVg for <sip@core3.amsl.com>;
	Sun, 26 Oct 2008 13:08:22 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20])
	by core3.amsl.com (Postfix) with SMTP id 0CEBB3A6820
	for <sip@ietf.org>; Sun, 26 Oct 2008 13:08:21 -0700 (PDT)
Received: (qmail invoked by alias); 26 Oct 2008 20:09:47 -0000
Received: from a91-154-101-110.elisa-laajakaista.fi (EHLO 4FIL42860)
	[91.154.101.110]
	by mail.gmx.net (mp059) with SMTP; 26 Oct 2008 21:09:47 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/3KMQHJkT3KIDzQeD/0Vf2eTU81toUueLGW9F5Ra
	5Ge8b5hclASaJg
From: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>
To: "'Juha Heinanen'" <jh@tutpro.com>
References: <C528BB73.9465%hsinnrei@adobe.com><01b301c93795$ed79ff60$04ffa8c0@nsnintra.net>
	<18692.52595.364526.196499@harjus.tutpro.com>
Date: Sun, 26 Oct 2008 22:09:54 +0200
Message-ID: <01c601c937a6$d09eb2d0$04ffa8c0@nsnintra.net>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Ack3piHsjnF0rwH8QWSXcLz09RpOZAAACwBg
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <18692.52595.364526.196499@harjus.tutpro.com>
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.75
Cc: Dorgham.Sisalem@tekelec.com, 'SIP IETF' <sip@ietf.org>,
	Raphael.Coeffic@tekelec.com,
	'Henry Sinnreich' <hsinnrei@adobe.com>, Jiri.Kuthan@tekelec.com,
	Victor.Pascual@tekelec.com
Subject: Re: [Sip] draft-kuthan-sip-derive
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


>Hannes Tschofenig writes:
>
> > Given that only 2 out of 50 implementations had support for 
>SIP Identity at  > SIPit#23 I wonder how urgent the need for 
>anything beyond P-Asserted-ID  > actually is: 
> > https://www.sipit.net/SIPit23_Summary
>
>pai does not help if you receive a request from anywhere on 
>the internet.

Depends a bit on what you call "YOU receive". 

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


From sip-bounces@ietf.org  Sun Oct 26 14:08:41 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2B9943A6892;
	Sun, 26 Oct 2008 14:08:41 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 679893A6892
	for <sip@core3.amsl.com>; Sun, 26 Oct 2008 14:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.574
X-Spam-Level: 
X-Spam-Status: No, score=-2.574 tagged_above=-999 required=5 tests=[AWL=0.025, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6UfTtGhMfvlI for <sip@core3.amsl.com>;
	Sun, 26 Oct 2008 14:08:39 -0700 (PDT)
Received: from taimen.tutpro.com (harjus.tutpro.com [192.98.100.3])
	by core3.amsl.com (Postfix) with ESMTP id 972C03A6820
	for <sip@ietf.org>; Sun, 26 Oct 2008 14:08:39 -0700 (PDT)
Received: by taimen.tutpro.com (Postfix, from userid 1000)
	id 8F5F133ABC2; Sun, 26 Oct 2008 23:10:09 +0200 (EET)
MIME-Version: 1.0
Message-ID: <18692.56497.467318.995252@harjus.tutpro.com>
Date: Sun, 26 Oct 2008 23:10:09 +0200
To: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>
In-Reply-To: <01c601c937a6$d09eb2d0$04ffa8c0@nsnintra.net>
References: <C528BB73.9465%hsinnrei@adobe.com>
	<01b301c93795$ed79ff60$04ffa8c0@nsnintra.net>
	<18692.52595.364526.196499@harjus.tutpro.com>
	<01c601c937a6$d09eb2d0$04ffa8c0@nsnintra.net>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: Dorgham.Sisalem@tekelec.com, 'SIP IETF' <sip@ietf.org>,
	Raphael.Coeffic@tekelec.com,
	'Henry Sinnreich' <hsinnrei@adobe.com>, Jiri.Kuthan@tekelec.com,
	Victor.Pascual@tekelec.com
Subject: Re: [Sip] draft-kuthan-sip-derive
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hannes Tschofenig writes:

 > >pai does not help if you receive a request from anywhere on 
 > >the internet.
 > 
 > Depends a bit on what you call "YOU receive". 

if you cannot trust the proxy or ua you receive the request from, pai
header has no value.

-- juha

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


From sip-bounces@ietf.org  Sun Oct 26 16:07:21 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 362C63A6A56;
	Sun, 26 Oct 2008 16:07:21 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E1F5D3A67B1
	for <sip@core3.amsl.com>; Sun, 26 Oct 2008 16:07:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.301
X-Spam-Level: 
X-Spam-Status: No, score=0.301 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2Ac7tmsdem8c for <sip@core3.amsl.com>;
	Sun, 26 Oct 2008 16:07:19 -0700 (PDT)
Received: from mail-gx0-f16.google.com (mail-gx0-f16.google.com
	[209.85.217.16])
	by core3.amsl.com (Postfix) with ESMTP id C8E1C28C111
	for <sip@ietf.org>; Sun, 26 Oct 2008 16:05:52 -0700 (PDT)
Received: by gxk9 with SMTP id 9so1736393gxk.13
	for <sip@ietf.org>; Sun, 26 Oct 2008 16:05:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=0SKwbMzt006xNT16EolTy+A6hKjz8FHmcbcmBTxPrjs=;
	b=os14cSCCYVaq4R6BZ3Va9uv+vc66udrvj62m61TZJgd/U0F/uw5fM55JmHzqgVhSg5
	WBwjt1/V6nzcuDWnw4ELUTkIdz43Y0G24VkZuv+l09lsyfZmtN880qnq4YxSZN3fVC7/
	Ttcd9E3gs2EZymxtJhYQNa90QTt8713QP311g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=dv12wYJIBbd+1AoGEPKA6aNWlzkofqoqpfuYfgruDKMyAI7RgKqzG4b+Db53ZW99rz
	sFPGVV4OTm/8O7OYze2JtpufKRn1Dskc5OcBg0asFX63b9a9HIwSMuDaiNtZw8r+Ytk5
	Vp7+3zp3eDvfDFlh92wnW6XiG9SZsX2EmQ9Qg=
Received: by 10.90.93.13 with SMTP id q13mr4068212agb.32.1225062352085;
	Sun, 26 Oct 2008 16:05:52 -0700 (PDT)
Received: by 10.90.114.2 with HTTP; Sun, 26 Oct 2008 16:05:51 -0700 (PDT)
Message-ID: <618e24240810261605w3d358b5bo52b3b725c7080d22@mail.gmail.com>
Date: Mon, 27 Oct 2008 00:05:51 +0100
From: "=?UTF-8?Q?Victor_Pascual_=C3=81vila?=" <victor.pascual.avila@gmail.com>
To: "Juha Heinanen" <jh@tutpro.com>
In-Reply-To: <18692.56497.467318.995252@harjus.tutpro.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <C528BB73.9465%hsinnrei@adobe.com>
	<01b301c93795$ed79ff60$04ffa8c0@nsnintra.net>
	<18692.52595.364526.196499@harjus.tutpro.com>
	<01c601c937a6$d09eb2d0$04ffa8c0@nsnintra.net>
	<18692.56497.467318.995252@harjus.tutpro.com>
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] draft-kuthan-sip-derive
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

T24gU3VuLCBPY3QgMjYsIDIwMDggYXQgMTA6MTAgUE0sIEp1aGEgSGVpbmFuZW4gPGpoQHR1dHBy
by5jb20+IHdyb3RlOgo+IEhhbm5lcyBUc2Nob2ZlbmlnIHdyaXRlczoKPgo+ICA+ID5wYWkgZG9l
cyBub3QgaGVscCBpZiB5b3UgcmVjZWl2ZSBhIHJlcXVlc3QgZnJvbSBhbnl3aGVyZSBvbgo+ICA+
ID50aGUgaW50ZXJuZXQuCj4gID4KPiAgPiBEZXBlbmRzIGEgYml0IG9uIHdoYXQgeW91IGNhbGwg
IllPVSByZWNlaXZlIi4KPgo+IGlmIHlvdSBjYW5ub3QgdHJ1c3QgdGhlIHByb3h5IG9yIHVhIHlv
dSByZWNlaXZlIHRoZSByZXF1ZXN0IGZyb20sIHBhaQo+IGhlYWRlciBoYXMgbm8gdmFsdWUuCgpJ
IGNvbnNpZGVyIFsxXSB0byBnaXZlIGEgZ29vZCBkZXNjcmlwdGlvbi4KClsxXSBodHRwOi8vdG9v
bHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1lbHdlbGwtc2lwLWUyZS1pZGVudGl0eS1pbXBvcnRhbnQt
MDEjc2VjdGlvbi0yLjIKClRoYW5rcywKLS0gClZpY3RvciBQYXNjdWFsIMOBdmlsYQpfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpTaXAgbWFpbGluZyBsaXN0
ICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpcApUaGlzIGxpc3QgaXMg
Zm9yIE5FVyBkZXZlbG9wbWVudCBvZiB0aGUgY29yZSBTSVAgUHJvdG9jb2wKVXNlIHNpcC1pbXBs
ZW1lbnRvcnNAY3MuY29sdW1iaWEuZWR1IGZvciBxdWVzdGlvbnMgb24gY3VycmVudCBzaXAKVXNl
IHNpcHBpbmdAaWV0Zi5vcmcgZm9yIG5ldyBkZXZlbG9wbWVudHMgb24gdGhlIGFwcGxpY2F0aW9u
IG9mIHNpcA==


From sip-bounces@ietf.org  Sun Oct 26 17:50:24 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 979753A6823;
	Sun, 26 Oct 2008 17:50:24 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A5D923A6823
	for <sip@core3.amsl.com>; Sun, 26 Oct 2008 17:50:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5
	tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id w-yWhlW01SWf for <sip@core3.amsl.com>;
	Sun, 26 Oct 2008 17:50:22 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33])
	by core3.amsl.com (Postfix) with ESMTP id D0AC33A67E1
	for <sip@ietf.org>; Sun, 26 Oct 2008 17:50:22 -0700 (PDT)
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id m9R0jcSq025569;
	Sun, 26 Oct 2008 19:45:38 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by
	ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 26 Oct 2008 19:44:37 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.28]) by
	DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 01:44:34 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Mon, 27 Oct 2008 01:44:33 +0100
Message-ID: <5D1A7985295922448D5550C94DE29180024260D5@DEEXC1U01.de.lucent.com>
In-Reply-To: <5736B897-8C58-4923-AB2B-8AE1BA9B2747@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: Content-Type vsInfo-Package
	[was RE: draft-ietf-sip-info-events-00: multiplepackages per
	INFO]
Thread-Index: Ack2IKzq4FhnOAYARoKHk3ecuFaQlgBezCCQ
References: <48FDEAD8.8010803@cisco.com><CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se><48FF2C45.7010204@cisco.com><CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se><093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se><5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se><07AD9FC7-C9D2-4229-B364-BD051728BF37@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF083CCFB6@esealmw113.eemea.ericsson.se>
	<5736B897-8C58-4923-AB2B-8AE1BA9B2747@softarmor.com>
From: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: "Dean Willis" <dean.willis@softarmor.com>,
	"Christer Holmberg" <christer.holmberg@ericsson.com>
X-OriginalArrivalTime: 27 Oct 2008 00:44:34.0605 (UTC)
	FILETIME=[2E9415D0:01C937CD]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Cc: SIP IETF <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type
	vsInfo-Package [was RE: draft-ietf-sip-info-events-00:
	multiplepackages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Should we even allow bodies that do not relate to info packages in INFO
messages (legacy issues excepted).

If I had a SDP offer to send at the same time as a body for an info
package, I suspect I would be told to send one in a reINVITE and the
other in an INFO, rather than combine them in a single message.

Whatever the answer to this question, I guest the draft would need a
paragraph to cover it.

Regards

Keith

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Dean Willis
> Sent: Friday, October 24, 2008 10:36 PM
> To: Christer Holmberg
> Cc: SIP IETF; Paul Kyzivat
> Subject: Re: [Sip] draft-ietf-sip-info-events-00: 
> Content-Type vsInfo-Package [was RE: 
> draft-ietf-sip-info-events-00: multiplepackages per INFO]
> 
> 
> On Oct 24, 2008, at 4:32 PM, Christer Holmberg wrote:
> 
> > Hi,
> >
> >>> [Christer] I agree that a package could be associated 
> with a number 
> >>> of content types. But, since the Info-Package header shows which 
> >>> package is included, I just wonder why we can't use a common C-T 
> >>> mime.
> >>>
> >>
> >> Then which of the multiple bodies, each of which carries 
> the same C-T 
> >> mime marking, is which? Are you relying on ordering?
> >
> > Let's assume BOTH bodies contain C-T: image/jpeg. How do you know 
> > which is associated with the info package?
> >
> 
> So you have a multipart body, with one or more parts related to an  
> INFO package, and other parts related to something else, such 
> as AIB,  
> E2M, etc. Right?
> 
> The content-disposition of the body parts related to INFO packages  
> needs to differentiate them from the other body parts.
> 
> --
> Dean
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Sun Oct 26 18:06:00 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 448F73A68B3;
	Sun, 26 Oct 2008 18:06:00 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E15583A67E1
	for <sip@core3.amsl.com>; Sun, 26 Oct 2008 18:05:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tMwY57AgVOwh for <sip@core3.amsl.com>;
	Sun, 26 Oct 2008 18:05:57 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id A50363A6825
	for <sip@ietf.org>; Sun, 26 Oct 2008 18:05:57 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,489,1220227200"; d="scan'208";a="25740349"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 27 Oct 2008 01:05:56 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9R15uOx012675; 
	Sun, 26 Oct 2008 21:05:56 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9R15umk026278;
	Mon, 27 Oct 2008 01:05:56 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 26 Oct 2008 21:05:55 -0400
Received: from [10.86.249.64] ([10.86.249.64]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 26 Oct 2008 21:05:55 -0400
Message-ID: <490513F2.1070900@cisco.com>
Date: Sun, 26 Oct 2008 21:05:54 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
References: <48FDEAD8.8010803@cisco.com><CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se><48FF2C45.7010204@cisco.com><CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se><093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se><5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se><07AD9FC7-C9D2-4229-B364-BD051728BF37@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF083CCFB6@esealmw113.eemea.ericsson.se>
	<5736B897-8C58-4923-AB2B-8AE1BA9B2747@softarmor.com>
	<5D1A7985295922448D5550C94DE29180024260D5@DEEXC1U01.de.lucent.com>
In-Reply-To: <5D1A7985295922448D5550C94DE29180024260D5@DEEXC1U01.de.lucent.com>
X-OriginalArrivalTime: 27 Oct 2008 01:05:55.0774 (UTC)
	FILETIME=[2A36F5E0:01C937D0]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2826; t=1225069556;
	x=1225933556; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20Content-Type=20vsInfo-Package=0A=20[was=20RE=3A=20draft-
	ietf-sip-info-events-00=3A=20multiplepackages=20per=20INFO]
	|Sender:=20
	|To:=20=22DRAGE,=20Keith=20\(Keith\)=22=20<drage@alcatel-lu
	cent.com>; bh=AUqPdpN6hhFuIWJH64DUwVoizWj5kl3sbmuonyd2XTs=;
	b=IFmCociPTjaMEe1fNHbuviz43iaNGYa7K+ERho9bcJl93t1UmR/o8l6d7I
	It4A2vddMRbzZE3oUkorzdCnAeu7O04+HmRhzuc86AC5zI9jnatj+byShfn6
	keK6cKuMsJ;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type
 vsInfo-Package [was RE: draft-ietf-sip-info-events-00: multiplepackages per
 INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



DRAGE, Keith (Keith) wrote:
> Should we even allow bodies that do not relate to info packages in INFO
> messages (legacy issues excepted).

I think we must allow it. The use case I have in mind is when there is a 
header in the message that contains a URI, and the desire is to use a 
CID URI referencing a  body part in the message. (To avoid the need to 
have or access a separate server.

An example of this would be a Geolocation header. (Although the draft 
for that seems to have expired.)

I don't know if that precise case makes practical sense, but its an 
example of a general mechanism we have that should not be excluded.

Another example (though improbable) is an S/MIME body.

> If I had a SDP offer to send at the same time as a body for an info
> package, I suspect I would be told to send one in a reINVITE and the
> other in an INFO, rather than combine them in a single message.

Yes, it is certainly true that sending a SDP for purposes of O/A is 
inappropriate in INFO.

> Whatever the answer to this question, I guest the draft would need a
> paragraph to cover it.

Yes, I agree.

	Thanks,
	Paul

> Regards
> 
> Keith
> 
>> -----Original Message-----
>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
>> Behalf Of Dean Willis
>> Sent: Friday, October 24, 2008 10:36 PM
>> To: Christer Holmberg
>> Cc: SIP IETF; Paul Kyzivat
>> Subject: Re: [Sip] draft-ietf-sip-info-events-00: 
>> Content-Type vsInfo-Package [was RE: 
>> draft-ietf-sip-info-events-00: multiplepackages per INFO]
>>
>>
>> On Oct 24, 2008, at 4:32 PM, Christer Holmberg wrote:
>>
>>> Hi,
>>>
>>>>> [Christer] I agree that a package could be associated 
>> with a number 
>>>>> of content types. But, since the Info-Package header shows which 
>>>>> package is included, I just wonder why we can't use a common C-T 
>>>>> mime.
>>>>>
>>>> Then which of the multiple bodies, each of which carries 
>> the same C-T 
>>>> mime marking, is which? Are you relying on ordering?
>>> Let's assume BOTH bodies contain C-T: image/jpeg. How do you know 
>>> which is associated with the info package?
>>>
>> So you have a multipart body, with one or more parts related to an  
>> INFO package, and other parts related to something else, such 
>> as AIB,  
>> E2M, etc. Right?
>>
>> The content-disposition of the body parts related to INFO packages  
>> needs to differentiate them from the other body parts.
>>
>> --
>> Dean
>>
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sipping@ietf.org for new developments on the application of sip
>>
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct 27 00:06:25 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2239F3A693E;
	Mon, 27 Oct 2008 00:06:25 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8DED63A693E
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 00:06:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.786
X-Spam-Level: 
X-Spam-Status: No, score=-0.786 tagged_above=-999 required=5 tests=[AWL=0.324, 
	BAYES_05=-1.11]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id hcs2l8oNxVkY for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 00:06:22 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id C204E3A6925
	for <sip@ietf.org>; Mon, 27 Oct 2008 00:06:22 -0700 (PDT)
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9R76H9U031489
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Mon, 27 Oct 2008 02:06:19 -0500
Message-Id: <75F6E6CD-446C-4F59-A3F9-2258866D782F@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Juha Heinanen <jh@tutpro.com>
In-Reply-To: <18692.12450.342904.645834@harjus.tutpro.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 27 Oct 2008 02:06:11 -0500
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<200810260100.38716.ibc@aliax.net>
	<18692.12450.342904.645834@harjus.tutpro.com>
X-Mailer: Apple Mail (2.929.2)
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR
	Identity	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 26, 2008, at 3:56 AM, Juha Heinanen wrote:

> I=F1aki Baz Castillo writes:
>
>> PD: Thanks for proposing a feasible solution instead of proposing  =

>> exotic
>> specifications that depend on other specifications which nobody
>> implement.
>
> i agree with this and long time ago (before presence existed)  =

> proposed a
> similar (if not even simpler) solution:
>
> - my phone receives a call from sip:foo@bar
>
> - my phone sends a query to sip:foo@bar asking if foo@bar is trying to
>  call me
>
> in order for this to work, the phone from which sip:foo@bar is  =

> calling,
> needs to be registered.

Not only that, but it needs to deal with forking, or it needs to  =

require all the calls originating @bar go through the @bar proxy/sbc.

Jonathan may be right -- perhaps we should revisit the core SIP specs  =

assuming universal deployment of SBCs. It still won't be right, but at  =

least we'd  get some new problems to chew on.

--
Dean

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


From sip-bounces@ietf.org  Mon Oct 27 00:08:02 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D37283A6925;
	Mon, 27 Oct 2008 00:08:02 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 327FB3A68A2
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 00:08:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.489
X-Spam-Level: 
X-Spam-Status: No, score=-1.489 tagged_above=-999 required=5 tests=[AWL=0.810, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id dKx-8BhctUB1 for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 00:08:01 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 595B43A6838
	for <sip@ietf.org>; Mon, 27 Oct 2008 00:08:01 -0700 (PDT)
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9R77vFm031499
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Mon, 27 Oct 2008 02:07:58 -0500
Message-Id: <57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: =?ISO-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
In-Reply-To: <200810261145.19745.ibc@aliax.net>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 27 Oct 2008 02:07:50 -0500
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>
	<200810261145.19745.ibc@aliax.net>
X-Mailer: Apple Mail (2.929.2)
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR Identity
	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 26, 2008, at 5:45 AM, I=F1aki Baz Castillo wrote:

> El Domingo, 26 de Octubre de 2008, Dean Willis escribi=F3:
>>> A new I-D, draft-kuthan-sip-derive-00, was just submitted. Your
>>> comments are always welcome.
>>
>> Sounds like you have reinvented identd, which has pretty much  =

>> vanished
>> from the Internet because it was found to not really add any useful
>> authentication.
>
> draft-kuthan-sip-derive-00 proposal is 100% SIP based instead of  =

> depending on
> other protocols. IMHO it has *nothing* to do with Identd mechanism.
>

But it is very much LIKE the ident mechanism, in that, in response to  =

a connection attempt, the connected party does a reverse-to-host  =

connection to ask "Is this from you, and which user is it from"?

You've just implemented a complicated version of a return-routability  =

check.

--
Dean


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


From sip-bounces@ietf.org  Mon Oct 27 00:08:59 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B54B33A692C;
	Mon, 27 Oct 2008 00:08:59 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B55F53A68A2
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 00:08:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.196
X-Spam-Level: 
X-Spam-Status: No, score=-0.196 tagged_above=-999 required=5
	tests=[AWL=-0.887, BAYES_00=-2.599, FRT_OPPORTUN1=1.893,
	FRT_OPPORTUN2=1.397]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CuRNdbfiQaQO for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 00:08:57 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id CD8D13A6925
	for <sip@ietf.org>; Mon, 27 Oct 2008 00:08:57 -0700 (PDT)
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9R77vFn031499
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Mon, 27 Oct 2008 02:08:55 -0500
Message-Id: <D6D4BB88-023A-4D3F-A646-61226B8C1F5E@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF083CCFB9@esealmw113.eemea.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 27 Oct 2008 02:08:54 -0500
References: <20081016203334.229803A68EC@core3.amsl.com><1A80883E-AB46-4776-92C0-798C7E662D21@softarmor.com>
	<41397D90-A4BD-4AC0-8598-3B10783612C4@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFB9@esealmw113.eemea.ericsson.se>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Does SIP want to participate in the Interim
	MeetingOpportunity in January 2009
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


My bad; Jan 20-22. Three days, Tues-Thurs.

--
Dean

On Oct 26, 2008, at 5:53 AM, Christer Holmberg wrote:

> I guess there is something wrong with the dates, or is there going  
> to be a ONE-day large-scale meeting?
>
> ________________________________
>
> From: sip-bounces@ietf.org on behalf of Dean Willis
> Sent: Fri 24/10/2008 23:40
> To: SIP IETF
> Subject: [Sip] Does SIP want to participate in the Interim  
> MeetingOpportunity in January 2009
>
>
>
> IETF is hosting a large-scale interim meeting in Malta, Jan 22-22  
> 2009.
>
> Do we want to have an interim meeting? The AD's assumption is "yes",
> so please reply if you think otherwise.
>
> --
> Dean
>
> Begin forwarded message:
>
>> From: IETF Chair <chair@ietf.org>
>> Date: October 16, 2008 3:33:34 PM CDT
>> To: Working Group Chairs <wgchairs@ietf.org>
>> Cc: chair@ietf.org
>> Subject: WG Interim Meeting Opportunity in January 2009
>>
>> In our continuing effort to ensure that IETF WGs are getting enough
>> meeting time to progress their work, we are conducting another
>> experiment.
>> Many WGs have found interim meetings an effective way to tackle  
>> thorny
>> technical issues, resolve contentious technical issues, accelerate
>> standards development, and provide traction for new work.  As
>> always, an
>> interim WG meeting is not a substitute for a regular session at the
>> traditional IETF meeting.  Since some WG Chairs and ADs have found  
>> the
>> amount of time necessary to put together an interim meeting can be
>> excessive, we are trying to reduce the effort necessary to conduct an
>> interim meeting to determine whether reducing this burden will
>> expedite
>> IETF standards development.  To this end, the Secretariat will
>> facilitate
>> a large interim meeting from 20-22 January 2009 in Malta.  If you are
>> interested in participating in this experiment, please contact your
>> Area
>> Director for approval.  All face-to-face interim meetings require AD
>> approval, and this is no exception.  The IETF Secretariat is putting
>> together a program with three full days and four tracks on each
>> day.  Each
>> WG interim meeting is expected to consume at least one full day on
>> one of
>> the tracks.
>>
>> ADs will schedule the sessions.  A URL for the schedule will be
>> announced
>> shortly.  Once it is available, if you detect a scheduling conflict,
>> please raise the concern with your AD for resolution.  Session time  
>> is
>> limited, and sessions will be allocated first come, first served.
>>
>> The Secretariat will provide registration, food and beverage, audio
>> visual facilities, and on site registration support.  VeriLAN will
>> provide
>> network and audio streaming support.  It is expected that the
>> meeting fee
>> will be $375 for early registration and $475 for late registration.
>>
>> The Internet Society is looking for meeting sponsors for this event.
>> Anyone interested please contact Drew Dvorshak <dvorshak@isoc.org>.
>>
>> Russ
>>
>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>
>
>

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


From sip-bounces@ietf.org  Mon Oct 27 00:09:47 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8ADCD3A6A2D;
	Mon, 27 Oct 2008 00:09:47 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1D89A3A6925
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 00:09:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.664
X-Spam-Level: 
X-Spam-Status: No, score=-1.664 tagged_above=-999 required=5 tests=[AWL=0.935, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id J8mQAhwgX033 for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 00:09:45 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 5BA6828C131
	for <sip@ietf.org>; Mon, 27 Oct 2008 00:09:45 -0700 (PDT)
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9R77vFo031499
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Mon, 27 Oct 2008 02:09:41 -0500
Message-Id: <61D19F8F-B1DE-4104-98B2-94FB7FC46FD3@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF083CCFB8@esealmw113.eemea.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 27 Oct 2008 02:09:41 -0500
References: <48FDEAD8.8010803@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>	<48FF2C45.7010204@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>	<4901BA73.1010700@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>	<4901C2B1.1050209@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>	<4901D025.6060302@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>	<490239C8.3020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>	<4902467E.3010603@cisco.com>
	<F05558E6-AF75-41BC-9691-8A7E14748C8B@softarmor.com>
	<49025A2E.4050801@cisco.com> <CA9998CD4!
	A020D418654FCDEF4E707DF083CCFB8@esealmw113.eemea.ericsson.se>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type
	vs	Info-Package [was RE: draft-ietf-sip-info-events-00:
	multiple	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 26, 2008, at 5:52 AM, Christer Holmberg wrote:
>
> example: Content-Type: application/foo-data;info-package=foo

You think the MIME people are going to approve this?

--
Dean

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


From sip-bounces@ietf.org  Mon Oct 27 00:11:44 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 640993A6973;
	Mon, 27 Oct 2008 00:11:44 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C099C3A693F
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 00:11:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.89
X-Spam-Level: 
X-Spam-Status: No, score=-0.89 tagged_above=-999 required=5 tests=[AWL=-0.150, 
	BAYES_20=-0.74]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id DE6Z-hPzEqyW for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 00:11:42 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 0F8B13A6925
	for <sip@ietf.org>; Mon, 27 Oct 2008 00:11:42 -0700 (PDT)
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9R7Ba9I031540
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Mon, 27 Oct 2008 02:11:38 -0500
Message-Id: <02B09DA6-A57A-4817-B0B6-D8A65F4F2744@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Henry Sinnreich <hsinnrei@adobe.com>
In-Reply-To: <C529EE27.94A0%hsinnrei@adobe.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 27 Oct 2008 02:11:31 -0500
References: <C529EE27.94A0%hsinnrei@adobe.com>
X-Mailer: Apple Mail (2.929.2)
Cc: Dorgham.Sisalem@tekelec.com, SIP IETF <sip@ietf.org>,
	Raphael.Coeffic@tekelec.com, Henry Sinnreich <henry@henrysinnreich.net>,
	Jiri.Kuthan@tekelec.com, Victor.Pascual@tekelec.com
Subject: Re: [Sip] draft-kuthan-sip-derive
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 26, 2008, at 9:51 AM, Henry Sinnreich wrote:

> Folks,
>
> To prove me wrong, someone just sent this forged email
>
>> email verification successfully deployed throughout the internet?
>> really?
>>
>> Yes, this is a demonstration of forged From addresses. Very sloppily
>> done, so you can see who sent it.
>
> It was not me for sure.
> Then how come some many web sites include the email in their  
> verification?
>

Because they like to allow Sarah Palin's email to get hacked?

--
Dean

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


From sip-bounces@ietf.org  Mon Oct 27 00:13:31 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 14AC53A693F;
	Mon, 27 Oct 2008 00:13:31 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CC11B3A6925
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 00:13:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.798
X-Spam-Level: 
X-Spam-Status: No, score=-1.798 tagged_above=-999 required=5 tests=[AWL=0.801, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RovsNGDoXFmV for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 00:13:28 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id C890B3A693F
	for <sip@ietf.org>; Mon, 27 Oct 2008 00:13:28 -0700 (PDT)
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9R7DMKO031566
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Mon, 27 Oct 2008 02:13:24 -0500
Message-Id: <D76D4941-BD3A-4DB1-A0B2-641B98FFA024@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Juha Heinanen <jh@tutpro.com>
In-Reply-To: <18692.52595.364526.196499@harjus.tutpro.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 27 Oct 2008 02:13:17 -0500
References: <C528BB73.9465%hsinnrei@adobe.com>
	<01b301c93795$ed79ff60$04ffa8c0@nsnintra.net>
	<18692.52595.364526.196499@harjus.tutpro.com>
X-Mailer: Apple Mail (2.929.2)
Cc: Dorgham.Sisalem@tekelec.com, 'SIP IETF' <sip@ietf.org>,
	Raphael.Coeffic@tekelec.com,
	'Henry Sinnreich' <hsinnrei@adobe.com>, Jiri.Kuthan@tekelec.com,
	Victor.Pascual@tekelec.com
Subject: Re: [Sip] draft-kuthan-sip-derive
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 26, 2008, at 3:05 PM, Juha Heinanen wrote:

> Hannes Tschofenig writes:
>
>> Given that only 2 out of 50 implementations had support for SIP  
>> Identity at
>> SIPit#23 I wonder how urgent the need for anything beyond P- 
>> Asserted-ID
>> actually is:
>> https://www.sipit.net/SIPit23_Summary
>
> pai does not help if you receive a request from anywhere on the
> internet.
>

But in the "real world", nobody uses this stuff on the Internet,  
right? It's always proxy-tied, with no interdomain calls.

So why are we bothering? is it that we THINK interdomain will really  
happen with peering agreegements?

--
Dean


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


From sip-bounces@ietf.org  Mon Oct 27 00:14:21 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BBCF13A693F;
	Mon, 27 Oct 2008 00:14:21 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1DFBD3A693F
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 00:14:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[AWL=0.701, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5KNG4949Phms for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 00:14:19 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 656603A6925
	for <sip@ietf.org>; Mon, 27 Oct 2008 00:14:19 -0700 (PDT)
Received: from [192.168.1.4] (65-65-155-30.dsl.bigbend.net [65.65.155.30] (may
	be forged)) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9R7DMKP031566
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Mon, 27 Oct 2008 02:14:10 -0500
Message-Id: <4F293C6A-D011-4EA4-AA2A-F21BE7861028@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
In-Reply-To: <5D1A7985295922448D5550C94DE29180024260D5@DEEXC1U01.de.lucent.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 27 Oct 2008 02:14:09 -0500
References: <48FDEAD8.8010803@cisco.com><CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se><48FF2C45.7010204@cisco.com><CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se><093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se><5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se><07AD9FC7-C9D2-4229-B364-BD051728BF37@softarmor.com><CA9998CD4A020D418654FCDEF4E707DF083CCFB6@esealmw113.eemea.ericsson.se>
	<5736B897-8C58-4923-AB2B-8AE1BA9B2747@softarmor.com>
	<5D1A7985295922448D5550C94DE29180024260D5@DEEXC1U01.de.lucent.com>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type
	vsInfo-Package [was RE: draft-ietf-sip-info-events-00:
	multiplepackages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 26, 2008, at 7:44 PM, DRAGE, Keith (Keith) wrote:

> Should we even allow bodies that do not relate to info packages in  
> INFO
> messages (legacy issues excepted).

Probably have to, given things like AIB and E2M . . .

Not that those are actually deployed, of course.

--
Dean

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


From sip-bounces@ietf.org  Mon Oct 27 00:16:50 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 873A03A6927;
	Mon, 27 Oct 2008 00:16:50 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9252B3A6A46
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 00:16:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id VhUenvgUvWWM for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 00:16:48 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net
	[217.115.75.234])
	by core3.amsl.com (Postfix) with ESMTP id 130B93A6927
	for <sip@ietf.org>; Mon, 27 Oct 2008 00:15:53 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55])
	by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id
	m9R7FlkC018175
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 27 Oct 2008 08:15:47 +0100
Received: from demuexc022.nsn-intra.net (webmail.nsn-intra.net [10.150.128.35])
	by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP
	id m9R7FjNB031439; Mon, 27 Oct 2008 08:15:47 +0100
Received: from demuexc024.nsn-intra.net ([10.159.32.11]) by
	demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 27 Oct 2008 08:15:01 +0100
Received: from FIESEXC007.nsn-intra.net ([10.159.0.15]) by
	demuexc024.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 27 Oct 2008 08:15:01 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Mon, 27 Oct 2008 09:14:57 +0200
Message-ID: <C41BFCED3C088E40A8510B57B165C162A5CFBF@FIESEXC007.nsn-intra.net>
In-Reply-To: <D76D4941-BD3A-4DB1-A0B2-641B98FFA024@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-kuthan-sip-derive
Thread-Index: Ack4A4vjSTnfFrKTSa+MdjEZ0ogrMwAAByWw
References: <C528BB73.9465%hsinnrei@adobe.com><01b301c93795$ed79ff60$04ffa8c0@nsnintra.net><18692.52595.364526.196499@harjus.tutpro.com>
	<D76D4941-BD3A-4DB1-A0B2-641B98FFA024@softarmor.com>
From: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
To: "ext Dean Willis" <dean.willis@softarmor.com>,
	"Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 27 Oct 2008 07:15:01.0195 (UTC)
	FILETIME=[B9EA09B0:01C93803]
X-purgate: clean
X-purgate: This mail is considered clean
X-purgate-type: clean
X-purgate-Ad: Checked for Spam by eleven - eXpurgate www.eXpurgate.net
X-purgate-ID: 151667::081027081547-63991BB0-0150E7E3/0-0/0-15
X-purgate-size: 1474/0
Cc: Dorgham.Sisalem@tekelec.com, SIP IETF <sip@ietf.org>,
	Raphael.Coeffic@tekelec.com,
	Henry Sinnreich <hsinnrei@adobe.com>, Jiri.Kuthan@tekelec.com,
	Victor.Pascual@tekelec.com
Subject: Re: [Sip] draft-kuthan-sip-derive
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Thanks Dean. This was roughly where I wanted to get to in subsequent
questions... 
 

>-----Original Message-----
>From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
>Behalf Of ext Dean Willis
>Sent: 27 October, 2008 09:13
>To: Juha Heinanen
>Cc: Dorgham.Sisalem@tekelec.com; 'SIP IETF'; 
>Raphael.Coeffic@tekelec.com; 'Henry Sinnreich'; 
>Jiri.Kuthan@tekelec.com; Victor.Pascual@tekelec.com
>Subject: Re: [Sip] draft-kuthan-sip-derive
>
>
>On Oct 26, 2008, at 3:05 PM, Juha Heinanen wrote:
>
>> Hannes Tschofenig writes:
>>
>>> Given that only 2 out of 50 implementations had support for SIP 
>>> Identity at
>>> SIPit#23 I wonder how urgent the need for anything beyond P- 
>>> Asserted-ID actually is:
>>> https://www.sipit.net/SIPit23_Summary
>>
>> pai does not help if you receive a request from anywhere on the 
>> internet.
>>
>
>But in the "real world", nobody uses this stuff on the 
>Internet, right? It's always proxy-tied, with no interdomain calls.
>
>So why are we bothering? is it that we THINK interdomain will 
>really happen with peering agreegements?
>
>--
>Dean
>
>
>_______________________________________________
>Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>This list is for NEW development of the core SIP Protocol Use 
>sip-implementors@cs.columbia.edu for questions on current sip 
>Use sipping@ietf.org for new developments on the application of sip
>
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct 27 00:23:09 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 497B43A6927;
	Mon, 27 Oct 2008 00:23:09 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AF1F03A6878
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 00:23:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.649
X-Spam-Level: 
X-Spam-Status: No, score=-5.649 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_37=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Y9H4BtOeI0od for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 00:23:07 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 833BC3A67E5
	for <sip@ietf.org>; Mon, 27 Oct 2008 00:23:07 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	A758521077; Mon, 27 Oct 2008 08:23:05 +0100 (CET)
X-AuditID: c1b4fb3e-aaf7ebb00000537b-30-49056c5900b9
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	81C0220FCA; Mon, 27 Oct 2008 08:23:05 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 08:23:05 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 27 Oct 2008 08:23:04 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF089CA230@esealmw113.eemea.ericsson.se>
In-Reply-To: <4904BE56.7050704@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: Content-Type
	vs	Info-Package [was RE: draft-ietf-sip-info-events-00:
	multiple	packages per INFO]
Thread-Index: Ack3nSRYr74/RmxPQy6LavKZcWwkuwAZYfKg
References: <48FDEAD8.8010803@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>	<48FF2C45.7010204@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>	<4901BA73.1010700@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>	<4901C2B1.1050209@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>	<4901D025.6060302@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>	<490239C8.3020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>	<4902467E.3010603@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFBA@esealmw113.eemea.ericsson.se>
	<490456A8.6090109@zon net.nl> <4904BE56.7050704@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>,
	"Jeroen van Bemmel" <jbemmel@zonnet.nl>
X-OriginalArrivalTime: 27 Oct 2008 07:23:05.0198 (UTC)
	FILETIME=[DA6708E0:01C93804]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type
	vs	Info-Package [was RE: draft-ietf-sip-info-events-00:
	multiple	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>>Like I wrote before: adding the INFO package as a parameter to 
>>>Content-Type solves all this. I don't think C-D is the right header, 
>>>because the "disposition" would depend on the semantics of 
>>>the event package. We simply need an additional qualifier to
disambiguate the 
>>>interpretation of the body
>> 
>>If you mentioned this before I missed it.
> 
>>Its an interesting idea. But I don't think it is technicallyh 
>>feasible.
>>AFAIK the parameters to a C-T must be defined as part of the 
>>definition of the C-T. That wold mean that only 
>>yet-to-be-defined C-Ts could be used for info packages.

That would be a reason to use a COMMON C-T type, and then a parameter
which identifies the info package.



Let's keep in mind that info packages have been NEGOTIATED. Ie I will
not send you a package unless you have indicated support for it.

Therefor, if I send you a picture, I don't think it matters if C-T is
image/jpeg, or application/info;info-package=jpeg-package.

...because, YOU know the semantics of the package. Also, since an info
package is not supposed to change the core SIP state, the stack itself
doesn't need to know the semantics of the body, does it?


The problem is if I send you ONLY image/jpeg - without any negotiation,
and semantics we both have agreed on. I don't know what you will do it.
I think THAT is the problem that Eric initially raised.

Regards,

Christer






> > Regards,
> > Jeroen
> > 
> > Christer Holmberg wrote:
> >> Hi,
> >>
> >>  
> >>>> So, just to make sure I understand: you are talking about a case 
> >>>> where the INFO does contain a multipart message body, 
> but only one 
> >>>> of the mimes contains an actual info-package (the other mime(s) 
> >>>> contains something else)?
> >>>>       
> >>> pretty much. And to distinguish those, you need more than C-T.
> >>> But I think as we have been discussing, if we only allow one info 
> >>> package per INFO, then the Info-Package header belongs in the 
> >>> message, not in the body part.
> >>>     
> >>  
> >> I don't think that defining Info-Package as a mime header 
> would even 
> >> be within the scope of the SIP WG, would it?
> >>  
> >> My assumption has been that the I-P header is in the SIP message 
> >> part, and that causes the problem: in the case of 
> multipart, how to 
> >> associate the correct mime with the I-P header? I still 
> think making 
> >> assumptions on C-D is very dangerous, considering the very little 
> >> experience we have of the C-D header in the first place.
> >>
> >>  
> >>> I'll revise your example a bit:
> >>>
> >>> INFO sip:foo@bar.com
> >>> To:...
> >>> From:...
> >>> Some-Header: CID:abcdefg
> >>> Info-Package: foo
> >>> Content-Type:multipart/mixed
> >>> Content-Length:...
> >>>
> >>> --boundary
> >>> Content-Type: application/foo-data
> >>> Content-Disposition: package;handling=required
> >>>
> >>> foo data
> >>> --boundary
> >>> Content-ID: abcdefg
> >>> Content-Type: application/some-header-data
> >>> Content-Disposition: by-reference;handling=optional
> >>>
> >>> some other (non-info package) data
> >>> --boundary--
> >>>
> >>> In the above I have used C-D of "package" to identify the 
> part that 
> >>> contains the info package. That is yet to be determined, 
> but I think 
> >>> it needs to be well defined, even if it is "render".
> >>>     
> >>
> >> Again, I don't think using C-D for the "association" is a 
> good idea.
> >>  
> >>
> >>  
> >>> A more straightforward case would be:
> >>>
> >>> INFO sip:foo@bar.com
> >>> To:...
> >>> From:...
> >>> Info-Package: foo
> >>> Content-Type: application/foo-data
> >>> Content-Disposition: package;handling=required Content-Length:10
> >>>
> >>> foo data
> >>>     
> >>
> >> ...assuming that we don't allow multipart in INFOs, yes.
> >>  
> >> Regards,
> >>  
> >> Christer
> >>  
> >> _______________________________________________
> >> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> >> This list is for NEW development of the core SIP Protocol Use 
> >> sip-implementors@cs.columbia.edu for questions on current sip Use 
> >> sipping@ietf.org for new developments on the application of sip
> >>
> >>   
> > 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct 27 00:24:51 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 466563A6927;
	Mon, 27 Oct 2008 00:24:51 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1D5B13A67E5
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 00:24:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.949
X-Spam-Level: 
X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[AWL=0.300, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jchxCH18Jx1t for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 00:24:49 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 3642C3A6878
	for <sip@ietf.org>; Mon, 27 Oct 2008 00:24:49 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	8926C2053A; Mon, 27 Oct 2008 08:24:47 +0100 (CET)
X-AuditID: c1b4fb3c-ae8cfbb0000015b5-49-49056cbfacba
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	6E1CF2046D; Mon, 27 Oct 2008 08:24:47 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 08:24:47 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 27 Oct 2008 08:24:46 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF089CA245@esealmw113.eemea.ericsson.se>
In-Reply-To: <61D19F8F-B1DE-4104-98B2-94FB7FC46FD3@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: Content-Type
	vs	Info-Package [was RE: draft-ietf-sip-info-events-00:
	multiple	packages per INFO]
Thread-Index: Ack4Av1oggOX5dkITcCBJZIzQtqbowAAgPCw
References: <48FDEAD8.8010803@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>	<48FF2C45.7010204@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>	<4901BA73.1010700@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>	<4901C2B1.1050209@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>	<4901D025.6060302@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>	<490239C8.3020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>	<4902467E.3010603@cisco.com>
	<F05558E6-AF75-41BC-9691-8A7E14748C8B@softarmor.com>
	<49025A2E.4050801@cisco.com> <CA9998CD4! A020D41 8654FCDEF4E7
	07DF083CCFB8@esealmw113.eemea.ericsson.se>
	<61D19F8F-B1DE-4104-98B2-94FB7FC46FD3@softarmor.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Dean Willis" <dean.willis@softarmor.com>
X-OriginalArrivalTime: 27 Oct 2008 07:24:47.0116 (UTC)
	FILETIME=[17267CC0:01C93805]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type
	vs	Info-Package [was RE: draft-ietf-sip-info-events-00:
	multiple	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 

>>>example: Content-Type: application/foo-data;info-package=foo
>>You think the MIME people are going to approve this?

Dunno. Maybe they would approve Content-Type:
application/info;info-package=foo

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


From sip-bounces@ietf.org  Mon Oct 27 00:27:58 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1810B3A68F2;
	Mon, 27 Oct 2008 00:27:58 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 089D63A68A2
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 00:27:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_91=0.6]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YJWh+Ul0NCpS for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 00:27:56 -0700 (PDT)
Received: from taimen.tutpro.com (harjus.tutpro.com [192.98.100.3])
	by core3.amsl.com (Postfix) with ESMTP id 42A2E3A6878
	for <sip@ietf.org>; Mon, 27 Oct 2008 00:27:56 -0700 (PDT)
Received: by taimen.tutpro.com (Postfix, from userid 1000)
	id 1ADEB33A679; Mon, 27 Oct 2008 09:27:54 +0200 (EET)
MIME-Version: 1.0
Message-ID: <18693.28026.64153.636982@harjus.tutpro.com>
Date: Mon, 27 Oct 2008 09:27:54 +0200
To: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <75F6E6CD-446C-4F59-A3F9-2258866D782F@softarmor.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<200810260100.38716.ibc@aliax.net>
	<18692.12450.342904.645834@harjus.tutpro.com>
	<75F6E6CD-446C-4F59-A3F9-2258866D782F@softarmor.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR
	Identity	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Dean Willis writes:

 > Not only that, but it needs to deal with forking, or it needs to  
 > require all the calls originating @bar go through the @bar proxy/sbc.

when sip:foo@bar makes the call, it does not need to go through bar's
proxy.  all that is needed is that sip:foo@bar is registered with its
registrar.l

forking is needed if sip:foo@bar has currently registered from multiple
UAs, but forking is normal rfc3261 stuff.

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


From sip-bounces@ietf.org  Mon Oct 27 00:29:40 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DD22D3A6912;
	Mon, 27 Oct 2008 00:29:40 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D54D73A68A2
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 00:29:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id e-hvOoui8Hip for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 00:29:38 -0700 (PDT)
Received: from taimen.tutpro.com (harjus.tutpro.com [192.98.100.3])
	by core3.amsl.com (Postfix) with ESMTP id 09A2D3A6927
	for <sip@ietf.org>; Mon, 27 Oct 2008 00:29:38 -0700 (PDT)
Received: by taimen.tutpro.com (Postfix, from userid 1000)
	id A08E833A679; Mon, 27 Oct 2008 09:29:37 +0200 (EET)
MIME-Version: 1.0
Message-ID: <18693.28129.618794.915466@harjus.tutpro.com>
Date: Mon, 27 Oct 2008 09:29:37 +0200
To: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>
	<200810261145.19745.ibc@aliax.net>
	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR
	Identity	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Dean Willis writes:

 > But it is very much LIKE the ident mechanism, in that, in response to  
 > a connection attempt, the connected party does a reverse-to-host  
 > connection to ask "Is this from you, and which user is it from"?
 > 
 > You've just implemented a complicated version of a return-routability  
 > check.

i don't know about the dialog event solution, but what i had proposed is
VERY simple:  one request and a response to it.

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


From sip-bounces@ietf.org  Mon Oct 27 01:08:53 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 62EA73A68A2;
	Mon, 27 Oct 2008 01:08:53 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8E2CA3A6855
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 01:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id n3ii8r+nsSmq for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 01:08:51 -0700 (PDT)
Received: from taimen.tutpro.com (harjus.tutpro.com [192.98.100.3])
	by core3.amsl.com (Postfix) with ESMTP id BD40C3A68F1
	for <sip@ietf.org>; Mon, 27 Oct 2008 01:08:50 -0700 (PDT)
Received: by taimen.tutpro.com (Postfix, from userid 1000)
	id E9D1D33A679; Mon, 27 Oct 2008 10:08:49 +0200 (EET)
MIME-Version: 1.0
Message-ID: <18693.30481.912555.303781@harjus.tutpro.com>
Date: Mon, 27 Oct 2008 10:08:49 +0200
To: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <D76D4941-BD3A-4DB1-A0B2-641B98FFA024@softarmor.com>
References: <C528BB73.9465%hsinnrei@adobe.com>
	<01b301c93795$ed79ff60$04ffa8c0@nsnintra.net>
	<18692.52595.364526.196499@harjus.tutpro.com>
	<D76D4941-BD3A-4DB1-A0B2-641B98FFA024@softarmor.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: Dorgham.Sisalem@tekelec.com, 'SIP IETF' <sip@ietf.org>,
	Raphael.Coeffic@tekelec.com,
	'Henry Sinnreich' <hsinnrei@adobe.com>, Jiri.Kuthan@tekelec.com,
	Victor.Pascual@tekelec.com
Subject: Re: [Sip] draft-kuthan-sip-derive
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Dean Willis writes:

 > But in the "real world", nobody uses this stuff on the Internet,  
 > right? It's always proxy-tied, with no interdomain calls.

you can call me at sip:jh@tutpro.com from anywhere on the internet.  if
you think that sip is not for the internet, then ietf is not the right
forum for you and you can setup your own club.

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


From sip-bounces@ietf.org  Mon Oct 27 01:13:51 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 85F0428C160;
	Mon, 27 Oct 2008 01:13:51 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D0EC93A68A2
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 01:13:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id a97s-RZaIkdI for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 01:13:48 -0700 (PDT)
Received: from mail.iptel.org (smtp.iptel.org [213.192.59.67])
	by core3.amsl.com (Postfix) with ESMTP id 9475F3A6855
	for <sip@ietf.org>; Mon, 27 Oct 2008 01:13:48 -0700 (PDT)
Received: by mail.iptel.org (Postfix, from userid 103)
	id 6B6231812D25; Mon, 27 Oct 2008 09:13:47 +0100 (CET)
Received: from webmail.iptel.org (unknown [192.168.0.72])
	by mail.iptel.org (Postfix) with ESMTP id CDAA71812961
	for <sip@ietf.org>; Mon, 27 Oct 2008 09:13:46 +0100 (CET)
Received: from 88.103.98.182 (SquirrelMail authenticated user jiri)
	by webmail.iptel.org with HTTP; Mon, 27 Oct 2008 09:13:46 +0100 (CET)
Message-ID: <59319.88.103.98.182.1225095226.squirrel@webmail.iptel.org>
In-Reply-To: <C41BFCED3C088E40A8510B57B165C162A5CFBF@FIESEXC007.nsn-intra.net>
References: <C528BB73.9465%hsinnrei@adobe.com><01b301c93795$ed79ff60$04ffa8c0@nsnintra.net><18692.52595.364526.196499@harjus.tutpro.com>
	<D76D4941-BD3A-4DB1-A0B2-641B98FFA024@softarmor.com>
	<C41BFCED3C088E40A8510B57B165C162A5CFBF@FIESEXC007.nsn-intra.net>
Date: Mon, 27 Oct 2008 09:13:46 +0100 (CET)
From: jiri@iptel.org
To: sip@ietf.org
User-Agent: SquirrelMail/1.4.9a
MIME-Version: 1.0
X-Priority: 3 (Normal)
Importance: Normal
Subject: Re: [Sip] draft-kuthan-sip-derive
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Generally, multi-domain life seems to exist indeed in a rather
limited way -- mostly regionally using ENUM-like technologies to find
target domain. I'm not 100% sure yet why is that, supposedly
the economy of interconnection via PSTN is favorable.

wrt to security it seems that attackers are apparently not worried
about what we think about multi-domain stuff or not. see the reports
on the recent incidents in Germany I posted before. The interesting
part I find here is we can set up a barrier which does not take
inventing new protocols.


-jiri

> Thanks Dean. This was roughly where I wanted to get to in subsequent
> questions...
>
>
>>-----Original Message-----
>>From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
>>Behalf Of ext Dean Willis
>>Sent: 27 October, 2008 09:13
>>To: Juha Heinanen
>>Cc: Dorgham.Sisalem@tekelec.com; 'SIP IETF';
>>Raphael.Coeffic@tekelec.com; 'Henry Sinnreich';
>>Jiri.Kuthan@tekelec.com; Victor.Pascual@tekelec.com
>>Subject: Re: [Sip] draft-kuthan-sip-derive
>>
>>
>>On Oct 26, 2008, at 3:05 PM, Juha Heinanen wrote:
>>
>>> Hannes Tschofenig writes:
>>>
>>>> Given that only 2 out of 50 implementations had support for SIP
>>>> Identity at
>>>> SIPit#23 I wonder how urgent the need for anything beyond P-
>>>> Asserted-ID actually is:
>>>> https://www.sipit.net/SIPit23_Summary
>>>
>>> pai does not help if you receive a request from anywhere on the
>>> internet.
>>>
>>
>>But in the "real world", nobody uses this stuff on the
>>Internet, right? It's always proxy-tied, with no interdomain calls.
>>
>>So why are we bothering? is it that we THINK interdomain will
>>really happen with peering agreegements?
>>
>>--
>>Dean
>>
>>
>>_______________________________________________
>>Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>This list is for NEW development of the core SIP Protocol Use
>>sip-implementors@cs.columbia.edu for questions on current sip
>>Use sipping@ietf.org for new developments on the application of sip
>>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>


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


From sip-bounces@ietf.org  Mon Oct 27 01:56:45 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5F00C3A69D6;
	Mon, 27 Oct 2008 01:56:45 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 146C73A6855
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 01:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.354
X-Spam-Level: 
X-Spam-Status: No, score=-5.354 tagged_above=-999 required=5
	tests=[AWL=-0.595, BAYES_05=-1.11, HELO_EQ_SE=0.35,
	HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id DkkmamaaXgrE for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 01:56:43 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id D8AD33A67D0
	for <sip@ietf.org>; Mon, 27 Oct 2008 01:56:42 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	5FAC120888 for <sip@ietf.org>; Mon, 27 Oct 2008 09:56:41 +0100 (CET)
X-AuditID: c1b4fb3c-af8d1bb0000015b5-dd-490582491d9a
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	4EC3220864 for <sip@ietf.org>; Mon, 27 Oct 2008 09:56:41 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 09:56:40 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 27 Oct 2008 09:56:40 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF089CA7C8@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New version of sip-keep draft
Thread-Index: Ack4Ee1aALiMEVXJQziL7HJPBvghDg==
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "SIP IETF" <sip@ietf.org>
X-OriginalArrivalTime: 27 Oct 2008 08:56:40.0878 (UTC)
	FILETIME=[ED9BCCE0:01C93811]
X-Brightmail-Tracker: AAAAAA==
Subject: [Sip] New version of sip-keep draft
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1715077493=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1715077493==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C93811.ED83AF60"

This is a multi-part message in MIME format.

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


Hi,

I've submitted a new version of the sip-keep draft.

Based on the comments received, I have made the text more general to
cover also proxy-to-proxy use-cases.

I've also added the outbound dialog flow use-case, where an explicit
indication for keep-alive is needed (see Outbound draft).

You can also find the draft at:

http://users.piuha.net/cholmber/drafts/draft-holmberg-sip-keep-02.txt

Regards,

Christer



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

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

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

<P><FONT SIZE=3D2 FACE=3D"Arial">I've submitted a new version of the =
sip-keep draft.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Based on the comments received, I have =
made the text more general to cover also proxy-to-proxy =
use-cases.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I've also added the outbound dialog =
flow use-case, where an explicit indication for keep-alive is needed =
(see Outbound draft).</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">You can also find the draft at:</FONT>
</P>

<P><A =
HREF=3D"http://users.piuha.net/cholmber/drafts/draft-holmberg-sip-keep-02=
.txt"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">http://users.piuha.net/cholmber/drafts/draft-holmberg-sip-=
keep-02.txt</FONT></U></A>
</P>

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

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

</BODY>
</HTML>
------_=_NextPart_001_01C93811.ED83AF60--

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

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


From sip-bounces@ietf.org  Mon Oct 27 03:39:00 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F40133A6855;
	Mon, 27 Oct 2008 03:38:59 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CB9EB3A6855
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 03:38:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id PZoVPH-3mkGd for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 03:38:57 -0700 (PDT)
Received: from taimen.tutpro.com (harjus.tutpro.com [192.98.100.3])
	by core3.amsl.com (Postfix) with ESMTP id B88AF3A67D9
	for <sip@ietf.org>; Mon, 27 Oct 2008 03:38:57 -0700 (PDT)
Received: by taimen.tutpro.com (Postfix, from userid 1000)
	id 2F70833A679; Mon, 27 Oct 2008 12:38:57 +0200 (EET)
MIME-Version: 1.0
Message-ID: <18693.39489.149630.617350@harjus.tutpro.com>
Date: Mon, 27 Oct 2008 12:38:57 +0200
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF089CA7C8@esealmw113.eemea.ericsson.se>
References: <CA9998CD4A020D418654FCDEF4E707DF089CA7C8@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: SIP IETF <sip@ietf.org>
Subject: [Sip]  New version of sip-keep draft
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

i don't understand why uac needs to act as a stun client.  why don't you
simply say that the uac must be able to send double crlf message to the
edge proxy?  stun draft is 51 pages long and requiring keepalive
implementer to read it is clearly an overkill.

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


From sip-bounces@ietf.org  Mon Oct 27 05:14:21 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A09B23A6A38;
	Mon, 27 Oct 2008 05:14:21 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 10EFB3A69F3
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 05:14:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.555
X-Spam-Level: 
X-Spam-Status: No, score=-0.555 tagged_above=-999 required=5 tests=[AWL=0.555, 
	BAYES_05=-1.11]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id bVSZM-vJbyrX for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 05:14:19 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39])
	by core3.amsl.com (Postfix) with ESMTP id 4AD173A6A13
	for <sip@ietf.org>; Mon, 27 Oct 2008 05:14:19 -0700 (PDT)
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2])
	by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id m9RCDbEM017915
	for <sip@ietf.org>; Mon, 27 Oct 2008 07:14:07 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by
	ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 07:14:06 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.28]) by
	DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 13:14:04 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Mon, 27 Oct 2008 13:14:10 +0100
Message-ID: <5D1A7985295922448D5550C94DE2918002426290@DEEXC1U01.de.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Draft-ietf-sip-info-events-00: Other messages for Send-Info and
	Recv-Info
Thread-Index: Ack4LYR0jzUi9yAlSwq3f5sjVq46fw==
From: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: "SIP IETF" <sip@ietf.org>
X-OriginalArrivalTime: 27 Oct 2008 12:14:05.0038 (UTC)
	FILETIME=[814730E0:01C9382D]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Subject: [Sip] Draft-ietf-sip-info-events-00: Other messages for Send-Info
	and Recv-Info
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I notice that the current document does define the validity of these
elements for REG, but leaves the section describing the use empty. If
the purpose of inclusion was to somehow register this things in the
registrar against the contact, surely this should be left to feature
tags, as I think has already been suggested on the list. Or was there
some other purpose? If not, I would suggest removal.

The other method that crossed my mind was OPTIONS. Should OPTIONS
provide a mechanism of identifying what the entity at the Request-URI
supports, in the same manner as it does for SDP and option tags, or
should be ignore this possibility on the grounds of simplicity.
Thoughts?

Regards

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


From sip-bounces@ietf.org  Mon Oct 27 05:21:49 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 731533A6A38;
	Mon, 27 Oct 2008 05:21:49 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E50D23A6964
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 05:21:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5
	tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_37=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id c15Km11rTl2X for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 05:21:47 -0700 (PDT)
Received: from ind-iport-1.cisco.com (ind-iport-1.cisco.com [64.104.129.195])
	by core3.amsl.com (Postfix) with ESMTP id 24B793A6A38
	for <sip@ietf.org>; Mon, 27 Oct 2008 05:21:45 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,492,1220227200"; d="scan'208";a="31898054"
Received: from hkg-dkim-2.cisco.com ([10.75.231.163])
	by ind-iport-1.cisco.com with ESMTP; 27 Oct 2008 12:21:40 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94])
	by hkg-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9RCLe20006288; 
	Mon, 27 Oct 2008 20:21:40 +0800
Received: from xbh-hkg-412.apac.cisco.com (xbh-hkg-412.cisco.com
	[64.104.123.69])
	by hkg-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9RCLb2x000148;
	Mon, 27 Oct 2008 12:21:39 GMT
Received: from xbh-rtp-211.amer.cisco.com ([64.102.31.102]) by
	xbh-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 20:21:27 +0800
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 08:21:21 -0400
Received: from [10.86.249.64] ([10.86.249.64]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 08:21:21 -0400
Message-ID: <4905B23F.10609@cisco.com>
Date: Mon, 27 Oct 2008 08:21:19 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <48FDEAD8.8010803@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>	<48FF2C45.7010204@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>	<4901BA73.1010700@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>	<4901C2B1.1050209@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>	<4901D025.6060302@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>	<490239C8.3020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>	<4902467E.3010603@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFBA@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF083CCFBA@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 27 Oct 2008 12:21:21.0557 (UTC)
	FILETIME=[8576B450:01C9382E]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2892; t=1225110100;
	x=1225974100; c=relaxed/simple; s=hkgdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20Content-Type=20vs=09Info-Package=0A=20[was=20RE=3A=20dra
	ft-ietf-sip-info-events-00=3A=20multiple=09packages=20per=20
	INFO] |Sender:=20;
	bh=bLX0kGRAdHdhFWdeluS3oKCNPM9lVyoUlkfGDqnt5wg=;
	b=jZ0q/gMPQ+ykYBwChjqjAJDzaV43zmSqN8WCzF2m0FWcag3L4rafdYP36p
	4v21qXUxaJCODCdRjrpkEzz2aIlnWNGqGVn+MCs47mchR8ViDVG/5ElaDQdj
	DO9vtg0vXILsbB/WMEkgiCyoWBT0uFR48vu9avt7hbX5br5BFZdxg=;
Authentication-Results: hkg-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/hkgdkim2001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type
 vs	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple	packages
 per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Christer Holmberg wrote:
> Hi,
> 
>>> So, just to make sure I understand: you are talking about a case where the INFO does contain a multipart message body, but only one of the mimes contains an actual info-package (the other mime(s) contains something else)?
>> pretty much. And to distinguish those, you need more than C-T.
>> But I think as we have been discussing, if we only allow one info
>> package per INFO, then the Info-Package header belongs in the message,
>> not in the body part.
>  
> I don't think that defining Info-Package as a mime header would even be within the scope of the SIP WG, would it?

Before I say more, I will first point out that discussion is irrelevant 
if we only intend to allow one info package per INFO.

But MIME bodies are extensible with arbitrary headers. I don't recall if 
there is any requirement about standardizing them.

> My assumption has been that the I-P header is in the SIP message part, and that causes the problem: in the case of multipart, how to associate the correct mime with the I-P header?

Lets not get off in the weeds discussing this until and unless we decide 
to support multiple info packages per INFO.

> I still think making assumptions on C-D is very dangerous, considering the very little experience we have of the C-D header in the first place.

Could you please spell out precisely what your concern is?

>> I'll revise your example a bit:
>>
>> INFO sip:foo@bar.com
>> To:...
>> From:...
>> Some-Header: CID:abcdefg
>> Info-Package: foo
>> Content-Type:multipart/mixed
>> Content-Length:...
>>
>> --boundary
>> Content-Type: application/foo-data
>> Content-Disposition: package;handling=required
>>
>> foo data
>> --boundary
>> Content-ID: abcdefg
>> Content-Type: application/some-header-data
>> Content-Disposition: by-reference;handling=optional
>>
>> some other (non-info package) data
>> --boundary--
>>
>> In the above I have used C-D of "package" to identify the part that
>> contains the info package. That is yet to be determined, but I think it
>> needs to be well defined, even if it is "render".
> 
> Again, I don't think using C-D for the "association" is a good idea.
>  
> 
>> A more straightforward case would be:
>>
>> INFO sip:foo@bar.com
>> To:...
>> From:...
>> Info-Package: foo
>> Content-Type: application/foo-data
>> Content-Disposition: package;handling=required
>> Content-Length:10
>>
>> foo data
> 
> ...assuming that we don't allow multipart in INFOs, yes.
>  
> Regards,
>  
> Christer
>  
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct 27 05:35:03 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 616573A6987;
	Mon, 27 Oct 2008 05:35:03 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A03D23A6A40
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 05:35:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4FIACe5UehRI for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 05:34:58 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 6F6EF3A6987
	for <sip@ietf.org>; Mon, 27 Oct 2008 05:34:58 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,492,1220227200"; d="scan'208";a="25739174"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 27 Oct 2008 12:34:57 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9RCYvJF032289; 
	Mon, 27 Oct 2008 08:34:57 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9RCYvFg021484;
	Mon, 27 Oct 2008 12:34:57 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 08:34:57 -0400
Received: from [10.86.249.64] ([10.86.249.64]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 08:34:56 -0400
Message-ID: <4905B570.2030805@cisco.com>
Date: Mon, 27 Oct 2008 08:34:56 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <48FDEAD8.8010803@cisco.com>	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>	<4901BA73.1010700@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>	<4901C2B1.1050209@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>	<4901D025.6060302@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>	<490239C8.3020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>	<4902467E.3010603@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFBA@esealmw113.eemea.ericsson.se>
	<490456A8.6090109@zon net.nl>	 <4904BE56.7050704@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF089CA230@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF089CA230@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 27 Oct 2008 12:34:56.0948 (UTC)
	FILETIME=[6B797F40:01C93830]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2700; t=1225110897;
	x=1225974897; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20Content-Type=20vs=09Info-Package=0A=20[was=20RE=3A=20dra
	ft-ietf-sip-info-events-00=3A=20multiple=09packages=20per=20
	INFO] |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=6CDpPQQ2EC4VZskazEAn9lI1AJKytce5Z3ryaVldVqs=;
	b=Y/T/yxzJzPpmYGnJZY4eW5e98EZhCQYKd8v0VnDaUCsirXlrX7ot3DiY11
	RqbZ21nLFc1JQN1p8+2PZgThVhEU31e7HJI8LYNCSPFHvv/336WL5zxF+xKI
	vZiRT2QHvf;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type
 vs	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple	packages
 per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Christer Holmberg wrote:
> Hi, 
> 
>>>> Like I wrote before: adding the INFO package as a parameter to 
>>>> Content-Type solves all this. I don't think C-D is the right header, 
>>>> because the "disposition" would depend on the semantics of 
>>>> the event package. We simply need an additional qualifier to
> disambiguate the 
>>>> interpretation of the body
>>> If you mentioned this before I missed it.
>>> Its an interesting idea. But I don't think it is technicallyh 
>>> feasible.
>>> AFAIK the parameters to a C-T must be defined as part of the 
>>> definition of the C-T. That wold mean that only 
>>> yet-to-be-defined C-Ts could be used for info packages.
> 
> That would be a reason to use a COMMON C-T type, and then a parameter
> which identifies the info package.
> 
> 
> 
> Let's keep in mind that info packages have been NEGOTIATED. Ie I will
> not send you a package unless you have indicated support for it.
> 
> Therefor, if I send you a picture, I don't think it matters if C-T is
> image/jpeg, or application/info;info-package=jpeg-package.
> 
> ...because, YOU know the semantics of the package. Also, since an info
> package is not supposed to change the core SIP state, the stack itself
> doesn't need to know the semantics of the body, does it?
> 
> 
> The problem is if I send you ONLY image/jpeg - without any negotiation,
> and semantics we both have agreed on. I don't know what you will do it.
> I think THAT is the problem that Eric initially raised.

So you are suggesting that *all* info packages share a single C-T, 
except for parameters to it. But then that single C-T may be used with a 
range of C-D types???

This seems like it would be quite inconvenient for the use case here. If 
there is to be an info package where I can send you a picture for some 
purpose, then the info package must specify the precise format of the 
picture (equivalent of C-T) because the C-T will be this fixed value. 
There may be a bunch of different C-Ts that are useful for encoding my 
picture, but I'll need a separate info package for each. And I'll need 
to fudge my encoding/decoding logic to no longer work based on C-T in 
this case.

IMO what I am suggesting is much simpler and more straightforward. A 
single C-D type identifies which body part should be processed as the 
"payload" of the INFO message. (In a way entirely analogous to the way 
the C-D of "session" identifies the payload of INVITE.) The C-T of this 
payload identifies how it is encoded, and the value from the 
Info-Package header is used to demultiplex the payload across all the 
possible ways that INFO can be used.

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


From sip-bounces@ietf.org  Mon Oct 27 06:28:40 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 975213A6ADB;
	Mon, 27 Oct 2008 06:28:40 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 57AF53A6AD5
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 06:28:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.901
X-Spam-Level: 
X-Spam-Status: No, score=-5.901 tagged_above=-999 required=5 tests=[AWL=0.348, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Hf3TeYaRRTyK for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 06:28:34 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id EBD3E3A6AC0
	for <sip@ietf.org>; Mon, 27 Oct 2008 06:28:33 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	BB9992015C; Mon, 27 Oct 2008 14:28:31 +0100 (CET)
X-AuditID: c1b4fb3e-aef86bb00000537b-f5-4905c1ffb1b5
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	A61072006D; Mon, 27 Oct 2008 14:28:31 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 14:28:31 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 27 Oct 2008 14:28:30 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF089F575A@esealmw113.eemea.ericsson.se>
In-Reply-To: <18693.39489.149630.617350@harjus.tutpro.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] New version of sip-keep draft
Thread-Index: Ack4L8jdNeHCHTK9S6KovJalwORWQwACAD2Q
References: <CA9998CD4A020D418654FCDEF4E707DF089CA7C8@esealmw113.eemea.ericsson.se>
	<18693.39489.149630.617350@harjus.tutpro.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 27 Oct 2008 13:28:31.0513 (UTC)
	FILETIME=[E7813090:01C93837]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] New version of sip-keep draft
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


 
>i don't understand why uac needs to act as a stun client.  
>why don't you simply say that the uac must be able to send 
>double crlf message to the edge proxy?  stun draft is 51 
>pages long and requiring keepalive implementer to read it is 
>clearly an overkill.

Perhaps. But, the whole idea is to use the keep-alive methods defined in
Outbound, and Outbound says stun.

Regards,

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


From sip-bounces@ietf.org  Mon Oct 27 06:44:52 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E29643A6A63;
	Mon, 27 Oct 2008 06:44:52 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F25873A6855
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 06:44:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.988
X-Spam-Level: 
X-Spam-Status: No, score=-5.988 tagged_above=-999 required=5 tests=[AWL=0.261, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id leEM5f69jWvq for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 06:44:51 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id B26E03A67DF
	for <sip@ietf.org>; Mon, 27 Oct 2008 06:44:50 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	DD1CE20A6A; Mon, 27 Oct 2008 14:44:24 +0100 (CET)
X-AuditID: c1b4fb3c-ab0c8bb0000015b5-b6-4905c5b860ae
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	AD15A20A43; Mon, 27 Oct 2008 14:44:24 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 14:44:24 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 27 Oct 2008 14:44:23 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF089F585E@esealmw113.eemea.ericsson.se>
In-Reply-To: <4905B570.2030805@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: Content-Type
	vs	Info-Package [was RE: draft-ietf-sip-info-events-00:
	multiple	packages per INFO]
Thread-Index: Ack4N568ZS3/CbIiRBSLHt7FYiDnKQAAdSUg
References: <48FDEAD8.8010803@cisco.com>	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>	<4901BA73.1010700@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>	<4901C2B1.1050209@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>	<4901D025.6060302@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>	<490239C8.3020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>	<4902467E.3010603@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFBA@esealmw113.eemea.ericsson.se>
	<490456A8.6090109@zon net.nl>	 <4904BE56.7050704@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF089CA230@esealmw113.eemea.ericsson.se>
	<4905B570.2030805@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 27 Oct 2008 13:44:24.0501 (UTC)
	FILETIME=[1F879E50:01C9383A]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type
	vs	Info-Package [was RE: draft-ietf-sip-info-events-00:
	multiple	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>>>>Like I wrote before: adding the INFO package as a parameter to 
>>>>>Content-Type solves all this. I don't think C-D is the right 
>>>>>header, because the "disposition" would depend on the semantics of 
>>>>>the event package. We simply need an additional qualifier to
>>>>>disambiguate the interpretation of the body
>>>>If you mentioned this before I missed it.
>>>>Its an interesting idea. But I don't think it is technicallyh 
>>>>feasible.
>>>>AFAIK the parameters to a C-T must be defined as part of the 
>>>>definition of the C-T. That wold mean that only yet-to-be-defined 
>>>>C-Ts could be used for info packages.
>> 
>>That would be a reason to use a COMMON C-T type, and then a parameter 
>>which identifies the info package.
>> 
>> 
>> 
>>Let's keep in mind that info packages have been NEGOTIATED. 
>>Ie I will not send you a package unless you have indicated support for
it.
>> 
>>Therefor, if I send you a picture, I don't think it matters if C-T is 
>>image/jpeg, or application/info;info-package=jpeg-package.
>> 
>>...because, YOU know the semantics of the package. Also, since an info

>>package is not supposed to change the core SIP state, the stack itself

>>doesn't need to know the semantics of the body, does it?
>> 
>> 
>>The problem is if I send you ONLY image/jpeg - without any 
>>negotiation, and semantics we both have agreed on. I don't 
>>know what you will do it. I think THAT is the problem that Eric
initially raised.
> 
>So you are suggesting that *all* info packages share a single C-T,
except for parameters to it.

Yes.

>But then that single C-T may be used with a range of C-D types???

Yes.

 
>This seems like it would be quite inconvenient for the use 
>case here. If there is to be an info package where I can send 
>you a picture for some purpose, then the info package must 
>specify the precise format of the picture (equivalent of C-T) 
>because the C-T will be this fixed value. 
>There may be a bunch of different C-Ts that are useful for 
>encoding my picture, but I'll need a separate info package 
>for each. And I'll need to fudge my encoding/decoding logic 
>to no longer work based on C-T in this case.
> 
>IMO what I am suggesting is much simpler and more 
>straightforward. A single C-D type identifies which body part 
>should be processed as the "payload" of the INFO message. (In 
>a way entirely analogous to the way the C-D of "session" 
>identifies the payload of INVITE.) The C-T of this payload 
>identifies how it is encoded, and the value from the 
>Info-Package header is used to demultiplex the payload across 
>all the possible ways that INFO can be used.

I am just wondering whether the C-D mechanism is 100% waterproof.

Or, are you proposing an info specific C-D type? "Info" for example?

Regards,

Christer
















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


From sip-bounces@ietf.org  Mon Oct 27 06:48:53 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B5BDA3A6AA3;
	Mon, 27 Oct 2008 06:48:53 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 024AD3A69EC
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 06:48:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.74
X-Spam-Level: 
X-Spam-Status: No, score=-5.74 tagged_above=-999 required=5 tests=[AWL=-0.091, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_37=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id lM5sj5JTz0CV for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 06:48:48 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id C27513A6A3E
	for <sip@ietf.org>; Mon, 27 Oct 2008 06:48:47 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	2B6CF20FF4; Mon, 27 Oct 2008 14:48:46 +0100 (CET)
X-AuditID: c1b4fb3e-aa77dbb00000537b-b8-4905c6be302d
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	0CEAC2036E; Mon, 27 Oct 2008 14:48:46 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 14:48:45 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 27 Oct 2008 14:48:44 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF089F589E@esealmw113.eemea.ericsson.se>
In-Reply-To: <4905B23F.10609@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: Content-Type
	vs	Info-Package [was RE: draft-ietf-sip-info-events-00:
	multiple	packages per INFO]
Thread-Index: Ack4OVMJwF/nOFu1QoyTya18xY0fTAAANTjg
References: <48FDEAD8.8010803@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>	<48FF2C45.7010204@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>	<4901BA73.1010700@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>	<4901C2B1.1050209@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>	<4901D025.6060302@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>	<490239C8.3020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>	<4902467E.3010603@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFBA@esealmw113.eemea.ericsson.se>
	<4905B23F.10609@cisco .com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 27 Oct 2008 13:48:45.0899 (UTC)
	FILETIME=[BB55C9B0:01C9383A]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type
	vs	Info-Package [was RE: draft-ietf-sip-info-events-00:
	multiple	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>>>So, just to make sure I understand: you are talking about 
>>>>a case where the INFO does contain a multipart message body, 
>>>>but only one of the mimes contains an actual info-package 
>>>>(the other mime(s) contains something else)?
>>>>pretty much. And to distinguish those, you need more than C-T.
>>>>But I think as we have been discussing, if we only allow one info 
>>>>package per INFO, then the Info-Package header belongs in the 
>>>>message, not in the body part.
>>  
>>>I don't think that defining Info-Package as a mime header 
>>>would even be within the scope of the SIP WG, would it?
> 
>Before I say more, I will first point out that discussion is 
>irrelevant if we only intend to allow one info package per INFO.

I think it's irrelevant if we only intent to allow one MIME per INFO.

Because, IF you have multipart, and one of them contains the info
package, the question is how to figure out which it is.


>But MIME bodies are extensible with arbitrary headers. I don't recall
if there is any requirement about standardizing them.

Well, if we could put the Info-Package header into the mime itself we
obviously won't have a problem.



>>My assumption has been that the I-P header is in the SIP  message
part, and that causes the problem: in the case of 
>>multipart, how to associate the correct mime with the I-P header?
> 
>Lets not get off in the weeds discussing this until and 
>unless we decide to support multiple info packages per INFO.
> 
>>I still think making assumptions on C-D is very dangerous, considering
the very little experience we have of the C-D 
>>header in the first place.
> 
>Could you please spell out precisely what your concern is?

You have multipart.

One mime contains the info package.

One mime contains something else.

My concern is that, by looking at the C-D you will always be able to
determine which mime contains the info package.

...again, unless you specify a info specific C-D value.

Regards,

Christer
















> 
> >> I'll revise your example a bit:
> >>
> >> INFO sip:foo@bar.com
> >> To:...
> >> From:...
> >> Some-Header: CID:abcdefg
> >> Info-Package: foo
> >> Content-Type:multipart/mixed
> >> Content-Length:...
> >>
> >> --boundary
> >> Content-Type: application/foo-data
> >> Content-Disposition: package;handling=required
> >>
> >> foo data
> >> --boundary
> >> Content-ID: abcdefg
> >> Content-Type: application/some-header-data
> >> Content-Disposition: by-reference;handling=optional
> >>
> >> some other (non-info package) data
> >> --boundary--
> >>
> >> In the above I have used C-D of "package" to identify the 
> part that 
> >> contains the info package. That is yet to be determined, 
> but I think 
> >> it needs to be well defined, even if it is "render".
> > 
> > Again, I don't think using C-D for the "association" is a good idea.
> >  
> > 
> >> A more straightforward case would be:
> >>
> >> INFO sip:foo@bar.com
> >> To:...
> >> From:...
> >> Info-Package: foo
> >> Content-Type: application/foo-data
> >> Content-Disposition: package;handling=required Content-Length:10
> >>
> >> foo data
> > 
> > ...assuming that we don't allow multipart in INFOs, yes.
> >  
> > Regards,
> >  
> > Christer
> >  
> > _______________________________________________
> > Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol Use 
> > sip-implementors@cs.columbia.edu for questions on current sip Use 
> > sipping@ietf.org for new developments on the application of sip
> > 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct 27 07:06:30 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CEA3B3A6B00;
	Mon, 27 Oct 2008 07:06:30 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C4B2A3A6A88
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 07:06:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_37=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Ge3GYcSLCc1k for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 07:06:28 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 6687B3A6B00
	for <sip@ietf.org>; Mon, 27 Oct 2008 07:06:28 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,492,1220227200"; d="scan'208";a="25785263"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 27 Oct 2008 14:06:27 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9RE6RFD021671; 
	Mon, 27 Oct 2008 10:06:27 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9RE6RxP026761;
	Mon, 27 Oct 2008 14:06:27 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 10:06:27 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 10:06:27 -0400
Message-ID: <4905CAE2.9020808@cisco.com>
Date: Mon, 27 Oct 2008 10:06:26 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <48FDEAD8.8010803@cisco.com>	<48FF2C45.7010204@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>	<4901BA73.1010700@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>	<4901C2B1.1050209@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>	<4901D025.6060302@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>	<490239C8.3020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>	<4902467E.3010603@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFBA@esealmw113.eemea.ericsson.se>	<4905B23F.10609@cisco
	.com>
	<CA9998CD4A020D418654FCDEF4E707DF089F589E@esealmw113.eemea.ericss
	on.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF089F589E@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 27 Oct 2008 14:06:27.0115 (UTC)
	FILETIME=[33DE7FB0:01C9383D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5055; t=1225116387;
	x=1225980387; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20Content-Type=09vs=09Info-Package=0A=20[was=20RE=3A=20dra
	ft-ietf-sip-info-events-00=3A=09multiple=09packages=20per=20
	INFO] |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=zbBuI2sEt9IwzYQQF0t7lYW4iQNMhcwBUedlVrMsg7Y=;
	b=kl/qP7blCduSB0iCt4KWhwtJqkTDF1ASzizH+Nw6w4SMRsUd9992jVcY9E
	9xNDJLo/h2uP589BlL76pS5cuNepptAVJaGFrjaCyMv/+msMtt8LZoAo8aM4
	jaCrX2ckQK;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00:
 Content-Type	vs	Info-Package [was RE:
 draft-ietf-sip-info-events-00:	multiple	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Christer Holmberg wrote:
> Hi, 
> 
>>>>> So, just to make sure I understand: you are talking about 
>>>>> a case where the INFO does contain a multipart message body, 
>>>>> but only one of the mimes contains an actual info-package 
>>>>> (the other mime(s) contains something else)?
>>>>> pretty much. And to distinguish those, you need more than C-T.
>>>>> But I think as we have been discussing, if we only allow one info 
>>>>> package per INFO, then the Info-Package header belongs in the 
>>>>> message, not in the body part.
>>>  
>>>> I don't think that defining Info-Package as a mime header 
>>>> would even be within the scope of the SIP WG, would it?
>> Before I say more, I will first point out that discussion is 
>> irrelevant if we only intend to allow one info package per INFO.
> 
> I think it's irrelevant if we only intent to allow one MIME per INFO.

I think it is irrelevant if we only allow one info package per INFO, 
even if we allow multipart bodies where one of those is the info package.

> Because, IF you have multipart, and one of them contains the info
> package, the question is how to figure out which it is.

Yes, we then require a way to distinguish which part is the info 
package. Hopefully we can find a way better than using the Info-Package 
header in the body part to do that.

>> But MIME bodies are extensible with arbitrary headers. I don't recall
> if there is any requirement about standardizing them.
> 
> Well, if we could put the Info-Package header into the mime itself we
> obviously won't have a problem.

I'd rather not have to be searching all the body parts to that extent to 
figure it out. The advantage of C-D is that its already necessary to 
look at that to figure out the role of each body part.

>>> My assumption has been that the I-P header is in the SIP  message
> part, and that causes the problem: in the case of 
>>> multipart, how to associate the correct mime with the I-P header?
>> Lets not get off in the weeds discussing this until and 
>> unless we decide to support multiple info packages per INFO.
>>
>>> I still think making assumptions on C-D is very dangerous, considering
> the very little experience we have of the C-D 
>>> header in the first place.
>> Could you please spell out precisely what your concern is?
> 
> You have multipart.
> 
> One mime contains the info package.
> 
> One mime contains something else.
> 
> My concern is that, by looking at the C-D you will always be able to
> determine which mime contains the info package.
> 
> ...again, unless you specify a info specific C-D value.

Indeed, IMO there *must* be a C-D value that, *in INFO messages*, is 
used *only* for the info package body part.

My preference would be for a new value, say "package", "info", or 
"info-package". I think we *might* be able to define that "render" 
serves this purpose *for INFO messages*, but I would rather not do that 
because it is indeed asking from trouble and confusion.

	Thanks,
	Paul

> Regards,
> 
> Christer
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>>>> I'll revise your example a bit:
>>>>
>>>> INFO sip:foo@bar.com
>>>> To:...
>>>> From:...
>>>> Some-Header: CID:abcdefg
>>>> Info-Package: foo
>>>> Content-Type:multipart/mixed
>>>> Content-Length:...
>>>>
>>>> --boundary
>>>> Content-Type: application/foo-data
>>>> Content-Disposition: package;handling=required
>>>>
>>>> foo data
>>>> --boundary
>>>> Content-ID: abcdefg
>>>> Content-Type: application/some-header-data
>>>> Content-Disposition: by-reference;handling=optional
>>>>
>>>> some other (non-info package) data
>>>> --boundary--
>>>>
>>>> In the above I have used C-D of "package" to identify the 
>> part that 
>>>> contains the info package. That is yet to be determined, 
>> but I think 
>>>> it needs to be well defined, even if it is "render".
>>> Again, I don't think using C-D for the "association" is a good idea.
>>>  
>>>
>>>> A more straightforward case would be:
>>>>
>>>> INFO sip:foo@bar.com
>>>> To:...
>>>> From:...
>>>> Info-Package: foo
>>>> Content-Type: application/foo-data
>>>> Content-Disposition: package;handling=required Content-Length:10
>>>>
>>>> foo data
>>> ...assuming that we don't allow multipart in INFOs, yes.
>>>  
>>> Regards,
>>>  
>>> Christer
>>>  
>>> _______________________________________________
>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>> This list is for NEW development of the core SIP Protocol Use 
>>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>>> sipping@ietf.org for new developments on the application of sip
>>>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct 27 07:12:36 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DED7D3A6B00;
	Mon, 27 Oct 2008 07:12:36 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3A1153A6B00
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 07:12:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tIVhMxaPfh+B for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 07:12:35 -0700 (PDT)
Received: from taimen.tutpro.com (harjus.tutpro.com [192.98.100.3])
	by core3.amsl.com (Postfix) with ESMTP id 57B503A69EC
	for <sip@ietf.org>; Mon, 27 Oct 2008 07:12:35 -0700 (PDT)
Received: by taimen.tutpro.com (Postfix, from userid 1000)
	id 6ADF533A679; Mon, 27 Oct 2008 16:12:36 +0200 (EET)
MIME-Version: 1.0
Message-ID: <18693.52308.390388.179923@harjus.tutpro.com>
Date: Mon, 27 Oct 2008 16:12:36 +0200
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF089F575A@esealmw113.eemea.ericsson.se>
References: <CA9998CD4A020D418654FCDEF4E707DF089CA7C8@esealmw113.eemea.ericsson.se>
	<18693.39489.149630.617350@harjus.tutpro.com>
	<CA9998CD4A020D418654FCDEF4E707DF089F575A@esealmw113.eemea.ericsson.se>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] New version of sip-keep draft
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Christer Holmberg writes:

 > Perhaps. But, the whole idea is to use the keep-alive methods defined in
 > Outbound, and Outbound says stun.

this is yet another example of badly organized i-d structure.  keepalive
mechanisms should have been defined in its own i-d, not in stun or
outbound i-d.  all of these drafts should go back to drawing board.

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


From sip-bounces@ietf.org  Mon Oct 27 07:15:00 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D47333A6B53;
	Mon, 27 Oct 2008 07:15:00 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9932E3A6B47
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 07:14:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.025
X-Spam-Level: 
X-Spam-Status: No, score=-6.025 tagged_above=-999 required=5 tests=[AWL=0.224, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id lYCLxSHAV1o0 for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 07:14:58 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id BFC403A6B29
	for <sip@ietf.org>; Mon, 27 Oct 2008 07:14:58 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	3696320A09; Mon, 27 Oct 2008 15:14:57 +0100 (CET)
X-AuditID: c1b4fb3c-af8d1bb0000015b5-f9-4905cce1cb61
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	1630720798; Mon, 27 Oct 2008 15:14:57 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 15:14:56 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 27 Oct 2008 15:14:55 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF089F59E5@esealmw113.eemea.ericsson.se>
In-Reply-To: <18693.52308.390388.179923@harjus.tutpro.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] New version of sip-keep draft
Thread-Index: Ack4Pg9XwQT2rFzJRgGdUFqT3wvbEwAABblg
References: <CA9998CD4A020D418654FCDEF4E707DF089CA7C8@esealmw113.eemea.ericsson.se><18693.39489.149630.617350@harjus.tutpro.com><CA9998CD4A020D418654FCDEF4E707DF089F575A@esealmw113.eemea.ericsson.se>
	<18693.52308.390388.179923@harjus.tutpro.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Juha Heinanen" <jh@tutpro.com>
X-OriginalArrivalTime: 27 Oct 2008 14:14:56.0911 (UTC)
	FILETIME=[63BB31F0:01C9383E]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] New version of sip-keep draft
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 
>>Perhaps. But, the whole idea is to use the keep-alive methods defined
in Outbound, and Outbound says stun.
> 
>this is yet another example of badly organized i-d structure. 
>keepalive mechanisms should have been defined in its own 
>i-d, not in stun or outbound i-d.  all of these drafts should 
>go back to drawing board.

If people want to actually define the keep-alive mechanism in the keep
draft that's fine with me.

BUT, I have done the draft based on the current working assumptions,
where the keep-alive mechanism is defined in Outbound.

Regards,

Christer

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


From sip-bounces@ietf.org  Mon Oct 27 11:24:35 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 89F4F28C1FC;
	Mon, 27 Oct 2008 11:24:35 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 255723A6B44
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 11:24:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.757
X-Spam-Level: 
X-Spam-Status: No, score=-5.757 tagged_above=-999 required=5
	tests=[AWL=-0.108, BAYES_00=-2.599, HELO_EQ_SE=0.35,
	J_CHICKENPOX_37=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id hK8a2j9Bwpcw for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 11:24:33 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 3BEEF3A6B9A
	for <sip@ietf.org>; Mon, 27 Oct 2008 11:23:22 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	E4D7520B96; Mon, 27 Oct 2008 19:22:46 +0100 (CET)
X-AuditID: c1b4fb3c-ac0cabb0000015b5-d9-490606f6d9ba
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	B3C2520521; Mon, 27 Oct 2008 19:22:46 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 19:22:45 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 27 Oct 2008 19:22:44 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F8FF@esealmw113.eemea.ericsson.se>
In-Reply-To: <4905CAE2.9020808@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00:
	Content-Type	vs	Info-Package [was RE:
	draft-ietf-sip-info-events-00:	multiple	packages per INFO]
Thread-Index: Ack4XufQ0C/eC5EQQ/q9pzuG+lVSPgAAD/sA
References: <48FDEAD8.8010803@cisco.com>	<48FF2C45.7010204@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>	<4901BA73.1010700@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>	<4901C2B1.1050209@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>	<4901D025.6060302@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>	<490239C8.3020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>	<4902467E.3010603@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFBA@esealmw113.eemea.ericsson.se>	<4905B23F.10609@cisco.com><CA9998CD4A020D418654FCDEF4E707DF089F589E@esealmw113.eemea.ericsson
	.se> <49 05CAE2.9020808@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 27 Oct 2008 18:22:45.0466 (UTC)
	FILETIME=[0214A3A0:01C93861]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00:
	Content-Type	vs	Info-Package [was RE:
	draft-ietf-sip-info-events-00:	multiple	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>>>>> So, just to make sure I understand: you are talking about a case 
>>>>>> where the INFO does contain a multipart message body, but only
one 
>>>>>> of the mimes contains an actual info-package (the other mime(s) 
>>>>>> contains something else)?
>>>>>> pretty much. And to distinguish those, you need more than C-T.
>>>>>> But I think as we have been discussing, if we only allow one info

>>>>>> package per INFO, then the Info-Package header belongs in the 
>>>>>> message, not in the body part.
>>>>  
>>>>> I don't think that defining Info-Package as a mime header would 
>>>>> even be within the scope of the SIP WG, would it?
>>> Before I say more, I will first point out that discussion is 
>>> irrelevant if we only intend to allow one info package per INFO.
>> 
>>I think it's irrelevant if we only intent to allow one MIME per INFO.
>
>I think it is irrelevant if we only allow one info package per INFO,
even if we allow multipart bodies where one of those is the info
package.
>
>>Because, IF you have multipart, and one of them contains the info
package, the question is how to figure out which it is.
>
>Yes, we then require a way to distinguish which part is the info
package. Hopefully we can find a way better than using the Info-Package
header in the body part to do that.
>
>>>But MIME bodies are extensible with arbitrary headers. I don't recall
if there is any requirement about standardizing them.
>> 
>>Well, if we could put the Info-Package header into the mime itself we
obviously won't have a problem.
>
>I'd rather not have to be searching all the body parts to that extent
to figure it out. The advantage of C-D is that its already necessary to
look at that to figure out the role of each body part.

You will have to look through "all" (not sure there will be too many...)
body parts anyway. Even if the info package happens to be in the "first"
body part you look at, you still need to look through the rest if there
are body parts with handling=required etc. That is normal multipart
handling.

>>>Could you please spell out precisely what your concern is?
>> 
>>You have multipart.
>> 
>>One mime contains the info package.
>> 
>>One mime contains something else.
>> 
>>My concern is that, by looking at the C-D you will always be able to 
>>determine which mime contains the info package.
>> 
>>...again, unless you specify a info specific C-D value.
>
>Indeed, IMO there *must* be a C-D value that, *in INFO messages*, is
used *only* for the info package body part.
>
>My preference would be for a new value, say "package", "info", or
"info-package". I think we *might* be able to define that "render" 
>serves this purpose *for INFO messages*, but I would rather not do that
because it is indeed asking from trouble and confusion.

IF we define a new C-D value, which is unique for info packages, I have
no problem with a C-D based solution. 

But, it would still be more work to define info packages, because you
would need to specify which C-T value to use. Maybe not a big issue if
you can use an existing value, but it's more work if you have to define
a new value. For example, is there a standardized value which could be
used for DTMF? Has Cisco registerd the value they use in C-T when
sending DTMFs? :)

My issue is if we want to re-use an existing value, because I don't
think we for sure can say that couldn't be a case where more than one
body part has a "render" value (or whatever existing value we would
choose for info packages).

Regards,

Christer






>>>> I'll revise your example a bit:
>>>>
>>>> INFO sip:foo@bar.com
>>>> To:...
>>>> From:...
>>>> Some-Header: CID:abcdefg
>>>> Info-Package: foo
>>>> Content-Type:multipart/mixed
>>>> Content-Length:...
>>>>
>>>> --boundary
>>>> Content-Type: application/foo-data
>>>> Content-Disposition: package;handling=required
>>>>
>>>> foo data
>>>> --boundary
>>>> Content-ID: abcdefg
>>>> Content-Type: application/some-header-data
>>>> Content-Disposition: by-reference;handling=optional
>>>>
>>>> some other (non-info package) data
>>>> --boundary--
>>>>
>>>> In the above I have used C-D of "package" to identify the
>> part that
>>>> contains the info package. That is yet to be determined,
>> but I think
>>>> it needs to be well defined, even if it is "render".
>>> Again, I don't think using C-D for the "association" is a good idea.
>>>  
>>>
>>>> A more straightforward case would be:
>>>>
>>>> INFO sip:foo@bar.com
>>>> To:...
>>>> From:...
>>>> Info-Package: foo
>>>> Content-Type: application/foo-data
>>>> Content-Disposition: package;handling=required Content-Length:10
>>>>
>>>> foo data
>>> ...assuming that we don't allow multipart in INFOs, yes.
>>>  
>>> Regards,
>>>  
>>> Christer
>>>  
>>> _______________________________________________
>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>> This list is for NEW development of the core SIP Protocol Use 
>>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>>> sipping@ietf.org for new developments on the application of sip
>>>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors@cs.columbia.edu for questions on current sip Use 
> sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol Use
sip-implementors@cs.columbia.edu for questions on current sip Use
sipping@ietf.org for new developments on the application of sip
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct 27 11:52:18 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C1A2228C194;
	Mon, 27 Oct 2008 11:52:18 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0593D28C194
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 11:52:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.300, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id N2ILXx+Zjvbe for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 11:52:16 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 8172A28C156
	for <sip@ietf.org>; Mon, 27 Oct 2008 11:52:16 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,493,1220227200"; d="scan'208";a="25826730"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 27 Oct 2008 18:52:07 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9RIq5Wg015309; 
	Mon, 27 Oct 2008 14:52:05 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9RIq5ik017045;
	Mon, 27 Oct 2008 18:52:05 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 14:52:05 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 14:52:05 -0400
Message-ID: <49060DD4.7070804@cisco.com>
Date: Mon, 27 Oct 2008 14:52:04 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <48FDEAD8.8010803@cisco.com>	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>	<4901BA73.1010700@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>	<4901C2B1.1050209@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>	<4901D025.6060302@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>	<490239C8.3020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>	<4902467E.3010603@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFBA@esealmw113.eemea.ericsson.se>	<4905B23F.10609@cisco.com><CA9998CD4A020D418654FCDEF4E707DF089F589E@esealmw113.eemea.ericsson
	.se> <49	05CAE2.9020808@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8FF@esealmw113.eemea.ericss
	on.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F8FF@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 27 Oct 2008 18:52:05.0494 (UTC)
	FILETIME=[1B239960:01C93865]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3459; t=1225133525;
	x=1225997525; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20Content-Type=09vs=09Info-Package=0A=20[was=20RE=3A=20dra
	ft-ietf-sip-info-events-00=3A=09multiple=09packages=20per=20
	INFO] |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=eJ19rN3z9sSEMak7tGYg12LxYrhH10/lnwGl08VsMIY=;
	b=Jc+8vkUOO/mq6W1t3LgPXtM4AFW5wUkFnKRJvFuExYIYki/ui5ark7fAsx
	0g/ck/VqYyoqHkU67bovPXXFiwTNCVTSC3xB9GWc6Bmnb1nqBkXJCPHUspy6
	V7s6+p60+4;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00:
 Content-Type	vs	Info-Package [was RE:
 draft-ietf-sip-info-events-00:	multiple	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Pruning out a lot...

Christer Holmberg wrote:

>> I'd rather not have to be searching all the body parts to that extent
>> to figure it out. The advantage of C-D is that its already necessary to
>> look at that to figure out the role of each body part.
> 
> You will have to look through "all" (not sure there will be too many...)
> body parts anyway.

If implementing for the general case, it will at least be a loop over 
parts of a multipart/mixed, if present, and possibly recursion.

> Even if the info package happens to be in the "first"
> body part you look at, you still need to look through the rest if there
> are body parts with handling=required etc. That is normal multipart
> handling.

See Dale's document with a process oriented take on the C-D stuff.
In general, every UA is going to have to implement that general 
framework for processing body parts, independent of method.

What we are talking about here is potentially another search *in 
addition* to that. Admittedly its not a huge deal, but it starts to mess 
up modularity of implementation.

>> My preference would be for a new value, say "package", "info", or
> "info-package". I think we *might* be able to define that "render" 
>> serves this purpose *for INFO messages*, but I would rather not do that
> because it is indeed asking from trouble and confusion.
> 
> IF we define a new C-D value, which is unique for info packages, I have
> no problem with a C-D based solution. 

OK. That is progress!!!

> But, it would still be more work to define info packages, because you
> would need to specify which C-T value to use.

The document already calls for this:

    7.2.4.  INFO Bodies

    Each Info Package MUST define what type or types of bodies are
    expected in INFO requests.  Such packages MUST specify or cite
    detailed specifications for the syntax and semantics associated with
    such a body.

    Info Packages also MUST define a default MIME type if the "Accept"
    header fails to define any MIME types in the INVITE request.

The wording could be better. There are no explicit IANA considerations 
about registering an INFO package. Its just implied here. Its a little 
confusing here what is intended to be part of the *definition* of a new 
package vs. what is intended to be in the content of a particular 
package instance in an INFO message.

> Maybe not a big issue if
> you can use an existing value, but it's more work if you have to define
> a new value.

If you need to do that, then so be it.

> For example, is there a standardized value which could be
> used for DTMF? Has Cisco registerd the value they use in C-T when
> sending DTMFs? :)

I don't know, but I doubt it.

> My issue is if we want to re-use an existing value, because I don't
> think we for sure can say that couldn't be a case where more than one
> body part has a "render" value (or whatever existing value we would
> choose for info packages).

This is all hypothetical, because we don't have any usages with the new 
info package stuff.

What I guess you are getting at is if there are any existing uses of 
body parts with "render" that might have to coexist with the info 
package in the message. I agree that is a potential problem, since for 
instance people rarely put C-D for a multipart itself, thus defaulting 
to "render".

So I agree, we need a new value.

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


From sip-bounces@ietf.org  Mon Oct 27 12:09:00 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F09973A6BA2;
	Mon, 27 Oct 2008 12:08:59 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0FC223A6804
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 12:08:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id bthqdKf-14wo for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 12:08:57 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id F21513A67D4
	for <sip@ietf.org>; Mon, 27 Oct 2008 12:08:56 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,493,1220227200"; d="scan'208";a="183499634"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 27 Oct 2008 19:08:56 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9RJ8uio006862; 
	Mon, 27 Oct 2008 12:08:56 -0700
Received: from [128.107.147.212] ([128.107.147.212])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9RJ8u4p028483;
	Mon, 27 Oct 2008 19:08:56 GMT
Message-ID: <490611C8.5090506@cisco.com>
Date: Mon, 27 Oct 2008 12:08:56 -0700
From: Anders Kristensen <andersk@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
References: <48FDEB20.9040109@cisco.com>	<200810241732.m9OHWbxv52636270@shell01.TheWorld.com>	<4902FC59.3000303@zonnet.nl>
	<490326C7.5010601@cisco.com>
In-Reply-To: <490326C7.5010601@cisco.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3798; t=1225134536;
	x=1225998536; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=andersk@cisco.com;
	z=From:=20Anders=20Kristensen=20<andersk@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20CANCEL??? |Sender:=20;
	bh=z5RCV5KC5Ra3Ut3nhg9zuv/MJGDrCtP99G3ArL/m+Bk=;
	b=l4RRupMcwO1vlRb8tmZFGYAG7HhHS+oveguSH+nfXAQ/4t1+gcCdex5qeB
	mn9K6ofcZ2VmADmjbyigUkp3jigS1CQiNNlt0KpDCXIT/Tk8S9GhtMhTYevs
	c6Sii0/QlY2z+DBN51eDHR8RFLCZ6oh5wVGf577k/VfAyYhVbTZ/U=;
Authentication-Results: sj-dkim-1; header.From=andersk@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: sip@ietf.org
Subject: Re: [Sip] draft-ietf-sip-info-events-00: CANCEL???
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Paul Kyzivat wrote:
> Jeroen,
> 
> Re CANCEL of INFO, I don't see this any different than CANCEL of any 
> other non-INVITE transaction: you are free to ask, but don't get your 
> hopes up, because it probably won't work.

True, it's not different from other non-INVITE transactions but given 
the inability to challenge CANCELs maybe we'd be better off not 
perpetuating it's use. If it works, it's a potential security hole, if 
it doesn't then we don't loose anything by not having the option of 
canceling.

Thanks,
Anders

> 
> Re CANCEL of reINVITE: I already raised the issue of the need to define 
> what happens to the negotiated info package state when a reINVITE fails. 
> This is just an instance of that. (The issue is around the resulting 487 
> response to the INVITE, not the CANCEL itself that is the issue.)
> 
>     Thanks,
>     Paul
> 
> Jeroen van Bemmel wrote:
>> All,
>>
>> IMHO allowing CANCEL of INFO requests is a bad idea, it introduces a 
>> RACE condition that any CANCEL will generally loose. It also 
>> introduces semantic issues: what does it mean to cancel a given INFO 
>> event? For INVITE it somewhat intuitively means stop ringing the phone 
>> and signal to the callee that the call was aborted, it is not 
>> generally clear what CANCEL for a generic INFO event would mean. For 
>> example, an INFO event might trigger some action that is not 
>> "undoable" (e.g. a gaming move in a multiplayer game, the final digit 
>> of a 4-digit access code, ... )
>>
>> I do have a question regarding the - somewhat hypothetical - scenario 
>> of a mid-dialog INVITE being CANCELed: How does that affect the INFO 
>> negotiation mechanism state? I guess from a UAS perspective the 
>> UAC-provided Send-Info and Recv-Info in the INVITE should be reverted 
>> back to the last known values, and for the UAC the 487 response should 
>> cause it to revert to the previous state?
>>
>> Regards,
>> Jeroen
>>
>> Dale.Worley@comcast.net wrote:
>>>    From: Paul Kyzivat <pkyzivat@cisco.com>
>>>
>>>    I have a question regarding the following paragraph:
>>>
>>>        A UAC MAY CANCEL an INFO request.  A UAS receiving a CANCEL 
>>> for an
>>>        INFO request SHOULD respond to the INFO with a "487 Request
>>>        Cancelled" response unless the UAC has already sent a final 
>>> response.
>>>        The UAS then MUST ignore future INFO requests.
>>>
>>>    Why would the CANCEL affect *future* info requests???
>>>
>>> I'm sure we *don't* want CANCEL to affect future INFO requests.  That
>>> adds another bit of state that has to be remembered, and I'm sure it
>>> will cause some weird complications.  (Among other things, what is it
>>> to "ignore" an INFO request?  What response code is that?)
>>>
>>> Dale
>>> _______________________________________________
>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>> This list is for NEW development of the core SIP Protocol
>>> Use sip-implementors@cs.columbia.edu for questions on current sip
>>> Use sipping@ietf.org for new developments on the application of sip
>>>
>>>   
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sipping@ietf.org for new developments on the application of sip
>>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Mon Oct 27 13:14:59 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E88163A68E1;
	Mon, 27 Oct 2008 13:14:58 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 119BF3A68E1
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 13:14:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id esZf0EqinGWT for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 13:14:57 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27])
	by core3.amsl.com (Postfix) with ESMTP id D19FF3A680D
	for <sip@ietf.org>; Mon, 27 Oct 2008 13:14:56 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 9so996104eyd.31
	for <sip@ietf.org>; Mon, 27 Oct 2008 13:14:45 -0700 (PDT)
Received: by 10.210.123.2 with SMTP id v2mr7213773ebc.0.1225138485145;
	Mon, 27 Oct 2008 13:14:45 -0700 (PDT)
Received: from portatil.local (240.pool85-58-8.dynamic.orange.es [85.58.8.240])
	by mx.google.com with ESMTPS id c24sm326342ika.8.2008.10.27.13.14.43
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Mon, 27 Oct 2008 13:14:44 -0700 (PDT)
From: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
To: sip@ietf.org
Date: Mon, 27 Oct 2008 21:14:40 +0100
User-Agent: KMail/1.9.9
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
	<18693.28129.618794.915466@harjus.tutpro.com>
In-Reply-To: <18693.28129.618794.915466@harjus.tutpro.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810272114.40331.ibc@aliax.net>
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR Identity
	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

El Lunes, 27 de Octubre de 2008, Juha Heinanen escribi=F3:
> i don't know about the dialog event solution, but what i had proposed is
> VERY simple: =A0one request and a response to it.

It's basically the same, but devices that already support Dialog event supp=
ort =

(as servers) already implement this draft "Dialog Event foR Identity =

VErification" while using a new custom request/response would require devic=
es =

supporting it as a new feature.

-- =

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


From sip-bounces@ietf.org  Mon Oct 27 13:48:12 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 08DB23A69E7;
	Mon, 27 Oct 2008 13:48:12 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E26743A68E1
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 13:48:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.043
X-Spam-Level: 
X-Spam-Status: No, score=-6.043 tagged_above=-999 required=5 tests=[AWL=0.206, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rviaeRFz8xc9 for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 13:48:10 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id B80593A68C4
	for <sip@ietf.org>; Mon, 27 Oct 2008 13:48:09 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	2268C203F1; Mon, 27 Oct 2008 21:48:08 +0100 (CET)
X-AuditID: c1b4fb3e-adf84bb00000537b-c4-490629076f85
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	F255B2039F; Mon, 27 Oct 2008 21:48:07 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 21:48:07 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 27 Oct 2008 21:48:07 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F906@esealmw113.eemea.ericsson.se>
In-Reply-To: <49060DD4.7070804@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00:
	Content-Type	vs	Info-Package [was RE:
	draft-ietf-sip-info-events-00:	multiple	packages per INFO]
Thread-Index: Ack4ZSJRtUSNJmHeTDOPfyHthqQ3/gADphlA
References: <48FDEAD8.8010803@cisco.com>	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>	<4901BA73.1010700@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>	<4901C2B1.1050209@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>	<4901D025.6060302@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>	<490239C8.3020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>	<4902467E.3010603@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFBA@esealmw113.eemea.ericsson.se>	<4905B23F.10609@cisco.com><CA9998CD4A020D418654FCDEF4E707DF089F589E@esealmw113.eemea.ericsson
	.se> <49	05CAE2.9020808@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8FF@esealmw113.eemea.ericss
	on.se> <49060DD4.7070804@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 27 Oct 2008 20:48:07.0900 (UTC)
	FILETIME=[510E71C0:01C93875]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00:
	Content-Type	vs	Info-Package [was RE:
	draft-ietf-sip-info-events-00:	multiple	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi, 

>>>My preference would be for a new value, say "package", "info", or
>>>"info-package". I think we *might* be able to define that "render" 
>>>serves this purpose *for INFO messages*, but I would rather not do 
>>>that because it is indeed asking from trouble and confusion.
>> 
>>IF we define a new C-D value, which is unique for info packages, I
have no problem with a C-D based solution.
>
>OK. That is progress!!!
>
>>But, it would still be more work to define info packages, because you 
>>would need to specify which C-T value to use.
>
>The document already calls for this:
>
>    7.2.4.  INFO Bodies
>
>    Each Info Package MUST define what type or types of bodies are
>    expected in INFO requests.  Such packages MUST specify or cite
>    detailed specifications for the syntax and semantics associated
with
>    such a body.
>
>    Info Packages also MUST define a default MIME type if the "Accept"
>    header fails to define any MIME types in the INVITE request.

Yes, it's in the document. The point was that one may have to define
this new MIME type. But, maybe that is not a big problem (I haven't
defined mime types, so I can't tell).

>The wording could be better. There are no explicit IANA considerations
about registering an INFO package. Its just implied here. Its a little
confusing here what is intended to be part of the 
>*definition* of a new package vs. what is intended to be in the content
of a particular package instance in an INFO message.

We do need to have a section on what needs to be part of an info package
definition. The mime type is one thing, for sure.

I guess we should also look at what/if we can re-use from SIP events.

We also need to decide whether info packages should have a version
number system. From experience I think that would be very useful.

Info-Package: foo-package;version=1

...or something like that.

>>My issue is if we want to re-use an existing value, because I don't
think we for sure can say that couldn't be a case where more than one 
>>body part has a "render" value (or whatever existing value we would
choose for info packages).
>
>This is all hypothetical, because we don't have any usages with the new
info package stuff.

Exactly.

>What I guess you are getting at is if there are any existing uses of
body parts with "render" that might have to coexist with the info
package in the message.

Yes.

>So I agree, we need a new value.

Good :)

Regards,

Christer

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


From sip-bounces@ietf.org  Mon Oct 27 14:01:05 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BCB4B28C1EA;
	Mon, 27 Oct 2008 14:01:05 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ACBF53A6A66
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 14:01:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.066
X-Spam-Level: 
X-Spam-Status: No, score=-6.066 tagged_above=-999 required=5 tests=[AWL=0.183, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RRQWtQPlzy7B for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 14:01:03 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 8D49728C1EA
	for <sip@ietf.org>; Mon, 27 Oct 2008 14:00:35 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	D79DF20CB6; Mon, 27 Oct 2008 22:00:33 +0100 (CET)
X-AuditID: c1b4fb3c-ab8c9bb0000015b5-e7-49062bf1cbae
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	B760E20C92; Mon, 27 Oct 2008 22:00:33 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 22:00:31 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 27 Oct 2008 22:00:30 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF05C0F907@esealmw113.eemea.ericsson.se>
In-Reply-To: <5D1A7985295922448D5550C94DE2918002426290@DEEXC1U01.de.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Draft-ietf-sip-info-events-00: Other messages for
	Send-Infoand Recv-Info
Thread-Index: Ack4LYR0jzUi9yAlSwq3f5sjVq46fwAR+Kdw
References: <5D1A7985295922448D5550C94DE2918002426290@DEEXC1U01.de.lucent.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>,
	"SIP IETF" <sip@ietf.org>
X-OriginalArrivalTime: 27 Oct 2008 21:00:31.0240 (UTC)
	FILETIME=[0C1F2080:01C93877]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] Draft-ietf-sip-info-events-00: Other messages for
	Send-Infoand Recv-Info
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi Keith, 

>I notice that the current document does define the validity of these
elements for REG, but leaves the section describing the use empty. If
the purpose of inclusion was to somehow register this things in 
>the registrar against the contact, surely this should be left to
feature tags, as I think has already been suggested on the list. Or was
there some other purpose? If not, I would suggest removal.

As indicated earlier, being able to register the supported packages, and
use them for forking, would be very useful, and I think that is the
intention of the text.

Yes, maybe we need to define a feature tag, or feature tags. The
question is whether we would need a single feature tag which can list
all supported info packages, or a feature tag for each package (in which
case each info package definition would have to specify a feature tag
value). The advantage of having separate feature tags is that it gives
you much more flexibility.

>The other method that crossed my mind was OPTIONS. Should OPTIONS
provide a mechanism of identifying what the entity at the Request-URI
supports, in the same manner as it does for SDP and option tags, or 
>should be ignore this possibility on the grounds of simplicity.
>Thoughts?

I see no reasons why the Info headers couldn't be included in OPTIONS,
so I think that should be fixed.

Regards,

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


From sip-bounces@ietf.org  Mon Oct 27 14:14:10 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7932D28C10E;
	Mon, 27 Oct 2008 14:14:10 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BAE363A69E7
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 14:14:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.389
X-Spam-Level: 
X-Spam-Status: No, score=-2.389 tagged_above=-999 required=5
	tests=[AWL=-0.090, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5sj-X5yfUJcC for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 14:14:08 -0700 (PDT)
Received: from taimen.tutpro.com (harjus.tutpro.com [192.98.100.3])
	by core3.amsl.com (Postfix) with ESMTP id E8E023A6849
	for <sip@ietf.org>; Mon, 27 Oct 2008 14:14:07 -0700 (PDT)
Received: by taimen.tutpro.com (Postfix, from userid 1000)
	id 1FCF133A679; Mon, 27 Oct 2008 23:14:11 +0200 (EET)
MIME-Version: 1.0
Message-ID: <18694.12066.980412.507913@harjus.tutpro.com>
Date: Mon, 27 Oct 2008 23:14:10 +0200
To: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
In-Reply-To: <200810272114.40331.ibc@aliax.net>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
	<18693.28129.618794.915466@harjus.tutpro.com>
	<200810272114.40331.ibc@aliax.net>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR
	Identity	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I=F1aki Baz Castillo writes:

 > It's basically the same, but devices that already support Dialog
 > event support  =

 > (as servers) already implement this draft "Dialog Event foR Identity =

 > VErification" while using a new custom request/response would require
 > devices supporting it as a new feature.

i did my proposal before presence was invented and it is still way
simpler, less messages, and lower delay.

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


From sip-bounces@ietf.org  Mon Oct 27 14:25:25 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 252AF3A6A66;
	Mon, 27 Oct 2008 14:25:25 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B7AF63A69E7
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 14:25:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gYuw0VdiTqBx for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 14:25:20 -0700 (PDT)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28])
	by core3.amsl.com (Postfix) with ESMTP id 372F63A6A69
	for <sip@ietf.org>; Mon, 27 Oct 2008 14:25:18 -0700 (PDT)
Received: by yw-out-2324.google.com with SMTP id 3so592507ywj.49
	for <sip@ietf.org>; Mon, 27 Oct 2008 14:25:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=Ap3wrTnc0H9b30Sgs5O/B0pJ+VOn5z2erHxfJ3rDoyA=;
	b=F8N4pqDUxWplj6Tu+sJkj1WztgY1N6kE+lyKzjbbkb3VitVTLFuhJ6CSFQ6OaJLVuN
	niSCxn2quSzfuTKKlhOCw1T5Uj/iM5cVpx1OlqgvH1xjzj0xENuvwVji1eGqOc0Fx9F3
	YR6n5E/CvTbgYUrWGLdGXPAP2VsPx2x0lTVrI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=rBy/E+tUuysMX/3xcZ4FNsdThIsr4mH2gd4rhpk1gNaZdtKmkrUUQltYtmhNsXf8zv
	gxYz/en/jW71zREDG6VOlkBiELWkDWedv8b/GBq4kJJQghmp+JFr57PGHdrAcxULE0EC
	XSgHyAZEL7yJdWY5fqfNuL9IkUj1ISpdR8fJM=
Received: by 10.90.33.15 with SMTP id g15mr5162094agg.0.1225142717399;
	Mon, 27 Oct 2008 14:25:17 -0700 (PDT)
Received: by 10.90.114.2 with HTTP; Mon, 27 Oct 2008 14:25:17 -0700 (PDT)
Message-ID: <618e24240810271425h2b6290b4o830a4b8c6849580a@mail.gmail.com>
Date: Mon, 27 Oct 2008 22:25:17 +0100
From: "=?UTF-8?Q?Victor_Pascual_=C3=81vila?=" <victor.pascual.avila@gmail.com>
To: "Juha Heinanen" <jh@tutpro.com>
In-Reply-To: <18694.12066.980412.507913@harjus.tutpro.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
	<18693.28129.618794.915466@harjus.tutpro.com>
	<200810272114.40331.ibc@aliax.net>
	<18694.12066.980412.507913@harjus.tutpro.com>
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR Identity
	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

T24gTW9uLCBPY3QgMjcsIDIwMDggYXQgMTA6MTQgUE0sIEp1aGEgSGVpbmFuZW4gPGpoQHR1dHBy
by5jb20+IHdyb3RlOgo+IGkgZGlkIG15IHByb3Bvc2FsIGJlZm9yZSBwcmVzZW5jZSB3YXMgaW52
ZW50ZWQgYW5kIGl0IGlzIHN0aWxsIHdheQo+IHNpbXBsZXIsIGxlc3MgbWVzc2FnZXMsIGFuZCBs
b3dlciBkZWxheS4KCkknZCByZWFsbHkgYXBwcmVjaWF0ZSBpZiB5b3UgY291bGQgc2hhcmUgaXQg
d2l0aCB1cy4KLS0gClZpY3RvciBQYXNjdWFsIMOBdmlsYQpfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXwpTaXAgbWFpbGluZyBsaXN0ICBodHRwczovL3d3dy5p
ZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpcApUaGlzIGxpc3QgaXMgZm9yIE5FVyBkZXZlbG9w
bWVudCBvZiB0aGUgY29yZSBTSVAgUHJvdG9jb2wKVXNlIHNpcC1pbXBsZW1lbnRvcnNAY3MuY29s
dW1iaWEuZWR1IGZvciBxdWVzdGlvbnMgb24gY3VycmVudCBzaXAKVXNlIHNpcHBpbmdAaWV0Zi5v
cmcgZm9yIG5ldyBkZXZlbG9wbWVudHMgb24gdGhlIGFwcGxpY2F0aW9uIG9mIHNpcA==


From sip-bounces@ietf.org  Mon Oct 27 14:27:03 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E499D3A6BCF;
	Mon, 27 Oct 2008 14:27:03 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A05FE3A6A69
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 14:27:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id oEV5PZWWTSOV for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 14:27:01 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id ACEE53A6B90
	for <sip@ietf.org>; Mon, 27 Oct 2008 14:27:01 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,494,1220227200"; d="scan'208";a="25816731"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 27 Oct 2008 21:27:00 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9RLR0Is003065; 
	Mon, 27 Oct 2008 17:27:00 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9RLR0ap013333;
	Mon, 27 Oct 2008 21:27:00 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 17:27:00 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Oct 2008 17:27:00 -0400
Message-ID: <49063223.90006@cisco.com>
Date: Mon, 27 Oct 2008 17:26:59 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <5D1A7985295922448D5550C94DE2918002426290@DEEXC1U01.de.lucent.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F907@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F907@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 27 Oct 2008 21:27:00.0070 (UTC)
	FILETIME=[BF235860:01C9387A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=754; t=1225142820; x=1226006820;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Draft-ietf-sip-info-events-00=3
	A=20Other=20messages=20for=09Send-Infoand=0A=20Recv-Info
	|Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=poCx6oc9e1UZaRXmIcUDysNQeRPXjrnni2sucXc7/io=;
	b=DavBMCiIrRF9VupfowxRVOgNCzBsjFkAbqqxkQsz6J1WYAiA3v8PoR6mfH
	VlTrmwTpuvbNg8mW4bUrXLUHS8xb6c8Uv8oELGfOwqm59ABVOoUgKCipydFL
	eQrqhPjqA0;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>
Subject: Re: [Sip] Draft-ietf-sip-info-events-00: Other messages
 for	Send-Infoand Recv-Info
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Christer Holmberg wrote:

> Yes, maybe we need to define a feature tag, or feature tags. The
> question is whether we would need a single feature tag which can list
> all supported info packages, or a feature tag for each package (in which
> case each info package definition would have to specify a feature tag
> value). The advantage of having separate feature tags is that it gives
> you much more flexibility.

The decision about that depends on what kinds of selection you want to 
be able to make using callerprefs. (If anybody uses callerprefs to make 
selections.)

If you make it a single feature with a list of values then it becomes 
impossible to select a particular Contact based on which packages it 
supports.

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


From sip-bounces@ietf.org  Mon Oct 27 14:48:30 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E409D3A67EE;
	Mon, 27 Oct 2008 14:48:30 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D5BD03A67EE
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 14:48:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id NKOqjY9Nn6SD for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 14:48:29 -0700 (PDT)
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187])
	by core3.amsl.com (Postfix) with ESMTP id E7F4E3A67D4
	for <sip@ietf.org>; Mon, 27 Oct 2008 14:48:27 -0700 (PDT)
Received: by nf-out-0910.google.com with SMTP id b11so834361nfh.39
	for <sip@ietf.org>; Mon, 27 Oct 2008 14:48:23 -0700 (PDT)
Received: by 10.210.81.3 with SMTP id e3mr2712677ebb.112.1225144103532;
	Mon, 27 Oct 2008 14:48:23 -0700 (PDT)
Received: from portatil.local (240.pool85-58-8.dynamic.orange.es [85.58.8.240])
	by mx.google.com with ESMTPS id b30sm416728ika.3.2008.10.27.14.48.21
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Mon, 27 Oct 2008 14:48:22 -0700 (PDT)
From: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
To: sip@ietf.org
Date: Mon, 27 Oct 2008 22:48:18 +0100
User-Agent: KMail/1.9.9
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<200810272114.40331.ibc@aliax.net>
	<18694.12066.980412.507913@harjus.tutpro.com>
In-Reply-To: <18694.12066.980412.507913@harjus.tutpro.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810272248.19014.ibc@aliax.net>
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR Identity
	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

El Lunes, 27 de Octubre de 2008, Juha Heinanen escribi=F3:
> I=F1aki Baz Castillo writes:
>  > It's basically the same, but devices that already support Dialog
>  > event support
>  > (as servers) already implement this draft "Dialog Event foR Identity
>  > VErification" while using a new custom request/response would require
>  > devices supporting it as a new feature.
>
> i did my proposal before presence was invented and it is still way
> simpler, less messages, and lower delay.

Your suggestion is:

> - my phone receives a call from sip:foo@bar
> - my phone sends a query to sip:foo@bar asking if foo@bar is trying to
>   call me

Ok, but which is that request and response?



-- =

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


From sip-bounces@ietf.org  Mon Oct 27 18:58:18 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 20FC73A694A;
	Mon, 27 Oct 2008 18:58:18 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 74DE23A693F
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 18:58:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5
	tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5G5KY9t1DDGS for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 18:58:16 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 6C2FB3A694A
	for <sip@ietf.org>; Mon, 27 Oct 2008 18:58:16 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,495,1220227200"; d="scan'208";a="183720876"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 28 Oct 2008 01:58:14 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9S1wF8g001203; 
	Mon, 27 Oct 2008 18:58:15 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9S1wFlZ027616;
	Tue, 28 Oct 2008 01:58:15 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Dean Willis'" <dean.willis@softarmor.com>,
	"=?iso-8859-1?Q?'I=F1aki_Baz_Castillo'?=" <ibc@aliax.net>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com><D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com><200810261145.19745.ibc@aliax.net>
	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
Date: Mon, 27 Oct 2008 18:58:14 -0700
Message-ID: <084c01c938a0$a41ff390$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
Thread-Index: Ack4AsTSF5EsTKnLSMWpaV9GFs5YrQAnUMWw
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1407; t=1225159096;
	x=1226023096; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[Sip]=20submission=20of=20a=20new=20I-D
	=3A=20=22Dialog=20Event=20foR=20IdentityVErification=22
	|Sender:=20; bh=TGGSvjzRvUK7bHP1fbV+Lz00zbv1nrKTY9yK6n9rrNE=;
	b=zSCF1rocV1LAXllU1lrcB02T3Ti21ANGI/HVKU3ZmO0T99eRSt+ltDPn75
	UjcAm9IMKuLUeDOMezYCF/kzTKXO45RixtHBbRPeJC0Bc7KbhB0U3LLAclhy
	ZORhM+BLjo;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR
	IdentityVErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 =


> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On =

> Behalf Of Dean Willis
> Sent: Monday, October 27, 2008 12:08 AM
> To: I=F1aki Baz Castillo
> Cc: sip@ietf.org
> Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR =

> IdentityVErification"
> =

> =

> On Oct 26, 2008, at 5:45 AM, I=F1aki Baz Castillo wrote:
> =

> > El Domingo, 26 de Octubre de 2008, Dean Willis escribi=F3:
> >>> A new I-D, draft-kuthan-sip-derive-00, was just submitted. Your
> >>> comments are always welcome.
> >>
> >> Sounds like you have reinvented identd, which has pretty much  =

> >> vanished
> >> from the Internet because it was found to not really add any useful
> >> authentication.
> >
> > draft-kuthan-sip-derive-00 proposal is 100% SIP based instead of  =

> > depending on
> > other protocols. IMHO it has *nothing* to do with Identd mechanism.
> >
> =

> But it is very much LIKE the ident mechanism, in that, in =

> response to  =

> a connection attempt, the connected party does a reverse-to-host  =

> connection to ask "Is this from you, and which user is it from"?
> =

> You've just implemented a complicated version of a =

> return-routability check.

Here is another return routability check,
http://tools.ietf.org/html/draft-wing-sip-e164-rrc-01#section-3.1
(My I-D expired due to lack of interest.)

-d

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


From sip-bounces@ietf.org  Mon Oct 27 23:08:58 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 78B563A6BA1;
	Mon, 27 Oct 2008 23:08:58 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2A00F3A67B4
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 23:08:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.374
X-Spam-Level: 
X-Spam-Status: No, score=-2.374 tagged_above=-999 required=5
	tests=[AWL=-0.075, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id VN1uh8RZBHLl for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 23:08:56 -0700 (PDT)
Received: from taimen.tutpro.com (harjus.tutpro.com [192.98.100.3])
	by core3.amsl.com (Postfix) with ESMTP id 577B03A6B96
	for <sip@ietf.org>; Mon, 27 Oct 2008 23:08:55 -0700 (PDT)
Received: by taimen.tutpro.com (Postfix, from userid 1000)
	id 6596833A679; Tue, 28 Oct 2008 08:08:52 +0200 (EET)
MIME-Version: 1.0
Message-ID: <18694.44148.327220.629364@harjus.tutpro.com>
Date: Tue, 28 Oct 2008 08:08:52 +0200
To: "=?UTF-8?Q?Victor_Pascual_=C3=81vila?=" <victor.pascual.avila@gmail.com>
In-Reply-To: <618e24240810271425h2b6290b4o830a4b8c6849580a@mail.gmail.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
	<18693.28129.618794.915466@harjus.tutpro.com>
	<200810272114.40331.ibc@aliax.net>
	<18694.12066.980412.507913@harjus.tutpro.com>
	<618e24240810271425h2b6290b4o830a4b8c6849580a@mail.gmail.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR Identity
	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Victor Pascual =C1vila writes:

 > I'd really appreciate if you could share it with us.

i don't remember the details.  the idea was very simple:

- UAS receives a call from sip:foo@bar

- UAS sends a query (INFO, OPTIONS, whatever) to sip:foo@bar and
  includes in it relevant info about the request (call-id, from uri,
  from tag, date, to uri, ...)

- when sip:foo@bar UA receives the query, it replies with 200 ok if this
  UA is currently making the call in question

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


From sip-bounces@ietf.org  Mon Oct 27 23:11:32 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7274D3A6979;
	Mon, 27 Oct 2008 23:11:32 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 45D1B3A6979
	for <sip@core3.amsl.com>; Mon, 27 Oct 2008 23:11:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.363
X-Spam-Level: 
X-Spam-Status: No, score=-2.363 tagged_above=-999 required=5
	tests=[AWL=-0.064, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id t2k-SyFge0Dq for <sip@core3.amsl.com>;
	Mon, 27 Oct 2008 23:11:30 -0700 (PDT)
Received: from taimen.tutpro.com (harjus.tutpro.com [192.98.100.3])
	by core3.amsl.com (Postfix) with ESMTP id 746193A67B4
	for <sip@ietf.org>; Mon, 27 Oct 2008 23:11:30 -0700 (PDT)
Received: by taimen.tutpro.com (Postfix, from userid 1000)
	id 7F28933A679; Tue, 28 Oct 2008 08:11:29 +0200 (EET)
MIME-Version: 1.0
Message-ID: <18694.44305.477491.261118@harjus.tutpro.com>
Date: Tue, 28 Oct 2008 08:11:29 +0200
To: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
In-Reply-To: <200810272248.19014.ibc@aliax.net>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<200810272114.40331.ibc@aliax.net>
	<18694.12066.980412.507913@harjus.tutpro.com>
	<200810272248.19014.ibc@aliax.net>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR
	Identity	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I=F1aki Baz Castillo writes:

 > Ok, but which is that request and response?

i don't care, whatever ietf had decided on, e.g. options, info, or
something new.  if you implement presence based version of this, UAs
need to be changed anyhow. probably you need to make changes also in
presence server in order to cope with privacy issues, i.e., who is
allowed to subscribe dialog state.

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


From sip-bounces@ietf.org  Tue Oct 28 02:49:23 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3AF1C3A67F5;
	Tue, 28 Oct 2008 02:49:23 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1DC9B3A67AF
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 02:49:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[AWL=1.300, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1bcBAJkTA38j for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 02:49:21 -0700 (PDT)
Received: from mail-gx0-f18.google.com (mail-gx0-f18.google.com
	[209.85.217.18])
	by core3.amsl.com (Postfix) with ESMTP id 2FB0A3A67F5
	for <sip@ietf.org>; Tue, 28 Oct 2008 02:49:21 -0700 (PDT)
Received: by gxk11 with SMTP id 11so1239872gxk.13
	for <sip@ietf.org>; Tue, 28 Oct 2008 02:49:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=YpMPw0xmANUxFj4hqCJRwFFkyusM4Tqg+XfGO/3IUhM=;
	b=FasEHE6KPxgP0SWjXTd8Y9aaQUXl9Au4/1lK3y/+aM/0tcw1h3vJ0YqhsLmdsbXfya
	9M2nx3sVzecKylUXYe+NS+SfyplffZ0LoYuLA2+z01gEPrgWEhl7z2eBsdJSNTFVBc/9
	NOKU0LTPT+mF88NMkStoBSu2GIXAtm7hn+rfw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=P3axfhFcR2p3Se7iRS8FX8Aawg3LRnN/Yxk9BqI4ALEY96oMgNEFL19ilh2i2JiF4n
	XMkZSURen4SAlYgSD+YmdnwEYLlYiUES9vUugfwR7JAYLC8qpmw1DZWPBE9GRi2sreus
	7WOYhOXeFFgXe34pSgxMPoT+HBp/t7CHwhCx0=
Received: by 10.90.101.7 with SMTP id y7mr5847032agb.44.1225187359224;
	Tue, 28 Oct 2008 02:49:19 -0700 (PDT)
Received: by 10.90.114.2 with HTTP; Tue, 28 Oct 2008 02:49:19 -0700 (PDT)
Message-ID: <618e24240810280249h135256b1n746dec9cab51d053@mail.gmail.com>
Date: Tue, 28 Oct 2008 10:49:19 +0100
From: "=?UTF-8?Q?Victor_Pascual_=C3=81vila?=" <victor.pascual.avila@gmail.com>
To: "Juha Heinanen" <jh@tutpro.com>
In-Reply-To: <18694.44148.327220.629364@harjus.tutpro.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
	<18693.28129.618794.915466@harjus.tutpro.com>
	<200810272114.40331.ibc@aliax.net>
	<18694.12066.980412.507913@harjus.tutpro.com>
	<618e24240810271425h2b6290b4o830a4b8c6849580a@mail.gmail.com>
	<18694.44148.327220.629364@harjus.tutpro.com>
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR Identity
	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

SGkgSnVoYSwKY29tbWVudHMgaW5saW5lLgoKT24gVHVlLCBPY3QgMjgsIDIwMDggYXQgNzowOCBB
TSwgSnVoYSBIZWluYW5lbiA8amhAdHV0cHJvLmNvbT4gd3JvdGU6Cj4gVmljdG9yIFBhc2N1YWwg
w4F2aWxhIHdyaXRlczoKPgo+ICA+IEknZCByZWFsbHkgYXBwcmVjaWF0ZSBpZiB5b3UgY291bGQg
c2hhcmUgaXQgd2l0aCB1cy4KPgo+IGkgZG9uJ3QgcmVtZW1iZXIgdGhlIGRldGFpbHMuICB0aGUg
aWRlYSB3YXMgdmVyeSBzaW1wbGU6Cj4KPiAtIFVBUyByZWNlaXZlcyBhIGNhbGwgZnJvbSBzaXA6
Zm9vQGJhcgo+Cj4gLSBVQVMgc2VuZHMgYSBxdWVyeSAoSU5GTywgT1BUSU9OUywgd2hhdGV2ZXIp
IHRvIHNpcDpmb29AYmFyIGFuZAo+ICBpbmNsdWRlcyBpbiBpdCByZWxldmFudCBpbmZvIGFib3V0
IHRoZSByZXF1ZXN0IChjYWxsLWlkLCBmcm9tIHVyaSwKPiAgZnJvbSB0YWcsIGRhdGUsIHRvIHVy
aSwgLi4uKQoKSW4gZGVyaXZlLCB0aGlzIHF1ZXJ5IGlzIGEgU1VCU0NSSUJFIHJlcXVlc3QKCj4g
LSB3aGVuIHNpcDpmb29AYmFyIFVBIHJlY2VpdmVzIHRoZSBxdWVyeSwgaXQgcmVwbGllcyB3aXRo
IDIwMCBvayBpZiB0aGlzCj4gIFVBIGlzIGN1cnJlbnRseSBtYWtpbmcgdGhlIGNhbGwgaW4gcXVl
c3Rpb24KCkEgMjAwIHJlc3BvbnNlIHRvIHRoZSBzdWJzY3JpcHRpb24gaW5kaWNhdGVzIHRoZSBD
YWxsZXIncyBhd2FyZW5lc3Mgb2YKdGhlIGRpYWxvZwpiZWluZyBtb25pdG9yZWQgYnkgdGhlIENh
bGxlZS4gT3RoZXJ3aXNlICh3aGVuIHRoZSBDYWxsZXIgaXMgbm90IGF3YXJlCm9mIHRoZSBzdWJz
Y3JpYmVkIGRpYWxvZykgdGhpcyBzdWJzY3JpcHRpb24gd29uJ3QgYmUgYWNjZXB0ZWQuCgpPbiBN
b24sIE9jdCAyNywgMjAwOCBhdCAxMDoxNCBQTSwgSnVoYSBIZWluYW5lbiA8amhAdHV0cHJvLmNv
bT4gd3JvdGU6Cj4gaSBkaWQgbXkgcHJvcG9zYWwgYmVmb3JlIHByZXNlbmNlIHdhcyBpbnZlbnRl
ZCBhbmQgaXQgaXMgc3RpbGwgd2F5Cj4gc2ltcGxlciwgbGVzcyBtZXNzYWdlcywgYW5kIGxvd2Vy
IGRlbGF5LgoKQ29uY2VybmluZyB0byB0aGUgImxvd2VyIGRlbGF5Iiwgd2VyZSB5b3UgdXNpbmcg
YW55IHRpbWVyIG90aGVyIHRoYW4KVGltZXIgRiAoNjQqVDEpPwoKClRoYW5rcyBmb3IgeW91ciBj
b21tZW50cywKLS0gClZpY3RvciBQYXNjdWFsIMOBdmlsYQpfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXwpTaXAgbWFpbGluZyBsaXN0ICBodHRwczovL3d3dy5p
ZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpcApUaGlzIGxpc3QgaXMgZm9yIE5FVyBkZXZlbG9w
bWVudCBvZiB0aGUgY29yZSBTSVAgUHJvdG9jb2wKVXNlIHNpcC1pbXBsZW1lbnRvcnNAY3MuY29s
dW1iaWEuZWR1IGZvciBxdWVzdGlvbnMgb24gY3VycmVudCBzaXAKVXNlIHNpcHBpbmdAaWV0Zi5v
cmcgZm9yIG5ldyBkZXZlbG9wbWVudHMgb24gdGhlIGFwcGxpY2F0aW9uIG9mIHNpcA==


From sip-bounces@ietf.org  Tue Oct 28 02:55:39 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 723223A69FC;
	Tue, 28 Oct 2008 02:55:39 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D0B3B3A69FC
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 02:55:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.355
X-Spam-Level: 
X-Spam-Status: No, score=-2.355 tagged_above=-999 required=5
	tests=[AWL=-0.056, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id p+n9x+b96jOI for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 02:55:37 -0700 (PDT)
Received: from taimen.tutpro.com (harjus.tutpro.com [192.98.100.3])
	by core3.amsl.com (Postfix) with ESMTP id 12F353A694A
	for <sip@ietf.org>; Tue, 28 Oct 2008 02:55:36 -0700 (PDT)
Received: by taimen.tutpro.com (Postfix, from userid 1000)
	id A24AC33ABB3; Tue, 28 Oct 2008 11:55:33 +0200 (EET)
MIME-Version: 1.0
Message-ID: <18694.57749.609275.78711@harjus.tutpro.com>
Date: Tue, 28 Oct 2008 11:55:33 +0200
To: "=?UTF-8?Q?Victor_Pascual_=C3=81vila?=" <victor.pascual.avila@gmail.com>
In-Reply-To: <618e24240810280249h135256b1n746dec9cab51d053@mail.gmail.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
	<18693.28129.618794.915466@harjus.tutpro.com>
	<200810272114.40331.ibc@aliax.net>
	<18694.12066.980412.507913@harjus.tutpro.com>
	<618e24240810271425h2b6290b4o830a4b8c6849580a@mail.gmail.com>
	<18694.44148.327220.629364@harjus.tutpro.com>
	<618e24240810280249h135256b1n746dec9cab51d053@mail.gmail.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR Identity
	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Victor Pascual =C1vila writes:

 > Concerning to the "lower delay", were you using any timer other than
 > Timer F (64*T1)?

no, i'm just comparing the number of messages that each cause some
delay. =


in case of a presence based solution, caller needs to publish its
dialog, not just send an invite, which means more messages.

when presence server receives subscribe from callee, it needs to make
xcap query, before it can reply, which in again means more delay.

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


From sip-bounces@ietf.org  Tue Oct 28 03:06:48 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 50CE23A6835;
	Tue, 28 Oct 2008 03:06:48 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9C7AF3A687D
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 03:06:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level: 
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[AWL=0.650, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6SwPwdREDnha for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 03:06:47 -0700 (PDT)
Received: from mail-gx0-f18.google.com (mail-gx0-f18.google.com
	[209.85.217.18])
	by core3.amsl.com (Postfix) with ESMTP id CB9073A6835
	for <sip@ietf.org>; Tue, 28 Oct 2008 03:06:46 -0700 (PDT)
Received: by gxk11 with SMTP id 11so1252453gxk.13
	for <sip@ietf.org>; Tue, 28 Oct 2008 03:06:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=4Q6wLF16FKyaJpMIqyPm+qyvZAtFOjO9sX3T2/oS+xY=;
	b=f/F6mG8KlJGrKqEEklaZk8oNbnVdob+cVVlDvK/IIsmbDQO1JnPHUZWnHZwEVotcTN
	8yoXONl+tXBXtslyGBREYP6J9GD9smmBL14SUBfOCryBF1RBbecHk+CFBFH9vbgOVxoQ
	pYLGL22G5NPNgg9FUM67OGeoLj1DFvxfQH+1g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=j1peD3CckaPJdm0nuobeujXGfmK0bESdqBaezujLb36njxXBTGjlmYr8cvgz2+qGwW
	GDxhlFYy6862eTmrLobrP91RtFdAubbdVci1g7luix21nbfPmyFkFZ1ygPa0MxjJe4FQ
	/hBkwxaB5VNO0tpbAFrBC7Z1fe4If2RModfgE=
Received: by 10.90.106.4 with SMTP id e4mr5859675agc.29.1225188405173;
	Tue, 28 Oct 2008 03:06:45 -0700 (PDT)
Received: by 10.90.114.2 with HTTP; Tue, 28 Oct 2008 03:06:45 -0700 (PDT)
Message-ID: <618e24240810280306l2e27a76ag417ad59c8362efc9@mail.gmail.com>
Date: Tue, 28 Oct 2008 11:06:45 +0100
From: "=?UTF-8?Q?Victor_Pascual_=C3=81vila?=" <victor.pascual.avila@gmail.com>
To: "Juha Heinanen" <jh@tutpro.com>
In-Reply-To: <18694.57749.609275.78711@harjus.tutpro.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
	<18693.28129.618794.915466@harjus.tutpro.com>
	<200810272114.40331.ibc@aliax.net>
	<18694.12066.980412.507913@harjus.tutpro.com>
	<618e24240810271425h2b6290b4o830a4b8c6849580a@mail.gmail.com>
	<18694.44148.327220.629364@harjus.tutpro.com>
	<618e24240810280249h135256b1n746dec9cab51d053@mail.gmail.com>
	<18694.57749.609275.78711@harjus.tutpro.com>
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR Identity
	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

T24gVHVlLCBPY3QgMjgsIDIwMDggYXQgMTA6NTUgQU0sIEp1aGEgSGVpbmFuZW4gPGpoQHR1dHBy
by5jb20+IHdyb3RlOgo+IFZpY3RvciBQYXNjdWFsIMOBdmlsYSB3cml0ZXM6Cj4KPiAgPiBDb25j
ZXJuaW5nIHRvIHRoZSAibG93ZXIgZGVsYXkiLCB3ZXJlIHlvdSB1c2luZyBhbnkgdGltZXIgb3Ro
ZXIgdGhhbgo+ICA+IFRpbWVyIEYgKDY0KlQxKT8KPgo+IG5vLCBpJ20ganVzdCBjb21wYXJpbmcg
dGhlIG51bWJlciBvZiBtZXNzYWdlcyB0aGF0IGVhY2ggY2F1c2Ugc29tZQo+IGRlbGF5Lgo+Cj4g
aW4gY2FzZSBvZiBhIHByZXNlbmNlIGJhc2VkIHNvbHV0aW9uLCBjYWxsZXIgbmVlZHMgdG8gcHVi
bGlzaCBpdHMKPiBkaWFsb2csIG5vdCBqdXN0IHNlbmQgYW4gaW52aXRlLCB3aGljaCBtZWFucyBt
b3JlIG1lc3NhZ2VzLgo+Cj4gd2hlbiBwcmVzZW5jZSBzZXJ2ZXIgcmVjZWl2ZXMgc3Vic2NyaWJl
IGZyb20gY2FsbGVlLCBpdCBuZWVkcyB0byBtYWtlCj4geGNhcCBxdWVyeSwgYmVmb3JlIGl0IGNh
biByZXBseSwgd2hpY2ggaW4gYWdhaW4gbWVhbnMgbW9yZSBkZWxheS4KCkknbSBhZnJhaWQgdGhh
dCB5b3UgYXJlIGFzc3VtaW5nIHRoYXQgYSBwcmVzZW5jZSBzZXJ2ZXIgaXMgdXNlZC4KRGVyaXZl
IGlzIGFuIF9lbmQtdG8tZW5kIG1lY2hhbmlzbV8gaW1wbGVtZW50ZWQgaW4gdGhlIFVBcy4KCkNo
ZWVycywKLS0gClZpY3RvciBQYXNjdWFsIMOBdmlsYQpfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXwpTaXAgbWFpbGluZyBsaXN0ICBodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpcApUaGlzIGxpc3QgaXMgZm9yIE5FVyBkZXZlbG9wbWVu
dCBvZiB0aGUgY29yZSBTSVAgUHJvdG9jb2wKVXNlIHNpcC1pbXBsZW1lbnRvcnNAY3MuY29sdW1i
aWEuZWR1IGZvciBxdWVzdGlvbnMgb24gY3VycmVudCBzaXAKVXNlIHNpcHBpbmdAaWV0Zi5vcmcg
Zm9yIG5ldyBkZXZlbG9wbWVudHMgb24gdGhlIGFwcGxpY2F0aW9uIG9mIHNpcA==


From sip-bounces@ietf.org  Tue Oct 28 04:03:25 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2CC843A694A;
	Tue, 28 Oct 2008 04:03:25 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0AB7A3A694A
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 04:03:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.866
X-Spam-Level: 
X-Spam-Status: No, score=-1.866 tagged_above=-999 required=5 tests=[AWL=0.433, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id wffi91xxp1iI for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 04:03:23 -0700 (PDT)
Received: from mail-gx0-f18.google.com (mail-gx0-f18.google.com
	[209.85.217.18])
	by core3.amsl.com (Postfix) with ESMTP id DF6FB3A68D5
	for <sip@ietf.org>; Tue, 28 Oct 2008 04:03:22 -0700 (PDT)
Received: by gxk11 with SMTP id 11so1295111gxk.13
	for <sip@ietf.org>; Tue, 28 Oct 2008 04:03:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:mime-version:content-type:content-transfer-encoding
	:content-disposition;
	bh=S8f8S0RMQnE6WtRZMJSU8APL+bsl2DIAvNgbotiZAlA=;
	b=w7ONQR3IGFhs47Cbnfyd5RtcyURedtgrsV5Fw5VBPbcpq0quJwKjeJnQ6cbK+RMnd2
	zzXdetuoAfFdjplHyMJVZRP5whM3P7MiWVMrAenAAXQt8IbwYNnaQYgmwGmCOO5E9kuq
	dl+MovUbpaYxw8ysVsPhuwiSbGE1xWNe0S1bQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:mime-version:content-type
	:content-transfer-encoding:content-disposition;
	b=uaOtEvgAa3Ai4yJyKLluof8lxc6nLiI2/MFRn1ZXkhs1pLJ/5NoM8fFBi+81h1pa+D
	opQogz0xHv5I1V3vRrcRrCnbi4AxWVg/JAJVKn1Q1w+przOKFB7pvLLSGPEJcY+OJGsy
	0uUxP2FZtrw/b+10/JHvBwWijzMnc0yJ4EB6Q=
Received: by 10.90.87.7 with SMTP id k7mr4764616agb.85.1225191801026;
	Tue, 28 Oct 2008 04:03:21 -0700 (PDT)
Received: by 10.90.114.2 with HTTP; Tue, 28 Oct 2008 04:03:20 -0700 (PDT)
Message-ID: <618e24240810280403q3523f2d6raf2aa403602fbf4f@mail.gmail.com>
Date: Tue, 28 Oct 2008 12:03:20 +0100
From: "=?UTF-8?Q?Victor_Pascual_=C3=81vila?=" <victor.pascual.avila@gmail.com>
To: "SIP IETF" <sip@ietf.org>
MIME-Version: 1.0
Content-Disposition: inline
Subject: [Sip] TEL URIs in SUBSCRIBE requests
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

SGksIGFzIGRpc2N1c3NlZCBpbiBzaXAtaW1wbGVtZW50b3JzWzFdIGl0IHNlZW1zIHRoYXQgdGhl
IHVzZSBvZiBURUwKVVJJcyBpbiBTVUJTQ1JJQkUgcmVxdWVzdHMgaXMgbm90IGNvbnNpZGVyZWQg
aW4gUkZDIDM4NTYuCgpSRkMgMzg1NiwgU2VjdGlvbiA1CiJTVUJTQ1JJQkUgbWVzc2FnZXMgYWxz
byBjb250YWluIGxvZ2ljYWwgaWRlbnRpZmllcnMgdGhhdCBkZWZpbmUgdGhlCm9yaWdpbmF0b3Ig
YW5kIHJlY2lwaWVudCBvZiB0aGUgc3Vic2NyaXB0aW9uICh0aGUgVG8gYW5kIEZyb20gaGVhZGVy
CmZpZWxkcykuIFRoZXNlIGhlYWRlcnMgY2FuIHRha2UgZWl0aGVyIGEgcHJlcyBvciBTSVAgVVJJ
LiIKCklNTyBpdCBzaG91bGQgYmUgcGVybWl0dGVkIHNpbmNlIGEgU1VCU0NSSUJFIHJlcXVlc3Qg
d291bGQgYmUgcm91dGVkCnRoZSBzYW1lIHdheSBhbiBJTlZJVEUgcmVxdWVzdCB3b3VsZC4KCgpb
MV0gaHR0cHM6Ly9saXN0cy5jcy5jb2x1bWJpYS5lZHUvcGlwZXJtYWlsL3NpcC1pbXBsZW1lbnRv
cnMvMjAwOC1PY3RvYmVyLzAyMDc0NC5odG1sCgpJJ2QgYXBwcmVjaWF0ZSBhbnkgY2xhcmlmaWNh
dGlvbiB5b3UgY2FuIGdpdmUgb24gdGhpcywKLS0gClZpY3RvciBQYXNjdWFsIMOBdmlsYQpfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpTaXAgbWFpbGluZyBs
aXN0ICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpcApUaGlzIGxpc3Qg
aXMgZm9yIE5FVyBkZXZlbG9wbWVudCBvZiB0aGUgY29yZSBTSVAgUHJvdG9jb2wKVXNlIHNpcC1p
bXBsZW1lbnRvcnNAY3MuY29sdW1iaWEuZWR1IGZvciBxdWVzdGlvbnMgb24gY3VycmVudCBzaXAK
VXNlIHNpcHBpbmdAaWV0Zi5vcmcgZm9yIG5ldyBkZXZlbG9wbWVudHMgb24gdGhlIGFwcGxpY2F0
aW9uIG9mIHNpcA==


From sip-bounces@ietf.org  Tue Oct 28 04:39:51 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DED933A6946;
	Tue, 28 Oct 2008 04:39:51 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9560E3A6896
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 04:39:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.385
X-Spam-Level: 
X-Spam-Status: No, score=-0.385 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3,
	MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jdbCMYYH0gSi for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 04:39:45 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232])
	by core3.amsl.com (Postfix) with ESMTP id 52F683A6946
	for <sip@ietf.org>; Tue, 28 Oct 2008 04:39:45 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so2531476rvf.49
	for <sip@ietf.org>; Tue, 28 Oct 2008 04:39:44 -0700 (PDT)
Received: by 10.141.68.5 with SMTP id v5mr4090100rvk.179.1225193984373;
	Tue, 28 Oct 2008 04:39:44 -0700 (PDT)
Received: by 10.141.41.1 with HTTP; Tue, 28 Oct 2008 04:39:44 -0700 (PDT)
Message-ID: <cc1f582e0810280439q792bc5f9he2a84225013e90e8@mail.gmail.com>
Date: Tue, 28 Oct 2008 12:39:44 +0100
From: "=?UTF-8?Q?I=C3=B1aki_Baz_Castillo?=" <ibc@aliax.net>
Cc: sip@ietf.org
In-Reply-To: <18694.57749.609275.78711@harjus.tutpro.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
	<18693.28129.618794.915466@harjus.tutpro.com>
	<200810272114.40331.ibc@aliax.net>
	<18694.12066.980412.507913@harjus.tutpro.com>
	<618e24240810271425h2b6290b4o830a4b8c6849580a@mail.gmail.com>
	<18694.44148.327220.629364@harjus.tutpro.com>
	<618e24240810280249h135256b1n746dec9cab51d053@mail.gmail.com>
	<18694.57749.609275.78711@harjus.tutpro.com>
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR Identity
	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

MjAwOC8xMC8yOCBKdWhhIEhlaW5hbmVuIDxqaEB0dXRwcm8uY29tPjoKCj4gaW4gY2FzZSBvZiBh
IHByZXNlbmNlIGJhc2VkIHNvbHV0aW9uLCBjYWxsZXIgbmVlZHMgdG8gcHVibGlzaCBpdHMKPiBk
aWFsb2csIG5vdCBqdXN0IHNlbmQgYW4gaW52aXRlLCB3aGljaCBtZWFucyBtb3JlIG1lc3NhZ2Vz
LgoKVGhhdCdzIG5vdCB0cnVlLgotIEEgY2FsbHMgQgotIElubWVkaWF0ZWxseSBCIHNlbmRzIGEg
U1VCU0NSSUJFIChFdmVudDoKZGlhbG9nO2NhbGwtaWQ9eHh4O3RvLXRhZz14eHgpIHRvIEEgQW9S
ICh3aGljaCBjb3VsZCBmb3JrKS4KLSBUaGUgQSBjb250YWN0IGluIHRoaXMgZGlhbG9nIHdpbGwg
cmVwbHkgMjAwIE9LIGZvciB0aGUgU1VCU0NSSUJFLgotIEIgYWxyZWFkeSBub3dzIHRoYXQgdGhl
IHNlbmRlciBpcyB2ZXJpZmllZCBhbmQgc2VuZHMgdGhlIDE4MCBSaW5naWcKZm9yIHRoZSBJTlZJ
VEUuLi4KLSBBIGFsc28gc2VuZHMgYSBOT1RJRlkgYXMgaXMgbWFuZGF0b3J5IGZvciBwcmVzZW5j
ZSAoYnV0IHRoaXMgaXMgbm90CmltcG9ydGFudCBhbmQgQSBkb2Vzbid0IHJlcXVpcmUgdG8gcmVj
ZWl2ZSBpdCkuCgpObyBQVUJMSVNIIGlzIG5lZWRlZC4gUFVCTElTSCBhcHBlYXJzIHdoZW4gc3Vi
c2NyaWJpbmcgdG8gYW4gQW9SIGNhbGxzCndpdGhvdXQgc3BlY2lmeW5nICJjYWxsLWlkIiBhbmQg
InRvLXRhZyIgcGFyYW1ldGVycy4KClBsZWFzZSwgcmV2aWV3IHRoZSBkcmFmdCBmbG93cyA7KQoK
CgotLSAKScOxYWtpIEJheiBDYXN0aWxsbwo8aWJjQGFsaWF4Lm5ldD4KX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KU2lwIG1haWxpbmcgbGlzdCAgaHR0cHM6
Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zaXAKVGhpcyBsaXN0IGlzIGZvciBORVcg
ZGV2ZWxvcG1lbnQgb2YgdGhlIGNvcmUgU0lQIFByb3RvY29sClVzZSBzaXAtaW1wbGVtZW50b3Jz
QGNzLmNvbHVtYmlhLmVkdSBmb3IgcXVlc3Rpb25zIG9uIGN1cnJlbnQgc2lwClVzZSBzaXBwaW5n
QGlldGYub3JnIGZvciBuZXcgZGV2ZWxvcG1lbnRzIG9uIHRoZSBhcHBsaWNhdGlvbiBvZiBzaXA=


From sip-bounces@ietf.org  Tue Oct 28 04:41:30 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2F2F93A6ABD;
	Tue, 28 Oct 2008 04:41:30 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C08523A6C03
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 04:41:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.385
X-Spam-Level: 
X-Spam-Status: No, score=-0.385 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3,
	MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QhEDZM1Q2HFE for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 04:41:28 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.238])
	by core3.amsl.com (Postfix) with ESMTP id 1402A3A6956
	for <sip@ietf.org>; Tue, 28 Oct 2008 04:41:28 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so2532224rvf.49
	for <sip@ietf.org>; Tue, 28 Oct 2008 04:41:26 -0700 (PDT)
Received: by 10.141.161.6 with SMTP id n6mr4104078rvo.41.1225194086386;
	Tue, 28 Oct 2008 04:41:26 -0700 (PDT)
Received: by 10.141.41.1 with HTTP; Tue, 28 Oct 2008 04:41:26 -0700 (PDT)
Message-ID: <cc1f582e0810280441p20fa51c7tf80b1da313a78d5a@mail.gmail.com>
Date: Tue, 28 Oct 2008 12:41:26 +0100
From: "=?UTF-8?Q?I=C3=B1aki_Baz_Castillo?=" <ibc@aliax.net>
Cc: sip@ietf.org
In-Reply-To: <18694.44305.477491.261118@harjus.tutpro.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<200810272114.40331.ibc@aliax.net>
	<18694.12066.980412.507913@harjus.tutpro.com>
	<200810272248.19014.ibc@aliax.net>
	<18694.44305.477491.261118@harjus.tutpro.com>
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR Identity
	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

MjAwOC8xMC8yOCBKdWhhIEhlaW5hbmVuIDxqaEB0dXRwcm8uY29tPjoKPiBJw7Fha2kgQmF6IENh
c3RpbGxvIHdyaXRlczoKPgo+ICA+IE9rLCBidXQgd2hpY2ggaXMgdGhhdCByZXF1ZXN0IGFuZCBy
ZXNwb25zZT8KPgo+IGkgZG9uJ3QgY2FyZSwgd2hhdGV2ZXIgaWV0ZiBoYWQgZGVjaWRlZCBvbiwg
ZS5nLiBvcHRpb25zLCBpbmZvLCBvcgo+IHNvbWV0aGluZyBuZXcuCgo+IGlmIHlvdSBpbXBsZW1l
bnQgcHJlc2VuY2UgYmFzZWQgdmVyc2lvbiBvZiB0aGlzLCBVQXMKPiBuZWVkIHRvIGJlIGNoYW5n
ZWQgYW55aG93LgoKV2h5PyBhIFVBIHN1cHBvcnRpbmcgRGlhbG9nIEV2ZW50IHBhY2thZ2UgKGFz
IGEgc2VydmVyKSBhbHJlYXlzIGFsbG93cwp0aGUgbWVjaGFuaW1zIGRlZmluZWQgaW4gdGhpcyBk
cmFmdC4KCgo+IHByb2JhYmx5IHlvdSBuZWVkIHRvIG1ha2UgY2hhbmdlcyBhbHNvIGluCj4gcHJl
c2VuY2Ugc2VydmVyIGluIG9yZGVyIHRvIGNvcGUgd2l0aCBwcml2YWN5IGlzc3VlcywgaS5lLiwg
d2hvIGlzCj4gYWxsb3dlZCB0byBzdWJzY3JpYmUgZGlhbG9nIHN0YXRlLgoKVGhlIHNhbWUgd291
bGQgYmUgcmVxdWllcmVkIGlmIHlvdSBzZW5kIGFueSBvdGhlciByZXF1ZXN0IHR5cGUsIHdvdWxk
bid0IGl0PwoKUmVnYXJkcy4KCgotLSAKScOxYWtpIEJheiBDYXN0aWxsbwo8aWJjQGFsaWF4Lm5l
dD4KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KU2lwIG1h
aWxpbmcgbGlzdCAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zaXAKVGhp
cyBsaXN0IGlzIGZvciBORVcgZGV2ZWxvcG1lbnQgb2YgdGhlIGNvcmUgU0lQIFByb3RvY29sClVz
ZSBzaXAtaW1wbGVtZW50b3JzQGNzLmNvbHVtYmlhLmVkdSBmb3IgcXVlc3Rpb25zIG9uIGN1cnJl
bnQgc2lwClVzZSBzaXBwaW5nQGlldGYub3JnIGZvciBuZXcgZGV2ZWxvcG1lbnRzIG9uIHRoZSBh
cHBsaWNhdGlvbiBvZiBzaXA=


From sip-bounces@ietf.org  Tue Oct 28 04:44:29 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BAAAD3A6C18;
	Tue, 28 Oct 2008 04:44:29 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3E5F93A6C09
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 04:44:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.385
X-Spam-Level: 
X-Spam-Status: No, score=-0.385 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3,
	MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id E9TZj3hz2PFv for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 04:44:23 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.227])
	by core3.amsl.com (Postfix) with ESMTP id F32883A694A
	for <sip@ietf.org>; Tue, 28 Oct 2008 04:44:22 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so2533467rvf.49
	for <sip@ietf.org>; Tue, 28 Oct 2008 04:44:17 -0700 (PDT)
Received: by 10.140.202.21 with SMTP id z21mr4099840rvf.81.1225194257835;
	Tue, 28 Oct 2008 04:44:17 -0700 (PDT)
Received: by 10.141.41.1 with HTTP; Tue, 28 Oct 2008 04:44:17 -0700 (PDT)
Message-ID: <cc1f582e0810280444y42b8f723w938004e902fb1180@mail.gmail.com>
Date: Tue, 28 Oct 2008 12:44:17 +0100
From: "=?UTF-8?Q?I=C3=B1aki_Baz_Castillo?=" <ibc@aliax.net>
Cc: sip@ietf.org
In-Reply-To: <084c01c938a0$a41ff390$c3f0200a@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>
	<200810261145.19745.ibc@aliax.net>
	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
	<084c01c938a0$a41ff390$c3f0200a@cisco.com>
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR
	IdentityVErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

MjAwOC8xMC8yOCBEYW4gV2luZyA8ZHdpbmdAY2lzY28uY29tPjoKPiBIZXJlIGlzIGFub3RoZXIg
cmV0dXJuIHJvdXRhYmlsaXR5IGNoZWNrLAo+IGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2Ry
YWZ0LXdpbmctc2lwLWUxNjQtcnJjLTAxI3NlY3Rpb24tMy4xCj4gKE15IEktRCBleHBpcmVkIGR1
ZSB0byBsYWNrIG9mIGludGVyZXN0LikKCkl0IHVzZXMgUkZDIDQ0NzQsIGNlcnRpZmljYXRlcy4u
LiBpcyBpdCByZWFsbHkgZmVhc2libGUgaW4gdGhpcyByZWFsIHdvcmxkPwoKSU1ITyAiRGlhbG9n
IEV2ZW50IGZvUiBJZGVudGl0eSBWRXJpZmljYXRpb24iIGlzIHRoZSBtb3JlIGZlYXNpYmxlCnNv
bHV0aW9uIGF0IHRoZSBtb21lbnQuCgoKLS0gCknDsWFraSBCYXogQ2FzdGlsbG8KPGliY0BhbGlh
eC5uZXQ+Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClNp
cCBtYWlsaW5nIGxpc3QgIGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2lw
ClRoaXMgbGlzdCBpcyBmb3IgTkVXIGRldmVsb3BtZW50IG9mIHRoZSBjb3JlIFNJUCBQcm90b2Nv
bApVc2Ugc2lwLWltcGxlbWVudG9yc0Bjcy5jb2x1bWJpYS5lZHUgZm9yIHF1ZXN0aW9ucyBvbiBj
dXJyZW50IHNpcApVc2Ugc2lwcGluZ0BpZXRmLm9yZyBmb3IgbmV3IGRldmVsb3BtZW50cyBvbiB0
aGUgYXBwbGljYXRpb24gb2Ygc2lw


From sip-bounces@ietf.org  Tue Oct 28 05:54:33 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 30E5E28C1E8;
	Tue, 28 Oct 2008 05:54:33 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 37DFA28C1E8
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 05:54:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5
	tests=[AWL=-0.050, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id PF8wqcEmFPXG for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 05:54:28 -0700 (PDT)
Received: from taimen.tutpro.com (harjus.tutpro.com [192.98.100.3])
	by core3.amsl.com (Postfix) with ESMTP id 68BBA28C155
	for <sip@ietf.org>; Tue, 28 Oct 2008 05:54:27 -0700 (PDT)
Received: by taimen.tutpro.com (Postfix, from userid 1000)
	id 9F40533ABB3; Tue, 28 Oct 2008 14:54:26 +0200 (EET)
MIME-Version: 1.0
Message-ID: <18695.2946.519788.917581@harjus.tutpro.com>
Date: Tue, 28 Oct 2008 14:54:26 +0200
To: "=?UTF-8?Q?Victor_Pascual_=C3=81vila?=" <victor.pascual.avila@gmail.com>
In-Reply-To: <618e24240810280306l2e27a76ag417ad59c8362efc9@mail.gmail.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
	<18693.28129.618794.915466@harjus.tutpro.com>
	<200810272114.40331.ibc@aliax.net>
	<18694.12066.980412.507913@harjus.tutpro.com>
	<618e24240810271425h2b6290b4o830a4b8c6849580a@mail.gmail.com>
	<18694.44148.327220.629364@harjus.tutpro.com>
	<618e24240810280249h135256b1n746dec9cab51d053@mail.gmail.com>
	<18694.57749.609275.78711@harjus.tutpro.com>
	<618e24240810280306l2e27a76ag417ad59c8362efc9@mail.gmail.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR Identity
	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Victor Pascual =C1vila writes:

 > I'm afraid that you are assuming that a presence server is used.
 > Derive is an _end-to-end mechanism_ implemented in the UAs.

if i have configured my proxy to use presence server for local users,
how does subscribe reach the UA?

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


From sip-bounces@ietf.org  Tue Oct 28 06:02:09 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4C0963A6979;
	Tue, 28 Oct 2008 06:02:09 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CA2CC3A6979
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 06:02:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.344
X-Spam-Level: 
X-Spam-Status: No, score=-2.344 tagged_above=-999 required=5
	tests=[AWL=-0.045, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id idNUhMaYl3iY for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 06:02:03 -0700 (PDT)
Received: from taimen.tutpro.com (harjus.tutpro.com [192.98.100.3])
	by core3.amsl.com (Postfix) with ESMTP id 613F43A6827
	for <sip@ietf.org>; Tue, 28 Oct 2008 06:02:03 -0700 (PDT)
Received: by taimen.tutpro.com (Postfix, from userid 1000)
	id 7565F33ABB3; Tue, 28 Oct 2008 15:02:03 +0200 (EET)
MIME-Version: 1.0
Message-ID: <18695.3403.264395.73585@harjus.tutpro.com>
Date: Tue, 28 Oct 2008 15:02:03 +0200
To: "=?UTF-8?Q?I=C3=B1aki_Baz_Castillo?=" <ibc@aliax.net>
In-Reply-To: <cc1f582e0810280439q792bc5f9he2a84225013e90e8@mail.gmail.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
	<18693.28129.618794.915466@harjus.tutpro.com>
	<200810272114.40331.ibc@aliax.net>
	<18694.12066.980412.507913@harjus.tutpro.com>
	<618e24240810271425h2b6290b4o830a4b8c6849580a@mail.gmail.com>
	<18694.44148.327220.629364@harjus.tutpro.com>
	<618e24240810280249h135256b1n746dec9cab51d053@mail.gmail.com>
	<18694.57749.609275.78711@harjus.tutpro.com>
	<cc1f582e0810280439q792bc5f9he2a84225013e90e8@mail.gmail.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR
	Identity	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I=F1aki Baz Castillo writes:

 > - Inmediatelly B sends a SUBSCRIBE (Event:
 > dialog;call-id=3Dxxx;to-tag=3Dxxx) to A AoR (which could fork).

as i replied earlier, normally my proxy is configured to use presence
server for subscribes.  are you suggesting that i would need to
configure it somehow to make an exception on these subscribes?  if so,
how do they differ from normal ones where presence server is used?

other than that, i'm ok with the proposal.

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


From sip-bounces@ietf.org  Tue Oct 28 06:23:30 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 61D3A28C223;
	Tue, 28 Oct 2008 06:23:30 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B6A7728C223
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 06:23:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.385
X-Spam-Level: 
X-Spam-Status: No, score=-0.385 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3,
	MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UvHmBxhGuTdN for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 06:23:29 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.227])
	by core3.amsl.com (Postfix) with ESMTP id 0C0F628C132
	for <sip@ietf.org>; Tue, 28 Oct 2008 06:23:28 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id k40so2708632rvb.1
	for <sip@ietf.org>; Tue, 28 Oct 2008 06:23:27 -0700 (PDT)
Received: by 10.140.201.21 with SMTP id y21mr4132559rvf.259.1225200207654;
	Tue, 28 Oct 2008 06:23:27 -0700 (PDT)
Received: by 10.141.41.1 with HTTP; Tue, 28 Oct 2008 06:23:27 -0700 (PDT)
Message-ID: <cc1f582e0810280623i1f19c767s2aae6de19ec03d1c@mail.gmail.com>
Date: Tue, 28 Oct 2008 14:23:27 +0100
From: "=?UTF-8?Q?I=C3=B1aki_Baz_Castillo?=" <ibc@aliax.net>
Cc: sip@ietf.org
In-Reply-To: <18695.3403.264395.73585@harjus.tutpro.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<18693.28129.618794.915466@harjus.tutpro.com>
	<200810272114.40331.ibc@aliax.net>
	<18694.12066.980412.507913@harjus.tutpro.com>
	<618e24240810271425h2b6290b4o830a4b8c6849580a@mail.gmail.com>
	<18694.44148.327220.629364@harjus.tutpro.com>
	<618e24240810280249h135256b1n746dec9cab51d053@mail.gmail.com>
	<18694.57749.609275.78711@harjus.tutpro.com>
	<cc1f582e0810280439q792bc5f9he2a84225013e90e8@mail.gmail.com>
	<18695.3403.264395.73585@harjus.tutpro.com>
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR Identity
	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

MjAwOC8xMC8yOCBKdWhhIEhlaW5hbmVuIDxqaEB0dXRwcm8uY29tPjoKPiBJw7Fha2kgQmF6IENh
c3RpbGxvIHdyaXRlczoKPgo+ICA+IC0gSW5tZWRpYXRlbGx5IEIgc2VuZHMgYSBTVUJTQ1JJQkUg
KEV2ZW50Ogo+ICA+IGRpYWxvZztjYWxsLWlkPXh4eDt0by10YWc9eHh4KSB0byBBIEFvUiAod2hp
Y2ggY291bGQgZm9yaykuCj4KPiBhcyBpIHJlcGxpZWQgZWFybGllciwgbm9ybWFsbHkgbXkgcHJv
eHkgaXMgY29uZmlndXJlZCB0byB1c2UgcHJlc2VuY2UKPiBzZXJ2ZXIgZm9yIHN1YnNjcmliZXMu
CgpGb3IgYm90aCBTSU1QTEUgYW5kIERpYWxvZyBwcmVzZW5jZT8KCgo+IGFyZSB5b3Ugc3VnZ2Vz
dGluZyB0aGF0IGkgd291bGQgbmVlZCB0bwo+IGNvbmZpZ3VyZSBpdCBzb21laG93IHRvIG1ha2Ug
YW4gZXhjZXB0aW9uIG9uIHRoZXNlIHN1YnNjcmliZXM/CgpOb3QgbmVlZGVkIGF0IGFsbC4gSWYg
eW91IGFyZSB1c2luZyBhIEV2ZW50IERpYWxvZyBwcmVzZW5jZSBhZ2VudAooaS5lOiBwdWFfZGlh
bG9naW5mbykgeW91IGRvbid0IG5lZWQgZm9yd2FyZGluZyBTVUJTQ1JJQkUgKEV2ZW50OgpkaWFs
b2cpIHRvIFVBUy4KCgo+IGlmIHNvLAo+IGhvdyBkbyB0aGV5IGRpZmZlciBmcm9tIG5vcm1hbCBv
bmVzIHdoZXJlIHByZXNlbmNlIHNlcnZlciBpcyB1c2VkPwoKSXQgZGVwZW5kcyBvbiB5b3VyIGVu
dmlyb25tZW50LiBJZiB5b3UgdXNlIERpYWxnbyBwcmVzZW5jZSBpbXBsZW1lbnRlZAppbiB0aGUg
cHJveHkgdGhlbiB5b3UgbmVlZCBhIHByZXNlbmNlIGFnZW50ICh3aG8gc2VuZHMgdGhlIE5PVElG
WSB0bwpzdWJzY3JpYmVycyBhYm91dCBjYWxscyBmcm9tL3RvIGFuIEFvUikuIEFsc28geW91IGhh
dmUgYSBwcmVzZW5jZQpzZXJ2ZXIgdGhhdCB3aWxsIHJlY2VpdmUgdGhlIFNVQlNDUklCRSAoRXZl
bnQ6IGRpYWxvZykuCllvdSBjb3VsZCB1c2UgdGhpcyBzY2VuYXJpbyB3aXRoIHRoZSBjdXJyZW50
IGRyYWZ0LiBKdXN0IG9uZSBpbXBvcnRhbnQgaXNzdWU6CgpJIHN1cHBvc2UgeW91IGRvbid0IGFs
bG93IGFueW9uZSBzdWJzY3JpYmluZyB0byBjYWxscyBzdGF0dXMgb2YgYW55CmxvY2FsIHVzZXJz
LCBidXQgaW4gdGhlIGNhc2Ugb2YgdGhpcyBkcmFmdCB5b3Ugc2hvdWxkIGFsbG93IGFueQpTVUJT
Q1JJQkUgd2l0aDoKCiAgRXZlbnQ6IGRpYWxvZztjYWxsLWlkPXh4eHg7dG8tdGFnPXh4eHgKICBF
eHBpcmVzOiAwCgpOb3RlIHRoaXMgc3Vic2NyaXB0aW9uIG9ubHkgaW52b2x2ZXMgYW4gc3BlY2lm
aWMgZGlhbG9nLiBJZiBCIGtub3dzCnRoZXNlIGRpYWxvZyBwYXJhbWV0ZXJzIGl0IG1lYW5zIHRo
YXQgaGUgaXMgdGhlIHJlY2VwdG9yIGFuZCBoZSBpcwp0cnlpbmcgdG8gdmVyaWZ5IHRoZSBzZW5k
ZXIgQW9SIChGcm9tKS4gSW4gdGhpcyBjYXNlIHlvdXIgcHJlc2VuY2UKc2VydmVyIHNob3VsZCBh
bGxvdyB0aGF0IFNVQlNDUklCRSAob3IgeW91ciBwcm94eSBzaG91bGQgYWxsb3cgdGhhdApTVUJT
Q1JJQkUgYmVpbmcgZm9yd2FyZGVkIHRvIFVBUyBpZiB5b3UgZG9uJ3QgdXNlIGEgZGlhbG9nIHBy
ZXNlbmNlCnNlcnZlcikuCgoKCgoKCi0tIApJw7Fha2kgQmF6IENhc3RpbGxvCjxpYmNAYWxpYXgu
bmV0PgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpTaXAg
bWFpbGluZyBsaXN0ICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpcApU
aGlzIGxpc3QgaXMgZm9yIE5FVyBkZXZlbG9wbWVudCBvZiB0aGUgY29yZSBTSVAgUHJvdG9jb2wK
VXNlIHNpcC1pbXBsZW1lbnRvcnNAY3MuY29sdW1iaWEuZWR1IGZvciBxdWVzdGlvbnMgb24gY3Vy
cmVudCBzaXAKVXNlIHNpcHBpbmdAaWV0Zi5vcmcgZm9yIG5ldyBkZXZlbG9wbWVudHMgb24gdGhl
IGFwcGxpY2F0aW9uIG9mIHNpcA==


From sip-bounces@ietf.org  Tue Oct 28 06:25:25 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4261E28C277;
	Tue, 28 Oct 2008 06:25:25 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 15C2428C27A
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 06:25:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.385
X-Spam-Level: 
X-Spam-Status: No, score=-0.385 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3,
	MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LDQSeM0bkqYF for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 06:25:07 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.226])
	by core3.amsl.com (Postfix) with ESMTP id 6ADE928C274
	for <sip@ietf.org>; Tue, 28 Oct 2008 06:25:05 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id g9so3221807rvb.3
	for <sip@ietf.org>; Tue, 28 Oct 2008 06:25:04 -0700 (PDT)
Received: by 10.140.249.20 with SMTP id w20mr4152905rvh.103.1225200304643;
	Tue, 28 Oct 2008 06:25:04 -0700 (PDT)
Received: by 10.141.41.1 with HTTP; Tue, 28 Oct 2008 06:25:04 -0700 (PDT)
Message-ID: <cc1f582e0810280625p1c18982bkb6faad2fba3b1b95@mail.gmail.com>
Date: Tue, 28 Oct 2008 14:25:04 +0100
From: "=?UTF-8?Q?I=C3=B1aki_Baz_Castillo?=" <ibc@aliax.net>
Cc: sip@ietf.org
In-Reply-To: <18695.2946.519788.917581@harjus.tutpro.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<18693.28129.618794.915466@harjus.tutpro.com>
	<200810272114.40331.ibc@aliax.net>
	<18694.12066.980412.507913@harjus.tutpro.com>
	<618e24240810271425h2b6290b4o830a4b8c6849580a@mail.gmail.com>
	<18694.44148.327220.629364@harjus.tutpro.com>
	<618e24240810280249h135256b1n746dec9cab51d053@mail.gmail.com>
	<18694.57749.609275.78711@harjus.tutpro.com>
	<618e24240810280306l2e27a76ag417ad59c8362efc9@mail.gmail.com>
	<18695.2946.519788.917581@harjus.tutpro.com>
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR Identity
	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

MjAwOC8xMC8yOCBKdWhhIEhlaW5hbmVuIDxqaEB0dXRwcm8uY29tPjoKPiBWaWN0b3IgUGFzY3Vh
bCDDgXZpbGEgd3JpdGVzOgo+Cj4gID4gSSdtIGFmcmFpZCB0aGF0IHlvdSBhcmUgYXNzdW1pbmcg
dGhhdCBhIHByZXNlbmNlIHNlcnZlciBpcyB1c2VkLgo+ICA+IERlcml2ZSBpcyBhbiBfZW5kLXRv
LWVuZCBtZWNoYW5pc21fIGltcGxlbWVudGVkIGluIHRoZSBVQXMuCj4KPiBpZiBpIGhhdmUgY29u
ZmlndXJlZCBteSBwcm94eSB0byB1c2UgcHJlc2VuY2Ugc2VydmVyIGZvciBsb2NhbCB1c2VycywK
PiBob3cgZG9lcyBzdWJzY3JpYmUgcmVhY2ggdGhlIFVBPwoKSWYgeW91IHByb3h5IGluY2x1ZGVz
IGEgZGlhbG9nIHByZXNlbmNlIHNlcnZlciwgdGhlbiB0aGUgU1VCU0NSSUJFCmRvZXNuJ3QgbmVl
ZCB0byByZWFjaCB0aGUgVUEgc2luY2UgeW91ciBwcm94eSBhbHJlYWR5IGhhcyB0aGUKaW5mb3Jt
YXRpb24gYWJvdXQgZGlhbG9ncyBvZiB0aGF0IFVBLgoKCi0tIApJw7Fha2kgQmF6IENhc3RpbGxv
CjxpYmNAYWxpYXgubmV0PgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXwpTaXAgbWFpbGluZyBsaXN0ICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL3NpcApUaGlzIGxpc3QgaXMgZm9yIE5FVyBkZXZlbG9wbWVudCBvZiB0aGUgY29yZSBT
SVAgUHJvdG9jb2wKVXNlIHNpcC1pbXBsZW1lbnRvcnNAY3MuY29sdW1iaWEuZWR1IGZvciBxdWVz
dGlvbnMgb24gY3VycmVudCBzaXAKVXNlIHNpcHBpbmdAaWV0Zi5vcmcgZm9yIG5ldyBkZXZlbG9w
bWVudHMgb24gdGhlIGFwcGxpY2F0aW9uIG9mIHNpcA==


From sip-bounces@ietf.org  Tue Oct 28 07:38:25 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8FE1A3A6C35;
	Tue, 28 Oct 2008 07:38:25 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2D7EC28C2B9
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 07:34:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.509
X-Spam-Level: 
X-Spam-Status: No, score=-1.509 tagged_above=-999 required=5 tests=[AWL=1.091, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id SQUrRfBF5Xps for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 07:34:29 -0700 (PDT)
Received: from web50701.mail.re2.yahoo.com (web50701.mail.re2.yahoo.com
	[206.190.38.99]) by core3.amsl.com (Postfix) with SMTP id 1DD9528C2AF
	for <sip@ietf.org>; Tue, 28 Oct 2008 07:34:29 -0700 (PDT)
Received: (qmail 1045 invoked by uid 60001); 28 Oct 2008 14:34:28 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Message-ID;
	b=K7vBsXA22MI5X4PgMDCnktDKkzkWppflWvwM6WgbWWyf668WqiiXpkCij8yrWitm+9hZHwI7oeLEHnsFqEloYOAt7Iy/ve+LzdFkKVyK6XTac1rEomOGpvj22RhUFFf1ex74bPilGJN6mLv5GBLpFaxv8GFGxBmkp39lGN9hv58=;
X-YMail-OSG: hLZF_BkVM1k27u5JS9ezF1no6zB9S8e2b4XaNThLj3B7CbIWHalyFFrsi4tCBTUQjyYw0Ah2zOf7nVJD.I7IDBicNytu1h5wFql4s9rDpH14eUIgwlr_U_R.fSDVzicLGoi2Q_qpZzBHcOPv1RrBPsAG8iPtvx9oFC1CvmU-
Received: from [139.85.236.92] by web50701.mail.re2.yahoo.com via HTTP;
	Tue, 28 Oct 2008 07:34:28 PDT
X-Mailer: YahooMailWebService/0.7.247.3
Date: Tue, 28 Oct 2008 07:34:28 -0700 (PDT)
From: Zakaria Gaguk <gaguk_el80@yahoo.com>
To: sip@ietf.org
MIME-Version: 1.0
Message-ID: <358180.676.qm@web50701.mail.re2.yahoo.com>
Subject: [Sip] Non-default SIP port
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: gaguk_el80@yahoo.com
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi
I just joined this mailing list so I am not sure if my following questions have been posted.
1. is there any "danger" if a sip UA agent registers with port other than that 5060 (default) port, for example 5062 or any other unassigned ports? 
2. In this case SIP messages for any incoming call to thsi UA will have the UDP destination port defiend as 5062. Is this a correct understanding?
3. General question: when a UA register, is it alwasy assumed that this is only for VoIP?

Thanks
Gaguk


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


From sip-bounces@ietf.org  Tue Oct 28 08:01:52 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D00B928C2AF;
	Tue, 28 Oct 2008 08:01:52 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F2E6628C268
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 08:01:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.34
X-Spam-Level: 
X-Spam-Status: No, score=-2.34 tagged_above=-999 required=5 tests=[AWL=-0.041, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nz+JwiFFQhaS for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 08:01:51 -0700 (PDT)
Received: from taimen.tutpro.com (harjus.tutpro.com [192.98.100.3])
	by core3.amsl.com (Postfix) with ESMTP id E27B93A6C51
	for <sip@ietf.org>; Tue, 28 Oct 2008 08:00:43 -0700 (PDT)
Received: by taimen.tutpro.com (Postfix, from userid 1000)
	id 44FE633ABB3; Tue, 28 Oct 2008 16:46:00 +0200 (EET)
MIME-Version: 1.0
Message-ID: <18695.9640.142118.959882@harjus.tutpro.com>
Date: Tue, 28 Oct 2008 16:46:00 +0200
To: "=?UTF-8?Q?I=C3=B1aki_Baz_Castillo?=" <ibc@aliax.net>
In-Reply-To: <cc1f582e0810280625p1c18982bkb6faad2fba3b1b95@mail.gmail.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<18693.28129.618794.915466@harjus.tutpro.com>
	<200810272114.40331.ibc@aliax.net>
	<18694.12066.980412.507913@harjus.tutpro.com>
	<618e24240810271425h2b6290b4o830a4b8c6849580a@mail.gmail.com>
	<18694.44148.327220.629364@harjus.tutpro.com>
	<618e24240810280249h135256b1n746dec9cab51d053@mail.gmail.com>
	<18694.57749.609275.78711@harjus.tutpro.com>
	<618e24240810280306l2e27a76ag417ad59c8362efc9@mail.gmail.com>
	<18695.2946.519788.917581@harjus.tutpro.com>
	<cc1f582e0810280625p1c18982bkb6faad2fba3b1b95@mail.gmail.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR
	Identity	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I=F1aki Baz Castillo writes:

 > >  > I'm afraid that you are assuming that a presence server is used.
 > >  > Derive is an _end-to-end mechanism_ implemented in the UAs.
 > >
 > > if i have configured my proxy to use presence server for local users,
 > > how does subscribe reach the UA?
 > =

 > If you proxy includes a dialog presence server, then the SUBSCRIBE
 > doesn't need to reach the UA since your proxy already has the
 > information about dialogs of that UA.

inaki,

now i'm confused again.  in above, you say that this is a UA thing,  now
you seem to indicate, that proxy needs to keep track of the dialogs.
so far i'm not convinced that proxy can reliable keep track of dialogs.

in openser/kamailio environment, for example, keeping track of dialogs
is implemented using dialog module, which has the history of being the
most buggies module of all.  perhaps that is due to the difficulty of
the problem, i.e., proxy is made to do something it is not really
intended for.

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


From sip-bounces@ietf.org  Tue Oct 28 08:11:16 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 224353A6C59;
	Tue, 28 Oct 2008 08:11:16 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 607693A6C4D
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 08:11:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.385
X-Spam-Level: 
X-Spam-Status: No, score=-0.385 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3,
	MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nF6U0jSDUTVA for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 08:11:13 -0700 (PDT)
Received: from po-out-1718.google.com (po-out-1718.google.com [72.14.252.156])
	by core3.amsl.com (Postfix) with ESMTP id 79E103A6C2B
	for <sip@ietf.org>; Tue, 28 Oct 2008 08:11:13 -0700 (PDT)
Received: by po-out-1718.google.com with SMTP id c31so4217003poi.4
	for <sip@ietf.org>; Tue, 28 Oct 2008 08:11:11 -0700 (PDT)
Received: by 10.140.164.1 with SMTP id m1mr4204861rve.266.1225206670920;
	Tue, 28 Oct 2008 08:11:10 -0700 (PDT)
Received: by 10.141.41.1 with HTTP; Tue, 28 Oct 2008 08:11:10 -0700 (PDT)
Message-ID: <cc1f582e0810280811h7e1bbea9mbb63c390808e3bff@mail.gmail.com>
Date: Tue, 28 Oct 2008 16:11:10 +0100
From: "=?UTF-8?Q?I=C3=B1aki_Baz_Castillo?=" <ibc@aliax.net>
Cc: sip@ietf.org
In-Reply-To: <18695.9640.142118.959882@harjus.tutpro.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<18694.12066.980412.507913@harjus.tutpro.com>
	<618e24240810271425h2b6290b4o830a4b8c6849580a@mail.gmail.com>
	<18694.44148.327220.629364@harjus.tutpro.com>
	<618e24240810280249h135256b1n746dec9cab51d053@mail.gmail.com>
	<18694.57749.609275.78711@harjus.tutpro.com>
	<618e24240810280306l2e27a76ag417ad59c8362efc9@mail.gmail.com>
	<18695.2946.519788.917581@harjus.tutpro.com>
	<cc1f582e0810280625p1c18982bkb6faad2fba3b1b95@mail.gmail.com>
	<18695.9640.142118.959882@harjus.tutpro.com>
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR Identity
	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

MjAwOC8xMC8yOCBKdWhhIEhlaW5hbmVuIDxqaEB0dXRwcm8uY29tPjoKPiBJw7Fha2kgQmF6IENh
c3RpbGxvIHdyaXRlczoKPgo+ICA+ID4gID4gSSdtIGFmcmFpZCB0aGF0IHlvdSBhcmUgYXNzdW1p
bmcgdGhhdCBhIHByZXNlbmNlIHNlcnZlciBpcyB1c2VkLgo+ICA+ID4gID4gRGVyaXZlIGlzIGFu
IF9lbmQtdG8tZW5kIG1lY2hhbmlzbV8gaW1wbGVtZW50ZWQgaW4gdGhlIFVBcy4KPiAgPiA+Cj4g
ID4gPiBpZiBpIGhhdmUgY29uZmlndXJlZCBteSBwcm94eSB0byB1c2UgcHJlc2VuY2Ugc2VydmVy
IGZvciBsb2NhbCB1c2VycywKPiAgPiA+IGhvdyBkb2VzIHN1YnNjcmliZSByZWFjaCB0aGUgVUE/
Cj4gID4KPiAgPiBJZiB5b3UgcHJveHkgaW5jbHVkZXMgYSBkaWFsb2cgcHJlc2VuY2Ugc2VydmVy
LCB0aGVuIHRoZSBTVUJTQ1JJQkUKPiAgPiBkb2Vzbid0IG5lZWQgdG8gcmVhY2ggdGhlIFVBIHNp
bmNlIHlvdXIgcHJveHkgYWxyZWFkeSBoYXMgdGhlCj4gID4gaW5mb3JtYXRpb24gYWJvdXQgZGlh
bG9ncyBvZiB0aGF0IFVBLgo+Cj4gaW5ha2ksCj4KPiBub3cgaSdtIGNvbmZ1c2VkIGFnYWluLiAg
aW4gYWJvdmUsIHlvdSBzYXkgdGhhdCB0aGlzIGlzIGEgVUEgdGhpbmcsICBub3cKPiB5b3Ugc2Vl
bSB0byBpbmRpY2F0ZSwgdGhhdCBwcm94eSBuZWVkcyB0byBrZWVwIHRyYWNrIG9mIHRoZSBkaWFs
b2dzLgo+IHNvIGZhciBpJ20gbm90IGNvbnZpbmNlZCB0aGF0IHByb3h5IGNhbiByZWxpYWJsZSBr
ZWVwIHRyYWNrIG9mIGRpYWxvZ3MuCgpUaGVyZSBhcmUgdHdvIHBvc3NpYmlsaXRpZXM6CgoxKSBU
aGUgU1VCU0NSSUJFIGFycml2ZXMgdG8gdGhlIFVBIGxvY2F0aW9uLgotIEEgY2FsbHMgQi4KLSBC
IHNlbmRzIGEgU1VCU0NSSUJFIChFdmVudDogZGlhbG9nO2FjbGwtaWQ9eHg7dG8tdGFnPXh4KSB0
byBBIEFvUi4KLSBUaGUgcHJveHkgcmVzcG9uc2libGUgZm9yIEEgcmVjZWl2ZXMgdGhlIFNVQlND
UklCRSBhbmQgZm9yd2FyZHMgaXQKdG8gQSBsb2NhdGlvbihzKS4gTm90ZSB0aGF0IHRoZSBwcm94
eSBhbGxvd3MgdGhpcyBTVUJTQ1JJQkUgc2luY2UgdGhlCiJFdmVudCIgaGVhZGVyIGlzICJkaWFs
b2ciIGNvbnRhaW5pbmcgImNhbGwtaWQiIGFuZCAidG8tdGFnIi4gSXQgY291bGQKYWxzbyBjaGVj
ayBpZiB0aGUgIkV4cGlyZXMiIGVxdWFscyAwLiBTbyB0aGlzIGlzIG5vdCBhIFNVQlNDUklCRSAi
Zm9yCmFsbCB0aGUgY2FsbHMgZnJvbS90byBBIiwgYnV0IGEgU1VCU0NSSUJFIGZvciBhbiBzcGVk
aWZpYyBkaWFsb2cuCi0gQiByZWNlaXZlcyB0aGUgU1VCU0NSSUJFIGFuZCBzaW5jZSBCIGltcGxl
bWVudHMgUkZDIDQyMzUgKHJlY2VpdmluZwp0aGUgU1VCU0NSSUJFLCBub3QganVzdCBwdWJsaXNo
aW5nKSBpdCBjaGVja3MgaWYgdGhhdCBkaWFsb2cgZXhpc3RzLgpJZiBpdCwgQiByZXBsaWVzIDIw
MCBhbmQgc2VuZHMgYSBOT1RJRlkgKG1hbmRhdG9yeSkuCi0gQSByZWNlaXZlcyB0aGUgMjAwIHNv
IGhhcyB2ZXJpZmllZCB0aGUgc2VuZGVyIGlkZW50aXR5LgotIEIgc3RhcnQgcmluZ2luZyBhbmQg
c28uLi4KCjIpIFRoZSBTVUJTQ1JJQkUgaXMgaGFuZGxlZCBieSBhIHByb3h5IC8gcHJlc2VuY2Ug
c2VydmVyLgotIEEgY2FsbHMgQiB0aHJvdWdoIFAxIChwcm94eSByZXNwb25zaWJsZSBmb3IgQSku
Ci0gUDEgaW5jbHVkZXMgYSBkaWFsb2cgcHJlc2VuY2UgYWdlbnQgKGFzIHB1YV9kaWFsb2dpbmZv
KS4gVGhpcyBhZ2VudApnZW5lcmF0ZXMgYSBQVUJMSVNIIHRoYXQgaXMgc2VudCB0byB0aGUgaW50
ZWdyYXRlZCAob3Igc2VwYXJhdGUpCmRpYWxvZyBwcmVzZW5jZSBzZXJ2ZXIgKHdlIGFyZSBub3Qg
c3BlYWtpbmcgYWJvdXQgYSBTSU1QTEUgcHJlc2VuY2UKc2VydmVyKS4gU28gdGhlIGRpYWxvZyBw
cmVzZW5jZSBzZXJ2ZXIgaXMgbm93IGF3YXJlIG9mIHRoZSBjdXJyZW50CmRpYWxvZyBiZXR3ZWVu
IEEgYW5kIEIuCi0gQiBzZW5kcyBhIFNVQlNDUklCRSAoRXZlbnQ6IGRpYWxvZzthY2xsLWlkPXh4
O3RvLXRhZz14eCkgdG8gQSBBb1IuCi0gVGhlIHByb3h5IHJlc3BvbnNpYmxlIGZvciBBIHJlY2Vp
dmVzIHRoZSBTVUJTQ1JJQkUgYW5kIGZvcndhcmRzIGl0CnRvIGl0cyBwcmVzZW5jZSBzZXJ2ZXIu
IEFnYWluLCB0aGUgcHJveHkgYWxsb3dzIHRoaXMgU1VCU0NSSUJFIHNpbmNlCnRoZSAiRXZlbnQi
IGhlYWRlciBpcyAiZGlhbG9nIiBjb250YWluaW5nICJjYWxsLWlkIiBhbmQgInRvLXRhZyIuCi0g
VGhlIHByZXNlbmNlIHNlcnZlciBjaGVja3MgdGhlIGRpYWxvZyBkYXRhIGluIHRoZSAiRXZlbnQi
IGhlYWRlciBvZgp0aGUgU1VCU0NSSUJFIChhcyBBIGRvZXMgaW4gY2FzZSAxKS4gSWYgaXQgbWF0
Y2hlcyBhbiBleGlzdGluZyBkaWFsb2cKaWYgcmVwbGllcyAyMDAgYW5kIE5PVElGWSBhcyBpbiBj
YXNlIDEuCi0gQSByZWNlaXZlcyB0aGUgMjAwIHNvIGhhcyB2ZXJpZmllZCB0aGUgc2VuZGVyIGlk
ZW50aXR5LgotIEIgc3RhcnQgcmluZ2luZyBhbmQgc28uLi4KCgo+IGluIG9wZW5zZXIva2FtYWls
aW8gZW52aXJvbm1lbnQsIGZvciBleGFtcGxlLCBrZWVwaW5nIHRyYWNrIG9mIGRpYWxvZ3MKPiBp
cyBpbXBsZW1lbnRlZCB1c2luZyBkaWFsb2cgbW9kdWxlLCB3aGljaCBoYXMgdGhlIGhpc3Rvcnkg
b2YgYmVpbmcgdGhlCj4gbW9zdCBidWdnaWVzIG1vZHVsZSBvZiBhbGwuICBwZXJoYXBzIHRoYXQg
aXMgZHVlIHRvIHRoZSBkaWZmaWN1bHR5IG9mCj4gdGhlIHByb2JsZW0sIGkuZS4sIHByb3h5IGlz
IG1hZGUgdG8gZG8gc29tZXRoaW5nIGl0IGlzIG5vdCByZWFsbHkKPiBpbnRlbmRlZCBmb3IuCgpQ
cm9iYWJseS4gQW55d2F5IHRoaXMgZHJhZnQgZGVmaW5lcyBhIGNvcnJlY3QgYmVoYXZpb3VyIHRo
YXQgY2FuIHdvcmsKaW4gZW52aXJvbm1lbnRzIGluIHdoaWNoIHRoZSBTVUJTQ1JJQkUgd291bGQg
YmUgc2VudCB0byBVQSBvciB3b3VsZCBiZQpoYW5kbGVkIGJ5IGEgcHJlc2VuY2Ugc2VydmVyLgpB
cyB5b3Ugc2F5LCBwcm9iYWJseSBkaWFsb2cgc3RhdHVzIHNob3VsZG4ndCBiZSBoYW5kbGVkIGJ5
IGEgcHJveHksCmJ1dCB0aGF0J3MgYSBkaWZmZXJlbnQgaXNzdWUuCgoKCi0tIApJw7Fha2kgQmF6
IENhc3RpbGxvCjxpYmNAYWxpYXgubmV0PgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXwpTaXAgbWFpbGluZyBsaXN0ICBodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL3NpcApUaGlzIGxpc3QgaXMgZm9yIE5FVyBkZXZlbG9wbWVudCBvZiB0
aGUgY29yZSBTSVAgUHJvdG9jb2wKVXNlIHNpcC1pbXBsZW1lbnRvcnNAY3MuY29sdW1iaWEuZWR1
IGZvciBxdWVzdGlvbnMgb24gY3VycmVudCBzaXAKVXNlIHNpcHBpbmdAaWV0Zi5vcmcgZm9yIG5l
dyBkZXZlbG9wbWVudHMgb24gdGhlIGFwcGxpY2F0aW9uIG9mIHNpcA==


From sip-bounces@ietf.org  Tue Oct 28 08:12:45 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4282628C2DA;
	Tue, 28 Oct 2008 08:12:45 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E918A28C2DA
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 08:12:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6Mut10tB7fzN for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 08:12:44 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6])
	by core3.amsl.com (Postfix) with ESMTP id 09C8A28C2D8
	for <sip@ietf.org>; Tue, 28 Oct 2008 08:12:44 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com
	(216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.291.1;
	Tue, 28 Oct 2008 11:11:22 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with
	mapi; Tue, 28 Oct 2008 11:11:22 -0400
From: Bob Penfield <BPenfield@acmepacket.com>
To: Juha Heinanen <jh@tutpro.com>, =?iso-8859-1?Q?I=F1aki_Baz_Castillo?=
	<ibc@aliax.net>
Date: Tue, 28 Oct 2008 11:10:20 -0400
Thread-Topic: [Sip] submission of a new I-D: "Dialog Event foR	Identity
	VErification"
Thread-Index: Ack5DfwwKDR3pJTwSJmJrSMltbN+dAAAEI2Q
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC3129FB89336@mail>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<18693.28129.618794.915466@harjus.tutpro.com>
	<200810272114.40331.ibc@aliax.net>
	<18694.12066.980412.507913@harjus.tutpro.com>
	<618e24240810271425h2b6290b4o830a4b8c6849580a@mail.gmail.com>
	<18694.44148.327220.629364@harjus.tutpro.com>
	<618e24240810280249h135256b1n746dec9cab51d053@mail.gmail.com>
	<18694.57749.609275.78711@harjus.tutpro.com>
	<618e24240810280306l2e27a76ag417ad59c8362efc9@mail.gmail.com>
	<18695.2946.519788.917581@harjus.tutpro.com>
	<cc1f582e0810280625p1c18982bkb6faad2fba3b1b95@mail.gmail.com>
	<18695.9640.142118.959882@harjus.tutpro.com>
In-Reply-To: <18695.9640.142118.959882@harjus.tutpro.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "sip@ietf.org" <sip@ietf.org>
Subject: Re: [Sip] submission of a new I-D: "Dialog Event
	foR	Identity	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Juha,

Could your proxy distinguish between subscription for the presence server a=
nd those for the UA based on the Request-URI? Something like this:

For the presence server:

        SUBSCRIBE sip:ps.example.com

For the UA:

        SUBSCRIBE sip:user@example.com

cheers,
(-:bob

-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of Juha =
Heinanen
Sent: Tuesday, October 28, 2008 10:46 AM
To: I=F1aki Baz Castillo
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR Identity VEri=
fication"

I=F1aki Baz Castillo writes:

 > >  > I'm afraid that you are assuming that a presence server is used.
 > >  > Derive is an _end-to-end mechanism_ implemented in the UAs.
 > >
 > > if i have configured my proxy to use presence server for local users,
 > > how does subscribe reach the UA?
 >
 > If you proxy includes a dialog presence server, then the SUBSCRIBE
 > doesn't need to reach the UA since your proxy already has the
 > information about dialogs of that UA.

inaki,

now i'm confused again.  in above, you say that this is a UA thing,  now
you seem to indicate, that proxy needs to keep track of the dialogs.
so far i'm not convinced that proxy can reliable keep track of dialogs.

in openser/kamailio environment, for example, keeping track of dialogs
is implemented using dialog module, which has the history of being the
most buggies module of all.  perhaps that is due to the difficulty of
the problem, i.e., proxy is made to do something it is not really
intended for.

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


From sip-bounces@ietf.org  Tue Oct 28 08:18:44 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4E3793A6C59;
	Tue, 28 Oct 2008 08:18:44 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E1EAB28C28C
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 08:18:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.385
X-Spam-Level: 
X-Spam-Status: No, score=-0.385 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3,
	MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1wF9NDUhE+Zk for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 08:18:42 -0700 (PDT)
Received: from po-out-1718.google.com (po-out-1718.google.com [72.14.252.158])
	by core3.amsl.com (Postfix) with ESMTP id 3F0F63A6C42
	for <sip@ietf.org>; Tue, 28 Oct 2008 08:18:41 -0700 (PDT)
Received: by po-out-1718.google.com with SMTP id c31so4222119poi.4
	for <sip@ietf.org>; Tue, 28 Oct 2008 08:18:27 -0700 (PDT)
Received: by 10.141.19.9 with SMTP id w9mr4202658rvi.202.1225207106738;
	Tue, 28 Oct 2008 08:18:26 -0700 (PDT)
Received: by 10.141.41.1 with HTTP; Tue, 28 Oct 2008 08:18:26 -0700 (PDT)
Message-ID: <cc1f582e0810280818n6b23b1acma3664538f332db99@mail.gmail.com>
Date: Tue, 28 Oct 2008 16:18:26 +0100
From: "=?UTF-8?Q?I=C3=B1aki_Baz_Castillo?=" <ibc@aliax.net>
Cc: "sip@ietf.org" <sip@ietf.org>
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC3129FB89336@mail>
MIME-Version: 1.0
Content-Disposition: inline
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<618e24240810271425h2b6290b4o830a4b8c6849580a@mail.gmail.com>
	<18694.44148.327220.629364@harjus.tutpro.com>
	<618e24240810280249h135256b1n746dec9cab51d053@mail.gmail.com>
	<18694.57749.609275.78711@harjus.tutpro.com>
	<618e24240810280306l2e27a76ag417ad59c8362efc9@mail.gmail.com>
	<18695.2946.519788.917581@harjus.tutpro.com>
	<cc1f582e0810280625p1c18982bkb6faad2fba3b1b95@mail.gmail.com>
	<18695.9640.142118.959882@harjus.tutpro.com>
	<E6C2E8958BA59A4FB960963D475F7AC3129FB89336@mail>
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR Identity
	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

MjAwOC8xMC8yOCBCb2IgUGVuZmllbGQgPEJQZW5maWVsZEBhY21lcGFja2V0LmNvbT46Cj4gQ291
bGQgeW91ciBwcm94eSBkaXN0aW5ndWlzaCBiZXR3ZWVuIHN1YnNjcmlwdGlvbiBmb3IgdGhlIHBy
ZXNlbmNlIHNlcnZlciBhbmQgdGhvc2UgZm9yIHRoZSBVQSBiYXNlZCBvbiB0aGUgUmVxdWVzdC1V
Ukk/IFNvbWV0aGluZyBsaWtlIHRoaXM6Cj4KPiBGb3IgdGhlIHByZXNlbmNlIHNlcnZlcjoKPgo+
ICAgICAgICBTVUJTQ1JJQkUgc2lwOnBzLmV4YW1wbGUuY29tCj4KPiBGb3IgdGhlIFVBOgo+Cj4g
ICAgICAgIFNVQlNDUklCRSBzaXA6dXNlckBleGFtcGxlLmNvbQoKVGhpcyBpcyBpbmNvcnJlY3Qu
IFRoZSBzZW5kZXIgb2YgdGhlIFNVQlNDUklCRSB3aWxsIGFsd2F5cyB1c2U6CiAgU1VCU0NSSUJF
IHNpcDp1c2VyQGV4YW1wbGUuY29tCgpBbHNvLCB0aGlzIHNlbmRlciBkb2Vzbid0IGtub3cgaWYg
aXRzIFNVQlNDUklCRSB3aWwgYmUgaGFuZGxlZCBieSBBJ3MKVUEgb3IgYnkgYSBwcmVzZW5jZSBz
ZXJ2ZXIuCgoKRXhhbXBsZToKCi0gQSBjYWxscyBCOgogICAgSU5WSVRFIHNpcDpCQGRvbWFpbl9C
LmNvbQogICAgRnJvbTogc2lwOkFAZG9tYWluX0Eub3JnO3RhZz0xMjM0CiAgICBDYWxsLUlEOiBh
YmNkZWZnCgotIEIgZ2VuZXJhdGVzIHRoaXMgU1VCU0NSSUJFOgogICAgU1VCU0NSSUJFIHNpcDpB
QGRvbWFpbl9BLm9yZyBTSVAvMi4wCiAgICBGcm9tOiBCQGRvbWFpbl9CLmNvbTt0YWc9eHh4eHgK
ICAgIFRvOiBzaXA6QUBkb21haW5fQS5vcmcKICAgIEV2ZW50OiBkaWFsb2c7Y2FsbC1pZD1hYmNk
ZWZnO3RvLXRhZz0xMjM0CgoKVGhlIFNVQlNDUklCRSBzZW50IGJ5IEIgKmFsd2F5cyogY29udGFp
bnMgdGhlIHVzZXJuYW1lIChBKSBpbiB0aGUgUlVSSS4KCi0tIApJw7Fha2kgQmF6IENhc3RpbGxv
CjxpYmNAYWxpYXgubmV0PgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXwpTaXAgbWFpbGluZyBsaXN0ICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL3NpcApUaGlzIGxpc3QgaXMgZm9yIE5FVyBkZXZlbG9wbWVudCBvZiB0aGUgY29yZSBT
SVAgUHJvdG9jb2wKVXNlIHNpcC1pbXBsZW1lbnRvcnNAY3MuY29sdW1iaWEuZWR1IGZvciBxdWVz
dGlvbnMgb24gY3VycmVudCBzaXAKVXNlIHNpcHBpbmdAaWV0Zi5vcmcgZm9yIG5ldyBkZXZlbG9w
bWVudHMgb24gdGhlIGFwcGxpY2F0aW9uIG9mIHNpcA==


From sip-bounces@ietf.org  Tue Oct 28 08:27:05 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7B30128C13E;
	Tue, 28 Oct 2008 08:27:05 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7F18028C13E
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 08:27:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.337
X-Spam-Level: 
X-Spam-Status: No, score=-2.337 tagged_above=-999 required=5
	tests=[AWL=-0.038, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id MN97426Ce5Bl for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 08:27:03 -0700 (PDT)
Received: from taimen.tutpro.com (harjus.tutpro.com [192.98.100.3])
	by core3.amsl.com (Postfix) with ESMTP id 97FC228C0E9
	for <sip@ietf.org>; Tue, 28 Oct 2008 08:27:03 -0700 (PDT)
Received: by taimen.tutpro.com (Postfix, from userid 1000)
	id BF20D33ABB3; Tue, 28 Oct 2008 17:26:38 +0200 (EET)
MIME-Version: 1.0
Message-ID: <18695.12078.714795.751159@harjus.tutpro.com>
Date: Tue, 28 Oct 2008 17:26:38 +0200
To: "=?UTF-8?Q?I=C3=B1aki_Baz_Castillo?=" <ibc@aliax.net>
In-Reply-To: <cc1f582e0810280811h7e1bbea9mbb63c390808e3bff@mail.gmail.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<18694.12066.980412.507913@harjus.tutpro.com>
	<618e24240810271425h2b6290b4o830a4b8c6849580a@mail.gmail.com>
	<18694.44148.327220.629364@harjus.tutpro.com>
	<618e24240810280249h135256b1n746dec9cab51d053@mail.gmail.com>
	<18694.57749.609275.78711@harjus.tutpro.com>
	<618e24240810280306l2e27a76ag417ad59c8362efc9@mail.gmail.com>
	<18695.2946.519788.917581@harjus.tutpro.com>
	<cc1f582e0810280625p1c18982bkb6faad2fba3b1b95@mail.gmail.com>
	<18695.9640.142118.959882@harjus.tutpro.com>
	<cc1f582e0810280811h7e1bbea9mbb63c390808e3bff@mail.gmail.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR
	Identity	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I=F1aki Baz Castillo writes:

 > 1) The SUBSCRIBE arrives to the UA location.
 > - A calls B.
 > - B sends a SUBSCRIBE (Event: dialog;acll-id=3Dxx;to-tag=3Dxx) to A AoR.
 > - The proxy responsible for A receives the SUBSCRIBE and forwards it
 > to A location(s). Note that the proxy allows this SUBSCRIBE since the
 > "Event" header is "dialog" containing "call-id" and "to-tag". It could
 > also check if the "Expires" equals 0. So this is not a SUBSCRIBE "for
 > all the calls from/to A", but a SUBSCRIBE for an spedific dialog.

ok, that kind of tests are feasible for the proxy to do.

 > 2) The SUBSCRIBE is handled by a proxy / presence server.
 > - A calls B through P1 (proxy responsible for A).
 > - P1 includes a dialog presence agent (as pua_dialoginfo). This agent
 > generates a PUBLISH that is sent to the integrated (or separate)
 > dialog presence server (we are not speaking about a SIMPLE presence
 > server). So the dialog presence server is now aware of the current
 > dialog between A and B.

this kind thing would be very hard to implement reliably.

in summary, i'm in favor of this draft and suggest that it will
be published as a working group document.

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


From sip-bounces@ietf.org  Tue Oct 28 08:27:38 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2EB2D28C2C8;
	Tue, 28 Oct 2008 08:27:38 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BBC1928C2C8
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 08:27:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.484
X-Spam-Level: 
X-Spam-Status: No, score=-2.484 tagged_above=-999 required=5 tests=[AWL=0.115, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tO2UpNs3Wpck for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 08:27:36 -0700 (PDT)
Received: from taimen.tutpro.com (harjus.tutpro.com [192.98.100.3])
	by core3.amsl.com (Postfix) with ESMTP id E449628C268
	for <sip@ietf.org>; Tue, 28 Oct 2008 08:27:35 -0700 (PDT)
Received: by taimen.tutpro.com (Postfix, from userid 1000)
	id DE9C533ABB3; Tue, 28 Oct 2008 17:27:20 +0200 (EET)
MIME-Version: 1.0
Message-ID: <18695.12120.871852.576893@harjus.tutpro.com>
Date: Tue, 28 Oct 2008 17:27:20 +0200
To: Bob Penfield <BPenfield@acmepacket.com>
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC3129FB89336@mail>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<18693.28129.618794.915466@harjus.tutpro.com>
	<200810272114.40331.ibc@aliax.net>
	<18694.12066.980412.507913@harjus.tutpro.com>
	<618e24240810271425h2b6290b4o830a4b8c6849580a@mail.gmail.com>
	<18694.44148.327220.629364@harjus.tutpro.com>
	<618e24240810280249h135256b1n746dec9cab51d053@mail.gmail.com>
	<18694.57749.609275.78711@harjus.tutpro.com>
	<618e24240810280306l2e27a76ag417ad59c8362efc9@mail.gmail.com>
	<18695.2946.519788.917581@harjus.tutpro.com>
	<cc1f582e0810280625p1c18982bkb6faad2fba3b1b95@mail.gmail.com>
	<18695.9640.142118.959882@harjus.tutpro.com>
	<E6C2E8958BA59A4FB960963D475F7AC3129FB89336@mail>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: "sip@ietf.org" <sip@ietf.org>
Subject: Re: [Sip] submission of a new I-D: "Dialog Event
	foR	Identity	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Bob Penfield writes:

 > For the presence server:
 > 
 >         SUBSCRIBE sip:ps.example.com
 > 
 > For the UA:
 > 
 >         SUBSCRIBE sip:user@example.com

in this application at least, it is better to check the dialog package
and parameters.

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


From sip-bounces@ietf.org  Tue Oct 28 08:58:49 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EA06E3A6A64;
	Tue, 28 Oct 2008 08:58:48 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ACC6B3A6A64
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 08:58:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.227
X-Spam-Level: 
X-Spam-Status: No, score=-0.227 tagged_above=-999 required=5 tests=[AWL=2.372, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zR8aep3ntAB6 for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 08:58:46 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id 798793A6C31
	for <SIP@ietf.org>; Tue, 28 Oct 2008 08:58:43 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K9G001A5HPT7Z@siemenscomms.co.uk> for SIP@ietf.org; Tue,
	28 Oct 2008 15:58:41 +0000 (GMT)
Date: Tue, 28 Oct 2008 15:58:22 +0000
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <4901D477.5010209@cisco.com>
To: Paul Kyzivat <pkyzivat@cisco.com>, Eric Burger <eburger@standardstrack.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D001382884@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] INFO Events Replacing or Updating INFO?
Thread-Index: Ack14JUlwzhg4jwUSsGeMVNYes4ZWQDMCx+g
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <C9685920-CA2B-435A-9FA9-767BE5085AB6@standardstrack.com>
	<4901D477.5010209@cisco.com>
Cc: SIP IETF <SIP@ietf.org>
Subject: Re: [Sip] INFO Events Replacing or Updating INFO?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

+1, provided existing use for ISUP and QSIG (Ecma-355) continues to be
valid.

John 

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Paul Kyzivat
> Sent: 24 October 2008 14:58
> To: Eric Burger
> Cc: SIP IETF
> Subject: Re: [Sip] INFO Events Replacing or Updating INFO?
> 
> 
> 
> Eric Burger wrote:
> 
> > [X] INFO Events should Obsolete RFC 2976
> > [ ] INFO Events should Update RFC 2796, because ____________
> > [ ] I do not care what you do
> 
> But of course the new document must carefully define backward 
> compatible 
> behavior. Its made a stab at that, and I expect it to be 
> complete before 
> approval.
> 
> 	Thanks,
> 	Paul
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Tue Oct 28 10:24:15 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6598828C33A;
	Tue, 28 Oct 2008 10:24:15 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6A0FA28C333
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 10:24:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.263
X-Spam-Level: 
X-Spam-Status: No, score=-1.263 tagged_above=-999 required=5 tests=[AWL=1.036, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8RPfnw4U2uWu for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 10:24:13 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id 7379E28C327
	for <sip@ietf.org>; Tue, 28 Oct 2008 10:24:13 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K9G0069XLO9AV@siemenscomms.co.uk> for sip@ietf.org; Tue,
	28 Oct 2008 17:24:09 +0000 (GMT)
Date: Tue, 28 Oct 2008 17:24:09 +0000
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
To: =?iso-8859-1?Q?Victor_Pascual_=C1vila?= <victor.pascual.avila@gmail.com>, 
	sip@ietf.org
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: Comment on DERIVE and B2BUAs
Thread-Index: Ack2s7f8ejTIhYY1SY+Ym+lIzxMIUgCbW15w
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
Subject: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Viktor,

An interesting draft addressing a known problem space. Dan Wing has already=
 pointed out similarities with draft-wing-sip-e164-rrc (now expired). I fea=
r the present draft will not work in the presence of B2BUAs along the path =
of the INVITE request, since these tend to change things like call-ID, to-t=
ag and from-tag. Since B2BUAs, and SBCs in particular, are the main reasons=
 why RFC 4474 will not work, any solution has to be able to work through th=
ese devices.

John =


> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On =

> Behalf Of Victor Pascual =C1vila
> Sent: 25 October 2008 16:09
> To: sip@ietf.org
> Subject: [Sip] submission of a new I-D: "Dialog Event foR =

> Identity VErification"
> =

> Hi all,
> =

> A new I-D, draft-kuthan-sip-derive-00, was just submitted. Your
> comments are always welcome.
> =

> Filename:          draft-kuthan-sip-derive
> Version:           00
> Staging URL:
> http://www3.ietf.org/proceedings/staging/draft-kuthan-sip-deri
ve-00.txt
> Title:             Dialog Event foR Identity VErification
> Creation_date:     2008-10-25
> WG ID:             Indvidual Submission
> Number_of_pages: 24
> Abstract:
> This document provides a simple mechanism to prevent an attacker from
> presenting a forged "From" header field.  It offers an end-to-end
> identity assumption which does not require any previous association
> or trust relationship between administrative domains or the UAs.  The
> UAS verifies the "From" header by subscribing to the Dialog Event
> package [RFC 4235] at the AOR in the "From" header field.  If the
> entity calling is registered under this AOR, it will confirm that it
> is calling by sending some valid dialog state.  In this case, the
> identity of the caller is considered to be verified.
> =

> Submitter: Victor Pascual (victor@iptel.org)
> =

> Author(s):
> Jiri Kuthan, Jiri.Kuthan@tekelec.com
> Dorgham Sisalem, Dorgham.Sisalem@tekelec.com
> Raphael Coeffic, Raphael.Coeffic@tekelec.com
> Victor Pascual, Victor.Pascual@tekelec.com
> =

> =

> Thanks,
> -- =

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

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


From sip-bounces@ietf.org  Tue Oct 28 10:42:59 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5C3C03A6C97;
	Tue, 28 Oct 2008 10:42:59 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DE78128C2BA
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 10:42:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.492
X-Spam-Level: 
X-Spam-Status: No, score=-2.492 tagged_above=-999 required=5 tests=[AWL=0.107, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id n2pWDA0Ydu0K for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 10:42:57 -0700 (PDT)
Received: from taimen.tutpro.com (harjus.tutpro.com [192.98.100.3])
	by core3.amsl.com (Postfix) with ESMTP id 02F7F3A6C97
	for <sip@ietf.org>; Tue, 28 Oct 2008 10:42:56 -0700 (PDT)
Received: by taimen.tutpro.com (Postfix, from userid 1000)
	id 225CF33ABB3; Tue, 28 Oct 2008 19:42:56 +0200 (EET)
MIME-Version: 1.0
Message-ID: <18695.20256.100950.244075@harjus.tutpro.com>
Date: Tue, 28 Oct 2008 19:42:56 +0200
To: "Elwell, John" <john.elwell@siemens.com>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org
Subject: [Sip]  Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Elwell, John writes:

 > An interesting draft addressing a known problem space. Dan Wing has
 > already pointed out similarities with draft-wing-sip-e164-rrc (now
 > expired). I fear the present draft will not work in the presence of
 > B2BUAs along the path of the INVITE request, since these tend to
 > change things like call-ID, to-tag and from-tag. Since B2BUAs, and
 > SBCs in particular, are the main reasons why RFC 4474 will not work,
 > any solution has to be able to work through these devices.

i don't accept that kind of requirement.  if you have problems with this
draft in B2BUAs, then you have to cope with them in your B2BUAs.  from
the point of view of this draft (and any SIP standard), B2BUAs are just
UAs.

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


From sip-bounces@ietf.org  Tue Oct 28 10:52:10 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 335093A6CA0;
	Tue, 28 Oct 2008 10:52:10 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C848028C273
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 10:52:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.385
X-Spam-Level: 
X-Spam-Status: No, score=-0.385 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3,
	MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id mOOv2QViRt4Z for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 10:52:08 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.229])
	by core3.amsl.com (Postfix) with ESMTP id 2280D3A6C74
	for <sip@ietf.org>; Tue, 28 Oct 2008 10:52:07 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so2692489rvf.49
	for <sip@ietf.org>; Tue, 28 Oct 2008 10:52:07 -0700 (PDT)
Received: by 10.141.198.2 with SMTP id a2mr4287730rvq.219.1225216327015;
	Tue, 28 Oct 2008 10:52:07 -0700 (PDT)
Received: by 10.141.41.1 with HTTP; Tue, 28 Oct 2008 10:52:06 -0700 (PDT)
Message-ID: <cc1f582e0810281052y34f5bf88h300c6f59d84879fe@mail.gmail.com>
Date: Tue, 28 Oct 2008 18:52:06 +0100
From: "=?UTF-8?Q?I=C3=B1aki_Baz_Castillo?=" <ibc@aliax.net>
Cc: sip@ietf.org
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
MIME-Version: 1.0
Content-Disposition: inline
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

MjAwOC8xMC8yOCBFbHdlbGwsIEpvaG4gPGpvaG4uZWx3ZWxsQHNpZW1lbnMuY29tPjoKPiBWaWt0
b3IsCj4KPiBBbiBpbnRlcmVzdGluZyBkcmFmdCBhZGRyZXNzaW5nIGEga25vd24gcHJvYmxlbSBz
cGFjZS4gRGFuIFdpbmcgaGFzIGFscmVhZHkgcG9pbnRlZCBvdXQgc2ltaWxhcml0aWVzIHdpdGgg
ZHJhZnQtd2luZy1zaXAtZTE2NC1ycmMgKG5vdyBleHBpcmVkKS4gSSBmZWFyIHRoZSBwcmVzZW50
IGRyYWZ0IHdpbGwgbm90IHdvcmsgaW4gdGhlIHByZXNlbmNlIG9mIEIyQlVBcyBhbG9uZyB0aGUg
cGF0aCBvZiB0aGUgSU5WSVRFIHJlcXVlc3QsIHNpbmNlIHRoZXNlIHRlbmQgdG8gY2hhbmdlIHRo
aW5ncyBsaWtlIGNhbGwtSUQsIHRvLXRhZyBhbmQgZnJvbS10YWcuIFNpbmNlIEIyQlVBcywgYW5k
IFNCQ3MgaW4gcGFydGljdWxhciwgYXJlIHRoZSBtYWluIHJlYXNvbnMgd2h5IFJGQyA0NDc0IHdp
bGwgbm90IHdvcmssIGFueSBzb2x1dGlvbiBoYXMgdG8gYmUgYWJsZSB0byB3b3JrIHRocm91Z2gg
dGhlc2UgZGV2aWNlcy4KClNpbmNlIHRoZSBCMkJVQSBoYXMgZGV0YWlsZWQgaW5mbyBvZiBib3Ro
IGxlZ3MgQSBhbmQgQiwgaXQgaXMgY2FwYWJsZQpvZiBkb2luZyBuZWVkZWQgY2hhbmdlcywgYXMg
cmVwbGFjaW5nIGNhbGwtaWQgYW5kIHRvLXRhZyBpbiBFdmVudApoZWFkZXIuCkFsc28sIHRoZSBC
MkJVQSBjb3VsZCBoYW5kbGUgdGhlIFNVQlNDUklCRSBieSBpdHMgb3duLCB0aGlzIGlzLApiZWNv
bWluZyBhIGRpYWxvZyBwcmVzZW5jZSBzZXJ2ZXIgaW5zdGVhZCBvZiBmb3J3YXJkaW5nIHRoZSBT
VUJTQ1JJQkUKdG8gdGhlIFVBLgpCMkJVQSBtdXN0IGhhbmRsZSBhbGwgdGhpcyBzdHVmZiBzaW5j
ZSB0aGV5IGFyZSwgaW4gZmFjdCwgdGhlIGVuZApwb2ludCwgbm90IHRoZSBVQSdzIGJlaGluZCB0
aGVtLgoKCi0tIApJw7Fha2kgQmF6IENhc3RpbGxvCjxpYmNAYWxpYXgubmV0PgpfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpTaXAgbWFpbGluZyBsaXN0ICBo
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpcApUaGlzIGxpc3QgaXMgZm9y
IE5FVyBkZXZlbG9wbWVudCBvZiB0aGUgY29yZSBTSVAgUHJvdG9jb2wKVXNlIHNpcC1pbXBsZW1l
bnRvcnNAY3MuY29sdW1iaWEuZWR1IGZvciBxdWVzdGlvbnMgb24gY3VycmVudCBzaXAKVXNlIHNp
cHBpbmdAaWV0Zi5vcmcgZm9yIG5ldyBkZXZlbG9wbWVudHMgb24gdGhlIGFwcGxpY2F0aW9uIG9m
IHNpcA==


From sip-bounces@ietf.org  Tue Oct 28 10:55:57 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 529E03A6C9E;
	Tue, 28 Oct 2008 10:55:57 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 48BEA3A69DF
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 10:55:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.763
X-Spam-Level: 
X-Spam-Status: No, score=-1.763 tagged_above=-999 required=5 tests=[AWL=0.836, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Uh5Gy-CwWRZ7 for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 10:55:54 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39])
	by core3.amsl.com (Postfix) with ESMTP id 621E13A6C74
	for <SIP@ietf.org>; Tue, 28 Oct 2008 10:55:54 -0700 (PDT)
Received: from ilexp03.ndc.lucent.com (h135-3-39-50.lucent.com [135.3.39.50])
	by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id m9SHtIJX022826; 
	Tue, 28 Oct 2008 12:55:50 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by
	ilexp03.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Oct 2008 12:55:49 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.28]) by
	DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Oct 2008 18:55:46 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 28 Oct 2008 18:55:45 +0100
Message-ID: <5D1A7985295922448D5550C94DE291800245BCD8@DEEXC1U01.de.lucent.com>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D001382884@GBNTHT12009MSX.gb002.siemens.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] INFO Events Replacing or Updating INFO?
Thread-Index: Ack14JUlwzhg4jwUSsGeMVNYes4ZWQDMCx+gAARaDfA=
References: <C9685920-CA2B-435A-9FA9-767BE5085AB6@standardstrack.com><4901D477.5010209@cisco.com>
	<0D5F89FAC29E2C41B98A6A762007F5D001382884@GBNTHT12009MSX.gb002.siemens.net>
From: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: "Elwell, John" <john.elwell@siemens.com>,
	"Paul Kyzivat" <pkyzivat@cisco.com>,
	"Eric Burger" <eburger@standardstrack.com>
X-OriginalArrivalTime: 28 Oct 2008 17:55:46.0976 (UTC)
	FILETIME=[67CC6A00:01C93926]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: SIP IETF <SIP@ietf.org>
Subject: Re: [Sip] INFO Events Replacing or Updating INFO?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Depends what you mean by that statement.

A legacy usage of INFO should interwork with a new usage. 

However, the question of what criteria exist for package definition in
conformance with the new document is still open.

Note also that obsolete RFCs do not disappear, they are just tagged
"obsolete".

Regards

Keith

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Elwell, John
> Sent: Tuesday, October 28, 2008 3:58 PM
> To: Paul Kyzivat; Eric Burger
> Cc: SIP IETF
> Subject: Re: [Sip] INFO Events Replacing or Updating INFO?
> 
> +1, provided existing use for ISUP and QSIG (Ecma-355) continues to be
> valid.
> 
> John 
> 
> > -----Original Message-----
> > From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of 
> > Paul Kyzivat
> > Sent: 24 October 2008 14:58
> > To: Eric Burger
> > Cc: SIP IETF
> > Subject: Re: [Sip] INFO Events Replacing or Updating INFO?
> > 
> > 
> > 
> > Eric Burger wrote:
> > 
> > > [X] INFO Events should Obsolete RFC 2976 [ ] INFO Events should 
> > > Update RFC 2796, because ____________ [ ] I do not care 
> what you do
> > 
> > But of course the new document must carefully define backward 
> > compatible behavior. Its made a stab at that, and I expect it to be 
> > complete before approval.
> > 
> > 	Thanks,
> > 	Paul
> > _______________________________________________
> > Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol Use 
> > sip-implementors@cs.columbia.edu for questions on current sip Use 
> > sipping@ietf.org for new developments on the application of sip
> > 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors@cs.columbia.edu for questions on current sip 
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Tue Oct 28 14:31:28 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C57003A6CAB;
	Tue, 28 Oct 2008 14:31:28 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AF59628C1C4
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 14:31:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.608
X-Spam-Level: 
X-Spam-Status: No, score=-1.608 tagged_above=-999 required=5 tests=[AWL=0.691, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LCgJ-vCMeq2m for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 14:31:27 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id D27CB3A6C6C
	for <sip@ietf.org>; Tue, 28 Oct 2008 14:31:26 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K9G00K5GX47MP@siemenscomms.co.uk> for sip@ietf.org; Tue,
	28 Oct 2008 21:31:20 +0000 (GMT)
Date: Tue, 28 Oct 2008 21:31:16 +0000
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <cc1f582e0810281052y34f5bf88h300c6f59d84879fe@mail.gmail.com>
To: =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D00138295A@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] Comment on DERIVE and B2BUAs
Thread-Index: Ack5JfblyVo4eO+ASa+kDlPzmw78FQAHe+qQ
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
	<cc1f582e0810281052y34f5bf88h300c6f59d84879fe@mail.gmail.com>
Cc: sip@ietf.org
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 =


> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On =

> Behalf Of I=F1aki Baz Castillo
> Sent: 28 October 2008 17:52
> Cc: sip@ietf.org
> Subject: Re: [Sip] Comment on DERIVE and B2BUAs
> =

> 2008/10/28 Elwell, John <john.elwell@siemens.com>:
> > Viktor,
> >
> > An interesting draft addressing a known problem space. Dan =

> Wing has already pointed out similarities with =

> draft-wing-sip-e164-rrc (now expired). I fear the present =

> draft will not work in the presence of B2BUAs along the path =

> of the INVITE request, since these tend to change things like =

> call-ID, to-tag and from-tag. Since B2BUAs, and SBCs in =

> particular, are the main reasons why RFC 4474 will not work, =

> any solution has to be able to work through these devices.
> =

> Since the B2BUA has detailed info of both legs A and B, it is capable
> of doing needed changes, as replacing call-id and to-tag in Event
> header.
> Also, the B2BUA could handle the SUBSCRIBE by its own, this is,
> becoming a dialog presence server instead of forwarding the SUBSCRIBE
> to the UA.
> B2BUA must handle all this stuff since they are, in fact, the end
> point, not the UA's behind them.
[JRE] This reduces it to transitive trust, i.e., no better than P-Asserted-=
Identity. The UA that receives the INVITE request has to trust its local B2=
BUA to confirm that the INVITE request really did come from the wherever it=
 claimed to have come from.

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


From sip-bounces@ietf.org  Tue Oct 28 15:32:31 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A1CCE3A6CB0;
	Tue, 28 Oct 2008 15:32:31 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2D0033A6CB6
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 15:32:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id eHYnKhPm83Dx for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 15:32:25 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 5ACE43A6CB0
	for <sip@ietf.org>; Tue, 28 Oct 2008 15:32:25 -0700 (PDT)
Received: from [192.168.2.2] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9SMWHVl012349
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Tue, 28 Oct 2008 17:32:19 -0500
Message-ID: <490792EA.2020106@softarmor.com>
Date: Tue, 28 Oct 2008 17:32:10 -0500
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Icedove 1.5.0.14eol (X11/20080724)
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
X-Enigmail-Version: 0.94.2.0
Cc: sip@ietf.org
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Elwell, John wrote:
> Viktor,
> 
> An interesting draft addressing a known problem space. Dan Wing has
> already pointed out similarities with draft-wing-sip-e164-rrc (now
> expired). I fear the present draft will not work in the presence of
> B2BUAs along the path of the INVITE request, since these tend to
> change things like call-ID, to-tag and from-tag. Since B2BUAs, and
> SBCs in particular, are the main reasons why RFC 4474 will not work,
> any solution has to be able to work through these devices.
> 

Would the SBC not have to handle the SUBSCRIBE request locally? After
all, since it is a terminal UA for the call, it also knows about all the
dialog states. The end-user UA would never even see the SUBSCRIBE.

So the SBC's lack of transparency on tags, etc. is irrelevant.

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


From sip-bounces@ietf.org  Tue Oct 28 15:36:03 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E1A113A6968;
	Tue, 28 Oct 2008 15:36:03 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 95B433A6830
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 15:36:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9FyKJ7u75y0Z for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 15:35:55 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id ADD333A6968
	for <sip@ietf.org>; Tue, 28 Oct 2008 15:35:53 -0700 (PDT)
Received: from [192.168.2.2] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9SMZmA7012384
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Tue, 28 Oct 2008 17:35:49 -0500
Message-ID: <490793BF.10702@softarmor.com>
Date: Tue, 28 Oct 2008 17:35:43 -0500
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Icedove 1.5.0.14eol (X11/20080724)
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>	<0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>	<cc1f582e0810281052y34f5bf88h300c6f59d84879fe@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D00138295A@GBNTHT12009MSX.gb002.siemens.net>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D00138295A@GBNTHT12009MSX.gb002.siemens.net>
X-Enigmail-Version: 0.94.2.0
Cc: sip@ietf.org
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Elwell, John wrote:
> 
> IBC said:
>> Since the B2BUA has detailed info of both legs A and B, it is
>> capable of doing needed changes, as replacing call-id and to-tag in
>> Event header. Also, the B2BUA could handle the SUBSCRIBE by its
>> own, this is, becoming a dialog presence server instead of
>> forwarding the SUBSCRIBE to the UA. B2BUA must handle all this
>> stuff since they are, in fact, the end point, not the UA's behind
>> them.
>
> [JRE] This reduces it to transitive trust, i.e., no better than
> P-Asserted-Identity. The UA that receives the INVITE request has to
> trust its local B2BUA to confirm that the INVITE request really did
> come from the wherever it claimed to have come from.
> 
>

Since the INVITE is coming from the SBC (even though the SBC was
influenced by something else to get it to send the INVITE), I don't see
a problem with this.

Otherwise said, SBCs are always transitive trust unless we have
end-to-end crypto, in which case we don't really have SBCs.

So?

--
Dean

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


From sip-bounces@ietf.org  Tue Oct 28 15:39:34 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 365DA3A6CB6;
	Tue, 28 Oct 2008 15:39:34 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 646863A6CB4
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 15:39:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id udveWwFGEx3F for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 15:39:32 -0700 (PDT)
Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.187])
	by core3.amsl.com (Postfix) with ESMTP id 1113C3A6CB6
	for <sip@ietf.org>; Tue, 28 Oct 2008 15:39:31 -0700 (PDT)
Received: by rn-out-0910.google.com with SMTP id m7so1392663rnd.18
	for <sip@ietf.org>; Tue, 28 Oct 2008 15:39:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type:references;
	bh=wD/dq1zf1lI87h9H64eGtQBrDvog2hnhUeF9ah7Sz4c=;
	b=Y5Wspvpq8BmfICQRXAsYExL7MvsEgcUDUJSkImWqizgChcASgWxzOGvbz9Yzu9Ivff
	35TtX2HyA6nzPD/cjR6JBQ7dDTR480m17mfXLxyqnk8wwyzd2oSWUjeAesZ6+B1gpFIL
	7PUais1g0q0m+LjHZYdAtOP2iQFvU/5ytMl70=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:references;
	b=SlX/Few5q+ABC3HjE9eYVFUrdQf2FhIFYfNw66QKYPvw/iciWxgYREmMKiORaGZ96z
	y4OgsfDeac9X5m63pMGJpwVYzskRAEbxkNaU4ZNzLYz6mfARf/G90iqRFZ+66Eqrxd/Z
	s/7J0sAdssGMjSwYV/HPNnhGZJj1hSz+6F97k=
Received: by 10.142.223.20 with SMTP id v20mr3642516wfg.152.1225233569486;
	Tue, 28 Oct 2008 15:39:29 -0700 (PDT)
Received: by 10.142.105.18 with HTTP; Tue, 28 Oct 2008 15:39:29 -0700 (PDT)
Message-ID: <21964a950810281539g41320a0bk7f7b2c879a1c3e93@mail.gmail.com>
Date: Tue, 28 Oct 2008 18:39:29 -0400
From: "Nasir Khan" <nkhan.sip@gmail.com>
To: "Dean Willis" <dean.willis@softarmor.com>
In-Reply-To: <490793BF.10702@softarmor.com>
MIME-Version: 1.0
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
	<cc1f582e0810281052y34f5bf88h300c6f59d84879fe@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D00138295A@GBNTHT12009MSX.gb002.siemens.net>
	<490793BF.10702@softarmor.com>
Cc: sip@ietf.org, "Elwell, John" <john.elwell@siemens.com>
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2064498581=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

--===============2064498581==
Content-Type: multipart/alternative; 
	boundary="----=_Part_51300_11607879.1225233569475"

------=_Part_51300_11607879.1225233569475
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Yes, obviously RFC 4474s mechanisms end at a B2BUA because the B2BUA
effectively starts a new call (from the UAC side).
In fact the B2BUA cannot even provide a new Identity header if the From
header remains unchanged because the Contact would typically be specific to
the B2BUA and the private key for senders domain is unknown to this B2BUA.

It however is not as bad as it sounds because typically B2BUAs (SBCs in
particular) would be within the final UASs trust domain.

Nasir
-- 
Get the most comprehensive open source SIP testing framework at
http://sipper.agnity.com
--

On Tue, Oct 28, 2008 at 6:35 PM, Dean Willis <dean.willis@softarmor.com>wrote:

> Elwell, John wrote:
> >
> > IBC said:
> >> Since the B2BUA has detailed info of both legs A and B, it is
> >> capable of doing needed changes, as replacing call-id and to-tag in
> >> Event header. Also, the B2BUA could handle the SUBSCRIBE by its
> >> own, this is, becoming a dialog presence server instead of
> >> forwarding the SUBSCRIBE to the UA. B2BUA must handle all this
> >> stuff since they are, in fact, the end point, not the UA's behind
> >> them.
> >
> > [JRE] This reduces it to transitive trust, i.e., no better than
> > P-Asserted-Identity. The UA that receives the INVITE request has to
> > trust its local B2BUA to confirm that the INVITE request really did
> > come from the wherever it claimed to have come from.
> >
> >
>
> Since the INVITE is coming from the SBC (even though the SBC was
> influenced by something else to get it to send the INVITE), I don't see
> a problem with this.
>
> Otherwise said, SBCs are always transitive trust unless we have
> end-to-end crypto, in which case we don't really have SBCs.
>
> So?
>
> --
> Dean
>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>



-- 
Get the most comprehensive open source SIP testing framework at
http://sipper.agnity.com

------=_Part_51300_11607879.1225233569475
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>Yes, obviously RFC 4474s mechanisms end at a B2BUA because the B2BUA effectively starts a new call (from the UAC side). </div>
<div>In fact the B2BUA cannot even provide a new Identity header if the From header remains unchanged because the Contact would typically be specific to the B2BUA and the private key for senders domain is unknown to this B2BUA. </div>

<div>&nbsp;</div>
<div>It however is not as bad as it sounds because typically B2BUAs (SBCs in particular) would be within the final UASs trust domain. </div>
<div>&nbsp;</div>
<div>Nasir<br></div>
<div>-- <br>Get the most comprehensive open source SIP testing framework at <a href="http://sipper.agnity.com/">http://sipper.agnity.com</a></div>
<div>--<br><br></div>
<div class="gmail_quote">On Tue, Oct 28, 2008 at 6:35 PM, Dean Willis <span dir="ltr">&lt;<a href="mailto:dean.willis@softarmor.com">dean.willis@softarmor.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Elwell, John wrote:<br>
<div class="Ih2E3d">&gt;<br>&gt; IBC said:<br>&gt;&gt; Since the B2BUA has detailed info of both legs A and B, it is<br>&gt;&gt; capable of doing needed changes, as replacing call-id and to-tag in<br>&gt;&gt; Event header. Also, the B2BUA could handle the SUBSCRIBE by its<br>
&gt;&gt; own, this is, becoming a dialog presence server instead of<br>&gt;&gt; forwarding the SUBSCRIBE to the UA. B2BUA must handle all this<br>&gt;&gt; stuff since they are, in fact, the end point, not the UA&#39;s behind<br>
&gt;&gt; them.<br>&gt;<br>&gt; [JRE] This reduces it to transitive trust, i.e., no better than<br>&gt; P-Asserted-Identity. The UA that receives the INVITE request has to<br>&gt; trust its local B2BUA to confirm that the INVITE request really did<br>
&gt; come from the wherever it claimed to have come from.<br>&gt;<br>&gt;<br><br></div>Since the INVITE is coming from the SBC (even though the SBC was<br>influenced by something else to get it to send the INVITE), I don&#39;t see<br>
a problem with this.<br><br>Otherwise said, SBCs are always transitive trust unless we have<br>end-to-end crypto, in which case we don&#39;t really have SBCs.<br><br>So?<br><br>--<br><font color="#888888">Dean<br></font>
<div>
<div></div>
<div class="Wj3C7c"><br>_______________________________________________<br>Sip mailing list &nbsp;<a href="https://www.ietf.org/mailman/listinfo/sip" target="_blank">https://www.ietf.org/mailman/listinfo/sip</a><br>This list is for NEW development of the core SIP Protocol<br>
Use <a href="mailto:sip-implementors@cs.columbia.edu">sip-implementors@cs.columbia.edu</a> for questions on current sip<br>Use <a href="mailto:sipping@ietf.org">sipping@ietf.org</a> for new developments on the application of sip<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Get the most comprehensive open source SIP testing framework at <a href="http://sipper.agnity.com">http://sipper.agnity.com</a><br>

------=_Part_51300_11607879.1225233569475--

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

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


From sip-bounces@ietf.org  Tue Oct 28 15:50:15 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4C4EE3A6CB6;
	Tue, 28 Oct 2008 15:50:15 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0C3293A6CB6
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 15:50:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.735
X-Spam-Level: 
X-Spam-Status: No, score=-1.735 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553,
	HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id TrsBuLGLBsi7 for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 15:50:08 -0700 (PDT)
Received: from xcvs.xcastlabs.com (mail.xcastlabs.net [66.153.122.23])
	by core3.amsl.com (Postfix) with ESMTP id 5B6E13A6CC9
	for <sip@ietf.org>; Tue, 28 Oct 2008 15:50:08 -0700 (PDT)
Received: from [10.10.10.51] ([10.10.10.51])
	by xcvs.xcastlabs.com (8.13.8/8.13.8) with ESMTP id m9SMo0AY025571
	for <sip@ietf.org>; Tue, 28 Oct 2008 17:50:00 -0500
From: Victor Grinberg <VictorG@xcastlabs.com>
To: sip <sip@ietf.org>
In-Reply-To: <21964a950810281539g41320a0bk7f7b2c879a1c3e93@mail.gmail.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
	<cc1f582e0810281052y34f5bf88h300c6f59d84879fe@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D00138295A@GBNTHT12009MSX.gb002.siemens.net>
	<490793BF.10702@softarmor.com>
	<21964a950810281539g41320a0bk7f7b2c879a1c3e93@mail.gmail.com>
Date: Tue, 28 Oct 2008 17:49:59 -0500
Message-Id: <1225234199.6143.22.camel@victorg>
Mime-Version: 1.0
X-Mailer: Evolution 2.22.3.1 (2.22.3.1-1.fc9) 
X-Virus-Scanned: ClamAV version 0.93.1,
	clamav-milter version 0.93.1 on xcvs.xcastlabs.com
X-Virus-Status: Clean
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

On Tue, 2008-10-28 at 18:39 -0400, Nasir Khan wrote:
> Yes, obviously RFC 4474s mechanisms end at a B2BUA because the B2BUA
> effectively starts a new call (from the UAC side). 
> In fact the B2BUA cannot even provide a new Identity header if the
> From header remains unchanged because the Contact would typically be
> specific to the B2BUA and the private key for senders domain is
> unknown to this B2BUA. 
>  
> It however is not as bad as it sounds because typically B2BUAs (SBCs
> in particular) would be within the final UASs trust domain. 
>  


In practice SBC is most likely a third-party piece of hardware/software
with it's own functionality and most likely do not have access to local
trust domain database.

--
VictorG



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


From sip-bounces@ietf.org  Tue Oct 28 19:38:13 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E06123A69C3;
	Tue, 28 Oct 2008 19:38:13 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7F0293A68A0
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 19:38:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ybqDoXmGcMxw for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 19:38:11 -0700 (PDT)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146])
	by core3.amsl.com (Postfix) with ESMTP id 790073A677D
	for <sip@ietf.org>; Tue, 28 Oct 2008 19:38:11 -0700 (PDT)
Received: from shell.TheWorld.com (mlutton@shell01.theworld.com
	[192.74.137.71])
	by TheWorld.com (8.13.6/8.13.6) with ESMTP id m9T2apPD026174
	for <sip@ietf.org>; Tue, 28 Oct 2008 22:36:53 -0400
Received: from shell01.TheWorld.com (localhost [127.0.0.1])
	by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id m9T2aoT255676888
	for <sip@ietf.org>; Tue, 28 Oct 2008 21:36:51 -0500 (EST)
Received: (from worley@localhost)
	by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id m9T2akDN55854559;
	Tue, 28 Oct 2008 22:36:46 -0400 (EDT)
Date: Tue, 28 Oct 2008 22:36:46 -0400 (EDT)
Message-Id: <200810290236.m9T2akDN55854559@shell01.TheWorld.com>
To: sip@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>
	(dean.willis@softarmor.com)
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR Identity
	VErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

   From: Dean Willis <dean.willis@softarmor.com>

   Sounds like you have reinvented identd, which has pretty much vanished  
   from the Internet because it was found to not really add any useful  
   authentication.

   See: http://en.wikipedia.org/wiki/Ident

Well, "Nonetheless Ident is widely used and considered useful by
some."

   So tell me, how is this operationally different from IDENT?

Ident is used to verify the other end of a TCP connection.  The
problem with Ident is that it doesn't reliably tell you more than the
identity of the host from which the connection comes from (because you
can't really trust identd at the far end), and you knew what the host
was already by looking at the packet addresses.

With SIP, you don't know that the originating UAS has the same name as
it is claiming to have, because you got the SIP message from some
nearby proxy.  DERIVE is more like doing a reverse DNS lookup to see
if the originating host has the name that it claims to have.

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


From sip-bounces@ietf.org  Tue Oct 28 19:38:14 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A90423A6A01;
	Tue, 28 Oct 2008 19:38:14 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 38CF53A6941
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 19:38:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Ysoc398hdKhU for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 19:38:12 -0700 (PDT)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146])
	by core3.amsl.com (Postfix) with ESMTP id 581AD3A69C3
	for <sip@ietf.org>; Tue, 28 Oct 2008 19:38:11 -0700 (PDT)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71])
	by TheWorld.com (8.13.6/8.13.6) with ESMTP id m9T2abLa018009
	for <sip@ietf.org>; Tue, 28 Oct 2008 22:36:39 -0400
Received: from shell01.TheWorld.com (localhost [127.0.0.1])
	by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id m9T2aaut56001116
	for <sip@ietf.org>; Tue, 28 Oct 2008 21:36:37 -0500 (EST)
Received: (from worley@localhost)
	by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id m9T2aagI55951354;
	Tue, 28 Oct 2008 22:36:36 -0400 (EDT)
Date: Tue, 28 Oct 2008 22:36:36 -0400 (EDT)
Message-Id: <200810290236.m9T2aagI55951354@shell01.TheWorld.com>
To: sip@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
	(john.elwell@siemens.com)
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

   From: "Elwell, John" <john.elwell@siemens.com>

   An interesting draft addressing a known problem space. Dan Wing has
   already pointed out similarities with draft-wing-sip-e164-rrc (now
   expired). I fear the present draft will not work in the presence of
   B2BUAs along the path of the INVITE request, since these tend to
   change things like call-ID, to-tag and from-tag. Since B2BUAs, and
   SBCs in particular, are the main reasons why RFC 4474 will not
   work, any solution has to be able to work through these devices.

However...  If we change the sequence of operations a bit, so that the
UAS sends a 183 with a Contact carrying a specific header parameter
carrying a crypto-random value, and we get B2BUAs to pass it through
(attaching it to the Contact they use in the 183 they emit on the
other side), then if the UAS does a non-filtered dialog event
SUBSCRIBE, it can check the returned NOTIFY to see if it carries the
Contact header parameter that it created.  That's a reasonably good
test that the UAC of the INVITE can be reached via the From value that
the UAS received.

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


From sip-bounces@ietf.org  Tue Oct 28 19:38:15 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6A41228C332;
	Tue, 28 Oct 2008 19:38:15 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 916473A6941
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 19:38:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.523
X-Spam-Level: 
X-Spam-Status: No, score=-3.523 tagged_above=-999 required=5
	tests=[AWL=-0.076, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1,
	SARE_SUB_ENC_UTF8=0.152]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ofV6SUyBCXz8 for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 19:38:12 -0700 (PDT)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145])
	by core3.amsl.com (Postfix) with ESMTP id B84623A677D
	for <sip@ietf.org>; Tue, 28 Oct 2008 19:38:12 -0700 (PDT)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71])
	by TheWorld.com (8.13.6/8.13.6) with ESMTP id m9T2assN028430
	for <sip@ietf.org>; Tue, 28 Oct 2008 22:36:57 -0400
Received: from shell01.TheWorld.com (localhost [127.0.0.1])
	by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id m9T2aswB55636509
	for <sip@ietf.org>; Tue, 28 Oct 2008 21:36:54 -0500 (EST)
Received: (from worley@localhost)
	by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id m9T2asoN55836835;
	Tue, 28 Oct 2008 22:36:54 -0400 (EDT)
Date: Tue, 28 Oct 2008 22:36:54 -0400 (EDT)
Message-Id: <200810290236.m9T2asoN55836835@shell01.TheWorld.com>
To: sip@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <200810252305.20030.ibc@aliax.net>
References: <200810251926.17644.ibc@aliax.net> <490382B6.1090400@cisco.com>
	<200810252305.20030.ibc@aliax.net>
Subject: Re: [Sip]
	=?utf-8?q?=5BRFC_4235_=26_draft-kuthan-sip-derive=5D_481_?=
	=?utf-8?q?=22Call_doesn=27t_exist=22_=09for_initial_SUBSCRIBE_=3F?=
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

   From: =?utf-8?q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>

   I suppose 404 is also unappropiate, isn't?

It's not clear to me reading RFC 4235 that a SUBSCRIBE with an Event
header that specifies a Call-Id that is unknown to the UAS will result
in a failure response.  It may obtain a NOTIFY that lists no dialogs.

But if it does receive an error, 404 seems the most appropriate.

In any case, for the purposes of DERIVE, none of that matters:  Any
failure response to the SUBSCRIBE, or a NOTIFY that does not list the
call in question, results in call rejection.

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


From sip-bounces@ietf.org  Tue Oct 28 20:42:56 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 039CB3A68BE;
	Tue, 28 Oct 2008 20:42:56 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 379A83A680A
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 20:42:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.412
X-Spam-Level: 
X-Spam-Status: No, score=-6.412 tagged_above=-999 required=5
	tests=[AWL=-0.112, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id wyHCpX-ZaLs2 for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 20:42:53 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 6C0023A6880
	for <sip@ietf.org>; Tue, 28 Oct 2008 20:42:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,504,1220227200"; d="scan'208";a="97299351"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-1.cisco.com with ESMTP; 29 Oct 2008 03:42:52 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m9T3gqbt030519; 
	Tue, 28 Oct 2008 20:42:52 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m9T3gqp5016979;
	Wed, 29 Oct 2008 03:42:52 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "=?iso-8859-1?Q?'I=F1aki_Baz_Castillo'?=" <ibc@aliax.net>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com><D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com><200810261145.19745.ibc@aliax.net><57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com><084c01c938a0$a41ff390$c3f0200a@cisco.com>
	<cc1f582e0810280444y42b8f723w938004e902fb1180@mail.gmail.com>
Date: Tue, 28 Oct 2008 20:42:51 -0700
Message-ID: <032301c93978$6b249c70$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <cc1f582e0810280444y42b8f723w938004e902fb1180@mail.gmail.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: Ack48o50sUW4tzUTRqqrncebd3/KFQAhTAPA
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1393; t=1225251772;
	x=1226115772; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[Sip]=20submission=20of=20a=20new=20I-D
	=3A=20=22Dialog=20Event=20foRIdentityVErification=22
	|Sender:=20; bh=F7+UByyc8yUhKBCFq+LkMeK0tRIcGb7SFwmF+NNPj4s=;
	b=V76aKhnW2SOnFgXU9OLtncBu6EEMkw8TIURXncz+2R1b+KNdi0ROqkPATh
	Wh8Wx2IsXLmBMv10E91//sAcnBf7xdwHTHil2lCG/6KUIkVY4dssHANgj6H7
	wAS8sShglJ;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event
	foRIdentityVErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 =


> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On =

> Behalf Of I=F1aki Baz Castillo
> Sent: Tuesday, October 28, 2008 4:44 AM
> Cc: sip@ietf.org
> Subject: Re: [Sip] submission of a new I-D: "Dialog Event =

> foRIdentityVErification"
> =

> 2008/10/28 Dan Wing <dwing@cisco.com>:
> > Here is another return routability check,
> > http://tools.ietf.org/html/draft-wing-sip-e164-rrc-01#section-3.1
> > (My I-D expired due to lack of interest.)
> =

> It uses RFC 4474, certificates... is it really feasible in =

> this real world?

No, it doesn't use RFC4474.  The steps merely show where an RFC4474 =

signature could be performed.  If no RFC4474 signatures are
being created, or validated, those steps are the 'null operation'
(not performed).  Without those steps, it is remarkably similar
to DERIVE.

> IMHO "Dialog Event foR Identity VErification" is the more feasible
> solution at the moment.

The differences are minor.

-d


> =

> =

> -- =

> I=F1aki Baz Castillo
> <ibc@aliax.net>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip

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


From sip-bounces@ietf.org  Tue Oct 28 20:52:07 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3EADC3A6A51;
	Tue, 28 Oct 2008 20:52:07 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B42443A6A51
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 20:52:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.539
X-Spam-Level: 
X-Spam-Status: No, score=-6.539 tagged_above=-999 required=5 tests=[AWL=0.060, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ss7lkoKf3X4L for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 20:52:05 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 0A4C13A689C
	for <sip@ietf.org>; Tue, 28 Oct 2008 20:52:05 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,504,1220227200"; d="scan'208";a="184510546"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 29 Oct 2008 03:52:04 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9T3q4As030630; 
	Tue, 28 Oct 2008 20:52:04 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9T3q4Mt010083;
	Wed, 29 Oct 2008 03:52:04 GMT
From: "Dan Wing" <dwing@cisco.com>
To: <Dale.Worley@comcast.net>, <sip@ietf.org>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com><D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>
	<200810290236.m9T2akDN55854559@shell01.TheWorld.com>
Date: Tue, 28 Oct 2008 20:52:02 -0700
Message-ID: <033d01c93979$b3cf1990$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <200810290236.m9T2akDN55854559@shell01.TheWorld.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: Ack5b20FZ3GeTM5zTlGiZA+VDSiCrQACXFxw
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=954; t=1225252324; x=1226116324;
	c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[Sip]=20submission=20of=20a=20new=20I-D
	=3A=20=22Dialog=20Event=20foR=20IdentityVErification=22
	|Sender:=20; bh=papDMMy/OCAzGNn8vHk+TGmBdH0ZNYY7sFShcRfD6ps=;
	b=HCo7+bUVI2x1U10z9BsRh5bIBy6zdq7TgQGAnaTQgnZwL0Ymyho8mEtFha
	FXuh4YDCQ56NNSPtyjEqd4Q0pMv5xdmHMYJH0JACw5+oITxLS8ZatJGu3nuO
	b2L9gU8bITZ8Muj78v5IDNll1+dZqW3GTdfhB98mPOLz9EYBVKga4=;
Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR
	IdentityVErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

> With SIP, you don't know that the originating UAS has the same name as
> it is claiming to have, because you got the SIP message from some
> nearby proxy.  DERIVE is more like doing a reverse DNS lookup to see
> if the originating host has the name that it claims to have.

Yeah, that's walking the DNS tree.  It is valuable; heck, IETF's own
mailservers are doing it to reduce spam so it Must Be Good!  :-)

DERIVE is checking to see if your SIP routing takes you to the
same place that (claims to) be originating the incoming INVITE.  
It is using your *outgoing* SIP routing -- which you must already 
trust to send outbound messages -- to test the validity of the
(proported) From: address of an incoming INVITE.


Such a return routability check is probably the best SIP can do in the
presence of SBCs and the inability to get
draft-fischer-sip-e2e-sec-media-01.txt or draft-wing-sip-identity-media-03.txt
off the ground.

-d

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


From sip-bounces@ietf.org  Tue Oct 28 21:05:15 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0F55E3A6A73;
	Tue, 28 Oct 2008 21:05:15 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 42FCB3A677D
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 21:05:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.549
X-Spam-Level: 
X-Spam-Status: No, score=-6.549 tagged_above=-999 required=5 tests=[AWL=0.050, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id oGmnCsyVP9Ul for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 21:05:12 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 746403A6A51
	for <sip@ietf.org>; Tue, 28 Oct 2008 21:05:12 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,504,1220227200"; d="scan'208";a="111540436"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-3.cisco.com with ESMTP; 29 Oct 2008 04:05:09 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9T456rL028783; 
	Tue, 28 Oct 2008 21:05:06 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9T456lt016843;
	Wed, 29 Oct 2008 04:05:06 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Dean Willis'" <dean.willis@softarmor.com>,
	"'Elwell, John'" <john.elwell@siemens.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com><0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
	<490792EA.2020106@softarmor.com>
Date: Tue, 28 Oct 2008 21:05:04 -0700
Message-ID: <033f01c9397b$860847a0$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <490792EA.2020106@softarmor.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: Ack5TRcfKcaXrgdjRqGXwdgwzD05IgALXE8g
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1558; t=1225253106;
	x=1226117106; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[Sip]=20Comment=20on=20DERIVE=20and=20B
	2BUAs |Sender:=20;
	bh=1+rzMg0GZs363Mi1RwBl6Hsb/4AB9J8t+ZVFVAEWgSg=;
	b=TYyDpvUcSl9jNoN596fHDGr+qG9vQpBfr84cl9jCME5E/DOhFOi2OTq/c2
	9KJaWkx95I7+miJ6TFHJCTGf9POEo+KZRnqQV0AvjTA537Mkeryssc2bWZbH
	Gwp3Hl89Q9;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: sip@ietf.org
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Dean Willis
> Sent: Tuesday, October 28, 2008 3:32 PM
> To: Elwell, John
> Cc: sip@ietf.org
> Subject: Re: [Sip] Comment on DERIVE and B2BUAs
> 
> Elwell, John wrote:
> > Viktor,
> > 
> > An interesting draft addressing a known problem space. Dan Wing has
> > already pointed out similarities with draft-wing-sip-e164-rrc (now
> > expired). I fear the present draft will not work in the presence of
> > B2BUAs along the path of the INVITE request, since these tend to
> > change things like call-ID, to-tag and from-tag. Since B2BUAs, and
> > SBCs in particular, are the main reasons why RFC 4474 will not work,
> > any solution has to be able to work through these devices.
> > 
> 
> Would the SBC not have to handle the SUBSCRIBE request locally? After
> all, since it is a terminal UA for the call, it also knows 
> about all the
> dialog states. The end-user UA would never even see the SUBSCRIBE.

If that's a problem, just use some different method that goes end to
end.  The always-loved INFO comes to mind.

-d

> So the SBC's lack of transparency on tags, etc. is irrelevant.
> 
> --
> Dean
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip

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


From sip-bounces@ietf.org  Tue Oct 28 21:16:33 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A7FDA3A6983;
	Tue, 28 Oct 2008 21:16:33 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E7F813A6983
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 21:16:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.556
X-Spam-Level: 
X-Spam-Status: No, score=-7.556 tagged_above=-999 required=5 tests=[AWL=1.043, 
	BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UFbTgmK7yyke for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 21:16:32 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 2463B3A68A0
	for <sip@ietf.org>; Tue, 28 Oct 2008 21:16:32 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,504,1220227200"; d="scan'208";a="97308199"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-1.cisco.com with ESMTP; 29 Oct 2008 04:16:31 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m9T4GVGh030393; 
	Tue, 28 Oct 2008 21:16:31 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m9T4GVEj002178;
	Wed, 29 Oct 2008 04:16:31 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Dean Willis'" <dean.willis@softarmor.com>,
	"'Elwell, John'" <john.elwell@siemens.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>	<0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>	<cc1f582e0810281052y34f5bf88h300c6f59d84879fe@mail.gmail.com><0D5F89FAC29E2C41B98A6A762007F5D00138295A@GBNTHT12009MSX.gb002.siemens.net>
	<490793BF.10702@softarmor.com>
Date: Tue, 28 Oct 2008 21:16:29 -0700
Message-ID: <034601c9397d$1e055150$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <490793BF.10702@softarmor.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: Ack5TZTjY39XMHUTQpqEtozVFadSWgALfy3A
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2315; t=1225253791;
	x=1226117791; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[Sip]=20Comment=20on=20DERIVE=20and=20B
	2BUAs |Sender:=20;
	bh=WBJHnLlaE3qcuW9EtRxdaGR1qbig9dmBSnoQOlI9URc=;
	b=CgOyKJE5ZcUIKlZRJkLDjxJAboTwA2oD200/2xMQDzh0Us/inUpltQ6H7N
	BEgrjbeVb+enNt6sTsygvMeQhkvtvgA8KdLaWPUVqTai/xQY4TkgzeCB9iGf
	4wJFl8DVFB;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: sip@ietf.org
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Dean Willis
> Sent: Tuesday, October 28, 2008 3:36 PM
> To: Elwell, John
> Cc: sip@ietf.org
> Subject: Re: [Sip] Comment on DERIVE and B2BUAs
> 
> Elwell, John wrote:
> > 
> > IBC said:
> >> Since the B2BUA has detailed info of both legs A and B, it is
> >> capable of doing needed changes, as replacing call-id and to-tag in
> >> Event header. Also, the B2BUA could handle the SUBSCRIBE by its
> >> own, this is, becoming a dialog presence server instead of
> >> forwarding the SUBSCRIBE to the UA. B2BUA must handle all this
> >> stuff since they are, in fact, the end point, not the UA's behind
> >> them.
> >
> > [JRE] This reduces it to transitive trust, i.e., no better than
> > P-Asserted-Identity. The UA that receives the INVITE request has to
> > trust its local B2BUA to confirm that the INVITE request really did
> > come from the wherever it claimed to have come from.
> 
> Since the INVITE is coming from the SBC (even though the SBC was
> influenced by something else to get it to send the INVITE), I 
> don't see a problem with this.
> 
> Otherwise said, SBCs are always transitive trust unless we have
> end-to-end crypto, in which case we don't really have SBCs.
> 
> So?

I trust my post office to route a package to the "To:" address 
much more than I trust the "From:" address of a package on my 
doorstep.  I expect you do, too -- or do you really believe those
letters are from Ed McMahon?

An analogy:  DERIVE (and my old RRC draft) are looking at the 
characteristics of that package on the doorstep (SIP INVITE), and 
sending a letter to the "From:" address written on the package,
asking "Did you really send that?".  The post office will route
that letter correctly, and it will be opened by the addressee,
who will say "Yes, I sent you that package", which is routed
back to me.  I will *then* pick up the package (the SIP INVITE).

For additional protection (as described in my RRC draft) from
the post office opening that letter and responding on behalf
of the addressee (which an SBC or B2BUA might be tempted to
do), we could require the addressee to use a wax seal on 
their reply letter (a signature over their reply).

-d

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


From sip-bounces@ietf.org  Tue Oct 28 21:46:03 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6B12B3A68C0;
	Tue, 28 Oct 2008 21:46:03 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BD3F33A6874
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 21:46:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.598
X-Spam-Level: 
X-Spam-Status: No, score=-0.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_HEXOCTDWORD=2]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Ky2jVwK3LcoW for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 21:46:01 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.225])
	by core3.amsl.com (Postfix) with ESMTP id 4EADC3A6892
	for <sip@ietf.org>; Tue, 28 Oct 2008 21:45:58 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so2962657rvf.49
	for <sip@ietf.org>; Tue, 28 Oct 2008 21:45:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type:references;
	bh=aWFwEgJpNqBH3tBT8Ies2+NutlRi7LSFjnrUenqdO/c=;
	b=QIq09ak3BHQWh84Byh+nisyAV7X9YvMCh0+kgHVjS5iFUxeDC6gKeP+0CyAIzZ7wre
	etsCzbVXS6mzpA7zPJTRYmXKnjSg+zO2lVpEBRVPVdw/DQaeu1+ZNpCi/AJVy5uYh6Qi
	CQcB1bPOaSXfHrfW4r0ywQl9NheNEYqYDbsyY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:references;
	b=fWYSSFEmWglFTJx8QaG8KN/51y73JXaMXffAgNfKRJ9Xifxo5Lg6Q0/6nkHtBKTi/L
	QTx9fD9qDufjLz5sT0507rFa/TpoSe9fJjNuggHghqluZojrLQnI/FscAptMumFSRtpF
	YJ9Nk0bVvS+TlufrrSqcvDa0zY8cO5O/7ex78=
Received: by 10.142.204.18 with SMTP id b18mr3796819wfg.126.1225255556556;
	Tue, 28 Oct 2008 21:45:56 -0700 (PDT)
Received: by 10.142.105.18 with HTTP; Tue, 28 Oct 2008 21:45:56 -0700 (PDT)
Message-ID: <21964a950810282145t6950acdeo411824ec604cb219@mail.gmail.com>
Date: Wed, 29 Oct 2008 00:45:56 -0400
From: "Nasir Khan" <nkhan.sip@gmail.com>
To: "Christer Holmberg" <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F906@esealmw113.eemea.ericsson.se>
MIME-Version: 1.0
References: <48FDEAD8.8010803@cisco.com> <4901D025.6060302@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>
	<490239C8.3020808@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>
	<4902467E.3010603@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFBA@esealmw113.eemea.ericsson.se>
	<4905B23F.10609@cisco.com> <49060DD4.7070804@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F906@esealmw113.eemea.ericsson.se>
Cc: SIP IETF <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2009482648=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

--===============2009482648==
Content-Type: multipart/alternative; 
	boundary="----=_Part_54126_19317963.1225255556549"

------=_Part_54126_19317963.1225255556549
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Maybe it warrants a separate thread but I would like to discuss section
7.1.3 of this draft where 3265 is talked about as an alternative.
Since we are talking about the notion of well defined info packages and the
INFO messages
will carry information as a result of an event like an ISUP event or DTMF
event (the name of the draft itself has "event" in it), then the two User
Agents can very well subscribe to these events and use the notifications for
the information exchange.
This will automatically inherit all the good work done around notification
framework and will lay to rest lot of questions and perhaps save some
re-invention.

Regards
Nasir

On Mon, Oct 27, 2008 at 4:48 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

>
> Hi,
>
> >>>My preference would be for a new value, say "package", "info", or
> >>>"info-package". I think we *might* be able to define that "render"
> >>>serves this purpose *for INFO messages*, but I would rather not do
> >>>that because it is indeed asking from trouble and confusion.
> >>
> >>IF we define a new C-D value, which is unique for info packages, I
> have no problem with a C-D based solution.
> >
> >OK. That is progress!!!
> >
> >>But, it would still be more work to define info packages, because you
> >>would need to specify which C-T value to use.
> >
> >The document already calls for this:
> >
> >    7.2.4.  INFO Bodies
> >
> >    Each Info Package MUST define what type or types of bodies are
> >    expected in INFO requests.  Such packages MUST specify or cite
> >    detailed specifications for the syntax and semantics associated
> with
> >    such a body.
> >
> >    Info Packages also MUST define a default MIME type if the "Accept"
> >    header fails to define any MIME types in the INVITE request.
>
> Yes, it's in the document. The point was that one may have to define
> this new MIME type. But, maybe that is not a big problem (I haven't
> defined mime types, so I can't tell).
>
> >The wording could be better. There are no explicit IANA considerations
> about registering an INFO package. Its just implied here. Its a little
> confusing here what is intended to be part of the
> >*definition* of a new package vs. what is intended to be in the content
> of a particular package instance in an INFO message.
>
> We do need to have a section on what needs to be part of an info package
> definition. The mime type is one thing, for sure.
>
> I guess we should also look at what/if we can re-use from SIP events.
>
> We also need to decide whether info packages should have a version
> number system. From experience I think that would be very useful.
>
> Info-Package: foo-package;version=1
>
> ...or something like that.
>
> >>My issue is if we want to re-use an existing value, because I don't
> think we for sure can say that couldn't be a case where more than one
> >>body part has a "render" value (or whatever existing value we would
> choose for info packages).
> >
> >This is all hypothetical, because we don't have any usages with the new
> info package stuff.
>
> Exactly.
>
> >What I guess you are getting at is if there are any existing uses of
> body parts with "render" that might have to coexist with the info
> package in the message.
>
> Yes.
>
> >So I agree, we need a new value.
>
> Good :)
>
> Regards,
>
> Christer
>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>



-- 
Get the most comprehensive open source SIP testing framework at
http://sipper.agnity.com

------=_Part_54126_19317963.1225255556549
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>Maybe it warrants a separate thread but I would like to discuss section 7.1.3 of this draft where 3265 is talked about as an alternative. </div>
<div>Since&nbsp;we are talking about the notion of well defined info packages and the INFO messages </div>
<div>will carry information as a result of an event like an ISUP event or DTMF event (the name of the draft itself has &quot;event&quot; in it), then the two User Agents can very well subscribe to these events and use the notifications for the information exchange. </div>

<div>This will automatically inherit all the good work done around notification framework and will lay to rest lot of questions and perhaps save some re-invention. </div>
<div>&nbsp;</div>
<div>Regards</div>
<div>Nasir <br><br></div>
<div class="gmail_quote">On Mon, Oct 27, 2008 at 4:48 PM, Christer Holmberg <span dir="ltr">&lt;<a href="mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>Hi,<br>
<div class="Ih2E3d"><br>&gt;&gt;&gt;My preference would be for a new value, say &quot;package&quot;, &quot;info&quot;, or<br>&gt;&gt;&gt;&quot;info-package&quot;. I think we *might* be able to define that &quot;render&quot;<br>
&gt;&gt;&gt;serves this purpose *for INFO messages*, but I would rather not do<br>&gt;&gt;&gt;that because it is indeed asking from trouble and confusion.<br>&gt;&gt;<br>&gt;&gt;IF we define a new C-D value, which is unique for info packages, I<br>
have no problem with a C-D based solution.<br>&gt;<br>&gt;OK. That is progress!!!<br>&gt;<br>&gt;&gt;But, it would still be more work to define info packages, because you<br>&gt;&gt;would need to specify which C-T value to use.<br>
&gt;<br>&gt;The document already calls for this:<br>&gt;<br>&gt; &nbsp; &nbsp;<a href="http://7.2.4./" target="_blank">7.2.4.</a> &nbsp;INFO Bodies<br>&gt;<br>&gt; &nbsp; &nbsp;Each Info Package MUST define what type or types of bodies are<br>&gt; &nbsp; &nbsp;expected in INFO requests. &nbsp;Such packages MUST specify or cite<br>
&gt; &nbsp; &nbsp;detailed specifications for the syntax and semantics associated<br>with<br>&gt; &nbsp; &nbsp;such a body.<br>&gt;<br>&gt; &nbsp; &nbsp;Info Packages also MUST define a default MIME type if the &quot;Accept&quot;<br>&gt; &nbsp; &nbsp;header fails to define any MIME types in the INVITE request.<br>
<br></div>Yes, it&#39;s in the document. The point was that one may have to define<br>this new MIME type. But, maybe that is not a big problem (I haven&#39;t<br>defined mime types, so I can&#39;t tell).<br>
<div class="Ih2E3d"><br>&gt;The wording could be better. There are no explicit IANA considerations<br>about registering an INFO package. Its just implied here. Its a little<br>confusing here what is intended to be part of the<br>
&gt;*definition* of a new package vs. what is intended to be in the content<br>of a particular package instance in an INFO message.<br><br></div>We do need to have a section on what needs to be part of an info package<br>
definition. The mime type is one thing, for sure.<br><br>I guess we should also look at what/if we can re-use from SIP events.<br><br>We also need to decide whether info packages should have a version<br>number system. From experience I think that would be very useful.<br>
<br>Info-Package: foo-package;version=1<br><br>...or something like that.<br>
<div class="Ih2E3d"><br>&gt;&gt;My issue is if we want to re-use an existing value, because I don&#39;t<br>think we for sure can say that couldn&#39;t be a case where more than one<br>&gt;&gt;body part has a &quot;render&quot; value (or whatever existing value we would<br>
choose for info packages).<br>&gt;<br>&gt;This is all hypothetical, because we don&#39;t have any usages with the new<br>info package stuff.<br><br></div>Exactly.<br>
<div class="Ih2E3d"><br>&gt;What I guess you are getting at is if there are any existing uses of<br>body parts with &quot;render&quot; that might have to coexist with the info<br>package in the message.<br><br></div>Yes.<br>

<div class="Ih2E3d"><br>&gt;So I agree, we need a new value.<br><br></div>Good :)<br><br>Regards,<br><font color="#888888"><br>Christer<br></font>
<div>
<div></div>
<div class="Wj3C7c"><br>_______________________________________________<br>Sip mailing list &nbsp;<a href="https://www.ietf.org/mailman/listinfo/sip" target="_blank">https://www.ietf.org/mailman/listinfo/sip</a><br>This list is for NEW development of the core SIP Protocol<br>
Use <a href="mailto:sip-implementors@cs.columbia.edu">sip-implementors@cs.columbia.edu</a> for questions on current sip<br>Use <a href="mailto:sipping@ietf.org">sipping@ietf.org</a> for new developments on the application of sip<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Get the most comprehensive open source SIP testing framework at <a href="http://sipper.agnity.com">http://sipper.agnity.com</a><br>

------=_Part_54126_19317963.1225255556549--

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

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


From sip-bounces@ietf.org  Tue Oct 28 23:32:32 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 857643A6CCC;
	Tue, 28 Oct 2008 23:32:32 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A75F63A6CB4
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 23:32:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.931
X-Spam-Level: 
X-Spam-Status: No, score=-1.931 tagged_above=-999 required=5 tests=[AWL=0.668, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tvU5OoJ2mjAQ for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 23:32:31 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id A7FEB3A6CD4
	for <sip@ietf.org>; Tue, 28 Oct 2008 23:31:21 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K9H005BUM481X@siemenscomms.co.uk> for sip@ietf.org; Wed,
	29 Oct 2008 06:31:20 +0000 (GMT)
Date: Wed, 29 Oct 2008 06:31:18 +0000
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <490793BF.10702@softarmor.com>
To: Dean Willis <dean.willis@softarmor.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D001382975@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] Comment on DERIVE and B2BUAs
Thread-Index: Ack5TYw7YUWdxdBmSHO4RH2/xs6VjQAQlB3A
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
	<cc1f582e0810281052y34f5bf88h300c6f59d84879fe@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D00138295A@GBNTHT12009MSX.gb002.siemens.net>
	<490793BF.10702@softarmor.com>
Cc: sip@ietf.org
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 =


> -----Original Message-----
> From: Dean Willis [mailto:dean.willis@softarmor.com] =

> Sent: 28 October 2008 22:36
> To: Elwell, John
> Cc: I=F1aki Baz Castillo; sip@ietf.org
> Subject: Re: [Sip] Comment on DERIVE and B2BUAs
> =

> Elwell, John wrote:
> > =

> > IBC said:
> >> Since the B2BUA has detailed info of both legs A and B, it is
> >> capable of doing needed changes, as replacing call-id and to-tag in
> >> Event header. Also, the B2BUA could handle the SUBSCRIBE by its
> >> own, this is, becoming a dialog presence server instead of
> >> forwarding the SUBSCRIBE to the UA. B2BUA must handle all this
> >> stuff since they are, in fact, the end point, not the UA's behind
> >> them.
> >
> > [JRE] This reduces it to transitive trust, i.e., no better than
> > P-Asserted-Identity. The UA that receives the INVITE request has to
> > trust its local B2BUA to confirm that the INVITE request really did
> > come from the wherever it claimed to have come from.
> > =

> >
> =

> Since the INVITE is coming from the SBC (even though the SBC was
> influenced by something else to get it to send the INVITE), I =

> don't see
> a problem with this.
> =

> Otherwise said, SBCs are always transitive trust unless we have
> end-to-end crypto, in which case we don't really have SBCs.
[JRE] So we need to find a way of making e2e crypto work through SBCs.

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


From sip-bounces@ietf.org  Tue Oct 28 23:37:17 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 792153A6AAC;
	Tue, 28 Oct 2008 23:37:17 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8909F3A6AAE
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 23:37:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.065
X-Spam-Level: 
X-Spam-Status: No, score=-2.065 tagged_above=-999 required=5 tests=[AWL=0.534, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ynYuVzy9nm7D for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 23:37:14 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id A85153A6783
	for <sip@ietf.org>; Tue, 28 Oct 2008 23:37:14 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K9H00719ME13D@siemenscomms.co.uk> for sip@ietf.org; Wed,
	29 Oct 2008 06:37:13 +0000 (GMT)
Date: Wed, 29 Oct 2008 06:37:12 +0000
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <200810290236.m9T2aagI55951354@shell01.TheWorld.com>
To: Dale.Worley@comcast.net, sip@ietf.org
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D001382976@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] Comment on DERIVE and B2BUAs
Thread-Index: Ack5b4CMoGpREQqSRZy69pks0CAVlQAIJO9w
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
	<200810290236.m9T2aagI55951354@shell01.TheWorld.com>
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Dale.Worley@comcast.net
> Sent: 29 October 2008 02:37
> To: sip@ietf.org
> Subject: Re: [Sip] Comment on DERIVE and B2BUAs
> 
> 
>    From: "Elwell, John" <john.elwell@siemens.com>
> 
>    An interesting draft addressing a known problem space. Dan Wing has
>    already pointed out similarities with draft-wing-sip-e164-rrc (now
>    expired). I fear the present draft will not work in the presence of
>    B2BUAs along the path of the INVITE request, since these tend to
>    change things like call-ID, to-tag and from-tag. Since B2BUAs, and
>    SBCs in particular, are the main reasons why RFC 4474 will not
>    work, any solution has to be able to work through these devices.
> 
> However...  If we change the sequence of operations a bit, so that the
> UAS sends a 183 with a Contact carrying a specific header parameter
> carrying a crypto-random value, and we get B2BUAs to pass it through
> (attaching it to the Contact they use in the 183 they emit on the
> other side), then if the UAS does a non-filtered dialog event
> SUBSCRIBE, it can check the returned NOTIFY to see if it carries the
> Contact header parameter that it created.  That's a reasonably good
> test that the UAC of the INVITE can be reached via the From value that
> the UAS received.
[JRE] Unless a B2BUA fails to play according to the rules and
acknowledges the SUBSCRIBE without carrying out the same test on the
next hop. That is why we really need a cryptographic solution, so that
we can see for sure which domain is asserting that the identity is
correct.

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


From sip-bounces@ietf.org  Tue Oct 28 23:41:49 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 897423A6AAE;
	Tue, 28 Oct 2008 23:41:49 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 893BD3A6C9B
	for <sip@core3.amsl.com>; Tue, 28 Oct 2008 23:41:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.154
X-Spam-Level: 
X-Spam-Status: No, score=-2.154 tagged_above=-999 required=5 tests=[AWL=0.445, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9rKB5gC7l7Tq for <sip@core3.amsl.com>;
	Tue, 28 Oct 2008 23:41:47 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id A4A213A6AAC
	for <sip@ietf.org>; Tue, 28 Oct 2008 23:41:47 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K9H0070DMLMEJ@siemenscomms.co.uk> for sip@ietf.org; Wed,
	29 Oct 2008 06:41:46 +0000 (GMT)
Date: Wed, 29 Oct 2008 06:41:44 +0000
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <490792EA.2020106@softarmor.com>
To: Dean Willis <dean.willis@softarmor.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D001382978@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] Comment on DERIVE and B2BUAs
Thread-Index: Ack5TRLRw+oqogOqTj62eondS6t6fQAQU3eA
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
	<490792EA.2020106@softarmor.com>
Cc: sip@ietf.org
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 =


> -----Original Message-----
> From: Dean Willis [mailto:dean.willis@softarmor.com] =

> Sent: 28 October 2008 22:32
> To: Elwell, John
> Cc: Victor Pascual =C1vila; sip@ietf.org
> Subject: Re: [Sip] Comment on DERIVE and B2BUAs
> =

> Elwell, John wrote:
> > Viktor,
> > =

> > An interesting draft addressing a known problem space. Dan Wing has
> > already pointed out similarities with draft-wing-sip-e164-rrc (now
> > expired). I fear the present draft will not work in the presence of
> > B2BUAs along the path of the INVITE request, since these tend to
> > change things like call-ID, to-tag and from-tag. Since B2BUAs, and
> > SBCs in particular, are the main reasons why RFC 4474 will not work,
> > any solution has to be able to work through these devices.
> > =

> =

> Would the SBC not have to handle the SUBSCRIBE request locally? After
> all, since it is a terminal UA for the call, it also knows =

> about all the
> dialog states. The end-user UA would never even see the SUBSCRIBE.
> =

> So the SBC's lack of transparency on tags, etc. is irrelevant.
[JRE] Then we would only achieve confirmation of identity on the first hop =
(or hop-by-hop, if each B2BUA did it), resulting in transitive trust - no b=
etter than PAI.

John

> =

> --
> Dean
> =

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


From sip-bounces@ietf.org  Wed Oct 29 02:25:26 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C7E2428C2FA;
	Wed, 29 Oct 2008 02:25:26 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4E7063A69F5
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 02:25:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.385
X-Spam-Level: 
X-Spam-Status: No, score=-0.385 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3,
	MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id DWlUABd0o5F2 for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 02:25:17 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.239])
	by core3.amsl.com (Postfix) with ESMTP id A64163A694E
	for <sip@ietf.org>; Wed, 29 Oct 2008 02:25:16 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so3057430rvf.49
	for <sip@ietf.org>; Wed, 29 Oct 2008 02:25:12 -0700 (PDT)
Received: by 10.141.23.7 with SMTP id a7mr4765313rvj.5.1225272311780;
	Wed, 29 Oct 2008 02:25:11 -0700 (PDT)
Received: by 10.141.41.1 with HTTP; Wed, 29 Oct 2008 02:25:11 -0700 (PDT)
Message-ID: <cc1f582e0810290225j44b5075bsedc4148143c5046b@mail.gmail.com>
Date: Wed, 29 Oct 2008 10:25:11 +0100
From: "=?UTF-8?Q?I=C3=B1aki_Baz_Castillo?=" <ibc@aliax.net>
Cc: sip@ietf.org
In-Reply-To: <200810290236.m9T2asoN55836835@shell01.TheWorld.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <200810251926.17644.ibc@aliax.net> <490382B6.1090400@cisco.com>
	<200810252305.20030.ibc@aliax.net>
	<200810290236.m9T2asoN55836835@shell01.TheWorld.com>
Subject: Re: [Sip] [RFC 4235 & draft-kuthan-sip-derive] 481 "Call doesn't
	exist" for initial SUBSCRIBE ?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

MjAwOC8xMC8yOSAgPERhbGUuV29ybGV5QGNvbWNhc3QubmV0PjoKPiAgIEZyb206ID0/dXRmLTg/
cT9JPUMzPUIxYWtpX0Jhel9DYXN0aWxsbz89IDxpYmNAYWxpYXgubmV0Pgo+Cj4gICBJIHN1cHBv
c2UgNDA0IGlzIGFsc28gdW5hcHByb3BpYXRlLCBpc24ndD8KPgo+IEl0J3Mgbm90IGNsZWFyIHRv
IG1lIHJlYWRpbmcgUkZDIDQyMzUgdGhhdCBhIFNVQlNDUklCRSB3aXRoIGFuIEV2ZW50Cj4gaGVh
ZGVyIHRoYXQgc3BlY2lmaWVzIGEgQ2FsbC1JZCB0aGF0IGlzIHVua25vd24gdG8gdGhlIFVBUyB3
aWxsIHJlc3VsdAo+IGluIGEgZmFpbHVyZSByZXNwb25zZS4gIEl0IG1heSBvYnRhaW4gYSBOT1RJ
RlkgdGhhdCBsaXN0cyBubyBkaWFsb2dzLgoKSSBoYXZlIHRoZSBzYW1lIGRvdWJ0LiBUaGUgZHJh
ZnQgc3VnZ2VzdHMgIjQ4MSBDYWxsL1RyYW5zYWN0aW9uCmRvZXNuJ3QgZXhpc3QiIGJ1dCA0ODEg
aXMgc3VwcG9zZWQgZm9yIGluLWRpYWxvZyByZXF1ZXN0IG5vdCBtYXRjaGluZwphIHRyYW5zYWN0
aW9uIGluIHRoZSBVQVMgcmVjZWl2aW5nIGl0LgoKCj4gQnV0IGlmIGl0IGRvZXMgcmVjZWl2ZSBh
biBlcnJvciwgNDA0IHNlZW1zIHRoZSBtb3N0IGFwcHJvcHJpYXRlLgoKV2VsbCwgbm93IEkgZG9u
J3QgbGlrZSB0aGlzIGNvZGUuIE5vdGUgdGhhdCBhIFNVQlNDUklCRSdzIFJVUkkgaXMgbGlrZToK
ICBTVUJTQ1JJQkUgc2lwOmFsaWNlQGRvbWFpbi5vcmcgU0lQLzIuMAoKNDA0IHNob3VsZCBiZSBy
ZXBsaWVkIGJ5IGRvbWFpbi5vcmcgcHJveHkgaWYgaXQgZG9lc24ndCBrbm93IGEgbG9jYWwKdXNl
ciBjYWxsZWQgImFsaWNlIiAoNDgwIHdvdWxkIGJlIGluIGNhc2UgaXQgZXhpc3RzIGJ1dCBpcyBu
b3QKcmVnaXN0ZXJlZCBub3cpLgpTbywgaWYgdGhlIFNVQlNDUklCRSBhcnJpdmVzIHRvIHRoZSBV
QVMgYW5kIGl0IHJlcGxpZXMgd2l0aCA0MDQgaXQKd291bGQgYmUgc3RyYW5nZSwgd291bGRuJ3Qg
aXQ/CgoKPiBJbiBhbnkgY2FzZSwgZm9yIHRoZSBwdXJwb3NlcyBvZiBERVJJVkUsIG5vbmUgb2Yg
dGhhdCBtYXR0ZXJzOiAgQW55Cj4gZmFpbHVyZSByZXNwb25zZSB0byB0aGUgU1VCU0NSSUJFLCBv
ciBhIE5PVElGWSB0aGF0IGRvZXMgbm90IGxpc3QgdGhlCj4gY2FsbCBpbiBxdWVzdGlvbiwgcmVz
dWx0cyBpbiBjYWxsIHJlamVjdGlvbi4KCkJ1dCB0aGlzIGJlaGF2aW91ciB3b3VsZCBkZW55IGNh
bGxzIGZyb20gZGV2aWNlcyBub3Qgc3VwcG9ydGluZyBSRkMKNDIzNSAocmVjZWl2aW5nIGEgU1VC
U0NSSUJFIEV2ZW50OiBkaWFsb2cpLgpBRkFJSyB0aGlzIGRyYWZ0IHNheXMgdGhhdCBpZiB0aGUg
U1VCU0NSSUJFIGlzIHJlcGxpZWQgd2l0aCAyMDAgdGhlbgp0aGUgZGlhbG9nIGV4aXN0cyBhbmQg
aWRlbnRpdHkgdmVyaWZpZWQsIGlmIDQ4MSB0aGVuIHRoZSBkZXZpY2UKc3VwcG9ydHMgUkZDIDQy
MzUgYW5kIGl0J3MgYSBzdXNwaWNpdXMgY2FsbCwgYW5kIGZvciBhbnkgb3RoZXIgZmFpbHVyZQpy
b3V0ZSBpdCBjb3VsZCBtZWFuIHRoYXQgdGhlIGRldmljZSBkb2Vzbid0IHN1cHBvcnQgUkZDIDQy
MzUgb3IgYW55CmtpbmQgb2YgInByb3RlY3Rpb24iIGluIGFuIGludGVybWVkaWFyeSBwcm94eS4g
SW4gdGhlIGxhc3QgY2FzZSwgdGhlCnJlY2VwdG9yIG9mIHRoZSBJTlZJVEUgc2hvdWxkIGNob29z
ZSB0byBhY2NlcHQgb3IgZGVueSB0aGUgY2FsbCwgaGUKY2Fubm90IGtub3cgaWYgdGhlIHNlbmRl
ciBpcyByZWFsbHkgdGhlIEZyb20gKG9yIGlmIGhlIGlzIG5vdCkuCgoKLS0gCknDsWFraSBCYXog
Q2FzdGlsbG8KPGliY0BhbGlheC5uZXQ+Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fClNpcCBtYWlsaW5nIGxpc3QgIGh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vc2lwClRoaXMgbGlzdCBpcyBmb3IgTkVXIGRldmVsb3BtZW50IG9mIHRo
ZSBjb3JlIFNJUCBQcm90b2NvbApVc2Ugc2lwLWltcGxlbWVudG9yc0Bjcy5jb2x1bWJpYS5lZHUg
Zm9yIHF1ZXN0aW9ucyBvbiBjdXJyZW50IHNpcApVc2Ugc2lwcGluZ0BpZXRmLm9yZyBmb3IgbmV3
IGRldmVsb3BtZW50cyBvbiB0aGUgYXBwbGljYXRpb24gb2Ygc2lw


From sip-bounces@ietf.org  Wed Oct 29 04:16:02 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5599E3A68FB;
	Wed, 29 Oct 2008 04:16:02 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9BF133A6833
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 04:16:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.974
X-Spam-Level: 
X-Spam-Status: No, score=-1.974 tagged_above=-999 required=5 tests=[AWL=0.325, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LNVii1utzRZs for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 04:15:59 -0700 (PDT)
Received: from mail-gx0-f18.google.com (mail-gx0-f18.google.com
	[209.85.217.18])
	by core3.amsl.com (Postfix) with ESMTP id 4D1A03A68FB
	for <sip@ietf.org>; Wed, 29 Oct 2008 04:15:59 -0700 (PDT)
Received: by gxk11 with SMTP id 11so2548280gxk.13
	for <sip@ietf.org>; Wed, 29 Oct 2008 04:15:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=tmshfsJ1mg/FSknPHwlWm9o4xK2Tdxxq4hN0fkzUVtY=;
	b=VY26oRrRWtZJ3HuRZvlDcEk35flauIvREXamuAbQbNvzIn2wXqGAlKC9HNjYuUGwD9
	ZfCAufm1D4HRZitoXeYU1Gn0aMzpjlg54DWB+bKQZh6UHjNU0PmHk06TLaBPZ2/3+tT7
	v0/jggMryu2vZqW1Sb6qEopCOtU1OBNNkn7Go=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=L9QiKMRbR1TEN/9BPa7TiRxvzv3vscDIgD8l/pdUw+IyaPmifGEXsGlFZOsYax4FM7
	73TM/w4vrmos7nNT1HRz/cDaU/mcFcjeI2UR4+i5L/6TPSpRorcPx7gTW1CQLcfpiVLK
	DQnVvVuUOrqiWYN/HKm+BbehZaZYItjFK4F2A=
Received: by 10.90.90.4 with SMTP id n4mr3029594agb.93.1225278957643;
	Wed, 29 Oct 2008 04:15:57 -0700 (PDT)
Received: by 10.90.114.2 with HTTP; Wed, 29 Oct 2008 04:15:57 -0700 (PDT)
Message-ID: <618e24240810290415i7ede4601tf2fd78aaed755445@mail.gmail.com>
Date: Wed, 29 Oct 2008 12:15:57 +0100
From: "=?UTF-8?Q?Victor_Pascual_=C3=81vila?=" <victor.pascual.avila@gmail.com>
To: "Dan Wing" <dwing@cisco.com>
In-Reply-To: <032301c93978$6b249c70$c3f0200a@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>
	<200810261145.19745.ibc@aliax.net>
	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
	<084c01c938a0$a41ff390$c3f0200a@cisco.com>
	<cc1f582e0810280444y42b8f723w938004e902fb1180@mail.gmail.com>
	<032301c93978$6b249c70$c3f0200a@cisco.com>
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event
	foRIdentityVErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

SGkgRGFuLApQbGVhc2UsIHNlZSBteSBjb21tZW50cyBpbmxpbmUuCgpPbiBXZWQsIE9jdCAyOSwg
MjAwOCBhdCA0OjQyIEFNLCBEYW4gV2luZyA8ZHdpbmdAY2lzY28uY29tPiB3cm90ZToKPj4gMjAw
OC8xMC8yOCBEYW4gV2luZyA8ZHdpbmdAY2lzY28uY29tPjoKPj4gPiBIZXJlIGlzIGFub3RoZXIg
cmV0dXJuIHJvdXRhYmlsaXR5IGNoZWNrLAo+PiA+IGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1s
L2RyYWZ0LXdpbmctc2lwLWUxNjQtcnJjLTAxI3NlY3Rpb24tMy4xCj4+ID4gKE15IEktRCBleHBp
cmVkIGR1ZSB0byBsYWNrIG9mIGludGVyZXN0LikKPj4KPj4gSXQgdXNlcyBSRkMgNDQ3NCwgY2Vy
dGlmaWNhdGVzLi4uIGlzIGl0IHJlYWxseSBmZWFzaWJsZSBpbgo+PiB0aGlzIHJlYWwgd29ybGQ/
Cj4KPiBObywgaXQgZG9lc24ndCB1c2UgUkZDNDQ3NC4gIFRoZSBzdGVwcyBtZXJlbHkgc2hvdyB3
aGVyZSBhbiBSRkM0NDc0Cj4gc2lnbmF0dXJlIGNvdWxkIGJlIHBlcmZvcm1lZC4gIElmIG5vIFJG
QzQ0NzQgc2lnbmF0dXJlcyBhcmUKPiBiZWluZyBjcmVhdGVkLCBvciB2YWxpZGF0ZWQsIHRob3Nl
IHN0ZXBzIGFyZSB0aGUgJ251bGwgb3BlcmF0aW9uJwo+IChub3QgcGVyZm9ybWVkKS4gIFdpdGhv
dXQgdGhvc2Ugc3RlcHMsIGl0IGlzIHJlbWFya2FibHkgc2ltaWxhcgo+IHRvIERFUklWRS4KPgo+
PiBJTUhPICJEaWFsb2cgRXZlbnQgZm9SIElkZW50aXR5IFZFcmlmaWNhdGlvbiIgaXMgdGhlIG1v
cmUgZmVhc2libGUKPj4gc29sdXRpb24gYXQgdGhlIG1vbWVudC4KPgo+IFRoZSBkaWZmZXJlbmNl
cyBhcmUgbWlub3IuCgpUaGUgUmV0dXJuIFJvdXRhYmlsaXR5IENoZWNrIChSUkMpIGRldGVybWlu
ZXMgaWYgYSBkb21haW4gcmlnaHRmdWxseQonb3ducycgYW4gRS4xNjQgcGhvbmUgbnVtYmVyLCBi
dXQgRE9FUyBOT1QgcHJldmVudCBhbiBhdHRhY2tlciBmcm9tCnByZXNlbnRpbmcgYSBmb3JnZWQg
IkZyb20iIGhlYWRlciBmaWVsZC4KCkFzIGFuIGV4YW1wbGU6CgpJTlZJVEUgc2lwOnZpY3RvckB0
ZWtlbGVjLmNvbSBTSVAvMi4wCkZyb206ICsxNDA4NTU1MTIzNCA8c2lwOisxNDA4NTU1MTIzNEBp
cHRlbC5vcmc7dXNlcj1waG9uZT47dGFnPTlmeGNlZDc2c2wKVG86IFZpY3RvciA8c2lwOnZpY3Rv
ckB0ZWtlbGVjLmNvbT4KQ2FsbC1JRDogMzg0ODI3NjI5ODIyMDE4ODUxMUBpcHRlbC5vcmcKQ29u
dGFjdDogPHNpcDphdHRhY2tlckBwYzEuYXR0YWNrZXIuY29tPgpDb250ZW50LVR5cGU6IGFwcGxp
Y2F0aW9uL3NkcApDb250ZW50LUxlbmd0aDogLi4uCgpbU0RQIG5vdCBzaG93bl0KCldoZXJlIGlw
dGVsLm9yZyBvd25zIHRoZSArMTQwODU1NTEyMzQgbnVtYmVyLgoKU2VjdGlvbiAzLjI6Ci1UaGUg
U1VCU0NSSUJFIHNob3VsZCBiZSBpbW1lZGlhdGVseSBhY2tub3dsZWRnZWQKLUEgTk9USUZZIHNo
b3VsZCBiZSBpbW1lZGlhdGVseSBjcmVhdGVkIGFuZCBzZW50CgoKTW9yZW92ZXIgSU1POgotIGl0
IHJlcXVpcmVzIHRoZSB1c2Ugb2Ygc2lnbmF0dXJlcyAob3IgUkZDNDQ3NCk6IHNlZSBTZWN0aW9u
cyAzLCAzLjEgYW5kIDMuMgotIGl0IGlzIGRlZmluZWQgdG8gYmUgdXNlZCBvbmx5IHdpdGggZTE2
NC1iYXNlZCBTSVAgVVJJcwoKSW4gc2hvcnQsIHRoaXMgaXMgYSBnb29kIGRvY3VtZW50IGJ1dCwg
YXMgSSBtZW50aW9uZWQgYmVmb3JlLCBPTkxZCmRldGVybWluZXMgaWYgYSBkb21haW4gcmlnaHRm
dWxseSAnb3ducycgYW4gRS4xNjQgcGhvbmUgbnVtYmVyLCBpdApkb2Vzbid0IGFzayAiYXJlIHlv
dSBjYWxsaW5nIG1lPyIKClRoYW5rcyBhIGxvdCBmb3IgeW91ciBjb21tZW50cywKLS0gClZpY3Rv
ciBQYXNjdWFsIMOBdmlsYQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXwpTaXAgbWFpbGluZyBsaXN0ICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL3NpcApUaGlzIGxpc3QgaXMgZm9yIE5FVyBkZXZlbG9wbWVudCBvZiB0aGUgY29yZSBT
SVAgUHJvdG9jb2wKVXNlIHNpcC1pbXBsZW1lbnRvcnNAY3MuY29sdW1iaWEuZWR1IGZvciBxdWVz
dGlvbnMgb24gY3VycmVudCBzaXAKVXNlIHNpcHBpbmdAaWV0Zi5vcmcgZm9yIG5ldyBkZXZlbG9w
bWVudHMgb24gdGhlIGFwcGxpY2F0aW9uIG9mIHNpcA==


From sip-bounces@ietf.org  Wed Oct 29 06:58:22 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5DBD03A6CC2;
	Wed, 29 Oct 2008 06:58:22 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5CDAB3A6CC2
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 06:58:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.524
X-Spam-Level: 
X-Spam-Status: No, score=-5.524 tagged_above=-999 required=5
	tests=[AWL=-0.925, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4,
	SARE_HEXOCTDWORD=2]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id TKOtTpmJHh3v for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 06:58:20 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 0FCAC3A6AAF
	for <sip@ietf.org>; Wed, 29 Oct 2008 06:58:19 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,506,1220227200"; d="scan'208";a="26012074"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 29 Oct 2008 13:58:13 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9TDwDQ3001112; 
	Wed, 29 Oct 2008 09:58:13 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9TDwDN0014487;
	Wed, 29 Oct 2008 13:58:13 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 29 Oct 2008 09:58:08 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 29 Oct 2008 09:58:08 -0400
Message-ID: <49086BFA.9000305@cisco.com>
Date: Wed, 29 Oct 2008 09:58:18 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Nasir Khan <nkhan.sip@gmail.com>
References: <48FDEAD8.8010803@cisco.com>
	<4901D025.6060302@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>	<490239C8.3020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>	<4902467E.3010603@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFBA@esealmw113.eemea.ericsson.se>	<4905B23F.10609@cisco.com>
	<49060DD4.7070804@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF05C0F906@esealmw113.eemea.ericsson.se>
	<21964a950810282145t6950acdeo411824ec604cb219@mail.gmail.com>
In-Reply-To: <21964a950810282145t6950acdeo411824ec604cb219@mail.gmail.com>
X-OriginalArrivalTime: 29 Oct 2008 13:58:08.0571 (UTC)
	FILETIME=[5F8A38B0:01C939CE]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5293; t=1225288693;
	x=1226152693; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=3
	A=20Content-Type=20vs=09Info-Package=0A=20[was=20RE=3A=20dra
	ft-ietf-sip-info-events-00=3A=20multiple=09packages=20per=20
	INFO] |Sender:=20 |To:=20Nasir=20Khan=20<nkhan.sip@gmail.com>;
	bh=0BLXdyxIfxI9iWvl6tOWtb29B6Om+WAfZ3RzcK80xtY=;
	b=cgaGeWJ4yKxFcsXQJoyKqCWvZuLxm1lzqR4wls5CyHyr+O8q8/myB+AaB3
	258Ji49ZslLXOPHEE40+acp66gp1k41v+byRKuGfkRw5mEaKmaBGQbgPfEeN
	T/9o2yltSl;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Dean Willis <dean.willis@softarmor.com>,
	Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type
 vs	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple	packages
 per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I'm not certain I understand the point you are making.
Is it that we don't need info events because we could accomplish the 
same thing using subscriptions to suitable event packages?

If that is your point, we have been down that path already. Many of us 
have taken that position in the past (and may still believe it today), 
but there were many arguments that that approach is to heavy weight. 
Evidence of that is the continued use of info for DTMF even though we 
have an event package for that.

	Paul

Nasir Khan wrote:
> Maybe it warrants a separate thread but I would like to discuss section 
> 7.1.3 of this draft where 3265 is talked about as an alternative.
> Since we are talking about the notion of well defined info packages and 
> the INFO messages
> will carry information as a result of an event like an ISUP event or 
> DTMF event (the name of the draft itself has "event" in it), then the 
> two User Agents can very well subscribe to these events and use the 
> notifications for the information exchange.
> This will automatically inherit all the good work done around 
> notification framework and will lay to rest lot of questions and perhaps 
> save some re-invention.
>  
> Regards
> Nasir
> 
> On Mon, Oct 27, 2008 at 4:48 PM, Christer Holmberg 
> <christer.holmberg@ericsson.com <mailto:christer.holmberg@ericsson.com>> 
> wrote:
> 
> 
>     Hi,
> 
>      >>>My preference would be for a new value, say "package", "info", or
>      >>>"info-package". I think we *might* be able to define that "render"
>      >>>serves this purpose *for INFO messages*, but I would rather not do
>      >>>that because it is indeed asking from trouble and confusion.
>      >>
>      >>IF we define a new C-D value, which is unique for info packages, I
>     have no problem with a C-D based solution.
>      >
>      >OK. That is progress!!!
>      >
>      >>But, it would still be more work to define info packages, because you
>      >>would need to specify which C-T value to use.
>      >
>      >The document already calls for this:
>      >
>      >    7.2.4. <http://7.2.4./>  INFO Bodies
>      >
>      >    Each Info Package MUST define what type or types of bodies are
>      >    expected in INFO requests.  Such packages MUST specify or cite
>      >    detailed specifications for the syntax and semantics associated
>     with
>      >    such a body.
>      >
>      >    Info Packages also MUST define a default MIME type if the "Accept"
>      >    header fails to define any MIME types in the INVITE request.
> 
>     Yes, it's in the document. The point was that one may have to define
>     this new MIME type. But, maybe that is not a big problem (I haven't
>     defined mime types, so I can't tell).
> 
>      >The wording could be better. There are no explicit IANA considerations
>     about registering an INFO package. Its just implied here. Its a little
>     confusing here what is intended to be part of the
>      >*definition* of a new package vs. what is intended to be in the
>     content
>     of a particular package instance in an INFO message.
> 
>     We do need to have a section on what needs to be part of an info package
>     definition. The mime type is one thing, for sure.
> 
>     I guess we should also look at what/if we can re-use from SIP events.
> 
>     We also need to decide whether info packages should have a version
>     number system. From experience I think that would be very useful.
> 
>     Info-Package: foo-package;version=1
> 
>     ...or something like that.
> 
>      >>My issue is if we want to re-use an existing value, because I don't
>     think we for sure can say that couldn't be a case where more than one
>      >>body part has a "render" value (or whatever existing value we would
>     choose for info packages).
>      >
>      >This is all hypothetical, because we don't have any usages with
>     the new
>     info package stuff.
> 
>     Exactly.
> 
>      >What I guess you are getting at is if there are any existing uses of
>     body parts with "render" that might have to coexist with the info
>     package in the message.
> 
>     Yes.
> 
>      >So I agree, we need a new value.
> 
>     Good :)
> 
>     Regards,
> 
>     Christer
> 
>     _______________________________________________
>     Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>     This list is for NEW development of the core SIP Protocol
>     Use sip-implementors@cs.columbia.edu
>     <mailto:sip-implementors@cs.columbia.edu> for questions on current sip
>     Use sipping@ietf.org <mailto:sipping@ietf.org> for new developments
>     on the application of sip
> 
> 
> 
> 
> -- 
> Get the most comprehensive open source SIP testing framework at 
> http://sipper.agnity.com
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct 29 07:02:04 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CA3213A6D1A;
	Wed, 29 Oct 2008 07:02:04 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DAD223A6D1F
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 07:02:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id C2EMfqPVmZWn for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 07:01:58 -0700 (PDT)
Received: from exprod6og116.obsmtp.com (exprod6og116.obsmtp.com [64.18.1.37])
	by core3.amsl.com (Postfix) with ESMTP id 99F6428C36B
	for <sip@ietf.org>; Wed, 29 Oct 2008 07:01:19 -0700 (PDT)
Received: from source ([192.150.8.22]) by exprod6ob116.postini.com
	([64.18.5.12]) with SMTP; Wed, 29 Oct 2008 07:01:20 PDT
Received: from inner-relay-1.corp.adobe.com ([153.32.1.51])
	by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	m9TE0jE0008723; Wed, 29 Oct 2008 07:00:46 -0700 (PDT)
Received: from apacmail.pac.adobe.com (apacmail.pac.adobe.com [130.248.36.99])
	by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	m9TE0diq015301; Wed, 29 Oct 2008 07:00:40 -0700 (PDT)
Received: from namail5.corp.adobe.com ([10.8.192.88]) by
	apacmail.pac.adobe.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 29 Oct 2008 23:00:38 +0900
Received: from 10.7.241.174 ([10.7.241.174]) by namail5.corp.adobe.com
	([10.8.192.88]) with Microsoft Exchange Server HTTP-DAV ; 
	Wed, 29 Oct 2008 14:00:36 +0000
User-Agent: Microsoft-Entourage/12.13.0.080930
Date: Wed, 29 Oct 2008 09:00:36 -0500
From: Henry Sinnreich <hsinnrei@adobe.com>
To: Dan Wing <dwing@Cisco.COM>, <Dale.Worley@comcast.net>, <sip@ietf.org>
Message-ID: <C52DD6B4.96A9%hsinnrei@adobe.com>
Thread-Topic: [Sip] submission of a new I-D: "Dialog Event foR
	IdentityVErification"
Thread-Index: Ack5b20FZ3GeTM5zTlGiZA+VDSiCrQACXFxwABV2PU4=
In-Reply-To: <033d01c93979$b3cf1990$c3f0200a@cisco.com>
Mime-version: 1.0
X-OriginalArrivalTime: 29 Oct 2008 14:00:38.0919 (UTC)
	FILETIME=[B9278170:01C939CE]
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR
 IdentityVErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

> Such a return routability check is probably the best SIP can do in the
> presence of SBCs and the inability to get
> draft-fischer-sip-e2e-sec-media-01.txt or draft-wing-sip-identity-media-03.txt
> off the ground.
> 
> -d

I believe this sums it up; correct and balanced.

Henry


On 10/28/08 10:52 PM, "Dan Wing" <dwing@Cisco.COM> wrote:

>> With SIP, you don't know that the originating UAS has the same name as
>> it is claiming to have, because you got the SIP message from some
>> nearby proxy.  DERIVE is more like doing a reverse DNS lookup to see
>> if the originating host has the name that it claims to have.
> 
> Yeah, that's walking the DNS tree.  It is valuable; heck, IETF's own
> mailservers are doing it to reduce spam so it Must Be Good!  :-)
> 
> DERIVE is checking to see if your SIP routing takes you to the
> same place that (claims to) be originating the incoming INVITE.
> It is using your *outgoing* SIP routing -- which you must already
> trust to send outbound messages -- to test the validity of the
> (proported) From: address of an incoming INVITE.
> 
> 
> Such a return routability check is probably the best SIP can do in the
> presence of SBCs and the inability to get
> draft-fischer-sip-e2e-sec-media-01.txt or draft-wing-sip-identity-media-03.txt
> off the ground.
> 
> -d
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip

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


From sip-bounces@ietf.org  Wed Oct 29 10:06:23 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 84DE83A6841;
	Wed, 29 Oct 2008 10:06:23 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 282373A681B
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 10:06:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.598
X-Spam-Level: 
X-Spam-Status: No, score=-1.598 tagged_above=-999 required=5 tests=[AWL=1.000, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OwOCMkYcvHmM for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 10:06:21 -0700 (PDT)
Received: from mail-gx0-f18.google.com (mail-gx0-f18.google.com
	[209.85.217.18])
	by core3.amsl.com (Postfix) with ESMTP id C4DAE3A635F
	for <sip@ietf.org>; Wed, 29 Oct 2008 10:06:20 -0700 (PDT)
Received: by gxk11 with SMTP id 11so3063746gxk.13
	for <sip@ietf.org>; Wed, 29 Oct 2008 10:06:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:mime-version:content-type;
	bh=+A8WGfOaaRViDaA2fGlPBaOcQvbAAIvKoN8DFueqito=;
	b=KYkWGt1NmtkBRyBBgJEC+ivyh//T0bg9hBmsjRz7LoxGak9pRU9q2sdGbEB64dAL5h
	OznF7bqbj5lvpvw5ca9/msrYP8GXWF1J6oQRxv9pEnHeuKQp82h8pPNyIVcj4ezYO6px
	rY71cwQD3cWzq0wCwUCyCy2wY/Vv5h7cT5w4Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:mime-version:content-type;
	b=TroVMlc9zRMoqT9zaiOMB1ycQGOwk1z6wdfXh4+5Md2bAzgWvo7pmuj6njNOia4fm2
	9zgY0onTzoKBcST2DwoaDrOrl2hz/fb4yymB82HUYB/FCGlzxZHS+r9rigZHJoDQL7xS
	6k0fKDgp/axtCs8b5zlcuPsrwSoIvF4H3da70=
Received: by 10.142.199.16 with SMTP id w16mr4133584wff.268.1225299978292;
	Wed, 29 Oct 2008 10:06:18 -0700 (PDT)
Received: by 10.142.105.18 with HTTP; Wed, 29 Oct 2008 10:06:18 -0700 (PDT)
Message-ID: <21964a950810291006i6940f9fdi1f5fcf05a28a307d@mail.gmail.com>
Date: Wed, 29 Oct 2008 13:06:18 -0400
From: "Nasir Khan" <nkhan.sip@gmail.com>
To: "SIP IETF" <sip@ietf.org>
MIME-Version: 1.0
Subject: [Sip] draft-ietf-sip-info-events-00 using RFC 3265 instead
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1317946497=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

--===============1317946497==
Content-Type: multipart/alternative; 
	boundary="----=_Part_64627_5725844.1225299978281"

------=_Part_64627_5725844.1225299978281
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

[Per Keith's suggestion starting a new thread, copied from last one]

Yes Paul, that is what I was trying to get at.
Sorry if all this was already discussed and closed.
Do we have a comaparitive between the two approaches from past?

The reason I brought it out was that there are several similarities in where
we are going with info events and 3265.

 I hope we do not undermine the usage of SIP events.
As an example if one comes up with a brand new application that has some
small data to be transferred between UAs and the session is INVITE based
then which approach should one take? Will we have clear guidelines or leave
it open?
IMHO overlapping semantics is also not very good for interoperability.

Is the legacy (mis)use of INFO the most compelling reason for this approach
of bringing it into proper framework?

again apologies for repetition.

regards
nasir



-------------------------------
I'm not certain I understand the point you are making.
Is it that we don't need info events because we could accomplish the same
thing using subscriptions to suitable event packages?

If that is your point, we have been down that path already. Many of us have
taken that position in the past (and may still believe it today), but there
were many arguments that that approach is to heavy weight. Evidence of that
is the continued use of info for DTMF even though we have an event package
for that.

       Paul

Nasir Khan wrote:

Maybe it warrants a separate thread but I would like to discuss section
7.1.3 of this draft where 3265 is talked about as an alternative.
Since we are talking about the notion of well defined info packages and the
INFO messages
will carry information as a result of an event like an ISUP event or DTMF
event (the name of the draft itself has "event" in it), then the two User
Agents can very well subscribe to these events and use the notifications for
the information exchange.
This will automatically inherit all the good work done around notification
framework and will lay to rest lot of questions and perhaps save some
re-invention.
 Regards
Nasir

-- 
Get the most comprehensive open source SIP application testing framework at
http://sipper.agnity.com

------=_Part_64627_5725844.1225299978281
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>[Per Keith&#39;s suggestion starting a new thread, copied from last one]</div>
<div>&nbsp;</div>
<div>Yes Paul, that is what I was trying to get at. </div>
<div>Sorry if all this was already discussed and closed. </div>
<div>Do we have a comaparitive between the two approaches&nbsp;from past? </div>
<div>&nbsp;</div>
<div>The reason I brought it out was that there are several similarities in where we are going with info events and 3265.</div>
<div>&nbsp;</div>
<div>
<div>I hope we do not undermine the usage of SIP events. </div>
<div>As an example if one comes up with a brand new application that has some small data to be transferred between UAs and the session is INVITE based then which approach should one take? Will we have clear guidelines or leave it open? </div>

<div>IMHO overlapping semantics is also not very good for interoperability. </div>
<div>&nbsp;</div></div>
<div>Is the legacy (mis)use of INFO the most compelling reason for this approach of bringing it into proper framework? </div>
<div>&nbsp;</div>
<div>again apologies for repetition. </div>
<div>&nbsp;</div>
<div>regards</div>
<div>nasir </div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>-------------------------------</div>
<div>I&#39;m not certain I understand the point you are making.<br>Is it that we don&#39;t need info events because we could accomplish the same thing using subscriptions to suitable event packages?</div>
<p>If that is your point, we have been down that path already. Many of us have taken that position in the past (and may still believe it today), but there were many arguments that that approach is to heavy weight. Evidence of that is the continued use of info for DTMF even though we have an event package for that.</p>

<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Paul</p>
<p>Nasir Khan wrote:</p>
<p>Maybe it warrants a separate thread but I would like to discuss section 7.1.3 of this draft where 3265 is talked about as an alternative.<br>Since we are talking about the notion of well defined info packages and the INFO messages<br>
will carry information as a result of an event like an ISUP event or DTMF event (the name of the draft itself has &quot;event&quot; in it), then the two User Agents can very well subscribe to these events and use the notifications for the information exchange.<br>
This will automatically inherit all the good work done around notification framework and will lay to rest lot of questions and perhaps save some re-invention.<br>&nbsp;Regards<br>Nasir<br clear="all"><br>-- <br>Get the most comprehensive open source SIP application testing framework at <a href="http://sipper.agnity.com/" target="_blank">http://sipper.agnity.com</a><br>
</p>

------=_Part_64627_5725844.1225299978281--

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

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


From sip-bounces@ietf.org  Wed Oct 29 10:56:56 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BC9BF3A6C73;
	Wed, 29 Oct 2008 10:56:56 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 71A533A6C6E
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 10:56:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.339
X-Spam-Level: 
X-Spam-Status: No, score=-6.339 tagged_above=-999 required=5 tests=[AWL=0.260, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id MbMbYwVe1BAM for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 10:56:54 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 112743A68C1
	for <sip@ietf.org>; Wed, 29 Oct 2008 10:56:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,507,1220227200"; d="scan'208";a="26083033"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 29 Oct 2008 17:56:46 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9THukCw023499; 
	Wed, 29 Oct 2008 13:56:46 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9THuk0s026387;
	Wed, 29 Oct 2008 17:56:46 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 29 Oct 2008 13:56:45 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 29 Oct 2008 13:56:45 -0400
Message-ID: <4908A3D8.6020104@cisco.com>
Date: Wed, 29 Oct 2008 13:56:40 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Nasir Khan <nkhan.sip@gmail.com>
References: <21964a950810291006i6940f9fdi1f5fcf05a28a307d@mail.gmail.com>
In-Reply-To: <21964a950810291006i6940f9fdi1f5fcf05a28a307d@mail.gmail.com>
X-OriginalArrivalTime: 29 Oct 2008 17:56:45.0725 (UTC)
	FILETIME=[B53A8CD0:01C939EF]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3283; t=1225303006;
	x=1226167006; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20draft-ietf-sip-info-events-00=2
	0using=20RFC=203265=20instead |Sender:=20
	|To:=20Nasir=20Khan=20<nkhan.sip@gmail.com>;
	bh=FneUuC/3z2N+JiGuf3MTWgM1/YGCAPKjoPAItPtG3X0=;
	b=oolEfMm3j3sJ9hLhJKfp1W4f55vAs3lLCDhiH24AQDi+SBL1oTOtOZvQhg
	eoDzawKU5PhREpk/I8QXK2HdAkCWxSDugA98YEbcTacN71Fcr+K4bDOxkZqS
	hkoi2uzLr/;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] draft-ietf-sip-info-events-00 using RFC 3265 instead
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I will try to summarize the essence of the arguments:

Establishing the subscription requires more messages to be exchanged.

The subscription then requires state to be maintained, and it must be 
refreshed periodically.

The desired uses of info are often things that *might* be exchanged on 
any call, but often (usually?) are not. So paying a lot of cost for the 
possibility is thought to be a bad deal.

	Thanks,
	Paul

Nasir Khan wrote:
> [Per Keith's suggestion starting a new thread, copied from last one]
>  
> Yes Paul, that is what I was trying to get at.
> Sorry if all this was already discussed and closed.
> Do we have a comaparitive between the two approaches from past?
>  
> The reason I brought it out was that there are several similarities in 
> where we are going with info events and 3265.
>  
> I hope we do not undermine the usage of SIP events.
> As an example if one comes up with a brand new application that has some 
> small data to be transferred between UAs and the session is INVITE based 
> then which approach should one take? Will we have clear guidelines or 
> leave it open?
> IMHO overlapping semantics is also not very good for interoperability.
>  
> Is the legacy (mis)use of INFO the most compelling reason for this 
> approach of bringing it into proper framework?
>  
> again apologies for repetition.
>  
> regards
> nasir
>  
>  
>  
> -------------------------------
> I'm not certain I understand the point you are making.
> Is it that we don't need info events because we could accomplish the 
> same thing using subscriptions to suitable event packages?
> 
> If that is your point, we have been down that path already. Many of us 
> have taken that position in the past (and may still believe it today), 
> but there were many arguments that that approach is to heavy weight. 
> Evidence of that is the continued use of info for DTMF even though we 
> have an event package for that.
> 
>        Paul
> 
> Nasir Khan wrote:
> 
> Maybe it warrants a separate thread but I would like to discuss section 
> 7.1.3 of this draft where 3265 is talked about as an alternative.
> Since we are talking about the notion of well defined info packages and 
> the INFO messages
> will carry information as a result of an event like an ISUP event or 
> DTMF event (the name of the draft itself has "event" in it), then the 
> two User Agents can very well subscribe to these events and use the 
> notifications for the information exchange.
> This will automatically inherit all the good work done around 
> notification framework and will lay to rest lot of questions and perhaps 
> save some re-invention.
>  Regards
> Nasir
> 
> -- 
> Get the most comprehensive open source SIP application testing framework 
> at http://sipper.agnity.com <http://sipper.agnity.com/>
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct 29 11:25:50 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9CBB328C3A0;
	Wed, 29 Oct 2008 11:25:50 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AECBA28C3A0
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 11:25:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ja3eBJo8gHdR for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 11:25:47 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net
	[IPv6:2001:470:1f03:267::2])
	by core3.amsl.com (Postfix) with ESMTP id 3063528C186
	for <sip@ietf.org>; Wed, 29 Oct 2008 11:25:45 -0700 (PDT)
Received: from dn3-231.estacado.net (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.14.3/8.14.1) with ESMTP id m9TIPdoK013290
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 29 Oct 2008 13:25:39 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <4908AAA3.1030800@nostrum.com>
Date: Wed, 29 Oct 2008 13:25:39 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
References: <21964a950810291006i6940f9fdi1f5fcf05a28a307d@mail.gmail.com>
	<4908A3D8.6020104@cisco.com>
In-Reply-To: <4908A3D8.6020104@cisco.com>
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Virus-Scanned: ClamAV 0.94/8537/Wed Oct 29 08:26:33 2008 on
	shaman.nostrum.com
X-Virus-Status: Clean
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] draft-ietf-sip-info-events-00 using RFC 3265 instead
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

So, draft-burger-sip-info-02 went over some of the comparisons between 
3265 and INFO packages. Perhaps we can head off future confusion by 
merging even more 3265-related text from that document into the 
info-packages document.

To address Nasir's comments on a more practical level: currently, INFO 
is so underspecified that every additional use causes harm to the entire 
SIP protocol by introducing new incompatibilities. We can either 
deprecate the use of INFO (and be soundly ignored by implementors all 
over the world), or we can try to reform INFO to be a (somewhat) 
upstanding member of the SIP method pantheon.

And until we do so, we're going to burn unwarranted quantities of time 
arguing about the open festering sore that is INFO.

/a


On 10/29/08 12:56 PM, Paul Kyzivat wrote:
> I will try to summarize the essence of the arguments:
>
> Establishing the subscription requires more messages to be exchanged.
>
> The subscription then requires state to be maintained, and it must be 
> refreshed periodically.
>
> The desired uses of info are often things that *might* be exchanged on 
> any call, but often (usually?) are not. So paying a lot of cost for 
> the possibility is thought to be a bad deal.
>
>     Thanks,
>     Paul
>
> Nasir Khan wrote:
>> [Per Keith's suggestion starting a new thread, copied from last one]
>>  
>> Yes Paul, that is what I was trying to get at.
>> Sorry if all this was already discussed and closed.
>> Do we have a comaparitive between the two approaches from past?
>>  
>> The reason I brought it out was that there are several similarities 
>> in where we are going with info events and 3265.
>>  
>> I hope we do not undermine the usage of SIP events.
>> As an example if one comes up with a brand new application that has 
>> some small data to be transferred between UAs and the session is 
>> INVITE based then which approach should one take? Will we have clear 
>> guidelines or leave it open?
>> IMHO overlapping semantics is also not very good for interoperability.
>>  
>> Is the legacy (mis)use of INFO the most compelling reason for this 
>> approach of bringing it into proper framework?
>>  
>> again apologies for repetition.
>>  
>> regards
>> nasir
>>  
>>  
>>  
>> -------------------------------
>> I'm not certain I understand the point you are making.
>> Is it that we don't need info events because we could accomplish the 
>> same thing using subscriptions to suitable event packages?
>>
>> If that is your point, we have been down that path already. Many of 
>> us have taken that position in the past (and may still believe it 
>> today), but there were many arguments that that approach is to heavy 
>> weight. Evidence of that is the continued use of info for DTMF even 
>> though we have an event package for that.
>>
>>        Paul
>>
>> Nasir Khan wrote:
>>
>> Maybe it warrants a separate thread but I would like to discuss 
>> section 7.1.3 of this draft where 3265 is talked about as an 
>> alternative.
>> Since we are talking about the notion of well defined info packages 
>> and the INFO messages
>> will carry information as a result of an event like an ISUP event or 
>> DTMF event (the name of the draft itself has "event" in it), then the 
>> two User Agents can very well subscribe to these events and use the 
>> notifications for the information exchange.
>> This will automatically inherit all the good work done around 
>> notification framework and will lay to rest lot of questions and 
>> perhaps save some re-invention.
>>  Regards
>> Nasir
>>
>> -- 
>> Get the most comprehensive open source SIP application testing 
>> framework at http://sipper.agnity.com <http://sipper.agnity.com/>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sipping@ietf.org for new developments on the application of sip
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip

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


From sip-bounces@ietf.org  Wed Oct 29 11:45:39 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9DC653A6B08;
	Wed, 29 Oct 2008 11:45:39 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A2BE03A6818
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 11:45:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5
	tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KgPVXITRIRfM for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 11:45:28 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id A3E903A6B34
	for <sip@ietf.org>; Wed, 29 Oct 2008 11:45:28 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,507,1220227200"; d="scan'208";a="97660026"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-1.cisco.com with ESMTP; 29 Oct 2008 18:44:53 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9TIirgj022157; 
	Wed, 29 Oct 2008 11:44:53 -0700
Received: from dwingwxp01 (dhcp-128-107-114-36.cisco.com [128.107.114.36])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9TIirBS027553;
	Wed, 29 Oct 2008 18:44:53 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "=?iso-8859-1?Q?'Victor_Pascual_=C1vila'?="
	<victor.pascual.avila@gmail.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>
	<200810261145.19745.ibc@aliax.net>
	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
	<084c01c938a0$a41ff390$c3f0200a@cisco.com>
	<cc1f582e0810280444y42b8f723w938004e902fb1180@mail.gmail.com>
	<032301c93978$6b249c70$c3f0200a@cisco.com>
	<618e24240810290415i7ede4601tf2fd78aaed755445@mail.gmail.com>
Date: Wed, 29 Oct 2008 11:44:54 -0700
Message-ID: <007b01c939f6$6f33e5e0$24726b80@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Ack5t7eqvsEFA64yQGajGAp6h2A1tAAOorZw
In-Reply-To: <618e24240810290415i7ede4601tf2fd78aaed755445@mail.gmail.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4565; t=1225305893;
	x=1226169893; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[Sip]=20submission=20of=20a=20new=20I-D
	=3A=20=22Dialog=20Event=20foRIdentityVErification=22
	|Sender:=20; bh=mGNqNaWk6o3pid2pfB1tZWFHFAFBZsdypkhHvThoVCk=;
	b=ZBBXjciWz4Ca4IU3+GwGzk+VHCikzVbbmzkBCzW0hg8YSA9rnndYY5RWtV
	xiLdqzEBXTN0F/CaPurtqHHUSSAWDHkKPewtN3u5rFc5c6BNcTJX2Sw+Ts51
	jC/on4vxck;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event
	foRIdentityVErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 =


> -----Original Message-----
> From: Victor Pascual =C1vila [mailto:victor.pascual.avila@gmail.com] =

> Sent: Wednesday, October 29, 2008 4:16 AM
> To: Dan Wing
> Cc: sip@ietf.org
> Subject: Re: [Sip] submission of a new I-D: "Dialog Event =

> foRIdentityVErification"
> =

> Hi Dan,
> Please, see my comments inline.
> =

> On Wed, Oct 29, 2008 at 4:42 AM, Dan Wing <dwing@cisco.com> wrote:
> >> 2008/10/28 Dan Wing <dwing@cisco.com>:
> >> > Here is another return routability check,
> >> > http://tools.ietf.org/html/draft-wing-sip-e164-rrc-01#section-3.1
> >> > (My I-D expired due to lack of interest.)
> >>
> >> It uses RFC 4474, certificates... is it really feasible in
> >> this real world?
> >
> > No, it doesn't use RFC4474.  The steps merely show where an RFC4474
> > signature could be performed.  If no RFC4474 signatures are
> > being created, or validated, those steps are the 'null operation'
> > (not performed).  Without those steps, it is remarkably similar
> > to DERIVE.
> >
> >> IMHO "Dialog Event foR Identity VErification" is the more feasible
> >> solution at the moment.
> >
> > The differences are minor.
> =

> The Return Routability Check (RRC) determines if a domain rightfully
> 'owns' an E.164 phone number, but DOES NOT prevent an attacker from
> presenting a forged "From" header field.
> =

> As an example:
> =

> INVITE sip:victor@tekelec.com SIP/2.0
> From: +14085551234 =

> <sip:+14085551234@iptel.org;user=3Dphone>;tag=3D9fxced76sl
> To: Victor <sip:victor@tekelec.com>
> Call-ID: 3848276298220188511@iptel.org
> Contact: <sip:attacker@pc1.attacker.com>
> Content-Type: application/sdp
> Content-Length: ...
> =

> [SDP not shown]
> =

> Where iptel.org owns the +14085551234 number.
> =

> Section 3.2:
> -The SUBSCRIBE should be immediately acknowledged
> -A NOTIFY should be immediately created and sent
> =

> =

> Moreover IMO:
> - it requires the use of signatures (or RFC4474): see =

> Sections 3, 3.1 and 3.2

As I said previously:  if there is no signature service, this is the null
operation.  The UA is competely incapable of causing or forcing its domain =
to
generate an RFC4474 signature, anyway, so it's impossible for a UA to
'require' such a signature.

> - it is defined to be used only with e164-based SIP URIs
> =

> In short, this is a good document but, as I mentioned before, ONLY
> determines if a domain rightfully 'owns' an E.164 phone number, it
> doesn't ask "are you calling me?"

Easily added; draft-wing-sip-e164-rrc-01 currently reads:

   3.2.  Authentication Service or Calling Endpoint Operation

   The steps described in this section can be performed by the
   authentication service or by the calling endpoint.

   The authentication service or the calling endpoint, upon receiving a
   SUBSCRIBE for the return-routability event package, performs the
   following steps:

   1.   The SUBSCRIBE should be immediately acknowledged with a 200 Ok
       ^
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   INSERT "If there is another active INVITE dialog, which has not =

           received its 200 Ok, then"

       message.
                ^
      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      INSERT "If there is not another active INVITE dialog, an error
        response is sent (e.g., 4xx), and processing stops."

   2.  A NOTIFY should be immediately created, containing the same
       application/return-routability-nonce copied from the SUBSCRIBE.
       This NOTIFY contains a To and Request-URI which match the From of
       the SUBSCRIBE.

   3.  This NOTIFY is sent.

   4.  The RFC4474 authentication service, operating at the domain, will
       create a signature over the NOTIFY.  This is used by the remote
       domain's verification service (see Section 3.1).


I'm not interested in having a competing proposal, though, or arguing
nits about which 4xx response code is most appropriate.

We should be arguing about larger issues, such as the value of proving =

someone is actually originating a call.  Without that, we cannot have =

reliable whitelists or reliably blacklists, which are the foundations =

for authorizing incoming SIP requests.

I support draft-kuthan-sip-derive-00, and hope the WG can devote
time and energy to improving and standardizing it to work well
across a variety of networks.

-d

> Thanks a lot for your comments,
> -- =

> Victor Pascual =C1vila
> =


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


From sip-bounces@ietf.org  Wed Oct 29 12:48:22 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 05CA23A684D;
	Wed, 29 Oct 2008 12:48:22 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1502F3A684D
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 12:48:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.32
X-Spam-Level: 
X-Spam-Status: No, score=-5.32 tagged_above=-999 required=5 tests=[AWL=0.929, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id GDfRuRfAvsuR for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 12:48:20 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id C05993A67AC
	for <sip@ietf.org>; Wed, 29 Oct 2008 12:48:19 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	3EBE120B6C; Wed, 29 Oct 2008 20:47:23 +0100 (CET)
X-AuditID: c1b4fb3c-ad8cdbb0000015b5-7e-4908bdcbebc9
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	08D4620A52; Wed, 29 Oct 2008 20:47:23 +0100 (CET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 29 Oct 2008 20:47:13 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 29 Oct 2008 20:46:56 +0100
Received: from [131.160.126.26] (rvi2-126-26.lmf.ericsson.se [131.160.126.26])
	by mail.lmf.ericsson.se (Postfix) with ESMTP id C5A1F245F;
	Wed, 29 Oct 2008 21:46:55 +0200 (EET)
Message-ID: <4908BDAF.8080900@ericsson.com>
Date: Wed, 29 Oct 2008 21:46:55 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: sip@ietf.org
References: <BF4D24CF-D537-4476-87D2-8E30B8462B95@softarmor.com>	<200810200250.m9K2oifX50014113@shell01.TheWorld.com>
	<48FEE01A.90305@ericsson.com>
In-Reply-To: <48FEE01A.90305@ericsson.com>
X-OriginalArrivalTime: 29 Oct 2008 19:46:56.0118 (UTC)
	FILETIME=[19547960:01C939FF]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] So where are we at with WGLC
	of	draft-ietf-sip-body-handling?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi,

I have revised the draft per my email below. The new rules (per our 
mailing list discussions) can be found on Section 7.2:

http://www.ietf.org/internet-drafts/draft-ietf-sip-body-handling-04.txt

Cheers,

Gonzalo

Gonzalo Camarillo wrote:
> Hi Dale,
> 
> thanks for all your comments and for putting your time on analyzing
> these issues. Let's agree on how to resolve the open issues, which you
> list below in your summary:
> 
>> There is an open discussion point on the precise semantics of 
>> 'required' -- in the SIP context, it is probably more convenient to 
>> mean "required for processing of the containing body part", but in
>> the e-mail gateway context, it is used to mean "required for the
>> overall message to be processed".  (The two are equivalent for
>> non-nested multiparts.)
> 
> yes, the current I-D specifies the latter; what has been called "global"
> in the email threads. The idea was to be consistent with email. However,
> I agree with the conclusions of the email discussions. That is, using
> the "local" approach probably makes more sense in a SIP context.
> 
> So, if nobody objects, I suggest we specify the following:
> 
> multipart/mixed:
> 
> o the handling of a multipart/mixed is 'required' if its processing as a
> whole is required.
> 
> o the handling parameter of a given component inside the multipart/mixed
> is set regardless of the handling parameter of the multipart/mixed.
> 
>   This rules means that we can have an optional multipart/mixed that has
>   required parts in it. *If* and only if the processor decides to
>   process the multipart/mixed, then it needs to process the required
>   parts.
> 
>   It can also happen that we have a required multipart/mixed with all
>   its components being optional. This is not a big deal. The only thing
>   that could happen is that the processor decides to process the
>   multipart/mixed and then it decides not to process any of its parts.
>   This of course relates to Paul's point on what it takes to process a
>   body part.
> 
> 
> multipart/alternative:
> 
> o the handling of a multipart/alternative is 'required' if its
> processing as a whole is required.
> 
> o the handling parameter of a given component inside the
> multipart/alternative is irrelevant. We can still recommend that it is
> set to optional.
> 
>   This rules means that now the multipart/alternative can contain
>   multipart/mixed parts that contain required components. This was not
>   possible with the rules in the current I-D.
> 
> multipart/related:
> 
> o the handling of a multipart/related is 'required' if its processing as
>   a whole is required.
> 
> o the handling of the root element within a multipart/related should
>   probably always be required. However, since we support required
>   multipart/mixed bodies with only optional components, I suggest we do
>   not bother specifying anything here.
> 
> 
>> My elaborate algorithm is, IMHO, a direct expression of the rules in 
>> the I-D, although I've probably added some "it could only mean this" 
>> assumptions which should be made explicit.  Whether the algorithm 
>> itself is given in the I-D is a presentation issue.
> 
> I tend to agree with others in that I prefer a declarative
> specification. My suggestion would be not to include the algorithm in
> the draft.
> 
>> If the algorithm it too complex to implement, we must simplify the I-D.
>>
>> I think we should make some statement that multipart/related should 
>> not be used unless it is "protected" by some extension-requirement 
>> that ensures the recipient can process multipart/related.
> 
> the draft already states that. In any case, in one of your previous
> emails, you suggested to strengthen the text. I suggest we do this:
> 
> OLD:
>    Authors wishing
>    to make use of 'multipart/related' bodies should keep in mind that
>    UAs that do not understand 'multipart/related' will treat it as
>    'multipart/mixed'.
> 
> 
> NEW:
>    Authors wishing
>    to make use of 'multipart/related' bodies should keep in mind that
>    UAs that do not understand 'multipart/related' will treat it as
>    'multipart/mixed'. If such treatment by a recipient is not acceptable
>    for a particular extension, the authors of such extension would need
>    to make sure (e.g., by using an option-tag or by other means) that
>    entities receiving the 'multipart/related' body were able to
>    correctly process them.
> 
> 
> Cheers,
> 
> Gonzalo
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 

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


From sip-bounces@ietf.org  Wed Oct 29 13:00:07 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 053F43A69A3;
	Wed, 29 Oct 2008 13:00:07 -0700 (PDT)
X-Original-To: sip@ietf.org
Delivered-To: sip@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 7D1933A68F4; Wed, 29 Oct 2008 13:00:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081029200004.7D1933A68F4@core3.amsl.com>
Date: Wed, 29 Oct 2008 13:00:02 -0700 (PDT)
Cc: sip@ietf.org
Subject: [Sip] I-D Action:draft-ietf-sip-body-handling-04.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--NextPart

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


	Title           : Message Body Handling in the Session Initiation Protocol (SIP)
	Author(s)       : G. Camarillo
	Filename        : draft-ietf-sip-body-handling-04.txt
	Pages           : 20
	Date            : 2008-10-29

This document specifies how message bodies are handled in SIP.
Additionally, this document specifies SIP user agent support for MIME
(Multipurpose Internet Mail Extensions) in message bodies.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sip-body-handling-04.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-sip-body-handling-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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


From sip-bounces@ietf.org  Wed Oct 29 13:30:04 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AA7C928C3D8;
	Wed, 29 Oct 2008 13:30:04 -0700 (PDT)
X-Original-To: sip@ietf.org
Delivered-To: sip@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id AAB6F3A6AF7; Wed, 29 Oct 2008 13:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081029203001.AAB6F3A6AF7@core3.amsl.com>
Date: Wed, 29 Oct 2008 13:30:01 -0700 (PDT)
Cc: sip@ietf.org
Subject: [Sip] I-D Action:draft-ietf-sip-dtls-srtp-framework-05.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--NextPart

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


	Title           : Framework for Establishing an SRTP Security Context using DTLS
	Author(s)       : J. Fischl, et al.
	Filename        : draft-ietf-sip-dtls-srtp-framework-05.txt
	Pages           : 34
	Date            : 2008-10-29

This document specifies how to use the Session Initiation Protocol
(SIP) to establish an Secure Real-time Transport Protocol (SRTP)
security context using the Datagram Transport Layer Security (DTLS)
protocol.  It describes a mechanism of transporting a fingerprint
attribute in the Session Description Protocol (SDP) that identifies
the key that will be presented during the DTLS handshake.  The key
exchange travels along the media path as opposed to the signaling
path.  The SIP Identity mechanism can be used to protect the
integrity of the fingerprint attribute from modification by
intermediate proxies.

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

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-sip-dtls-srtp-framework-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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


From sip-bounces@ietf.org  Wed Oct 29 13:46:31 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 16DD43A6B2A;
	Wed, 29 Oct 2008 13:46:31 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1CF3D3A67A5
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 13:46:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.039
X-Spam-Level: 
X-Spam-Status: No, score=-2.039 tagged_above=-999 required=5 tests=[AWL=0.260, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id clLahD+N4VJK for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 13:46:29 -0700 (PDT)
Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.182])
	by core3.amsl.com (Postfix) with ESMTP id 570593A6B19
	for <sip@ietf.org>; Wed, 29 Oct 2008 13:46:29 -0700 (PDT)
Received: by el-out-1112.google.com with SMTP id v27so90079ele.13
	for <sip@ietf.org>; Wed, 29 Oct 2008 13:46:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=KIcrDArCC9bV+gXJwRNjUaM9uJiSCfidzTBrKGD4vCw=;
	b=Plzv4eyd9tSWGjqiOSw5t5Gwlk51BD2VtryB6JTHeRl2atgS5LyxTNEqdW1G637ZS5
	ieyAqp72DnXvuwXk/sBeeS8e1fayx6+YuK2Pz9+LUWQ3RH5+HEsW8cDQ5tLQdsvV2zdT
	rVVTlYuhZDc+COIoyUrf1A1Tk2rVy8gEdh/PU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=UxtHN3Pwqh2TDrOQvACHmpLtXxZzps4dOQSUKkwpM5g9s+nVZC3tFe9yBm/InMQdPA
	Ld911VHEIQ1pd3td/8Jcokj4uC/2oBl0q/wqWGI7s6PrehPgWRh+8jnl38Y2gBqatchV
	J8s0ph9e+Fi2QEHBAhop6+ctQh760RLSV3T9A=
Received: by 10.90.33.15 with SMTP id g15mr7783039agg.0.1225309061705;
	Wed, 29 Oct 2008 12:37:41 -0700 (PDT)
Received: by 10.90.114.2 with HTTP; Wed, 29 Oct 2008 12:37:41 -0700 (PDT)
Message-ID: <618e24240810291237t440f25f2hcd783d93f90d38a0@mail.gmail.com>
Date: Wed, 29 Oct 2008 20:37:41 +0100
From: "=?UTF-8?Q?Victor_Pascual_=C3=81vila?=" <victor.pascual.avila@gmail.com>
To: "Dan Wing" <dwing@cisco.com>
In-Reply-To: <007b01c939f6$6f33e5e0$24726b80@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>
	<200810261145.19745.ibc@aliax.net>
	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
	<084c01c938a0$a41ff390$c3f0200a@cisco.com>
	<cc1f582e0810280444y42b8f723w938004e902fb1180@mail.gmail.com>
	<032301c93978$6b249c70$c3f0200a@cisco.com>
	<618e24240810290415i7ede4601tf2fd78aaed755445@mail.gmail.com>
	<007b01c939f6$6f33e5e0$24726b80@cisco.com>
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event
	foRIdentityVErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

T24gV2VkLCBPY3QgMjksIDIwMDggYXQgNzo0NCBQTSwgRGFuIFdpbmcgPGR3aW5nQGNpc2NvLmNv
bT4gd3JvdGU6Cj4gSSdtIG5vdCBpbnRlcmVzdGVkIGluIGhhdmluZyBhIGNvbXBldGluZyBwcm9w
b3NhbCwgdGhvdWdoLCBvciBhcmd1aW5nCj4gbml0cyBhYm91dCB3aGljaCA0eHggcmVzcG9uc2Ug
Y29kZSBpcyBtb3N0IGFwcHJvcHJpYXRlLgo+Cj4gV2Ugc2hvdWxkIGJlIGFyZ3VpbmcgYWJvdXQg
bGFyZ2VyIGlzc3Vlcywgc3VjaCBhcyB0aGUgdmFsdWUgb2YgcHJvdmluZwo+IHNvbWVvbmUgaXMg
YWN0dWFsbHkgb3JpZ2luYXRpbmcgYSBjYWxsLiAgV2l0aG91dCB0aGF0LCB3ZSBjYW5ub3QgaGF2
ZQo+IHJlbGlhYmxlIHdoaXRlbGlzdHMgb3IgcmVsaWFibHkgYmxhY2tsaXN0cywgd2hpY2ggYXJl
IHRoZSBmb3VuZGF0aW9ucwo+IGZvciBhdXRob3JpemluZyBpbmNvbWluZyBTSVAgcmVxdWVzdHMu
CgpJIGZ1bGx5IGFncmVlIHdpdGggeW91LgoKLS0gClZpY3RvciBQYXNjdWFsIMOBdmlsYQpfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpTaXAgbWFpbGluZyBs
aXN0ICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpcApUaGlzIGxpc3Qg
aXMgZm9yIE5FVyBkZXZlbG9wbWVudCBvZiB0aGUgY29yZSBTSVAgUHJvdG9jb2wKVXNlIHNpcC1p
bXBsZW1lbnRvcnNAY3MuY29sdW1iaWEuZWR1IGZvciBxdWVzdGlvbnMgb24gY3VycmVudCBzaXAK
VXNlIHNpcHBpbmdAaWV0Zi5vcmcgZm9yIG5ldyBkZXZlbG9wbWVudHMgb24gdGhlIGFwcGxpY2F0
aW9uIG9mIHNpcA==


From sip-bounces@ietf.org  Wed Oct 29 15:00:02 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7645A3A6AFC;
	Wed, 29 Oct 2008 15:00:02 -0700 (PDT)
X-Original-To: sip@ietf.org
Delivered-To: sip@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id BB98F3A6AFC; Wed, 29 Oct 2008 15:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081029220001.BB98F3A6AFC@core3.amsl.com>
Date: Wed, 29 Oct 2008 15:00:01 -0700 (PDT)
Cc: sip@ietf.org
Subject: [Sip] I-D Action:draft-ietf-sip-fork-loop-fix-08.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--NextPart

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


	Title           : Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies
	Author(s)       : R. Sparks, et al.
	Filename        : draft-ietf-sip-fork-loop-fix-08.txt
	Pages           : 26
	Date            : 2008-10-29

This document normatively updates RFC 3261, the Session Initiation
Protocol (SIP), to address a security vulnerability identified in SIP
proxy behavior.  This vulnerability enables an attack against SIP
networks where a small number of legitimate, even authorized, SIP
requests can stimulate massive amounts of proxy-to-proxy traffic.
This document strengthens loop-detection requirements on SIP proxies
when they fork requests (that is, forward a request to more than one
destination).  It also corrects and clarifies the description of the
loop-detection algorithm such proxies are required to implement.
Additionally, this document defines a Max-Breadth mechanism for
limiting the number of concurrent branches pursued for any given
request.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sip-fork-loop-fix-08.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-sip-fork-loop-fix-08.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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


From sip-bounces@ietf.org  Wed Oct 29 15:06:48 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C9B2628C3CA;
	Wed, 29 Oct 2008 15:06:48 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D76C328C3BA
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 15:06:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OdCV8p7PpQu6 for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 15:06:46 -0700 (PDT)
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188])
	by core3.amsl.com (Postfix) with ESMTP id ECB263A6ABF
	for <sip@ietf.org>; Wed, 29 Oct 2008 15:06:45 -0700 (PDT)
Received: by nf-out-0910.google.com with SMTP id b11so141276nfh.39
	for <sip@ietf.org>; Wed, 29 Oct 2008 15:06:43 -0700 (PDT)
Received: by 10.210.104.20 with SMTP id b20mr10672726ebc.113.1225318003295;
	Wed, 29 Oct 2008 15:06:43 -0700 (PDT)
Received: from portatil.local (174.pool85-58-22.dynamic.orange.es
	[85.58.22.174])
	by mx.google.com with ESMTPS id b33sm938413ika.1.2008.10.29.15.06.40
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Wed, 29 Oct 2008 15:06:41 -0700 (PDT)
From: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
To: sip@ietf.org
Date: Wed, 29 Oct 2008 23:06:44 +0100
User-Agent: KMail/1.9.9
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<490792EA.2020106@softarmor.com>
	<033f01c9397b$860847a0$c3f0200a@cisco.com>
In-Reply-To: <033f01c9397b$860847a0$c3f0200a@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810292306.44911.ibc@aliax.net>
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

El Mi=E9rcoles, 29 de Octubre de 2008, Dan Wing escribi=F3:
> > Would the SBC not have to handle the SUBSCRIBE request locally? After
> > all, since it is a terminal UA for the call, it also knows
> > about all the
> > dialog states. The end-user UA would never even see the SUBSCRIBE.
>
> If that's a problem, just use some different method that goes end to
> end. =A0The always-loved INFO comes to mind.

Anyway, you need to carry in the INFO body (or headers) data about the curr=
ent =

dialog, but this data changes in both legs of the B2BUA, so it will fail.
It's exactly the same case as if the SUBSCRIBE is "forwarded" between B2BUA =

legs without replacing the dialog data (from leg B to leg A).

Regards.

-- =

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


From sip-bounces@ietf.org  Wed Oct 29 15:08:20 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D79F728C3D2;
	Wed, 29 Oct 2008 15:08:20 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E646528C3CA
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 15:08:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3hoG81eh8Kxp for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 15:08:18 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net
	[IPv6:2001:470:1f03:267::2])
	by core3.amsl.com (Postfix) with ESMTP id 7EC8228C3F6
	for <sip@ietf.org>; Wed, 29 Oct 2008 15:08:17 -0700 (PDT)
Received: from dn3-232.estacado.net (vicuna-alt.estacado.net [75.53.54.121])
	(authenticated bits=0)
	by nostrum.com (8.14.3/8.14.1) with ESMTP id m9TM8Dm5029094
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO)
	for <sip@ietf.org>; Wed, 29 Oct 2008 17:08:14 -0500 (CDT)
	(envelope-from rjsparks@nostrum.com)
Message-Id: <36F1C677-2592-41A6-B790-1AB21BC1D1DD@nostrum.com>
From: Robert Sparks <rjsparks@nostrum.com>
To: "SIP@ietf.org List" <sip@ietf.org>
In-Reply-To: <20081029220001.BB98F3A6AFC@core3.amsl.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 29 Oct 2008 17:08:13 -0500
References: <20081029220001.BB98F3A6AFC@core3.amsl.com>
X-Mailer: Apple Mail (2.929.2)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted
	mechanism)
X-Virus-Scanned: ClamAV 0.94/8538/Wed Oct 29 13:45:41 2008 on
	shaman.nostrum.com
X-Virus-Status: Clean
Subject: Re: [Sip] I-D Action:draft-ietf-sip-fork-loop-fix-08.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This revision attempts to address some concerns raised in IESG review.
If you haven't been tracking this, the details are at:

https://datatracker.ietf.org/idtracker/draft-ietf-sip-fork-loop-fix/

RjS

On Oct 29, 2008, at 5:00 PM, Internet-Drafts@ietf.org wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts  
> directories.
> This draft is a work item of the Session Initiation Protocol Working  
> Group of the IETF.
>
>
> 	Title           : Addressing an Amplification Vulnerability in  
> Session Initiation Protocol (SIP) Forking Proxies
> 	Author(s)       : R. Sparks, et al.
> 	Filename        : draft-ietf-sip-fork-loop-fix-08.txt
> 	Pages           : 26
> 	Date            : 2008-10-29
>
> This document normatively updates RFC 3261, the Session Initiation
> Protocol (SIP), to address a security vulnerability identified in SIP
> proxy behavior.  This vulnerability enables an attack against SIP
> networks where a small number of legitimate, even authorized, SIP
> requests can stimulate massive amounts of proxy-to-proxy traffic.
> This document strengthens loop-detection requirements on SIP proxies
> when they fork requests (that is, forward a request to more than one
> destination).  It also corrects and clarifies the description of the
> loop-detection algorithm such proxies are required to implement.
> Additionally, this document defines a Max-Breadth mechanism for
> limiting the number of concurrent branches pursued for any given
> request.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-sip-fork-loop- 
> fix-08.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> <mime-attachment>_______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip

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


From sip-bounces@ietf.org  Wed Oct 29 15:55:16 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B0DD73A69D5;
	Wed, 29 Oct 2008 15:55:16 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 58BCC3A69D5
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 15:55:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.232
X-Spam-Level: 
X-Spam-Status: No, score=-6.232 tagged_above=-999 required=5 tests=[AWL=0.067, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rZuRa6Uc1fts for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 15:55:14 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 55D723A69CA
	for <sip@ietf.org>; Wed, 29 Oct 2008 15:55:14 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,509,1220227200"; d="scan'208";a="26098046"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 29 Oct 2008 22:55:12 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9TMtCsT030777; 
	Wed, 29 Oct 2008 18:55:12 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9TMtCYs017288;
	Wed, 29 Oct 2008 22:55:12 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 29 Oct 2008 18:55:12 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 29 Oct 2008 18:55:12 -0400
Message-ID: <4908E9CF.7050307@cisco.com>
Date: Wed, 29 Oct 2008 18:55:11 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: =?UTF-8?B?VmljdG9yIFBhc2N1YWwgw4F2aWxh?= <victor.pascual.avila@gmail.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>	<D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>	<200810261145.19745.ibc@aliax.net>	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>	<084c01c938a0$a41ff390$c3f0200a@cisco.com>	<cc1f582e0810280444y42b8f723w938004e902fb1180@mail.gmail.com>	<032301c93978$6b249c70$c3f0200a@cisco.com>	<618e24240810290415i7ede4601tf2fd78aaed755445@mail.gmail.com>	<007b01c939f6$6f33e5e0$24726b80@cisco.com>
	<618e24240810291237t440f25f2hcd783d93f90d38a0@mail.gmail.com>
In-Reply-To: <618e24240810291237t440f25f2hcd783d93f90d38a0@mail.gmail.com>
X-OriginalArrivalTime: 29 Oct 2008 22:55:12.0324 (UTC)
	FILETIME=[6664B840:01C93A19]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1339; t=1225320912;
	x=1226184912; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20submission=20of=20a=20new=20I-D
	=3A=20=22Dialog=20Event=09foRIdentityVErification=22
	|Sender:=20
	|To:=20=3D?UTF-8?B?VmljdG9yIFBhc2N1YWwgw4F2aWxh?=3D=0A=20<v
	ictor.pascual.avila@gmail.com>;
	bh=j/v+cbmFbUClfmfJCOzyd2IEsrESAKN7sEJKJx278vA=;
	b=WiGsxlccafbgYnGQeE1tUbRoupDc80lrZ0myJS7Tj+6LhCaXBlWephhijw
	bUQL0xd07JVv0xhbFRqcf3snT2zxOcBKy8KyNmbYDO+KWwhu8s3xPujP4R+H
	v580ocLfhQ;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: sip@ietf.org, Dan Wing <dwing@cisco.com>
Subject: Re: [Sip] submission of a new I-D: "Dialog
	Event	foRIdentityVErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

V2hpbGUgSSBhZ3JlZSB3aXRoIHdoYXQgeW91IHNheSwgdGhpcyBvbmx5IHdvcmtzIGlmIHRoZSB2
ZXJpZmljYXRpb24gCndpbGwgaGFwcGVuIGluIGEgdGltZWx5IHdheS4gSWYgeW91IHdhbnQgd2hp
dGUvYmxhY2sgbGlzdHMsIHRoZW4gdGhlIAp2ZXJpZmljYXRpb24gbXVzdCBoYXBwZW4gZXZlbiBi
ZWZvcmUgdGhlIHBob25lIHJpbmdzLiBJcyBpdCByZWFzb25hYmxlIAp0byBhc3N1bWUgdGhhdCBp
biB0eXBpY2FsIGRlcGxveW1lbnRzIHRoZSB0aW1lIGZvciB0aGUgcmV2ZXJzZSBsb29rdXAgCndp
bGwgYmUgcXVpY2sgZW5vdWdoIHRvIGdpdmUgcmVhc29uYWJsZSBleHBlcmllbmNlIHRvIHRoZSBj
YWxsZXI/IE9yIAp3aWxsIGhlIGhhdmUgYWxyZWFkeSBodW5nIHVwPyAoSSBkb24ndCBoYXZlIGEg
Z29vZCBzZW5zZSBmb3IgdGhlIG51bWJlcnMgCmhlcmUuKQoKV2hhdCB3aWxsIHRoZSBjYWxsZXIg
YmUgaGVhcmluZyB1bnRpbCB0aGlzIGdldHMgZG9uZT8gUGVyaGFwcyAxODAgY291bGQgCmJlIHJl
dHVybmVkLCB3aGljaCB3b3VsZCBhdCBsZWFzdCBnaXZlICpzb21lKiBmZWVkYmFjay4KCklmIHRo
aXMgdGFrZXMgdG9vIGxvbmcsIHRoZW4gSSB0aGluayBpdCBlbmRzIHVwIGJlaW5nIGluZm8gdGhh
dCBtYXkgYmUgCmRlbGl2ZXJlZCBhZnRlciB0aGUgY2FsbCBpcyBlc3RhYmxpc2hlZC4gKFBlcmhh
cHMgeW91ciBjYWxsZXJpZCBzdGFydHMgCm91dCB5ZWxsb3cgYW5kIHR1cm5zIGdyZWVuIHdoZW4g
aXQgaGFzIGJlZW4gY29uZmlybWVkLikKCglUaGFua3MsCglQYXVsCgpWaWN0b3IgUGFzY3VhbCDD
gXZpbGEgd3JvdGU6Cj4gT24gV2VkLCBPY3QgMjksIDIwMDggYXQgNzo0NCBQTSwgRGFuIFdpbmcg
PGR3aW5nQGNpc2NvLmNvbT4gd3JvdGU6Cj4+IEknbSBub3QgaW50ZXJlc3RlZCBpbiBoYXZpbmcg
YSBjb21wZXRpbmcgcHJvcG9zYWwsIHRob3VnaCwgb3IgYXJndWluZwo+PiBuaXRzIGFib3V0IHdo
aWNoIDR4eCByZXNwb25zZSBjb2RlIGlzIG1vc3QgYXBwcm9wcmlhdGUuCj4+Cj4+IFdlIHNob3Vs
ZCBiZSBhcmd1aW5nIGFib3V0IGxhcmdlciBpc3N1ZXMsIHN1Y2ggYXMgdGhlIHZhbHVlIG9mIHBy
b3ZpbmcKPj4gc29tZW9uZSBpcyBhY3R1YWxseSBvcmlnaW5hdGluZyBhIGNhbGwuICBXaXRob3V0
IHRoYXQsIHdlIGNhbm5vdCBoYXZlCj4+IHJlbGlhYmxlIHdoaXRlbGlzdHMgb3IgcmVsaWFibHkg
YmxhY2tsaXN0cywgd2hpY2ggYXJlIHRoZSBmb3VuZGF0aW9ucwo+PiBmb3IgYXV0aG9yaXppbmcg
aW5jb21pbmcgU0lQIHJlcXVlc3RzLgo+IAo+IEkgZnVsbHkgYWdyZWUgd2l0aCB5b3UuCj4gCl9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClNpcCBtYWlsaW5n
IGxpc3QgIGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc2lwClRoaXMgbGlz
dCBpcyBmb3IgTkVXIGRldmVsb3BtZW50IG9mIHRoZSBjb3JlIFNJUCBQcm90b2NvbApVc2Ugc2lw
LWltcGxlbWVudG9yc0Bjcy5jb2x1bWJpYS5lZHUgZm9yIHF1ZXN0aW9ucyBvbiBjdXJyZW50IHNp
cApVc2Ugc2lwcGluZ0BpZXRmLm9yZyBmb3IgbmV3IGRldmVsb3BtZW50cyBvbiB0aGUgYXBwbGlj
YXRpb24gb2Ygc2lw


From sip-bounces@ietf.org  Wed Oct 29 16:12:29 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CC5A43A6B16;
	Wed, 29 Oct 2008 16:12:29 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A83553A68DB
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 16:12:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3JJEZDfsvEUX for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 16:12:26 -0700 (PDT)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31])
	by core3.amsl.com (Postfix) with ESMTP id F2C453A6D54
	for <sip@ietf.org>; Wed, 29 Oct 2008 16:12:25 -0700 (PDT)
Received: by yw-out-2324.google.com with SMTP id 3so102155ywj.49
	for <sip@ietf.org>; Wed, 29 Oct 2008 16:12:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=hbd6uphUdgXV2HV6WuBVBVfb1Z0znGh2pULSzKG5VTQ=;
	b=ACk5bWYyJGknb8Pf6gwMSqOwCs5SpeE0ihDyjnzPXq6yW3z0FGbeAKL0rld8xJkfpV
	4fEezzfVXc9RYPi6msv6OMxtA+EbQ2mQ27YCK5D/6p4oILe9xXYlKfsnghmshgS3cWQ2
	7Isotc6HGe0HbjF5obY1Hd4rFgoNtt8rZE+RI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=GfKywS+7xzjjPQmwKrDMSUuH84vOVYEf9S7p489zzl7b1P3hOMHTPfbPM4KtDNrcCi
	lQfuGISlHpH2pYOkXAD/hFUkCOWr4eUvvpvfvDOwZ2pwvG8CifyNXGrOgUIUqCVQgvyF
	FiQHxds5bTCf5q5XjvRswRcBSMvF2i1yeLXso=
Received: by 10.90.79.12 with SMTP id c12mr7965695agb.65.1225321944392;
	Wed, 29 Oct 2008 16:12:24 -0700 (PDT)
Received: by 10.90.114.2 with HTTP; Wed, 29 Oct 2008 16:12:24 -0700 (PDT)
Message-ID: <618e24240810291612n2a8f4dffy69ca2d5a2c20000d@mail.gmail.com>
Date: Thu, 30 Oct 2008 00:12:24 +0100
From: "=?UTF-8?Q?Victor_Pascual_=C3=81vila?=" <victor.pascual.avila@gmail.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
In-Reply-To: <4908E9CF.7050307@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<200810261145.19745.ibc@aliax.net>
	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
	<084c01c938a0$a41ff390$c3f0200a@cisco.com>
	<cc1f582e0810280444y42b8f723w938004e902fb1180@mail.gmail.com>
	<032301c93978$6b249c70$c3f0200a@cisco.com>
	<618e24240810290415i7ede4601tf2fd78aaed755445@mail.gmail.com>
	<007b01c939f6$6f33e5e0$24726b80@cisco.com>
	<618e24240810291237t440f25f2hcd783d93f90d38a0@mail.gmail.com>
	<4908E9CF.7050307@cisco.com>
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event
	foRIdentityVErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

SGkgUGF1bCwKCk9uIFdlZCwgT2N0IDI5LCAyMDA4IGF0IDExOjU1IFBNLCBQYXVsIEt5eml2YXQg
PHBreXppdmF0QGNpc2NvLmNvbT4gd3JvdGU6Cj4gV2hpbGUgSSBhZ3JlZSB3aXRoIHdoYXQgeW91
IHNheSwgdGhpcyBvbmx5IHdvcmtzIGlmIHRoZSB2ZXJpZmljYXRpb24gd2lsbAo+IGhhcHBlbiBp
biBhIHRpbWVseSB3YXkuIElmIHlvdSB3YW50IHdoaXRlL2JsYWNrIGxpc3RzLCB0aGVuIHRoZSB2
ZXJpZmljYXRpb24KPiBtdXN0IGhhcHBlbiBldmVuIGJlZm9yZSB0aGUgcGhvbmUgcmluZ3MuIElz
IGl0IHJlYXNvbmFibGUgdG8gYXNzdW1lIHRoYXQgaW4KPiB0eXBpY2FsIGRlcGxveW1lbnRzIHRo
ZSB0aW1lIGZvciB0aGUgcmV2ZXJzZSBsb29rdXAgd2lsbCBiZSBxdWljayBlbm91Z2ggdG8KPiBn
aXZlIHJlYXNvbmFibGUgZXhwZXJpZW5jZSB0byB0aGUgY2FsbGVyPyBPciB3aWxsIGhlIGhhdmUg
YWxyZWFkeSBodW5nIHVwPwo+IChJIGRvbid0IGhhdmUgYSBnb29kIHNlbnNlIGZvciB0aGUgbnVt
YmVycyBoZXJlLikKCkFzIHlvdSBtZW50aW9uLCB0aGUgdXNlciAoQ2FsbGVlKSBzaG91bGQgbm90
IGJlIGFsZXJ0ZWQgdW50aWwgdGhlCnZlcmlmaWNhdGlvbiBwcm9jZXNzIGlzIGNvbXBsZXRlZC4g
SU1PIHRoZSB0aW1lIGZvciB0aGUgcmV2ZXJzZSBsb29rdXAKaXMgdHlwaWNhbGx5IHF1aWNrIGVu
b3VnaCBmb3IgYW4gYWNjZXB0YWJsZSB1c2VyIGV4cGVyaWVuY2UuCgo+IElmIHRoaXMgdGFrZXMg
dG9vIGxvbmcsIHRoZW4gSSB0aGluayBpdCBlbmRzIHVwIGJlaW5nIGluZm8gdGhhdCBtYXkgYmUK
PiBkZWxpdmVyZWQgYWZ0ZXIgdGhlIGNhbGwgaXMgZXN0YWJsaXNoZWQuIChQZXJoYXBzIHlvdXIg
Y2FsbGVyaWQgc3RhcnRzIG91dAo+IHllbGxvdyBhbmQgdHVybnMgZ3JlZW4gd2hlbiBpdCBoYXMg
YmVlbiBjb25maXJtZWQuKQoKVGhpcyBpcyBub3QgdXNlZnVsIGZvciBibGFjay93aGl0ZSBsaXN0
cy4KCkNoZWVycywKLS0gClZpY3RvciBQYXNjdWFsIMOBdmlsYQpfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXwpTaXAgbWFpbGluZyBsaXN0ICBodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpcApUaGlzIGxpc3QgaXMgZm9yIE5FVyBkZXZl
bG9wbWVudCBvZiB0aGUgY29yZSBTSVAgUHJvdG9jb2wKVXNlIHNpcC1pbXBsZW1lbnRvcnNAY3Mu
Y29sdW1iaWEuZWR1IGZvciBxdWVzdGlvbnMgb24gY3VycmVudCBzaXAKVXNlIHNpcHBpbmdAaWV0
Zi5vcmcgZm9yIG5ldyBkZXZlbG9wbWVudHMgb24gdGhlIGFwcGxpY2F0aW9uIG9mIHNpcA==


From sip-bounces@ietf.org  Wed Oct 29 16:36:30 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5F89528C3CA;
	Wed, 29 Oct 2008 16:36:30 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 841493A6D61
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 16:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jC4-GIQ9KdJg for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 16:36:27 -0700 (PDT)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29])
	by core3.amsl.com (Postfix) with ESMTP id B77A13A6D5E
	for <sip@ietf.org>; Wed, 29 Oct 2008 16:36:27 -0700 (PDT)
Received: by yw-out-2324.google.com with SMTP id 3so105572ywj.49
	for <sip@ietf.org>; Wed, 29 Oct 2008 16:36:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=7M5dQ5j6Q9Rqqht4VD8PYgdbuAxLfn++6iLdJLzfcTc=;
	b=Y0IPL+C8wYJP6EP7Phtdg4YaXKguSXvXSdl287SI6RBZM3czmu/1aWpEFyj66FzMsx
	fWl5Iv1HzJC7/iRZNY+VIYI9D6PpLtEaZ3pCBb6mHs4HmZI/8/9G7E2fw0f0EVO17Sai
	b9K2TnfSHUe+/jJiqy4PuIyEUwQn/77uUltWE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=clwnmMqyoQbnCd3gZTI2yTD1bbkn7eDjVP0aGbw2PDZ1xk87vEwdZxUGc54OyKViBo
	y71V1CttnCYcDYjBByo6cYsd4jTNq/eTqLOdfiq/I4kykRnhnEBwIqYWW/p3krpU0qAQ
	3nFU7JwfznCEVMzVgjMS+YdXASqToEYS4/cV4=
Received: by 10.90.33.5 with SMTP id g5mr713377agg.97.1225323380817;
	Wed, 29 Oct 2008 16:36:20 -0700 (PDT)
Received: by 10.90.114.2 with HTTP; Wed, 29 Oct 2008 16:36:20 -0700 (PDT)
Message-ID: <618e24240810291636q6986570as674cbe65e49a8c7b@mail.gmail.com>
Date: Thu, 30 Oct 2008 00:36:20 +0100
From: "=?UTF-8?Q?Victor_Pascual_=C3=81vila?=" <victor.pascual.avila@gmail.com>
To: "Dan Wing" <dwing@cisco.com>
In-Reply-To: <033d01c93979$b3cf1990$c3f0200a@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>
	<200810290236.m9T2akDN55854559@shell01.TheWorld.com>
	<033d01c93979$b3cf1990$c3f0200a@cisco.com>
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR
	IdentityVErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

T24gV2VkLCBPY3QgMjksIDIwMDggYXQgNDo1MiBBTSwgRGFuIFdpbmcgPGR3aW5nQGNpc2NvLmNv
bT4gd3JvdGU6Cj4gREVSSVZFIGlzIGNoZWNraW5nIHRvIHNlZSBpZiB5b3VyIFNJUCByb3V0aW5n
IHRha2VzIHlvdSB0byB0aGUKPiBzYW1lIHBsYWNlIHRoYXQgKGNsYWltcyB0bykgYmUgb3JpZ2lu
YXRpbmcgdGhlIGluY29taW5nIElOVklURS4KPiBJdCBpcyB1c2luZyB5b3VyICpvdXRnb2luZyog
U0lQIHJvdXRpbmcgLS0gd2hpY2ggeW91IG11c3QgYWxyZWFkeQo+IHRydXN0IHRvIHNlbmQgb3V0
Ym91bmQgbWVzc2FnZXMgLS0gdG8gdGVzdCB0aGUgdmFsaWRpdHkgb2YgdGhlCj4gKHByb3BvcnRl
ZCkgRnJvbTogYWRkcmVzcyBvZiBhbiBpbmNvbWluZyBJTlZJVEUuCgpTaGFsbCBERVJJVkUgYmUg
ZXh0ZW5kZWQgdG8gc3VwcG9ydCBub24tSU5WSVRFIHJlcXVlc3RzIChlLmcuIE1FU1NBR0UpPwoK
LS0gClZpY3RvciBQYXNjdWFsIMOBdmlsYQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXwpTaXAgbWFpbGluZyBsaXN0ICBodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL3NpcApUaGlzIGxpc3QgaXMgZm9yIE5FVyBkZXZlbG9wbWVudCBvZiB0
aGUgY29yZSBTSVAgUHJvdG9jb2wKVXNlIHNpcC1pbXBsZW1lbnRvcnNAY3MuY29sdW1iaWEuZWR1
IGZvciBxdWVzdGlvbnMgb24gY3VycmVudCBzaXAKVXNlIHNpcHBpbmdAaWV0Zi5vcmcgZm9yIG5l
dyBkZXZlbG9wbWVudHMgb24gdGhlIGFwcGxpY2F0aW9uIG9mIHNpcA==


From sip-bounces@ietf.org  Wed Oct 29 16:39:37 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9DD5828C3E0;
	Wed, 29 Oct 2008 16:39:37 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7E77728C3E0
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 16:39:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.223
X-Spam-Level: 
X-Spam-Status: No, score=-2.223 tagged_above=-999 required=5
	tests=[AWL=-0.076, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	SARE_SUB_ENC_UTF8=0.152]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jp3vnBD8lA6J for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 16:39:35 -0700 (PDT)
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171])
	by core3.amsl.com (Postfix) with ESMTP id 32C2128C3CA
	for <sip@ietf.org>; Wed, 29 Oct 2008 16:39:35 -0700 (PDT)
Received: by ug-out-1314.google.com with SMTP id b39so767035ugd.15
	for <sip@ietf.org>; Wed, 29 Oct 2008 16:39:31 -0700 (PDT)
Received: by 10.210.42.20 with SMTP id p20mr10807462ebp.4.1225323571768;
	Wed, 29 Oct 2008 16:39:31 -0700 (PDT)
Received: from portatil.local (174.pool85-58-22.dynamic.orange.es
	[85.58.22.174])
	by mx.google.com with ESMTPS id z34sm1071929ikz.0.2008.10.29.16.39.29
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Wed, 29 Oct 2008 16:39:30 -0700 (PDT)
From: =?utf-8?q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: sip@ietf.org
Date: Thu, 30 Oct 2008 00:39:32 +0100
User-Agent: KMail/1.9.9
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<618e24240810291237t440f25f2hcd783d93f90d38a0@mail.gmail.com>
	<4908E9CF.7050307@cisco.com>
In-Reply-To: <4908E9CF.7050307@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810300039.32527.ibc@aliax.net>
Subject: Re: [Sip]
	=?utf-8?q?submission_of_a_new_I-D=3A_=22Dialog_Event=09foRI?=
	=?utf-8?q?dentityVErification_=22?=
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

RWwgTWnDqXJjb2xlcywgMjkgZGUgT2N0dWJyZSBkZSAyMDA4LCBQYXVsIEt5eml2YXQgZXNjcmli
acOzOgo+IChQZXJoYXBzIHlvdXIgY2FsbGVyaWQgc3RhcnRzCj4gb3V0IHllbGxvdyBhbmQgdHVy
bnMgZ3JlZW4gd2hlbiBpdCBoYXMgYmVlbiBjb25maXJtZWQuKQoKSSBsaWtlIHRoaXMgaWRlYS4K
Ci0tIApJw7Fha2kgQmF6IENhc3RpbGxvCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fClNpcCBtYWlsaW5nIGxpc3QgIGh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vc2lwClRoaXMgbGlzdCBpcyBmb3IgTkVXIGRldmVsb3BtZW50IG9mIHRo
ZSBjb3JlIFNJUCBQcm90b2NvbApVc2Ugc2lwLWltcGxlbWVudG9yc0Bjcy5jb2x1bWJpYS5lZHUg
Zm9yIHF1ZXN0aW9ucyBvbiBjdXJyZW50IHNpcApVc2Ugc2lwcGluZ0BpZXRmLm9yZyBmb3IgbmV3
IGRldmVsb3BtZW50cyBvbiB0aGUgYXBwbGljYXRpb24gb2Ygc2lw


From sip-bounces@ietf.org  Wed Oct 29 16:40:22 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7E2E728C403;
	Wed, 29 Oct 2008 16:40:22 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B246A28C3E0
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 16:40:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5Shoe8kuUeZD for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 16:40:20 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id EB6CE28C3CA
	for <sip@ietf.org>; Wed, 29 Oct 2008 16:40:19 -0700 (PDT)
Received: from [192.168.2.102] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9TNeCPY020673
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Wed, 29 Oct 2008 18:40:13 -0500
Message-Id: <36E83843-775F-4317-BB0F-746E55194BFD@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Dan Wing <dwing@cisco.com>
In-Reply-To: <033f01c9397b$860847a0$c3f0200a@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 29 Oct 2008 18:40:06 -0500
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com><0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
	<490792EA.2020106@softarmor.com>
	<033f01c9397b$860847a0$c3f0200a@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: sip@ietf.org, "'Elwell, John'" <john.elwell@siemens.com>
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 28, 2008, at 11:05 PM, Dan Wing wrote:
>>
>> Would the SBC not have to handle the SUBSCRIBE request locally? After
>> all, since it is a terminal UA for the call, it also knows
>> about all the
>> dialog states. The end-user UA would never even see the SUBSCRIBE.
>
> If that's a problem, just use some different method that goes end to
> end.  The always-loved INFO comes to mind.

What makes you think that INFO goes end to end? An SBC can absorb it  
if it wants to.

But this handling is not a bug, it's a feature. Since the SBC is call- 
stateful, it knows about the outgoing call, and thus can  
authoritatively say "Yes, this call was from Dan" without having to  
congest your low-rate end-link.

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


From sip-bounces@ietf.org  Wed Oct 29 16:46:50 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 69D6B3A6D61;
	Wed, 29 Oct 2008 16:46:50 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BBE203A6D58
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 16:46:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.082
X-Spam-Level: 
X-Spam-Status: No, score=-2.082 tagged_above=-999 required=5 tests=[AWL=0.217, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FwFM4hXgTeuv for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 16:46:49 -0700 (PDT)
Received: from mail-gx0-f12.google.com (mail-gx0-f12.google.com
	[209.85.217.12])
	by core3.amsl.com (Postfix) with ESMTP id A01763A6D62
	for <sip@ietf.org>; Wed, 29 Oct 2008 16:46:48 -0700 (PDT)
Received: by gxk5 with SMTP id 5so3034gxk.13
	for <sip@ietf.org>; Wed, 29 Oct 2008 16:46:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=tWnP3ESuujQ40BBkALccn8qUP+9aXxpdGME0PGgsNf4=;
	b=CW/O2aMLVCwmPJ/D7SKzocAvYL6wASTgHgMUl8HviDyxijtekYaZx4h6RrFTmXIy5e
	flaMthmpu5EvsTbZAPFur0y741WVLMX6V4aTCkaaG5b5KtdZqarAPiNNMnNwY7aCIPVz
	wSb0P+lntoll/Z9rTl25oGtqxq00La+rbdp8I=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=nwFj19BBbwm8bkJQTaIQfxC2iaIUZvbEJ0VcC6cqxL1WFF/5ayFfN2kQUZPeHtS8/Y
	illQFHWxJ1nmeT0kMJL9Gx7HLrxE0IkAV0ivF1Uurc15lsySsF13w6OzRYhswiY/H8xg
	WW0hTmb7w6qPTPsrjSr+6TVUWrrue6zEWSPbY=
Received: by 10.90.27.5 with SMTP id a5mr7999338aga.107.1225324006218;
	Wed, 29 Oct 2008 16:46:46 -0700 (PDT)
Received: by 10.90.114.2 with HTTP; Wed, 29 Oct 2008 16:46:46 -0700 (PDT)
Message-ID: <618e24240810291646h46b29632o4a0b65e89baa6842@mail.gmail.com>
Date: Thu, 30 Oct 2008 00:46:46 +0100
From: "=?UTF-8?Q?Victor_Pascual_=C3=81vila?=" <victor.pascual.avila@gmail.com>
To: "Elwell, John" <john.elwell@siemens.com>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D001349A65@GBNTHT12009MSX.gb002.siemens.net>
MIME-Version: 1.0
Content-Disposition: inline
References: <0D5F89FAC29E2C41B98A6A762007F5D001349A65@GBNTHT12009MSX.gb002.siemens.net>
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] More on SIP Identity
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

SGkgSm9obiwKCk9uIFNhdCwgT2N0IDI1LCAyMDA4IGF0IDU6MTggUE0sIEVsd2VsbCwgSm9obiA8
am9obi5lbHdlbGxAc2llbWVucy5jb20+IHdyb3RlOgo+IFRoaXJkLCBhIHJlbWluZGVyIHRoYXQg
dGhlcmUgd2VyZSB0aG91Z2h0cyBleHByZXNzZWQgaW4gRHVibGluIHRoYXQgd2UKPiBzaG91bGQg
Y2FwdHVyZSBpbiBhIGRyYWZ0IGNvbnNpZGVyYXRpb25zIGFib3V0IGhvdyBhIFVBIHNob3VsZCBo
YW5kbGUKPiByZWNlaXZlZCBpZGVudGl0eSBpbmZvcm1hdGlvbi4gQSBmaXJzdCBhdHRlbXB0IGF0
IHRoaXMgaXMgaW46Cj4gaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQt
ZWx3ZWxsLXNpcC1pZGVudGl0eS1oYW5kbGluZy11Cj4gYS0wMC50eHQKClRoYW5rcyBmb3IgcHJv
ZHVjaW5nIHRoaXMgZHJhZnQuCkxvb2tpbmcgYXQgcmVzdWx0cyBmcm9tIHRoZSBsYXN0IFNJUGl0
IFsxXSwgU2VjdGlvbiAzIChVQSBiZXN0CnByYWN0aWNlIGZvciBoYW5kbGluZyByZWNlaXZlZCBj
YWxsZXIgaWRlbnRpZmllcnMpIGNvdWxkIHJlcHJlc2VudCBhCnZhbHVhYmxlIHdvcmsuCgoiSSBh
c2tlZCB3aGVyZSBwZW9wbGUgd2VyZSB0YWtpbmcgYml0cyBmcm9tIG1lc3NhZ2VzIHRvIGRpc3Bs
YXkgYXMgY2FsbGVyLWlkLgpUaGVyZSB3ZXJlIG1hbnkgZGlmZmVyZW50IGtpbmRzIG9mIGFuc3dl
cnMsIGluY2x1ZGluZwogUC1Bc3NlcnRlZC1JZGVudGl0eSBpZiBwcmVzZW50LCB0aGVuIEZyb20K
IEZyb20gZGlzcGxheSBuYW1lCiB1c2VybmFtZSBwYXJ0IG9mIEZyb20gdXJpCiBQLUFzc2VydGVk
LUlkZW50aXR5IG9ubHkKIENvbnRhY3QgdXJpCiBSZW1vdGUgSVAgYWRkcmVzcwogUC1Bc3NlcnRl
ZC1JZGVudGl0eSwgdGhlbiBSZW1vdGUtUGFydHktSUQsIHRoZW4gRnJvbQogRnJvbSwgdGhlbiBS
ZW1vdGUtUGFydHktSUQsIHRoZW4gUC1Bc3NlcnRlZC1JZGVudGl0eQogUmVtb3RlLVBhcnR5LUlE
IHRoZW4gRnJvbQogRnJvbSB0aGVuIFAtQXNzZXJ0aWQtSWRlbnRpdHkKIFAtQXNzZXJ0ZWQtSWRl
bnRpdHksIHRoZW4gUmVwbHktVG8sIHRoZW4gRnJvbQogZW50aXJlIEZyb20gVVJJIgpPZiB0aGVz
ZSwgdXNpbmcgdGhlIEZyb20gZGlzcGxheSBuYW1lIG9jY3VycmVkIG1vc3QgZnJlcXVlbnRseSwK
YnV0IG5vdCBtdWNoIG1vcmUgdGhhbiBhbnkgb2YgdGhlIG90aGVyIHJlc3BvbnNlcwoKClsxXSBo
dHRwczovL3d3dy5zaXBpdC5uZXQvU0lQaXQyM19TdW1tYXJ5CgpDaGVlcnMsCi0tIApWaWN0b3Ig
UGFzY3VhbCDDgXZpbGEKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18KU2lwIG1haWxpbmcgbGlzdCAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9zaXAKVGhpcyBsaXN0IGlzIGZvciBORVcgZGV2ZWxvcG1lbnQgb2YgdGhlIGNvcmUgU0lQ
IFByb3RvY29sClVzZSBzaXAtaW1wbGVtZW50b3JzQGNzLmNvbHVtYmlhLmVkdSBmb3IgcXVlc3Rp
b25zIG9uIGN1cnJlbnQgc2lwClVzZSBzaXBwaW5nQGlldGYub3JnIGZvciBuZXcgZGV2ZWxvcG1l
bnRzIG9uIHRoZSBhcHBsaWNhdGlvbiBvZiBzaXA=


From sip-bounces@ietf.org  Wed Oct 29 16:48:48 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 49C063A6D67;
	Wed, 29 Oct 2008 16:48:48 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 107D828C0FC
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 16:48:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zfTx0AlbQr1g for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 16:48:46 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 33E973A6D67
	for <sip@ietf.org>; Wed, 29 Oct 2008 16:48:46 -0700 (PDT)
Received: from [192.168.2.102] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9TNme5o020718
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Wed, 29 Oct 2008 18:48:42 -0500
Message-Id: <D9D56CA7-4BEE-4CCA-93D2-9FB83DC1E63B@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
In-Reply-To: <4908E9CF.7050307@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 29 Oct 2008 18:48:35 -0500
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>	<D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>	<200810261145.19745.ibc@aliax.net>	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>	<084c01c938a0$a41ff390$c3f0200a@cisco.com>	<cc1f582e0810280444y42b8f723w938004e902fb1180@mail.gmail.com>	<032301c93978$6b249c70$c3f0200a@cisco.com>	<618e24240810290415i7ede4601tf2fd78aaed755445@mail.gmail.com>	<007b01c939f6$6f33e5e0$24726b80@cisco.com>
	<618e24240810291237t440f25f2hcd783d93f90d38a0@mail.gmail.com>
	<4908E9CF.7050307@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: sip@ietf.org, Dan Wing <dwing@cisco.com>
Subject: Re: [Sip] submission of a new I-D: "Dialog
	Event	foRIdentityVErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 29, 2008, at 5:55 PM, Paul Kyzivat wrote:

> While I agree with what you say, this only works if the verification  
> will happen in a timely way. If you want white/black lists, then the  
> verification must happen even before the phone rings. Is it  
> reasonable to assume that in typical deployments the time for the  
> reverse lookup will be quick enough to give reasonable experience to  
> the caller? Or will he have already hung up? (I don't have a good  
> sense for the numbers here.)
>

a Really Bad Case would be 5 seconds PDD, with more typical being on  
the order of 1 second.

> What will the caller be hearing until this gets done? Perhaps 180  
> could be returned, which would at least give *some* feedback.

You might hear a chime for "Return Routability Check completed".

Of course, if we were fixing this "right", it would be yet-another  
precondition.

--
Dean



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


From sip-bounces@ietf.org  Wed Oct 29 16:54:46 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 45C653A6D69;
	Wed, 29 Oct 2008 16:54:46 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A74ED3A6D68
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 16:54:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.599
X-Spam-Level: 
X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nN3ptJOckxRI for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 16:54:41 -0700 (PDT)
Received: from zcars04f.nortel.com (zcars04f.nortel.com [47.129.242.57])
	by core3.amsl.com (Postfix) with ESMTP id 7612E3A682D
	for <sip@ietf.org>; Wed, 29 Oct 2008 16:54:41 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m9TNsWT02248; Wed, 29 Oct 2008 23:54:32 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 29 Oct 2008 18:54:12 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF1A0B455E@zrc2hxm0.corp.nortel.com>
In-Reply-To: <034601c9397d$1e055150$c3f0200a@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Comment on DERIVE and B2BUAs
Thread-Index: Ack5TZTjY39XMHUTQpqEtozVFadSWgALfy3AACl2wjA=
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
	<cc1f582e0810281052y34f5bf88h300c6f59d84879fe@mail.gmail.com><0D5F89FAC29E2C41B98A6A762007F5D00138295A@GBNTHT12009MSX.gb002.siemens.net>
	<490793BF.10702@softarmor.com>
	<034601c9397d$1e055150$c3f0200a@cisco.com>
From: "Francois Audet" <audet@nortel.com>
To: "Dan Wing" <dwing@cisco.com>, "Dean Willis" <dean.willis@softarmor.com>,
	"Elwell, John" <john.elwell@siemens.com>
Cc: sip@ietf.org
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Guys,

Instead of using a SUBSCRIBE or even INFO, it seems appropriate
to use OPTIONS.

By definition, OPTIONS is intended to be routed the same way 
as an INVITE, and therefore would be more likly to end-up at the
right place.  

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Dan Wing
> Sent: Tuesday, October 28, 2008 21:16
> To: 'Dean Willis'; 'Elwell, John'
> Cc: sip@ietf.org
> Subject: Re: [Sip] Comment on DERIVE and B2BUAs
> 
> > -----Original Message-----
> > From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of 
> > Dean Willis
> > Sent: Tuesday, October 28, 2008 3:36 PM
> > To: Elwell, John
> > Cc: sip@ietf.org
> > Subject: Re: [Sip] Comment on DERIVE and B2BUAs
> > 
> > Elwell, John wrote:
> > > 
> > > IBC said:
> > >> Since the B2BUA has detailed info of both legs A and B, it is 
> > >> capable of doing needed changes, as replacing call-id 
> and to-tag in 
> > >> Event header. Also, the B2BUA could handle the SUBSCRIBE by its 
> > >> own, this is, becoming a dialog presence server instead of 
> > >> forwarding the SUBSCRIBE to the UA. B2BUA must handle all this 
> > >> stuff since they are, in fact, the end point, not the 
> UA's behind 
> > >> them.
> > >
> > > [JRE] This reduces it to transitive trust, i.e., no better than 
> > > P-Asserted-Identity. The UA that receives the INVITE 
> request has to 
> > > trust its local B2BUA to confirm that the INVITE request 
> really did 
> > > come from the wherever it claimed to have come from.
> > 
> > Since the INVITE is coming from the SBC (even though the SBC was 
> > influenced by something else to get it to send the INVITE), I don't 
> > see a problem with this.
> > 
> > Otherwise said, SBCs are always transitive trust unless we have 
> > end-to-end crypto, in which case we don't really have SBCs.
> > 
> > So?
> 
> I trust my post office to route a package to the "To:" 
> address much more than I trust the "From:" address of a 
> package on my doorstep.  I expect you do, too -- or do you 
> really believe those letters are from Ed McMahon?
> 
> An analogy:  DERIVE (and my old RRC draft) are looking at the 
> characteristics of that package on the doorstep (SIP INVITE), 
> and sending a letter to the "From:" address written on the 
> package, asking "Did you really send that?".  The post office 
> will route that letter correctly, and it will be opened by 
> the addressee, who will say "Yes, I sent you that package", 
> which is routed back to me.  I will *then* pick up the 
> package (the SIP INVITE).
> 
> For additional protection (as described in my RRC draft) from 
> the post office opening that letter and responding on behalf 
> of the addressee (which an SBC or B2BUA might be tempted to 
> do), we could require the addressee to use a wax seal on 
> their reply letter (a signature over their reply).
> 
> -d
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors@cs.columbia.edu for questions on current sip 
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Wed Oct 29 16:56:45 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 650913A6D68;
	Wed, 29 Oct 2008 16:56:45 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0D6443A6D68
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 16:56:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.28
X-Spam-Level: 
X-Spam-Status: No, score=-2.28 tagged_above=-999 required=5 tests=[AWL=0.019, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id yAbHhoh5lV+A for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 16:56:44 -0700 (PDT)
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174])
	by core3.amsl.com (Postfix) with ESMTP id 177BC3A6974
	for <sip@ietf.org>; Wed, 29 Oct 2008 16:56:43 -0700 (PDT)
Received: by ug-out-1314.google.com with SMTP id b39so769856ugd.15
	for <sip@ietf.org>; Wed, 29 Oct 2008 16:56:42 -0700 (PDT)
Received: by 10.210.139.15 with SMTP id m15mr5574964ebd.182.1225324002071;
	Wed, 29 Oct 2008 16:46:42 -0700 (PDT)
Received: from portatil.local (174.pool85-58-22.dynamic.orange.es
	[85.58.22.174])
	by mx.google.com with ESMTPS id z40sm1101582ikz.2.2008.10.29.16.46.39
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Wed, 29 Oct 2008 16:46:40 -0700 (PDT)
From: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
To: sip@ietf.org
Date: Thu, 30 Oct 2008 00:46:43 +0100
User-Agent: KMail/1.9.9
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<033f01c9397b$860847a0$c3f0200a@cisco.com>
	<36E83843-775F-4317-BB0F-746E55194BFD@softarmor.com>
In-Reply-To: <36E83843-775F-4317-BB0F-746E55194BFD@softarmor.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810300046.43969.ibc@aliax.net>
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

El Jueves, 30 de Octubre de 2008, Dean Willis escribi=F3:
> > If that's a problem, just use some different method that goes end to
> > end. =A0The always-loved INFO comes to mind.
>
> What makes you think that INFO goes end to end? An SBC can absorb it =A0
> if it wants to.

Also, a B2BUA handling SIP + RTP could transform the INFO request into RTP =

data as RFC2833 (DTMF in RTP). =


-- =

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


From sip-bounces@ietf.org  Wed Oct 29 17:00:14 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D886428C421;
	Wed, 29 Oct 2008 17:00:14 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 00EA928C421
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 17:00:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id sHqxO4Hvlgi9 for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 17:00:12 -0700 (PDT)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28])
	by core3.amsl.com (Postfix) with ESMTP id 21DA128C420
	for <sip@ietf.org>; Wed, 29 Oct 2008 17:00:12 -0700 (PDT)
Received: by yw-out-2324.google.com with SMTP id 3so107968ywj.49
	for <sip@ietf.org>; Wed, 29 Oct 2008 17:00:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=IDXYpuL4oYu0TEMjYNq/UfeBiTHlF9pyTse3NAETOf8=;
	b=v+4FVbSbcy9LEIpLcTR0/XImTOiMGj1+4gqzeDvD6gOFxjvX4ujuW4nRbO39Yw0SCg
	Dz/2AWxoyh2TPuF1YOVOA6pks/h2BfKtPwgOj1ZocG/irYjddss7HS27TptctnI6jdML
	kSIWzSaZDsGBZXKYqxeYlcdB7zwqxIiLZFww0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=LdVrxd0FKh22vdpiObUDcS2UjR2wKeo6aivk3sskaNDDibuXxRp5qaOBVYIPxpQCw4
	l63xa4pjEAzxf4KaERf1e3NNKjVw0/kekHgk8i4tRQVR2eV/BFNYTdGoHKjjNqktxphX
	NCIrevfOtG1sgQoYKW59bUM8O80qPIk8hCAJQ=
Received: by 10.90.83.2 with SMTP id g2mr8055489agb.7.1225324809605;
	Wed, 29 Oct 2008 17:00:09 -0700 (PDT)
Received: by 10.90.114.2 with HTTP; Wed, 29 Oct 2008 17:00:09 -0700 (PDT)
Message-ID: <618e24240810291700g3eeccc66w21e31979b3dd5a0a@mail.gmail.com>
Date: Thu, 30 Oct 2008 01:00:09 +0100
From: "=?UTF-8?Q?Victor_Pascual_=C3=81vila?=" <victor.pascual.avila@gmail.com>
To: "Francois Audet" <audet@nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF1A0B455E@zrc2hxm0.corp.nortel.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
	<cc1f582e0810281052y34f5bf88h300c6f59d84879fe@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D00138295A@GBNTHT12009MSX.gb002.siemens.net>
	<490793BF.10702@softarmor.com>
	<034601c9397d$1e055150$c3f0200a@cisco.com>
	<1ECE0EB50388174790F9694F77522CCF1A0B455E@zrc2hxm0.corp.nortel.com>
Cc: sip@ietf.org
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

T24gVGh1LCBPY3QgMzAsIDIwMDggYXQgMTI6NTQgQU0sIEZyYW5jb2lzIEF1ZGV0IDxhdWRldEBu
b3J0ZWwuY29tPiB3cm90ZToKPiBJbnN0ZWFkIG9mIHVzaW5nIGEgU1VCU0NSSUJFIG9yIGV2ZW4g
SU5GTywgaXQgc2VlbXMgYXBwcm9wcmlhdGUKPiB0byB1c2UgT1BUSU9OUy4KPgo+IEJ5IGRlZmlu
aXRpb24sIE9QVElPTlMgaXMgaW50ZW5kZWQgdG8gYmUgcm91dGVkIHRoZSBzYW1lIHdheQo+IGFz
IGFuIElOVklURSwgYW5kIHRoZXJlZm9yZSB3b3VsZCBiZSBtb3JlIGxpa2x5IHRvIGVuZC11cCBh
dCB0aGUKPiByaWdodCBwbGFjZS4KCkRvIHlvdSBtZWFuIGluY2x1ZGluZyBzb21lIGRpYWxvZyBp
bmZvcm1hdGlvbiBpbiB0aGUgT1BUSU9OUy1yZXF1ZXN0CihlLmcgdXNpbmcgdGhlIFRhcmdldC1E
aWFsb2cgaGVhZGVyKT8KCkNoZWVycywKLS0gClZpY3RvciBQYXNjdWFsIMOBdmlsYQpfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpTaXAgbWFpbGluZyBsaXN0
ICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpcApUaGlzIGxpc3QgaXMg
Zm9yIE5FVyBkZXZlbG9wbWVudCBvZiB0aGUgY29yZSBTSVAgUHJvdG9jb2wKVXNlIHNpcC1pbXBs
ZW1lbnRvcnNAY3MuY29sdW1iaWEuZWR1IGZvciBxdWVzdGlvbnMgb24gY3VycmVudCBzaXAKVXNl
IHNpcHBpbmdAaWV0Zi5vcmcgZm9yIG5ldyBkZXZlbG9wbWVudHMgb24gdGhlIGFwcGxpY2F0aW9u
IG9mIHNpcA==


From sip-bounces@ietf.org  Wed Oct 29 17:13:28 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 214DD28C42C;
	Wed, 29 Oct 2008 17:13:28 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 458AB28C42C
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 17:13:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.449
X-Spam-Level: 
X-Spam-Status: No, score=-7.449 tagged_above=-999 required=5
	tests=[AWL=-1.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id JpvR27Gu-p5d for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 17:13:25 -0700 (PDT)
Received: from zcars04f.nortel.com (zcars04f.nortel.com [47.129.242.57])
	by core3.amsl.com (Postfix) with ESMTP id 47DD828C3A1
	for <sip@ietf.org>; Wed, 29 Oct 2008 17:13:25 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com
	[47.103.123.71])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m9U0DJ303674; Thu, 30 Oct 2008 00:13:19 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 29 Oct 2008 19:12:17 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF1A0B4581@zrc2hxm0.corp.nortel.com>
In-Reply-To: <618e24240810291700g3eeccc66w21e31979b3dd5a0a@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Comment on DERIVE and B2BUAs
Thread-Index: Ack6Inw93gIumLiPTzK7haOgeg7IYQAAY6QQ
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
	<cc1f582e0810281052y34f5bf88h300c6f59d84879fe@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D00138295A@GBNTHT12009MSX.gb002.siemens.net>
	<490793BF.10702@softarmor.com>	
	<034601c9397d$1e055150$c3f0200a@cisco.com>
	<1ECE0EB50388174790F9694F77522CCF1A0B455E@zrc2hxm0.corp.nortel.com>
	<618e24240810291700g3eeccc66w21e31979b3dd5a0a@mail.gmail.com>
From: "Francois Audet" <audet@nortel.com>
To: =?UTF-8?B?VmljdG9yIFBhc2N1YWwgw4F2aWxh?= <victor.pascual.avila@gmail.com>
Cc: sip@ietf.org
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

SSB3YXMgbW9yZSB0aGlua2luZyBvZiBhIG5vbmNlIGFzIHBlciBEYW4ncyBkcmFmdC4gQnV0IEkg
ZG9uJ3QgaGF2ZQ0KYSBzdHJvbmcgb3Bpbmlvbi4NCg0KSSBhbSBqdXN0IHRoaW5raW5nIGl0J3Mg
YSBtb3JlIGFwcHJvcHJpYXRlIG1lc3NhZ2UgdGhhbiB0aGUgb3RoZXJzLiANCg0KPiAtLS0tLU9y
aWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBWaWN0b3IgUGFzY3VhbCDDgXZpbGEgW21haWx0
bzp2aWN0b3IucGFzY3VhbC5hdmlsYUBnbWFpbC5jb21dIA0KPiBTZW50OiBXZWRuZXNkYXksIE9j
dG9iZXIgMjksIDIwMDggMTc6MDANCj4gVG86IEF1ZGV0LCBGcmFuY29pcyAoU0MxMDA6MzA1NSkN
Cj4gQ2M6IHNpcEBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogW1NpcF0gQ29tbWVudCBvbiBERVJJ
VkUgYW5kIEIyQlVBcw0KPiANCj4gT24gVGh1LCBPY3QgMzAsIDIwMDggYXQgMTI6NTQgQU0sIEZy
YW5jb2lzIEF1ZGV0IA0KPiA8YXVkZXRAbm9ydGVsLmNvbT4gd3JvdGU6DQo+ID4gSW5zdGVhZCBv
ZiB1c2luZyBhIFNVQlNDUklCRSBvciBldmVuIElORk8sIGl0IHNlZW1zIA0KPiBhcHByb3ByaWF0
ZSB0byB1c2UgDQo+ID4gT1BUSU9OUy4NCj4gPg0KPiA+IEJ5IGRlZmluaXRpb24sIE9QVElPTlMg
aXMgaW50ZW5kZWQgdG8gYmUgcm91dGVkIHRoZSBzYW1lIHdheSBhcyBhbiANCj4gPiBJTlZJVEUs
IGFuZCB0aGVyZWZvcmUgd291bGQgYmUgbW9yZSBsaWtseSB0byBlbmQtdXAgYXQgdGhlIHJpZ2h0
IA0KPiA+IHBsYWNlLg0KPiANCj4gRG8geW91IG1lYW4gaW5jbHVkaW5nIHNvbWUgZGlhbG9nIGlu
Zm9ybWF0aW9uIGluIHRoZSANCj4gT1BUSU9OUy1yZXF1ZXN0IChlLmcgdXNpbmcgdGhlIFRhcmdl
dC1EaWFsb2cgaGVhZGVyKT8NCj4gDQo+IENoZWVycywNCj4gLS0NCj4gVmljdG9yIFBhc2N1YWwg
w4F2aWxhDQo+IA0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18KU2lwIG1haWxpbmcgbGlzdCAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9zaXAKVGhpcyBsaXN0IGlzIGZvciBORVcgZGV2ZWxvcG1lbnQgb2YgdGhlIGNvcmUgU0lQIFBy
b3RvY29sClVzZSBzaXAtaW1wbGVtZW50b3JzQGNzLmNvbHVtYmlhLmVkdSBmb3IgcXVlc3Rpb25z
IG9uIGN1cnJlbnQgc2lwClVzZSBzaXBwaW5nQGlldGYub3JnIGZvciBuZXcgZGV2ZWxvcG1lbnRz
IG9uIHRoZSBhcHBsaWNhdGlvbiBvZiBzaXA=


From sip-bounces@ietf.org  Wed Oct 29 17:14:38 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EA8D128C432;
	Wed, 29 Oct 2008 17:14:37 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D838528C432
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 17:14:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.284
X-Spam-Level: 
X-Spam-Status: No, score=-2.284 tagged_above=-999 required=5 tests=[AWL=0.015, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1loZpzgJ7Z82 for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 17:14:36 -0700 (PDT)
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173])
	by core3.amsl.com (Postfix) with ESMTP id C5F2928C42D
	for <sip@ietf.org>; Wed, 29 Oct 2008 17:14:35 -0700 (PDT)
Received: by ug-out-1314.google.com with SMTP id b39so772366ugd.15
	for <sip@ietf.org>; Wed, 29 Oct 2008 17:14:33 -0700 (PDT)
Received: by 10.210.54.19 with SMTP id c19mr10848003eba.24.1225325672935;
	Wed, 29 Oct 2008 17:14:32 -0700 (PDT)
Received: from portatil.local (174.pool85-58-22.dynamic.orange.es
	[85.58.22.174])
	by mx.google.com with ESMTPS id b30sm1127436ika.3.2008.10.29.17.14.30
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Wed, 29 Oct 2008 17:14:31 -0700 (PDT)
From: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
To: sip@ietf.org
Date: Thu, 30 Oct 2008 01:14:35 +0100
User-Agent: KMail/1.9.9
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<034601c9397d$1e055150$c3f0200a@cisco.com>
	<1ECE0EB50388174790F9694F77522CCF1A0B455E@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF1A0B455E@zrc2hxm0.corp.nortel.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810300114.35470.ibc@aliax.net>
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

El Jueves, 30 de Octubre de 2008, Francois Audet escribi=F3:
> Guys,
>
> Instead of using a SUBSCRIBE or even INFO, it seems appropriate
> to use OPTIONS.
>
> By definition, OPTIONS is intended to be routed the same way
> as an INVITE, and therefore would be more likly to end-up at the
> right place.

Any *current* SIP device already implementing RFC 4235 already implements t=
his =

draft. But if it would be handled by other request (i.e. OPTIONS) then no o=
ne =

of the current implementations would support this draft now, and they would =

need to be modified.

Also, why sending dialog info into an OPTIONS while a SUBSCRIBE (Event: =

dialog;call-id=3Dxxxx;to-tag=3Dxxx) already defines it?
Sending that info into an OPTIONS would require a new kind of headers or XM=
L =

body.



-- =

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


From sip-bounces@ietf.org  Wed Oct 29 18:42:09 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6127D3A68C5;
	Wed, 29 Oct 2008 18:42:09 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BAB8E3A68C5
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 18:42:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.527
X-Spam-Level: 
X-Spam-Status: No, score=-6.527 tagged_above=-999 required=5
	tests=[AWL=-0.228, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fT-3h5pXCkFI for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 18:42:07 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id E5BB43A6826
	for <sip@ietf.org>; Wed, 29 Oct 2008 18:42:06 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,511,1220227200"; d="scan'208";a="185223613"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 30 Oct 2008 01:42:06 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m9U1g67N004847; 
	Wed, 29 Oct 2008 18:42:06 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9U1g5SI015424;
	Thu, 30 Oct 2008 01:42:05 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "=?iso-8859-1?Q?'Victor_Pascual_=C1vila'?="
	<victor.pascual.avila@gmail.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>
	<200810290236.m9T2akDN55854559@shell01.TheWorld.com>
	<033d01c93979$b3cf1990$c3f0200a@cisco.com>
	<618e24240810291636q6986570as674cbe65e49a8c7b@mail.gmail.com>
Date: Wed, 29 Oct 2008 18:42:05 -0700
Message-ID: <00e801c93a30$b704b4f0$24726b80@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Ack6HyXWUgR1xPeKSYCTaX74gmiWpQAEXGfg
In-Reply-To: <618e24240810291636q6986570as674cbe65e49a8c7b@mail.gmail.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=558; t=1225330926; x=1226194926;
	c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[Sip]=20submission=20of=20a=20new=20I-D
	=3A=20=22Dialog=20Event=20foR=20IdentityVErification=22
	|Sender:=20; bh=cZAhCse1iSWh5QLa8U6rRw0S1nga6TGBpbbptHA9V+s=;
	b=gCVwm8vO1x6m2Of7XpYtshLwqATmd+THy4eRLSNRoZGu094mv8eGrvbd5y
	aeEZrw/Tm+l6txFOybeUwj4/MyqHPdMoP3/0B+1NpIErpAmxUc2yWVxpH0x6
	zxKKvjcEvy;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR
	IdentityVErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

> On Wed, Oct 29, 2008 at 4:52 AM, Dan Wing <dwing@cisco.com> wrote:
> > DERIVE is checking to see if your SIP routing takes you to the
> > same place that (claims to) be originating the incoming INVITE.
> > It is using your *outgoing* SIP routing -- which you must already
> > trust to send outbound messages -- to test the validity of the
> > (proported) From: address of an incoming INVITE.
> 
> Shall DERIVE be extended to support non-INVITE requests (e.g. 
> MESSAGE)?

Yes, it seems suitable that DERIVE be able to support any method.

-d

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


From sip-bounces@ietf.org  Wed Oct 29 18:48:48 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3D8873A6D77;
	Wed, 29 Oct 2008 18:48:48 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7A89E3A6D77
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 18:48:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.504
X-Spam-Level: 
X-Spam-Status: No, score=-6.504 tagged_above=-999 required=5
	tests=[AWL=-0.205, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rKtZ2IeHv2Gd for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 18:48:46 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 98CF63A6D76
	for <sip@ietf.org>; Wed, 29 Oct 2008 18:48:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,511,1220227200"; d="scan'208";a="111811938"
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-3.cisco.com with ESMTP; 30 Oct 2008 01:48:45 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m9U1mjkT032510; 
	Wed, 29 Oct 2008 18:48:45 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m9U1mjdb013149;
	Thu, 30 Oct 2008 01:48:45 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Paul Kyzivat'" <pkyzivat@cisco.com>,
	"=?iso-8859-1?Q?'Victor_Pascual_=C1vila'?="
	<victor.pascual.avila@gmail.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>	<D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>	<200810261145.19745.ibc@aliax.net>	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>	<084c01c938a0$a41ff390$c3f0200a@cisco.com>	<cc1f582e0810280444y42b8f723w938004e902fb1180@mail.gmail.com>	<032301c93978$6b249c70$c3f0200a@cisco.com>	<618e24240810290415i7ede4601tf2fd78aaed755445@mail.gmail.com>	<007b01c939f6$6f33e5e0$24726b80@cisco.com>
	<618e24240810291237t440f25f2hcd783d93f90d38a0@mail.gmail.com>
	<4908E9CF.7050307@cisco.com>
Date: Wed, 29 Oct 2008 18:48:44 -0700
Message-ID: <00f101c93a31$a52147c0$24726b80@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Ack6GWbLypjzhX54QBqflOS1GRat9AAF14Ww
In-Reply-To: <4908E9CF.7050307@cisco.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1589; t=1225331325;
	x=1226195325; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[Sip]=20submission=20of=20a=20new=20I-D
	=3A=20=22Dialog=20Event=09foRIdentityVErification=22
	|Sender:=20; bh=lpLENoyzHqxEHxwSKdg9pxB64s8l90b05oNX/j7mnog=;
	b=HMR+/Mmx9NGj6LEsVjO17le4HDOSkAIKPccrLwbHXa02K1V9EL3+uNHg05
	3Ed00jx7GU6GXijW7SEAYsUo6yy0nMzdqa0T3W73lBDIUbDmiLjb77BAbH2u
	kuswd+qoUI;
Authentication-Results: sj-dkim-3; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog
	Event	foRIdentityVErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

> While I agree with what you say, this only works if the verification 
> will happen in a timely way. If you want white/black lists, then the 
> verification must happen even before the phone rings. Is it 
> reasonable 
> to assume that in typical deployments the time for the reverse lookup 
> will be quick enough to give reasonable experience to the caller? Or 
> will he have already hung up? (I don't have a good sense for 
> the numbers here.)

It's an extra round trip, yes.  So are ICE, DTLS-SRTP, connectivity
preconditions, security preconditions, QoS preconditions, Connected-
Identity, and a myriad of other things.  Why should DERIVE be viewed
with derision when SIP has already enjoyed a rich history of 
additional messages to handle important cases?  And if validating
a "From:" isn't important, I have a phone call from George W. Bush
for you..

> What will the caller be hearing until this gets done? Perhaps 
> 180 could be returned, which would at least give *some* feedback.

Sure.  Let's discuss the bigger picture, though:  do we need 
something like DERIVE.

> If this takes too long, then I think it ends up being info 
> that may be delivered after the call is established. (Perhaps 
> your callerid starts out yellow and turns green when it 
> has been confirmed.)

Yep, that is a reasonable approach, too.  If/when spoofed
>From becomes a common problem (how is everyone's daily dose
of email spam today?), this allows the called party to tighten
up their local policy to only ring the phone after the From:
is validated.

-d

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


From sip-bounces@ietf.org  Wed Oct 29 19:00:02 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9BD093A6D80;
	Wed, 29 Oct 2008 19:00:02 -0700 (PDT)
X-Original-To: sip@ietf.org
Delivered-To: sip@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 8B25A3A6D80; Wed, 29 Oct 2008 19:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081030020001.8B25A3A6D80@core3.amsl.com>
Date: Wed, 29 Oct 2008 19:00:01 -0700 (PDT)
Cc: sip@ietf.org
Subject: [Sip] I-D Action:draft-ietf-sip-outbound-16.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--NextPart

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


	Title           : Managing Client Initiated Connections in the Session Initiation Protocol (SIP)
	Author(s)       : C. Jennings, R. Mahy
	Filename        : draft-ietf-sip-outbound-16.txt
	Pages           : 48
	Date            : 2008-10-29

The Session Initiation Protocol (SIP) allows proxy servers to
initiate TCP connections or to send asynchronous UDP datagrams to
User Agents in order to deliver requests.  However, in a large number
of real deployments, many practical considerations, such as the
existence of firewalls and Network Address Translators (NATs) or the
use of TLS with server-provided certificates, prevent servers from
connecting to User Agents in this way.  This specification defines
behaviors for User Agents, registrars and proxy servers that allow
requests to be delivered on existing connections established by the
User Agent.  It also defines keep alive behaviors needed to keep NAT
bindings open and specifies the usage of multiple connections from
the User Agent to its Registrar.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sip-outbound-16.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-sip-outbound-16.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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


From sip-bounces@ietf.org  Wed Oct 29 19:21:42 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C8C0D28C39F;
	Wed, 29 Oct 2008 19:21:42 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B99703A6D8A
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 19:21:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.485
X-Spam-Level: 
X-Spam-Status: No, score=-6.485 tagged_above=-999 required=5
	tests=[AWL=-0.186, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OvggRPvF1e3k for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 19:21:39 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id C05EB3A6D89
	for <sip@ietf.org>; Wed, 29 Oct 2008 19:21:39 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,511,1220227200"; d="scan'208";a="185243076"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 30 Oct 2008 02:21:39 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9U2Ld40025788; 
	Wed, 29 Oct 2008 19:21:39 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9U2LJ5a011939;
	Thu, 30 Oct 2008 02:21:27 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "=?iso-8859-1?Q?'I=F1aki_Baz_Castillo'?=" <ibc@aliax.net>, <sip@ietf.org>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com><490792EA.2020106@softarmor.com><033f01c9397b$860847a0$c3f0200a@cisco.com>
	<200810292306.44911.ibc@aliax.net>
Date: Wed, 29 Oct 2008 19:21:17 -0700
Message-ID: <000901c93a36$3d4755e0$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Ack6Eqw4Bewmjh3JRaWYol6CZoh4xAAIXhUg
In-Reply-To: <200810292306.44911.ibc@aliax.net>
x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.3350
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1224; t=1225333299;
	x=1226197299; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[Sip]=20Comment=20on=20DERIVE=20and=20B
	2BUAs |Sender:=20;
	bh=6toCfo47NOdHwomspi2qY7LuGTIYrxkaD6tzURuaWTk=;
	b=bwcIlvlw8/tD7Fwh2k+dljLcpcbXomhWPHAec6zm0sB5oPTvnM8Iqf11Nb
	KxyGET/2Z6WeYSignlyPhJk6hfBvbT9r3tJX5/VRt0F+Gf/+n6wNIBgkhnuB
	Wvcvlr+6rm;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

> El Mi=E9rcoles, 29 de Octubre de 2008, Dan Wing escribi=F3:
> > > Would the SBC not have to handle the SUBSCRIBE request =

> locally? After
> > > all, since it is a terminal UA for the call, it also knows
> > > about all the
> > > dialog states. The end-user UA would never even see the SUBSCRIBE.
> >
> > If that's a problem, just use some different method that goes end to
> > end. =A0The always-loved INFO comes to mind.
> =

> Anyway, you need to carry in the INFO body (or headers) data =

> about the current =

> dialog, but this data changes in both legs of the B2BUA, so =

> it will fail.
> It's exactly the same case as if the SUBSCRIBE is "forwarded" =

> between B2BUA =

> legs without replacing the dialog data (from leg B to leg A).

And that is why there are two proposals that use something that
can't change -- the certificate fingerprint of the endpoint:

  draft-fischer-sip-e2e-sec-media (expired)
  draft-wing-sip-identity-media (expired)

They expired due to lack of interest.


Let's talk about the meta-issue:  do we want assurance of a =

"From:" over SBCs?  If so, let us please convince the ADs =

in Minneapolis and let us please get a new SIP milestone.

-d

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


From sip-bounces@ietf.org  Wed Oct 29 21:54:29 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5487D3A699E;
	Wed, 29 Oct 2008 21:54:29 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E21AE3A699E
	for <sip@core3.amsl.com>; Wed, 29 Oct 2008 21:54:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BBjvCS8Uxzb0 for <sip@core3.amsl.com>;
	Wed, 29 Oct 2008 21:54:28 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 0E8963A680F
	for <sip@ietf.org>; Wed, 29 Oct 2008 21:54:27 -0700 (PDT)
Received: from [192.168.2.102] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9U4s29f022352
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Wed, 29 Oct 2008 23:54:04 -0500
Message-Id: <17345A0C-8BFD-4D0D-B597-ECA8801F72D5@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Dan Wing <dwing@cisco.com>
In-Reply-To: <000901c93a36$3d4755e0$c3f0200a@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 29 Oct 2008 23:53:56 -0500
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com><490792EA.2020106@softarmor.com><033f01c9397b$860847a0$c3f0200a@cisco.com>
	<200810292306.44911.ibc@aliax.net>
	<000901c93a36$3d4755e0$c3f0200a@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: sip@ietf.org
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 29, 2008, at 9:21 PM, Dan Wing wrote:
>
> Let's talk about the meta-issue:  do we want assurance of a
> "From:" over SBCs?  If so, let us please convince the ADs
> in Minneapolis and let us please get a new SIP milestone.

I'd rather charter a SIP RRC working group than put a new milestone in  
SIP.

This seems like a perfect item for a working group that could conclude  
in a reasonable and timely fashion.

--
Dean

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


From sip-bounces@ietf.org  Wed Oct 29 22:45:03 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C643B28C111;
	Wed, 29 Oct 2008 22:45:03 -0700 (PDT)
X-Original-To: sip@ietf.org
Delivered-To: sip@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 922853A6C71; Wed, 29 Oct 2008 22:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081030054501.922853A6C71@core3.amsl.com>
Date: Wed, 29 Oct 2008 22:45:01 -0700 (PDT)
Cc: sip@ietf.org
Subject: [Sip] I-D Action:draft-ietf-sip-ua-privacy-03.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--NextPart

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


	Title           : UA-Driven Privacy Mechanism for SIP
	Author(s)       : M. Munakata, et al.
	Filename        : draft-ietf-sip-ua-privacy-03.txt
	Pages           : 12
	Date            : 2008-10-29

This document defines a best current practice for a user agent to
generate an anonymous SIP message by utilizing mechanisms such as
GRUU (Globally Routable User Agent URIs) and TURN (Traversal Using
Relays around NAT) without the need for a privacy service defined in
RFC 3323.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sip-ua-privacy-03.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-sip-ua-privacy-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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


From sip-bounces@ietf.org  Thu Oct 30 00:15:11 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DD1EF3A684F;
	Thu, 30 Oct 2008 00:15:11 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7695D3A684F
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 00:15:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id xxggJnnyCKT1 for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 00:15:10 -0700 (PDT)
Received: from tutpro.com (sip.tutpro.com [192.98.100.10])
	by core3.amsl.com (Postfix) with ESMTP id 9DAD33A6405
	for <sip@ietf.org>; Thu, 30 Oct 2008 00:15:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by tutpro.com (Postfix) with ESMTP id 000F21EC311;
	Thu, 30 Oct 2008 09:14:57 +0200 (EET)
Received: from tutpro.com ([127.0.0.1])
	by localhost (tutpro.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id xlx1V7QjCXCM; Thu, 30 Oct 2008 09:14:56 +0200 (EET)
Received: from rautu (h007096.gprs.dnafinland.fi [87.93.7.96])
	(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by tutpro.com (Postfix) with ESMTPSA;
	Thu, 30 Oct 2008 09:14:56 +0200 (EET)
Received: by rautu (Postfix, from userid 1000)
	id B97D719406D; Thu, 30 Oct 2008 09:14:40 +0200 (EET)
MIME-Version: 1.0
Message-ID: <18697.24288.601088.439365@tutpro.com>
Date: Thu, 30 Oct 2008 09:14:40 +0200
To: "Francois Audet" <audet@nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF1A0B455E@zrc2hxm0.corp.nortel.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
	<cc1f582e0810281052y34f5bf88h300c6f59d84879fe@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D00138295A@GBNTHT12009MSX.gb002.siemens.net>
	<490793BF.10702@softarmor.com>
	<034601c9397d$1e055150$c3f0200a@cisco.com>
	<1ECE0EB50388174790F9694F77522CCF1A0B455E@zrc2hxm0.corp.nortel.com>
X-Mailer: VM 8.0.9 under Emacs 22.2.1 (i486-pc-linux-gnu)
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, "Elwell, John" <john.elwell@siemens.com>,
	Dan Wing <dwing@cisco.com>, Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Francois Audet writes:

 > Instead of using a SUBSCRIBE or even INFO, it seems appropriate
 > to use OPTIONS.

then you are back to my pre-presence proposal (which is fine with me
too).

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


From sip-bounces@ietf.org  Thu Oct 30 01:12:12 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8408C3A68F8;
	Thu, 30 Oct 2008 01:12:12 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A028B3A6901
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 01:12:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.115
X-Spam-Level: 
X-Spam-Status: No, score=-2.115 tagged_above=-999 required=5 tests=[AWL=0.184, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id r9OpUi7IquDs for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 01:12:09 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id 2D4443A686B
	for <sip@ietf.org>; Thu, 30 Oct 2008 01:12:06 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K9J0050YLG1ZI@siemenscomms.co.uk> for sip@ietf.org; Thu,
	30 Oct 2008 08:12:01 +0000 (GMT)
Date: Thu, 30 Oct 2008 08:12:00 +0000
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <000901c93a36$3d4755e0$c3f0200a@cisco.com>
To: Dan Wing <dwing@cisco.com>,
	=?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>, sip@ietf.org
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D001382DE8@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] Comment on DERIVE and B2BUAs
Thread-Index: Ack6Eqw4Bewmjh3JRaWYol6CZoh4xAAIXhUgAAy4wYA=
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<490792EA.2020106@softarmor.com>
	<033f01c9397b$860847a0$c3f0200a@cisco.com>
	<200810292306.44911.ibc@aliax.net>
	<000901c93a36$3d4755e0$c3f0200a@cisco.com>
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 =


> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On =

> Behalf Of Dan Wing
> Sent: 30 October 2008 02:21
> To: 'I=F1aki Baz Castillo'; sip@ietf.org
> Subject: Re: [Sip] Comment on DERIVE and B2BUAs
> =

> > El Mi=E9rcoles, 29 de Octubre de 2008, Dan Wing escribi=F3:
> > > > Would the SBC not have to handle the SUBSCRIBE request =

> > locally? After
> > > > all, since it is a terminal UA for the call, it also knows
> > > > about all the
> > > > dialog states. The end-user UA would never even see the =

> SUBSCRIBE.
> > >
> > > If that's a problem, just use some different method that =

> goes end to
> > > end. =A0The always-loved INFO comes to mind.
> > =

> > Anyway, you need to carry in the INFO body (or headers) data =

> > about the current =

> > dialog, but this data changes in both legs of the B2BUA, so =

> > it will fail.
> > It's exactly the same case as if the SUBSCRIBE is "forwarded" =

> > between B2BUA =

> > legs without replacing the dialog data (from leg B to leg A).
> =

> And that is why there are two proposals that use something that
> can't change -- the certificate fingerprint of the endpoint:
> =

>   draft-fischer-sip-e2e-sec-media (expired)
>   draft-wing-sip-identity-media (expired)
> =

> They expired due to lack of interest.
> =

> =

> Let's talk about the meta-issue:  do we want assurance of a =

> "From:" over SBCs?  If so, let us please convince the ADs =

> in Minneapolis and let us please get a new SIP milestone.
[JRE] Agreed. DERIVE (or something derived from it) would then be one of th=
e candidates.

John

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


From sip-bounces@ietf.org  Thu Oct 30 03:34:44 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1FDDC3A6AEE;
	Thu, 30 Oct 2008 03:34:44 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A8D6D3A6AEE
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 03:34:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.181
X-Spam-Level: 
X-Spam-Status: No, score=-2.181 tagged_above=-999 required=5 tests=[AWL=0.418, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id f7z+umyi2AHz for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 03:34:41 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39])
	by core3.amsl.com (Postfix) with ESMTP id C12563A690D
	for <sip@ietf.org>; Thu, 30 Oct 2008 03:34:41 -0700 (PDT)
Received: from ilexp03.ndc.lucent.com (h135-3-39-50.lucent.com [135.3.39.50])
	by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id m9UAXB7U017590; 
	Thu, 30 Oct 2008 05:34:08 -0500 (CDT)
Received: from DEEXP02.DE.lucent.com ([135.248.187.66]) by
	ilexp03.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Oct 2008 05:33:58 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.28]) by
	DEEXP02.DE.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Oct 2008 11:33:56 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 30 Oct 2008 11:33:54 +0100
Message-ID: <5D1A7985295922448D5550C94DE291800245C0C7@DEEXC1U01.de.lucent.com>
In-Reply-To: <17345A0C-8BFD-4D0D-B597-ECA8801F72D5@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Comment on DERIVE and B2BUAs
Thread-Index: Ack6S54OflWW2QcUROqWFAHxYvsRRAALjzNg
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com><490792EA.2020106@softarmor.com><033f01c9397b$860847a0$c3f0200a@cisco.com><200810292306.44911.ibc@aliax.net><000901c93a36$3d4755e0$c3f0200a@cisco.com>
	<17345A0C-8BFD-4D0D-B597-ECA8801F72D5@softarmor.com>
From: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: "Dean Willis" <dean.willis@softarmor.com>, "Dan Wing" <dwing@cisco.com>,
	<sip@ietf.org>
X-OriginalArrivalTime: 30 Oct 2008 10:33:56.0234 (UTC)
	FILETIME=[02FDB6A0:01C93A7B]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

(As WG cochair)

The group with current scope for this work is SIP. Therefore if the SIP
WG believes it can make progress in identifying valid work in the SIP
timeframe, the chairs can ask the RAI ADs for a charter milestone. The
ADs can choose to direct that milestone to some other group if they so
wish.

There is a separate RAIarea agenda slot where people can discuss their
ideas on future RAI WG structure. That discussion does not need to
impact on whether this is valid IETF work or not.

So core to the discussion is whether we feel we can get an agreement for
a suitable area of identity related work in Minneapolis based on
discussion of this draft. If the answer is no, the chairs will push it
down the priority order in allocating agenda slots. If the answer is yes
then we push it up the priority. (Note that the same applies for all the
other active identity related documents). 

Note also that we would also like to see any discussion in this area
bringing in new issues and points. There is little point in the same
people standing up at the mic and saying the same things they said in
Dublin, as presumably, we will end up with the same absence of decision.

With this in mind, the chairs welcome discussion on this list, and in
private emails, to see if something can come out of this.

Regards

Keith

 

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Dean Willis
> Sent: Thursday, October 30, 2008 4:54 AM
> To: Dan Wing
> Cc: sip@ietf.org
> Subject: Re: [Sip] Comment on DERIVE and B2BUAs
> 
> 
> On Oct 29, 2008, at 9:21 PM, Dan Wing wrote:
> >
> > Let's talk about the meta-issue:  do we want assurance of a "From:" 
> > over SBCs?  If so, let us please convince the ADs in 
> Minneapolis and 
> > let us please get a new SIP milestone.
> 
> I'd rather charter a SIP RRC working group than put a new 
> milestone in SIP.
> 
> This seems like a perfect item for a working group that could 
> conclude in a reasonable and timely fashion.
> 
> --
> Dean
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors@cs.columbia.edu for questions on current sip 
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 30 09:58:52 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 419E73A694C;
	Thu, 30 Oct 2008 09:58:52 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 410DA3A694C
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 09:58:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 7lWevfEAD0CN for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 09:58:49 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 71E893A6881
	for <SIP@ietf.org>; Thu, 30 Oct 2008 09:58:49 -0700 (PDT)
Received: from [75.68.119.237] (port=63799 helo=[192.168.15.102])
	by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1Kvar5-0005fS-2W for SIP@ietf.org; Thu, 30 Oct 2008 09:58:43 -0700
Message-Id: <A91408BF-6356-4D69-B96E-02428C6A136C@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: SIP IETF <SIP@ietf.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 30 Oct 2008 12:03:43 -0400
X-Mailer: Apple Mail (2.929.2)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: [Sip] E-Mail Address
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0434444120=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--===============0434444120==
Content-Type: multipart/signed; boundary=Apple-Mail-70-114804281; micalg=sha1; protocol="application/pkcs7-signature"


--Apple-Mail-70-114804281
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

It looks like people have been trying to reach me at my BEA address.   
Oracle bought BEA; I'm getting my pilot's license.

You can reach me at eburger@standardstrack.com
--Apple-Mail-70-114804281
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGPTCCBjkw
ggUhoAMCAQICEC+VK1RLWxrF8KJZDR9k8p8wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYTAlVT
MQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VS
VFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQD
Ey1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwwHhcNMDgwODEz
MDAwMDAwWhcNMDkwODEzMjM1OTU5WjCB4TE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsg
LSBQRVJTT05BIE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9m
IHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDMg
Q29tb2RvIExpbWl0ZWQxFDASBgNVBAMTC0VyaWMgQnVyZ2VyMSkwJwYJKoZIhvcNAQkBFhplYnVy
Z2VyQHN0YW5kYXJkc3RyYWNrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMTF
RRoA4LgOACMFph0aomRC/UpqoA5C/d6DUTOvTMrYSEqkjwnU4zxDtBcHlcB4AxKAov00MYsUvEU4
loz7BHjfDjv76AIkcwu33VYQbzGmarVnyaXsVb6f/cyRL3fPT0VOVO2tQAEEgwg//CX0jN8Kn2jH
uXD/HEvko7cmpL3Pwevf3+DwB61v7ca79PpEZfn/WhaqRKA4uVNPj/JbieeaLo2v/0RJzrEElZK0
pHCqxiD3mQ8ossPkA9fUCSxLlbdMcPU3be5x8vt8Q8mYTXF5Z3d9RZmYrmNkvTQtdzVpfYWr/hgV
Xqm9tByOOAR+hoN3FKbubR/OrAHL9yDAd4sCAwEAAaOCAhwwggIYMB8GA1UdIwQYMBaAFImCZ33E
nSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBRDWgutb7b8R/L7G3Y3D+molAA3VzAOBgNVHQ8BAf8E
BAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJ
YIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEW
HWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMIGlBgNVHR8EgZ0wgZowTKBKoEiGRmh0dHA6
Ly9jcmwuY29tb2RvY2EuY29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRF
bWFpbC5jcmwwSqBIoEaGRGh0dHA6Ly9jcmwuY29tb2RvLm5ldC9VVE4tVVNFUkZpcnN0LUNsaWVu
dEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMGwGCCsGAQUFBwEBBGAwXjA2BggrBgEFBQcwAoYq
aHR0cDovL2NydC5jb21vZG9jYS5jb20vVVROQUFBQ2xpZW50Q0EuY3J0MCQGCCsGAQUFBzABhhho
dHRwOi8vb2NzcC5jb21vZG9jYS5jb20wJQYDVR0RBB4wHIEaZWJ1cmdlckBzdGFuZGFyZHN0cmFj
ay5jb20wDQYJKoZIhvcNAQEFBQADggEBAGeBR7NPCvrY3GQoIi49JOuciatY2r4st905Jw1etp6J
umFFWlaCBl11tFSclk/3S45B+lUv3SEvG4CEjUByPScprVmCqHR+y8BAQaB/CV+N1y14x3MbhJ+Z
8XDGKeUXuuyGd9w0l3/t/QPid6TRXQjQFrLPFs1IALuNpNiFMHEF/xFbMG1Z2vznR/gSPlePekoZ
TqcExIDBNZTBebpZqwAXzPpedNNOclbMLFLWDMOAozVRpkfjI0eiFsk8SF1Ho1Gb9Bx8DeG4peE2
KRVOR9FFnZZgBpFjXYRcglsMOSKCY8HgE+NGvbbqbrMoBV/BlYyxRXwfti71RL9Zs2Cq1eQxggP8
MIID+AIBATCBwzCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExh
a2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8v
d3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkNH2TynzAJBgUrDgMCGgUAoIICDTAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wODEwMzAxNjAzNDRaMCMGCSqGSIb3
DQEJBDEWBBQvzKiNAVCHf+1D5PHmAI8dbHGaQjCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD
VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU
aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2
MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv
lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN
H2TynzANBgkqhkiG9w0BAQEFAASCAQBigrUjx5gYfFASMgu99f/7m/4LRSyWaZVS0xCmTPdtktpT
B5lsY/GA9GtlSW7qI5wFNhGXTClB3DEeTy6XY9YiHMhzpGwdL4rBOygj+UqyuF+sr6bvskZOmoZy
jZXKkkkT2UDUpmHY/zwWuEl71WlGHyWR33iHF8ffoqf6A1jn2h4eu/cuayMyUQin/dGPC9xKcyJZ
vUyPeQofL95NSQhzNtHwYqEaecf1JiVmQyTqzGQFZbiwalD7+yff/MYvhgIWmHqHoL+qZxve8aJ7
1tpVWNCIxY8dsvXPvJ+AlK8QFk4HtIYhehSxDlTiKvP4NaaE/tawCF7LUX1KQjAzLzRfAAAAAAAA

--Apple-Mail-70-114804281--

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

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


From sip-bounces@ietf.org  Thu Oct 30 10:34:48 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BCB483A6AA7;
	Thu, 30 Oct 2008 10:34:48 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B8EA33A6AB4
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 10:34:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9GL011zTFQ69 for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 10:34:47 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id F12373A6AA7
	for <sip@ietf.org>; Thu, 30 Oct 2008 10:34:46 -0700 (PDT)
Received: from [75.68.119.237] (port=63891 helo=[192.168.15.102])
	by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1KvbPQ-0003No-S5; Thu, 30 Oct 2008 10:34:13 -0700
Message-Id: <81521DF0-2666-4500-BE62-412FBB6966A7@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
In-Reply-To: <48FDECB5.3030607@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 30 Oct 2008 12:13:57 -0400
References: <20081020231502.43DCA3A69EF@core3.amsl.com>
	<48FDECB5.3030607@cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: SIP IETF <sip@ietf.org>
Subject: [Sip] Legacy Info Package Registration
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1173826224=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--===============1173826224==
Content-Type: multipart/signed; boundary=Apple-Mail-71-115418067; micalg=sha1; protocol="application/pkcs7-signature"


--Apple-Mail-71-115418067
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

We discussed creating a registry, and we discussed whether it would be  
in this document.

On the one hand, the discussion was not conclusive.  On the other,  
here are my reasons for not including it in the Info Packages document:

1. We go at lengths to say how to do Info Packages.  The last thing we  
need to do is say, "by the way, it's not so bad if you don't."

2. People not involved today will look at such a registry and, no  
matter how much doom and gloom wording we use, will think it's OK to  
not use Info Packages.

3. People will be confused, thinking Content-Type is sufficient to  
identify an Info Package.  It is not.

4. How would we possibly police the registry? If someone comes to IANA  
to register a new MIME type do the klaxons ring?  That would not be a  
good thing.

So, time for another poll:
[ ] Yes - we really, really need an IANA registry of "legacy" INFO  
usages, and we need it done in this draft
     (NOTE: creating the IANA registry requires the seed values, which  
means this draft will enumerate the
      known legacy usages)

[ ] No, do not create an IANA registry, but please enumerate known  
legacy usages in this draft

[ ] No - please do not create an IANA registry

[ ] Punt - I may or may not want an IANA registry, but if we do create  
one, do it in another draft

[ ] Other: ________________________________



On Oct 21, 2008, at 10:52 AM, Paul Kyzivat wrote:

> Regarding registration if INFO packages - I thought we also wanted  
> to introduce a registry for legacy usages of INFO, to encourage them  
> to come out into the daylight. I guess maybe that would be a  
> separate registry, since the key for it will have to be Content- 
> Type. So it *could* be established from a different document. But I  
> think this is the likely place to do it, since its the place where  
> all the eyeballs will be. I think the rule for registering those  
> needs to be that one can only be registered if the Content-Type has  
> not already been registered, and it was in *use* with INFO prior to  
> this document becoming an RFC. (The registration itself could be  
> done later. I guess it would be the honor system.) Any usages being  
> deployed after this becomes an RFC would be required to use the new  
> mechanism.

--Apple-Mail-71-115418067
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGPTCCBjkw
ggUhoAMCAQICEC+VK1RLWxrF8KJZDR9k8p8wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYTAlVT
MQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VS
VFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQD
Ey1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwwHhcNMDgwODEz
MDAwMDAwWhcNMDkwODEzMjM1OTU5WjCB4TE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsg
LSBQRVJTT05BIE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9m
IHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDMg
Q29tb2RvIExpbWl0ZWQxFDASBgNVBAMTC0VyaWMgQnVyZ2VyMSkwJwYJKoZIhvcNAQkBFhplYnVy
Z2VyQHN0YW5kYXJkc3RyYWNrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMTF
RRoA4LgOACMFph0aomRC/UpqoA5C/d6DUTOvTMrYSEqkjwnU4zxDtBcHlcB4AxKAov00MYsUvEU4
loz7BHjfDjv76AIkcwu33VYQbzGmarVnyaXsVb6f/cyRL3fPT0VOVO2tQAEEgwg//CX0jN8Kn2jH
uXD/HEvko7cmpL3Pwevf3+DwB61v7ca79PpEZfn/WhaqRKA4uVNPj/JbieeaLo2v/0RJzrEElZK0
pHCqxiD3mQ8ossPkA9fUCSxLlbdMcPU3be5x8vt8Q8mYTXF5Z3d9RZmYrmNkvTQtdzVpfYWr/hgV
Xqm9tByOOAR+hoN3FKbubR/OrAHL9yDAd4sCAwEAAaOCAhwwggIYMB8GA1UdIwQYMBaAFImCZ33E
nSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBRDWgutb7b8R/L7G3Y3D+molAA3VzAOBgNVHQ8BAf8E
BAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJ
YIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEW
HWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMIGlBgNVHR8EgZ0wgZowTKBKoEiGRmh0dHA6
Ly9jcmwuY29tb2RvY2EuY29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRF
bWFpbC5jcmwwSqBIoEaGRGh0dHA6Ly9jcmwuY29tb2RvLm5ldC9VVE4tVVNFUkZpcnN0LUNsaWVu
dEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMGwGCCsGAQUFBwEBBGAwXjA2BggrBgEFBQcwAoYq
aHR0cDovL2NydC5jb21vZG9jYS5jb20vVVROQUFBQ2xpZW50Q0EuY3J0MCQGCCsGAQUFBzABhhho
dHRwOi8vb2NzcC5jb21vZG9jYS5jb20wJQYDVR0RBB4wHIEaZWJ1cmdlckBzdGFuZGFyZHN0cmFj
ay5jb20wDQYJKoZIhvcNAQEFBQADggEBAGeBR7NPCvrY3GQoIi49JOuciatY2r4st905Jw1etp6J
umFFWlaCBl11tFSclk/3S45B+lUv3SEvG4CEjUByPScprVmCqHR+y8BAQaB/CV+N1y14x3MbhJ+Z
8XDGKeUXuuyGd9w0l3/t/QPid6TRXQjQFrLPFs1IALuNpNiFMHEF/xFbMG1Z2vznR/gSPlePekoZ
TqcExIDBNZTBebpZqwAXzPpedNNOclbMLFLWDMOAozVRpkfjI0eiFsk8SF1Ho1Gb9Bx8DeG4peE2
KRVOR9FFnZZgBpFjXYRcglsMOSKCY8HgE+NGvbbqbrMoBV/BlYyxRXwfti71RL9Zs2Cq1eQxggP8
MIID+AIBATCBwzCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExh
a2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8v
d3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkNH2TynzAJBgUrDgMCGgUAoIICDTAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wODEwMzAxNjEzNTdaMCMGCSqGSIb3
DQEJBDEWBBSj0LAGHq80qvZD3mXkLMJvwmPPizCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD
VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU
aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2
MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv
lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN
H2TynzANBgkqhkiG9w0BAQEFAASCAQBJVGmYe0zRR9+A6on33W2uAQD8PObq4PFDvDfGpO8cJ6ca
Gd+zUWvTZxcpaaqVJZkr5yViVF9fx04tkH24xyrCGUmf8Vjc0yc3ce/vBgyMMZ4OdaLTMOMenokw
d+uxgfxPC3JiYAI0+1ojgP+7QLTmoIo4knAd4uBSqpow8cM6nU9RjqzynUn2aFK28+C5gAVsgrC2
+c/Plgc0qODcnApMEeFee2oUyBqv8bRuDazbQDy+WoI8i7/t2GN6BQZAJJQ8LLX42kpzc8wTwiRo
AuWLZGqtMUaIKnOdY0IaSmfv+sp7dI2nVFBtHH5FC+HXhmyhwqlRmgREDn4YSe2l7lFvAAAAAAAA

--Apple-Mail-71-115418067--

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

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


From sip-bounces@ietf.org  Thu Oct 30 10:34:54 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C55D428C143;
	Thu, 30 Oct 2008 10:34:54 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E834A28C148
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 10:34:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id G9a6P-SxbcT3 for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 10:34:52 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 32CE328C12F
	for <SIP@ietf.org>; Thu, 30 Oct 2008 10:34:52 -0700 (PDT)
Received: from c-75-68-119-237.hsd1.nh.comcast.net ([75.68.119.237]:63891
	helo=[192.168.15.102])
	by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1KvbPT-0003No-2p for SIP@ietf.org; Thu, 30 Oct 2008 10:34:15 -0700
Message-Id: <C99A6E88-8550-45D8-BBD1-A37D91026317@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: SIP IETF <SIP@ietf.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 30 Oct 2008 12:31:55 -0400
X-Mailer: Apple Mail (2.929.2)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: [Sip] Comment: Info Events and Events and SUBSCRIBE/NOTIFY
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1695555615=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--===============1695555615==
Content-Type: multipart/signed; boundary=Apple-Mail-72-116496583; micalg=sha1; protocol="application/pkcs7-signature"


--Apple-Mail-72-116496583
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

The word "event"/"events" occurs precisely three times in the Info  
Packages document.  Two instances of the word describe SUBSCRIBE/ 
NOTIFY events.  The last instance is in the sentence "This includes  
detailed information about what events cause the UA to send an INFO  
request." Here we are talking about an event in a computer science  
context.

The word "event" does not appear in the title of the draft.

However, there is an unfortunate bit of legacy surrounding this draft,  
which I suppose is not surprising for the topic: the FILENAME of the  
draft is "info-events".

PLEASE do not think there will be any confusion because of the draft  
name - that will go away once this gets published.
--Apple-Mail-72-116496583
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGPTCCBjkw
ggUhoAMCAQICEC+VK1RLWxrF8KJZDR9k8p8wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYTAlVT
MQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VS
VFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQD
Ey1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwwHhcNMDgwODEz
MDAwMDAwWhcNMDkwODEzMjM1OTU5WjCB4TE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsg
LSBQRVJTT05BIE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9m
IHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDMg
Q29tb2RvIExpbWl0ZWQxFDASBgNVBAMTC0VyaWMgQnVyZ2VyMSkwJwYJKoZIhvcNAQkBFhplYnVy
Z2VyQHN0YW5kYXJkc3RyYWNrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMTF
RRoA4LgOACMFph0aomRC/UpqoA5C/d6DUTOvTMrYSEqkjwnU4zxDtBcHlcB4AxKAov00MYsUvEU4
loz7BHjfDjv76AIkcwu33VYQbzGmarVnyaXsVb6f/cyRL3fPT0VOVO2tQAEEgwg//CX0jN8Kn2jH
uXD/HEvko7cmpL3Pwevf3+DwB61v7ca79PpEZfn/WhaqRKA4uVNPj/JbieeaLo2v/0RJzrEElZK0
pHCqxiD3mQ8ossPkA9fUCSxLlbdMcPU3be5x8vt8Q8mYTXF5Z3d9RZmYrmNkvTQtdzVpfYWr/hgV
Xqm9tByOOAR+hoN3FKbubR/OrAHL9yDAd4sCAwEAAaOCAhwwggIYMB8GA1UdIwQYMBaAFImCZ33E
nSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBRDWgutb7b8R/L7G3Y3D+molAA3VzAOBgNVHQ8BAf8E
BAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJ
YIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEW
HWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMIGlBgNVHR8EgZ0wgZowTKBKoEiGRmh0dHA6
Ly9jcmwuY29tb2RvY2EuY29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRF
bWFpbC5jcmwwSqBIoEaGRGh0dHA6Ly9jcmwuY29tb2RvLm5ldC9VVE4tVVNFUkZpcnN0LUNsaWVu
dEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMGwGCCsGAQUFBwEBBGAwXjA2BggrBgEFBQcwAoYq
aHR0cDovL2NydC5jb21vZG9jYS5jb20vVVROQUFBQ2xpZW50Q0EuY3J0MCQGCCsGAQUFBzABhhho
dHRwOi8vb2NzcC5jb21vZG9jYS5jb20wJQYDVR0RBB4wHIEaZWJ1cmdlckBzdGFuZGFyZHN0cmFj
ay5jb20wDQYJKoZIhvcNAQEFBQADggEBAGeBR7NPCvrY3GQoIi49JOuciatY2r4st905Jw1etp6J
umFFWlaCBl11tFSclk/3S45B+lUv3SEvG4CEjUByPScprVmCqHR+y8BAQaB/CV+N1y14x3MbhJ+Z
8XDGKeUXuuyGd9w0l3/t/QPid6TRXQjQFrLPFs1IALuNpNiFMHEF/xFbMG1Z2vznR/gSPlePekoZ
TqcExIDBNZTBebpZqwAXzPpedNNOclbMLFLWDMOAozVRpkfjI0eiFsk8SF1Ho1Gb9Bx8DeG4peE2
KRVOR9FFnZZgBpFjXYRcglsMOSKCY8HgE+NGvbbqbrMoBV/BlYyxRXwfti71RL9Zs2Cq1eQxggP8
MIID+AIBATCBwzCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExh
a2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8v
d3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkNH2TynzAJBgUrDgMCGgUAoIICDTAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wODEwMzAxNjMxNTZaMCMGCSqGSIb3
DQEJBDEWBBSV+ouYvELvdnqcsQR0942i+MRxdzCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD
VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU
aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2
MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv
lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN
H2TynzANBgkqhkiG9w0BAQEFAASCAQC/Ob1q47mkGu2BXjuI8foQb39EmiTQxQWACjfD5Rvw0LIM
xXsgWzSbTfdvPPfIDBEsr/stGB74qwu8QGMyePf8tTNWFJtoOWLbGXPOPpn0Mc+fFy3wMTjyRge8
naEMDj8kOf9W74y9Sg/NWFehlYl2+V4Znc+VhEijrcBG/y+FUjWJa0U564r8UHroAg4GGo+aKuEr
+eJ2f0fh8pbbke7Y8Q+um1GgCtuXB88wQfyyJgiZNQmF+0YyM+UpPeeehZn3AZHesLu4afPnPT7m
l/3lTaRrbLrVmGU2RtzOCLeF4XwE4aTHG8D6W+r/w1omQM2A4g4tKhV0DTXUar0CU35BAAAAAAAA

--Apple-Mail-72-116496583--

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

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


From sip-bounces@ietf.org  Thu Oct 30 10:34:55 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7975828C161;
	Thu, 30 Oct 2008 10:34:55 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5CF5728C12F
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 10:34:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id bEUDQa7TIX13 for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 10:34:52 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 9427628C143
	for <sip@ietf.org>; Thu, 30 Oct 2008 10:34:52 -0700 (PDT)
Received: from c-75-68-119-237.hsd1.nh.comcast.net ([75.68.119.237]:63891
	helo=[192.168.15.102])
	by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1KvbPT-0003No-SK; Thu, 30 Oct 2008 10:34:16 -0700
Message-Id: <0E7B9938-E8A0-44D2-AB3F-F77B9FF6E731@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: Salvatore Loreto <salvatore.loreto@ericsson.com>
In-Reply-To: <4903478E.9040402@ericsson.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 30 Oct 2008 12:43:46 -0400
References: <20081020231502.43DCA3A69EF@core3.amsl.com>
	<48FDECB5.3030607@cisco.com> <4903478E.9040402@ericsson.com>
X-Mailer: Apple Mail (2.929.2)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Legacy usage of INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I see this as no worse than what we have today, and there is little we  
can do about it.  A bad UAC implementation is a bad UAC.

Unfortunately, this is one of those excuses for an SBC...


On Oct 25, 2008, at 12:21 PM, Salvatore Loreto wrote:

> the following paragraph of Section 5.2 puzzles me:
>
>  If a server receives an INFO request with a body it understands, but
>  it has no Info-Package header, the UAS MAY render the body.  Note the
>  semantics of "rendering" is up to the Info Package definition.  The
>  UAS MUST respond to the INFO request with a 200 OK.  This enables
>  legacy use of INFO.
>
>
> Now it states that is to enable legacy use of INFO, but at same time  
> refer to the Info Package definition
> that is something only for the new usage.
>
> IMO with this text it would be possible send also an INFO request  
> the other end is not willing to receive,
> it is enough not include the Info-Package header. Is this can be  
> seen as a possible security problem?
>
> Thanks
> Sal
>
>
> Paul Kyzivat wrote:
>> While I see rules in 5.1 and 6 that permit use of legacy packages  
>> at the INFO UAS, I find no rules that permit sending a legacy INFO.  
>> I guess it must be possible to use legacy INFO even when both sides  
>> support this new info package mechanism. And I guess the evidence  
>> that a UA *doesn't* support this new mechanism (by the absence of  
>> the headers in request/response) is just equivalent to one that  
>> explicitly negotiates support of no packages.
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 30 10:34:56 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2650428C17F;
	Thu, 30 Oct 2008 10:34:56 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AA69F28C12F
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 10:34:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ywlLnAosFB5u for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 10:34:52 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id DD8ED28C147
	for <sip@ietf.org>; Thu, 30 Oct 2008 10:34:52 -0700 (PDT)
Received: from c-75-68-119-237.hsd1.nh.comcast.net ([75.68.119.237]:63891
	helo=[192.168.15.102])
	by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1KvbPU-0003No-Q8 for sip@ietf.org; Thu, 30 Oct 2008 10:34:16 -0700
Message-Id: <B4D5D87C-2EA1-49AD-A3CE-3F463C8E978F@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: SIP IETF <sip@ietf.org>
In-Reply-To: <4900D982.4050007@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 30 Oct 2008 12:45:25 -0400
References: <48FDEAD8.8010803@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889E49A@esealmw113.eemea.ericsson.se>
	<48FF2C45.7010204@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF088F10A7@esealmw113.eemea.ericsson.se>
	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>
	<4900C09A.9060104@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCF9F@esealmw113.eemea.ericsson.se>
	<4900D982.4050007@cisco.com>
X-Mailer: Apple Mail (2.929.2)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs
	Info-Package [was RE: draft-ietf-sip-info-events-00: multiple
	packages per INFO]
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Correct.

On Oct 23, 2008, at 4:07 PM, Paul Kyzivat wrote:

>
>
> Christer Holmberg wrote:
>> Hi,
>> Let's assume I want to send an INFO with package foo.
>> The value of the Info-Package header is "foo", right?
>> Now, what is the value of the Content-Type header?
>
> The package could support a number of content types: image/jpeg,  
> text/plain, multipart/related, ...
> Anything that the definition of the package says is allowed.
>
> At least that is how I think Eric intended to to be.
>
> 	Paul
>
>> Is it something which is generic for all info packages (e.g.  
>> application/info), OR is it something which is specified in the foo  
>> package description?
>> Regards,
>> Christer
>> ________________________________
>> From: Paul Kyzivat [mailto:pkyzivat@cisco.com]
>> Sent: Thu 23/10/2008 20:21
>> To: Christer Holmberg
>> Cc: Dean Willis; SIP IETF; Eric Burger
>> Subject: Re: [Sip] draft-ietf-sip-info-events-00: Content-Type vs  
>> Info-Package [was RE: draft-ietf-sip-info-events-00: multiple  
>> packages per INFO]
>> Christer,
>> I don't understand where you are heading with this?
>> If I want to send an INFO with a jpeg, then what is this other mime  
>> type
>> doing other than getting in my way.
>> OTOH, we haven't discussed Content-Disposition wrt INFO. In the  
>> absence
>> of any mention, I assume that "render" will be used for info  
>> packages,
>> and the detailed processing defined by the Info-Package value.
>> In some sense, the Info-Package value is serving the same purpose as
>> Content-Disposition. We could *consider* using the C-D *instead* of  
>> the
>> Info-Package header, so that what we would be negotiating would be  
>> the
>> acceptable C-D values. The downside of that is that we would then  
>> need
>> to open up the registration of new C-D values. I think that might be
>> opposed by a lot of people.
>>        Thanks,
>>        Paul
>> Christer Holmberg wrote:
>>> Hi,
>>>
>>>>> Shouldn't we use Content-Type to indicate what is in the message  
>>>>> body?
>>>>> After all, we may need Content-Length etc.
>>>> Ah, no.
>>>>
>>>> We had extended conversations on this earlier.  Content-Type  
>>>> tells you
>>>> what's in the body; it just doesn't tell you what to DO with the  
>>>> body.
>>>>
>>>> What, for example, is the purpose of an image/jpeg in an INFO?
>>> That is not what I meant.
>>>
>>> We can use the Info-Package header, but can't we use a generic  
>>> mime value - which tells us that there is an info package in the  
>>> body.
>>>
>>> Regards,
>>>
>>> Christer
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 30 11:00:05 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CEF3428C14D;
	Thu, 30 Oct 2008 11:00:05 -0700 (PDT)
X-Original-To: sip@ietf.org
Delivered-To: sip@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id E9A5E3A6987; Thu, 30 Oct 2008 11:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081030180001.E9A5E3A6987@core3.amsl.com>
Date: Thu, 30 Oct 2008 11:00:01 -0700 (PDT)
Cc: sip@ietf.org
Subject: [Sip] I-D ACTION:draft-ietf-sip-location-conveyance-11.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

--NextPart

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

	Title		: Location Conveyance for the Session Initiation Protocol
	Author(s)	: J. Polk, B. Rosen
	Filename	: draft-ietf-sip-location-conveyance-11.txt
	Pages		: 44
	Date		: 2008-10-30
	
This document defines an extension to the Session Initiation 
   Protocol (SIP) to convey geographic location information from one 
   SIP entity to another SIP entity.  The extension covers end to end 
   conveyance as well as location-based routing, where SIP servers 
   make routing decisions based on the location of the user agent 
   clients.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sip-location-conveyance-11.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-sip-location-conveyance-11.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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



From sip-bounces@ietf.org  Thu Oct 30 11:24:55 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F07CD3A6A3F;
	Thu, 30 Oct 2008 11:24:54 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B455D3A6A3F;
	Thu, 30 Oct 2008 11:24:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -18.299
X-Spam-Level: 
X-Spam-Status: No, score=-18.299 tagged_above=-999 required=5
	tests=[AWL=0.700, BAYES_00=-2.599, GB_I_INVITATION=-2,
	J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id VcYjZ1Ee3mgN; Thu, 30 Oct 2008 11:24:52 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207])
	by core3.amsl.com (Postfix) with ESMTP id E61FD3A693E;
	Thu, 30 Oct 2008 11:24:52 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70)
	id 1403C16CBA6; Thu, 30 Oct 2008 11:24:52 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20081030182452.1403C16CBA6@bosco.isi.edu>
Date: Thu, 30 Oct 2008 11:24:52 -0700 (PDT)
Cc: sip@ietf.org, rfc-editor@rfc-editor.org
Subject: [Sip] RFC 5360 on A Framework for Consent-Based Communications in
	the Session Initiation Protocol (SIP)
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


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

        
        RFC 5360

        Title:      A Framework for Consent-Based Communications 
                    in the Session Initiation Protocol (SIP) 
        Author:     J. Rosenberg, G. Camarillo,
                    Ed., D. Willis
        Status:     Standards Track
        Date:       October 2008
        Mailbox:    jdrosen@cisco.com, 
                    Gonzalo.Camarillo@ericsson.com, 
                    dean.willis@softarmor.com
        Pages:      31
        Characters: 70658
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sip-consent-framework-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5360.txt

SIP supports communications for several services, including real-time
audio, video, text, instant messaging, and presence.  In its current
form, it allows session invitations, instant messages, and other
requests to be delivered from one party to another without requiring
explicit consent of the recipient.  Without such consent, it is
possible for SIP to be used for malicious purposes, including
amplification and DoS (Denial of Service) attacks.  This document
identifies a framework for consent-based communications in SIP. 
[STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

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

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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


The RFC Editor Team
USC/Information Sciences Institute


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


From sip-bounces@ietf.org  Thu Oct 30 11:27:14 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 48CDA3A6ADF;
	Thu, 30 Oct 2008 11:27:14 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B439D3A6951
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 11:27:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.494
X-Spam-Level: 
X-Spam-Status: No, score=-6.494 tagged_above=-999 required=5 tests=[AWL=0.105, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id R9E8ZtlFuHA0 for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 11:27:08 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 0411428C125
	for <sip@ietf.org>; Thu, 30 Oct 2008 11:26:55 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,516,1220227200"; d="scan'208";a="26247947"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 30 Oct 2008 18:26:42 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9UIQgsj002607
	for <sip@ietf.org>; Thu, 30 Oct 2008 14:26:42 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9UIQgjH003016
	for <sip@ietf.org>; Thu, 30 Oct 2008 18:26:42 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Oct 2008 14:26:42 -0400
Received: from jmpolk-wxp01.cisco.com ([10.82.223.148]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Oct 2008 14:26:41 -0400
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 30 Oct 2008 13:26:41 -0500
To: sip@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Mime-Version: 1.0
Message-ID: <XFE-RTP-202yoVTvKRN00000563@xfe-rtp-202.amer.cisco.com>
X-OriginalArrivalTime: 30 Oct 2008 18:26:41.0979 (UTC)
	FILETIME=[0E4AE8B0:01C93ABD]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2203; t=1225391202;
	x=1226255202; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jmpolk@cisco.com;
	z=From:=20=22James=20M.=20Polk=22=20<jmpolk@cisco.com>
	|Subject:=20sip-location-conveyance-11=20submitted=20
	|Sender:=20 |To:=20sip@ietf.org;
	bh=iNWaYWx4Fx0IWbwQxE99cjZEzABQ1k+f1vdNEaJMmBQ=;
	b=MtDfQyoCMZYc3U+2gpjs9vvCvKwuhDeof91ykppc9BG2c0L2hRBQwQSYLl
	en4XeLkdJWZXGuLg1fLXnawn6bd1QkgCp27S84jEv4b+spyhzy68XweR1wmx
	8VW3HZodxl;
Authentication-Results: rtp-dkim-2; header.From=jmpolk@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Subject: [Sip] sip-location-conveyance-11 submitted
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

SIP WG

I've submitted version -11 of Location Conveyance.

Minor nits were fixed, and some text about updating location after it 
has been sent (which I had in there at one point, and don't know when 
I deleted it somehow) are the only real changes.

By request of the SIP chairs, I did not address anything regarding 
the <retransmission-allowed> ID that's in Geopriv -- since that's 
still being discussed in Geopriv.

Comments are welcome.

James


>Date: Thu, 30 Oct 2008 11:00:01 -0700 (PDT)
>Cc: sip@ietf.org
>Subject: [Sip] I-D ACTION:draft-ietf-sip-location-conveyance-11.txt
>
>A New Internet-Draft is available from the on-line Internet-Drafts
>directories.
>This draft is a work item of the Session Initiation Protocol Working 
>Group of the IETF.
>
>         Title           : Location Conveyance for the Session 
> Initiation Protocol
>         Author(s)       : J. Polk, B. Rosen
>         Filename        : draft-ietf-sip-location-conveyance-11.txt
>         Pages           : 44
>         Date            : 2008-10-30
>
>This document defines an extension to the Session Initiation
>    Protocol (SIP) to convey geographic location information from one
>    SIP entity to another SIP entity.  The extension covers end to end
>    conveyance as well as location-based routing, where SIP servers
>    make routing decisions based on the location of the user agent
>    clients.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-sip-location-conveyance-11.txt
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/
>
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>
>
><ftp://ftp.ietf.org/internet-drafts/draft-ietf-sip-location-conveyance-11.txt>
>_______________________________________________
>Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>This list is for NEW development of the core SIP Protocol
>Use sip-implementors@cs.columbia.edu for questions on current sip
>Use sipping@ietf.org for new developments on the application of sip

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


From sip-bounces@ietf.org  Thu Oct 30 11:27:51 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1C49F28C1D6;
	Thu, 30 Oct 2008 11:27:51 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4E08428C1D6;
	Thu, 30 Oct 2008 11:27:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.249
X-Spam-Level: 
X-Spam-Status: No, score=-17.249 tagged_above=-999 required=5
	tests=[AWL=-0.250, BAYES_00=-2.599, J_CHICKENPOX_93=0.6,
	USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id regFukHCxd9G; Thu, 30 Oct 2008 11:27:48 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207])
	by core3.amsl.com (Postfix) with ESMTP id 6DDDA28C1CF;
	Thu, 30 Oct 2008 11:27:48 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70)
	id C638416CBB0; Thu, 30 Oct 2008 11:27:23 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20081030182723.C638416CBB0@bosco.isi.edu>
Date: Thu, 30 Oct 2008 11:27:23 -0700 (PDT)
Cc: sip@ietf.org, rfc-editor@rfc-editor.org
Subject: [Sip] RFC 5365 on Multiple-Recipient MESSAGE Requests in the
	Session Initiation Protocol (SIP)
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


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

        
        RFC 5365

        Title:      Multiple-Recipient MESSAGE Requests in the 
                    Session Initiation Protocol (SIP) 
        Author:     M. Garcia-Martin, G. Camarillo
        Status:     Standards Track
        Date:       October 2008
        Mailbox:    miguel.a.garcia@ericsson.com, 
                    Gonzalo.Camarillo@ericsson.com
        Pages:      18
        Characters: 41393
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sip-uri-list-message-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5365.txt

This document specifies a mechanism that allows a SIP User Agent
Client (UAC) to send a SIP MESSAGE request to a set of destinations,
by using a SIP URI-list (Uniform Resource Identifier list) service.
The UAC sends a SIP MESSAGE request that includes the payload along
with the URI list to the MESSAGE URI-list service, which sends a
MESSAGE request including the payload to each of the URIs included in
the list.  [STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

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

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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


The RFC Editor Team
USC/Information Sciences Institute


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


From sip-bounces@ietf.org  Thu Oct 30 11:28:30 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1B1693A6A97;
	Thu, 30 Oct 2008 11:28:30 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2989D28C1D4;
	Thu, 30 Oct 2008 11:28:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.226
X-Spam-Level: 
X-Spam-Status: No, score=-17.226 tagged_above=-999 required=5
	tests=[AWL=-0.227, BAYES_00=-2.599, J_CHICKENPOX_93=0.6,
	USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id fnBA+0Kmn7fn; Thu, 30 Oct 2008 11:28:28 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207])
	by core3.amsl.com (Postfix) with ESMTP id 4C59528C1A1;
	Thu, 30 Oct 2008 11:28:28 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70)
	id 5A84016CBB7; Thu, 30 Oct 2008 11:27:57 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20081030182757.5A84016CBB7@bosco.isi.edu>
Date: Thu, 30 Oct 2008 11:27:57 -0700 (PDT)
Cc: sip@ietf.org, rfc-editor@rfc-editor.org
Subject: [Sip] RFC 5368 on Referring to Multiple Resources in the Session
	Initiation Protocol (SIP)
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


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

        
        RFC 5368

        Title:      Referring to Multiple Resources in 
                    the Session Initiation Protocol (SIP) 
        Author:     G. Camarillo, A. Niemi,
                    M. Isomaki, M. Garcia-Martin,
                    H. Khartabil
        Status:     Standards Track
        Date:       October 2008
        Mailbox:    Gonzalo.Camarillo@ericsson.com, 
                    Aki.Niemi@nokia.com, 
                    markus.isomaki@nokia.com,  
                    miguel.a.garcia@ericsson.com, 
                    hisham.khartabil@gmail.com
        Pages:      13
        Characters: 29389
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sip-multiple-refer-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5368.txt

This document defines extensions to the SIP REFER method so that it
can be used to refer to multiple resources in a single request.
These extensions include the use of pointers to Uniform Resource
Identifier (URI) lists in the Refer-To header field and the
"multiple-refer" SIP option-tag.  [STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

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

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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


The RFC Editor Team
USC/Information Sciences Institute


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


From sip-bounces@ietf.org  Thu Oct 30 11:30:38 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7B1B13A69D3;
	Thu, 30 Oct 2008 11:30:38 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 57D4A28C2B1
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 11:30:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XjalaFWDK-Cr for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 11:30:36 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id F402A28C2EB
	for <SIP@ietf.org>; Thu, 30 Oct 2008 11:30:26 -0700 (PDT)
Received: from [75.68.119.237] (port=60504 helo=[192.168.15.102])
	by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1KvcGl-0004TI-W0 for SIP@ietf.org; Thu, 30 Oct 2008 11:29:20 -0700
Message-Id: <322862FF-3683-465F-B1A0-8C619A5D60E1@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: IETF SIP List <SIP@ietf.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 30 Oct 2008 14:29:22 -0400
X-Mailer: Apple Mail (2.929.2)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: [Sip] Proposal for multiple INFO bodies in an INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0026372351=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--===============0026372351==
Content-Type: multipart/signed; boundary=Apple-Mail-78-123542999; micalg=sha1; protocol="application/pkcs7-signature"


--Apple-Mail-78-123542999
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Good thing I waited 10 days...

Initially, I was very swayed by the argument that things would be  
much, much easier if we restricted an INFO request to a single Info- 
Package.

However, and especially as the last person to touch RFC 4483, I can  
see the argument that *any* SIP message can end up with a multipart/ 
mime body, even if you think you can limit it to just your stuff,  
because the UA can always have a content indirection pointer in the  
header pointing to a mime body part.

Therefore, even if we restrict an INFO request to carry a single Info- 
Package, we need a mechanism to uniquely identify and, at the SIP  
header level, indicate which body part belongs to the package.

I would offer once we solve that, we also get multiple INFO request  
bodies for free.

I would also offer that since INFO does not change SIP state, which  
means there is not even a concept of a message succeeding but the INFO  
body doing something that "fails", the objection that it would be hard  
for a UA to report on one body "failing" with another body  
"succeeding" is a non-issue.  Yes, this does mean that you cannot use  
INFO to tunnel IP.  See RFC 3252 for more on this.  I do not see this  
as a problem.

Therefore, on to the solution.  We use the MIME approach.  The body  
parts get tagged with Content-IDs. The Info-Package has a parameter,  
CID, which points to the body part.  The ONLY question I have is  
whether we should simply mandate always having this parameter to make  
the protocol and parser easier, but a small burden on UAC's that  
really are only sending a single body.  Other than that, the mechanism  
looks like:

INFO .....
To: ....
From: ....
Info-Package: foo
Content-Type: application/foo;cid=this
Content-Id: this
...

<foo body>



Multipart mixed example with indirect content:

INFO ....
To: ....
From: ....
Info-Package: foo;cid=abcd1234zz
Mumble: <cid:abcd9999qq>
Content-Type: multipart/mixed;boundary="theboundary"
...

--theboundary
Content-Type: application/mumble
Content-Id: abcd9999qq
...

<mumble stuff>

--theboundary
Content-Type: application/foo
Content-Id: abcd1234zz

<foo body>

--theboundary--




Multiple Info Packages follow. Note that by using Content-Id, order is  
irrelevant.

INFO ....
To: ....
From: ....
Info-Package: foo;cid=abcd1234zz
Info-Package: bar;cid=wxyz9876
Content-Type: multipart/mixed;boundary="theboundary"
...

--theboundary
Content-Type: application/bar
Content-Id: wxyz9876
...

<bar stuff>

--theboundary
Content-Type: application/foo
Content-Id: abcd1234zz

<foo body>

--theboundary--
--Apple-Mail-78-123542999
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGPTCCBjkw
ggUhoAMCAQICEC+VK1RLWxrF8KJZDR9k8p8wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYTAlVT
MQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VS
VFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQD
Ey1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwwHhcNMDgwODEz
MDAwMDAwWhcNMDkwODEzMjM1OTU5WjCB4TE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsg
LSBQRVJTT05BIE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9m
IHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDMg
Q29tb2RvIExpbWl0ZWQxFDASBgNVBAMTC0VyaWMgQnVyZ2VyMSkwJwYJKoZIhvcNAQkBFhplYnVy
Z2VyQHN0YW5kYXJkc3RyYWNrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMTF
RRoA4LgOACMFph0aomRC/UpqoA5C/d6DUTOvTMrYSEqkjwnU4zxDtBcHlcB4AxKAov00MYsUvEU4
loz7BHjfDjv76AIkcwu33VYQbzGmarVnyaXsVb6f/cyRL3fPT0VOVO2tQAEEgwg//CX0jN8Kn2jH
uXD/HEvko7cmpL3Pwevf3+DwB61v7ca79PpEZfn/WhaqRKA4uVNPj/JbieeaLo2v/0RJzrEElZK0
pHCqxiD3mQ8ossPkA9fUCSxLlbdMcPU3be5x8vt8Q8mYTXF5Z3d9RZmYrmNkvTQtdzVpfYWr/hgV
Xqm9tByOOAR+hoN3FKbubR/OrAHL9yDAd4sCAwEAAaOCAhwwggIYMB8GA1UdIwQYMBaAFImCZ33E
nSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBRDWgutb7b8R/L7G3Y3D+molAA3VzAOBgNVHQ8BAf8E
BAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJ
YIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEW
HWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMIGlBgNVHR8EgZ0wgZowTKBKoEiGRmh0dHA6
Ly9jcmwuY29tb2RvY2EuY29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRF
bWFpbC5jcmwwSqBIoEaGRGh0dHA6Ly9jcmwuY29tb2RvLm5ldC9VVE4tVVNFUkZpcnN0LUNsaWVu
dEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMGwGCCsGAQUFBwEBBGAwXjA2BggrBgEFBQcwAoYq
aHR0cDovL2NydC5jb21vZG9jYS5jb20vVVROQUFBQ2xpZW50Q0EuY3J0MCQGCCsGAQUFBzABhhho
dHRwOi8vb2NzcC5jb21vZG9jYS5jb20wJQYDVR0RBB4wHIEaZWJ1cmdlckBzdGFuZGFyZHN0cmFj
ay5jb20wDQYJKoZIhvcNAQEFBQADggEBAGeBR7NPCvrY3GQoIi49JOuciatY2r4st905Jw1etp6J
umFFWlaCBl11tFSclk/3S45B+lUv3SEvG4CEjUByPScprVmCqHR+y8BAQaB/CV+N1y14x3MbhJ+Z
8XDGKeUXuuyGd9w0l3/t/QPid6TRXQjQFrLPFs1IALuNpNiFMHEF/xFbMG1Z2vznR/gSPlePekoZ
TqcExIDBNZTBebpZqwAXzPpedNNOclbMLFLWDMOAozVRpkfjI0eiFsk8SF1Ho1Gb9Bx8DeG4peE2
KRVOR9FFnZZgBpFjXYRcglsMOSKCY8HgE+NGvbbqbrMoBV/BlYyxRXwfti71RL9Zs2Cq1eQxggP8
MIID+AIBATCBwzCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExh
a2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8v
d3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkNH2TynzAJBgUrDgMCGgUAoIICDTAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wODEwMzAxODI5MjJaMCMGCSqGSIb3
DQEJBDEWBBRe3hKr1cvOpahhlLxzmgFx2cRMDzCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD
VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU
aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2
MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv
lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN
H2TynzANBgkqhkiG9w0BAQEFAASCAQBJLSlvWJXNpWg9puc/TozKGEBvR6TR2b/GN9L4OjE4IoAR
h4XrNzLGcAcLo2QIYDtwwCtJtpITJ7gOYBJmjshjZn33SvW/Iw8dcnIVDHIymmL9z4remlQ1D5ML
1UrW6oJ3AndDJn7mAM1573veNoPS+3n1t8cF+TNbWhBWM0XgwpqDnwZMFFNjeHPKWBqMjcj56ZMK
N08IQFlUDXaV11UYmgnH4fR4C+W6Hcizz2fokROzPwVRJFfin6Uq/6730OPmWZZh9SKEFJCv51z9
KlsRTREjGtAHB45cuhfHYgzyE45H+5UnCF13Cp4UcOwYkQhhSbfv1GQ0f/UrfNkA9kt1AAAAAAAA

--Apple-Mail-78-123542999--

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

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


From sip-bounces@ietf.org  Thu Oct 30 11:48:25 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 846F628C39B;
	Thu, 30 Oct 2008 11:28:41 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E705128C386;
	Thu, 30 Oct 2008 11:28:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.507
X-Spam-Level: 
X-Spam-Status: No, score=-17.507 tagged_above=-999 required=5
	tests=[AWL=0.092, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id A5qAQcME0B3W; Thu, 30 Oct 2008 11:28:38 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207])
	by core3.amsl.com (Postfix) with ESMTP id CAB9C28C37E;
	Thu, 30 Oct 2008 11:28:37 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70)
	id D547B16CBBA; Thu, 30 Oct 2008 11:28:08 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20081030182808.D547B16CBBA@bosco.isi.edu>
Date: Thu, 30 Oct 2008 11:28:08 -0700 (PDT)
Cc: sip@ietf.org, rfc-editor@rfc-editor.org
Subject: [Sip] RFC 5369 on Framework for Transcoding with the Session
	Initiation Protocol (SIP)
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


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

        
        RFC 5369

        Title:      Framework for Transcoding with the 
                    Session Initiation Protocol (SIP) 
        Author:     G. Camarillo
        Status:     Informational
        Date:       October 2008
        Mailbox:    Gonzalo.Camarillo@ericsson.com
        Pages:      10
        Characters: 20428
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sipping-transc-framework-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5369.txt

This document defines a framework for transcoding with SIP.  This
framework includes how to discover the need for transcoding services
in a session and how to invoke those transcoding services.  Two
models for transcoding services invocation are discussed: the
conference bridge model and the third-party call control model.  Both
models meet the requirements for SIP regarding transcoding services
invocation to support deaf, hard of hearing, and speech-impaired
individuals.  This memo provides information for the Internet community.

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


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

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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


The RFC Editor Team
USC/Information Sciences Institute


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


From sip-bounces@ietf.org  Thu Oct 30 11:57:14 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6CCFD28C1C3;
	Thu, 30 Oct 2008 11:57:14 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8BB153A6358;
	Thu, 30 Oct 2008 11:57:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.199
X-Spam-Level: 
X-Spam-Status: No, score=-17.199 tagged_above=-999 required=5
	tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_93=0.6,
	USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id bO-q4uZABgJQ; Thu, 30 Oct 2008 11:57:10 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207])
	by core3.amsl.com (Postfix) with ESMTP id BF70328C160;
	Thu, 30 Oct 2008 11:57:10 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70)
	id A520E16CBB4; Thu, 30 Oct 2008 11:27:47 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20081030182747.A520E16CBB4@bosco.isi.edu>
Date: Thu, 30 Oct 2008 11:27:47 -0700 (PDT)
Cc: sip@ietf.org, rfc-editor@rfc-editor.org
Subject: [Sip] RFC 5367 on Subscriptions to Request-Contained Resource Lists
	in the Session Initiation Protocol (SIP)
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


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

        
        RFC 5367

        Title:      Subscriptions to Request-Contained Resource Lists 
                    in the Session Initiation Protocol (SIP) 
        Author:     G. Camarillo, A.B. Roach,
                    O. Levin
        Status:     Standards Track
        Date:       October 2008
        Mailbox:    Gonzalo.Camarillo@ericsson.com, 
                    Adam.Roach@tekelec.com, 
                    oritl@microsoft.com
        Pages:      9
        Characters: 18329
        Updates:    RFC3265

        I-D Tag:    draft-ietf-sip-uri-list-subscribe-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5367.txt

This document specifies a way to create subscription to a list of
resources in SIP.  This is achieved by including the list of
resources in the body of a SUBSCRIBE request.  Instead of having a
subscriber send a SUBSCRIBE request for each resource individually,
the subscriber defines the resource list, subscribes to it, and gets
notifications about changes in the resources' states using a single
SUBSCRIBE dialog.  [STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

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

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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


The RFC Editor Team
USC/Information Sciences Institute


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


From sip-bounces@ietf.org  Thu Oct 30 12:13:52 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4D3C73A6A45;
	Thu, 30 Oct 2008 12:13:52 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 58DA23A6A67
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 12:13:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id AZBgcxJskx7W for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 12:13:50 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 8D69F3A6951
	for <sip@ietf.org>; Thu, 30 Oct 2008 12:13:50 -0700 (PDT)
Received: from [192.168.2.102] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9UJDY5l027374
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 30 Oct 2008 14:13:36 -0500
Message-Id: <BB1FCCF4-D0F2-4C5B-B838-34AFA9329064@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <81521DF0-2666-4500-BE62-412FBB6966A7@standardstrack.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 30 Oct 2008 14:13:29 -0500
References: <20081020231502.43DCA3A69EF@core3.amsl.com>
	<48FDECB5.3030607@cisco.com>
	<81521DF0-2666-4500-BE62-412FBB6966A7@standardstrack.com>
X-Mailer: Apple Mail (2.929.2)
Cc: SIP IETF <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] Legacy Info Package Registration
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 30, 2008, at 11:13 AM, Eric Burger wrote:

>

I like:

> [ ] No, do not create an IANA registry, but please enumerate known  
> legacy usages in this draft

--
Dean

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


From sip-bounces@ietf.org  Thu Oct 30 12:30:54 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 571CE3A6AE1;
	Thu, 30 Oct 2008 12:30:54 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A4A413A6A67;
	Thu, 30 Oct 2008 12:30:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.186
X-Spam-Level: 
X-Spam-Status: No, score=-17.186 tagged_above=-999 required=5
	tests=[AWL=-0.187, BAYES_00=-2.599, J_CHICKENPOX_93=0.6,
	USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1Y0jV2Zalk90; Thu, 30 Oct 2008 12:30:53 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207])
	by core3.amsl.com (Postfix) with ESMTP id 017DC3A698A;
	Thu, 30 Oct 2008 12:30:53 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70)
	id C991D16CBB2; Thu, 30 Oct 2008 11:27:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20081030182735.C991D16CBB2@bosco.isi.edu>
Date: Thu, 30 Oct 2008 11:27:35 -0700 (PDT)
Cc: sip@ietf.org, rfc-editor@rfc-editor.org
Subject: [Sip] RFC 5366 on Conference Establishment Using Request-Contained
	Lists in the Session Initiation Protocol (SIP)
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


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

        
        RFC 5366

        Title:      Conference Establishment Using Request-Contained Lists 
                    in the Session Initiation Protocol (SIP) 
        Author:     G. Camarillo, A. Johnston
        Status:     Standards Track
        Date:       October 2008
        Mailbox:    Gonzalo.Camarillo@ericsson.com, 
                    alan@sipstation.com
        Pages:      13
        Characters: 28369
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sip-uri-list-conferencing-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5366.txt

This document describes how to create a conference using SIP URI-list
services.  In particular, it describes a mechanism that allows a User
Agent Client to provide a conference server with the initial list of
participants using an INVITE-contained URI list.  [STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

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

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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


The RFC Editor Team
USC/Information Sciences Institute


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


From sip-bounces@ietf.org  Thu Oct 30 12:37:04 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D213C3A6A33;
	Thu, 30 Oct 2008 12:37:04 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 427973A6A33
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 12:37:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id I10scI92TtxX for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 12:37:03 -0700 (PDT)
Received: from empbedex1.empirix.com (empbedex1.empirix.com [12.38.203.54])
	by core3.amsl.com (Postfix) with ESMTP id 2765D3A6909
	for <sip@ietf.org>; Thu, 30 Oct 2008 12:36:59 -0700 (PDT)
Received: from EMPBEDEX.empirix.com ([10.16.0.92]) by empbedex1.empirix.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Oct 2008 15:36:57 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 30 Oct 2008 15:36:44 -0400
Message-ID: <BD261180E6D35F4D9D32F3E44FD3D9010ECE53A8@EMPBEDEX.empirix.com>
In-Reply-To: <BB1FCCF4-D0F2-4C5B-B838-34AFA9329064@softarmor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Legacy Info Package Registration
Thread-Index: Ack6w7y16SwoWD9HTgaOpHSuMEzFYQAAwKJA
References: <20081020231502.43DCA3A69EF@core3.amsl.com><48FDECB5.3030607@cisco.com><81521DF0-2666-4500-BE62-412FBB6966A7@standardstrack.com>
	<BB1FCCF4-D0F2-4C5B-B838-34AFA9329064@softarmor.com>
From: "Beith, Gordon" <GBeith@empirix.com>
To: "Dean Willis" <dean.willis@softarmor.com>,
	"Eric Burger" <eburger@standardstrack.com>
X-OriginalArrivalTime: 30 Oct 2008 19:36:57.0669 (UTC)
	FILETIME=[DF0A2750:01C93AC6]
Cc: SIP IETF <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] Legacy Info Package Registration
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I also support 
 [X] No, do not create an IANA registry, but please enumerate known
legacy usages in this draft

/Gordon

-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Dean Willis
Sent: Thursday, October 30, 2008 12:13 PM
To: Eric Burger
Cc: SIP IETF; Paul Kyzivat
Subject: Re: [Sip] Legacy Info Package Registration


On Oct 30, 2008, at 11:13 AM, Eric Burger wrote:

>

I like:

> [ ] No, do not create an IANA registry, but please enumerate known  
> legacy usages in this draft

--
Dean

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


From sip-bounces@ietf.org  Thu Oct 30 12:44:05 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B19C63A6894;
	Thu, 30 Oct 2008 12:44:05 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9B2393A6951
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 12:44:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id MSoDSzwNyK7L for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 12:44:02 -0700 (PDT)
Received: from mail.iptel.org (smtp.iptel.org [213.192.59.67])
	by core3.amsl.com (Postfix) with ESMTP id 543CA3A67D6
	for <sip@ietf.org>; Thu, 30 Oct 2008 12:44:02 -0700 (PDT)
Received: from nc1lt1470.nc.tekelec.com (shell.iptel.org [213.192.59.74])
	by mail.iptel.org (Postfix) with ESMTP id D83331817C35;
	Thu, 30 Oct 2008 20:43:59 +0100 (CET)
Message-ID: <490A0E7F.3010206@iptel.org>
Date: Thu, 30 Oct 2008 20:43:59 +0100
From: Jiri Kuthan <jiri@iptel.org>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com><490792EA.2020106@softarmor.com><033f01c9397b$860847a0$c3f0200a@cisco.com><200810292306.44911.ibc@aliax.net><000901c93a36$3d4755e0$c3f0200a@cisco.com>	<17345A0C-8BFD-4D0D-B597-ECA8801F72D5@softarmor.com>
	<5D1A7985295922448D5550C94DE291800245C0C7@DEEXC1U01.de.lucent.com>
In-Reply-To: <5D1A7985295922448D5550C94DE291800245C0C7@DEEXC1U01.de.lucent.com>
Cc: sip@ietf.org, Dan Wing <dwing@cisco.com>,
	Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

DRAGE, Keith (Keith) wrote:
> (As WG cochair)
> 
> The group with current scope for this work is SIP. Therefore if the SIP
> WG believes it can make progress in identifying valid work in the SIP
> timeframe, the chairs can ask the RAI ADs for a charter milestone. The
> ADs can choose to direct that milestone to some other group if they so
> wish.
> 
> There is a separate RAIarea agenda slot where people can discuss their
> ideas on future RAI WG structure. That discussion does not need to
> impact on whether this is valid IETF work or not.
> 
> So core to the discussion is whether we feel we can get an agreement for
> a suitable area of identity related work in Minneapolis based on
> discussion of this draft. If the answer is no, the chairs will push it
> down the priority order in allocating agenda slots. If the answer is yes
> then we push it up the priority. (Note that the same applies for all the
> other active identity related documents). 
> 
> Note also that we would also like to see any discussion in this area
> bringing in new issues and points. There is little point in the same
> people standing up at the mic and saying the same things they said in
> Dublin, as presumably, we will end up with the same absence of decision.
> 
> With this in mind, the chairs welcome discussion on this list, and in
> private emails, to see if something can come out of this.

I'm wondering if other WG participants would agree with me that "verifying
who is sending me this SIP request is who he claims to be in the simplest
possible way (i.e., without other protocols and infrastructures) by reverse
lookup" would be an appropriate goal.

The number of drafts and emails posted to this topic and more importantly
the problems in the field indicate this is a real and important problem.
Additionally, it seems that folks are interested in something VERY simple.

An implication of that to me is this effort is small and self-contained,
and shall stay so on purpose. From the sizing perspective, the SIP WG thus
seems more appropriate to me than more general (and bigger) fora, and also
it does not seem big enough to me for its own WG.

For sake of completeness: Many of the points raised so far appear to relate
to a solution rather than to question the problem: SUB/NOT versus OPTIONS,
"B2BUA traversal", as well as those not addressed yet much: reverse 
routability,
latency, security considerations....

-jiri


> 
> Regards
> 
> Keith
> 
>  
> 
>> -----Original Message-----
>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
>> Behalf Of Dean Willis
>> Sent: Thursday, October 30, 2008 4:54 AM
>> To: Dan Wing
>> Cc: sip@ietf.org
>> Subject: Re: [Sip] Comment on DERIVE and B2BUAs
>>
>>
>> On Oct 29, 2008, at 9:21 PM, Dan Wing wrote:
>>> Let's talk about the meta-issue:  do we want assurance of a "From:" 
>>> over SBCs?  If so, let us please convince the ADs in 
>> Minneapolis and 
>>> let us please get a new SIP milestone.
>> I'd rather charter a SIP RRC working group than put a new 
>> milestone in SIP.
>>
>> This seems like a perfect item for a working group that could 
>> conclude in a reasonable and timely fashion.
>>
>> --
>> Dean
>>
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol Use 
>> sip-implementors@cs.columbia.edu for questions on current sip 
>> Use sipping@ietf.org for new developments on the application of sip
>>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 30 13:09:01 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8B7FA3A68BF;
	Thu, 30 Oct 2008 13:09:01 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 981EE3A68BF
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 13:09:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.31
X-Spam-Level: 
X-Spam-Status: No, score=-6.31 tagged_above=-999 required=5 tests=[AWL=0.289, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9gSxQAoPDP4c for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 13:08:59 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56])
	by core3.amsl.com (Postfix) with ESMTP id 7804D3A6894
	for <sip@ietf.org>; Thu, 30 Oct 2008 13:08:59 -0700 (PDT)
Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com
	[47.103.123.72])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m9UK8pV00902; Thu, 30 Oct 2008 20:08:51 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 30 Oct 2008 15:05:25 -0500
Message-ID: <F66D7286825402429571678A16C2F5EE060E08C4@zrc2hxm1.corp.nortel.com>
In-Reply-To: <81521DF0-2666-4500-BE62-412FBB6966A7@standardstrack.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Legacy Info Package Registration
Thread-Index: Ack6tdhvcdy6u0IiRLWq8BLS2MC73AAFDHNA
References: <20081020231502.43DCA3A69EF@core3.amsl.com>
	<48FDECB5.3030607@cisco.com>
	<81521DF0-2666-4500-BE62-412FBB6966A7@standardstrack.com>
From: "Mary Barnes" <mary.barnes@nortel.com>
To: "Eric Burger" <eburger@standardstrack.com>
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Legacy Info Package Registration
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 
[X] Punt - I may or may not want an IANA registry, but if we do create
one, do it in another draft

I think we should punt for now. However, IF we decide that for SIP, as a
whole, we do try to bring more real implemenation stuff into the fold,
then I think we should have a registry, that should be included in a
separate document. I'm afraid we may get very delayed if we try to do
that now, as there may be a tendency to analyze legacy usages in terms
of how reasonable people think they are - i.e., there may be some for
which there is a clear standard's solution and then we'll debate whether
we include them all whether folks would ever deem them useful or not.   

Mary. 

-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Eric Burger
Sent: Thursday, October 30, 2008 11:14 AM
To: Paul Kyzivat
Cc: SIP IETF
Subject: [Sip] Legacy Info Package Registration

We discussed creating a registry, and we discussed whether it would be
in this document.

On the one hand, the discussion was not conclusive.  On the other, here
are my reasons for not including it in the Info Packages document:

1. We go at lengths to say how to do Info Packages.  The last thing we
need to do is say, "by the way, it's not so bad if you don't."

2. People not involved today will look at such a registry and, no matter
how much doom and gloom wording we use, will think it's OK to not use
Info Packages.

3. People will be confused, thinking Content-Type is sufficient to
identify an Info Package.  It is not.

4. How would we possibly police the registry? If someone comes to IANA
to register a new MIME type do the klaxons ring?  That would not be a
good thing.

So, time for another poll:
[ ] Yes - we really, really need an IANA registry of "legacy" INFO
usages, and we need it done in this draft
     (NOTE: creating the IANA registry requires the seed values, which
means this draft will enumerate the
      known legacy usages)

[ ] No, do not create an IANA registry, but please enumerate known
legacy usages in this draft

[ ] No - please do not create an IANA registry

[ ] Punt - I may or may not want an IANA registry, but if we do create
one, do it in another draft

[ ] Other: ________________________________



On Oct 21, 2008, at 10:52 AM, Paul Kyzivat wrote:

> Regarding registration if INFO packages - I thought we also wanted to 
> introduce a registry for legacy usages of INFO, to encourage them to 
> come out into the daylight. I guess maybe that would be a separate 
> registry, since the key for it will have to be Content- Type. So it 
> *could* be established from a different document. But I think this is 
> the likely place to do it, since its the place where all the eyeballs 
> will be. I think the rule for registering those needs to be that one 
> can only be registered if the Content-Type has not already been 
> registered, and it was in *use* with INFO prior to this document 
> becoming an RFC. (The registration itself could be done later. I guess

> it would be the honor system.) Any usages being deployed after this 
> becomes an RFC would be required to use the new mechanism.
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 30 13:33:01 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DE6293A6804;
	Thu, 30 Oct 2008 13:33:01 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EE0253A67D6
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 13:32:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rgLbcPtL6XeR for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 13:32:59 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 051D33A6894
	for <sip@ietf.org>; Thu, 30 Oct 2008 13:32:58 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,517,1220227200"; d="scan'208";a="26234408"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 30 Oct 2008 20:32:57 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9UKWv07023236; 
	Thu, 30 Oct 2008 16:32:57 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9UKWvfV017268;
	Thu, 30 Oct 2008 20:32:57 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Oct 2008 16:32:57 -0400
Received: from [10.86.241.187] ([10.86.241.187]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Oct 2008 16:32:56 -0400
Message-ID: <490A19F5.40201@cisco.com>
Date: Thu, 30 Oct 2008 16:32:53 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Eric Burger <eburger@standardstrack.com>
References: <20081020231502.43DCA3A69EF@core3.amsl.com>
	<48FDECB5.3030607@cisco.com>
	<81521DF0-2666-4500-BE62-412FBB6966A7@standardstrack.com>
In-Reply-To: <81521DF0-2666-4500-BE62-412FBB6966A7@standardstrack.com>
X-OriginalArrivalTime: 30 Oct 2008 20:32:57.0141 (UTC)
	FILETIME=[B170E650:01C93ACE]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1592; t=1225398777;
	x=1226262777; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20Legacy=20Info=20Package=20Registration
	|Sender:=20
	|To:=20Eric=20Burger=20<eburger@standardstrack.com>;
	bh=Cc5l5rBlM2PVi+sL7/6hKs1X2EimQzd6xB/uwH6FkmU=;
	b=yfKLck4vp4iqPwWdKMkIKTXXiN7afMjG/r/axnhXNOH5dlw2SqmM4AThBZ
	iZ68xByoqfqmb0tHTPv1r/BXVi6pDD4jcZXO0ju9qWrW+x5xbgREfWoJHLw5
	yAz/ziLsfO;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Legacy Info Package Registration
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

In some sense "enumerate known legacy usages" is what I hoped the 
registry would do. If we just try to do it in this document, without 
provision for update, then which ones will we get, and which will we miss?

I am opposed to a registry of legacy issues if it isn't restricted to 
*legacy* uses. I'd like to restrict it to usages that were in production 
use prior to the info usage draft - say before the end of 2008. But I 
don't know how to put teeth into that, if somebody comes along in 2010 
and says "I have this info usage that I have been using since 2004 but I 
didn't know about this registry till now." I think it must be honor 
system, and I don't know how well that will work.

Regarding keeping the registry separate from the info package document: 
when the document describes legacy usage, IMO it would be helpful to say 
that to comply with the new document, the legacy usages you use must be 
registered in the registry. That would provide some incentive to get 
that registry populated. In terms of encouraging migration to the info 
packages, we would have to depend on the honor system for legacy usage.

Eric Burger wrote:

> [1] Yes - we really, really need an IANA registry of "legacy" INFO 
> usages, and we need it done in this draft
>     (NOTE: creating the IANA registry requires the seed values, which 
> means this draft will enumerate the
>      known legacy usages)
> [2] Punt - I may or may not want an IANA registry, but if we do create 
> one, do it in another draft

I can go with either of the above.

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


From sip-bounces@ietf.org  Thu Oct 30 13:33:26 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8C62E3A6B20;
	Thu, 30 Oct 2008 13:33:26 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D3F633A6A0E
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 13:33:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8+dLvB2DRN78 for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 13:33:25 -0700 (PDT)
Received: from estacado.net (estacado-pt.tunnel.tserv2.fmt.ipv6.he.net
	[IPv6:2001:470:1f03:266::2])
	by core3.amsl.com (Postfix) with ESMTP id 9327B3A6B20
	for <sip@ietf.org>; Thu, 30 Oct 2008 13:33:24 -0700 (PDT)
Received: from [10.0.1.196] (adsl-68-94-38-205.dsl.rcsntx.swbell.net
	[68.94.38.205]) (authenticated bits=0)
	by estacado.net (8.14.2/8.14.1) with ESMTP id m9UKXFlS046376
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 30 Oct 2008 15:33:20 -0500 (CDT)
	(envelope-from ben@estacado.net)
Message-Id: <87C0A6AC-1D65-4EB6-99EC-39A20AF48211@estacado.net>
From: Ben Campbell <ben@estacado.net>
To: Eric Burger <eburger@standardstrack.com>, SIP IETF <sip@ietf.org>
In-Reply-To: <BD261180E6D35F4D9D32F3E44FD3D9010ECE53A8@EMPBEDEX.empirix.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 30 Oct 2008 15:33:15 -0500
References: <20081020231502.43DCA3A69EF@core3.amsl.com><48FDECB5.3030607@cisco.com><81521DF0-2666-4500-BE62-412FBB6966A7@standardstrack.com>
	<BB1FCCF4-D0F2-4C5B-B838-34AFA9329064@softarmor.com>
	<BD261180E6D35F4D9D32F3E44FD3D9010ECE53A8@EMPBEDEX.empirix.com>
X-Mailer: Apple Mail (2.929.2)
Subject: Re: [Sip] Legacy Info Package Registration
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 30, 2008, at 2:36 PM, Beith, Gordon wrote:

> I also support
> [X] No, do not create an IANA registry, but please enumerate known
> legacy usages in this draft

+1

(With a second choice of punt)
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 30 13:44:13 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D2F213A680D;
	Thu, 30 Oct 2008 13:44:13 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 07EF43A680D
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 13:44:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level: 
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ArPrsGXOfTjQ for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 13:44:12 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id D9A1C3A6804
	for <SIP@ietf.org>; Thu, 30 Oct 2008 13:44:11 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,517,1220227200"; d="scan'208";a="26235966"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 30 Oct 2008 20:44:08 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9UKi8x8030122; 
	Thu, 30 Oct 2008 16:44:08 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9UKi8em021356;
	Thu, 30 Oct 2008 20:44:08 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Oct 2008 16:44:08 -0400
Received: from [10.86.241.187] ([10.86.241.187]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Oct 2008 16:44:08 -0400
Message-ID: <490A1C97.8050207@cisco.com>
Date: Thu, 30 Oct 2008 16:44:07 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Eric Burger <eburger@standardstrack.com>
References: <322862FF-3683-465F-B1A0-8C619A5D60E1@standardstrack.com>
In-Reply-To: <322862FF-3683-465F-B1A0-8C619A5D60E1@standardstrack.com>
X-OriginalArrivalTime: 30 Oct 2008 20:44:08.0239 (UTC)
	FILETIME=[417253F0:01C93AD0]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3601; t=1225399448;
	x=1226263448; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Proposal=20for=20multiple=20INF
	O=20bodies=20in=20an=20INFO |Sender:=20
	|To:=20Eric=20Burger=20<eburger@standardstrack.com>;
	bh=hQccS1oGoUL0B99eT5/syIEgCmoy4OSyvHFk7ZY/dRU=;
	b=zBItIe2Kcysiq9qNe2E81TH4YHAJXknpWtTGEeRLRrbN6Dkcr9G0g70wt0
	nMdz4Zb96fLt1il+kZx1bVXK0/Ml9Q8qTrGby5gsV/vuIgJyLCmo3leWDIe+
	WidpEV1ad6;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: IETF SIP List <SIP@ietf.org>
Subject: Re: [Sip] Proposal for multiple INFO bodies in an INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Of course I agree with all the stuff below on the necessity of dealing 
with multipart bodies.

While I was advocating a Content-Disposition mechanism for identifying 
the relevant part(s), I have no problem with the CID: mechanism. If we 
go that way I think we should *always* use the CID reference.

	Thanks,
	Paul

Eric Burger wrote:
> Good thing I waited 10 days...
> 
> Initially, I was very swayed by the argument that things would be much, 
> much easier if we restricted an INFO request to a single Info-Package.
> 
> However, and especially as the last person to touch RFC 4483, I can see 
> the argument that *any* SIP message can end up with a multipart/mime 
> body, even if you think you can limit it to just your stuff, because the 
> UA can always have a content indirection pointer in the header pointing 
> to a mime body part.
> 
> Therefore, even if we restrict an INFO request to carry a single 
> Info-Package, we need a mechanism to uniquely identify and, at the SIP 
> header level, indicate which body part belongs to the package.
> 
> I would offer once we solve that, we also get multiple INFO request 
> bodies for free.
> 
> I would also offer that since INFO does not change SIP state, which 
> means there is not even a concept of a message succeeding but the INFO 
> body doing something that "fails", the objection that it would be hard 
> for a UA to report on one body "failing" with another body "succeeding" 
> is a non-issue.  Yes, this does mean that you cannot use INFO to tunnel 
> IP.  See RFC 3252 for more on this.  I do not see this as a problem.
> 
> Therefore, on to the solution.  We use the MIME approach.  The body 
> parts get tagged with Content-IDs. The Info-Package has a parameter, 
> CID, which points to the body part.  The ONLY question I have is whether 
> we should simply mandate always having this parameter to make the 
> protocol and parser easier, but a small burden on UAC's that really are 
> only sending a single body.  Other than that, the mechanism looks like:
> 
> INFO .....
> To: ....
> From: ....
> Info-Package: foo
> Content-Type: application/foo;cid=this
> Content-Id: this
> ...
> 
> <foo body>
> 
> 
> 
> Multipart mixed example with indirect content:
> 
> INFO ....
> To: ....
> From: ....
> Info-Package: foo;cid=abcd1234zz
> Mumble: <cid:abcd9999qq>
> Content-Type: multipart/mixed;boundary="theboundary"
> ...
> 
> --theboundary
> Content-Type: application/mumble
> Content-Id: abcd9999qq
> ...
> 
> <mumble stuff>
> 
> --theboundary
> Content-Type: application/foo
> Content-Id: abcd1234zz
> 
> <foo body>
> 
> --theboundary--
> 
> 
> 
> 
> Multiple Info Packages follow. Note that by using Content-Id, order is 
> irrelevant.
> 
> INFO ....
> To: ....
> From: ....
> Info-Package: foo;cid=abcd1234zz
> Info-Package: bar;cid=wxyz9876
> Content-Type: multipart/mixed;boundary="theboundary"
> ...
> 
> --theboundary
> Content-Type: application/bar
> Content-Id: wxyz9876
> ...
> 
> <bar stuff>
> 
> --theboundary
> Content-Type: application/foo
> Content-Id: abcd1234zz
> 
> <foo body>
> 
> --theboundary--
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 30 14:19:09 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 52E523A6B24;
	Thu, 30 Oct 2008 14:19:09 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A7E4D3A68E1
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 14:19:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id azYrvyOdcjuh for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 14:19:07 -0700 (PDT)
Received: from estacado.net (estacado-pt.tunnel.tserv2.fmt.ipv6.he.net
	[IPv6:2001:470:1f03:266::2])
	by core3.amsl.com (Postfix) with ESMTP id 5A2143A6804
	for <sip@ietf.org>; Thu, 30 Oct 2008 14:19:06 -0700 (PDT)
Received: from [10.0.1.196] (adsl-68-94-38-205.dsl.rcsntx.swbell.net
	[68.94.38.205]) (authenticated bits=0)
	by estacado.net (8.14.2/8.14.1) with ESMTP id m9ULIvdv052850
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 30 Oct 2008 16:19:02 -0500 (CDT)
	(envelope-from ben@estacado.net)
Message-Id: <1A770AC3-26C6-4D16-86A2-35533896F3C0@estacado.net>
From: Ben Campbell <ben@estacado.net>
To: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <36E83843-775F-4317-BB0F-746E55194BFD@softarmor.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 30 Oct 2008 16:11:50 -0500
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com><0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
	<490792EA.2020106@softarmor.com>
	<033f01c9397b$860847a0$c3f0200a@cisco.com>
	<36E83843-775F-4317-BB0F-746E55194BFD@softarmor.com>
X-Mailer: Apple Mail (2.929.2)
Cc: Sip List <sip@ietf.org>
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 29, 2008, at 6:40 PM, Dean Willis wrote:

>
> On Oct 28, 2008, at 11:05 PM, Dan Wing wrote:
>>>
>>> Would the SBC not have to handle the SUBSCRIBE request locally?  
>>> After
>>> all, since it is a terminal UA for the call, it also knows
>>> about all the
>>> dialog states. The end-user UA would never even see the SUBSCRIBE.
>>
>> If that's a problem, just use some different method that goes end to
>> end.  The always-loved INFO comes to mind.
>
> What makes you think that INFO goes end to end? An SBC can absorb it  
> if it wants to.
>
> But this handling is not a bug, it's a feature. Since the SBC is  
> call-stateful, it knows about the outgoing call, and thus can  
> authoritatively say "Yes, this call was from Dan" without having to  
> congest your low-rate end-link.
>

Smells a lot like the "you break it you bought it" model for SBCs and  
RFC 4474.


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

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


From sip-bounces@ietf.org  Thu Oct 30 14:41:46 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 52E9D3A6B72;
	Thu, 30 Oct 2008 14:41:46 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D0FD43A6B71
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 14:41:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.135
X-Spam-Level: 
X-Spam-Status: No, score=-2.135 tagged_above=-999 required=5 tests=[AWL=0.164, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id enV3q0mDGlEy for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 14:41:44 -0700 (PDT)
Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk
	[195.171.110.225])
	by core3.amsl.com (Postfix) with ESMTP id 8E7673A6B73
	for <sip@ietf.org>; Thu, 30 Oct 2008 14:41:44 -0700 (PDT)
Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235])
	by siemenscomms.co.uk (PMDF V6.3-x14 #31430)
	with ESMTP id <0K9K0081CMPQ5C@siemenscomms.co.uk> for sip@ietf.org; Thu,
	30 Oct 2008 21:37:03 +0000 (GMT)
Date: Thu, 30 Oct 2008 21:37:02 +0000
From: "Elwell, John" <john.elwell@siemens.com>
In-reply-to: <007b01c939f6$6f33e5e0$24726b80@cisco.com>
To: Dan Wing <dwing@cisco.com>, =?iso-8859-1?Q?Victor_Pascual_=C1vila?=
	<victor.pascual.avila@gmail.com>
Message-id: <0D5F89FAC29E2C41B98A6A762007F5D001383219@GBNTHT12009MSX.gb002.siemens.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: [Sip] submission of a new I-D:
	"Dialog Event	foRIdentityVErification"
Thread-Index: Ack5t7eqvsEFA64yQGajGAp6h2A1tAAOorZwAC0WVZA=
Content-class: urn:content-classes:message
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>
	<200810261145.19745.ibc@aliax.net>
	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
	<084c01c938a0$a41ff390$c3f0200a@cisco.com>
	<cc1f582e0810280444y42b8f723w938004e902fb1180@mail.gmail.com>
	<032301c93978$6b249c70$c3f0200a@cisco.com>
	<618e24240810290415i7ede4601tf2fd78aaed755445@mail.gmail.com>
	<007b01c939f6$6f33e5e0$24726b80@cisco.com>
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog
 Event	foRIdentityVErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 =


> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On =

> Behalf Of Dan Wing
> Sent: 29 October 2008 18:45
> To: 'Victor Pascual =C1vila'
> Cc: sip@ietf.org
> Subject: Re: [Sip] submission of a new I-D: "Dialog Event =

> foRIdentityVErification"
> =

> =

>  =

> =

> > -----Original Message-----
> > From: Victor Pascual =C1vila [mailto:victor.pascual.avila@gmail.com] =

> > Sent: Wednesday, October 29, 2008 4:16 AM
> > To: Dan Wing
> > Cc: sip@ietf.org
> > Subject: Re: [Sip] submission of a new I-D: "Dialog Event =

> > foRIdentityVErification"
> > =

> > Hi Dan,
> > Please, see my comments inline.
> > =

> > On Wed, Oct 29, 2008 at 4:42 AM, Dan Wing <dwing@cisco.com> wrote:
> > >> 2008/10/28 Dan Wing <dwing@cisco.com>:
> > >> > Here is another return routability check,
> > >> > =

> http://tools.ietf.org/html/draft-wing-sip-e164-rrc-01#section-3.1
> > >> > (My I-D expired due to lack of interest.)
> > >>
> > >> It uses RFC 4474, certificates... is it really feasible in
> > >> this real world?
> > >
> > > No, it doesn't use RFC4474.  The steps merely show where =

> an RFC4474
> > > signature could be performed.  If no RFC4474 signatures are
> > > being created, or validated, those steps are the 'null operation'
> > > (not performed).  Without those steps, it is remarkably similar
> > > to DERIVE.
> > >
> > >> IMHO "Dialog Event foR Identity VErification" is the =

> more feasible
> > >> solution at the moment.
> > >
> > > The differences are minor.
> > =

> > The Return Routability Check (RRC) determines if a domain rightfully
> > 'owns' an E.164 phone number, but DOES NOT prevent an attacker from
> > presenting a forged "From" header field.
> > =

> > As an example:
> > =

> > INVITE sip:victor@tekelec.com SIP/2.0
> > From: +14085551234 =

> > <sip:+14085551234@iptel.org;user=3Dphone>;tag=3D9fxced76sl
> > To: Victor <sip:victor@tekelec.com>
> > Call-ID: 3848276298220188511@iptel.org
> > Contact: <sip:attacker@pc1.attacker.com>
> > Content-Type: application/sdp
> > Content-Length: ...
> > =

> > [SDP not shown]
> > =

> > Where iptel.org owns the +14085551234 number.
> > =

> > Section 3.2:
> > -The SUBSCRIBE should be immediately acknowledged
> > -A NOTIFY should be immediately created and sent
> > =

> > =

> > Moreover IMO:
> > - it requires the use of signatures (or RFC4474): see =

> > Sections 3, 3.1 and 3.2
> =

> As I said previously:  if there is no signature service, this =

> is the null
> operation.  The UA is competely incapable of causing or =

> forcing its domain to
> generate an RFC4474 signature, anyway, so it's impossible for a UA to
> 'require' such a signature.
> =

> > - it is defined to be used only with e164-based SIP URIs
> > =

> > In short, this is a good document but, as I mentioned before, ONLY
> > determines if a domain rightfully 'owns' an E.164 phone number, it
> > doesn't ask "are you calling me?"
> =

> Easily added; draft-wing-sip-e164-rrc-01 currently reads:
> =

>    3.2.  Authentication Service or Calling Endpoint Operation
> =

>    The steps described in this section can be performed by the
>    authentication service or by the calling endpoint.
> =

>    The authentication service or the calling endpoint, upon =

> receiving a
>    SUBSCRIBE for the return-routability event package, performs the
>    following steps:
> =

>    1.   The SUBSCRIBE should be immediately acknowledged with a 200 Ok
>        ^
>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>    INSERT "If there is another active INVITE dialog, which has not =

>            received its 200 Ok, then"
> =

>        message.
>                 ^
>       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>       INSERT "If there is not another active INVITE dialog, an error
>         response is sent (e.g., 4xx), and processing stops."
> =

>    2.  A NOTIFY should be immediately created, containing the same
>        application/return-routability-nonce copied from the SUBSCRIBE.
>        This NOTIFY contains a To and Request-URI which match =

> the From of
>        the SUBSCRIBE.
> =

>    3.  This NOTIFY is sent.
> =

>    4.  The RFC4474 authentication service, operating at the =

> domain, will
>        create a signature over the NOTIFY.  This is used by the remote
>        domain's verification service (see Section 3.1).
> =

> =

> I'm not interested in having a competing proposal, though, or arguing
> nits about which 4xx response code is most appropriate.
> =

> We should be arguing about larger issues, such as the value =

> of proving =

> someone is actually originating a call.  Without that, we cannot have =

> reliable whitelists or reliably blacklists, which are the foundations =

> for authorizing incoming SIP requests.
> =

> I support draft-kuthan-sip-derive-00, and hope the WG can devote
> time and energy to improving and standardizing it to work well
> across a variety of networks.
[JRE] I agree. This must include networks that contain B2BUAs/SBCs.

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


From sip-bounces@ietf.org  Thu Oct 30 14:42:10 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 101CD3A6B53;
	Thu, 30 Oct 2008 14:42:10 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E7CBB3A6B53
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 14:42:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.085
X-Spam-Level: 
X-Spam-Status: No, score=-6.085 tagged_above=-999 required=5 tests=[AWL=0.164, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id pCdm1HccdKZp for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 14:42:08 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id A69793A6AB0
	for <SIP@ietf.org>; Thu, 30 Oct 2008 14:42:07 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	4CE5620C88; Thu, 30 Oct 2008 22:41:49 +0100 (CET)
X-AuditID: c1b4fb3c-ab0c8bb0000015b5-7a-490a2a1dbf7f
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	22F3920C27; Thu, 30 Oct 2008 22:41:49 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Oct 2008 22:41:49 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 30 Oct 2008 22:38:05 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CCFDD@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Proposal for multiple INFO bodies in an INFO
thread-index: Ack6wLh5s3PTvRyVRZayIfhxMiaWFwAFxKNj
References: <322862FF-3683-465F-B1A0-8C619A5D60E1@standardstrack.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Eric Burger" <eburger@standardstrack.com>, "IETF SIP List" <SIP@ietf.org>
X-OriginalArrivalTime: 30 Oct 2008 21:41:49.0049 (UTC)
	FILETIME=[50400690:01C93AD8]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [Sip] Proposal for multiple INFO bodies in an INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi Erick,
 
I am not your suggestion of using CID for Info packages is what has been discussed (I may be wrong, of course).
 
I think what Paul was proposing was to have a Content-Disposition value indicating that a particular body shall be treated as in info package.
 
INFO .....
To: ....
From: ....
Info-Package: foo
Content-Type: application/foo
Content-Dispotistion: info
...

<foo body>


Multipart mixed example with indirect content:

INFO ....
To: ....
From: ....
Info-Package: foo
Content-Type: multipart/mixed;boundary="theboundary"
...

--theboundary
Content-Type: application/mumble
Content-Disposition: whatever

<mumble body>

--theboundary
Content-Type: application/foo
Content-Disposition: info

<foo body>

--theboundary--

 
 
Regards,
 
Christer

________________________________

From: sip-bounces@ietf.org on behalf of Eric Burger
Sent: Thu 30/10/2008 19:29
To: IETF SIP List
Subject: [Sip] Proposal for multiple INFO bodies in an INFO



Good thing I waited 10 days...

Initially, I was very swayed by the argument that things would be 
much, much easier if we restricted an INFO request to a single Info-
Package.

However, and especially as the last person to touch RFC 4483, I can 
see the argument that *any* SIP message can end up with a multipart/
mime body, even if you think you can limit it to just your stuff, 
because the UA can always have a content indirection pointer in the 
header pointing to a mime body part.

Therefore, even if we restrict an INFO request to carry a single Info-
Package, we need a mechanism to uniquely identify and, at the SIP 
header level, indicate which body part belongs to the package.

I would offer once we solve that, we also get multiple INFO request 
bodies for free.

I would also offer that since INFO does not change SIP state, which 
means there is not even a concept of a message succeeding but the INFO 
body doing something that "fails", the objection that it would be hard 
for a UA to report on one body "failing" with another body 
"succeeding" is a non-issue.  Yes, this does mean that you cannot use 
INFO to tunnel IP.  See RFC 3252 for more on this.  I do not see this 
as a problem.

Therefore, on to the solution.  We use the MIME approach.  The body 
parts get tagged with Content-IDs. The Info-Package has a parameter, 
CID, which points to the body part.  The ONLY question I have is 
whether we should simply mandate always having this parameter to make 
the protocol and parser easier, but a small burden on UAC's that 
really are only sending a single body.  Other than that, the mechanism 
looks like:

INFO .....
To: ....
From: ....
Info-Package: foo
Content-Type: application/foo;cid=this
Content-Id: this
...

<foo body>



Multipart mixed example with indirect content:

INFO ....
To: ....
From: ....
Info-Package: foo;cid=abcd1234zz
Mumble: <cid:abcd9999qq>
Content-Type: multipart/mixed;boundary="theboundary"
...

--theboundary
Content-Type: application/mumble
Content-Id: abcd9999qq
...

<mumble stuff>

--theboundary
Content-Type: application/foo
Content-Id: abcd1234zz

<foo body>

--theboundary--




Multiple Info Packages follow. Note that by using Content-Id, order is 
irrelevant.

INFO ....
To: ....
From: ....
Info-Package: foo;cid=abcd1234zz
Info-Package: bar;cid=wxyz9876
Content-Type: multipart/mixed;boundary="theboundary"
...

--theboundary
Content-Type: application/bar
Content-Id: wxyz9876
...

<bar stuff>

--theboundary
Content-Type: application/foo
Content-Id: abcd1234zz

<foo body>

--theboundary-- 

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


From sip-bounces@ietf.org  Thu Oct 30 14:51:31 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CE3493A68CC;
	Thu, 30 Oct 2008 14:51:31 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 975123A68CC
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 14:51:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2lBDNMWM5OPv for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 14:51:29 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id BB4EC3A67A4
	for <sip@ietf.org>; Thu, 30 Oct 2008 14:51:29 -0700 (PDT)
Received: from [192.168.2.102] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9ULotrb028638
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 30 Oct 2008 16:50:57 -0500
Message-Id: <5BC604B4-17CA-4CC7-8476-1485A5A20FB8@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Jiri Kuthan <jiri@iptel.org>
In-Reply-To: <490A0E7F.3010206@iptel.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 30 Oct 2008 16:50:48 -0500
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com><490792EA.2020106@softarmor.com><033f01c9397b$860847a0$c3f0200a@cisco.com><200810292306.44911.ibc@aliax.net><000901c93a36$3d4755e0$c3f0200a@cisco.com>	<17345A0C-8BFD-4D0D-B597-ECA8801F72D5@softarmor.com>
	<5D1A7985295922448D5550C94DE291800245C0C7@DEEXC1U01.de.lucent.com>
	<490A0E7F.3010206@iptel.org>
X-Mailer: Apple Mail (2.929.2)
Cc: sip@ietf.org, "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>,
	Dan Wing <dwing@cisco.com>
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 30, 2008, at 2:43 PM, Jiri Kuthan wrote:
>
> I'm wondering if other WG participants would agree with me that  
> "verifying
> who is sending me this SIP request is who he claims to be in the  
> simplest
> possible way (i.e., without other protocols and infrastructures) by  
> reverse
> lookup" would be an appropriate goal.
>

Leaving aside the question of whether the success of the DERIVE RRC  
answer's the question you've asked above (I don't think it does; it  
merely verifies that the a node reachable at the AOR to which the  
request is attributed has particular knowledge of the SIP request in  
question), let's ask if we understand the unintended consequences.

There are fundamental assumptions in this sort of RRC model that the  
node initiating the dialog request is in fact reachable by some sort  
of AOR, and that this is the AOR that will be presented in the request  
as that of its originator. This is not universally true.

Envision a presence-enabled call controller (PECC) employed by Alice.  
Alice wants to call Bob, whenever Alice and Bob are both on-line.

So PECC subscribes to Alice and Bob.

Eventually Alice and BOb are both on-line, so PECC sets up the call.

What's in the From" going to Bob? It's probably Alice's AOR, as PECC  
is working on her behalf, and there's some reason to think that Bob is  
willing to accept calls from Alice. But PECC cannot REGISTER as Alice,  
for obvious reasons.

Bob uses DERIVE, and sends a SUBSCRIBE to Alice that references the  
dialog that is between PECC and Bob.

Can Alice's UA respond appropriately? I think not.

There are other ways to construct the type of application I'm talking  
about, that might work with DERIVE. Do we want to force a redesign of  
SIP applications so that return-routability to the originating AOR is  
required? This might not be a bad thing, but I think it is a very  
primal thing, and is potentially quite disruptive to application  
scenarios. That might be OK, but we need to understand the  
consequences before we go down that road.

--
Dean




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


From sip-bounces@ietf.org  Thu Oct 30 14:54:04 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4333C3A6B53;
	Thu, 30 Oct 2008 14:54:04 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DC14F3A6B53
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 14:54:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id sUtm8ybagTPV for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 14:54:02 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 19F513A6B45
	for <sip@ietf.org>; Thu, 30 Oct 2008 14:54:02 -0700 (PDT)
Received: from [192.168.2.102] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9ULrnED028678
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Thu, 30 Oct 2008 16:53:50 -0500
Message-Id: <CB5ABE64-B8E6-4FEF-B56E-9D68E253B689@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Ben Campbell <ben@estacado.net>
In-Reply-To: <1A770AC3-26C6-4D16-86A2-35533896F3C0@estacado.net>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 30 Oct 2008 16:53:43 -0500
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com><0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
	<490792EA.2020106@softarmor.com>
	<033f01c9397b$860847a0$c3f0200a@cisco.com>
	<36E83843-775F-4317-BB0F-746E55194BFD@softarmor.com>
	<1A770AC3-26C6-4D16-86A2-35533896F3C0@estacado.net>
X-Mailer: Apple Mail (2.929.2)
Cc: Sip List <sip@ietf.org>
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 30, 2008, at 4:11 PM, Ben Campbell wrote:

>
> On Oct 29, 2008, at 6:40 PM, Dean Willis wrote:
>
>>
>> On Oct 28, 2008, at 11:05 PM, Dan Wing wrote:
>>>>
>>>> Would the SBC not have to handle the SUBSCRIBE request locally?  
>>>> After
>>>> all, since it is a terminal UA for the call, it also knows
>>>> about all the
>>>> dialog states. The end-user UA would never even see the SUBSCRIBE.
>>>
>>> If that's a problem, just use some different method that goes end to
>>> end.  The always-loved INFO comes to mind.
>>
>> What makes you think that INFO goes end to end? An SBC can absorb  
>> it if it wants to.
>>
>> But this handling is not a bug, it's a feature. Since the SBC is  
>> call-stateful, it knows about the outgoing call, and thus can  
>> authoritatively say "Yes, this call was from Dan" without having to  
>> congest your low-rate end-link.
>>
>
> Smells a lot like the "you break it you bought it" model for SBCs  
> and RFC 4474.

Which is why identity is always transitive in nature . . .

Alice's cousin Bob knows this woman Carol who is placing a call to  
Alice's friend Dave. Meanwhile, weasels have eaten our PBX.

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


From sip-bounces@ietf.org  Thu Oct 30 15:51:30 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3BD5E3A68C6;
	Thu, 30 Oct 2008 15:51:30 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7192B3A68C6
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 15:51:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Y-NUwcarDbij for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 15:51:28 -0700 (PDT)
Received: from mail.iptel.org (smtp.iptel.org [213.192.59.67])
	by core3.amsl.com (Postfix) with ESMTP id 413B13A67A1
	for <sip@ietf.org>; Thu, 30 Oct 2008 15:51:28 -0700 (PDT)
Received: from jiri-kuthans-macbook-pro-8.local (shell.iptel.org
	[213.192.59.74])
	by mail.iptel.org (Postfix) with ESMTP id D30EF1812D55;
	Thu, 30 Oct 2008 23:51:25 +0100 (CET)
Message-ID: <490A3A6D.5030404@iptel.org>
Date: Thu, 30 Oct 2008 23:51:25 +0100
From: Jiri Kuthan <jiri@iptel.org>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com><490792EA.2020106@softarmor.com><033f01c9397b$860847a0$c3f0200a@cisco.com><200810292306.44911.ibc@aliax.net><000901c93a36$3d4755e0$c3f0200a@cisco.com>	<17345A0C-8BFD-4D0D-B597-ECA8801F72D5@softarmor.com>
	<5D1A7985295922448D5550C94DE291800245C0C7@DEEXC1U01.de.lucent.com>
	<490A0E7F.3010206@iptel.org>
	<5BC604B4-17CA-4CC7-8476-1485A5A20FB8@softarmor.com>
In-Reply-To: <5BC604B4-17CA-4CC7-8476-1485A5A20FB8@softarmor.com>
Cc: sip@ietf.org, "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>,
	Dan Wing <dwing@cisco.com>
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Dean Willis wrote:
> 
> On Oct 30, 2008, at 2:43 PM, Jiri Kuthan wrote:
>>
>> I'm wondering if other WG participants would agree with me that 
>> "verifying
>> who is sending me this SIP request is who he claims to be in the simplest
>> possible way (i.e., without other protocols and infrastructures) by 
>> reverse
>> lookup" would be an appropriate goal.
>>
> 
> Leaving aside the question of whether the success of the DERIVE RRC 
> answer's the question you've asked above (I don't think it does; it 
> merely verifies that the a node reachable at the AOR to which the 
> request is attributed has particular knowledge of the SIP request in 
> question), let's ask if we understand the unintended consequences.
> 
> There are fundamental assumptions in this sort of RRC model that the 
> node initiating the dialog request is in fact reachable by some sort of 
> AOR, 

Indeed -- that's a known limitation. There is a variety of reasons why
derive leaning on backwards routing for a subscription can fail:
UAC is unregistered, UAC has permanent call-forwarding set up, UAC
chose to make itself known as "anonymous", the UAC does support SUB-NOT,
tel-URI is not assignable to the originating UAC, ....

In summary, we gain a good deal of certainty in case it works and that's
it. If it does not work, we know that we don't know, like before.
Actually applicability should have been stated already in the abstract,
that's an important point -- sorry about that.


> and that this is the AOR that will be presented in the request as 
> that of its originator. This is not universally true.

Agreed too, that should be clearly stated under known limitations too.

> Envision a presence-enabled call controller (PECC) employed by Alice. 
> Alice wants to call Bob, whenever Alice and Bob are both on-line.
> 
> So PECC subscribes to Alice and Bob.
> 
> Eventually Alice and BOb are both on-line, so PECC sets up the call.
> 
> What's in the From" going to Bob? It's probably Alice's AOR, as PECC is 
> working on her behalf, and there's some reason to think that Bob is 
> willing to accept calls from Alice. But PECC cannot REGISTER as Alice, 
> for obvious reasons.
> 
> Bob uses DERIVE, and sends a SUBSCRIBE to Alice that references the 
> dialog that is between PECC and Bob.
> 
> Can Alice's UA respond appropriately? I think not.


The point is DERIVE tells you here "we know that we don't know". It
can label the incoming call grey (as opposed to green if it worked)
and leave it to the callee's discretion how to handle it. (deny-all,
deny-this,answer-this,what-have-you).

The 3pcc case you are mentioning is certainly not the only one we
could add to the list of failure reasons mentioned above.


> There are other ways to construct the type of application I'm talking 
> about, that might work with DERIVE. Do we want to force a redesign of 
> SIP applications so that return-routability to the originating AOR is 
> required? 

Well -- I don't think this is about us/ietf, it is about the actual users
and deployments choosing how to put things together. In the actual
deployments I'm aware of, non-reverse-routeable URIs are not a concern
for the adopters (except tel URI), unsolicited traffic begins to be.
Obviously, in environments building upon 3pcc, derive can produce little
value.

How the balance develops between UAS users relying on derive-like
mechanisms for "trash separation", and UAC users using it to increase
the chance of their calls to get through -- difficult to say now.
DNS reverse verification has apparently taken off, even though I'm sure
there were similar limitations.



> This might not be a bad thing, but I think it is a very primal
> thing, and is potentially quite disruptive to application scenarios. 
> That might be OK, but we need to understand the consequences before we 
> go down that road.

Understanding the known limitations and applicability is for sure one
of the most important pieces here.

-jiri

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


From sip-bounces@ietf.org  Thu Oct 30 16:07:09 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 889D63A6B73;
	Thu, 30 Oct 2008 16:07:09 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2715528C191
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 16:07:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.286
X-Spam-Level: 
X-Spam-Status: No, score=-2.286 tagged_above=-999 required=5 tests=[AWL=0.013, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id yfMjVNU3VJU4 for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 16:07:07 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.26])
	by core3.amsl.com (Postfix) with ESMTP id D698E3A6B73
	for <sip@ietf.org>; Thu, 30 Oct 2008 16:07:06 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 9so370789eyd.31
	for <sip@ietf.org>; Thu, 30 Oct 2008 16:07:03 -0700 (PDT)
Received: by 10.210.57.12 with SMTP id f12mr12392383eba.199.1225408023445;
	Thu, 30 Oct 2008 16:07:03 -0700 (PDT)
Received: from portatil.local (82.pool85-58-129.dynamic.orange.es
	[85.58.129.82])
	by mx.google.com with ESMTPS id b33sm2287081ika.1.2008.10.30.16.07.01
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Thu, 30 Oct 2008 16:07:02 -0700 (PDT)
From: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
To: sip@ietf.org
Date: Fri, 31 Oct 2008 00:06:58 +0100
User-Agent: KMail/1.9.9
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<490A0E7F.3010206@iptel.org>
	<5BC604B4-17CA-4CC7-8476-1485A5A20FB8@softarmor.com>
In-Reply-To: <5BC604B4-17CA-4CC7-8476-1485A5A20FB8@softarmor.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810310006.58854.ibc@aliax.net>
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

El Jueves, 30 de Octubre de 2008, Dean Willis escribi=F3:
> On Oct 30, 2008, at 2:43 PM, Jiri Kuthan wrote:
> > I'm wondering if other WG participants would agree with me that
> > "verifying
> > who is sending me this SIP request is who he claims to be in the
> > simplest
> > possible way (i.e., without other protocols and infrastructures) by
> > reverse
> > lookup" would be an appropriate goal.
>
> Leaving aside the question of whether the success of the DERIVE RRC
> answer's the question you've asked above (I don't think it does; it
> merely verifies that the a node reachable at the AOR to which the
> request is attributed has particular knowledge of the SIP request in
> question), let's ask if we understand the unintended consequences.
>
> There are fundamental assumptions in this sort of RRC model that the
> node initiating the dialog request is in fact reachable by some sort
> of AOR, and that this is the AOR that will be presented in the request
> as that of its originator. This is not universally true.
>
> Envision a presence-enabled call controller (PECC) employed by Alice.
> Alice wants to call Bob, whenever Alice and Bob are both on-line.
>
> So PECC subscribes to Alice and Bob.
>
> Eventually Alice and BOb are both on-line, so PECC sets up the call.
>
> What's in the From" going to Bob? It's probably Alice's AOR, as PECC
> is working on her behalf, and there's some reason to think that Bob is
> willing to accept calls from Alice. But PECC cannot REGISTER as Alice,
> for obvious reasons.
>
> Bob uses DERIVE, and sends a SUBSCRIBE to Alice that references the
> dialog that is between PECC and Bob.
>
> Can Alice's UA respond appropriately? I think not.
>
> There are other ways to construct the type of application I'm talking
> about, that might work with DERIVE. Do we want to force a redesign of
> SIP applications so that return-routability to the originating AOR is
> required? This might not be a bad thing, but I think it is a very
> primal thing, and is potentially quite disruptive to application
> scenarios. That might be OK, but we need to understand the
> consequences before we go down that road.

Hi,

While your explanation makes sense, it seems to conclude that the simple =

mechanism described in DERIVE should not be considered due to some "exotic" =

scenarios in which it could fail (mostly in presence of border controller).

But I'm sure that any other sender verification proposals appearing in this =

thread (as other drafts) also doesn't cover all the possible scenarios. At =

least, DERIVE seems useful in most common cases, and it just requires devic=
es =

supporting RFC 4235.
Of course, the presence of border controllers and B2BUA's always break any =

divine topology full of proxies defined in any RFC. DERIVE is not an =

exception.

So people involved in IETF can accept a simple and feasible solution as the =

current proposal, or just drop it and wait for other proposals full of =

certificate usage, bidirectional authentication and more stuff that will be =

never feasible in the real world. But this is just my opinion. Of course yo=
u =

could be right.

Thanks.


-- =

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


From sip-bounces@ietf.org  Thu Oct 30 16:09:43 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D33483A6B73;
	Thu, 30 Oct 2008 16:09:43 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 070943A6B73
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 16:09:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id uCleE3pdYoYh for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 16:09:41 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net
	[IPv6:2001:470:1f03:267::2])
	by core3.amsl.com (Postfix) with ESMTP id D3A2D3A6943
	for <sip@ietf.org>; Thu, 30 Oct 2008 16:09:38 -0700 (PDT)
Received: from hydra-3.local (ppp-70-244-167-40.dsl.rcsntx.swbell.net
	[70.244.167.40]) (authenticated bits=0)
	by nostrum.com (8.14.3/8.14.1) with ESMTP id m9UN9Sg7033440
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 30 Oct 2008 18:09:29 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <490A3EA8.1040004@nostrum.com>
Date: Thu, 30 Oct 2008 18:09:28 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.com>
References: <200810251926.17644.ibc@aliax.net> <490382B6.1090400@cisco.com>
In-Reply-To: <490382B6.1090400@cisco.com>
Received-SPF: pass (nostrum.com: 70.244.167.40 is authenticated by a trusted
	mechanism)
X-Virus-Scanned: ClamAV 0.94/8544/Thu Oct 30 13:59:19 2008 on
	shaman.nostrum.com
X-Virus-Status: Clean
Cc: sip@ietf.org
Subject: Re: [Sip] [RFC 4235 & draft-kuthan-sip-derive] 481 "Call doesn't
 exist"	for initial SUBSCRIBE ?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

V2hpbGUgNDAzIHdvdWxkIGJlIHZhbGlkIGlmIGxvY2FsIHBvbGljeSB3YXJyYW50cywgbXkgcmVh
ZGluZyBvZiA0MjM1IGlzIAp0aGF0IGFuIGF1dGhvcml6ZWQgc3Vic2NyaWJlciB3b3VsZCBzdGFy
dCBnZXR0aW5nIE5PVElGWSBtZXNzYWdlcyB0aGF0IApjb250YWluIG5vIGRpYWxvZyBpbmZvcm1h
dGlvbi4gVGhlIGRpYWxvZyBpZGVudGlmaWVyIGlzIHRyZWF0ZWQgYXMgYSAKZmlsdGVyLiBUaGUg
YXBwbGljYXRpb24gb2YgdGhhdCBmaWx0ZXIgdG8gdGhlIGV4aXN0aW5nIGRpYWxvZ3MgbWlnaHQg
YmUgCmFuIGVtcHR5IHNldC4KCi9hCgpQYXVsIEt5eml2YXQgd3JvdGU6Cj4gSSBhZ3JlZSB0aGF0
IDQ4MSBzZWVtcyBhbiB1bnN1aXRhYmxlIHJlc3BvbnNlIGluIHRoaXMgY2FzZS4KPiBJdHMgbm90
IGNsZWFyIHRvIG1lIHdoYXQgcmVzcG9uc2UgaXMgYmVzdCBzdWl0ZWQuIFBlcmhhcHMgNDAzIG9y
IDYwMy4KPgo+ICAgICBUaGFua3MsCj4gICAgIFBhdWwKPgo+IEnDsWFraSBCYXogQ2FzdGlsbG8g
d3JvdGU6Cj4+IEhpLCBJJ3ZlIGEgZG91YnQgYWJvdXQgd2hhdCBzaG91bGQgYmUgdGhlIGNvcnJl
Y3QgcmVzcG9uc2UgZm9yIGFuIAo+PiBpbml0aWFsIFNVQlNDUklCRSAoRXZlbnQ6IGRpYWxvZykg
aWYgdGhlIGluZGljYXRlZCBkaWFsb2cgZG9lc24ndCAKPj4gZXhpc3QgaW4gdGhlIHJlY2lwaWVu
dCBvZiB0aGUgU1VCU0NSSUJFLgo+Pgo+PiBUaGlzIGRvdWJ0IGNvbWVzIGFmdGVyIHJlYWRpbmcg
dGhlIHRvZGF5IHN1Ym1pdHRlZCBkcmFmdCAiRGlhbG9nIAo+PiBFdmVudCBmb1IgSWRlbnRpdHkg
VkVyaWZpY2F0aW9uIjoKPj4gICAKPj4gaHR0cDovL3d3dzMuaWV0Zi5vcmcvcHJvY2VlZGluZ3Mv
c3RhZ2luZy9kcmFmdC1rdXRoYW4tc2lwLWRlcml2ZS0wMC50eHQKPj4KPj4gSW4gcGFnZSAxNCBv
ZiB0aGlzIGRyYWZ0IHRoZXJlIGlzIGEgZmxvdyBhYm91dCBhIHN1c3BpY2lvdXMgY2FsbCAKPj4g
KHNwb29mZWQgRnJvbSkuIFRoZSBmbG93IGlzIGNvcnJlY3RseSBkaXNwbGF5ZWQgdXNpbmcgZml4
ZWQgbGVuZ3RoIAo+PiB0eXBvZ3JhcGh5LCBpZiBpdCdzIG5vdCB5b3VyIGNhc2UgcmVmZXIgdG8g
cGFnZSAxNCBvZiB0aGUgZHJhZnQuCj4+Cj4+Cj4+ICAgICBBdHRhY2tlciAgICAgICAgQWxpY2Ug
ICBQcm94eSAxIChhdGxhbnRhLmNvbSkgUHJveHkgMiAKPj4gKGJpbG94aS5jb20pIEJvYgo+PiAg
ICAgfCAgICAgICAgICAgICAgIHwgSU5WSVRFIEY1ICAgICAgfCAgICAgICAgICAgICAgICB8ICAg
ICAgICAgICAgICAgIHwKPj4gICAgIHwtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0+fCAgICAgICAgICAgICAgICB8Cj4+ICAgICB8ICAgICAgICAgICAgICAg
fCAxMDAgRjYgICAgICAgICB8ICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgfAo+PiAg
ICAgfDwtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS18IElO
VklURSBGNyAgICAgIHwKPj4gICAgIHwgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgIHwg
ICAgICAgICAgICAgICAgfC0tLS0tLS0tLS0tLS0tLT58Cj4+ICAgICB8ICAgICAgICAgICAgICAg
fCAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgIHwgMTAwIEY4ICAgICAgICAgfAo+PiAg
ICAgfCAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICB8PC0t
LS0tLS0tLS0tLS0tLXwKPj4gICAgIHwgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgIHwg
ICAgICAgICAgICAgICAgfCBTVUJTQ1JJQkUgRjkgICB8Cj4+ICAgICB8ICAgICAgICAgICAgICAg
fCAgICAgICAgICAgICAgICB8IFNVQlNDUklCRSBGMTAgIHw8LS0tLS0tLS0tLS0tLS0tfAo+PiAg
ICAgfCAgICAgICAgICAgICAgIHwgU1VCU0NSSUJFIEYxMSAgfDwtLS0tLS0tLS0tLS0tLS18ICAg
ICAgICAgICAgICAgIHwKPj4gICAgIHwgICAgICAgICAgICAgICB8PC0tLS0tLS0tLS0tLS0tLXwg
ICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICB8Cj4+ICAgICB8ICAgICAgICAgICAgICAg
fCA0ODEgRjEyICAgICAgICB8ICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgfAo+PiAg
ICAgfCAgICAgICAgICAgICAgIHwtLS0tLS0tLS0tLS0tLS0+fCA0ODEgRjEzICAgICAgICB8ICAg
ICAgICAgICAgICAgIHwKPj4gICAgIHwgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgIHwt
LS0tLS0tLS0tLS0tLS0+fCA0ODEgRjE0ICAgICAgICB8Cj4+ICAgICB8ICAgICAgICAgICAgICAg
fCAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgIHwtLS0tLS0tLS0tLS0tLS0+fAo+Pgo+
Pgo+PiBTbywgQm9iIHNlbmRzIGFuIGluaXRpYWwgU1VCU0NSSUJFIHRvIEFsaWNlIEFvUiAodGhl
IHJlY2VpdmVkIEZyb20gCj4+IHVyaSBpbiB0aGUgSU5WSVRFIEY1L0Y3KSB3aXRoIHRoZSBoYWxm
LWRpYWxvZyBkYXRhOgo+Pgo+PiAgICBTVUJTQ1JJQkUgc2lwOmFsaWNlQGF0bGFudGEuY29tIFNJ
UC8yLjAKPj4gICAgRnJvbTogQm9iIDxzaXA6Qm9iQGJpbG94aS5jb20+O3RhZz04NjcyMzQ5Cj4+
ICAgIFRvOiA8c2lwOmFsaWNlQGF0bGFudGEuY29tPgo+PiAgICBDYWxsLUlEOiB4dDQ2NTNnczJo
YW1AYmlsb3hpLmNvbQo+PiAgICBDb250YWN0OiA8c2lwOmJvYkBjbGllbnQuYmlsb3h5LmNvbT4K
Pj4gICAgRXZlbnQ6IAo+PiBkaWFsb2c7Y2FsbC1pZD0zODQ4Mjc2Mjk4MjIwMTg4NTExQGF0bGFu
dGEuY29tO3RvLXRhZz05ZnhjZWQ3NnNsCj4+ICAgIEV4cGlyZXM9MAo+PiAgICBBY2NlcHQ6IGFw
cGxpY2F0aW9uL2RpYWxvZy1pbmZvK3htbAo+PiAgICBDb250ZW50LUxlbmd0aDogMAo+Pgo+PiBO
b3RlIHRoYXQgIkV2ZW50IiBoZWFkZXIgY29udGFpbnMgc3BlY2lmaWMgaGFsZi1kaWFsb2cgaW5m
b3JtYXRpb24uCj4+Cj4+IFRoaXMgU1VCU0NSSUJFIGFycml2ZXMgdG8gQWxpY2UncyBVQSB3aGlj
aCBpcyBub3QgYXdhcmUgb2YgdGhhdCAKPj4gZGlhbG9nLiBXaGljaCByZXNwb25zZSBzaG91bGQg
aXQgcmVwbHk/IFRoZSBmbG93IHN1Z2dlc3RzICI0ODEgCj4+IENhbGwvVHJhbnNhY3Rpb24gZG9l
c24ndCBleGlzdCIsIGJ1dC4uLiBpcyBpdCBjb3JyZWN0Pwo+Pgo+PiBBRkFJSywgYSA0ODEgc2hv
dWxkIGJlIHJlcGxpZWQgd2hlbiBhbiAqaW4tZGlhbG9nKiByZXF1ZXN0IGFycml2ZXMgdG8gCj4+
IGFuIFVBUyB3aGljaCBpcyBub3QgYXdhcmUgb2YgdGhhdCBkaWFsb2cuIEJ1dCBpbiB0aGUgYWJv
dmUgY2FzZSB3ZSAKPj4gaGF2ZSBhbiAqaW5pdGlhbCogcmVxdWVzdCBhbmQgdGhlIDQ4MSByZWZl
cnMgdG8gdGhlIHNwZWNpZmljIGRpYWxvZyAKPj4gaW4gdGhlICJFdmVudCIgaGVhZGVyLgo+Pgo+
Pgo+PiBXZWxsLCBJIHN1Z2dlc3QgYSBwb3NzaWJsZSBpc3N1ZSB3aXRoIHRoZSBhYm92ZSBiZWhh
dmlvdXI6Cj4+Cj4+IC0gQWxpY2UgaW52aXRlcyBCb2IuCj4+IC0gQmVmb3JlIHNlbmRpbmcgYSBw
cm92aXNpb25hbCByZXNwb25zZSwgQm9iIHNlbmRzIGFuICppbml0aWFsKiAKPj4gU1VCU0NSSUJF
IHRvIEFsaWNlIHdpdGggdGhlIGN1cnJlbnQgaGFsZi1kaWFsb2cgaW5mb3JtYXRpb24gaW4gdGhl
IAo+PiAiRXZlbnQiIGhlYWRlci4KPj4gLSBBbGljZSBhY2NlcHRzIHRoZSBTVUJTQ1JJQkUsIHJl
cGxpZXMgMjAwIGFuZCBsYXRlciBhIE5PVElGWSB3aXRoIAo+PiB0aGUgc3BlY2lmaWMgZGlhbG9n
IHN0YXR1cy4KPj4KPj4gYSkKPj4gLSBBZnRlciA0MCBzZWNvbmRzIEFsaWNlJ3MgVUEgY3Jhc2hl
cyBhbmQgaXMgcmVzdGFydGVkIChkaWFsb2cgaW5mbyAKPj4gbG9zdCkuCj4+IC0gQm9iIHNlbmRz
IGEgU1VCU0NSSUJFIHJlZnJlc2ggKGFuIGluLWRpYWxvZyByZXF1ZXN0KS4KPj4gLSBUaGF0IGRp
YWxvZyAodGhlIFNVQlNDUklCRSBkaWFsb2cpIGRvZXNuJ3QgZXhpc3QgaW4gQWxpY2UgYW55bW9y
ZSwgCj4+IHNvIEFsaWNlIHJlcGxpZXMgNDgxLgo+Pgo+PiBiKQo+PiAtIERpYWxvZyBiZXR3ZWVu
IEFsaWNlIGFuZCBCb2IgZW5kcyBiZWNhdXNlIEFsaWNlIHNlbmRzIGEgQllFLCBidXQgCj4+IGJl
Zm9yZSBBbGljZSByZWNlaXZlcyB0aGUgQllFIGFuZCB0aGUgZGlhbG9nIE5PVElGWSB1cGRhdGUs
IEJvYiBzZW5kcyAKPj4gYSBTVUJTQ1JJQkUgcmVmcmVzaCAoYW4gaW4tZGlhbG9nIHJlcXVlc3Qp
IGZvciB0aGF0IGRpYWxvZy4KPj4gLSBUaGlzIFNVQlNDUklCRSBhcnJpdmVzIHRvIEFsaWNlLCB0
aGUgU1VCU0NSSUJFIHJlcXVlc3QgZGlhbG9nIAo+PiBleGlzdHMgYnV0IHRoZSBkaWFsb2cgaW5k
aWNhdGVkIGluICJFdmVudCIgaGVhZGVyIGRvZXNuJ3QgZXhpc3QgYW55bW9yZS4KPj4gLSBBcyB0
aGUgYWJvdmUgZmxvdyBzdWdnZXN0cywgQWxpY2UgcmVwbGllcyA0ODEuCj4+Cj4+IEluIGJvdGgg
Y2FzZXMgYSkgYW5kIGIpLCBBbGljZSByZXBsaWVzIDQ4MSBidXQgdGhlIHNjZW5hcmlvIGlzIAo+
PiBjb21wbGV0ZWx5IGRpZmZlcmVudC4gVGhlIDQ4MSBpbiBhKSBtZWFucyB0aGF0IHRoZSBpbi1k
aWFsb2cgCj4+IFNVQlNDUklCRSBiZWxvbmdzIHRvIGEgbm9uIGV4aXN0aW5nIGRpYWxvZyBpbiBB
bGljZSwgd2hpbGUgdGhlIDQ4MSBpbiAKPj4gYikgbWVhbnMgdGhhdCBhIGRpYWxvZyBpbmRpY2F0
ZWQgaW4gdGhlIEV2ZW50IGhlYWRlciBkb2Vzbid0IGV4aXN0Lgo+PiBCdXQgdGhlcmUgaXMgbm8g
d2F5IGZvciBCb2IgdG8gcmVhbGl6ZSB3aGljaCBpcyB0aGUgY2FzZSBhKSBvciBiKS4KPj4KPj4K
Pj4gVGhlIG1haW4gcXVlc3Rpb24gaXM6IGlzIDQ4MSB0aGUgYXBwcm9pYXRlIChhbmQgdmFsaWQp
IHJlcGx5IGluIHRoZSAKPj4gYWJvdmUgZmxvdyAoY2FzZSBiKT8gSXMgNDgxIHJlYWxseSB2YWxp
ZCBhcyBhIHJlcGx5IGZvciBhbiBpbml0aWFsIAo+PiByZXF1ZXN0Pwo+Pgo+Pgo+Pgo+Pgo+IF9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4gU2lwIG1haWxp
bmcgbGlzdCAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zaXAKPiBUaGlz
IGxpc3QgaXMgZm9yIE5FVyBkZXZlbG9wbWVudCBvZiB0aGUgY29yZSBTSVAgUHJvdG9jb2wKPiBV
c2Ugc2lwLWltcGxlbWVudG9yc0Bjcy5jb2x1bWJpYS5lZHUgZm9yIHF1ZXN0aW9ucyBvbiBjdXJy
ZW50IHNpcAo+IFVzZSBzaXBwaW5nQGlldGYub3JnIGZvciBuZXcgZGV2ZWxvcG1lbnRzIG9uIHRo
ZSBhcHBsaWNhdGlvbiBvZiBzaXAKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fClNpcCBtYWlsaW5nIGxpc3QgIGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vc2lwClRoaXMgbGlzdCBpcyBmb3IgTkVXIGRldmVsb3BtZW50IG9mIHRoZSBj
b3JlIFNJUCBQcm90b2NvbApVc2Ugc2lwLWltcGxlbWVudG9yc0Bjcy5jb2x1bWJpYS5lZHUgZm9y
IHF1ZXN0aW9ucyBvbiBjdXJyZW50IHNpcApVc2Ugc2lwcGluZ0BpZXRmLm9yZyBmb3IgbmV3IGRl
dmVsb3BtZW50cyBvbiB0aGUgYXBwbGljYXRpb24gb2Ygc2lw


From sip-bounces@ietf.org  Thu Oct 30 16:10:32 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C7F9C28C191;
	Thu, 30 Oct 2008 16:10:32 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6DCCD28C1C1
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 16:10:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.257
X-Spam-Level: 
X-Spam-Status: No, score=-2.257 tagged_above=-999 required=5 tests=[AWL=0.342, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Z9P5xTHuebeB for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 16:10:30 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39])
	by core3.amsl.com (Postfix) with ESMTP id 27EA53A6B73
	for <sip@ietf.org>; Thu, 30 Oct 2008 16:10:30 -0700 (PDT)
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2])
	by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id m9UN9pWw025859;
	Thu, 30 Oct 2008 18:10:05 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by
	ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Oct 2008 18:10:01 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.28]) by
	DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 00:09:59 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 31 Oct 2008 00:09:57 +0100
Message-ID: <5D1A7985295922448D5550C94DE291800245C378@DEEXC1U01.de.lucent.com>
In-Reply-To: <81521DF0-2666-4500-BE62-412FBB6966A7@standardstrack.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Legacy Info Package Registration
Thread-Index: Ack6tdzDqTZCJfucTp2rgz2/yiHxhAALeSNA
References: <20081020231502.43DCA3A69EF@core3.amsl.com><48FDECB5.3030607@cisco.com>
	<81521DF0-2666-4500-BE62-412FBB6966A7@standardstrack.com>
From: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: "Eric Burger" <eburger@standardstrack.com>,
	"Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 30 Oct 2008 23:09:59.0510 (UTC)
	FILETIME=[A19C4F60:01C93AE4]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Legacy Info Package Registration
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

(As individual)

At the moment I think this draft should concentrate on the packages, and
interoperability with the legacy issues.

I don't think I want to identify (except by way of example for the
above) any of the legacy usages.

I do not have an objection to creating another draft that creates a
registry of legacy usages, and if that wants to list known ones then
fine. I have no objection if we do that now or later, but the main draft
would not be dependent on it.

I would note that if we do create a registry, then whether we need to
seed it or not depends on the registration criteria - if it is first
come first served, then anyone can register their own legacy usages
without waiting for an RFC to do it for them. 

At the moment I am also unsure what criteria we would use for identifing
a legacy usage, apart from some rather vague textual description. It
after all does not have a package name. 

So I'll accept either of these:

> [ ] No - please do not create an IANA registry
> 
> [ ] Punt - I may or may not want an IANA registry, but if we 
> do create one, do it in another draft

regards

Keith

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Eric Burger
> Sent: Thursday, October 30, 2008 4:14 PM
> To: Paul Kyzivat
> Cc: SIP IETF
> Subject: [Sip] Legacy Info Package Registration
> 
> We discussed creating a registry, and we discussed whether it 
> would be in this document.
> 
> On the one hand, the discussion was not conclusive.  On the 
> other, here are my reasons for not including it in the Info 
> Packages document:
> 
> 1. We go at lengths to say how to do Info Packages.  The last 
> thing we need to do is say, "by the way, it's not so bad if 
> you don't."
> 
> 2. People not involved today will look at such a registry 
> and, no matter how much doom and gloom wording we use, will 
> think it's OK to not use Info Packages.
> 
> 3. People will be confused, thinking Content-Type is 
> sufficient to identify an Info Package.  It is not.
> 
> 4. How would we possibly police the registry? If someone 
> comes to IANA to register a new MIME type do the klaxons 
> ring?  That would not be a good thing.
> 
> So, time for another poll:
> [ ] Yes - we really, really need an IANA registry of "legacy" 
> INFO usages, and we need it done in this draft
>      (NOTE: creating the IANA registry requires the seed 
> values, which means this draft will enumerate the
>       known legacy usages)
> 
> [ ] No, do not create an IANA registry, but please enumerate 
> known legacy usages in this draft
> 
> [ ] No - please do not create an IANA registry
> 
> [ ] Punt - I may or may not want an IANA registry, but if we 
> do create one, do it in another draft
> 
> [ ] Other: ________________________________
> 
> 
> 
> On Oct 21, 2008, at 10:52 AM, Paul Kyzivat wrote:
> 
> > Regarding registration if INFO packages - I thought we also 
> wanted to 
> > introduce a registry for legacy usages of INFO, to 
> encourage them to 
> > come out into the daylight. I guess maybe that would be a separate 
> > registry, since the key for it will have to be Content- Type. So it 
> > *could* be established from a different document. But I 
> think this is 
> > the likely place to do it, since its the place where all 
> the eyeballs 
> > will be. I think the rule for registering those needs to be 
> that one 
> > can only be registered if the Content-Type has not already been 
> > registered, and it was in *use* with INFO prior to this document 
> > becoming an RFC. (The registration itself could be done 
> later. I guess 
> > it would be the honor system.) Any usages being deployed after this 
> > becomes an RFC would be required to use the new mechanism.
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 30 16:11:28 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9501428C1F3;
	Thu, 30 Oct 2008 16:11:28 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 917A33A6943
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 16:11:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.288
X-Spam-Level: 
X-Spam-Status: No, score=-2.288 tagged_above=-999 required=5 tests=[AWL=0.011, 
	BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 533JpC1-BKSp for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 16:11:26 -0700 (PDT)
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171])
	by core3.amsl.com (Postfix) with ESMTP id 0A68628C1FA
	for <sip@ietf.org>; Thu, 30 Oct 2008 16:10:45 -0700 (PDT)
Received: by ug-out-1314.google.com with SMTP id b39so1092249ugd.15
	for <sip@ietf.org>; Thu, 30 Oct 2008 16:10:43 -0700 (PDT)
Received: by 10.210.130.14 with SMTP id c14mr12424275ebd.124.1225408243019;
	Thu, 30 Oct 2008 16:10:43 -0700 (PDT)
Received: from portatil.local (82.pool85-58-129.dynamic.orange.es
	[85.58.129.82])
	by mx.google.com with ESMTPS id z34sm2292023ikz.0.2008.10.30.16.10.41
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Thu, 30 Oct 2008 16:10:41 -0700 (PDT)
From: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
To: sip@ietf.org
Date: Fri, 31 Oct 2008 00:10:38 +0100
User-Agent: KMail/1.9.9
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<5BC604B4-17CA-4CC7-8476-1485A5A20FB8@softarmor.com>
	<200810310006.58854.ibc@aliax.net>
In-Reply-To: <200810310006.58854.ibc@aliax.net>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200810310010.38762.ibc@aliax.net>
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

El Viernes, 31 de Octubre de 2008, I=F1aki Baz Castillo escribi=F3:
> While your explanation makes sense, it seems to conclude that the simple
> mechanism described in DERIVE should not be considered due to some "exoti=
c"
> scenarios in which it could fail

Well, the possible scenarios in which it could fail are not so "exotic", so=
rry =

for that.

-- =

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


From sip-bounces@ietf.org  Thu Oct 30 16:50:32 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C0E9C3A6A69;
	Thu, 30 Oct 2008 16:50:32 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0E3F73A6A68
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 16:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.5
X-Spam-Level: 
X-Spam-Status: No, score=-6.5 tagged_above=-999 required=5 tests=[AWL=0.099,
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Uzy9YcLDBRXV for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 16:50:30 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id E04963A6905
	for <sip@ietf.org>; Thu, 30 Oct 2008 16:50:30 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,518,1220227200"; d="scan'208";a="185938539"
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 30 Oct 2008 23:50:29 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9UNoT2i031324; 
	Thu, 30 Oct 2008 16:50:29 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9UNoTRu022790;
	Thu, 30 Oct 2008 23:50:29 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Dean Willis'" <dean.willis@softarmor.com>,
	"'Jiri Kuthan'" <jiri@iptel.org>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com><490792EA.2020106@softarmor.com><033f01c9397b$860847a0$c3f0200a@cisco.com><200810292306.44911.ibc@aliax.net><000901c93a36$3d4755e0$c3f0200a@cisco.com>	<17345A0C-8BFD-4D0D-B597-ECA8801F72D5@softarmor.com>
	<5D1A7985295922448D5550C94DE291800245C0C7@DEEXC1U01.de.lucent.com>
	<490A0E7F.3010206@iptel.org>
	<5BC604B4-17CA-4CC7-8476-1485A5A20FB8@softarmor.com>
Date: Thu, 30 Oct 2008 16:50:29 -0700
Message-ID: <009c01c93aea$4a2ef740$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <5BC604B4-17CA-4CC7-8476-1485A5A20FB8@softarmor.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: Ack62aqG/YpjZmjSSmeqJCXGeyC3mAADzeoQ
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3609; t=1225410629;
	x=1226274629; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[Sip]=20Comment=20on=20DERIVE=20and=20B
	2BUAs |Sender:=20;
	bh=dGDZ1JI5BrTh/rkPj5iDlPzujgWKromMl5/7VnFcr+E=;
	b=DwwoxmnUTizvDlD9P9kHO1gsos0x4sAYVALUWfv36+47PWNT+DcWB1ObjA
	WmrQ6ueii7RR/LD7PL+7FvCVh3+hGJLboDC4gXazhbnQBV5ZaZiUAIiu93/z
	QCNbPpQA2t;
Authentication-Results: sj-dkim-2; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: sip@ietf.org, "'DRAGE, Keith \(Keith\)'" <drage@alcatel-lucent.com>
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

> On Oct 30, 2008, at 2:43 PM, Jiri Kuthan wrote:
> >
> > I'm wondering if other WG participants would agree with me that  
> > "verifying
> > who is sending me this SIP request is who he claims to be in the  
> > simplest
> > possible way (i.e., without other protocols and 
> > infrastructures) by reverse
> > lookup" would be an appropriate goal.
> 
> Leaving aside the question of whether the success of the DERIVE RRC  
> answer's the question you've asked above (I don't think it does; it  
> merely verifies that the a node reachable at the AOR to which the  
> request is attributed has particular knowledge of the SIP request in  
> question), let's ask if we understand the unintended consequences.
> 
> There are fundamental assumptions in this sort of RRC model that the  
> node initiating the dialog request is in fact reachable by some sort  
> of AOR, and that this is the AOR that will be presented in 
> the request as that of its originator. This is not universally true.

Agreed.

But in order for me to get a postmark that says "San Jose", I need
to drop my mail into a San Jose post office.  And if you see my package
arrive with my San Jose address, but you see a Wasila, Alaska postmark,
you might be more suspicious about it than usual.

> Envision a presence-enabled call controller (PECC) employed 
> by Alice.  
> Alice wants to call Bob, whenever Alice and Bob are both on-line.
> 
> So PECC subscribes to Alice and Bob.
> 
> Eventually Alice and BOb are both on-line, so PECC sets up the call.
> 
> What's in the From" going to Bob? It's probably Alice's AOR, as PECC  
> is working on her behalf, and there's some reason to think 
> that Bob is  
> willing to accept calls from Alice. But PECC cannot REGISTER 
> as Alice, for obvious reasons.
> 
> Bob uses DERIVE, and sends a SUBSCRIBE to Alice that references the  
> dialog that is between PECC and Bob.
> 
> Can Alice's UA respond appropriately? I think not.

You're right.

(I might wonder aloud how well all of SIP's features work with
3rd party call control.  But we know the answer is "not all".)

I will note that for RFC4474 to operate in that same scenario, 
PECC would need to be inside of Alice's domain (in order that 
Alice's domain creates the necessary RFC4474 signature over the 
[spoofed] INVITE emitted by PECC).

> There are other ways to construct the type of application I'm 
> talking about, that might work with DERIVE. Do we want to force 
> a redesign of SIP applications so that return-routability to 
> the originating AOR is required?
> This might not be a bad thing, but I think it is a very  
> primal thing, and is potentially quite disruptive to application  
> scenarios. That might be OK, but we need to understand the  
> consequences before we go down that road.

I'm just desiging in this email, but it may well be sufficient,
for the case you describe above (and maybe others?) if PECC were
to inform Alice of the impending automated call to Bob.  Alice
would probably want to know this, anyway.  Afterall, seeing or
hearing "Bob is online right now; initiating call" and seeing
or hearing call progress indications is more reasonable than
Alice suddenly hearing Bob's voice saying "Hi, Alice, it's good
you called me.  Let's talk about the weather."

Such a notification to Alice could be as straightforward as 
the PECC sending Alice a NOTIFY, so that when Alice receives
the RRC message (e.g., [INFO|SUBSCRIBE|OPTIONS]), she has the
necessary dialog information to respond correctly to the 
RRC.


-d

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


From sip-bounces@ietf.org  Thu Oct 30 16:57:05 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C51BE3A6A69;
	Thu, 30 Oct 2008 16:57:05 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 20BED3A6A68
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 16:57:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id uoT6-OYDnycs for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 16:57:03 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6])
	by core3.amsl.com (Postfix) with ESMTP id 06E523A68CC
	for <sip@ietf.org>; Thu, 30 Oct 2008 16:57:02 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com
	(216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.291.1;
	Thu, 30 Oct 2008 19:55:38 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with
	mapi; Thu, 30 Oct 2008 19:55:38 -0400
From: Bob Penfield <BPenfield@acmepacket.com>
To: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>, Eric Burger
	<eburger@standardstrack.com>, Paul Kyzivat <pkyzivat@cisco.com>
Date: Thu, 30 Oct 2008 19:55:38 -0400
Thread-Topic: [Sip] Legacy Info Package Registration
Thread-Index: Ack6tdzDqTZCJfucTp2rgz2/yiHxhAALeSNAAAHBTzA=
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC3129FE89AA8@mail>
References: <20081020231502.43DCA3A69EF@core3.amsl.com><48FDECB5.3030607@cisco.com>
	<81521DF0-2666-4500-BE62-412FBB6966A7@standardstrack.com>
	<5D1A7985295922448D5550C94DE291800245C378@DEEXC1U01.de.lucent.com>
In-Reply-To: <5D1A7985295922448D5550C94DE291800245C378@DEEXC1U01.de.lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Legacy Info Package Registration
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I'm think I agree with Keith.

How about:

 [X] No, do not create an IANA registry, but please enumerate
 known legacy usages in separate draft

cheers,
(-:bob

-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of DRAGE, Keith (Keith)
Sent: Thursday, October 30, 2008 7:10 PM
To: Eric Burger; Paul Kyzivat
Cc: SIP IETF
Subject: Re: [Sip] Legacy Info Package Registration

(As individual)

At the moment I think this draft should concentrate on the packages, and
interoperability with the legacy issues.

I don't think I want to identify (except by way of example for the
above) any of the legacy usages.

I do not have an objection to creating another draft that creates a
registry of legacy usages, and if that wants to list known ones then
fine. I have no objection if we do that now or later, but the main draft
would not be dependent on it.

I would note that if we do create a registry, then whether we need to
seed it or not depends on the registration criteria - if it is first
come first served, then anyone can register their own legacy usages
without waiting for an RFC to do it for them.

At the moment I am also unsure what criteria we would use for identifing
a legacy usage, apart from some rather vague textual description. It
after all does not have a package name.

So I'll accept either of these:

> [ ] No - please do not create an IANA registry
>
> [ ] Punt - I may or may not want an IANA registry, but if we
> do create one, do it in another draft

regards

Keith

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
> Behalf Of Eric Burger
> Sent: Thursday, October 30, 2008 4:14 PM
> To: Paul Kyzivat
> Cc: SIP IETF
> Subject: [Sip] Legacy Info Package Registration
>
> We discussed creating a registry, and we discussed whether it
> would be in this document.
>
> On the one hand, the discussion was not conclusive.  On the
> other, here are my reasons for not including it in the Info
> Packages document:
>
> 1. We go at lengths to say how to do Info Packages.  The last
> thing we need to do is say, "by the way, it's not so bad if
> you don't."
>
> 2. People not involved today will look at such a registry
> and, no matter how much doom and gloom wording we use, will
> think it's OK to not use Info Packages.
>
> 3. People will be confused, thinking Content-Type is
> sufficient to identify an Info Package.  It is not.
>
> 4. How would we possibly police the registry? If someone
> comes to IANA to register a new MIME type do the klaxons
> ring?  That would not be a good thing.
>
> So, time for another poll:
> [ ] Yes - we really, really need an IANA registry of "legacy"
> INFO usages, and we need it done in this draft
>      (NOTE: creating the IANA registry requires the seed
> values, which means this draft will enumerate the
>       known legacy usages)
>
> [ ] No, do not create an IANA registry, but please enumerate
> known legacy usages in this draft
>
> [ ] No - please do not create an IANA registry
>
> [ ] Punt - I may or may not want an IANA registry, but if we
> do create one, do it in another draft
>
> [ ] Other: ________________________________
>
>
>
> On Oct 21, 2008, at 10:52 AM, Paul Kyzivat wrote:
>
> > Regarding registration if INFO packages - I thought we also
> wanted to
> > introduce a registry for legacy usages of INFO, to
> encourage them to
> > come out into the daylight. I guess maybe that would be a separate
> > registry, since the key for it will have to be Content- Type. So it
> > *could* be established from a different document. But I
> think this is
> > the likely place to do it, since its the place where all
> the eyeballs
> > will be. I think the rule for registering those needs to be
> that one
> > can only be registered if the Content-Type has not already been
> > registered, and it was in *use* with INFO prior to this document
> > becoming an RFC. (The registration itself could be done
> later. I guess
> > it would be the honor system.) Any usages being deployed after this
> > becomes an RFC would be required to use the new mechanism.
>
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 30 17:36:52 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E41193A6B53;
	Thu, 30 Oct 2008 17:36:51 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A38843A6A34
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 17:36:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.539
X-Spam-Level: 
X-Spam-Status: No, score=-6.539 tagged_above=-999 required=5 tests=[AWL=0.060, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BzTZcaXM2jRA for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 17:36:49 -0700 (PDT)
Received: from ind-iport-1.cisco.com (ind-iport-1.cisco.com [64.104.129.195])
	by core3.amsl.com (Postfix) with ESMTP id 94BB13A6813
	for <SIP@ietf.org>; Thu, 30 Oct 2008 17:36:48 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,519,1220227200"; d="scan'208";a="32257880"
Received: from hkg-dkim-1.cisco.com ([10.75.231.161])
	by ind-iport-1.cisco.com with ESMTP; 31 Oct 2008 00:36:42 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94])
	by hkg-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9V0aePG006912; 
	Fri, 31 Oct 2008 08:36:40 +0800
Received: from xbh-hkg-411.apac.cisco.com (xbh-hkg-411.cisco.com
	[64.104.123.72])
	by hkg-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9V0abd0012891;
	Fri, 31 Oct 2008 00:36:39 GMT
Received: from xbh-rtp-211.amer.cisco.com ([64.102.31.102]) by
	xbh-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 08:36:06 +0800
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Oct 2008 20:35:46 -0400
Received: from [10.86.241.187] ([10.86.241.187]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Oct 2008 20:35:45 -0400
Message-ID: <490A52E2.9050504@cisco.com>
Date: Thu, 30 Oct 2008 20:35:46 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <322862FF-3683-465F-B1A0-8C619A5D60E1@standardstrack.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFDD@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF083CCFDD@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 31 Oct 2008 00:35:45.0547 (UTC)
	FILETIME=[9CE33DB0:01C93AF0]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4489; t=1225413400;
	x=1226277400; c=relaxed/simple; s=hkgdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Proposal=20for=20multiple=20INF
	O=20bodies=20in=20an=20INFO |Sender:=20;
	bh=Ed75DhlvgsRCXIsjPsoO5MCCZlBbDk01pKZeiZv8ypQ=;
	b=AD9Jsms+FgiNKcevzzXiKyBwnEb5lPOS6jrIBTFmhcudryM/XppuqRTvcJ
	wawWM1t989hzmXVJgGRZFy7yBL4WBriVU0t1SKccqH9MHtTf5/g45xsa4K5V
	X2Y+7/5mdwI7NCCh+iP+Hy7HoWVpZySTOt5n2FU/UFEAudqZybTUg=;
Authentication-Results: hkg-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/hkgdkim1002 verified; ); 
Cc: IETF SIP List <SIP@ietf.org>
Subject: Re: [Sip] Proposal for multiple INFO bodies in an INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

I am ok with either way.

I think using C-D follows the precedent of INVITE for finding "its body 
part" via C-D of "session".

	Thanks,
	Paul

Christer Holmberg wrote:
> Hi Erick,
>  
> I am not your suggestion of using CID for Info packages is what has been discussed (I may be wrong, of course).
>  
> I think what Paul was proposing was to have a Content-Disposition value indicating that a particular body shall be treated as in info package.
>  
> INFO .....
> To: ....
> From: ....
> Info-Package: foo
> Content-Type: application/foo
> Content-Dispotistion: info
> ...
> 
> <foo body>
> 
> 
> Multipart mixed example with indirect content:
> 
> INFO ....
> To: ....
> From: ....
> Info-Package: foo
> Content-Type: multipart/mixed;boundary="theboundary"
> ...
> 
> --theboundary
> Content-Type: application/mumble
> Content-Disposition: whatever
> 
> <mumble body>
> 
> --theboundary
> Content-Type: application/foo
> Content-Disposition: info
> 
> <foo body>
> 
> --theboundary--
> 
>  
>  
> Regards,
>  
> Christer
> 
> ________________________________
> 
> From: sip-bounces@ietf.org on behalf of Eric Burger
> Sent: Thu 30/10/2008 19:29
> To: IETF SIP List
> Subject: [Sip] Proposal for multiple INFO bodies in an INFO
> 
> 
> 
> Good thing I waited 10 days...
> 
> Initially, I was very swayed by the argument that things would be 
> much, much easier if we restricted an INFO request to a single Info-
> Package.
> 
> However, and especially as the last person to touch RFC 4483, I can 
> see the argument that *any* SIP message can end up with a multipart/
> mime body, even if you think you can limit it to just your stuff, 
> because the UA can always have a content indirection pointer in the 
> header pointing to a mime body part.
> 
> Therefore, even if we restrict an INFO request to carry a single Info-
> Package, we need a mechanism to uniquely identify and, at the SIP 
> header level, indicate which body part belongs to the package.
> 
> I would offer once we solve that, we also get multiple INFO request 
> bodies for free.
> 
> I would also offer that since INFO does not change SIP state, which 
> means there is not even a concept of a message succeeding but the INFO 
> body doing something that "fails", the objection that it would be hard 
> for a UA to report on one body "failing" with another body 
> "succeeding" is a non-issue.  Yes, this does mean that you cannot use 
> INFO to tunnel IP.  See RFC 3252 for more on this.  I do not see this 
> as a problem.
> 
> Therefore, on to the solution.  We use the MIME approach.  The body 
> parts get tagged with Content-IDs. The Info-Package has a parameter, 
> CID, which points to the body part.  The ONLY question I have is 
> whether we should simply mandate always having this parameter to make 
> the protocol and parser easier, but a small burden on UAC's that 
> really are only sending a single body.  Other than that, the mechanism 
> looks like:
> 
> INFO .....
> To: ....
> From: ....
> Info-Package: foo
> Content-Type: application/foo;cid=this
> Content-Id: this
> ...
> 
> <foo body>
> 
> 
> 
> Multipart mixed example with indirect content:
> 
> INFO ....
> To: ....
> From: ....
> Info-Package: foo;cid=abcd1234zz
> Mumble: <cid:abcd9999qq>
> Content-Type: multipart/mixed;boundary="theboundary"
> ...
> 
> --theboundary
> Content-Type: application/mumble
> Content-Id: abcd9999qq
> ...
> 
> <mumble stuff>
> 
> --theboundary
> Content-Type: application/foo
> Content-Id: abcd1234zz
> 
> <foo body>
> 
> --theboundary--
> 
> 
> 
> 
> Multiple Info Packages follow. Note that by using Content-Id, order is 
> irrelevant.
> 
> INFO ....
> To: ....
> From: ....
> Info-Package: foo;cid=abcd1234zz
> Info-Package: bar;cid=wxyz9876
> Content-Type: multipart/mixed;boundary="theboundary"
> ...
> 
> --theboundary
> Content-Type: application/bar
> Content-Id: wxyz9876
> ...
> 
> <bar stuff>
> 
> --theboundary
> Content-Type: application/foo
> Content-Id: abcd1234zz
> 
> <foo body>
> 
> --theboundary-- 
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 30 17:43:27 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 401AB3A6B71;
	Thu, 30 Oct 2008 17:43:27 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7767128C163
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 17:43:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.549
X-Spam-Level: 
X-Spam-Status: No, score=-6.549 tagged_above=-999 required=5 tests=[AWL=0.050, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8RauICDGqLtj for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 17:43:25 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id DD5753A6B6E
	for <sip@ietf.org>; Thu, 30 Oct 2008 17:43:23 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,519,1220227200"; d="scan'208";a="26260588"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 31 Oct 2008 00:43:22 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9V0hMqu010530; 
	Thu, 30 Oct 2008 20:43:22 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9V0hJ9o026686;
	Fri, 31 Oct 2008 00:43:22 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Oct 2008 20:43:20 -0400
Received: from [10.86.241.187] ([10.86.241.187]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Oct 2008 20:43:19 -0400
Message-ID: <490A54A8.7070405@cisco.com>
Date: Thu, 30 Oct 2008 20:43:20 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
References: <20081020231502.43DCA3A69EF@core3.amsl.com><48FDECB5.3030607@cisco.com>
	<81521DF0-2666-4500-BE62-412FBB6966A7@standardstrack.com>
	<5D1A7985295922448D5550C94DE291800245C378@DEEXC1U01.de.lucent.com>
In-Reply-To: <5D1A7985295922448D5550C94DE291800245C378@DEEXC1U01.de.lucent.com>
X-OriginalArrivalTime: 31 Oct 2008 00:43:19.0894 (UTC)
	FILETIME=[ABB31760:01C93AF1]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=563; t=1225413802; x=1226277802;
	c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Legacy=20Info=20Package=20Regis
	tration |Sender:=20
	|To:=20=22DRAGE,=20Keith=20\(Keith\)=22=20<drage@alcatel-lu
	cent.com>; bh=RglnFKvx3dlfxGjkRwH5RPwL1bv6fnRnm8B0MKisCaw=;
	b=s+YRbkXmdas3t9iQTHVC3qhMkFigjIE+d9aXUodBAsDv0E4LGpO6v+u9yM
	ihcadiv0oPIeOfaxWgm2DINy0IZQPIHrkG9JleRF5lrqM1tbDlYlw9xOiRHo
	iV1xi/BmzK;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Legacy Info Package Registration
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



DRAGE, Keith (Keith) wrote:

> At the moment I am also unsure what criteria we would use for identifing
> a legacy usage, apart from some rather vague textual description. It
> after all does not have a package name. 

With legacy usage, the only distinguishing characteristic that I am 
aware has ever been used is Content-Type. So I think the registry has to 
be based on Content-Type, probably on a FCFS basis. (Though perhaps 
there might be need of an appeals process if there are conflicting 
usages. But I doubt we will find that.)

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


From sip-bounces@ietf.org  Thu Oct 30 17:45:48 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3F4C93A6B72;
	Thu, 30 Oct 2008 17:45:48 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1A0393A6B72
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 17:45:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Ec9+V5zymdRj for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 17:45:45 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 31FA63A69EC
	for <sip@ietf.org>; Thu, 30 Oct 2008 17:45:45 -0700 (PDT)
Received: from c-75-68-119-237.hsd1.nh.comcast.net ([75.68.119.237]:63891
	helo=[192.168.15.102])
	by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1KvbPX-0003No-Av; Thu, 30 Oct 2008 10:34:19 -0700
Message-Id: <317CC43C-9055-4601-8B4F-43E90865B338@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: Jeroen van Bemmel <jbemmel@zonnet.nl>
In-Reply-To: <4903081E.4090002@zonnet.nl>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 30 Oct 2008 13:09:46 -0400
References: <4903081E.4090002@zonnet.nl>
X-Mailer: Apple Mail (2.929.2)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: IETF SIP List <sip@ietf.org>
Subject: Re: [Sip] info-event: syntax simplification
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1108397677=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--===============1108397677==
Content-Type: multipart/signed; boundary=Apple-Mail-76-118767637; micalg=sha1; protocol="application/pkcs7-signature"


--Apple-Mail-76-118767637
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

I would offer the syntax looks simpler, but the parser gets more  
complicated.  The parser now needs to track state and set tables with  
direction, instead of simple set tables.

Moreover, once one lists media types in the negotiation (a subject of  
a coming thread), we are talking about potentially adding hundreds of  
mandatory bytes to the message, whereas the simplification proposed  
below saves at most 30 bytes.

Therefore, I would offer we keep the ABNF as it is.


On Oct 25, 2008, at 7:50 AM, Jeroen van Bemmel wrote:

> Current draft (with Recv fix):
>
> Info-Package        =  "Info-Package" HCOLON Info-package-type
>  Send-Info           =  "Send-Info" HCOLON Info-package-type
>                         *( COMMA Info-package-type )
>  Recv-Info           =  "Recv-Info" HCOLON Info-package-type
>                         *( COMMA Info-package-type )
>  Info-package-type   =  Info-package-name *( "." Info-package-param)
>  Info-package-name   =  token-nodot
>  token-nodot         =  1*( alphanum / "-"  / "!" / "%" / "*"
>                             / "_" / "+" / "`" / "'" / "~" ) ;rfc3265
>  Info-package-param  =  generic-param  ;this doesn't work due to dot!
>
>
> From an implementation perspective, this is unnecessarily complex  
> and verbose: if a UA can both send and receive the same INFO  
> package, it must list it twice.
>
> As an alternative, I would propose something similar to SDP media  
> streams:
>
> Supported-Info      = "Supported-Info" HCOLON Info-package-type  
> *(COMMA Info-package-type)
> Info-package-type   = token *( SEMI Info-package-param )
> Info-package-param  = "sendonly" / "recvonly" / generic-param ; only  
> one of "sendonly" or "recvonly" may be present
>
> Usage would be to include 1 "Supported-Info" header in requests/ 
> responses, instead of 2 separate "Send-Info" / "Recv-Info". By  
> default a package is "sendrecv" (i.e. UA may send it, and can  
> receive it), unless overridden by "sendonly" or "recvonly" flags
>
> Regards,
> Jeroen
>
>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip


--Apple-Mail-76-118767637
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGPTCCBjkw
ggUhoAMCAQICEC+VK1RLWxrF8KJZDR9k8p8wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYTAlVT
MQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VS
VFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQD
Ey1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwwHhcNMDgwODEz
MDAwMDAwWhcNMDkwODEzMjM1OTU5WjCB4TE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsg
LSBQRVJTT05BIE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9m
IHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDMg
Q29tb2RvIExpbWl0ZWQxFDASBgNVBAMTC0VyaWMgQnVyZ2VyMSkwJwYJKoZIhvcNAQkBFhplYnVy
Z2VyQHN0YW5kYXJkc3RyYWNrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMTF
RRoA4LgOACMFph0aomRC/UpqoA5C/d6DUTOvTMrYSEqkjwnU4zxDtBcHlcB4AxKAov00MYsUvEU4
loz7BHjfDjv76AIkcwu33VYQbzGmarVnyaXsVb6f/cyRL3fPT0VOVO2tQAEEgwg//CX0jN8Kn2jH
uXD/HEvko7cmpL3Pwevf3+DwB61v7ca79PpEZfn/WhaqRKA4uVNPj/JbieeaLo2v/0RJzrEElZK0
pHCqxiD3mQ8ossPkA9fUCSxLlbdMcPU3be5x8vt8Q8mYTXF5Z3d9RZmYrmNkvTQtdzVpfYWr/hgV
Xqm9tByOOAR+hoN3FKbubR/OrAHL9yDAd4sCAwEAAaOCAhwwggIYMB8GA1UdIwQYMBaAFImCZ33E
nSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBRDWgutb7b8R/L7G3Y3D+molAA3VzAOBgNVHQ8BAf8E
BAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJ
YIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEW
HWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMIGlBgNVHR8EgZ0wgZowTKBKoEiGRmh0dHA6
Ly9jcmwuY29tb2RvY2EuY29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRF
bWFpbC5jcmwwSqBIoEaGRGh0dHA6Ly9jcmwuY29tb2RvLm5ldC9VVE4tVVNFUkZpcnN0LUNsaWVu
dEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMGwGCCsGAQUFBwEBBGAwXjA2BggrBgEFBQcwAoYq
aHR0cDovL2NydC5jb21vZG9jYS5jb20vVVROQUFBQ2xpZW50Q0EuY3J0MCQGCCsGAQUFBzABhhho
dHRwOi8vb2NzcC5jb21vZG9jYS5jb20wJQYDVR0RBB4wHIEaZWJ1cmdlckBzdGFuZGFyZHN0cmFj
ay5jb20wDQYJKoZIhvcNAQEFBQADggEBAGeBR7NPCvrY3GQoIi49JOuciatY2r4st905Jw1etp6J
umFFWlaCBl11tFSclk/3S45B+lUv3SEvG4CEjUByPScprVmCqHR+y8BAQaB/CV+N1y14x3MbhJ+Z
8XDGKeUXuuyGd9w0l3/t/QPid6TRXQjQFrLPFs1IALuNpNiFMHEF/xFbMG1Z2vznR/gSPlePekoZ
TqcExIDBNZTBebpZqwAXzPpedNNOclbMLFLWDMOAozVRpkfjI0eiFsk8SF1Ho1Gb9Bx8DeG4peE2
KRVOR9FFnZZgBpFjXYRcglsMOSKCY8HgE+NGvbbqbrMoBV/BlYyxRXwfti71RL9Zs2Cq1eQxggP8
MIID+AIBATCBwzCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExh
a2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8v
d3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkNH2TynzAJBgUrDgMCGgUAoIICDTAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wODEwMzAxNzA5NDdaMCMGCSqGSIb3
DQEJBDEWBBSjMoa6SX3cLPLA8JhajWLzHdwgWjCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD
VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU
aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2
MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv
lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN
H2TynzANBgkqhkiG9w0BAQEFAASCAQAwn7Bh3Z9mTkCHVvTLpoGN/XmL8L8ykE70WnNUKF4dP/jW
+kUiZxNdt1w5E84AQvUhENfGKthWcp0V385PU6eWQtuHsqET+B96ExqR+z16i+Kxun7RL4hCViQU
vaDegedMKfIjLLoyJYGDdAjLqvsvkkipQJT7ke48zeXc1zXqPwRmaE2yzXTbAtGvIwvBDF2E1VBP
bpUJcAXzoAX3/atLduhYKGvTIZyYYEOJPeQ8MhMj7mDE1NBKytKjXhBZ1Zdd11+1EJa3XhrOvK5r
PH2N7ovPVRw3FTtQN1s3fkGkHEbXHkOiWOzxFArmXfxQ1k2e6QLMPZEomciTivJWtVfjAAAAAAAA

--Apple-Mail-76-118767637--

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

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


From sip-bounces@ietf.org  Thu Oct 30 18:20:40 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 36BC23A6A69;
	Thu, 30 Oct 2008 18:20:40 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8010A28C150
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 18:20:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id L4VnVBe8-H5a for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 18:20:37 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 994E53A6B53
	for <sip@ietf.org>; Thu, 30 Oct 2008 18:20:37 -0700 (PDT)
Received: from c-75-68-119-237.hsd1.nh.comcast.net ([75.68.119.237]:63891
	helo=[192.168.15.102])
	by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1KvbPV-0003No-B1; Thu, 30 Oct 2008 10:34:17 -0700
Message-Id: <9F7BFBEE-A96A-4E33-B3DB-9074DE2FE579@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF05C0F906@esealmw113.eemea.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 30 Oct 2008 12:52:40 -0400
References: <48FDEAD8.8010803@cisco.com>	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>	<4901BA73.1010700@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>	<4901C2B1.1050209@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>	<4901D025.6060302@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>	<490239C8.3020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>	<4902467E.3010603@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFBA@esealmw113.eemea.ericsson.se>	<4905B23F.10609@cisco.com><CA9998CD4A020D418654FCDEF4E707DF089F589E@esealmw113.eemea.ericsson
	.se> <49	05CAE2.9020808@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8FF@esealmw113.eemea.ericss
	on.se> <49060DD4.7070804@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F906@esealmw113.eemea.ericsson.se>
X-Mailer: Apple Mail (2.929.2)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: SIP IETF <sip@ietf.org>
Subject: [Sip] Info Package Versioning
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1925053884=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--===============1925053884==
Content-Type: multipart/signed; boundary=Apple-Mail-73-117741069; micalg=sha1; protocol="application/pkcs7-signature"


--Apple-Mail-73-117741069
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Channeling Keith here: is there a real use case for package versioning?

I cannot imagine backwards-compatible packages. Once one starts  
changing the stuff in an INFO package, it is a different package. That  
is, rather than

    Info-Package: foo-package;version=1
    Info-Package: foo-package;version=2

You, in reality have:

    Info-Package: foo-package
    Info-Package: something-like-foo-but-not-really-foo-anymore

This is more especially so when one considers there is no possibility  
of negotiating package versions, whereas there is a possibility of  
negotiating different packages.

For the one instance one could come up with in theory for needing  
versioning, remember one does get to have an arbitrary parameter:

    Info-Package: foo-package               /* Version 1 */
    Info-Package: foo-package;bar        /* Version 2 */


Is this latter mechanism sufficient?

Yet another poll:

[ ] We must have abstract versioning as part of the Info Framework  
document

[ ] We do not need to have abstract versioning, as it does not do  
anything for anyone

[ ] We do not need abstract versioning, but it would be worthwhile  
including some text,
     like what is above, to show people how to do it.

[ ] Something else? _____________________________________



On Oct 27, 2008, at 4:48 PM, Christer Holmberg wrote:

> [snip]
>> The wording could be better. There are no explicit IANA  
>> considerations
> about registering an INFO package. Its just implied here. Its a little
> confusing here what is intended to be part of the
>> *definition* of a new package vs. what is intended to be in the  
>> content
> of a particular package instance in an INFO message.
>
> We do need to have a section on what needs to be part of an info  
> package
> definition. The mime type is one thing, for sure.
>
> I guess we should also look at what/if we can re-use from SIP events.
>
> We also need to decide whether info packages should have a version
> number system. From experience I think that would be very useful.
>
> Info-Package: foo-package;version=1
>
> ...or something like that.
[snip]


--Apple-Mail-73-117741069
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGPTCCBjkw
ggUhoAMCAQICEC+VK1RLWxrF8KJZDR9k8p8wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYTAlVT
MQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VS
VFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQD
Ey1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwwHhcNMDgwODEz
MDAwMDAwWhcNMDkwODEzMjM1OTU5WjCB4TE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsg
LSBQRVJTT05BIE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9m
IHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDMg
Q29tb2RvIExpbWl0ZWQxFDASBgNVBAMTC0VyaWMgQnVyZ2VyMSkwJwYJKoZIhvcNAQkBFhplYnVy
Z2VyQHN0YW5kYXJkc3RyYWNrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMTF
RRoA4LgOACMFph0aomRC/UpqoA5C/d6DUTOvTMrYSEqkjwnU4zxDtBcHlcB4AxKAov00MYsUvEU4
loz7BHjfDjv76AIkcwu33VYQbzGmarVnyaXsVb6f/cyRL3fPT0VOVO2tQAEEgwg//CX0jN8Kn2jH
uXD/HEvko7cmpL3Pwevf3+DwB61v7ca79PpEZfn/WhaqRKA4uVNPj/JbieeaLo2v/0RJzrEElZK0
pHCqxiD3mQ8ossPkA9fUCSxLlbdMcPU3be5x8vt8Q8mYTXF5Z3d9RZmYrmNkvTQtdzVpfYWr/hgV
Xqm9tByOOAR+hoN3FKbubR/OrAHL9yDAd4sCAwEAAaOCAhwwggIYMB8GA1UdIwQYMBaAFImCZ33E
nSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBRDWgutb7b8R/L7G3Y3D+molAA3VzAOBgNVHQ8BAf8E
BAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJ
YIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEW
HWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMIGlBgNVHR8EgZ0wgZowTKBKoEiGRmh0dHA6
Ly9jcmwuY29tb2RvY2EuY29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRF
bWFpbC5jcmwwSqBIoEaGRGh0dHA6Ly9jcmwuY29tb2RvLm5ldC9VVE4tVVNFUkZpcnN0LUNsaWVu
dEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMGwGCCsGAQUFBwEBBGAwXjA2BggrBgEFBQcwAoYq
aHR0cDovL2NydC5jb21vZG9jYS5jb20vVVROQUFBQ2xpZW50Q0EuY3J0MCQGCCsGAQUFBzABhhho
dHRwOi8vb2NzcC5jb21vZG9jYS5jb20wJQYDVR0RBB4wHIEaZWJ1cmdlckBzdGFuZGFyZHN0cmFj
ay5jb20wDQYJKoZIhvcNAQEFBQADggEBAGeBR7NPCvrY3GQoIi49JOuciatY2r4st905Jw1etp6J
umFFWlaCBl11tFSclk/3S45B+lUv3SEvG4CEjUByPScprVmCqHR+y8BAQaB/CV+N1y14x3MbhJ+Z
8XDGKeUXuuyGd9w0l3/t/QPid6TRXQjQFrLPFs1IALuNpNiFMHEF/xFbMG1Z2vznR/gSPlePekoZ
TqcExIDBNZTBebpZqwAXzPpedNNOclbMLFLWDMOAozVRpkfjI0eiFsk8SF1Ho1Gb9Bx8DeG4peE2
KRVOR9FFnZZgBpFjXYRcglsMOSKCY8HgE+NGvbbqbrMoBV/BlYyxRXwfti71RL9Zs2Cq1eQxggP8
MIID+AIBATCBwzCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExh
a2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8v
d3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkNH2TynzAJBgUrDgMCGgUAoIICDTAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wODEwMzAxNjUyNDBaMCMGCSqGSIb3
DQEJBDEWBBQ17U2YoHeSB6PRJi8XjNErmwBZTzCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD
VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU
aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2
MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv
lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN
H2TynzANBgkqhkiG9w0BAQEFAASCAQAczLAPNA8hOG80onRVzAeL3swLDWZReSVJ+OqnxYE/ZduB
YWIszfqgII6wLhIXSVUPoBYvXiNb9HtLBeO+qvozHxLmFFukQuizwXWqyJO8HfspK79jher/K6fn
hBACM12q/tL1WLD19Xfa2SHbwYw15Tug4X7DcvyoEbfkQ5XeuNtrs1DuSXnSq8Sn/WoI6r1L1Gxx
JzT37H46Sz6+6nHGlHWpLCsmNrLvsgwXfU/fakoi6R0+4bV2EOKIKdOK4jAv7WdCp88liakjbtTV
0dgOuTN/uJAss+OTNe7iBgjf4vfy3IQkJHtH/caPH094kjA8hROuty0iCLhTjfeXWP+VAAAAAAAA

--Apple-Mail-73-117741069--

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

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


From sip-bounces@ietf.org  Thu Oct 30 18:56:23 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A38ED3A6A34;
	Thu, 30 Oct 2008 18:56:23 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 488B63A6B13
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 18:56:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 2WNeLZnr++l8 for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 18:56:21 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 86DD73A6A34
	for <SIP@ietf.org>; Thu, 30 Oct 2008 18:56:21 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,519,1220227200"; d="scan'208";a="98395932"
Received: from sj-dkim-7.cisco.com ([171.68.10.88])
	by sj-iport-1.cisco.com with ESMTP; 31 Oct 2008 01:56:20 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-7.cisco.com (8.12.11/8.12.11) with ESMTP id m9V1uKR7016622; 
	Thu, 30 Oct 2008 18:56:20 -0700
Received: from [10.21.76.130] ([10.21.76.130])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9V1uKJP009702;
	Fri, 31 Oct 2008 01:56:20 GMT
Message-ID: <490A65C4.1090109@cisco.com>
Date: Thu, 30 Oct 2008 18:56:20 -0700
From: Anders Kristensen <andersk@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Eric Burger <eburger@standardstrack.com>
References: <322862FF-3683-465F-B1A0-8C619A5D60E1@standardstrack.com>
In-Reply-To: <322862FF-3683-465F-B1A0-8C619A5D60E1@standardstrack.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=673; t=1225418180; x=1226282180;
	c=relaxed/simple; s=sjdkim7002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=andersk@cisco.com;
	z=From:=20Anders=20Kristensen=20<andersk@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Proposal=20for=20multiple=20INF
	O=20bodies=20in=20an=20INFO |Sender:=20;
	bh=tEGKD8h2SGf+BSHjczKxwnBDaiPTzzEKW5+ejJYgbho=;
	b=JM1N6GW/xsaq2dcBUm5J3meCaQ9baqylWymfhxhP06Or2bVVSY5XZRYxQp
	/zT3O7mruZf9iloBakJWNhbutzA01+GH5Gj7ZHF03n8EZq+olkzwSlK2g34S
	GBiXAz0J99;
Authentication-Results: sj-dkim-7; header.From=andersk@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim7002 verified; ); 
Cc: IETF SIP List <SIP@ietf.org>
Subject: Re: [Sip] Proposal for multiple INFO bodies in an INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org



Eric Burger wrote:
...
> 
> I would also offer that since INFO does not change SIP state, which 
> means there is not even a concept of a message succeeding but the INFO 
> body doing something that "fails", the objection that it would be hard 
> for a UA to report on one body "failing" with another body "succeeding" 
> is a non-issue.  Yes, this does mean that you cannot use INFO to tunnel 
> IP.  See RFC 3252 for more on this.  I do not see this as a problem.

Not sure I follow this. If an INFO carries bodies for info packages A 
and B and the one for A is fine but the one for B is malformed, then is 
the INFO rejected or not?

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


From sip-bounces@ietf.org  Thu Oct 30 19:16:40 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 74E023A6AF4;
	Thu, 30 Oct 2008 19:16:40 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6CBFB28C21B
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 19:15:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nLXZHHsz6YZs for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 19:15:09 -0700 (PDT)
Received: from smtp08.bis.na.blackberry.com (smtp08.bis.na.blackberry.com
	[216.9.248.55]) by core3.amsl.com (Postfix) with ESMTP id 854E228C20C
	for <SIP@ietf.org>; Thu, 30 Oct 2008 19:15:09 -0700 (PDT)
Received: from bda381.bisx.prod.on.blackberry (bda381.bisx.prod.on.blackberry
	[172.20.234.81])
	by srs.bis.na.blackberry.com (8.13.7 TEAMON/8.13.7) with ESMTP id
	m9V2F7d8023793; Fri, 31 Oct 2008 02:15:07 GMT
Received: from bda381.bisx.prod.on.blackberry (localhost.localdomain
	[127.0.0.1])
	by bda381.bisx.prod.on.blackberry (8.13.7 TEAMON/8.13.7) with ESMTP id
	m9V2F6pW024869; Fri, 31 Oct 2008 02:15:06 GMT
X-rim-org-msg-ref-id: 1756371787
Message-ID: <1756371787-1225419306-cardhu_decombobulator_blackberry.rim.net-534504805-@bxe155.bisx.prod.on.blackberry>
X-Priority: Normal
Sensitivity: Normal
Importance: Normal
To: "Anders Kristensen" <andersk@cisco.com>
From: "eburger" <eburger@standardstrack.com>
Date: Fri, 31 Oct 2008 02:15:05 +0000
MIME-Version: 1.0
Cc: IETF SIP List <SIP@ietf.org>
Subject: Re: [Sip] Proposal for multiple INFO bodies in an INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: eburger@standardstrack.com
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

INFO is rejected. You probably shouldn't have any application state semantics that would need SIP to transport an error. QED
------Original Message------
From: Anders Kristensen
To: Eric Burger
Cc: IETF SIP List
Subject: Re: [Sip] Proposal for multiple INFO bodies in an INFO
Sent: Oct 30, 2008 9:56 PM



Eric Burger wrote:
...
> 
> I would also offer that since INFO does not change SIP state, which 
> means there is not even a concept of a message succeeding but the INFO 
> body doing something that "fails", the objection that it would be hard 
> for a UA to report on one body "failing" with another body "succeeding" 
> is a non-issue.  Yes, this does mean that you cannot use INFO to tunnel 
> IP.  See RFC 3252 for more on this.  I do not see this as a problem.

Not sure I follow this. If an INFO carries bodies for info packages A 
and B and the one for A is fine but the one for B is malformed, then is 
the INFO rejected or not?

Thanks,
Anders


--
Eric Burger

Sent from my mobile device; sorry if terse. All mobile users need lemonade.  See <http://www.standardstrack.com/ietf/lemonade> for more information.
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 30 19:42:37 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9211C3A6B53;
	Thu, 30 Oct 2008 19:42:37 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 48EED28C150
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 19:42:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Ix2ZfrtTmxh6 for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 19:42:35 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id EFD733A69EC
	for <sip@ietf.org>; Thu, 30 Oct 2008 19:42:33 -0700 (PDT)
Received: from c-75-68-119-237.hsd1.nh.comcast.net ([75.68.119.237]:63891
	helo=[192.168.15.102])
	by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1KvbPW-0003No-MX; Thu, 30 Oct 2008 10:34:18 -0700
Message-Id: <975C30B3-A80B-4A6D-9892-7946404F89B4@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF0889EAE5@esealmw113.eemea.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Thu, 30 Oct 2008 13:07:18 -0400
References: <48FDEC6B.8090006@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF0889EAE5@esealmw113.eemea.ericsson.se>
X-Mailer: Apple Mail (2.929.2)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: SIP IETF <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: package negotiation
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1766303590=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--===============1766303590==
Content-Type: multipart/signed; boundary=Apple-Mail-75-118619103; micalg=sha1; protocol="application/pkcs7-signature"


--Apple-Mail-75-118619103
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

I would offer the likelihood of a UAC only half implementing Info  
Packages is about 00.000% (five zeros, anyone?).  I cannot imagine  
anyone expending the effort to implement Info Packages but not use them.

If the UAS is a legacy device, the UAC will detect it from the absence  
of Send/Recv-Info headers.

If the UAC is a legacy device, the UAS will detect it from the absence  
of Send/Recv-Info headers.

Since I will soon make it clear a conforming UAC can send a legacy  
INFO, half negotiation is a non-issue.

For example, let's say it's two weeks from now and I've published the  
update to RFC 3398 to use Info Packages. Either the implementor will  
implement the full ISUP package, or not. It just does not make sense  
to do half the job, since 90% of the job gets done when one does the  
first half. If one side does not do Info Packages, then presumably, in  
the interests of legacy interoperability (and often because the code  
is already written), the device falls back to legacy INFO/RFC 3398.

3pcc? By the time you can list one header (Send or Recv), you can list  
both.

Therefore, I would offer it is an implementation failure to list only  
a Send-Info or Recv-Info header.

On Oct 22, 2008, at 5:36 AM, Christer Holmberg wrote:

>
> Hi,
>
>> General issues with the negotiation mechanism:
>>
>> What happens if the initial INVITE by a UAC includes only Send-Info  
>> or
> Recv-Info? Does that indicate a "half-legacy" device??? Or does it  
> delay
> negotiation for one but not the other? Or does
>> the presence of one mean the absence of the other is equivalent to an
> empty one?
>>
>> As I think about it, I don't think its really necessary to treat the
> absence of these headers as meaning "legacy". Treating the absence of
> these headers as equivalent to their presence without
>> any packages is sufficient to get the proper legacy behavior. The
> tricky part is figuring out out when their absence *doesn't* mean  
> that,
> which is significant only in the non-legacy case. In
>> particular, when they aren't present in INVITE it means deferral of  
>> the
> "offer" to the UAS. And possibly absence in an UPDATE means "don't
> renegotiate"???
>
> I don't think the presence, or absence, of the S/R-Info headers should
> in any way be connected to legacy in any way. A UA can be legacy no
> matter if the headers are present, or not present, but that is all  
> done
> based on "configuration", as described in the draft.
>
> So, if a UAC only included Send-Info, it means that it only supports
> sending of Info packages. Then, it may, or may not, also support  
> legacy
> INFO usages, but that is completely separated.
>
>
>> I'm confused by the three way negotiation of info packages in
> INVITE/2xx/ACK. Its allowed when the Send-Info/Recv-Info are in the
> INVITE, but not when they are deferred to the INVITE response,
>> or when they are conveyed in UPDATE and its response. If the three  
>> way
> handshake is needed to seal the deal, then those other options  
> should be
> off the table. But the "deferred offer" of these
>> is really needed, so it can't be off the table. Or is this just an
> extra benefit that can be exploited when possible?
>>
>> Also, I don't see any provision for additional round(s) of  
>> negotiation
> before 2xx via PRACK and UPDATE, though there is provision for
> additional "half-negotiations" via provisional responses
>> and the final response. Given the parallels with O/A, I'd prefer to  
>> see
> them more aligned in this regard, though I can be talked out of that
> with a good argument.
>
> I agree (I think :). The negotiation whould be 2-way. Then, based on
> what the UAC gets from the UAS, it may send a PRACK/UPDATE/re-INVITE
> with a new set of supported Info packages, but that is a new 2-way
> negotiation transaction.
>
>
>> I'd also like to take advantage of the lessons that have been learned
> with O/A and nail down more of the semantics now. One issue that leaps
> to mind in that regard is what happens if we start
>> to negotiate info packages in a reINVITE and then the reINVITE fails?
>
> That's a good point.
>
> I think we should use the same rule as for offer/answer. Because,  
> assume
> I send you a new set of packages in a re-INVITE, and you send me  
> back a
> set in a 18x. Then we may start using info packages based on that
> negotiation long before the re-INVITE is rejected.
>
>> IMO what is needed is a state model for this stuff, added to the  
>> state
> for an invite-dialog-usage. This state should determine which packages
> may be sent, and which should be received without
>> error. We should be very clear about exactly which events cause  
>> changes
> to this state.
>>
>> Even then there are race conditions that need to be clarified. For
>> instance: Suppose, as a result of an INVITE/1xx exchange between  
>> Alice
> and Bob, that packages P & Q are allowed to be sent from Alice to Bob.
>> Alice then sends an INFO with package Q, and at the same time Bob  
>> sends
> a 2xx that only allows the receipt of package P. Then Bob receives the
> INFO with package Q. What should happen?
>>
>> Another issue is that if the Send-Info/Recv-Info contents change in
> subsequent 1xx responses to the same INVITE, the UAS has no guarantee
> that they are received. So any reduction in what can be
>> received cannot be counted upon until the 2xx/ACK.
>
> True. But, I wonder whether this will really be a real-life problem.
>
> And, we could a response code (4xx Info package not supported),  
> which is
> used by the UAS if it receives an info package which it doesn't  
> support.
> Then the UAC knows.
>
> Regards.
>
> Christer
>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip


--Apple-Mail-75-118619103
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGPTCCBjkw
ggUhoAMCAQICEC+VK1RLWxrF8KJZDR9k8p8wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYTAlVT
MQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VS
VFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQD
Ey1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwwHhcNMDgwODEz
MDAwMDAwWhcNMDkwODEzMjM1OTU5WjCB4TE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsg
LSBQRVJTT05BIE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9m
IHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDMg
Q29tb2RvIExpbWl0ZWQxFDASBgNVBAMTC0VyaWMgQnVyZ2VyMSkwJwYJKoZIhvcNAQkBFhplYnVy
Z2VyQHN0YW5kYXJkc3RyYWNrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMTF
RRoA4LgOACMFph0aomRC/UpqoA5C/d6DUTOvTMrYSEqkjwnU4zxDtBcHlcB4AxKAov00MYsUvEU4
loz7BHjfDjv76AIkcwu33VYQbzGmarVnyaXsVb6f/cyRL3fPT0VOVO2tQAEEgwg//CX0jN8Kn2jH
uXD/HEvko7cmpL3Pwevf3+DwB61v7ca79PpEZfn/WhaqRKA4uVNPj/JbieeaLo2v/0RJzrEElZK0
pHCqxiD3mQ8ossPkA9fUCSxLlbdMcPU3be5x8vt8Q8mYTXF5Z3d9RZmYrmNkvTQtdzVpfYWr/hgV
Xqm9tByOOAR+hoN3FKbubR/OrAHL9yDAd4sCAwEAAaOCAhwwggIYMB8GA1UdIwQYMBaAFImCZ33E
nSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBRDWgutb7b8R/L7G3Y3D+molAA3VzAOBgNVHQ8BAf8E
BAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJ
YIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEW
HWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMIGlBgNVHR8EgZ0wgZowTKBKoEiGRmh0dHA6
Ly9jcmwuY29tb2RvY2EuY29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRF
bWFpbC5jcmwwSqBIoEaGRGh0dHA6Ly9jcmwuY29tb2RvLm5ldC9VVE4tVVNFUkZpcnN0LUNsaWVu
dEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMGwGCCsGAQUFBwEBBGAwXjA2BggrBgEFBQcwAoYq
aHR0cDovL2NydC5jb21vZG9jYS5jb20vVVROQUFBQ2xpZW50Q0EuY3J0MCQGCCsGAQUFBzABhhho
dHRwOi8vb2NzcC5jb21vZG9jYS5jb20wJQYDVR0RBB4wHIEaZWJ1cmdlckBzdGFuZGFyZHN0cmFj
ay5jb20wDQYJKoZIhvcNAQEFBQADggEBAGeBR7NPCvrY3GQoIi49JOuciatY2r4st905Jw1etp6J
umFFWlaCBl11tFSclk/3S45B+lUv3SEvG4CEjUByPScprVmCqHR+y8BAQaB/CV+N1y14x3MbhJ+Z
8XDGKeUXuuyGd9w0l3/t/QPid6TRXQjQFrLPFs1IALuNpNiFMHEF/xFbMG1Z2vznR/gSPlePekoZ
TqcExIDBNZTBebpZqwAXzPpedNNOclbMLFLWDMOAozVRpkfjI0eiFsk8SF1Ho1Gb9Bx8DeG4peE2
KRVOR9FFnZZgBpFjXYRcglsMOSKCY8HgE+NGvbbqbrMoBV/BlYyxRXwfti71RL9Zs2Cq1eQxggP8
MIID+AIBATCBwzCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExh
a2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8v
d3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkNH2TynzAJBgUrDgMCGgUAoIICDTAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wODEwMzAxNzA3MThaMCMGCSqGSIb3
DQEJBDEWBBT2/0r+cAYIbGfJihVmq1zs7JLZGTCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD
VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU
aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2
MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv
lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN
H2TynzANBgkqhkiG9w0BAQEFAASCAQAh/+zoACy1QnpQoHJWbp9kgRVeoHbWhQoqf286PG0m5ysP
is/StxtoaVqg/RT8+uCHxFnbhQFX+rxhahCZP9nz0JkJQctmGzYH3yUyCEa7u5uBvHSTr8sQZIoA
XRURT6VmKnGIsi5hZZTI1A71PuLk0c+1jY/wn+s4xAsFGtJ6hms0J/RfEY3siIWQbs2H/k3d6ghg
B/n+zbLZ2zwrPSDlsM2Y89ZvPn8Ht0FniysfSW0ZIQCA7Y/l2fCpUWqLAieEV9Uo/33+08fPdBUs
HBRYywGDoKs8K1DW8MZ+CUMmPdO2DL1sf6/I020apM11ikB/VXNVEMSxGZbBD7NccDuRAAAAAAAA

--Apple-Mail-75-118619103--

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

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


From sip-bounces@ietf.org  Thu Oct 30 21:04:33 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A7D223A6BAB;
	Thu, 30 Oct 2008 21:04:33 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5756F3A6BAF
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 21:02:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, J_CHICKENPOX_34=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4Z2Dg4Xx8sRc for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 21:02:44 -0700 (PDT)
Received: from mail119.messagelabs.com (mail119.messagelabs.com
	[216.82.245.51]) by core3.amsl.com (Postfix) with SMTP id 5B59A3A6BA9
	for <sip@ietf.org>; Thu, 30 Oct 2008 21:02:44 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: nedved.yang@motorola.com
X-Msg-Ref: server-2.tower-119.messagelabs.com!1225425762!29228808!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [136.182.1.13]
Received: (qmail 27784 invoked from network); 31 Oct 2008 04:02:42 -0000
Received: from unknown (HELO motgate3.mot.com) (136.182.1.13)
	by server-2.tower-119.messagelabs.com with SMTP;
	31 Oct 2008 04:02:42 -0000
Received: from il27exr04.cig.mot.com ([10.17.196.73])
	by motgate3.mot.com (8.12.11/Motorola) with ESMTP id m9V42e76017727
	for <sip@ietf.org>; Thu, 30 Oct 2008 21:02:42 -0700 (MST)
Received: from az10vts04.mot.com (il27vts04.cig.mot.com [10.17.196.88])
	by il27exr04.cig.mot.com (8.13.1/Vontu) with SMTP id m9V42erh023526
	for <sip@ietf.org>; Thu, 30 Oct 2008 23:02:40 -0500 (CDT)
Received: from ZMY16EXM65.ds.mot.com (zmy16exm65.ap.mot.com [10.179.4.25])
	by il27exr04.cig.mot.com (8.13.1/8.13.0) with ESMTP id m9V42cPZ023522
	for <sip@ietf.org>; Thu, 30 Oct 2008 23:02:39 -0500 (CDT)
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 31 Oct 2008 12:02:33 +0800
Message-ID: <26CE93408156DB4F94B954E3D93ACE5904E3DC88@ZMY16EXM65.ds.mot.com>
In-Reply-To: <mailman.0.1225425511.6276.sip@ietf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Questions regarding P_ASSOCIATED_URL
Thread-Index: Ack7DPLwk+OkDc79QqaPWO9Pk5J/fgAACBmA
References: <mailman.0.1225425511.6276.sip@ietf.org>
From: "Yang Nedved-FDB473" <nedved.yang@motorola.com>
To: <sip@ietf.org>
X-CFilter-Loop: Reflected
Subject: [Sip] Questions regarding P_ASSOCIATED_URL
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Hi all,

I hv a question regarding P_ASSOCIATED_HEADER,
 
If I register a public user identity, for example , bob @ mot.net,  then
when the response 200 ok comes, in P_ASSOCIATED_HEADER, it has:
 
bob_sky@mot.net;bob@mot.net.  so here default URL is bob_sky@mot.net...
if I subscribe the reg event of it...will the incoming notify be the
state change of bob or bob_sky or both? 

(here it is assume we follow TS24_229, it says, the default public user
identify (as one of the associated url)must be registered. (Page 52) )


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


From sip-bounces@ietf.org  Thu Oct 30 21:45:32 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 793863A6359;
	Thu, 30 Oct 2008 21:45:32 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7B87A3A6359
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 21:45:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.556
X-Spam-Level: 
X-Spam-Status: No, score=-6.556 tagged_above=-999 required=5 tests=[AWL=0.043, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4sSsrcSVwESJ for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 21:45:16 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id E1A923A6A82
	for <sip@ietf.org>; Thu, 30 Oct 2008 21:45:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,520,1220227200"; d="scan'208";a="26307451"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 31 Oct 2008 04:45:04 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9V4j4EG001001; 
	Fri, 31 Oct 2008 00:45:04 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9V4j4B8016391;
	Fri, 31 Oct 2008 04:45:04 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 00:45:03 -0400
Received: from [10.86.250.64] ([10.86.250.64]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 00:45:03 -0400
Message-ID: <490A8D4F.7030509@cisco.com>
Date: Fri, 31 Oct 2008 00:45:03 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Eric Burger <eburger@standardstrack.com>
References: <48FDEAD8.8010803@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>	<4901BA73.1010700@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>	<4901C2B1.1050209@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>	<4901D025.6060302@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>	<490239C8.3020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>	<4902467E.3010603@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFBA@esealmw113.eemea.ericsson.se>	<4905B23F.10609@cisco.com><CA9998CD4A020D418654FCDEF4E707DF089F589E@esealmw113.eemea.ericsson	.se>
	<49	05CAE2.9020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF05C0F8FF@esealmw113.eemea.ericss	on.se>
	<49060DD4.7070804@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF05C0F906@esealmw113.eemea.ericsson.se>
	<9F7BFBEE-A96A-4E33-B3DB-9074DE2FE579@standardstrack.com>
In-Reply-To: <9F7BFBEE-A96A-4E33-B3DB-9074DE2FE579@standardstrack.com>
X-OriginalArrivalTime: 31 Oct 2008 04:45:03.0549 (UTC)
	FILETIME=[708D36D0:01C93B13]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=421; t=1225428304; x=1226292304;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Info=20Package=20Versioning
	|Sender:=20
	|To:=20Eric=20Burger=20<eburger@standardstrack.com>;
	bh=EZ2fJNdRkHpPeTGfOsqjHOifQsLWdB1J5lbVTSWJRXM=;
	b=XIsXhwAnl4cRryrV144CJr9b0izBfkkUAMp9a/utCXAvYLhaHVUFUe9Bl8
	U+uNVSYvjfjTtZ883ktW2taEUza3bAINGAJwzzFF8rCAcsRsmr9CnadaPzfi
	Dn1/w9evc/;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Info Package Versioning
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

> Yet another poll:
> 
> [ ] We must have abstract versioning as part of the Info Framework document
> 
> [ ] We do not need to have abstract versioning, as it does not do 
> anything for anyone
> 
> [x] We do not need abstract versioning, but it would be worthwhile 
> including some text,
>     like what is above, to show people how to do it.
> 
> [ ] Something else? _____________________________________
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Thu Oct 30 23:31:29 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0B41F3A6804;
	Thu, 30 Oct 2008 23:31:29 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A34BB3A67CC
	for <sip@core3.amsl.com>; Thu, 30 Oct 2008 23:31:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Rky37vWfaxsH for <sip@core3.amsl.com>;
	Thu, 30 Oct 2008 23:31:27 -0700 (PDT)
Received: from taimen.tutpro.com (harjus.tutpro.com [192.98.100.3])
	by core3.amsl.com (Postfix) with ESMTP id CCB453A657C
	for <sip@ietf.org>; Thu, 30 Oct 2008 23:31:26 -0700 (PDT)
Received: by taimen.tutpro.com (Postfix, from userid 1000)
	id 8D2A433A725; Fri, 31 Oct 2008 08:31:22 +0200 (EET)
MIME-Version: 1.0
Message-ID: <18698.42554.506756.292138@harjus.tutpro.com>
Date: Fri, 31 Oct 2008 08:31:22 +0200
To: "Elwell, John" <john.elwell@siemens.com>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D001383219@GBNTHT12009MSX.gb002.siemens.net>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>
	<200810261145.19745.ibc@aliax.net>
	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
	<084c01c938a0$a41ff390$c3f0200a@cisco.com>
	<cc1f582e0810280444y42b8f723w938004e902fb1180@mail.gmail.com>
	<032301c93978$6b249c70$c3f0200a@cisco.com>
	<618e24240810290415i7ede4601tf2fd78aaed755445@mail.gmail.com>
	<007b01c939f6$6f33e5e0$24726b80@cisco.com>
	<0D5F89FAC29E2C41B98A6A762007F5D001383219@GBNTHT12009MSX.gb002.siemens.net>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: sip@ietf.org, Dan Wing <dwing@cisco.com>
Subject: Re: [Sip] submission of a new I-D: "Dialog
 Event	foRIdentityVErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Elwell, John writes:

 > > I support draft-kuthan-sip-derive-00, and hope the WG can devote
 > > time and energy to improving and standardizing it to work well
 > > across a variety of networks.
 > [JRE] I agree. This must include networks that contain B2BUAs/SBCs.

i strongly disagree.  b2bua is just an ua.  if you you build or deploy
such boxes, it is your headache, not sip wg's.  it is enough that this
work is based on rfc3261 components.

-- juha


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


From sip-bounces@ietf.org  Fri Oct 31 00:12:00 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2FCC73A67FD;
	Fri, 31 Oct 2008 00:12:00 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CCF8B3A67D4
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 00:11:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.507
X-Spam-Level: 
X-Spam-Status: No, score=-6.507 tagged_above=-999 required=5 tests=[AWL=0.092, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8YaDtVNgCbeZ for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 00:11:57 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id C0E7B3A67FD
	for <sip@ietf.org>; Fri, 31 Oct 2008 00:11:57 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,520,1220227200"; d="scan'208";a="186116017"
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 31 Oct 2008 07:11:56 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m9V7BuBM016002; 
	Fri, 31 Oct 2008 00:11:56 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m9V7Bu5Q017439;
	Fri, 31 Oct 2008 07:11:56 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Dean Willis'" <dean.willis@softarmor.com>,
	"'Ben Campbell'" <ben@estacado.net>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com><0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net><490792EA.2020106@softarmor.com><033f01c9397b$860847a0$c3f0200a@cisco.com><36E83843-775F-4317-BB0F-746E55194BFD@softarmor.com><1A770AC3-26C6-4D16-86A2-35533896F3C0@estacado.net>
	<CB5ABE64-B8E6-4FEF-B56E-9D68E253B689@softarmor.com>
Date: Fri, 31 Oct 2008 00:11:56 -0700
Message-ID: <00a501c93b27$f5b198b0$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <CB5ABE64-B8E6-4FEF-B56E-9D68E253B689@softarmor.com>
Thread-Index: Ack62g4Qy3EnGJatSpa2OiWMWqazqAATLiCg
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1019; t=1225437116;
	x=1226301116; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20[Sip]=20Comment=20on=20DERIVE=20and=20B
	2BUAs |Sender:=20;
	bh=Qrwm1RCiuJMooAeQyjHgxYU2MX+ialsB4SUfL2ORWF8=;
	b=n42xut88LXiXCwnXAKDPggUYAOQyY3Iz7uJoLnLdp9pDMio67/0kEpWBcV
	j6p8MYM28aQfaXe644Gy0ohMkcdf72P6AOTD4BeeYtt7N9kdccydwKyn0gwg
	q7pakO9WRd;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
Cc: 'Sip List' <sip@ietf.org>
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


> Which is why identity is always transitive in nature . . .

The post office provides reliable forward routing, even 
across service providers (countries).  So do ISPs.  And 
the PSTN.

In all those cases, the only thing the recipient knows 
is the last hop:  the mail delivery person, their local
Internet access provider, or their local phone company
said "here is your [package | packet | phone call]".

If you want to verify its claimed "From:", a technology
appropirate to that communication mechanism is necessary:
A wet signature (post office), a certificate (ISPs), or 
the other person's voice (PSTN).

SIP provides reliable forward routing, too.  I don't
see a consensus forming that we want to utilize SIP's
reliable forward routing to build a verification system.
That is a shame, because the SIP working group's 
unwillingness to build a verification system for SIP will 
keep SIP locked inside of small networks instead of 
allowing SIP to grow and to run on the Internet.

-d

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


From sip-bounces@ietf.org  Fri Oct 31 00:34:22 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E81813A67FD;
	Fri, 31 Oct 2008 00:34:21 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CCEC13A6879
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 00:34:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Usz58GmIIGg8 for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 00:34:20 -0700 (PDT)
Received: from cluster-f.mailcontrol.com (cluster-f.mailcontrol.com
	[85.119.2.190]) by core3.amsl.com (Postfix) with ESMTP id B7B763A67F0
	for <sip@ietf.org>; Fri, 31 Oct 2008 00:34:19 -0700 (PDT)
Received: from rly03f.srv.mailcontrol.com (localhost.localdomain [127.0.0.1])
	by rly03f.srv.mailcontrol.com (MailControl) with ESMTP id
	m9V7YGFk001946 for <sip@ietf.org>; Fri, 31 Oct 2008 07:34:16 GMT
Received: from submission.mailcontrol.com (submission.mailcontrol.com
	[86.111.216.190])
	by rly03f.srv.mailcontrol.com (MailControl) id m9V7Xw5U030420
	for sip@ietf.org; Fri, 31 Oct 2008 07:33:58 GMT
Received: from exsmtp02.nasstar-t1.net (exsmtp02.nasstar-t1.net
	[89.28.233.152]) by rly03f-eth0.srv.mailcontrol.com (envelope-sender
	attila.sipos@vegastream.com) (MIMEDefang) with ESMTP id
	m9V7XrYM030094; Fri, 31 Oct 2008 07:33:58 +0000 (GMT)
Received: from EXVS02.nasstar-t1.net ([10.2.10.106]) by
	exsmtp02.nasstar-t1.net with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 07:35:52 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 31 Oct 2008 07:33:52 -0000
Message-ID: <680808427CF931459462C3D78CB5EC60038B6296@EXVS02.nasstar-t1.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: B2B-UA's provide an unsolveable identity problem (was RE: [Sip]
	submission of a new I-D: "Dialog Event	foRIdentityVErification")
Thread-Index: Ack7Is0pSB88yMJ/RrSjESLUT19SBgABGWwg
From: "Attila Sipos" <attila.sipos@vegastream.com>
To: "Juha Heinanen" <jh@tutpro.com>, "Elwell, John" <john.elwell@siemens.com>
X-OriginalArrivalTime: 31 Oct 2008 07:35:52.0738 (UTC)
	FILETIME=[4D8B5820:01C93B2B]
X-Scanned-By: MailControl A-08-50-15 (www.mailcontrol.com) on 10.70.1.113
Cc: sip@ietf.org, Dan Wing <dwing@cisco.com>
Subject: [Sip] B2B-UA's provide an unsolveable identity problem (was RE:
	submission of a new I-D: "Dialog Event	foRIdentityVErification")
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

>>i strongly disagree.  b2bua is just an ua.  if you you build or deploy
>>such boxes, it is your headache, not sip wg's.

I agree with Juha here.

Every attempt at fixing identity problems (and they have been clever
solutions) has been hindered with the "but it won't work with B2BUAs"
argument.

The problem is not "it won't work with B2BUAs" - the  problem is that
B2BUA identity and security problems are unsolveable anyway. A B2BUA
cannot be forced to do anything because even if you said "it must do
this and that", a B2BUA can do what it wants anyway (I'm sure we've all
seen this).  Even if B2BUAs agreed to do certain things, one would
always enf up with something else that gets B2B'ed.

It is no different to trying to solve the problem of 2 telephones taped
together.

You can only trust things up to a certain boundary.  And the boundaries
of SIP are the UAs.  The best that SIP can do is to control what happens
between a UA and another UA (and proxies in between) and that's it.

Regards,

Attila


 

-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Juha Heinanen
Sent: 31 October 2008 06:31
To: Elwell, John
Cc: sip@ietf.org; Dan Wing
Subject: Re: [Sip] submission of a new I-D: "Dialog Event
foRIdentityVErification"

Elwell, John writes:

 > > I support draft-kuthan-sip-derive-00, and hope the WG can devote  >
> time and energy to improving and standardizing it to work well  > >
across a variety of networks.
 > [JRE] I agree. This must include networks that contain B2BUAs/SBCs.

i strongly disagree.  b2bua is just an ua.  if you you build or deploy
such boxes, it is your headache, not sip wg's.  it is enough that this
work is based on rfc3261 components.

-- juha


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


From sip-bounces@ietf.org  Fri Oct 31 02:16:01 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F3B563A6BC7;
	Fri, 31 Oct 2008 02:16:00 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 73EC43A6B79
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 02:15:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.385
X-Spam-Level: 
X-Spam-Status: No, score=-0.385 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3,
	MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id aGIUKep3MRWg for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 02:15:57 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232])
	by core3.amsl.com (Postfix) with ESMTP id 3055728C273
	for <sip@ietf.org>; Fri, 31 Oct 2008 02:15:43 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so1076774rvf.49
	for <sip@ietf.org>; Fri, 31 Oct 2008 02:15:41 -0700 (PDT)
Received: by 10.141.5.3 with SMTP id h3mr6492401rvi.138.1225444541776;
	Fri, 31 Oct 2008 02:15:41 -0700 (PDT)
Received: by 10.141.41.1 with HTTP; Fri, 31 Oct 2008 02:15:41 -0700 (PDT)
Message-ID: <cc1f582e0810310215x7c259014rb8e570564168f04b@mail.gmail.com>
Date: Fri, 31 Oct 2008 10:15:41 +0100
From: "=?UTF-8?Q?I=C3=B1aki_Baz_Castillo?=" <ibc@aliax.net>
In-Reply-To: <18698.42554.506756.292138@harjus.tutpro.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<200810261145.19745.ibc@aliax.net>
	<57762491-BE4C-4763-9312-09335B1D7C0C@softarmor.com>
	<084c01c938a0$a41ff390$c3f0200a@cisco.com>
	<cc1f582e0810280444y42b8f723w938004e902fb1180@mail.gmail.com>
	<032301c93978$6b249c70$c3f0200a@cisco.com>
	<618e24240810290415i7ede4601tf2fd78aaed755445@mail.gmail.com>
	<007b01c939f6$6f33e5e0$24726b80@cisco.com>
	<0D5F89FAC29E2C41B98A6A762007F5D001383219@GBNTHT12009MSX.gb002.siemens.net>
	<18698.42554.506756.292138@harjus.tutpro.com>
Cc: sip@ietf.org, "Elwell, John" <john.elwell@siemens.com>,
	Dan Wing <dwing@cisco.com>
Subject: Re: [Sip] submission of a new I-D: "Dialog Event
	foRIdentityVErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

MjAwOC8xMC8zMSBKdWhhIEhlaW5hbmVuIDxqaEB0dXRwcm8uY29tPjoKPiBFbHdlbGwsIEpvaG4g
d3JpdGVzOgo+Cj4gID4gPiBJIHN1cHBvcnQgZHJhZnQta3V0aGFuLXNpcC1kZXJpdmUtMDAsIGFu
ZCBob3BlIHRoZSBXRyBjYW4gZGV2b3RlCj4gID4gPiB0aW1lIGFuZCBlbmVyZ3kgdG8gaW1wcm92
aW5nIGFuZCBzdGFuZGFyZGl6aW5nIGl0IHRvIHdvcmsgd2VsbAo+ICA+ID4gYWNyb3NzIGEgdmFy
aWV0eSBvZiBuZXR3b3Jrcy4KPiAgPiBbSlJFXSBJIGFncmVlLiBUaGlzIG11c3QgaW5jbHVkZSBu
ZXR3b3JrcyB0aGF0IGNvbnRhaW4gQjJCVUFzL1NCQ3MuCj4KPiBpIHN0cm9uZ2x5IGRpc2FncmVl
LiAgYjJidWEgaXMganVzdCBhbiB1YS4gIGlmIHlvdSB5b3UgYnVpbGQgb3IgZGVwbG95Cj4gc3Vj
aCBib3hlcywgaXQgaXMgeW91ciBoZWFkYWNoZSwgbm90IHNpcCB3ZydzLiAgaXQgaXMgZW5vdWdo
IHRoYXQgdGhpcwo+IHdvcmsgaXMgYmFzZWQgb24gcmZjMzI2MSBjb21wb25lbnRzLgoKSSBhZ3Jl
ZS4gSWYgYSBCMkJVQSBpcyBjYXBhYmxlIG9mIHNlbmRpbmcgcmVxdWVzdHMgd2l0aCBhIHNwZWNp
ZmljCkZyb20gaXQncyBiZWNvbWVzIGluIGZhY3QgYW4gVUEgcmVzcG9uc2libGUgZm9yIHRoYXQg
QW9SIGluIHRoZSBGcm9tLApzbyBpdCBzaG91bGQgYmUgY2FwYWJsZSBvZiBoYW5kbGUgaW5jb21p
bmcgU1VCU0NSSUJFIGZvciB0aGF0IEFvUi4KClRoZSBtb3N0IHByb2JsZW1hdGljIGNhc2UgY291
bGQgYmUgdGhlIGZvbGxvd2luZywgaW4gd2hpY2ggdGhlCm91dGJvdW5kIHByb3h5IFByb3h5IHJl
c3BvbnNpYmxlIGZvciBkb21haW4ub3JnIGZvcndhcmRzIHRoZSByZXF1ZXN0CnRvIGEgQjJCVUEg
YnV0IGF0IHRoZSBzYW1lIHRpbWUgdGhpcyBwcm94eSBpcyB0aGUgcmVzb2x1dGlvbiAoUkZDMzI2
MykKZm9yIGRvbWFpbi5vcmcsIHNvIGFjdHMgYWxzbyBhcyBpbmJvdW5kIHByb3h5LiBJbiB0aGlz
IGNhc2UKYm9iQGRvbWFpbi5vcmcgd2lsbCBrbm93IG5vdGhpbmcgYWJvdXQgdGhlIGRpYWxvZyBk
YXRhIHJlY2VpdmVkIGluIHRoZQpTVUJTQ1JJQkUuCgogIGJvYkBkb21haW4ub3JnICAgLS0tLSAg
UHJveHkgKGRvbWFpbi5vcmcpICAtLS0tICBCMkJVQSAtLS0tICBhbGljZUBvdGhlci5jb20KICAg
ICAgICAgICBJTlZJVEUgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLT4KICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIElOVklURSAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tPgoK
CiAgICAgIElOVklURSAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tPgoKPC0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSBTVUJTQ1JJQkUKICAgICAgICAgICAgIDwt
LS0tLS0tLS0tLS0tLS0tLS0tLS0gU1VCU0NSSUJFCgoKQnV0LCBob3cgbXVjaCBjb21tb24gaXMg
dGhpcyBzY2VuYXJpbz8gSG93ZXZlciB0aGVyZSBpcyBhIHNvbHV0aW9uOgoKVGhlcmUgYXJlIHR3
byBkaWFsb2dzIG5vdzoKMSkgVUEgYm9iQGRvbWFpbi5vcmcgPC0tLS0tPiBCMkJVQQoyKSBCMkJV
QSBib2JAZG9tYWluLm9yZyA8LS0tLT4gYWxpY2VAb3RoZXIuY29tCgpTbyBjbGVhcmx5IGFsaWNl
IG11c3QgdmVyaWZ5IHRoZSBkaWFsb2cgd2l0aCBCMkJVQSwgc28gdGhlIFNVQlNDUklCRQptdXN0
IGFycml2ZSB0byBCMkJVQS4gSW4gb3JkZXIgdG8gZ2V0IGl0LCBQcm94eSAoZG9tYWluLm9yZykg
Y291bGQKZm9yd2FyZCB0aGUgU1VCU0NSSUJFIHRvIEIyQlVBIHdoaWNoIHdpbGwgbWF0Y2ggdGhl
IHNwZWNpZmllZCBkaWFsb2cKYW5kIHJlcGx5IDIwMCBPSy4gUHJveHkgd291bGQgZGVjaWRlIHRv
IGZvcndhcmQgdGhpcyBTVUJTQ1JJQkUgdG8KQjJCVUEgdXBvbiB0aGUgcHJlc2VuY2Ugb2YgYSAi
RXZlbnQ6IGRpYWxvZztjYWxsLWlkPXh4eCx0by10YWc9eHh4IgpoZWFkZXIuCgoKLS0gCknDsWFr
aSBCYXogQ2FzdGlsbG8KPGliY0BhbGlheC5uZXQ+Cl9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fClNpcCBtYWlsaW5nIGxpc3QgIGh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vc2lwClRoaXMgbGlzdCBpcyBmb3IgTkVXIGRldmVsb3BtZW50
IG9mIHRoZSBjb3JlIFNJUCBQcm90b2NvbApVc2Ugc2lwLWltcGxlbWVudG9yc0Bjcy5jb2x1bWJp
YS5lZHUgZm9yIHF1ZXN0aW9ucyBvbiBjdXJyZW50IHNpcApVc2Ugc2lwcGluZ0BpZXRmLm9yZyBm
b3IgbmV3IGRldmVsb3BtZW50cyBvbiB0aGUgYXBwbGljYXRpb24gb2Ygc2lw


From sip-bounces@ietf.org  Fri Oct 31 02:20:18 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4AD8B3A6BBF;
	Fri, 31 Oct 2008 02:20:18 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 673C93A688C
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 02:20:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level: 
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id s8qGqQ-pgzlD for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 02:20:15 -0700 (PDT)
Received: from gateway13.websitewelcome.com (gateway13.websitewelcome.com
	[67.18.68.4]) by core3.amsl.com (Postfix) with SMTP id 907383A682B
	for <sip@ietf.org>; Fri, 31 Oct 2008 02:20:15 -0700 (PDT)
Received: (qmail 22461 invoked from network); 31 Oct 2008 09:31:05 -0000
Received: from gator465.hostgator.com (69.56.174.130)
	by gateway13.websitewelcome.com with SMTP; 31 Oct 2008 09:31:05 -0000
Received: from nttfba2-052.246.ne.jp ([61.206.225.52]:54085
	helo=[192.168.1.27])
	by gator465.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.69) (envelope-from <shida@ntt-at.com>)
	id 1KvqAt-0000hv-GG; Fri, 31 Oct 2008 04:20:11 -0500
Message-Id: <433AEBD3-1D7C-4161-93F4-388B4924ECA0@ntt-at.com>
From: Shida Schubert <shida@ntt-at.com>
To: Jonathan Rosenberg <jdrosen@cisco.com>
In-Reply-To: <20081027043001.656543A6781@core3.amsl.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 31 Oct 2008 18:19:57 +0900
References: <20081027043001.656543A6781@core3.amsl.com>
X-Mailer: Apple Mail (2.929.2)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator465.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ntt-at.com
Cc: "sip@ietf.org List" <sip@ietf.org>
Subject: Re: [Sip] I-D Action:draft-rosenberg-sip-target-uri-delivery-00.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Jonathan;

  Thanks for writing up the draft.

  There was a use-case for freephone number mentioned in section 2.7 of
loose-route draft which no longer exists in this draft.

  I do recall that in section 2.7 of loose-route you expressed that  
freephone
number is just another form of alias, so I am assuming that is the  
reason
you removed the text OR was there any technical reason why you removed
the use-case?

  If there is no technical reason behind removing the text, could you
add its use for freephone number as a use-case either as a separate
sub-section or as part of alias use-case..

  Thanks & Regards
   Shida

On 27-Oct-08, at 1:30 PM, Internet-Drafts@ietf.org wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts  
> directories.
>
> 	Title           : Delivery of Request-URI Targets to User Agents
> 	Author(s)       : J. Rosenberg
> 	Filename        : draft-rosenberg-sip-target-uri-delivery-00.txt
> 	Pages           : 12
> 	Date            : 2008-10-26
>
> When a Session Initiation Protocol (SIP) proxy receives a request
> targeted at a URI identifying a user or resource it is responsible
> for, the proxy translates the URI to a registered contact URI of an
> agent representing that user or resource.  In the process, the
> original URI is removed from the request.  Numerous use cases have
> arisen which require this information to be delivered to the user
> agent.  This document describes these use cases and defines an
> extension to the History-Info header field which allows it to be used
> to support those cases.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-rosenberg-sip-target-uri-delivery-00.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> <mime-attachment>_______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

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


From sip-bounces@ietf.org  Fri Oct 31 03:30:43 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 991723A6B75;
	Fri, 31 Oct 2008 03:30:43 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 450DC3A6B75
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 03:30:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id V6tp6x4i8lJr for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 03:30:41 -0700 (PDT)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30])
	by core3.amsl.com (Postfix) with ESMTP id DF7EC3A6B55
	for <sip@ietf.org>; Fri, 31 Oct 2008 03:30:40 -0700 (PDT)
Received: by yw-out-2324.google.com with SMTP id 3so474370ywj.49
	for <sip@ietf.org>; Fri, 31 Oct 2008 03:30:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=s7Eigvrm1trfRBw5WCaZu0VYXJu02xGAe+jJIPTo3ZE=;
	b=gWtfvbDucGO3V3nUTEDjW/ok7ttZoJYNJS7Ok2PMkIYzVO5EYGsuRwc5ySkXEAUK8H
	yeYnXxuMM2ODRVUelBvNiYQmQHaVxr7zKc5xnYhqFZVL3729t98Vw3tL8dbv+BP9URNx
	FZ1ndVB0FxonfGMxrsNBLb+ZPffjQvLd2oQOk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=D0n1TVWy1DNtD5uoeHSiDeJhw2LBOIvZwMubCxGHsmCu3XeEccTQN2e3cpaO677v9P
	yfFy5uDCFcnXbR1ICn8CM4VyQwfGXACZ8t1VrpVK00+swb+RYum0qmWl+FILxWiZWz5k
	hDBWPTKTtYLwwdoPgeLOi0D0DsOTMrst21PUo=
Received: by 10.90.69.7 with SMTP id r7mr9871921aga.102.1225449007273;
	Fri, 31 Oct 2008 03:30:07 -0700 (PDT)
Received: by 10.90.114.2 with HTTP; Fri, 31 Oct 2008 03:30:07 -0700 (PDT)
Message-ID: <618e24240810310330h765b06bele08cd9cef8de2de9@mail.gmail.com>
Date: Fri, 31 Oct 2008 11:30:07 +0100
From: "=?UTF-8?Q?Victor_Pascual_=C3=81vila?=" <victor.pascual.avila@gmail.com>
To: sip@ietf.org
In-Reply-To: <680808427CF931459462C3D78CB5EC60038B6296@EXVS02.nasstar-t1.net>
MIME-Version: 1.0
Content-Disposition: inline
References: <680808427CF931459462C3D78CB5EC60038B6296@EXVS02.nasstar-t1.net>
Subject: Re: [Sip] B2B-UA's provide an unsolveable identity problem (was RE:
	submission of a new I-D: "Dialog Event foRIdentityVErification")
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

PiBFbHdlbGwsIEpvaG4gd3JpdGVzOgo+Cj4gID4gPiBJIHN1cHBvcnQgZHJhZnQta3V0aGFuLXNp
cC1kZXJpdmUtMDAsIGFuZCBob3BlIHRoZSBXRyBjYW4gZGV2b3RlICA+Cj4+IHRpbWUgYW5kIGVu
ZXJneSB0byBpbXByb3ZpbmcgYW5kIHN0YW5kYXJkaXppbmcgaXQgdG8gd29yayB3ZWxsICA+ID4K
PiBhY3Jvc3MgYSB2YXJpZXR5IG9mIG5ldHdvcmtzLgo+ICA+IFtKUkVdIEkgYWdyZWUuIFRoaXMg
bXVzdCBpbmNsdWRlIG5ldHdvcmtzIHRoYXQgY29udGFpbiBCMkJVQXMvU0JDcy4KCkEgQjJCVUEg
aXMgYSBtYW4taW4tdGhlLW1pZGRsZSwgdGhlcmUncyBubyBmZWFzaWJsZSBlbmQtdG8tZW5kIHNj
ZW5hcmlvIGhlcmUuCi0tIApWaWN0b3IgUGFzY3VhbCDDgXZpbGEKX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18KU2lwIG1haWxpbmcgbGlzdCAgaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zaXAKVGhpcyBsaXN0IGlzIGZvciBORVcgZGV2
ZWxvcG1lbnQgb2YgdGhlIGNvcmUgU0lQIFByb3RvY29sClVzZSBzaXAtaW1wbGVtZW50b3JzQGNz
LmNvbHVtYmlhLmVkdSBmb3IgcXVlc3Rpb25zIG9uIGN1cnJlbnQgc2lwClVzZSBzaXBwaW5nQGll
dGYub3JnIGZvciBuZXcgZGV2ZWxvcG1lbnRzIG9uIHRoZSBhcHBsaWNhdGlvbiBvZiBzaXA=


From sip-bounces@ietf.org  Fri Oct 31 05:27:57 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C6C8D3A6990;
	Fri, 31 Oct 2008 05:27:57 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ACDAA3A6940
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 05:27:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5Tddc7GbvLNi for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 05:27:56 -0700 (PDT)
Received: from sov.voip.co.uk (smtp.sov.voip.co.uk [80.249.108.49])
	by core3.amsl.com (Postfix) with ESMTP id E86943A67FA
	for <sip@ietf.org>; Fri, 31 Oct 2008 05:27:55 -0700 (PDT)
Message-ID: <490ADE61.4030005@voip.co.uk>
Date: Fri, 31 Oct 2008 10:30:57 +0000
From: Michael Procter <michael@voip.co.uk>
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: =?UTF-8?B?VmljdG9yIFBhc2N1YWwgw4F2aWxh?= <victor.pascual.avila@gmail.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>	<D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>	<200810290236.m9T2akDN55854559@shell01.TheWorld.com>	<033d01c93979$b3cf1990$c3f0200a@cisco.com>
	<618e24240810291636q6986570as674cbe65e49a8c7b@mail.gmail.com>
In-Reply-To: <618e24240810291636q6986570as674cbe65e49a8c7b@mail.gmail.com>
Cc: sip@ietf.org, Dan Wing <dwing@cisco.com>
Subject: Re: [Sip] submission of a new I-D: "Dialog Event
	foR	IdentityVErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

VmljdG9yIFBhc2N1YWwgw4F2aWxhIHdyb3RlOgo+IE9uIFdlZCwgT2N0IDI5LCAyMDA4IGF0IDQ6
NTIgQU0sIERhbiBXaW5nIDxkd2luZ0BjaXNjby5jb20+IHdyb3RlOgo+ICAgCj4+IERFUklWRSBp
cyBjaGVja2luZyB0byBzZWUgaWYgeW91ciBTSVAgcm91dGluZyB0YWtlcyB5b3UgdG8gdGhlCj4+
IHNhbWUgcGxhY2UgdGhhdCAoY2xhaW1zIHRvKSBiZSBvcmlnaW5hdGluZyB0aGUgaW5jb21pbmcg
SU5WSVRFLgo+PiBJdCBpcyB1c2luZyB5b3VyICpvdXRnb2luZyogU0lQIHJvdXRpbmcgLS0gd2hp
Y2ggeW91IG11c3QgYWxyZWFkeQo+PiB0cnVzdCB0byBzZW5kIG91dGJvdW5kIG1lc3NhZ2VzIC0t
IHRvIHRlc3QgdGhlIHZhbGlkaXR5IG9mIHRoZQo+PiAocHJvcG9ydGVkKSBGcm9tOiBhZGRyZXNz
IG9mIGFuIGluY29taW5nIElOVklURS4KPj4gICAgIAo+Cj4gU2hhbGwgREVSSVZFIGJlIGV4dGVu
ZGVkIHRvIHN1cHBvcnQgbm9uLUlOVklURSByZXF1ZXN0cyAoZS5nLiBNRVNTQUdFKQoKSSdtIG5v
dCBzdXJlIGl0IGNhbi4gIFJGQzQyMzUgaXMgZGVmaW5lZCBmb3IgSU5WSVRFLWluaXRpYXRlZCBk
aWFsb2cKdXNhZ2VzIG9ubHkuICBZZXMsIGl0IGNvdWxkIGJlIGV4dGVuZGVkLCBidXQgSSdtIG5v
dCBjb252aW5jZWQgdGhhdCBpcwpuZWNlc3NhcmlseSB0aGUgYmVzdCB3YXkgZm9yd2FyZCBmcm9t
IGhlcmUhCgpSZWdhcmRzLAoKTWljaGFlbAoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18KU2lwIG1haWxpbmcgbGlzdCAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9zaXAKVGhpcyBsaXN0IGlzIGZvciBORVcgZGV2ZWxvcG1lbnQgb2Yg
dGhlIGNvcmUgU0lQIFByb3RvY29sClVzZSBzaXAtaW1wbGVtZW50b3JzQGNzLmNvbHVtYmlhLmVk
dSBmb3IgcXVlc3Rpb25zIG9uIGN1cnJlbnQgc2lwClVzZSBzaXBwaW5nQGlldGYub3JnIGZvciBu
ZXcgZGV2ZWxvcG1lbnRzIG9uIHRoZSBhcHBsaWNhdGlvbiBvZiBzaXA=


From sip-bounces@ietf.org  Fri Oct 31 05:52:05 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0EDB93A6BDF;
	Fri, 31 Oct 2008 05:52:05 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6F4D93A696B
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 05:52:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.949
X-Spam-Level: 
X-Spam-Status: No, score=-4.949 tagged_above=-999 required=5
	tests=[AWL=-1.000, BAYES_00=-2.599, HELO_EQ_SE=0.35,
	MANGLED_DELIVY=2.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 8vSeWAXg567O for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 05:52:02 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 3C36828C0EA
	for <sip@ietf.org>; Fri, 31 Oct 2008 05:52:02 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	338DA20257; Fri, 31 Oct 2008 13:51:59 +0100 (CET)
X-AuditID: c1b4fb3e-acf82bb00000537b-48-490aff6f2f0c
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	1B379206BD; Fri, 31 Oct 2008 13:51:59 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 13:51:59 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 31 Oct 2008 13:51:58 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF08B606CA@esealmw113.eemea.ericsson.se>
In-Reply-To: <433AEBD3-1D7C-4161-93F4-388B4924ECA0@ntt-at.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-rosenberg-sip-target-uri-delivery-00.txt: P-Called-Party-ID
thread-index: Ack7OewccjJuawvoS5yUbDn4ssduewAHRlFA
References: <20081027043001.656543A6781@core3.amsl.com>
	<433AEBD3-1D7C-4161-93F4-388B4924ECA0@ntt-at.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Jonathan Rosenberg" <jdrosen@cisco.com>
X-OriginalArrivalTime: 31 Oct 2008 12:51:59.0001 (UTC)
	FILETIME=[76516890:01C93B57]
X-Brightmail-Tracker: AAAAAA==
Cc: sip@ietf.org
Subject: [Sip] draft-rosenberg-sip-target-uri-delivery-00.txt:
	P-Called-Party-ID
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 
Hi,

The draft-holmberg-sip-target-uri-delivery-01.txt draft contained text
on why the P-Called-Party-ID header was used. Would it be a good idea to
keep that text in this spec, because I have already received questions
regarding that.

Regards,

Christer




> > A New Internet-Draft is available from the on-line Internet-Drafts 
> > directories.
> >
> > 	Title           : Delivery of Request-URI Targets to User Agents
> > 	Author(s)       : J. Rosenberg
> > 	Filename        : draft-rosenberg-sip-target-uri-delivery-00.txt
> > 	Pages           : 12
> > 	Date            : 2008-10-26
> >
> > When a Session Initiation Protocol (SIP) proxy receives a request 
> > targeted at a URI identifying a user or resource it is responsible 
> > for, the proxy translates the URI to a registered contact URI of an 
> > agent representing that user or resource.  In the process, the 
> > original URI is removed from the request.  Numerous use cases have 
> > arisen which require this information to be delivered to the user 
> > agent.  This document describes these use cases and defines an 
> > extension to the History-Info header field which allows it 
> to be used 
> > to support those cases.
> >
> > A URL for this Internet-Draft is:
> > 
> http://www.ietf.org/internet-drafts/draft-rosenberg-sip-target-uri-del
> > ivery-00.txt
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > Below is the data which will enable a MIME compliant mail reader 
> > implementation to automatically retrieve the ASCII version of the 
> > Internet-Draft.
> > <mime-attachment>_______________________________________________
> > I-D-Announce mailing list
> > I-D-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > Internet-Draft directories: http://www.ietf.org/shadow.html or 
> > ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors@cs.columbia.edu for questions on current sip 
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 31 05:53:32 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F14D028C2EB;
	Fri, 31 Oct 2008 05:53:31 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3660928C1DD
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 05:53:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id dNteScjEHeu4 for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 05:53:30 -0700 (PDT)
Received: from mail119.messagelabs.com (mail119.messagelabs.com
	[216.82.245.51]) by core3.amsl.com (Postfix) with SMTP id 5028D28C0EA
	for <sip@ietf.org>; Fri, 31 Oct 2008 05:53:30 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: ranjit@motorola.com
X-Msg-Ref: server-2.tower-119.messagelabs.com!1225457605!29249324!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [136.182.1.14]
Received: (qmail 2685 invoked from network); 31 Oct 2008 12:53:25 -0000
Received: from unknown (HELO motgate4.mot.com) (136.182.1.14)
	by server-2.tower-119.messagelabs.com with SMTP;
	31 Oct 2008 12:53:25 -0000
Received: from il27exr04.cig.mot.com (il27exr04.mot.com [10.17.196.73])
	by motgate4.mot.com (8.12.11/Motorola) with ESMTP id m9VCrOhq015501
	for <sip@ietf.org>; Fri, 31 Oct 2008 05:53:24 -0700 (MST)
Received: from il27vts02.mot.com (il27vts02.cig.mot.com [10.17.196.86])
	by il27exr04.cig.mot.com (8.13.1/Vontu) with SMTP id m9VCrOuU005877
	for <sip@ietf.org>; Fri, 31 Oct 2008 07:53:24 -0500 (CDT)
Received: from ZMY16EXM66.ds.mot.com (zmy16exm66.ap.mot.com [10.179.4.26])
	by il27exr04.cig.mot.com (8.13.1/8.13.0) with ESMTP id m9VCrNFR005863
	for <sip@ietf.org>; Fri, 31 Oct 2008 07:53:24 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 31 Oct 2008 20:53:30 +0800
Message-ID: <750BBC72E178114F9DC4872EBFF29A5B05B82208@ZMY16EXM66.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on draft-saklikar-comm-diversion-notification-00.txt
Thread-Index: Ack7STTU7Ays1SkcQli2PfLI8+1XCwADmf0Q
From: "Avasarala Ranjit-A20990" <ranjit@motorola.com>
To: <sip@ietf.org>
X-CFilter-Loop: Reflected
Subject: [Sip] Comments on draft-saklikar-comm-diversion-notification-00.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1625530589=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1625530589==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C93B57.A8243760"

This is a multi-part message in MIME format.

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


> Hi
>=20
> This draft on communication diversion notification info proposes a SIP
> based XML event package for notifying subscribers of call diversions
> that occur on their behalf in the network. Please review the draft and
> comment
>=20
> Link for the draft:
> http://www.ietf.org/internet-drafts/draft-saklikar-comm-diversion-noti
> fication-00.txt
>=20
> Thanks
>=20
> Regards
> Ranjit
>=20

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>Comments on =
draft-saklikar-comm-diversion-notification-00.txt</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Hi</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">This draft on =
communication diversion notification info proposes a SIP based XML event =
package for notifying subscribers of call diversions that occur on their =
behalf in the network. Please review the draft and comment</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Link for the =
draft:&nbsp;</FONT> <A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-saklikar-comm-diversion=
-notification-00.txt"><U></U><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">http://www.ietf.org/internet-drafts/draft-saklikar-comm-di=
version-notification-00.txt</FONT></U></A>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Thanks</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Regards</FONT>

<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Ranjit</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C93B57.A8243760--

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

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


From sip-bounces@ietf.org  Fri Oct 31 06:02:37 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 711423A6C0D;
	Fri, 31 Oct 2008 06:02:37 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5F3B13A6C0C
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 06:02:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.016
X-Spam-Level: 
X-Spam-Status: No, score=-6.016 tagged_above=-999 required=5 tests=[AWL=0.233, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jPii7Xj+0N-V for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 06:02:35 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 47E513A6C28
	for <sip@ietf.org>; Fri, 31 Oct 2008 06:00:42 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	EE1C2220C0; Fri, 31 Oct 2008 13:59:23 +0100 (CET)
X-AuditID: c1b4fb3e-aaf7ebb00000537b-87-490b012bb20f
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	CDB9D21148; Fri, 31 Oct 2008 13:59:23 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 13:59:23 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 31 Oct 2008 13:59:22 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF08B6071B@esealmw113.eemea.ericsson.se>
In-Reply-To: <9F7BFBEE-A96A-4E33-B3DB-9074DE2FE579@standardstrack.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: Info Package Versioning
thread-index: Ack6tcFdQXygytTxTIiWX4eFZhdKMAAofZ9Q
References: <48FDEAD8.8010803@cisco.com>	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>	<4901BA73.1010700@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>	<4901C2B1.1050209@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>	<4901D025.6060302@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>	<490239C8.3020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>	<4902467E.3010603@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFBA@esealmw113.eemea.ericsson.se>	<4905B23F.10609@cisco.com><CA9998CD4A020D418654FCDEF4E707DF089F589E@esealmw113.eemea.ericsson
	.se> <49	05CAE2.9020808@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8FF@esealmw113.eemea.ericss
	on.se> <49060DD4.7 070804@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F906@esealmw113.eemea.ericsson.se>
	<9F7BFBEE-A96A-4E33-B3DB-9074DE2FE579@standardstrack.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Eric Burger" <eburger@standardstrack.com>
X-OriginalArrivalTime: 31 Oct 2008 12:59:23.0714 (UTC)
	FILETIME=[7F633A20:01C93B58]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Info Package Versioning
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0228046605=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0228046605==
Content-class: urn:content-classes:message
Content-Type: multipart/signed;
	protocol="application/x-pkcs7-signature";
	micalg=SHA1;
	boundary="----=_NextPart_000_001E_01C93B69.4263A040"

This is a multi-part message in MIME format.

------=_NextPart_000_001E_01C93B69.4263A040
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit


Hi,

Before I give my vote, I just want to clarify a little what I meant.

Assume you have package A, which can carry some information.

Then you figure out you need a new information element, but all the old
information still remains exactly the same. You create package B.

Now, package B would be fully backward compatible with package A.

But, if there is no versioning, and backward compability guidelines, I would
have to indicate explicit support of both package A and B.

Of course, if package B is NOT backward compatible, it would have to be a
compeltely new package.

Another option is of course to deal with these kind of things inside the
info packet itself.

Regards,

Christer



 

> -----Original Message-----
> From: Eric Burger [mailto:eburger@standardstrack.com] 
> Sent: 30. lokakuuta 2008 18:53
> To: Christer Holmberg
> Cc: SIP IETF
> Subject: Info Package Versioning
> 
> Channeling Keith here: is there a real use case for package 
> versioning?
> 
> I cannot imagine backwards-compatible packages. Once one 
> starts changing the stuff in an INFO package, it is a 
> different package. That is, rather than
> 
>     Info-Package: foo-package;version=1
>     Info-Package: foo-package;version=2
> 
> You, in reality have:
> 
>     Info-Package: foo-package
>     Info-Package: something-like-foo-but-not-really-foo-anymore
> 
> This is more especially so when one considers there is no 
> possibility of negotiating package versions, whereas there is 
> a possibility of negotiating different packages.
> 
> For the one instance one could come up with in theory for 
> needing versioning, remember one does get to have an 
> arbitrary parameter:
> 
>     Info-Package: foo-package               /* Version 1 */
>     Info-Package: foo-package;bar        /* Version 2 */
> 
> 
> Is this latter mechanism sufficient?
> 
> Yet another poll:
> 
> [ ] We must have abstract versioning as part of the Info 
> Framework document
> 
> [ ] We do not need to have abstract versioning, as it does 
> not do anything for anyone
> 
> [ ] We do not need abstract versioning, but it would be 
> worthwhile including some text,
>      like what is above, to show people how to do it.
> 
> [ ] Something else? _____________________________________
> 
> 
> 
> On Oct 27, 2008, at 4:48 PM, Christer Holmberg wrote:
> 
> > [snip]
> >> The wording could be better. There are no explicit IANA 
> >> considerations
> > about registering an INFO package. Its just implied here. 
> Its a little 
> > confusing here what is intended to be part of the
> >> *definition* of a new package vs. what is intended to be in the 
> >> content
> > of a particular package instance in an INFO message.
> >
> > We do need to have a section on what needs to be part of an info 
> > package definition. The mime type is one thing, for sure.
> >
> > I guess we should also look at what/if we can re-use from 
> SIP events.
> >
> > We also need to decide whether info packages should have a version 
> > number system. From experience I think that would be very useful.
> >
> > Info-Package: foo-package;version=1
> >
> > ...or something like that.
> [snip]
> 
> 

------=_NextPart_000_001E_01C93B69.4263A040
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIQXjCCA2Ew
ggJJoAMCAQICEAoBAQEAAAJ8AAAACgAAAAIwDQYJKoZIhvcNAQEFBQAwOjEZMBcGA1UEChMQUlNB
IFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDggVjMwHhcNMDEwMjIyMjAz
OTIzWhcNMjYwMjIyMjAzOTIzWjA6MRkwFwYDVQQKExBSU0EgU2VjdXJpdHkgSW5jMR0wGwYDVQQL
ExRSU0EgU2VjdXJpdHkgMjA0OCBWMzCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALeP
VXHSgN17aXmn8BhQMjxiZ/YKlQfd5hvzntnSQVRrrZ98vhnN+0arQWgeGOpVyC+ReIko+ycpYP/f
j4w7yUmbtaSUzgHqPrVje38m/RndwCG9hNEtT0bDTtzYNzk7KK/LnRrqK68hpcEjIri4G1oTh1eD
0fAg5+hPI0KwAKV9ienpYXOUmHEmvC1q4PdN8PG2KjgxgQ0p4QDBUQ9MUvgEWqp9ctO4hyq7YxAD
KrOhTw1aXka3PQ71dOyZn/k9JIGIpt1gVOiVNj3GCZOaoxKAAFWZGUe90KV8w7r7H/f1D/isubX0
N5gTGN6FW7cMgjuHb5U5WDDabgFoFyLMwAsCAwEAAaNjMGEwDwYDVR0TAQH/BAUwAwEB/zAOBgNV
HQ8BAf8EBAMCAQYwHwYDVR0jBBgwFoAUB8NRMKSq6UWuNST6/yQsM9CxnYwwHQYDVR0OBBYEFAfD
UTCkqulFrjUk+v8kLDPQsZ2MMA0GCSqGSIb3DQEBBQUAA4IBAQBfPoZ2brg1PE42HB55mL/91RIR
eVIO7jGJvN1/+dHGFSHoigFUDTr7VLnWY9SxqpZNokJN1FMfixDef2W+YBMncYikc+OEY9GkVeFQ
k+YbDnnQZ7xGyL8/Fw2V5saQad7ntC/elX3QEj89Pn9NPxRo9RFQ1cH0kKUIHTFg/2CMI1QKr/6h
bsXReipoeM8eggogtB+t5YWyamh1Tq0lN5SFvr2h1Oq3DEs8negSAPBfrA3hrHBjc/d/eZ8yJUJ0
BYAov73BJJZYFbEXIemJS9sHiGf0Fa1wPi9NhTvCt9v+mGgjieF0D970xYRjKRvMywfJAKSp18Ii
T2fXd+wgBWHeMIIEOzCCAyOgAwIBAgIRAJVH75z4QARyornUiAPBkWswDQYJKoZIhvcNAQEFBQAw
OTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0Ew
MTAeFw0wODA0MjQwNzQ1MjVaFw0xMTA0MjQwNzQ1MjJaMG8xETAPBgNVBAoMCEVyaWNzc29uMRow
GAYDVQQDDBFDaHJpc3RlciBIb2xtYmVyZzEPMA0GA1UEBRMGTE1GQ0hIMS0wKwYJKoZIhvcNAQkB
Fh5jaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJ
AoGBAIEQRcFxzKUClXod2Fgx0hXOshVy2Tb+a/3Idz+tbTlkf6ctY/oiog7p1KAt2yhnHl0VNXYC
6HqeOdKVzXfFC/SXlSM5drm2zAQSCjp/sG8PJjX0i+Kdqsv1BtcAfDauavWu9xnxjxN2urorN4XE
IB/7KyANnHBvYbfc6B9maq/zAgMBAAGjggGKMIIBhjCBwAYDVR0fBIG4MIG1MIGyoIGvoIGshjdo
dHRwOi8vY3JsLnRydXN0LnRlbGlhLmNvbS9Fcmljc3Nvbk5MSW5kaXZpZHVhbENBMDEuY3JshnFs
ZGFwOi8vbGRhcC50cnVzdC50ZWxpYS5jb20vY249RXJpY3Nzb24lMjBOTCUyMEluZGl2aWR1YWwl
MjBDQTAxLG89RXJpY3Nzb24/Y2VydGlmaWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnk/YmFzZTAp
BgNVHREEIjAggR5jaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20wRgYDVR0gBD8wPTA7BgYq
hXBrAQEwMTAvBggrBgEFBQcCARYjaHR0cDovL3d3dy5lcmljc3Nvbi5jb20vbGVnYWwuc2h0bWww
HQYDVR0OBBYEFAh/qeNFQFeOQVkqjxEElbl724C1MB8GA1UdIwQYMBaAFJYnw7jepV9dRD45UuVF
sXZfYzCbMA4GA1UdDwEB/wQEAwIFoDANBgkqhkiG9w0BAQUFAAOCAQEALkfHT85VI4KjtTfmNwdS
wAX9HgA7Mo5R35LHQ5zi+On/XlK73aAhVT4YmYzQGPfRD1VM5CjDghkD1gPyV8sQGrViMjTkf3qz
ZlzC0kPndA3IM9wHJMYsIPNxoqSSgF39GpxuJ35bXlliCcVeU/jmUJySnBOZKueYQVe0H8L1OYYT
u9yMMSfOT3BgQ7a8up1T7MjDffAWOVOcx9csvbgXWugZyX2rnuANIkt/XLdiRDStLk6M1pr7rQHP
8ZLPwENu0/RhcnFdb8O0dIJslTwkZh3RrmAluhkptje3VKwvg9JkPiontpQqhtFgtcJoWteKRjv1
tiBZlEvfdA74nDpgZjCCBEUwggMtoAMCAQICEBPJ6v/eJq2p3KTKI4GDR+MwDQYJKoZIhvcNAQEF
BQAwRDEaMBgGA1UECgwRVGVsaWFTb25lcmEgR3JvdXAxJjAkBgNVBAMMHVRlbGlhU29uZXJhIFB1
YmxpYyBSb290IENBIHYxMB4XDTA2MTAwNjEwMDA1M1oXDTE2MTAwMjA1MDQxN1owOTERMA8GA1UE
CgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBALYQd+Q1HuuHxDyNGFlEPzCxuPPFO5W2xyr+nqCVnNJ4
QYFe1HACqavqNLwUGIqIEyHv1rLnfub9LBc7dQpRHjl/dggin0ONOFJ36nbGEbfHjLJz2BzOWvwl
84Sc+Fx09IrDU/SZSWFSfhqTu3TT39h79brHdRkdPBUgBYgsiFKriHI0TjP5G8628H27BDzqUpzG
LSYWgt6/tpwuOH5lcfNfHWMcCYXRlobv0Klu8lxG5amWqAnqrH6ECOyYJTRbHTsaTIZOHy9Qw/0e
XPujKT7tU5xxSI2SdceJqzUbAz2oFRQ6Px7/GydpM/Rl+qYoGPcauHUL1aSeVJZqDFqcIF0CAwEA
AaOCATwwggE4MBIGA1UdEwEB/wQIMAYBAf8CAQAwRgYDVR0gBD8wPTA7BgcqhXAjAgEBMDAwLgYI
KwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wgYkGA1UdHwSBgTB/
MH2ge6B5hndsZGFwOi8vbGRhcC50cnVzdC50ZWxpYS5jb20vY249VGVsaWFTb25lcmElMjBQdWJs
aWMlMjBSb290JTIwQ0ElMjB2MSxvPVRlbGlhU29uZXJhJTIwR3JvdXA/YXV0aG9yaXR5cmV2b2Nh
dGlvbmxpc3Q/YmFzZTAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFJYnw7jepV9dRD45UuVFsXZf
YzCbMB8GA1UdIwQYMBaAFEXb8I+4GmKhqCMbY4g4o9vgGmLxMA0GCSqGSIb3DQEBBQUAA4IBAQB2
AEoqQz+M3Ra9alkpn/YnwhXIv6tPjhUvSuNs00Nhd0T9XhlIU3a65CaB/UKSqnayE0t7Q0Qq3r+x
/GK3in/mik8i/PK2/q8HutzYFSzz6Npztpo2JG7AEKOJPVaeebjng45m6vNC7RIfzU9sG2LBR/he
wS8s6dFFn70w795xUwJBWZ67OzIKXrIVVvHTOYpbWA+MESKAXwFhnVONrOTWlVwrMUi4HbiPWpOk
+xQbgehCEi7mu3cXsaU1Xq3kMXuiNuC7VKoob8mFO9o9RT+dlirD2uRXwNpvCu3but6Kyhu0+nvy
2iXGKjdlxlWTsdDyulXYz+OYCMZ9lFWRzMIPMIIEbTCCA1WgAwIBAgIRAJywjASay5cieGNithuG
Wj0wDQYJKoZIhvcNAQEFBQAwOjEZMBcGA1UEChMQUlNBIFNlY3VyaXR5IEluYzEdMBsGA1UECxMU
UlNBIFNlY3VyaXR5IDIwNDggVjMwHhcNMDYxMDMxMjA0MjI3WhcNMTYxMTAxMTU0MjI1WjBEMRow
GAYDVQQKDBFUZWxpYVNvbmVyYSBHcm91cDEmMCQGA1UEAwwdVGVsaWFTb25lcmEgUHVibGljIFJv
b3QgQ0EgdjEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDKTxADapCAq3mplX4R4gNt
+WZe5QKGnaVEQSyY7lICKF5DuVdWPMLHDjzhw5IzDd860ZZx/0VrhGB3DmP4SDIWCKo2PxvY5Nck
dBWPWp/T2uaQdOAwgqHpN0pe1X7/jel59WsWYXKGg/81Wth73ZK/geE7Gz9Pvj1LU6N4YhLMgoox
KnCS+ZjB5icWAg+Qd1QpQhF46H1ibp6LsBWDp56MPpg8F5X6y7MGVcKYLdnLOPs84uxRW9qs1kBo
pzQBj6s5SyVh8A+j5liDBjghXYpw/+paGEdqHPeSFYxZKeJatmjEKLYlxcZWRKf436KvQA9jBhME
mytMNbGicR1mRH6tAgMBAAGjggFiMIIBXjAfBgNVHSMEGDAWgBQHw1EwpKrpRa41JPr/JCwz0LGd
jDAdBgNVHQ4EFgQURdvwj7gaYqGoIxtjiDij2+AaYvEwEgYDVR0TAQH/BAgwBgEB/wIBBDCBhQYD
VR0gBH4wfDA9BgkqhkiG9w0FBgEwMDAuBggrBgEFBQcCARYiaHR0cHM6Ly9yZXBvc2l0b3J5LnRy
dXN0LnRlbGlhLmNvbTA7BgcqhXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9y
eS50cnVzdC50ZWxpYS5jb20wcAYDVR0fBGkwZzBloGOgYYZfaHR0cDovL3d3dy5yc2FzZWN1cml0
eS5jb20vcHJvZHVjdHMva2Vvbi9yZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0YXR1cy9SU0FfU2Vj
dXJpdHlfMjA0OF92My5DUkwwDgYDVR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUAA4IBAQAEXpos
2CnIm7/872ytSrEHWZgvhOUEkUm25PWf/XkWko41TaL9vIS1S6AdWChNqWmnYiS7GfaIiDM9s1D6
K7hidWBDOm46bNdM3ZwhMyDCfkDJSgeJ0w+7YmjvChu7gWqDZCsbtZ5gA1ixCTdDnuZB67JGSPGW
6r73coraDP8diOpiQouMvM6bKuTPBH/1poLccsUxsKgrQ23JC9LWCRb8cYHkZjXFH1K44TsIl5Ln
e2oT0JI3pwdA2v6jO4p/OLHntP+npjwPbedMPUZkDYCkd3LSxj8c3JTxtA8SlPCtIHE1hh65xihg
1JRIliSphrqr9kbfwHdeVxPdOI5GtDYPMYICfjCCAnoCAQEwTjA5MREwDwYDVQQKDAhFcmljc3Nv
bjEkMCIGA1UEAwwbRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQTAxAhEAlUfvnPhABHKiudSIA8GR
azAJBgUrDgMCGgUAoIIBhjAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEP
Fw0wODEwMzExMjU5MjJaMCMGCSqGSIb3DQEJBDEWBBS6Wpsc9w8Uze5mXMjVZVVGGKJ5czBdBgkr
BgEEAYI3EAQxUDBOMDkxETAPBgNVBAoMCEVyaWNzc29uMSQwIgYDVQQDDBtFcmljc3NvbiBOTCBJ
bmRpdmlkdWFsIENBMDECEQCVR++c+EAEcqK51IgDwZFrMF8GCyqGSIb3DQEJEAILMVCgTjA5MREw
DwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQTAxAhEA
lUfvnPhABHKiudSIA8GRazBnBgkqhkiG9w0BCQ8xWjBYMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMC
AgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDAHBgUrDgMCGjAKBggq
hkiG9w0CBTANBgkqhkiG9w0BAQEFAASBgD8zuGWoJi4RS/Iz4tzIvp2tD9OP9z8/FtaNPM57vwt2
iyeV3E3+jU3G+tVGTeDV3UDunygOCMoXApoE6j+wnLyAtCT8lJvunIhgRDUUnAEzceQEPVt/cpMP
tGmQ78IK0jxWS/VHMjyBSg+Sr0xn43lMUeQEsOmgSy7Qb4NF30d0AAAAAAAA

------=_NextPart_000_001E_01C93B69.4263A040--

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

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


From sip-bounces@ietf.org  Fri Oct 31 06:03:45 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D450428C1E1;
	Fri, 31 Oct 2008 06:03:45 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E42A928C14C
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 06:03:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.385
X-Spam-Level: 
X-Spam-Status: No, score=-0.385 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3,
	MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id iS1C3WfW5mVN for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 06:03:41 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.235])
	by core3.amsl.com (Postfix) with ESMTP id 1F9EC3A6BF4
	for <sip@ietf.org>; Fri, 31 Oct 2008 06:03:34 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id g9so214539rvb.5
	for <sip@ietf.org>; Fri, 31 Oct 2008 06:03:32 -0700 (PDT)
Received: by 10.141.79.12 with SMTP id g12mr6627777rvl.126.1225458212204;
	Fri, 31 Oct 2008 06:03:32 -0700 (PDT)
Received: by 10.141.41.1 with HTTP; Fri, 31 Oct 2008 06:03:32 -0700 (PDT)
Message-ID: <cc1f582e0810310603w21a4cc7fga1d978c0fb4f5bd7@mail.gmail.com>
Date: Fri, 31 Oct 2008 14:03:32 +0100
From: "=?UTF-8?Q?I=C3=B1aki_Baz_Castillo?=" <ibc@aliax.net>
Cc: sip@ietf.org
In-Reply-To: <490ADE61.4030005@voip.co.uk>
MIME-Version: 1.0
Content-Disposition: inline
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>
	<200810290236.m9T2akDN55854559@shell01.TheWorld.com>
	<033d01c93979$b3cf1990$c3f0200a@cisco.com>
	<618e24240810291636q6986570as674cbe65e49a8c7b@mail.gmail.com>
	<490ADE61.4030005@voip.co.uk>
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR
	IdentityVErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

MjAwOC8xMC8zMSBNaWNoYWVsIFByb2N0ZXIgPG1pY2hhZWxAdm9pcC5jby51az46Cgo+PiBTaGFs
bCBERVJJVkUgYmUgZXh0ZW5kZWQgdG8gc3VwcG9ydCBub24tSU5WSVRFIHJlcXVlc3RzIChlLmcu
IE1FU1NBR0UpCj4KPiBJJ20gbm90IHN1cmUgaXQgY2FuLiAgUkZDNDIzNSBpcyBkZWZpbmVkIGZv
ciBJTlZJVEUtaW5pdGlhdGVkIGRpYWxvZwo+IHVzYWdlcyBvbmx5LiAgWWVzLCBpdCBjb3VsZCBi
ZSBleHRlbmRlZCwgYnV0IEknbSBub3QgY29udmluY2VkIHRoYXQgaXMKPiBuZWNlc3NhcmlseSB0
aGUgYmVzdCB3YXkgZm9yd2FyZCBmcm9tIGhlcmUhCgpBbHNvIG5vdGUgdGhhdCBNRVNTQUdFIGRv
ZXNuJ3QgZXN0YWJsaXNoIGEgZGlhbG9nLCBpdCBqdXN0IGFuCmluZGVwZW5kZW50IHRyYW5zYWN0
aW9uLgoKCgotLSAKScOxYWtpIEJheiBDYXN0aWxsbwo8aWJjQGFsaWF4Lm5ldD4KX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KU2lwIG1haWxpbmcgbGlzdCAg
aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zaXAKVGhpcyBsaXN0IGlzIGZv
ciBORVcgZGV2ZWxvcG1lbnQgb2YgdGhlIGNvcmUgU0lQIFByb3RvY29sClVzZSBzaXAtaW1wbGVt
ZW50b3JzQGNzLmNvbHVtYmlhLmVkdSBmb3IgcXVlc3Rpb25zIG9uIGN1cnJlbnQgc2lwClVzZSBz
aXBwaW5nQGlldGYub3JnIGZvciBuZXcgZGV2ZWxvcG1lbnRzIG9uIHRoZSBhcHBsaWNhdGlvbiBv
ZiBzaXA=


From sip-bounces@ietf.org  Fri Oct 31 06:04:08 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B62CF3A6BF1;
	Fri, 31 Oct 2008 06:04:08 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 64A603A6BF1
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 06:04:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.505
X-Spam-Level: 
X-Spam-Status: No, score=-2.505 tagged_above=-999 required=5 tests=[AWL=0.094, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RxOZ5VxBs6NN for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 06:04:07 -0700 (PDT)
Received: from taimen.tutpro.com (harjus.tutpro.com [192.98.100.3])
	by core3.amsl.com (Postfix) with ESMTP id A53E43A6BF2
	for <sip@ietf.org>; Fri, 31 Oct 2008 06:04:06 -0700 (PDT)
Received: by taimen.tutpro.com (Postfix, from userid 1000)
	id B306D33A723; Fri, 31 Oct 2008 15:04:05 +0200 (EET)
MIME-Version: 1.0
Message-ID: <18699.581.694792.826949@harjus.tutpro.com>
Date: Fri, 31 Oct 2008 15:04:05 +0200
To: "Dan Wing" <dwing@cisco.com>
In-Reply-To: <00a501c93b27$f5b198b0$c3f0200a@cisco.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>
	<490792EA.2020106@softarmor.com>
	<033f01c9397b$860847a0$c3f0200a@cisco.com>
	<36E83843-775F-4317-BB0F-746E55194BFD@softarmor.com>
	<1A770AC3-26C6-4D16-86A2-35533896F3C0@estacado.net>
	<CB5ABE64-B8E6-4FEF-B56E-9D68E253B689@softarmor.com>
	<00a501c93b27$f5b198b0$c3f0200a@cisco.com>
X-Mailer: VM 7.19 under Emacs 22.1.1
From: jh@tutpro.com (Juha Heinanen)
Cc: 'Sip List' <sip@ietf.org>, 'Dean Willis' <dean.willis@softarmor.com>
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Dan Wing writes:

 > SIP provides reliable forward routing, too.  I don't
 > see a consensus forming that we want to utilize SIP's
 > reliable forward routing to build a verification system.

there has not been uniform consensus on many things (especially 3gpp
rubber stamping) that this working group has decided to do.  in my
opinion there has been enough interest expressed on this mailing list to
go forward with DERIVE.  those who don't need it or are not planning to
use it, can do something else.  they should not try to prevent other
people working on DERIVE.

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


From sip-bounces@ietf.org  Fri Oct 31 06:05:32 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BB08428C19D;
	Fri, 31 Oct 2008 06:05:32 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6E4013A6C08
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 06:05:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.034
X-Spam-Level: 
X-Spam-Status: No, score=-6.034 tagged_above=-999 required=5 tests=[AWL=0.215, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id HP9IaUsFsJcJ for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 06:05:30 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 8A8DC3A6963
	for <SIP@ietf.org>; Fri, 31 Oct 2008 06:05:29 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	410AC22397; Fri, 31 Oct 2008 14:05:24 +0100 (CET)
X-AuditID: c1b4fb3e-aa77dbb00000537b-91-490b02937ad0
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	EFE3A223B3; Fri, 31 Oct 2008 14:05:23 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 14:05:03 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 31 Oct 2008 14:05:02 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF08B60752@esealmw113.eemea.ericsson.se>
In-Reply-To: <490A52E2.9050504@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Proposal for multiple INFO bodies in an INFO
thread-index: Ack68MGGWZ5z3xZ9SfmZ21g1wybqoQAZ/CXw
References: <322862FF-3683-465F-B1A0-8C619A5D60E1@standardstrack.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFDD@esealmw113.eemea.ericsson.se>
	<490A52E2.9050504@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>
X-OriginalArrivalTime: 31 Oct 2008 13:05:03.0762 (UTC)
	FILETIME=[4A126F20:01C93B59]
X-Brightmail-Tracker: AAAAAA==
Cc: IETF SIP List <SIP@ietf.org>
Subject: Re: [Sip] Proposal for multiple INFO bodies in an INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi,

Erick says that once we are able to indicate which mime contains the
info package, we would be able to allow multiple info packages.

For, that would of course require that we either allow multiple
Info-Package headers, or that a single header can list multiple info
packages.

Regards,

Christer

> -----Original Message-----
> From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
> Sent: 31. lokakuuta 2008 2:36
> To: Christer Holmberg
> Cc: Eric Burger; IETF SIP List
> Subject: Re: [Sip] Proposal for multiple INFO bodies in an INFO
> 
> I am ok with either way.
> 
> I think using C-D follows the precedent of INVITE for finding 
> "its body part" via C-D of "session".
> 
> 	Thanks,
> 	Paul
> 
> Christer Holmberg wrote:
> > Hi Erick,
> >  
> > I am not your suggestion of using CID for Info packages is 
> what has been discussed (I may be wrong, of course).
> >  
> > I think what Paul was proposing was to have a 
> Content-Disposition value indicating that a particular body 
> shall be treated as in info package.
> >  
> > INFO .....
> > To: ....
> > From: ....
> > Info-Package: foo
> > Content-Type: application/foo
> > Content-Dispotistion: info
> > ...
> > 
> > <foo body>
> > 
> > 
> > Multipart mixed example with indirect content:
> > 
> > INFO ....
> > To: ....
> > From: ....
> > Info-Package: foo
> > Content-Type: multipart/mixed;boundary="theboundary"
> > ...
> > 
> > --theboundary
> > Content-Type: application/mumble
> > Content-Disposition: whatever
> > 
> > <mumble body>
> > 
> > --theboundary
> > Content-Type: application/foo
> > Content-Disposition: info
> > 
> > <foo body>
> > 
> > --theboundary--
> > 
> >  
> >  
> > Regards,
> >  
> > Christer
> > 
> > ________________________________
> > 
> > From: sip-bounces@ietf.org on behalf of Eric Burger
> > Sent: Thu 30/10/2008 19:29
> > To: IETF SIP List
> > Subject: [Sip] Proposal for multiple INFO bodies in an INFO
> > 
> > 
> > 
> > Good thing I waited 10 days...
> > 
> > Initially, I was very swayed by the argument that things would be 
> > much, much easier if we restricted an INFO request to a 
> single Info- 
> > Package.
> > 
> > However, and especially as the last person to touch RFC 4483, I can 
> > see the argument that *any* SIP message can end up with a 
> multipart/ 
> > mime body, even if you think you can limit it to just your stuff, 
> > because the UA can always have a content indirection pointer in the 
> > header pointing to a mime body part.
> > 
> > Therefore, even if we restrict an INFO request to carry a 
> single Info- 
> > Package, we need a mechanism to uniquely identify and, at the SIP 
> > header level, indicate which body part belongs to the package.
> > 
> > I would offer once we solve that, we also get multiple INFO request 
> > bodies for free.
> > 
> > I would also offer that since INFO does not change SIP state, which 
> > means there is not even a concept of a message succeeding 
> but the INFO 
> > body doing something that "fails", the objection that it 
> would be hard 
> > for a UA to report on one body "failing" with another body 
> > "succeeding" is a non-issue.  Yes, this does mean that you 
> cannot use 
> > INFO to tunnel IP.  See RFC 3252 for more on this.  I do 
> not see this 
> > as a problem.
> > 
> > Therefore, on to the solution.  We use the MIME approach.  The body 
> > parts get tagged with Content-IDs. The Info-Package has a 
> parameter, 
> > CID, which points to the body part.  The ONLY question I have is 
> > whether we should simply mandate always having this 
> parameter to make 
> > the protocol and parser easier, but a small burden on UAC's that 
> > really are only sending a single body.  Other than that, 
> the mechanism 
> > looks like:
> > 
> > INFO .....
> > To: ....
> > From: ....
> > Info-Package: foo
> > Content-Type: application/foo;cid=this
> > Content-Id: this
> > ...
> > 
> > <foo body>
> > 
> > 
> > 
> > Multipart mixed example with indirect content:
> > 
> > INFO ....
> > To: ....
> > From: ....
> > Info-Package: foo;cid=abcd1234zz
> > Mumble: <cid:abcd9999qq>
> > Content-Type: multipart/mixed;boundary="theboundary"
> > ...
> > 
> > --theboundary
> > Content-Type: application/mumble
> > Content-Id: abcd9999qq
> > ...
> > 
> > <mumble stuff>
> > 
> > --theboundary
> > Content-Type: application/foo
> > Content-Id: abcd1234zz
> > 
> > <foo body>
> > 
> > --theboundary--
> > 
> > 
> > 
> > 
> > Multiple Info Packages follow. Note that by using 
> Content-Id, order is 
> > irrelevant.
> > 
> > INFO ....
> > To: ....
> > From: ....
> > Info-Package: foo;cid=abcd1234zz
> > Info-Package: bar;cid=wxyz9876
> > Content-Type: multipart/mixed;boundary="theboundary"
> > ...
> > 
> > --theboundary
> > Content-Type: application/bar
> > Content-Id: wxyz9876
> > ...
> > 
> > <bar stuff>
> > 
> > --theboundary
> > Content-Type: application/foo
> > Content-Id: abcd1234zz
> > 
> > <foo body>
> > 
> > --theboundary--
> > 
> > _______________________________________________
> > Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol Use 
> > sip-implementors@cs.columbia.edu for questions on current sip Use 
> > sipping@ietf.org for new developments on the application of sip
> > 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 31 06:11:06 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 253953A68E4;
	Fri, 31 Oct 2008 06:11:06 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1D1A73A68C3
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 06:11:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.049
X-Spam-Level: 
X-Spam-Status: No, score=-6.049 tagged_above=-999 required=5 tests=[AWL=0.200, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tIFDO+4Jdye1 for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 06:11:02 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 27BED3A682B
	for <sip@ietf.org>; Fri, 31 Oct 2008 06:10:46 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	B2E982099A; Fri, 31 Oct 2008 14:10:43 +0100 (CET)
X-AuditID: c1b4fb3c-ac0cabb0000015b5-a0-490b03d31018
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	9DF66208C5; Fri, 31 Oct 2008 14:10:43 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 14:10:43 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 31 Oct 2008 14:10:42 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF08B60791@esealmw113.eemea.ericsson.se>
In-Reply-To: <490A54A8.7070405@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Legacy Info Package Registration
thread-index: Ack68bWdZvlFue05QR2cGCPuqx7+wwAZ+tOQ
References: <20081020231502.43DCA3A69EF@core3.amsl.com><48FDECB5.3030607@cisco.com><81521DF0-2666-4500-BE62-412FBB6966A7@standardstrack.com><5D1A7985295922448D5550C94DE291800245C378@DEEXC1U01.de.lucent.com>
	<490A54A8.7070405@cisco.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>,
	"DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
X-OriginalArrivalTime: 31 Oct 2008 13:10:43.0167 (UTC)
	FILETIME=[145F86F0:01C93B5A]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Legacy Info Package Registration
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi,

I guess one option is to e.g. have an annex, where we for legacy usages
list Content-Type and a reference (if available) to where the usage is
described.

If there are different legacy usages with the same Content-Type, I don't
think we should deal with that. That would just show the need for the
info packages.

Also, I don't think we would need to collect each and every legacy usage
out there (I am not sure we would manage to do that even with a
registry).

Regards,

Christer




> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Paul Kyzivat
> Sent: 31. lokakuuta 2008 2:43
> To: DRAGE, Keith (Keith)
> Cc: SIP IETF
> Subject: Re: [Sip] Legacy Info Package Registration
> 
> 
> 
> DRAGE, Keith (Keith) wrote:
> 
> > At the moment I am also unsure what criteria we would use for 
> > identifing a legacy usage, apart from some rather vague textual 
> > description. It after all does not have a package name.
> 
> With legacy usage, the only distinguishing characteristic 
> that I am aware has ever been used is Content-Type. So I 
> think the registry has to be based on Content-Type, probably 
> on a FCFS basis. (Though perhaps there might be need of an 
> appeals process if there are conflicting usages. But I doubt 
> we will find that.)
> 
> 	Paul
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use 
> sip-implementors@cs.columbia.edu for questions on current sip 
> Use sipping@ietf.org for new developments on the application of sip
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 31 06:16:54 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8E71228C1F7;
	Fri, 31 Oct 2008 06:16:54 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9C63028C1F7
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 06:16:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.063
X-Spam-Level: 
X-Spam-Status: No, score=-6.063 tagged_above=-999 required=5 tests=[AWL=0.186, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id MSt1fTRhps-z for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 06:16:51 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 87F4C28C165
	for <sip@ietf.org>; Fri, 31 Oct 2008 06:16:47 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	38553208C5; Fri, 31 Oct 2008 14:16:45 +0100 (CET)
X-AuditID: c1b4fb3c-ae0cebb0000015b5-94-490b053decd7
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	102DA20738; Fri, 31 Oct 2008 14:16:45 +0100 (CET)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 14:16:44 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 31 Oct 2008 14:16:44 +0100
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF08B607C8@esealmw113.eemea.ericsson.se>
In-Reply-To: <975C30B3-A80B-4A6D-9892-7946404F89B4@standardstrack.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] draft-ietf-sip-info-events-00: package negotiation
thread-index: Ack7Al9raRRYGym3RVKBUtnRQtQ9JQAWC7Dw
References: <48FDEC6B.8090006@cisco.com><CA9998CD4A020D418654FCDEF4E707DF0889EAE5@esealmw113.eemea.ericsson.se>
	<975C30B3-A80B-4A6D-9892-7946404F89B4@standardstrack.com>
From: "Christer Holmberg" <christer.holmberg@ericsson.com>
To: "Eric Burger" <eburger@standardstrack.com>
X-OriginalArrivalTime: 31 Oct 2008 13:16:44.0981 (UTC)
	FILETIME=[EC07F650:01C93B5A]
X-Brightmail-Tracker: AAAAAA==
Cc: SIP IETF <sip@ietf.org>, Paul Kyzivat <pkyzivat@cisco.com>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: package negotiation
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


Hi,

A UA can support both legacy usages and INFO packages.

For example, ISUP transport may have been implemented in a network years
ago, and now some new fancy Info package stuff starts to come around. A
UA which supports the new stuff will still have to support the old
stuff.

Regards,

Christer

 

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of Eric Burger
> Sent: 30. lokakuuta 2008 19:07
> To: Christer Holmberg
> Cc: SIP IETF; Paul Kyzivat
> Subject: Re: [Sip] draft-ietf-sip-info-events-00: package negotiation
> 
> I would offer the likelihood of a UAC only half implementing 
> Info Packages is about 00.000% (five zeros, anyone?).  I 
> cannot imagine anyone expending the effort to implement Info 
> Packages but not use them.
> 
> If the UAS is a legacy device, the UAC will detect it from 
> the absence of Send/Recv-Info headers.
> 
> If the UAC is a legacy device, the UAS will detect it from 
> the absence of Send/Recv-Info headers.
> 
> Since I will soon make it clear a conforming UAC can send a 
> legacy INFO, half negotiation is a non-issue.
> 
> For example, let's say it's two weeks from now and I've 
> published the update to RFC 3398 to use Info Packages. Either 
> the implementor will implement the full ISUP package, or not. 
> It just does not make sense to do half the job, since 90% of 
> the job gets done when one does the first half. If one side 
> does not do Info Packages, then presumably, in the interests 
> of legacy interoperability (and often because the code is 
> already written), the device falls back to legacy INFO/RFC 3398.
> 
> 3pcc? By the time you can list one header (Send or Recv), you 
> can list both.
> 
> Therefore, I would offer it is an implementation failure to 
> list only a Send-Info or Recv-Info header.
> 
> On Oct 22, 2008, at 5:36 AM, Christer Holmberg wrote:
> 
> >
> > Hi,
> >
> >> General issues with the negotiation mechanism:
> >>
> >> What happens if the initial INVITE by a UAC includes only 
> Send-Info 
> >> or
> > Recv-Info? Does that indicate a "half-legacy" device??? Or does it 
> > delay negotiation for one but not the other? Or does
> >> the presence of one mean the absence of the other is 
> equivalent to an
> > empty one?
> >>
> >> As I think about it, I don't think its really necessary to 
> treat the
> > absence of these headers as meaning "legacy". Treating the 
> absence of 
> > these headers as equivalent to their presence without
> >> any packages is sufficient to get the proper legacy behavior. The
> > tricky part is figuring out out when their absence *doesn't* mean 
> > that, which is significant only in the non-legacy case. In
> >> particular, when they aren't present in INVITE it means 
> deferral of 
> >> the
> > "offer" to the UAS. And possibly absence in an UPDATE means "don't 
> > renegotiate"???
> >
> > I don't think the presence, or absence, of the S/R-Info 
> headers should 
> > in any way be connected to legacy in any way. A UA can be legacy no 
> > matter if the headers are present, or not present, but that is all 
> > done based on "configuration", as described in the draft.
> >
> > So, if a UAC only included Send-Info, it means that it only 
> supports 
> > sending of Info packages. Then, it may, or may not, also support 
> > legacy INFO usages, but that is completely separated.
> >
> >
> >> I'm confused by the three way negotiation of info packages in
> > INVITE/2xx/ACK. Its allowed when the Send-Info/Recv-Info are in the
> > INVITE, but not when they are deferred to the INVITE response,
> >> or when they are conveyed in UPDATE and its response. If 
> the three  
> >> way
> > handshake is needed to seal the deal, then those other options  
> > should be
> > off the table. But the "deferred offer" of these
> >> is really needed, so it can't be off the table. Or is this just an
> > extra benefit that can be exploited when possible?
> >>
> >> Also, I don't see any provision for additional round(s) of  
> >> negotiation
> > before 2xx via PRACK and UPDATE, though there is provision for
> > additional "half-negotiations" via provisional responses
> >> and the final response. Given the parallels with O/A, I'd 
> prefer to  
> >> see
> > them more aligned in this regard, though I can be talked out of that
> > with a good argument.
> >
> > I agree (I think :). The negotiation whould be 2-way. Then, based on
> > what the UAC gets from the UAS, it may send a PRACK/UPDATE/re-INVITE
> > with a new set of supported Info packages, but that is a new 2-way
> > negotiation transaction.
> >
> >
> >> I'd also like to take advantage of the lessons that have 
> been learned
> > with O/A and nail down more of the semantics now. One issue 
> that leaps
> > to mind in that regard is what happens if we start
> >> to negotiate info packages in a reINVITE and then the 
> reINVITE fails?
> >
> > That's a good point.
> >
> > I think we should use the same rule as for offer/answer. Because,  
> > assume
> > I send you a new set of packages in a re-INVITE, and you send me  
> > back a
> > set in a 18x. Then we may start using info packages based on that
> > negotiation long before the re-INVITE is rejected.
> >
> >> IMO what is needed is a state model for this stuff, added to the  
> >> state
> > for an invite-dialog-usage. This state should determine 
> which packages
> > may be sent, and which should be received without
> >> error. We should be very clear about exactly which events cause  
> >> changes
> > to this state.
> >>
> >> Even then there are race conditions that need to be clarified. For
> >> instance: Suppose, as a result of an INVITE/1xx exchange between  
> >> Alice
> > and Bob, that packages P & Q are allowed to be sent from 
> Alice to Bob.
> >> Alice then sends an INFO with package Q, and at the same time Bob  
> >> sends
> > a 2xx that only allows the receipt of package P. Then Bob 
> receives the
> > INFO with package Q. What should happen?
> >>
> >> Another issue is that if the Send-Info/Recv-Info contents change in
> > subsequent 1xx responses to the same INVITE, the UAS has no 
> guarantee
> > that they are received. So any reduction in what can be
> >> received cannot be counted upon until the 2xx/ACK.
> >
> > True. But, I wonder whether this will really be a real-life problem.
> >
> > And, we could a response code (4xx Info package not supported),  
> > which is
> > used by the UAS if it receives an info package which it doesn't  
> > support.
> > Then the UAC knows.
> >
> > Regards.
> >
> > Christer
> >
> > _______________________________________________
> > Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol
> > Use sip-implementors@cs.columbia.edu for questions on current sip
> > Use sipping@ietf.org for new developments on the application of sip
> 
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 31 06:35:51 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B076D3A6896;
	Fri, 31 Oct 2008 06:35:51 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4B2063A67ED
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 06:35:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.392
X-Spam-Level: 
X-Spam-Status: No, score=-6.392 tagged_above=-999 required=5 tests=[AWL=0.207, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id i2c8ifJLdkrx for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 06:35:49 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id C5FEC3A6896
	for <SIP@ietf.org>; Fri, 31 Oct 2008 06:35:48 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,522,1220227200"; d="scan'208";a="26340670"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 31 Oct 2008 13:35:47 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9VDZldS002442; 
	Fri, 31 Oct 2008 09:35:47 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9VDZl8n002838;
	Fri, 31 Oct 2008 13:35:47 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 09:35:47 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 09:35:46 -0400
Message-ID: <490B09B2.4020202@cisco.com>
Date: Fri, 31 Oct 2008 09:35:46 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <322862FF-3683-465F-B1A0-8C619A5D60E1@standardstrack.com>
	<CA9998CD4A020D418654FCDEF4E707DF083CCFDD@esealmw113.eemea.ericsson.se>
	<490A52E2.9050504@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF08B60752@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF08B60752@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 31 Oct 2008 13:35:46.0747 (UTC)
	FILETIME=[9493A0B0:01C93B5D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5620; t=1225460147;
	x=1226324147; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Proposal=20for=20multiple=20INF
	O=20bodies=20in=20an=20INFO |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=jrUJPXW+PMDnKmLpAbNZ3U9HEOiIhMCRPbCwY9toKoQ=;
	b=ZRITdno2q2sJIht6mKXDYCG3NU0DPqmPk9LyjCdNlRNTTejsIZTgzYDuBp
	bKkoOqz7kIsIKSTgc4AFDa62RUehV+9B2GyAi8m27EhqG1qAA0yBesDCDnLD
	bl3I1epb3y;
Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: IETF SIP List <SIP@ietf.org>
Subject: Re: [Sip] Proposal for multiple INFO bodies in an INFO
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Either way can allow multiple. The means for expressing it are somewhat 
different, but not of consequence.

	Thanks,
	Paul

Christer Holmberg wrote:
> Hi,
> 
> Erick says that once we are able to indicate which mime contains the
> info package, we would be able to allow multiple info packages.
> 
> For, that would of course require that we either allow multiple
> Info-Package headers, or that a single header can list multiple info
> packages.
> 
> Regards,
> 
> Christer
> 
>> -----Original Message-----
>> From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
>> Sent: 31. lokakuuta 2008 2:36
>> To: Christer Holmberg
>> Cc: Eric Burger; IETF SIP List
>> Subject: Re: [Sip] Proposal for multiple INFO bodies in an INFO
>>
>> I am ok with either way.
>>
>> I think using C-D follows the precedent of INVITE for finding 
>> "its body part" via C-D of "session".
>>
>> 	Thanks,
>> 	Paul
>>
>> Christer Holmberg wrote:
>>> Hi Erick,
>>>  
>>> I am not your suggestion of using CID for Info packages is 
>> what has been discussed (I may be wrong, of course).
>>>  
>>> I think what Paul was proposing was to have a 
>> Content-Disposition value indicating that a particular body 
>> shall be treated as in info package.
>>>  
>>> INFO .....
>>> To: ....
>>> From: ....
>>> Info-Package: foo
>>> Content-Type: application/foo
>>> Content-Dispotistion: info
>>> ...
>>>
>>> <foo body>
>>>
>>>
>>> Multipart mixed example with indirect content:
>>>
>>> INFO ....
>>> To: ....
>>> From: ....
>>> Info-Package: foo
>>> Content-Type: multipart/mixed;boundary="theboundary"
>>> ...
>>>
>>> --theboundary
>>> Content-Type: application/mumble
>>> Content-Disposition: whatever
>>>
>>> <mumble body>
>>>
>>> --theboundary
>>> Content-Type: application/foo
>>> Content-Disposition: info
>>>
>>> <foo body>
>>>
>>> --theboundary--
>>>
>>>  
>>>  
>>> Regards,
>>>  
>>> Christer
>>>
>>> ________________________________
>>>
>>> From: sip-bounces@ietf.org on behalf of Eric Burger
>>> Sent: Thu 30/10/2008 19:29
>>> To: IETF SIP List
>>> Subject: [Sip] Proposal for multiple INFO bodies in an INFO
>>>
>>>
>>>
>>> Good thing I waited 10 days...
>>>
>>> Initially, I was very swayed by the argument that things would be 
>>> much, much easier if we restricted an INFO request to a 
>> single Info- 
>>> Package.
>>>
>>> However, and especially as the last person to touch RFC 4483, I can 
>>> see the argument that *any* SIP message can end up with a 
>> multipart/ 
>>> mime body, even if you think you can limit it to just your stuff, 
>>> because the UA can always have a content indirection pointer in the 
>>> header pointing to a mime body part.
>>>
>>> Therefore, even if we restrict an INFO request to carry a 
>> single Info- 
>>> Package, we need a mechanism to uniquely identify and, at the SIP 
>>> header level, indicate which body part belongs to the package.
>>>
>>> I would offer once we solve that, we also get multiple INFO request 
>>> bodies for free.
>>>
>>> I would also offer that since INFO does not change SIP state, which 
>>> means there is not even a concept of a message succeeding 
>> but the INFO 
>>> body doing something that "fails", the objection that it 
>> would be hard 
>>> for a UA to report on one body "failing" with another body 
>>> "succeeding" is a non-issue.  Yes, this does mean that you 
>> cannot use 
>>> INFO to tunnel IP.  See RFC 3252 for more on this.  I do 
>> not see this 
>>> as a problem.
>>>
>>> Therefore, on to the solution.  We use the MIME approach.  The body 
>>> parts get tagged with Content-IDs. The Info-Package has a 
>> parameter, 
>>> CID, which points to the body part.  The ONLY question I have is 
>>> whether we should simply mandate always having this 
>> parameter to make 
>>> the protocol and parser easier, but a small burden on UAC's that 
>>> really are only sending a single body.  Other than that, 
>> the mechanism 
>>> looks like:
>>>
>>> INFO .....
>>> To: ....
>>> From: ....
>>> Info-Package: foo
>>> Content-Type: application/foo;cid=this
>>> Content-Id: this
>>> ...
>>>
>>> <foo body>
>>>
>>>
>>>
>>> Multipart mixed example with indirect content:
>>>
>>> INFO ....
>>> To: ....
>>> From: ....
>>> Info-Package: foo;cid=abcd1234zz
>>> Mumble: <cid:abcd9999qq>
>>> Content-Type: multipart/mixed;boundary="theboundary"
>>> ...
>>>
>>> --theboundary
>>> Content-Type: application/mumble
>>> Content-Id: abcd9999qq
>>> ...
>>>
>>> <mumble stuff>
>>>
>>> --theboundary
>>> Content-Type: application/foo
>>> Content-Id: abcd1234zz
>>>
>>> <foo body>
>>>
>>> --theboundary--
>>>
>>>
>>>
>>>
>>> Multiple Info Packages follow. Note that by using 
>> Content-Id, order is 
>>> irrelevant.
>>>
>>> INFO ....
>>> To: ....
>>> From: ....
>>> Info-Package: foo;cid=abcd1234zz
>>> Info-Package: bar;cid=wxyz9876
>>> Content-Type: multipart/mixed;boundary="theboundary"
>>> ...
>>>
>>> --theboundary
>>> Content-Type: application/bar
>>> Content-Id: wxyz9876
>>> ...
>>>
>>> <bar stuff>
>>>
>>> --theboundary
>>> Content-Type: application/foo
>>> Content-Id: abcd1234zz
>>>
>>> <foo body>
>>>
>>> --theboundary--
>>>
>>> _______________________________________________
>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>> This list is for NEW development of the core SIP Protocol Use 
>>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>>> sipping@ietf.org for new developments on the application of sip
>>>
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 31 06:39:12 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0D7BF28C1F7;
	Fri, 31 Oct 2008 06:39:12 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0E3F228C246
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 06:39:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.418
X-Spam-Level: 
X-Spam-Status: No, score=-6.418 tagged_above=-999 required=5 tests=[AWL=0.181, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Uyj4LeESv9QL for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 06:39:09 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148])
	by core3.amsl.com (Postfix) with ESMTP id 0BBEC28C1F7
	for <sip@ietf.org>; Fri, 31 Oct 2008 06:39:08 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,522,1220227200"; d="scan'208";a="26341250"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 31 Oct 2008 13:39:07 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m9VDd7Xj018031; 
	Fri, 31 Oct 2008 09:39:07 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9VDd7Ax004003;
	Fri, 31 Oct 2008 13:39:07 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 09:39:07 -0400
Received: from [161.44.174.168] ([161.44.174.168]) by
	xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 09:39:06 -0400
Message-ID: <490B0A7A.6040304@cisco.com>
Date: Fri, 31 Oct 2008 09:39:06 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <20081020231502.43DCA3A69EF@core3.amsl.com><48FDECB5.3030607@cisco.com><81521DF0-2666-4500-BE62-412FBB6966A7@standardstrack.com><5D1A7985295922448D5550C94DE291800245C378@DEEXC1U01.de.lucent.com>
	<490A54A8.7070405@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF08B60791@esealmw113.eemea.ericsson.se>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF08B60791@esealmw113.eemea.ericsson.se>
X-OriginalArrivalTime: 31 Oct 2008 13:39:06.0981 (UTC)
	FILETIME=[0BECE950:01C93B5E]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2311; t=1225460347;
	x=1226324347; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20[Sip]=20Legacy=20Info=20Package=20Regis
	tration |Sender:=20
	|To:=20Christer=20Holmberg=20<christer.holmberg@ericsson.co m>;
	bh=5kFudcKMJpmlDJUa7bMmk1J7T+3HjidQmnlwjtHydWI=;
	b=wpf7bVcfkY+6UBJyt50pviK+EbJ4uR9miO53zQTeUKV++rWVh5/IpMfa4k
	A2Cs2R8LKcPYTUdMT4nHNAZoc3K54dLZdOsqb197D/DCn7OKOJpS8ZxVTPZ1
	qN+Fv/NAzI;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
Cc: SIP IETF <sip@ietf.org>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>
Subject: Re: [Sip] Legacy Info Package Registration
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Now that you mention it, allowing multiple definitions for the same C-T 
probably does make sense, though we hope there aren't any such cases.
This is only for legacy, so we won't be making the problem worse that way.

The advantage of a registry is that there isn't a deadline for when 
things are added to it. If another legacy usage is discovered in a few 
years, it can be added to a registry. But if we just put the list in a 
document, then it only contains those we find before the doc is finalized.

	Thanks,
	Paul

Christer Holmberg wrote:
> Hi,
> 
> I guess one option is to e.g. have an annex, where we for legacy usages
> list Content-Type and a reference (if available) to where the usage is
> described.
> 
> If there are different legacy usages with the same Content-Type, I don't
> think we should deal with that. That would just show the need for the
> info packages.
> 
> Also, I don't think we would need to collect each and every legacy usage
> out there (I am not sure we would manage to do that even with a
> registry).
> 
> Regards,
> 
> Christer
> 
> 
> 
> 
>> -----Original Message-----
>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
>> Behalf Of Paul Kyzivat
>> Sent: 31. lokakuuta 2008 2:43
>> To: DRAGE, Keith (Keith)
>> Cc: SIP IETF
>> Subject: Re: [Sip] Legacy Info Package Registration
>>
>>
>>
>> DRAGE, Keith (Keith) wrote:
>>
>>> At the moment I am also unsure what criteria we would use for 
>>> identifing a legacy usage, apart from some rather vague textual 
>>> description. It after all does not have a package name.
>> With legacy usage, the only distinguishing characteristic 
>> that I am aware has ever been used is Content-Type. So I 
>> think the registry has to be based on Content-Type, probably 
>> on a FCFS basis. (Though perhaps there might be need of an 
>> appeals process if there are conflicting usages. But I doubt 
>> we will find that.)
>>
>> 	Paul
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol Use 
>> sip-implementors@cs.columbia.edu for questions on current sip 
>> Use sipping@ietf.org for new developments on the application of sip
>>
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 31 07:04:17 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BC7A428C1E8;
	Fri, 31 Oct 2008 07:04:17 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 109E13A6A20
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 07:04:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WJC0POrAjjqW for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 07:04:15 -0700 (PDT)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29])
	by core3.amsl.com (Postfix) with ESMTP id 2468628C271
	for <sip@ietf.org>; Fri, 31 Oct 2008 07:04:15 -0700 (PDT)
Received: by yw-out-2324.google.com with SMTP id 3so514999ywj.49
	for <sip@ietf.org>; Fri, 31 Oct 2008 07:04:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:cc:in-reply-to:mime-version:content-type
	:content-transfer-encoding:content-disposition:references;
	bh=iP7Zp26wodkm3vA9QTthLX8NkTdoQFHrq0LusSIQ840=;
	b=HQMJ0RPsU2dqgMoqH2a+IIMkeEtm8aiP8RGY1EtYF+QbQPyCn4xaX5p2Xr2klJUnmk
	TGSgu6z1ymyzitO1HIifiRWQqCL80Gq+jPzO3A67RMlwXLeInBJcNjzglqhNkpGvlpzE
	Ffgpy/KraT16Qn/vZMx7d5tLB9yRA7XT/r0Jc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=ZScfKRtOle1r+6Tu0QRqxmL2SzEs3xLKW4m4AG+SKROYsOGbcz1/zOIKWV+ldCpaUp
	J/dg5uFfNU+5So7jcy6GJIP6jOyVb9XxlxwMAaE3rjVxM8rVY/Ohjy1gYt5EH/jU6ucM
	KKnS3e8debdLR8EE3+XiMyKE5ENmE9Wkoi/WU=
Received: by 10.90.29.13 with SMTP id c13mr10103707agc.68.1225461852366;
	Fri, 31 Oct 2008 07:04:12 -0700 (PDT)
Received: by 10.90.114.2 with HTTP; Fri, 31 Oct 2008 07:04:12 -0700 (PDT)
Message-ID: <618e24240810310704j17030e14y9b46a79b0103cdd@mail.gmail.com>
Date: Fri, 31 Oct 2008 15:04:12 +0100
From: "=?UTF-8?Q?Victor_Pascual_=C3=81vila?=" <victor.pascual.avila@gmail.com>
To: "=?UTF-8?Q?I=C3=B1aki_Baz_Castillo?=" <ibc@aliax.net>
In-Reply-To: <cc1f582e0810310603w21a4cc7fga1d978c0fb4f5bd7@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>
	<200810290236.m9T2akDN55854559@shell01.TheWorld.com>
	<033d01c93979$b3cf1990$c3f0200a@cisco.com>
	<618e24240810291636q6986570as674cbe65e49a8c7b@mail.gmail.com>
	<490ADE61.4030005@voip.co.uk>
	<cc1f582e0810310603w21a4cc7fga1d978c0fb4f5bd7@mail.gmail.com>
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR
	IdentityVErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

SGkgScOxYWtpLAoKT24gRnJpLCBPY3QgMzEsIDIwMDggYXQgMjowMyBQTSwgScOxYWtpIEJheiBD
YXN0aWxsbyA8aWJjQGFsaWF4Lm5ldD4gd3JvdGU6Cj4gMjAwOC8xMC8zMSBNaWNoYWVsIFByb2N0
ZXIgPG1pY2hhZWxAdm9pcC5jby51az46Cj4KPj4+IFNoYWxsIERFUklWRSBiZSBleHRlbmRlZCB0
byBzdXBwb3J0IG5vbi1JTlZJVEUgcmVxdWVzdHMgKGUuZy4gTUVTU0FHRSkKPj4KPj4gSSdtIG5v
dCBzdXJlIGl0IGNhbi4gIFJGQzQyMzUgaXMgZGVmaW5lZCBmb3IgSU5WSVRFLWluaXRpYXRlZCBk
aWFsb2cKPj4gdXNhZ2VzIG9ubHkuICBZZXMsIGl0IGNvdWxkIGJlIGV4dGVuZGVkLCBidXQgSSdt
IG5vdCBjb252aW5jZWQgdGhhdCBpcwo+PiBuZWNlc3NhcmlseSB0aGUgYmVzdCB3YXkgZm9yd2Fy
ZCBmcm9tIGhlcmUhCj4KPiBBbHNvIG5vdGUgdGhhdCBNRVNTQUdFIGRvZXNuJ3QgZXN0YWJsaXNo
IGEgZGlhbG9nLCBpdCBqdXN0IGFuCj4gaW5kZXBlbmRlbnQgdHJhbnNhY3Rpb24uCgpEbyB5b3Ug
bWVhbiB0aGF0IHdlIHNob3VsZCBwcm92aWRlIGEgcmVhc29uYWJsZSBhc3N1cmFuY2UgdGhhdCB0
aGUKIkNhbGxlci1JRCIgaXMgbm90IG1pc2xlYWRpbmcgT05MWSBmb3IgZGlhbG9nLWZvcm1pbmcg
cmVxdWVzdHM/CgpDaGVlcnMsCi0tIApWaWN0b3IgUGFzY3VhbCDDgXZpbGEKX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KU2lwIG1haWxpbmcgbGlzdCAgaHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zaXAKVGhpcyBsaXN0IGlzIGZvciBO
RVcgZGV2ZWxvcG1lbnQgb2YgdGhlIGNvcmUgU0lQIFByb3RvY29sClVzZSBzaXAtaW1wbGVtZW50
b3JzQGNzLmNvbHVtYmlhLmVkdSBmb3IgcXVlc3Rpb25zIG9uIGN1cnJlbnQgc2lwClVzZSBzaXBw
aW5nQGlldGYub3JnIGZvciBuZXcgZGV2ZWxvcG1lbnRzIG9uIHRoZSBhcHBsaWNhdGlvbiBvZiBz
aXA=


From sip-bounces@ietf.org  Fri Oct 31 07:07:25 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 33A733A6BFE;
	Fri, 31 Oct 2008 07:07:25 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E60663A6BFE
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 07:07:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level: 
X-Spam-Status: No, score=-6.382 tagged_above=-999 required=5 tests=[AWL=0.217, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vjyNxQHHB6b1 for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 07:07:22 -0700 (PDT)
Received: from zcars04f.nortel.com (zcars04f.nortel.com [47.129.242.57])
	by core3.amsl.com (Postfix) with ESMTP id A4A063A6784
	for <sip@ietf.org>; Fri, 31 Oct 2008 07:07:22 -0700 (PDT)
Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com
	[47.103.123.72])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m9VE72Z22676; Fri, 31 Oct 2008 14:07:03 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 31 Oct 2008 09:03:28 -0500
Message-ID: <F66D7286825402429571678A16C2F5EE0612C817@zrc2hxm1.corp.nortel.com>
In-Reply-To: <490A8D4F.7030509@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Info Package Versioning
Thread-Index: Ack7E5/mO9ybkB9yT+qXqbf5ybQyMQATckuA
References: <48FDEAD8.8010803@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>	<4901BA73.1010700@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>	<4901C2B1.1050209@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>	<4901D025.6060302@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>	<490239C8.3020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>	<4902467E.3010603@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFBA@esealmw113.eemea.ericsson.se>	<4905B23F.10609@cisco.com><CA9998CD4A020D418654FCDEF4E707DF089F589E@esealmw113.eemea.ericsson	.se><49	05CAE2.9020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF05C0F8FF@esealmw113.eemea.ericss	on.se><49060DD4.7070804@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF05C0F906@esealmw113.eemea.ericsson.se><9F7BFBEE-A96A-4E33-B3DB-9074DE2FE579@standardstrack.com>
	<490A8D4F.703! 0509@cisc o.com>
From: "Mary Barnes" <mary.barnes@nortel.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>,
	"Eric Burger" <eburger@standardstrack.com>
Cc: SIP IETF <sip@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [Sip] Info Package Versioning
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Ditto.

-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Paul Kyzivat
Sent: Thursday, October 30, 2008 11:45 PM
To: Eric Burger
Cc: SIP IETF; Christer Holmberg
Subject: Re: [Sip] Info Package Versioning

> Yet another poll:
> 
> [ ] We must have abstract versioning as part of the Info Framework 
> document
> 
> [ ] We do not need to have abstract versioning, as it does not do 
> anything for anyone
> 
> [x] We do not need abstract versioning, but it would be worthwhile 
> including some text,
>     like what is above, to show people how to do it.
> 
> [ ] Something else? _____________________________________
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol Use
sip-implementors@cs.columbia.edu for questions on current sip Use
sipping@ietf.org for new developments on the application of sip
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 31 07:11:08 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2908428C260;
	Fri, 31 Oct 2008 07:11:08 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E360228C1E9
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 07:11:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.099
X-Spam-Level: 
X-Spam-Status: No, score=-6.099 tagged_above=-999 required=5
	tests=[AWL=-0.100, BAYES_00=-2.599, J_CHICKENPOX_55=0.6,
	RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id hBV-BA+4MLHP for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 07:11:02 -0700 (PDT)
Received: from zcars04f.nortel.com (zcars04f.nortel.com [47.129.242.57])
	by core3.amsl.com (Postfix) with ESMTP id AF42F28C132
	for <sip@ietf.org>; Fri, 31 Oct 2008 07:11:02 -0700 (PDT)
Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com
	[47.103.123.72])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	m9VEAuZ23068; Fri, 31 Oct 2008 14:10:56 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 31 Oct 2008 09:07:30 -0500
Message-ID: <F66D7286825402429571678A16C2F5EE0612C827@zrc2hxm1.corp.nortel.com>
In-Reply-To: <490B0A7A.6040304@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Legacy Info Package Registration
Thread-Index: Ack7Xhy4MKCEsN4dTRO8oUMCpew/LgAA2ZGg
References: <20081020231502.43DCA3A69EF@core3.amsl.com><48FDECB5.3030607@cisco.com><81521DF0-2666-4500-BE62-412FBB6966A7@standardstrack.com><5D1A7985295922448D5550C94DE291800245C378@DEEXC1U01.de.lucent.com><490A54A8.7070405@cisco.com><CA9998CD4A020D418654FCDEF4E707DF08B60791@esealmw113.eemea.ericsson.se>
	<490B0A7A.6040304@cisco.com>
From: "Mary Barnes" <mary.barnes@nortel.com>
To: "Paul Kyzivat" <pkyzivat@cisco.com>,
	"Christer Holmberg" <christer.holmberg@ericsson.com>
Cc: SIP IETF <sip@ietf.org>, "DRAGE,
	Keith \(Keith\)" <drage@alcatel-lucent.com>
Subject: Re: [Sip] Legacy Info Package Registration
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Per your last point, this is why I "voted" as I did. I think it's
important if we do document legacy to have a registry, so it's much
easier to find. Unfortunately, when folks read drafts, they usually read
only the sections that are related to why they picked up the doc in the
first place and don't always comprehensively review the doc. 

Based on some offline discussions, I think the legacy issue is not as
bad as I had thought it would be. But, still a registry is most useful.
And, again, we don't want this doc held up while we go searching for
those. And, we don't want to have to update this doc later to add more
(or worse yet, have them end up in a separate doc). The addition of the
legacy usages should be quick and easy and maybe we can just designate a
prime as first point of contact to offload chairs.

Mary. 

-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Paul Kyzivat
Sent: Friday, October 31, 2008 8:39 AM
To: Christer Holmberg
Cc: SIP IETF; DRAGE,Keith (Keith)
Subject: Re: [Sip] Legacy Info Package Registration

Now that you mention it, allowing multiple definitions for the same C-T
probably does make sense, though we hope there aren't any such cases.
This is only for legacy, so we won't be making the problem worse that
way.

The advantage of a registry is that there isn't a deadline for when
things are added to it. If another legacy usage is discovered in a few
years, it can be added to a registry. But if we just put the list in a
document, then it only contains those we find before the doc is
finalized.

	Thanks,
	Paul

Christer Holmberg wrote:
> Hi,
> 
> I guess one option is to e.g. have an annex, where we for legacy 
> usages list Content-Type and a reference (if available) to where the 
> usage is described.
> 
> If there are different legacy usages with the same Content-Type, I 
> don't think we should deal with that. That would just show the need 
> for the info packages.
> 
> Also, I don't think we would need to collect each and every legacy 
> usage out there (I am not sure we would manage to do that even with a 
> registry).
> 
> Regards,
> 
> Christer
> 
> 
> 
> 
>> -----Original Message-----
>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of

>> Paul Kyzivat
>> Sent: 31. lokakuuta 2008 2:43
>> To: DRAGE, Keith (Keith)
>> Cc: SIP IETF
>> Subject: Re: [Sip] Legacy Info Package Registration
>>
>>
>>
>> DRAGE, Keith (Keith) wrote:
>>
>>> At the moment I am also unsure what criteria we would use for 
>>> identifing a legacy usage, apart from some rather vague textual 
>>> description. It after all does not have a package name.
>> With legacy usage, the only distinguishing characteristic that I am 
>> aware has ever been used is Content-Type. So I think the registry has

>> to be based on Content-Type, probably on a FCFS basis. (Though 
>> perhaps there might be need of an appeals process if there are 
>> conflicting usages. But I doubt we will find that.)
>>
>> 	Paul
>> _______________________________________________
>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol Use 
>> sip-implementors@cs.columbia.edu for questions on current sip Use 
>> sipping@ietf.org for new developments on the application of sip
>>
> 
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol Use
sip-implementors@cs.columbia.edu for questions on current sip Use
sipping@ietf.org for new developments on the application of sip
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip


From sip-bounces@ietf.org  Fri Oct 31 07:13:11 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 125DE28C132;
	Fri, 31 Oct 2008 07:13:11 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E209E3A682F
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 07:13:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.391
X-Spam-Level: 
X-Spam-Status: No, score=-6.391 tagged_above=-999 required=5 tests=[AWL=0.207, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id VgbSvxtRdHq6 for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 07:13:08 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56])
	by core3.amsl.com (Postfix) with ESMTP id D6FDF3A6784
	for <sip@ietf.org>; Fri, 31 Oct 2008 07:13:07 -0700 (PDT)
Received: from zrc2hxm1.corp.nortel.com (zrc2hxm1.corp.nortel.com
	[47.103.123.72])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	m9VEA5q01541; Fri, 31 Oct 2008 14:10:05 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 31 Oct 2008 09:09:37 -0500
Message-ID: <F66D7286825402429571678A16C2F5EE0612C832@zrc2hxm1.corp.nortel.com>
In-Reply-To: <750BBC72E178114F9DC4872EBFF29A5B05B82208@ZMY16EXM66.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Sip] Comments on
	draft-saklikar-comm-diversion-notification-00.txt
Thread-Index: Ack7STTU7Ays1SkcQli2PfLI8+1XCwADmf0QAAKk+pA=
References: <750BBC72E178114F9DC4872EBFF29A5B05B82208@ZMY16EXM66.ds.mot.com>
From: "Mary Barnes" <mary.barnes@nortel.com>
To: "Avasarala Ranjit-A20990" <ranjit@motorola.com>, <sip@ietf.org>
Subject: Re: [Sip] Comments on
	draft-saklikar-comm-diversion-notification-00.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0287742934=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0287742934==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C93B62.C8EBDC7F"

This is a multi-part message in MIME format.

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

Folks, this note was also posted on SIPPING WG mailing list, which is
the right place for the discussion of this doc. So, please don't reply
to this thread, but rather please reply to SIPPING WG posting.
=20
Thanks,
Mary
SIPPING WG co-chair.=20

________________________________

From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Avasarala Ranjit-A20990
Sent: Friday, October 31, 2008 7:54 AM
To: sip@ietf.org
Subject: [Sip] Comments on
draft-saklikar-comm-diversion-notification-00.txt




Hi=20

This draft on communication diversion notification info proposes a SIP
based XML event package for notifying subscribers of call diversions
that occur on their behalf in the network. Please review the draft and
comment

Link for the draft:
http://www.ietf.org/internet-drafts/draft-saklikar-comm-diversion-notifi
cation-00.txt
<http://www.ietf.org/internet-drafts/draft-saklikar-comm-diversion-notif
ication-00.txt> =20

Thanks=20

Regards=20
Ranjit=20


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Comments on =
draft-saklikar-comm-diversion-notification-00.txt</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3395" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D671460814-31102008>Folks,=20
this note was also posted on SIPPING WG mailing list, which is the right =
place=20
for the discussion of this doc. So, please don't reply to this thread, =
but=20
rather please reply to SIPPING WG posting.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D671460814-31102008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D671460814-31102008>Thanks,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D671460814-31102008>Mary</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D671460814-31102008>SIPPING WG co-chair. </SPAN></FONT></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> sip-bounces@ietf.org=20
[mailto:sip-bounces@ietf.org] <B>On Behalf Of </B>Avasarala=20
Ranjit-A20990<BR><B>Sent:</B> Friday, October 31, 2008 7:54 =
AM<BR><B>To:</B>=20
sip@ietf.org<BR><B>Subject:</B> [Sip] Comments on=20
draft-saklikar-comm-diversion-notification-00.txt<BR></FONT><BR></DIV>
<DIV></DIV><!-- Converted from text/rtf format --><BR>
<P><FONT face=3DArial color=3D#0000ff size=3D2>Hi</FONT> </P>
<P><FONT face=3DArial color=3D#0000ff size=3D2>This draft on =
communication diversion=20
notification info proposes a SIP based XML event package for notifying=20
subscribers of call diversions that occur on their behalf in the =
network. Please=20
review the draft and comment</FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2>Link for the =
draft:&nbsp;</FONT> <A=20
href=3D"http://www.ietf.org/internet-drafts/draft-saklikar-comm-diversion=
-notification-00.txt"><U></U><U><FONT=20
face=3DArial color=3D#0000ff=20
size=3D2>http://www.ietf.org/internet-drafts/draft-saklikar-comm-diversio=
n-notification-00.txt</FONT></U></A>=20
</P>
<P><FONT face=3DArial color=3D#0000ff size=3D2>Thanks</FONT> </P>
<P><FONT face=3DArial color=3D#0000ff size=3D2>Regards</FONT> <BR><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Ranjit</FONT> </P></BODY></HTML>

------_=_NextPart_001_01C93B62.C8EBDC7F--

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

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


From sip-bounces@ietf.org  Fri Oct 31 08:24:59 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CA2DD3A6994;
	Fri, 31 Oct 2008 08:24:59 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 12E643A6994
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 08:24:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XTtZAMaeGXfX for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 08:24:57 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 282483A67F3
	for <sip@ietf.org>; Fri, 31 Oct 2008 08:24:57 -0700 (PDT)
Received: from [75.68.119.237] (port=60190 helo=[192.168.15.102])
	by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1Kvvrn-0007Sg-1x; Fri, 31 Oct 2008 08:24:51 -0700
Message-Id: <ED59337D-3154-4CF1-A5EF-802A868F2D9E@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF08B6071B@esealmw113.eemea.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 31 Oct 2008 11:24:51 -0400
References: <48FDEAD8.8010803@cisco.com>	<093BE299-DB32-4012-AC94-405DE4D00FF9@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCF9B@esealmw113.eemea.ericsson.se>	<5CE22097-8807-48B3-A9AA-2EDD4588D4A7@softarmor.com>	<CA9998CD4A020D418654FCDEF4E707DF08955CCC@esealmw113.eemea.ericsson.se>	<4901BA73.1010700@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E1B4@esealmw113.eemea.ericsson.se>	<4901C2B1.1050209@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF0897E2CE@esealmw113.eemea.ericsson.se>	<4901D025.6060302@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB2@esealmw113.eemea.ericsson.se>	<490239C8.3020808@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFB4@esealmw113.eemea.ericsson.se>	<4902467E.3010603@cisco.com>	<CA9998CD4A020D418654FCDEF4E707DF083CCFBA@esealmw113.eemea.ericsson.se>	<4905B23F.10609@cisco.com><CA9998CD4A020D418654FCDEF4E707DF089F589E@esealmw113.eemea.ericsson
	.se> <49	05CAE2.9020808@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F8FF@esealmw113.eemea.ericss
	on.se> <49060DD4.7 070804@cisco.com>
	<CA9998CD4A020D418654FCDEF4E707DF05C0F906@esealmw113.eemea.ericsson.se>
	<9F7BFBEE-A96A-4E33-B3DB-9074DE2FE579@standardstrack.com>
	<CA9998CD4A020D418654FCDEF4E707DF08B6071B@esealmw113.eemea.ericsson.se>
X-Mailer: Apple Mail (2.929.2)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] Info Package Versioning
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1004895287=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--===============1004895287==
Content-Type: multipart/signed; boundary=Apple-Mail-95-198872114; micalg=sha1; protocol="application/pkcs7-signature"


--Apple-Mail-95-198872114
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

I'm leaning toward "inside the INFO packet", or, ad hoc. My reasoning  
is if Y is X with a little more, if you advertise Y, would X  
understand it? X would probably say, "hmmm - version greater than me,  
so I should reject it." That doesn't help.

On the other hand, if you are on the XML bandwagon, you could always  
have backwards compatible stuff in your schema.


On Oct 31, 2008, at 8:59 AM, Christer Holmberg wrote:

>
> Hi,
>
> Before I give my vote, I just want to clarify a little what I meant.
>
> Assume you have package A, which can carry some information.
>
> Then you figure out you need a new information element, but all the  
> old
> information still remains exactly the same. You create package B.
>
> Now, package B would be fully backward compatible with package A.
>
> But, if there is no versioning, and backward compability guidelines,  
> I would
> have to indicate explicit support of both package A and B.
>
> Of course, if package B is NOT backward compatible, it would have to  
> be a
> compeltely new package.
>
> Another option is of course to deal with these kind of things inside  
> the
> info packet itself.
>
> Regards,
>
> Christer
>
>
>
>
>
>> -----Original Message-----
>> From: Eric Burger [mailto:eburger@standardstrack.com]
>> Sent: 30. lokakuuta 2008 18:53
>> To: Christer Holmberg
>> Cc: SIP IETF
>> Subject: Info Package Versioning
>>
>> Channeling Keith here: is there a real use case for package
>> versioning?
>>
>> I cannot imagine backwards-compatible packages. Once one
>> starts changing the stuff in an INFO package, it is a
>> different package. That is, rather than
>>
>>    Info-Package: foo-package;version=1
>>    Info-Package: foo-package;version=2
>>
>> You, in reality have:
>>
>>    Info-Package: foo-package
>>    Info-Package: something-like-foo-but-not-really-foo-anymore
>>
>> This is more especially so when one considers there is no
>> possibility of negotiating package versions, whereas there is
>> a possibility of negotiating different packages.
>>
>> For the one instance one could come up with in theory for
>> needing versioning, remember one does get to have an
>> arbitrary parameter:
>>
>>    Info-Package: foo-package               /* Version 1 */
>>    Info-Package: foo-package;bar        /* Version 2 */
>>
>>
>> Is this latter mechanism sufficient?
>>
>> Yet another poll:
>>
>> [ ] We must have abstract versioning as part of the Info
>> Framework document
>>
>> [ ] We do not need to have abstract versioning, as it does
>> not do anything for anyone
>>
>> [ ] We do not need abstract versioning, but it would be
>> worthwhile including some text,
>>     like what is above, to show people how to do it.
>>
>> [ ] Something else? _____________________________________
>>
>>
>>
>> On Oct 27, 2008, at 4:48 PM, Christer Holmberg wrote:
>>
>>> [snip]
>>>> The wording could be better. There are no explicit IANA
>>>> considerations
>>> about registering an INFO package. Its just implied here.
>> Its a little
>>> confusing here what is intended to be part of the
>>>> *definition* of a new package vs. what is intended to be in the
>>>> content
>>> of a particular package instance in an INFO message.
>>>
>>> We do need to have a section on what needs to be part of an info
>>> package definition. The mime type is one thing, for sure.
>>>
>>> I guess we should also look at what/if we can re-use from
>> SIP events.
>>>
>>> We also need to decide whether info packages should have a version
>>> number system. From experience I think that would be very useful.
>>>
>>> Info-Package: foo-package;version=1
>>>
>>> ...or something like that.
>> [snip]
>>
>>


--Apple-Mail-95-198872114
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGPTCCBjkw
ggUhoAMCAQICEC+VK1RLWxrF8KJZDR9k8p8wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYTAlVT
MQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VS
VFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQD
Ey1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwwHhcNMDgwODEz
MDAwMDAwWhcNMDkwODEzMjM1OTU5WjCB4TE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsg
LSBQRVJTT05BIE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9m
IHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDMg
Q29tb2RvIExpbWl0ZWQxFDASBgNVBAMTC0VyaWMgQnVyZ2VyMSkwJwYJKoZIhvcNAQkBFhplYnVy
Z2VyQHN0YW5kYXJkc3RyYWNrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMTF
RRoA4LgOACMFph0aomRC/UpqoA5C/d6DUTOvTMrYSEqkjwnU4zxDtBcHlcB4AxKAov00MYsUvEU4
loz7BHjfDjv76AIkcwu33VYQbzGmarVnyaXsVb6f/cyRL3fPT0VOVO2tQAEEgwg//CX0jN8Kn2jH
uXD/HEvko7cmpL3Pwevf3+DwB61v7ca79PpEZfn/WhaqRKA4uVNPj/JbieeaLo2v/0RJzrEElZK0
pHCqxiD3mQ8ossPkA9fUCSxLlbdMcPU3be5x8vt8Q8mYTXF5Z3d9RZmYrmNkvTQtdzVpfYWr/hgV
Xqm9tByOOAR+hoN3FKbubR/OrAHL9yDAd4sCAwEAAaOCAhwwggIYMB8GA1UdIwQYMBaAFImCZ33E
nSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBRDWgutb7b8R/L7G3Y3D+molAA3VzAOBgNVHQ8BAf8E
BAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJ
YIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEW
HWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMIGlBgNVHR8EgZ0wgZowTKBKoEiGRmh0dHA6
Ly9jcmwuY29tb2RvY2EuY29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRF
bWFpbC5jcmwwSqBIoEaGRGh0dHA6Ly9jcmwuY29tb2RvLm5ldC9VVE4tVVNFUkZpcnN0LUNsaWVu
dEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMGwGCCsGAQUFBwEBBGAwXjA2BggrBgEFBQcwAoYq
aHR0cDovL2NydC5jb21vZG9jYS5jb20vVVROQUFBQ2xpZW50Q0EuY3J0MCQGCCsGAQUFBzABhhho
dHRwOi8vb2NzcC5jb21vZG9jYS5jb20wJQYDVR0RBB4wHIEaZWJ1cmdlckBzdGFuZGFyZHN0cmFj
ay5jb20wDQYJKoZIhvcNAQEFBQADggEBAGeBR7NPCvrY3GQoIi49JOuciatY2r4st905Jw1etp6J
umFFWlaCBl11tFSclk/3S45B+lUv3SEvG4CEjUByPScprVmCqHR+y8BAQaB/CV+N1y14x3MbhJ+Z
8XDGKeUXuuyGd9w0l3/t/QPid6TRXQjQFrLPFs1IALuNpNiFMHEF/xFbMG1Z2vznR/gSPlePekoZ
TqcExIDBNZTBebpZqwAXzPpedNNOclbMLFLWDMOAozVRpkfjI0eiFsk8SF1Ho1Gb9Bx8DeG4peE2
KRVOR9FFnZZgBpFjXYRcglsMOSKCY8HgE+NGvbbqbrMoBV/BlYyxRXwfti71RL9Zs2Cq1eQxggP8
MIID+AIBATCBwzCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExh
a2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8v
d3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkNH2TynzAJBgUrDgMCGgUAoIICDTAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wODEwMzExNTI0NTFaMCMGCSqGSIb3
DQEJBDEWBBStLIv2fBD2R4DEIhRw0yr4go2UmjCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD
VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU
aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2
MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv
lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN
H2TynzANBgkqhkiG9w0BAQEFAASCAQBiq2nFWZpmqjQH0pxpoTYBxq7rKsG48Jd84WFm8LQJX1Ep
PdDWwYdmlu/s5EiMV8pdFqmakOR+TRjZSf4g43w91XBm/aK7yi3y1pg8m6j8HrrD8/brB7AWR9OI
My7TKu2LangNFQJlWnRb5u48mjBXF0YtlDQWFUaBEL80IABoOlfyc0YOr0TcbxXU+lT45mfN9G48
8K6JhWbUk89hP/gpkLqcS/gXtWSU2XoqjrNz1Y6Tl3V/0zZw2/OJoHPvG5PJBmeO+/NZH35HdC/N
+WCdw/NtGLhK8qLoHQ60GwAxdJtCkBv6JFE//z75nsIfffY6MfzbYZnxTjBN7ocCeCrsAAAAAAAA

--Apple-Mail-95-198872114--

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

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


From sip-bounces@ietf.org  Fri Oct 31 08:27:03 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D5F7F3A6C0C;
	Fri, 31 Oct 2008 08:27:03 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 443453A6A92
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 08:27:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BThZqC8cM3ao for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 08:27:01 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com
	[66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 0485C3A6BC0
	for <sip@ietf.org>; Fri, 31 Oct 2008 08:27:01 -0700 (PDT)
Received: from [75.68.119.237] (port=60199 helo=[192.168.15.102])
	by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <eburger@standardstrack.com>)
	id 1Kvvtl-0007kU-NI; Fri, 31 Oct 2008 08:26:54 -0700
Message-Id: <08FADB9E-F725-42AE-977B-257F00CAE88D@standardstrack.com>
From: Eric Burger <eburger@standardstrack.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
In-Reply-To: <CA9998CD4A020D418654FCDEF4E707DF08B607C8@esealmw113.eemea.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 31 Oct 2008 11:26:54 -0400
References: <48FDEC6B.8090006@cisco.com><CA9998CD4A020D418654FCDEF4E707DF0889EAE5@esealmw113.eemea.ericsson.se>
	<975C30B3-A80B-4A6D-9892-7946404F89B4@standardstrack.com>
	<CA9998CD4A020D418654FCDEF4E707DF08B607C8@esealmw113.eemea.ericsson.se>
X-Mailer: Apple Mail (2.929.2)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: SIP IETF <sip@ietf.org>
Subject: Re: [Sip] draft-ietf-sip-info-events-00: package negotiation
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1786380485=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--===============1786380485==
Content-Type: multipart/signed; boundary=Apple-Mail-96-198994776; micalg=sha1; protocol="application/pkcs7-signature"


--Apple-Mail-96-198994776
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Agreed.  I would offer that just about 100% of the implementations in  
the next 18 months that do New ISUP will support Old ISUP, AND...

If a UA supports new ISUP transport, the likelihood of that UA only  
supporting sending New INFO, but only receiving Old INFO, is zero.

On Oct 31, 2008, at 9:16 AM, Christer Holmberg wrote:

>
> Hi,
>
> A UA can support both legacy usages and INFO packages.
>
> For example, ISUP transport may have been implemented in a network  
> years
> ago, and now some new fancy Info package stuff starts to come  
> around. A
> UA which supports the new stuff will still have to support the old
> stuff.
>
> Regards,
>
> Christer
>
>
>
>> -----Original Message-----
>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On
>> Behalf Of Eric Burger
>> Sent: 30. lokakuuta 2008 19:07
>> To: Christer Holmberg
>> Cc: SIP IETF; Paul Kyzivat
>> Subject: Re: [Sip] draft-ietf-sip-info-events-00: package negotiation
>>
>> I would offer the likelihood of a UAC only half implementing
>> Info Packages is about 00.000% (five zeros, anyone?).  I
>> cannot imagine anyone expending the effort to implement Info
>> Packages but not use them.
>>
>> If the UAS is a legacy device, the UAC will detect it from
>> the absence of Send/Recv-Info headers.
>>
>> If the UAC is a legacy device, the UAS will detect it from
>> the absence of Send/Recv-Info headers.
>>
>> Since I will soon make it clear a conforming UAC can send a
>> legacy INFO, half negotiation is a non-issue.
>>
>> For example, let's say it's two weeks from now and I've
>> published the update to RFC 3398 to use Info Packages. Either
>> the implementor will implement the full ISUP package, or not.
>> It just does not make sense to do half the job, since 90% of
>> the job gets done when one does the first half. If one side
>> does not do Info Packages, then presumably, in the interests
>> of legacy interoperability (and often because the code is
>> already written), the device falls back to legacy INFO/RFC 3398.
>>
>> 3pcc? By the time you can list one header (Send or Recv), you
>> can list both.
>>
>> Therefore, I would offer it is an implementation failure to
>> list only a Send-Info or Recv-Info header.
>>
>> On Oct 22, 2008, at 5:36 AM, Christer Holmberg wrote:
>>
>>>
>>> Hi,
>>>
>>>> General issues with the negotiation mechanism:
>>>>
>>>> What happens if the initial INVITE by a UAC includes only
>> Send-Info
>>>> or
>>> Recv-Info? Does that indicate a "half-legacy" device??? Or does it
>>> delay negotiation for one but not the other? Or does
>>>> the presence of one mean the absence of the other is
>> equivalent to an
>>> empty one?
>>>>
>>>> As I think about it, I don't think its really necessary to
>> treat the
>>> absence of these headers as meaning "legacy". Treating the
>> absence of
>>> these headers as equivalent to their presence without
>>>> any packages is sufficient to get the proper legacy behavior. The
>>> tricky part is figuring out out when their absence *doesn't* mean
>>> that, which is significant only in the non-legacy case. In
>>>> particular, when they aren't present in INVITE it means
>> deferral of
>>>> the
>>> "offer" to the UAS. And possibly absence in an UPDATE means "don't
>>> renegotiate"???
>>>
>>> I don't think the presence, or absence, of the S/R-Info
>> headers should
>>> in any way be connected to legacy in any way. A UA can be legacy no
>>> matter if the headers are present, or not present, but that is all
>>> done based on "configuration", as described in the draft.
>>>
>>> So, if a UAC only included Send-Info, it means that it only
>> supports
>>> sending of Info packages. Then, it may, or may not, also support
>>> legacy INFO usages, but that is completely separated.
>>>
>>>
>>>> I'm confused by the three way negotiation of info packages in
>>> INVITE/2xx/ACK. Its allowed when the Send-Info/Recv-Info are in the
>>> INVITE, but not when they are deferred to the INVITE response,
>>>> or when they are conveyed in UPDATE and its response. If
>> the three
>>>> way
>>> handshake is needed to seal the deal, then those other options
>>> should be
>>> off the table. But the "deferred offer" of these
>>>> is really needed, so it can't be off the table. Or is this just an
>>> extra benefit that can be exploited when possible?
>>>>
>>>> Also, I don't see any provision for additional round(s) of
>>>> negotiation
>>> before 2xx via PRACK and UPDATE, though there is provision for
>>> additional "half-negotiations" via provisional responses
>>>> and the final response. Given the parallels with O/A, I'd
>> prefer to
>>>> see
>>> them more aligned in this regard, though I can be talked out of that
>>> with a good argument.
>>>
>>> I agree (I think :). The negotiation whould be 2-way. Then, based on
>>> what the UAC gets from the UAS, it may send a PRACK/UPDATE/re-INVITE
>>> with a new set of supported Info packages, but that is a new 2-way
>>> negotiation transaction.
>>>
>>>
>>>> I'd also like to take advantage of the lessons that have
>> been learned
>>> with O/A and nail down more of the semantics now. One issue
>> that leaps
>>> to mind in that regard is what happens if we start
>>>> to negotiate info packages in a reINVITE and then the
>> reINVITE fails?
>>>
>>> That's a good point.
>>>
>>> I think we should use the same rule as for offer/answer. Because,
>>> assume
>>> I send you a new set of packages in a re-INVITE, and you send me
>>> back a
>>> set in a 18x. Then we may start using info packages based on that
>>> negotiation long before the re-INVITE is rejected.
>>>
>>>> IMO what is needed is a state model for this stuff, added to the
>>>> state
>>> for an invite-dialog-usage. This state should determine
>> which packages
>>> may be sent, and which should be received without
>>>> error. We should be very clear about exactly which events cause
>>>> changes
>>> to this state.
>>>>
>>>> Even then there are race conditions that need to be clarified. For
>>>> instance: Suppose, as a result of an INVITE/1xx exchange between
>>>> Alice
>>> and Bob, that packages P & Q are allowed to be sent from
>> Alice to Bob.
>>>> Alice then sends an INFO with package Q, and at the same time Bob
>>>> sends
>>> a 2xx that only allows the receipt of package P. Then Bob
>> receives the
>>> INFO with package Q. What should happen?
>>>>
>>>> Another issue is that if the Send-Info/Recv-Info contents change in
>>> subsequent 1xx responses to the same INVITE, the UAS has no
>> guarantee
>>> that they are received. So any reduction in what can be
>>>> received cannot be counted upon until the 2xx/ACK.
>>>
>>> True. But, I wonder whether this will really be a real-life problem.
>>>
>>> And, we could a response code (4xx Info package not supported),
>>> which is
>>> used by the UAS if it receives an info package which it doesn't
>>> support.
>>> Then the UAC knows.
>>>
>>> Regards.
>>>
>>> Christer
>>>
>>> _______________________________________________
>>> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
>>> This list is for NEW development of the core SIP Protocol
>>> Use sip-implementors@cs.columbia.edu for questions on current sip
>>> Use sipping@ietf.org for new developments on the application of sip
>>
>>


--Apple-Mail-96-198994776
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGPTCCBjkw
ggUhoAMCAQICEC+VK1RLWxrF8KJZDR9k8p8wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYTAlVT
MQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VS
VFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQD
Ey1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwwHhcNMDgwODEz
MDAwMDAwWhcNMDkwODEzMjM1OTU5WjCB4TE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsg
LSBQRVJTT05BIE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9m
IHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDMg
Q29tb2RvIExpbWl0ZWQxFDASBgNVBAMTC0VyaWMgQnVyZ2VyMSkwJwYJKoZIhvcNAQkBFhplYnVy
Z2VyQHN0YW5kYXJkc3RyYWNrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMTF
RRoA4LgOACMFph0aomRC/UpqoA5C/d6DUTOvTMrYSEqkjwnU4zxDtBcHlcB4AxKAov00MYsUvEU4
loz7BHjfDjv76AIkcwu33VYQbzGmarVnyaXsVb6f/cyRL3fPT0VOVO2tQAEEgwg//CX0jN8Kn2jH
uXD/HEvko7cmpL3Pwevf3+DwB61v7ca79PpEZfn/WhaqRKA4uVNPj/JbieeaLo2v/0RJzrEElZK0
pHCqxiD3mQ8ossPkA9fUCSxLlbdMcPU3be5x8vt8Q8mYTXF5Z3d9RZmYrmNkvTQtdzVpfYWr/hgV
Xqm9tByOOAR+hoN3FKbubR/OrAHL9yDAd4sCAwEAAaOCAhwwggIYMB8GA1UdIwQYMBaAFImCZ33E
nSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBRDWgutb7b8R/L7G3Y3D+molAA3VzAOBgNVHQ8BAf8E
BAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJ
YIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEW
HWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMIGlBgNVHR8EgZ0wgZowTKBKoEiGRmh0dHA6
Ly9jcmwuY29tb2RvY2EuY29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRF
bWFpbC5jcmwwSqBIoEaGRGh0dHA6Ly9jcmwuY29tb2RvLm5ldC9VVE4tVVNFUkZpcnN0LUNsaWVu
dEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMGwGCCsGAQUFBwEBBGAwXjA2BggrBgEFBQcwAoYq
aHR0cDovL2NydC5jb21vZG9jYS5jb20vVVROQUFBQ2xpZW50Q0EuY3J0MCQGCCsGAQUFBzABhhho
dHRwOi8vb2NzcC5jb21vZG9jYS5jb20wJQYDVR0RBB4wHIEaZWJ1cmdlckBzdGFuZGFyZHN0cmFj
ay5jb20wDQYJKoZIhvcNAQEFBQADggEBAGeBR7NPCvrY3GQoIi49JOuciatY2r4st905Jw1etp6J
umFFWlaCBl11tFSclk/3S45B+lUv3SEvG4CEjUByPScprVmCqHR+y8BAQaB/CV+N1y14x3MbhJ+Z
8XDGKeUXuuyGd9w0l3/t/QPid6TRXQjQFrLPFs1IALuNpNiFMHEF/xFbMG1Z2vznR/gSPlePekoZ
TqcExIDBNZTBebpZqwAXzPpedNNOclbMLFLWDMOAozVRpkfjI0eiFsk8SF1Ho1Gb9Bx8DeG4peE2
KRVOR9FFnZZgBpFjXYRcglsMOSKCY8HgE+NGvbbqbrMoBV/BlYyxRXwfti71RL9Zs2Cq1eQxggP8
MIID+AIBATCBwzCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExh
a2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8v
d3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRp
Y2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkNH2TynzAJBgUrDgMCGgUAoIICDTAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wODEwMzExNTI2NTRaMCMGCSqGSIb3
DQEJBDEWBBRcBPazdh7YfuI3MwOCmh5pqIVp8TCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD
VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU
aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2
MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv
lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN
H2TynzANBgkqhkiG9w0BAQEFAASCAQCAmre1JKbuo46AWpOecJzMAllWenrK2ws78LVqyUEf4EYu
pbxnl68dFcCEJ7uTgCs6wXbvv9UUD7g/83gCB2Z3mJQqu0Qvpxrv5eQ4EwEqcOTNWnfBVcI8NvT8
TfLDuDSeEvKXX13/4kE7kWnlJYs+D4PvL1qs5VYZhFlQGLJ4G5pG8NIWgGUBjDnKY3rGUtR0yZlx
QuXLZ78fCMbu1RQFuQcbeRdmttHrZggWcHTr9k6kbPOBrXBpn032fQJklQo2m/GSDXl3Qj7viect
22vl39PJ3zN6xTM9FaInQ2K4pxCfI42JLXBH+QT+lMJ2B5ZRNEN33jsUqtJMRKp0YcykAAAAAAAA

--Apple-Mail-96-198994776--

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

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


From sip-bounces@ietf.org  Fri Oct 31 09:22:05 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 544AE3A68F0;
	Fri, 31 Oct 2008 09:22:05 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1CAE63A6A2C
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 09:22:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.513
X-Spam-Level: 
X-Spam-Status: No, score=-6.513 tagged_above=-999 required=5 tests=[AWL=0.086, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id gJpgDLEEmhQ8 for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 09:22:03 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 23D113A68F0
	for <sip@ietf.org>; Fri, 31 Oct 2008 09:21:28 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,523,1220227200"; d="scan'208";a="98665004"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-1.cisco.com with ESMTP; 31 Oct 2008 16:21:27 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9VGLR21010446; 
	Fri, 31 Oct 2008 09:21:27 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m9VGLMQq003637;
	Fri, 31 Oct 2008 16:21:24 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Attila Sipos'" <attila.sipos@vegastream.com>,
	"'Juha Heinanen'" <jh@tutpro.com>,
	"'Elwell, John'" <john.elwell@siemens.com>
References: <680808427CF931459462C3D78CB5EC60038B6296@EXVS02.nasstar-t1.net>
Date: Fri, 31 Oct 2008 09:21:21 -0700
Message-ID: <01ce01c93b74$b9133a60$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <680808427CF931459462C3D78CB5EC60038B6296@EXVS02.nasstar-t1.net>
Thread-Index: Ack7Is0pSB88yMJ/RrSjESLUT19SBgABGWwgABNMdPA=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3197; t=1225470087;
	x=1226334087; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20B2B-UA's=20provide=20an=20unsolveable=2
	0identity=20problem=20=20=20(was=20RE=3A=20[Sip]=20submissio
	n=20of=20a=20new=20I-D=3A=20=22Dialog=20Event=09foRIdentityV
	Erification=22) |Sender:=20;
	bh=efTDS97LB2BC30/2fo7mwrbTOcvWZfTc2X1o09p/KqY=;
	b=FBd7NiPwN9C2OJAa9CJyFm+viXPt2cNIqkKdbkvsLgT/LdQ2FtY+xIHvay
	KLyotwBhjNyP+bGATXkalz32BjjOI/1orwqVBFv9L17vsm+V3mqg62nCD32m
	U3lm/Na8fDYlMoA40KA28kD1xB40w/Snn4CwFs9urHF0j9IMfa9V4=;
Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: sip@ietf.org
Subject: Re: [Sip] B2B-UA's provide an unsolveable identity problem (was RE:
	submission of a new I-D: "Dialog Event	foRIdentityVErification")
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

B2BUAs, and SBCs, need to provide their features to their
customers (service providers), and can *also* provide end-to-
end identity.  The two requirements are not mutually exclusive,
and I don't understand what causes that argument to persist.  
Please talk to your favorite SBC vendor and ask them.

And when SIP spam becomes a problem (do you doubt it will?)
it will be much easier if we have a specification that can
solve the problem -- otherwise, vendors will be rushed to
create something that may not work as well as an IETF-
designed solution.  Spam won't wait for the IETF.

-d



> -----Original Message-----
> From: Attila Sipos [mailto:attila.sipos@vegastream.com] 
> Sent: Friday, October 31, 2008 12:34 AM
> To: Juha Heinanen; Elwell, John
> Cc: sip@ietf.org; Dan Wing
> Subject: B2B-UA's provide an unsolveable identity problem 
> (was RE: [Sip] submission of a new I-D: "Dialog Event 
> foRIdentityVErification")
> 
> >>i strongly disagree.  b2bua is just an ua.  if you you 
> build or deploy
> >>such boxes, it is your headache, not sip wg's.
> 
> I agree with Juha here.
> 
> Every attempt at fixing identity problems (and they have been clever
> solutions) has been hindered with the "but it won't work with B2BUAs"
> argument.
> 
> The problem is not "it won't work with B2BUAs" - the  problem is that
> B2BUA identity and security problems are unsolveable anyway. A B2BUA
> cannot be forced to do anything because even if you said "it must do
> this and that", a B2BUA can do what it wants anyway (I'm sure 
> we've all
> seen this).  Even if B2BUAs agreed to do certain things, one would
> always enf up with something else that gets B2B'ed.
> 
> It is no different to trying to solve the problem of 2 
> telephones taped
> together.
> 
> You can only trust things up to a certain boundary.  And the 
> boundaries
> of SIP are the UAs.  The best that SIP can do is to control 
> what happens
> between a UA and another UA (and proxies in between) and that's it.
> 
> Regards,
> 
> Attila
> 
> 
>  
> 
> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
> Juha Heinanen
> Sent: 31 October 2008 06:31
> To: Elwell, John
> Cc: sip@ietf.org; Dan Wing
> Subject: Re: [Sip] submission of a new I-D: "Dialog Event
> foRIdentityVErification"
> 
> Elwell, John writes:
> 
>  > > I support draft-kuthan-sip-derive-00, and hope the WG 
> can devote  >
> > time and energy to improving and standardizing it to work well  > >
> across a variety of networks.
>  > [JRE] I agree. This must include networks that contain B2BUAs/SBCs.
> 
> i strongly disagree.  b2bua is just an ua.  if you you build or deploy
> such boxes, it is your headache, not sip wg's.  it is enough that this
> work is based on rfc3261 components.
> 
> -- juha
> 
> 
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use
> sip-implementors@cs.columbia.edu for questions on current sip Use
> sipping@ietf.org for new developments on the application of sip

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


From sip-bounces@ietf.org  Fri Oct 31 10:15:04 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 022EF28C1F8;
	Fri, 31 Oct 2008 10:15:04 -0700 (PDT)
X-Original-To: sip@ietf.org
Delivered-To: sip@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 5BB073A6C34; Fri, 31 Oct 2008 10:15:00 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20081031171501.5BB073A6C34@core3.amsl.com>
Date: Fri, 31 Oct 2008 10:15:01 -0700 (PDT)
Cc: sip@ietf.org
Subject: [Sip] I-D Action:draft-ietf-sip-media-security-requirements-08.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


--NextPart

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


	Title           : Requirements and Analysis of Media Security Management Protocols
	Author(s)       : D. Wing, et al.
	Filename        : draft-ietf-sip-media-security-requirements-08.txt
	Pages           : 48
	Date            : 2008-10-31

This document describes requirements for a protocol to negotiate a
security context for SIP-signaled SRTP media.  In addition to the
natural security requirements, this negotiation protocol must
interoperate well with SIP in certain ways.  A number of proposals
have been published and a summary of these proposals is in the
appendix of this document.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sip-media-security-requirements-08.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-sip-media-security-requirements-08.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


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

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


From sip-bounces@ietf.org  Fri Oct 31 10:19:18 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4EE263A6994;
	Fri, 31 Oct 2008 10:19:18 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 513BE28C1B9
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 10:19:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.286
X-Spam-Level: 
X-Spam-Status: No, score=-2.286 tagged_above=-999 required=5 tests=[AWL=0.313, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id GgPWmxAiF3SV for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 10:19:08 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39])
	by core3.amsl.com (Postfix) with ESMTP id B1E2128C123
	for <sip@ietf.org>; Fri, 31 Oct 2008 10:19:03 -0700 (PDT)
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2])
	by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id m9VHIxla026388
	for <sip@ietf.org>; Fri, 31 Oct 2008 12:18:59 -0500 (CDT)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by
	ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 12:18:59 -0500
Received: from DEEXC1U01.de.lucent.com ([135.248.187.28]) by
	DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 18:18:57 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 31 Oct 2008 18:18:56 +0100
Message-ID: <5D1A7985295922448D5550C94DE291800245C5C5@DEEXC1U01.de.lucent.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Interim meeting in Malta
Thread-Index: Ack7fMGQheZ3DvVpRR6jejzEPY9L8A==
From: "DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com>
To: "SIP IETF" <sip@ietf.org>
X-OriginalArrivalTime: 31 Oct 2008 17:18:57.0412 (UTC)
	FILETIME=[C208F440:01C93B7C]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Subject: [Sip] Interim meeting in Malta
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

(As WG chair)

The SIP and SIPPING chairs have agreed (with the support of the AD) that
both SIP and SIPPING WGs will meet in Malta at the proposed interim
meeting 20th - 22nd January 2009. There are still arrangements to be
made as to precise dates and time allocation, but this should give you
enough time to go ahead and reserve flights at the cheapest rates.

You can see information here about the interim which will be updated as
it developes.

http://trac.tools.ietf.org/2009/jan-large-interim/

For SIP, what we will be looking for is agenda items that need some
considerable in depth discussion with large blocks of time, rather than
those that require 15 minute slots to make one decision. If you believe
there is a subject area that would benefit from such detailed discussion
(yours draft or someone elses), then please send us an email before the
start of IETF#73, so that we can float a tentative agenda at the SIP WG
meeting there.

I strongly suspect we may have an identity discussion at the interim
meeting, but would appreciate ideas on the best way of moving forward on
this subject.

All decisions of the interim meeting will of course be taken to the list
in some form or other.

regards

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


From sip-bounces@ietf.org  Fri Oct 31 10:41:35 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 71FA53A69A9;
	Fri, 31 Oct 2008 10:41:35 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 220313A688A
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 10:41:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.54
X-Spam-Level: 
X-Spam-Status: No, score=-2.54 tagged_above=-999 required=5 tests=[AWL=0.060, 
	BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5QInb6ZKB1OY for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 10:41:33 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net
	[IPv6:2001:470:1f03:267::2])
	by core3.amsl.com (Postfix) with ESMTP id B07053A677C
	for <sip@ietf.org>; Fri, 31 Oct 2008 10:41:29 -0700 (PDT)
Received: from hydra-3.local (ppp-70-244-83-54.dsl.rcsntx.swbell.net
	[70.244.83.54]) (authenticated bits=0)
	by nostrum.com (8.14.3/8.14.1) with ESMTP id m9VHfNqB011774
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 31 Oct 2008 12:41:23 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <490B4343.1010100@nostrum.com>
Date: Fri, 31 Oct 2008 12:41:23 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>	<0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>	<cc1f582e0810281052y34f5bf88h300c6f59d84879fe@mail.gmail.com>
	<0D5F89FAC29E2C41B98A6A762007F5D00138295A@GBNTHT12009MSX.gb002.siemens.net>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D00138295A@GBNTHT12009MSX.gb002.siemens.net>
Received-SPF: pass (nostrum.com: 70.244.83.54 is authenticated by a trusted
	mechanism)
X-Virus-Scanned: ClamAV 0.94/8549/Fri Oct 31 11:00:42 2008 on
	shaman.nostrum.com
X-Virus-Status: Clean
Cc: sip@ietf.org
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Elwell, John wrote:
> Also, the B2BUA could handle the SUBSCRIBE by its own, this is,
> > becoming a dialog presence server instead of forwarding the SUBSCRIBE
> > to the UA.
> > B2BUA must handle all this stuff since they are, in fact, the end
> > point, not the UA's behind them.
>
> [JRE] This reduces it to transitive trust, i.e., no better than P-Asserted-Identity. 
>
>   

Yes. Excepting cryptographic approaches: with any man-in-the-middle, 
you're at the mercy of that man-in-the-middle, regardless of whether 
their presence is an attack.

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


From sip-bounces@ietf.org  Fri Oct 31 10:47:57 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4DD5E3A6C6F;
	Fri, 31 Oct 2008 10:47:57 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C8CBA3A6BF0
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 10:47:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level: 
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[AWL=0.050, 
	BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id jLVYramfmzt1 for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 10:47:56 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net
	[IPv6:2001:470:1f03:267::2])
	by core3.amsl.com (Postfix) with ESMTP id 939673A6C09
	for <sip@ietf.org>; Fri, 31 Oct 2008 10:47:55 -0700 (PDT)
Received: from hydra-3.local (ppp-70-244-83-54.dsl.rcsntx.swbell.net
	[70.244.83.54]) (authenticated bits=0)
	by nostrum.com (8.14.3/8.14.1) with ESMTP id m9VHlNnB012193
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 31 Oct 2008 12:47:26 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <490B44AB.5060503@nostrum.com>
Date: Fri, 31 Oct 2008 12:47:23 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com><0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>	<490792EA.2020106@softarmor.com>	<033f01c9397b$860847a0$c3f0200a@cisco.com>
	<36E83843-775F-4317-BB0F-746E55194BFD@softarmor.com>
In-Reply-To: <36E83843-775F-4317-BB0F-746E55194BFD@softarmor.com>
Received-SPF: pass (nostrum.com: 70.244.83.54 is authenticated by a trusted
	mechanism)
X-Virus-Scanned: ClamAV 0.94/8549/Fri Oct 31 11:00:42 2008 on
	shaman.nostrum.com
X-Virus-Status: Clean
Cc: sip@ietf.org, "'Elwell, John'" <john.elwell@siemens.com>,
	Dan Wing <dwing@cisco.com>
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Dean Willis wrote:
>
> On Oct 28, 2008, at 11:05 PM, Dan Wing wrote:
>>>
>>> Would the SBC not have to handle the SUBSCRIBE request locally? After
>>> all, since it is a terminal UA for the call, it also knows
>>> about all the
>>> dialog states. The end-user UA would never even see the SUBSCRIBE.
>>
>> If that's a problem, just use some different method that goes end to
>> end.  The always-loved INFO comes to mind.
>
> What makes you think that INFO goes end to end? An SBC can absorb it 
> if it wants to.

And, in any case, you can't send an INFO out of dialog. So you can't 
route it to the address in the From -- all you can do is route it back 
along the dialog path. And, of course, *that's* going to work. If it's a 
legitimate call, you'll reach the legitimate caller, who will confirm 
the call is legitimate. If it's a forged call, you'll reach the 
attacker, who will confirm the call is legitimate.

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


From sip-bounces@ietf.org  Fri Oct 31 10:54:12 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C80DB3A6C57;
	Fri, 31 Oct 2008 10:54:12 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 612DF3A6AC0
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 10:54:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.574
X-Spam-Level: 
X-Spam-Status: No, score=-3.574 tagged_above=-999 required=5 tests=[AWL=0.025, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Fk+WVChrk-Ed for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 10:54:11 -0700 (PDT)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145])
	by core3.amsl.com (Postfix) with ESMTP id 370C83A6C57
	for <sip@ietf.org>; Fri, 31 Oct 2008 10:54:10 -0700 (PDT)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71])
	by TheWorld.com (8.13.6/8.13.6) with ESMTP id m9VHs1Q9026739
	for <sip@ietf.org>; Fri, 31 Oct 2008 13:54:03 -0400
Received: from shell01.TheWorld.com (localhost [127.0.0.1])
	by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id m9VHs0cC57637154
	for <sip@ietf.org>; Fri, 31 Oct 2008 12:54:01 -0500 (EST)
Received: (from worley@localhost)
	by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id m9VHs09X57587141;
	Fri, 31 Oct 2008 13:54:00 -0400 (EDT)
Date: Fri, 31 Oct 2008 13:54:00 -0400 (EDT)
Message-Id: <200810311754.m9VHs09X57587141@shell01.TheWorld.com>
To: sip@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <cc1f582e0810290225j44b5075bsedc4148143c5046b@mail.gmail.com>
	(ibc@aliax.net)
References: <200810251926.17644.ibc@aliax.net> <490382B6.1090400@cisco.com>
	<200810252305.20030.ibc@aliax.net>
	<200810290236.m9T2asoN55836835@shell01.TheWorld.com>
	<cc1f582e0810290225j44b5075bsedc4148143c5046b@mail.gmail.com>
Subject: Re: [Sip] [RFC 4235 & draft-kuthan-sip-derive] 481 "Call
	doesn't	exist" for initial SUBSCRIBE ?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

   From: "=?UTF-8?Q?I=C3=B1aki_Baz_Castillo?=" <ibc@aliax.net>

   > In any case, for the purposes of DERIVE, none of that matters:
   > Any failure response to the SUBSCRIBE, or a NOTIFY that does not
   > list the call in question, results in call rejection.

   But this behaviour would deny calls from devices not supporting
   RFC4235 (receiving a SUBSCRIBE Event: dialog).AFAIK this draft says
   that if the SUBSCRIBE is replied with 200 thenthe dialog exists and
   identity verified, if 481 then the devicesupports RFC 4235 and it's
   a suspicius call, and for any other failureroute it could mean that
   the device doesn't support RFC 4235 or anykind of "protection" in
   an intermediary proxy. In the last case, thereceptor of the INVITE
   should choose to accept or deny the call, hecannot know if the
   sender is really the From (or if he is not).

In my experience, it's very difficult to accurately distinguish
between "authentication mechanism is not supported by the
correspondent" and "authentication mechanism denies the
correspondent's identity".  The only cases where that distinction can
be made accurately are where both ends of the communication
specifically signal the presence/absence of the authentication
mechanism.

In the case of DERIVE, the goal is for the recipient to be able to
authenticate the caller in a large fraction of cases without requiring
the caller to specifically implement a mechanism to do so.  Given the
high variability of SIP implementations, one cannot reliably impute
meanings to failure response codes.

I would expect that many SIP implementations would not handle Event
parameters (filtering) correctly, and would just return all dialogs
present at the UAC.  So the UAS will have to inspect the event body to
see if its dialog is listed.

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


From sip-bounces@ietf.org  Fri Oct 31 10:54:20 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 98D7C3A6D5F;
	Fri, 31 Oct 2008 10:54:20 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4B1383A6C9D
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 10:54:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.557
X-Spam-Level: 
X-Spam-Status: No, score=-2.557 tagged_above=-999 required=5 tests=[AWL=0.043, 
	BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id kJ+AWdsFXok1 for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 10:54:18 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net
	[IPv6:2001:470:1f03:267::2])
	by core3.amsl.com (Postfix) with ESMTP id E58993A6C98
	for <sip@ietf.org>; Fri, 31 Oct 2008 10:54:17 -0700 (PDT)
Received: from hydra-3.local (ppp-70-244-83-54.dsl.rcsntx.swbell.net
	[70.244.83.54]) (authenticated bits=0)
	by nostrum.com (8.14.3/8.14.1) with ESMTP id m9VHsCUv012641
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 31 Oct 2008 12:54:12 -0500 (CDT)
	(envelope-from adam@nostrum.com)
Message-ID: <490B4644.90705@nostrum.com>
Date: Fri, 31 Oct 2008 12:54:12 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens.com>
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>	<0D5F89FAC29E2C41B98A6A762007F5D001382923@GBNTHT12009MSX.gb002.siemens.net>	<200810290236.m9T2aagI55951354@shell01.TheWorld.com>
	<0D5F89FAC29E2C41B98A6A762007F5D001382976@GBNTHT12009MSX.gb002.siemens.net>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D001382976@GBNTHT12009MSX.gb002.siemens.net>
Received-SPF: pass (nostrum.com: 70.244.83.54 is authenticated by a trusted
	mechanism)
X-Virus-Scanned: ClamAV 0.94/8549/Fri Oct 31 11:00:42 2008 on
	shaman.nostrum.com
X-Virus-Status: Clean
Cc: sip@ietf.org
Subject: Re: [Sip] Comment on DERIVE and B2BUAs
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Elwell, John wrote:
>
>   
>> -----Original Message-----
>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
>> Behalf Of Dale.Worley@comcast.net
>>
>> However...  If we change the sequence of operations a bit, so that the
>> UAS sends a 183 with a Contact carrying a specific header parameter
>> carrying a crypto-random value, and we get B2BUAs to pass it through
>> (attaching it to the Contact they use in the 183 they emit on the
>> other side), then if the UAS does a non-filtered dialog event
>> SUBSCRIBE, it can check the returned NOTIFY to see if it carries the
>> Contact header parameter that it created.  That's a reasonably good
>> test that the UAC of the INVITE can be reached via the From value that
>> the UAS received.
>>     
> [JRE] Unless a B2BUA fails to play according to the rules and
> acknowledges the SUBSCRIBE without carrying out the same test on the
> next hop.

That's kind of the point of Juri's draft, though -- semantically, the 
recipient of the SUBSCRIBE doesn't need to know that this is an identity 
check. So the B2BUA would have no obligation to do anything towards the 
calling party.

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


From sip-bounces@ietf.org  Fri Oct 31 11:52:14 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 184DB3A6CA3;
	Fri, 31 Oct 2008 11:52:14 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 234333A6CA3
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 11:52:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id PjYPtSjcwozy for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 11:52:12 -0700 (PDT)
Received: from rn-out-0910.google.com (rn-out-0910.google.com [64.233.170.188])
	by core3.amsl.com (Postfix) with ESMTP id 4C3F03A6C6D
	for <sip@ietf.org>; Fri, 31 Oct 2008 11:51:34 -0700 (PDT)
Received: by rn-out-0910.google.com with SMTP id m7so1117977rnd.18
	for <sip@ietf.org>; Fri, 31 Oct 2008 11:51:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:mime-version:content-type:content-transfer-encoding
	:content-disposition;
	bh=tAvy4DyUf4hyEl6dr5WmXtJgxw/hw8MPfwCGEYBvTTo=;
	b=iyT21XqpQzFUNBbMc/PoHHhZy9qnRYb7beSykN12frdyVmvByvr9rxdrnFbqEG+GtQ
	8hZh9RmW3VkkrQH48OX63Rcyvg8oyTFzAPDjzQpW1zf6mfs7MTvwcjdiK1MPkYrlCuZ2
	Mwtjgu5iXbxDvHavYlVxLGKVCQRho1hGv+pco=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:mime-version:content-type
	:content-transfer-encoding:content-disposition;
	b=EiINnS2yY7iA91vIrSf3qvCAhiiMYLgd9gCX38jW+BIOEY7b96q8FnU6ct88WtAHt/
	7sDisBAxa4fh+Q1JDP5mv/UIes8TjYcmrx7h4WlsAyVWWCpOfwEhkCVih/FOIB6q7nCe
	xMwf9Wzoj3NR9OJK8/N28tyoQj8vPrnJntgYU=
Received: by 10.90.98.13 with SMTP id v13mr10372830agb.112.1225479091655;
	Fri, 31 Oct 2008 11:51:31 -0700 (PDT)
Received: by 10.90.114.2 with HTTP; Fri, 31 Oct 2008 11:51:31 -0700 (PDT)
Message-ID: <618e24240810311151p45f6f160h86725e2d7c83a2d9@mail.gmail.com>
Date: Fri, 31 Oct 2008 19:51:31 +0100
From: "=?UTF-8?Q?Victor_Pascual_=C3=81vila?=" <victor.pascual.avila@gmail.com>
To: "SIP IETF" <sip@ietf.org>
MIME-Version: 1.0
Content-Disposition: inline
Subject: [Sip] Thoughts on e2e identity verification
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

QWZ0ZXIgc29tZSBkaXNjdXNzaW9uLCB0aGUgZm9sbG93aW5nIHF1ZXN0aW9ucyBjb21lIHRvIG15
IG1pbmQ6Ci0gRG8gd2UgaGF2ZSBjbGVhciByZXF1aXJlbWVudHMgZm9yIGUyZSB2ZXJpZmljYXRp
b24/Ci0gRG8gd2UgaGF2ZSBjbGVhciBhcHBsaWNhdGlvbiBzY2VuYXJpb3M/Ci0gU2hhbGwgd2Ug
c29sdmUgYjJidWEtcmVsYXRlZCBwcm9ibGVtcyBoZXJlPwotIElzIGRyYWZ0LWt1dGhhbi1zaXAt
ZGVyaXZlIGEgZ29vZCBzdGFydGluZyBwb2ludD8KCkknZCBhcHByZWNpYXRlIHlvdXIgdGhvdWdo
dHMgb24gdGhpcywKLS0gClZpY3RvciBQYXNjdWFsIMOBdmlsYQpfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXwpTaXAgbWFpbGluZyBsaXN0ICBodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NpcApUaGlzIGxpc3QgaXMgZm9yIE5FVyBkZXZl
bG9wbWVudCBvZiB0aGUgY29yZSBTSVAgUHJvdG9jb2wKVXNlIHNpcC1pbXBsZW1lbnRvcnNAY3Mu
Y29sdW1iaWEuZWR1IGZvciBxdWVzdGlvbnMgb24gY3VycmVudCBzaXAKVXNlIHNpcHBpbmdAaWV0
Zi5vcmcgZm9yIG5ldyBkZXZlbG9wbWVudHMgb24gdGhlIGFwcGxpY2F0aW9uIG9mIHNpcA==


From sip-bounces@ietf.org  Fri Oct 31 14:06:23 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2DB6F3A693A;
	Fri, 31 Oct 2008 14:06:23 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C50B33A693A
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 14:06:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5
	tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9wduA6CWVjXH for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 14:06:20 -0700 (PDT)
Received: from cluster-f.mailcontrol.com (cluster-f.mailcontrol.com
	[85.119.2.190]) by core3.amsl.com (Postfix) with ESMTP id DFBFC3A679C
	for <sip@ietf.org>; Fri, 31 Oct 2008 14:06:19 -0700 (PDT)
Received: from rly22f.srv.mailcontrol.com (localhost.localdomain [127.0.0.1])
	by rly22f.srv.mailcontrol.com (MailControl) with ESMTP id
	m9VL674f031448 for <sip@ietf.org>; Fri, 31 Oct 2008 21:06:14 GMT
Received: from submission.mailcontrol.com (submission.mailcontrol.com
	[86.111.216.190])
	by rly22f.srv.mailcontrol.com (MailControl) id m9VL5nYb030367
	for sip@ietf.org; Fri, 31 Oct 2008 21:05:49 GMT
Received: from exsmtp01.nasstar-t1.net (exsmtp01.nasstar-t1.net [89.28.233.12])
	by rly22f-eth0.srv.mailcontrol.com (envelope-sender
	attila.sipos@vegastream.com) (MIMEDefang) with ESMTP id
	m9VL5Xek027860; Fri, 31 Oct 2008 21:05:48 +0000 (GMT)
Received: from EXVS02.nasstar-t1.net ([10.2.10.106]) by
	exsmtp01.nasstar-t1.net with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 31 Oct 2008 21:06:46 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 31 Oct 2008 21:06:46 -0000
Message-ID: <680808427CF931459462C3D78CB5EC601CCF63@EXVS02.nasstar-t1.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: B2B-UA's provide an unsolveable identity problem (was RE: [Sip]
	submission of a new I-D: "Dialog Event	foRIdentityVErification")
Thread-Index: Ack7Is0pSB88yMJ/RrSjESLUT19SBgABGWwgABNMdPAACL89Og==
References: <680808427CF931459462C3D78CB5EC60038B6296@EXVS02.nasstar-t1.net>
	<01ce01c93b74$b9133a60$c3f0200a@cisco.com>
From: "Attila Sipos" <attila.sipos@vegastream.com>
To: "Dan Wing" <dwing@cisco.com>, "Juha Heinanen" <jh@tutpro.com>,
	"Elwell, John" <john.elwell@siemens.com>
X-OriginalArrivalTime: 31 Oct 2008 21:06:46.0910 (UTC)
	FILETIME=[95B0D1E0:01C93B9C]
X-Scanned-By: MailControl A-08-50-15 (www.mailcontrol.com) on 10.70.1.132
Cc: sip@ietf.org
Subject: Re: [Sip] B2B-UA's provide an unsolveable identity problem (was RE:
	submission of a new I-D: "Dialog Event	foRIdentityVErification")
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0369093286=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0369093286==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C93B9C.95A88B08"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C93B9C.95A88B08
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Yes, you are right, there are "end-to-end" solutions.
I take back the comment about unsolveable.
=20
My comments were a bit extreme but I guess I was trying to say you are alwa=
ys at the mercy of the B2BUA.
As we know, the problems with B2BUAs are not because of problems with UA-to=
-UA SIP but with the fields and bodies that B2BUA's change.  So, for me, it=
 should be the B2BUA makers who fix those problems.
=20
So, in conclusion I would prefer that UA-to-UA works first.
=20
>>designed solution.  Spam won't wait for the IETF.

Agreed.  And finding a solution will take even longer if we have to conside=
r B2BUAs.
=20
Regards,
Attila
=20
PS Don't get me wrong, I don't hate B2BUA's, I just think they should fix t=
heir own issues.
=20

________________________________

From: Dan Wing [mailto:dwing@cisco.com]
Sent: Fri 31/10/2008 16:21
To: Attila Sipos; 'Juha Heinanen'; 'Elwell, John'
Cc: sip@ietf.org
Subject: RE: B2B-UA's provide an unsolveable identity problem (was RE: [Sip=
] submission of a new I-D: "Dialog Event foRIdentityVErification")



B2BUAs, and SBCs, need to provide their features to their
customers (service providers), and can *also* provide end-to-
end identity.  The two requirements are not mutually exclusive,
and I don't understand what causes that argument to persist.=20
Please talk to your favorite SBC vendor and ask them.

And when SIP spam becomes a problem (do you doubt it will?)
it will be much easier if we have a specification that can
solve the problem -- otherwise, vendors will be rushed to
create something that may not work as well as an IETF-
designed solution.  Spam won't wait for the IETF.

-d



> -----Original Message-----
> From: Attila Sipos [mailto:attila.sipos@vegastream.com]
> Sent: Friday, October 31, 2008 12:34 AM
> To: Juha Heinanen; Elwell, John
> Cc: sip@ietf.org; Dan Wing
> Subject: B2B-UA's provide an unsolveable identity problem
> (was RE: [Sip] submission of a new I-D: "Dialog Event
> foRIdentityVErification")
>
> >>i strongly disagree.  b2bua is just an ua.  if you you
> build or deploy
> >>such boxes, it is your headache, not sip wg's.
>
> I agree with Juha here.
>
> Every attempt at fixing identity problems (and they have been clever
> solutions) has been hindered with the "but it won't work with B2BUAs"
> argument.
>
> The problem is not "it won't work with B2BUAs" - the  problem is that
> B2BUA identity and security problems are unsolveable anyway. A B2BUA
> cannot be forced to do anything because even if you said "it must do
> this and that", a B2BUA can do what it wants anyway (I'm sure
> we've all
> seen this).  Even if B2BUAs agreed to do certain things, one would
> always enf up with something else that gets B2B'ed.
>
> It is no different to trying to solve the problem of 2
> telephones taped
> together.
>
> You can only trust things up to a certain boundary.  And the
> boundaries
> of SIP are the UAs.  The best that SIP can do is to control
> what happens
> between a UA and another UA (and proxies in between) and that's it.
>
> Regards,
>
> Attila
>
>
>=20
>
> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
> Juha Heinanen
> Sent: 31 October 2008 06:31
> To: Elwell, John
> Cc: sip@ietf.org; Dan Wing
> Subject: Re: [Sip] submission of a new I-D: "Dialog Event
> foRIdentityVErification"
>
> Elwell, John writes:
>
>  > > I support draft-kuthan-sip-derive-00, and hope the WG
> can devote  >
> > time and energy to improving and standardizing it to work well  > >
> across a variety of networks.
>  > [JRE] I agree. This must include networks that contain B2BUAs/SBCs.
>
> i strongly disagree.  b2bua is just an ua.  if you you build or deploy
> such boxes, it is your headache, not sip wg's.  it is enough that this
> work is based on rfc3261 components.
>
> -- juha
>
>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol Use
> sip-implementors@cs.columbia.edu for questions on current sip Use
> sipping@ietf.org for new developments on the application of sip




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

<HTML dir=3Dltr><HEAD><TITLE>RE: B2B-UA's provide an unsolveable identity p=
roblem (was RE: [Sip] submission of a new I-D: "Dialog Event foRIdentityVEr=
ification")</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR></HEAD>
<BODY>
<DIV id=3DidOWAReplyText17876 dir=3Dltr>
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Yes, you are rig=
ht, there are "end-to-end" solutions.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>I take back the comment about un=
solveable.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>My comments were a bit extreme b=
ut I guess I was trying to say you are always at the mercy of the B2BUA.</F=
ONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>As we know, the problems with B2=
BUAs are not because of problems with UA-to-UA SIP but with the fields and =
bodies that B2BUA's change.&nbsp;&nbsp;So, for me,&nbsp;it should be the B2=
BUA makers who fix those problems.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>So, in conclusion&nbsp;I would p=
refer that UA-to-UA works first.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2><FONT face=3D"Times New Roman">&=
gt;&gt;designed solution.&nbsp; Spam won't wait for the IETF.</FONT><BR></F=
ONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Agreed.&nbsp; And finding a solu=
tion will take even longer if we have to consider B2BUAs.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Regards,</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Attila</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2>PS Don't get me wrong, I don't h=
ate B2BUA's, I just think they should fix their own issues.</FONT></DIV>
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></DIV>
<DIV dir=3Dltr><BR>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Dan Wing [mailto:dwing@cisco.com]=
<BR><B>Sent:</B> Fri 31/10/2008 16:21<BR><B>To:</B> Attila Sipos; 'Juha Hei=
nanen'; 'Elwell, John'<BR><B>Cc:</B> sip@ietf.org<BR><B>Subject:</B> RE: B2=
B-UA's provide an unsolveable identity problem (was RE: [Sip] submission of=
 a new I-D: "Dialog Event foRIdentityVErification")<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=3D2>B2BUAs, and SBCs, need to provide their features to their=
<BR>customers (service providers), and can *also* provide end-to-<BR>end id=
entity.&nbsp; The two requirements are not mutually exclusive,<BR>and I don=
't understand what causes that argument to persist.&nbsp;<BR>Please talk to=
 your favorite SBC vendor and ask them.<BR><BR>And when SIP spam becomes a =
problem (do you doubt it will?)<BR>it will be much easier if we have a spec=
ification that can<BR>solve the problem -- otherwise, vendors will be rushe=
d to<BR>create something that may not work as well as an IETF-<BR>designed =
solution.&nbsp; Spam won't wait for the IETF.<BR><BR>-d<BR><BR><BR><BR>&gt;=
 -----Original Message-----<BR>&gt; From: Attila Sipos [<A href=3D"mailto:a=
ttila.sipos@vegastream.com">mailto:attila.sipos@vegastream.com</A>]<BR>&gt;=
 Sent: Friday, October 31, 2008 12:34 AM<BR>&gt; To: Juha Heinanen; Elwell,=
 John<BR>&gt; Cc: sip@ietf.org; Dan Wing<BR>&gt; Subject: B2B-UA's provide =
an unsolveable identity problem<BR>&gt; (was RE: [Sip] submission of a new =
I-D: "Dialog Event<BR>&gt; foRIdentityVErification")<BR>&gt;<BR>&gt; &gt;&g=
t;i strongly disagree.&nbsp; b2bua is just an ua.&nbsp; if you you<BR>&gt; =
build or deploy<BR>&gt; &gt;&gt;such boxes, it is your headache, not sip wg=
's.<BR>&gt;<BR>&gt; I agree with Juha here.<BR>&gt;<BR>&gt; Every attempt a=
t fixing identity problems (and they have been clever<BR>&gt; solutions) ha=
s been hindered with the "but it won't work with B2BUAs"<BR>&gt; argument.<=
BR>&gt;<BR>&gt; The problem is not "it won't work with B2BUAs" - the&nbsp; =
problem is that<BR>&gt; B2BUA identity and security problems are unsolveabl=
e anyway. A B2BUA<BR>&gt; cannot be forced to do anything because even if y=
ou said "it must do<BR>&gt; this and that", a B2BUA can do what it wants an=
yway (I'm sure<BR>&gt; we've all<BR>&gt; seen this).&nbsp; Even if B2BUAs a=
greed to do certain things, one would<BR>&gt; always enf up with something =
else that gets B2B'ed.<BR>&gt;<BR>&gt; It is no different to trying to solv=
e the problem of 2<BR>&gt; telephones taped<BR>&gt; together.<BR>&gt;<BR>&g=
t; You can only trust things up to a certain boundary.&nbsp; And the<BR>&gt=
; boundaries<BR>&gt; of SIP are the UAs.&nbsp; The best that SIP can do is =
to control<BR>&gt; what happens<BR>&gt; between a UA and another UA (and pr=
oxies in between) and that's it.<BR>&gt;<BR>&gt; Regards,<BR>&gt;<BR>&gt; A=
ttila<BR>&gt;<BR>&gt;<BR>&gt;&nbsp;<BR>&gt;<BR>&gt; -----Original Message--=
---<BR>&gt; From: sip-bounces@ietf.org [<A href=3D"mailto:sip-bounces@ietf.=
org">mailto:sip-bounces@ietf.org</A>] On Behalf Of<BR>&gt; Juha Heinanen<BR=
>&gt; Sent: 31 October 2008 06:31<BR>&gt; To: Elwell, John<BR>&gt; Cc: sip@=
ietf.org; Dan Wing<BR>&gt; Subject: Re: [Sip] submission of a new I-D: "Dia=
log Event<BR>&gt; foRIdentityVErification"<BR>&gt;<BR>&gt; Elwell, John wri=
tes:<BR>&gt;<BR>&gt;&nbsp; &gt; &gt; I support draft-kuthan-sip-derive-00, =
and hope the WG<BR>&gt; can devote&nbsp; &gt;<BR>&gt; &gt; time and energy =
to improving and standardizing it to work well&nbsp; &gt; &gt;<BR>&gt; acro=
ss a variety of networks.<BR>&gt;&nbsp; &gt; [JRE] I agree. This must inclu=
de networks that contain B2BUAs/SBCs.<BR>&gt;<BR>&gt; i strongly disagree.&=
nbsp; b2bua is just an ua.&nbsp; if you you build or deploy<BR>&gt; such bo=
xes, it is your headache, not sip wg's.&nbsp; it is enough that this<BR>&gt=
; work is based on rfc3261 components.<BR>&gt;<BR>&gt; -- juha<BR>&gt;<BR>&=
gt;<BR>&gt; _______________________________________________<BR>&gt; Sip mai=
ling list&nbsp; <A href=3D"https://www.ietf.org/mailman/listinfo/sip">https=
://www.ietf.org/mailman/listinfo/sip</A><BR>&gt; This list is for NEW devel=
opment of the core SIP Protocol Use<BR>&gt; sip-implementors@cs.columbia.ed=
u for questions on current sip Use<BR>&gt; sipping@ietf.org for new develop=
ments on the application of sip<BR><BR></FONT></P></DIV><br><br>
<P align=3Dleft><FONT style=3D"BACKGROUND-COLOR: #ffffff">.</FONT></P>
</body></HTML>=

------_=_NextPart_001_01C93B9C.95A88B08--

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

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


From sip-bounces@ietf.org  Fri Oct 31 14:42:54 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6B5F53A6A64;
	Fri, 31 Oct 2008 14:42:54 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A65193A6A64
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 14:42:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.522
X-Spam-Level: 
X-Spam-Status: No, score=-6.522 tagged_above=-999 required=5 tests=[AWL=0.077, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RNJZP5WmdgZi for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 14:42:52 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 7B6693A67B2
	for <sip@ietf.org>; Fri, 31 Oct 2008 14:42:52 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,524,1220227200"; d="scan'208";a="186537552"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 31 Oct 2008 21:42:51 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m9VLgpeK014031; 
	Fri, 31 Oct 2008 14:42:51 -0700
Received: from dwingwxp01 ([10.32.240.195])
	by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m9VLgoNN013935;
	Fri, 31 Oct 2008 21:42:51 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Attila Sipos'" <attila.sipos@vegastream.com>,
	"'Juha Heinanen'" <jh@tutpro.com>,
	"'Elwell, John'" <john.elwell@siemens.com>
References: <680808427CF931459462C3D78CB5EC60038B6296@EXVS02.nasstar-t1.net>
	<01ce01c93b74$b9133a60$c3f0200a@cisco.com>
	<680808427CF931459462C3D78CB5EC601CCF63@EXVS02.nasstar-t1.net>
Date: Fri, 31 Oct 2008 14:42:50 -0700
Message-ID: <038601c93ba1$9fcb15f0$c3f0200a@cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <680808427CF931459462C3D78CB5EC601CCF63@EXVS02.nasstar-t1.net>
Thread-Index: Ack7Is0pSB88yMJ/RrSjESLUT19SBgABGWwgABNMdPAACL89OgACZtuQ
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5635; t=1225489371;
	x=1226353371; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dwing@cisco.com;
	z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com>
	|Subject:=20RE=3A=20B2B-UA's=20provide=20an=20unsolveable=2
	0identity=20problem=20=20=20(was=20RE=3A=20[Sip]=20submissio
	n=20of=20a=20new=20I-D=3A=20=22Dialog=20Event=09foRIdentityV
	Erification=22) |Sender:=20;
	bh=UjTTHip7ZYmAexFLlYt+O4n0jdad+2hJhh+dMK02VxU=;
	b=jDT2QS/5npN5OTCHvhSX5KZ1jgDyk1CGSy3ztaIuxccROCzTb8IsneUru+
	vNcSa9t38OtfPNUUBDijxHuuvuZ9ahtK1IQwoe8KSrikP+I9DURQIKaOW5Uh
	cawG7wNfyfggQsIPKW/Vm3sZaO9pw2ln9nNOTbwGq51r5TrD5E84w=;
Authentication-Results: sj-dkim-1; header.From=dwing@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: sip@ietf.org
Subject: Re: [Sip] B2B-UA's provide an unsolveable identity problem (was RE:
	submission of a new I-D: "Dialog Event	foRIdentityVErification")
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

 

> -----Original Message-----
> From: Attila Sipos [mailto:attila.sipos@vegastream.com] 
> Sent: Friday, October 31, 2008 2:07 PM
> To: Dan Wing; Juha Heinanen; Elwell, John
> Cc: sip@ietf.org
> Subject: RE: B2B-UA's provide an unsolveable identity problem 
> (was RE: [Sip] submission of a new I-D: "Dialog Event 
> foRIdentityVErification")
> 
> Yes, you are right, there are "end-to-end" solutions.
> I take back the comment about unsolveable.
>  
> My comments were a bit extreme but I guess I was trying to 
> say you are always at the mercy of the B2BUA.

Yes, of course.  We are also at the mercy of the postal
service, IP providers (to forward IP packets), telephone
companies to send our tones without interfering with them
(remember how their echo cancellers interfered with 9600bps
and higher modems?), and all other intermediaries.

This is not something new, or unique, to SIP or to B2BUAs/
SBCs.  It is an engineering challange to work through.  

> As we know, the problems with B2BUAs are not because of 
> problems with UA-to-UA SIP but with the fields and bodies 
> that B2BUA's change.  So, for me, it should be the B2BUA 
> makers who fix those problems.
>
> So, in conclusion I would prefer that UA-to-UA works first.

RFC4474 works UA-to-UA.  As would mutually-authenticated
TLS between those UAs.

> >>designed solution.  Spam won't wait for the IETF.
> 
> Agreed.  And finding a solution will take even longer if we 
> have to consider B2BUAs.

With few exceptions, all large ITSPs have SBCs and B2BUAs.

> Regards,
> Attila
>  
> PS Don't get me wrong, I don't hate B2BUA's, I just think 
> they should fix their own issues.

We need to provide the necessary guidance to what they need
to do -- while still allowing them to provide the primary
functions for which they are operated.

-d


> 
> ________________________________
> 
> From: Dan Wing [mailto:dwing@cisco.com]
> Sent: Fri 31/10/2008 16:21
> To: Attila Sipos; 'Juha Heinanen'; 'Elwell, John'
> Cc: sip@ietf.org
> Subject: RE: B2B-UA's provide an unsolveable identity problem 
> (was RE: [Sip] submission of a new I-D: "Dialog Event 
> foRIdentityVErification")
> 
> 
> 
> B2BUAs, and SBCs, need to provide their features to their
> customers (service providers), and can *also* provide end-to-
> end identity.  The two requirements are not mutually exclusive,
> and I don't understand what causes that argument to persist. 
> Please talk to your favorite SBC vendor and ask them.
> 
> And when SIP spam becomes a problem (do you doubt it will?)
> it will be much easier if we have a specification that can
> solve the problem -- otherwise, vendors will be rushed to
> create something that may not work as well as an IETF-
> designed solution.  Spam won't wait for the IETF.
> 
> -d
> 
> 
> 
> > -----Original Message-----
> > From: Attila Sipos [mailto:attila.sipos@vegastream.com]
> > Sent: Friday, October 31, 2008 12:34 AM
> > To: Juha Heinanen; Elwell, John
> > Cc: sip@ietf.org; Dan Wing
> > Subject: B2B-UA's provide an unsolveable identity problem
> > (was RE: [Sip] submission of a new I-D: "Dialog Event
> > foRIdentityVErification")
> >
> > >>i strongly disagree.  b2bua is just an ua.  if you you
> > build or deploy
> > >>such boxes, it is your headache, not sip wg's.
> >
> > I agree with Juha here.
> >
> > Every attempt at fixing identity problems (and they have been clever
> > solutions) has been hindered with the "but it won't work 
> with B2BUAs"
> > argument.
> >
> > The problem is not "it won't work with B2BUAs" - the  
> problem is that
> > B2BUA identity and security problems are unsolveable anyway. A B2BUA
> > cannot be forced to do anything because even if you said "it must do
> > this and that", a B2BUA can do what it wants anyway (I'm sure
> > we've all
> > seen this).  Even if B2BUAs agreed to do certain things, one would
> > always enf up with something else that gets B2B'ed.
> >
> > It is no different to trying to solve the problem of 2
> > telephones taped
> > together.
> >
> > You can only trust things up to a certain boundary.  And the
> > boundaries
> > of SIP are the UAs.  The best that SIP can do is to control
> > what happens
> > between a UA and another UA (and proxies in between) and that's it.
> >
> > Regards,
> >
> > Attila
> >
> >
> > 
> >
> > -----Original Message-----
> > From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of
> > Juha Heinanen
> > Sent: 31 October 2008 06:31
> > To: Elwell, John
> > Cc: sip@ietf.org; Dan Wing
> > Subject: Re: [Sip] submission of a new I-D: "Dialog Event
> > foRIdentityVErification"
> >
> > Elwell, John writes:
> >
> >  > > I support draft-kuthan-sip-derive-00, and hope the WG
> > can devote  >
> > > time and energy to improving and standardizing it to work 
> well  > >
> > across a variety of networks.
> >  > [JRE] I agree. This must include networks that contain 
> B2BUAs/SBCs.
> >
> > i strongly disagree.  b2bua is just an ua.  if you you 
> build or deploy
> > such boxes, it is your headache, not sip wg's.  it is 
> enough that this
> > work is based on rfc3261 components.
> >
> > -- juha
> >
> >
> > _______________________________________________
> > Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> > This list is for NEW development of the core SIP Protocol Use
> > sip-implementors@cs.columbia.edu for questions on current sip Use
> > sipping@ietf.org for new developments on the application of sip
> 
> 
> 
> 
> 
> .
> 
> 

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


From sip-bounces@ietf.org  Fri Oct 31 15:02:26 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7EF783A6802;
	Fri, 31 Oct 2008 15:02:26 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 995843A67B2
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 15:02:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5
	tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id WwvxnedMzzAz for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 15:02:25 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id D78713A6359
	for <sip@ietf.org>; Fri, 31 Oct 2008 15:02:24 -0700 (PDT)
Received: from [192.168.2.102] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9VM2KMO004462
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 31 Oct 2008 17:02:21 -0500
Message-Id: <8D041140-D5C3-4AA3-B785-B6BD8C896773@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: =?ISO-8859-1?Q?Victor_Pascual_=C1vila?= <victor.pascual.avila@gmail.com>
In-Reply-To: <618e24240810310330h765b06bele08cd9cef8de2de9@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 31 Oct 2008 17:02:15 -0500
References: <680808427CF931459462C3D78CB5EC60038B6296@EXVS02.nasstar-t1.net>
	<618e24240810310330h765b06bele08cd9cef8de2de9@mail.gmail.com>
X-Mailer: Apple Mail (2.929.2)
Cc: sip@ietf.org
Subject: Re: [Sip] B2B-UA's provide an unsolveable identity problem (was RE:
	submission of a new I-D: "Dialog Event foRIdentityVErification")
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 31, 2008, at 5:30 AM, Victor Pascual =C1vila wrote:

>> Elwell, John writes:
>>
>>>> I support draft-kuthan-sip-derive-00, and hope the WG can devote  >
>>> time and energy to improving and standardizing it to work well  > >
>> across a variety of networks.
>>> [JRE] I agree. This must include networks that contain B2BUAs/SBCs.
>
> A B2BUA is a man-in-the-middle, there's no feasible end-to-end  =

> scenario here.
>

One might argue that we could define a "standard B2BUA function for  =

optimal transparency". We would then add "Considerations at the  =

Standard B2BUA" into every SIP extension.

Would this change what SBCs do to make them application transparent?

I rather doubt it. My sense is that the SBCs do what they do for  =

reasons that are not dictated by our specifications, but from the  =

valid or invalid perceptions of network operators and the business  =

decisions they make in response to those perceptions.

We can tell them that not beating their heads on the wall will reduce  =

their cranial pain, but it is entirely possible that they're beating  =

their heads because they enjoy it, feel that it will scare away the  =

bogeyman, are using it to distract themselves from other self- =

inflicted wounds, don't have anything better to do with their money,  =

or have found that ritual head-beating sedates the liability vultures  =

and auditing zombies.

Happy Halloween!

--
Dean

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


From sip-bounces@ietf.org  Fri Oct 31 15:06:48 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8C05E3A6802;
	Fri, 31 Oct 2008 15:06:48 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 324D63A6802
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 15:06:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5
	tests=[AWL=-0.138, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id X8iRgLJQ2iiR for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 15:06:46 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 737E23A6359
	for <sip@ietf.org>; Fri, 31 Oct 2008 15:06:46 -0700 (PDT)
Received: from [192.168.2.102] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9VM6fIV004494
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 31 Oct 2008 17:06:42 -0500
Message-Id: <701FB600-CBE9-4A66-BA0C-52F3B86F0A5B@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: =?ISO-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
In-Reply-To: <cc1f582e0810310603w21a4cc7fga1d978c0fb4f5bd7@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 31 Oct 2008 17:06:35 -0500
References: <618e24240810250809j664bf47ay2745cc9fbf7b0565@mail.gmail.com>
	<D38ED479-3722-438A-83B8-F023E02B58A3@softarmor.com>
	<200810290236.m9T2akDN55854559@shell01.TheWorld.com>
	<033d01c93979$b3cf1990$c3f0200a@cisco.com>
	<618e24240810291636q6986570as674cbe65e49a8c7b@mail.gmail.com>
	<490ADE61.4030005@voip.co.uk>
	<cc1f582e0810310603w21a4cc7fga1d978c0fb4f5bd7@mail.gmail.com>
X-Mailer: Apple Mail (2.929.2)
Cc: sip@ietf.org
Subject: Re: [Sip] submission of a new I-D: "Dialog Event foR
	IdentityVErification"
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 31, 2008, at 8:03 AM, I=F1aki Baz Castillo wrote:

> 2008/10/31 Michael Procter <michael@voip.co.uk>:
>
>>> Shall DERIVE be extended to support non-INVITE requests (e.g.  =

>>> MESSAGE)
>>
>> I'm not sure it can.  RFC4235 is defined for INVITE-initiated dialog
>> usages only.  Yes, it could be extended, but I'm not convinced that  =

>> is
>> necessarily the best way forward from here!
>
> Also note that MESSAGE doesn't establish a dialog, it just an
> independent transaction.

So we're asking "Is this from you" rather than "Did you initiate this  =

dialog"?

It still seems like it might be a useful thing to know. Of course,  =

this argues that 42325 may be the wrong basis.

Now, if we'd just made SIP work with opposing pairs of two-way  =

transactions for everything, instead of singular two and three-way  =

transactions, we could build confirmation options into everything. But  =

we didn't.


Now, from a security perspective: Who's done the analysis on whether  =

DERIVE introduces new attack opportunities?

For example, is there a DOS opportunity in using the home proxy as a  =

message-exploder for source-forged SUBSCRIBE requests? Seems like thre  =

might be a problem there . . .

--
Dean

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


From sip-bounces@ietf.org  Fri Oct 31 15:11:56 2008
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B4BF628C2A0;
	Fri, 31 Oct 2008 15:11:56 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 42B1B28C1E6
	for <sip@core3.amsl.com>; Fri, 31 Oct 2008 15:11:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.576
X-Spam-Level: 
X-Spam-Status: No, score=-2.576 tagged_above=-999 required=5 tests=[AWL=0.023, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ElyzPe1-1kSZ for <sip@core3.amsl.com>;
	Fri, 31 Oct 2008 15:11:54 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164])
	by core3.amsl.com (Postfix) with ESMTP id 6645828C26F
	for <sip@ietf.org>; Fri, 31 Oct 2008 15:11:54 -0700 (PDT)
Received: from [192.168.2.102] (cpe-76-185-142-113.tx.res.rr.com
	[76.185.142.113]) (authenticated bits=0)
	by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id
	m9VMBmwU004532
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT);
	Fri, 31 Oct 2008 17:11:50 -0500
Message-Id: <CEF61ADA-D79F-4D11-A3CA-9C101CA67226@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Dale.Worley@comcast.net
In-Reply-To: <200810311754.m9VHs09X57587141@shell01.TheWorld.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Fri, 31 Oct 2008 17:11:43 -0500
References: <200810251926.17644.ibc@aliax.net> <490382B6.1090400@cisco.com>
	<200810252305.20030.ibc@aliax.net>
	<200810290236.m9T2asoN55836835@shell01.TheWorld.com>
	<cc1f582e0810290225j44b5075bsedc4148143c5046b@mail.gmail.com>
	<200810311754.m9VHs09X57587141@shell01.TheWorld.com>
X-Mailer: Apple Mail (2.929.2)
Cc: sip@ietf.org
Subject: Re: [Sip] [RFC 4235 & draft-kuthan-sip-derive] 481 "Call
	doesn't	exist" for initial SUBSCRIBE ?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
	<mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org


On Oct 31, 2008, at 12:54 PM, Dale.Worley@comcast.net wrote:

>   From: "=?UTF-8?Q?I=C3=B1aki_Baz_Castillo?=" <ibc@aliax.net>
>
>> In any case, for the purposes of DERIVE, none of that matters:
>> Any failure response to the SUBSCRIBE, or a NOTIFY that does not
>> list the call in question, results in call rejection.
>
>   But this behaviour would deny calls from devices not supporting
>   RFC4235 (receiving a SUBSCRIBE Event: dialog).AFAIK this draft says
>   that if the SUBSCRIBE is replied with 200 thenthe dialog exists and
>   identity verified, if 481 then the devicesupports RFC 4235 and it's
>   a suspicius call, and for any other failureroute it could mean that
>   the device doesn't support RFC 4235 or anykind of "protection" in
>   an intermediary proxy. In the last case, thereceptor of the INVITE
>   should choose to accept or deny the call, hecannot know if the
>   sender is really the From (or if he is not).

clearly one needs a Supported option-tag in the initial request to let  
the called party know that it might be reasonable to try to RRC using  
DERIVE.


--
Dean


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


