Re: [OPSAWG] WG LC for draft-ietf-opsawg-sdi-02
Warren Kumari <warren@kumari.net> Thu, 05 March 2020 00:23 UTC
Return-Path: <warren@kumari.net>
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 130FD3A0CD4 for <opsawg@ietfa.amsl.com>; Wed, 4 Mar 2020 16:23:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com
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 yAYXYtFaL0jF for <opsawg@ietfa.amsl.com>; Wed, 4 Mar 2020 16:23:22 -0800 (PST)
Received: from mail-qk1-x729.google.com (mail-qk1-x729.google.com [IPv6:2607:f8b0:4864:20::729]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E38FA3A0CD7 for <opsawg@ietf.org>; Wed, 4 Mar 2020 16:23:21 -0800 (PST)
Received: by mail-qk1-x729.google.com with SMTP id p62so3640239qkb.0 for <opsawg@ietf.org>; Wed, 04 Mar 2020 16:23:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=k1Wv+OXuq7VlZC6u8tCSG35MzoZGgGEcnehGHzW8H3U=; b=JaU3mGl5+CAMmw1mufhRl/HdCrynTboNI+xGAbrhhbptiWIALPwi/wF3KF30KjmLaO KZaltZqP9GUo8oGDGDj9sJiOOQDw8b3gYQSUhpps9bbv9TPcTnqnGNUKx39g89Bifafp Pzv/9lPzh+Vcw3K9Tt8PddwhOqOK3KC7zZCy2OpQhBbREP/2zqL2jiQ8dyQwlBIodR12 /s5RZHK4Q5axVeYNW/9mdmMHSyjQUfMGfP8SAIKCNNDxBQxRSJ2ZAQqr4DfTnfmA41kk OIImrXQXsqrjY+pXJnjlhgnwb/rWEMl4Ozm7RPyYl5b8IHcmMSGW4FyD8pHw7MOGkbaG ymnQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=k1Wv+OXuq7VlZC6u8tCSG35MzoZGgGEcnehGHzW8H3U=; b=mzu+aC7NS5H0ta6z7bnU0ej0fTTxhydiDl5TaIneekCq6jJaZK6sIvHXGiEv6t70pi o9fbqeGSufdyg6ceynMxE8OJBzKIEvKQh3Yk8Ou3K9WzLJe3U76EEx2j0zkAVUYL2teA i26d/6VntHvm5dVhhPMe3B8XiVVMsHfM568LmJw8A3v8exUn2GvKToDKK2hE/A6dnf3b a8YxxQTD1kB9XdhSBe7RB8MWQt5/JrWxuHNNYpSwYKs1o2z6Zlr8j07IcMsTfD59EY6K eMXPN8lqJjbX80V3ZM2Z7Ssy2XaliVIbOs/JACHN2DcicRDe5UfKpuANjUfVihKs030N 2hfA==
X-Gm-Message-State: ANhLgQ05gi43XDztxuyfmx8kM0aeZMlABgLDhxlpD16ub8vgyJkH5sGL GHgleWHENrErQQjzVKAZRwfl6j/HV480FPHC7mjB2A==
X-Google-Smtp-Source: ADFU+vu3/Iun8iEcfZeb2wd3hjz0B6u+iwx4QGLq7OQuLvej8EB0AtQ80S6RfMlBktqb8Tmw0HUWKFPO9QienrXl5yk=
X-Received: by 2002:a37:a50d:: with SMTP id o13mr2862982qke.37.1583367800681; Wed, 04 Mar 2020 16:23:20 -0800 (PST)
MIME-Version: 1.0
References: <BE7A5042-266D-4E49-B528-34896063D7D1@cisco.com> <35E49E63-BDE4-4190-ACA7-1BB343656F06@cisco.com>
In-Reply-To: <35E49E63-BDE4-4190-ACA7-1BB343656F06@cisco.com>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 04 Mar 2020 19:22:44 -0500
Message-ID: <CAHw9_iKQyFrUnbbSAdO31v_SjTjV0iq7CZcQLqevdZVA6fOKtg@mail.gmail.com>
To: "Joe Clarke (jclarke)" <jclarke@cisco.com>
Cc: opsawg <opsawg@ietf.org>, "draft-ietf-opsawg-sdi@ietf.org" <draft-ietf-opsawg-sdi@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004f0aed05a0108b3d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/SV_3sZJw3_1hOPvoTvQ-3GvEGrM>
Subject: Re: [OPSAWG] WG LC for draft-ietf-opsawg-sdi-02
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: Thu, 05 Mar 2020 00:23:25 -0000
On Wed, Feb 19, 2020 at 7:45 PM Joe Clarke (jclarke) <jclarke@cisco.com> wrote: > A bit late, but we did get some good review from Gen Art and some opsawg > members. This yielded a rev 03 and will certainly lead to an 04. With > that, we will push this draft forward to the IESG after all pending > comments are addressed. > Thank you, I have just posted -04, and think that this addresses the open comments. Joe's comments suggesting a magic header led to a significant improvement -- I now suggest vendors expect a file extension, header, or use a different DHCP codepoint for encrypted configs. I'm intentionally not being too prescriptive, so vendors can choose other solutions if they fit their deployment model better. I've also addressed Tom's comments by including additional text on the applicability, and that this issue is common in other industries / environments as well. If / when this gets sent to the IESG, I will obviously not be the responsible AD - I will conscript^W politely ask for someone else to carry it, and will recuse myself from balloting (as is standard practice). W > > Who in opsawg would be interested in serving as shepherd for this draft? > @Tom Petch, I know you called out some prior art concern. Would you have > an interest in shepherding? In general, I think the draft is (or very soon > will be) in good shape. I would have liked to see a security directorate > review, but no current reviews have called out serious security issues. > > Joe > > > On Feb 4, 2020, at 12:41, Joe Clarke (jclarke) <jclarke@cisco.com> > wrote: > > > > With the publication of -02 of this draft, it seems to have reached > stability. There has been interest in both usage an implementation of this > draft expressed in the past, but discussion has been quiet lately. > > > > This email serves as a two-week start of a WG LC for this document. > Please [re-]read this draft and comment on its content as well as whether > or not you feel it’s ready. WG LC will conclude on February 18, 2020. > > > > Authors and contributors, please reply on-list as to whether or not you > are aware of any intellectual property attributed to this work. Reply that > either you are not aware of any such IP, or reply with the details of known > IP while also making sure you complete any IPR disclosures in data tracker. > > > > Joe and Tianran > > _______________________________________________ > > OPSAWG mailing list > > OPSAWG@ietf.org > > https://www.ietf.org/mailman/listinfo/opsawg > > -- I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf
- [OPSAWG] WG LC for draft-ietf-opsawg-sdi-02 Joe Clarke (jclarke)
- Re: [OPSAWG] WG LC for draft-ietf-opsawg-sdi-02 Warren Kumari
- Re: [OPSAWG] WG LC for draft-ietf-opsawg-sdi-02 Colin Doyle
- Re: [OPSAWG] WG LC for draft-ietf-opsawg-sdi-02 Warren Kumari
- Re: [OPSAWG] WG LC for draft-ietf-opsawg-sdi-02 Joe Clarke (jclarke)
- Re: [OPSAWG] WG LC for draft-ietf-opsawg-sdi-02 Joe Clarke (jclarke)
- Re: [OPSAWG] WG LC for draft-ietf-opsawg-sdi-02 Warren Kumari
- Re: [OPSAWG] WG LC for draft-ietf-opsawg-sdi-02 Joe Clarke (jclarke)
- Re: [OPSAWG] WG LC for draft-ietf-opsawg-sdi-02 tom petch
- Re: [OPSAWG] WG LC for draft-ietf-opsawg-sdi-02 tom petch
- Re: [OPSAWG] WG LC for draft-ietf-opsawg-sdi-02 Joe Clarke (jclarke)
- Re: [OPSAWG] WG LC for draft-ietf-opsawg-sdi-02 Warren Kumari
- Re: [OPSAWG] WG LC for draft-ietf-opsawg-sdi-02 Warren Kumari