[babel] Opsdir last call review of draft-ietf-babel-source-specific-06

Dan Romascanu via Datatracker <noreply@ietf.org> Sat, 24 October 2020 09:24 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: babel@ietf.org
Delivered-To: babel@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 44FBE3A0115; Sat, 24 Oct 2020 02:24:17 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dan Romascanu via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: last-call@ietf.org, draft-ietf-babel-source-specific.all@ietf.org, babel@ietf.org, dromasca@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.20.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <160353145725.25780.13209881668449255473@ietfa.amsl.com>
Reply-To: Dan Romascanu <dromasca@gmail.com>
Date: Sat, 24 Oct 2020 02:24:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/wW8qZXt3A5w77cPWX-vl5zPVBHs>
Subject: [babel] Opsdir last call review of draft-ietf-babel-source-specific-06
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Oct 2020 09:24:17 -0000

Reviewer: Dan Romascanu
Review result: Ready

Ready.

This document describes an extension for source-specific routing  (also known
as Source-Address Dependent Routing, SADR) to the Babel routing protocol. It's
a well written, clear and complete document.

>From an operational point of view, operators should pay special attention to
section 6 - Compatibility to the base protocol:

> The protocol extension defined in this document is, to a great
   extent, interoperable with the base protocol defined in [BABEL] (and
   all previously standardised extensions).  More precisely, if non-
   source-specific routers and source-specific routers are mixed in a
   single routing domain, Babel's loop-avoidance properties are
   preserved, and, in particular, no persistent routing loops will
   occur.

  > However, this extension is encoded using mandatory sub-TLVs,
   introduced in [BABEL], and therefore is not compatible with the older
   version of the Babel Routing Protocol [RFC6126] which does not
   support such sub-TLVs.  Consequently, this extension MUST NOT be used
   with routers implementing RFC 6126, otherwise persistent routing
   loops may occur.

There are no manageability considerations in this document. I assume that
management actions and objects, if relevant, will be included in complementary
documents.