Protocol Action: 'IPv4 routes with an IPv6 next hop in the Babel routing protocol' to Proposed Standard (draft-ietf-babel-v4viav6-08.txt)
The IESG <iesg-secretary@ietf.org> Tue, 01 March 2022 23:06 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 872B73A1171; Tue, 1 Mar 2022 15:06:20 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'IPv4 routes with an IPv6 next hop in the Babel routing protocol' to Proposed Standard (draft-ietf-babel-v4viav6-08.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 7.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, babel-chairs@ietf.org, babel@ietf.org, d3e3e3@gmail.com, draft-ietf-babel-v4viav6@ietf.org, martin.vigoureux@nokia.com, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <164617598053.17936.1368129720851802196@ietfa.amsl.com>
Date: Tue, 01 Mar 2022 15:06:20 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/oybMxQbud2RvpyBBn8hkMTKakm4>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2022 23:06:21 -0000
The IESG has approved the following document: - 'IPv4 routes with an IPv6 next hop in the Babel routing protocol' (draft-ietf-babel-v4viav6-08.txt) as Proposed Standard This document is the product of the Babel routing protocol Working Group. The IESG contact persons are Alvaro Retana, John Scudder and Martin Vigoureux. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-babel-v4viav6/ Technical Summary This document update the Babel routing protocol to support announcing routes to an IPv4 prefix with an IPv6 next-hop. This makes it possible for IPv4 traffic to flow through interfaces that have not been assigned an IPv4 address. Since an IPv6 next hop can use an IPv6 link-local address that is autonomously configured, the use of such routes enables a mode of operation where the network core has no statically assigned IP addresses. Working Group Summary The Babel WG was enthusiastic about this update to the Babel protocol. Things were moving along when the group hit the speed bump of what IPv4 source address to use when a v4-via-v6 Babel router generates a v4 ICMP message. It took a little while to resolve that resulting in the current specification which includes use of the IPv4 dummy address if no other source of an IPv4 address is available on the router. Based on the mailing list and WG meetings, there is strong consensus for the draft. Document Quality This a reasonably short document of high quality. v4-via-v6 has been implemented in babeld but not merged into the mainline source yet. It has not yet been implemented in BIRD but the maintainer has indicated their intention to do so. (The use of the IPv4 dummy address when generating a v4 packet with no v4 addresses configured has been submitted for inclusion in the Linux kernel.) Personnel Document Shepherd: Donald Eastlake Area Director: Martin Vigoureux