[netconf] logjam was re: YANG prefix Re: WG adoption poll for draft-wwlh-netconf-list-pagination

[tom petch <[e-mail]>]

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