Simple Firewall Traversal Mechanisms and Their Pitfalls
draft-lear-callhome-description-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Eliot Lear | ||
| Last updated | 2005-10-20 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Many devices make use of so-called "Call Home" functionality in order to be managed or updated, or to otherwise establish outbound communication in the face of NATs, firewalls, and mobility. This memo defines call home functionality, discusses the requirement for firewall traversal, some mechanisms used, and security considerations of those mechanisms. Several existing examples will be shown. This memo also contains examples of how one would make SNMP over SSH, NETCONF over SSH, and interactive terminal access call-home protocols.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)