Re: [Lsr] I-D Action: draft-ietf-lsr-isis-area-proxy-03.txt

tony.li@tony.li Mon, 07 September 2020 14:27 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 6A2143A0E4A for <lsr@ietfa.amsl.com>; Mon, 7 Sep 2020 07:27:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.5
X-Spam-Level:
X-Spam-Status: No, score=-1.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 HX_SSuNT5bBl for <lsr@ietfa.amsl.com>; Mon, 7 Sep 2020 07:27:49 -0700 (PDT)
Received: from mail-pf1-x441.google.com (mail-pf1-x441.google.com [IPv6:2607:f8b0:4864:20::441]) (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 EA2FA3A0E47 for <lsr@ietf.org>; Mon, 7 Sep 2020 07:27:48 -0700 (PDT)
Received: by mail-pf1-x441.google.com with SMTP id z19so6553639pfn.8 for <lsr@ietf.org>; Mon, 07 Sep 2020 07:27:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=az9FdeZeBsTa5XfzEg2V2iTcb39ihdHdpTTBISvSsqQ=; b=gTHrbRwOHqWJfXbANfuhc5faQVi4E2UZ6oSvDUFvQkp/y8/KcCJCDk7EGvjZsimU5G I4iPJV/Gl3c1MsK2mJNz5Zu84+8O3nY54LBhvPTIVrElHRk0ANUEGeWFTbXZAnsxTYcb rHXFtcwBDVPzzU+nYxmZULXZRVYsPfgEc322NsYU03M5WMjKqvbdg6xMAOWR+w6+8MFT SwUSqFt31pOfIvS6B0m0HJA9WvJN1GS0x3RjOhW6itPMRpF+Pw6+F2DjgjzQusIyPKr9 l2m3VfRpzcS+QPMg2FVV2i9+Shy6kdKfb2gID90PeaewS4XFihmp1hBoCm6zJ4+4Bx21 voQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=az9FdeZeBsTa5XfzEg2V2iTcb39ihdHdpTTBISvSsqQ=; b=sukew7y1DOqsWIVkzy4lthrqbrxXo2SPb/z4DoGYStoy0NSZazlCHIX+A6EhFyeXGT sRgmHNj9OkhrKT4GQeZEtLHLsVpqDUZ50RyQawt4neIQmF7APyOjw60bhjiWIqjOHXqI YCUmYsz8gUz2Th399VSg/JJQgQ9KsxK1Hlal19+WI21T8Cml/HTGTQdtWf8xyIkl7CUg nTnmlcQmi7Ps2l+4OgGFEYf973ChfTipIpV4B6ZvYp8lx5LgFfJZxqMb5VcJDJ0k8QWu ej6BKbO5XCzF2URMlbOcm6A/1NQzHDIe+d8O8GBvJx7B4xzIgtc+OCs2T3OUz38wUYO8 u7tA==
X-Gm-Message-State: AOAM5339yCifRLNGucyTaekHUJc/lTnYtU54atxhfOjpU29dYbdQjl1z MW1V/OENDwQXVlkYVFAb+i4P6ZoXA62aOQ==
X-Google-Smtp-Source: ABdhPJx5gF0g3O05eXYtClTqsL9LAYQJnKVkO4hGFTR39U9DVtcvsMBryXu/PFdfCI58xjBIeJobYw==
X-Received: by 2002:a63:62c7:: with SMTP id w190mr17248793pgb.25.1599488866698; Mon, 07 Sep 2020 07:27:46 -0700 (PDT)
Received: from [10.95.80.239] ([162.210.129.5]) by smtp.gmail.com with ESMTPSA id i62sm15261904pfe.140.2020.09.07.07.27.45 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 07 Sep 2020 07:27:45 -0700 (PDT)
Sender: Tony Li <tony1athome@gmail.com>
From: tony.li@tony.li
Message-Id: <F255842F-DF42-4F9F-9C5C-86FC22D4A6B7@tony.li>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F4843A34-DC0E-4582-B267-B976B641268F"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Date: Mon, 07 Sep 2020 07:27:44 -0700
In-Reply-To: <1887_1599476406_5F5612B6_1887_424_11_53C29892C857584299CBF5D05346208A48F5E4CC@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
Cc: "lsr@ietf.org" <lsr@ietf.org>
To: bruno.decraene@orange.com
References: <159665865921.15026.2581762617571023706@ietfa.amsl.com> <476BCC1F-0C33-4DEA-84DF-365FB5CBA377@tony.li> <21324_1599222537_5F523309_21324_463_12_53C29892C857584299CBF5D05346208A48F586AF@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <27306_1599228768_5F524B60_27306_466_34_53C29892C857584299CBF5D05346208A48F58942@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <CE94541D-C326-40A1-A1E2-436E14B31A5A@tony.li> <1887_1599476406_5F5612B6_1887_424_11_53C29892C857584299CBF5D05346208A48F5E4CC@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/pnFzTO-35P3GcwO29vE0nuqHBgk>
Subject: Re: [Lsr] I-D Action: draft-ietf-lsr-isis-area-proxy-03.txt
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: Mon, 07 Sep 2020 14:27:50 -0000

Hi Bruno,


> At this point, area proxy spec is clear with regards to nominal behavior. So indeed we are discussing error handling / transitions. (and thank you for considering those cases, much appreciated).
>  
> From memory, my understanding is the area proxy nominal behaviour requires:
> -          All routers in the area are L1 & L2
> -          All inside routers advertise the area proxy TLV
> -          An area leader advertises the Area Proxy System Identifier Sub-TLV


Something that we’re not allowed to talk about in the spec is that we’re assuming that ALL routers in the Inside Area are configured to enable Area Proxy.  Partial configuration is a misconfiguration or transitional to full configuration.

 
> If the above is not fulfilled, what is the expected behaviour? There is a priori 2 options:
> -          A) Return to regular IS-IS behaviour. i.e. all L2 LSPs from inside routers are flooded to L2 outside routers
> o   Pro: no new behaviour/code as this is regular IS-IS. Correct transit forwarding across the area.
> o   Con: suddenly increase size of L2 LSDB
> -          B) Keep filtering L2 LSP from inside routers
> o   Pro: no sudden increase of L2 LSDB size
> o   Con: transit traffic is partially dropped (if area LSP advertised while some routers are L1 only), no transit is possible (if area LSP is not advertised), or partial transit (some inside edge node do not advertise the area proxy TLV).
> §  Lack of transit is not an issue if there is a backup proxy area (e.g. a proxy area a replace a big single chassis).  It’s likely an issue is there is no backup proxy area (e.g. the area has built-in redundancy (e.g. spife/leaf) hence there is no need for another/backup proxy area. Network operator needs to be well aware in order to choose the correct design (rather than experience a bad surprise)
>  
> That’s an open question.
> As this point I do not have a preference, although naively I had “A” in mind. From your below answer, I think that you have “B” in mind. 


Yes. Given the above assumption, we want to assume transition.


> A priori the choice may be dependent on the missing condition.
> Possibly this could be clarified in a “operational consideration” or “error handling” section for network operator to be aware of the behaviour under failure/transition condition.


I’m open to suggestions and/or contributions.


> FYI, I’m considering such failure to be plausible over the years as all it need is one L1 router to boot and not advertise the area proxy TLV or be configured as L1 only.


30 years of doing this says that any crazy thing is possible and WILL happen somewhere, someplace in the fullness of time. Yes, ok, withdrawing the Proxy LSP in these cases is probably not optimal.  What should we say instead? Some failures are clearly fatal, some are not. What’s the right thing to do without a dissertation worth of analysis and special cases?

Tony