Homenet Routing Consensus Call
draft-ietf-homenet-routing-consensus-call-01

Document Type Expired Internet-Draft (homenet WG)
Last updated 2016-07-24 (latest revision 2016-01-21)
Stream IETF
Intended RFC status Informational
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-homenet-routing-consensus-call-01.txt

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

Ray Bellis (ray@isc.org)
Mark Townsley (mark@townsley.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)