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

Kent Watsen <kwatsen@juniper.net> Tue, 19 July 2011 20:14 UTC

Return-Path: <kwatsen@juniper.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 9C3EE21F8AB9; Tue, 19 Jul 2011 13:14:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id scDYZ1s+PBqK; Tue, 19 Jul 2011 13:14:01 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by ietfa.amsl.com (Postfix) with ESMTP id 0C6D821F8AF2; Tue, 19 Jul 2011 13:13:59 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKTiXlg+3zs3eS4FGa5a4Gnhry4vMrgvRu@postini.com; Tue, 19 Jul 2011 13:14:00 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Tue, 19 Jul 2011 13:13:09 -0700
From: Kent Watsen <kwatsen@juniper.net>
To: Phil Shafer <phil@juniper.net>, Randy Presuhn <randy_presuhn@mindspring.com>
Date: Tue, 19 Jul 2011 13:13:07 -0700
Thread-Topic: [Netconf] [OPSAWG] guidance on draft-kwatsen-reverse-ssh
Thread-Index: AcxGRLYK1V0uv75tQIeMy0W4zj+yVQAB/ZfQ
Message-ID: <84600D05C20FF943918238042D7670FD3E849038AE@EMBX01-HQ.jnpr.net>
References: <005201cc463f$b0b90060$6801a8c0@oemcomputer> <201107191823.p6JINNRq002843@idle.juniper.net>
In-Reply-To: <201107191823.p6JINNRq002843@idle.juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, "netconf@ietf.org" <netconf@ietf.org>
Subject: Re: [Netconf] [OPSAWG] guidance on draft-kwatsen-reverse-ssh
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 19 Jul 2011 20:14:01 -0000

> 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.  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