Last Call: <draft-ietf-ospf-xaf-te-06.txt> (OSPF Routing with Cross-Address Family Traffic Engineering Tunnels) to Proposed Standard

The IESG <> Thu, 27 June 2019 13:16 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 61F2F120043; Thu, 27 Jun 2019 06:16:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: "IETF-Announce" <>
Subject: Last Call: <draft-ietf-ospf-xaf-te-06.txt> (OSPF Routing with Cross-Address Family Traffic Engineering Tunnels) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.98.1
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <>
CC:,, Acee Lindem <>,,,
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <>
Date: Thu, 27 Jun 2019 06:16:37 -0700
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 27 Jun 2019 13:16:38 -0000

The IESG has received a request from the Link State Routing WG (lsr) to
consider the following document: - 'OSPF Routing with Cross-Address Family
Traffic Engineering Tunnels'
  <draft-ietf-ospf-xaf-te-06.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the mailing lists by 2019-07-11. Exceptionally, comments may be
sent to instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.


   When using Traffic Engineering (TE) in a dual-stack IPv4/IPv6
   network, the Multiprotocol Label Switching (MPLS) TE Label Switched
   Paths (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 RFC5786 that allows for the easy
   identification of a router's local X-AF IP addresses.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.