--- 1/draft-ietf-babel-v4viav6-05.txt 2021-06-18 12:13:10.725672727 -0700 +++ 2/draft-ietf-babel-v4viav6-06.txt 2021-06-18 12:13:10.749673333 -0700 @@ -1,43 +1,44 @@ Network Working Group J. Chroboczek Internet-Draft IRIF, University of Paris -Updates: 8966 (if approved) 9 June 2021 +Updates: 8966 (if approved) 18 June 2021 Intended status: Standards Track -Expires: 11 December 2021 +Expires: 20 December 2021 IPv4 routes with an IPv6 next hop in the Babel routing protocol - draft-ietf-babel-v4viav6-05 + draft-ietf-babel-v4viav6-06 Abstract This document defines an extension to the Babel routing protocol that allows annoncing routes to an IPv4 prefix with an IPv6 next-hop, which makes it possible for IPv4 traffic to flow through interfaces - that have not been assigned an IPv4 address. + that have not been assigned an IPv4 address. This document updates + RFC 8966. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on 11 December 2021. + This Internet-Draft will expire on 20 December 2021. Copyright Notice Copyright (c) 2021 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights @@ -110,21 +111,22 @@ We call a route towards an IPv4 prefix that uses an IPv6 next hop a "v4-via-v6" route. This document describes an extension that allows the Babel routing protocol [RFC8966] to announce v4-via-v6 routes across interfaces that have no IPv4 addresses assigned. Section 3 describes procedures that ensure that all routers can originate ICMPv4 packets, even if they have not been assigned any IPv4 addresses. The extension described in this document is inspired by a previously - defined extension to the BGP protocol [RFC5549]. + defined extension to the BGP protocol [RFC5549]. This document + updates [RFC8966]. 1.1. Specification of Requirements The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. 2. Protocol operation @@ -219,21 +221,21 @@ 2.4. Other TLVs The only other TLVs defined by [RFC8966] that carry an AE field are Next Hop and TLV. Next Hop and IHU TLVs MUST NOT carry the AE 4 (v4- via-v6). 3. ICMPv4 and PMTU discovery The Internet Control Message Protocol (ICMPv4, or simply ICMP) - [RFC792] is a protocol related to IPv4 that is primarily used to + [RFC0792] is a protocol related to IPv4 that is primarily used to carry diagnostic and debugging information. ICMPv4 packets may be originated by end hosts (e.g., the "destination unreachable, port unreachable" ICMPv4 packet), but they may also be originated by intermediate routers (e.g., most other kinds of "destination unreachable" packets). Some protocols deployed in the Internet rely on ICMPv4 packets sent by intermediate routers. Most notably, path MTU Discovery (PMTUd) [RFC1191] is an algorithm executed by end hosts to discover the maximum packet size that a route is able to carry. While there exist @@ -380,29 +382,29 @@ This protocol extension was originally designed, described and implemented in collaboration with Theophile Bastian. Margaret Cullen pointed out the issues with ICMP and helped coin the phrase "v4-via- v6". The author is also indebted to Donald Eastlake, Toke Hoiland- Jorgensen, and David Schinazi. 9. References 9.1. Normative References + [RFC0792] Postel, J., "Internet Control Message Protocol", STD 5, + RFC 792, DOI 10.17487/RFC0792, September 1981, + . + [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . - [RFC792] Postel, J., "Internet Control Message Protocol", STD 5, - RFC 792, DOI 10.17487/RFC0792, September 1981, - . - [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . [RFC8966] Chroboczek, J. and D. Schinazi, "The Babel Routing Protocol", RFC 8966, DOI 10.17487/RFC8966, January 2021, . 9.2. Informative References