Re: [Netconf] I-D Action: draft-ietf-netconf-reverse-ssh-04.txt

[t.petch <[e-mail]>]

Kent

I saw your exchange with Alan about the paragraph starting

"However, configuring distinct host keys on the management system
   doesn't scale well, which is an important consideration to a network
   management system.  "

That sounds plausible but seems to me to undermine the use of SSH for
NETCONF generally, nothing to do with call home.  Why is this not an
implicit update to RFC4742?

Tom Petch

----- Original Message -----
From: "Kent Watsen" <[e-mail]>
To: <[e-mail]>; <[e-mail]>
Cc: <[e-mail]>
Sent: Monday, April 07, 2014 4:28 PM
>
> Please see the Change Log to see what's new in the draft.
>
> I have not heard back from Steve yet on the Applicability Statement.
This
> is the only open issue I'm aware of and otherwise the draft is ready
for
> last call.
>
> The draft contains a reference to "draft-ietf-netconf-server-model",
which
> doesn't exist yet, as that draft was last submitted as
> "draft-kwatsen-netconf-server" and hasn't been updated yet.  I don't
> believe this is an issue since the reference happens in text that
clearly
> says the model is outside the scope.
>
> PS: Bert, I'm already using the xml2rfc v2 script
>
> Thanks,
> Kent
>
>
>
> On 4/7/14 11:05 AM, "[e-mail]"
<[e-mail]>
> wrote:
>
> >
> >A New Internet-Draft is available from the on-line Internet-Drafts
> >directories.
> > This draft is a work item of the Network Configuration Working Group
of
> >the IETF.
> >
> >        Title           : Reverse SSH for NETCONF Call Home
> >        Author          : Kent Watsen
> > Filename        : draft-ietf-netconf-reverse-ssh-04.txt
> > Pages           : 10
> > Date            : 2014-04-07
> >
> >Abstract:
> >   This document presents a technique for a NETCONF server to
initiate a
> >   SSH connection to a NETCONF client.  This is accomplished by the
> >   NETCONF client listening on IANA-assigned TCP port YYYY and
starting
> >   the SSH client protocol immediately after accepting a TCP
connection
> >   on it.  This role-reversal is necessary as the NETCONF server must
> >   also be the SSH server, in order for the NETCONF client to open
the
> >   IANA-assigned SSH subsystem "netconf".
> >
> >
> >The IETF datatracker status page for this draft is:
> >https://datatracker.ietf.org/doc/draft-ietf-netconf-reverse-ssh/
> >
> >There's also a htmlized version available at:
> >http://tools.ietf.org/html/draft-ietf-netconf-reverse-ssh-04
> >
> >A diff from the previous version is available at:
> >http://www.ietf.org/rfcdiff?url2=draft-ietf-netconf-reverse-ssh-04
> >
> >
> >Please note that it may take a couple of minutes from the time of
> >submission
> >until the htmlized version and diff are available at tools.ietf.org.
> >
> >Internet-Drafts are also available by anonymous FTP at:
> >ftp://ftp.ietf.org/internet-drafts/
> >
> >_______________________________________________
> >Netconf mailing list
> >[e-mail]
> >https://www.ietf.org/mailman/listinfo/netconf
> >
> >
>
>
> _______________________________________________
> Netconf mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/netconf