[sipcore] RESPONSE REQUESTED: SIPCORE work and milestones
Adam Roach <adam@nostrum.com> Tue, 20 December 2016 20:27 UTC
Return-Path: <adam@nostrum.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C3161295F4 for <sipcore@ietfa.amsl.com>; Tue, 20 Dec 2016 12:27:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.999
X-Spam-Level:
X-Spam-Status: No, score=-4.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-3.1] autolearn=ham autolearn_force=no
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 aPKS_Tln4koU for <sipcore@ietfa.amsl.com>; Tue, 20 Dec 2016 12:27:17 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FC831295F0 for <sipcore@ietf.org>; Tue, 20 Dec 2016 12:27:17 -0800 (PST)
Received: from Orochi.local (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id uBKKRF8j091023 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 20 Dec 2016 14:27:16 -0600 (CST) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110] claimed to be Orochi.local
To: 'SIPCORE' <sipcore@ietf.org>
From: Adam Roach <adam@nostrum.com>
Message-ID: <e42393d8-9ddb-78ba-78fe-34f04f6d672d@nostrum.com>
Date: Tue, 20 Dec 2016 14:27:15 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------E296881C99DCCA5BB7B28506"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/dv-DpgsvxXwBcdfzVjuJQHlxEKk>
Cc: Ben Campbell <ben@nostrum.com>
Subject: [sipcore] RESPONSE REQUESTED: SIPCORE work and milestones
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 20 Dec 2016 20:27:18 -0000
[as chair] Now that we have our new charter approved, I'd like the working group to have a discussion about the specific work items that we should take on in the short- to medium-term so that we can revise our milestones appropriately. Based on recent discussions on the mailing list, the following topics have some mind-share behind them. What I'd like from everyone with an interest in any of these topics is to indicate (a) whether you are willing to actively review and comment on documents on the topic; and (b) what priority each task has relative to each other: there are five topics; please indicate a unique priority from one (most important) to five (least important) for each topic. 1. "Happy Eyeballs for SIP" (aka Happy Earballs), currently under discussion on the list. 2. "DTLS Transport for SIP", as proposed by Tolga Asveren's recent messages. 3. A mechanism for labeling the nature of SIP calls, with <draft-schulzrinne-sipcore-callinfo-spam> as a likely candidate draft. 4. Fixing Content-ID in SIP, as discussed in <https://www.ietf.org/mail-archive/web/sipcore/current/msg07245.html>, with <draft-holmberg-sipcore-content-id> as a likely candidate draft. 5. Clarifications around SIP name-addr, with <draft-sparks-sipcore-name-addr-guidance> as a likely candidate draft I will also note that we have already declared consensus on adopting <draft-ietf-sipcore-status-unwanted> as a WG document, and will be adding an associated milestone. I want to take this opportunity to remind people that the document is in WGLC, and your comments are strongly encouraged, the earlier the better. Please respond before the end of 2016. Thanks! Thanks! /a
- [sipcore] RESPONSE REQUESTED: SIPCORE work and mi… Adam Roach
- Re: [sipcore] RESPONSE REQUESTED: SIPCORE work an… Gonzalo Salgueiro (gsalguei)
- Re: [sipcore] RESPONSE REQUESTED: SIPCORE work an… Asveren, Tolga
- Re: [sipcore] RESPONSE REQUESTED: SIPCORE work an… Drage, Keith (Nokia - GB)
- Re: [sipcore] RESPONSE REQUESTED: SIPCORE work an… Dale R. Worley
- Re: [sipcore] RESPONSE REQUESTED: SIPCORE work an… Henning Schulzrinne
- Re: [sipcore] RESPONSE REQUESTED: SIPCORE work an… Richard Shockey
- Re: [sipcore] RESPONSE REQUESTED: SIPCORE work an… Christer Holmberg
- Re: [sipcore] RESPONSE REQUESTED: SIPCORE work an… Asveren, Tolga
- Re: [sipcore] RESPONSE REQUESTED: SIPCORE work an… Olle E. Johansson
- Re: [sipcore] RESPONSE REQUESTED: SIPCORE work an… Asveren, Tolga
- Re: [sipcore] RESPONSE REQUESTED: SIPCORE work an… Olle E. Johansson
- Re: [sipcore] RESPONSE REQUESTED: SIPCORE work an… Asveren, Tolga
- Re: [sipcore] RESPONSE REQUESTED: SIPCORE work an… Olle E. Johansson
- Re: [sipcore] RESPONSE REQUESTED: SIPCORE work an… Asveren, Tolga
- Re: [sipcore] RESPONSE REQUESTED: SIPCORE work an… Asveren, Tolga
- Re: [sipcore] RESPONSE REQUESTED: SIPCORE work an… Paul Kyzivat
- Re: [sipcore] RESPONSE REQUESTED: SIPCORE work an… Asveren, Tolga
- Re: [sipcore] RESPONSE REQUESTED: SIPCORE work an… Paul Kyzivat
- Re: [sipcore] RESPONSE REQUESTED: SIPCORE work an… Asveren, Tolga