IETF Logo Mail Archive

Re: [Lsr] Open issues with Dynamic Flooding

Peter Psenak <ppsenak@cisco.com> Thu, 07 March 2019 19:20 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 E1786128678 for <lsr@ietfa.amsl.com>; Thu, 7 Mar 2019 11:20:45 -0800 (PST)
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 WClgD0eo51lD for <lsr@ietfa.amsl.com>; Thu, 7 Mar 2019 11:20:44 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 675F4130EDD for <lsr@ietf.org>; Thu, 7 Mar 2019 11:20:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=922; q=dns/txt; s=iport; t=1551986442; x=1553196042; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=AxuKBb9lhED/44CZDnkDjLCHwvziA7YEbrESUgrp55s=; b=SYDnK8pf+JzruTyTF+8EFmUYjxE7kHhU9ilxqmZ4CwfuJF6nMWwo6lBj XZvRZaVeAO0bRTrhFLbqHiCgvr5Bn3pViTuZNxEW7o67XOE8XMRKT68mH KWoCmyODFrUu2OH5s5HkELpzhm4e/jeqBDBjUSnao05UONcn1t5vfGRup 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AKAAC+boFc/xbLJq1kGgEBAQEBAgEBAQEHAgEBAQGBUwMBAQEBCwGDaBInhAmIeYwqLZgjgXsNhGwChFc2Bw0BAQMBAQcBAwJtHAyFSgEBAQMBIw8BBUEQCxgCAiMDAgJGERMGAgEBgx6BbgirXYEvhUSEYoELJAGLQoFAP4E4gj0uhFp0gj2CVwKkFQmSfwYZgXiFZoMiiDWdUIFODiOBVjMaCBsVgyeJPocOPgMwizMqgiMBAQ
X-IronPort-AV: E=Sophos;i="5.58,451,1544486400"; d="scan'208";a="10606141"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Mar 2019 19:20:28 +0000
Received: from [10.60.140.54] (ams-ppsenak-nitro5.cisco.com [10.60.140.54]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTP id x27JKReM005568; Thu, 7 Mar 2019 19:20:28 GMT
To: tony.li@tony.li
References: <AAD29CF0-F0CA-4C3C-B73A-78CD2573C446@tony.li> <c1adac3a-cd4b-130e-d225-a5f40bf0ef55@cisco.com> <F3C4B9B2-F101-4E28-8928-9208D5EBAF99@tony.li> <be28dbcf-8382-329a-229f-5b146538fabe@cisco.com> <966E5756-8CEF-47F4-8564-E23D38F0743E@tony.li> <c8f40acb-94fe-f42a-aa0a-3a42e0067be8@cisco.com> <7F522B6C-9D28-4533-8ABD-9F492D9AF26C@tony.li> <a33ff3ba-975b-2ef2-93e9-1bc9664fdd5a@cisco.com> <2932F33A-1F9E-4C20-A233-E569D8935AE4@tony.li> <C723C078-72FD-426C-99F2-F0A494E0E971@tony.li>
Cc: lsr@ietf.org
From: Peter Psenak <ppsenak@cisco.com>
Message-ID: <884f0f45-813f-93f0-a63e-f510e5f01ab1@cisco.com>
Date: Thu, 07 Mar 2019 20:20:27 +0100
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: <C723C078-72FD-426C-99F2-F0A494E0E971@tony.li>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Outbound-SMTP-Client: 10.60.140.54, ams-ppsenak-nitro5.cisco.com
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/d2sPOJaG0qsiQVu2-woK93JlyGI>
Subject: Re: [Lsr] Open issues with Dynamic Flooding
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, 07 Mar 2019 19:20:46 -0000

On 07/03/2019 18:16 , tony.li@tony.li wrote:
>
>
>> On Mar 5, 2019, at 1:31 PM, tony.li@tony.li <mailto:tony.li@tony.li>
>> wrote:
>>
>> Let me propose that we add something to sections 6.7.5, 6.7.9, and
>> 6.7.11 like:
>>
>> Addition of temporary flooding should be done with caution, as the
>> addition of excessive connectivity to the flooding topology may
>> trigger unwanted behavior. Routers SHOULD add temporary flooding in a
>> rate limited manner, if not configured otherwise.
>
>
> Hi,
>
> I haven’t heard any feedback on this.  Can we please adopt this?
>
> The draft cutoff is Monday, March 11.  Could we please incorporate this
> change and the addition of the pseudonode identifier by then?

I don't think there is an agreement on the LAN side.

Rate limiting we can add, but we can do that after March 11, I don't see 
a need to do it before.

thanks,
Peter


>
> Tony
>

v2.23.0 | Report a Bug | By Email