[stir] Discussion venue for 666 (was SHAKEN but not STIRred means 666 can cause collateral damage)

Adam Roach <adam@nostrum.com> Thu, 17 November 2016 08:27 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id D7D5C1296A2; Thu, 17 Nov 2016 00:27:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.397
X-Spam-Status: No, score=-3.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.497] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id lM34JkTe-etA; Thu, 17 Nov 2016 00:27:06 -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 BB3D212941A; Thu, 17 Nov 2016 00:27:06 -0800 (PST)
Received: from dhcp-978a.meeting.ietf.org (dhcp-978a.meeting.ietf.org []) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id uAH8R2Z4048601 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 17 Nov 2016 02:27:04 -0600 (CST) (envelope-from adam@nostrum.com)
To: Brian Rosen <br@brianrosen.net>, IETF STIR Mail List <stir@ietf.org>
References: <AE9EB3D9-1F5C-4CA4-8F8C-66D4993D2318@brianrosen.net>
From: Adam Roach <adam@nostrum.com>
Message-ID: <aeb0871f-e96e-c87c-3cc6-951ed4dc5c27@nostrum.com>
Date: Thu, 17 Nov 2016 17:27:01 +0900
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <AE9EB3D9-1F5C-4CA4-8F8C-66D4993D2318@brianrosen.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/xZJUdlq3m8DR8C7OgpJ3BH5Rdro>
Cc: "dispatch@ietf.org" <dispatch@ietf.org>, 'SIPCORE' <sipcore@ietf.org>
Subject: [stir] Discussion venue for 666 (was SHAKEN but not STIRred means 666 can cause collateral damage)
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: 'SIPCORE' <sipcore@ietf.org>
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir/>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Nov 2016 08:27:08 -0000

[as SIPCORE chair]

On 11/17/16 10:14, Brian Rosen wrote:
> I’ve sent this to stir, even though it has not been decided where the 666 draft will land

My understanding coming out of DISPATCH is that 666 is appropriate for 
SIPCORE, assuming the new charter is approved by the IESG. I expect the 
proposed charter changes to be uncontroversial.

Based on the foregoing, we (the SIPCORE chairs) think it would be 
appropriate to hold general discussion of both of the
draft-schulzrinne-dispatch-callinfo-spam and 
draft-schulzrinne-dispatch-status-unwanted documents on the SIPCORE list.

I've copied DISPATCH and SIPCORE on this message, and set followups to