[Ideas] Eric Rescorla's No Record on charter-ietf-ideas-00-01: (with COMMENT)

Eric Rescorla <ekr@rtfm.com> Thu, 28 September 2017 03:26 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: ideas@ietf.org
Delivered-To: ideas@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B064132D18; Wed, 27 Sep 2017 20:26:23 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Eric Rescorla <ekr@rtfm.com>
To: The IESG <iesg@ietf.org>
Cc: aretana@cisco.com, ideas-chairs@ietf.org, ideas@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.62.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150656918358.13632.8901471235240437918.idtracker@ietfa.amsl.com>
Date: Wed, 27 Sep 2017 20:26:23 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ideas/07sS5cSSIdp7oDrlytXqeyMr2JU>
Subject: [Ideas] Eric Rescorla's No Record on charter-ietf-ideas-00-01: (with COMMENT)
X-BeenThere: ideas@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "Discussions relating to the development, clarification, and implementation of control-plane infrastructures and functionalities in ID enabled networks." <ideas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ideas>, <mailto:ideas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ideas/>
List-Post: <mailto:ideas@ietf.org>
List-Help: <mailto:ideas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ideas>, <mailto:ideas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Sep 2017 03:26:24 -0000

Eric Rescorla has entered the following ballot position for
charter-ietf-ideas-00-01: No Record

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-ideas/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

The privacy text in this charter seems pretty week. We're spending a lot of
effort right now to deal with the privacy impacts of our existing protocol that
maps text names to IP addresses (DNS), so we don't want to recapitulate that
one layer down. I think it needs to say something about how a major part of the
framework is defining the privacy requirements and how to meet them. I'm not
going to push "block" for external review, but I do expect to raise this issue
at chartering time.