IETF Logo Mail Archive

Re: [Lsr] Flooding Path Direction

tony.li@tony.li Thu, 04 April 2019 17:04 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 436C5120104 for <lsr@ietfa.amsl.com>; Thu, 4 Apr 2019 10:04:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 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, 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 ZKNQmmXlUJyv for <lsr@ietfa.amsl.com>; Thu, 4 Apr 2019 10:04:30 -0700 (PDT)
Received: from mail-pg1-x542.google.com (mail-pg1-x542.google.com [IPv6:2607:f8b0:4864:20::542]) (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 360E01200C7 for <lsr@ietf.org>; Thu, 4 Apr 2019 10:04:30 -0700 (PDT)
Received: by mail-pg1-x542.google.com with SMTP id y3so1520903pgk.12 for <lsr@ietf.org>; Thu, 04 Apr 2019 10:04:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ZuaODUBGhNG1uX8bpPZ+IOdsKHuC0WBBqoRlJHfA3nc=; b=ItVKMogH3TFatrfhl1agrsW4/qra98gnQLDZ+rYROAQON2wbik4a5baUSj8QFVqtr9 fLKli2cTTPOH2YdUinX62cSJI9l5OO4os+dkp+J/tfD9jaSbXKuTJtd2VEzyk8HEMsgU UbdjkbBXtNu5dwHQgXhTTpvao1/gdkR/LuOPo4uDNxMb8YwtsF95rDHAQ+iKImPlM7Po Yp10+KQZHgzvjPIcf32d3un+HQDDVsSIgY9DRJ3ZOiX2eNGTwX+MbvkE/bW4bhth5HYV RpdqM/ROL1UVidVU8d0GjPNGhhEDDysd4o16SaoRMYnKWsoB/lu59sLd8E6Ngr9GI5rq s95A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:mime-version:subject:from:in-reply-to :date:cc:content-transfer-encoding:message-id:references:to; bh=ZuaODUBGhNG1uX8bpPZ+IOdsKHuC0WBBqoRlJHfA3nc=; b=FLrApHJjliggrYQ348vzOB1JGKg/iqmGTwDbDLlfTW1l8/1Zxy7hGD47iRrzsplbnM 2wvHrgmx6DtElxhl4Il1gooE5+4HxBh7V53I3hKP2Iv8K5DedetJF8d3D3KjucnnmswK I2TWBWjOmIdeWNM0ToDZ5XGKwSin5ljaExUWvcCcGgQPhT6n8ByAYhRENxzVZUmDspLc VQnchxsBOza7etjm1wthLyERV7RSwO9kI0fvWHw3IfKNQOBhg+xa2ZpNF/qYKltkw060 4JthlA/g07kKvjuCHRUK++0HaAnIeJzmf/+iRNqgFGiJ41pm7mF98QCFCUkmubFJMudF TLiw==
X-Gm-Message-State: APjAAAXxlFB9JHQSiSE2Hs2fRYSZrsntpxWD09M2EjiWR1X3RC+jrIwr 1CXwKcIrhziypB0dco2sPNI=
X-Google-Smtp-Source: APXvYqzLcerfioeP4LpXw0WeFx4aEFHxDFxCISmvdT9uP46P44eA7isjdwrTaCaJfFjjvR4hEgfQww==
X-Received: by 2002:a62:b418:: with SMTP id h24mr7003211pfn.145.1554397469500; Thu, 04 Apr 2019 10:04:29 -0700 (PDT)
Received: from ?IPv6:2601:640:108:d578:7970:add0:a124:3d5? ([2601:640:108:d578:7970:add0:a124:3d5]) by smtp.gmail.com with ESMTPSA id t5sm958947pfl.106.2019.04.04.10.04.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Apr 2019 10:04:27 -0700 (PDT)
Sender: Tony Li <tony1athome@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: tony.li@tony.li
In-Reply-To: <BYAPR15MB3078AEBB55A61477277BA1AED0500@BYAPR15MB3078.namprd15.prod.outlook.com>
Date: Thu, 04 Apr 2019 10:04:26 -0700
Cc: Peter Psenak <ppsenak@cisco.com>, "Jakob Heitz (jheitz)" <jheitz@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <76B663DD-B500-477B-9957-F38A5F8D7B7E@tony.li>
References: <BYAPR11MB375152970011BD7563A8E271C0500@BYAPR11MB3751.namprd11.prod.outlook.com> <DE048608-1403-431D-BD88-27D95E49E089@tony.li> <BYAPR11MB375129E24A8D1C0BB5E4D598C0500@BYAPR11MB3751.namprd11.prod.outlook.com> <89E37338-8E33-43F9-B8AB-76DD1884914C@tony.li> <BYAPR11MB3751127FEA49D06038EBE623C0500@BYAPR11MB3751.namprd11.prod.outlook.com> <0c505c69-955f-4eb5-c0b0-820ec8e0019f@cisco.com> <BYAPR11MB3751BE6C14F9879D482EF377C0500@BYAPR11MB3751.namprd11.prod.outlook.com> <7cc74779-8825-dfc5-b87e-b9f494133add@cisco.com> <BYAPR15MB3078AEBB55A61477277BA1AED0500@BYAPR15MB3078.namprd15.prod.outlook.com>
To: David Allan I <david.i.allan@ericsson.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/HMhkSUsQnUHLkDag_Ui9cq8XWoI>
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 17:04:31 -0000

Hi Dave,

> The algorithm in draft-allan actually has the notion of upstream, downstream
> and both upstream and downstream FT adjacencies. However as a generalized
> form is still a WIP and has yet to demonstrate merit against any of the
> other approaches on the table, I'd not be looking to suggest a specific
> encoding. 


Thanks.


> If at some point it is decided that different classes of FT adjacency are
> required, simply using additional types that share the format of the
> flooding path TLV would appear to be sufficient....(?)

Or perhaps having a separate TLV for a unidirectional path would suffice.

That would allow both paths to be encoded most optimally.

Tony

v2.23.0 | Report a Bug | By Email