[Anima] Alissa Cooper's Discuss on draft-ietf-anima-bootstrapping-keyinfra-28: (with DISCUSS and COMMENT)
Alissa Cooper via Datatracker <noreply@ietf.org> Wed, 16 October 2019 14:56 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: anima@ietf.org
Delivered-To: anima@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D5A3F12002E; Wed, 16 Oct 2019 07:56:17 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-anima-bootstrapping-keyinfra@ietf.org, Toerless Eckert <tte+ietf@cs.fau.de>, anima-chairs@ietf.org, tte+ietf@cs.fau.de, anima@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.105.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alissa Cooper <alissa@cooperw.in>
Message-ID: <157123777786.7830.10713306244839546046.idtracker@ietfa.amsl.com>
Date: Wed, 16 Oct 2019 07:56:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/MqFDiDAvAicu1My4JDaWmNjodzc>
Subject: [Anima] Alissa Cooper's Discuss on draft-ietf-anima-bootstrapping-keyinfra-28: (with DISCUSS and COMMENT)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Oct 2019 14:56:18 -0000
Alissa Cooper has entered the following ballot position for draft-ietf-anima-bootstrapping-keyinfra-28: Discuss 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.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-anima-bootstrapping-keyinfra/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- Apologies for the multiple emails, I failed to realize there was a new Gen-ART review for this document. The follow-up from the Gen-ART review seems to indicate that a YANG doctor review of this document is needed and/or that the YANG issues raised by Tom Petch need fixing. Is there a plan to get either of those done? ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks for addressing my original DISCUSS points. Please respond to the full Gen-ART review. Original COMMENT below. ------ I think this document would benefit from two concise lists, with notes about which items in each list are defined in this document and which ones are not defined: (1) what is operationally required of a manufacturer to support BRSKI, and (2) what is operationally required of a domain owner to support BRSKI. = Section 2.3.1 = What precisely is meant by "TPM identification"? Could a citation be provided? = Section 10.1 = "The domain can maintain some privacy since it has not necessarily been authenticated and is not authoritatively bound to the supply chain." What does this mean? That the domain can expect the manufacturer not to trust the domainID because it hasn't been authenticated? = Section 10.2 = "The above situation is to be distinguished from a residential/ individual person who registers a device from a manufacturer: that an enterprise/ISP purchases routing products is hardly worth mentioning. Deviations would, however, be notable." What does the last sentence mean?
- [Anima] Alissa Cooper's Discuss on draft-ietf-ani… Alissa Cooper via Datatracker
- Re: [Anima] Alissa Cooper's Discuss on draft-ietf… Michael Richardson
- Re: [Anima] Alissa Cooper's Discuss on draft-ietf… Michael Richardson
- Re: [Anima] Alissa Cooper's Discuss on draft-ietf… Alissa Cooper
- Re: [Anima] Alissa Cooper's Discuss on draft-ietf… Michael Richardson
- Re: [Anima] Alissa Cooper's Discuss on draft-ietf… Alissa Cooper
- Re: [Anima] Alissa Cooper's Discuss on draft-ietf… Brian E Carpenter
- Re: [Anima] Alissa Cooper's Discuss on draft-ietf… tom petch
- Re: [Anima] Alissa Cooper's Discuss on draft-ietf… Michael Richardson
- Re: [Anima] Alissa Cooper's Discuss on draft-ietf… tom petch
- Re: [Anima] Alissa Cooper's Discuss on draft-ietf… Michael Richardson
- Re: [Anima] Alissa Cooper's Discuss on draft-ietf… tom petch
- Re: [Anima] Alissa Cooper's Discuss on draft-ietf… Michael Richardson
- Re: [Anima] Alissa Cooper's Discuss on draft-ietf… tom petch
- Re: [Anima] Alissa Cooper's Discuss on draft-ietf… Michael Richardson
- [Anima] draft-ietf-anima-bootstrapping-keyinfra tom petch
- Re: [Anima] draft-ietf-anima-bootstrapping-keyinf… Eliot Lear