Re: Observations on (non-technical) changes affecting IETF operations

Joseph Lorenzo Hall <joe@cdt.org> Fri, 25 March 2016 13:55 UTC

Return-Path: <jhall@cdt.org>
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 5BA9012D976 for <ietf@ietfa.amsl.com>; Fri, 25 Mar 2016 06:55:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cdt.org
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 1fxBP2lTnoVy for <ietf@ietfa.amsl.com>; Fri, 25 Mar 2016 06:55:09 -0700 (PDT)
Received: from mail-vk0-x22c.google.com (mail-vk0-x22c.google.com [IPv6:2607:f8b0:400c:c05::22c]) (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 7E1AD12DA1F for <ietf@ietf.org>; Fri, 25 Mar 2016 06:55:09 -0700 (PDT)
Received: by mail-vk0-x22c.google.com with SMTP id k1so92143785vkb.0 for <ietf@ietf.org>; Fri, 25 Mar 2016 06:55:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=n5gG4bFRpsiXv9NchT5Gflt/KFmGpWqWvytbup7uALE=; b=QMO2CPOnG2Ofhn0jeDIznuks4CHMhJ6/F9K+6LxUClHcPaNRXI8INHVu3hFZBZ8ZD6 awX7OXghuCT7j1xRKcVBBOA2z3x3j4rqUbZZZeSOLQEQAOh4D7teh/w2TsRzpoZgp3fO FSh153ffpzgK6+Z916oBagN4boqW5n3dReCIA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=n5gG4bFRpsiXv9NchT5Gflt/KFmGpWqWvytbup7uALE=; b=F7ttedF6/JNZ1jtp7NrNfY8hrWkU4rFHk5lXurrxFuuR9UtlglDK5TJGivStB/oSDb AAH2xrEzWthn+qimNz3T+aVU/o27in2AHsO3M7F+gEKC3uXE4CRa0LyUhXeJIthkAVmx SAx+W1JOqR09xLiwWypR0zufHEDfbM9mHoiD6nL6WyNjr/4oCslJ18R2uWodHI4TDnjz MVS57WSo1ZAmBmh/Mp1EmNSgj3m+qQ/2QWQUnXmb7UTaU6H4YFByGvO96wF67IdYFYF5 Vz0gx39xsKpBiOoe6auLZEpPC/UGA+H4QImDNXHn93CRHfSOEO/TwZ5wMlq9KFEkGNqb IBqA==
X-Gm-Message-State: AD7BkJKDMNnnKmDIDOtq4h2fzyzOoMtFwNOHtwkLzKKwetmQuHlWA3NyvwyO3harBYuVGxrYwWvKPIa1r/NnHItW
X-Received: by 10.176.2.107 with SMTP id 98mr7704253uas.112.1458914108571; Fri, 25 Mar 2016 06:55:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.70.156 with HTTP; Fri, 25 Mar 2016 06:54:49 -0700 (PDT)
In-Reply-To: <CABtrr-Xy412wMyagmx9+n98iCmyN6mOiY7mL0VVYgjo0tv3Deg@mail.gmail.com>
References: <6.2.5.6.2.20160324231112.0e0a2d78@elandsys.com> <CABtrr-Xy412wMyagmx9+n98iCmyN6mOiY7mL0VVYgjo0tv3Deg@mail.gmail.com>
From: Joseph Lorenzo Hall <joe@cdt.org>
Date: Fri, 25 Mar 2016 09:54:49 -0400
Message-ID: <CABtrr-UBsbqm6VG5tcgcj846p_QLB_LfrxiReAb=OJ098PhKtQ@mail.gmail.com>
Subject: Re: Observations on (non-technical) changes affecting IETF operations
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/UUBY4G9Tuw3TXOaVSxeruhjY4y8>
Cc: Steve Olshansky <olshansky@isoc.org>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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, 25 Mar 2016 13:55:11 -0000

Someone kindly pointed out my stupidity off-list that yest this did
become an IAB-track RFC in 2013:

https://tools.ietf.org/html/rfc6973

On Fri, Mar 25, 2016 at 6:44 AM, Joseph Lorenzo Hall <joe@cdt.org> wrote:
> On Fri, Mar 25, 2016 at 6:06 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:
>> Hello,
>> At 15:03 29-02-2016, Jari Arkko wrote:
>>>
>>> The team has been working and they have today published
>>> an -00 draft. We'd love to have your feedback and thoughts
>>> on this topic!
>>
>>
>> The draft is interesting.  Some of the topics which might be of interest
>> are: succession planning, fragmentation and cross-culture communication.
>>
>> If I am not mistaken it is the first time that a (IETF) draft acknowledges
>> that politics and technology are intertwined.
>
> I guess it depends on what you mean by politics. There have certainly
> been drafts that discuss law and policy considerations of potential
> IETF standards, including this one from us from 2003 (long before I
> was here at CDT), that while it never was seen through to official
> Informational RFC status, still has a lot of good material in it:
>
> https://tools.ietf.org/html/draft-morris-policy-considerations-00
>
> "This document is motivated by the recognition that technical design
> decisions made within the IETF and other standards bodies can have
> significant impacts on public policy concerns."
>
> --
> Joseph Lorenzo Hall
> Chief Technologist, Center for Democracy & Technology [https://www.cdt.org]
> e: joe@cdt.org, p: 202.407.8825, pgp: https://josephhall.org/gpg-key
> Fingerprint: 3CA2 8D7B 9F6D DBD3 4B10  1607 5F86 6987 40A9 A871
>
> CDT's annual dinner, Tech Prom, is April 6, 2016! https://cdt.org/annual-dinner



-- 
Joseph Lorenzo Hall
Chief Technologist, Center for Democracy & Technology [https://www.cdt.org]
e: joe@cdt.org, p: 202.407.8825, pgp: https://josephhall.org/gpg-key
Fingerprint: 3CA2 8D7B 9F6D DBD3 4B10  1607 5F86 6987 40A9 A871

CDT's annual dinner, Tech Prom, is April 6, 2016! https://cdt.org/annual-dinner