Re: [babel] Unicast Hellos -- conclusions so far

Juliusz Chroboczek <jch@irif.fr> Sat, 08 April 2017 14:14 UTC

Return-Path: <jch@irif.fr>
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 7526C127010 for <babel@ietfa.amsl.com>; Sat, 8 Apr 2017 07:14:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham 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 bE5EjNiiiZkG for <babel@ietfa.amsl.com>; Sat, 8 Apr 2017 07:14:08 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D7EE1200F1 for <babel@ietf.org>; Sat, 8 Apr 2017 07:14:08 -0700 (PDT)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56228) with ESMTP id v38EE5v8007178; Sat, 8 Apr 2017 16:14:06 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id E2FDBD79D5; Sat, 8 Apr 2017 16:14:05 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id b-cyUzkcrDrE; Sat, 8 Apr 2017 16:14:04 +0200 (CEST)
Received: from trurl.irif.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 0C3CDD79B8; Sat, 8 Apr 2017 16:14:03 +0200 (CEST)
Date: Sat, 08 Apr 2017 16:14:05 +0200
Message-ID: <87lgrb0yxe.wl-jch@irif.fr>
From: Juliusz Chroboczek <jch@irif.fr>
To: Teco Boot <teco@inf-net.nl>
Cc: babel@ietf.org
In-Reply-To: <1344FE29-570C-4ECA-83C4-8AC400A347D6@inf-net.nl>
References: <87y3vcuuv8.wl-jch@irif.fr> <1344FE29-570C-4ECA-83C4-8AC400A347D6@inf-net.nl>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Sat, 08 Apr 2017 16:14:06 +0200 (CEST)
X-Miltered: at korolev with ID 58E8F02D.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 58E8F02D.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@irif.fr>
X-j-chkmail-Score: MSGID : 58E8F02D.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/uV_3oylAQBJ5P4rvXkmvvvwpHC4>
Subject: Re: [babel] Unicast Hellos -- conclusions so far
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: Sat, 08 Apr 2017 14:14:10 -0000

>> - perform 2/3 for multicast hellos;
>> - perform 2/3 for unicast hellos;
>> - assume link is up if either instance of 2/3 says it's up.

> Appendix A2 is for Cost Computation, right? 
> Link Up depends on IHU.
> OK, link from Hello sender to Hello receiver is assumed up.

> Or is this "Link Up" equivalent to "it has recently heard a Hello" 
> in rfc6126bis section-2.1? I couldn't find a precise definition 
> that quickly.

Yes, that's what I meant.

> What means recently?

In the reference implementation -- within three times the interval
advertised by the most recent Hello.

-- Juliusz