Last Call: <draft-ietf-sipcore-refer-clarifications-04.txt> (Clarifications for the use of REFER with RFC6665) to Proposed Standard
The IESG <iesg-secretary@ietf.org> Wed, 03 June 2015 23:38 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AFD81B3089; Wed, 3 Jun 2015 16:38:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 R6nXMZIE5PAw; Wed, 3 Jun 2015 16:38:26 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BFD4C1A8AAD; Wed, 3 Jun 2015 16:38:26 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-sipcore-refer-clarifications-04.txt> (Clarifications for the use of REFER with RFC6665) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.3.p2
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
Message-ID: <20150603233826.8955.40177.idtracker@ietfa.amsl.com>
Date: Wed, 03 Jun 2015 16:38:26 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/Wk5o8BtLmG4_S7pwswhrSHKj0pI>
Cc: sipcore@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jun 2015 23:38:28 -0000
The IESG has received a request from the Session Initiation Protocol Core WG (sipcore) to consider the following document: - 'Clarifications for the use of REFER with RFC6665' <draft-ietf-sipcore-refer-clarifications-04.txt> as 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 2015-06-17. 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. 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 file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-sipcore-refer-clarifications/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-sipcore-refer-clarifications/ballot/ No IPR declarations have been submitted directly on this I-D.