BGP Colored Prefix Routing (CPR) for SRv6 based Services
draft-ietf-idr-cpr-08

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>, draft-ietf-idr-cpr@ietf.org, idr-chairs@ietf.org, idr@ietf.org, jgs@juniper.net, rfc-editor@rfc-editor.org, shares@ndzh.com
Subject: Document Action: 'BGP Colored Prefix Routing (CPR) for SRv6 based Services' to Informational RFC (draft-ietf-idr-cpr-08.txt)

The IESG has approved the following document:
- 'BGP Colored Prefix Routing (CPR) for SRv6 based Services'
  (draft-ietf-idr-cpr-08.txt) as Informational RFC

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

The IESG contact persons are Gunter Van de Velde, Jim Guichard and John
Scudder.

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

Ballot Text

Technical Summary

   This document describes a mechanism to advertise IPv6 prefixes in BGP
   which are associated with Color Extended Communities to establish
   end-to-end intent-aware paths for Segment Routing over IPv6 (SRv6)
   services.  Such IPv6 prefixes are called "Colored Prefixes", and this
   mechanism is called Colored Prefix Routing (CPR).  In SRv6 networks,
   the Colored prefixes are the SRv6 locators associated with different
   intent.  SRv6 services (e.g.  SRv6 VPN services) with specific intent
   could be assigned with SRv6 Segment Identifiers (SIDs) under the
   corresponding SRv6 locators, which are advertised as Colored
   prefixes.

   This operational methodology allows the SRv6 service traffic to be
   steered into end-to-end intent-aware paths simply based on the
   longest prefix matching of SRv6 Service SIDs to the Colored prefixes.
   The existing IPv6 Address Family and Color Extended Community are
   reused for the advertisement of IPv6 Colored prefixes without new BGP
   extensions, thus this mechanism is easy to interoperate and can be
   deployed incrementally in multi-Autonomous System (AS) networks which
   belong to the same trusted domain.

Working Group Summary

   The shepherd writeup provides a detailed timeline and explanation 
   of the WG process. The eventual consensus to publish as 
   informational reflects engagement from the WG, the various draft 
   proponents, the chairs, and the past and present ADs.

Document Quality

   Per the shepherd writeup:

   This informational draft does not specify additional protocol changes, 
   but provides a description of an applied use of existing protocols.
   These protocols were applied in 3+ existing networks.

Personnel

   The Document Shepherd for this document is Susan Hares. The Responsible
   Area Director is John Scudder.

RFC Editor Note