IETF Logo Mail Archive

[sipcore] Any implementations of the REFER update drafts?

Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 28 April 2015 17:00 UTC

Return-Path: <prvs=35608efab6=pkyzivat@alum.mit.edu>
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 2632B1B2ACA for <sipcore@ietfa.amsl.com>; Tue, 28 Apr 2015 10:00:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 VsrOa_MF4zHP for <sipcore@ietfa.amsl.com>; Tue, 28 Apr 2015 10:00:23 -0700 (PDT)
Received: from alum-mailsec-scanner-4.mit.edu (alum-mailsec-scanner-4.mit.edu [18.7.68.15]) by ietfa.amsl.com (Postfix) with ESMTP id 52BC21B2AC6 for <sipcore@ietf.org>; Tue, 28 Apr 2015 10:00:23 -0700 (PDT)
X-AuditID: 1207440f-f792a6d000001284-88-553fbca6b254
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) by alum-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id CC.62.04740.6ACBF355; Tue, 28 Apr 2015 13:00:22 -0400 (EDT)
Received: from Paul-Kyzivats-MacBook-Pro.local (c-50-138-229-151.hsd1.ma.comcast.net [50.138.229.151]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id t3SH0MCa014660 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <sipcore@ietf.org>; Tue, 28 Apr 2015 13:00:22 -0400
Message-ID: <553FBCA4.2010901@alum.mit.edu>
Date: Tue, 28 Apr 2015 13:00:20 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: SIPCORE <sipcore@ietf.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrGIsWRmVeSWpSXmKPExsUixO6iqLtsj32oQd9fA4uvPzaxOTB6LFny kymAMYrbJimxpCw4Mz1P3y6BO2NTy1XGgllMFW875rA1MH5k7GLk5JAQMJGYPH0qG4QtJnHh 3nogm4tDSOAyo8Sj3/NZIJx/TBILe46zg1TxCmhLbLr/hhnEZhFQldh7cC5YN5uAlsScQ/9Z QGxRgWSJlle3WCDqBSVOznwCZHNwiAjIScy+EQMSFhawkOh8fgqshFnATGLe5ofMELa8xPa3 c5gnMPLOQtI9C0nZLCRlCxiZVzHKJeaU5urmJmbmFKcm6xYnJ+blpRbpmujlZpbopaaUbmKE hBP/Dsau9TKHGAU4GJV4eC1u2oUKsSaWFVfmHmKU5GBSEuX9tcM+VIgvKT+lMiOxOCO+qDQn tfgQowQHs5IIb+cWoBxvSmJlVWpRPkxKmoNFSZxXfYm6n5BAemJJanZqakFqEUxWhoNDSYI3 YDdQo2BRanpqRVpmTglCmomDE2Q4l5RIcWpeSmpRYmlJRjwowuKLgTEGkuIB2lsE0s5bXJCY CxSFaD3FqMtxZ8r/RUxCLHn5ealS4rxZIEUCIEUZpXlwK2DJ4xWjONDHwrwyIFU8wMQDN+kV 0BImoCWVM21AlpQkIqSkGhhTuY14ZrJ79rw70C2vdn5JTvvTVQwZjzzCrOouymQycYrE/skw N3WY1SItaKTV/2Bl8SMXjklzl8+/Xr/Y/4zeDvYMowafj2LbDi13E84QXPpzb4KgeLT8m2eh 3xluGlv9v2yhKBPGnKjcu4n/tu1twUtHpjs+CG6SvPxvY0eu+KZJm4/a31RiKc5INNRiLipO BACQImlq+QIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/sipcore/OHb06kTmTTIyMX51KlLyU35mL5E>
Subject: [sipcore] Any implementations of the REFER update drafts?
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, 28 Apr 2015 17:00:30 -0000

The three REFER-related drafts will soon go to the IESG:
- draft-ietf-sipcore-refer-clarifications
- draft-ietf-sipcore-refer-explicit-subscription
- draft-ietf-sipcore-6665-clarification

*** Are there any implementations yet? Or plans for implementation?

	Thanks,
	Paul

v2.23.0 | Report a Bug | By Email