From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Fwd: [babel] RFC 9229 on IPv4 Routes with an IPv6 Next Hop in the Babel Routing Protocol
Date: Fri, 6 May 2022 11:35:21 -0700 [thread overview]
Message-ID: <CAA93jw4PhQ0pBXWc7_xJn_CuvPT74+J3DMo1_JV8GQAR6Sc+Dw@mail.gmail.com> (raw)
In-Reply-To: <20220506181529.63F1A8DED5@rfcpa.amsl.com>
yea!
---------- Forwarded message ---------
From: <rfc-editor@rfc-editor.org>
Date: Fri, May 6, 2022 at 11:16 AM
Subject: [babel] RFC 9229 on IPv4 Routes with an IPv6 Next Hop in the
Babel Routing Protocol
To: <ietf-announce@ietf.org>, <rfc-dist@rfc-editor.org>
Cc: <rfc-editor@rfc-editor.org>, <drafts-update-ref@iana.org>, <babel@ietf.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9229
Title: IPv4 Routes with an IPv6
Next Hop in the Babel Routing Protocol
Author: J. Chroboczek
Status: Experimental
Stream: IETF
Date: May 2022
Mailbox: jch@irif.fr
Pages: 9
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-babel-v4viav6-08.txt
URL: https://www.rfc-editor.org/info/rfc9229
DOI: 10.17487/RFC9229
This document defines an extension to the Babel routing protocol that
allows announcing 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 is a product of the Babel routing protocol Working Group
of the IETF.
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
babel mailing list
babel@ietf.org
https://www.ietf.org/mailman/listinfo/babel
--
FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
Dave Täht CEO, TekLibre, LLC
parent reply other threads:[~2022-05-06 18:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220506181529.63F1A8DED5@rfcpa.amsl.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4PhQ0pBXWc7_xJn_CuvPT74+J3DMo1_JV8GQAR6Sc+Dw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox