[babel] RFC 9079 on Source-Specific Routing in the Babel Routing Protocol
rfc-editor@rfc-editor.org Thu, 26 August 2021 23:00 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 2EFB03A011B;
Thu, 26 Aug 2021 16:00:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001,
URIBL_BLOCKED=0.001] autolearn=unavailable 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 qB2t62ZhPG2X; Thu, 26 Aug 2021 16:00:04 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 615163A0128;
Thu, 26 Aug 2021 16:00:02 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30)
id A0EAEF406F0; Thu, 26 Aug 2021 15:59:47 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, babel@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210826225947.A0EAEF406F0@rfc-editor.org>
Date: Thu, 26 Aug 2021 15:59:47 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/EOO1lwb9Y9yij9UWLNCyTkoBPNs>
Subject: [babel] =?utf-8?q?RFC_9079_on_Source-Specific_Routing_in_the_Bab?=
=?utf-8?q?el_Routing_Protocol?=
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: Thu, 26 Aug 2021 23:00:12 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9079
Title: Source-Specific Routing in the Babel
Routing Protocol
Author: M. Boutier,
J. Chroboczek
Status: Standards Track
Stream: IETF
Date: August 2021
Mailbox: boutier@irif.fr,
jch@irif.fr
Pages: 13
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-babel-source-specific-08.txt
URL: https://www.rfc-editor.org/info/rfc9079
DOI: 10.17487/RFC9079
Source-specific routing, also known as Source Address Dependent
Routing (SADR), is an extension to traditional next-hop routing where
packets are forwarded according to both their destination address and
their source address. This document describes an extension for
source-specific routing to the Babel routing protocol.
This document is a product of the Babel routing protocol Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. 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