[OSPF] Experimental support of OSPFv2 Segment Routing in Free Range Routing

Olivier Dugeon <olivier.dugeon@orange.com> Tue, 06 February 2018 20:13 UTC

Return-Path: <olivier.dugeon@orange.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1160D127873; Tue, 6 Feb 2018 12:13:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.943
X-Spam-Level:
X-Spam-Status: No, score=-1.943 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a1nEXE6Zk4pt; Tue, 6 Feb 2018 12:13:00 -0800 (PST)
Received: from p-mail1.rd.orange.com (p-mail1.rd.orange.com [161.106.1.2]) by ietfa.amsl.com (Postfix) with ESMTP id D51AC12773A; Tue, 6 Feb 2018 12:12:59 -0800 (PST)
Received: from p-mail1.rd.orange.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 6EA7A410273; Tue, 6 Feb 2018 21:12:58 +0100 (CET)
Received: from FTRDCH01.rd.francetelecom.fr (unknown [10.194.32.11]) by p-mail1.rd.orange.com (Postfix) with ESMTP id 5ECEC410272; Tue, 6 Feb 2018 21:12:58 +0100 (CET)
Received: from renot.local (10.192.150.9) by FTRDCH01.rd.francetelecom.fr (10.194.32.11) with Microsoft SMTP Server id 14.3.382.0; Tue, 6 Feb 2018 21:12:57 +0100
To: SPRING WG List <spring@ietf.org>, OSPF WG List <ospf@ietf.org>
From: Olivier Dugeon <olivier.dugeon@orange.com>
Message-ID: <7ff65339-d8f2-c640-2f68-bf9ddea7b871@orange.com>
Date: Tue, 06 Feb 2018 21:12:57 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------18CE4B4DB6DC81C48B177BFD"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/pK99ukI0jLHFQ79sTCyjiuCn6Ms>
Subject: [OSPF] Experimental support of OSPFv2 Segment Routing in Free Range Routing
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Feb 2018 20:13:02 -0000

Hi all,

We are please to announce that we have added Experimental support of OSPF SR
(draft-ietf-ospf-segment-routing-extensions-24) in Free Range Routing
protocol suite https://frrouting.org

This feature is available on the master branch: 
https://github.com/FRRouting/frr
and will be part of the future 4.0 release.

Supported Features:

* Automatic computation of Primary and Backup Adjacency SID with
Cisco experimental remote IP address
* SRGB configuration
* Prefix configuration for Node SID with optional NO-PHP flag (Linux
kernel support both mode)
* Node MSD configuration (with Linux Kernel >= 4.10 a maximum of 32 labels
could be stack)
* Automatic provisioning of MPLS table
* Static route configuration with label stack up to 32 labels

Interoperability:
* tested on various topology including point-to-point and LAN interfaces
in a mix of Free Range Routing instance and Cisco IOS-XR 6.0.x
* check OSPF LSA conformity with latest wireshark release 2.5.0-rc

Known limitations

* Runs only within default VRF
* Only single Area is supported. ABR is not yet supported
* Only SPF algorithm is supported
* Extended Prefix Range is not supported
* MPLS table are not flush at startup. Thus, restarting zebra process is
   mandatory to remove old MPLS entries in the data plane after a crash of
   ospfd daemon
* With NO Penultimate Hop Popping, it is not possible to express a Segment
   Path with an Adjacency SID due to the impossibility for the Linux 
Kernel to
   perform double POP instruction.

For details implementation & instructions on how to use this new feature,
please consult doc/OSPF-SR.rst.

Regards

FRR team