Re: [sipcore] Any implementations of the REFER update drafts?
Andrew Allen <aallen@blackberry.com> Tue, 28 April 2015 21:18 UTC
Return-Path: <aallen@blackberry.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 380441A89A9 for <sipcore@ietfa.amsl.com>; Tue, 28 Apr 2015 14:18:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 aRSolK2V6R2l for <sipcore@ietfa.amsl.com>; Tue, 28 Apr 2015 14:18:38 -0700 (PDT)
Received: from smtp-p02.blackberry.com (smtp-p02.blackberry.com [208.65.78.89]) by ietfa.amsl.com (Postfix) with ESMTP id 724AC1A89A7 for <sipcore@ietf.org>; Tue, 28 Apr 2015 14:18:37 -0700 (PDT)
Received: from xct106cnc.rim.net ([10.65.161.206]) by mhs214cnc.rim.net with ESMTP/TLS/AES128-SHA; 28 Apr 2015 17:18:35 -0400
Received: from XCT111CNC.rim.net (10.65.161.211) by XCT106CNC.rim.net (10.65.161.206) with Microsoft SMTP Server (TLS) id 14.3.210.2; Tue, 28 Apr 2015 17:18:35 -0400
Received: from XMB122CNC.rim.net ([fe80::28c6:fa1c:91c6:2e23]) by XCT111CNC.rim.net ([::1]) with mapi id 14.03.0210.002; Tue, 28 Apr 2015 17:18:34 -0400
From: Andrew Allen <aallen@blackberry.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, SIPCORE <sipcore@ietf.org>
Thread-Topic: [sipcore] Any implementations of the REFER update drafts?
Thread-Index: AQHQgdTYx+ORFd+apk++s1JnwrT+Q51i7htV
Date: Tue, 28 Apr 2015 21:18:34 +0000
Message-ID: <20150428211830.6664273.73762.7495@blackberry.com>
References: <553FBCA4.2010901@alum.mit.edu>
In-Reply-To: <553FBCA4.2010901@alum.mit.edu>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/sipcore/EQ_h68lU6yj8gZ509tP3FGrFcRk>
Subject: Re: [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 21:18:40 -0000
3GPP release 12 references these drafts. I think you could call that a plan for implementation.
Sent from my BlackBerry 10 smartphone.
Original Message
From: Paul Kyzivat
Sent: Tuesday, April 28, 2015 13:00
To: SIPCORE
Subject: [sipcore] Any implementations of the REFER update drafts?
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
_______________________________________________
sipcore mailing list
sipcore@ietf.org
https://www.ietf.org/mailman/listinfo/sipcore
- [sipcore] Any implementations of the REFER update… Paul Kyzivat
- Re: [sipcore] Any implementations of the REFER up… Andrew Allen
- Re: [sipcore] Any implementations of the REFER up… Christer Holmberg