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

Robert Sparks <rjsparks@nostrum.com> Thu, 17 November 2016 08:53 UTC

Return-Path: <rjsparks@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 337E81294F0; Thu, 17 Nov 2016 00:53:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.396
X-Spam-Status: No, score=-3.396 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 6DmcS5_GFdrG; Thu, 17 Nov 2016 00:53:21 -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 E44FB1294C6; Thu, 17 Nov 2016 00:53:21 -0800 (PST)
Received: from dhcp-9744.meeting.ietf.org (dhcp-9744.meeting.ietf.org []) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id uAH8rJ59050982 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=OK); Thu, 17 Nov 2016 02:53:21 -0600 (CST) (envelope-from rjsparks@nostrum.com)
References: <da53a12d-0058-1244-e069-21662eedd1d9@nostrum.com>
To: stir@ietf.org, "sipcore@ietf.org" <sipcore@ietf.org>
From: Robert Sparks <rjsparks@nostrum.com>
X-Forwarded-Message-Id: <da53a12d-0058-1244-e069-21662eedd1d9@nostrum.com>
Message-ID: <927fb975-f4e2-2021-f719-972d4f62cbde@nostrum.com>
Date: Thu, 17 Nov 2016 17:53:19 +0900
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <da53a12d-0058-1244-e069-21662eedd1d9@nostrum.com>
Content-Type: multipart/alternative; boundary="------------BE1EC0B521888C9EC1D72E8B"
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/3MLvSpd9PRSgiqIADBcZWaz1xqA>
Subject: [stir] Fwd: Re: [dispatch] 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
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:53:23 -0000

Reply-all betrayed me. Forwarding for completeness.

Sorry for the extra noise.

-------- Forwarded Message --------
Subject: 	Re: [dispatch] Discussion venue for 666 (was SHAKEN but not 
STIRred means 666 can cause collateral damage)
Date: 	Thu, 17 Nov 2016 17:51:52 +0900
From: 	Robert Sparks <rjsparks@nostrum.com>
To: 	dispatch@ietf.org

[as a STIR co-chair]

I agree with this.

Later in the discussion, I expect we will recommend splitting the
passport extension work out and running that through STIR, but that
doesn't need to happen immediately.

If we discover that there's frequent unnatural tension in needing to
talk about stir things while figuring out the SIP mechanics in these
drafts, we can revisit.


On 11/17/16 5:27 PM, Adam Roach wrote:
> [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
> /a
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch