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

"Acee Lindem (acee)" <acee@cisco.com> Wed, 07 February 2018 14:43 UTC

Return-Path: <acee@cisco.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 73E2512D779; Wed, 7 Feb 2018 06:43:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Level:
X-Spam-Status: No, score=-14.53 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 nMPVyihWHwzG; Wed, 7 Feb 2018 06:43:22 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C476712AAB6; Wed, 7 Feb 2018 06:43:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11882; q=dns/txt; s=iport; t=1518014601; x=1519224201; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=VRjcabMLRSZ/B9elnnTN9oWAmHddiJC1FKv45nHcBWs=; b=b/8+KeHEnxeKuo7LkVHfjkCNQ2LKSum0svfebwejNEMAKyAcJk8XqvnM 8c/VUicM0faQNnnONPnlaXdZoWWAmx1cZETPIGv4/BL/UsqQK4o//gv9m 0jcjk8T3Tbw73xbx0DR+/U/199A+ARcs64Yye3aNKDudP0Onjko55zxNw I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C+AQDvD3ta/4oNJK1dGQEBAQEBAQEBAQEBAQcBAQEBAYJZeGZwKAqDW5hKggKReYVZghgKH4UcAhqCT1YWAQIBAQEBAQECayiFIwEBAQQjZgIBCBEDAQIrAgICMB0IAgQBEhqJN2SxfoIniHaCCgEBAQEBAQEBAQEBAQEBAQEBAQEBARgFhHWCFYM+ASmDBYMvAgKBK2QGgnExgjQFiwdrmDcJAogcjV0OghCGJ4t5EI1qiWMCERkBgTsBJgIwgVBwFT0qAYIbCYJMHIIGeIx9gRcBAQE
X-IronPort-AV: E=Sophos; i="5.46,473,1511827200"; d="scan'208,217"; a="67561047"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Feb 2018 14:43:20 +0000
Received: from XCH-RTP-011.cisco.com (xch-rtp-011.cisco.com [64.101.220.151]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id w17EhK0a031682 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 7 Feb 2018 14:43:20 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-011.cisco.com (64.101.220.151) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 7 Feb 2018 09:43:19 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1320.000; Wed, 7 Feb 2018 09:43:19 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Olivier Dugeon <olivier.dugeon@orange.com>, SPRING WG List <spring@ietf.org>, OSPF WG List <ospf@ietf.org>
Thread-Topic: [OSPF] Experimental support of OSPFv2 Segment Routing in Free Range Routing
Thread-Index: AQHTn4bp9/slLb3lz0m6WGKUCzGbA6OZBOiA
Date: Wed, 07 Feb 2018 14:43:19 +0000
Message-ID: <E21A2D91-38CB-47F9-802E-5C390B25C55E@cisco.com>
References: <7ff65339-d8f2-c640-2f68-bf9ddea7b871@orange.com>
In-Reply-To: <7ff65339-d8f2-c640-2f68-bf9ddea7b871@orange.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.195]
Content-Type: multipart/alternative; boundary="_000_E21A2D9138CB47F9802E5C390B25C55Eciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/fKaz57bJAstaF_RyfrAIEJUO1_Q>
Subject: Re: [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: Wed, 07 Feb 2018 14:43:24 -0000

Hi Olivier,

Great news Olivier! I’m hoping you are looking at OSPFv3 Extended LSAs and OSPFv3 SR as well.

Thanks,
Acee

From: OSPF <ospf-bounces@ietf.org> on behalf of Olivier Dugeon <olivier.dugeon@orange.com>
Date: Tuesday, February 6, 2018 at 3:13 PM
To: SPRING WG List <spring@ietf.org>, OSPF WG List <ospf@ietf.org>
Subject: [OSPF] Experimental support of OSPFv2 Segment Routing in Free Range Routing

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