Protocol Action: 'Explicit Subscriptions for the REFER Method' to Proposed Standard (draft-ietf-sipcore-refer-explicit-subscription-03.txt)

The IESG <iesg-secretary@ietf.org> Mon, 29 June 2015 22:06 UTC

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: Protocol Action: 'Explicit Subscriptions for the REFER Method' to Proposed Standard (draft-ietf-sipcore-refer-explicit-subscription-03.txt)
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150629220652.31144.7364.idtracker@ietfa.amsl.com>
Date: Mon, 29 Jun 2015 15:06:52 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/wKYE8PZ86S1WlnL_5V6HOVj-8oc>
Cc: sipcore mailing list <sipcore@ietf.org>, sipcore chair <sipcore-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Reply-To: ietf@ietf.org

The IESG has approved the following document:
- 'Explicit Subscriptions for the REFER Method'
  (draft-ietf-sipcore-refer-explicit-subscription-03.txt) as Proposed
Standard

This document is the product of the Session Initiation Protocol Core
Working Group.

The IESG contact persons are Barry Leiba, Ben Campbell and Alissa Cooper.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-sipcore-refer-explicit-subscription/





Technical Summary

  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 prevent the implicit
  subscription and, if desired, replace it with an explicit one.

Working Group Summary

  There was some controversy and difficulty in reaching agreement on this draft.
  Before work on this draft and the companion draft (draft-ietf-sipcore-refer-
  clarifications) commenced, some (notably 3GPP) made attempts to use existing
  mechanisms (RFC4488) to avoid the need for GRUUs. That mechanism as insufficient
  on its own, and so was enhanced with particular conventions. There was a desire
  to maintain compatibility with that work. This led to careful word smithing.
  That has been discussed at length within the WG. The results are now acceptable
  to all parties.

Document Quality

  The shepherd is not aware of any implementations yet. 
  It is the shepherd's understanding that 3GPP release 12 has a reference,
  indicating that implementations can be expected. 

  This document has been thoroughly reviewed and discussed. Everyone
  that had something to say has aired it. 

Personnel

  The document shepherd is Paul Kyzivat.
  The area director is Ben Campbell.

Protocol Action: 'Explicit Subscriptions for the … The IESG