Re: [babel] What's up with AE 0?

David Schinazi <dschinazi@apple.com> Wed, 19 July 2017 16:27 UTC

Return-Path: <dschinazi@apple.com>
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 BA13D12F3CB for <babel@ietfa.amsl.com>; Wed, 19 Jul 2017 09:27:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.321
X-Spam-Level:
X-Spam-Status: No, score=-4.321 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_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 sfDont5s-QNj for <babel@ietfa.amsl.com>; Wed, 19 Jul 2017 09:27:44 -0700 (PDT)
Received: from mail-in2.euro.apple.com (mail-in2.euro.apple.com [17.72.148.12]) (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 06AD3129482 for <babel@ietf.org>; Wed, 19 Jul 2017 09:27:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1500481662; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-transfer-encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=FZDcvwjvWsBVH8Odz886V37vcovuOm227xKEB+mtofY=; b=iExaVJ3xHE5ICGWONohAxxOappRn/RlN0vtej5sOcn1nyM24gyMaAzPvsPjI+GjF hI1opft3IGMCNWeRK8CmtG0DSpG6pA5DHppkTInzj2YcX2CgeOU1LwoxC5BosqjK hfdiqxcjymE24aAfWvI9fWH2ZbAYBrhmTr6KL1vcHpd0b7ZiOU8fqRPWIiUMZcYh iisc+TPzsev4079Ja1uKlvZuRP0tG1tnku2Gt3o4dgLYj3xbY8vDqf17ChisL+Xy PLmtobcuHZrzAcZsqb9AqfT6CKQtXJe8llKt/XWruSYLI/Z8vC+qPmQen9yWYMxH T+WhIzBQ10pGqQ+boPE6UA==;
Received: from relay2.euro.apple.com (relay2.euro.apple.com [17.66.55.12]) (using TLS with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail-in2.euro.apple.com (Symantec Mail Security) with SMTP id BB.B3.06273.D788F695; Wed, 19 Jul 2017 17:27:41 +0100 (BST)
X-AuditID: 1148940c-1926f9c000001881-06-596f887d0c18
Received: from crk-phonehomebzp-sz03.euro.apple.com ( [17.72.133.83]) by relay2.euro.apple.com (Symantec Mail Security) with SMTP id 9F.05.07255.D788F695; Wed, 19 Jul 2017 17:27:41 +0100 (BST)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: text/plain; CHARSET="US-ASCII"
Received: from [17.235.208.162] (unknown [17.235.208.162]) by phonehome3.euro.apple.com (Oracle Communications Messaging Server 8.0.1.2.20170222 64bit (built Feb 22 2017)) with ESMTPSA id <0OTC006MCJ22XI90@phonehome3.euro.apple.com>; Wed, 19 Jul 2017 17:27:41 +0100 (IST)
Sender: dschinazi@apple.com
From: David Schinazi <dschinazi@apple.com>
In-reply-to: <87k234xuo3.wl-jch@irif.fr>
Date: Wed, 19 Jul 2017 18:27:34 +0200
Cc: babel@ietf.org
Message-id: <98717A22-9C7C-42C3-AE8A-97A5DFA44427@apple.com>
References: <87k234xuo3.wl-jch@irif.fr>
To: Juliusz Chroboczek <jch@irif.fr>
X-Mailer: Apple Mail (2.3273)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOLMWRmVeSWpSXmKPExsUi6GTOo1vbkR9pcOOStcWWRd0sFvNbl7E5 MHksWfKTyWPxlreMAUxRXDYpqTmZZalF+nYJXBlLth9iKpgsWHH20XvWBsb7vF2MnBwSAiYS LXdes3YxcnEICWxnkjhyahErTKLn1zYWiMQhRokvRzazgyR4BQQlfky+B5Tg4GAWkJc4eF4W JMwsoCXx/VErVP10JokNjS+ZQBLCAtISXRfuskLYmhIHju9kB+llA2o4sMYIJMwpoCFx78ID sJEsAqoSr/qqIEYKSZy5NgMszCtgIzH9QABIWEhAXWLl9Edgw0UEVCSWT3vGDnGxrMSt2ZeY IexGNomdP+QmMArPQnLzLISbZyG5eQEj8ypG8dzEzBzdzDwjvdTSony9xIKCnFS95PzcTYyg 4PaYwrOD8eJBw0OMAhyMSjy8sXG+kUKsiWXFlbnAsOFgVhLhXd2WHynEm5JYWZValB9fVJqT WnyIUZqDRUmc16RUPlJIID2xJDU7NbUgtQgmy8TBKdXAmCh3slpQPeNMWUDHJr33xSlXvMxF FD4KWpwx6mFlrVW6/yuUzfbzPb+GE99izlW0eTS4ygbbHFN8amUvFNwzLW/C9Ou3TjMLXnbb adyrtVDk1vRG0Yk7Gaq3zr239vTyBzy8PwXmhU0uN3tRKrPjvaJhw5tZLT4Ptqpt2/jqwgeJ ju9fF+5ZpsRSnJFoqMVcVJwIAK5TQvBqAgAA
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrALMWRmVeSWpSXmKPExsUi6NEarFvbkR9pcHW6pcWWRd0sFvNbl7E5 MHksWfKTyWPxlreMAUxRXDYpqTmZZalF+nYJXBlLth9iKpgsWHH20XvWBsb7vF2MnBwSAiYS Pb+2sXQxcnEICRxilPhyZDM7SIJXQFDix+R7QAkODmYBeYmD52VBwswCWhLfH7VC1U9nktjQ +JIJJCEsIC3RdeEuK4StKXHg+E52kF42oIYDa4xAwpwCGhL3LjwAG8kioCrxqq8KYqSQxJlr M8DCvAI2EtMPBICEhQTUJVZOfwQ2XERARWL5tGfsEBfLStyafYl5AqPALCR3zkK4cxaSOxcw Mq9iFC1KzUmsNNJLLS3K10ssKMhJ1UvOz93ECApHJ3OeHYyvDhoeYhTgYFTi4f3Zlh8pxJpY VlyZCwwNDmYlEd577UAh3pTEyqrUovz4otKc1OJDjNIcLErivAUPIyKFBNITS1KzU1MLUotg skwcnFINjHttT3ztC3DfWcwk71x2R9ZNPGfa+qWT/ffMUdTy6hKLrb59I+3FnfI5i793dsy8 2NF4ZKua8aGalPISzt0Tz7940q19o0LKd8cdqxqhGw1s19f6rEn/wLtvulS2nd9vNW6X10wa x6QiVkzZmRn+yL1M0GXn8TnezUv3Ll+019l3DV8ZP2+5ixJLcUaioRZzUXEiALTi9LVDAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/Y3R6WY687fjcZH0kUWm8jMBKprQ>
Subject: Re: [babel] What's up with 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: Wed, 19 Jul 2017 16:27:46 -0000

My initial preference was to forbid (MUST NOT) IHU_AE=0 over multicast.
Now I understand that it can be used by implementations that do not
want bidirectional detection. I'm fine with making this a SHOULD NOT
as long as we add text in the same paragraph (or close by) that explains
that using IHU_AE=0 over multicast will disable bidirectional detection.

David Schinazi


> On Jul 19, 2017, at 18:23, Juliusz Chroboczek <jch@irif.fr> wrote:
> 
> Executive summary: rfc6126bis leaves the wildcard AE mostly unchanged.
> 
> AE 0 specifies a wildcard: the only element of the AE is the 0-length byte
> sequence, and represents "all the things you have".  AE 0 is allowed in
> three places:
> 
>  1. in a route request, it requests a full route dump;
>  2. in an Update with Metric=infinity, it retracts all the routes
>     announced by the sender;
>  3. in an IHU, it says "I Heard You" to anyone who receives this update.
> 
> All three applications of AE 0 remain in rfc6126bis.  We've clarified that
> for implementations with extensions, (1) and (2) apply to all routes --
> a wildcard request requests all routes, even the ones that require an
> extension, and a wildcard retraction retracts all routes.  This needs
> adding to Appendix C.
> 
> IHU(AE=0) were originally intended for implementations that are not
> interested in bidirectional detection, and perform simple inverse
> detection, RIP style; such implementation can just send IHU(AE=0), "I hear
> everyone!".  However, no implementation ever did that -- even sbabeld
> produces proper per-neighbour IHUs.
> 
> David uses IHU(AE=0) for a different purpose: he sends IHUs over unicast,
> and hence doesn't need to use the Address field to constrain the receiver.
> This was not intended, but looks to me like a perfectly valid
> implementation.
> 
> I will edit the document to say that IHU(AE=0) SHOULD NOT be used for
> multicast IHUs, and MAY be used over unicast.  (David suggests MUST NOT,
> but I feel it's too strong.)
> 
> -- Juliusz
> 
> _______________________________________________
> babel mailing list
> babel@ietf.org
> https://www.ietf.org/mailman/listinfo/babel