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

Robert Sparks <rjsparks@nostrum.com> Mon, 21 July 2014 22:23 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 A91251A02E1 for <sipcore@ietfa.amsl.com>; Mon, 21 Jul 2014 15:23:49 -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 dzya6KYgCDCY for <sipcore@ietfa.amsl.com>; Mon, 21 Jul 2014 15:23:48 -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 D98741A006B for <sipcore@ietf.org>; Mon, 21 Jul 2014 15:23:47 -0700 (PDT)
Received: from dhcp-b347.meeting.ietf.org (dhcp-b347.meeting.ietf.org [31.133.179.71]) (authenticated bits=0) by nostrum.com (8.14.9/8.14.7) with ESMTP id s6LMNkVE063828 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK) for <sipcore@ietf.org>; Mon, 21 Jul 2014 17:23:47 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <53CD92F2.9060403@nostrum.com>
Date: Mon, 21 Jul 2014 18:23:46 -0400
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: <20140721222239.14965.50656.idtracker@ietfa.amsl.com>
In-Reply-To: <20140721222239.14965.50656.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20140721222239.14965.50656.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------070604090702060103090302"
Archived-At: http://mailarchive.ietf.org/arch/msg/sipcore/QdEdJKm1QXWGX1GglfTnvXAUl2I
Subject: [sipcore] Fwd: New Version Notification for draft-sparks-sipcore-refer-clarifications-02.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, 21 Jul 2014 22:23:49 -0000

This fixed the missing slide 3 text.

RjS


-------- Original Message --------
Subject: 	New Version Notification for 
draft-sparks-sipcore-refer-clarifications-02.txt
Date: 	Mon, 21 Jul 2014 15:22:39 -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-02.txt
has been successfully submitted by Robert Sparks and posted to the
IETF repository.

Name:		draft-sparks-sipcore-refer-clarifications
Revision:	02
Title:		Clarifications for the use of REFER with RFC6665
Document date:	2014-07-21
Group:		Individual Submission
Pages:		4
URL:            http://www.ietf.org/internet-drafts/draft-sparks-sipcore-refer-clarifications-02.txt
Status:         https://datatracker.ietf.org/doc/draft-sparks-sipcore-refer-clarifications/
Htmlized:       http://tools.ietf.org/html/draft-sparks-sipcore-refer-clarifications-02
Diff:           http://www.ietf.org/rfcdiff?url2=draft-sparks-sipcore-refer-clarifications-02

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