Automatically Connecting Stub Networks to Unmanaged Infrastructure
draft-lemon-stub-networks-07
| Document | Type |
Replaced Internet-Draft
(snac WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Ted Lemon | ||
| Last updated | 2022-11-14 (Latest revision 2022-11-10) | ||
| Replaced by | draft-ietf-snac-simple | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Candidate for WG Adoption | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-snac-simple | |
| Consensus boilerplate | Unknown | ||
| 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
This document describes a set of practices for connecting stub networks to adjacent infrastructure networks. This is applicable in cases such as constrained (Internet of Things) networks where there is a need to provide functional parity of service discovery and reachability between devices on the stub network and devices on an adjacent infrastructure link (for example, a home network).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)