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

Jeff Tantsura <jefftant.ietf@gmail.com> Thu, 23 August 2018 23:00 UTC

Return-Path: <jefftant.ietf@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 4F384130DDB for <lsr@ietfa.amsl.com>; Thu, 23 Aug 2018 16:00:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level:
X-Spam-Status: No, score=-0.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 HD3CQcDUlW0y for <lsr@ietfa.amsl.com>; Thu, 23 Aug 2018 16:00:03 -0700 (PDT)
Received: from mail-yb0-x22c.google.com (mail-yb0-x22c.google.com [IPv6:2607:f8b0:4002:c09::22c]) (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 EB63B12D949 for <lsr@ietf.org>; Thu, 23 Aug 2018 16:00:01 -0700 (PDT)
Received: by mail-yb0-x22c.google.com with SMTP id c1-v6so2824758ybq.5 for <lsr@ietf.org>; Thu, 23 Aug 2018 16:00:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version:content-transfer-encoding; bh=Hj0bOCo1+d4/8cnXGVq198WkCKXeNn4g2n82Ovp7mTw=; b=JzvzaLKHN1l65UfOEch4J71mnRhtB/AxvN++bTasEJM8UrBfWaK5M9/dRILQ3lc5Dz LSypAJJqR1gZKlxZwPlITq/eZp8BJfJPYaxUk7Rl0L7V3Iq7omdMAmdglGHynqSuSWLa K9Ui2UZ8CVe45i/fKNzrbiFYqmgDT7aSjx0Ex8QS5NsoI4L3fbQPnC+1FgmyFcwZTJB+ LCUWmNWE9bFLuimMefSCYfVTeG11TQo6uqM5zLm4fSHrK43nI9CzvAMm1GefCoqonVB+ 6iOTal4zXib+f9TzDHHOBdTOdUF6NbetdkYycPCxsWwJ+uYEyYLS2ETq0y9/jJolfKcK dECA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version :content-transfer-encoding; bh=Hj0bOCo1+d4/8cnXGVq198WkCKXeNn4g2n82Ovp7mTw=; b=HSY29f8HU3ZEZtgJqrEG9sUTEG7q8KzGokgK8D6sjvSOB+9vTTTva8+Rq5B/wc0Td0 tbzH51lf2JrmjMkxvi7JJdaGkcf53U15W7ctHktSPsY0T7VYILVw/gkk9/m4ekLmZjWq +apq/JV3UT+kpq/SuSxj24VyEWtTABdwBNdcFPCppv8Drf4ksi+6tA541ouTWdg5T1if hMGX/vVevNozizYFgGtJIBW3X7BKKQuFsw29EoDxnFilajYDdsf0dWsF/25uVtJFBSBW fuIAgdXt7+o4fRkGQNXE7H3oWjQOJb7ZGF++UGyUJbuZPxr0EeFmORAcFSu4/0XEB2tm /OlA==
X-Gm-Message-State: AOUpUlHTvYmQjTcmmvYNkXNDp/g/DHqeg5Mvfm3mmUUKOeqaR0ySUUtO r7I5Y/1crg8MD8DVIYNzMh4=
X-Google-Smtp-Source: AA+uWPwk/q6fzhG7hn0+wrBwpw//Bj94Gjhmb55TbKnM4r74yGt41hyurRXuW15m4WAq/oJc5rov/A==
X-Received: by 2002:a25:5ed4:: with SMTP id s203-v6mr26300965ybb.488.1535065200986; Thu, 23 Aug 2018 16:00:00 -0700 (PDT)
Received: from [135.227.239.108] ([66.201.62.254]) by smtp.gmail.com with ESMTPSA id 63-v6sm2239127ywd.8.2018.08.23.15.59.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Aug 2018 16:00:00 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/10.10.0.180812
Date: Thu, 23 Aug 2018 15:59:58 -0700
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: Peter Psenak <ppsenak@cisco.com>, Tony Li <tony1athome@gmail.com>
CC: "lsr@ietf.org" <lsr@ietf.org>, "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>
Message-ID: <172728E8-49E6-4F43-9356-815E1F4C22E7@gmail.com>
Thread-Topic: [Lsr] LSR Flooding Reduction Drafts - Moving Forward
References: <8F5D2891-2DD1-4E51-9617-C30FF716E9FB@cisco.com> <C64E476F-1C00-435E-9C74-BEC3053377E8@gmail.com> <2F5FDB3F-ADCA-4DB4-83DA-D2BC3129D2F2@gmail.com> <5B7E78DD.90302@cisco.com>
In-Reply-To: <5B7E78DD.90302@cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/wKJQl2EMKLLGGaoXJ9RxAub975w>
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 23:00:06 -0000

Peter,

As previously stated - I'm against gating, it should be developed in parallel and with cooperation with the ongoing/existing work.
Note - there's a document (albeit expired, it played its role) that talks about generic DC Routing requirements, work in LSR would be scooped to LSR only.
So no going into religious discussions - new vs old/ls vs pv, etc, but focusing on ospf/isis and what is needed for DC specifically.
I think it would be good to do some gain/complexity mental exercise...  

Cheers,
Jeff

On 8/23/18, 02:05, "Peter Psenak" <ppsenak@cisco.com> wrote:

    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
    >