IETF Logo Mail Archive

Re: [Lsr] Flooding Path Direction

tony.li@tony.li Thu, 04 April 2019 06:19 UTC

Return-Path: <tony1athome@gmail.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0FDE1203A5 for <lsr@ietfa.amsl.com>; Wed, 3 Apr 2019 23:19:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.648
X-Spam-Level:
X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 fItBjqQh8ldo for <lsr@ietfa.amsl.com>; Wed, 3 Apr 2019 23:19:16 -0700 (PDT)
Received: from mail-pl1-x630.google.com (mail-pl1-x630.google.com [IPv6:2607:f8b0:4864:20::630]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30176120338 for <lsr@ietf.org>; Wed, 3 Apr 2019 23:19:16 -0700 (PDT)
Received: by mail-pl1-x630.google.com with SMTP id g37so630204plb.5 for <lsr@ietf.org>; Wed, 03 Apr 2019 23:19:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=eZqol2MAW4yRFAluQA0hV7fY5wTnniKYoYNQ+Bqz7S4=; b=LuxEKoFHzjrmagX9eeOVFCcPg1KeFKv6ytyG0gnSmZpNHwXtLNw+c1SewGHr+NLh1U gY3T26VnDa0fglEa3bofJzI9bQxs5ILlXiYjrl8x/p7bORA/RIbmunAI/smctZpY/nlc vP1+bsgbzPc8SVxKJ7UhhtmhQGD4kArb2kFM/rHlHQMFaenO2wPGehFX/nYRSlqp0iyy 1pweExW9kNONsCDZ8h/FMu9aVO3sDdIQBet66A2+ZzPjlA56R/aHMnu7v6JDrsLIc8QJ lKK1cRwbn8VVfh3qtmhSiaZKEUBOf5reBxbobjAKjqY+ixNl0+kijC+u1FycMsz/lXBm /sVg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=eZqol2MAW4yRFAluQA0hV7fY5wTnniKYoYNQ+Bqz7S4=; b=n+pWc6Fkm8J/rSWvu0NwxbT5xg8mwR57rLoKNq+xWM3inBXy3INB8S/isi5G0onxAg HLZhzPa9aGy+WPvuIMJUf0ZMJyDc1dKLLp8ZqHa28grp7+DrVv/TEXgf2vsvsqmabala SkL9MXJvODGhqeEHBWt6dKCJIjJSjY8EuWzR7PTTYFD4tl+s0pyQI08D+wGvXtCaFM9F D9z2P41+y7eBSEsuLhg4rpxW5ZYrl1BAJB05xLiddRq50mI0GCGqolmIShbVtMW0ZKpU sr+4uYR+0vlGYOSfmLzWQr07Y0K2omfhoGbK3FfmxYWBglRkziKwSJEDivRGRgF3Ucq1 KCpg==
X-Gm-Message-State: APjAAAUik2co0GGIdGDTuenIdkxZhDBJ2pWjq0Nu6BQ/oNnvbKrik4tT fNQUFTqVRKEqrZwQaRrLxyk=
X-Google-Smtp-Source: APXvYqybCK+FgYw95gsbKJUq7ZRPE3Ce4h/inmk69663WHZUBhv1gtRv5794Jg2d4Iw3fgQDFVa/SQ==
X-Received: by 2002:a17:902:526:: with SMTP id 35mr4496732plf.276.1554358755463; Wed, 03 Apr 2019 23:19:15 -0700 (PDT)
Received: from [192.168.1.5] (c-73-158-115-137.hsd1.ca.comcast.net. [73.158.115.137]) by smtp.gmail.com with ESMTPSA id d129sm25604964pfa.142.2019.04.03.23.19.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Apr 2019 23:19:14 -0700 (PDT)
Sender: Tony Li <tony1athome@gmail.com>
From: tony.li@tony.li
Message-Id: <89E37338-8E33-43F9-B8AB-76DD1884914C@tony.li>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E796F6B1-5B9B-4993-855D-270FE187D5CF"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Wed, 03 Apr 2019 23:19:13 -0700
In-Reply-To: <BYAPR11MB375129E24A8D1C0BB5E4D598C0500@BYAPR11MB3751.namprd11.prod.outlook.com>
Cc: "lsr@ietf.org" <lsr@ietf.org>
To: "Jakob Heitz (jheitz)" <jheitz@cisco.com>
References: <BYAPR11MB375152970011BD7563A8E271C0500@BYAPR11MB3751.namprd11.prod.outlook.com> <DE048608-1403-431D-BD88-27D95E49E089@tony.li> <BYAPR11MB375129E24A8D1C0BB5E4D598C0500@BYAPR11MB3751.namprd11.prod.outlook.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/4DiiSIkQo_xVlHWNDiPFpUwH520>
Subject: Re: [Lsr] Flooding Path Direction
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Apr 2019 06:19:18 -0000

> I think this is too restrictive.
> We should not exclude algorithms that can build a flooding topology with unidirectional links.


Well, right now, the protocol doesn’t really support unidirectional links. At all.

Tony

v2.23.0 | Report a Bug | By Email