Homenet Routing Consensus Call
draft-ietf-homenet-routing-consensus-call-01
| Document | Type |
Expired Internet-Draft
(homenet WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ray Bellis , Mark Townsley | ||
| Last updated | 2016-07-24 (Latest revision 2016-01-21) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| 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
In order to support arbitrary network topologies and multi-homing the IETF Homenet Architecture [RFC7368] requires that a routing protocol operates inside each home network. For interoperability reasons it is necessary for there be a single "mandatory to implement" routing protocol. With the Homenet Working Group unable to reach clear consensus on which protocol that should be the Working Group Chairs (with the support of the Internet Area Director) declared rough consensus that the chosen protocol is BABEL [RFC6126]. This document (not intended for publication as an RFC) serves as an additional record of that decision.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)