Re: [babel] information model supports IPv6 operation only

David Schinazi <> Thu, 04 February 2021 21:14 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8CFEF3A183C for <>; Thu, 4 Feb 2021 13:14:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Status: No, score=-2.097 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_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id rIW55hWGqC9Y for <>; Thu, 4 Feb 2021 13:14:12 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::533]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 005763A183A for <>; Thu, 4 Feb 2021 13:14:11 -0800 (PST)
Received: by with SMTP id o7so3029766pgl.1 for <>; Thu, 04 Feb 2021 13:14:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=isx8hAsRmnDA/k73lnqOVphKphOpIIgVr0ysgQtj5O4=; b=coLyXQrZto7rrie2xzjyPSbqZ8oYenIXuNRMJr9Pu4MnFtHPczg0IR8XbddqlZGThD DQt6/cCfMQf5yxhwOvYbIOAP8oYCeifyeIKe99cddQqgULlglnfEZhi0ps5tnK5tJUMF cSGxnZ2emFYZIWgsmF55PeuCqGvgoyCa5eou3CNC8yFoz3XL+c1AiwxZpm5dQTKk4h85 VAgMM5gNmZTqu5X84s8tm2sJokUKJ0fhS7Q94ubYoCcQnGs3wpIybKRrpvGmtuf2nUg7 pqn4tkK5iX3ygZE4M+CcIz/BKoUedLZadwB2pxJ6JNvsZb1xgA1baJfZs6LYTNwSlDu5 nQ5g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=isx8hAsRmnDA/k73lnqOVphKphOpIIgVr0ysgQtj5O4=; b=h6AT7ZlSbgtAvfUa6JKNYLjBZlHqlqXzBalXT5fJkUdqf+1YXzxOJZJh9ezmnTg2la HYnX1EcDDkbIGpS+wgHmr04KAcin0gCTtkCchTwa41KohYpQQcb8bjtDiMmuoigeacte FFUqV2CE5VJ7a32Rdk87gP5yQwmFZfpkNQ4fSf0uQCxORk6jHcOUEmlBpz6BL1U90AA7 OvFgsoExRuH31qeqn4PvQ2Hxxi1/piPt6s9nzV1KAlaUVD66s1S7qqm0d6ZnJeKN153V qY8X2yMQf4O5yTIHaMmaettVxaTIw2HMaS80SdLT0+iIkWjSlf76H40qLN0Bft4tBHnM DB2w==
X-Gm-Message-State: AOAM530DUEuKbQvvVEfY3An2zxV3XhtnS4yy2pfINx//W10UkOjY8GGn J0D8R5v0TAusDIa52mL8Y8u4JaFgkuI48hV8RmnDchrhPKQ=
X-Google-Smtp-Source: ABdhPJzNe37S8wvC2gQzBSzCR/Mcw+SE0nXoP6Li1zUVOkoZ02giyFe3+n2uKjzOEeeVUXMKNrFLIcOKRZiuNCXsQFk=
X-Received: by 2002:a63:1865:: with SMTP id 37mr912539pgy.206.1612473251321; Thu, 04 Feb 2021 13:14:11 -0800 (PST)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: David Schinazi <>
Date: Thu, 4 Feb 2021 13:14:00 -0800
Message-ID: <>
Cc: "" <>
Content-Type: multipart/alternative; boundary="0000000000005adf4005ba892f30"
Archived-At: <>
Subject: Re: [babel] information model supports IPv6 operation only
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 04 Feb 2021 21:14:14 -0000

The added language looks good to me.
One optional note, we can now replace references to
I-D.ietf-babel-rfc6126bis with RFC8966 :-)


On Thu, Feb 4, 2021 at 5:56 AM STARK, BARBARA H <> wrote:

> Hi Babel WG,
> Donald suggested I make sure the WG members were comfortable with the
> language I've now included (to resolve IESG / IETF LC comments) in the info
> model draft, to express the fact it doesn't include parameters for
> operating Babel over IPv4.
> At the end of the abstract I added "This information model only includes
>    parameters and parameter values useful for managing Babel over IPv6."
> At the end of the Introduction I added the paragraph:
>    This information model only includes parameters and parameter values
>    useful for managing Babel over IPv6.  This model has no parameters or
>    values specific to operating Babel over IPv4, even though
>    [I-D.ietf-babel-rfc6126bis] does define a multicast group for sending
>    and listening to multicast announcements on IPv4.  There is less
>    likelihood of breakage due to inconsistent configuration and
>    increased implementation simplicity if Babel is operated always and
>    only over IPv6.  Running Babel over IPv6 requires IPv6 at the link
>    layer and does not need advertised prefixes, router advertisements or
>    DHCPv6 to be present in the network.  Link-local IPv6 is widely
>    supported among devices where Babel is expected to be used.  Note
>    that Babel over IPv6 can be used for configuration of both IPv4 and
>    IPv6 routes.
> If this language is objectionable, please let me know. Thx,
> Barbara
> _______________________________________________
> babel mailing list