[rfc-dist] RFC 9013 on OSPF Advertisement of Tunnel Encapsulations
rfc-editor@rfc-editor.org Tue, 27 April 2021 22:06 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B01D43A2281 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 27 Apr 2021 15:06:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, 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 4CgxuCIaBMSt for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 27 Apr 2021 15:06:11 -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 428E83A2283 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 27 Apr 2021 15:06:11 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id F3D62F407F1; Tue, 27 Apr 2021 15:05:57 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 74510F407EF; Tue, 27 Apr 2021 15:05:57 -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
Message-Id: <20210427220557.74510F407EF@rfc-editor.org>
Date: Tue, 27 Apr 2021 15:05:57 -0700
Subject: [rfc-dist] RFC 9013 on OSPF Advertisement of Tunnel Encapsulations
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: lsr@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9013
Title: OSPF Advertisement of Tunnel Encapsulations
Author: X. Xu, Ed.,
B. Decraene, Ed.,
R. Raszuk,
L. Contreras,
L. Jalil
Status: Standards Track
Stream: IETF
Date: April 2021
Mailbox: xiaohu.xu@capitalonline.net,
bruno.decraene@orange.com,
robert@raszuk.net,
luismiguel.contrerasmurillo@telefonica.com,
luay.jalil@verizon.com
Pages: 10
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ospf-encapsulation-cap-09.txt
URL: https://www.rfc-editor.org/info/rfc9013
DOI: 10.17487/RFC9013
Networks use tunnels for a variety of reasons. A large variety of
tunnel types are defined, and the tunnel encapsulator router needs to
select a type of tunnel that is supported by the tunnel decapsulator
router. This document defines how to advertise, in OSPF Router
Information Link State Advertisements (LSAs), the list of tunnel
encapsulations supported by the tunnel decapsulator.
This document is a product of the Open Shortest Path First IGP 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
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org