Re: [Lsr] Flooding Path Direction

tony.li@tony.li Thu, 04 April 2019 05:10 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 950DA120442 for <lsr@ietfa.amsl.com>; Wed, 3 Apr 2019 22:10:07 -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 CzBtGFYt6dw6 for <lsr@ietfa.amsl.com>; Wed, 3 Apr 2019 22:10:06 -0700 (PDT)
Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (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 2EA5D120437 for <lsr@ietf.org>; Wed, 3 Apr 2019 22:10:06 -0700 (PDT)
Received: by mail-pg1-x52e.google.com with SMTP id k19so628326pgh.0 for <lsr@ietf.org>; Wed, 03 Apr 2019 22:10:06 -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=ZhcvrAtKo4zBD2n2MKPHMXdm8GgYV5gvLsHuIwxdN38=; b=Cm9wGcRuHKowRKgD9+XkpeKpiUvlofsgkYaFeiboDstqounGLf7oLSi/tlYXP3ebza +yFi3G9WncbCbuh+5y8qFmFOxpSz7MSQxIh3cwwQfhf8rn35UuOf86x28asDqK/sgfi5 1Hv1pVqREyF2CPAilzmzqR6ZwjYHhyjpTUOd+EPL1F39T1M/CljVpDNVleF++0bEKEe+ tdWYrKcOH0gWlt3VYVMVhu9DPdW9DecF8FZzID8Ww3xeKK1c/DwWzVqLD+VlxPjem+yn Est+5k0IX559X12/dchzKPv+NjkYF7lZD3S+GbBZCvArMMZHjHr4+CSCpsyTKLmbUK9F +kYg==
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=ZhcvrAtKo4zBD2n2MKPHMXdm8GgYV5gvLsHuIwxdN38=; b=VR3GWS9h2ashRDZb9SrxKcDhxyXHjvBr1OYj03SFOaT4aODCfdWVGn4zyKmo7HlXyp ze3pzP4PYneMpKNSIEM/AQ84uvrBwYEo9MO9g/IJwBg6cVV18sOPUywdUcK4KS6qRpiS Y7tlNbIo5jFuLfsg38FgVtFeiSdMzYqI+9cIO3ZU5dPWCzriBD5K+PitbixLVVowcvi7 K8tA2bpuUl/ZJdkYRp2fd8d7E1pRNMEmcLvDo43c+z9m4Cb7+ZW+OR0IZXMNmgF85ucG mFSOXzVYWbbwbAakSQhkWGq5QC+16vTW5Bu0O0Q4dN6zo+1YhOrciMPsvJd1+2ETXuoV FNEA==
X-Gm-Message-State: APjAAAXxacuOIWIbdXHB/ej78lFjQ9XzI+glIb2T811Y3K0Idvf+zBfX 2aFf3daHN5x3KVkPh9OdKoA=
X-Google-Smtp-Source: APXvYqwzRmOkikXTDxrOOY77Gu+tLr9CP7ETVvY7totKomHyA3McRlpGjh7UxgsTbzBX/218g5ixhw==
X-Received: by 2002:a63:bd42:: with SMTP id d2mr3764393pgp.319.1554354605702; Wed, 03 Apr 2019 22:10:05 -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 l74sm27508323pfi.174.2019.04.03.22.10.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Apr 2019 22:10:05 -0700 (PDT)
Sender: Tony Li <tony1athome@gmail.com>
From: tony.li@tony.li
Message-Id: <DE048608-1403-431D-BD88-27D95E49E089@tony.li>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D486524B-118B-4207-B26C-7BD7F676E719"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Wed, 03 Apr 2019 22:10:04 -0700
In-Reply-To: <BYAPR11MB375152970011BD7563A8E271C0500@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>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/DLfL0XYcVogASzyn3ZXMne1gcsA>
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 05:10:08 -0000

> The direction of the Flooding Path in draft-ietf-lsr-dynamic-flooding-00
> is not clear.
>  
> I think it should be uni-directional, such that path (1,2) is different to
> path (2,1). If the path (1,2) should be bi-directional, then it can be encoded
> as (1,2,1).


Hi Jakob,

The intent was that flooding be bi-directional on all links and thus (1,2) is sufficient to describe that link.

The reason for encoding things as paths is for the encoding efficiency.  (1,2,3) is more efficient than (1,2) and (2,3).

Regards,
Tony