Homenet WG, The WG is still at an impasse on selecting a single routing protocol and we ADs understand that this impasse must be resolved since it is a detriment to ongoing work and implementation.
In the working group meeting at IETF 92, Alia Atlas as Routing AD, proposed that a homenet design team be formed to select the routing protocol for homenet. In the room, there appeared to be support for this. This email is to provide the proposed charter for that design team and to confirm on the mailing list (as with all decisions) that there is consensus that this is how homenet will move from this impasse. The output from the design team would be subject to the question of whether there are any substantial technical objections to the selected routing protocol such that the homenet charter can not be met. The proposed homenet design team charter is below. =-=-=-=-=-=-=-=- Homenet's architecture (RFC 7368) articulates the general features required. The working group has agreed that a single routing protocol must be identified as mandatory to implement. The final purpose of this design team is to select and present a single routing protocol with a summary of the necessary extensions and work to be the one that is mandatory to implement. Once the design team has made its recommendation, the working group will consider any substantial technical objections (see RFC 7282) as part of gaining consensus. For the design team to make this determination, it shall first understand the use-cases for homenet and derive routing requirements from those. Then it shall compare these routing requirements to candidate routing protocols and examine the gaps in each. For each highly plausible candidate routing protocol, the design team will estimate the work needed and the associated timeline to get an acceptable, full, standardized solution using each protocol. Based upon this information and the perceived market timing needs of the technology, the design team will make its selection. The requirements, gaps, and reasoning will be documented. This document should be delivered by the July 2015 IETF. =-=-=-=-=-=-=-=- Thanks, Alia (RTG), Brian (INT), Terry (INT)
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
