Re: [babel] Work to do (IHU TLV AE 0)

Denis Ovsienko <denis@ovsienko.info> Mon, 26 March 2018 21:16 UTC

Return-Path: <denis@ovsienko.info>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAADC124234 for <babel@ietfa.amsl.com>; Mon, 26 Mar 2018 14:16:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level:
X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ovsienko.info
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 Rtu_2T2KftQL for <babel@ietfa.amsl.com>; Mon, 26 Mar 2018 14:16:57 -0700 (PDT)
Received: from sender-of-o51.zoho.com (sender-of-o51.zoho.com [135.84.80.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FA4F126CB6 for <babel@ietf.org>; Mon, 26 Mar 2018 14:16:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1522099010; s=zohomail; d=ovsienko.info; i=denis@ovsienko.info; h=Date:From:To:Message-ID:In-Reply-To:References:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding; l=2025; bh=PzBM9XPndZTZurZLyIUjwoZyWsCTZLPHciSaffr1SzM=; b=k8H3/2fc6VXCIO4F96IV/IFhojD7WCnv71AifFiahE3HqGetIJJmll6SB6vW0GP9 2eso2OPyH9pdF0pYjM25AmmRiNZbuufbWtlHxoa2a4unwxW1FoOCmUBDEiOf7W+QMAX viyAm1xGcJZvi0HzvWzCSk9RsKx9Ieh+pOFeuxo8=
Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1522099010864376.536998300641; Mon, 26 Mar 2018 14:16:50 -0700 (PDT)
Date: Mon, 26 Mar 2018 22:16:50 +0100
From: Denis Ovsienko <denis@ovsienko.info>
To: Babel at IETF <babel@ietf.org>
Message-ID: <162642bbd2f.1266904f2130878.513114391174006256@ovsienko.info>
In-Reply-To: <87r2o6k2jm.wl-jch@irif.fr>
References: <87k1u1uekt.wl-jch@irif.fr> <16263df4d35.c134482a130573.7360272675488949721@ovsienko.info> <87r2o6k2jm.wl-jch@irif.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: Medium
User-Agent: Zoho Mail
X-Mailer: Zoho Mail
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/VZyPkQAK8Rk_QEK5yXFP1JQgt14>
Subject: Re: [babel] Work to do (IHU TLV AE 0)
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
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: Mon, 26 Mar 2018 21:16:59 -0000

---- On Mon, 26 Mar 2018 21:25:01 +0100 Juliusz Chroboczek  wrote ---- 
>> There is one more important thing to check before setting 6126bis in 
>> stone. The current revision of 6126bis says an IHU TLV may omit Address 
>> (AE = 0). The current revision of 7298bis needs Address meaningfully set 
>> so that the receiving node can pick the TS/PC sub-TLV from the IHU TLV 
>> and translate that to the age threshold in units of seconds. 
> 
>I need to think that over. 
> 
>> 1. 6126bis and 7298bis coordinate to have IHU AE 1 or 3 when 7298bis is 
>> enabled 
>> 2. 6126bis simply mandates Address in IHU (AE = 1 or 3) 
> 
>I'm fine with either of these. 

Alright. Then 2 would be straightforward if the problem does not require 3 (see below).

>> 3. 7298bis does destination address protection too for all packets (7298 
>> did only source, as 6126 is multicast-only). 
> 
>Please clarify. 6126 already allows unicast operation, except for Hello 
>TLVs (Section 3.1 of RFC 6126). 

I am sorry, a more correct wording would be: the destination address was not meaningful in 6126 (I remember discussing this with you at some point). Do the new unicast provisions in 6126bis make the destination address meaningful? I.e. can a man in the middle change it and cause any damage beyond ignored Babel packets?

The destination address can be covered by the integrity check too with no additional expense of bytes in the protocol encoding.

>> I am still considering those options, feedback is welcome. One thing 
>> I wanted to confirm is whether point-to-point links in Babel are always 
>> meant to have addresses or they can be address-less. 
> 
>You need an adress to put in the source field of the IP packet. For IPv6, 
>this SHOULD be a link-local address. For IPv4, this could be an address 
>assigned to a different interface of the same node, but carrying Babel 
>over IPv4 is NOT RECOMMENDED. 

"Unnumbered interface" is the correct term from OSPF. It is out of scope in Babel, right?

-- 

    Denis Ovsienko