Re: [Isms] ISMS charter broken- onus should be on WG to fix it

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>>>>> "David" == David B Harrington <ietfdbh@xxxxxxxxxxx> writes:

    David> Hi, Personally, I'd rather see the issue of working through
    David> NATs and firewalls solved at the SSH level, and then SNMP
    David> and other SSH-using applications, such as Netconf and CLI,
    David> could use the solution in a consistent manner.


I think that the ssh connection application already has a fairly
reasonable story for NATs and firewalls, so I don't see much of a need
for ssh itself to advance in this area.  

For the most part people who block port 22 really do intend to block
ssh and so having standard facilities to get around that would not be
appropriate.  The port forwarding support in ssh seems to be an
adequate solution for NATs.

SNMP can use these facilities certainly.  However you may want/need a
more automated solution.

_______________________________________________

Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]