
From nobody Fri Jan 14 14:58:28 2022
Return-Path: <d3e3e3@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7CBC3A14B9; Fri, 14 Jan 2022 14:58:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level: 
X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Dww4fGJcO0K; Fri, 14 Jan 2022 14:58:22 -0800 (PST)
Received: from mail-il1-x12c.google.com (mail-il1-x12c.google.com [IPv6:2607:f8b0:4864:20::12c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 708713A14B6; Fri, 14 Jan 2022 14:58:22 -0800 (PST)
Received: by mail-il1-x12c.google.com with SMTP id i14so9576983ila.11; Fri, 14 Jan 2022 14:58:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=mime-version:from:date:message-id:subject:to:cc; bh=BEvj0hRfW0EOfW56RIdNSsHtIpqz90DhnCs8IAFaGW0=; b=mT3g4OtzaB5Kn4Vcszl7uZlDXLMiwPSmhYrahr/Vkr6ERw006lhXOecbjzFwHjACO7 LuIRqzqV/YOD34qtcbyopxFYh4O1OLw6cnyVJtS0u/COCQSUG18XzWkSarPTN0YmOg3K p144Mxw5aWCxRMFHUEqoYsQiMjB/et3rOj1U0th/PYueSjYlcb+yp7a5vD4VUK3CWmeU 6kDyYcpUgGLkyaViq4ldPV/Y8urGnmmu50z6YprRp1zMsxP9baCN2D/6fExA4fxHoltV 9ak7G4fPOYEBdYJ+aOaGHM+fblD+SiAC3V9raqMQhJyUTfhhe1lETm2y9I3KDaCukt7o BS9Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=BEvj0hRfW0EOfW56RIdNSsHtIpqz90DhnCs8IAFaGW0=; b=LwzTXEvJbvV1KibmB+peK/2L1VVi7aekwfK/ox/GuRZt+o8glB3arBz523d5+/drhH 1EidJ36bJWCWOBHl3ShVlZ20jpcwgNeE2iu0FfkhOEPK+jLzpQfZ+RPIgXtTtnzTrvWC VeiNpwEkqWE/It6H5iNMSdR4iIg3uiW2EP2xNdns6w8JP5mon+Ce4FgDfQ8K3hv4rqqq 6Y90gqHAAhgZhETynlXBgo2YdlSS1URo6765fhlbH/Uy5qZXQNfLe3mRkjU1SP/u1PGD yU0rGTmMcDbnSuVFMb4uuQBaaFfAf7vZ4xT2QlOso65WwcOB8J/Y6iD184mpjN0JAIXG jPYw==
X-Gm-Message-State: AOAM532qPS2BWcIsA66w7tSyqo4xQkpOvP1vCFSCjmGUdHrCFmAHV/pK 8PUL4WHGQ0CqDgQAc0keACwj5OFCMQFC7QzzLNt+4fNtpFY=
X-Google-Smtp-Source: ABdhPJxyWy364QCUYbR9BKDLbLt50RwZN1arDA/v+U5XzrHOyyGmVg7OYCd9Q8gilp0hidnRLTjL79vKG/kE6nBVneY=
X-Received: by 2002:a05:6e02:1645:: with SMTP id v5mr5957574ilu.106.1642201100964;  Fri, 14 Jan 2022 14:58:20 -0800 (PST)
MIME-Version: 1.0
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 14 Jan 2022 17:58:10 -0500
Message-ID: <CAF4+nEGHMR06gpCV0ySKezHy0q9Y+X5mohiw5_vwAkND3C46YA@mail.gmail.com>
To: Babel at IETF <babel@ietf.org>
Cc: babel-chairs <babel-chairs@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/LiFcniiYCJoPZ5t3H9h8PJgizm0>
Subject: [babel] Babel WG at IETF 113
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jan 2022 22:58:27 -0000

Hi,

The upcoming IETF 113 meeting, 19-25 March, will include both in
person participation in Vienna as well as remote participation.
https://www.ietf.org/how/meetings/113/

Should there be a Babel WG meeting at IETF 113? If you think there
should be or wish to present at it, please reply to this message or
contact the Chair in the next week.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 d3e3e3@gmail.com


From nobody Sun Jan 16 08:30:23 2022
Return-Path: <internet-drafts@ietf.org>
X-Original-To: babel@ietf.org
Delivered-To: babel@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C3AD43A1118; Sun, 16 Jan 2022 08:30:16 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: babel@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: babel@ietf.org
Message-ID: <164235061674.7377.8811938166193166476@ietfa.amsl.com>
Date: Sun, 16 Jan 2022 08:30:16 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/Fl2K1G3rCY-pE6rkyeEMUt9Wieg>
Subject: [babel] I-D Action: draft-ietf-babel-v4viav6-07.txt
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Jan 2022 16:30:17 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Babel routing protocol WG of the IETF.

        Title           : IPv4 routes with an IPv6 next hop in the Babel routing protocol
        Author          : Juliusz Chroboczek
	Filename        : draft-ietf-babel-v4viav6-07.txt
	Pages           : 10
	Date            : 2022-01-16

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.  This document updates
   RFC 8966.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-babel-v4viav6/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-babel-v4viav6-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-babel-v4viav6-07


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts



From nobody Sun Jan 16 08:34:08 2022
Return-Path: <jch@irif.fr>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39E523A1153 for <babel@ietfa.amsl.com>; Sun, 16 Jan 2022 08:34:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FAbv5Uk9JQ4g for <babel@ietfa.amsl.com>; Sun, 16 Jan 2022 08:34:05 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 965643A1151 for <babel@ietf.org>; Sun, 16 Jan 2022 08:34:04 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/82085) with ESMTP id 20GGY0YC016526 for <babel@ietf.org>; Sun, 16 Jan 2022 17:34:00 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id DFDE410BD13 for <babel@ietf.org>; Sun, 16 Jan 2022 17:34:00 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id gynts4Bemrgx for <babel@ietf.org>; Sun, 16 Jan 2022 17:33:59 +0100 (CET)
Received: from pirx.irif.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 806CF10BD10 for <babel@ietf.org>; Sun, 16 Jan 2022 17:33:59 +0100 (CET)
Date: Sun, 16 Jan 2022 17:33:59 +0100
Message-ID: <87czkrtzbc.wl-jch@irif.fr>
From: Juliusz Chroboczek <jch@irif.fr>
To: babel@ietf.org
In-Reply-To: <164235061674.7377.8811938166193166476@ietfa.amsl.com>
References: <164235061674.7377.8811938166193166476@ietfa.amsl.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.1 Mule/6.0
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Sun, 16 Jan 2022 17:34:00 +0100 (CET)
X-Miltered: at korolev with ID 61E448F8.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 61E448F8.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@irif.fr>
X-j-chkmail-Score: MSGID : 61E448F8.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/kNncULSZ6i1DGWV7HUxoeoATF7c>
Subject: Re: [babel] I-D Action: draft-ietf-babel-v4viav6-07.txt
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Jan 2022 16:34:07 -0000

> 	Filename        : draft-ietf-babel-v4viav6-07.txt

This integrates the tweaks requested by Martin.  The only change I did not
integrate was the removal of the option to borrow an address from
a different interface, since this usage is well-established, and reflects
the default behaviour of Linux (and probably other systems that use the
weak host model).

My apologies for the delay, it's a rather complicated period on my side.

-- Juliusz


From nobody Mon Jan 24 15:20:22 2022
Return-Path: <d3e3e3@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6CA63A1674; Mon, 24 Jan 2022 15:20:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level: 
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HYVYBvB57fYM; Mon, 24 Jan 2022 15:20:19 -0800 (PST)
Received: from mail-il1-x129.google.com (mail-il1-x129.google.com [IPv6:2607:f8b0:4864:20::129]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F7FA3A1672; Mon, 24 Jan 2022 15:20:19 -0800 (PST)
Received: by mail-il1-x129.google.com with SMTP id x3so612878ilm.3; Mon, 24 Jan 2022 15:20:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GeEFXx4EiHR3SvVcKs7ATxIXYvHHjshM9O+qwXdUo3A=; b=djTl0mcCKJsjepPbimIbjLGzBJi+oK14aFkwJPZqFeKJcvLr8llhSSsvd12GskDeWU IOb763bds9gUDMjYAmxyhYRG0wrYu3vNnkMZCy5UJs1sJjZD9iUnIXOf0rvs75VRZ/3i 1GcBC+gl+XvhojLcvwxubroe0HcDA6F+aJUx2RfoLZZoTKkdxXVifvFtzLSVdIMier3R O2yoLxxaTWdORhYqeHi0uRTfd2YLidVh7q51ITsDkmrFcD/o7lWakxGtY0YgipVoYqqr MIcfdyxvfH/ejzFr+NZ75u754QYwx2CBAy1uwg5u4SgrbBqkZo2ihU6KClfQYXsr/bqn CoRw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GeEFXx4EiHR3SvVcKs7ATxIXYvHHjshM9O+qwXdUo3A=; b=ZNHta9Bd4JIvsOhDmPETr9qWvwO1Vyv/ywGO+RQo7z1k7tK3wAUPSLoPApp3kHyB7J lJbqK/YUTZX7IEq7712CcUU+rONLPWJIy0+F1o+uukIx2OneSlE0cqfNLKBI/otjysJ6 02r3P33Prkwkn0/8tLBQMyM6hOvvqBGCS0gAcSoiez+LwdQPdnD7Y9fPmYQnddt/ZyGr nCK9tRqocnxY8aord9Gs7MoxhIjy+h0kL61l5GNZ2L4ENHUQBdiqV6Ees9++4Wk3H+hx frq8fm+LILfZ423Ld8T/QCF7553P1NoMzysPSAicYQt4wZUs2Mi4hKdJnEoDLJeAxhW+ IKrA==
X-Gm-Message-State: AOAM530qz58wX60XZbB75KdObKgCBiYxXJf8vWJimjckprbBfsqSpEHq KrhdtiERv6OqVggfWp1vxEB+XnOWmsnCT0UqwQpyqob9
X-Google-Smtp-Source: ABdhPJzw/9Cf34uLPKFc+esciiHJZxzOIC7RlONE0V/e4NVbatSRjorT+sAarj+nASnZcUetmdeBG9H2JqyDMTZ/Tmo=
X-Received: by 2002:a05:6e02:1645:: with SMTP id v5mr10235121ilu.106.1643066417420;  Mon, 24 Jan 2022 15:20:17 -0800 (PST)
MIME-Version: 1.0
References: <CAF4+nEGHMR06gpCV0ySKezHy0q9Y+X5mohiw5_vwAkND3C46YA@mail.gmail.com>
In-Reply-To: <CAF4+nEGHMR06gpCV0ySKezHy0q9Y+X5mohiw5_vwAkND3C46YA@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 24 Jan 2022 18:20:06 -0500
Message-ID: <CAF4+nEFC1YyZoDXVoA_uN72fEacp73jumJDSNXMHaLObxVr+0w@mail.gmail.com>
To: Babel at IETF <babel@ietf.org>
Cc: babel-chairs <babel-chairs@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/GiugEe0d0jyf8lCmPJSgbObxNM0>
Subject: Re: [babel] Babel WG at IETF 113
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jan 2022 23:20:21 -0000

Hi,

Please respond to the message below if you think there should be a
Babel WG meeting at IETF 113 in March. If I don't hear anything, there
will not be a WG meeting.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 d3e3e3@gmail.com

On Fri, Jan 14, 2022 at 5:58 PM Donald Eastlake <d3e3e3@gmail.com> wrote:
>
> Hi,
>
> The upcoming IETF 113 meeting, 19-25 March, will include both in
> person participation in Vienna as well as remote participation.
> https://www.ietf.org/how/meetings/113/
>
> Should there be a Babel WG meeting at IETF 113? If you think there
> should be or wish to present at it, please reply to this message or
> contact the Chair in the next week.
>
> Thanks,
> Donald
> ===============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  2386 Panoramic Circle, Apopka, FL 32703 USA
>  d3e3e3@gmail.com


From nobody Tue Jan 25 07:29:45 2022
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: babel@ietf.org
Delivered-To: babel@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 798A43A0AC1; Tue, 25 Jan 2022 07:29:38 -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>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.43.0
Auto-Submitted: auto-generated
Precedence: bulk
CC: babel-chairs@ietf.org, babel@ietf.org, d3e3e3@gmail.com, draft-ietf-babel-v4viav6@ietf.org, martin.vigoureux@nokia.com
Reply-To: last-call@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <164312457839.26764.16088001905261967769@ietfa.amsl.com>
Date: Tue, 25 Jan 2022 07:29:38 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/B9nAfIyMj5KQx1b5P8p9i4AqOfg>
Subject: [babel] Last Call: <draft-ietf-babel-v4viav6-07.txt> (IPv4 routes with an IPv6 next hop in the Babel routing protocol) to Proposed Standard
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jan 2022 15:29:39 -0000

The IESG has received a request from the Babel routing protocol WG (babel) to
consider the following document: - 'IPv4 routes with an IPv6 next hop in the
Babel routing protocol'
  <draft-ietf-babel-v4viav6-07.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2022-02-08. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

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.  This document updates
   RFC 8966.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-babel-v4viav6/



No IPR declarations have been submitted directly on this I-D.






From nobody Thu Jan 27 10:20:26 2022
Return-Path: <noreply@ietf.org>
X-Original-To: babel@ietf.org
Delivered-To: babel@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B2973A0A1F; Thu, 27 Jan 2022 10:20:25 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Bernie Volz via Datatracker <noreply@ietf.org>
To: <int-dir@ietf.org>
Cc: babel@ietf.org, draft-ietf-babel-v4viav6.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <164330762512.24177.752612723340018892@ietfa.amsl.com>
Reply-To: Bernie Volz <bevolz@gmail.com>
Date: Thu, 27 Jan 2022 10:20:25 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/m-L5ivWSu6A_LP575Ga6_XkHGC4>
Subject: [babel] Intdir last call review of draft-ietf-babel-v4viav6-07
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jan 2022 18:20:25 -0000

Reviewer: Bernie Volz
Review result: Ready with Nits

I am an assigned INT directorate reviewer for draft-ietf-babel-v4viav6-07.
These comments were written primarily for the benefit of the Internet Area
Directors. Document editors and shepherd(s) should treat these comments just
like they would treat comments from any other IETF contributors and resolve
them along with any other Last Call comments that have been received. For more
details on the INT Directorate, see
https://datatracker.ietf.org/group/intdir/about/.

Based on my review, the document IS ready to go to IETF Last Call and therefore
can be forwarded to the IESG.

The following are some nits:

In Abstract and Introduction, the "updates RFC 8966" is really that it extends
RFC 8966 as this adds additional capabilities ("defines extensions"). This is
probably a minor nit, but someone may be looking for explicit that "fixes"
issues in RFC 8966 when there is really none and an implementation that adheres
to RFC 8966 can continue to function as it has before. I also know that this is
an open issue within the IETF as there aren't clear tags to distinguish these
kinds of changes.

For section 2, I wonder whether "the fame format as the existing AE for IPv4
addresses" would benefit by calling that AE value (1) out (as is done in other
places?

Section 2.3 says "Prefix and seqno requests" but RFC8966 does not appear to
have a "Prefix request"? I think this should be "Route"?

For section 3 (last paragraph), does this imply that if the router has
127.0.0.1 assigned it can be used for ICMPv4 packets? Or is this not common for
routers?

For section 4.2.2, would changing the title from "Other TLVs" to just "Route
Request and Seqno Request" be useful (as these are the only other TLVs). And,
would a reference back to section 2.3 be useful (as use of AE value 4 is SHOULD
NOT).

For 6, this is usually a request to IANA to update - the RFC editor would
change it to indicate the allocated value? (Minor as it could only be an issue
if there were multiple documents trying to assign value 4.)

Thanks.

- Bernie Volz


