IETF Logo Mail Archive

Re: [Add] [Ext] Updated charter proposal for ADD

"Robert Mortimer" <robm@scramworks.net> Wed, 15 January 2020 15:43 UTC

Return-Path: <robm@scramworks.net>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6670120025 for <add@ietfa.amsl.com>; Wed, 15 Jan 2020 07:43:52 -0800 (PST)
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, HTML_MESSAGE=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=scramworks.net
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 orjh7RfL7jq5 for <add@ietfa.amsl.com>; Wed, 15 Jan 2020 07:43:48 -0800 (PST)
Received: from knid.scramworks.net (knid.scramworks.net [IPv6:2a01:4f8:c17:50eb::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB1EB120091 for <add@ietf.org>; Wed, 15 Jan 2020 07:43:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=scramworks.net; s=bofh; h=References:In-Reply-To:To:From:Subject:Message-ID :Date:MIME-Version:Content-Type:Sender:Reply-To:Cc:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=DYs9lkMPzm5KipHIj9XaT1600qpOUs/YxIhmiXWVbh4=; b=MTu0ZJsgdn4XBF+s997AMqFJrx w5eDMWms5P8PVeM7J6veYDTdOIxJjCo76YJffKfqz8k3lqUaEZ5t52QDZ4J8I98jg0gVEhLFWO8JT D+n1QIiLPuXOO82UGxZyK+apwvtXlI2J6UBWOnGyztKMV+vHFTkoPEnD7TeOIIR7vUD4=;
Received: from [90.240.133.23] (helo=[192.168.1.6]) by knid.scramworks.net with esmtpsa (TLS1.1:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.90_1) (envelope-from <robm@scramworks.net>) id 1irkpb-0000W6-QL for add@ietf.org; Wed, 15 Jan 2020 15:43:44 +0000
Content-Type: multipart/alternative; boundary="----=_NextPart_4249344.873757954056"
MIME-Version: 1.0
Date: Wed, 15 Jan 2020 15:42:42 +0000
Message-ID: <Mailbird-6b932a67-158f-43e3-b660-bf7399d207b1@scramworks.net>
From: Robert Mortimer <robm@scramworks.net>
To: add@ietf.org
In-Reply-To: <AD6E599F-96E8-44FC-8A05-8BFD2F659129@icann.org>
References: <236B0A34-8C7F-49D2-8075-5AF5AC35BDFB@apple.com> <AD6E599F-96E8-44FC-8A05-8BFD2F659129@icann.org>
User-Agent: Mailbird/2.7.9.0
X-Mailbird-ID: Mailbird-6b932a67-158f-43e3-b660-bf7399d207b1@scramworks.net
X-Spam-Score-SW: -1.0 (-)
X-SW-Scan: 9207447d32bfa5765bb6a1125ce59f3b
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/XJ0NaUBekSF4BUqCPvdViV5KMZc>
Subject: Re: [Add] [Ext] Updated charter proposal for ADD
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2020 15:43:53 -0000

+1


-- 
Robm
873
  "Ask not what I can do for the stupid, 
         but what the stupid can do for me" - Graeme Garden
On 15/01/2020 15:15:09, Paul Hoffman <paul.hoffman@icann.org> wrote:
The following paragraph in the proposed charter is impossible to meet for the vast majority of use cases that have been discussed on this list:

Any mechanisms that specify interactions between clients and
servers must provide the security properties expected of IETF
protocols, e.g., confidentiality protection, integrity protection,
and authentication with strong work factor.

Any mechanism whose understanding of the network and network services comes from interactions that were not cryptographically authenticated (such as DHCP and RA) cannot meet those requirements.

The presence of that paragraph will basically stop work being done in the WG once it is chartered. Please strongly consider removing it. Without that paragraph, the charter seems fine.

--Paul Hoffman--
Add mailing list
Add@ietf.org
https://www.ietf.org/mailman/listinfo/add

v2.23.0 | Report a Bug | By Email