Skip to main content

OSPFv3 Extensions for Segment Routing over IPv6 (SRv6)
draft-ietf-lsr-ospfv3-srv6-extensions-15

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>, acee@cisco.com, draft-ietf-lsr-ospfv3-srv6-extensions@ietf.org, jgs@juniper.net, lsr-chairs@ietf.org, lsr@ietf.org, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'OSPFv3 Extensions for SRv6' to Proposed Standard (draft-ietf-lsr-ospfv3-srv6-extensions-15.txt)

The IESG has approved the following document:
- 'OSPFv3 Extensions for SRv6'
  (draft-ietf-lsr-ospfv3-srv6-extensions-15.txt) as Proposed Standard

This document is the product of the Link State Routing Working Group.

The IESG contact persons are Jim Guichard, Andrew Alston and John Scudder.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-lsr-ospfv3-srv6-extensions/


Ballot Text

Technical Summary

   The Segment Routing (SR) architecture allows a flexible definition of
   the end-to-end path by encoding it as a sequence of topological
   elements called segments.  It can be implemented over an MPLS or IPv6
   data plane.  This document describes the OSPFv3 extensions required
   to support Segment Routing over the IPv6 data plane (SRv6).

Working Group Summary

  There was no real controversy although there was discussion as to whether it
  was a good idea to have separate Link State Advertisements (LSAs) for the
  SRv6 Locators as opposed to using the existing LSAs. Unlike IS-IS, one of
  the advantages of OSPFv3 is that disjoint information can be advertised in
  separate LSAs.

  Review by OSPFv3 implementors revealed that the OSPFv3 PrefixOptions needed
  to be advertised in the SRv6 Locator TLV. This specification adds the AC-Bit
  (AnyCast Bit) which is applicable to all usages of the OSPFv3 PrefixOptions.

Document Quality

   The shepherd's report notes nothing exceptional, and doesn't identify any
   implementations other than "a Huawei implemenation underway but it has not 
   been released yet and there is no report."

Personnel

   The Document Shepherd for this document is Acee Lindem. The Responsible
   Area Director is John Scudder.

RFC Editor Note