[babel] Robert Wilton's Discuss on draft-ietf-babel-source-specific-07: (with DISCUSS and COMMENT)

Robert Wilton via Datatracker <noreply@ietf.org> Thu, 05 November 2020 13:08 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 18C5F3A1075; Thu, 5 Nov 2020 05:08:33 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Wilton via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-babel-source-specific@ietf.org, babel-chairs@ietf.org, babel@ietf.org, Donald Eastlake <d3e3e3@gmail.com>, d3e3e3@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Robert Wilton <rwilton@cisco.com>
Message-ID: <160458171308.17244.3373983961712478100@ietfa.amsl.com>
Date: Thu, 05 Nov 2020 05:08:33 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/Qdhr2I13C527EVXWgowkBDRwXao>
Subject: [babel] Robert Wilton's Discuss on draft-ietf-babel-source-specific-07: (with DISCUSS and COMMENT)
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: Thu, 05 Nov 2020 13:08:33 -0000

Robert Wilton has entered the following ballot position for
draft-ietf-babel-source-specific-07: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-babel-source-specific/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Please see the comment below for further description.

My specific discuss issue relates to clarifying the indexes of the 'source' and
'route' tables to indicate whether they are replacing the 'prefix-len' elements
of the existing 3 tuple indexes, or adding additional elements to the existing
index, effectively making them 5 tuple indexes.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Hi,

Caveat, I'm not familiar with the Babel routing protocol, and I might be
getting the wrong end of the stick.

In some ways I found the content and concepts of this document easy to
understand, but the choice of particular terminology made is hard for me to
know for sure that I am correctly interpreting this document.  In particular, I
am confused between the definition of "source", "destination prefix" and
"source prefix" between this document and draft-ietf-babel-rfc6126bis.

I might be completely confused, but my understanding is that what is called the
"destination prefix" in this document, is effectively what is referred to as
the "source" in draft-ietf-babel-rfc6126bis (e.g., in the Route Table in
section 3.2.5), that also happens to be a prefix.  Is that right?

A further confusion is that this draft seems to sometimes describes prefixes
differently from how they are described in the Babel RFC that it is extending. 
E.g., it seems that in some cases the prefix-length is implicitly part of the
prefix, and in other cases it is described as a separate element (e.g., in the
'source' and 'route' table indexes).

Specifically:

    3.1.  The Source Table

       Every Babel node maintains a source table, as described in [BABEL]
       Section 3.2.5.  A source-specific Babel node extends this table with
       the following field:

       o  The source prefix specifying the source address of packets to
          which this entry applies.

       The source table is now indexed by triples of the form (prefix,
       source prefix, router-id).

According to 3.2.5 of draft-ietf-babel-rfc6126bis, the table is already index
by a triple, i.e. prefix, prefix-len, router-id.  Is the intention of this
document to remove prefix-len as one of the keys to the index?  I presume not,
and that the new table is really indexed by a 5-tuple, i.e., adding
source-prefix and source-prefix length to the existing keys.

       Note that the route entry contains a source (see sections 2 and 3.2.5
       of [BABEL]) which itself contains a source prefix.  These are two
       very different concepts that should not be confused.

Should this reference be to 3.2.6?  It may be helpful to expand on what the
original "source" in a route entry means to avoid any confusion.

If my understanding is right, then I think that this document would greatly
benefit from being very clear on the differences in terminology and probably be
very specific about what they mean in the context of this document.

Regards,
Rob