[Lsr] RFC 8687 on OSPF Routing with Cross-Address Family Traffic Engineering Tunnels

rfc-editor@rfc-editor.org Wed, 27 November 2019 18:50 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 07AB2120BBE; Wed, 27 Nov 2019 10:50:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id btDwocFJM-ep; Wed, 27 Nov 2019 10:50:35 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2DE0120B66; Wed, 27 Nov 2019 10:50:34 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id EE8F4F4071D; Wed, 27 Nov 2019 10:50:07 -0800 (PST)
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, lsr@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20191127185007.EE8F4F4071D@rfc-editor.org>
Date: Wed, 27 Nov 2019 10:50:07 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/lIX5cqjsbRXP0LuTA0b9EwaxiUw>
Subject: [Lsr] =?utf-8?q?RFC_8687_on_OSPF_Routing_with_Cross-Address_Fami?= =?utf-8?q?ly_Traffic_Engineering_Tunnels?=
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Nov 2019 18:50:37 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 8687

        Title:      OSPF Routing with Cross-Address Family 
                    Traffic Engineering Tunnels 
        Author:     A. Smirnov, 
                    A. Retana,
                    M. Barnes
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2019
        Mailbox:    as@cisco.com, 
        Pages:      8
        Updates:    RFC 5786

        I-D Tag:    draft-ietf-ospf-xaf-te-07.txt

        URL:        https://www.rfc-editor.org/info/rfc8687

        DOI:        10.17487/RFC8687

When using Traffic Engineering (TE) in a dual-stack IPv4/IPv6
network, the Multiprotocol Label Switching (MPLS) TE Label Switched
Path (LSP) infrastructure may be duplicated, even if the destination
IPv4 and IPv6 addresses belong to the same remote router.   In order
to achieve an integrated MPLS TE LSP infrastructure, OSPF routes must
be computed over MPLS TE tunnels created using information propagated
in another OSPF instance. This issue is solved by advertising
cross-address family (X-AF) OSPF TE information.

This document describes an update to RFC 5786 that allows for the
easy identification of a router's local X-AF IP addresses.

This document is a product of the Link State Routing 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

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