Hi,

I have submitted a n= ew version of the draft to refresh it, and added a new section, section 1.5= , that made it explicit that this document will only cover the Proxy-to-Use= r authentication, but not the User-to-User authentication which is cover by= the mechanism defined in STIR.

https://datatrack= er.ietf.org/doc/draft-yusef-sipcore-sip-oauth/

I am planning in resuming the SIP OAuth discussion and = its use cases in the coming few weeks.

Regards,

=A0Rifaat

--089e013cb9ccdfff6e0513a42db2-- From nobody Mon Apr 20 08:45:39 2015 Return-Path: X-Original-To: sipcore@ietfa.amsl.com Delivered-To: sipcore@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7F2A1B2B5D for ; Mon, 20 Apr 2015 08:45:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pKaQPC4f9K-s for ; Mon, 20 Apr 2015 08:45:37 -0700 (PDT) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 851D11B2F20 for ; Mon, 20 Apr 2015 08:45:36 -0700 (PDT) Received: from unnumerable.local (pool-71-170-237-80.dllstx.fios.verizon.net [71.170.237.80]) (authenticated bits=0) by nostrum.com (8.15.1/8.14.9) with ESMTPSA id t3KFjZId019103 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 20 Apr 2015 10:45:36 -0500 (CDT) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host pool-71-170-237-80.dllstx.fios.verizon.net [71.170.237.80] claimed to be unnumerable.local Message-ID: <55351F1B.1040200@nostrum.com> Date: Mon, 20 Apr 2015 10:45:31 -0500 From: Robert Sparks User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: "sipcore@ietf.org" Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: [sipcore] Post WGLC comment on -refer-clarifications X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Apr 2015 15:45:38 -0000 Keith brought up something that -clarifications should talk about. RFC6665 deprecates the 202 response code for SIP Events. That should carry forward to REFER. I plan to add the following to the document before we send this off for AD Evaluation. If you see something fundamentally wrong with this text, please yell ASAP. ------- 5. The 202 response code is deprecated Section 8.3.1 of RFC6665 requires that elements do not send a 202 response code to a subscribe request, but use the 200 response code instead. Any 202 response codes received to a subscribe request are treated as 200s. These changes also apply to REFER. Specifically, an element accepting a REFER request MUST NOT reply with a 202 response code and MUST treat any 202 responses received as identical to a 200 response. Wherever RFC 3515 requires sending a 202 response code, a 200 response code MUST be sent instead. From nobody Mon Apr 20 09:05:05 2015 Return-Path: X-Original-To: sipcore@ietfa.amsl.com Delivered-To: sipcore@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 692B41B2F3B for ; Mon, 20 Apr 2015 09:05:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wvSuM0mqQztt for ; Mon, 20 Apr 2015 09:05:02 -0700 (PDT) Received: from smtp-p02.blackberry.com (smtp-p02.blackberry.com [208.65.78.89]) by ietfa.amsl.com (Postfix) with ESMTP id 340231B2F58 for ; Mon, 20 Apr 2015 09:04:48 -0700 (PDT) Received: from xct105cnc.rim.net ([10.65.161.205]) by mhs215cnc.rim.net with ESMTP/TLS/AES128-SHA; 20 Apr 2015 12:04:00 -0400 Received: from XCT112CNC.rim.net (10.65.161.212) by XCT105CNC.rim.net (10.65.161.205) with Microsoft SMTP Server (TLS) id 14.3.210.2; Mon, 20 Apr 2015 12:03:59 -0400 Received: from XMB122CNC.rim.net ([fe80::28c6:fa1c:91c6:2e23]) by XCT112CNC.rim.net ([::1]) with mapi id 14.03.0210.002; Mon, 20 Apr 2015 12:03:59 -0400 From: Andrew Allen To: Robert Sparks , "sipcore@ietf.org" Thread-Topic: [sipcore] Post WGLC comment on -refer-clarifications Thread-Index: AQHQe4EQtjUH2vtD2U2KBl5UK6bXtJ1WEDYW Date: Mon, 20 Apr 2015 16:03:58 +0000 Message-ID: <20150420160349.6680648.40448.6475@blackberry.com> References: <55351F1B.1040200@nostrum.com> In-Reply-To: <55351F1B.1040200@nostrum.com> Accept-Language: en-CA, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: Re: [sipcore] Post WGLC comment on -refer-clarifications X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Apr 2015 16:05:04 -0000 I support including this change in the draft. This was also my understanding of RFC 6665 text implication but I think it = is useful to explicitly include it in the clarifications draft. Andrew Sent from my BlackBerry 10 smartphone. Original Message From: Robert Sparks Sent: Monday, April 20, 2015 11:45 To: sipcore@ietf.org Subject: [sipcore] Post WGLC comment on -refer-clarifications Keith brought up something that -clarifications should talk about. RFC6665 deprecates the 202 response code for SIP Events. That should carry forward to REFER. I plan to add the following to the document before we send this off for AD Evaluation. If you see something fundamentally wrong with this text, please yell ASAP. ------- 5. The 202 response code is deprecated Section 8.3.1 of RFC6665 requires that elements do not send a 202 response code to a subscribe request, but use the 200 response code instead. Any 202 response codes received to a subscribe request are treated as 200s. These changes also apply to REFER. Specifically, an element accepting a REFER request MUST NOT reply with a 202 response code and MUST treat any 202 responses received as identical to a 200 response. Wherever RFC 3515 requires sending a 202 response code, a 200 response code MUST be sent instead. _______________________________________________ sipcore mailing list sipcore@ietf.org https://www.ietf.org/mailman/listinfo/sipcore From nobody Wed Apr 22 07:23:52 2015 Return-Path: X-Original-To: sipcore@ietfa.amsl.com Delivered-To: sipcore@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBF111ACCD9; Wed, 22 Apr 2015 07:23:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3n4YzsgRA6yJ; Wed, 22 Apr 2015 07:23:42 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BCEFE1ABD37; Wed, 22 Apr 2015 07:22:26 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.0.1.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150422142226.23146.71253.idtracker@ietfa.amsl.com> Date: Wed, 22 Apr 2015 07:22:26 -0700 Archived-At: Cc: sipcore@ietf.org Subject: [sipcore] I-D Action: draft-ietf-sipcore-refer-clarifications-04.txt X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.15 List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Apr 2015 14:23:48 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Session Initiation Protocol Core Working Group of the IETF. Title : Clarifications for the use of REFER with RFC6665 Authors : Robert Sparks Adam Roach Filename : draft-ietf-sipcore-refer-clarifications-04.txt Pages : 7 Date : 2015-04-22 Abstract: The SIP REFER method relies on the SIP-Specific Event Notification Framework. That framework was revised by RFC6665. This document highlights the implications of the requirement changes in RFC6665, and updates the definition of the REFER method, RFC3515, to clarify and disambiguate the impact of those changes. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-sipcore-refer-clarifications/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-sipcore-refer-clarifications-04 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-sipcore-refer-clarifications-04 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Wed Apr 22 07:24:19 2015 Return-Path: X-Original-To: sipcore@ietfa.amsl.com Delivered-To: sipcore@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8355E1AC41D; Wed, 22 Apr 2015 07:24:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a8owuQCJDd8X; Wed, 22 Apr 2015 07:24:15 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E3A911ACD12; Wed, 22 Apr 2015 07:22:40 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.0.1.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150422142240.21717.20754.idtracker@ietfa.amsl.com> Date: Wed, 22 Apr 2015 07:22:40 -0700 Archived-At: Cc: sipcore@ietf.org Subject: [sipcore] I-D Action: draft-ietf-sipcore-refer-explicit-subscription-02.txt X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.15 List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Apr 2015 14:24:16 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Session Initiation Protocol Core Working Group of the IETF. Title : Explicit Subscriptions for the REFER Method Author : Robert Sparks Filename : draft-ietf-sipcore-refer-explicit-subscription-02.txt Pages : 14 Date : 2015-04-22 Abstract: The Session Initiation Protocol (SIP) REFER request, as defined by RFC3515, triggers an implicit SIP-Specific Event Notification framework subscription. Conflating the start of the subscription with handling the REFER request makes negotiating SUBSCRIBE extensions impossible, and complicates avoiding SIP dialog sharing. This document defines extensions to REFER to remove the implicit subscription and, if desired, replace it with an explicit one. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-sipcore-refer-explicit-subscription/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-sipcore-refer-explicit-subscription-02 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-sipcore-refer-explicit-subscription-02 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Wed Apr 22 07:28:12 2015 Return-Path: X-Original-To: sipcore@ietfa.amsl.com Delivered-To: sipcore@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CDF11ACCF4 for ; Wed, 22 Apr 2015 07:28:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.889 X-Spam-Level: X-Spam-Status: No, score=-0.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, T_RP_MATCHES_RCVD=-0.01] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KWHT6WFo-roa for ; Wed, 22 Apr 2015 07:28:08 -0700 (PDT) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E103F1AC425 for ; Wed, 22 Apr 2015 07:27:53 -0700 (PDT) Received: from unnumerable.local (pool-71-170-237-80.dllstx.fios.verizon.net [71.170.237.80]) (authenticated bits=0) by nostrum.com (8.15.1/8.14.9) with ESMTPSA id t3MERqWM088530 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 22 Apr 2015 09:27:52 -0500 (CDT) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host pool-71-170-237-80.dllstx.fios.verizon.net [71.170.237.80] claimed to be unnumerable.local Message-ID: <5537AFE2.9040306@nostrum.com> Date: Wed, 22 Apr 2015 09:27:46 -0500 From: Robert Sparks User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 CC: sipcore@ietf.org References: <20150422142226.23146.71253.idtracker@ietfa.amsl.com> In-Reply-To: <20150422142226.23146.71253.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-refer-clarifications-04.txt X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Apr 2015 14:28:10 -0000 This adds the section on deprecating 202 with the text I sent to the list earlier. On 4/22/15 9:22 AM, internet-drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Session Initiation Protocol Core Working Group of the IETF. > > Title : Clarifications for the use of REFER with RFC6665 > Authors : Robert Sparks > Adam Roach > Filename : draft-ietf-sipcore-refer-clarifications-04.txt > Pages : 7 > Date : 2015-04-22 > > Abstract: > The SIP REFER method relies on the SIP-Specific Event Notification > Framework. That framework was revised by RFC6665. This document > highlights the implications of the requirement changes in RFC6665, > and updates the definition of the REFER method, RFC3515, to clarify > and disambiguate the impact of those changes. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-sipcore-refer-clarifications/ > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-sipcore-refer-clarifications-04 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-sipcore-refer-clarifications-04 > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore From nobody Wed Apr 22 07:28:49 2015 Return-Path: X-Original-To: sipcore@ietfa.amsl.com Delivered-To: sipcore@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 014441ACC91 for ; Wed, 22 Apr 2015 07:28:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bg3L-tF3pZVc for ; Wed, 22 Apr 2015 07:28:46 -0700 (PDT) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E1721AC3C2 for ; Wed, 22 Apr 2015 07:28:46 -0700 (PDT) Received: from unnumerable.local (pool-71-170-237-80.dllstx.fios.verizon.net [71.170.237.80]) (authenticated bits=0) by nostrum.com (8.15.1/8.14.9) with ESMTPSA id t3MESjcR088701 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 22 Apr 2015 09:28:46 -0500 (CDT) (envelope-from rjsparks@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host pool-71-170-237-80.dllstx.fios.verizon.net [71.170.237.80] claimed to be unnumerable.local Message-ID: <5537B018.6060507@nostrum.com> Date: Wed, 22 Apr 2015 09:28:40 -0500 From: Robert Sparks User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: sipcore@ietf.org References: <20150422142240.21717.20754.idtracker@ietfa.amsl.com> In-Reply-To: <20150422142240.21717.20754.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-refer-explicit-subscription-02.txt X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Apr 2015 14:28:48 -0000 This corrects the ABNF (Paul's review found some syntax errors). On 4/22/15 9:22 AM, internet-drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Session Initiation Protocol Core Working Group of the IETF. > > Title : Explicit Subscriptions for the REFER Method > Author : Robert Sparks > Filename : draft-ietf-sipcore-refer-explicit-subscription-02.txt > Pages : 14 > Date : 2015-04-22 > > Abstract: > The Session Initiation Protocol (SIP) REFER request, as defined by > RFC3515, triggers an implicit SIP-Specific Event Notification > framework subscription. Conflating the start of the subscription > with handling the REFER request makes negotiating SUBSCRIBE > extensions impossible, and complicates avoiding SIP dialog sharing. > This document defines extensions to REFER to remove the implicit > subscription and, if desired, replace it with an explicit one. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-sipcore-refer-explicit-subscription/ > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-sipcore-refer-explicit-subscription-02 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-sipcore-refer-explicit-subscription-02 > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore From nobody Wed Apr 22 09:09:32 2015 Return-Path: X-Original-To: sipcore@ietfa.amsl.com Delivered-To: sipcore@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5275E1ACE51; Wed, 22 Apr 2015 09:09:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7LmsSUQzs8-0; Wed, 22 Apr 2015 09:09:29 -0700 (PDT) Received: from smtp-p02.blackberry.com (smtp-p02.blackberry.com [208.65.78.89]) by ietfa.amsl.com (Postfix) with ESMTP id EA1831ACE02; Wed, 22 Apr 2015 09:09:07 -0700 (PDT) Received: from xct107cnc.rim.net ([10.65.161.207]) by mhs215cnc.rim.net with ESMTP/TLS/AES128-SHA; 22 Apr 2015 12:09:07 -0400 Received: from XMB122CNC.rim.net ([fe80::28c6:fa1c:91c6:2e23]) by XCT107CNC.rim.net ([fe80::b815:71ef:9f8f:e07c%16]) with mapi id 14.03.0210.002; Wed, 22 Apr 2015 12:09:06 -0400 From: Andrew Allen To: "internet-drafts@ietf.org" , "i-d-announce@ietf.org" Thread-Topic: [sipcore] I-D Action: draft-ietf-sipcore-refer-clarifications-04.txt Thread-Index: AQHQfQf8w2Ymm8lVR0eUamLFMR66mZ1ZMxaQ Date: Wed, 22 Apr 2015 16:09:06 +0000 Message-ID: References: <20150422142226.23146.71253.idtracker@ietfa.amsl.com> In-Reply-To: <20150422142226.23146.71253.idtracker@ietfa.amsl.com> Accept-Language: en-CA, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.65.160.251] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Cc: "sipcore@ietf.org" Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-refer-clarifications-04.txt X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Apr 2015 16:09:31 -0000 I have reviewed the changes in this draft and believe it is ready to go. Andrew -----Original Message----- From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of internet-draft= s@ietf.org Sent: Wednesday, April 22, 2015 10:22 AM To: i-d-announce@ietf.org Cc: sipcore@ietf.org Subject: [sipcore] I-D Action: draft-ietf-sipcore-refer-clarifications-04.t= xt A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Session Initiation Protocol Core Working = Group of the IETF. Title : Clarifications for the use of REFER with RFC6665 Authors : Robert Sparks Adam Roach Filename : draft-ietf-sipcore-refer-clarifications-04.txt Pages : 7 Date : 2015-04-22 Abstract: The SIP REFER method relies on the SIP-Specific Event Notification Framework. That framework was revised by RFC6665. This document highlights the implications of the requirement changes in RFC6665, and updates the definition of the REFER method, RFC3515, to clarify and disambiguate the impact of those changes. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-sipcore-refer-clarifications/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-sipcore-refer-clarifications-04 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-sipcore-refer-clarifications-= 04 Please note that it may take a couple of minutes from the time of submissio= n until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ sipcore mailing list sipcore@ietf.org https://www.ietf.org/mailman/listinfo/sipcore From nobody Wed Apr 22 09:13:49 2015 Return-Path: X-Original-To: sipcore@ietfa.amsl.com Delivered-To: sipcore@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 513701B372E; Wed, 22 Apr 2015 09:13:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V65QxB5SjVgq; Wed, 22 Apr 2015 09:13:46 -0700 (PDT) Received: from smtp-p02.blackberry.com (smtp-p02.blackberry.com [208.65.78.89]) by ietfa.amsl.com (Postfix) with ESMTP id A068B1B36FC; Wed, 22 Apr 2015 09:13:34 -0700 (PDT) Received: from xct107cnc.rim.net ([10.65.161.207]) by mhs215cnc.rim.net with ESMTP/TLS/AES128-SHA; 22 Apr 2015 12:13:31 -0400 Received: from XCT115CNC.rim.net (10.65.161.215) by XCT107CNC.rim.net (10.65.161.207) with Microsoft SMTP Server (TLS) id 14.3.210.2; Wed, 22 Apr 2015 12:13:30 -0400 Received: from XMB122CNC.rim.net ([fe80::28c6:fa1c:91c6:2e23]) by XCT115CNC.rim.net ([::1]) with mapi id 14.03.0210.002; Wed, 22 Apr 2015 12:13:30 -0400 From: Andrew Allen To: "internet-drafts@ietf.org" , "i-d-announce@ietf.org" Thread-Topic: [sipcore] I-D Action: draft-ietf-sipcore-refer-explicit-subscription-02.txt Thread-Index: AQHQfQgsL++3v5gmvkKrzPnhyGGdtZ1ZNGMg Date: Wed, 22 Apr 2015 16:13:29 +0000 Message-ID: References: <20150422142240.21717.20754.idtracker@ietfa.amsl.com> In-Reply-To: <20150422142240.21717.20754.idtracker@ietfa.amsl.com> Accept-Language: en-CA, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.65.160.251] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Cc: "sipcore@ietf.org" Subject: Re: [sipcore] I-D Action: draft-ietf-sipcore-refer-explicit-subscription-02.txt X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Apr 2015 16:13:48 -0000 I have reviewed this change and think this one is ready to go as well -----Original Message----- From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of internet-draft= s@ietf.org Sent: Wednesday, April 22, 2015 10:23 AM To: i-d-announce@ietf.org Cc: sipcore@ietf.org Subject: [sipcore] I-D Action: draft-ietf-sipcore-refer-explicit-subscripti= on-02.txt A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Session Initiation Protocol Core Working = Group of the IETF. Title : Explicit Subscriptions for the REFER Method Author : Robert Sparks Filename : draft-ietf-sipcore-refer-explicit-subscription-02.txt Pages : 14 Date : 2015-04-22 Abstract: The Session Initiation Protocol (SIP) REFER request, as defined by RFC3515, triggers an implicit SIP-Specific Event Notification framework subscription. Conflating the start of the subscription with handling the REFER request makes negotiating SUBSCRIBE extensions impossible, and complicates avoiding SIP dialog sharing. This document defines extensions to REFER to remove the implicit subscription and, if desired, replace it with an explicit one. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-sipcore-refer-explicit-subscrip= tion/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-sipcore-refer-explicit-subscription-0= 2 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-sipcore-refer-explicit-subscr= iption-02 Please note that it may take a couple of minutes from the time of submissio= n until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ sipcore mailing list sipcore@ietf.org https://www.ietf.org/mailman/listinfo/sipcore From nobody Wed Apr 22 21:11:58 2015 Return-Path: X-Original-To: sipcore@ietfa.amsl.com Delivered-To: sipcore@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 551BB1A0235 for ; Wed, 22 Apr 2015 19:15:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.912 X-Spam-Level: X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lIivrwMbZzlo for ; Wed, 22 Apr 2015 19:15:42 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id AE9D81A0196 for ; Wed, 22 Apr 2015 19:15:36 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 0799A180207; Wed, 22 Apr 2015 19:14:36 -0700 (PDT) To: mary.ietf.barnes@gmail.com, francois.audet@skype.net, shida@ntt-at.com, ietf.hanserik@gmail.com, christer.holmberg@ericsson.com, ben@nostrum.com, alissa@cooperw.in, adam@nostrum.com, pkyzivat@alum.mit.edu X-PHP-Originating-Script: 6000:errata_mail_lib.php From: RFC Errata System Message-Id: <20150423021436.0799A180207@rfc-editor.org> Date: Wed, 22 Apr 2015 19:14:36 -0700 (PDT) Archived-At: X-Mailman-Approved-At: Wed, 22 Apr 2015 21:11:56 -0700 Cc: chao.aa.wang@ericsson.con, sipcore@ietf.org, rfc-editor@rfc-editor.org Subject: [sipcore] [Editorial Errata Reported] RFC7044 (4345) X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Apr 2015 02:15:43 -0000 The following errata report has been submitted for RFC7044, "An Extension to the Session Initiation Protocol (SIP) for Request History Information". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=7044&eid=4345 -------------------------------------- Type: Editorial Reported by: chao wang Section: 6.2 Original Text ------------- 6.2. User Agent Server (UAS) Behavior When receiving a request, a UAS MUST follow the procedures defined in Section 9.2. Corrected Text -------------- 6.2. User Agent Server (UAS) Behavior When receiving a request, a UAS MUST follow the procedures defined in Section 9.1. Notes ----- In fact, the subject of 9.2 is "Sending a Request with History-Info", according to the original text, it wants to refer to how to handle a received request in UAS, the right reference shall be section 9.1 (9.1. Receiving a Request). Instructions: ------------- This erratum 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. -------------------------------------- RFC7044 (draft-ietf-sipcore-rfc4244bis-12) -------------------------------------- Title : An Extension to the Session Initiation Protocol (SIP) for Request History Information Publication Date : February 2014 Author(s) : M. Barnes, F. Audet, S. Schubert, J. van Elburg, C. Holmberg Category : PROPOSED STANDARD Source : Session Initiation Protocol Core Area : Real-time Applications and Infrastructure Stream : IETF Verifying Party : IESG From nobody Mon Apr 27 12:09:42 2015 Return-Path: X-Original-To: sipcore@ietfa.amsl.com Delivered-To: sipcore@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0A961AC42F for ; Mon, 27 Apr 2015 12:09:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id faGA0f3KOT6p for ; Mon, 27 Apr 2015 12:09:40 -0700 (PDT) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 099311AC420 for ; Mon, 27 Apr 2015 12:09:37 -0700 (PDT) Received: from [10.0.1.23] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.1/8.14.9) with ESMTPSA id t3RJ9LGh056202 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Apr 2015 14:09:31 -0500 (CDT) (envelope-from ben@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.23] From: "Ben Campbell" To: SIPCORE , "Paul Kyzivat" , "Jean Mahoney" , "Adam Roach" , "Alissa Cooper" Date: Mon, 27 Apr 2015 14:09:21 -0500 Message-ID: <9C875451-26E9-47EA-B265-711BDA611B23@nostrum.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Mailer: MailMate (1.9.1r5084) Archived-At: Subject: [sipcore] Chair Change X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Apr 2015 19:09:41 -0000 Hi Paul is stepping down as co-chair of sipcore. Please join me in thanking Paul for all the work he has done for sipcore, and all he has contributed (and will likely continue to contribute) to RAI in general. Jean Mahoney will fill the vacancy left by Paul. Please join me in welcoming Jean to the new role. Thanks! Ben. From nobody Mon Apr 27 12:25:23 2015 Return-Path: X-Original-To: sipcore@ietfa.amsl.com Delivered-To: sipcore@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60D111ACD16 for ; Mon, 27 Apr 2015 12:25:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1lKNcEyteVRf for ; Mon, 27 Apr 2015 12:25:21 -0700 (PDT) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E27181ACCFD for ; Mon, 27 Apr 2015 12:25:20 -0700 (PDT) Received: from mutabilis-2.local (pool-71-170-237-80.dllstx.fios.verizon.net [71.170.237.80]) (authenticated bits=0) by nostrum.com (8.15.1/8.14.9) with ESMTPSA id t3RJPGtF057515 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Apr 2015 14:25:16 -0500 (CDT) (envelope-from mahoney@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host pool-71-170-237-80.dllstx.fios.verizon.net [71.170.237.80] claimed to be mutabilis-2.local Message-ID: <553E8D17.8060009@nostrum.com> Date: Mon, 27 Apr 2015 14:25:11 -0500 From: "A. Jean Mahoney" User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Ben Campbell , SIPCORE , Paul Kyzivat , Jean Mahoney , Adam Roach , Alissa Cooper References: <9C875451-26E9-47EA-B265-711BDA611B23@nostrum.com> In-Reply-To: <9C875451-26E9-47EA-B265-711BDA611B23@nostrum.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [sipcore] Chair Change X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Apr 2015 19:25:22 -0000 Thank you, Ben and Paul. Hi all, I'll be meeting with Adam, Paul and Ben sometime soon to go over the working group's status. I look forward to working with you! Jean On 4/27/15 2:09 PM, Ben Campbell wrote: > Hi > > Paul is stepping down as co-chair of sipcore. Please join me in > thanking Paul for all the work he has done for sipcore, and all he has > contributed (and will likely continue to contribute) to RAI in general. > > Jean Mahoney will fill the vacancy left by Paul. Please join me in > welcoming Jean to the new role. > > Thanks! > > Ben. From nobody Tue Apr 28 10:00:31 2015 Return-Path: X-Original-To: sipcore@ietfa.amsl.com Delivered-To: sipcore@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2632B1B2ACA for ; Tue, 28 Apr 2015 10:00:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.211 X-Spam-Level: X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VsrOa_MF4zHP for ; Tue, 28 Apr 2015 10:00:23 -0700 (PDT) Received: from alum-mailsec-scanner-4.mit.edu (alum-mailsec-scanner-4.mit.edu [18.7.68.15]) by ietfa.amsl.com (Postfix) with ESMTP id 52BC21B2AC6 for ; Tue, 28 Apr 2015 10:00:23 -0700 (PDT) X-AuditID: 1207440f-f792a6d000001284-88-553fbca6b254 Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) by alum-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id CC.62.04740.6ACBF355; Tue, 28 Apr 2015 13:00:22 -0400 (EDT) Received: from Paul-Kyzivats-MacBook-Pro.local (c-50-138-229-151.hsd1.ma.comcast.net [50.138.229.151]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id t3SH0MCa014660 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Tue, 28 Apr 2015 13:00:22 -0400 Message-ID: <553FBCA4.2010901@alum.mit.edu> Date: Tue, 28 Apr 2015 13:00:20 -0400 From: Paul Kyzivat User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: SIPCORE Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrGIsWRmVeSWpSXmKPExsUixO6iqLtsj32oQd9fA4uvPzaxOTB6LFny kymAMYrbJimxpCw4Mz1P3y6BO2NTy1XGgllMFW875rA1MH5k7GLk5JAQMJGYPH0qG4QtJnHh 3nogm4tDSOAyo8Sj3/NZIJx/TBILe46zg1TxCmhLbLr/hhnEZhFQldh7cC5YN5uAlsScQ/9Z QGxRgWSJlle3WCDqBSVOznwCZHNwiAjIScy+EQMSFhawkOh8fgqshFnATGLe5ofMELa8xPa3 c5gnMPLOQtI9C0nZLCRlCxiZVzHKJeaU5urmJmbmFKcm6xYnJ+blpRbpmujlZpbopaaUbmKE hBP/Dsau9TKHGAU4GJV4eC1u2oUKsSaWFVfmHmKU5GBSEuX9tcM+VIgvKT+lMiOxOCO+qDQn tfgQowQHs5IIb+cWoBxvSmJlVWpRPkxKmoNFSZxXfYm6n5BAemJJanZqakFqEUxWhoNDSYI3 YDdQo2BRanpqRVpmTglCmomDE2Q4l5RIcWpeSmpRYmlJRjwowuKLgTEGkuIB2lsE0s5bXJCY CxSFaD3FqMtxZ8r/RUxCLHn5ealS4rxZIEUCIEUZpXlwK2DJ4xWjONDHwrwyIFU8wMQDN+kV 0BImoCWVM21AlpQkIqSkGhhTuY14ZrJ79rw70C2vdn5JTvvTVQwZjzzCrOouymQycYrE/skw N3WY1SItaKTV/2Bl8SMXjklzl8+/Xr/Y/4zeDvYMowafj2LbDi13E84QXPpzb4KgeLT8m2eh 3xluGlv9v2yhKBPGnKjcu4n/tu1twUtHpjs+CG6SvPxvY0eu+KZJm4/a31RiKc5INNRiLipO BACQImlq+QIAAA== Archived-At: Subject: [sipcore] Any implementations of the REFER update drafts? X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Apr 2015 17:00:30 -0000 The three REFER-related drafts will soon go to the IESG: - draft-ietf-sipcore-refer-clarifications - draft-ietf-sipcore-refer-explicit-subscription - draft-ietf-sipcore-6665-clarification *** Are there any implementations yet? Or plans for implementation? Thanks, Paul From nobody Tue Apr 28 14:18:40 2015 Return-Path: X-Original-To: sipcore@ietfa.amsl.com Delivered-To: sipcore@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 380441A89A9 for ; Tue, 28 Apr 2015 14:18:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aRSolK2V6R2l for ; Tue, 28 Apr 2015 14:18:38 -0700 (PDT) Received: from smtp-p02.blackberry.com (smtp-p02.blackberry.com [208.65.78.89]) by ietfa.amsl.com (Postfix) with ESMTP id 724AC1A89A7 for ; Tue, 28 Apr 2015 14:18:37 -0700 (PDT) Received: from xct106cnc.rim.net ([10.65.161.206]) by mhs214cnc.rim.net with ESMTP/TLS/AES128-SHA; 28 Apr 2015 17:18:35 -0400 Received: from XCT111CNC.rim.net (10.65.161.211) by XCT106CNC.rim.net (10.65.161.206) with Microsoft SMTP Server (TLS) id 14.3.210.2; Tue, 28 Apr 2015 17:18:35 -0400 Received: from XMB122CNC.rim.net ([fe80::28c6:fa1c:91c6:2e23]) by XCT111CNC.rim.net ([::1]) with mapi id 14.03.0210.002; Tue, 28 Apr 2015 17:18:34 -0400 From: Andrew Allen To: Paul Kyzivat , SIPCORE Thread-Topic: [sipcore] Any implementations of the REFER update drafts? Thread-Index: AQHQgdTYx+ORFd+apk++s1JnwrT+Q51i7htV Date: Tue, 28 Apr 2015 21:18:34 +0000 Message-ID: <20150428211830.6664273.73762.7495@blackberry.com> References: <553FBCA4.2010901@alum.mit.edu> In-Reply-To: <553FBCA4.2010901@alum.mit.edu> Accept-Language: en-CA, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: Re: [sipcore] Any implementations of the REFER update drafts? X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Apr 2015 21:18:40 -0000 3GPP release 12 references these drafts. I think you could call that a plan= for implementation. Sent from my BlackBerry 10 smartphone. Original Message From: Paul Kyzivat Sent: Tuesday, April 28, 2015 13:00 To: SIPCORE Subject: [sipcore] Any implementations of the REFER update drafts? The three REFER-related drafts will soon go to the IESG: - draft-ietf-sipcore-refer-clarifications - draft-ietf-sipcore-refer-explicit-subscription - draft-ietf-sipcore-6665-clarification *** Are there any implementations yet? Or plans for implementation? Thanks, Paul _______________________________________________ sipcore mailing list sipcore@ietf.org https://www.ietf.org/mailman/listinfo/sipcore From nobody Wed Apr 29 06:13:38 2015 Return-Path: X-Original-To: sipcore@ietfa.amsl.com Delivered-To: sipcore@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 674981B2CBB for ; Wed, 29 Apr 2015 06:13:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q2XbucUEp2c5 for ; Wed, 29 Apr 2015 06:13:34 -0700 (PDT) Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D403B1B2CB5 for ; Wed, 29 Apr 2015 06:13:28 -0700 (PDT) X-AuditID: c1b4fb2d-f794d6d000004501-e4-5540d8f6f889 Received: from ESESSHC004.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 66.AF.17665.6F8D0455; Wed, 29 Apr 2015 15:13:27 +0200 (CEST) Received: from ESESSMB209.ericsson.se ([169.254.9.61]) by ESESSHC004.ericsson.se ([153.88.183.30]) with mapi id 14.03.0210.002; Wed, 29 Apr 2015 15:13:26 +0200 From: Christer Holmberg To: Andrew Allen , Paul Kyzivat , SIPCORE Thread-Topic: [sipcore] Any implementations of the REFER update drafts? Thread-Index: AQHQgdTZi6WSbb/d5E2cqVEuW6l6L51izJMAgAEsR3A= Date: Wed, 29 Apr 2015 13:13:25 +0000 Message-ID: <7594FB04B1934943A5C02806D1A2204B1D7E06D8@ESESSMB209.ericsson.se> References: <553FBCA4.2010901@alum.mit.edu> <20150428211830.6664273.73762.7495@blackberry.com> In-Reply-To: <20150428211830.6664273.73762.7495@blackberry.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.148] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrNLMWRmVeSWpSXmKPExsUyM+Jvje73Gw6hBh83cVncn7eV0WLFhgOs Fl9/bGJzYPb4+/4Dk8eshrXsHkuW/GQKYI7isklJzcksSy3St0vgythzexlzwQLOijVt21kb GK+xdzFyckgImEj86exjhrDFJC7cW8/WxcjFISRwlFHi9KnTzBDOYkaJFYdnATkcHGwCFhLd /7RBGkQEciT6Pq5hBLGFBdwkTrbsYoeIu0uc+LWGBcK2kmh4uQ2shkVAVaLn8kmwOK+Ar8SO J91MILaQQILE14t9YDangL3EvScHwOYwAh30/dQasDizgLjErSfzmSAOFZBYsuc81NGiEi8f /2OFsJUkGpc8YYWo15FYsPsTG4StLbFs4WtmiL2CEidnPmGZwCg6C8nYWUhaZiFpmYWkZQEj yypG0eLU4uLcdCNjvdSizOTi4vw8vbzUkk2MwNg5uOW37g7G1a8dDzEKcDAq8fAqWDuECrEm lhVX5h5ilOZgURLntTM+FCIkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qB0bds/wPRFepCc3R+ nyw4lm426draDeEG5X8qMs7EH/13f9e/1/9zXK2Dik/1MbyZOS/6wy3NHxcYHp17ySKsf/Ck 9pKIS+yr30nM3fO1fu7aP17aURXmF5/PMHr6t0b24GV/9US/o9ef8E21/cEb/uDqEqb/X0Qq X8Y9L4xM5P70V3VxyPffx28qsRRnJBpqMRcVJwIAy9JNTX4CAAA= Archived-At: Subject: Re: [sipcore] Any implementations of the REFER update drafts? X-BeenThere: sipcore@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: SIP Core Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Apr 2015 13:13:37 -0000 Hi, Andrew took the words out of my mouth :) Regards, Christer -----Original Message----- From: sipcore [mailto:sipcore-bounces@ietf.org] On Behalf Of Andrew Allen Sent: 29 April 2015 00:19 To: Paul Kyzivat; SIPCORE Subject: Re: [sipcore] Any implementations of the REFER update drafts? 3GPP release 12 references these drafts. I think you could call that a plan= for implementation. Sent from my BlackBerry 10 smartphone. Original Message From: Paul Kyzivat Sent: Tuesday, April 28, 2015 13:00 To: SIPCORE Subject: [sipcore] Any implementations of the REFER update drafts? The three REFER-related drafts will soon go to the IESG: - draft-ietf-sipcore-refer-clarifications - draft-ietf-sipcore-refer-explicit-subscription - draft-ietf-sipcore-6665-clarification *** Are there any implementations yet? Or plans for implementation? Thanks, Paul _______________________________________________ sipcore mailing list sipcore@ietf.org https://www.ietf.org/mailman/listinfo/sipcore _______________________________________________ sipcore mailing list sipcore@ietf.org https://www.ietf.org/mailman/listinfo/sipcore