IETF Logo Mail Archive

Re: [Lsr] Flooding Path Direction

Peter Psenak <ppsenak@cisco.com> Thu, 04 April 2019 07:27 UTC

Return-Path: <ppsenak@cisco.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 70906120456 for <lsr@ietfa.amsl.com>; Thu, 4 Apr 2019 00:27:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 vlMTgHUipMSE for <lsr@ietfa.amsl.com>; Thu, 4 Apr 2019 00:27:49 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB2B0120448 for <lsr@ietf.org>; Thu, 4 Apr 2019 00:27:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1071; q=dns/txt; s=iport; t=1554362869; x=1555572469; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=ukERzKFhiESfAAQv7dMDwqnbUPMT8sVB4NwZRLM5fA4=; b=XavldpRFh3rUAA9euG0CRA7aBEQANc1rnsQkEytrsUOxqc+wb+tCjK4d 7CsJPlxbH1A51NxxRlJpvbahR61LWY/aaYJRMZFnY7aMWj0GTedbFwtCC wyvYFdcLk+5+F0iMazqw8RZ/X10E/fW9i/ul+3Ln3ehNr0m4WQXVx7yTD I=;
X-IronPort-AV: E=Sophos;i="5.60,306,1549929600"; d="scan'208";a="11170700"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 04 Apr 2019 07:27:46 +0000
Received: from [10.60.140.53] (ams-ppsenak-nitro4.cisco.com [10.60.140.53]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTP id x347Rk7L030880; Thu, 4 Apr 2019 07:27:46 GMT
To: "Jakob Heitz (jheitz)" <jheitz@cisco.com>, "tony.li@tony.li" <tony.li@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>
Cc: "lsr@ietf.org" <lsr@ietf.org>
From: Peter Psenak <ppsenak@cisco.com>
Message-ID: <0c505c69-955f-4eb5-c0b0-820ec8e0019f@cisco.com>
Date: Thu, 04 Apr 2019 09:27:46 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <BYAPR11MB3751127FEA49D06038EBE623C0500@BYAPR11MB3751.namprd11.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Outbound-SMTP-Client: 10.60.140.53, ams-ppsenak-nitro4.cisco.com
X-Outbound-Node: aer-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/JjgpveGngGwJSmwSPHK4YRMK3W8>
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 07:27:51 -0000

Jakob,

given that there is a single flooding topology calculated for an area, I 
don't see how this can be unidirectional, considering that flooding 
topology is used to flood in any direction.

thanks,
Peter


On 04/04/2019 08:26 , Jakob Heitz (jheitz) wrote:
> I mean flooding in one direction only, not unidirectional forwarding.
>
>
>
> Regards,
>
> Jakob.
>
>
>
> *From:* Tony Li <tony1athome@gmail.com> *On Behalf Of *tony.li@tony.li
> *Sent:* Wednesday, April 3, 2019 11:19 PM
> *To:* Jakob Heitz (jheitz) <jheitz@cisco.com>
> *Cc:* lsr@ietf.org
> *Subject:* Re: [Lsr] Flooding Path Direction
>
>
>
>
>
>     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
>
>
>
>
>
>
>
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
>

v2.23.0 | Report a Bug | By Email