Distribution of Link-State and Traffic Engineering Information Using BGP
draft-ietf-idr-rfc7752bis-17

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, aretana.ietf@gmail.com, draft-ietf-idr-rfc7752bis@ietf.org, idr-chairs@ietf.org, idr@ietf.org, jhaas@pfrc.org, rfc-editor@rfc-editor.org, shares@ndzh.com
Subject: Protocol Action: 'Distribution of Link-State and Traffic Engineering Information Using BGP' to Proposed Standard (draft-ietf-idr-rfc7752bis-16.txt)

The IESG has approved the following document:
- 'Distribution of Link-State and Traffic Engineering Information Using
   BGP'
  (draft-ietf-idr-rfc7752bis-16.txt) as Proposed Standard

This document is the product of the Inter-Domain Routing Working Group.

The IESG contact persons are Alvaro Retana, Andrew Alston and John Scudder.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-rfc7752bis/

Ballot Text

Technical Summary

   This document describes a mechanism by which link-state and TE
   information can be collected from networks and shared with external
   components using the BGP routing protocol.  This is achieved using a
   new BGP Network Layer Reachability Information (NLRI) encoding
   format.  The mechanism applies to physical and virtual (e.g., tunnel)
   IGP links.  The mechanism described is subject to policy control.

   Applications of this technique include Application-Layer Traffic
   Optimization (ALTO) servers and Path Computation Elements (PCEs).

   This document obsoletes RFC7752 by completely replacing that
   document.  It makes some small changes and clarifications to the
   previous specification.  This document also obsoletes RFC9029 by
   incorporating the updates that it made to RFC7752.


Working Group Summary

   Nothing specific to highlight.

Document Quality

   The document is of high quality.  Since this is a -bis document, 
   the original content had been through the RFC process and started 
   in good shape.  The new text and clarifications introduced in each 
   revision were well-considered and cleanly worded.

   BGP-LS is widely deployed.  The (short) implementation report for this 
   draft: https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-RFC7752bis%20implementations%20

Personnel

   Document Shepherd: Jeffrey Haas
   Area Director: Alvaro Retana

RFC Editor Note