Re: [Lsr] Prefix Unreachable Announcement Use Cases

Jeff Tantsura <jefftant.ietf@gmail.com> Mon, 16 November 2020 10:35 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 61AF93A03AA for <lsr@ietfa.amsl.com>; Mon, 16 Nov 2020 02:35:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 GWwyUHhGr_B8 for <lsr@ietfa.amsl.com>; Mon, 16 Nov 2020 02:35:51 -0800 (PST)
Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) (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 3A47F3A0128 for <lsr@ietf.org>; Mon, 16 Nov 2020 02:35:51 -0800 (PST)
Received: by mail-pl1-x62f.google.com with SMTP id k7so8188896plk.3 for <lsr@ietf.org>; Mon, 16 Nov 2020 02:35:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=T3mT7j8YHrUkgunAwOtG6VMC6JCrDXt672ctuVok4V0=; b=WRLqoeJ2+XE7IAS2CZDq7ebLnef4sln2lhCmuzX0ECW6ZpgW/++xoJHXYnAwGRJKXO 6sxXFckyzBRGRRILeMDtb8vMcjjO0NpXj/0RYBmy/EPx9dUSbZSPQ85iPamTCnVwAMII cEXYUco8snd1tzuCMiK1R6WH5XBJ8nmbGpVvYMDL4lDTpCKYwjzSeBv8IkQxMyfjd9fr 6ctcD67U5Nd6j2YAFBG1g7qQPSke2nCOIktXYkL3z+caRkx5ZjSWit0qfPPk0zZiSDnS JJIDUVwgsz1pZSqba4oksAbklCKayhHXQKx7fVaNGicxauTHUTzs4f0fRhBqU3uG2gh+ uZBg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=T3mT7j8YHrUkgunAwOtG6VMC6JCrDXt672ctuVok4V0=; b=QWoLIdtrFH9XNiQAP8T+vXejb0OlT5CT5f+Qjz3Dd7AhYBHOejK8v7rGJjh209MrtC TJpW8MrRdcdb3YgTiMJrQCJYP2L6cKODePGnnn4pC3W+kaep8L4v7mV+S6FioHKe2q9v 1usFttdbG52j6F5i6GdAu0fni/ylNpyfrnfRupGwJJOVeTfRoUIHwPnosxE6ln52zx3q ZsxmNnaz/Z49yCWapR/adX4uyji6+53feuakoUSIsmmG27BYxwYa7gQ/Ia7NGtyUlW4s vueBZNPCayB5w3otLs3KAohuJZWcuY0zXJNsaF5QEZua247ZRbsFEmvD/Gsfsn6ZOO6M FaTA==
X-Gm-Message-State: AOAM533HszPli+L79c36zjTrokG86U5g5pM5rFvdE/vZTiKqI2M/+ixd NEocTdyGnriXtHUraeVCL7s=
X-Google-Smtp-Source: ABdhPJxmQ1P+TeS9FCRKuYBH7fJKd5icp4qQZFEH6b7xgeDh5LlZ2q8lLoCcGKLXZnCOxtREE+02eQ==
X-Received: by 2002:a17:902:bb94:b029:d6:edb2:4f41 with SMTP id m20-20020a170902bb94b02900d6edb24f41mr12224351pls.3.1605522950683; Mon, 16 Nov 2020 02:35:50 -0800 (PST)
Received: from [192.168.1.12] (c-73-63-232-212.hsd1.ca.comcast.net. [73.63.232.212]) by smtp.gmail.com with ESMTPSA id l20sm9501515pjq.33.2020.11.16.02.35.49 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 16 Nov 2020 02:35:49 -0800 (PST)
Content-Type: multipart/alternative; boundary=Apple-Mail-C5A33B63-BC90-42EF-BF4D-E3D755C0E8E0
Content-Transfer-Encoding: 7bit
From: Jeff Tantsura <jefftant.ietf@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Mon, 16 Nov 2020 02:35:48 -0800
Message-Id: <D477846E-1086-46A8-B2D6-E552623E2643@gmail.com>
References: <CAOj+MMH7zRaXNJTRC0ua7ohasUpo0MmeqgzcU9BdpcD7wD+Yrg@mail.gmail.com>
Cc: Aijun Wang <wangaijun@tsinghua.org.cn>, lsr <lsr@ietf.org>, "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>
In-Reply-To: <CAOj+MMH7zRaXNJTRC0ua7ohasUpo0MmeqgzcU9BdpcD7wD+Yrg@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
X-Mailer: iPhone Mail (18B92)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/qIS5mRRKpj8iFavkgC87bP3Ruk0>
Subject: Re: [Lsr] Prefix Unreachable Announcement Use Cases
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, 16 Nov 2020 10:35:52 -0000

+1 with Robert.

So you expect the following RIB state after PUA has been advertised:
10.0.0.1 - drop
10/24 - forward 

Unless there’s a recursively discarded next-hop (ala RTBH )  - how do you envision it?

Regards,
Jeff

> On Nov 16, 2020, at 00:25, Robert Raszuk <robert@raszuk.net> wrote:
> 
> 
>> I was not bringing RIFT's negative routies example as something inherently negative. I was just pointing it out to illustrate that today's data plane lookup does not really support "if does not match" checks.
>> 
>> [WAJ] In data plane, the device do still the “match” check, not “does not match” check.  When the router receives the PUA information, it will install one black hole route for a short time.
>> 
> 
> So your idea is that you install route for unreachable prefix to /dev/null ? 
> 
> And how would that help connectivity restoration ? 
> 
> Moreover it seems that it will just also prevent any local protection to locally bypass the failed destination. 
> 
> Bottom line is that I agree with one problem statement. However IMHO described actions upon reception of PUA are questionable at best. 
> 
> Cheers,
> R.