idnits 2.17.1 draft-ietf-homenet-routing-consensus-call-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The abstract seems to contain references ([RFC7368], [RFC6126]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (November 18, 2015) is 3082 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 6126 (Obsoleted by RFC 8966) -- Obsolete informational reference (is this intentional?): RFC 7557 (Obsoleted by RFC 8966) == Outdated reference: A later version (-03) exists of draft-boutier-babel-source-specific-01 Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Homenet Working Group R. Bellis 3 Internet-Draft ISC 4 Intended status: Informational W. Townsley 5 Expires: May 21, 2016 Cisco 6 November 18, 2015 8 Homenet Routing Consensus Call 9 draft-ietf-homenet-routing-consensus-call-00 11 Abstract 13 In order to support arbitrary network topologies and multi-homing the 14 IETF Homenet Architecture [RFC7368] requires that a routing protocol 15 operates inside each home network. For interoperability reasons it 16 is necessary for there be a single "mandatory to implement" routing 17 protocol. With the Homenet Working Group unable to reach clear 18 consensus on which protocol that should be the Working Group Chairs 19 (with the support of the Internet Area Director) declared rough 20 consensus that the chosen protocol is BABEL [RFC6126]. This document 21 confirms this decision for the record. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on May 21, 2016. 40 Copyright Notice 42 Copyright (c) 2015 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Statement . . . . . . . . . . . . . . . . . . . . . . . . . . 2 58 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 59 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 60 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 61 5. Informative References . . . . . . . . . . . . . . . . . . . 3 62 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 3 64 1. Statement 66 On the 27th of October, 2015, the Working Group Chairs and the 67 Internet Area Director made the following statement to the Homenet 68 Mailing List: 70 The Chairs believe that there is WG consensus that a single 71 "mandatory to implement" routing protocol must be chosen. We also 72 believe that further delaying the direction here has long passed 73 the point of diminishing returns. 75 Based on the feedback received in Prague and on the WG mailing 76 list thereafter, we are therefore declaring rough consensus that 77 BABEL [RFC6126] shall be the "mandatory to implement" routing 78 protocol for Homenet routers, albeit only on an Experimental basis 79 at this time. 81 The aim in making this decision is to allow the non-routing- 82 protocol aspects of Homenet to move forward in the near term, 83 while allowing time for additional implementation, experimentation 84 and specification. To that end, we solicit Experimental Internet 85 Drafts to document Homenet-specific profiles of any applicable 86 routing solution and to report results of any relevant 87 experimentation and implementation. 89 We expect that this decision will be revisited in a future 90 Standards Track document based on specifications and running code 91 available at that time. 93 Vendors looking to ship Homenet routers in the near term should 94 refer to [RFC6126], [RFC7557], 95 [I-D.boutier-babel-source-specific], and available open source 96 implementations thereof for the routing protocol portion of the 97 Homenet solution space. 99 2. IANA Considerations 101 This document has no IANA considerations. 103 3. Security Considerations 105 This document has no security considerations. 107 4. Acknowledgements 109 We wish to thank Terry Manderson (INT Area AD) for his support. 111 5. Informative References 113 [RFC7368] Chown, T., Ed., Arkko, J., Brandt, A., Troan, O., and J. 114 Weil, "IPv6 Home Networking Architecture Principles", RFC 115 7368, DOI 10.17487/RFC7368, October 2014, 116 . 118 [RFC6126] Chroboczek, J., "The Babel Routing Protocol", RFC 6126, 119 DOI 10.17487/RFC6126, April 2011, 120 . 122 [RFC7557] Chroboczek, J., "Extension Mechanism for the Babel Routing 123 Protocol", RFC 7557, DOI 10.17487/RFC7557, May 2015, 124 . 126 [I-D.boutier-babel-source-specific] 127 Boutier, M. and J. Chroboczek, "Source-Specific Routing in 128 Babel", draft-boutier-babel-source-specific-01 (work in 129 progress), May 2015. 131 Authors' Addresses 133 Ray Bellis 134 Internet Systems Consortium, Inc. 135 950 Charter Street 136 Redwood City CA 94063 137 USA 139 Phone: +1 640 423 1200 140 Email: ray@isc.org 141 Mark Townsley 142 Cisco 144 Email: mark@townsley.net