Re: [Idr] [GROW] BGP Looking Glass Capability

Gyan Mishra <hayabusagsm@gmail.com> Mon, 26 April 2021 01:37 UTC

Return-Path: <hayabusagsm@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C1193A0E6C; Sun, 25 Apr 2021 18:37:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.086
X-Spam-Level:
X-Spam-Status: No, score=-2.086 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, 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 6zQxkAUcL-FH; Sun, 25 Apr 2021 18:37:03 -0700 (PDT)
Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) (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 E30BD3A0E6B; Sun, 25 Apr 2021 18:37:02 -0700 (PDT)
Received: by mail-pj1-x1032.google.com with SMTP id gq23-20020a17090b1057b0290151869af68bso4203887pjb.4; Sun, 25 Apr 2021 18:37:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=r4gBTV9BCd6tDgR2Arxs5Mdzz6ffCVUOxmL+f5dYdig=; b=DPLmZAbp9LS4GeWnssKsGEDj/PArFg+Y9XG4a7f/4W92DEEGlKwt/PIyFpORDMsarz Kn+AixJwIZndF2GcLz7qHyEqHTEAsjNStfDJFPMQNQCAqxd7XTMmQqKJz2Q+zdL+Bx4e swaCmT8YLr1Pcl6yi0cHPsCBUEdZSKFIUMBCg6z2DmOxy8wXEB4LaO/dXewRZ39G96t6 DnUeYc1j0f5OEpdYdNgbss5lb7mavMe76inPaaWueto+D19hJcDMF7FcyccLwlxAH5YG CXDvk+8uJUbLq5i9EU5x+8IhBU2+3krJMomkRbt9DNX+NVZE/XXaumQ8sc6uVogh0pPw by6g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=r4gBTV9BCd6tDgR2Arxs5Mdzz6ffCVUOxmL+f5dYdig=; b=OHZ9UibN86HUwXYxJ9Z4BruozGqGo1hWXpYV/acdcWniUJbfNTN9uFAIzYAO5wytT+ 74Ah0TyAB8JOVxD9baC1mY3FqUBGm0orHKFQnxLOj8Jc5Vyrys6l4A75urOvoqgos01D ZE9rqjCNK0X1r6dDJNQhwwqBnu4nplHuIDBZUogIVjcOYYsZWsI6YkH5Md676p8lP2x7 1pVYbo0B+2hyDTsCzz0Iwm2ZW2GG9yJ1VI01Khdv9XcxCy5bFohtL1juGFA7ZwXcbyPF 5sQCaEhcrPspU0WNuDJCHEwE/ZjehpFYtJenFwzTMYxt8ABNEnZF1sP72GkHvSNmp9tA TV9A==
X-Gm-Message-State: AOAM533MY5+lE00yFoslgm6o6QZ6fdyxSDppaWR/eGZszo3Zwt3oGOUi HFLcIIzRcAZzar/2BFsHCUN245QbWndQ/jTPvQg=
X-Google-Smtp-Source: ABdhPJxrJSzbclyjcp3xQMOr5RhvXkMPhtjL7kPJgzWkBSdc+4K0dTwmXxqJoFG2RyrdFEZLEzWvLqWfhycHyk/lAlY=
X-Received: by 2002:a17:902:c1c1:b029:ed:1e01:201d with SMTP id c1-20020a170902c1c1b02900ed1e01201dmr4433992plc.50.1619401020315; Sun, 25 Apr 2021 18:37:00 -0700 (PDT)
MIME-Version: 1.0
References: <CACcWx2FN=o4chgOH6chbYkuCK82n2m+BCjfjpRPnM0qznBVQDw@mail.gmail.com> <BYAPR11MB3207629609F96C9D6EE61DACC0439@BYAPR11MB3207.namprd11.prod.outlook.com> <CAOj+MMHYdboq6on9-uB8uNQTzzJ=1hWU_qH38CegMXJzvV_Sxg@mail.gmail.com> <CACcWx2F2m_tyWXXrt1Mtr7PcmCfbO87eZGWNT=ifEW2XdjbCtA@mail.gmail.com> <CAOj+MMG4yhTq2nk08iE_uVcDY_T3PstS4UjLDrLQUcpsBm+B-g@mail.gmail.com> <CACcWx2EONXwhjZe+EhSPznhsT8bce2bT+XrDb-XiFLrGqNfHPA@mail.gmail.com> <CAOj+MMGYGTmLQQUrY_GrYhE1rrzUG783QZZRFoZM7PU5Ef0Fsg@mail.gmail.com> <CACcWx2Hum00bkHLiL0ZAzzBEAKavCEHCPyV_kkovw9AgC4-oaw@mail.gmail.com>
In-Reply-To: <CACcWx2Hum00bkHLiL0ZAzzBEAKavCEHCPyV_kkovw9AgC4-oaw@mail.gmail.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Sun, 25 Apr 2021 21:36:49 -0400
Message-ID: <CABNhwV3Kqnu74dV-wvzjgf6_v15ZF-KE77G=LfU0=rOGtvdo8Q@mail.gmail.com>
To: "Rayhaan Jaufeerally (IETF)" <ietf@rayhaan.ch>
Cc: Robert Raszuk <robert@raszuk.net>, "grow@ietf.org" <grow@ietf.org>, "idr@ietf. org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000909d6105c0d62e49"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/gyzFRXoL2AumwKXcs6Eid6OrYic>
Subject: Re: [Idr] [GROW] BGP Looking Glass Capability
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Apr 2021 01:37:07 -0000

+1 on the new AFI idea.  I would support developing the new draft.

Out of al the ideas proposed I think the new AFI seems to be the best
method of achieving the BGP looking glass capability and propagation of
routes.

Thanks

Gyan

On Sun, Apr 25, 2021 at 7:25 PM Rayhaan Jaufeerally (IETF) <ietf@rayhaan.ch>
wrote:

> Thanks for the history Robert, I should have read the authors list more
> closely on that draft :)
>
> From that description it seems that it was more circumstances at the time
> rather than push back on the implementation itself which is good news for
> trying to revive it,
>
> I'll try and rework the draft to use the operational message and see which
> common parts are useful here, then reply to the list / IDR with the updated
> draft,
>
> Cheers,
> Rayhaan
>
> On Mon, Apr 26, 2021 at 12:48 AM Robert Raszuk <robert@raszuk.net> wrote:
>
>> Hi Rayhaan,
>>
>>
>>> I guess a good starting point would be to reach out to IDR folks /
>>> authors of the operational message draft and get their input as to why it
>>> didn't progress further since that would be useful to guide any revival
>>> attempts.
>>>
>>
>> Good idea. As I am co-author of this draft taking the liberty to do it
>> right here :)
>>
>> A bit of history  - in min 2010 I wrote
>> https://tools.ietf.org/html/draft-raszuk-bgp-diagnostic-message-00.
>>
>> Then we spoke about it, trimmed a bit and formed what we considered most
>> important operationally into
>> https://tools.ietf.org/html/draft-ietf-idr-operational-message-00
>>
>> The draft was having good support during the IDR WG adoption and hence it
>> became WG doc.
>>
>> Since then most of the authors left the vendor world and our influence to
>> implement it in significant commercial BGP code bases was no longer
>> sufficient. Yet vendors told we will implement it if customers ask for it.
>> So we are 9+ years and still I am not sure if anyone cares much about
>> switching phone and email channels between NOCs into more programmatic way.
>>
>> Yet we do see from time to time a pop request to some form to tell peer
>> ascii strings like sms by BGP, pass some well known address, etc ...
>>
>> I think this is the fundamental challenge in how we operate peering
>> relations. I have seen a lot of good automation happening in the IX world,
>> but when trying to establish BGP sessions today it seems still emails, xls,
>> word documents style ...
>>
>> While it does not need to be all TLVs as listed in the
>> https://tools.ietf.org/html/draft-ietf-idr-operational-message-00 draft
>> but I think operational message is indeed needed.
>>
>> Cheers,
>> R.
>>
>> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*