Re: IETF subpoena processes update and a request

Pete Resnick <presnick@qti.qualcomm.com> Fri, 24 March 2017 19:40 UTC

Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E86C1298C8 for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 12:40:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.022
X-Spam-Level:
X-Spam-Status: No, score=-7.022 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
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 FEZ53KFAz4jD for <ietf@ietfa.amsl.com>; Fri, 24 Mar 2017 12:40:30 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9636B1294EC for <ietf@ietf.org>; Fri, 24 Mar 2017 12:40:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1490384424; x=1521920424; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=sob1tZulRfxlWPbr0VRL3DerEXx3TIiqK2UNmyfhAp4=; b=LxlJV8jIjlgTWPB2yO1jlSTpCJp/LE4fNTS6bfH9yIDTDjNnYL81QuE6 vogTSkapuKaGMwNAXpG2BYbaDJcsXRL7f8t/I8wo05XBHeYwN/6bzH/WJ n06rJnRe3oZp0oJ+5Eablg+3OeqTp8UzZSfnXK/0AC3+xWk3L7BMs/dCK 8=;
X-IronPort-AV: E=Sophos;i="5.36,216,1486454400"; d="scan'208";a="367920805"
Received: from unknown (HELO Ironmsg03-L.qualcomm.com) ([10.53.140.110]) by wolverine02.qualcomm.com with ESMTP; 24 Mar 2017 12:40:24 -0700
X-IronPort-AV: E=McAfee;i="5800,7501,8477"; a="1338163766"
X-MGA-submission: MDFSdffZ2UwJdoMwj2H8uRKDvV7Vr9E3EI8qxfcn4hqxEivcQbq933MubF4tnxjW4pa8cx8bKVSIbdrVfO3LRWNRh/2wqaamAyxhIx3laonA/uNyyhyk0GCRcQUbvNSH64GdEwPoDYFs6luukEy6sdmz
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 24 Mar 2017 12:40:23 -0700
Received: from [10.64.118.210] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 24 Mar 2017 12:40:23 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
CC: ietf@ietf.org
Subject: Re: IETF subpoena processes update and a request
Date: Fri, 24 Mar 2017 14:40:21 -0500
Message-ID: <74917090-33FB-4D1A-BE11-6ECDF214B1E1@qti.qualcomm.com>
In-Reply-To: <25630.1490382918@obiwan.sandelman.ca>
References: <149033560170.22298.4992160350083194861.idtracker@ietfa.amsl.com> <FB90DAC1-5822-4A33-9A06-C07B61CA9847@qti.qualcomm.com> <25630.1490382918@obiwan.sandelman.ca>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; markup="markdown"
X-Mailer: MailMate (1.9.6r5347)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01C.na.qualcomm.com (10.85.0.83) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Zia96PLM2QSANIZ6XQwZ56nwhUc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Mar 2017 19:40:39 -0000

On 24 Mar 2017, at 14:15, Michael Richardson wrote:

> Pete Resnick <presnick@qti.qualcomm.com> wrote:
>     > To deal with the second issue, it seems to me that we should 
> address
>     > the first issue by making it crystal clear in the procedures 
> that the
>     > subpoena must go to the entire IESG, not just the chair, and 
> that
>     > whatever action is taken on the subpoena be approved by the IESG 
> (with
>     > advice of counsel). If the entire IESG gets a copy of the 
> subpoena, and
>     > our procedures make it clear to any court or other issuing 
> authority
>     > that more than one person outside of their jurisdiction will be 
> seeing
>     > the subpoena, perhaps that will mitigate the second issue.
>
> Is your goal here to dissuade them from placing gag orders on the 
> subpeona,
> or is it to make it clear that their subpoena should omit unnecessary
> identifying information, as we will post it publically.

Certainly I hope to dissuade gag orders, and certainly I want to make it 
clear that they should omit unnecessary identifying information, but 
note that I did not say that "we will post it publicly". We may, or we 
may not, post it publicly (cf. JCK's message), but either way I'd like 
it to be crystal clear that at least some persons over whom the issuer 
has no jurisdictional control (e.g., because the court is outside of the 
US and members of the IESG are US citizens, or vice versa) will be 
getting copies of the subpoena. So, gag orders will at best be advisory 
and it would be wise to omit unnecessary identifying information.

(My un-legally-educated guess here is that publicly posting something 
that is subject to a gag order, even by someone not normally subject to 
a particular jurisdiction, is a bit of a game of legal "chicken", since 
that person might want to enter that jurisdiction some day. But this is 
where I'd like like to leave it to our leadership to take advice of 
counsel and make their best judgment about what is right for the 
community. What I don't want is to have procedures that make it easy for 
any particular jurisdiction to dictate terms to us.)

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478