Re: [Anima] Alissa Cooper's Discuss on draft-ietf-anima-bootstrapping-keyinfra-28: (with DISCUSS and COMMENT)

Alissa Cooper <alissa@cooperw.in> Mon, 16 December 2019 20:08 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB24912093B; Mon, 16 Dec 2019 12:08:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=Wvbp7qq1; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=rZ+/ORzn
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 xM9PEfqzubES; Mon, 16 Dec 2019 12:08:38 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75623120932; Mon, 16 Dec 2019 12:08:38 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id CB6B122268; Mon, 16 Dec 2019 15:08:37 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Mon, 16 Dec 2019 15:08:37 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=b lLDYwr2keDlEuLO8WgTqKpkEcVQBzz3pTORuowi+7I=; b=Wvbp7qq1MV/5GRuHW Lk6hcLZddbPSDBey2NECpeeUG5CcgEu2YZQ6nmQQdNcJ0r4Rd4dUW2uXXq8YW/Yf 5yLfJ7O9tyG0OzqXEqPZTQ1otVAiP6GlykzmEOCU5QcX3q6uTJYUm+9SMB6Uhbis K5Lj/s/T1yGXw2aY601lABhue8I5JhiBLi5TFcBk0k8VbYR3/hnm0WYyDTSADsaO 0kSnVLNOAiD5RBIF3rZW8JjV3s23BkcNbV9zfWUIBLsm976J4hF2KoZTvoR7uJWh TICwWSnSNzPsAZjI76Y8JLzpt2U0uILu53iYyxv4xZo7owRbCeWTjJjh9KQC8SM+ hOVAw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=blLDYwr2keDlEuLO8WgTqKpkEcVQBzz3pTORuowi+ 7I=; b=rZ+/ORzn5Lvf4PpEVqlGlNisRpqqLmcgd4joBwfA/29Gf1G8tVupfDtkP ucEjGsmZeQ8kXcCkaTE+6oKW4pJxwkHmJ9GEtr503LsnR/8Ox0NMZ5d6vfN77sT7 E4OYbpxwdNnSRJ5yFhmy4scyhaDElTAUj+yMBIl9yrvVejaCSqYHMwN6OsaZ7JjU bpqvFzz4xqJZmCIdryBA4Aal6z+fVVl6kc5yFZW2pU1Bp56r7PIjJLutLyGsY0BO I2ajdQ1I8zsqSgwd1RtaMoOLll9JlJrRZ71KFn+lJRY+9PQVYX76YOArzO3V229W NojshxqrkezIpG2NnmOmS9/tz0hmQ==
X-ME-Sender: <xms:ReT3XRRydQ0by_sqsdVP8G56BijPf1O00GUkys1P03yulvhsXlEf_g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrvddthedgudefgecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurheptggguffhjgffgffkfhfvofesth hqmhdthhdtvdenucfhrhhomheptehlihhsshgrucevohhophgvrhcuoegrlhhishhsrges tghoohhpvghrfidrihhnqeenucfkphepudejfedrfeekrdduudejrdeltdenucfrrghrrg hmpehmrghilhhfrhhomheprghlihhsshgrsegtohhophgvrhifrdhinhenucevlhhushht vghrufhiiigvpedt
X-ME-Proxy: <xmx:ReT3XYLzr1Up_Yh0kjdAjPpUgXSFZVlW76GW0wpH7N-9VCkjx0oQbA> <xmx:ReT3XQWL-4qrZ_lx5plEEMvpQk33VtDC3ICCzEOxPuhXjnsQhzBG9g> <xmx:ReT3XURxFzTyekIOy6eXMdwlSHKfhbsYCt2IwF0PBHDGa-QYigvm7w> <xmx:ReT3XTgSAKEXUDh_YaVAk0KNoQoRePn6ItHlYMtoyCgoAFwdDp7CLg>
Received: from rtp-alcoop-nitro2.cisco.com (unknown [173.38.117.90]) by mail.messagingengine.com (Postfix) with ESMTPA id BEFE830600D7; Mon, 16 Dec 2019 15:08:36 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <20062.1576526178@localhost>
Date: Mon, 16 Dec 2019 15:08:35 -0500
Cc: tom petch <daedulus@btconnect.com>, IESG <iesg@ietf.org>, draft-ietf-anima-bootstrapping-keyinfra@ietf.org, tte+ietf@cs.fau.de, anima@ietf.org, anima-chairs@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <E9ED3FC1-A36A-416F-8016-ED6D851A954B@cooperw.in>
References: <157123777786.7830.10713306244839546046.idtracker@ietfa.amsl.com> <9637.1574756997@localhost> <2FA2728E-6484-4A69-992A-479D8053354E@cooperw.in> <20062.1576526178@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/Anyqt6iryl98LVhLeF2ykUs1duo>
Subject: Re: [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
Precedence: list
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: Mon, 16 Dec 2019 20:08:44 -0000

Thanks Michael. Should Section 8.1 now be removed as well?

Alissa

> On Dec 16, 2019, at 2:56 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> 
> {Hi Tom, I don't quite understand, but I don't seem to get emails directly
> From you.  Or perhaps it has to do with it being posted through the
> datatracker.  This is not the first review I have missed in this way.}
> 
> We had forgotten about the content of Appendix C, which is not normative.
> It stems from an era when we were not sure how successful RFC8520 will be.
> 
> I have issued version -31 in which we remove Appendix C rather than fix it.
> 
> This extension could be added correctly at a later date, and at this point,
> we don't see the MUD FILE->MASA URL flow as particularly important.
> 
> Both URLs can be in the IDevID if needed, at the cost of bytes in the IDevID
> certificate.
> 
> I think that there are operational problems with embedding the MUD URL in the
> IDevID relating to firmware upgrades, nor is that related to this appendix.
> It is not a BRSKI issue, but it does mean that the likelyhood of a MUD URL
> being the only extension that can be afforded an IDevID is significantly less
> likely.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> -= IPv6 IoT consulting =-
> 
> 
>