Re: [OPSAWG] [Netconf] guidance on draft-kwatsen-reverse-ssh

----- Original Message -----
From: "Kent Watsen" <kwatsen@juniper.net>
To: "Phil Shafer" <phil@juniper.net>; "Randy Presuhn"
<randy_presuhn@mindspring.com>
Cc: <opsawg@ietf.org>; <netconf@ietf.org>
Sent: Tuesday, July 19, 2011 10:13 PM

> > The terms "broad" and "narrow" seem meaningless in this discussion.
> > Can we choose better terms?  "new-device" and "reachability" are
> > perhaps more self-explanitory.
>
> Regarding the narrow/broad terminology, I tend to use "initial discovery" and
"on-going management".  The draft enumerates motivation the for both cases.
>
>
> > Are there issues with Kent's draft?
>
> When considering this, please reference the -00 draft.

How?  With the death of watersprings, I know of no way to get an obsoleted
draft; the IETF web site only gives me -01 which is what I would expect.  If you
really want us to consider the earlier version then I think that you should
re-issue it as -02.

And a URL would help.

Tom Petch

> The -01 draft was put together to appease some SAAG/IETF-SSH list members, but
it is unnecessarily more complex than the solution presented in the -00 draft.
>
> That said, if there's support for the -00 draft, I recommend updating its
bootstrap sequence to be more like SSH, by having the MAC and Host-Key
algorithms negotiated.
>
>
> Thanks,
> Kent
>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg