Re: [netconf] logjam was re: YANG prefix Re: WG adoption poll for draft-wwlh-netconf-list-pagination
Kent Watsen <kent+ietf@watsen.net> Thu, 28 April 2022 13:50 UTC
Return-Path: <01000180706faa07-f0f47fac-5432-47b4-9a2b-ee869ca1dd52-000000@amazonses.watsen.net>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CFBCC15E6D8 for <netconf@ietfa.amsl.com>; Thu, 28 Apr 2022 06:50:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oE23P90PF3NF for <netconf@ietfa.amsl.com>; Thu, 28 Apr 2022 06:50:09 -0700 (PDT)
Received: from a48-95.smtp-out.amazonses.com (a48-95.smtp-out.amazonses.com [54.240.48.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52965C15E6CE for <netconf@ietf.org>; Thu, 28 Apr 2022 06:50:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1651153808; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:Feedback-ID; bh=Zv0UUBU1zNKA64rMZFCW+GDGQKsiyLDG8CevlRgs0vo=; b=jpoHYc0YpS+vBnS+jJxZ71zBKH+50zCT3gtlglixksdnZqIPuvNK8edv0XjeKEtN eFv1laEMkZZ1NfOZpzDpzjvmt9zLTeC7GtQ4cyG10zrQvGlxKvZ8Uf9/J4eXJNQx19J nEULChv4O50JzcvdC4gNFd5r6/yOYKTc/7/q5hXU=
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Kent Watsen <kent+ietf@watsen.net>
In-Reply-To: <AM7PR07MB62480A662037D028D498EC1FA0FD9@AM7PR07MB6248.eurprd07.prod.outlook.com>
Date: Thu, 28 Apr 2022 13:50:08 +0000
Cc: "netconf@ietf.org" <netconf@ietf.org>, "michael.scharf@hs-esslingen.de" <michael.scharf@hs-esslingen.de>
Content-Transfer-Encoding: quoted-printable
Message-ID: <01000180706faa07-f0f47fac-5432-47b4-9a2b-ee869ca1dd52-000000@email.amazonses.com>
References: <F0DD43C9-ED92-4CEB-B2FF-3B62170B6EEE@gmail.com> <tencent_8AE86C089985513D6D2AEDAE7A4B7338F308@qq.com> <AM7PR07MB62483608303747857CD1E9AAA01F9@AM7PR07MB6248.eurprd07.prod.outlook.com> <CABCOCHSziMOZFFpHzXVwYtEQtd1DkW0XURSc=Q_+q_FMUjVgzg@mail.gmail.com> <0100017fe157e336-8a013b15-6bb0-48bd-965d-c68858e59b8f-000000@email.amazonses.com> <AM7PR07MB6248D0C1607D7B7DCF436195A0FA9@AM7PR07MB6248.eurprd07.prod.outlook.com> <AM7PR07MB62480A662037D028D498EC1FA0FD9@AM7PR07MB6248.eurprd07.prod.outlook.com>
To: tom petch <ietfc@btconnect.com>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2022.04.28-54.240.48.95
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/5K-jGdCyJHeI-Az6M00KwhOlkn0>
Subject: Re: [netconf] logjam was re: YANG prefix Re: WG adoption poll for draft-wwlh-netconf-list-pagination
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Apr 2022 13:50:10 -0000
Tom, The set of drafts move forward together. Every time another WG complains, the response is the same, can you help? Crickets every time! The current biggest blocker is ensuring the IANA-defined module sections in the ssh-client-server and tls-client-server drafts are ready, given draft-boucadair-netmod-iana-registries...not that we have to adhere to it, but it contains suggestions to reduce/avoid blowback from IANA. Can you take a look? BTW, did you look at the update made to the tls-client-server draft to address the 1.3 issue you raised? It was a massive effort that so far has yet to even be acknowledged... PS: regarding the Subject line, note the that the "list-pagination" draft adoption has not proceeded. As author, I'm happy for the chairs to block-adoptions until this suite of drafts goes through. Kent > On Apr 28, 2022, at 6:49 AM, tom petch <ietfc@btconnect.com> wrote: > > The resolution to a logjam, which is how I see the netconf I-D, is often just finding one log and taking it out and then the river runs freely. > > Looking at Normative dependencies, crypto-types is everywhere. I had thought to propose working on tcp-client-server as something that could soon be in the RFC Editor's queue, but no, it too depends on crypto-types. > > crypto-types is everything cryptography plus YANG. At the best times, you need a post-doc mathematician to review cryptography, here I doubt if anyone in the IETF, perhaps anyone in the world, has the technical skills to review this in its entirety. I then see this taking a year or two or more to wind its way through the system so it may be the key log, but it may not the best place to start. > > Thinking laterally, the barrier to tcp-client-server is the use, from crypto-types, of > choice password type > case plaintext > case encrypted > which then requires augments into the encrypted option (which tcp-client-server does not do. so it looks as if it is fairly useless). Whether it is or not, ditch it from tcp-client server, make the I-D do its own thing for password type and then there is an I-D which we could hope to move forward; and having moved one, we might have the energy to move another. > > Tom Petch
- [netconf] WG adoption poll for draft-wwlh-netconf… Mahesh Jethanandani
- Re: [netconf] WG adoption poll for draft-wwlh-net… Andy Bierman
- Re: [netconf] WG adoption poll for draft-wwlh-net… Qin Wu
- Re: [netconf] WG adoption poll for draft-wwlh-net… Hongwei Li
- Re: [netconf] WG adoption poll for draft-wwlh-net… Wei Wang
- Re: [netconf] WG adoption poll for draft-wwlh-net… tom petch
- Re: [netconf] WG adoption poll for draft-wwlh-net… Balázs Lengyel
- Re: [netconf] WG adoption poll for draft-wwlh-net… Andy Bierman
- Re: [netconf] WG adoption poll for draft-wwlh-net… Kent Watsen
- Re: [netconf] WG adoption poll for draft-wwlh-net… Andy Bierman
- Re: [netconf] WG adoption poll for draft-wwlh-net… Jürgen Schönwälder
- Re: [netconf] WG adoption poll for draft-wwlh-net… Kent Watsen
- Re: [netconf] WG adoption poll for draft-wwlh-net… Andy Bierman
- Re: [netconf] WG adoption poll for draft-wwlh-net… Kent Watsen
- Re: [netconf] WG adoption poll for draft-wwlh-net… Andy Bierman
- Re: [netconf] WG adoption poll for draft-wwlh-net… Andy Bierman
- Re: [netconf] WG adoption poll for draft-wwlh-net… Gyan Mishra
- [netconf] YANG prefix Re: WG adoption poll for dr… tom petch
- [netconf] logjam was re: YANG prefix Re: WG adopt… tom petch
- Re: [netconf] logjam was re: YANG prefix Re: WG a… Kent Watsen
- Re: [netconf] WG adoption poll for draft-wwlh-net… Mahesh Jethanandani
- Re: [netconf] logjam was re: YANG prefix Re: WG a… Scharf, Michael
- Re: [netconf] logjam was re: YANG prefix Re: WG a… tom petch
- Re: [netconf] logjam was re: YANG prefix tom petch