[sipcore] Fwd: New Version Notification for draft-sparks-sipcore-refer-clarifications-03.txt
Robert Sparks <rjsparks@nostrum.com> Mon, 28 July 2014 22:18 UTC
Return-Path: <rjsparks@nostrum.com>
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 DC2BC1A02E1 for <sipcore@ietfa.amsl.com>; Mon, 28 Jul 2014 15:18:39 -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, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-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 omrGU4XMDZbn for <sipcore@ietfa.amsl.com>; Mon, 28 Jul 2014 15:18: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 AC38C1A028E for <sipcore@ietf.org>; Mon, 28 Jul 2014 15:18:37 -0700 (PDT)
Received: from unnumerable.local (pool-173-57-89-168.dllstx.fios.verizon.net [173.57.89.168]) (authenticated bits=0) by nostrum.com (8.14.9/8.14.7) with ESMTP id s6SMIaaQ040568 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK) for <sipcore@ietf.org>; Mon, 28 Jul 2014 17:18:37 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host pool-173-57-89-168.dllstx.fios.verizon.net [173.57.89.168] claimed to be unnumerable.local
Message-ID: <53D6CC3D.4000005@nostrum.com>
Date: Mon, 28 Jul 2014 17:18:37 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "sipcore@ietf.org" <sipcore@ietf.org>
References: <20140728221604.19558.73431.idtracker@ietfa.amsl.com>
In-Reply-To: <20140728221604.19558.73431.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20140728221604.19558.73431.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------050000020102020500060101"
Archived-At: http://mailarchive.ietf.org/arch/msg/sipcore/uzPJEx-xW1jNlU02Bvjhio2HHSo
Subject: [sipcore] Fwd: New Version Notification for draft-sparks-sipcore-refer-clarifications-03.txt
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jul 2014 22:18:40 -0000
Adam and I spent some time today editing to account for the discussion. We believe we covered all the concerns raised. The sentence in section 3 was getting a bit complex, so we split it up into several. Here's what it was before splitting it up: A UA that will accept a subscription-creating REFER request needs to include a GRUU as the Contact in all INVITE requests to ensure out-of-dialog REFER requests related to any dialog created by the INVITE arrive at this UA. You can see what it turned into by looking in the draft. RjS -------- Original Message -------- Subject: New Version Notification for draft-sparks-sipcore-refer-clarifications-03.txt Date: Mon, 28 Jul 2014 15:16:04 -0700 From: internet-drafts@ietf.org To: Robert Sparks <rjs@nostrum.com>, "Adam Roach" <adam@nostrum.com>, Adam Roach <adam@nostrum.com>, "Robert Sparks" <RjS@nostrum.com> A new version of I-D, draft-sparks-sipcore-refer-clarifications-03.txt has been successfully submitted by Robert Sparks and posted to the IETF repository. Name: draft-sparks-sipcore-refer-clarifications Revision: 03 Title: Clarifications for the use of REFER with RFC6665 Document date: 2014-07-28 Group: Individual Submission Pages: 4 URL: http://www.ietf.org/internet-drafts/draft-sparks-sipcore-refer-clarifications-03.txt Status: https://datatracker.ietf.org/doc/draft-sparks-sipcore-refer-clarifications/ Htmlized: http://tools.ietf.org/html/draft-sparks-sipcore-refer-clarifications-03 Diff: http://www.ietf.org/rfcdiff?url2=draft-sparks-sipcore-refer-clarifications-03 Abstract: An accepted SIP REFER method creates an implicit subscription using 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. 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. The IETF Secretariat
- [sipcore] Fwd: New Version Notification for draft… Robert Sparks
- Re: [sipcore] Fwd: New Version Notification for d… Ivo Sedlacek
- Re: [sipcore] Fwd: New Version Notification for d… Adam Roach
- Re: [sipcore] Fwd: New Version Notification for d… Ivo Sedlacek
- Re: [sipcore] Fwd: New Version Notification for d… Andrew Allen
- Re: [sipcore] Fwd: New Version Notification for d… Robert Sparks
- Re: [sipcore] Fwd: New Version Notification for d… Ivo Sedlacek
- Re: [sipcore] Fwd: New Version Notification for d… Ivo Sedlacek
- Re: [sipcore] Fwd: New Version Notification for d… Ivo Sedlacek
- Re: [sipcore] Fwd: New Version Notification for d… Christer Holmberg
- Re: [sipcore] Fwd: New Version Notification for d… Adam Roach
- Re: [sipcore] Fwd: New Version Notification for d… Ivo Sedlacek
- Re: [sipcore] Fwd: New Version Notification for d… Christer Holmberg
- Re: [sipcore] Fwd: New Version Notification for d… Ivo Sedlacek
- Re: [sipcore] Fwd: New Version Notification for d… OKUMURA Shinji
- Re: [sipcore] Fwd: New Version Notification for d… Robert Sparks
- Re: [sipcore] Fwd: New Version Notification for d… Ivo Sedlacek
- Re: [sipcore] Fwd: New Version Notification for d… Ivo Sedlacek
- Re: [sipcore] Fwd: New Version Notification for d… Andrew Allen
- Re: [sipcore] Fwd: New Version Notification for d… Andrew Allen
- Re: [sipcore] Fwd: New Version Notification for d… OKUMURA Shinji
- Re: [sipcore] Fwd: New Version Notification for d… Robert Sparks
- Re: [sipcore] Fwd: New Version Notification for d… Andrew Allen
- Re: [sipcore] Fwd: New Version Notification for d… Andrew Allen
- Re: [sipcore] Fwd: New Version Notification for d… Robert Sparks
- Re: [sipcore] Fwd: New Version Notification for d… Ivo Sedlacek
- Re: [sipcore] Fwd: New Version Notification for d… Ivo Sedlacek
- Re: [sipcore] Fwd: New Version Notification for d… Robert Sparks
- Re: [sipcore] Fwd: New Version Notification for d… Ivo Sedlacek
- Re: [sipcore] Fwd: New Version Notification for d… Adam Roach
- Re: [sipcore] Fwd: New Version Notification for d… Ivo Sedlacek
- Re: [sipcore] Fwd: New Version Notification for d… Robert Sparks
- Re: [sipcore] Fwd: New Version Notification for d… Christer Holmberg
- Re: [sipcore] Fwd: New Version Notification for d… Christer Holmberg
- Re: [sipcore] Fwd: New Version Notification for d… Adam Roach
- Re: [sipcore] Fwd: New Version Notification for d… Ivo Sedlacek