From cheri@jacksonorthopedics.com Thu Jan 1 05:27:37 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C4E628C604; Thu, 1 Jan 2009 05:27:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -35.017 X-Spam-Level: X-Spam-Status: No, score=-35.017 tagged_above=-999 required=5 tests=[BAYES_99=3.5, HELO_EQ_PL=1.135, HOST_EQ_PL=1.95, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N8H1MWUtDDlF; Thu, 1 Jan 2009 05:27:37 -0800 (PST) Received: from 093105157140.bpl.vectranet.pl (093105157140.bpl.vectranet.pl [93.105.157.140]) by core3.amsl.com (Postfix) with SMTP id 1FE8B29599E; Thu, 1 Jan 2009 05:12:01 -0800 (PST) Message-ID: Date: Thu, 01 Jan 2009 08:11:55 -0500 From: "Rex Bullock" Subject: Gucci watch for a New Year Gift! To: sip@ietf.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Dear Rex, Christmas is the time to get Omega watch, and the only place to get top notch watches that look and perform exactly like the originals is http://www.clipcape.com/ Take an extra 15% off your purchase during month of December. http://www.clipcape.com/ Our Omega watches have perfect weight and feel same as orginal. Sincerely, Mr Bullock From sip-bounces@ietf.org Thu Jan 1 11:05:58 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 14CFF28C16B; Thu, 1 Jan 2009 11:05:58 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6244028C16B for ; Thu, 1 Jan 2009 11:05:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.385 X-Spam-Level: X-Spam-Status: No, score=-6.385 tagged_above=-999 required=5 tests=[AWL=0.214, 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 6441ronSYK+q for ; Thu, 1 Jan 2009 11:05:55 -0800 (PST) Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 4334E28C16A for ; Thu, 1 Jan 2009 11:05:52 -0800 (PST) Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n01J5bm18088 for ; Thu, 1 Jan 2009 19:05:37 GMT Received: from [47.141.31.221] ([47.141.31.221]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 1 Jan 2009 14:05:24 -0500 From: "Dale Worley" To: SIP Organization: Nortel Networks Date: Thu, 01 Jan 2009 14:05:23 -0500 Message-Id: <1230836723.21939.8.camel@victoria-pingtel-com.us.nortel.com> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8) X-OriginalArrivalTime: 01 Jan 2009 19:05:25.0056 (UTC) FILETIME=[E6FA9400:01C96C43] Subject: [Sip] Duplicate parameter names X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org I know that this question has been wrangled over, but I'm having trouble determining the proper resolution. A SIP name-addr has three types of parameter: URI-parameters, headers, and header-parameters: ;name=value Which of these admit two parameters with the same name? RFC 3261 section 19.1.1 clearly specifies that URI-parameters may not be duplicated. RFC 3261 section 7.3.1 implies that headers can be duplicated, because in SIP requests some headers can appear more than once even though they cannot be combined into a comma-separated list. But what about the header-parameters? I can't find any clear statement in RFC 3261. But I'm sure we've discussed this and come to a conclusion... 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 Thu Jan 1 12:02:51 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0737628C173; Thu, 1 Jan 2009 12:02:51 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1449728C173 for ; Thu, 1 Jan 2009 12:02:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.63 X-Spam-Level: X-Spam-Status: No, score=-2.63 tagged_above=-999 required=5 tests=[AWL=-0.032, 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 UlvPiv5B5nLt for ; Thu, 1 Jan 2009 12:02:49 -0800 (PST) Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com [66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 34F2828C169 for ; Thu, 1 Jan 2009 12:02:49 -0800 (PST) Received: from [75.68.118.126] (port=63098 helo=[192.168.15.103]) by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1LITkY-0007xW-Af; Thu, 01 Jan 2009 12:02:34 -0800 Message-Id: <0E994A1D-91A4-4218-AF50-31D8959B5007@standardstrack.com> From: Eric Burger To: Mahesh In-Reply-To: <026a01c96bcf$759c2720$650710ac@globaledgesoft.com> Mime-Version: 1.0 (Apple Message framework v930.3) X-Priority: 3 Date: Thu, 1 Jan 2009 15:02:31 -0500 References: <026a01c96bcf$759c2720$650710ac@globaledgesoft.com> X-Mailer: Apple Mail (2.930.3) 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.org Subject: Re: [Sip] "Happy New Year " X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0095364881==" Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org --===============0095364881== Content-Type: multipart/signed; boundary=Apple-Mail-19--870118403; micalg=sha1; protocol="application/pkcs7-signature" --Apple-Mail-19--870118403 Content-Type: multipart/alternative; boundary=Apple-Mail-18--870118450 --Apple-Mail-18--870118450 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit I feel very damaged from this message. Are you sure I cannot sue, even if I did do a virus check? :-)) Happy New Year. On Jan 1, 2009, at 12:11 AM, Mahesh wrote: > Hi All, > > Give a Smiling start to the New Year Wishing you & your Family a > Wonderful New Year ahead "Happy New Year " > > Regards > Mahesh > This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION > intended solely for the use of the addressee(s). If you are not the > intended recipient, please notify the sender by e-mail and delete > the original message.Global Edge Software Ltd has taken every > reasonable precaution to minimize this risk, but is not liable for > any damage you may sustain as a result of any virus in this e-mail. > You should carry out your own virus checks before opening the e-mail > or attachment. Global Edge Software Ltd reserves the right to > monitor and review the content of all messages sent to or from this > e-mail address > _______________________________________________ > Sip mailing list https://www.ietf.org/mailman/listinfo/sip > This list is for NEW development of the core SIP 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-18--870118450 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I = feel very damaged from this message. Are you sure I cannot sue, even if = I did do a virus = check?

:-))

Happy New = Year.

On Jan 1, 2009, at 12:11 AM, Mahesh = wrote:

Hi = All,
 
Give a = Smiling start to the New Year Wishing you & your = Family a Wonderful New Year ahead "Happy New Year = "
 
<= font color=3D"#800000">Regards
= Mahesh
This e-mail = contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the = use of the addressee(s). If you are not the intended recipient, please = notify the sender by e-mail and delete the original message.Global Edge = Software Ltd has taken every reasonable precaution to minimize this = risk, but is not liable for any damage you may sustain as a result of = any virus in this e-mail. You should carry out your own virus checks = before opening the e-mail or attachment. Global Edge Software Ltd = reserves the right to monitor and review the content of all messages = sent to or from this e-mail = address
_______________________________________________
Sip = mailing list  https://www.ietf.org/ma= ilman/listinfo/sip
This list is for NEW development of the core = SIP Protocol
Use sip-implementors@cs.colum= bia.edu for = questions on current sip
Use sipping@ietf.org for new developments on the = application of = sip

= --Apple-Mail-18--870118450-- --Apple-Mail-19--870118403 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 9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wOTAxMDEyMDAyMzJaMCMGCSqGSIb3 DQEJBDEWBBR1iRvipG8yoKd7pecmNRtHSmDDEjCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2 MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN H2TynzANBgkqhkiG9w0BAQEFAASCAQBQ2McadQDknbrC77SLUi3iLcYLa2/7xPYqNbIGkg+psgi1 1hmYXW/dOHjGpF/MBzuwcFqoNrbHU7FQAd8gtQNGXpRmTpYIcVWQx/RCLJX5FJkoQCoeyCrpOBAL Uv0Iznk2g4MCdWiFuPfmgSHHSLD9LpLAnskWNvB1uj+k2Qj8tWv0WLAEYARu7Iqp3FyCG1w//1XO ezZ5a9cB5TSESiBD6G4aDMHdW0tfUyFP08dc3J92JxN6lziA0w/SPckHIwoae1DDqq4S52JJzgp8 IuyLwF67MAXWlj35U/p0xiqVD9SBrO4QgH45uOx87TiEwNQmslh/mxH1kVU3DurY/M21AAAAAAAA --Apple-Mail-19--870118403-- --===============0095364881== 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 --===============0095364881==-- From sip-bounces@ietf.org Thu Jan 1 16:11:37 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 447073A6A2D; Thu, 1 Jan 2009 16:11:37 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C6E73A69CE for ; Thu, 1 Jan 2009 16:11:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.511 X-Spam-Level: X-Spam-Status: No, score=-6.511 tagged_above=-999 required=5 tests=[AWL=0.088, 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 A-pH5Dq-rqX7 for ; Thu, 1 Jan 2009 16:11:35 -0800 (PST) Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 12BBD3A686A for ; Thu, 1 Jan 2009 16:11:34 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.36,315,1228089600"; d="scan'208";a="32526195" Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 02 Jan 2009 00:11:22 +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 n020BMFK019798; Thu, 1 Jan 2009 19:11:22 -0500 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 n020BMmJ007342; Fri, 2 Jan 2009 00:11:22 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, 1 Jan 2009 19:02:51 -0500 Received: from [10.86.243.39] ([10.86.243.39]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 1 Jan 2009 19:02:51 -0500 Message-ID: <495D59AB.3080309@cisco.com> Date: Thu, 01 Jan 2009 19:02:51 -0500 From: Paul Kyzivat User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Dale Worley References: <1230836723.21939.8.camel@victoria-pingtel-com.us.nortel.com> In-Reply-To: <1230836723.21939.8.camel@victoria-pingtel-com.us.nortel.com> X-OriginalArrivalTime: 02 Jan 2009 00:02:51.0627 (UTC) FILETIME=[745D33B0:01C96C6D] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1338; t=1230855082; x=1231719082; 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 |Subject:=20Re=3A=20[Sip]=20Duplicate=20parameter=20names |Sender:=20 |To:=20Dale=20Worley=20; bh=9d7JiSN9gLcZHNlcjkrITJN8yLmOSD3O6i+eRU3jhC8=; b=Qv4KqTvf3lYlsmxOuSvDyPG3WNMGXargMwdOR94ZDuOjC/FLoFlk5p1v+R NQ1W+9GuK60tR2XapBuAcOg2hlvtpzb/HOrDzpmSeIb7RIGiI+llq8a2p1ZO tK7mPfdQrT; Authentication-Results: rtp-dkim-1; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; ); Cc: SIP Subject: Re: [Sip] Duplicate parameter names X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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 Dale Worley wrote: > I know that this question has been wrangled over, but I'm having trouble > determining the proper resolution. > > A SIP name-addr has three types of parameter: URI-parameters, headers, > and header-parameters: > > > > ;name=value > > Which of these admit two parameters with the same name? > > RFC 3261 section 19.1.1 clearly specifies that URI-parameters may not be > duplicated. > > RFC 3261 section 7.3.1 implies that headers can be duplicated, because > in SIP requests some headers can appear more than once even though they > cannot be combined into a comma-separated list. > > But what about the header-parameters? I can't find any clear statement > in RFC 3261. But I'm sure we've discussed this and come to a > conclusion... Section 7.3.1 of 3261: Many existing header fields will adhere to the general form of a value followed by a semi-colon separated sequence of parameter-name, parameter-value pairs: field-name: field-value *(;parameter-name=parameter-value) Even though an arbitrary number of parameter pairs may be attached to a header field value, any given parameter-name MUST NOT appear more than once. 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 donotreply@forse.com Thu Jan 1 17:52:23 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D789A3A6859 for ; Thu, 1 Jan 2009 17:52:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 4.348 X-Spam-Level: **** X-Spam-Status: No, score=4.348 tagged_above=-999 required=5 tests=[AWL=0.409, BAYES_50=0.001, FORGED_MUA_OUTLOOK=3.116, FORGED_OUTLOOK_TAGS=0.001, HTML_MESSAGE=0.001, MSOE_MID_WRONG_CASE=0.82] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vZG7m5NBhJof for ; Thu, 1 Jan 2009 17:52:23 -0800 (PST) Received: from smtp2.tdm.co.mz (mail.tdm.co.mz [41.220.162.35]) by core3.amsl.com (Postfix) with ESMTP id 34D253A67FD for ; Thu, 1 Jan 2009 17:52:21 -0800 (PST) Received: (qmail 21123 invoked by uid 507); 2 Jan 2009 00:56:23 +0200 Received: from unknown (HELO Munjal-PC) (41.220.167.86) by smtp2.tdm.co.mz with SMTP; 2 Jan 2009 00:56:13 +0200 From: "Cheapest Calls." subject: ***High level SPAM*** sip-archive secret of making cheapest international calls right from your mobile phone. To: "sip-archive" Content-Type: multipart/alternative; boundary="=_NextPart_2rfkindysadvnqw3nerasdf"; charset="windows-1252" MIME-Version: 1.0 Date: Fri, 2 Jan 2009 00:56:45 +0200 X-Priority: 3 X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-vamsi: scanned Message-Id: <20090102015222.34D253A67FD@core3.amsl.com> This is a multi-part message in MIME format --=_NextPart_2rfkindysadvnqw3nerasdf Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Hi sip-archive ,=20 Are you looking for cheapest internation calls ? We can provide you Best Voice Quality Right from your Mobile Phone @ Lo= west Rates and Per Second Billing.=20 Some sample rates are as follows in USD per min. Brazil 0.0414=20 Phillipines 0.1290=20 India 0.0529 Nigeria 0.1297 Italy 0.0259 Zimbabwe 0.0725 UK 0.0227 Pakistan 0.0995=20 UAE 0.1645 Saudi Arebia 0.1081=20 Sigapore 0.0232=20 Japan 0.0357=20 For more information do email us only on cheapestcalls@indiatimes.com=20= Please do not reply to sender's email. That will not reach to us. Thanks.=20 --=_NextPart_2rfkindysadvnqw3nerasdf Content-Type: text/html; charset="windows-1252" Content-Transfer-Encoding: quoted-printable
Hi  sip-archive=20 ,
 
 
Are you=20 looking for cheapest internation calls ?
 
 
We can=20 provide you  Best Voice Quality Right from your= Mobile=20 Phone @ Lowest Rates and Per Second Billing.=20 =20
 
Some sampl= e rates are as=20 follows in USD per min.
 
Brazil        &n= bsp;  =20 0.0414=20
Phillipines      0.1290 =
India        &nb= sp;    0.0529
Nigeria        &= nbsp;0.1297
Italy        &nb= sp;     0.0259
Zimbabwe     0.0725
 UK        =       0.0227
Pakistan       =20 0.0995
UAE         = ;    0.1645
Saudi Arebia 0.1081
Sigapore       0.0232
Japan        &nb= sp;  =20 0.0357=20
 
 
 For more information do email us only on cheapestcalls@indiatimes.c= om
 
Please do not reply to sender's email= That will not reach to=20 us.
 
Thanks.
--=_NextPart_2rfkindysadvnqw3nerasdf-- From sip-bounces@ietf.org Thu Jan 1 18:55:09 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E9393A6954; Thu, 1 Jan 2009 18:55:09 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1E9363A67FD for ; Thu, 1 Jan 2009 18:55:08 -0800 (PST) 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 BWIOQKk1lYj4 for ; Thu, 1 Jan 2009 18:55:07 -0800 (PST) Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id 5C0D63A684C for ; Thu, 1 Jan 2009 18:55:07 -0800 (PST) Received: from [192.168.2.102] (cpe-72-181-150-177.tx.res.rr.com [72.181.150.177] (may be forged)) (authenticated bits=0) by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id n022smBV007176 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 1 Jan 2009 20:54:50 -0600 From: Dean Willis To: Eric Burger In-Reply-To: <0E994A1D-91A4-4218-AF50-31D8959B5007@standardstrack.com> X-Priority: 3 References: <026a01c96bcf$759c2720$650710ac@globaledgesoft.com> <0E994A1D-91A4-4218-AF50-31D8959B5007@standardstrack.com> Message-Id: <8A90B82D-6F38-416F-86DC-24178974CB72@softarmor.com> Mime-Version: 1.0 (Apple Message framework v930.3) Date: Thu, 1 Jan 2009 20:54:43 -0600 X-Mailer: Apple Mail (2.930.3) Cc: sip@ietf.org, Mahesh Subject: Re: [Sip] "Happy New Year " X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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 Jan 1, 2009, at 2:02 PM, Eric Burger wrote: > I feel very damaged from this message. Are you sure I cannot sue, > even if I did do a virus check? > Hey, you live in the USA. You can sue anybody you want, anytime you want, and you can probably pick a favorable court to do it in. That's what makes the USA such a great place. But as for feeling damaged, that's probably just the aftermath of last night's party consumables . Try Alka-Seltzer. Happy New Year! -- 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 jkiffedd@advanced-connect.net Thu Jan 1 20:58:44 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 42E3328C19E for ; Thu, 1 Jan 2009 20:58:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.611 X-Spam-Level: X-Spam-Status: No, score=-15.611 tagged_above=-999 required=5 tests=[BAYES_99=3.5, HELO_EQ_DSL=1.129, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_SBL=20, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8jf5wU-JNhcH for ; Thu, 1 Jan 2009 20:58:43 -0800 (PST) Received: from athedsl-328118.home.otenet.gr (athedsl-338142.home.otenet.gr [85.72.176.124]) by core3.amsl.com (Postfix) with SMTP id 18D6D28C19C for ; Thu, 1 Jan 2009 20:58:41 -0800 (PST) To: Subject: Happy New Year! From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090102045842.18D6D28C19C@core3.amsl.com> Date: Thu, 1 Jan 2009 20:58:41 -0800 (PST)


Please do not reply to this email. To contact Max Volume, please visit us

This email message was sent to . If you do not wish to receive further communications from Max Volume, click here to unsubscribe.

If you've experience any difficulty in being removed from a Max Volume email list, click here for personalized help.

Copyright © 2008 Max Volume, Inc. All rights reserved.
65856 A Alaska, Luissvill, AT 43125

From krispy_69@aerovironment.com Thu Jan 1 22:30:01 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8DC773A6895 for ; Thu, 1 Jan 2009 22:30:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.227 X-Spam-Level: X-Spam-Status: No, score=-7.227 tagged_above=-999 required=5 tests=[BAYES_99=3.5, DNS_FROM_RFC_BOGUSMX=1.482, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, GB_I_LETTER=-2, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_BR=0.955, HOST_EQ_BR=1.295, HTML_EXTRA_CLOSE=2.809, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_UNI=0.591, TVD_RCVD_IP=1.931, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2debdtv--zYJ for ; Thu, 1 Jan 2009 22:30:00 -0800 (PST) Received: from 189-69-175-105.dial-up.telesp.net.br (189-69-175-105.dial-up.telesp.net.br [189.69.175.105]) by core3.amsl.com (Postfix) with SMTP id C546D3A67A4 for ; Thu, 1 Jan 2009 22:29:59 -0800 (PST) To: Subject: Your message could not be delivered From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090102062959.C546D3A67A4@core3.amsl.com> Date: Thu, 1 Jan 2009 22:29:59 -0800 (PST) About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

C2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 98052
From nabe-mj@agate.plala.or.jp Fri Jan 2 00:00:06 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D05593A6B0A for ; Fri, 2 Jan 2009 00:00:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.993 X-Spam-Level: X-Spam-Status: No, score=-2.993 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_NJABL_PROXY=1.643, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_NONE=0.1, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_SBL=20, URIBL_SC_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kU+zXodcPqBn for ; Thu, 1 Jan 2009 23:59:57 -0800 (PST) Received: from amis.com (unknown [194.208.128.101]) by core3.amsl.com (Postfix) with SMTP id 6FC5E3A6AF8 for ; Thu, 1 Jan 2009 23:59:55 -0800 (PST) To: Subject: May your Dreams Come True! From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090102075956.6FC5E3A6AF8@core3.amsl.com> Date: Thu, 1 Jan 2009 23:59:55 -0800 (PST)


Please do not reply to this email. To contact Max Volume, please visit us

This email message was sent to . If you do not wish to receive further communications from Max Volume, click here to unsubscribe.

If you've experience any difficulty in being removed from a Max Volume email list, click here for personalized help.

Copyright © 2008 Max Volume, Inc. All rights reserved.
65856 A Alaska, Luissvill, AT 43125

From angela@hollywoodos.com Fri Jan 2 01:25:29 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C4653A68A9; Fri, 2 Jan 2009 01:25:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -20.413 X-Spam-Level: X-Spam-Status: No, score=-20.413 tagged_above=-999 required=5 tests=[AWL=-2.521, BAYES_80=2, HELO_EQ_BR=0.955, HOST_EQ_BR=1.295, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_SBL=20, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SA0EOMiLKd7I; Fri, 2 Jan 2009 01:25:28 -0800 (PST) Received: from 20151098074.user.veloxzone.com.br (20151098074.user.veloxzone.com.br [201.51.98.74]) by core3.amsl.com (Postfix) with SMTP id 8F1BA3A683D; Fri, 2 Jan 2009 01:25:03 -0800 (PST) Message-ID: Date: Fri, 02 Jan 2009 04:24:55 -0500 From: "Tamara Crawford" Subject: IWC watch models from 2009! To: sip@ietf.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Dear Tamara, Christmas is the time to get Jaeger LeCoultre watch, and the only place to get top notch watches that look and perform exactly like the originals is http://www.peonmine.com/ With top notch customer service and super warranty, we stand behind our watches. http://www.peonmine.com/ Our Jaeger LeCoultre have all appropriate markings, wordings and engravings same as orginal. Sincerely, Mr Crawford From sip-bounces@ietf.org Fri Jan 2 07:34:38 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 600B63A6832; Fri, 2 Jan 2009 07:34:38 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 02C1D3A6832 for ; Fri, 2 Jan 2009 07:34:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.451 X-Spam-Level: X-Spam-Status: No, score=-6.451 tagged_above=-999 required=5 tests=[AWL=0.148, 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 Xum1j3uI-lVH for ; Fri, 2 Jan 2009 07:34:36 -0800 (PST) Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 25AE13A63D2 for ; Fri, 2 Jan 2009 07:34:35 -0800 (PST) Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n02FYKP22020; Fri, 2 Jan 2009 15:34:20 GMT Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 2 Jan 2009 10:34:04 -0500 From: "Dale Worley" To: Johansson Olle E In-Reply-To: <07953AE2-F02A-4E6D-82F5-6730383B44FF@edvina.net> References: <07953AE2-F02A-4E6D-82F5-6730383B44FF@edvina.net> Organization: Nortel Networks Date: Fri, 02 Jan 2009 10:34:04 -0500 Message-Id: <1230910444.3835.1.camel@victoria-pingtel-com.us.nortel.com> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8) X-OriginalArrivalTime: 02 Jan 2009 15:34:04.0578 (UTC) FILETIME=[8B3CF020:01C96CEF] Cc: IETF SIP List , Dean Willis Subject: Re: [Sip] News article on CA impersonation attack X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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-12-30 at 21:30 +0100, Johansson Olle E wrote: > Also: How can we move away from MD5 digest auth? The authentication headers all allow the algorithm to be specified, so we can convert to SHA1 fairly straightforwardly. But the current attack benefits from the fact that one can spend hours synthesizing a certificate. I doubt one could attack a SIP session setup fast enough to be useful with reasonably-priced hardware. But that will come with time... 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 Jan 2 08:17:46 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 028543A69C3; Fri, 2 Jan 2009 08:17:46 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D9AEE3A69F2 for ; Fri, 2 Jan 2009 08:17:44 -0800 (PST) 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_SE=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 EVHh+4lkIOuf for ; Fri, 2 Jan 2009 08:17:44 -0800 (PST) Received: from ns.webway.se (ns.webway.se [87.96.134.125]) by core3.amsl.com (Postfix) with ESMTP id 2B8C53A695E for ; Fri, 2 Jan 2009 08:17:16 -0800 (PST) Received: from [192.168.40.21] (unknown [192.168.40.21]) by ns.webway.se (Postfix) with ESMTP id 0797526C06; Fri, 2 Jan 2009 17:17:05 +0100 (CET) From: Johansson Olle E To: "Dale Worley" In-Reply-To: <1230910444.3835.1.camel@victoria-pingtel-com.us.nortel.com> References: <07953AE2-F02A-4E6D-82F5-6730383B44FF@edvina.net> <1230910444.3835.1.camel@victoria-pingtel-com.us.nortel.com> Message-Id: <5D6CB5AC-3ADF-4294-89E9-2FA197545865@edvina.net> Mime-Version: 1.0 (Apple Message framework v930.3) Date: Fri, 2 Jan 2009 17:17:02 +0100 X-Mailer: Apple Mail (2.930.3) Cc: IETF SIP List Subject: Re: [Sip] News article on CA impersonation attack X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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 2 jan 2009 kl. 16.34 skrev Dale Worley: > On Tue, 2008-12-30 at 21:30 +0100, Johansson Olle E wrote: >> Also: How can we move away from MD5 digest auth? > > The authentication headers all allow the algorithm to be specified, so > we can convert to SHA1 fairly straightforwardly. But the current > attack > benefits from the fact that one can spend hours synthesizing a > certificate. I doubt one could attack a SIP session setup fast enough > to be useful with reasonably-priced hardware. But that will come with > time... We need some implementation guidelines for doing this. How do we respond to an MD5 auth request we don't accept? If for some strange reason, I want to support both old MD5 UA's and new SHAx UA's - how do I indicate both? We propably need some test code and test scenarios here. /O _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.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 Jan 2 08:27:30 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CEE2D3A68F9; Fri, 2 Jan 2009 08:27:30 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5207C3A68F9 for ; Fri, 2 Jan 2009 08:27:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.457 X-Spam-Level: X-Spam-Status: No, score=-6.457 tagged_above=-999 required=5 tests=[AWL=0.142, 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 5SRt3LR47Gzo for ; Fri, 2 Jan 2009 08:27:29 -0800 (PST) Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 093A93A67D6 for ; Fri, 2 Jan 2009 08:27:28 -0800 (PST) Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n02GRDP27772; Fri, 2 Jan 2009 16:27:13 GMT Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 2 Jan 2009 11:27:13 -0500 From: "Dale Worley" To: Johansson Olle E In-Reply-To: <5D6CB5AC-3ADF-4294-89E9-2FA197545865@edvina.net> References: <07953AE2-F02A-4E6D-82F5-6730383B44FF@edvina.net> <1230910444.3835.1.camel@victoria-pingtel-com.us.nortel.com> <5D6CB5AC-3ADF-4294-89E9-2FA197545865@edvina.net> Organization: Nortel Networks Date: Fri, 02 Jan 2009 11:27:13 -0500 Message-Id: <1230913633.3835.29.camel@victoria-pingtel-com.us.nortel.com> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8) X-OriginalArrivalTime: 02 Jan 2009 16:27:13.0327 (UTC) FILETIME=[F7E16BF0:01C96CF6] Cc: IETF SIP List Subject: Re: [Sip] News article on CA impersonation attack X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org On Fri, 2009-01-02 at 17:17 +0100, Johansson Olle E wrote: > 2 jan 2009 kl. 16.34 skrev Dale Worley: > > > On Tue, 2008-12-30 at 21:30 +0100, Johansson Olle E wrote: > >> Also: How can we move away from MD5 digest auth? > > > > The authentication headers all allow the algorithm to be specified, so > > we can convert to SHA1 fairly straightforwardly. But the current > > attack > > benefits from the fact that one can spend hours synthesizing a > > certificate. I doubt one could attack a SIP session setup fast enough > > to be useful with reasonably-priced hardware. But that will come with > > time... > > We need some implementation guidelines for doing this. How do we > respond to an MD5 auth request we don't accept? > > If for some strange reason, I want to support both old MD5 UA's and > new SHAx UA's - how do I indicate both? > > We propably need some test code and test scenarios here. There isn't any negotiation mechanism for auth algorithms. But if you generate both, you could include two auth headers for your realm, one with 'algorithm=MD5' and one with 'algorithm=SHA1'. Of course, we have yet to define the details of the header with 'algorithm=SHA1'. The current method of rejecting the use of any particular authentication system is for the UAS to ignore the auth header generated by that system, which usually results in the UAC receiving a 401/407 response to a request which carries all the credentials the UAC is prepared to attach to the request. So the UAC gives up on the request (and returns the 401/407 to the application layer). 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 Jan 2 08:39:09 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7BE2128C11E; Fri, 2 Jan 2009 08:39:09 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8EA7028C110 for ; Fri, 2 Jan 2009 08:39:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.462 X-Spam-Level: X-Spam-Status: No, score=-6.462 tagged_above=-999 required=5 tests=[AWL=0.137, 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 VeFenHBkEebS for ; Fri, 2 Jan 2009 08:39:07 -0800 (PST) Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id B02B628C0F5 for ; Fri, 2 Jan 2009 08:39:07 -0800 (PST) Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n02GcMP28781; Fri, 2 Jan 2009 16:38:22 GMT Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 2 Jan 2009 11:38:22 -0500 From: "Dale Worley" To: Paul Kyzivat In-Reply-To: <495D59AB.3080309@cisco.com> References: <1230836723.21939.8.camel@victoria-pingtel-com.us.nortel.com> <495D59AB.3080309@cisco.com> Organization: Nortel Networks Date: Fri, 02 Jan 2009 11:38:21 -0500 Message-Id: <1230914301.3835.32.camel@victoria-pingtel-com.us.nortel.com> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8) X-OriginalArrivalTime: 02 Jan 2009 16:38:22.0206 (UTC) FILETIME=[869041E0:01C96CF8] Cc: SIP Subject: Re: [Sip] Duplicate parameter names X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org On Thu, 2009-01-01 at 19:02 -0500, Paul Kyzivat wrote: > Section 7.3.1 of 3261: > > Many existing header fields will adhere to the general form of a > value followed by a semi-colon separated sequence of parameter-name, > parameter-value pairs: > > field-name: field-value *(;parameter-name=parameter-value) > > Even though an arbitrary number of parameter pairs may be attached to > a header field value, any given parameter-name MUST NOT appear more > than once. Thanks! I was wondering why I didn't find it when searching 3261, and it seems to be because the word "parameter" isn't preceded by "header" or "field" anywhere in that passage. 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 Jan 2 08:45:53 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 702113A69BD; Fri, 2 Jan 2009 08:45:53 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 51DF23A69BD for ; Fri, 2 Jan 2009 08:45:51 -0800 (PST) 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_SE=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 AME3csB8BxMD for ; Fri, 2 Jan 2009 08:45:50 -0800 (PST) Received: from ns.webway.se (ns.webway.se [87.96.134.125]) by core3.amsl.com (Postfix) with ESMTP id 3B3B13A695E for ; Fri, 2 Jan 2009 08:45:49 -0800 (PST) Received: from [192.168.40.21] (unknown [192.168.40.21]) by ns.webway.se (Postfix) with ESMTP id 7F64F26C06; Fri, 2 Jan 2009 17:45:38 +0100 (CET) From: Johansson Olle E To: "Dale Worley" In-Reply-To: <1230913633.3835.29.camel@victoria-pingtel-com.us.nortel.com> References: <07953AE2-F02A-4E6D-82F5-6730383B44FF@edvina.net> <1230910444.3835.1.camel@victoria-pingtel-com.us.nortel.com> <5D6CB5AC-3ADF-4294-89E9-2FA197545865@edvina.net> <1230913633.3835.29.camel@victoria-pingtel-com.us.nortel.com> Message-Id: <2DC20D47-8F42-486A-9D18-AE6A6FA86001@edvina.net> Mime-Version: 1.0 (Apple Message framework v930.3) Date: Fri, 2 Jan 2009 17:45:36 +0100 X-Mailer: Apple Mail (2.930.3) Cc: IETF SIP List Subject: Re: [Sip] Implementing SHA digest auth (new topic) X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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 2 jan 2009 kl. 17.27 skrev Dale Worley: > On Fri, 2009-01-02 at 17:17 +0100, Johansson Olle E wrote: >> 2 jan 2009 kl. 16.34 skrev Dale Worley: >> >>> On Tue, 2008-12-30 at 21:30 +0100, Johansson Olle E wrote: >>>> Also: How can we move away from MD5 digest auth? >>> >>> The authentication headers all allow the algorithm to be >>> specified, so >>> we can convert to SHA1 fairly straightforwardly. But the current >>> attack >>> benefits from the fact that one can spend hours synthesizing a >>> certificate. I doubt one could attack a SIP session setup fast >>> enough >>> to be useful with reasonably-priced hardware. But that will come >>> with >>> time... >> >> We need some implementation guidelines for doing this. How do we >> respond to an MD5 auth request we don't accept? >> >> If for some strange reason, I want to support both old MD5 UA's and >> new SHAx UA's - how do I indicate both? >> >> We propably need some test code and test scenarios here. > > There isn't any negotiation mechanism for auth algorithms. But if you > generate both, you could include two auth headers for your realm, one > with 'algorithm=MD5' and one with 'algorithm=SHA1'. > > Of course, we have yet to define the details of the header with > 'algorithm=SHA1'. Might as well define all SHA's at the same time and prepare for new algorithms as well. The HTTP digest auth RFC doesn't really mention much about this. My experience from SIPit tests tells me we need very detailed guidelines for developers as well as test suites, reference implementations, to test with in order for any change to happen. > > > The current method of rejecting the use of any particular > authentication > system is for the UAS to ignore the auth header generated by that > system, which usually results in the UAC receiving a 401/407 > response to > a request which carries all the credentials the UAC is prepared to > attach to the request. So the UAC gives up on the request (and > returns > the 401/407 to the application layer). So in that case, the implementation guideline for an UA set for both methods would be to first try with the strongest algorithm, then upon reception of a 401/407 to that one, test with the next one in list until it is out of algorithms in which case the 401/407 means that the password is indeed wrong. The UA could also, as you point out, send all headers at once to make it a quicker round-trip, but doing it that way would also expose the weaker MD5 hash which we want to avoid. Thanks for your replies, Dale. This seems easier than expected. Anyone else that sees any caveats or issues? /O _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.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 Jan 2 10:00:03 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 527CB3A696B; Fri, 2 Jan 2009 10:00:03 -0800 (PST) X-Original-To: sip@ietf.org Delivered-To: sip@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id E0EAB3A69A4; Fri, 2 Jan 2009 10:00:01 -0800 (PST) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20090102180001.E0EAB3A69A4@core3.amsl.com> Date: Fri, 2 Jan 2009 10:00:01 -0800 (PST) Cc: sip@ietf.org Subject: [Sip] I-D Action:draft-ietf-sip-info-events-02.txt X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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-02.txt Pages : 37 Date : 2009-01-02 This document defines the new SIP INFO method and a mechanism for defining, negotiating and exchanging Info Packages that use the INFO method. Applications that need to exchange session-related information within a SIP INVITE-created dialog, also known as application level information, 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]. The terminology in this document conforms to the Internet Security Glossary [RFC4949]. Be mindful of the terms User Agent Server (UAS) and User Agent Client (UAC). This document strictly follows RFC 3261 [RFC3261]. The UAC issues a SIP request and the UAS responds. This terminology may be confusing when one combines the INFO case with the INVITE case. For an INVITE, the initiator of the session is the UAC and the target of the session is the UAS. However, it is possible for the target UA of the session, the UAS of the INVITE transaction, to send an INFO to the initiating UA of the session, the UAC of the INVITE transaction. >From the perspective of the INFO, the target UA of the session (INVITE UAS) is, in fact, the UAC (sender) of the INFO request. Likewise, from the perspective of the INFO, the initiating UA of the session (INVITE UAC) is the UAS (recipient) of the INFO request. Since this document strictly follows RFC 3261, we refer to the UA that issues the INVITE as the "initiating UA" and the UA that responds to the INVITE as the "target UA" to remove any confusion. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sip-info-events-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-info-events-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-01-02094627.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 michelle.branco@24hourmall.com Fri Jan 2 11:23:50 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B95E28C146 for ; Fri, 2 Jan 2009 11:23:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -32.466 X-Spam-Level: X-Spam-Status: No, score=-32.466 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_VERIZON_P=2.144, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_VERIZON_POOL=1.495, HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_HTML_A_BODY=0.742, SARE_HTML_IMG_ONLY=1.666, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_RHS_DOB=1.083, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o0ZnNm3GMcEo for ; Fri, 2 Jan 2009 11:23:50 -0800 (PST) Received: from adcb.com (84.91.56.190.dsl.intelnet.net.gt [190.56.91.84]) by core3.amsl.com (Postfix) with SMTP id 8778428C11F for ; Fri, 2 Jan 2009 11:23:49 -0800 (PST) To: Subject: Let's meet as usually From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090102192349.8778428C11F@core3.amsl.com> Date: Fri, 2 Jan 2009 11:23:49 -0800 (PST) Having trouble viewing this email? Click here to view as a webpage. From a.yepes@vestilab.com Fri Jan 2 13:04:28 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E865B28C11F; Fri, 2 Jan 2009 13:04:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -12.533 X-Spam-Level: X-Spam-Status: No, score=-12.533 tagged_above=-999 required=5 tests=[BAYES_60=1, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DSL=1.129, HELO_EQ_RU=0.595, HOST_EQ_RU=0.875, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_SBL=20, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lN43fr5FVJte; Fri, 2 Jan 2009 13:04:28 -0800 (PST) Received: from ppp91-122-78-177.pppoe.avangarddsl.ru (ppp91-122-78-177.pppoe.avangarddsl.ru [91.122.78.177]) by core3.amsl.com (Postfix) with SMTP id C5DEF28C196; Fri, 2 Jan 2009 13:04:06 -0800 (PST) Message-ID: Date: Fri, 02 Jan 2009 16:03:58 -0500 From: "Chelsea Mims" Subject: Gucci watches wholesale all year long! To: sip@ietf.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Dear Chelsea, Christmas is the time to get Gucci watch, and the only place to get top notch watches that look and perform exactly like the originals is http://www.peonmeld.com/ We are offering wholesaler prices on all watches during the month of December. http://www.peonmeld.com/ Our Gucci have Weights/feels and looks exactly same as original. Sincerely, Mr Mims From mmakiti@amec-connectionallay.org Sat Jan 3 06:04:14 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E54483A6821 for ; Sat, 3 Jan 2009 06:04:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.353 X-Spam-Level: X-Spam-Status: No, score=-7.353 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_SBL=20, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gNXajUZyFXBt for ; Sat, 3 Jan 2009 06:04:14 -0800 (PST) Received: from host217-43-31-66.range217-43.btcentralplus.com (host217-43-31-66.range217-43.btcentralplus.com [217.43.31.66]) by core3.amsl.com (Postfix) with SMTP id 410BB3A6894 for ; Sat, 3 Jan 2009 06:04:12 -0800 (PST) To: Subject: A touch of pure elegance From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090103140413.410BB3A6894@core3.amsl.com> Date: Sat, 3 Jan 2009 06:04:12 -0800 (PST)

Shiny pieces of pure beauty that will simply blow her mind!


Please do not reply to this email. To contact Armstrong Shank Advertising, please visit us

This email message was sent to . If you do not wish to receive further communications from Armstrong Shank Advertising, click here to unsubscribe.

If you've experience any difficulty in being removed from a Armstrong Shank Advertising email list, click here for personalized help.

Copyright © 2008 Armstrong Shank Advertising, Inc. All rights reserved.
7450 S Seneca, Haysville, KS 67060

From brianna@sexxxnet.net Sat Jan 3 11:42:24 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4E1153A698A; Sat, 3 Jan 2009 11:42:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -71.016 X-Spam-Level: X-Spam-Status: No, score=-71.016 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_PL=1.135, HOST_EQ_PL=1.95, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, URIBL_SBL=20, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Vp-ydX37tI9; Sat, 3 Jan 2009 11:42:23 -0800 (PST) Received: from chello089074034080.chello.pl (chello089074034080.chello.pl [89.74.34.80]) by core3.amsl.com (Postfix) with SMTP id B7F463A6817; Sat, 3 Jan 2009 11:41:53 -0800 (PST) Message-ID: Date: Sat, 03 Jan 2009 14:41:43 -0500 From: "Gerald Goodwin" Subject: Emporio Armani watches wholesale all year long! To: sip@ietf.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Dear Gerald, New Year is the time to get Chopard watch, and the only place to get top notch watches that look and perform exactly like the originals is http://www.wanewall.com/ Take advantage of our christmas specials and get yourself {$WATCH$} watch that you've always wanted! http://www.wanewall.com/ Our Chopard watches have perfect weight and feel same as orginal. Sincerely, Mr Goodwin From alb@wisconsinclub.com Sat Jan 3 23:14:03 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 42BD53A6A6C; Sat, 3 Jan 2009 23:14:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -30.195 X-Spam-Level: X-Spam-Status: No, score=-30.195 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_BR=0.955, HOST_EQ_BR=1.295, HOST_EQ_STATIC=1.172, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033, TVD_RCVD_IP=1.931, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_SBL=20, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uIFc5HXAline; Sat, 3 Jan 2009 23:14:02 -0800 (PST) Received: from 201-048-155-138.static.ctbctelecom.com.br (201-048-155-138.static.ctbctelecom.com.br [201.48.155.138]) by core3.amsl.com (Postfix) with SMTP id 1BE8F3A6A5F; Sat, 3 Jan 2009 23:13:48 -0800 (PST) Message-ID: Date: Sun, 04 Jan 2009 02:13:40 -0500 From: "Odessa Garland" Subject: Take a look at the Jaeger LeCoultre watches! To: sip@ietf.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Dear Odessa, Looking for a Jaeger LeCoultre watch that no one can tell from the original? You're in luck, because we have the best copies http://www.wanemake.com/ From logue@agate.plala.or.jp Sun Jan 4 02:08:16 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 137F33A68CD for ; Sun, 4 Jan 2009 02:08:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -30.588 X-Spam-Level: X-Spam-Status: No, score=-30.588 tagged_above=-999 required=5 tests=[BAYES_99=3.5, GB_I_LETTER=-2, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, HTML_EXTRA_CLOSE=2.809, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, SARE_UNI=0.591, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LCryRlzD6pGX for ; Sun, 4 Jan 2009 02:08:15 -0800 (PST) Received: from chello084114010010.16.14.vie.surfer.at (chello084114010010.16.14.vie.surfer.at [84.114.10.10]) by core3.amsl.com (Postfix) with SMTP id EB2AE3A68AD for ; Sun, 4 Jan 2009 02:08:13 -0800 (PST) To: Subject: Please confirm your message From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090104100813.EB2AE3A68AD@core3.amsl.com> Date: Sun, 4 Jan 2009 02:08:13 -0800 (PST) About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

C2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 98052 From sip-bounces@ietf.org Sun Jan 4 08:24:51 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F34CE3A69C1; Sun, 4 Jan 2009 08:24:50 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BBCD93A6A7E for ; Sun, 4 Jan 2009 08:24:49 -0800 (PST) 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 j-iLpdlBsN+f for ; Sun, 4 Jan 2009 08:24:49 -0800 (PST) Received: from zrtps0kn.nortel.com (zrtps0kn.nortel.com [47.140.192.55]) by core3.amsl.com (Postfix) with ESMTP id CE0213A69A6 for ; Sun, 4 Jan 2009 08:24:48 -0800 (PST) Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n04GOVn23983; Sun, 4 Jan 2009 16:24:31 GMT Received: from [47.141.31.156] ([47.141.31.156]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 4 Jan 2009 11:24:30 -0500 From: "Dale Worley" To: Johansson Olle E In-Reply-To: <2DC20D47-8F42-486A-9D18-AE6A6FA86001@edvina.net> References: <07953AE2-F02A-4E6D-82F5-6730383B44FF@edvina.net> <1230910444.3835.1.camel@victoria-pingtel-com.us.nortel.com> <5D6CB5AC-3ADF-4294-89E9-2FA197545865@edvina.net> <1230913633.3835.29.camel@victoria-pingtel-com.us.nortel.com> <2DC20D47-8F42-486A-9D18-AE6A6FA86001@edvina.net> Organization: Nortel Networks Date: Sun, 04 Jan 2009 11:24:30 -0500 Message-Id: <1231086270.22641.3.camel@victoria-pingtel-com.us.nortel.com> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8) X-OriginalArrivalTime: 04 Jan 2009 16:24:30.0725 (UTC) FILETIME=[EBC9D350:01C96E88] Cc: IETF SIP List Subject: Re: [Sip] Implementing SHA digest auth (new topic) X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org On Fri, 2009-01-02 at 17:45 +0100, Johansson Olle E wrote: > So in that case, the implementation guideline for an UA set for both > methods would be to first try with the strongest algorithm, then upon > reception of a 401/407 to that one, test with the next one in list until it is > out of algorithms in which case the 401/407 means that the password is indeed > wrong. I don't see why you'd want to have a multiple-try algorithm -- if you're willing to send the MD5 hash at all, you should send it the first time. Otherwise you're just adding round-trips before you send the MD5 hash. > The UA could also, as you point out, send all headers at once to make it > a quicker round-trip, but doing it that way would also expose the > weaker MD5 hash which we want to avoid. We actually haven't resolved the question whether using MD5 *exposes* your key. As far as I can tell, what's been shown is that *trusting* an MD5 is not a good idea. But I'm not a crypto expert. 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 madge.fu@akzonobel.com Sun Jan 4 12:05:50 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9DB513A689C for ; Sun, 4 Jan 2009 12:05:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -47.51 X-Spam-Level: X-Spam-Status: No, score=-47.51 tagged_above=-999 required=5 tests=[BAYES_95=3, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_HTML_A_BODY=0.742, SARE_HTML_IMG_ONLY=1.666, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_RHS_DOB=1.083, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xqjj+lA7x4Ti for ; Sun, 4 Jan 2009 12:05:50 -0800 (PST) Received: from 88-199-28-195.tktelekom.pl (88-199-28-195.tktelekom.pl [88.199.28.195]) by core3.amsl.com (Postfix) with SMTP id 5E9143A6972 for ; Sun, 4 Jan 2009 12:05:48 -0800 (PST) To: Subject: Where are you, I'm frozen! From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090104200549.5E9143A6972@core3.amsl.com> Date: Sun, 4 Jan 2009 12:05:48 -0800 (PST) Having trouble viewing this email? Click here to view as a webpage. From 2gkah6kejhh059hf@deutsche-bank.de Sun Jan 4 23:13:40 2009 Return-Path: <2gkah6kejhh059hf@deutsche-bank.de> X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE9E13A6AC1; Sun, 4 Jan 2009 23:13:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -40.687 X-Spam-Level: X-Spam-Status: No, score=-40.687 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_RFC_BOGUSMX=1.482, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_PL=1.135, HOST_EQ_PL=1.95, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aBrgLbSmPAT1; Sun, 4 Jan 2009 23:13:40 -0800 (PST) Received: from host-81-190-221-72.wroclaw.mm.pl (host-81-190-221-72.wroclaw.mm.pl [81.190.221.72]) by core3.amsl.com (Postfix) with SMTP id CA63B3A6A5A; Sun, 4 Jan 2009 23:13:23 -0800 (PST) Message-ID: Date: Mon, 05 Jan 2009 02:13:21 -0500 From: "Joan Kim" Subject: Jaeger LeCoultre cheaper than you could imagine! To: sip@ietf.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Dear Joan, If you've waited to get your Longines watch, this is the right time to go for it. http://www.wanewave.com/ Take an extra 15% off your purchase during month of January (2009). http://www.wanewave.com/ Our Longines have all appropriate markings, wordings and engravings same as orginal. Sincerely, Mr Kim From luell@1164.com Mon Jan 5 10:18:17 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A22333A67D6 for ; Mon, 5 Jan 2009 10:18:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -22.06 X-Spam-Level: X-Spam-Status: No, score=-22.06 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_RELAY_NODNS=1.451, HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RDNS_NONE=0.1, SARE_HTML_A_BODY=0.742, SARE_HTML_IMG_ONLY=1.666, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pskj0Z+LWK3z for ; Mon, 5 Jan 2009 10:18:17 -0800 (PST) Received: from afpc.net.sy (unknown [201.80.68.186]) by core3.amsl.com (Postfix) with SMTP id 13EB03A687B for ; Mon, 5 Jan 2009 10:18:15 -0800 (PST) To: Subject: I've got problems, can't find u From: MIME-Version: 1.0 Importance: High Content-Type: text/html X-Antivirus: avast! (VPS 080630-1, 30/06/2008), Outbound message X-Antivirus-Status: Clean Message-Id: <20090105181816.13EB03A687B@core3.amsl.com> Date: Mon, 5 Jan 2009 10:18:15 -0800 (PST) Having trouble viewing this email? Click here to view as a webpage. From bps@albawardi.com Mon Jan 5 10:51:05 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CC23328C111; Mon, 5 Jan 2009 10:51:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.125 X-Spam-Level: X-Spam-Status: No, score=-6.125 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_DSL=1.129, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, TVD_RCVD_IP=1.931, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_SBL=20, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LHnlXQfmMAgj; Mon, 5 Jan 2009 10:51:05 -0800 (PST) Received: from 239-232-222-201.adsl.terra.cl (239-232-222-201.adsl.terra.cl [201.222.232.239]) by core3.amsl.com (Postfix) with SMTP id 20C2428C0E2; Mon, 5 Jan 2009 10:50:51 -0800 (PST) Message-ID: From: "Thad Talbot" Date: Mon, 05 Jan 2009 13:50:48 -0500 Subject: Emporio Armani better than you could imagine! To: sip@ietf.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Dear Thad, How about buying yourself a two Vacheron Constantin watches the same day? It's not impossible, mostly when you can get them for a couple hundred bucks http://www.maymiss.com/ Take an extra 15% off your purchase during month of January (2009). http://www.maymiss.com/ Our Vacheron Constantin have all appropriate markings, wordings and engravings same as orginal. Sincerely, Mr Talbot From kalsadound@almozoon.com Mon Jan 5 17:43:54 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 77C713A677E for ; Mon, 5 Jan 2009 17:43:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -12.049 X-Spam-Level: X-Spam-Status: No, score=-12.049 tagged_above=-999 required=5 tests=[BAYES_99=3.5, HELO_EQ_CZ=0.445, HOST_EQ_BROADBND=1.118, HOST_EQ_CZ=0.904, HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033, SARE_HTML_A_BODY=0.742, SARE_HTML_IMG_ONLY=1.666, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2M-Zz1ev3rwv for ; Mon, 5 Jan 2009 17:43:53 -0800 (PST) Received: from 227.90.broadband11.iol.cz (227.90.broadband11.iol.cz [90.178.90.227]) by core3.amsl.com (Postfix) with SMTP id AD8843A63D2 for ; Mon, 5 Jan 2009 17:43:50 -0800 (PST) To: Subject: When will we meet again? From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090106014351.AD8843A63D2@core3.amsl.com> Date: Mon, 5 Jan 2009 17:43:50 -0800 (PST) Having trouble viewing this email? Click here to view as a webpage. From bi@garmann.no Mon Jan 5 22:12:40 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3598D3A68BA; Mon, 5 Jan 2009 22:12:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.376 X-Spam-Level: X-Spam-Status: No, score=-0.376 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_BR=0.955, HELO_EQ_DSL=1.129, HOST_EQ_BR=1.295, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, TVD_RCVD_IP=1.931, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_SBL=20, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P4vcExQwwx1i; Mon, 5 Jan 2009 22:12:38 -0800 (PST) Received: from 200-181-84-24.bsace705.dsl.brasiltelecom.net.br (200-181-84-24.bsace705.dsl.brasiltelecom.net.br [200.181.84.24]) by core3.amsl.com (Postfix) with SMTP id 564F03A69B8; Mon, 5 Jan 2009 22:12:21 -0800 (PST) Message-ID: From: "Carson Shearer" Date: Tue, 06 Jan 2009 01:12:16 -0500 Subject: Franck Muller watch models from 2009! To: sip@ietf.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Dear Carson, New Year is the time to get Breitling watch, and the only place to get top notch watches that look and perform exactly like the originals is http://www.maypad.com/ We are offering wholesaler prices on all watches during the month of January 2009. http://www.maypad.com/ Our Breitling have all appropriate markings, wordings and engravings same as orginal. Sincerely, Mr Shearer From sip-bounces@ietf.org Tue Jan 6 04:24:27 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 75B673A686D; Tue, 6 Jan 2009 04:24:27 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 51AA93A67AF for ; Tue, 6 Jan 2009 04:24:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.629 X-Spam-Level: X-Spam-Status: No, score=-2.629 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 UFkO7vnfE180 for ; Tue, 6 Jan 2009 04:24:25 -0800 (PST) Received: from gs19.inmotionhosting.com (gs19b.inmotionhosting.com [66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 8E91F3A6892 for ; Tue, 6 Jan 2009 04:24:25 -0800 (PST) Received: from [75.68.118.126] (port=61127 helo=[192.168.15.105]) by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1LKAyf-0005Mj-O0 for SIP@ietf.org; Tue, 06 Jan 2009 04:24:10 -0800 Message-Id: <14DE4439-4C16-41D7-A19D-8E37CD05C9FB@standardstrack.com> From: Eric Burger To: IETF SIP List Mime-Version: 1.0 (Apple Message framework v930.3) Date: Tue, 6 Jan 2009 07:24:08 -0500 X-Mailer: Apple Mail (2.930.3) 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 Stunning Silence X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2131231165==" Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org --===============2131231165== Content-Type: multipart/signed; boundary=Apple-Mail-78--465621607; micalg=sha1; protocol="application/pkcs7-signature" --Apple-Mail-78--465621607 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit I know, we are just back from vacation. However, for a document that generated over 300 e-mails, I'm surprised there isn't another flood. Check out: http://tools.ietf.org/html/draft-ietf-sip-info-events-02 --Apple-Mail-78--465621607 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 9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wOTAxMDYxMjI0MDlaMCMGCSqGSIb3 DQEJBDEWBBRt5nC0lzaxDlFRbgkCG5EVjOU1OzCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2 MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN H2TynzANBgkqhkiG9w0BAQEFAASCAQCGLO0dywD7hUHvvF1sAFST7iWUVGOHDOyIht2HOCg+e99B NcMEomLygdZU30HPKpsyc2xdG075/D4MFRImf2LRB4gY0epwGou+UMyvLsMUu3gisVvorm7vPyDV U1rugf7/8Tq6owpCjJ0uNuydqkKEeezpWkhdN2HF+fBfOzhnk2Y0b90o+7GFncI5rbNKViwvRp3K r1SjuhT/1tqcQcmQ3kJY3Zoc01VQqCYkpmf83p/6tJ0wVmZOYuRCc0Wt2ZqxvTthKz0zbcQqrkGY nuW+bQi3idbVf7EUmEajCcOsffaedojyTBgHQt5YHHfjboDv3n/52ofs/N79WagOrK/TAAAAAAAA --Apple-Mail-78--465621607-- --===============2131231165== 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 --===============2131231165==-- From sip-bounces@ietf.org Tue Jan 6 05:34:27 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 748CF3A68FF; Tue, 6 Jan 2009 05:34:27 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4F3F93A68FF for ; Tue, 6 Jan 2009 05:34:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.559 X-Spam-Level: X-Spam-Status: No, score=-6.559 tagged_above=-999 required=5 tests=[AWL=0.040, 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 9QJUkksW7jL7 for ; Tue, 6 Jan 2009 05:34:25 -0800 (PST) Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 5AEAB3A68A4 for ; Tue, 6 Jan 2009 05:34:25 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.36,339,1228089600"; d="scan'208";a="32830477" Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 06 Jan 2009 13:34:12 +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 n06DYCN7032124; Tue, 6 Jan 2009 08:34:12 -0500 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 n06DYCPE010391; Tue, 6 Jan 2009 13:34:12 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, 6 Jan 2009 08:34:11 -0500 Received: from [161.44.174.126] ([161.44.174.126]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 6 Jan 2009 08:34:11 -0500 Message-ID: <49635DD3.5050405@cisco.com> Date: Tue, 06 Jan 2009 08:34:11 -0500 From: Paul Kyzivat User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Eric Burger References: <14DE4439-4C16-41D7-A19D-8E37CD05C9FB@standardstrack.com> In-Reply-To: <14DE4439-4C16-41D7-A19D-8E37CD05C9FB@standardstrack.com> X-OriginalArrivalTime: 06 Jan 2009 13:34:11.0502 (UTC) FILETIME=[757BA4E0:01C97003] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=982; t=1231248852; x=1232112852; 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 |Subject:=20Re=3A=20[Sip]=20INFO=20Stunning=20Silence |Sender:=20 |To:=20Eric=20Burger=20; bh=oUkjWZ1ZgiPnqMeLT/PxsPfdpzuPzfFO+7oIn4YJLNU=; b=e03Ny9NqMWFcWw5UmU04FuvT1d6z/AfW/xVhSmAywQ6FjGlPsR+6N7gmNV X5uyxsR6MEShNkJaMf/KosWrt9Hjz+E8TELKu09VEn+ZlRA7WFq83egw4G3A /m2QOP2Iir; Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); Cc: IETF SIP List Subject: Re: [Sip] INFO Stunning Silence X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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 just haven't had time to look at it. I knew I had better wait till I really had time to go over it. Between actually taking some time off, and doing *some* of my own ietf homework, and being behind in my day job, I just don't have such a block of time right now. But I promise I will comment! Thanks, Paul Eric Burger wrote: > I know, we are just back from vacation. However, for a document that > generated over 300 e-mails, I'm surprised there isn't another flood. > > Check out: > http://tools.ietf.org/html/draft-ietf-sip-info-events-02 > > > ------------------------------------------------------------------------ > > _______________________________________________ > Sip mailing list https://www.ietf.org/mailman/listinfo/sip > This list is for NEW development of the core SIP 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 Jan 6 06:33:51 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C404C3A6987; Tue, 6 Jan 2009 06:33:51 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DA0583A6987 for ; Tue, 6 Jan 2009 06:33:50 -0800 (PST) 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 IDeNPI1eKc3k for ; Tue, 6 Jan 2009 06:33:50 -0800 (PST) Received: from bespin.rfc3261.net (cl-395.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:18a::2]) by core3.amsl.com (Postfix) with ESMTP id E57743A6917 for ; Tue, 6 Jan 2009 06:33:49 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by bespin.rfc3261.net (Postfix) with ESMTP id C5BB27FA6; Tue, 6 Jan 2009 15:33:34 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at bespin.rfc3261.net Received: from bespin.rfc3261.net ([127.0.0.1]) by localhost (bespin.rfc3261.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QHgUBHYT8AAy; Tue, 6 Jan 2009 15:33:34 +0100 (CET) Received: from www.ohlmeier.com (localhost [127.0.0.1]) by bespin.rfc3261.net (Postfix) with ESMTP id 7B1A47FA3; Tue, 6 Jan 2009 15:33:34 +0100 (CET) Received: from proxy4-nsn.nsn-inter.net ([217.115.75.232]) (SquirrelMail authenticated user lando) by www.ohlmeier.com with HTTP; Tue, 6 Jan 2009 15:33:34 +0100 (CET) Message-ID: In-Reply-To: <2DC20D47-8F42-486A-9D18-AE6A6FA86001@edvina.net> References: <07953AE2-F02A-4E6D-82F5-6730383B44FF@edvina.net> <1230910444.3835.1.camel@victoria-pingtel-com.us.nortel.com> <5D6CB5AC-3ADF-4294-89E9-2FA197545865@edvina.net> <1230913633.3835.29.camel@victoria-pingtel-com.us.nortel.com> <2DC20D47-8F42-486A-9D18-AE6A6FA86001@edvina.net> Date: Tue, 6 Jan 2009 15:33:34 +0100 (CET) From: "Nils Ohlmeier" To: "Johansson Olle E" User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 X-Priority: 3 (Normal) Importance: Normal Cc: IETF SIP List Subject: Re: [Sip] Implementing SHA digest auth (new topic) X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org > > So in that case, the implementation guideline for an UA set for both > methods would be to first try with the strongest algorithm, then upon > reception > of a 401/407 to that one, test with the next one in list until it is > out of > algorithms in which case the 401/407 means that the password is indeed > wrong. > > The UA could also, as you point out, send all headers at once to make it > a quicker round-trip, but doing it that way would also expose the > weaker MD5 > hash which we want to avoid. > > Thanks for your replies, Dale. This seems easier than expected. Anyone > else > that sees any caveats or issues? I fear I can only agree partially. To me it seems that you are only seeing the upgrade path from the server side: the server simply supports multiple, not to say all, hash or authentication algorithms and advertises all of them. And you are missing an possible attack in your current proposal (see below). If we remove the current restriction of only one madatory hash algorithm for everybody we will, or at least might, have implementations with multiple hash algorithms. And in worst case both implementations will not have a common subset. We already have a similar problem with AKA vs. MD5 in IMS (which is caused by differences between implementations and specifications - but that is a different story). Don't get me wrong: I totaly agree that we should look for alternatives to MD5. But I think if we take that road we should consider some mechanism which allows UAC and UAS to advertise and agree (?) on the most preferred algorithm for the authentication. And I guess it should be mandatory that this mechanism prevents that an attacker can modify the message exchange in a way that the weakest algorithm is chosen (which is the case with current proposed solution). Greetings Nils Ohlmeier _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip From _m_s_d@afterwork.com Tue Jan 6 06:51:44 2009 Return-Path: <_m_s_d@afterwork.com> X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F1FA73A67EA for ; Tue, 6 Jan 2009 06:51:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -33.046 X-Spam-Level: X-Spam-Status: No, score=-33.046 tagged_above=-999 required=5 tests=[BAYES_99=3.5, HELO_EQ_RU=0.595, HOST_EQ_RU=0.875, HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033, SARE_HTML_A_BODY=0.742, SARE_HTML_IMG_ONLY=1.666, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_SC_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P09lrQhkpm6o for ; Tue, 6 Jan 2009 06:51:38 -0800 (PST) Received: from home.istra.ru (home.istra.ru [82.204.188.241]) by core3.amsl.com (Postfix) with SMTP id 3F8C13A67B2 for ; Tue, 6 Jan 2009 06:51:35 -0800 (PST) To: Subject: It's cold, don't keep me waiting From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090106145137.3F8C13A67B2@core3.amsl.com> Date: Tue, 6 Jan 2009 06:51:35 -0800 (PST) Having trouble viewing this email? Click here to view as a webpage. From sip-bounces@ietf.org Tue Jan 6 07:27:50 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1559E3A683A; Tue, 6 Jan 2009 07:27:50 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C796F3A683A for ; Tue, 6 Jan 2009 07:27:48 -0800 (PST) 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 8dTq0qAGf1DI for ; Tue, 6 Jan 2009 07:27:48 -0800 (PST) Received: from bespin.rfc3261.net (cl-395.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:18a::2]) by core3.amsl.com (Postfix) with ESMTP id F27AD3A67B2 for ; Tue, 6 Jan 2009 07:27:47 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by bespin.rfc3261.net (Postfix) with ESMTP id CA13B7FA6; Tue, 6 Jan 2009 16:27:33 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at bespin.rfc3261.net Received: from bespin.rfc3261.net ([127.0.0.1]) by localhost (bespin.rfc3261.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wFKVVD4mzXFd; Tue, 6 Jan 2009 16:27:33 +0100 (CET) Received: from www.ohlmeier.com (localhost [127.0.0.1]) by bespin.rfc3261.net (Postfix) with ESMTP id 7EF537FA3; Tue, 6 Jan 2009 16:27:33 +0100 (CET) Received: from proxy4-nsn.nsn-inter.net ([217.115.75.232]) (SquirrelMail authenticated user lando) by www.ohlmeier.com with HTTP; Tue, 6 Jan 2009 16:27:33 +0100 (CET) Message-ID: <29c1b51ee320c2850e86c62591dfbdb0.squirrel@www.ohlmeier.com> In-Reply-To: <1231086270.22641.3.camel@victoria-pingtel-com.us.nortel.com> References: <07953AE2-F02A-4E6D-82F5-6730383B44FF@edvina.net> <1230910444.3835.1.camel@victoria-pingtel-com.us.nortel.com> <5D6CB5AC-3ADF-4294-89E9-2FA197545865@edvina.net> <1230913633.3835.29.camel@victoria-pingtel-com.us.nortel.com> <2DC20D47-8F42-486A-9D18-AE6A6FA86001@edvina.net> <1231086270.22641.3.camel@victoria-pingtel-com.us.nortel.com> Date: Tue, 6 Jan 2009 16:27:33 +0100 (CET) From: "Nils Ohlmeier" To: "Dale Worley" User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 X-Priority: 3 (Normal) Importance: Normal Cc: IETF SIP List , Johansson Olle E Subject: Re: [Sip] Implementing SHA digest auth (new topic) X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org > On Fri, 2009-01-02 at 17:45 +0100, Johansson Olle E wrote: >> The UA could also, as you point out, send all headers at once to make it >> a quicker round-trip, but doing it that way would also expose the >> weaker MD5 hash which we want to avoid. > > We actually haven't resolved the question whether using MD5 *exposes* > your key. As far as I can tell, what's been shown is that *trusting* an > MD5 is not a good idea. But I'm not a crypto expert. I'm not a crypto expert either but I think it is a good idea to be prepared to replace MD5 whenever we will have to do it. And as such a replacement takes time until it reaches the end user it would be better to start early. Just my 2 cents Nils _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip From nbsod@ama-assn.org Tue Jan 6 13:09:39 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7E4273A6A37 for ; Tue, 6 Jan 2009 13:09:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.975 X-Spam-Level: X-Spam-Status: No, score=0.975 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_DHCP=1.398, HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DSL=1.129, HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_HTML_A_BODY=0.742, SARE_HTML_IMG_ONLY=1.666, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dOzfp2eDpL8Z for ; Tue, 6 Jan 2009 13:09:38 -0800 (PST) Received: from adsl-68-94-12-83.dsl.rcsntx.swbell.net (adsl-68-94-12-83.dsl.rcsntx.swbell.net [68.94.12.83]) by core3.amsl.com (Postfix) with SMTP id 291203A6893 for ; Tue, 6 Jan 2009 13:09:37 -0800 (PST) To: Subject: I lost your cell number From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090106210938.291203A6893@core3.amsl.com> Date: Tue, 6 Jan 2009 13:09:37 -0800 (PST) Having trouble viewing this email? Click here to view as a webpage. From 27jigs@goggo.com Tue Jan 6 14:46:34 2009 Return-Path: <27jigs@goggo.com> X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 36DB63A69C9; Tue, 6 Jan 2009 14:46:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.086 X-Spam-Level: X-Spam-Status: No, score=-17.086 tagged_above=-999 required=5 tests=[BAYES_60=1, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_DSL=1.129, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, TVD_RCVD_IP=1.931, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_SBL=20, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WL1juFSsz2cE; Tue, 6 Jan 2009 14:46:33 -0800 (PST) Received: from 190-82-230-243.adsl.tie.cl (190-82-230-243.adsl.tie.cl [190.82.230.243]) by core3.amsl.com (Postfix) with SMTP id E3E043A6B0A; Tue, 6 Jan 2009 14:46:21 -0800 (PST) Message-ID: From: "Shane Lockhart" Date: Tue, 06 Jan 2009 17:46:15 -0500 Subject: Gucci better than you could imagine! To: sip@ietf.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Dear Shane, I had never seen such beautiful and greatly-performing watches like the ones I found online at http://www.laneday.com/ We are offering wholesaler prices on all watches during the month of January 2009. http://www.laneday.com/ Our Franck Muller have Weights/feels and looks exactly same as original. Sincerely, Mr Lockhart From sip-bounces@ietf.org Wed Jan 7 00:49:13 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B5C4A3A6856; Wed, 7 Jan 2009 00:49:13 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EFBFD3A6856 for ; Wed, 7 Jan 2009 00:49:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.463 X-Spam-Level: X-Spam-Status: No, score=-5.463 tagged_above=-999 required=5 tests=[AWL=-0.704, 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 WVQeLuQZZnzi for ; Wed, 7 Jan 2009 00:49:12 -0800 (PST) Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id F15823A67F6 for ; Wed, 7 Jan 2009 00:49:11 -0800 (PST) Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id BFA0020124 for ; Wed, 7 Jan 2009 09:48:57 +0100 (CET) X-AuditID: c1b4fb3e-af070bb00000429e-4d-49646c7996d9 Received: from esealmw126.eemea.ericsson.se (unknown [153.88.253.125]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id A50BF20113 for ; Wed, 7 Jan 2009 09:48: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); Wed, 7 Jan 2009 09:48:57 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 7 Jan 2009 09:48:56 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: New version (-04) of draft-ietf-sip-199 thread-index: AclwpMa2gVaTl0oqRZ+oKLyml2UY7w== From: "Christer Holmberg" To: X-OriginalArrivalTime: 07 Jan 2009 08:48:57.0457 (UTC) FILETIME=[C7215E10:01C970A4] X-Brightmail-Tracker: AAAAAA== Subject: [Sip] New version (-04) of draft-ietf-sip-199 X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1205597190==" Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org This is a multi-part message in MIME format. --===============1205597190== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C970A4.C6EBC08A" This is a multi-part message in MIME format. ------_=_NextPart_001_01C970A4.C6EBC08A Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Based on comments and discussions, I've submitted a new version of the 199 draft. The currently remaining to-do is to add text to the security chapter. The draft can also be found at: http://users.piuha.net/cholmber/drafts/draft-ietf-sip-199-04.txt Regards, Christer ------_=_NextPart_001_01C970A4.C6EBC08A Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable New version (-04) of draft-ietf-sip-199

Hi,

Based on comments and discussions, I've = submitted a new version of the 199 draft.

The currently remaining to-do is to add = text to the security chapter.

The draft can also be found at:

http://users.piuha.net/cholmber/drafts/draft-ietf-sip-199-= 04.txt

Regards,

Christer

------_=_NextPart_001_01C970A4.C6EBC08A-- --===============1205597190== 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 --===============1205597190==-- From sip-bounces@ietf.org Wed Jan 7 01:00:03 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D5F028C0D6; Wed, 7 Jan 2009 01:00:03 -0800 (PST) X-Original-To: sip@ietf.org Delivered-To: sip@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 3B7E73A698F; Wed, 7 Jan 2009 01:00:00 -0800 (PST) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20090107090001.3B7E73A698F@core3.amsl.com> Date: Wed, 7 Jan 2009 01:00:01 -0800 (PST) Cc: sip@ietf.org Subject: [Sip] I-D Action:draft-ietf-sip-199-04.txt X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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-04.txt Pages : 14 Date : 2009-01-07 This specification defines a new SIP response code, 199 Early Dialog Terminated, which a SIP forking proxy and a UAS can use to indicate upstream towards the UAC that an early dialog has been terminated, before a final response is sent towards the UAC. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sip-199-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-199-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-01-07004705.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 Jan 7 02:43:47 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D46DD3A6821; Wed, 7 Jan 2009 02:43:47 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 374F33A6821 for ; Wed, 7 Jan 2009 02:43:46 -0800 (PST) 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 U7bQpMz2d1Zu for ; Wed, 7 Jan 2009 02:43:45 -0800 (PST) Received: from gateway13.websitewelcome.com (gateway13.websitewelcome.com [70.85.130.30]) by core3.amsl.com (Postfix) with SMTP id 018F43A6808 for ; Wed, 7 Jan 2009 02:43:44 -0800 (PST) Received: (qmail 4538 invoked from network); 7 Jan 2009 10:57:58 -0000 Received: from gator465.hostgator.com (69.56.174.130) by gateway13.websitewelcome.com with SMTP; 7 Jan 2009 10:57:58 -0000 Received: from fl1-118-109-64-205.tky.mesh.ad.jp ([118.109.64.205]:43015 helo=[10.0.1.2]) by gator465.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1LKVsm-00009B-VH; Wed, 07 Jan 2009 04:43:29 -0600 Message-Id: From: Shida Schubert To: "sip@ietf.org List" Mime-Version: 1.0 (Apple Message framework v930.3) Date: Wed, 7 Jan 2009 19:43:26 +0900 X-Mailer: Apple Mail (2.930.3) 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: "Drage, Keith \(Keith\)" , "Elwell, John" Subject: [Sip] BCP or Informational: Mechanisms for UA initiated privacy X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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 At the last meeting, Keith asked the group to provide feedback on whether the draft-ietf-sip-ua-privacy addressing the milestone "Mechanisms for UA initiated privacy" should proceed as BCP or as an informational. As a co-author of the draft, my inclination is to go informational. Reason is because the 2 specifications the draft requires, namely GRUU and TURN aren't widely deployed, and neither are RFCs (Although GRUU I believe is pretty close.). Despite the fact that people I talked to are keen on implementing these specifications, I don't think the draft which requires and depends on specifications that aren't widely deployed neither RFC should be proceeded as a Best Current Practice.. Regards Shida _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.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 Jan 7 03:10:59 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 365AE3A6808; Wed, 7 Jan 2009 03:10:59 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 398BE3A6808 for ; Wed, 7 Jan 2009 03:10:58 -0800 (PST) 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 gtTz9Ic+fGfp for ; Wed, 7 Jan 2009 03:10:57 -0800 (PST) Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk [195.171.110.225]) by core3.amsl.com (Postfix) with ESMTP id EECF33A6806 for ; Wed, 7 Jan 2009 03:10:56 -0800 (PST) Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235]) by siemenscomms.co.uk (PMDF V6.3-x14 #31430) with ESMTP id <0KD30074ELOYQI@siemenscomms.co.uk> for sip@ietf.org; Wed, 07 Jan 2009 11:10:40 +0000 (GMT) Date: Wed, 07 Jan 2009 11:10:32 +0000 From: "Elwell, John" In-reply-to: A To: Christer Holmberg , sip@ietf.org Message-id: <0D5F89FAC29E2C41B98A6A762007F5D00167DF83@GBNTHT12009MSX.gb002.siemens.net> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft Exchange V6.5 Thread-Topic: [Sip] New version (-04) of draft-ietf-sip-199 Thread-Index: AclwpMa2gVaTl0oqRZ+oKLyml2UY7wAEccgw Content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: References: A Subject: Re: [Sip] New version (-04) of draft-ietf-sip-199 X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org Christer, "If the received initial request contains an 199 option tag, the UAS SHOULD NOT send a 199 response for a dialog on which it intends to send a final response, unless it e.g. has been configured to do so due to lack of 199 support by forking proxies or other intermediate SIP entities." I doubt that a UAS would implement a new configurable parameter just so that it can reduce resource consumption at the UAC when the forking proxy has not bothered to implement 199. It is far easier for the UAS never to send 199. So is it really worth specifying this option? "When a forking proxy receives a non-2xx final response which terminates one or more (if forking has occured downstream a final response received by the forking proxy MAY terminate multiple early dialogs), and the proxy does not intend to forward the final response immedialetly (due to the rules for a forking proxy), and the UAC has indicated support of the 199 response code, the proxy SHOULD generate and send a 199 response upstream for the early dialog on which the non-2xx final response was received, unless the proxy has previously recieved and forwarded a 199 response for the dialog." Wow! We really must shorten this sentence. In particular I don't like including a second normative sentence in parentheses within the main sentence. "If the forking proxy has stored the Contact and Record-Route headers for the early dialogs, it SHALL insert the headers in the 199 responses." Which Contact and Record-Route header fields? Presumably the ones received from the UAS (as opposed to the UAC), but it doesn't make this clear. Also, if there is no compulsion to store these header fields, why make it mandatory to transmit them if they have been stored? John ________________________________ From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of Christer Holmberg Sent: 07 January 2009 08:49 To: sip@ietf.org Subject: [Sip] New version (-04) of draft-ietf-sip-199 Hi, Based on comments and discussions, I've submitted a new version of the 199 draft. The currently remaining to-do is to add text to the security chapter. The draft can also be found at: http://users.piuha.net/cholmber/drafts/draft-ietf-sip-199-04.txt 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 Jan 7 03:12:22 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F26313A6829; Wed, 7 Jan 2009 03:12:21 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E6F823A6829 for ; Wed, 7 Jan 2009 03:12:20 -0800 (PST) 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 BbqNqL2Aji1Q for ; Wed, 7 Jan 2009 03:12:20 -0800 (PST) Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk [195.171.110.225]) by core3.amsl.com (Postfix) with ESMTP id 2A8E83A6806 for ; Wed, 7 Jan 2009 03:12:20 -0800 (PST) Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235]) by siemenscomms.co.uk (PMDF V6.3-x14 #31430) with ESMTP id <0KD30078KLS6QI@siemenscomms.co.uk> for sip@ietf.org; Wed, 07 Jan 2009 11:12:06 +0000 (GMT) Date: Wed, 07 Jan 2009 11:12:05 +0000 From: "Elwell, John" In-reply-to: To: Shida Schubert , sip@ietf.org Message-id: <0D5F89FAC29E2C41B98A6A762007F5D00167DF86@GBNTHT12009MSX.gb002.siemens.net> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft Exchange V6.5 Thread-Topic: BCP or Informational: Mechanisms for UA initiated privacy Thread-Index: AclwtMprehH/aWIQRWavHXEbsg0jaAAA/TmQ Content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: References: Cc: "Drage, Keith \(Keith\)" Subject: Re: [Sip] BCP or Informational: Mechanisms for UA initiated privacy X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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. John > -----Original Message----- > From: Shida Schubert [mailto:shida@ntt-at.com] > Sent: 07 January 2009 10:43 > To: sip@ietf.org List > Cc: Elwell, John; Drage, Keith (Keith) > Subject: BCP or Informational: Mechanisms for UA initiated privacy > > > At the last meeting, Keith asked the group to provide feedback on > whether the draft-ietf-sip-ua-privacy addressing the milestone > "Mechanisms for UA initiated privacy" should proceed as BCP or > as an informational. > > As a co-author of the draft, my inclination is to go informational. > > Reason is because the 2 specifications the draft requires, namely > GRUU and TURN aren't widely deployed, and neither are RFCs > (Although GRUU I believe is pretty close.). > > Despite the fact that people I talked to are keen on implementing > these specifications, I don't think the draft which requires and > depends on specifications that aren't widely deployed neither RFC > should be proceeded as a Best Current Practice.. > > Regards > Shida > > > _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.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 Jan 7 03:32:24 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9335628C141; Wed, 7 Jan 2009 03:32:24 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BC45C28C12B for ; Wed, 7 Jan 2009 03:32:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.581 X-Spam-Level: X-Spam-Status: No, score=-3.581 tagged_above=-999 required=5 tests=[AWL=-0.982, 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 k5GpseKW8I4f for ; Wed, 7 Jan 2009 03:32:23 -0800 (PST) Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [217.115.75.234]) by core3.amsl.com (Postfix) with ESMTP id AA3B03A6989 for ; Wed, 7 Jan 2009 03:32:22 -0800 (PST) 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 n07BW4eQ028773 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 7 Jan 2009 12:32:04 +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 n07BW0a9026379; Wed, 7 Jan 2009 12:32:04 +0100 Received: from FIESEXC007.nsn-intra.net ([10.159.0.15]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 7 Jan 2009 12:32:03 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 7 Jan 2009 13:32:32 +0200 Message-ID: In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D00167DF86@GBNTHT12009MSX.gb002.siemens.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Sip] BCP or Informational: Mechanisms for UA initiated privacy Thread-Index: AclwtMprehH/aWIQRWavHXEbsg0jaAAA/TmQAACz/5A= References: <0D5F89FAC29E2C41B98A6A762007F5D00167DF86@GBNTHT12009MSX.gb002.siemens.net> From: "Tschofenig, Hannes (NSN - FI/Espoo)" To: "ext Elwell, John" , "Shida Schubert" , X-OriginalArrivalTime: 07 Jan 2009 11:32:03.0711 (UTC) FILETIME=[903138F0:01C970BB] Cc: "Drage, Keith \(Keith\)" Subject: Re: [Sip] BCP or Informational: Mechanisms for UA initiated privacy X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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 as well. Informational is a good choice. BCP would be quite far fetched. >-----Original Message----- >From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On >Behalf Of ext Elwell, John >Sent: 07 January, 2009 13:12 >To: Shida Schubert; sip@ietf.org >Cc: Drage, Keith (Keith) >Subject: Re: [Sip] BCP or Informational: Mechanisms for UA >initiated privacy > >I agree. > >John > >> -----Original Message----- >> From: Shida Schubert [mailto:shida@ntt-at.com] >> Sent: 07 January 2009 10:43 >> To: sip@ietf.org List >> Cc: Elwell, John; Drage, Keith (Keith) >> Subject: BCP or Informational: Mechanisms for UA initiated privacy >> >> >> At the last meeting, Keith asked the group to provide feedback on >> whether the draft-ietf-sip-ua-privacy addressing the milestone >> "Mechanisms for UA initiated privacy" should proceed as BCP or as an >> informational. >> >> As a co-author of the draft, my inclination is to go informational. >> >> Reason is because the 2 specifications the draft requires, namely >> GRUU and TURN aren't widely deployed, and neither are RFCs (Although >> GRUU I believe is pretty close.). >> >> Despite the fact that people I talked to are keen on implementing >> these specifications, I don't think the draft which requires and >> depends on specifications that aren't widely deployed neither RFC >> should be proceeded as a Best Current Practice.. >> >> Regards >> Shida >> >> >> >_______________________________________________ >Sip mailing list https://www.ietf.org/mailman/listinfo/sip >This list is for NEW development of the core SIP 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 Jan 7 04:09:20 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1F3423A6A3F; Wed, 7 Jan 2009 04:09:20 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 22C143A6A16 for ; Wed, 7 Jan 2009 04:09:19 -0800 (PST) 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 edRslWOyf7uf for ; Wed, 7 Jan 2009 04:09:17 -0800 (PST) Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 961BE3A6A4C for ; Wed, 7 Jan 2009 04:09:12 -0800 (PST) Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 7EE07212CD; Wed, 7 Jan 2009 13:08:58 +0100 (CET) X-AuditID: c1b4fb3e-ad86dbb00000429e-54-49649b5a2014 Received: from esealmw128.eemea.ericsson.se (unknown [153.88.253.125]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 59B58211A7; Wed, 7 Jan 2009 13:08:58 +0100 (CET) Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Jan 2009 13:08:58 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 7 Jan 2009 13:08:57 +0100 Message-ID: In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D00167DF83@GBNTHT12009MSX.gb002.siemens.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Sip] New version (-04) of draft-ietf-sip-199 thread-index: AclwpMa2gVaTl0oqRZ+oKLyml2UY7wAEccgwAAJTriA= References: A <0D5F89FAC29E2C41B98A6A762007F5D00167DF83@GBNTHT12009MSX.gb002.siemens.net> From: "Christer Holmberg" To: "Elwell, John" , X-OriginalArrivalTime: 07 Jan 2009 12:08:58.0323 (UTC) FILETIME=[B8343230:01C970C0] X-Brightmail-Tracker: AAAAAA== Subject: Re: [Sip] New version (-04) of draft-ietf-sip-199 X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org Hi John, >>"If the received initial request contains an 199 option tag, the UAS >> SHOULD NOT send a 199 response for a dialog on which it intends to >> send a final response, unless it e.g. has been configured to do so >> due to lack of 199 support by forking proxies or other intermediate >> SIP entities." > >I doubt that a UAS would implement a new configurable >parameter just so that it can reduce resource consumption at >the UAC when the forking proxy has not bothered to implement >199. It is far easier for the UAS never to send 199. So is it >really worth specifying this option? It is probably true that a SIP phone type of UAS would not implement a new configurable parameter for this. However, the UAS could be a "network entity", e.g. an application server, or a B2BUA, and in such cases the operator may have a configurable parameter. So, I think we should allow it. >>"When a forking proxy receives a non-2xx final response which >>terminates one or more (if forking has occured downstream a final >>response received by the forking proxy MAY terminate multiple early >>dialogs), and the proxy does not intend to forward the >>final response immedialetly (due to the rules for a forking proxy), and >>the UAC has indicated support of the 199 response code, the proxy >>SHOULD generate and send a 199 response upstream for the early dialog on which the >>non-2xx final response was received, unless the proxy has >>previously recieved and forwarded a 199 response for the dialog." > >Wow! We really must shorten this sentence. In particular I >don't like including a second normative sentence in >parentheses within the main sentence. I can try to think of more simple wording. And, text suggestions are of course always welcome :) >>"If the forking proxy has stored the Contact and Record-Route headers >>for the early dialogs, it SHALL insert the headers in the 199 >>responses." >Which Contact and Record-Route header fields? Presumably the >ones received from the UAS (as opposed to the UAC), but it >doesn't make this clear. Yes, that should be clarified. >Also, if there is no compulsion to store these header fields, why make it mandatory to transmit >them if they have been stored? I was requested to add text about the possibility to store the header fields and included them in the response. I see no harm in doing so, since storing the parameters is optional anyway. Regards, Christer > From: sip-bounces@ietf.org > [mailto:sip-bounces@ietf.org] On Behalf Of Christer Holmberg > Sent: 07 January 2009 08:49 > To: sip@ietf.org > Subject: [Sip] New version (-04) of draft-ietf-sip-199 > > > > > Hi, > > Based on comments and discussions, I've submitted a new > version of the 199 draft. > > The currently remaining to-do is to add text to the > security chapter. > > The draft can also be found at: > > http://users.piuha.net/cholmber/drafts/draft-ietf-sip-199-04.txt > > > 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 joyzhangdd@aiptek.com.cn Wed Jan 7 04:24:28 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E1D0728C151 for ; Wed, 7 Jan 2009 04:24:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.849 X-Spam-Level: X-Spam-Status: No, score=-14.849 tagged_above=-999 required=5 tests=[BAYES_95=3, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, GB_I_LETTER=-2, HELO_DYNAMIC_DHCP=1.398, HELO_DYNAMIC_IPADDR=2.426, HTML_EXTRA_CLOSE=2.809, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_UNI=0.591, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xvmwyhlwortp for ; Wed, 7 Jan 2009 04:24:28 -0800 (PST) Received: from dslb-092-072-150-113.pools.arcor-ip.net (dslb-092-072-150-113.pools.arcor-ip.net [92.72.150.113]) by core3.amsl.com (Postfix) with SMTP id 0156428C132 for ; Wed, 7 Jan 2009 04:24:25 -0800 (PST) To: Subject: Mail delivery failed: returning message to sender From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090107122427.0156428C132@core3.amsl.com> Date: Wed, 7 Jan 2009 04:24:25 -0800 (PST) About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

C2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 98052 From sip-bounces@ietf.org Wed Jan 7 04:45:13 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D5F5F28C15F; Wed, 7 Jan 2009 04:45:13 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 03FDC3A67DA for ; Wed, 7 Jan 2009 04:45:13 -0800 (PST) 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 SWUXQ58xSxl9 for ; Wed, 7 Jan 2009 04:45:06 -0800 (PST) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id CD1B828C153 for ; Wed, 7 Jan 2009 04:45:05 -0800 (PST) Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 856C62082F; Wed, 7 Jan 2009 13:44:51 +0100 (CET) X-AuditID: c1b4fb3c-acf5cbb00000304c-fd-4964a3c3025f Received: from esealmw128.eemea.ericsson.se (unknown [153.88.253.125]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 660CC20525; Wed, 7 Jan 2009 13:44:51 +0100 (CET) Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Jan 2009 13:44:51 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 7 Jan 2009 13:44:50 +0100 Message-ID: In-Reply-To: <14DE4439-4C16-41D7-A19D-8E37CD05C9FB@standardstrack.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Sip] INFO Stunning Silence thread-index: Aclv+bbUGMneGRmpQW28QfikBJRTTgAyjStQ References: <14DE4439-4C16-41D7-A19D-8E37CD05C9FB@standardstrack.com> From: "Christer Holmberg" To: "Eric Burger" , "IETF SIP List" X-OriginalArrivalTime: 07 Jan 2009 12:44:51.0366 (UTC) FILETIME=[BB847C60:01C970C5] X-Brightmail-Tracker: AAAAAA== Subject: Re: [Sip] INFO Stunning Silence X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org Hi, Some comments: 1. Would it be good to add some words to section 2, saying that "For backward compabiltiy, this document does not forbid legacy usage of INFO with no info-package, as described in section 6.", or something like that... 2. Section 4.1 says: The text: "The initiating UA of the first INVITE MUST be prepared to receive multiple INFO requests, as the first INVITE may fork." ...should be modified with something like: "The initiation UA of the first INVITE MUST be prepared to receive INFO requests from multiple remote destinations, as the INVITE may fork." 3. In section 4.1, would it be good to add some explicit words about the fact that it is allowed for the UAS to send INFO during the early dialog? RFC3311 says the following for UPDATE: "The UPDATE request is constructed as would any other request within an existing dialog, as described in Section 12.2.1 of RFC 3261. It MAY be sent for both early and confirmed dialogs, and MAY be sent by either caller or callee." ...so I think we could say something similar for INFO. Regards, Christer > -----Original Message----- > From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On > Behalf Of Eric Burger > Sent: 6. tammikuuta 2009 14:24 > To: IETF SIP List > Subject: [Sip] INFO Stunning Silence > > I know, we are just back from vacation. However, for a > document that generated over 300 e-mails, I'm surprised there > isn't another flood. > > Check out: > http://tools.ietf.org/html/draft-ietf-sip-info-events-02 > > _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip From matriz@agroparts.com.br Wed Jan 7 05:09:17 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A5CCB3A68ED for ; Wed, 7 Jan 2009 05:09:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.93 X-Spam-Level: X-Spam-Status: No, score=-10.93 tagged_above=-999 required=5 tests=[BAYES_99=3.5, DNS_FROM_RFC_BOGUSMX=1.482, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033, RDNS_NONE=0.1, SARE_HTML_A_BODY=0.742, SARE_HTML_IMG_ONLY=1.666, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RzHxxDVUUulL for ; Wed, 7 Jan 2009 05:09:17 -0800 (PST) Received: from 093105037225.swk.vectranet.pl (093105037225.swk.vectranet.pl [93.105.37.225]) by core3.amsl.com (Postfix) with SMTP id 51DC93A67DA for ; Wed, 7 Jan 2009 05:09:15 -0800 (PST) To: Subject: You probably gave wrong number From: MIME-Version: 1.0 Importance: High Content-Type: text/html X-Antivirus: avast! (VPS 080831-0, 2008-08-31), Outbound message X-Antivirus-Status: Clean Message-Id: <20090107130916.51DC93A67DA@core3.amsl.com> Date: Wed, 7 Jan 2009 05:09:15 -0800 (PST) Having trouble viewing this email? Click here to view as a webpage. From sip-bounces@ietf.org Wed Jan 7 06:09:31 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB5F43A6966; Wed, 7 Jan 2009 06:09:31 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 62E853A6A03 for ; Wed, 7 Jan 2009 06:09:30 -0800 (PST) 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 z8JjU94UBUjK for ; Wed, 7 Jan 2009 06:09:29 -0800 (PST) Received: from ATL1VEXC020.usdom003.tco.tc (atl1vexc020.usdom003.tco.tc [209.225.56.95]) by core3.amsl.com (Postfix) with ESMTP id 7D5003A6966 for ; Wed, 7 Jan 2009 06:09:29 -0800 (PST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 7 Jan 2009 09:11:11 -0500 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Sip] New version (-04) of draft-ietf-sip-199 Thread-Index: AclwpMa2gVaTl0oqRZ+oKLyml2UY7wAEccgwAAJTriAAArvcsA== From: "Brett Tate" To: "Christer Holmberg" , "Elwell, John" , Subject: Re: [Sip] New version (-04) of draft-ietf-sip-199 X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org > > "If the forking proxy has stored the Contact > > and Record-Route headers for the early dialogs, > > it SHALL insert the headers in the 199 responses." > > Also, if there is no compulsion to store these > > header fields, why make it mandatory to transmit > > them if they have been stored? > > I was requested to add text about the possibility > to store the header fields and included them in > the response. I see no harm in doing so, since > storing the parameters is optional anyway. For clarity, the following is a snippet from my 11/17/2008 draft-ietf-sip-199-02 comments and questions posting to the sip list. I don't have strong preference concerning the normative strength to include (or not include) the headers. http://www.ietf.org/mail-archive/web/sip/current/msg25605.html "Section 6 paragraph 2 last sentence: Since using another's To tag when sending the 199, the draft should mention something concerning headers Contact and Record-Route. If proxy chooses not to add them, a missing Contact and Record-Route will not be an issue for UAC; however another proxy (not supporting this draft) may be surprised to see their Record-Route entry missing. Additionally since this draft defines a 1xx with To tag which does not create a dialog (unless section 4 paragraph 4 modified), does this draft update RFC 3261?" _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip From jmeehandd@amcore.com Wed Jan 7 08:54:11 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EBBD33A6843 for ; Wed, 7 Jan 2009 08:54:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -38.922 X-Spam-Level: X-Spam-Status: No, score=-38.922 tagged_above=-999 required=5 tests=[BAYES_99=3.5, GB_I_LETTER=-2, HELO_EQ_DK=1.009, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033, SARE_UNI=0.591, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QHJCXTnPpJ4g for ; Wed, 7 Jan 2009 08:54:05 -0800 (PST) Received: from 4008ds1-vg.0.fullrate.dk (4008ds1-vg.0.fullrate.dk [90.185.252.101]) by core3.amsl.com (Postfix) with SMTP id 4A7153A6A82 for ; Wed, 7 Jan 2009 08:54:03 -0800 (PST) To: Subject: Your order 92491 From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090107165404.4A7153A6A82@core3.amsl.com> Date: Wed, 7 Jan 2009 08:54:03 -0800 (PST)
About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

©2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 12532
From sip-bounces@ietf.org Wed Jan 7 09:21:12 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 012B33A694D; Wed, 7 Jan 2009 09:21:12 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 303463A694D for ; Wed, 7 Jan 2009 09:21:11 -0800 (PST) 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 tpTEmTv2IHlz for ; Wed, 7 Jan 2009 09:21:10 -0800 (PST) Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 085173A6843 for ; Wed, 7 Jan 2009 09:21:09 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,227,1231113600"; d="scan'208";a="33004749" Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 07 Jan 2009 17:20:56 +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 n07HKu9Y009587; Wed, 7 Jan 2009 12:20:56 -0500 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 n07HKuph001665; Wed, 7 Jan 2009 17:20:56 GMT Received: from xmb-rtp-201.amer.cisco.com ([64.102.31.13]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Jan 2009 12:20:56 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 7 Jan 2009 12:20:27 -0500 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Sip] New version (-04) of draft-ietf-sip-199 thread-index: AclwpMa2gVaTl0oqRZ+oKLyml2UY7wAEccgwAAJTriAACurO0A== References: A<0D5F89FAC29E2C41B98A6A762007F5D00167DF83@GBNTHT12009MSX.gb002.siemens.net> From: "Sanjay Sinha (sanjsinh)" To: "Christer Holmberg" , "Elwell, John" , X-OriginalArrivalTime: 07 Jan 2009 17:20:56.0062 (UTC) FILETIME=[4CD881E0:01C970EC] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1441; t=1231348856; x=1232212856; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=sanjsinh@cisco.com; z=From:=20=22Sanjay=20Sinha=20(sanjsinh)=22=20 |Subject:=20RE=3A=20[Sip]=20New=20version=20(-04)=20of=20dr aft-ietf-sip-199 |Sender:=20 |To:=20=22Christer=20Holmberg=22=20,=0A=20=20=20=20=20=20=20=20=22Elwell,=20John=22=20< john.elwell@siemens.com>,=20; bh=7q2ROglaN9cGL0PeljH24I0vZDWCD79TxV1WxMbqnog=; b=eF3CL8PP10P7E6A1tf1I3ll6hk9NN2NZMcSE/6nYCeEi7O7DJPUppQ+4Af 2yzIKl0i83ckxwgM1LXAoDqgIEisUiDXPrL5jEHBTW3i6zEcFoMrkNorOZSB XRjvlmjLqO; Authentication-Results: rtp-dkim-1; header.From=sanjsinh@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; ); Subject: Re: [Sip] New version (-04) of draft-ietf-sip-199 X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org > > >>>"When a forking proxy receives a non-2xx final response which >>>terminates one or more (if forking has occured downstream a final >>>response received by the forking proxy MAY terminate multiple early >>>dialogs), and the proxy does not intend to forward the final >response >>>immedialetly (due to the rules for a forking proxy), >and >>>the UAC has indicated support of the 199 response code, the proxy >>>SHOULD generate and send a 199 response upstream for the early dialog >on which the >>>non-2xx final response was received, unless the proxy has previously >>>recieved and forwarded a 199 response for the dialog." >> >>Wow! We really must shorten this sentence. In particular I don't like >>including a second normative sentence in parentheses within the main >>sentence. > >I can try to think of more simple wording. > >And, text suggestions are of course always welcome :) Along the same lines, I found text about support for 100rel also confusing. I think the preference is that this response be not sent reliably, though the normative strength is slightly week for UAS as compared to a forking proxy. I think it should be simplified and just say that 100rel option does not have significance for this. As an addition, it will also simplify it's association with offer-answer exchange (fact that 199 should have offer sdp for delayed media Invite) Sanjay _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.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 Jan 7 09:22:29 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C6D5C3A6951; Wed, 7 Jan 2009 09:22:29 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5893D3A6951 for ; Wed, 7 Jan 2009 09:22:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.535 X-Spam-Level: X-Spam-Status: No, score=-2.535 tagged_above=-999 required=5 tests=[AWL=0.064, 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 ETjeqKbPpsDA for ; Wed, 7 Jan 2009 09:22:28 -0800 (PST) Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk [195.171.110.225]) by core3.amsl.com (Postfix) with ESMTP id 4D3C93A6802 for ; Wed, 7 Jan 2009 09:22:28 -0800 (PST) Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235]) by siemenscomms.co.uk (PMDF V6.3-x14 #31430) with ESMTP id <0KD4006E92X0SY@siemenscomms.co.uk> for sip@ietf.org; Wed, 07 Jan 2009 17:22:12 +0000 (GMT) Date: Wed, 07 Jan 2009 17:22:12 +0000 From: "Elwell, John" In-reply-to: A To: Christer Holmberg , sip@ietf.org Message-id: <0D5F89FAC29E2C41B98A6A762007F5D0016B395D@GBNTHT12009MSX.gb002.siemens.net> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft Exchange V6.5 Thread-Topic: [Sip] New version (-04) of draft-ietf-sip-199 Thread-Index: AclwpMa2gVaTl0oqRZ+oKLyml2UY7wAEccgwAAJTriAACo7ZIA== Content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: References: A <0D5F89FAC29E2C41B98A6A762007F5D00167DF83@GBNTHT12009MSX.gb002.siemens.net> A Subject: Re: [Sip] New version (-04) of draft-ietf-sip-199 X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org Christer, > >>"When a forking proxy receives a non-2xx final response which > >>terminates one or more (if forking has occured downstream a final > >>response received by the forking proxy MAY terminate multiple early > >>dialogs), and the proxy does not intend to forward the > >>final response immedialetly (due to the rules for a forking proxy), > and > >>the UAC has indicated support of the 199 response code, the proxy > >>SHOULD generate and send a 199 response upstream for the > early dialog > on which the > >>non-2xx final response was received, unless the proxy has > >>previously recieved and forwarded a 199 response for the dialog." > > > >Wow! We really must shorten this sentence. In particular I > >don't like including a second normative sentence in > >parentheses within the main sentence. > > I can try to think of more simple wording. > > And, text suggestions are of course always welcome :) > How about: "When a forking proxy receives a non-2xx final response that terminates one or more early dialogs, if the proxy does not intend to forward the final response immediately (in accordance with rules for a forking proxy) and the UAC has indicated support for the 199 response code, the proxy SHOULD generate and send a 199 response upstream for each early dialog terminated on the downstream side by the non-2xx final response, except for any early dialog for which the proxy has previously received and forwarded a 199 response. Note that if forking has also occurred downstream of the forking proxy, a final response received by the forking proxy can terminate multiple early dialogs." I have removed the normative statement that was in parentheses and created a separate sentence at the end. However, I believe it does not need to be normative - it is just a statement of something that arises because of the normative provisions of RFC 3261. I believe the proxy should send a 199 response on EACH affected early dialog (unless 199 already sent). This too is reflected in my proposed rewording. I hope this helps. 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 misha.a@ampi.com.tw Wed Jan 7 09:28:57 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C644F3A6843 for ; Wed, 7 Jan 2009 09:28:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -11.47 X-Spam-Level: X-Spam-Status: No, score=-11.47 tagged_above=-999 required=5 tests=[BAYES_99=3.5, GB_I_LETTER=-2, HELO_EQ_DYNAMIC=1.144, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_EXTRA_CLOSE=2.809, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_UNI=0.591, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mMu1S-05KdoY for ; Wed, 7 Jan 2009 09:28:56 -0800 (PST) Received: from host86-4-dynamic.47-79-r.retail.telecomitalia.it (host86-4-dynamic.47-79-r.retail.telecomitalia.it [79.47.4.86]) by core3.amsl.com (Postfix) with SMTP id B55F93A6802 for ; Wed, 7 Jan 2009 09:28:53 -0800 (PST) To: Subject: failure notice From: MIME-Version: 1.0 Importance: High Content-Type: text/html X-Antivirus: avast! (VPS 080930-0, 30/09/2008), Outbound message X-Antivirus-Status: Clean Message-Id: <20090107172855.B55F93A6802@core3.amsl.com> Date: Wed, 7 Jan 2009 09:28:53 -0800 (PST) About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

C2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 98052 From sip-bounces@ietf.org Wed Jan 7 11:37:03 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 035E33A6999; Wed, 7 Jan 2009 11:37:03 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D4B183A6932 for ; Wed, 7 Jan 2009 11:37:00 -0800 (PST) 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 pRPKmKyxUnPg for ; Wed, 7 Jan 2009 11:36:55 -0800 (PST) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 746B43A6843 for ; Wed, 7 Jan 2009 11:36:55 -0800 (PST) Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id D083820692; Wed, 7 Jan 2009 20:36:40 +0100 (CET) X-AuditID: c1b4fb3c-aaf58bb00000304c-87-496504484334 Received: from esealmw126.eemea.ericsson.se (unknown [153.88.253.125]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id A70DA2025B; Wed, 7 Jan 2009 20:36:40 +0100 (CET) Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Jan 2009 20:36:40 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 7 Jan 2009 20:36:39 +0100 Message-ID: In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D0016B395D@GBNTHT12009MSX.gb002.siemens.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Sip] New version (-04) of draft-ietf-sip-199 thread-index: AclwpMa2gVaTl0oqRZ+oKLyml2UY7wAEccgwAAJTriAACo7ZIAAE4Evw References: A <0D5F89FAC29E2C41B98A6A762007F5D00167DF83@GBNTHT12009MSX.gb002.siemens.net> A <0D5F89FAC29E2C41B98A6A762007F5D0016B395D@GBNTHT12009MSX.gb002.siemens.net> From: "Christer Holmberg" To: "Elwell, John" , X-OriginalArrivalTime: 07 Jan 2009 19:36:40.0286 (UTC) FILETIME=[432E77E0:01C970FF] X-Brightmail-Tracker: AAAAAA== Subject: Re: [Sip] New version (-04) of draft-ietf-sip-199 X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org Hi John, >>>>"When a forking proxy receives a non-2xx final response which >>>>terminates one or more (if forking has occured downstream a final >>>>response received by the forking proxy MAY terminate multiple early >>>>dialogs), and the proxy does not intend to forward the final >>>>response immedialetly (due to the rules for a forking proxy), >>>>and the UAC has indicated support of the 199 response code, the proxy >>>>SHOULD generate and send a 199 response upstream for the early dialog >>>>on which the non-2xx final response was received, unless the proxy has previously >>>>recieved and forwarded a 199 response for the dialog." >>> >>>Wow! We really must shorten this sentence. In particular I don't like >>>including a second normative sentence in parentheses within the main >>>sentence. >> >>I can try to think of more simple wording. >> >>And, text suggestions are of course always welcome :) >> >How about: >"When a forking proxy receives a non-2xx final response that terminates one or more early dialogs, if the proxy does not intend to forward the final response immediately (in accordance with rules for a >forking proxy) and the UAC has indicated support for the 199 response code, the proxy SHOULD generate and send a 199 response upstream for each early dialog terminated on the downstream side by the >non-2xx final response, except for any early dialog for which the proxy has previously received and forwarded a 199 response. Note that if forking has also occurred downstream of the forking proxy, a >final response received by the forking proxy can terminate multiple early dialogs." > >I have removed the normative statement that was in parentheses and created a separate sentence at the end. However, I believe it does not need to be normative - it is just a statement of something that >arises because of the normative provisions of RFC 3261. > >I believe the proxy should send a 199 response on EACH affected early dialog (unless 199 already sent). This too is reflected in my proposed rewording. That is covered in the existing text: "If the forking proxy generates a 199 response, and if the forking proxy is able to identify additional early dialogs which are terminated by the same non-2xx final response, it MUST also generate and send a 199 response upstream for each of those early dialogs, except for any dialog on which the proxy has previously received and forwarded a 199 response." I don't mind working with your proposal, but I think it important to keep the "IF the forking proxy is able to identify additional early dialogs" part, because the forking proxy may not be able to associate other early dialogs with the non-2xx response. One proposal would be the following: "When a forking proxy receives a non-2xx final response that terminates one or more early dialogs, if the proxy does not intend to forward the final response immediately (in accordance with rules for a forking proxy) and the UAC has indicated support for the 199 response code, the proxy SHOULD generate and send a 199 response upstream for each early dialog terminated (if the forking proxy is able to identify additional early dialogs that are terminated by the non-2xx final response) on the downstream side by the non-2xx final response, except for any early dialog for which the proxy has previously received and forwarded a 199 response. Note that if forking has also occurred downstream of the forking proxy, a final response received by the forking proxy can terminate multiple early dialogs. Based on implementation policy, the proxy MAY wait before sending the 199 response, e.g. if the proxy expects to receive a 2xx final response on another dialog shortly after it received the non-2xx final response which triggered the 199 response." 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 Jan 7 11:42:19 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BBD613A6991; Wed, 7 Jan 2009 11:42:19 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 647593A6991 for ; Wed, 7 Jan 2009 11:42:18 -0800 (PST) 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 kgmbjYa-HcYL for ; Wed, 7 Jan 2009 11:42:17 -0800 (PST) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 584613A6843 for ; Wed, 7 Jan 2009 11:42:17 -0800 (PST) Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 2F7D2203DC; Wed, 7 Jan 2009 20:42:03 +0100 (CET) X-AuditID: c1b4fb3c-ab759bb00000304c-2e-4965058b4170 Received: from esealmw128.eemea.ericsson.se (unknown [153.88.253.125]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 0740720014; Wed, 7 Jan 2009 20:42:03 +0100 (CET) Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Jan 2009 20:42:02 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 7 Jan 2009 20:42:01 +0100 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Sip] New version (-04) of draft-ietf-sip-199 thread-index: AclwpMa2gVaTl0oqRZ+oKLyml2UY7wAEccgwAAJTriAACurO0AAFCe7w References: A<0D5F89FAC29E2C41B98A6A762007F5D00167DF83@GBNTHT12009MSX.gb002.siemens.net> From: "Christer Holmberg" To: "Sanjay Sinha (sanjsinh)" , "Elwell, John" , X-OriginalArrivalTime: 07 Jan 2009 19:42:02.0784 (UTC) FILETIME=[0367C200:01C97100] X-Brightmail-Tracker: AAAAAA== Subject: Re: [Sip] New version (-04) of draft-ietf-sip-199 X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org Hi, >>>>"When a forking proxy receives a non-2xx final response which >>>>terminates one or more (if forking has occured downstream a final >>>>response received by the forking proxy MAY terminate multiple early >>>>dialogs), and the proxy does not intend to forward the final >>>>response immedialetly (due to the rules for a forking proxy), >>>>and the UAC has indicated support of the 199 response code, the proxy >>>>SHOULD generate and send a 199 response upstream for the early dialog >>>>on which the non-2xx final response was received, unless the proxy has previously >>>>recieved and forwarded a 199 response for the dialog." >>> >>>Wow! We really must shorten this sentence. In particular I don't like >>>including a second normative sentence in parentheses within the main >>>sentence. >> >>I can try to think of more simple wording. >> >>And, text suggestions are of course always welcome :) > >Along the same lines, I found text about support for 100rel also confusing. I think the preference is that this response be not sent reliably, though the normative strength is slightly week for UAS as >compared to a forking proxy. I think it should be simplified and just say that 100rel option does not have significance for this. As an addition, it will also simplify it's association with offer-answer >exchange (fact that 199 should have offer sdp for delayed media Invite) Well, one of the previous open issues were whether it should be allowed to send 199 reliably, and the proposed way forward was to allow the UAS to send it reliably. 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 Jan 7 13:11:28 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 709DB3A67ED; Wed, 7 Jan 2009 13:11:28 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B5C473A687C for ; Wed, 7 Jan 2009 13:11:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.358 X-Spam-Level: X-Spam-Status: No, score=-1.358 tagged_above=-999 required=5 tests=[AWL=-1.173, BAYES_40=-0.185] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bIS9ayUdYXr6 for ; Wed, 7 Jan 2009 13:11:25 -0800 (PST) Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id BA03C3A677D for ; Wed, 7 Jan 2009 13:11:25 -0800 (PST) Received: from [192.168.2.102] (cpe-72-181-150-177.tx.res.rr.com [72.181.150.177] (may be forged)) (authenticated bits=0) by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id n07LBAeA023089 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for ; Wed, 7 Jan 2009 15:11:12 -0600 Message-Id: From: Dean Willis To: IETF SIP List Mime-Version: 1.0 (Apple Message framework v930.3) Date: Wed, 7 Jan 2009 15:11:04 -0600 X-Mailer: Apple Mail (2.930.3) Subject: [Sip] Heads-up on changes in US Visa Waiver Progam X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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 was sent to the IETF 73 attendees list, and appears to be valid: ------ This is to inform you that, effective January 12, 2009, the requirements to travel visa-free into the United States will be changed. Nationals of Visa Waiver Program countries will still be eligible to travel without a visa, but will have to obtain an approved travel authorization prior to their travel to the United States. The actual approval form and additional information may be found at https://esta.cbp.dhs.gov . ------ This would appear to require that you know what flight you're coming in on before you can request permission to enter the country, so it may affect your trip-planning schedule. I hope the other nations of the world don't enact a retaliatory requirement, but they probably will. Well, there goes the neighborhood. Good luck, everybody! -- 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 Jan 7 13:55:59 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C46FA3A6929; Wed, 7 Jan 2009 13:55:59 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 672453A6996 for ; Wed, 7 Jan 2009 13:55:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uRY5teVRiDnL for ; Wed, 7 Jan 2009 13:55:53 -0800 (PST) Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by core3.amsl.com (Postfix) with ESMTP id C16B43A6813 for ; Wed, 7 Jan 2009 13:55:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=sdoken@qualcomm.com; q=dns/txt; s=qcdkim; t=1231365340; x=1262901340; h=from:to:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:mime-version:x-ironport-av; z=From:=20"Doken,=20Serhad"=20|To:=20 Christer=20Holmberg=20, =0D=0A=20=20=20=20=20=20=20=20"sip@ietf.org"=0D=0A=09|Date:=20Wed,=207=20Jan=202009=2013:55:36=20-08 00|Subject:=20RE:=20New=20version=20(-04)=20of=20draft-ie tf-sip-199|Thread-Topic:=20New=20version=20(-04)=20of=20d raft-ietf-sip-199|Thread-Index:=20AclwpMa2gVaTl0oqRZ+oKLy ml2UY7wAYzdqw|Message-ID:=20|References: =20|In-Reply-To:=20 |Accept-Language:=20en-US|Content-Language:=20en-US |X-MS-Has-Attach:|X-MS-TNEF-Correlator:|acceptlanguage: =20en-US|Content-Type:=20multipart/alternative=3B=0D=0A =09boundary=3D"_000_ED88AAAE8B3D764B9FD8558DE1775B69137D3 DE412NASANEXMB09na_"|MIME-Version:=201.0|X-IronPort-AV: =20E=3DMcAfee=3Bi=3D"5100,188,5488"=3B=20a=3D"14443182"; bh=9hV3R6WiAcSep90dFEXFGAzE+3miLmPb+sH+FJRLynk=; b=TmUR+ShZhq0qZbwmmFZ+yG0/0z/7sSVP2wIClI9IF4yRlkvP8u/8CdvF 5EGigl/c11gKVSNsHoHR1JKzfSIWWbDnByGUk4Tady1QSK9hnXVP26c/J UYxGHoisVMSraGWprnO5X/0wMLOgvAoeuXQfC72HUzrP2t+RyULSXdC37 g=; X-IronPort-AV: E=McAfee;i="5100,188,5488"; a="14443182" Received: from pdmz-ns-mip.qualcomm.com (HELO numenor.qualcomm.com) ([199.106.114.10]) by wolverine02.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 07 Jan 2009 13:55:40 -0800 Received: from msgtransport04.qualcomm.com (msgtransport04.qualcomm.com [129.46.61.156]) by numenor.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n07LtdoF025903 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 7 Jan 2009 13:55:40 -0800 Received: from nasanexhub02.na.qualcomm.com (nasanexhub02.na.qualcomm.com [10.46.143.120]) by msgtransport04.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n07LtT7P021962 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 7 Jan 2009 13:55:39 -0800 Received: from NASANEXMB09.na.qualcomm.com ([129.46.53.109]) by nasanexhub02.na.qualcomm.com ([10.46.143.120]) with mapi; Wed, 7 Jan 2009 13:55:37 -0800 From: "Doken, Serhad" To: Christer Holmberg , "sip@ietf.org" Date: Wed, 7 Jan 2009 13:55:36 -0800 Thread-Topic: New version (-04) of draft-ietf-sip-199 Thread-Index: AclwpMa2gVaTl0oqRZ+oKLyml2UY7wAYzdqw Message-ID: References: In-Reply-To: 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] New version (-04) of draft-ietf-sip-199 X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1179647664==" Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org --===============1179647664== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_ED88AAAE8B3D764B9FD8558DE1775B69137D3DE412NASANEXMB09na_" --_000_ED88AAAE8B3D764B9FD8558DE1775B69137D3DE412NASANEXMB09na_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Last sentence in 3rd paragraph in Sec 1: "When SIP entities upstream receive the first 2xx final response, and they = do not to intend to accept subsequent 2xx final responses, they will automatically terminate other ass= ociated outstanding early dialogs. If additional 2xx final responses are received, for INVITE initiat= ed dialogs those SIP entities will normally send a BYE request using the dialog identifier retri= eved from the subsequent 2xx final response." since the context is 199 and early dialogs, do we need the reference to INV= or can we simplify say : "If additional 2xx final responses are received, they will send a BYE reque= st using the dialog identifier retrieved from the subsequent 2xx final response" Sec 4.1, last sentence, readability is better if modified as : "...if a 199 response is received for that early dialog, client terminates = it. Afterwards, client SHOULD act as before the first early dialog as estab= lished Other nits: Sec 1 and 4, decissions -> decisions Sec4, dialogusage -> dialog usage desribed -> described Sec 4.1example 6, diaogs ->dialogs Sec 4.2, announcement -> announcement Sec 6, immedialetly > immediately occurred -> occurred received -> received reliably -> reliably prxy -> proxy Sec 7, compability -> compatibility Thanks, Serhad ________________________________ From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of Chris= ter Holmberg Sent: Wednesday, January 07, 2009 12:49 AM To: sip@ietf.org Subject: [Sip] New version (-04) of draft-ietf-sip-199 Hi, Based on comments and discussions, I've submitted a new version of the 199 = draft. The currently remaining to-do is to add text to the security chapter. The draft can also be found at: http://users.piuha.net/cholmber/drafts/draft-ietf-sip-199-04.txt Regards, Christer --_000_ED88AAAE8B3D764B9FD8558DE1775B69137D3DE412NASANEXMB09na_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable New version (-04) of draft-ietf-sip-199

Last sentence in 3rd paragr= aph in Sec 1:

 

“When SIP entities upstream receive the first 2xx final resp=
onse, and they do not to intend to accept
su= bsequent 2xx final responses, they will automatically terminate other assoc= iated outstanding early 
di=
alogs. If additional 2xx final responses are received, for INVITE initiated=
 dialogs those SIP
en=
tities will normally send a BYE request using the dialog identifier retriev=
ed from the subsequent
2x=
x final response.”

 

since the context is 199 and early dialogs, do we need the reference to INV or can we simplify say  :

 

“If additional 2xx final responses are received,=
 they will send a BYE request using the dialog identifier retrieved from th=
e subsequent
2x=
x final response”

 

Sec 4.1, last sentence, readability is= better if modified as :

 

“…if a 199 response is received for that early dialog, client terminates it. Afterwards, client SH= OULD act as before the first early dialog as established

 

 

Other nits:

Sec 1 and 4, decissions<= font size=3D2 color=3Dnavy face=3DArial> -> decisions

Sec4, dialogusage -> dialog usage

      &n= bsp;   desribed -> described

Sec 4.1example 6, diaogs ->dialogs<= o:p>

Sec 4.2, announcement -&= gt; announcement

Sec 6, immedialetly > immediately

           occurr= ed -> occurred

           receiv= ed -> received

           reliably  -> reliably

           prxy -= > proxy

Sec 7, compability -> compatibility=

 

Thanks,

Serhad

 

From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of Christer Holmberg
Sent: Wednesday, January 07,= 2009 12:49 AM
To: sip@ietf.org
Subject: [Sip] New version (= -04) of draft-ietf-sip-199

 

 

Hi,

Based on comments and discussions, I've submitted a new version of the 199 draft.=

The currently remaining to-do is to add text to the security chapter.

The draft can also be found at:

<= font size=3D2 face=3DArial>ht= tp://users.piuha.net/cholmber/drafts/draft-ietf-sip-199-04.txt

Regards,

Christer

--_000_ED88AAAE8B3D764B9FD8558DE1775B69137D3DE412NASANEXMB09na_-- --===============1179647664== 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 --===============1179647664==-- From sip-bounces@ietf.org Wed Jan 7 18:06:28 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C72583A68A6; Wed, 7 Jan 2009 18:06:28 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 882B73A68A6 for ; Wed, 7 Jan 2009 18:06:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.598 X-Spam-Level: X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lisJ6GpsG7QN for ; Wed, 7 Jan 2009 18:06:26 -0800 (PST) Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by core3.amsl.com (Postfix) with ESMTP id 52C573A6885 for ; Wed, 7 Jan 2009 18:06:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=sreeramk@qualcomm.com; q=dns/txt; s=qcdkim; t=1231380373; x=1262916373; h=from:to:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:mime-version:x-ironport-av; z=From:=20"Kanumuri,=20Sreeram"=20 |To:=20"christer.holmberg@ericsson.com"=20,=0D=0A=20=20=20=20=20=20=20=20"sip@ietf .org"=20|Date:=20Wed,=207=20Jan=202009=2018 :06:11=20-0800|Subject:=20RE:=20New=20version=20(-04)=20o f=20draft-ietf-sip-199|Thread-Topic:=20New=20version=20(- 04)=20of=20draft-ietf-sip-199|Thread-Index:=20AclwpMa2gVa Tl0oqRZ+oKLyml2UY7wAYzdqwAAsnL4A=3D|Message-ID:=20|References:=20=0D=0A=20|In-Reply-To:=20|Accept-Language:=20en -US|Content-Language:=20en-US|X-MS-Has-Attach: |X-MS-TNEF-Correlator:|acceptlanguage:=20en-US |Content-Type:=20multipart/alternative=3B=0D=0A=09boundar y=3D"_000_C520399B2DDD5448ABBD34D7348FA40C0357D73404NALAS EXMB06na_"|MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfe e=3Bi=3D"5100,188,5488"=3B=20a=3D"14451164"; bh=alK9E+Q4lWYv4fykWoBki2bqmbyLkTLO1s4Qgc1BKeo=; b=radnpRUgLVhkTi37xb/bdh4Un+W3m5zLUsE/pz+cm4CK4RIxiyO+4kjg +lRLzqetHtt81THRqtm9KlBZuI5vC+E4VgVtRuo1pB0OHresbJ70kTDWe kPbzXDZc668hOrba7zStK/Sn4yPCxk/wcqUGIrzvlB+dNStS/KdpdGmGT o=; X-IronPort-AV: E=McAfee;i="5100,188,5488"; a="14451164" Received: from pdmz-ns-mip.qualcomm.com (HELO ithilien.qualcomm.com) ([199.106.114.10]) by wolverine02.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 07 Jan 2009 18:06:13 -0800 Received: from msgtransport05.qualcomm.com (msgtransport05.qualcomm.com [129.46.61.150]) by ithilien.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n0826Cfm010430 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 7 Jan 2009 18:06:13 -0800 Received: from nasanexhub01.na.qualcomm.com (nasanexhub01.na.qualcomm.com [10.46.93.121]) by msgtransport05.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n0826Cnk030951 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 7 Jan 2009 18:06:12 -0800 Received: from nalasexhub01.na.qualcomm.com (10.47.130.49) by nasanexhub01.na.qualcomm.com (10.46.93.121) with Microsoft SMTP Server (TLS) id 8.1.336.0; Wed, 7 Jan 2009 18:06:11 -0800 Received: from NALASEXMB06.na.qualcomm.com ([10.47.7.245]) by nalasexhub01.na.qualcomm.com ([10.47.130.49]) with mapi; Wed, 7 Jan 2009 18:06:11 -0800 From: "Kanumuri, Sreeram" To: "christer.holmberg@ericsson.com" , "sip@ietf.org" Date: Wed, 7 Jan 2009 18:06:11 -0800 Thread-Topic: New version (-04) of draft-ietf-sip-199 Thread-Index: AclwpMa2gVaTl0oqRZ+oKLyml2UY7wAYzdqwAAsnL4A= Message-ID: References: In-Reply-To: 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] New version (-04) of draft-ietf-sip-199 X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0944376238==" Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org --===============0944376238== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_C520399B2DDD5448ABBD34D7348FA40C0357D73404NALASEXMB06na_" --_000_C520399B2DDD5448ABBD34D7348FA40C0357D73404NALASEXMB06na_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Here are my comments on the draft: >From section 9 >NOTE: If the INVITE request did not contain an SDP offer, and the 199 >response is the first reliably sent response, the 199 response is >required to contain an SDP offer. Can you make clear about the SDP-offer more clearly.. >From sec 10 it looks like 199 is not send reliably but from sec 9 ,"the 199 response is the first reliably sent response is re= quired to contain an SDP offer". I would say, we may not get a case where we will be ending up sending SDP-o= ffer in 199. Thanking you, Regards, Sreeram ________________________________ From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of Chris= ter Holmberg Sent: Wednesday, January 07, 2009 12:49 AM To: sip@ietf.org Subject: [Sip] New version (-04) of draft-ietf-sip-199 Hi, Based on comments and discussions, I've submitted a new version of the 199 = draft. The currently remaining to-do is to add text to the security chapter. The draft can also be found at: http://users.piuha.net/cholmber/drafts/draft-ietf-sip-199-04.txt Regards, Christer --_000_C520399B2DDD5448ABBD34D7348FA40C0357D73404NALASEXMB06na_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable New version (-04) of draft-ietf-sip-199

Hi,

 

Here are my comments on the draft:

 

From section 9

>NOTE: If the INVITE request did not contain an SDP offer, and t= he 199

>response is the first reliably sent response, the 199 response = is

>required to contain an SDP offer.

 

Can you make clear about the SDP-offer more clearly..=

 

From sec 10 it looks like 199 is not send reliably

but from sec 9 ,"the 199 response is the first reliably sent response is required to contain an SDP offer".

 

I would say, we may not get a case where we will be ending up sendi= ng SDP-offer in 199.

 

Thanking you,

 

Regards,

Sreeram

 

From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of Christer Holmberg
Sent: Wednesday, January 07,= 2009 12:49 AM
To: sip@ietf.org
Subject: [Sip] New version (= -04) of draft-ietf-sip-199

 

 

Hi,

Based on comments and discussions, I've submitted a new version of the 199 draft.=

The currently remaining to-do is to add text to the security chapter.

The draft can also be found at:

<= font size=3D2 face=3DArial>ht= tp://users.piuha.net/cholmber/drafts/draft-ietf-sip-199-04.txt

Regards,

Christer

--_000_C520399B2DDD5448ABBD34D7348FA40C0357D73404NALASEXMB06na_-- --===============0944376238== 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 --===============0944376238==-- From klosterboert@advantis.vnet.ibm.com Wed Jan 7 20:27:30 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E7423A6827 for ; Wed, 7 Jan 2009 20:27:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -27.622 X-Spam-Level: X-Spam-Status: No, score=-27.622 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, GB_I_LETTER=-2, HELO_DYNAMIC_DHCP=1.398, HELO_DYNAMIC_IPADDR=2.426, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_UNI=0.591, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tEN8jI-CHasg for ; Wed, 7 Jan 2009 20:27:29 -0800 (PST) Received: from DSL62-0-147-58.bb.netvision.net.il (DSL62-0-147-58.bb.netvision.net.il [62.0.147.58]) by core3.amsl.com (Postfix) with SMTP id 594E83A67B3 for ; Wed, 7 Jan 2009 20:27:27 -0800 (PST) To: Subject: Your order 99816 From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090108042728.594E83A67B3@core3.amsl.com> Date: Wed, 7 Jan 2009 20:27:27 -0800 (PST)
About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

©2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 82352
From sip-bounces@ietf.org Wed Jan 7 22:20:57 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E5A283A69FF; Wed, 7 Jan 2009 22:20:56 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E18AE3A6A08 for ; Wed, 7 Jan 2009 22:20:55 -0800 (PST) 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 rNomFBePhdwm for ; Wed, 7 Jan 2009 22:20:54 -0800 (PST) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 636803A69FF for ; Wed, 7 Jan 2009 22:20:53 -0800 (PST) Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 185AF2096F; Thu, 8 Jan 2009 07:20:36 +0100 (CET) X-AuditID: c1b4fb3c-abf5abb00000304c-cf-49659b3330ad Received: from esealmw128.eemea.ericsson.se (unknown [153.88.253.125]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id E5E5B2098E; Thu, 8 Jan 2009 07:20:35 +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, 8 Jan 2009 07:20:35 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 8 Jan 2009 07:20:34 +0100 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: New version (-04) of draft-ietf-sip-199 thread-index: AclwpMa2gVaTl0oqRZ+oKLyml2UY7wAYzdqwAAsnL4AACSAjwA== References: From: "Christer Holmberg" To: "Kanumuri, Sreeram" , X-OriginalArrivalTime: 08 Jan 2009 06:20:35.0847 (UTC) FILETIME=[37C53970:01C97159] X-Brightmail-Tracker: AAAAAA== Subject: Re: [Sip] New version (-04) of draft-ietf-sip-199 X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1537677041==" Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org This is a multi-part message in MIME format. --===============1537677041== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C97159.3772417A" This is a multi-part message in MIME format. ------_=_NextPart_001_01C97159.3772417A Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Sreeram, =20 An UAS is currently allowed to send 199 reliably (a forking proxy is not allowed to do it). =20 Regards, =20 Christer ________________________________ From: Kanumuri, Sreeram [mailto:sreeramk@qualcomm.com]=20 Sent: 8. tammikuuta 2009 4:06 To: Christer Holmberg; sip@ietf.org Subject: RE: New version (-04) of draft-ietf-sip-199 =09 =09 Hi, =20 Here are my comments on the draft: =20 From section 9 >NOTE: If the INVITE request did not contain an SDP offer, and the 199 >response is the first reliably sent response, the 199 response is >required to contain an SDP offer. =20 Can you make clear about the SDP-offer more clearly.. =20 From sec 10 it looks like 199 is not send reliably but from sec 9 ,"the 199 response is the first reliably sent response is required to contain an SDP offer". =20 I would say, we may not get a case where we will be ending up sending SDP-offer in 199. =20 Thanking you, =20 Regards, Sreeram =20 =09 ________________________________ From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of Christer Holmberg Sent: Wednesday, January 07, 2009 12:49 AM To: sip@ietf.org Subject: [Sip] New version (-04) of draft-ietf-sip-199 =20 =20 Hi,=20 Based on comments and discussions, I've submitted a new version of the 199 draft.=20 The currently remaining to-do is to add text to the security chapter.=20 The draft can also be found at:=20 http://users.piuha.net/cholmber/drafts/draft-ietf-sip-199-04.txt =20 Regards,=20 Christer=20 ------_=_NextPart_001_01C97159.3772417A Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable New version (-04) of draft-ietf-sip-199
Hi Sreeram,
 
An UAS is currently allowed to send 199 = reliably (a forking=20 proxy is not allowed to do it).
 
Regards,
 
Christer

From: Kanumuri, Sreeram=20 [mailto:sreeramk@qualcomm.com]
Sent: 8. tammikuuta 2009=20 4:06
To: Christer Holmberg; sip@ietf.org
Subject: = RE: New=20 version (-04) of draft-ietf-sip-199

Hi,

 

Here are my comments on the = draft:

 

From section 9

>NOTE: If the INVITE request did not = contain an SDP=20 offer, and the 199

>response is the first reliably sent = response, the=20 199 response is

>required to contain an SDP=20 offer.

 

Can you make clear about the SDP-offer more=20 clearly..

 

From sec 10 it looks like 199 is not send=20 reliably

but from sec 9 ,"the 199 response is the = first=20 reliably sent response is required to contain an SDP = offer".

 

I would say, we may not get a case where we = will be=20 ending up sending SDP-offer in 199.

 

Thanking you,

 

Regards,

Sreeram

 

From:=20 sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of Christer=20 Holmberg
Sent: = Wednesday,=20 January 07, 2009 12:49 AM
To:=20 sip@ietf.org
Subject: [Sip]=20 New version (-04) of draft-ietf-sip-199

 

 

Hi,

Based on comments and = discussions,=20 I've submitted a new version of the 199 draft.

The currently remaining = to-do is=20 to add text to the security chapter.

The draft can also be = found=20 at:

http://users.piuha.net/cholmber/drafts/draft-ietf-sip-199-04.txt=20

Regards, =

Christer=20

------_=_NextPart_001_01C97159.3772417A-- --===============1537677041== 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 --===============1537677041==-- From sip-bounces@ietf.org Wed Jan 7 22:58:34 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B4BC03A6A6D; Wed, 7 Jan 2009 22:58:34 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BCD7528C102 for ; Wed, 7 Jan 2009 22:58:32 -0800 (PST) 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 cFCI-iK1v2nW for ; Wed, 7 Jan 2009 22:58:31 -0800 (PST) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 99F5E3A68B0 for ; Wed, 7 Jan 2009 22:58:31 -0800 (PST) Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 43B2020733; Thu, 8 Jan 2009 07:58:17 +0100 (CET) X-AuditID: c1b4fb3c-acf5cbb00000304c-10-4965a409e72f Received: from esealmw126.eemea.ericsson.se (unknown [153.88.253.125]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 1A4462058E; Thu, 8 Jan 2009 07:58:17 +0100 (CET) Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 8 Jan 2009 07:58:16 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 8 Jan 2009 07:58:16 +0100 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: New version (-04) of draft-ietf-sip-199 thread-index: AclwpMa2gVaTl0oqRZ+oKLyml2UY7wAYzdqwABT8VuA= References: From: "Christer Holmberg" To: "Doken, Serhad" , X-OriginalArrivalTime: 08 Jan 2009 06:58:16.0806 (UTC) FILETIME=[7B683060:01C9715E] X-Brightmail-Tracker: AAAAAA== Subject: Re: [Sip] New version (-04) of draft-ietf-sip-199 X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org Hi Serhad, >Last sentence in 3rd paragraph in Sec 1: > >"When SIP entities upstream receive the first 2xx final response, and they do not to intend to accept >subsequent 2xx final responses, they will automatically terminate other associated outstanding early >dialogs. If additional 2xx final responses are received, for INVITE initiated dialogs those SIP >entities will normally send a BYE request using the dialog identifier retrieved from the subsequent >2xx final response." > >since the context is 199 and early dialogs, do we need the reference to INV or can we simplify say : > >"If additional 2xx final responses are received, they will send a BYE request using the dialog identifier retrieved from the subsequent >2xx final response" Looks ok. >Sec 4.1, last sentence, readability is better if modified as : > >"...if a 199 response is received for that early dialog, client terminates it. Afterwards, client SHOULD act as before the first early dialog as established Ok. So, the new text would be something like (with some minor additional editorials): "If the client only has a single early dialog (other early dialogs MAY not have been established, or they MAY have been established and later terminated) and a 199 response is received for that early dialog, the client terminates it. Afterwards, the client after the client SHOULD act as before the first early dialog was established." >Other nits: > >Sec 1 and 4, decissions -> decisions > >Sec4, dialogusage -> dialog usage > >desribed -> described > >Sec 4.1example 6, diaogs ->dialogs > >Sec 4.2, announcement -> announcement > >Sec 6, immedialetly > immediately > >occurred -> occurred > >received -> received > >reliably -> reliably > >prxy -> proxy > >Sec 7, compability -> compatibility I'll fix those. Thank You for the comments! :) Regards, Christer ________________________________ From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of Christer Holmberg Sent: Wednesday, January 07, 2009 12:49 AM To: sip@ietf.org Subject: [Sip] New version (-04) of draft-ietf-sip-199 Hi, Based on comments and discussions, I've submitted a new version of the 199 draft. The currently remaining to-do is to add text to the security chapter. The draft can also be found at: http://users.piuha.net/cholmber/drafts/draft-ietf-sip-199-04.txt 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 Jan 8 06:18:08 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2B8353A677C; Thu, 8 Jan 2009 06:18:08 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0132828C163 for ; Thu, 8 Jan 2009 06:18:07 -0800 (PST) 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 ARFk+50V4XIj for ; Thu, 8 Jan 2009 06:18:05 -0800 (PST) Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 5ACA93A676A for ; Thu, 8 Jan 2009 06:18:05 -0800 (PST) Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id EF67B20018; Thu, 8 Jan 2009 15:17:50 +0100 (CET) X-AuditID: c1b4fb3e-af070bb00000429e-ce-49660b0e898c Received: from esealmw127.eemea.ericsson.se (unknown [153.88.253.125]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id C17BD2019B; Thu, 8 Jan 2009 15:17:50 +0100 (CET) Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 8 Jan 2009 15:17:50 +0100 Received: from [131.160.37.44] ([131.160.37.44]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 8 Jan 2009 15:17:50 +0100 Message-ID: <49660B0D.5050207@ericsson.com> Date: Thu, 08 Jan 2009 16:17:49 +0200 From: Gonzalo Camarillo User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Hadriel Kaplan References: <49305D82.7000907@cisco.com> <49347B88.3010801@softarmor.com> <4934F9C1.5070400@ericsson.com> <3C59889E-BE62-4881-9CAA-E1A12355EF50@standardstrack.com> <49476F22.7050603@ericsson.com> In-Reply-To: X-OriginalArrivalTime: 08 Jan 2009 14:17:50.0262 (UTC) FILETIME=[E3363560:01C9719B] X-Brightmail-Tracker: AAAAAA== Cc: SIP List Subject: Re: [Sip] Body handling - Contexts WAS (Re: multiple bodies in any SIP message) X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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, by now, most people should be back from their vacation. I will wait a few days for further comments and, if everybody is happy with the current draft and no one proposes new text, we will go ahead request its publication. Thanks, Gonzalo Hadriel Kaplan wrote: > I think that's really a question for the others (Paul, Dean, Eric). I interpreted body-handling to address the issue already, but maybe not the backward compatibility issue. > > Also, section 8.1. talks about the context being defined by the method, C-D and C-T. It should probably mention that the Event package for SUB/NOT/PUB and soon the Info-Event package narrows the context further. And I'm not sure that C-T has anything to do with defining a context. > > -hadriel > >> -----Original Message----- >> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com] >> Sent: Tuesday, December 16, 2008 4:05 AM >> To: Hadriel Kaplan >> Cc: Eric Burger; SIP List >> Subject: Body handling - Contexts WAS (Re: [Sip] multiple bodies in any >> SIP message) >> >> Hi Hadriel, >> >> > I think the body-handling draft already does it, although maybe I'm >> > reading into it what I want to and not what it really says. >> >> the draft already talks about contexts: >> >> http://tools.ietf.org/html/draft-ietf-sip-body-handling-05#section-8.1 >> >> I would like to agree on a concrete way forward. Do you think we should >> add something to the body handling draft? Maybe expand the information >> on contexts? Maybe provide guidelines for extension developers so that >> they take them into account when defining new extensions? >> >> Thanks, >> >> Gonzalo >> >> >> Hadriel Kaplan wrote: >>> [note: changing the thread to be consistent] >>> >>>> -----Original Message----- >>>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of >> Eric >>>> Burger >>>> Sent: Sunday, December 07, 2008 10:37 AM >>>> Everyone seems to think there needs to be a generic way of identifying >>>> body bits. >>>> I do not see an obvious, generic way of doing this. >>>> Thus for those out there who think there is a generic way of >>>> identifying body parts for SIP, please write text. >>> I think the body-handling draft already does it, although maybe I'm >> reading into it what I want to and not what it really says. >>> You asked, so this email is long. This is what I think is the way to do >> it... >>> :Executive summary: basically we let C-D of "render" mean render to the >> specific context of the message; we mandate future extensions which are >> not for that context disambiguate themselves, by not using a C-D of >> "render" or the other ones already in use, and that they can't use a C-T >> already used today either. (and that includes changing geoloc's C-T >> immediately) >>> :The Details: >>> >>> Definitions: >>> User-context = the specific context defined by the method name, and >> package if it's a method which has a package sub-context >> (SUB/NOT/PUB/INF). The target user is the user-context's app-layer. For >> example an "application/dtmf-relay" body-part would want to be targeted to >> the user-context defined by the "dtmf" package in an INFO. >>> Method-only-context = the context defined by the method name alone, >> ignoring any package. The target is the specific message processor/state- >> machine for that method, but for any/all packages/sub-contexts. For >> example the Event and Subscription-State headers are for this context in a >> SUBSCRIBE. For methods that don't have a package (INV/UPD/ACK/PRA/MSG), >> the method-only-context and user-context are the same. So the "session" >> and "early-session" C-D's are really for a user-context, but it's the same >> context as method-only-context. I don't know of any bodies which are >> currently only for a method-only-context.(?) Nor am I convinced we even >> need this context to be defined separately. >>> All-messages-context = the context is just the SIP message processing >> rules common to all messages. The target is the SIP message processor >> common to all SIP messages. The mandatory SIP headers (Call-ID, To, From, >> etc.) are examples of things targeted for this context. An AIB, geoloc, >> and maybe sipfrag(?) bodies are targets for this context. >>> Note on above: If you think of this as a layered model with an API, or >> better yet a class object model - basically the all-messages-context is >> for things needing to be handled/extracted in the base SIP message class, >> the method-only-context is for stuff to be handled in a derived class for >> a given method, and the user-context is for stuff to be handled by a >> derived class from that for a given package, which may just be the same >> class for some methods (INV/UPD/etc.). >>> Rules: >>> 1) Any body-part with a C-D of "render", means to render it to the >> "user" - not the human user, but the *user-context*. This lets us get >> backwards-compatibility for free, because a C-D of "render" is implicit >> and what current SIP messages actually have and UA's expect. That C-D >> becomes the "default" so to speak, which it already is today. >>> 2) Any package (event of info) can define additional C-D's that belong >> to it, just like they can define C-T's that they support. I am not >> entirely thrilled with letting packages define C-D's, but some already do >> ("signal", for example). If we'd rather just grandfather those and say no >> more that's fine. ISTM that a package could get that semantic purpose >> information from within the boy content itself (in XML, for example) if it >> really needs such. Methods already do too, like "session" or "early- >> session". If we decide packages can have their own C-D's, then we need >> additional rules not to step on body parts for others, but I'll skip that >> for now. >>> 3) Any body-part that is NOT for the user-context, for example a geoloc, >> needs to disambiguate itself from the rest, by using a C-D other than >> "render" or the ones already defined. If it needs a sub-context other >> than the all-messages-context, or is in fact tied to a SIP header, then it >> needs to use CID, and a C-D of "by-reference". I would in fact suggest >> that all future extensions which need to be for something other than the >> user-context MUST have a referencing SIP header and use a CID and a C-D of >> by-reference. >>> 4) Furthermore, any future extension which is not for the user-context >> MUST NOT use any C-T currently defined in any RFC or WG draft for SIP, >> including already defined event-packages. That sounds harsh, but that's >> what we need to do to get a very high degree of backwards-compatibility I >> think. So this means you can't do a geoloc-type thing using "text/plain", >> for example, or really even "application/pidf+xml", which is what geoloc >> currently uses in its draft. And body-handling or some other draft should >> list all such C-T's, so future extensions can know the list to avoid. And >> if we want to just say no C-T currently define by IANA period, I'm fine >> with that too. Note this does NOT prevent future SIP RFCs from using a C- >> T defined by such an extension as geoloc. For example, if geoloc uses >> "application/foobar", then a future Event-package could use that too; >> because that future event package would normatively reference body- >> handling. >>> 5) IF we need an option tag (and I do NOT think we do), then we should >> create one and only one tag right now, for the body-handling draft's >> logic. Future extensions which are not for the user-context would then >> NOT need more option tags simply due to body-handling issues, but can use >> that generic one. I would also put in some extreme language into the >> body-handling option tag about what it means to put such a thing in a >> Require header, to dissuade people from doing that. >>> 6) If there are some already defined things which do not follow the >> above rules, we either (a) grandfather them into body-handling right now, >> or if they're not really in use, then either (b) deprecate or (c) replace >> them. (and I would vote for (b), fwiw) >>> -hadriel > _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.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 Jan 8 08:54:22 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B6733A6859; Thu, 8 Jan 2009 08:54:22 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8724E3A6853 for ; Thu, 8 Jan 2009 08:54:20 -0800 (PST) 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 bET1e6tAMzyi for ; Thu, 8 Jan 2009 08:54:09 -0800 (PST) Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 8D2E93A6859 for ; Thu, 8 Jan 2009 08:54:09 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,235,1231113600"; d="scan'208";a="33181507" Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 08 Jan 2009 16:53:55 +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 n08Grtff016704; Thu, 8 Jan 2009 11:53:55 -0500 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 n08GrtrA010959; Thu, 8 Jan 2009 16:53:55 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, 8 Jan 2009 11:53:55 -0500 Received: from [10.82.250.46] ([10.82.250.46]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 8 Jan 2009 11:53:55 -0500 Message-ID: <49662FA2.5050800@cisco.com> Date: Thu, 08 Jan 2009 11:53:54 -0500 From: Jonathan Rosenberg User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Shida Schubert References: In-Reply-To: X-OriginalArrivalTime: 08 Jan 2009 16:53:55.0300 (UTC) FILETIME=[B1359A40:01C971B1] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1442; t=1231433635; x=1232297635; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jdrosen@cisco.com; z=From:=20Jonathan=20Rosenberg=20 |Subject:=20Re=3A=20[Sip]=20BCP=20or=20Informational=3A=20M echanisms=20for=20UA=20initiated=20privacy |Sender:=20 |To:=20Shida=20Schubert=20; bh=NGybPIzghs2Xc90CTul92Nzf7YbUDWfPWaR9HXQ3pG4=; b=GswMhtEIBgLUfKkKGfXWFJIMm/DpDhPfP2Y/yHR8kBG1Yes8B92uB1uUFQ 5BasUmbxUOgmuUnTtQ90M8ldPn9rAruXoRUH6VdsllAI7q15asFm6aiJ1rdK 3cLPuqWVSb; Authentication-Results: rtp-dkim-2; header.From=jdrosen@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); Cc: "sip@ietf.org List" , "Elwell, John" , "Drage, Keith \(Keith\)" Subject: Re: [Sip] BCP or Informational: Mechanisms for UA initiated privacy X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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. -Jonathan R. Shida Schubert wrote: > > At the last meeting, Keith asked the group to provide feedback on > whether the draft-ietf-sip-ua-privacy addressing the milestone > "Mechanisms for UA initiated privacy" should proceed as BCP or > as an informational. > > As a co-author of the draft, my inclination is to go informational. > > Reason is because the 2 specifications the draft requires, namely > GRUU and TURN aren't widely deployed, and neither are RFCs > (Although GRUU I believe is pretty close.). > > Despite the fact that people I talked to are keen on implementing > these specifications, I don't think the draft which requires and > depends on specifications that aren't widely deployed neither RFC > should be proceeded as a Best Current Practice.. > > Regards > Shida > > > _______________________________________________ > Sip mailing list https://www.ietf.org/mailman/listinfo/sip > This list is for NEW development of the core SIP Protocol > Use sip-implementors@cs.columbia.edu for questions on current sip > Use sipping@ietf.org for new developments on the application of sip > -- Jonathan D. Rosenberg, Ph.D. 111 Wood Avenue South Cisco Fellow Iselin, NJ 08830 Cisco, Voice Technology Group jdrosen@cisco.com http://www.jdrosen.net PHONE: (408) 902-3084 http://www.cisco.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 From kristien.spruyt@accent.be Thu Jan 8 10:13:56 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 045963A68C2 for ; Thu, 8 Jan 2009 10:13:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -12.831 X-Spam-Level: X-Spam-Status: No, score=-12.831 tagged_above=-999 required=5 tests=[BAYES_80=2, FH_HOST_EQ_D_D_D_D=0.765, GB_I_LETTER=-2, HELO_DYNAMIC_IPADDR=2.426, HTML_EXTRA_CLOSE=2.809, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_UNI=0.591, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1AbA0c6f8m-9 for ; Thu, 8 Jan 2009 10:13:55 -0800 (PST) Received: from host27.190-224-71.telecom.net.ar (host27.190-224-71.telecom.net.ar [190.224.71.27]) by core3.amsl.com (Postfix) with SMTP id DC73B3A6897 for ; Thu, 8 Jan 2009 10:13:52 -0800 (PST) To: Subject: Mail delivery failed: returning message to sender From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090108181353.DC73B3A6897@core3.amsl.com> Date: Thu, 8 Jan 2009 10:13:52 -0800 (PST) About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

C2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 98052 From sip-mib-subscriben@egroups.com Thu Jan 8 11:03:13 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B13C23A6922 for ; Thu, 8 Jan 2009 11:03:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -59.967 X-Spam-Level: X-Spam-Status: No, score=-59.967 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HOST_EQ_D_D_D_D=0.765, GB_H_CANADIAN=0.5, GB_H_PHARMACY=1, GB_I_LETTER=-2, GB_PHARMACY=1, HELO_MISMATCH_COM=0.553, HOST_EQ_RO=0.904, HTML_IMAGE_ONLY_32=1.778, HTML_MESSAGE=0.001, J_CHICKENPOX_102=0.6, J_CHICKENPOX_25=0.6, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, URIBL_SBL=20, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sxAFHGPlnR8T for ; Thu, 8 Jan 2009 11:03:07 -0800 (PST) Received: from mta.email.webmd.com (dyn-86.106.59.215.ph.upcnet.ro [86.106.59.215]) by core3.amsl.com (Postfix) with SMTP id 6138F3A6968 for ; Thu, 8 Jan 2009 11:03:06 -0800 (PST) Content-Return: allowed X-Mailer: CME-V6.5.4.3; MSN Message-Id: <20090108110156.9026.qmail@mta.email.webmd.com> From: "Doctor Ty" To: sip-archive@lists.ietf.org Subject: RE: (Canadian Pharmacy Message) I had an accident, come now! MIME-Version: 1.0 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Date: Thu, 8 Jan 2009 11:03:06 -0800 (PST) cf.WebMD - Living Better Newsletter.jv
Thu, 8 Jan 2009 09:01:56 +0200
 






 
Women's Health  |  Men's Health   |  Health News  |  Home Page
You are subscribed as sip-archive@lists.ietf.org.
Subscribe to more newsletters. Change/update your email address.


1175 Peachtree Street, Suite 2400, Atlanta, GA 30361
© 2009 WebMD, LLC. All rights reserved.
From mail@abacus-info.de Thu Jan 8 14:49:12 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5C6EC28C0E7 for ; Thu, 8 Jan 2009 14:49:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.318 X-Spam-Level: X-Spam-Status: No, score=-1.318 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_ALMOST_IP=5.417, FH_HOST_ALMOST_IP=1.889, GB_I_LETTER=-2, HELO_DYNAMIC_SPLIT_IP=3.493, HOST_EQ_STATIC=1.172, HOST_EQ_STATICIP=1.511, HTML_EXTRA_CLOSE=2.809, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, SARE_UNI=0.591, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KywNhjZzT9PJ for ; Thu, 8 Jan 2009 14:49:11 -0800 (PST) Received: from 178.Red-88-17-220.staticIP.rima-tde.net (178.Red-88-17-220.staticIP.rima-tde.net [88.17.220.178]) by core3.amsl.com (Postfix) with SMTP id 27B1D3A67F8 for ; Thu, 8 Jan 2009 14:49:09 -0800 (PST) To: Subject: Undeliverable Mail From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090108224910.27B1D3A67F8@core3.amsl.com> Date: Thu, 8 Jan 2009 14:49:09 -0800 (PST) About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

C2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 98052 From akirou@rou-s.akita-c.ed.jp Thu Jan 8 23:32:46 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 95B7B3A68C9; Thu, 8 Jan 2009 23:32:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.158 X-Spam-Level: X-Spam-Status: No, score=-3.158 tagged_above=-999 required=5 tests=[BAYES_60=1, GB_ROLEX=5, J_CHICKENPOX_15=0.6, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033, SARE_SPEC_ROLEX=1.666, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_SBL=20, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HXPF6nmwSc1i; Thu, 8 Jan 2009 23:32:45 -0800 (PST) Received: from U62.N143.QueensU.CA (U62.N143.QueensU.CA [130.15.143.62]) by core3.amsl.com (Postfix) with SMTP id 6DE7F3A65A5; Thu, 8 Jan 2009 23:32:25 -0800 (PST) X-Originating-IP: 192.106.224.192 by smtp.130.15.143.62; Fri, 09 Jan 2009 07:23:09 +0100 Message-ID: Subject: Rolex Submariner Full 18k Gold Only For You Date: Fri, 09 Jan 2009 01:32:09 -0500 From: "Tomas Griffin" To: "Esther Walls" Content-Type: text/plain; Content-Transfer-Encoding: 7bit Hello Esther Get the Finest Rolex Watches here! We only sell premium watches. These original watches sell in stores for thousands of dollars. We sell them for much less. http://www.mindmiss.com/brand.php?br_x=37 * Automatic movement. * Hack mechanism (second hand stops when crown is pulled out to set the time . standard feature on all genuine Rolex watches). * Diver.s extension to watch bracelet. * Sapphire crystal watchglass. * Screws in the links, not pins. * Rolex logo etched at 6 o.clock position on watch dial. * Gold date wheel (as per genuine Rolex All Gold models). * Rubber seal at trip-lock winding crown. * Heavily micron-plated genuine gold. * Magnified quick-set date at 3 o.clock position. * Serial band/number on last link/lugs. * Fliplock oyster bracelet, steelinox clasp, serial number on clasp. * Solid back with characteristic Rolex green sticker. * Screw-in watch crown. * Luminescent hour markers/hands. * All the appropriate Rolex markings in the correct places. http://www.mindmiss.com/product.php?Brand=37&Model=4&Product=1 New Year discount this week only! Make your order before the prices go up. Best regards, Mr. Walls From sip-bounces@ietf.org Fri Jan 9 13:30:50 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 21C573A68FD; Fri, 9 Jan 2009 13:30:50 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D81F43A68FD for ; Fri, 9 Jan 2009 13:30:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.432 X-Spam-Level: X-Spam-Status: No, score=-2.432 tagged_above=-999 required=5 tests=[AWL=0.168, 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 StAYYhEMIqfh for ; Fri, 9 Jan 2009 13:30:47 -0800 (PST) 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 7EE093A68DC for ; Fri, 9 Jan 2009 13:30:47 -0800 (PST) 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.3) with ESMTP id n09LUWR1035314 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 9 Jan 2009 15:30:32 -0600 (CST) (envelope-from adam@nostrum.com) Message-ID: <4967C1F7.7030407@nostrum.com> Date: Fri, 09 Jan 2009 15:30:31 -0600 From: Adam Roach User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: SIP WG Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism) X-Virus-Scanned: ClamAV 0.94.2/8848/Fri Jan 9 07:16:38 2009 on shaman.nostrum.com X-Virus-Status: Clean Cc: Mark Nottingham , Theo Zourzouvillys , "Elwell, John" Subject: [Sip] New HTTP Event Package Draft X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: SIP WG List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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've submitted a new version of draft-roach-sip-http-subscribe, which should address most or all of the comments made to date. Draft available here: Differences between versions highlighted here: /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 Jan 9 17:00:04 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D846028C17E; Fri, 9 Jan 2009 17:00:04 -0800 (PST) X-Original-To: sip@ietf.org Delivered-To: sip@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 5EDCF3A6B09; Fri, 9 Jan 2009 17:00:01 -0800 (PST) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20090110010002.5EDCF3A6B09@core3.amsl.com> Date: Fri, 9 Jan 2009 17:00:01 -0800 (PST) Cc: sip@ietf.org Subject: [Sip] I-D Action:draft-ietf-sip-media-security-requirements-09.txt X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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-09.txt Pages : 47 Date : 2009-01-09 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-09.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-09.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-01-09165625.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 lydabarb@alteontraining.com Sat Jan 10 05:23:27 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 50B1128C1A4 for ; Sat, 10 Jan 2009 05:23:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -45.664 X-Spam-Level: X-Spam-Status: No, score=-45.664 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_RELAY_NODNS=1.451, GB_I_LETTER=-2, HTML_IMAGE_ONLY_12=2.46, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_NONE=0.1, SARE_UNI=0.591, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wql2NoiEmHF0 for ; Sat, 10 Jan 2009 05:23:26 -0800 (PST) Received: from a-m-c.ca (unknown [84.13.158.181]) by core3.amsl.com (Postfix) with SMTP id 82A9F28C19E for ; Sat, 10 Jan 2009 05:23:24 -0800 (PST) To: Subject: Your order 18201 From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090110132325.82A9F28C19E@core3.amsl.com> Date: Sat, 10 Jan 2009 05:23:24 -0800 (PST)

©2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 06619
From mstefanowicz@aacps.org Sat Jan 10 07:11:32 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A55313A68D7 for ; Sat, 10 Jan 2009 07:11:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.327 X-Spam-Level: X-Spam-Status: No, score=-15.327 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_RELAY_NODNS=1.451, GB_I_LETTER=-2, HELO_MISMATCH_COM=0.553, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033, RDNS_NONE=0.1, SARE_UNI=0.591, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wpk3c9gqDYR7 for ; Sat, 10 Jan 2009 07:11:32 -0800 (PST) Received: from allwebcodesign.com (unknown [187.5.16.230]) by core3.amsl.com (Postfix) with SMTP id B799F3A689B for ; Sat, 10 Jan 2009 07:11:30 -0800 (PST) To: Subject: Re: Order status 75960 From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090110151130.B799F3A689B@core3.amsl.com> Date: Sat, 10 Jan 2009 07:11:30 -0800 (PST)
About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

c2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 91092
From osio@ahbennett.com Sat Jan 10 13:39:38 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B64D28C1D2 for ; Sat, 10 Jan 2009 13:39:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.397 X-Spam-Level: X-Spam-Status: No, score=-15.397 tagged_above=-999 required=5 tests=[BAYES_99=3.5, GB_I_LETTER=-2, HELO_EQ_DSL=1.129, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, SARE_UNI=0.591, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qtD19Svu6+uX for ; Sat, 10 Jan 2009 13:39:37 -0800 (PST) Received: from athedsl-4373173.home.otenet.gr (athedsl-4373173.home.otenet.gr [79.130.42.165]) by core3.amsl.com (Postfix) with SMTP id 0EC4128C1D5 for ; Sat, 10 Jan 2009 13:39:35 -0800 (PST) To: Subject: Re: Order status 61805 From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090110213936.0EC4128C1D5@core3.amsl.com> Date: Sat, 10 Jan 2009 13:39:35 -0800 (PST)
About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

c2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 68566
From krissaenz@absincorp.com Sun Jan 11 10:44:19 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B6B23A6AD6 for ; Sun, 11 Jan 2009 10:44:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -13.011 X-Spam-Level: X-Spam-Status: No, score=-13.011 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, GB_I_LETTER=-2, HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR2=4.395, HELO_DYNAMIC_SPLIT_IP=3.493, HELO_EQ_BR=0.955, HELO_EQ_DSL=1.129, HELO_EQ_IP_ADDR=1.119, HOST_EQ_BR=1.295, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RCVD_NUMERIC_HELO=2.067, RDNS_DYNAMIC=0.1, SARE_UNI=0.591, TVD_RCVD_IP=1.931, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nUW0-kNuDctG for ; Sun, 11 Jan 2009 10:44:18 -0800 (PST) Received: from 189.58.25.117.adsl.gvt.net.br (189.58.25.117.adsl.gvt.net.br [189.58.25.117]) by core3.amsl.com (Postfix) with SMTP id BBE383A6AC3 for ; Sun, 11 Jan 2009 10:44:17 -0800 (PST) To: Subject: Re: Order status 59712 From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090111184417.BBE383A6AC3@core3.amsl.com> Date: Sun, 11 Jan 2009 10:44:17 -0800 (PST)
About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

c2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 75166
From mercadoenigmas@aacpl.net Mon Jan 12 06:56:57 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 87FDC3A6941 for ; Mon, 12 Jan 2009 06:56:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -33.339 X-Spam-Level: X-Spam-Status: No, score=-33.339 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_RELAY_NODNS=1.451, GB_I_LETTER=-2, HELO_MISMATCH_COM=0.553, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RDNS_NONE=0.1, SARE_UNI=0.591, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fW9j6HUQLnto for ; Mon, 12 Jan 2009 06:56:55 -0800 (PST) Received: from alcoa.com (unknown [122.173.139.137]) by core3.amsl.com (Postfix) with SMTP id EB6E63A67AF for ; Mon, 12 Jan 2009 06:56:52 -0800 (PST) To: Subject: Your order 18184 From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090112145653.EB6E63A67AF@core3.amsl.com> Date: Mon, 12 Jan 2009 06:56:52 -0800 (PST)
About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

c2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 75739
From sip-bounces@ietf.org Mon Jan 12 09:45:27 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AF93228C343; Mon, 12 Jan 2009 09:45:27 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1805928C33D for ; Mon, 12 Jan 2009 09:45:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.8 X-Spam-Level: X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[AWL=-0.690, 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 k8ekdtMTpByB for ; Mon, 12 Jan 2009 09:45:25 -0800 (PST) Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id 469D328C33B for ; Mon, 12 Jan 2009 09:45:25 -0800 (PST) Received: from [192.168.2.102] (cpe-72-181-150-177.tx.res.rr.com [72.181.150.177] (may be forged)) (authenticated bits=0) by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id n0CHj9dL000868 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for ; Mon, 12 Jan 2009 11:45:10 -0600 Message-Id: <7E3E478E-17F2-4242-B95E-B06053E9BC63@softarmor.com> From: Dean Willis To: IETF SIP List Mime-Version: 1.0 (Apple Message framework v930.3) Date: Mon, 12 Jan 2009 11:45:03 -0600 X-Mailer: Apple Mail (2.930.3) Subject: [Sip] Google Chrome adds HTTPS-only mode X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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've read that the latest dev version of Chrome features a command- line switch to cause the browser to reject HTTP and only load HTTPS sites. That's an interesting concept, given that we've done so poorly at making SIPS actually work in the wild. -- 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 Jan 12 15:04:28 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E73FA28C110; Mon, 12 Jan 2009 15:04:27 -0800 (PST) X-Original-To: sip@ietf.org Delivered-To: sip@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id B79DA3A68CC; Mon, 12 Jan 2009 15:04:25 -0800 (PST) X-idtracker: yes To: IETF-Announce From: The IESG Message-Id: <20090112230425.B79DA3A68CC@core3.amsl.com> Date: Mon, 12 Jan 2009 15:04:25 -0800 (PST) Cc: sip@ietf.org Subject: [Sip] Last Call: draft-ietf-sip-certs (Certificate Management Service for The Session Initiation Protocol (SIP)) 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 List-Unsubscribe: , List-Post: List-Help: List-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: - 'Certificate Management Service for The Session Initiation Protocol (SIP) ' 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 2009-01-26. 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-certs-07.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=14709&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 Mon Jan 12 16:57:30 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 107123A6886; Mon, 12 Jan 2009 16:57:30 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 716C628C130 for ; Mon, 12 Jan 2009 16:57:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.628 X-Spam-Level: X-Spam-Status: No, score=-2.628 tagged_above=-999 required=5 tests=[AWL=-0.029, 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 0FFLKuBTzfAY for ; Mon, 12 Jan 2009 16:57:27 -0800 (PST) Received: from gs19.inmotionhosting.com (gs19.inmotionhosting.com [205.134.252.251]) by core3.amsl.com (Postfix) with ESMTP id 2BDE53A67AD for ; Mon, 12 Jan 2009 16:57:27 -0800 (PST) Received: from [75.68.118.126] (port=61474 helo=[192.168.15.105]) by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1LMXaX-0002g8-PI; Mon, 12 Jan 2009 16:57:02 -0800 Message-Id: From: Eric Burger To: Gonzalo Camarillo In-Reply-To: <49660B0D.5050207@ericsson.com> Mime-Version: 1.0 (Apple Message framework v930.3) Date: Mon, 12 Jan 2009 19:57:06 -0500 References: <49305D82.7000907@cisco.com> <49347B88.3010801@softarmor.com> <4934F9C1.5070400@ericsson.com> <3C59889E-BE62-4881-9CAA-E1A12355EF50@standardstrack.com> <49476F22.7050603@ericsson.com> <49660B0D.5050207@ericsson.com> X-Mailer: Apple Mail (2.930.3) 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 List Subject: Re: [Sip] Body handling - Contexts WAS (Re: multiple bodies in any SIP message) X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1906857604==" Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org --===============1906857604== Content-Type: multipart/signed; boundary=Apple-Mail-54-97956102; micalg=sha1; protocol="application/pkcs7-signature" --Apple-Mail-54-97956102 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit So I went with C-D for the last round of INFO. This isn't e-mail, so matching the C-D with the method, on a per-method basis, works in all cases, as the C-D is a unique (because of the IANA registry) and the method defines it. Thus no one will use INFO's C-D for something else (unless they want to get slapped silly). On Jan 8, 2009, at 9:17 AM, Gonzalo Camarillo wrote: > Hi, > > by now, most people should be back from their vacation. I will wait > a few days for further comments and, if everybody is happy with the > current draft and no one proposes new text, we will go ahead request > its publication. > > Thanks, > > Gonzalo > > Hadriel Kaplan wrote: >> I think that's really a question for the others (Paul, Dean, >> Eric). I interpreted body-handling to address the issue already, >> but maybe not the backward compatibility issue. >> Also, section 8.1. talks about the context being defined by the >> method, C-D and C-T. It should probably mention that the Event >> package for SUB/NOT/PUB and soon the Info-Event package narrows the >> context further. And I'm not sure that C-T has anything to do with >> defining a context. >> -hadriel >>> -----Original Message----- >>> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com] >>> Sent: Tuesday, December 16, 2008 4:05 AM >>> To: Hadriel Kaplan >>> Cc: Eric Burger; SIP List >>> Subject: Body handling - Contexts WAS (Re: [Sip] multiple bodies >>> in any >>> SIP message) >>> >>> Hi Hadriel, >>> >>> > I think the body-handling draft already does it, although maybe >>> I'm >>> > reading into it what I want to and not what it really says. >>> >>> the draft already talks about contexts: >>> >>> http://tools.ietf.org/html/draft-ietf-sip-body-handling-05#section-8.1 >>> >>> I would like to agree on a concrete way forward. Do you think we >>> should >>> add something to the body handling draft? Maybe expand the >>> information >>> on contexts? Maybe provide guidelines for extension developers so >>> that >>> they take them into account when defining new extensions? >>> >>> Thanks, >>> >>> Gonzalo >>> >>> >>> Hadriel Kaplan wrote: >>>> [note: changing the thread to be consistent] >>>> >>>>> -----Original Message----- >>>>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On >>>>> Behalf Of >>> Eric >>>>> Burger >>>>> Sent: Sunday, December 07, 2008 10:37 AM >>>>> Everyone seems to think there needs to be a generic way of >>>>> identifying >>>>> body bits. >>>>> I do not see an obvious, generic way of doing this. >>>>> Thus for those out there who think there is a generic way of >>>>> identifying body parts for SIP, please write text. >>>> I think the body-handling draft already does it, although maybe I'm >>> reading into it what I want to and not what it really says. >>>> You asked, so this email is long. This is what I think is the >>>> way to do >>> it... >>>> :Executive summary: basically we let C-D of "render" mean render >>>> to the >>> specific context of the message; we mandate future extensions >>> which are >>> not for that context disambiguate themselves, by not using a C-D of >>> "render" or the other ones already in use, and that they can't use >>> a C-T >>> already used today either. (and that includes changing geoloc's C-T >>> immediately) >>>> :The Details: >>>> >>>> Definitions: >>>> User-context = the specific context defined by the method name, and >>> package if it's a method which has a package sub-context >>> (SUB/NOT/PUB/INF). The target user is the user-context's app- >>> layer. For >>> example an "application/dtmf-relay" body-part would want to be >>> targeted to >>> the user-context defined by the "dtmf" package in an INFO. >>>> Method-only-context = the context defined by the method name alone, >>> ignoring any package. The target is the specific message >>> processor/state- >>> machine for that method, but for any/all packages/sub-contexts. For >>> example the Event and Subscription-State headers are for this >>> context in a >>> SUBSCRIBE. For methods that don't have a package (INV/UPD/ACK/PRA/ >>> MSG), >>> the method-only-context and user-context are the same. So the >>> "session" >>> and "early-session" C-D's are really for a user-context, but it's >>> the same >>> context as method-only-context. I don't know of any bodies which >>> are >>> currently only for a method-only-context.(?) Nor am I convinced >>> we even >>> need this context to be defined separately. >>>> All-messages-context = the context is just the SIP message >>>> processing >>> rules common to all messages. The target is the SIP message >>> processor >>> common to all SIP messages. The mandatory SIP headers (Call-ID, >>> To, From, >>> etc.) are examples of things targeted for this context. An AIB, >>> geoloc, >>> and maybe sipfrag(?) bodies are targets for this context. >>>> Note on above: If you think of this as a layered model with an >>>> API, or >>> better yet a class object model - basically the all-messages- >>> context is >>> for things needing to be handled/extracted in the base SIP message >>> class, >>> the method-only-context is for stuff to be handled in a derived >>> class for >>> a given method, and the user-context is for stuff to be handled by a >>> derived class from that for a given package, which may just be the >>> same >>> class for some methods (INV/UPD/etc.). >>>> Rules: >>>> 1) Any body-part with a C-D of "render", means to render it to the >>> "user" - not the human user, but the *user-context*. This lets us >>> get >>> backwards-compatibility for free, because a C-D of "render" is >>> implicit >>> and what current SIP messages actually have and UA's expect. That >>> C-D >>> becomes the "default" so to speak, which it already is today. >>>> 2) Any package (event of info) can define additional C-D's that >>>> belong >>> to it, just like they can define C-T's that they support. I am not >>> entirely thrilled with letting packages define C-D's, but some >>> already do >>> ("signal", for example). If we'd rather just grandfather those >>> and say no >>> more that's fine. ISTM that a package could get that semantic >>> purpose >>> information from within the boy content itself (in XML, for >>> example) if it >>> really needs such. Methods already do too, like "session" or >>> "early- >>> session". If we decide packages can have their own C-D's, then we >>> need >>> additional rules not to step on body parts for others, but I'll >>> skip that >>> for now. >>>> 3) Any body-part that is NOT for the user-context, for example a >>>> geoloc, >>> needs to disambiguate itself from the rest, by using a C-D other >>> than >>> "render" or the ones already defined. If it needs a sub-context >>> other >>> than the all-messages-context, or is in fact tied to a SIP header, >>> then it >>> needs to use CID, and a C-D of "by-reference". I would in fact >>> suggest >>> that all future extensions which need to be for something other >>> than the >>> user-context MUST have a referencing SIP header and use a CID and >>> a C-D of >>> by-reference. >>>> 4) Furthermore, any future extension which is not for the user- >>>> context >>> MUST NOT use any C-T currently defined in any RFC or WG draft for >>> SIP, >>> including already defined event-packages. That sounds harsh, but >>> that's >>> what we need to do to get a very high degree of backwards- >>> compatibility I >>> think. So this means you can't do a geoloc-type thing using "text/ >>> plain", >>> for example, or really even "application/pidf+xml", which is what >>> geoloc >>> currently uses in its draft. And body-handling or some other >>> draft should >>> list all such C-T's, so future extensions can know the list to >>> avoid. And >>> if we want to just say no C-T currently define by IANA period, I'm >>> fine >>> with that too. Note this does NOT prevent future SIP RFCs from >>> using a C- >>> T defined by such an extension as geoloc. For example, if geoloc >>> uses >>> "application/foobar", then a future Event-package could use that >>> too; >>> because that future event package would normatively reference body- >>> handling. >>>> 5) IF we need an option tag (and I do NOT think we do), then we >>>> should >>> create one and only one tag right now, for the body-handling draft's >>> logic. Future extensions which are not for the user-context would >>> then >>> NOT need more option tags simply due to body-handling issues, but >>> can use >>> that generic one. I would also put in some extreme language into >>> the >>> body-handling option tag about what it means to put such a thing >>> in a >>> Require header, to dissuade people from doing that. >>>> 6) If there are some already defined things which do not follow the >>> above rules, we either (a) grandfather them into body-handling >>> right now, >>> or if they're not really in use, then either (b) deprecate or (c) >>> replace >>> them. (and I would vote for (b), fwiw) >>>> -hadriel > --Apple-Mail-54-97956102 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 9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wOTAxMTMwMDU3MDZaMCMGCSqGSIb3 DQEJBDEWBBSwAn/D8KlKQKt8zYM0oTHBw4i9yDCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2 MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN H2TynzANBgkqhkiG9w0BAQEFAASCAQCiBm7j2ayv/ActzSH4ep219Nbnn8Md7dTTVaxYTrbmhi2a 4zA66RIbJI2FVfhfB/vGb0T7G4APgzI34eVQZyGKa9VLmHMmaQkGyv/HI8pCi6F+DkDXc0tNsNlX vmvlTahzThZrMJ6bEyi1mjxJTORk/J/eYM6g/UfRT8APB4jAlfQAOfZE2c+ELeQ36uh8v3+j5yvM nvkG5TzVimxwZrjHheUHdbewSHDeBS6WpnAHmBgQLHQvXDe2LUjKgABIk6mMHBHQrJwbqrxwpgnR TyzvSzIgGUYMQIyDwikzw0mOMAVJDXlLeOweW0LKnr/pInpDlGq4yBqkqDxmpiY0NlwEAAAAAAAA --Apple-Mail-54-97956102-- --===============1906857604== 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 --===============1906857604==-- From sip-bounces@ietf.org Tue Jan 13 06:29:29 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A570D3A6AB3; Tue, 13 Jan 2009 06:29:29 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EDCEF3A6A61 for ; Tue, 13 Jan 2009 06:29:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.512 X-Spam-Level: X-Spam-Status: No, score=-6.512 tagged_above=-999 required=5 tests=[AWL=0.087, 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 YTFgSGXg5hKj for ; Tue, 13 Jan 2009 06:29:26 -0800 (PST) Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 2F4133A6AA7 for ; Tue, 13 Jan 2009 06:29:26 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.37,260,1231113600"; d="scan'208";a="33599961" Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 13 Jan 2009 14:29:11 +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 n0DETBXu016906; Tue, 13 Jan 2009 09:29:11 -0500 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 n0DETB97025515; Tue, 13 Jan 2009 14:29:11 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, 13 Jan 2009 09:29:10 -0500 Received: from [161.44.174.124] ([161.44.174.124]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 13 Jan 2009 09:29:10 -0500 Message-ID: <496CA535.8030200@cisco.com> Date: Tue, 13 Jan 2009 09:29:09 -0500 From: Paul Kyzivat User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Eric Burger References: <49305D82.7000907@cisco.com> <49347B88.3010801@softarmor.com> <4934F9C1.5070400@ericsson.com> <3C59889E-BE62-4881-9CAA-E1A12355EF50@standardstrack.com> <49476F22.7050603@ericsson.com> <49660B0D.5050207@ericsson.com> In-Reply-To: X-OriginalArrivalTime: 13 Jan 2009 14:29:10.0371 (UTC) FILETIME=[4CA75B30:01C9758B] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=10193; t=1231856951; x=1232720951; 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 |Subject:=20Re=3A=20[Sip]=20Body=20handling=20-=20Contexts= 20WAS=20(Re=3A=20multiple=20bodies=20in=20any=0A=20SIP=20mes sage) |Sender:=20 |To:=20Eric=20Burger=20; bh=LYv1Qv6Y6hdtS/cDdMb5jY8NdLPs0/EXVo3ZtsXb3Xw=; b=lL/cc9cjvQf/x7XBcwSbKwizLRvzEeZlzTIn2ZyeYN4oXIbeCKq/vdE90D 9dUIvnubaI0QQVa7KrMK13BZr8ewteuVzZ9SkOHf5oGDchrhSTyJBVssHa/y n94zbSKnni; Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); Cc: SIP List , Gonzalo Camarillo Subject: Re: [Sip] Body handling - Contexts WAS (Re: multiple bodies in any SIP message) X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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: > So I went with C-D for the last round of INFO. I still haven't found time to review the latest. But you have now increased my motivation to do so! > This isn't e-mail, so > matching the C-D with the method, on a per-method basis, works in all > cases, as the C-D is a unique (because of the IANA registry) and the > method defines it. Thus no one will use INFO's C-D for something else > (unless they want to get slapped silly). Well... (Here it comes: Paul's exception to the rule) I might find some reason to put part or all of an INFO message in a sipfrag, and then send it to someone in a non-INFO message. (I haven't worked out a real use case yet.) So, will I get slapped silly for that? I think the context for interpreting that is determined by the container it is in, so it shouldn't be a problem. Thanks, Paul > On Jan 8, 2009, at 9:17 AM, Gonzalo Camarillo wrote: > >> Hi, >> >> by now, most people should be back from their vacation. I will wait a >> few days for further comments and, if everybody is happy with the >> current draft and no one proposes new text, we will go ahead request >> its publication. >> >> Thanks, >> >> Gonzalo >> >> Hadriel Kaplan wrote: >>> I think that's really a question for the others (Paul, Dean, Eric). >>> I interpreted body-handling to address the issue already, but maybe >>> not the backward compatibility issue. >>> Also, section 8.1. talks about the context being defined by the >>> method, C-D and C-T. It should probably mention that the Event >>> package for SUB/NOT/PUB and soon the Info-Event package narrows the >>> context further. And I'm not sure that C-T has anything to do with >>> defining a context. >>> -hadriel >>>> -----Original Message----- >>>> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com] >>>> Sent: Tuesday, December 16, 2008 4:05 AM >>>> To: Hadriel Kaplan >>>> Cc: Eric Burger; SIP List >>>> Subject: Body handling - Contexts WAS (Re: [Sip] multiple bodies in any >>>> SIP message) >>>> >>>> Hi Hadriel, >>>> >>>> > I think the body-handling draft already does it, although maybe I'm >>>> > reading into it what I want to and not what it really says. >>>> >>>> the draft already talks about contexts: >>>> >>>> http://tools.ietf.org/html/draft-ietf-sip-body-handling-05#section-8.1 >>>> >>>> I would like to agree on a concrete way forward. Do you think we should >>>> add something to the body handling draft? Maybe expand the information >>>> on contexts? Maybe provide guidelines for extension developers so that >>>> they take them into account when defining new extensions? >>>> >>>> Thanks, >>>> >>>> Gonzalo >>>> >>>> >>>> Hadriel Kaplan wrote: >>>>> [note: changing the thread to be consistent] >>>>> >>>>>> -----Original Message----- >>>>>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of >>>> Eric >>>>>> Burger >>>>>> Sent: Sunday, December 07, 2008 10:37 AM >>>>>> Everyone seems to think there needs to be a generic way of >>>>>> identifying >>>>>> body bits. >>>>>> I do not see an obvious, generic way of doing this. >>>>>> Thus for those out there who think there is a generic way of >>>>>> identifying body parts for SIP, please write text. >>>>> I think the body-handling draft already does it, although maybe I'm >>>> reading into it what I want to and not what it really says. >>>>> You asked, so this email is long. This is what I think is the way >>>>> to do >>>> it... >>>>> :Executive summary: basically we let C-D of "render" mean render to >>>>> the >>>> specific context of the message; we mandate future extensions which are >>>> not for that context disambiguate themselves, by not using a C-D of >>>> "render" or the other ones already in use, and that they can't use a >>>> C-T >>>> already used today either. (and that includes changing geoloc's C-T >>>> immediately) >>>>> :The Details: >>>>> >>>>> Definitions: >>>>> User-context = the specific context defined by the method name, and >>>> package if it's a method which has a package sub-context >>>> (SUB/NOT/PUB/INF). The target user is the user-context's >>>> app-layer. For >>>> example an "application/dtmf-relay" body-part would want to be >>>> targeted to >>>> the user-context defined by the "dtmf" package in an INFO. >>>>> Method-only-context = the context defined by the method name alone, >>>> ignoring any package. The target is the specific message >>>> processor/state- >>>> machine for that method, but for any/all packages/sub-contexts. For >>>> example the Event and Subscription-State headers are for this >>>> context in a >>>> SUBSCRIBE. For methods that don't have a package >>>> (INV/UPD/ACK/PRA/MSG), >>>> the method-only-context and user-context are the same. So the >>>> "session" >>>> and "early-session" C-D's are really for a user-context, but it's >>>> the same >>>> context as method-only-context. I don't know of any bodies which are >>>> currently only for a method-only-context.(?) Nor am I convinced we >>>> even >>>> need this context to be defined separately. >>>>> All-messages-context = the context is just the SIP message processing >>>> rules common to all messages. The target is the SIP message processor >>>> common to all SIP messages. The mandatory SIP headers (Call-ID, To, >>>> From, >>>> etc.) are examples of things targeted for this context. An AIB, >>>> geoloc, >>>> and maybe sipfrag(?) bodies are targets for this context. >>>>> Note on above: If you think of this as a layered model with an API, or >>>> better yet a class object model - basically the all-messages-context is >>>> for things needing to be handled/extracted in the base SIP message >>>> class, >>>> the method-only-context is for stuff to be handled in a derived >>>> class for >>>> a given method, and the user-context is for stuff to be handled by a >>>> derived class from that for a given package, which may just be the same >>>> class for some methods (INV/UPD/etc.). >>>>> Rules: >>>>> 1) Any body-part with a C-D of "render", means to render it to the >>>> "user" - not the human user, but the *user-context*. This lets us get >>>> backwards-compatibility for free, because a C-D of "render" is implicit >>>> and what current SIP messages actually have and UA's expect. That C-D >>>> becomes the "default" so to speak, which it already is today. >>>>> 2) Any package (event of info) can define additional C-D's that belong >>>> to it, just like they can define C-T's that they support. I am not >>>> entirely thrilled with letting packages define C-D's, but some >>>> already do >>>> ("signal", for example). If we'd rather just grandfather those and >>>> say no >>>> more that's fine. ISTM that a package could get that semantic purpose >>>> information from within the boy content itself (in XML, for example) >>>> if it >>>> really needs such. Methods already do too, like "session" or "early- >>>> session". If we decide packages can have their own C-D's, then we need >>>> additional rules not to step on body parts for others, but I'll skip >>>> that >>>> for now. >>>>> 3) Any body-part that is NOT for the user-context, for example a >>>>> geoloc, >>>> needs to disambiguate itself from the rest, by using a C-D other than >>>> "render" or the ones already defined. If it needs a sub-context other >>>> than the all-messages-context, or is in fact tied to a SIP header, >>>> then it >>>> needs to use CID, and a C-D of "by-reference". I would in fact suggest >>>> that all future extensions which need to be for something other than >>>> the >>>> user-context MUST have a referencing SIP header and use a CID and a >>>> C-D of >>>> by-reference. >>>>> 4) Furthermore, any future extension which is not for the user-context >>>> MUST NOT use any C-T currently defined in any RFC or WG draft for SIP, >>>> including already defined event-packages. That sounds harsh, but >>>> that's >>>> what we need to do to get a very high degree of >>>> backwards-compatibility I >>>> think. So this means you can't do a geoloc-type thing using >>>> "text/plain", >>>> for example, or really even "application/pidf+xml", which is what >>>> geoloc >>>> currently uses in its draft. And body-handling or some other draft >>>> should >>>> list all such C-T's, so future extensions can know the list to >>>> avoid. And >>>> if we want to just say no C-T currently define by IANA period, I'm fine >>>> with that too. Note this does NOT prevent future SIP RFCs from >>>> using a C- >>>> T defined by such an extension as geoloc. For example, if geoloc uses >>>> "application/foobar", then a future Event-package could use that too; >>>> because that future event package would normatively reference body- >>>> handling. >>>>> 5) IF we need an option tag (and I do NOT think we do), then we should >>>> create one and only one tag right now, for the body-handling draft's >>>> logic. Future extensions which are not for the user-context would then >>>> NOT need more option tags simply due to body-handling issues, but >>>> can use >>>> that generic one. I would also put in some extreme language into the >>>> body-handling option tag about what it means to put such a thing in a >>>> Require header, to dissuade people from doing that. >>>>> 6) If there are some already defined things which do not follow the >>>> above rules, we either (a) grandfather them into body-handling right >>>> now, >>>> or if they're not really in use, then either (b) deprecate or (c) >>>> replace >>>> them. (and I would vote for (b), fwiw) >>>>> -hadriel >> > > > ------------------------------------------------------------------------ > > _______________________________________________ > Sip mailing list https://www.ietf.org/mailman/listinfo/sip > This list is for NEW development of the core SIP 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 Jan 13 07:02:09 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8C57F28C0FC; Tue, 13 Jan 2009 07:02:09 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9BCED3A63D3 for ; Tue, 13 Jan 2009 07:02:07 -0800 (PST) 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 JKQgx76+Xtxg for ; Tue, 13 Jan 2009 07:02:06 -0800 (PST) Received: from gs19.inmotionhosting.com (gs19.inmotionhosting.com [205.134.252.251]) by core3.amsl.com (Postfix) with ESMTP id 236EF3A6904 for ; Tue, 13 Jan 2009 07:02:06 -0800 (PST) Received: from [24.61.135.43] (port=62629 helo=[192.168.15.105]) by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1LMklk-0003tI-Vf; Tue, 13 Jan 2009 07:01:29 -0800 Message-Id: <96C02542-CBD1-4023-B4F4-402DE59415F6@standardstrack.com> From: Eric Burger To: Paul Kyzivat In-Reply-To: <496CA535.8030200@cisco.com> Mime-Version: 1.0 (Apple Message framework v930.3) Date: Tue, 13 Jan 2009 10:01:46 -0500 References: <49305D82.7000907@cisco.com> <49347B88.3010801@softarmor.com> <4934F9C1.5070400@ericsson.com> <3C59889E-BE62-4881-9CAA-E1A12355EF50@standardstrack.com> <49476F22.7050603@ericsson.com> <49660B0D.5050207@ericsson.com> <496CA535.8030200@cisco.com> X-Mailer: Apple Mail (2.930.3) 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 List , Gonzalo Camarillo Subject: Re: [Sip] Body handling - Contexts WAS (Re: multiple bodies in any SIP message) X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1505957913==" Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org --===============1505957913== Content-Type: multipart/signed; boundary=Apple-Mail-78-148636206; micalg=sha1; protocol="application/pkcs7-signature" --Apple-Mail-78-148636206 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit On Jan 13, 2009, at 9:29 AM, Paul Kyzivat wrote: > Eric Burger wrote: >> So I went with C-D for the last round of INFO. > > I still haven't found time to review the latest. But you have now > increased my motivation to do so! > >> This isn't e-mail, so matching the C-D with the method, on a per- >> method basis, works in all cases, as the C-D is a unique (because >> of the IANA registry) and the method defines it. Thus no one will >> use INFO's C-D for something else (unless they want to get slapped >> silly). > > Well... > > (Here it comes: Paul's exception to the rule) > > I might find some reason to put part or all of an INFO message in a > sipfrag, and then send it to someone in a non-INFO message. (I > haven't worked out a real use case yet.) So, will I get slapped > silly for that? I think the context for interpreting that is > determined by the container it is in, so it shouldn't be a problem. Fair enough. In fact, using C-D as the tag makes your scenario work! > Thanks, > Paul > >> On Jan 8, 2009, at 9:17 AM, Gonzalo Camarillo wrote: >>> Hi, >>> >>> by now, most people should be back from their vacation. I will >>> wait a few days for further comments and, if everybody is happy >>> with the current draft and no one proposes new text, we will go >>> ahead request its publication. >>> >>> Thanks, >>> >>> Gonzalo >>> >>> Hadriel Kaplan wrote: >>>> I think that's really a question for the others (Paul, Dean, >>>> Eric). I interpreted body-handling to address the issue already, >>>> but maybe not the backward compatibility issue. >>>> Also, section 8.1. talks about the context being defined by the >>>> method, C-D and C-T. It should probably mention that the Event >>>> package for SUB/NOT/PUB and soon the Info-Event package narrows >>>> the context further. And I'm not sure that C-T has anything to >>>> do with defining a context. >>>> -hadriel >>>>> -----Original Message----- >>>>> From: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com] >>>>> Sent: Tuesday, December 16, 2008 4:05 AM >>>>> To: Hadriel Kaplan >>>>> Cc: Eric Burger; SIP List >>>>> Subject: Body handling - Contexts WAS (Re: [Sip] multiple bodies >>>>> in any >>>>> SIP message) >>>>> >>>>> Hi Hadriel, >>>>> >>>>> > I think the body-handling draft already does it, although >>>>> maybe I'm >>>>> > reading into it what I want to and not what it really says. >>>>> >>>>> the draft already talks about contexts: >>>>> >>>>> http://tools.ietf.org/html/draft-ietf-sip-body-handling-05#section-8.1 >>>>> >>>>> I would like to agree on a concrete way forward. Do you think we >>>>> should >>>>> add something to the body handling draft? Maybe expand the >>>>> information >>>>> on contexts? Maybe provide guidelines for extension developers >>>>> so that >>>>> they take them into account when defining new extensions? >>>>> >>>>> Thanks, >>>>> >>>>> Gonzalo >>>>> >>>>> >>>>> Hadriel Kaplan wrote: >>>>>> [note: changing the thread to be consistent] >>>>>> >>>>>>> -----Original Message----- >>>>>>> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On >>>>>>> Behalf Of >>>>> Eric >>>>>>> Burger >>>>>>> Sent: Sunday, December 07, 2008 10:37 AM >>>>>>> Everyone seems to think there needs to be a generic way of >>>>>>> identifying >>>>>>> body bits. >>>>>>> I do not see an obvious, generic way of doing this. >>>>>>> Thus for those out there who think there is a generic way of >>>>>>> identifying body parts for SIP, please write text. >>>>>> I think the body-handling draft already does it, although maybe >>>>>> I'm >>>>> reading into it what I want to and not what it really says. >>>>>> You asked, so this email is long. This is what I think is the >>>>>> way to do >>>>> it... >>>>>> :Executive summary: basically we let C-D of "render" mean >>>>>> render to the >>>>> specific context of the message; we mandate future extensions >>>>> which are >>>>> not for that context disambiguate themselves, by not using a C-D >>>>> of >>>>> "render" or the other ones already in use, and that they can't >>>>> use a C-T >>>>> already used today either. (and that includes changing geoloc's >>>>> C-T >>>>> immediately) >>>>>> :The Details: >>>>>> >>>>>> Definitions: >>>>>> User-context = the specific context defined by the method name, >>>>>> and >>>>> package if it's a method which has a package sub-context >>>>> (SUB/NOT/PUB/INF). The target user is the user-context's app- >>>>> layer. For >>>>> example an "application/dtmf-relay" body-part would want to be >>>>> targeted to >>>>> the user-context defined by the "dtmf" package in an INFO. >>>>>> Method-only-context = the context defined by the method name >>>>>> alone, >>>>> ignoring any package. The target is the specific message >>>>> processor/state- >>>>> machine for that method, but for any/all packages/sub-contexts. >>>>> For >>>>> example the Event and Subscription-State headers are for this >>>>> context in a >>>>> SUBSCRIBE. For methods that don't have a package (INV/UPD/ACK/ >>>>> PRA/MSG), >>>>> the method-only-context and user-context are the same. So the >>>>> "session" >>>>> and "early-session" C-D's are really for a user-context, but >>>>> it's the same >>>>> context as method-only-context. I don't know of any bodies >>>>> which are >>>>> currently only for a method-only-context.(?) Nor am I convinced >>>>> we even >>>>> need this context to be defined separately. >>>>>> All-messages-context = the context is just the SIP message >>>>>> processing >>>>> rules common to all messages. The target is the SIP message >>>>> processor >>>>> common to all SIP messages. The mandatory SIP headers (Call-ID, >>>>> To, From, >>>>> etc.) are examples of things targeted for this context. An AIB, >>>>> geoloc, >>>>> and maybe sipfrag(?) bodies are targets for this context. >>>>>> Note on above: If you think of this as a layered model with an >>>>>> API, or >>>>> better yet a class object model - basically the all-messages- >>>>> context is >>>>> for things needing to be handled/extracted in the base SIP >>>>> message class, >>>>> the method-only-context is for stuff to be handled in a derived >>>>> class for >>>>> a given method, and the user-context is for stuff to be handled >>>>> by a >>>>> derived class from that for a given package, which may just be >>>>> the same >>>>> class for some methods (INV/UPD/etc.). >>>>>> Rules: >>>>>> 1) Any body-part with a C-D of "render", means to render it to >>>>>> the >>>>> "user" - not the human user, but the *user-context*. This lets >>>>> us get >>>>> backwards-compatibility for free, because a C-D of "render" is >>>>> implicit >>>>> and what current SIP messages actually have and UA's expect. >>>>> That C-D >>>>> becomes the "default" so to speak, which it already is today. >>>>>> 2) Any package (event of info) can define additional C-D's that >>>>>> belong >>>>> to it, just like they can define C-T's that they support. I am >>>>> not >>>>> entirely thrilled with letting packages define C-D's, but some >>>>> already do >>>>> ("signal", for example). If we'd rather just grandfather those >>>>> and say no >>>>> more that's fine. ISTM that a package could get that semantic >>>>> purpose >>>>> information from within the boy content itself (in XML, for >>>>> example) if it >>>>> really needs such. Methods already do too, like "session" or >>>>> "early- >>>>> session". If we decide packages can have their own C-D's, then >>>>> we need >>>>> additional rules not to step on body parts for others, but I'll >>>>> skip that >>>>> for now. >>>>>> 3) Any body-part that is NOT for the user-context, for example >>>>>> a geoloc, >>>>> needs to disambiguate itself from the rest, by using a C-D other >>>>> than >>>>> "render" or the ones already defined. If it needs a sub-context >>>>> other >>>>> than the all-messages-context, or is in fact tied to a SIP >>>>> header, then it >>>>> needs to use CID, and a C-D of "by-reference". I would in fact >>>>> suggest >>>>> that all future extensions which need to be for something other >>>>> than the >>>>> user-context MUST have a referencing SIP header and use a CID >>>>> and a C-D of >>>>> by-reference. >>>>>> 4) Furthermore, any future extension which is not for the user- >>>>>> context >>>>> MUST NOT use any C-T currently defined in any RFC or WG draft >>>>> for SIP, >>>>> including already defined event-packages. That sounds harsh, >>>>> but that's >>>>> what we need to do to get a very high degree of backwards- >>>>> compatibility I >>>>> think. So this means you can't do a geoloc-type thing using >>>>> "text/plain", >>>>> for example, or really even "application/pidf+xml", which is >>>>> what geoloc >>>>> currently uses in its draft. And body-handling or some other >>>>> draft should >>>>> list all such C-T's, so future extensions can know the list to >>>>> avoid. And >>>>> if we want to just say no C-T currently define by IANA period, >>>>> I'm fine >>>>> with that too. Note this does NOT prevent future SIP RFCs from >>>>> using a C- >>>>> T defined by such an extension as geoloc. For example, if >>>>> geoloc uses >>>>> "application/foobar", then a future Event-package could use that >>>>> too; >>>>> because that future event package would normatively reference >>>>> body- >>>>> handling. >>>>>> 5) IF we need an option tag (and I do NOT think we do), then we >>>>>> should >>>>> create one and only one tag right now, for the body-handling >>>>> draft's >>>>> logic. Future extensions which are not for the user-context >>>>> would then >>>>> NOT need more option tags simply due to body-handling issues, >>>>> but can use >>>>> that generic one. I would also put in some extreme language >>>>> into the >>>>> body-handling option tag about what it means to put such a thing >>>>> in a >>>>> Require header, to dissuade people from doing that. >>>>>> 6) If there are some already defined things which do not follow >>>>>> the >>>>> above rules, we either (a) grandfather them into body-handling >>>>> right now, >>>>> or if they're not really in use, then either (b) deprecate or >>>>> (c) replace >>>>> them. (and I would vote for (b), fwiw) >>>>>> -hadriel >>> >> ------------------------------------------------------------------------ >> _______________________________________________ >> Sip mailing list https://www.ietf.org/mailman/listinfo/sip >> This list is for NEW development of the core SIP 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-78-148636206 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 9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wOTAxMTMxNTAxNDdaMCMGCSqGSIb3 DQEJBDEWBBTz/FZEUdTGuq4p9CeFQunQ5vGOHjCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2 MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN H2TynzANBgkqhkiG9w0BAQEFAASCAQAH2mdE80G1FLohu2PEzsmCDkaIcABIypf6upIlerqS2Oac ZyvLBu0mNEOD8YXGVnoZeRPi2vunVRMyVkKhnnTdQkXhH0FmgWqC5s3ydr/0HvN6YJ65LHs00yDH Fre1JkmFUKJCIIrQM6Wv8V2fudJyHsek/6gpncbL15UjONyrXeJxNuG33kBbnCeevOUbk3JWzOYM qpCxleSF8t0MFQH6WOUu8qkcFKC3OefmexUA6biEwxhhGHXCq9+XisiW3zmkezSVKLDEtwbf4S2R OgD43+znLKdZ1/zaEeBDV1UBG3CTWInWNt9DesDnf8vxLn1Cu/JyByOSjwADRBzFzczjAAAAAAAA --Apple-Mail-78-148636206-- --===============1505957913== 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 --===============1505957913==-- From sandsfamily@stoneyfields.fsnet.co.uk Tue Jan 13 19:36:52 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 943023A69B9; Tue, 13 Jan 2009 19:36:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -44.883 X-Spam-Level: X-Spam-Status: No, score=-44.883 tagged_above=-999 required=5 tests=[BAYES_99=3.5, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, URIBL_BLACK=20, URIBL_RHS_DOB=1.083, URIBL_SBL=20, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NZZ2hYC0bDVV; Tue, 13 Jan 2009 19:36:51 -0800 (PST) Received: from sv-cablemodem-011.cablenet.net.ar (sv-cablemodem-011.cablenet.net.ar [200.50.174.11]) by core3.amsl.com (Postfix) with SMTP id 96A143A6358; Tue, 13 Jan 2009 19:36:42 -0800 (PST) X-Originating-IP: 160.95.48.57 by smtp.200.50.174.11; Tue, 13 Jan 2009 21:29:29 -0500 Message-ID: Subject: Take a look at the Tag Heuer watches! Date: Tue, 13 Jan 2009 21:36:29 -0500 From: "Candice Purvis" To: "Rachelle Mock" Content-Type: text/plain; Content-Transfer-Encoding: 7bit Dear Rachelle, If you've waited to get your Breitling watch, this is the right time to go for it. http://www.murkpint.com/ From sip-bounces@ietf.org Wed Jan 14 03:40:29 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7028E3A6827; Wed, 14 Jan 2009 03:40:29 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 72DA03A6827 for ; Wed, 14 Jan 2009 03:40:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.076 X-Spam-Level: X-Spam-Status: No, score=-6.076 tagged_above=-999 required=5 tests=[AWL=0.173, BAYES_00=-2.599, HELO_EQ_FR=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 HBKCQdnrhTr3 for ; Wed, 14 Jan 2009 03:40:27 -0800 (PST) Received: from smail6.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5]) by core3.amsl.com (Postfix) with ESMTP id 6A4BA3A63EC for ; Wed, 14 Jan 2009 03:40:26 -0800 (PST) Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n0EBeAF0005674 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Wed, 14 Jan 2009 12:40:10 +0100 Received: from FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com ([135.120.45.41]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Wed, 14 Jan 2009 12:40:10 +0100 From: "DRAGE, Keith (Keith)" To: SIP List Date: Wed, 14 Jan 2009 12:40:09 +0100 Thread-Topic: Informal SIP identity discussions Thread-Index: Acl1nWOPIzSnmw42SX2cwags+0ZCRgAnsH4w Message-ID: <28B7C3AA2A7ABA4A841F11217ABE78D674895BC2@FRMRSSXCHMBSB3.dc-m.alcatel-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 X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84 Subject: [Sip] Informal SIP identity discussions X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org Attached find the rough notes of the last conference call of interested parties on the identity issue. John will be issuing a -02 version of draft-elwell-sip-e2e-identity-important which will represent the current work in progress in defining the issue. regards Keith -----Original Message----- From: Dan Wing [mailto:dwing@cisco.com] Sent: Tuesday, January 13, 2009 4:39 PM To: DRAGE, Keith (Keith) Subject: notes began at 7:40am pacific time * Keith proposes page-by-page review of John Elwell's draft, draft-elwell-sip-e2e-identity-important-01A.txt, which he emailed on January 12. (note draft -01A has not been formally issued) * Dan York asks if we will develop a problem statement. Keith said John's draft will become the problem statement. * Hannes begins discussing the document overall, and is worried the banking scenario has excessive security requirements and we should concentrate on a different scenario with lower security needs. - conclusion: we need to include SIP certficates as a mechanism to provide identity - include return routability check beginning document review at 8am PT: Section 1. We need to better describe 'end to end', and terminology section. Describe how to identify the user using media. Section 2.7, Q: should we discuss problems with converting tel URI to SIP URI. John suggests that the E.164 problem statement draft goes into that detail and we didn't want to repeat it here. Action: John to put out call for input to the requirements section to the interested parties. Action: John to put out -02 version of draft and solicit comments from the wider SIP community. _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.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 Jan 14 07:47:29 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8349E3A6B5C; Wed, 14 Jan 2009 07:47:29 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0691C3A6B5C for ; Wed, 14 Jan 2009 07:47:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.088 X-Spam-Level: X-Spam-Status: No, score=-6.088 tagged_above=-999 required=5 tests=[AWL=0.161, BAYES_00=-2.599, HELO_EQ_FR=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 KBLjSMeCoaQd for ; Wed, 14 Jan 2009 07:47:27 -0800 (PST) Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27]) by core3.amsl.com (Postfix) with ESMTP id 626463A68D6 for ; Wed, 14 Jan 2009 07:47:26 -0800 (PST) Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n0EFl8ZZ014443 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Wed, 14 Jan 2009 16:47:08 +0100 Received: from FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com ([135.120.45.41]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Wed, 14 Jan 2009 16:47:08 +0100 From: "DRAGE, Keith (Keith)" To: SIP List Date: Wed, 14 Jan 2009 16:47:06 +0100 Thread-Topic: Change to IETF RFC and draft rules Thread-Index: Acl2X1pWgOtoe1dIRlCSa8IPgVZBQQ== Message-ID: <28B7C3AA2A7ABA4A841F11217ABE78D674895CFD@FRMRSSXCHMBSB3.dc-m.alcatel-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 X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13 Subject: [Sip] Change to IETF RFC and draft rules X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org Calling all SIP authors and editors: If you are revising an existing internet draft or using significant text from an existing RFC (e.g. to provide a bis version) the the rights the original author granted to IETF for use of that text no longer apply and new rules are in effect for all submitted text. Obviously you can make a decision on text you supplied as to whether the new grant of rights is OK to you or not. However you will need to contact the authors of any other material and ensure that they have also agreed to the text being used under the new rights. It would be appropriate for you to do this now, rather than wait for the submission deadline to find that you have a problem. The relevant RFC covering this is RFC 5378 and the appropriate section is as follows (if you need to consult with your legal people please use RFC 5378 for the discussion and none of the text of this email): 5.3. Rights Granted by Contributors to the IETF Trust To the extent that a Contribution or any portion thereof is protected by copyright or other rights of authorship, the Contributor and each named co-Contributor grant a perpetual, irrevocable, non-exclusive, royalty-free, world-wide, sublicensable right and license to the IETF Trust under all such copyrights and other rights in the Contribution: a. to copy, publish, display, and distribute the Contribution, in whole or in part, b. to prepare translations of the Contribution into languages other than English, in whole or in part, and to copy, publish, display, and distribute such translations or portions thereof, c. to modify or prepare derivative works (in addition to translations) that are based on or incorporate all or part of the Contribution, and to copy, publish, display, and distribute such derivative works, or portions thereof unless explicitly disallowed in the notices contained in a Contribution (in the form specified by the Legend Instructions), and d. to reproduce any trademarks, service marks, or trade names which are included in the Contribution solely in connection with the reproduction, distribution, or publication of the Contribution and derivative works thereof as permitted by this Section 5.3, provided that when reproducing Contributions, trademark and service mark identifiers used in the Contribution, including TM and (R), will be preserved. Essentially when you submit an internet draft, you sign up to this, but you need to ensure that you have the ability to transfer those rights in the first place, which is where this message comes in. You may also find it appropriate to read RFC 5377 as well. Please note that I am not a legal expert, and you may find that if you have questions of interpretation, you will receive a better (and quicker) answer on the main IETF discussion list, rather than from the SIP list or from the SIP WG chairs! 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 Wed Jan 14 08:29:41 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9292D3A68C3; Wed, 14 Jan 2009 08:29:41 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 218B728C1BF for ; Wed, 14 Jan 2009 08:29:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.098 X-Spam-Level: X-Spam-Status: No, score=-6.098 tagged_above=-999 required=5 tests=[AWL=0.151, BAYES_00=-2.599, HELO_EQ_FR=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 rhhIzrGJOy+u for ; Wed, 14 Jan 2009 08:29:38 -0800 (PST) Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id EADC93A6878 for ; Wed, 14 Jan 2009 08:29:36 -0800 (PST) Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n0EGTK1B023002 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Wed, 14 Jan 2009 17:29:20 +0100 Received: from FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com ([135.120.45.41]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Wed, 14 Jan 2009 17:29:20 +0100 From: "DRAGE, Keith (Keith)" To: SIP List Date: Wed, 14 Jan 2009 17:29:18 +0100 Thread-Topic: Change to IETF RFC and draft rules Thread-Index: Acl2X1pWgOtoe1dIRlCSa8IPgVZBQQABZqkA Message-ID: <28B7C3AA2A7ABA4A841F11217ABE78D674895D18@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com> References: <28B7C3AA2A7ABA4A841F11217ABE78D674895CFD@FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com> In-Reply-To: <28B7C3AA2A7ABA4A841F11217ABE78D674895CFD@FRMRSSXCHMBSB3.dc-m.alcatel-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 X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13 Subject: Re: [Sip] Change to IETF RFC and draft rules X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org The advice in the previous mail applies, but there is some ongoing work to provide some flexibility as follows. As we will not know the result of this for 30 days, I strongly suggest you do continue gathering the appropriate rights from text authors: >From: "Ed Juskevicius" >To: "'IETF Discussion'" , , > , , , > >Date: Thu, 8 Jan 2009 16:43:50 -0500 >Cc: 'Trustees' >Subject: [Trustees] ANNOUNCEMENT: The IETF Trustees invite your review and > comments on a proposed Work-Around to the Pre-5378 Problem > >The purpose of this message is twofold: > >1) To summarize the issues that some members of our community > have experienced since the publication of RFC 5378 in November 2008, > and >2) To invite community review and discussion on a potential work-around > being considered by the IETF Trustees. > >Some I-D authors are having difficulty implementing RFC 5378. An >example of the difficulty is as follows: > > - an author wants to include pre-5378 content in a new submission > or contribution to the IETF, but > - s/he is not certain that all of the author(s) of the earlier > material have agreed to license it to the IETF Trust according > to RFC 5378. > >If an I-D author includes pre-5378 material in a new document, then >s/he must represent or warrant that all of the authors who created the >pre-5378 material have granted rights for that material to the IETF Trust. >If s/he cannot make this assertion, then s/he has a problem. > >This situation has halted the progression of some Internet-Drafts and >interrupted the publication of some RFCs. The Trustees of the IETF >Trust are investigating ways to implement a temporary work-around so >that IETF work can continue to progress. A permanent solution to this >"pre-5378 problem" may require an update to RFC 5378, for example new >work by the community to create a 5378-bis document. > >The remainder of this message provides an outline of the temporary >work- around being considered by the Trustees. > >RFC 5378 sections 1.j and 5.3.c provide the IETF Trust with the >authority to develop legend text for authors to use in situations where >they wish to limit the granting of rights to modify and prepare >derivatives of the documents they submit. The Trustees used this >authority in 2008 to develop and adopt the current "Legal Provisions >Relating to IETF Documents" which are posted at: >http://trustee.ietf.org/license-info/. > >The Trustees are now considering the creation of optional new legend >text which could be used by authors experiencing the "pre-5378 problem". > >The new legend text, if implemented, would do the following: > > a. Provide Authors and Contributors with a way to identify (to the > IETF Trust) that their contributions contain material from pre-5378 > documents for which RFC 5378 rights to modify the material outside > the IETF standards process may not have been granted, and > > b. Provide the IETF Trust and the community with a clear indication > of every document containing pre-5378 content and having the > "pre-5378 problem". > >So, how could the creation and use of some new legend text help people >work-around the pre-5378 problem? > >The proposed answer is as follows: > > 1. Anyone having a contribution with the "pre-5378" problem should add > new legend text to the contribution, to clearly flag that it includes > pre-5378 material for which all of the rights needed under RFC 5378 > may not have been granted, and > > 2. The IETF Trust will consider authors and contributors (with the > pre-5378 problem) to have met their RFC 5378 obligations if the > new legend text appears on their documents, and > > 3. Authors and contributors should only resort to adding the new > legend text to their documents (per #1) if they cannot develop > certainty that all of the author(s) of pre-5378 material in > their documents have agreed to license the pre-5378 content to > the IETF Trust according to RFC 5378. > >The proposed wording for the new legend text is now available for your >review and comments in section 6.c.iii of a draft revision to the IETF >Trust's "Legal Provisions Relating to IETF Documents" located at >http://trustee.ietf.org/policyandprocedures.html. > >Please note that the above document also contains new text in section >5.c dealing with "License Limitations". > >If your review and feedback on this proposed work-around is positive, >then the new text may be adopted by the Trustees in early February >2009, and then be published as an official revision to the Legal >Provisions document. If so adopted, Internet-Drafts with pre-5378 >material may advance within the Internet standards process and get >published as RFCs where otherwise qualified to do so. Unless covered >by sections 6.c.i or 6.c.ii, authors of documents in which there is no >pre-5378 material must provide a RFC 5378 license with no limitation on >modifications outside the IETF standards process. > >The IETF Trust will not grant the right to modify or prepare derivative >works of any specific RFC or other IETF Contribution outside the IETF >standards process until RFC 5378 rights pertaining to that document >have been obtained from all authors and after compliance by the IETF >Trust with RFC 5377. The Trustees will establish one or more >mechanisms by which authors of pre-5378 documents may grant RFC 5378 rights. > >The Trustees hereby invite your review, comments and suggestions on >this proposed work-around to the "pre-5378 problem". The period for >this review is 30 days. Microsoft WORD and PDF versions of the >proposed revisions are attached to this message. Copies are also >available on the IETF Trust website under the heading "DRAFT Policy and Procedures Being Developed" at: >http://trustee.ietf.org/policyandprocedures.html > >All feedback submitted before the end of February 7th will be >considered by the Trustees. A decision on whether to move forward with >this proposal will be made and communicated to you before the end of February 15th. > >Please give this your attention. > >Regards and Happy New Year ! > >Ed Juskevicius, on behalf of the IETF Trustees edj.etc@gmail.com > -----Original Message----- > From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On > Behalf Of DRAGE, Keith (Keith) > Sent: Wednesday, January 14, 2009 3:47 PM > To: SIP List > Subject: [Sip] Change to IETF RFC and draft rules > > Calling all SIP authors and editors: > > If you are revising an existing internet draft or using > significant text from an existing RFC (e.g. to provide a bis > version) the the rights the original author granted to IETF > for use of that text no longer apply and new rules are in > effect for all submitted text. > > Obviously you can make a decision on text you supplied as to > whether the new grant of rights is OK to you or not. However > you will need to contact the authors of any other material > and ensure that they have also agreed to the text being used > under the new rights. > > It would be appropriate for you to do this now, rather than > wait for the submission deadline to find that you have a problem. > > The relevant RFC covering this is RFC 5378 and the > appropriate section is as follows (if you need to consult > with your legal people please use RFC 5378 for the discussion > and none of the text of this email): > > 5.3. Rights Granted by Contributors to the IETF Trust > > To the extent that a Contribution or any portion thereof > is protected > by copyright or other rights of authorship, the > Contributor and each > named co-Contributor grant a perpetual, irrevocable, non-exclusive, > royalty-free, world-wide, sublicensable right and license > to the IETF > Trust under all such copyrights and other rights in the > Contribution: > > a. to copy, publish, display, and distribute the Contribution, in > whole or in part, > > b. to prepare translations of the Contribution into languages other > than English, in whole or in part, and to copy, > publish, display, > and distribute such translations or portions thereof, > > c. to modify or prepare derivative works (in addition to > translations) that are based on or incorporate all or > part of the > Contribution, and to copy, publish, display, and distribute such > derivative works, or portions thereof unless explicitly > disallowed > in the notices contained in a Contribution (in the form > specified > by the Legend Instructions), and > > d. to reproduce any trademarks, service marks, or trade names which > are included in the Contribution solely in connection with the > reproduction, distribution, or publication of the > Contribution and > derivative works thereof as permitted by this Section 5.3, > provided that when reproducing Contributions, trademark and > service mark identifiers used in the Contribution, including TM > and (R), will be preserved. > > Essentially when you submit an internet draft, you sign up to > this, but you need to ensure that you have the ability to > transfer those rights in the first place, which is where this > message comes in. > > You may also find it appropriate to read RFC 5377 as well. > > Please note that I am not a legal expert, and you may find > that if you have questions of interpretation, you will > receive a better (and quicker) answer on the main IETF > discussion list, rather than from the SIP list or from the > SIP WG chairs! > > 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 Wed Jan 14 08:34:25 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7625F28C1BB; Wed, 14 Jan 2009 08:34:25 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6862828C1C8 for ; Wed, 14 Jan 2009 08:34:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.439 X-Spam-Level: X-Spam-Status: No, score=-1.439 tagged_above=-999 required=5 tests=[AWL=1.161, 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 rQ1puaKjApVW for ; Wed, 14 Jan 2009 08:34:23 -0800 (PST) Received: from mobismtp.orbit.net.pk (mobismtp.orbit.net.pk [202.125.143.20]) by core3.amsl.com (Postfix) with ESMTP id AECB628C1C7 for ; Wed, 14 Jan 2009 08:34:21 -0800 (PST) Received: from [61.5.141.107] (helo=lhe-smtp-02.mobilink.net.pk) by mobismtp.orbit.net.pk with esmtp (Exim 4.44) id 1LN8fq-0008Ct-OS; Wed, 14 Jan 2009 21:32:58 +0500 Received: from (unknown [10.50.16.20]) by WS-SMTP-02.mobilink.net.pk with smtp id 328e_1ad8c168_e258_11dd_beda_0014221d2d3a; Wed, 14 Jan 2009 21:26:32 +0500 Received: from lhemail.mobilink.net.pk ([10.50.12.13]) by lhe-smtp-02.mobilink.net.pk with Microsoft SMTPSVC(6.0.3790.3959); Wed, 14 Jan 2009 21:37:13 +0500 Content-class: urn:content-classes:message MIME-Version: 1.0 x-mimeole: Produced By Microsoft Exchange V6.5 Date: Wed, 14 Jan 2009 21:37:11 +0500 Message-ID: <4E0B2197827CA5488735B06CA6FE4AAC07B0CECD@lhemail.mobilink.net.pk> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Change to IETF RFC and draft rules Thread-Index: Acl2X1pWgOtoe1dIRlCSa8IPgVZBQQABZqkAAABZFXU= From: "Syed Shams Uddin Ahmad/IT/LHR" To: , X-OriginalArrivalTime: 14 Jan 2009 16:37:13.0296 (UTC) FILETIME=[5A726D00:01C97666] Subject: Re: [Sip] Change to IETF RFC and draft rules X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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 he is right. Shams __________________________________________ Sent from my Mobilink BlackBerry Wireless Handheld ----- Original Message ----- From: sip-bounces@ietf.org To: SIP List Sent: Wed Jan 14 21:29:18 2009 Subject: Re: [Sip] Change to IETF RFC and draft rules The advice in the previous mail applies, but there is some ongoing work to provide some flexibility as follows. As we will not know the result of this for 30 days, I strongly suggest you do continue gathering the appropriate rights from text authors: >From: "Ed Juskevicius" >To: "'IETF Discussion'" , , > , , , > >Date: Thu, 8 Jan 2009 16:43:50 -0500 >Cc: 'Trustees' >Subject: [Trustees] ANNOUNCEMENT: The IETF Trustees invite your review and > comments on a proposed Work-Around to the Pre-5378 Problem > >The purpose of this message is twofold: > >1) To summarize the issues that some members of our community > have experienced since the publication of RFC 5378 in November 2008, > and >2) To invite community review and discussion on a potential work-around > being considered by the IETF Trustees. > >Some I-D authors are having difficulty implementing RFC 5378. An >example of the difficulty is as follows: > > - an author wants to include pre-5378 content in a new submission > or contribution to the IETF, but > - s/he is not certain that all of the author(s) of the earlier > material have agreed to license it to the IETF Trust according > to RFC 5378. > >If an I-D author includes pre-5378 material in a new document, then >s/he must represent or warrant that all of the authors who created the >pre-5378 material have granted rights for that material to the IETF Trust. >If s/he cannot make this assertion, then s/he has a problem. > >This situation has halted the progression of some Internet-Drafts and >interrupted the publication of some RFCs. The Trustees of the IETF >Trust are investigating ways to implement a temporary work-around so >that IETF work can continue to progress. A permanent solution to this >"pre-5378 problem" may require an update to RFC 5378, for example new >work by the community to create a 5378-bis document. > >The remainder of this message provides an outline of the temporary >work- around being considered by the Trustees. > >RFC 5378 sections 1.j and 5.3.c provide the IETF Trust with the >authority to develop legend text for authors to use in situations where >they wish to limit the granting of rights to modify and prepare >derivatives of the documents they submit. The Trustees used this >authority in 2008 to develop and adopt the current "Legal Provisions >Relating to IETF Documents" which are posted at: >http://trustee.ietf.org/license-info/. > >The Trustees are now considering the creation of optional new legend >text which could be used by authors experiencing the "pre-5378 problem". > >The new legend text, if implemented, would do the following: > > a. Provide Authors and Contributors with a way to identify (to the > IETF Trust) that their contributions contain material from pre-5378 > documents for which RFC 5378 rights to modify the material outside > the IETF standards process may not have been granted, and > > b. Provide the IETF Trust and the community with a clear indication > of every document containing pre-5378 content and having the > "pre-5378 problem". > >So, how could the creation and use of some new legend text help people >work-around the pre-5378 problem? > >The proposed answer is as follows: > > 1. Anyone having a contribution with the "pre-5378" problem should add > new legend text to the contribution, to clearly flag that it includes > pre-5378 material for which all of the rights needed under RFC 5378 > may not have been granted, and > > 2. The IETF Trust will consider authors and contributors (with the > pre-5378 problem) to have met their RFC 5378 obligations if the > new legend text appears on their documents, and > > 3. Authors and contributors should only resort to adding the new > legend text to their documents (per #1) if they cannot develop > certainty that all of the author(s) of pre-5378 material in > their documents have agreed to license the pre-5378 content to > the IETF Trust according to RFC 5378. > >The proposed wording for the new legend text is now available for your >review and comments in section 6.c.iii of a draft revision to the IETF >Trust's "Legal Provisions Relating to IETF Documents" located at >http://trustee.ietf.org/policyandprocedures.html. > >Please note that the above document also contains new text in section >5.c dealing with "License Limitations". > >If your review and feedback on this proposed work-around is positive, >then the new text may be adopted by the Trustees in early February >2009, and then be published as an official revision to the Legal >Provisions document. If so adopted, Internet-Drafts with pre-5378 >material may advance within the Internet standards process and get >published as RFCs where otherwise qualified to do so. Unless covered >by sections 6.c.i or 6.c.ii, authors of documents in which there is no >pre-5378 material must provide a RFC 5378 license with no limitation on >modifications outside the IETF standards process. > >The IETF Trust will not grant the right to modify or prepare derivative >works of any specific RFC or other IETF Contribution outside the IETF >standards process until RFC 5378 rights pertaining to that document >have been obtained from all authors and after compliance by the IETF >Trust with RFC 5377. The Trustees will establish one or more >mechanisms by which authors of pre-5378 documents may grant RFC 5378 rights. > >The Trustees hereby invite your review, comments and suggestions on >this proposed work-around to the "pre-5378 problem". The period for >this review is 30 days. Microsoft WORD and PDF versions of the >proposed revisions are attached to this message. Copies are also >available on the IETF Trust website under the heading "DRAFT Policy and Procedures Being Developed" at: >http://trustee.ietf.org/policyandprocedures.html > >All feedback submitted before the end of February 7th will be >considered by the Trustees. A decision on whether to move forward with >this proposal will be made and communicated to you before the end of February 15th. > >Please give this your attention. > >Regards and Happy New Year ! > >Ed Juskevicius, on behalf of the IETF Trustees edj.etc@gmail.com > -----Original Message----- > From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On > Behalf Of DRAGE, Keith (Keith) > Sent: Wednesday, January 14, 2009 3:47 PM > To: SIP List > Subject: [Sip] Change to IETF RFC and draft rules > > Calling all SIP authors and editors: > > If you are revising an existing internet draft or using > significant text from an existing RFC (e.g. to provide a bis > version) the the rights the original author granted to IETF > for use of that text no longer apply and new rules are in > effect for all submitted text. > > Obviously you can make a decision on text you supplied as to > whether the new grant of rights is OK to you or not. However > you will need to contact the authors of any other material > and ensure that they have also agreed to the text being used > under the new rights. > > It would be appropriate for you to do this now, rather than > wait for the submission deadline to find that you have a problem. > > The relevant RFC covering this is RFC 5378 and the > appropriate section is as follows (if you need to consult > with your legal people please use RFC 5378 for the discussion > and none of the text of this email): > > 5.3. Rights Granted by Contributors to the IETF Trust > > To the extent that a Contribution or any portion thereof > is protected > by copyright or other rights of authorship, the > Contributor and each > named co-Contributor grant a perpetual, irrevocable, non-exclusive, > royalty-free, world-wide, sublicensable right and license > to the IETF > Trust under all such copyrights and other rights in the > Contribution: > > a. to copy, publish, display, and distribute the Contribution, in > whole or in part, > > b. to prepare translations of the Contribution into languages other > than English, in whole or in part, and to copy, > publish, display, > and distribute such translations or portions thereof, > > c. to modify or prepare derivative works (in addition to > translations) that are based on or incorporate all or > part of the > Contribution, and to copy, publish, display, and distribute such > derivative works, or portions thereof unless explicitly > disallowed > in the notices contained in a Contribution (in the form > specified > by the Legend Instructions), and > > d. to reproduce any trademarks, service marks, or trade names which > are included in the Contribution solely in connection with the > reproduction, distribution, or publication of the > Contribution and > derivative works thereof as permitted by this Section 5.3, > provided that when reproducing Contributions, trademark and > service mark identifiers used in the Contribution, including TM > and (R), will be preserved. > > Essentially when you submit an internet draft, you sign up to > this, but you need to ensure that you have the ability to > transfer those rights in the first place, which is where this > message comes in. > > You may also find it appropriate to read RFC 5377 as well. > > Please note that I am not a legal expert, and you may find > that if you have questions of interpretation, you will > receive a better (and quicker) answer on the main IETF > discussion list, rather than from the SIP list or from the > SIP WG chairs! > > 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 This email has been scanned virus free @ Mobilink _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip From milliganx@aml.lynden.com Wed Jan 14 10:39:47 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E0EE93A6A5B for ; Wed, 14 Jan 2009 10:39:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.967 X-Spam-Level: X-Spam-Status: No, score=-14.967 tagged_above=-999 required=5 tests=[BAYES_99=3.5, GB_I_LETTER=-2, HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_HEXIP=2.204, HELO_EQ_DK=1.009, HELO_EQ_DSL=1.129, HELO_EQ_DYNAMIC=1.144, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_UNI=0.591, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_SC_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zRFMOXBo+zHW for ; Wed, 14 Jan 2009 10:39:47 -0800 (PST) Received: from 0x573beb4a.banqu1.dynamic.dsl.tele.dk (0x573beb4a.banqu1.dynamic.dsl.tele.dk [87.59.235.74]) by core3.amsl.com (Postfix) with SMTP id E79293A6A15 for ; Wed, 14 Jan 2009 10:39:45 -0800 (PST) To: Subject: News from Microsoft From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090114183945.E79293A6A15@core3.amsl.com> Date: Wed, 14 Jan 2009 10:39:45 -0800 (PST)
About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

c2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 18400
From sip-bounces@ietf.org Wed Jan 14 12:06:59 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8DCF328C1FF; Wed, 14 Jan 2009 12:06:59 -0800 (PST) X-Original-To: sip@ietf.org Delivered-To: sip@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id 4A25728C1D4; Wed, 14 Jan 2009 12:06:58 -0800 (PST) X-idtracker: yes From: The IESG To: IETF-Announce Message-Id: <20090114200658.4A25728C1D4@core3.amsl.com> Date: Wed, 14 Jan 2009 12:06:58 -0800 (PST) Cc: sip mailing list , sip chair , Internet Architecture Board , RFC Editor Subject: [Sip] Protocol Action: 'The use of the SIPS URI Scheme in the Session Initiation Protocol (SIP)' to Proposed Standard X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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 approved the following document: - 'The use of the SIPS URI Scheme in the Session Initiation Protocol (SIP) ' as a Proposed Standard This document is the product of the Session Initiation Protocol Working Group. The IESG contact persons are Cullen Jennings and Jon Peterson. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sip-sips-09.txt Technical Summary: This document updates RFC 3261 to provide clarifications and guidelines concerning the use of the SIPS URI scheme in the Session Initiation Protocol (SIP). This document also provides a discussion of possible future steps in specification. The SIPS URI scheme was originally documented in RFC 3261, but experience has shown that the specification therein is incomplete, and that at least one use case that increased the complexity of the specification (the "last hop exception") can be eliminated. Several possible error conditions relating to mismatch of sips vs. sip on sending and receiving ends exist. This documents adds new SIP error codes to provide for the detection and correction of these error conditions. Working Group Summary: There were several topics of significance that are worth noting. The foremost is the deprecation of the "last hop exception" from RFC 3261. This exception allowed a proxy/registrar supporting SIPS to relay requests received using SIPS on to user agent servers that did not indicate support for SIPS. This increases the complexity of implementations and weakens the end-to-end assurance of signaling security provided by SIPS. After extensive debate, the working group resolved to eliminate this exception and make SIPS fully end-to-end. Doing so required extensive discussion and annotation on what "end to end" means in the context of gateways to non-SIP protocols. Detection and correction of error conditions resulting where a UAC has specified a SIPS request and the terminating UAS has not registered a SIP contact, or where the UAC has specified a SIP request and the terminating UAS has registered only a SIP contact was another problem requiring extensive discussion. The "obvious" approach of using 400 class responses created problems when interacting with forking proxies. The WG concluded on using two new 300-class SIP response codes to enable request resolution in these scenarios. During the process of developing this specification, the working group began to converge on a new process for incrementally updating RFC 3261. As a precursor to this process, this specification contains an appendix that provides explicit in-context changes to RFC 3261 as required by this specification. The intent here is to reduce the complexity of discussions at interoperability events. Document Quality There are several notable implementations of the specification at varying levels of maturity. The SIPIt interop events have included SIPS for some time, and the changes in this specification were in-part driven by experiences at those interop events. The document' Acknowledgements section cites numerous active participants for providing detailed review. _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip From dressner@louisdressner.com Wed Jan 14 13:27:56 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3970F3A6822; Wed, 14 Jan 2009 13:27:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -82.601 X-Spam-Level: X-Spam-Status: No, score=-82.601 tagged_above=-999 required=5 tests=[BAYES_60=1, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR2=4.395, HOST_EQ_STATIC=1.172, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, TVD_RCVD_IP=1.931, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GQcBI30KxjP0; Wed, 14 Jan 2009 13:27:55 -0800 (PST) Received: from 210-213-36-107.static.asianet.co.th (210-213-36-107.static.asianet.co.th [210.213.36.107]) by core3.amsl.com (Postfix) with SMTP id 5600E3A6AAF; Wed, 14 Jan 2009 13:27:37 -0800 (PST) X-Originating-IP: 240.135.97.27 by smtp.210.213.36.107; Wed, 14 Jan 2009 21:20:22 +0100 Message-ID: Subject: Omega cheaper than you could imagine! Date: Wed, 14 Jan 2009 15:27:22 -0500 From: "Doug Knowles" To: "Frank Bergman" Content-Type: text/plain; Content-Transfer-Encoding: 7bit Dear Frank, I had never seen such beautiful and greatly-performing watches like the ones I found online at http://alexanderhxj.narod.ru From orcia@agora.pl Thu Jan 15 04:52:12 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3FBE528C187 for ; Thu, 15 Jan 2009 04:52:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.676 X-Spam-Level: X-Spam-Status: No, score=-6.676 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, GB_I_LETTER=-2, HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_BR=0.955, HELO_EQ_DSL=1.129, HELO_EQ_TELESP=1.245, HOST_EQ_BR=1.295, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, SARE_RECV_SPAM_DOMN02=1.666, SARE_UNI=0.591, TVD_RCVD_IP=1.931, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4AFokWdjG3he for ; Thu, 15 Jan 2009 04:52:11 -0800 (PST) Received: from 189-46-69-220.dsl.telesp.net.br (189-46-231-42.dsl.telesp.net.br [189.46.231.42]) by core3.amsl.com (Postfix) with SMTP id 818C928C15D for ; Thu, 15 Jan 2009 04:52:10 -0800 (PST) To: Subject: News from Microsoft From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090115125210.818C928C15D@core3.amsl.com> Date: Thu, 15 Jan 2009 04:52:10 -0800 (PST)
About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

c2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 78908
From sip-bounces@ietf.org Thu Jan 15 16:08:39 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F0A103A685E; Thu, 15 Jan 2009 16:08:38 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 93BA63A685E; Thu, 15 Jan 2009 16:08:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.974 X-Spam-Level: X-Spam-Status: No, score=-2.974 tagged_above=-999 required=5 tests=[AWL=-0.374, 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 YPatM2GMa6Q2; Thu, 15 Jan 2009 16:08:36 -0800 (PST) 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 2C5D43A67FC; Thu, 15 Jan 2009 16:08:35 -0800 (PST) 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.3) with ESMTP id n0G08JKt032896 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Jan 2009 18:08:19 -0600 (CST) (envelope-from adam@nostrum.com) Message-ID: <496FCFF3.2090607@nostrum.com> Date: Thu, 15 Jan 2009 18:08:19 -0600 From: Adam Roach User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: RAI Area , SIP WG , sipping WG , "'simple@ietf.org'" , GEOPRIV Working Group Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism) X-Virus-Scanned: ClamAV 0.94.2/8870/Thu Jan 15 14:57:00 2009 on shaman.nostrum.com X-Virus-Status: Clean Subject: [Sip] RFC 5378 (IPR Rights Policy) and RFC 3265 X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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 an IPR lawyer, so I don't pretend to understand the various issues surrounding the RFC 5378 brouhaha. However, it has been brought to my attention that my position as author of RFC 3265 may necessitate some action on my part, since it contains text intended to be incorporated into other documents (section 4.4 and its subsections). To remove ambiguity, I am using this email to make a public statement regarding any rights I may have in RFC 3265 as they relate to the IETF's intellectual property policies: As the author of RFC 3265, I hereby grant all Necessary Rights in that document that I may legally grant to the IETF Trust. For the purpose of this statement, the term "Necessary Rights" is defined as the rights enumerated in section 5.3 of RFC 5378. In the interest of full disclosure: I developed RFC 3265 as an employee of Ericsson Inc. and, later, dynamicsoft, Inc. Subsequently, Cisco Systems, Inc. acquired all or substantially all of dynamicsoft's assets. I cannot speak on behalf of either organization regarding their position on what rights, if any, they believe they retain in RFC 3265. /Adam Roach _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip From document@chemtradeasia.com Thu Jan 15 17:58:23 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 75CC23A63EC; Thu, 15 Jan 2009 17:58:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -82.461 X-Spam-Level: X-Spam-Status: No, score=-82.461 tagged_above=-999 required=5 tests=[BAYES_60=1, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_DHCP=1.398, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_CPE=0.5, HOST_EQ_CPE=0.979, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xz-oQUkdT0Jk; Thu, 15 Jan 2009 17:58:22 -0800 (PST) Received: from cpe-24-28-182-29.elp.res.rr.com (cpe-24-28-182-29.elp.res.rr.com [24.28.182.29]) by core3.amsl.com (Postfix) with SMTP id 5C7413A67FC; Thu, 15 Jan 2009 17:58:00 -0800 (PST) X-Originating-IP: 232.90.150.132 by smtp.24.28.182.29; Thu, 15 Jan 2009 20:54:12 -0500 Message-ID: Subject: Bvlgari watch models from 2009! Date: Thu, 15 Jan 2009 21:01:12 -0500 From: "Gina Woody" To: "Joseph Bowen" Content-Type: text/plain; Content-Transfer-Encoding: 7bit Dear Joseph, How about buying yourself a two Vacheron Constantin watches the same day? It's not impossible, mostly when you can get them for a couple hundred bucks http://richardsonrgl.narod.ru Take advantage of our christmas specials and get yourself Vacheron Constantin watch that you've always wanted! http://richardsonrgl.narod.ru Our Vacheron Constantin watches have perfect weight and feel same as orginal. Sincerely, Mr Bowen From sip-bounces@ietf.org Fri Jan 16 01:41:27 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D7F7C3A6851; Fri, 16 Jan 2009 01:41:27 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 10F7C3A6851 for ; Fri, 16 Jan 2009 01:41:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.091 X-Spam-Level: X-Spam-Status: No, score=-6.091 tagged_above=-999 required=5 tests=[AWL=0.158, 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 UrFnnJGxN9K3 for ; Fri, 16 Jan 2009 01:41:25 -0800 (PST) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 05B403A677C for ; Fri, 16 Jan 2009 01:41:24 -0800 (PST) Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 64CDE20E88; Fri, 16 Jan 2009 10:41:08 +0100 (CET) X-AuditID: c1b4fb3c-ac75bbb00000304c-1a-497056344806 Received: from esealmw126.eemea.ericsson.se (unknown [153.88.253.125]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 4D69720D5C; Fri, 16 Jan 2009 10:41:08 +0100 (CET) Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 16 Jan 2009 10:41:07 +0100 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 16 Jan 2009 10:41:07 +0100 Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id D0A0427DB; Fri, 16 Jan 2009 11:41:07 +0200 (EET) Received: from localhost.localdomain (localhost [IPv6:::1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 9C9B44DC94; Fri, 16 Jan 2009 11:41:07 +0200 (EET) Message-ID: <49705633.20107@ericsson.com> Date: Fri, 16 Jan 2009 11:41:07 +0200 From: salvatore loreto User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Dean Willis References: <1222413851.8449.15.camel@little.research.nokia.com> <91B7DF7A-8076-4589-8464-1422FCA1E44E@softarmor.com> In-Reply-To: <91B7DF7A-8076-4589-8464-1422FCA1E44E@softarmor.com> X-OriginalArrivalTime: 16 Jan 2009 09:41:07.0705 (UTC) FILETIME=[8E9F0E90:01C977BE] X-Brightmail-Tracker: AAAAAA== Cc: SIP IETF , Keith Drage , Aki Niemi Subject: Re: [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 List-Unsubscribe: , List-Post: List-Help: List-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 Dean, I am wandering what happened to this draft, almost one year ago the draft was ready to progress to be published, but it didn't and the draft expired in July! Now what is it necessary to do to let this draft progress and finally become an RFC ? /Sal Dean Willis wrote: > > 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 > _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.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 Jan 16 10:18:55 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 05CA63A69A8; Fri, 16 Jan 2009 10:18:55 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A9FA3A69A8 for ; Fri, 16 Jan 2009 10:18:53 -0800 (PST) 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 CqMHFqiPL6EV for ; Fri, 16 Jan 2009 10:18:52 -0800 (PST) Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id A78FE3A6806 for ; Fri, 16 Jan 2009 10:18:52 -0800 (PST) Received: from [192.168.2.102] (cpe-72-181-150-177.tx.res.rr.com [72.181.150.177]) (authenticated bits=0) by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id n0GIIUWG008748 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 16 Jan 2009 12:18:31 -0600 Message-Id: From: Dean Willis To: salvatore loreto In-Reply-To: <49705633.20107@ericsson.com> Mime-Version: 1.0 (Apple Message framework v930.3) Date: Fri, 16 Jan 2009 12:18:24 -0600 References: <1222413851.8449.15.camel@little.research.nokia.com> <91B7DF7A-8076-4589-8464-1422FCA1E44E@softarmor.com> <49705633.20107@ericsson.com> X-Mailer: Apple Mail (2.930.3) Cc: SIP IETF , Keith Drage , Aki Niemi Subject: Re: [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 List-Unsubscribe: , List-Post: List-Help: List-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 Jan 16, 2009, at 3:41 AM, salvatore loreto wrote: > Hi Dean, > > I am wandering what happened to this draft, > almost one year ago the draft was ready to progress to be published, > but it didn't > and the draft expired in July! > Now what is it necessary to do to let this draft progress and > finally become an RFC ? > The author lost motivation. I now have a volunteer tech writer and a regular IETFer working on polishing up the last bits for publication, assuming we don't get derailed by this new rights-assignment thing. We expect to get it done fairly soon. -- 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 k-aida@akebono-brake.co.jp Sat Jan 17 13:57:33 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0DED23A6A9E for ; Sat, 17 Jan 2009 13:57:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.319 X-Spam-Level: X-Spam-Status: No, score=-5.319 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_DHCP=1.398, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_CPE=0.5, HOST_EQ_CPE=0.979, HTML_IMAGE_ONLY_28=1.561, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k5+Hjw80jDD7 for ; Sat, 17 Jan 2009 13:57:31 -0800 (PST) Received: from cpe-173-88-159-6.neo.res.rr.com (cpe-173-88-159-6.neo.res.rr.com [173.88.159.6]) by core3.amsl.com (Postfix) with SMTP id 39DE83A6851 for ; Sat, 17 Jan 2009 13:57:29 -0800 (PST) To: Subject: RE: Q&A Doctor Anita Graves From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090117215730.39DE83A6851@core3.amsl.com> Date: Sat, 17 Jan 2009 13:57:29 -0800 (PST)
January 16, 2009 | "SPECIAL OFFERS"-Pfizer Company!




Contact: Email Administrator, Pfizer World Headquarters 462 E. 42nd Street New York, NY 43185
® 2001-2009 Pfizer Inc. All rights reserved!
Pfizer is a licensee of the TRUSTe Privacy Program!, click here.

» Help  »Advertise  »Terms of Service  »Privacy Policy
From k.kijanka@alstor.com.pl Sun Jan 18 09:32:27 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6D0303A6A14 for ; Sun, 18 Jan 2009 09:32:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -22.968 X-Spam-Level: X-Spam-Status: No, score=-22.968 tagged_above=-999 required=5 tests=[BAYES_99=3.5, GB_I_LETTER=-2, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033, SARE_UNI=0.591, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_SC_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eWRLHZUrbZa0 for ; Sun, 18 Jan 2009 09:32:26 -0800 (PST) Received: from host49-98-static.5-79-b.business.telecomitalia.it (host49-98-static.5-79-b.business.telecomitalia.it [79.5.98.49]) by core3.amsl.com (Postfix) with SMTP id 2F5203A69E9 for ; Sun, 18 Jan 2009 09:32:24 -0800 (PST) To: Subject: Re: Order status 04705 From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090118173225.2F5203A69E9@core3.amsl.com> Date: Sun, 18 Jan 2009 09:32:24 -0800 (PST)
About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

c2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 44120
From cristina.pol@antex.es Sun Jan 18 13:53:53 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E6B13A6B4F; Sun, 18 Jan 2009 13:53:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.05 X-Spam-Level: X-Spam-Status: No, score=-3.05 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, GB_ROLEX=5, HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_BR=0.955, HELO_EQ_DSL=1.129, HOST_EQ_BR=1.295, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, SARE_SPEC_ROLEX=1.666, SARE_SPEC_ROLEX_SEL=2.222, SARE_SUB_PERFECT=0.725, TVD_RCVD_IP=1.931, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_SBL=20, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ykZiYQxLvkMR; Sun, 18 Jan 2009 13:53:52 -0800 (PST) Received: from 201-67-128-148.bnut3703.dsl.brasiltelecom.net.br (201-67-128-148.bnut3703.dsl.brasiltelecom.net.br [201.67.128.148]) by core3.amsl.com (Postfix) with SMTP id 3F3083A67BD; Sun, 18 Jan 2009 13:53:36 -0800 (PST) X-Originating-IP: 228.56.52.145 by smtp.201.67.128.148; Sun, 18 Jan 2009 13:46:25 -0700 Message-ID: Subject: Rep watch is a perfect gift Date: Sun, 18 Jan 2009 15:53:25 -0500 From: "Damion Womack" To: "Cornelia Mooney" Content-Type: text/plain; Content-Transfer-Encoding: 7bit Looking for superior quality rep watches? Then welcome to the newly redesigned Prestige Reps, home of the best reproduction Rolex Sportmodel watches on the whole web! Prestige Reps offers a tremendous selection of Rolex rep timepieces for both men and women, all of them featuring the original manufacturer markings along with a myriad of details that make these watches look so much like the brand new Rolexes that even the experts are having a hard time differentiating them! http://www.murkjoin.com So, come visit Prestige Reps and enjoy not only the most beautiful Rolex Sportmodel rep watches at unbelievable prices, but also get an extra 15% off when you buy two! http://www.murkjoin.com From sip-bounces@ietf.org Sun Jan 18 22:38:40 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BA1F83A6918; Sun, 18 Jan 2009 22:38:40 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 291433A6918 for ; Sun, 18 Jan 2009 22:38:39 -0800 (PST) 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 Pf2KfTATaVZg for ; Sun, 18 Jan 2009 22:38:38 -0800 (PST) Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id 12B693A6803 for ; Sun, 18 Jan 2009 22:38:37 -0800 (PST) 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 n0J6c2SB009885; Mon, 19 Jan 2009 08:38:16 +0200 Received: from vaebh104.NOE.Nokia.com ([10.160.244.30]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 19 Jan 2009 08:37:44 +0200 Received: from mgw-int01.ntc.nokia.com ([172.21.143.96]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Mon, 19 Jan 2009 08:37:39 +0200 Received: from [172.21.43.191] (esdhcp043191.research.nokia.com [172.21.43.191]) by mgw-int01.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id n0J6bbFa025697; Mon, 19 Jan 2009 08:37:38 +0200 From: Aki Niemi To: ext Dean Willis In-Reply-To: References: <1222413851.8449.15.camel@little.research.nokia.com> <91B7DF7A-8076-4589-8464-1422FCA1E44E@softarmor.com> <49705633.20107@ericsson.com> Organization: Nokia Devices R&D Date: Mon, 19 Jan 2009 08:37:38 +0200 Message-Id: <1232347058.28389.117.camel@little.research.nokia.com> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 X-OriginalArrivalTime: 19 Jan 2009 06:37:39.0500 (UTC) FILETIME=[6C7586C0:01C97A00] X-Nokia-AV: Clean Cc: SIP IETF , Keith Drage Subject: Re: [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 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org pe, 2009-01-16 kello 12:18 -0600, ext Dean Willis kirjoitti: > > I am wandering what happened to this draft, > > almost one year ago the draft was ready to progress to be published, > > but it didn't > > and the draft expired in July! > > Now what is it necessary to do to let this draft progress and > > finally become an RFC ? > > > > The author lost motivation. Huh? Admittedly not an entirely incorrect description of the current author's status, however, I was under the impression that we were waiting for document shepherd write-up: http://www.ietf.org/mail-archive/web/sip/current/msg24819.html At least I've not seen nor heard of any fresh issues on this draft that would need my attention. I may not have the cycles to get deeply involved in the WG discussions at the moment, but I have enough time to work this draft past the finish line. Cheers, Aki -- Aki Niemi Maemo Software, Nokia Devices R&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 fengyi@fyqp.com Mon Jan 19 00:57:57 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 74F4B3A69A3; Mon, 19 Jan 2009 00:57:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -23.845 X-Spam-Level: X-Spam-Status: No, score=-23.845 tagged_above=-999 required=5 tests=[BAYES_99=3.5, HELO_EQ_DYNAMIC=1.144, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_SBL=20, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zMYpbAb1Rz9W; Mon, 19 Jan 2009 00:57:56 -0800 (PST) Received: from pcsp251-132.dynamic.supercable.net.ve (pcsp251-132.dynamic.supercable.net.ve [200.35.251.132]) by core3.amsl.com (Postfix) with SMTP id 8F3E928C19E; Mon, 19 Jan 2009 00:57:26 -0800 (PST) X-Originating-IP: 112.6.34.0 by smtp.200.35.251.132; Mon, 19 Jan 2009 04:50:14 -0300 Message-ID: Subject: Take a look at the latest rep watches Date: Mon, 19 Jan 2009 02:57:14 -0500 From: "Cecile Rivera" To: "Sonia Bailey" Content-Type: text/plain; Content-Transfer-Encoding: 7bit Prestige Reps is now bigger and better than ever before! I'm sure you're familiar with this popular rep store, so I'm glad to announce that Prestige Reps has been completely redesigned and now offers not only the highest quality rep watches but also handbags and jewelry! In addition, they're running a 15% special these days when you buy two watches! There's never been a better time to buy a rep watch, especially a Tag Heuer! With prices as low as $200, and the store unmatched privacy assurance guarantee, I'm sure you won't want to wait to get your superior quality Tag Heuer rep! http://www.murkpint.com From k8jh3zee088920@ambrisko.com Mon Jan 19 04:25:44 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8AAFF3A68B3 for ; Mon, 19 Jan 2009 04:25:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -19.942 X-Spam-Level: X-Spam-Status: No, score=-19.942 tagged_above=-999 required=5 tests=[BAYES_99=3.5, GB_I_LETTER=-2, HELO_EQ_DYNAMIC=1.144, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_UNI=0.591, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oAIso-sag19m for ; Mon, 19 Jan 2009 04:25:44 -0800 (PST) Received: from host206-218-dynamic.4-87-r.retail.telecomitalia.it (host206-218-dynamic.4-87-r.retail.telecomitalia.it [87.4.218.206]) by core3.amsl.com (Postfix) with SMTP id B2C063A6821 for ; Mon, 19 Jan 2009 04:25:41 -0800 (PST) To: Subject: News from Microsoft From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090119122542.B2C063A6821@core3.amsl.com> Date: Mon, 19 Jan 2009 04:25:41 -0800 (PST)
About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

c2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 01729
From sip-bounces@ietf.org Mon Jan 19 05:15:59 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4F04E28C1C6; Mon, 19 Jan 2009 05:15:59 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8267128C1C6 for ; Mon, 19 Jan 2009 05:15:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.134 X-Spam-Level: X-Spam-Status: No, score=-6.134 tagged_above=-999 required=5 tests=[AWL=0.115, 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 7RkuhZoIZnwF for ; Mon, 19 Jan 2009 05:15:56 -0800 (PST) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 697E428C137 for ; Mon, 19 Jan 2009 05:15:56 -0800 (PST) Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 65FC620D25; Mon, 19 Jan 2009 14:15:39 +0100 (CET) X-AuditID: c1b4fb3c-af761bb00000304c-68-49747cfb95c9 Received: from esealmw129.eemea.ericsson.se (unknown [153.88.253.125]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 42819206D3; Mon, 19 Jan 2009 14:15:39 +0100 (CET) Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon, 19 Jan 2009 14:15:38 +0100 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon, 19 Jan 2009 14:15:38 +0100 Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 5B20B2328; Mon, 19 Jan 2009 15:15:38 +0200 (EET) Received: from localhost.localdomain (localhost [IPv6:::1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 1D5F34DC91; Mon, 19 Jan 2009 15:15:38 +0200 (EET) Message-ID: <49747CF9.4030407@ericsson.com> Date: Mon, 19 Jan 2009 15:15:37 +0200 From: Salvatore Loreto User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Aki Niemi References: <1222413851.8449.15.camel@little.research.nokia.com> <91B7DF7A-8076-4589-8464-1422FCA1E44E@softarmor.com> <49705633.20107@ericsson.com> <1232347058.28389.117.camel@little.research.nokia.com> In-Reply-To: <1232347058.28389.117.camel@little.research.nokia.com> X-OriginalArrivalTime: 19 Jan 2009 13:15:38.0619 (UTC) FILETIME=[0585ECB0:01C97A38] X-Brightmail-Tracker: AAAAAA== Cc: SIP IETF , Keith Drage , ext Dean Willis Subject: Re: [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 List-Unsubscribe: , List-Post: List-Help: List-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 Aki following the mail discussion, I understood that there weren't any other issues pending and the document was ready for a shepherd write-up and sent to publication. is it just a matter of polishing up or there is also some fresh issue ? if it is just a matter of polishing, it should be better that Aki will do it so we don't get derailed /Sal Aki Niemi wrote: > pe, 2009-01-16 kello 12:18 -0600, ext Dean Willis kirjoitti: > >>> I am wandering what happened to this draft, >>> almost one year ago the draft was ready to progress to be published, >>> but it didn't >>> and the draft expired in July! >>> Now what is it necessary to do to let this draft progress and >>> finally become an RFC ? >>> >>> >> The author lost motivation. >> > > Huh? Admittedly not an entirely incorrect description of the current > author's status, however, I was under the impression that we were > waiting for document shepherd write-up: > > http://www.ietf.org/mail-archive/web/sip/current/msg24819.html > > At least I've not seen nor heard of any fresh issues on this draft that > would need my attention. > > I may not have the cycles to get deeply involved in the WG discussions > at the moment, but I have enough time to work this draft past the finish > line. > > Cheers, > Aki > > _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip From notifit@24hpoker.com Tue Jan 20 01:17:17 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3EBA53A6BB2 for ; Tue, 20 Jan 2009 01:17:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -22.239 X-Spam-Level: X-Spam-Status: No, score=-22.239 tagged_above=-999 required=5 tests=[BAYES_99=3.5, GB_I_LETTER=-2, HELO_EQ_BR=0.955, HOST_EQ_BR=1.295, HTML_IMAGE_ONLY_32=1.778, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tyRjgTUE81yX for ; Tue, 20 Jan 2009 01:17:16 -0800 (PST) Received: from 20151229077.user.veloxzone.com.br (20151229077.user.veloxzone.com.br [201.51.229.77]) by core3.amsl.com (Postfix) with SMTP id 74B553A6B19 for ; Tue, 20 Jan 2009 01:17:09 -0800 (PST) To: Subject: Re: Getting the best results From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090120091713.74B553A6B19@core3.amsl.com> Date: Tue, 20 Jan 2009 01:17:09 -0800 (PST)
We ship Worldwide! To all countries! To all destinations!
Dont see a picture? Click Here!

To unsubscribe from this mailing list, please log in to www.positionthough.com, click on "My Account", click "Update" to edit your registration details and uncheck the "Receive Newsletter?" check box.
Or unsubscribe at http://positionthough.com/faq.php

Privacy Statement | Terms & Conditions | Contact

BRANDKEYWORD Ltd.
Tower Bridge Business Complex. Unit 0, B500. 902 Clements Road. London. SE32 8DG

© 2006-2008 BRANDKEYWORD, Ltd. All Rights Reserved

From sip-bounces@ietf.org Tue Jan 20 04:26:12 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7F65A3A6BCD; Tue, 20 Jan 2009 04:26:12 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 964FF3A6BCD for ; Tue, 20 Jan 2009 04:26:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.784 X-Spam-Level: X-Spam-Status: No, score=-5.784 tagged_above=-999 required=5 tests=[AWL=0.465, 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 MbAwCybWR-uI for ; Tue, 20 Jan 2009 04:26:10 -0800 (PST) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 9872F3A6BC6 for ; Tue, 20 Jan 2009 04:26:10 -0800 (PST) Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 9BDCF20768 for ; Tue, 20 Jan 2009 13:25:53 +0100 (CET) X-AuditID: c1b4fb3c-af761bb00000304c-e8-4975c2d19d6d Received: from esealmw127.eemea.ericsson.se (unknown [153.88.253.125]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 7BCAA20756 for ; Tue, 20 Jan 2009 13:25:53 +0100 (CET) Received: from eseldmw101.eemea.ericsson.se ([136.225.228.103]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 20 Jan 2009 13:25:53 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 20 Jan 2009 13:25:52 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: SIP de-REGISTER: Expires header vs expires parameter i Contact Thread-Index: Acl6+jv/20UE0jY8SkKYLXKhRqw4sg== From: "Gert Olsson" To: X-OriginalArrivalTime: 20 Jan 2009 12:25:53.0071 (UTC) FILETIME=[3C6933F0:01C97AFA] X-Brightmail-Tracker: AAAAAA== Subject: [Sip] SIP de-REGISTER: Expires header vs expires parameter i Contact X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1215920134==" Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org This is a multi-part message in MIME format. --===============1215920134== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C97AFA.3C442D7D" This is a multi-part message in MIME format. ------_=_NextPart_001_01C97AFA.3C442D7D Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, SIP de-registration is performed by sending a REGISTER message with either a Contact header containing an 'expires=3D0' parameter or an Expires header with value 0. My question is: is it FORBIDDEN to have both? Shouldn't any decent server, if it has found 'expires=3D0' in the Contact header (or in all if many), just happily ignore an Expires header? br /GO __________________________________________________________________| Gert Olsson / phone: +46 10 7154604 / e-mail: gert.olsson@ericsson.com Ericsson AB - Business Unit Mobile Platforms, SE-221 83 Lund, Sweden ------_=_NextPart_001_01C97AFA.3C442D7D Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable SIP de-REGISTER: Expires header vs expires parameter i = Contact

Hi,

SIP de-registration is = performed by sending a REGISTER message with either a Contact header = containing an 'expires=3D0' parameter or an Expires header with value 0. = My question is: is it FORBIDDEN to have both? Shouldn't any decent = server, if it has found 'expires=3D0' in the Contact header (or in all = if many), just happily ignore an Expires header?

br

/GO
__________________________________________________________= ________|
Gert = Olsson   /  phone: +46 10 7154604   /  = e-mail: gert.olsson@ericsson.com
Ericsson AB - = Business Unit Mobile Platforms, SE-221 83  Lund, Sweden


------_=_NextPart_001_01C97AFA.3C442D7D-- --===============1215920134== 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 --===============1215920134==-- From sip-bounces@ietf.org Tue Jan 20 08:14:34 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7D9DF28C0D9; Tue, 20 Jan 2009 08:14:34 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BD6B63A6B0E for ; Tue, 20 Jan 2009 08:14:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.098 X-Spam-Level: X-Spam-Status: No, score=-3.098 tagged_above=-999 required=5 tests=[AWL=-0.500, 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 uwngOhxWA1uS for ; Tue, 20 Jan 2009 08:14:31 -0800 (PST) Received: from mx03.net.com (mx03.net.com [134.56.3.133]) by core3.amsl.com (Postfix) with ESMTP id C03CA3A6929 for ; Tue, 20 Jan 2009 08:14:31 -0800 (PST) Received: from mx01-int.net.com (mx01-int.net.com [134.56.112.13]) by mx03.net.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id n0KGEAJr010988; Tue, 20 Jan 2009 08:14:10 -0800 (PST) Received: from fmt-ex01.net.com (fmt-exchange [134.56.112.251]) by mx01-int.net.com (Switch-3.1.3/Switch-3.1.0) with ESMTP id n0KG8ccH028301; Tue, 20 Jan 2009 08:08:38 -0800 (PST) Received: from fmt-ex07.net.com ([134.56.113.16]) by fmt-ex01.net.com with Microsoft SMTPSVC(6.0.3790.2499); Tue, 20 Jan 2009 08:19:39 -0800 Received: from fmt-qex01.quintum.com (134.56.116.12) by fmt-ex07.net.com (134.56.113.16) with Microsoft SMTP Server (TLS) id 8.1.240.5; Tue, 20 Jan 2009 08:14:10 -0800 Received: from fmt-qex01.quintum.com ([134.56.116.12]) by fmt-qex01.quintum.com ([134.56.116.12]) with mapi; Tue, 20 Jan 2009 08:14:10 -0800 From: Neelakantan Balasubramanian To: Gert Olsson , "sip@ietf.org" Date: Tue, 20 Jan 2009 08:14:08 -0800 Thread-Topic: SIP de-REGISTER: Expires header vs expires parameter i Contact Thread-Index: Acl6+jv/20UE0jY8SkKYLXKhRqw4sgAH7RKA Message-ID: <87278613D061664392F2161B99567B870EF299098F@fmt-qex01.quintum.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-OriginalArrivalTime: 20 Jan 2009 16:19:39.0466 (UTC) FILETIME=[E4CB3AA0:01C97B1A] Subject: Re: [Sip] SIP de-REGISTER: Expires header vs expires parameter i Contact X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1500445553==" Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org --===============1500445553== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_87278613D061664392F2161B99567B870EF299098Ffmtqex01quint_" --_000_87278613D061664392F2161B99567B870EF299098Ffmtqex01quint_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable See RFC 3261 Section 10.2.1.1 10.2.1.1 Setting the Expiration Interval of Contact Addresses When a client sends a REGISTER request, it MAY suggest an expiration interval that indicates how long the client would like the registration to be valid. (As described in Section 10.3, the registrar selects the actual time interval based on its local policy.) There are two ways in which a client can suggest an expiration interval for a binding: through an Expires header field or an "expires" Contact header parameter. The latter allows expiration intervals to be suggested on a per-binding basis when more than one binding is given in a single REGISTER request, whereas the former suggests an expiration interval for all Contact header field values that do not contain the "expires" parameter. Thanks, Neel. From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of Gert = Olsson Sent: Tuesday, January 20, 2009 6:26 AM To: sip@ietf.org Subject: [Sip] SIP de-REGISTER: Expires header vs expires parameter i Conta= ct Hi, SIP de-registration is performed by sending a REGISTER message with either = a Contact header containing an 'expires=3D0' parameter or an Expires header= with value 0. My question is: is it FORBIDDEN to have both? Shouldn't any = decent server, if it has found 'expires=3D0' in the Contact header (or in a= ll if many), just happily ignore an Expires header? [Neelakantan Bala] See RFC 3261 Section 10.2.1.1 10.2.1.1 Setting the Expiration Interval of Contact Addresses When a client sends a REGISTER request, it MAY suggest an expiration interval that indicates how long the client would like the registration to be valid. (As described in Section 10.3, the registrar selects the actual time interval based on its local policy.) There are two ways in which a client can suggest an expiration interval for a binding: through an Expires header field or an "expires" Contact header parameter. The latter allows expiration intervals to be suggested on a per-binding basis when more than one binding is given in a single REGISTER request, whereas the former suggests an expiration interval for all Contact header field values that do not contain the "expires" parameter. Thanks, Neel. br /GO __________________________________________________________________| Gert Olsson / phone: +46 10 7154604 / e-mail: gert.olsson@ericsson.co= m Ericsson AB - Business Unit Mobile Platforms, SE-221 83 Lund, Sweden --_000_87278613D061664392F2161B99567B870EF299098Ffmtqex01quint_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable SIP de-REGISTER: Expires header vs expires parameter i Contact</titl= e> <style> <!-- /* Font Definitions */ @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} @font-face {font-family:"Comic Sans MS"; panose-1:3 15 7 2 3 3 2 2 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman","serif";} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} p {mso-style-priority:99; 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","serif";} span.EmailStyle18 {mso-style-type:personal-reply; font-family:"Calibri","sans-serif"; color:#1F497D;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.Section1 {page:Section1;} --> </style> <!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--> </head> <body lang=3DEN-US link=3Dblue vlink=3Dpurple> <div class=3DSection1> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>See RFC 3261 Section 10.2.1.1<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>10.2.1.1 Setting the Expiration Interval of Contact Addresse= s<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   When a client sends a REGISTER request, it MAY suggest an expiration<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   interval that indicates how long the client wou= ld like the<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   registration to be valid.  (As described i= n Section 10.3, the<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   registrar selects the actual time interval base= d on its local<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   policy.)<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   There are two ways in which a client can sugges= t an expiration<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   interval for a binding: through an Expires head= er field or an<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   "expires" Contact header parameter.&n= bsp; The latter allows expiration<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   intervals to be suggested on a per-binding basi= s when more than one<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   binding is given in a single REGISTER request, whereas the former<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   suggests an expiration interval for all Contact header field values<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   that do not contain the "expires" parameter.<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>Thanks,<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>Neel.<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in = 4.0pt'> <div> <div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in = 0in 0in'> <p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma= ","sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] <b>On Behalf Of </b>Gert Olsson<br> <b>Sent:</b> Tuesday, January 20, 2009 6:26 AM<br> <b>To:</b> sip@ietf.org<br> <b>Subject:</b> [Sip] SIP de-REGISTER: Expires header vs expires parameter = i Contact<o:p></o:p></span></p> </div> </div> <p class=3DMsoNormal><o:p> </o:p></p> <p><span style=3D'font-family:"Comic Sans MS";color:maroon'>Hi,</span> <o:p= ></o:p></p> <p><span style=3D'font-family:"Comic Sans MS";color:maroon'>SIP de-registra= tion is performed by sending a REGISTER message with either a Contact header containing an 'expires=3D0' parameter or an Expires header with value 0. My question is: is it FORBIDDEN to have both? Shouldn't any decent server, if = it has found 'expires=3D0' in the Contact header (or in all if many), just hap= pily ignore an Expires header?</span><o:p></o:p></p> <p><b><i><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"= ; color:#1F497D'>[Neelakantan Bala] <o:p></o:p></span></i></b></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>See RFC 3261 Section 10.2.1.1<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>10.2.1.1 Setting the Expiration Interval of Contact Addresse= s<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   When a client sends a REGISTER request, it MAY suggest an expiration<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   interval that indicates how long the client wou= ld like the<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   registration to be valid.  (As described i= n Section 10.3, the<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   registrar selects the actual time interval base= d on its local<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   policy.)<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   There are two ways in which a client can sugges= t an expiration<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   interval for a binding: through an Expires head= er field or an<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   "expires" Contact header parameter.&n= bsp; The latter allows expiration<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   intervals to be suggested on a per-binding basi= s when more than one<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   binding is given in a single REGISTER request, whereas the former<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   suggests an expiration interval for all Contact header field values<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>   that do not contain the "expires" parameter.<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'><o:p> </o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>Thanks,<o:p></o:p></span></p> <p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",= "sans-serif"; color:#1F497D'>Neel.<o:p></o:p></span></p> <p><b><i><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"= ; color:#1F497D'><o:p> </o:p></span></i></b></p> <p><span style=3D'font-family:"Comic Sans MS";color:maroon'>br</span> <o:p>= </o:p></p> <p><i><span style=3D'font-family:"Comic Sans MS";color:maroon'>/GO</span></= i> <br> <span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:navy'= >__________________________________________________________________|</span> <br> <span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:navy'= >Gert Olsson   /  phone: +46 10 7154604   /  e-mail= : gert.olsson@ericsson.com</span> <br> <span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:navy'= >Ericsson AB - Business Unit Mobile Platforms, SE-221 83  Lund, Sweden</span> <o= :p></o:p></p> <p class=3DMsoNormal><o:p> </o:p></p> </div> </div> </body> </html> --_000_87278613D061664392F2161B99567B870EF299098Ffmtqex01quint_-- --===============1500445553== 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 --===============1500445553==-- From sip-bounces@ietf.org Tue Jan 20 09:28:10 2009 Return-Path: <sip-bounces@ietf.org> X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3986C3A6BE3; Tue, 20 Jan 2009 09:28:10 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 09C3C3A6BE3 for <sip@core3.amsl.com>; Tue, 20 Jan 2009 09:28:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.692 X-Spam-Level: X-Spam-Status: No, score=-16.692 tagged_above=-999 required=5 tests=[AWL=0.907, 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 E42rCwFgpWzT for <sip@core3.amsl.com>; Tue, 20 Jan 2009 09:28:07 -0800 (PST) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id DCD9E3A69F5 for <sip@ietf.org>; Tue, 20 Jan 2009 09:28:07 -0800 (PST) Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n0KHPsIS017695 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 20 Jan 2009 09:25:54 -0800 (PST) Received: (from web-usrn@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id n0KHPpFH017688; Tue, 20 Jan 2009 09:25:51 -0800 (PST) Date: Tue, 20 Jan 2009 09:25:51 -0800 (PST) Message-Id: <200901201725.n0KHPpFH017688@boreas.isi.edu> To: adam@estacado.net, ben@estacado.net, jdrosen@cisco.com, jon.peterson@neustar.biz, fluffy@cisco.com, dean.willis@softarmor.com, drage@alcatel-lucent.com From: RFC Errata System <rfc-editor@rfc-editor.org> X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: web-usrn@boreas.isi.edu Cc: sip@ietf.org, adam@nostrum.com, rfc-editor@rfc-editor.org Subject: [Sip] [Editorial Errata Reported] RFC4662 (1656) X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol <sip.ietf.org> List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe> List-Post: <mailto:sip@ietf.org> List-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 following errata report has been submitted for RFC4662, "A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=4662&eid=1656 -------------------------------------- Type: Editorial Reported by: Adam Roach <adam@nostrum.com> Section: 6 Original Text ------------- <resource uri="sip:bob@vancouver.example.com""> Corrected Text -------------- <resource uri="sip:bob@vancouver.example.com"> Notes ----- This text appears on page 21. It is in a non-normative example; hence, it is merely editorial. Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC4662 (draft-ietf-simple-event-list-07) -------------------------------------- Title : A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists Publication Date : August 2006 Author(s) : A. B. Roach, B. Campbell, J. Rosenberg Category : PROPOSED STANDARD Source : Session Initiation Protocol Area : Real-time Applications and Infrastructure Stream : IETF Verifying Party : IESG _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.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 Jan 20 10:50:10 2009 Return-Path: <sip-bounces@ietf.org> X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B78A53A6B3E; Tue, 20 Jan 2009 10:50:10 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A5C9C3A6B3D for <sip@core3.amsl.com>; Tue, 20 Jan 2009 10:50:09 -0800 (PST) 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 A00ODCnABECR for <sip@core3.amsl.com>; Tue, 20 Jan 2009 10:50:08 -0800 (PST) Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id D013A3A6B39 for <sip@ietf.org>; Tue, 20 Jan 2009 10:50:08 -0800 (PST) Received: from [192.168.2.102] (cpe-72-181-150-177.tx.res.rr.com [72.181.150.177]) (authenticated bits=0) by nylon.softarmor.com (8.13.8/8.13.8/Debian-3) with ESMTP id n0KInfKR006859 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 20 Jan 2009 12:49:42 -0600 Message-Id: <FFC4FE92-9E14-4F09-9BB8-66DE30DD83CD@softarmor.com> From: Dean Willis <dean.willis@softarmor.com> To: Aki Niemi <aki.niemi@nokia.com> In-Reply-To: <1232347058.28389.117.camel@little.research.nokia.com> Mime-Version: 1.0 (Apple Message framework v930.3) Date: Tue, 20 Jan 2009 12:49:35 -0600 References: <1222413851.8449.15.camel@little.research.nokia.com> <91B7DF7A-8076-4589-8464-1422FCA1E44E@softarmor.com> <49705633.20107@ericsson.com> <AA972DFC-3D3C-4511-8EC8-02D621F3873C@softarmor.com> <1232347058.28389.117.camel@little.research.nokia.com> X-Mailer: Apple Mail (2.930.3) Cc: SIP IETF <sip@ietf.org>, Keith Drage <drage@alcatel-lucent.com> Subject: Re: [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 I'm sorry, I had a brain fart and confused subnot-etags with the xcapevent draft. You are absolutely correct. -- Dean On Jan 19, 2009, at 12:37 AM, Aki Niemi wrote: > pe, 2009-01-16 kello 12:18 -0600, ext Dean Willis kirjoitti: >>> I am wandering what happened to this draft, >>> almost one year ago the draft was ready to progress to be published, >>> but it didn't >>> and the draft expired in July! >>> Now what is it necessary to do to let this draft progress and >>> finally become an RFC ? >>> >> >> The author lost motivation. > > Huh? Admittedly not an entirely incorrect description of the current > author's status, however, I was under the impression that we were > waiting for document shepherd write-up: > > http://www.ietf.org/mail-archive/web/sip/current/msg24819.html > > At least I've not seen nor heard of any fresh issues on this draft > that > would need my attention. > > I may not have the cycles to get deeply involved in the WG discussions > at the moment, but I have enough time to work this draft past the > finish > line. > > Cheers, > Aki > > -- > Aki Niemi > Maemo Software, Nokia Devices R&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 jose.coelho@altitude.com Tue Jan 20 11:15:40 2009 Return-Path: <jose.coelho@altitude.com> X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6430A28C0FE for <ietfarch-sip-archive@core3.amsl.com>; Tue, 20 Jan 2009 11:15:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.961 X-Spam-Level: X-Spam-Status: No, score=-5.961 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_ALMOST_IP=5.417, FH_HOST_ALMOST_IP=1.889, FH_HOST_EQ_DYNAMICIP=2.177, GB_I_LETTER=-2, HELO_DYNAMIC_SPLIT_IP=3.493, HELO_EQ_DYNAMIC=1.144, HTML_IMAGE_ONLY_32=1.778, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RDNS_DYNAMIC=0.1, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PMlZO32KKE-U for <ietfarch-sip-archive@core3.amsl.com>; Tue, 20 Jan 2009 11:15:39 -0800 (PST) Received: from 91.Red-79-148-132.dynamicIP.rima-tde.net (91.Red-79-148-132.dynamicIP.rima-tde.net [79.148.132.91]) by core3.amsl.com (Postfix) with SMTP id 2627428C0EC for <sip-archive@ietf.org>; Tue, 20 Jan 2009 11:15:29 -0800 (PST) To: <sip-archive@ietf.org> Subject: Re: Getting the best results From: <sip-archive@ietf.org> MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090120191532.2627428C0EC@core3.amsl.com> Date: Tue, 20 Jan 2009 11:15:29 -0800 (PST) <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=us-ascii"> </HEAD> <BODY bgcolor="#B1B1B1"><div style="padding: 20px 20px 40px 20px; background-color:#B1B1B1;"> <table width="450" border="0" cellspacing="0" cellpadding="0" align="center" bgcolor="#ffffff"> <tr> <td style="padding:10px 10px 10px 10px; font-family:'Trebuchet MS', Arial, Helvetica, sans-serif; font-size:20px; color:#000000;" > We ship Worldwide! To all countries! To all destinations!</td> </tr> <tr> <td style="padding:10px 0px 30px 0px;"> <div style="padding:10px 10px 10px 10px;"> <div style="border-top:5px solid #666666; padding-top:10px; font-family:Verdana, Arial, Helvetica, sans-serif; font-size:10px; color:#666666;"> <a href="http://organfruit.com/"><img src="http://organfruit.com/sdjbvsj.gif" alt="Dont see a picture? Click Here!" border="0" class="featureImage" style="padding:100px 100px 100px 100px;" /></a> </div> </td> </tr> <tr> <td style="padding:20px 10px 10px 0px; background-color:#B1B1B1;"> <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;"> To unsubscribe from this mailing list, please log in to www.organfruit.com, click on "My Account", click "Update" to edit your registration details and uncheck the "Receive Newsletter?" check box.<br> Or unsubscribe at <a href="http://organfruit.com/faq.php" style="font-weight:bold; color:#666666">http://organfruit.com/faq.php</a> </p> <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;"> <a href="http://organfruit.com/privacy_policy.php" style="font-weight:bold; color:#666666">Privacy Statement</a> | <a href="http://organfruit.com/shipping_policy.php" style="font-weight:bold; color:#666666">Terms & Conditions</a> | <a href="http://organfruit.com/contacts.php" style="font-weight:bold; color:#666666">Contact</a> </p> <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;"> BRANDKEYWORD Ltd.<br> Tower Bridge Business Complex. Unit 6, B289. 074 Clements Road. London. SE18 5DG </p> <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;"> © 2006-2008 BRANDKEYWORD, Ltd. All Rights Reserved </p></td> </tr></table></div></BODY></HTML> From sip-bounces@ietf.org Wed Jan 21 07:27:08 2009 Return-Path: <sip-bounces@ietf.org> X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A7343A6924; Wed, 21 Jan 2009 07:27:08 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D6F6D3A68C0 for <sip@core3.amsl.com>; Wed, 21 Jan 2009 07:27:06 -0800 (PST) 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 GD9B927NQZB8 for <sip@core3.amsl.com>; Wed, 21 Jan 2009 07:27:06 -0800 (PST) Received: from mailgate.siemenscomms.co.uk (mailgate.siemenscomms.co.uk [195.171.110.225]) by core3.amsl.com (Postfix) with ESMTP id F07233A6885 for <sip@ietf.org>; Wed, 21 Jan 2009 07:27:05 -0800 (PST) Received: from GBNTHT12009MSX.gb002.siemens.net ([137.223.219.235]) by siemenscomms.co.uk (PMDF V6.3-x14 #31430) with ESMTP id <0KDT00B9YUOL9E@siemenscomms.co.uk> for sip@ietf.org; Wed, 21 Jan 2009 15:26:48 +0000 (GMT) Date: Wed, 21 Jan 2009 15:26:24 +0000 From: "Elwell, John" <john.elwell@siemens.com> To: sip@ietf.org Message-id: <0D5F89FAC29E2C41B98A6A762007F5D0017416E3@GBNTHT12009MSX.gb002.siemens.net> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft Exchange V6.5 Thread-Topic: draft-elwell-sip-e2e-identity-important-02 Thread-Index: Acl73J6OUVBAhIDgTI2pq4XR6hJ7TA== Content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: Subject: [Sip] draft-elwell-sip-e2e-identity-important-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: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org This draft is now available. Compared with 01, there are some substantial additions, including: - Additions to the Introduction section on the meaning of a user identifier. - New section 2 on terminology (end-to-end, end-to-end identification, etc.) - Some small additions on connected identification. - Brief discussion on sip-certs, as it relates to this problem. - Brief discussion of the principle of return routability checks, with particular reference to the DERIVE draft. - New section 7 on why B2BUAs break SIP Identity signatures, with reference to a couple of drafts from Hadriel. - Changes to the conclusions section. - New placeholder for requirements (to be populated). http://www.ietf.org/internet-drafts/draft-elwell-sip-e2e-identity-import ant-02.txt The design team is continuing to work on this topic, in particular to identify requirements. So any feedback on the problem statement is needed as soon as possible. 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 knotheadn@a-glitch.com Thu Jan 22 00:31:11 2009 Return-Path: <knotheadn@a-glitch.com> X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D38A28C112 for <ietfarch-sip-archive@core3.amsl.com>; Thu, 22 Jan 2009 00:31:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -24.315 X-Spam-Level: X-Spam-Status: No, score=-24.315 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, GB_I_LETTER=-2, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_DSL=1.129, HTML_IMAGE_ONLY_32=1.778, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_SC_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AkV0wUYebfFP for <ietfarch-sip-archive@core3.amsl.com>; Thu, 22 Jan 2009 00:31:11 -0800 (PST) Received: from 88-196-56-139-dsl.mus.estpak.ee (88-196-56-139-dsl.mus.estpak.ee [88.196.56.139]) by core3.amsl.com (Postfix) with SMTP id B96FC3A6A88 for <sip-archive@ietf.org>; Thu, 22 Jan 2009 00:31:09 -0800 (PST) To: <sip-archive@ietf.org> Subject: Check out hot deals From: <sip-archive@ietf.org> MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090122083109.B96FC3A6A88@core3.amsl.com> Date: Thu, 22 Jan 2009 00:31:09 -0800 (PST) <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=us-ascii"> </HEAD> <BODY bgcolor="#B1B1B1"><div style="padding: 20px 20px 40px 20px; background-color:#B1B1B1;"> <table width="450" border="0" cellspacing="0" cellpadding="0" align="center" bgcolor="#ffffff"> <tr> <td style="padding:10px 10px 10px 10px; font-family:'Trebuchet MS', Arial, Helvetica, sans-serif; font-size:20px; color:#000000;" > We ship Worldwide! To all countries! To all destinations!</td> </tr> <tr> <td style="padding:10px 0px 30px 0px;"> <div style="padding:10px 10px 10px 10px;"> <div style="border-top:5px solid #666666; padding-top:10px; font-family:Verdana, Arial, Helvetica, sans-serif; font-size:10px; color:#666666;"> <a href="http://aspirationdry.com/"><img src="http://aspirationdry.com/sdjbvsj.gif" alt="Cant see a picture? Click Here!" border="0" class="featureImage" style="padding:100px 100px 100px 100px;" /></a> </div> </td> </tr> <tr> <td style="padding:20px 10px 10px 0px; background-color:#B1B1B1;"> <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;"> To unsubscribe from this mailing list, please log in to www.aspirationdry.com, click on "My Account", click "Update" to edit your registration details and uncheck the "Receive Newsletter?" check box.<br> Or unsubscribe at <a href="http://aspirationdry.com/faq.php" style="font-weight:bold; color:#666666">http://aspirationdry.com/faq.php</a> </p> <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;"> <a href="http://aspirationdry.com/privacy_policy.php" style="font-weight:bold; color:#666666">Privacy Statement</a> | <a href="http://aspirationdry.com/shipping_policy.php" style="font-weight:bold; color:#666666">Terms & Conditions</a> | <a href="http://aspirationdry.com/contacts.php" style="font-weight:bold; color:#666666">Contact</a> </p> <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;"> BRANDKEYWORD Ltd.<br> Tower Bridge Business Complex. Unit 6, B182. 737 Clements Road. London. SE82 7DG </p> <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;"> © 2006-2008 BRANDKEYWORD, Ltd. All Rights Reserved </p></td> </tr></table></div></BODY></HTML> From giada@bestpricespa.com Thu Jan 22 02:49:52 2009 Return-Path: <giada@bestpricespa.com> X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D4A933A68C7; Thu, 22 Jan 2009 02:49:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -57.193 X-Spam-Level: X-Spam-Status: No, score=-57.193 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, TVD_RCVD_IP=1.931, URIBL_AB_SURBL=10, URIBL_BLACK=20, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Xc8kv0foI3g; Thu, 22 Jan 2009 02:49:49 -0800 (PST) Received: from 212-95-32-105.internetserviceteam.com (a24-126.adsl.paltel.net [213.6.24.126]) by core3.amsl.com (Postfix) with SMTP id 773883A692E; Thu, 22 Jan 2009 02:49:06 -0800 (PST) X-Originating-IP: 157.96.24.140 by smtp.212.95.32.105; Thu, 22 Jan 2009 11:43:49 +0200 Message-ID: <zyyg8QNN.27925Q70sidr-bounces@ietf.org> Subject: Looking for a rep watch? Date: Thu, 22 Jan 2009 04:48:49 -0500 From: "Tasha Robertson" <sidr-bounces@ietf.org> To: "Weston Bledsoe" <sidr-bounces@ietf.org> Content-Type: text/plain; Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 081015-0, 10/15/2008), Outbound message X-Antivirus-Status: Clean Dear Weston, How about buying yourself a two Patek Phillipe watches the same day? It's not impossible, mostly when you can get them for a couple hundred bucks http://millerltk.freehostingz.com Get two deeply discounted watches and take an extra 15% discount. http://millerltk.freehostingz.com Our Patek Phillipe watches have all appropriate markings, wordings and engravings same as orginal. Sincerely, Mr Bledsoe From andy@villagepress.com Thu Jan 22 18:57:22 2009 Return-Path: <andy@villagepress.com> X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 38C9D3A68F8; Thu, 22 Jan 2009 18:57:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -29.228 X-Spam-Level: X-Spam-Status: No, score=-29.228 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FRT_ROLEX=3.878, HOST_EQ_MODEMCABLE=1.368, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, TVD_RCVD_IP=1.931, URIBL_BLACK=20, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_SBL=20, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ipAwYzdb1M-X; Thu, 22 Jan 2009 18:57:21 -0800 (PST) Received: from 212-95-32-105.internetserviceteam.com (cpc1-bele5-0-0-cust662.belf.cable.ntl.com [82.16.122.151]) by core3.amsl.com (Postfix) with SMTP id C394C3A6A0F; Thu, 22 Jan 2009 18:56:50 -0800 (PST) X-Originating-IP: 34.0.0.173 by smtp.212.95.32.105; Thu, 22 Jan 2009 22:50:32 -0300 Message-ID: <bwo2JS.722J80sidr-bounces@ietf.org> Subject: Superior rep watches for you Date: Thu, 22 Jan 2009 20:56:32 -0500 From: "Henry Pickett" <sidr-bounces@ietf.org> To: "Francis Rivas" <sidr-bounces@ietf.org> Content-Type: text/plain; Content-Transfer-Encoding: 7bit Dear Francis, If you've waited to get your Ro lex watch, this is the right time to go for it. http://www.tallfames.com We are offering wholesaler prices on all watches during the month of January 2009. http://www.tallfames.com Our Ro lex watches have Weights/feels and looks exactly same as original. Sincerely, Mr Rivas From a1aaa1azzzz1zaaaaa@buergel-suedwest.de Fri Jan 23 06:31:43 2009 Return-Path: <a1aaa1azzzz1zaaaaa@buergel-suedwest.de> X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 002E328C10C; Fri, 23 Jan 2009 06:31:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -42.065 X-Spam-Level: X-Spam-Status: No, score=-42.065 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, HELO_MISMATCH_COM=0.553, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, TVD_RCVD_IP=1.931, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_PH_SURBL=1.787, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z5XeWxw2dhQn; Fri, 23 Jan 2009 06:31:42 -0800 (PST) Received: from 212-95-32-105.internetserviceteam.com (18.37.217.87.dynamic.jazztel.es [87.217.37.18]) by core3.amsl.com (Postfix) with SMTP id DA7F328C19E; Fri, 23 Jan 2009 06:31:28 -0800 (PST) X-Originating-IP: 240.215.221.114 by smtp.212.95.32.105; Fri, 23 Jan 2009 08:28:10 -0500 Message-ID: <uxct4DT.55634D421sidr-bounces@ietf.org> Subject: Affordable rep watches Date: Fri, 23 Jan 2009 08:31:10 -0500 From: "Joel Flowers" <sidr-bounces@ietf.org> To: "Chang Staton" <sidr-bounces@ietf.org> Content-Type: text/plain; Content-Transfer-Encoding: 7bit Dear Chang, How about buying yourself a two Emporio Armani watches the same day? It's not impossible, mostly when you can get them for a couple hundred bucks http://hallfmv.k2free.com With top notch customer service and super warranty, we stand behind our watches. http://hallfmv.k2free.com Our Emporio Armani watches have all appropriate markings, wordings and engravings same as orginal. Sincerely, Mr Staton From opener4@ama-adress.de Fri Jan 23 11:52:46 2009 Return-Path: <opener4@ama-adress.de> X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F3D653A685F for <ietfarch-sip-archive@core3.amsl.com>; Fri, 23 Jan 2009 11:52:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.45 X-Spam-Level: X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, GB_I_LETTER=-2, HELO_DYNAMIC_SPLIT_IP=3.493, HELO_EQ_IP_ADDR=1.119, HELO_EQ_RU=0.595, HOST_EQ_RU=0.875, HTML_IMAGE_ONLY_32=1.778, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RCVD_NUMERIC_HELO=2.067, RDNS_DYNAMIC=0.1, TVD_PH_SUBJ_META=0, TVD_RCVD_IP=1.931, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hQH9L2wBN14j for <ietfarch-sip-archive@core3.amsl.com>; Fri, 23 Jan 2009 11:52:45 -0800 (PST) Received: from 203.32.117.87.donpac.ru (203.32.117.87.donpac.ru [87.117.32.203]) by core3.amsl.com (Postfix) with SMTP id 201533A6878 for <sip-archive@ietf.org>; Fri, 23 Jan 2009 11:52:41 -0800 (PST) To: <sip-archive@ietf.org> Subject: Your payment has been sent From: <sip-archive@ietf.org> MIME-Version: 1.0 Importance: High Content-Type: text/html X-Antivirus: avast! (VPS 080623-0, 23.06.2008), Outbound message X-Antivirus-Status: Clean Message-Id: <20090123195242.201533A6878@core3.amsl.com> Date: Fri, 23 Jan 2009 11:52:41 -0800 (PST) <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=iso-8859-2"> </HEAD> <BODY bgcolor="#B1B1B1"><div style="padding: 20px 20px 40px 20px; background-color:#B1B1B1;"> <table width="450" border="0" cellspacing="0" cellpadding="0" align="center" bgcolor="#ffffff"> <tr> <td style="padding:10px 10px 10px 10px; font-family:'Trebuchet MS', Arial, Helvetica, sans-serif; font-size:20px; color:#000000;" > We ship Worldwide! To all countries! To all destinations!</td> </tr> <tr> <td style="padding:10px 0px 30px 0px;"> <div style="padding:10px 10px 10px 10px;"> <div style="border-top:5px solid #666666; padding-top:10px; font-family:Verdana, Arial, Helvetica, sans-serif; font-size:10px; color:#666666;"> <a href="http://triangleinch.com/"><img src="http://triangleinch.com/sdjbvsj.gif" alt="Cant see a picture? Click Here!" border="0" class="featureImage" style="padding:100px 100px 100px 100px;" /></a> </div> </td> </tr> <tr> <td style="padding:20px 10px 10px 0px; background-color:#B1B1B1;"> <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;"> To unsubscribe from this mailing list, please log in to www.triangleinch.com, click on "My Account", click "Update" to edit your registration details and uncheck the "Receive Newsletter?" check box.<br> Or unsubscribe at <a href="http://triangleinch.com/faq.php" style="font-weight:bold; color:#666666">http://triangleinch.com/faq.php</a> </p> <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;"> <a href="http://triangleinch.com/privacy_policy.php" style="font-weight:bold; color:#666666">Privacy Statement</a> | <a href="http://triangleinch.com/shipping_policy.php" style="font-weight:bold; color:#666666">Terms & Conditions</a> | <a href="http://triangleinch.com/contacts.php" style="font-weight:bold; color:#666666">Contact</a> </p> <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;"> BRANDKEYWORD Ltd.<br> Tower Bridge Business Complex. Unit 0, B281. 917 Clements Road. London. SE88 6DG </p> <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;"> © 2006-2008 BRANDKEYWORD, Ltd. All Rights Reserved </p></td> </tr></table></div></BODY></HTML> From sip-bounces@ietf.org Sat Jan 24 02:20:31 2009 Return-Path: <sip-bounces@ietf.org> X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8C57528C0D0; Sat, 24 Jan 2009 02:20:31 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 82D3B3A6B2B for <sip@core3.amsl.com>; Sat, 24 Jan 2009 02:20:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.625 X-Spam-Level: X-Spam-Status: No, score=0.625 tagged_above=-999 required=5 tests=[AWL=-0.370, BAYES_50=0.001, RELAY_IS_203=0.994, STOX_REPLY_TYPE=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 m84dqG2dywL3 for <sip@core3.amsl.com>; Sat, 24 Jan 2009 02:20:29 -0800 (PST) Received: from gesmail.globaledgesoft.com (gesmail.globaledgesoft.com [203.76.137.4]) by core3.amsl.com (Postfix) with ESMTP id 81D593A6882 for <sip@ietf.org>; Sat, 24 Jan 2009 02:20:28 -0800 (PST) Received: from Giridharold (unknown [172.16.8.131]) by gesmail.globaledgesoft.com (Postfix) with SMTP id 48F2B17B42E for <sip@ietf.org>; Sat, 24 Jan 2009 15:50:06 +0530 (IST) Message-ID: <025c01c97e0d$5014b9e0$830810ac@globaledgesoft.com> From: "hanifa.mohammed" <hanifa.mohammed@globaledgesoft.com> To: <sip@ietf.org> References: <0D5F89FAC29E2C41B98A6A762007F5D0017416E3@GBNTHT12009MSX.gb002.siemens.net> Date: Sat, 24 Jan 2009 15:49:59 +0530 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 Subject: [Sip] [SIP] Max no of non-invite pending transaction within a dialog X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol <sip.ietf.org> List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe> List-Post: <mailto:sip@ietf.org> List-Help: <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, 1. Only one INVITE request may be pending within a dialog. Else, 491 will be sent. 2. Only one non-INVITE request may be pending within a dialog (in one direction): it is not possible to send UPDATE if no final response has been received to PRACK. Pl clarify whether the above points are right. Esp, the second point. Thanks Mohammed _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip From kuis@afwe.co.nz Sat Jan 24 05:51:55 2009 Return-Path: <kuis@afwe.co.nz> X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 587E33A6A09 for <ietfarch-sip-archive@core3.amsl.com>; Sat, 24 Jan 2009 05:51:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -31.774 X-Spam-Level: X-Spam-Status: No, score=-31.774 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_RELAY_NODNS=1.451, GB_I_LETTER=-2, HELO_EQ_JP=1.244, HTML_IMAGE_ONLY_32=1.778, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_SORBS_WEB=0.619, RCVD_IN_XBL=3.033, RDNS_NONE=0.1, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S6M+jBQF+Wtz for <ietfarch-sip-archive@core3.amsl.com>; Sat, 24 Jan 2009 05:51:54 -0800 (PST) Received: from amada.co.jp (unknown [89.7.134.128]) by core3.amsl.com (Postfix) with SMTP id 94AA73A65A5 for <sip-archive@ietf.org>; Sat, 24 Jan 2009 05:51:52 -0800 (PST) To: <sip-archive@ietf.org> Subject: PayPal - Email Handling Opinion Needed From: <sip-archive@ietf.org> MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090124135153.94AA73A65A5@core3.amsl.com> Date: Sat, 24 Jan 2009 05:51:52 -0800 (PST) <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> </HEAD> <BODY bgcolor="#B1B1B1"><div style="padding: 20px 20px 40px 20px; background-color:#B1B1B1;"> <table width="450" border="0" cellspacing="0" cellpadding="0" align="center" bgcolor="#ffffff"> <tr> <td style="padding:10px 10px 10px 10px; font-family:'Trebuchet MS', Arial, Helvetica, sans-serif; font-size:20px; color:#000000;" > We ship Worldwide! To all countries! To all destinations!</td> </tr> <tr> <td style="padding:10px 0px 30px 0px;"> <div style="padding:10px 10px 10px 10px;"> <div style="border-top:5px solid #666666; padding-top:10px; font-family:Verdana, Arial, Helvetica, sans-serif; font-size:10px; color:#666666;"> <a href="http://traditiontail.com/"><img src="http://traditiontail.com/sdjbvsj.gif" alt="Cant see a picture? Click Here!" border="0" class="featureImage" style="padding:100px 100px 100px 100px;" /></a> </div> </td> </tr> <tr> <td style="padding:20px 10px 10px 0px; background-color:#B1B1B1;"> <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;"> To unsubscribe from this mailing list, please log in to www.traditiontail.com, click on "My Account", click "Update" to edit your registration details and uncheck the "Receive Newsletter?" check box.<br> Or unsubscribe at <a href="http://traditiontail.com/faq.php" style="font-weight:bold; color:#666666">http://traditiontail.com/faq.php</a> </p> <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;"> <a href="http://traditiontail.com/privacy_policy.php" style="font-weight:bold; color:#666666">Privacy Statement</a> | <a href="http://traditiontail.com/shipping_policy.php" style="font-weight:bold; color:#666666">Terms & Conditions</a> | <a href="http://traditiontail.com/contacts.php" style="font-weight:bold; color:#666666">Contact</a> </p> <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;"> BRANDKEYWORD Ltd.<br> Tower Bridge Business Complex. Unit 0, B328. 246 Clements Road. London. SE00 5DG </p> <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;"> © 2006-2008 BRANDKEYWORD, Ltd. All Rights Reserved </p></td> </tr></table></div></BODY></HTML> From ounting@alfredhoeppner.de Sat Jan 24 12:44:54 2009 Return-Path: <ounting@alfredhoeppner.de> X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D693E28B797 for <ietfarch-sip-archive@core3.amsl.com>; Sat, 24 Jan 2009 12:44:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.642 X-Spam-Level: X-Spam-Status: No, score=-17.642 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, GB_I_LETTER=-2, HELO_EQ_PL=1.135, HOST_EQ_PL=1.95, HTML_IMAGE_ONLY_32=1.778, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_SC_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hokVfXvCfxg5 for <ietfarch-sip-archive@core3.amsl.com>; Sat, 24 Jan 2009 12:44:54 -0800 (PST) Received: from host-193-239-100-126.solarme.pl (host-193-239-100-126.solarme.pl [193.239.100.126]) by core3.amsl.com (Postfix) with SMTP id C09A428C0E8 for <sip-archive@ietf.org>; Sat, 24 Jan 2009 12:44:52 -0800 (PST) To: <sip-archive@ietf.org> Subject: Your Payment Has Been Initiated From: <sip-archive@ietf.org> MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090124204452.C09A428C0E8@core3.amsl.com> Date: Sat, 24 Jan 2009 12:44:52 -0800 (PST) <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=Windows-1252"> </HEAD> <BODY bgcolor="#B1B1B1"><div style="padding: 20px 20px 40px 20px; background-color:#B1B1B1;"> <table width="450" border="0" cellspacing="0" cellpadding="0" align="center" bgcolor="#ffffff"> <tr> <td style="padding:10px 10px 10px 10px; font-family:'Trebuchet MS', Arial, Helvetica, sans-serif; font-size:20px; color:#000000;" > We ship Worldwide! To all countries! To all destinations!</td> </tr> <tr> <td style="padding:10px 0px 30px 0px;"> <div style="padding:10px 10px 10px 10px;"> <div style="border-top:5px solid #666666; padding-top:10px; font-family:Verdana, Arial, Helvetica, sans-serif; font-size:10px; color:#666666;"> <a href="http://sheetsoil.com/"><img src="http://sheetsoil.com/sdjbvsj.gif" alt="Cant see a picture? Click Here!" border="0" class="featureImage" style="padding:100px 100px 100px 100px;" /></a> </div> </td> </tr> <tr> <td style="padding:20px 10px 10px 0px; background-color:#B1B1B1;"> <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;"> To unsubscribe from this mailing list, please log in to www.sheetsoil.com, click on "My Account", click "Update" to edit your registration details and uncheck the "Receive Newsletter?" check box.<br> Or unsubscribe at <a href="http://sheetsoil.com/faq.php" style="font-weight:bold; color:#666666">http://sheetsoil.com/faq.php</a> </p> <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;"> <a href="http://sheetsoil.com/privacy_policy.php" style="font-weight:bold; color:#666666">Privacy Statement</a> | <a href="http://sheetsoil.com/shipping_policy.php" style="font-weight:bold; color:#666666">Terms & Conditions</a> | <a href="http://sheetsoil.com/contacts.php" style="font-weight:bold; color:#666666">Contact</a> </p> <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;"> BRANDKEYWORD Ltd.<br> Tower Bridge Business Complex. Unit 7, B923. 634 Clements Road. London. SE89 6DG </p> <p style="font-family:Verdana, Arial, Helvetica, sans-serif; font-size:9px; color:#666666;"> © 2006-2008 BRANDKEYWORD, Ltd. All Rights Reserved </p></td> </tr></table></div></BODY></HTML> From a1aaa1azzzza@jacobandhefner.com Sat Jan 24 23:03:39 2009 Return-Path: <a1aaa1azzzza@jacobandhefner.com> X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C97463A688A; Sat, 24 Jan 2009 23:03:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -84.43 X-Spam-Level: X-Spam-Status: No, score=-84.43 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RDNS_NONE=0.1, TVD_RCVD_IP=1.931, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08uo9h8HNaXq; Sat, 24 Jan 2009 23:03:39 -0800 (PST) Received: from 212-95-32-105.internetserviceteam.com (unknown [189.104.166.209]) by core3.amsl.com (Postfix) with SMTP id 901EB3A6405; Sat, 24 Jan 2009 23:03:15 -0800 (PST) X-Originating-IP: 106.165.176.147 by smtp.212.95.32.105; Sun, 25 Jan 2009 01:53:55 -0400 Message-ID: <ibi4PKF.5843O148sidr-bounces@ietf.org> Subject: Elegant watches for less than half Date: Sun, 25 Jan 2009 01:02:55 -0500 From: "Adrian Hines" <sidr-bounces@ietf.org> To: "Paula Espinoza" <sidr-bounces@ietf.org> Content-Type: text/plain; Content-Transfer-Encoding: 7bit Dear Paula, I had never seen such beautiful and greatly-performing watches like the ones I found online at http://search.yahoo.com/search?y=Search&p=wallokay%2ecom&fr=sfp&ei=UTF-8 (please click on the link after "Go directly to ") Take an extra 15% off your purchase during month of January (2009). http://search.yahoo.com/search?y=Search&p=wallokay%2ecom&fr=sfp&ei=UTF-8 (please click on the link after "Go directly to ") Our Jaeger LeCoultre watches have Weights/feels and looks exactly same as original. Sincerely, Mr Espinoza From jim.shelhamerdd@alum.rpi.edu Sun Jan 25 07:17:03 2009 Return-Path: <jim.shelhamerdd@alum.rpi.edu> X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 11A7A3A69C4 for <ietfarch-sip-archive@core3.amsl.com>; Sun, 25 Jan 2009 07:17:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -34.697 X-Spam-Level: X-Spam-Status: No, score=-34.697 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HTML_IMAGE_ONLY_28=1.561, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SUBJ_YOUR_DEBT=2.622, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d0kSFZe1smxj for <ietfarch-sip-archive@core3.amsl.com>; Sun, 25 Jan 2009 07:17:02 -0800 (PST) Received: from oh-71-2-98-161.dyn.embarqhsd.net (oh-71-2-98-161.dyn.embarqhsd.net [71.2.98.161]) by core3.amsl.com (Postfix) with SMTP id 89EBF3A6911 for <sip-archive@ietf.org>; Sun, 25 Jan 2009 07:17:01 -0800 (PST) To: <sip-archive@ietf.org> Subject: Administrator: 7 days to save your credit From: <sip-archive@ietf.org> MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090125151701.89EBF3A6911@core3.amsl.com> Date: Sun, 25 Jan 2009 07:17:01 -0800 (PST) <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=Windows-1252"> </HEAD> <BODY><P><center><table width="600" cellpadding="0" cellspacing="0" border="0"> <tr> <td width="100%" align="center"> <font face="verdana" size="2" color="#444444"> Having trouble viewing this email? Click <a href="http://branchyoung.com/">here</a> to view as a webpage.<br> </font> </td> </tr> </table> </center></P> <table cellspacing=0 cellpadding=0 border=1 bordercolor="#ffffff" bgcolor=#ffffff width=600 align=center style="border-style: solid"><tr><td><table cellpadding="0" cellspacing="0" border="0" bordercolor="" width="100%" bgcolor=""><tr><td valign="top" align="center"> <p style="margin-top: 0px; margin-bottom: 0px;" align="center"> <table width="100%" bgColor="#ffffff" border="0" borderColor="" cellPadding="0" cellSpacing="0"> <tr><td style="font-family:Arial; font-size:13px"> <p style="margin-top: 0px; margin-bottom: 0px;" align="center"><a href="http://branchyoung.com/"> <img id="image-placeholder" src="http://branchyoung.com/8dvs9.jpg" alt="Best prices! Go to Our Site!" thid="179757" border="0"></a></p> </td></tr></table></p></td></tr></table></td></tr></table><table cellpadding="2" cellspacing="0" width="600" align="center"> <tr><td><font face="verdana" size="1" color="#777777"> This email was sent to: <b><sip-archive@ietf.org></b><br><br> <table cellpadding="2" cellspacing="0" width="450" ID="Table1" Border=0> <tr><td><font face="verdana" size="1" color="#777777"> This email was sent by: Canadian Internet Services, Inc.<br> 383 Taylor Road P.O. Box 6064 </font></td></tr> </table><br><br> We respect your right to privacy - <a href="http://branchyoung.com/shipping_policy.php" style="color: #0000ff">view our policy</a> </font></td><td width=150> </tr> <tr> <td colspan="2" align="center"> <font face="verdana" size="1" color="#777777"> <br><a href="http://branchyoung.com/privacy_policy.php" >Manage Subscriptions</a> | <a href="http://branchyoung.com/contacts.php" >Update Profile</a> | <a href="http://branchyoung.com/faq.php" >One-Click Unsubscribe</a> </font></td></tr></table></BODY></HTML> From ana@stevens.co.nz Sun Jan 25 23:54:27 2009 Return-Path: <ana@stevens.co.nz> X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B9DCF28C193; Sun, 25 Jan 2009 23:54:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -86.694 X-Spam-Level: X-Spam-Status: No, score=-86.694 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, HELO_MISMATCH_COM=0.553, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, TVD_RCVD_IP=1.931, URIBL_PH_SURBL=1.787, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k4TBrmGxE4-3; Sun, 25 Jan 2009 23:54:26 -0800 (PST) Received: from 212-95-32-105.internetserviceteam.com (dxb-as37877.alshamil.net.ae [217.165.26.31]) by core3.amsl.com (Postfix) with SMTP id 4D43428C187; Sun, 25 Jan 2009 23:54:05 -0800 (PST) X-Originating-IP: 251.3.54.232 by smtp.212.95.32.105; Mon, 26 Jan 2009 11:43:29 +0500 Message-ID: <xgm8GFP.28184T969sidr-bounces@ietf.org> Subject: Watches made to impress Date: Mon, 26 Jan 2009 01:52:29 -0500 From: "Emanuel Lamb" <sidr-bounces@ietf.org> To: "Iva Cates" <sidr-bounces@ietf.org> Content-Type: text/plain; Content-Transfer-Encoding: 7bit Dear Iva, If you've waited to get your Omega watch, this is the right time to go for it. http://jreesergubo.12gbfree.com (please click on the link after "Go directly to ") Take advantage of our winter specials and get yourself Omega watch that you've always wanted! http://jreesergubo.12gbfree.com (please click on the link after "Go directly to ") Our Omega watches have all appropriate markings, wordings and engravings same as orginal. Sincerely, Mr Cates From sip-bounces@ietf.org Mon Jan 26 03:49:13 2009 Return-Path: <sip-bounces@ietf.org> X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CAD6028C18C; Mon, 26 Jan 2009 03:49:13 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1EF6E3A6AFF for <sip@core3.amsl.com>; Mon, 26 Jan 2009 03:49:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.938 X-Spam-Level: X-Spam-Status: No, score=-5.938 tagged_above=-999 required=5 tests=[AWL=0.310, 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 FujsZ0vFkmeB for <sip@core3.amsl.com>; Mon, 26 Jan 2009 03:49:11 -0800 (PST) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 645C928C18C for <sip@ietf.org>; Mon, 26 Jan 2009 03:49:09 -0800 (PST) Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id AA92820D11; Mon, 26 Jan 2009 12:48:50 +0100 (CET) X-AuditID: c1b4fb3c-ac75bbb00000304c-60-497da322b7ee Received: from esealmw127.eemea.ericsson.se (unknown [153.88.253.125]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 6A3A020B6C; Mon, 26 Jan 2009 12:48:50 +0100 (CET) Received: from eseldmw101.eemea.ericsson.se ([136.225.228.103]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Mon, 26 Jan 2009 12:48:50 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 26 Jan 2009 12:48:47 +0100 Message-ID: <DA392F15190F9D40BF916AD7146E972E0C0B9327@eseldmw101.eemea.ericsson.se> In-Reply-To: <87278613D061664392F2161B99567B870EF299098F@fmt-qex01.quintum.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: SIP de-REGISTER: Expires header vs expires parameter i Contact Thread-Index: Acl6+jv/20UE0jY8SkKYLXKhRqw4sgAH7RKAASSDTPA= References: <DA392F15190F9D40BF916AD7146E972E0BFDDF05@eseldmw101.eemea.ericsson.se> <87278613D061664392F2161B99567B870EF299098F@fmt-qex01.quintum.com> From: "Gert Olsson" <gert.olsson@ericsson.com> To: "Neelakantan Balasubramanian" <Bala_Neelakantan@Quintum.com>, <sip@ietf.org> X-OriginalArrivalTime: 26 Jan 2009 11:48:50.0110 (UTC) FILETIME=[0DE6C5E0:01C97FAC] X-Brightmail-Tracker: AAAAAA== Subject: Re: [Sip] SIP de-REGISTER: Expires header vs expires parameter i Contact X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol <sip.ietf.org> List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe> List-Post: <mailto:sip@ietf.org> List-Help: <mailto: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="===============0153466733==" Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org This is a multi-part message in MIME format. --===============0153466733== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C97FAC.0CA4AC46" This is a multi-part message in MIME format. ------_=_NextPart_001_01C97FAC.0CA4AC46 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Well, actually I was hoping for a 'yes' or 'no' on the question: "is it FORBIDDEN to have both ?" =20 br =20 /GO=20 __________________________________________________________________|=20 Gert Olsson / phone: +46 10 7154604 / e-mail: gert.olsson@ericsson.com=20 Ericsson AB - Business Unit Mobile Platforms, SE-221 83 Lund, Sweden=20 =20 ________________________________ From: Neelakantan Balasubramanian [mailto:Bala_Neelakantan@Quintum.com]=20 Sent: den 20 januari 2009 17:14 To: Gert Olsson; sip@ietf.org Subject: RE: SIP de-REGISTER: Expires header vs expires parameter i Contact See RFC 3261 Section 10.2.1.1 =20 10.2.1.1 Setting the Expiration Interval of Contact Addresses =20 When a client sends a REGISTER request, it MAY suggest an expiration interval that indicates how long the client would like the registration to be valid. (As described in Section 10.3, the registrar selects the actual time interval based on its local policy.) =20 There are two ways in which a client can suggest an expiration interval for a binding: through an Expires header field or an "expires" Contact header parameter. The latter allows expiration intervals to be suggested on a per-binding basis when more than one binding is given in a single REGISTER request, whereas the former suggests an expiration interval for all Contact header field values that do not contain the "expires" parameter. =20 Thanks, Neel. =20 From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of Gert Olsson Sent: Tuesday, January 20, 2009 6:26 AM To: sip@ietf.org Subject: [Sip] SIP de-REGISTER: Expires header vs expires parameter i Contact =20 Hi,=20 SIP de-registration is performed by sending a REGISTER message with either a Contact header containing an 'expires=3D0' parameter or an Expires header with value 0. My question is: is it FORBIDDEN to have both? Shouldn't any decent server, if it has found 'expires=3D0' in the Contact header (or in all if many), just happily ignore an Expires header? [Neelakantan Bala]=20 See RFC 3261 Section 10.2.1.1 =20 10.2.1.1 Setting the Expiration Interval of Contact Addresses =20 When a client sends a REGISTER request, it MAY suggest an expiration interval that indicates how long the client would like the registration to be valid. (As described in Section 10.3, the registrar selects the actual time interval based on its local policy.) =20 There are two ways in which a client can suggest an expiration interval for a binding: through an Expires header field or an "expires" Contact header parameter. The latter allows expiration intervals to be suggested on a per-binding basis when more than one binding is given in a single REGISTER request, whereas the former suggests an expiration interval for all Contact header field values that do not contain the "expires" parameter. =20 Thanks, Neel. =20 br=20 /GO=20 __________________________________________________________________|=20 Gert Olsson / phone: +46 10 7154604 / e-mail: gert.olsson@ericsson.com=20 Ericsson AB - Business Unit Mobile Platforms, SE-221 83 Lund, Sweden=20 =20 ------_=_NextPart_001_01C97FAC.0CA4AC46 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20 "urn:schemas-microsoft-com:vml" xmlns:o =3D=20 "urn:schemas-microsoft-com:office:office" xmlns:w =3D=20 "urn:schemas-microsoft-com:office:word" xmlns:m =3D=20 "http://schemas.microsoft.com/office/2004/12/omml"><HEAD><TITLE>SIP = de-REGISTER: Expires header vs expires parameter i Contact
Hi,
Well, actually I = was hoping=20 for a 'yes' or 'no' on the question:
"is=20 it FORBIDDEN to have both ?"
 
br
 

/GO
________________________________________________________________= __|=20
Gert = Olsson  =20 /  phone: +46 10 7154604   /  e-mail:=20 gert.olsson@ericsson.com
Ericsson AB - Business Unit Mobile Platforms, = SE-221=20 83  Lund, Sweden

 

From: Neelakantan Balasubramanian=20 [mailto:Bala_Neelakantan@Quintum.com]
Sent: den 20 januari = 2009=20 17:14
To: Gert Olsson; sip@ietf.org
Subject: RE: SIP = de-REGISTER: Expires header vs expires parameter i = Contact

See=20 RFC 3261 Section 10.2.1.1

 

10.2.1.1=20 Setting the Expiration Interval of Contact = Addresses

 

  =20 When a client sends a REGISTER request, it MAY suggest an=20 expiration

  =20 interval that indicates how long the client would like = the

  =20 registration to be valid.  (As described in Section 10.3,=20 the

  =20 registrar selects the actual time interval based on its=20 local

  =20 policy.)

 

  =20 There are two ways in which a client can suggest an=20 expiration

  =20 interval for a binding: through an Expires header field or=20 an

  =20 "expires" Contact header parameter.  The latter allows=20 expiration

  =20 intervals to be suggested on a per-binding basis when more than=20 one

  =20 binding is given in a single REGISTER request, whereas the=20 former

  =20 suggests an expiration interval for all Contact header field=20 values

  =20 that do not contain the "expires" parameter.

 

Thanks,

Neel.

 

From:=20 sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of = Gert=20 Olsson
Sent: Tuesday, January 20, 2009 6:26 AM
To:=20 sip@ietf.org
Subject: [Sip] SIP de-REGISTER: Expires header vs = expires=20 parameter i Contact

 

Hi,=20

SIP = de-registration=20 is performed by sending a REGISTER message with either a Contact header=20 containing an 'expires=3D0' parameter or an Expires header with value 0. = My=20 question is: is it FORBIDDEN to have both? Shouldn't any decent server, = if it=20 has found 'expires=3D0' in the Contact header (or in all if many), just = happily=20 ignore an Expires header?

[Neelakantan=20 Bala]

See=20 RFC 3261 Section 10.2.1.1

 

10.2.1.1=20 Setting the Expiration Interval of Contact = Addresses

 

  =20 When a client sends a REGISTER request, it MAY suggest an=20 expiration

  =20 interval that indicates how long the client would like = the

  =20 registration to be valid.  (As described in Section 10.3,=20 the

  =20 registrar selects the actual time interval based on its=20 local

  =20 policy.)

 

  =20 There are two ways in which a client can suggest an=20 expiration

  =20 interval for a binding: through an Expires header field or=20 an

  =20 "expires" Contact header parameter.  The latter allows=20 expiration

  =20 intervals to be suggested on a per-binding basis when more than=20 one

  =20 binding is given in a single REGISTER request, whereas the=20 former

  =20 suggests an expiration interval for all Contact header field=20 values

  =20 that do not contain the "expires" parameter.

 

Thanks,

Neel.

 

br =

/GO=20
___________________________________________________= _______________|=20
Gert=20 Olsson   /  phone: +46 10 7154604   /  = e-mail:=20 gert.olsson@ericsson.com
Ericsson=20 AB - Business Unit Mobile Platforms, SE-221 83  Lund, Sweden =

 

------_=_NextPart_001_01C97FAC.0CA4AC46-- --===============0153466733== 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 --===============0153466733==-- From sip-bounces@ietf.org Mon Jan 26 08:19:02 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BC7803A6AB1; Mon, 26 Jan 2009 08:19:02 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 17EF53A6AB1 for ; Mon, 26 Jan 2009 08:19:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.467 X-Spam-Level: X-Spam-Status: No, score=-6.467 tagged_above=-999 required=5 tests=[AWL=0.132, 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 kshV6LGsg+ZR for ; Mon, 26 Jan 2009 08:19:00 -0800 (PST) Received: from zrtps0kn.nortel.com (zrtps0kn.nortel.com [47.140.192.55]) by core3.amsl.com (Postfix) with ESMTP id 3A0013A6807 for ; Mon, 26 Jan 2009 08:19:00 -0800 (PST) Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n0QGIbQ25042; Mon, 26 Jan 2009 16:18:37 GMT Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 26 Jan 2009 11:18:37 -0500 From: "Dale Worley" To: Gert Olsson In-Reply-To: References: <87278613D061664392F2161B99567B870EF299098F@fmt-qex01.quintum.com> Organization: Nortel Networks Date: Mon, 26 Jan 2009 11:18:36 -0500 Message-Id: <1232986716.4042.3.camel@victoria-pingtel-com.us.nortel.com> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8) X-OriginalArrivalTime: 26 Jan 2009 16:18:37.0605 (UTC) FILETIME=[BE667D50:01C97FD1] Cc: sip@ietf.org, Neelakantan Balasubramanian Subject: Re: [Sip] SIP de-REGISTER: Expires header vs expires parameter i Contact X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org On Mon, 2009-01-26 at 12:48 +0100, Gert Olsson wrote: > Well, actually I was hoping for a 'yes' or 'no' on the question: > "is it FORBIDDEN to have both ?" You may have both. 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 Jan 26 09:28:56 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7FF7628C24E; Mon, 26 Jan 2009 09:28:56 -0800 (PST) X-Original-To: sip@ietf.org Delivered-To: sip@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id 68D243A6AD6; Mon, 26 Jan 2009 09:28:54 -0800 (PST) X-idtracker: yes From: The IESG To: IETF-Announce Message-Id: <20090126172854.68D243A6AD6@core3.amsl.com> Date: Mon, 26 Jan 2009 09:28:54 -0800 (PST) Cc: sip mailing list , sip chair , Internet Architecture Board , RFC Editor Subject: [Sip] Protocol Action: 'IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespaces' to Proposed Standard X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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 approved the following document: - 'IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespaces ' as a Proposed Standard This document is the product of the Session Initiation Protocol Working Group. The IESG contact persons are Cullen Jennings and Jon Peterson. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sip-rph-new-namespaces-04.txt Technical summary. 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. Working group summary. There is consensus in the working group to publish this document. Document Quality The document has received review by experts in the field as well as members of the SIP working group. Personnel The document shepherd for this document was Keith Drage. The responsible Area Director was Cullen Jennings. RFC Editor Note Change the 2nd bullet in the Intro (after paragraph 2) : OLD - some departments within the government (Homeland Security, Commerce, Treasury) NEW - some departments within the government (for example, Homeland Security) In the 3rd bullet below what I ask to change above, make this change "s/plus/to" with no other changes to that bullet (just the first word). In the 3rd paragraph of section 2, there is this text: OLD "... registered namespaces, not just adjacent namespaces." NEW "... registered namespaces, not just adjacent (i.e., consecutive) namespaces. _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.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 Jan 26 12:14:19 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5365C3A6B01; Mon, 26 Jan 2009 12:14:19 -0800 (PST) X-Original-To: sip@ietf.org Delivered-To: sip@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id 11F8D3A6880; Mon, 26 Jan 2009 12:14:16 -0800 (PST) X-idtracker: yes From: The IESG To: IETF-Announce Message-Id: <20090126201417.11F8D3A6880@core3.amsl.com> Date: Mon, 26 Jan 2009 12:14:17 -0800 (PST) Cc: sip mailing list , sip chair , Internet Architecture Board , RFC Editor Subject: [Sip] Document Action: 'Requirements and Analysis of Media Security Management Protocols' to Informational RFC X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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 approved the following document: - 'Requirements and Analysis of Media Security Management Protocols ' as an Informational RFC This document is the product of the Session Initiation Protocol Working Group. The IESG contact persons are Cullen Jennings and Jon Peterson. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sip-media-security-requirements-09.txt Technical Summary 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. Working Group Summary There was considerable controvery about the inclusion of requirements related to key disclosure. Document Quality Security adviser Eric Rescorla was actively involved in reviewing the requirements, as they apply to the SRTP/DTLS framework for which he is the editor. Personnel The Proto Shepherd is Dean Willis. The Responsible Area Director is Cullen Jennings. No IANA experts are required. RFC Editor Note Please review the comments in the tracker. If the RFC Editor agrees with them, they seemed like a good edition to me. _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip From sip-cargo@iourpakh.ru Mon Jan 26 22:48:20 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 98BC53A684D for ; Mon, 26 Jan 2009 22:48:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -62.431 X-Spam-Level: X-Spam-Status: No, score=-62.431 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, GB_I_LETTER=-2, HELO_MISMATCH_COM=0.553, HOST_EQ_BROADBND=1.118, HOST_EQ_RU=0.875, HTML_EXTRA_CLOSE=2.809, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_3=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, SARE_UNI=0.591, URIBL_SBL=20, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sioEoUCGfjEI for ; Mon, 26 Jan 2009 22:48:20 -0800 (PST) Received: from amerblind.outbound.ed10.com (89-138-14-184.bb.netvision.net.il [89.138.14.184]) by core3.amsl.com (Postfix) with SMTP id 032BB3A6816 for ; Mon, 26 Jan 2009 22:48:12 -0800 (PST) Content-Return: allowed X-Mailer: devMail.Net (3.0.1854.22234-2) To: sip-archive@ietf.org Subject: RE: Message 83294 From: Canadian Pharmacy id1978 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: 7bit Message-Id: <20090127064814.032BB3A6816@core3.amsl.com> Date: Mon, 26 Jan 2009 22:48:12 -0800 (PST)
Click Here!
About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

©2009 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 98052
From sip-bounces@ietf.org Tue Jan 27 02:15:03 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 57F0728C0E7; Tue, 27 Jan 2009 02:15:03 -0800 (PST) X-Original-To: sip@ietf.org Delivered-To: sip@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 6EA623A692A; Tue, 27 Jan 2009 02:15:02 -0800 (PST) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20090127101502.6EA623A692A@core3.amsl.com> Date: Tue, 27 Jan 2009 02:15:02 -0800 (PST) Cc: sip@ietf.org Subject: [Sip] I-D Action:draft-ietf-sip-info-events-03.txt X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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-03.txt Pages : 37 Date : 2009-01-27 This document defines the new SIP INFO method and a mechanism for defining, negotiating and exchanging Info Packages that use the INFO method. Applications that need to exchange session-related information within a SIP INVITE-created dialog, also known as application level information, 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]. The terminology in this document conforms to the Internet Security Glossary [RFC4949]. Be mindful of the terms User Agent Server (UAS) and User Agent Client (UAC). This document strictly follows RFC 3261 [RFC3261]. The UAC issues a SIP request and the UAS responds. This terminology may be confusing when one combines the INFO case with the INVITE case. For an INVITE, the initiator of the session is the UAC and the target of the session is the UAS. However, it is possible for the target UA of the session, the UAS of the INVITE transaction, to send an INFO to the initiating UA of the session, the UAC of the INVITE transaction. >From the perspective of the INFO, the target UA of the session (INVITE UAS) is, in fact, the UAC (sender) of the INFO request. Likewise, from the perspective of the INFO, the initiating UA of the session (INVITE UAC) is the UAS (recipient) of the INFO request. Since this document strictly follows RFC 3261, we refer to the UA that issues the INVITE as the "initiating UA" and the UA that responds to the INVITE as the "target UA" to remove any confusion. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-sip-info-events-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-info-events-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-01-27020932.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 dhuete@huetemortgage.com Wed Jan 28 01:11:20 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8829B28C1FE; Wed, 28 Jan 2009 01:11:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -63.743 X-Spam-Level: X-Spam-Status: No, score=-63.743 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RDNS_NONE=0.1, SUBJECT_FUZZY_TION=0.156, URIBL_AB_SURBL=10, URIBL_BLACK=20, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3nouj0HuawSB; Wed, 28 Jan 2009 01:11:19 -0800 (PST) Received: from CUSTOMER.VPLS.NET (unknown [212.156.208.222]) by core3.amsl.com (Postfix) with SMTP id D9FD028C0FA; Wed, 28 Jan 2009 01:10:44 -0800 (PST) X-Originating-IP: 110.206.160.240 by smtp.116.133.153.231; Wed, 28 Jan 2009 03:09:26 -0600 Message-ID: Subject: Inexpensive Louis Vuitton bags Date: Wed, 28 Jan 2009 04:10:26 -0500 From: "Judy Eldridge" To: "Derrick Benavides" Content-Type: text/plain; Content-Transfer-Encoding: 7bit Dear Derrick, If you've waited to get your Longines watch, this is the right time to go for it. http://mrhoades6nabi.hostmo.com Get two deeply discounted watches and take an extra 15% discount. http://mrhoades6nabi.hostmo.com Our Longines watches have Weights/feels and looks exactly same as original. Sincerely, Mr Benavides From sip-bounces@ietf.org Wed Jan 28 03:18:33 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EE33228C12D; Wed, 28 Jan 2009 03:18:32 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1A97C28C10F for ; Wed, 28 Jan 2009 03:18:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.123 X-Spam-Level: X-Spam-Status: No, score=-6.123 tagged_above=-999 required=5 tests=[AWL=0.126, BAYES_00=-2.599, HELO_EQ_FR=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 QQN1ufVXa3kX for ; Wed, 28 Jan 2009 03:18:30 -0800 (PST) Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id DE37528C112 for ; Wed, 28 Jan 2009 03:18:28 -0800 (PST) Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n0SBI54c026190 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Wed, 28 Jan 2009 12:18:05 +0100 Received: from FRMRSSXCHMBSB3.dc-m.alcatel-lucent.com ([135.120.45.41]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Wed, 28 Jan 2009 12:18:05 +0100 From: "DRAGE, Keith (Keith)" To: SIP List Date: Wed, 28 Jan 2009 12:18:03 +0100 Thread-Topic: Notes of conference call of group working on identity Thread-Index: AcmBOhX1m/gthhE5QMKZYvr+/uOqWw== Message-ID: <28B7C3AA2A7ABA4A841F11217ABE78D67495B3C4@FRMRSSXCHMBSB3.dc-m.alcatel-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 X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13 Subject: [Sip] Notes of conference call of group working on identity X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org Attached find the notes of a conference call of the informal group working on identity. If any members of the SIP WG want to participate in this issue, then please send me an email and I will send the details. If you have any comments on the draft identified in the notes, then please send them to the list and John Elwell. We are planning on an agenda item on this in San Francisco and are working on this identifying the problem. regards Keith ---------------------------- A conference call was held Tuesday 27th January 2009 amongst interested parties. Present: Keith Drage Dean Willis Hadriel Kaplan Cullen Jennings John Elwell Kai Fischer Hannes Tschofenig Eric Rescorla Dan York Dan Wing [and anyone else who joined after the roll call] Keith identified the purpose of the call was to bring up to speed some of the people who had not been on the previous call. Cullen questioned the use of the term "design team" which he had seen floating round. Keith identified that the group had no status beyond being that of a group of interested parties who were trying to capture in a document the problem that needed to be solved with identity, with the aim that this document would be presented in a WG meeting and hopefully result in some form of work being chartered to go forward. Keith believed that the term "design team" encompassed that but Cullen did not. In any case, the key think here is that this is currently informal work and what will be going as input to the WG from the group will only be the document we are currently working on. The draft will not mention the term "design team". John gave a presentation of draft-elwell-sip-e2e-important-02 for the benefit of the new participants. Cullen requested some sort of summary table at the end of section 7. John proposed that more detail needed to be added to the conclusion, and proposed to split this into two parts. One part would cover e2e identity with non-e164 identities and the other would cover it with e164 identities. EKR stated that when one builds a security system, one needs to look at what damange is allowed. Cullen wanted to know what are the middle boxes allowed to break. Keith indicated that it is not the function of this discussion to define SBC functions; there is a SIPPING document that does exactly that. Rather we need to take that document and identify what impact the functions defined in that document have on identity. If anything is missed in that process, that should possibly be a correction to the SIPPING document. Part of the discussion averred that Call-ID and CSeq could be allowed to break; CSeq currently not covered by the document. There was discussion around whose needs were being supported by the intervening SBC boxes, the service being provided to the calling user or the called user, or whether the changes were being made on behalf of some other entity. There was agreement that we should analyse in more detail specific header fields and body types, and the impact of SBCs on the identity characteristics of those elements. This will need to go into detail on the contents, for example, rather than a blanket change of a URI to a different URI, what is the impact of changing a URI to say an alias of that URI, or adding a "+" where one currently does not exist. Hadriel generally called these changes "protocol repair". Dan indicated that all current solutions break in some way, and we need to find a way round that. Agreed that we need to identity changes that can be considered "legitimate" changes where we expect the solution to work, versus "illegitimate" changes, where any solution will not be expected to work. Ihe call came up with some areas where the document should be revised and John would attempt to capture those suggestions in a revised version of the document. Target date for new version of the document was 10th February so it could be discussed on our next call on 17th February. John made a plea for input to the draft in the form of words targetted at the 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 klionelmicky@7-10.com Wed Jan 28 20:20:51 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7C7D73A67D8 for ; Wed, 28 Jan 2009 20:20:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.655 X-Spam-Level: X-Spam-Status: No, score=-16.655 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_ALMOST_IP=5.417, FH_HOST_ALMOST_IP=1.889, GB_I_LETTER=-2, HELO_EQ_FR=0.35, HTML_IMAGE_ONLY_32=1.778, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_SC_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WasLQy8NERql for ; Wed, 28 Jan 2009 20:20:50 -0800 (PST) Received: from abo-83-175-68.bab.modulonet.fr (abo-83-175-68.bab.modulonet.fr [85.68.175.83]) by core3.amsl.com (Postfix) with SMTP id CAE8D3A6768 for ; Wed, 28 Jan 2009 20:20:49 -0800 (PST) To: Subject: Welcome to eBay! From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090129042049.CAE8D3A6768@core3.amsl.com> Date: Wed, 28 Jan 2009 20:20:49 -0800 (PST)
We ship Worldwide! To all countries! To all destinations!
Cant see a picture? Click Here!

To unsubscribe from this mailing list, please log in to www.answerquiet.com, click on "My Account", click "Update" to edit your registration details and uncheck the "Receive Newsletter?" check box.
Or unsubscribe at http://answerquiet.com/faq.php

Privacy Statement | Terms & Conditions | Contact

KEYWORD Ltd.
Tower Bridge Business Complex. Unit 4, B583. 137 Clements Road. London. SE38 2DG

© 2006-2008 KEYWORD, Ltd. All Rights Reserved

From chuck@shelamer.com Thu Jan 29 06:21:00 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A6C3428C119; Thu, 29 Jan 2009 06:21:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -49.837 X-Spam-Level: X-Spam-Status: No, score=-49.837 tagged_above=-999 required=5 tests=[BAYES_95=3, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, HELO_MISMATCH_NET=0.611, HOST_EQ_PL=1.95, RDNS_DYNAMIC=0.1, SARE_SPEC_ROLEX_NOV5A=1.062, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_PH_SURBL=1.787, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pEwIxPRnk3Nf; Thu, 29 Jan 2009 06:20:59 -0800 (PST) Received: from CUSTOMER.VPLS.NET (83-1-13-185.informel.pl [83.1.13.185]) by core3.amsl.com (Postfix) with SMTP id 333343A6AA7; Thu, 29 Jan 2009 06:20:42 -0800 (PST) Message-ID: <9157T473.2451466sidr-bounces@ietf.org> Date: Thu, 29 Jan 2009 09:20:22 -0500 From: "Roberta Lyon" To: "Jeanie Newman" Subject: Breitling watch models from 2009! Content-Type: text/plain; Content-Transfer-Encoding: 7bit Dear Jeanie, Money is tight, times are hard. Christmas is over. Time to get a new Watch! http://tiponicaqibu.k2free.com So, come visit Prestige Reps, the famous watch-portal where thousands of satisfied customers have already found that superb imitation time piece for just a few hundred dollars. http://tiponicaqibu.k2free.com Enjoy the fastest shipping around, paired with secure billing, incredible customer service and the largest online selection of fine reproduction timepiece… only at Prestige Reps, of course! Sincerely, Mr Newman From sip-bounces@ietf.org Thu Jan 29 10:53:53 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A0AC93A6A56; Thu, 29 Jan 2009 10:53:53 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A38873A69CE for ; Thu, 29 Jan 2009 10:53:51 -0800 (PST) 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.650, 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 v5nCnxNKjvHt for ; Thu, 29 Jan 2009 10:53:50 -0800 (PST) Received: from zcars04f.nortel.com (zcars04f.nortel.com [47.129.242.57]) by core3.amsl.com (Postfix) with ESMTP id AD7213A684A for ; Thu, 29 Jan 2009 10:53:50 -0800 (PST) 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 n0TIrQv05568; Thu, 29 Jan 2009 18:53:27 GMT X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 29 Jan 2009 12:52:33 -0600 Message-ID: <1ECE0EB50388174790F9694F77522CCF1BF07428@zrc2hxm0.corp.nortel.com> In-Reply-To: <1232986716.4042.3.camel@victoria-pingtel-com.us.nortel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Sip] SIP de-REGISTER: Expires header vs expires parameteri Contact Thread-Index: Acl/0c1YgfbCONC8SImAWykLWQ13RwCcMR6A References: <87278613D061664392F2161B99567B870EF299098F@fmt-qex01.quintum.com> <1232986716.4042.3.camel@victoria-pingtel-com.us.nortel.com> From: "Francois Audet" To: "Dale Worley" , "Gert Olsson" Cc: sip@ietf.org, Neelakantan Balasubramanian Subject: Re: [Sip] SIP de-REGISTER: Expires header vs expires parameteri Contact X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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 if you have both, the one in the contact takes precedence. That allows you to have X+1 contacts, where X use the same expiry, and the other uses a per-contact expiry. That would be my take. > -----Original Message----- > From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On > Behalf Of Worley, Dale (BL60:9D30) > Sent: Monday, January 26, 2009 08:19 > To: Gert Olsson > Cc: sip@ietf.org; Neelakantan Balasubramanian > Subject: Re: [Sip] SIP de-REGISTER: Expires header vs expires > parameteri Contact > > On Mon, 2009-01-26 at 12:48 +0100, Gert Olsson wrote: > > Well, actually I was hoping for a 'yes' or 'no' on the question: > > "is it FORBIDDEN to have both ?" > > You may have both. > > 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 mikebecker@alrinc.com Thu Jan 29 14:18:41 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 262153A6814 for ; Thu, 29 Jan 2009 14:18:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -46.2 X-Spam-Level: X-Spam-Status: No, score=-46.2 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_RELAY_NODNS=1.451, GB_I_LETTER=-2, HELO_EQ_FR=0.35, HELO_IS_SMALL6=0.556, HTML_IMAGE_ONLY_32=1.778, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_WEB=0.619, RDNS_NONE=0.1, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_RHS_DOB=1.083, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aeqqh-jPqPNT for ; Thu, 29 Jan 2009 14:18:40 -0800 (PST) Received: from absi.fr (unknown [88.230.66.209]) by core3.amsl.com (Postfix) with SMTP id 39B8D3A67B4 for ; Thu, 29 Jan 2009 14:18:38 -0800 (PST) To: Subject: Order Shipped -- Order #94653 From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090129221839.39B8D3A67B4@core3.amsl.com> Date: Thu, 29 Jan 2009 14:18:38 -0800 (PST)
We ship Worldwide! To all countries! To all destinations!
Cant see a picture? Click Here!

To unsubscribe from this mailing list, please log in to www.juicypious.com, click on "My Account", click "Update" to edit your registration details and uncheck the "Receive Newsletter?" check box.
Or unsubscribe at http://juicypious.com/faq.php

Privacy Statement | Terms & Conditions | Contact

KEYWORD Ltd.
Tower Bridge Business Complex. Unit 6, B099. 434 Clements Road. London. SE66 3DG

© 2006-2008 KEYWORD, Ltd. All Rights Reserved

From sip-bounces@ietf.org Fri Jan 30 00:57:28 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 019343A6A4D; Fri, 30 Jan 2009 00:57:28 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 363E03A6A4D for ; Fri, 30 Jan 2009 00:57:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.972 X-Spam-Level: X-Spam-Status: No, score=0.972 tagged_above=-999 required=5 tests=[AWL=-0.624, BAYES_50=0.001, J_CHICKENPOX_74=0.6, RELAY_IS_203=0.994, STOX_REPLY_TYPE=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 doj4lLI537n0 for ; Fri, 30 Jan 2009 00:57:25 -0800 (PST) Received: from gesmail.globaledgesoft.com (gesmail.globaledgesoft.com [203.76.137.4]) by core3.amsl.com (Postfix) with ESMTP id 4FE433A6AB1 for ; Fri, 30 Jan 2009 00:57:24 -0800 (PST) Received: from MaheshAwaradi (unknown [172.16.7.101]) by gesmail.globaledgesoft.com (Postfix) with SMTP id 0FEA4A3AE4 for ; Fri, 30 Jan 2009 14:26:59 +0530 (IST) Message-ID: <002701c982b8$75a4ae90$650710ac@globaledgesoft.com> From: "Mahesh" To: References: Date: Fri, 30 Jan 2009 14:25:11 +0530 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 Subject: [Sip] gateway(like Gtalk toVoip) X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-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 All, can any body tell me ,is there any gateway(like Gtalk toVoip) so that i can communicate between my sip phone to yahoo messenger. Regards Mahesh _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.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 Jan 30 02:13:06 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D7BFF3A6AAB; Fri, 30 Jan 2009 02:13:06 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9DD6F3A6AAB for ; Fri, 30 Jan 2009 02:13:05 -0800 (PST) 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 mvuT9dKMLRHm for ; Fri, 30 Jan 2009 02:13:04 -0800 (PST) Received: from mail55.messagelabs.com (mail55.messagelabs.com [216.82.241.163]) by core3.amsl.com (Postfix) with SMTP id 930E93A6A9B for ; Fri, 30 Jan 2009 02:13:04 -0800 (PST) X-VirusChecked: Checked X-Env-Sender: ranjit@motorola.com X-Msg-Ref: server-11.tower-55.messagelabs.com!1233310365!31331994!1 X-StarScan-Version: 6.0.0; banners=-,-,- X-Originating-IP: [136.182.1.15] Received: (qmail 10486 invoked from network); 30 Jan 2009 10:12:45 -0000 Received: from unknown (HELO motgate5.mot.com) (136.182.1.15) by server-11.tower-55.messagelabs.com with SMTP; 30 Jan 2009 10:12:45 -0000 Received: from il27exr04.cig.mot.com ([10.17.196.73]) by motgate5.mot.com (8.12.11/Motorola) with ESMTP id n0UACdZV016320 for ; Fri, 30 Jan 2009 03:12:45 -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 n0UACctX004583 for ; Fri, 30 Jan 2009 04:12:38 -0600 (CST) 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 n0UACbn7004570 for ; Fri, 30 Jan 2009 04:12:38 -0600 (CST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 30 Jan 2009 18:12:35 +0800 Message-ID: <750BBC72E178114F9DC4872EBFF29A5B05ED5357@ZMY16EXM66.ds.mot.com> In-Reply-To: <002701c982b8$75a4ae90$650710ac@globaledgesoft.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Sip] gateway(like Gtalk toVoip) thread-index: AcmCuMiTMbzk9tWfR6KxA7iJDGDV8AACjO5w References: <002701c982b8$75a4ae90$650710ac@globaledgesoft.com> From: "Avasarala Ranjit-A20990" To: "Mahesh" , X-CFilter-Loop: Reflected Subject: Re: [Sip] gateway(like Gtalk toVoip) X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org Did not understand what exactly you want to do >From yahoo messenger you can make VoIP calls using SIP if Yahoo messenger supports SIP. Regards Ranjit -----Original Message----- From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of Mahesh Sent: Friday, January 30, 2009 2:25 PM To: sip@ietf.org Subject: [Sip] gateway(like Gtalk toVoip) Hi All, can any body tell me ,is there any gateway(like Gtalk toVoip) so that i can communicate between my sip phone to yahoo messenger. Regards Mahesh _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP 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 Jan 30 02:35:56 2009 Return-Path: X-Original-To: sip-archive@optimus.ietf.org Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E74983A68EC; Fri, 30 Jan 2009 02:35:55 -0800 (PST) X-Original-To: sip@core3.amsl.com Delivered-To: sip@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7CF183A6A87 for ; Fri, 30 Jan 2009 02:35:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.363 X-Spam-Level: X-Spam-Status: No, score=-1.363 tagged_above=-999 required=5 tests=[AWL=0.336, BAYES_00=-2.599, J_CHICKENPOX_74=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 B4+jeZ3a+bXE for ; Fri, 30 Jan 2009 02:35:53 -0800 (PST) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.184]) by core3.amsl.com (Postfix) with ESMTP id 8BE9D3A68EC for ; Fri, 30 Jan 2009 02:35:53 -0800 (PST) Received: by fk-out-0910.google.com with SMTP id f33so390208fkf.5 for ; Fri, 30 Jan 2009 02:35:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=UzXau2u5RhHtNckqqDMZ9eEVrCbibsw0GUXQSlqmiI8=; b=CMfGTII2rrIiRquhZQoxWacUup+bkDv4mVKJLp46lNtpE3WghAqNa62NgV4DoNx7SK rha/2I1RggzQo4xG+MJWW2xrF7AnWxldh8653vx+IP7kl5VrIWMHZXEliK34+xOZZNSZ 859oHv+7kKsMzOoYN34/jRRmo0ATBmNqqXY+8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=wkvBPWEQd3GHVXW6HdAuIXUXLCs1A0zs1Cf9UJGqc2/FKNDRTkVYjwWF+dM/M5Zg/o fJOSgn7jAMhz9sXuBGGggGRUOkdM5Hpbt0bpF8l86v/t/1pkUjwcQmN1XFQ54/vLWQDB tBHvSvjjhDNzN2MHlIVwHc/7BDjRj5o1oJ17c= MIME-Version: 1.0 Received: by 10.181.20.6 with SMTP id x6mr379922bki.167.1233311733949; Fri, 30 Jan 2009 02:35:33 -0800 (PST) In-Reply-To: <750BBC72E178114F9DC4872EBFF29A5B05ED5357@ZMY16EXM66.ds.mot.com> References: <002701c982b8$75a4ae90$650710ac@globaledgesoft.com> <750BBC72E178114F9DC4872EBFF29A5B05ED5357@ZMY16EXM66.ds.mot.com> Date: Fri, 30 Jan 2009 11:35:33 +0100 Message-ID: <618e24240901300235w4df5d4b0mb4e994ce5adbdf17@mail.gmail.com> From: =?UTF-8?Q?Victor_Pascual_=C3=81vila?= To: Avasarala Ranjit-A20990 Cc: sip@ietf.org, Mahesh Subject: Re: [Sip] gateway(like Gtalk toVoip) X-BeenThere: sip@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Session Initiation Protocol List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: sip-bounces@ietf.org Errors-To: sip-bounces@ietf.org SGkgTWFoZXNoLAoKT24gRnJpLCBKYW4gMzAsIDIwMDkgYXQgMTE6MTIgQU0sIEF2YXNhcmFsYSBS YW5qaXQtQTIwOTkwCjxyYW5qaXRAbW90b3JvbGEuY29tPiB3cm90ZToKPiBEaWQgbm90IHVuZGVy c3RhbmQgd2hhdCBleGFjdGx5IHlvdSB3YW50IHRvIGRvCj4KPiBGcm9tIHlhaG9vIG1lc3Nlbmdl ciB5b3UgY2FuIG1ha2UgVm9JUCBjYWxscyB1c2luZyBTSVAgaWYgWWFob28KPiBtZXNzZW5nZXIg c3VwcG9ydHMgU0lQLgoKUHVycGxlL2xpYnB1cnBsZSBpcyBhIGh1bWJsZSBnYXRld2F5IGJldHdl ZW4gU0lQIGFuZCBNU04vTGl2ZQpuZXR3b3Jrcy0tIG5vdCBzdXJlIGlmIHJldXNhYmxlIGZvciB5 YWhvby4KCmh0dHA6Ly9rYW1haWxpby5vcmcvZG9jcy9tb2R1bGVzL2RldmVsL3B1cnBsZS5odG1s CgpQUzogUGxlYXNlIHBvc3Qgc3VjaCBxdWVzdGlvbnMgdG8gc2lwLWltcGxlbWVudG9ycyBtYWls aW5nIGxpc3QKKHNpcC1pbXBsZW1lbnRvcnNAY3MuY29sdW1iaWEuZWR1KQoKUmVnYXJkcywKLS0g ClZpY3RvciBQYXNjdWFsIMOBdmlsYQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXwpTaXAgbWFpbGluZyBsaXN0ICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWls bWFuL2xpc3RpbmZvL3NpcApUaGlzIGxpc3QgaXMgZm9yIE5FVyBkZXZlbG9wbWVudCBvZiB0aGUg Y29yZSBTSVAgUHJvdG9jb2wKVXNlIHNpcC1pbXBsZW1lbnRvcnNAY3MuY29sdW1iaWEuZWR1IGZv ciBxdWVzdGlvbnMgb24gY3VycmVudCBzaXAKVXNlIHNpcHBpbmdAaWV0Zi5vcmcgZm9yIG5ldyBk ZXZlbG9wbWVudHMgb24gdGhlIGFwcGxpY2F0aW9uIG9mIHNpcA== From pettybooka@sister.co.jp Fri Jan 30 12:20:46 2009 Return-Path: X-Original-To: ietfarch-sip-archive@core3.amsl.com Delivered-To: ietfarch-sip-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 82C7528C0E5; Fri, 30 Jan 2009 12:20:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -54.594 X-Spam-Level: X-Spam-Status: No, score=-54.594 tagged_above=-999 required=5 tests=[BAYES_99=3.5, HELO_MISMATCH_NET=0.611, HOST_EQ_BR=1.295, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_SC_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s0ShQhKIaAr1; Fri, 30 Jan 2009 12:20:45 -0800 (PST) Received: from CUSTOMER.VPLS.NET (popmh.unoescmh.edu.br [201.14.179.100]) by core3.amsl.com (Postfix) with SMTP id 41B223A6825; Fri, 30 Jan 2009 12:20:08 -0800 (PST) Message-ID: <702R554.9846002sidr-bounces@ietf.org> Date: Fri, 30 Jan 2009 15:19:45 -0500 From: "Forest Velazquez" To: "Christian Chase" Subject: Why rep watches are better Content-Type: text/plain; Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 080711-0, 11/07/2008), Outbound message X-Antivirus-Status: Clean Dear Christian, Why waste your hard-earned money on an expensive watch when you can have the next best thing for a tenth of its price? http://mill7joshrare.freehostingz.com The watch of your dreams doesn't have to be an overpriced piece of machinery. Nowadays you can get the same functionality and distinctive looks from the next best thing. Vi it Pres ge Reps and choose from hundreds of gorgeous models at less than ten percent the price of an original. http://mill7joshrare.freehostingz.com Don't delay your pleasure: our incredible watch collection awaits you at Prest ge Reps, so come vi it us n w! Sincerely, Mr Chase