1 / 6

draft-ietf-netconf-reverse-ssh-06

draft-ietf-netconf-reverse-ssh-06. NETCONF Call-Home using SSH. Recap. NETCONF C all Home is a long time request This draft enables c all h ome for SSH RFC5539bis enables call h ome for TLS YANG in draft- netconf -server-model Discussed previously at IETF 89, 88, 87 and even 81.

pierce
Download Presentation

draft-ietf-netconf-reverse-ssh-06

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. draft-ietf-netconf-reverse-ssh-06 NETCONF Call-Home using SSH

  2. Recap • NETCONF Call Home is a long time request • This draft enables call home for SSH • RFC5539bis enables call home for TLS • YANG in draft-netconf-server-model • Discussed previously at IETF 89, 88, 87 and even 81

  3. Device initiates the TCP connection, and then runs SSH-server protocol NMS accepts TCP connection and then runs SSH-client protocol on top of it TBD Device NMS port TBD

  4. Changes since IETF 89 -04 • Improved language on how the management systemMUST authenticate the SSH server • Clarified that it is NOT RECOMMENDED for an NMS to identify a device using source IP address or simple certificate comparison • Device Configuration section now more clearly states that the YANG model is out of scope • Removed statement on how other SSH channels might be used for other protocols • Change requested port name to "netconf-ssh-ch” -05 • Changed "Reverse SSH" to "Call Home” everywhere • Changed title to “NETCONF over SSH Call Home” • Added references to Applicability Statement -06 (posted yesterday!) • Changed title to “NETCONF Call Home using SSH” • Changed MUST to SHOULD in Applicability Statement • Abstract and Introduction sections updated for clarity • Added “Draft Naming” section explaining apparent mismatch with “reverse-ssh” • Fixed grammar error in “Device Configuration” section

  5. Open Issues • Asymmetric document structure • 5539bis vs RFC6242 + reverse-ssh 6242bis instead? • Placement for generic content • Including: • Section 3: "Benefits to Device Management” • Section 5: "SSH Server Identification and Verification” • Best if moved to a common “Call Home” draft • A “6242bis” wouldn’t work after all… Proposal: • Have a single “NETCONF Call Home” (draft-ietf-netconf-call-home) draft that is equally valid for all NETCONF transports • rename this draft and move 5539bis content into it

  6. Questions / Concerns ?

More Related