Re: [sipcore] Fwd: New Version Notification for draft-sparks-sipcore-refer-clarifications-03.txt

OKUMURA Shinji <ietf.shinji@gmail.com> Tue, 12 August 2014 14:38 UTC

Return-Path: <ietf.shinji@gmail.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 0261F1A08F3 for <sipcore@ietfa.amsl.com>; Tue, 12 Aug 2014 07:38:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 1da9CjkWdCHn for <sipcore@ietfa.amsl.com>; Tue, 12 Aug 2014 07:38:46 -0700 (PDT)
Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B68A1A08F1 for <sipcore@ietf.org>; Tue, 12 Aug 2014 07:38:46 -0700 (PDT)
Received: by mail-pd0-f178.google.com with SMTP id w10so12703392pde.37 for <sipcore@ietf.org>; Tue, 12 Aug 2014 07:38:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:mime-version:content-type :content-transfer-encoding:in-reply-to:references:message-id; bh=pWCF6ox5F2qasMduU5RP0yx188weOLnZyY4klIsutRs=; b=V44a1ObEvXh1KK5w7OiEpHlSbjr0JIWDHoliqQWgGzJxExZxIa3rFB00Jdo0qr95dj X3yOuLnByOAr9gikY7MpkuljZW19Q7QX0ZKgKGrnQy8o4lK/vITMcgFms8h1KfyYCn4e nzv8WT0YDuWcA6sbKl+vvV7IxoreBBs6OvT+hINvGYhwDFh3ClrvYdxrkpZzd5puDPty 9xMcmKMNP3H1uTgUO15BswBWi0Mh01XnSYQmYT/jVIXMss16JDwOeHs/iOtOEgyxrxAl zXguoHnmUEkEUJaCWyXiU4xSYUJUYKRWLfvh/HuyCDvKFx9AtekVfG+4v7/qVxWmsKZX EBew==
X-Received: by 10.66.246.229 with SMTP id xz5mr4681520pac.119.1407854326176; Tue, 12 Aug 2014 07:38:46 -0700 (PDT)
Received: from gmail.com (softbank126001169004.bbtec.net. [126.1.169.4]) by mx.google.com with ESMTPSA id uw4sm13626790pab.40.2014.08.12.07.38.44 for <sipcore@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 12 Aug 2014 07:38:45 -0700 (PDT)
From: OKUMURA Shinji <ietf.shinji@gmail.com>
To: "sipcore@ietf.org" <sipcore@ietf.org>
Date: Tue, 12 Aug 2014 23:38:47 +0900
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: HidemaruMail 6.24 (WinNT,601)
In-Reply-To: <53D6CC3D.4000005@nostrum.com>
References: <20140728221604.19558.73431.idtracker@ietfa.amsl.com> <53D6CC3D.4000005@nostrum.com>
Message-Id: <47CFB63B20505Cietf.shinji@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/sipcore/CKsV-ygKv6mpe6jFBkb20Qq08gg
Subject: Re: [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: Tue, 12 Aug 2014 14:38:48 -0000

Hi,

I have another question.

If 6665 compliant UAS receives a REFER request within an
existing dialog that would create an implicit subscription,
how should the UAS handle the REFER request?

Regards,
Shinji

> 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: [a:mailto:internet-drafts@ietf.org]internet-drafts@ietf.org
> To: Robert Sparks [a:mailto:rjs@nostrum.com]<rjs@nostrum.com>, "Adam Roach" 
>[a:mailto:adam@nostrum.com]<adam@nostrum.com>, Adam Roach [a:mailto:
>adam@nostrum.com]<adam@nostrum.com>, "Robert Sparks" [a:mailto:RjS@nostrum.
>com]<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:            [a:http://www.ietf.org/internet-drafts/draft-sparks-sipcore-refer-clarifications-03.txt]http://www.ietf.org/internet-drafts/draft-sparks-sipcore-refer-clarifications-03.txt
>Status:         [a:https://datatracker.ietf.org/doc/draft-sparks-sipcore-refer-clarifications/]https://datatracker.ietf.org/doc/draft-sparks-sipcore-refer-clarifications/
>Htmlized:       [a:http://tools.ietf.org/html/draft-sparks-sipcore-refer-clarifications-03]http://tools.ietf.org/html/draft-sparks-sipcore-refer-clarifications-03
>Diff:           [a:http://www.ietf.org/rfcdiff?url2=draft-sparks-sipcore-refer-clarifications-03]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