IETF Logo Mail Archive

Re: [Lsr] LSR Flooding Reduction Drafts - Moving Forward

Peter Psenak <ppsenak@cisco.com> Thu, 23 August 2018 09:05 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 DB9E9130E48 for <lsr@ietfa.amsl.com>; Thu, 23 Aug 2018 02:05:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, 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 2tuXI7NG222e for <lsr@ietfa.amsl.com>; Thu, 23 Aug 2018 02:05:36 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20904127148 for <lsr@ietf.org>; Thu, 23 Aug 2018 02:05:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2334; q=dns/txt; s=iport; t=1535015136; x=1536224736; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=SifLZHg0m22GLx/QsupZsJ8qxllk/rbT1x5XnxCmRrw=; b=jkbJruoFkkvY7u9IwmWIKPx2gKTpO7non8IUutfya+XVLe1p78CUwvva Cd6L+zrNXCl9JhzC7lnabc7mWyfkAdEDvENy/iGk+zPZgsvqnq2GkpJFg C9NjUcbZl58bzLReNKKTEaojRyT9PLYFFqeUMmg6+gRhvI/szhDDPFvR9 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DsAQDod35b/xbLJq1bGgEBAQEBAgEBAQEIAQEBAYMggRR/KIxbjVSIU41igWYLGAuESQKDLTgUAQIBAQIBAQJtHAyFOAEBAQMBATABBTYLEAsYCR4HDwIQBh8RBgEMAQUCAQEXgwiBaQMVD6N5hGmCOQ2DLAWJNoFBP4ESgmQuglZFAQGBLgESAYV3AppxKwmMXYMQF4hChX6LeIdHgVghYXEzGggbFTuCaYIlF4hZhUA9MIwfgjsBAQ
X-IronPort-AV: E=Sophos;i="5.53,277,1531785600"; d="scan'208";a="5989185"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Aug 2018 09:05:33 +0000
Received: from [10.147.24.21] ([10.147.24.21]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTP id w7N95XKE032648; Thu, 23 Aug 2018 09:05:33 GMT
Message-ID: <5B7E78DD.90302@cisco.com>
Date: Thu, 23 Aug 2018 11:05:33 +0200
From: Peter Psenak <ppsenak@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Jeff Tantsura <jefftant.ietf@gmail.com>, Tony Li <tony1athome@gmail.com>
CC: "lsr@ietf.org" <lsr@ietf.org>, "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>
References: <8F5D2891-2DD1-4E51-9617-C30FF716E9FB@cisco.com> <C64E476F-1C00-435E-9C74-BEC3053377E8@gmail.com> <2F5FDB3F-ADCA-4DB4-83DA-D2BC3129D2F2@gmail.com>
In-Reply-To: <2F5FDB3F-ADCA-4DB4-83DA-D2BC3129D2F2@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Outbound-SMTP-Client: 10.147.24.21, [10.147.24.21]
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/GMm51APk3SwThB_mdiXZXkWEzIk>
Subject: Re: [Lsr] LSR Flooding Reduction Drafts - Moving Forward
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.27
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, 23 Aug 2018 09:05:39 -0000

Jeff, All,

we have added many extensions to IGP protocols over the years. Many 
times multiple solutions were proposed for the same or similar problem 
and WG picked from the set, many times multiple solutions were merged or 
combined together. We never asked for a requirement document. Even for 
more significant changes then we are talking about here.

I understand that the area of DC routing using IGPs is a broader area, 
but it does not fundamentally change IGPs to warrant the need for 
requirement document as a prerequisite to move forward with any work 
that is related to any optimization that may be applicable to DC 
environment.

So while I'm not against the existence of the document that would cover 
the requirements for IGPs in DC environments , I don't believe we should 
gate all proposed work in this space by such a document. And to be 
completely honest, the requirements are pretty straightforward for 
anyone that is familiar with the protocols' operation.

my 2c,
Peter

On 22/08/18 18:42 , Jeff Tantsura wrote:
> +1 Tony
>
> We could start with a document, similar to dc-routing requirements one
> we did in RTGWG before chartering RIFT and LSVR.
> Would help to disambiguate requirements from claims and have apple to
> apple comparison.
> Doing it on github was a good experience.
>
>
> Regards,
> Jeff
>
> On Aug 22, 2018, at 09:27, Tony Li <tony1athome@gmail.com
> <mailto:tony1athome@gmail.com>> wrote:
>
>>
>>
>>> At IETF 102, there was no dearth of flooding reduction proposals.  In
>>> fact, we have so many proposals that there wasn’t agree as how to
>>> move forward and we agreed to discuss on the list. This Email is to
>>> initiate that discussion (which I intend to participate in but as a
>>> WG member).
>>
>>
>> Hi Acee,
>>
>> Perhaps a useful starting point of the discussion is to talk about
>> requirements.  There seem to many different perceptions.
>>
>> Regards,
>> Tony
>>
>>
>> _______________________________________________
>> Lsr mailing list
>> Lsr@ietf.org <mailto:Lsr@ietf.org>
>> https://www..ietf.org/mailman/listinfo/lsr
>> <https://www.ietf.org/mailman/listinfo/lsr>
>
>
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
>

v2.23.0 | Report a Bug | By Email