Re: [OPSAWG] draft-ietf-opsawg-sdi status
Michael Richardson <mcr+ietf@sandelman.ca> Sat, 07 March 2020 01:17 UTC
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70DE03A0F28 for <opsawg@ietfa.amsl.com>; Fri, 6 Mar 2020 17:17:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 ilnN2fG8L-IF for <opsawg@ietfa.amsl.com>; Fri, 6 Mar 2020 17:17:36 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9DF33A0F25 for <opsawg@ietf.org>; Fri, 6 Mar 2020 17:17:36 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id B41A43897D; Fri, 6 Mar 2020 20:16:26 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id A7992D10; Fri, 6 Mar 2020 20:17:35 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Joe Clarke (jclarke)" <jclarke@cisco.com>
cc: opsawg <opsawg@ietf.org>
In-Reply-To: <49B4136E-589D-4E52-A9C2-1CD9281A8691@cisco.com>
References: <49B4136E-589D-4E52-A9C2-1CD9281A8691@cisco.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Fri, 06 Mar 2020 20:17:35 -0500
Message-ID: <25575.1583543855@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/HU6x9Kt06JXJJ7zUfQJb0kEOMA4>
Subject: Re: [OPSAWG] draft-ietf-opsawg-sdi status
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Mar 2020 01:17:38 -0000
I have posted a shepherd write-up. Some suggestions that I have, one of which came from the idnits: 1) IPv6 example maybe? How would IPv6 work at all? Can it work in a SLAAC-only environment? 2) no references for DHCP are there at all. Probably there should be a few? at least to RFC2131? Some questions about how the keys would be generated, kept, distributed, etc. were asked during WG adoption discussion (tom perch and other), and I'm not sure that those comments/questions were dealt with fully at the time. I don't think that this is blocking though. -- Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-
- [OPSAWG] draft-ietf-opsawg-sdi status Joe Clarke (jclarke)
- Re: [OPSAWG] draft-ietf-opsawg-sdi status Michael Richardson
- Re: [OPSAWG] draft-ietf-opsawg-sdi status Warren Kumari
- Re: [OPSAWG] draft-ietf-opsawg-sdi status tom petch
- Re: [OPSAWG] draft-ietf-opsawg-sdi status Warren Kumari