IETF Logo Mail Archive

[Iasa20] Am I missing something?

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 11 October 2018 00:56 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: iasa20@ietfa.amsl.com
Delivered-To: iasa20@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A801C130DEB for <iasa20@ietfa.amsl.com>; Wed, 10 Oct 2018 17:56:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Cg0x2R5mObvE for <iasa20@ietfa.amsl.com>; Wed, 10 Oct 2018 17:56:26 -0700 (PDT)
Received: from mail-pl1-x636.google.com (mail-pl1-x636.google.com [IPv6:2607:f8b0:4864:20::636]) (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 EC6B9130DDC for <iasa20@ietf.org>; Wed, 10 Oct 2018 17:56:25 -0700 (PDT)
Received: by mail-pl1-x636.google.com with SMTP id 1-v6so3324249plv.7 for <iasa20@ietf.org>; Wed, 10 Oct 2018 17:56:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=j7mN9eA5O6/l3fP4EsguJiNNR3kkHxvShnU/jbOW5gI=; b=qUlnSMo1M16CXXR0pXNhYEEpN1zO/ue8C7jqeKZPCFzC/ENp9lcJwCh1apremu6DGD +hFr9jYU5vpnHbZbtHFEjSLMXA2CoPowsLj7weSVbOLDp7/EKFGy6moRT9tP/Dxeo6QW mCqi8DZMiD5ajYvjxrhnRP90J3cJ13Ete985VemPyvGRrJ+gqYQkK3fB/fet1Fuaqbbc OLdNZvcJ+a8n1nxL7tkhKkiqcKuZ8X/Hw18Ir7gq/Pn+QNJkY1tbAMdKj2lDl3bS/Bmt iFV+Nz4xguC63VMFiLXTS+or4plvDa0PdT2A8QnYvsXMnrs5681K0nZP7sZEoFYLwDnH zCTw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=j7mN9eA5O6/l3fP4EsguJiNNR3kkHxvShnU/jbOW5gI=; b=hugVCOR7kH3O9HM15jBKoSPrN6phAm20O60kFg2GaEImUdMXlTIDkgTnzOoFvMLeUY ZiR+oaqMjkyIgHcDVykKdsAeHN6N3i5cXHqNNNnJzfoW2IayVEryOxObqGPzMGgRLZwv sm731xCaHVVyzudQoAiaW/R4t2PTvXPCCdf/16tcqJ5aa0YNTUApBFKc6Z7BEP3t8lca S3Q4ltSvH8cxg9XwGSg6dhJCbk/JEswkOWMmKxglL4zH90K4vfc9j7b+d+Ea6j6TpR3I 37LusGKLXdyq8YQx2jeZWWvqqBN1aamo3vsBCQD7QDbFwv87CW7BSKPXhQqFc2GWUYcJ ihtQ==
X-Gm-Message-State: ABuFfohai19RHzpCAaKKO7nz881LUMrezZ6oC+kfiykOslqLpytxEmlH lXtHXYMvVDbyU2YSOJqAXHeslC+g
X-Google-Smtp-Source: ACcGV62EGK84hj9L6pvpdgK0qMjxUXr3npE4McHNHQMzj8B1S894XvQTHvRoDJT8p7e36hlKVjoG/Q==
X-Received: by 2002:a17:902:6b4b:: with SMTP id g11-v6mr1507424plt.34.1539219385157; Wed, 10 Oct 2018 17:56:25 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.76.40]) by smtp.gmail.com with ESMTPSA id s80-v6sm35348666pfa.114.2018.10.10.17.56.23 for <iasa20@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Oct 2018 17:56:24 -0700 (PDT)
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
To: iasa20@ietf.org
Message-ID: <c5bd5495-a3ad-9529-5490-47fc253114c7@gmail.com>
Date: Thu, 11 Oct 2018 13:56:20 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/AzpjYI561BgUIAwhUL60TePeSOc>
Subject: [Iasa20] Am I missing something?
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions relating to reorganising the IETF administrative structures in the so called “IASA 2.0” project. <iasa20.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iasa20>, <mailto:iasa20-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iasa20/>
List-Post: <mailto:iasa20@ietf.org>
List-Help: <mailto:iasa20-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iasa20>, <mailto:iasa20-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2018 00:56:28 -0000

Hi,

While quickly reviewing draft-ietf-iasa2-rfc6220bis-01,
I noticed that it cites RFC4371 (part of BCP101), because
it needs a general reference for the IETF Trust.

Then I noticed that we do have a formal update to BCP101 planned
with respect to the Trust**, we don't seem to have a document planned
that normatively updates BCP101 by abolishing the IAOC (and incidentally
obsoleting RFC7691). draft-ietf-iasa2-struct can't do that since it's
intentionally Informational.

It seems to me that we need a short BCP that formally updates RFC4071
and obsoletes RFC7691. Its content would need to delete all the normative
specifics about the IAOC from 4071, possibly normatively replace
the term "IAD" by "IETF Executive Director", and refer informatively
to draft-ietf-iasa2-struct.

(The alternative would be a full-blown RFC4071bis, but I doubt if anyone
has the copious free time necessary for that.)

** draft-ietf-iasa2-trust-update updates 4071,4371 (if approved)

Or am I missing something else?
 
Regards
   Brian

v2.23.0 | Report a Bug | By Email