Re: [Idr] draft-head-idr-bgp-ls-isis-fr-01 - WG adoption call (6/6 to 6/20)

Susan Hares <shares@ndzh.com> Wed, 08 June 2022 17:43 UTC

Return-Path: <shares@ndzh.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 C5807C14CF13 for <idr@ietfa.amsl.com>; Wed, 8 Jun 2022 10:43:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id it37RsTudRth for <idr@ietfa.amsl.com>; Wed, 8 Jun 2022 10:43:51 -0700 (PDT)
Received: from NAM11-CO1-obe.outbound.protection.outlook.com (mail-co1nam11on2062b.outbound.protection.outlook.com [IPv6:2a01:111:f400:7eab::62b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E594CC14CF1F for <idr@ietf.org>; Wed, 8 Jun 2022 10:43:51 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=T1xZ+3stPmf+j0gjxVhZlm+mZ096fMOWrlNw4XpJ1RBgm9cDB4jVm+Fki8tSoDAcoscxxdEeaQquM2qHL4v3O6+bUs0ILiy7SVFrOzk8V1PeKW8Eaax/nZp1VddmDEoN5aB9mQr5JOq1BMe7SxDX6co0JPHCV4FLiGOGv06R7JxU0W833Yu3HC/UdB4Y8ro8zYV4Ncp0CSiaicQwj/Cv5cOm3fKCQKtfTeTC/Oq8/BC6gUs7HinzMNxKC8+0cC7cBnQ3cLOSMD8/uiqgQXKHDoe8r6rAON7zUUqaM/RqsWzmo8PhGe+g+pJefo7sXCkTcqnHiIITin6+CDG71TX6yA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=998k76QkgeOjMOigqMoi+FsYlpPLzcT57L3jVou+b+s=; b=Yw4MXwGBVmViQ6zk+TelqsIniZjlvzocWb3zP+mNFV0YSxG7iEInf6+gaZcf5vGvHE18NjmGkxuwKYAEtGHU3wtj6jPP3y3BGDjBhefma6t+aJrx1u0DqbdXios2iyfXCEVCTb5fkOHDpgUu511sF00D8QSwNUW9SxrOBSwJGqBzeaopPqSK5ZZge0iBGXSlV7A84jMquqdU0sXVkHEWIvbTe+jaivkUuoX165N0dQGdYWkX6QVnOHqNPVJus2KSjfpOEwxQNsdTchLzH7Q7S8f2UD+b6bdirsRVcdDO5mT+WSSJkDSSxSaRvdW7UXLjgwvgjgoF7o/1X3UBdzy4tw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=fail (sender ip is 13.59.96.180) smtp.rcpttodomain=btconnect.com smtp.mailfrom=ndzh.com; dmarc=none action=none header.from=ndzh.com; dkim=none (message not signed); arc=none
Received: from MW2PR16CA0028.namprd16.prod.outlook.com (2603:10b6:907::41) by CO1PR08MB6563.namprd08.prod.outlook.com (2603:10b6:303:92::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5332.12; Wed, 8 Jun 2022 17:43:48 +0000
Received: from MW2NAM12FT042.eop-nam12.prod.protection.outlook.com (2603:10b6:907:0:cafe::b6) by MW2PR16CA0028.outlook.office365.com (2603:10b6:907::41) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5332.12 via Frontend Transport; Wed, 8 Jun 2022 17:43:48 +0000
X-MS-Exchange-Authentication-Results: spf=fail (sender IP is 13.59.96.180) smtp.mailfrom=ndzh.com; dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=ndzh.com;
Received-SPF: Fail (protection.outlook.com: domain of ndzh.com does not designate 13.59.96.180 as permitted sender) receiver=protection.outlook.com; client-ip=13.59.96.180; helo=obx.inkyphishfence.com;
Received: from obx.inkyphishfence.com (13.59.96.180) by MW2NAM12FT042.mail.protection.outlook.com (10.13.180.237) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5353.5 via Frontend Transport; Wed, 8 Jun 2022 17:43:47 +0000
Received: from NAM10-MW2-obe.outbound.protection.outlook.com (mail-mw2nam10lp2104.outbound.protection.outlook.com [104.47.55.104]) by obx-inbound.inkyphishfence.com (Postfix) with ESMTPS id D9FA017D42F; Wed, 8 Jun 2022 17:43:45 +0000 (UTC)
Received: from BYAPR08MB4872.namprd08.prod.outlook.com (2603:10b6:a03:70::17) by BN7PR08MB4754.namprd08.prod.outlook.com (2603:10b6:408:30::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5314.13; Wed, 8 Jun 2022 17:43:43 +0000
Received: from BYAPR08MB4872.namprd08.prod.outlook.com ([fe80::495a:8996:ca89:7cff]) by BYAPR08MB4872.namprd08.prod.outlook.com ([fe80::495a:8996:ca89:7cff%5]) with mapi id 15.20.5293.019; Wed, 8 Jun 2022 17:43:43 +0000
From: Susan Hares <shares@ndzh.com>
To: Robert Raszuk <robert@raszuk.net>, tom petch <ietfc@btconnect.com>
CC: Jordan Head <jhead=40juniper.net@dmarc.ietf.org>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] draft-head-idr-bgp-ls-isis-fr-01 - WG adoption call (6/6 to 6/20)
Thread-Index: AQHYemqOCwf/zvFUqUiMOPLcqbFfqK1EA8/g//++j4CAAEqzAIABmI/agAAPH4CAABTp0A==
Date: Wed, 08 Jun 2022 17:43:43 +0000
Message-ID: <BYAPR08MB4872DF18CAFE52D4F1B668A1B3A49@BYAPR08MB4872.namprd08.prod.outlook.com>
References: <A7C54708-0C2D-45B2-B433-A27A34B3656C@cisco.com> <BY5PR11MB4337D15D1445502D594E0469C1A59@BY5PR11MB4337.namprd11.prod.outlook.com> <AC14EDB8-661D-4DB0-8147-7EE1666247BE@cisco.com> <9A369BED-21EE-465A-9423-22E0C16D2292@juniper.net> <AM7PR07MB6248884DAE02E90568F9F45AA0A49@AM7PR07MB6248.eurprd07.prod.outlook.com> <CAOj+MMEBM+ystwh40wyPRKo1j1MKU7HQ-_vqtB9owjvNGr0d8Q@mail.gmail.com>
In-Reply-To: <CAOj+MMEBM+ystwh40wyPRKo1j1MKU7HQ-_vqtB9owjvNGr0d8Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-MS-Office365-Filtering-Correlation-Id: 32db9bc3-a404-41ee-67c2-08da497670d7
x-ms-traffictypediagnostic: BN7PR08MB4754:EE_|MW2NAM12FT042:EE_|CO1PR08MB6563:EE_
X-Microsoft-Antispam-PRVS: <CO1PR08MB65637D44EAF96690616695BDB3A49@CO1PR08MB6563.namprd08.prod.outlook.com>
X-MS-Exchange-SenderADCheck: 1
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam-Untrusted: BCL:0;
X-Microsoft-Antispam-Message-Info-Original: PsgaKzWZghONzbx0y9kfq6ht9rH9vaELH4i2ZTmPAsM2vBVdyWsg/NfyuRlLE+Vj8qJ7DaRGFDHbrce7FeU4Jj9ZiM+HtT6wWhB2CTyE9OmHbRNIuKeuqUfw/maJwinxxR7riO50pHmHU+F/Jzzt0SJXtFjajHkwgd2DTAGpEzrC/HyCV+h8ZZ2DjWbObcqxU7na29qd6zKOrYt2wu0e7jA4T2dO7qG20Y65yHw0GODVuJrHwfC1Nzf+/xlcXjh7hzwMNO9+fcgsC5gsG9rI3ARlrF+Bjba4gVW+UQnAlbgcBBrXaL08lC8uhRN+99l3hchDeuS8PPWEElb5OMG3iGb7TKv+Lw+SkfUJQiSBrkEHlUQWGAlXkid4cIAiYfzhkpU1gcPcYftZxnxSwEJ+UTq8nc3dTg1hVZcc0gybP1UHSUPNyHHnsFTT64JQhQcNa/gqnNa61sx1G0rA0fwr1hkNf7F2Cm+bR+Ky5+tvBTLgRTPAWUW7PDr+q0M7GFHLqW49um0ELpcd1q5gg5rByeruxoPYuCbZaG7dN2yHFCvr/4CBOZn+L/zNHhISyAlQoMRG6WEhOXehmDtrqWyZav9QiawIqUhfz8ao6A/JkZvFvmCbI8j519A5EwtIBCUbnNeulz+ClprKgRqAoS5jfZYD0C4witcfEP9tapJ1JmVCC8jLC6eCLhXXRVXpyYjt990eRHJ96jOGxIdk3UWuOqd3H0nMKRtuHfqFRd4kMvZ0Ye/0gyCyVTwrLjNWEEZbOyvHlz3sCMNn62OUJID9gs3XkYYgvTy5QFu1ygR+EH2d0zVEgNawM+vstZuvWPik
X-Forefront-Antispam-Report-Untrusted: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BYAPR08MB4872.namprd08.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230001)(39830400003)(346002)(136003)(396003)(366004)(83380400001)(71200400001)(55016003)(316002)(508600001)(2906002)(166002)(122000001)(53546011)(7696005)(186003)(6506007)(8936002)(33656002)(38070700005)(4326008)(38100700002)(9686003)(26005)(52536014)(66556008)(966005)(54906003)(5660300002)(76116006)(66946007)(41300700001)(66476007)(64756008)(8676002)(66446008)(110136005)(86362001); DIR:OUT; SFP:1101;
Content-Type: multipart/alternative; boundary="_000_BYAPR08MB4872DF18CAFE52D4F1B668A1B3A49BYAPR08MB4872namp_"
MIME-Version: 1.0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN7PR08MB4754
X-Inky-Outbound-Processed: True
X-EOPAttributedMessage: 0
X-MS-Exchange-Transport-CrossTenantHeadersStripped: MW2NAM12FT042.eop-nam12.prod.protection.outlook.com
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id-Prvs: 3a74b362-32ba-4c52-e376-08da49766eac
X-IPW-GroupMember: False
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: pEEpJeOdw5K+nfCpSRogxmXxzgH+fLs+d5AgQUHfj+tWxvEvKg3odOwvZSfCuAve7Nclq4sKYuQBf5OEAEcRvNqy9hfWrpo/umSjZ6jC7S3O1Epp8d41+nWsxNkdKT+h6kIww0sWTzD2F+t4/gFp+d6NIz8zAScknajI/ChhSYFVBSvLGErcIjrku6WzTQndbEukTqmmN23Zebcee7uibQaeqnm17QW/wea/RusGVeUq4qX6+SRMl0cR05ain1alwjnNUN/ol19kqk8wyswwyWU75qqvrAu1Xe0omkoQu/EpzxQie739IOsQoymxjRzyPVSnWFlZZk9TMx9wXu95XZC+g2hEEhrTHCjW87KojMhlHf5Hn5vjj55fI7Im8XinL1ghPQK9G8M1QiNojdEaO5V3H7RfJveb/YSn1mrQA8D0xU/ux6MCJOkw9KHgAW5/5oJNvQlLqw15jhXXEihuiV348K0z9uzqQLEdFj2f4tof8mtbsEEjvUEeWPVEBQwvyneJGmCbuv97hMi/QXGHRnjjFWwiPES3Upuq1fbIPz0omFLC6c7zt2Lys8Jf+jMcM20UfTd95RSSpyRGjWRTtA/VfYk/fAIGImDli33HQzPO/vJ/tq+LmCuYnmYrwX5L+qnL2+vvH8fdIg2syzEDhucdZZtn7x/U55ZeoljtKFFBRAwH7Sdst5BwcUQ/cN/C7lT+sxY6ExX/T2BF691zRRaQXlhPGRLuCGCbqRmp4PFcZG7X3vq6E6d67rHZqRMvczibYh1Ot32De/mclwl7hdGO5EkswTvnNfQgo+2MIcU=
X-Forefront-Antispam-Report: CIP:13.59.96.180; CTRY:US; LANG:en; SCL:1; SRV:; IPV:CAL; SFV:NSPM; H:obx.inkyphishfence.com; PTR:obx-outbound.inkyphishfence.com; CAT:NONE; SFS:(13230001)(346002)(136003)(396003)(39830400003)(36840700001)(46966006)(316002)(5660300002)(55016003)(966005)(166002)(82310400005)(508600001)(45080400002)(4326008)(33656002)(52536014)(70586007)(70206006)(40480700001)(296002)(54906003)(8936002)(8676002)(30864003)(356005)(86362001)(186003)(7636003)(36860700001)(110136005)(41300700001)(83380400001)(336012)(47076005)(6506007)(53546011)(7696005)(2906002)(9686003)(33964004)(26005); DIR:OUT; SFP:1101;
X-OriginatorOrg: ndzh.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 08 Jun 2022 17:43:47.2605 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 32db9bc3-a404-41ee-67c2-08da497670d7
X-MS-Exchange-CrossTenant-Id: d6c573f1-34ce-4e5a-8411-94cc752db3e5
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=d6c573f1-34ce-4e5a-8411-94cc752db3e5; Ip=[13.59.96.180]; Helo=[obx.inkyphishfence.com]
X-MS-Exchange-CrossTenant-AuthSource: MW2NAM12FT042.eop-nam12.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR08MB6563
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/LiTN8voZnDxZ_w6oU3RzgYSU4iQ>
Subject: Re: [Idr] draft-head-idr-bgp-ls-isis-fr-01 - WG adoption call (6/6 to 6/20)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 08 Jun 2022 17:43:55 -0000

Robert:

I will be glad to bring up this topic at IETF-114.

Sue

From: Robert Raszuk <robert@raszuk.net>
Sent: Wednesday, June 8, 2022 12:29 PM
To: tom petch <ietfc@btconnect.com>
Cc: Jordan Head <jhead=40juniper.net@dmarc.ietf.org>; Susan Hares <shares@ndzh.com>; idr@ietf.org
Subject: Re: [Idr] draft-head-idr-bgp-ls-isis-fr-01 - WG adoption call (6/6 to 6/20)

Hi Tom, Just one clarification ... > too many ways of doing the same thing This discussion is not about accomplishing the same thing both with IGP and BGP. This discussion (generally about BGP-LS)
External (robert@raszuk.net<mailto:robert@raszuk.net>)
  Report This Email<https://protection.inkyphishfence.com/report?id=bmV0b3JnMTA1ODY5MTIvc2hhcmVzQG5kemguY29tLzQzNTkzNzNlYzFlZDg2MTZmN2NjMjE5MDUyNzVkMjUxLzE2NTQ3MDU3MjcuNDc=#key=9ca97d3b9b49d8207fcd341c8b489280>  FAQ<https://www.inky.com/banner-faq>  GoDaddy Advanced Email Security, Powered by INKY<https://www.inky.com/protection-by-inky>

Hi Tom,

Just one clarification ...

>  too many ways of doing the same thing

This discussion is not about accomplishing the same thing both with IGP and BGP. This discussion (generally about BGP-LS) is about mandating BGP to carry IGP info for services invented in IGP to even work.

And not only carry ... to understand every bit of it, parse it, check it, pack it, send it etc ... BGP hop by BGP hop.

And not only when you invent new stuff. Every time you do enhancement or even bug fix you need to do the same twice in IGP and in BGP as one seems useless without the other for end users.

This circle IMO really needs to be discussed and steps taken to break this loop.

Best,
R.












On Wed, Jun 8, 2022 at 5:43 PM tom petch <ietfc@btconnect.com<mailto:ietfc@btconnect.com>> wrote:
From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> on behalf of Jordan Head <jhead=40juniper.net@dmarc.ietf.org<mailto:40juniper.net@dmarc.ietf.org>>
Sent: 07 June 2022 20:12

Hi Acee, Les,

Good suggestion, happy to make the title more explicit on the next version of the draft.

<tp>

Loading up an identifier with lots of semantics rendering it cumbersome is  a pet hate of mine, but you have already done that:-(  At least it is only an ephemeral name that vanishes and has no relevance once a specification becomes an RFC

Changing the name to another one is even worse.  It makes it hard to track what the history of an I-D is.  You need to know where to look on the IETF website to find the old names.  I have known ADs who failed the test and did not find the early versions of an I-D at Last Call.

In this case,  it could make it hard to find the discussion about adoption which seems to be as much against as for.  I echo the thought that the protocols have got themselves into a tangle, too many ways of doing the same thing, and while the marketplace will decide, that can take several years and leave some frustrated that what was obviously the best approach has fallen by the wayside.

Tom Petch

Thanks

From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> on behalf of "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org<mailto:40cisco.com@dmarc.ietf.org>>
Date: Tuesday, June 7, 2022 at 10:45 AM
To: "Les Ginsberg (ginsberg)" <ginsberg=40cisco.com@dmarc.ietf.org<mailto:40cisco.com@dmarc.ietf.org>>, Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>, "idr@ietf.org<mailto:idr@ietf.org>" <idr@ietf.org<mailto:idr@ietf.org>>
Subject: Re: [Idr] draft-head-idr-bgp-ls-isis-fr-01 - WG adoption call (6/6 to 6/20)

[External Email. Be cautious of content]

I agree – for many of us, “fr” will always bring frame relay to mind first…
Acee

From: "Les Ginsberg (ginsberg)" <ginsberg=40cisco.com@dmarc.ietf.org<mailto:40cisco.com@dmarc.ietf.org>>
Date: Tuesday, June 7, 2022 at 10:42 AM
To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>, Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>, IDR List <idr@ietf.org<mailto:idr@ietf.org>>
Subject: RE: [Idr] draft-head-idr-bgp-ls-isis-fr-01 - WG adoption call (6/6 to 6/20)

I also support adoption.

Regarding the draft name, “fr” is quite cryptic and somewhat ambiguous.

“draft-head-idr-bgp-ls-isis-flood-reflection” would align the name with the LSR draft – but if that is considered too long maybe “draft-head-idr-bgp-ls-isis-freflect” ??

   Les


From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> On Behalf Of Acee Lindem (acee)
Sent: Tuesday, June 7, 2022 5:32 AM
To: Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>; idr@ietf.org<mailto:idr@ietf.org>
Subject: Re: [Idr] draft-head-idr-bgp-ls-isis-fr-01 - WG adoption call (6/6 to 6/20)

I support WG adoption – the corresponding LSR draft has completed WG last call and is awaiting AD review.

Thanks,
Acee

From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org><mailto:idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>>> on behalf of Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com><mailto:shares@ndzh.com<mailto:shares@ndzh.com>>>
Date: Monday, June 6, 2022 at 5:28 PM
To: IDR List <idr@ietf.org<mailto:idr@ietf.org><mailto:idr@ietf.org<mailto:idr@ietf.org>>>
Subject: [Idr] draft-head-idr-bgp-ls-isis-fr-01 - WG adoption call (6/6 to 6/20)

This begins a 2 week WG adoption call for draft-head-idr-bgp-ls-isis-fr-01.txt

https://datatracker.ietf.org/doc/draft-head-idr-bgp-ls-isis-fr/<https://shared.outlook.inky.com/link?domain=datatracker.ietf.org&t=h.eJxFjUESgyAQBL-S4hxAUEA9-RVkV6U0ai14MZW_R3PJdbqm-80OWlj7YFPOe2qlBJ99Jh9mJBExD2KjUcIWJJAfMp_QA49AvB93viQeU0x8IMmeDzbfnhXz9VCFqW2jtEyTJ0zdCuckwvaSVWma0pUYFEJtlR1cCFo1hdHOgDZKKmsqVxinnajcbcXbSluPlDvy6TxmcTVuAj_ynz5fdqU_Kw.MEQCIDCLNl0VXUL8vUhjUg-gdn4ZrY9wv-1v5orFUcJPqPkAAiBYyj-X2srBlqI8-tfUxIlUu-W_oxJPYzmUm8h-3MfP_w><https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-head-idr-bgp-ls-isis-fr/__;!!NEt6yMaO-gk!CafxHn3pbZysrIyVSxj84fABHpIaBa6N9ARiX1QpzY1aZZA_zdNvXbzlu0c5O_XryeexWrPa3CclpsKqYxOn2MWio074HA$<https://shared.outlook.inky.com/link?domain=urldefense.com&t=h.eJxFj8tugzAURH8lQV3WGAPGkG5CokqJqiR9SM1jg4wfgUKB2k4EVP33QlSpyztHM3Pn27qo0ppNrMyYRs8gHE4upKi0sFn9Ca8eTJI_xqmhRlFWCGXnwki7VmfIawa5otKATFAOcq5Aem5AqUGucw2kGvwP0-n20QTdhu7AuZguqWxXldekp06rdff-1n6EvowXq2ZNFzTYRvFrfkAvTX9E9HSKk55vr4e0Ly8Ow7vkoDoh2r16pt6SlY1--jq2u8rd7PPaIf4qvrPuJ1YxTqqEGT5EDg6DCLlQZ1QJPa94n92m-R6OPOIJhgQPAxRIwpiLIge7BHMXI4gC7BMHE5fYPhlTxZiq6lQoM1dU95fCHjpGwm_kX_r5BYL0byA.MEYCIQC--Ap91fs8cqybV2bx7pTsxZVVJNitUxpNhsN3vGJPIwIhAIw493ipjVUL-9PLlgLKKdl5OD-if1OiUDnreokHlsr_>>

  This document defines one new BGP-LS (BGP Link-State) TLV for
   Flood Reflection to match the ISIS TLV for flood reduction.

   The draft is short (5 total pages).

Since this BGP-LS feature has been adopted by IS-IS,
Please consider


1.       Is there any technical difficulty with adding this to the BGP-LS code points?
2.   Is this draft ready for publication?
3.   Does this addition help operational networks.

Cheers, Sue Hares





Juniper Business Use Only

_______________________________________________
Idr mailing list
Idr@ietf.org<mailto:Idr@ietf.org>
https://www.ietf.org/mailman/listinfo/idr<https://shared.outlook.inky.com/link?domain=www.ietf.org&t=h.eJxFjUEOgyAURK9iWDd8QeGrK69CAStRwQDGxKZ3r3TT7byZN29yxJUMFZlz3tMAcJ4ndTZPNMQXbMqtm_KwupSdnwI4E8mjIktZeJvvDqtFJ3vGIc0q2jR6c81Uhw3aRvQNNlYzazrJ5IRac9bXgqMwXDBgUrRYC-RIWyxWW6wxPG3MY1TpOhZ6fxRifuQffb68WTfC.MEYCIQCvv07_-09rJ9sFwheM9xPI1lcd1OnNRcwDcEwCuVBnrwIhAMypmIVkbt0tkJJfmSsxCkiSkXMENOz3tZOBD1HmfD8K>