Re: [Netconf] WG Last Call Comments ondraft-ietf-netconf-reverse-ssh-03.txt

t.petch <ietfc@btconnect.com> Sat, 12 April 2014 12:23 UTC

Return-Path: <ietfc@btconnect.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDEE71A0095 for <netconf@ietfa.amsl.com>; Sat, 12 Apr 2014 05:23:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.099
X-Spam-Level: ***
X-Spam-Status: No, score=3.099 tagged_above=-999 required=5 tests=[BAYES_50=0.8, MANGLED_TOOL=2.3, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=no
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 bDmSUf--HsVW for <netconf@ietfa.amsl.com>; Sat, 12 Apr 2014 05:23:52 -0700 (PDT)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3lp0075.outbound.protection.outlook.com [213.199.154.75]) by ietfa.amsl.com (Postfix) with ESMTP id 48B921A0092 for <netconf@ietf.org>; Sat, 12 Apr 2014 05:23:50 -0700 (PDT)
Received: from DB3PRD0710HT003.eurprd07.prod.outlook.com (10.255.75.38) by DB3PR07MB058.eurprd07.prod.outlook.com (10.242.137.148) with Microsoft SMTP Server (TLS) id 15.0.913.9; Sat, 12 Apr 2014 12:23:47 +0000
Received: from pc6 (86.171.207.36) by pod51017.outlook.com (10.255.75.38) with Microsoft SMTP Server (TLS) id 14.16.435.0; Sat, 12 Apr 2014 12:23:46 +0000
Message-ID: <009801cf5649$cd979b20$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: Kent Watsen <kwatsen@juniper.net>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
References: <201403251517.LAA15291@adminfs.snmp.com> <CF58ED17.65F0C%kwatsen@juniper.net> <533D47CF.30402@bwijnen.net> <01f401cf5342$4d48d740$4001a8c0@gateway.2wire.net> <CF69971C.685E2%kwatsen@juniper.net> <005101cf54b0$16a93940$4001a8c0@gateway.2wire.net> <CF6C7090.68D97%kwatsen@juniper.net> <20140410223815.GA99552@elstar.local> <CF6C990C.68FE4%kwatsen@juniper.net> <008901cf5565$418c3800$4001a8c0@gateway.2wire.net> <CF6D897A.6908F%kwatsen@juniper.net>
Date: Sat, 12 Apr 2014 13:20:44 +0100
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_0091_01CF5652.024F6B60"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [86.171.207.36]
X-Forefront-PRVS: 01792087B6
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009001)(6009001)(428001)(51444003)(164054003)(377454003)(189002)(199002)(13464003)(54534003)(51704005)(512934002)(61296002)(71636004)(4396001)(50226001)(44736004)(81542001)(83322001)(19580395003)(62966002)(81342001)(33646001)(99396002)(80976001)(71186001)(76482001)(14496001)(66066001)(86362001)(93916002)(1941001)(76176999)(575134002)(20776003)(87936001)(89996001)(88136002)(87286001)(84392001)(84326002)(77982001)(50986999)(77156001)(46102001)(81816999)(92726001)(79102001)(568964001)(19580405001)(80022001)(85852003)(92566001)(44716002)(62236002)(81686999)(31966008)(74502001)(74662001)(83072002)(74416001)(7726001); DIR:OUT; SFP:1101; SCL:1; SRVR:DB3PR07MB058; H:DB3PRD0710HT003.eurprd07.prod.outlook.com; FPR:EE34F01D.BEF26BF1.B3F35D70.94C2EDE1.20384; PTR:InfoNoRecords; MX:1; A:0; LANG:en;
Received-SPF: None (: btconnect.com does not designate permitted sender hosts)
X-OriginatorOrg: btconnect.com
Archived-At: http://mailarchive.ietf.org/arch/msg/netconf/yHksud4QkIf1LzJNxCsC3L2ZtLs
Cc: netconf@ietf.org
Subject: Re: [Netconf] WG Last Call Comments ondraft-ietf-netconf-reverse-ssh-03.txt
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 12 Apr 2014 12:23:57 -0000

Kent

I attach the updated XML.  I have replaced 'Reverse SSH' with 'call
home' or, where it seems necessary, 'NETCONF over SSH (call home),
following the style of 5539-bis.  xml2rfc says it is ok.  I update the
version to -05 and added a change log.  I think it would be wrong to
change the draft I-D name - yes, that name persists for ever in the data
tracker even after the RFC is created, but I think that the change of
name creates a discontinuity in the tracker that is a worse result.  I
think it would be better if you submitted this I-D - continuity again.

I would like to revise the first sentence of the Introduction/Abstract
(as I suggested last November) but including 'call home', but don't see
consensus on that yet so I have left that.

I will get back to you next week ( a busy one for me) on the other
points.

Tom Petch

----- Original Message -----
From: "Kent Watsen" <kwatsen@juniper.net>
To: "t.petch" <ietfc@btconnect.com>; "Juergen Schoenwaelder"
<j.schoenwaelder@jacobs-university.de>
Cc: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>; <netconf@ietf.org>
Sent: Friday, April 11, 2014 5:06 PM

Hi Tom,


>But as and when parts of ssh-server relate to the client, well then
>inbound and outbound are less clear, so I think that the use of inbound
>and outbound is an issue that needs more thought.

How about "listen" and "call-home", mimicing the names used for the
configuration nodes?




>And inbound is quite widespread in ssh-server, appearing in sections
>2.4, 2.5, 3.1, 3.2, 3.3, 3.4.  The usage is consistent within
>ssh-server but at odds with what I see as a set of documents, 5539-bis,
>reverse-ssh, ssh-server
>(and, perhaps, system-mgmt).  I read them all before making any
comments
>and it is the inconsistency between them that is driving me now.
>
>And, as I said before, I do see 5539-bis as the simplest, the clearest
>and so the one to move reverse-ssh and ssh-server towards.
>
>Which gives you the work to do, which is why I offered to help.


There looks to be WG consensus to do this now so, yes, please make this
change.  I suppose if we're removing "reverse" from the draft, then we
should rename it too - how about ietf-netconf-ssh-call-home?

Thanks,
Kent