Re: [Lsvr] Initiating LSVR re-chartering discussion - draft#1 proposal
Linda Dunbar <linda.dunbar@futurewei.com> Thu, 07 December 2023 01:21 UTC
Return-Path: <linda.dunbar@futurewei.com>
X-Original-To: lsvr@ietfa.amsl.com
Delivered-To: lsvr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 576E0C14F61C for <lsvr@ietfa.amsl.com>; Wed, 6 Dec 2023 17:21:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.com
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 s6H31WbtxL5h for <lsvr@ietfa.amsl.com>; Wed, 6 Dec 2023 17:21:49 -0800 (PST)
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (mail-bn8nam11on2100.outbound.protection.outlook.com [40.107.236.100]) (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 02600C151087 for <lsvr@ietf.org>; Wed, 6 Dec 2023 17:21:48 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=C4W1OU6dRVeXr7NJdWKjNL5z+V4tJYoqHyw8yFLuECgpNzhtURctxzZEuUnSTRyN797IzOmUe9DEcVaYsJg8uak0sEfjMxqVnxy8do90P/v+WfJxWOWQwVSPd3FY3zAhpp6jjbN7DdpLxIkPsx99Q1gffLMgXjdh1L9aHS/GrHoFhb2r/GCpcvEynCH/F11H400yCUdk/aBCSnhe2L+WR8vb5ObmlWD/R2utMoxg6605Cli/5++MfldJ+Pxuf8Q+yjLlDha1CX3uEEg0dKgkxqxufTMeI7YcAwCZ4weI59nBZJPX59sorTaFYb4qTzyj2RCI5FYkhLHxWIvk8gmIiw==
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=xwyFc9TApThv3A0xGeXKnAC25TBTK7YSfQ19MvwY/CM=; b=EV7yxEPi+02q+pRFFHw7BdvO5eWoAP/G7BO1wJz09ms/GfwI73gXG2NXaDxuTpZMiZcXoUmyDv3X6WtwR875+MULv7dMtC3BvyEG+uZBt98qg8XG3cfxmdRZ/fgoAd+lKPl3BMw6+It/zObl3856pJGeKI6pVvEv+BBQktCp9jKA2vYecAKEMP989KxNO1ODfWeQlyaGJyAdAbJke6i7fE56+bdTH/VeGH728r6pouGz0n85OI1+FrsDLlcqXcpIE6MLToGVc88Tgtlbf1Rg52tK0I6ICW/s2GnZRAfqZcUROef2QrmH2NNdx8jsCmoKx1jN3FlXJuW3CkmvjShkWg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=xwyFc9TApThv3A0xGeXKnAC25TBTK7YSfQ19MvwY/CM=; b=BLVwv+F7RgXwthZSFWXpeVzKpAaWgi8PPDGeFpac+mKBhqOJQ95HKC8eyD3oMaslJf1JAFo71fjPM373thyKP8f0Lq73QQjkg3yETHEWLr0FktEPY+DlL3/fx8K7e8PHN3IQEzUFmqb7kbHlNXCEaHnYX7OY27gOWKDuZ3O0Q2I=
Received: from CO1PR13MB4920.namprd13.prod.outlook.com (2603:10b6:303:f7::17) by CH2PR13MB3880.namprd13.prod.outlook.com (2603:10b6:610:9a::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7046.32; Thu, 7 Dec 2023 01:21:45 +0000
Received: from CO1PR13MB4920.namprd13.prod.outlook.com ([fe80::17a7:6986:bf6:5efb]) by CO1PR13MB4920.namprd13.prod.outlook.com ([fe80::17a7:6986:bf6:5efb%6]) with mapi id 15.20.7068.025; Thu, 7 Dec 2023 01:21:45 +0000
From: Linda Dunbar <linda.dunbar@futurewei.com>
To: "Gunter van de Velde (Nokia)" <gunter.van_de_velde@nokia.com>
CC: "lsvr@ietf.org" <lsvr@ietf.org>
Thread-Topic: [Lsvr] Initiating LSVR re-chartering discussion - draft#1 proposal
Thread-Index: AQHaKIRWbuoeudUQJEWF7VthaRi+8rCcxIEAgAA8yUA=
Date: Thu, 07 Dec 2023 01:21:44 +0000
Message-ID: <CO1PR13MB49207C095DBDD6398533B458858BA@CO1PR13MB4920.namprd13.prod.outlook.com>
References: <AS1PR07MB85897E82BA2DFFEDFB7C08FBE085A@AS1PR07MB8589.eurprd07.prod.outlook.com> <CA+RyBmVAgM7d2eN3S2+mnw1vzkMKm4VoVEuyMmLXExVY4kiYGQ@mail.gmail.com> <AS1PR07MB85891B2E18F6A9F826247C10E084A@AS1PR07MB8589.eurprd07.prod.outlook.com> <BY3PR06MB80525FC7A1751CCD26126C619A84A@BY3PR06MB8052.namprd06.prod.outlook.com> <m2msunqd4s.wl-randy@psg.com> <BY3PR06MB80529998FDB03A1DED3FDF949A84A@BY3PR06MB8052.namprd06.prod.outlook.com>
In-Reply-To: <BY3PR06MB80529998FDB03A1DED3FDF949A84A@BY3PR06MB8052.namprd06.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=futurewei.com;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: CO1PR13MB4920:EE_|CH2PR13MB3880:EE_
x-ms-office365-filtering-correlation-id: 5ce2b626-4c7f-4e86-1237-08dbf6c2e048
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 97xttgM2YwVDfLhSkrYS2Axwr+o4o2S5msdjSBIW2oHMmkC5BZwb/RdiFV5pa4+GwvlBdZEd+Mn3YsEoTbpBpqC1MS79laU34RHVZX12vYAIhMqg18LjBvbso8rJGyGkbgNuRxGU5XvraubXbfnymA/tqc95DpT4T5615UxSKwsOHvUKfSGfcg/mqQjlEWnVX0LhA7fxDEJwds6a6HABJ9QvDSrKTIwzSDHAHA6ZurPDnqU4cSGM+OgHDTRR0+ro6+Q6MI6tppOybbvWCVSLjp55t5lMoYZyaa1nOZ4XdCYv79s0Sq5oDPPmSQazQrKQQMQYIOGW2gWEVZXeIuH1X/sc+aXhMqFDWRaTrLHnwtSluM8Zsdkwea6boOXiYEn5b3yZSLkX6ycwsTvni+mXyFmWNtSy9qKWe2XTAqa47QgCPXVHSnQLK3jKblRbLhaoSBC0rk7ZKgmzTaya2PyhAsyMe4VtSKNnydGLwcbHvu8i+g9FS4YnTsvu5PM+oy4P1aOGHF3WNAZ6xYokT7EqHB9ix0B79xPw8Z6im+uZ8uYVSw1390r2iwNyGfg7ZtWZL0Oi1WMMGDHPPI4L/WsBIEYNNAgLAAsabLo9leAEsVTFitnwRizZ2mfAZT0iq3bCmfEoUDNqOap+K2rUmo7WY5czlI2cFmVaKEnQ/nXBIU+xoB2FJlSdw7U8v48yHkQqzbFTqt5C3yhxVKzMZV7SPa8X2KwgTsNKU82EIrqdZD2+loUfBYhfReC+crieiPv5
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:CO1PR13MB4920.namprd13.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230031)(366004)(136003)(39840400004)(376002)(396003)(346002)(230922051799003)(230273577357003)(230173577357003)(64100799003)(186009)(451199024)(1800799012)(6916009)(66946007)(66476007)(66446008)(64756008)(76116006)(8676002)(316002)(4326008)(296002)(8936002)(71200400001)(478600001)(66899024)(66556008)(3613699003)(38070700009)(41300700001)(5660300002)(44832011)(2906002)(33656002)(86362001)(52536014)(26005)(122000001)(83380400001)(38100700002)(6506007)(55016003)(7696005)(9686003)(17413003); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: dOfQ1I7ynKg5pcXhyUoCrYH/kxFjqC/EejRHi8rL3JmauK46YJTJavJjUlmY3OjH5CF8R1ixgsreYeoM6NEwhuzgnRu0Dz+1CI5vi5fWRfncqup4XAxvc+qBKSL44tEziJM76sxEcQMpYOf5mSXZPjoG3l842u6TfA7GUQ9KjHqDGvshhbyGkOpYP4mv0Ou7YNpAwCnTYBTH9sdya2pJXwfTSPToGnqgezaHYe73wOAUPNRzc0QxJBUNwUXHfK5dKEaMPxlksNMTsBX/IAM2On9ZiWbgdnM+WhF/k0WlpW1cItfmlGzlI2k/o98tkP6FkRRPqIQ7UbSuLaYXaRcGXhsVVxVq8jUgCcQISQpfCMhYmYsnCvl4d61T5g1hEY49QHGFFD/o83PyVnReneAguorsiMxNYr4gLl9CeAp4hb2i/c8Rt80C3jmYCRst5fiUXunv1iDyeMjz87e032KdOqFWC52foKqB3Cm8ZH8VdP9aWfnmE2xme/ssHE9dxWGosJdDotCWMNb8AnXowgRtw6sGhwusePlWTdqzmF4yglrZz3hOJ72o7AzsZw3QA/rGj+wNu7U5RY+Bhpodq1iL+6BhK/qNELBWOvARs1+vyNs6eLUj42b4b7C8877dcGru94WdVBQna+/6i3hb+vvcNFNCREsIULi2wHQcx2DEZeZ7kawJHWXsG1IYcv3HjjP+nb+CdZ40LphK5gMdIxvBfmzR9x/kH1+rB4XxYrqGd5TPdiR2kwCwbOTcMe5Z7oJ0Ozi1Dy1upWAsymDso2cWmsaUMXe78cJe+vHVivFYZ9ivBV9BqJUN7THZP5NWXHKlv65nRHjcaonw3VZalWAiZjYzX+oFoHLZdRi0rJlnF0Bkdya1v4Ttb8Lxdz1GfPECCYTijJ4O9Zq3MH/D1fOX6Cq5CZKV4x7xlDiET7pzztlIefiMmLNzWXKZsGfqz+Ti4cctVhgCDXyOwva7k/+5NKVL4l6+GKEupQZo14wlMPWhI1ms5v7LOeiJ64MyNMumbvkz6jWTKBHSfDxEEO0rX33/vONGazguK71KnTlwQ8BEcWHWfLsJ7bJn0lRhlKT8oORCGQg18421qEFuDqNuOztw8bvEk22NeV+EIKl8ScikJwJCEWNqMG0cTGqUWMya0lpS0taxJhEChBp8iEN0gjCm7HPXg7ufUDcJ49Rsys7OsxkYWCm1V5dtvNrXbwnxD7L8VHA1GjDJ0pDXcXSK+EucRA09MBfqJCX0heBta0QkBYQUql9RBNduXqkphmSinGv48ps7iBww0z0nPCcqnjqq1nMoWWaOXQloKEqv90AkFvO07tV6/ZuYertOKMrGd5BUWLpTxQcC9fuwypalm9AxyC4kMuDk85+zoyVRMqA56jo7wdU9cgnupNMuTOWju1c9P4UahqUvLrDiAr9Taep3lzNvmvTD+7ajEIW02R70eyh57Jyq4T/8OJczfttOFLHltHf1C98tvl8XFgtuK5J5kNb69w8eGJOhZKIsmdnPXouVW0zCJ+nCHoOZMUI3gSLyTtWL9aHzcn/sKAWO/7Ne4aD9TyUIJ17VtWYXv2N0WfbAmp/6JPhMu9FkaITa
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CO1PR13MB4920.namprd13.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 5ce2b626-4c7f-4e86-1237-08dbf6c2e048
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Dec 2023 01:21:44.9654 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: w/5I+3X0tFQb13mj+dXXddBG5+j6czUzG1r6S7mQcu/yoTpB/BWTEpgudj7EPOo7Ibwk1hWXKBNJLgl7uuiTSw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR13MB3880
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsvr/-d8GeFQLE8tlUqo0W-9-MeGouZg>
Subject: Re: [Lsvr] Initiating LSVR re-chartering discussion - draft#1 proposal
X-BeenThere: lsvr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Link State Vector Routing <lsvr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsvr>, <mailto:lsvr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsvr/>
List-Post: <mailto:lsvr@ietf.org>
List-Help: <mailto:lsvr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsvr>, <mailto:lsvr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Dec 2023 01:21:53 -0000
Gunter, et al. , Thanks for initiating the re-chartering discussion. With many large-scale data centers using only Path Vector based routing, as described in RFC7938 (Use of BGP for Routing in Large-Scale Data Centers), and the trend towards congestion control in hyperscale DC for ML training models, the LSVR rechartering should consider addressing those issues. For example, the new LSVR WG can explore potential mechanisms to enable data centers with only path vector-based routing (e.g., BGP) for superscale computing.. Cheers, Linda -----Original Message----- [Lsvr] Initiating LSVR re-chartering discussion - draft#1 proposal "Gunter van de Velde (Nokia)" <gunter.van_de_velde@nokia.com> Tue, 05 December 2023 10:49 UTCShow header Hi LSVR WG, We would like to initiate the convergence towards a first LSVR charter update. During IETF LSVR118 WG session there was consensus we should initially embrace the L3DL work, and consider additional enhancements in a later follow-up charter update Look for the embedded L3DL text <new>text</new> . Thoughts, suggestions and constructive feedback on the draft#1 charter proposal is appreciated. If necessary we could setup an interim to discuss detailed nuances. **********DRAFT#1********** Charter for Working Group Data Centers have been steadily growing to commonly host tens of thousands of end points, or more, in a single network. Because of their topologies (traditional and emerging), traffic patterns, need for fast restoration, and for low human intervention, data center networks have a unique set of requirements that is resulting in the design of routing solutions specific to them. The Link-State Vector Routing (LSVR) Working Group is chartered to develop and document a hybrid routing protocol utilizing a combination of link-state and path-vector routing mechanisms <new> and the Layer-3 Discovery and Liveness (L3DL) protocol to discover IP Layer-3 attributes of links, such as neighbor IP addressing, logical link IP encapsulation abilities, and link liveness </new>. The LSVR WG will utilize existing IPv4/IPv6 transport, packet formats and error handling of BGP-4 consistent with BGP-LS NLRI encoding mechanisms (https://datatracker.ietf.org/doc/rfc7752/) to facilitate Link-State Vector (LSV) routing information distribution. An LSV is intended to be specified as a data structure comprised of link attributes, neighbor information, and other and other potential attributes that can be utilized to make routing decisions. The LSVR specification is initially focused on operation within a single datacenter (DC) as a single distribution domain, which is defined as a set of participating nodes in a single administrative domain. Routing protocol functionality defined by LSVR would be typically routing within a datacenter's underlay routing plane. The work will include coexistence considerations with BGP IPv4/IPv6 unicast address families installing and advertising routes into the same RIB. <new>The L3DL protocol is developed to discover link IP Layer-3 attributes and is focused upon discovering mutually supported layer-3 encapsulations for IP and/or MPLS interface addressing. The discovery protocol must present this data to BGP-SPF so that topology and routing tables can be build. L3DL should provide support for authenticity verification of protocol messages and provide a mechanism for Layer-2 keep-alive messaging to support session continuity, and finally support build-up for Layer-3 link liveness such as BFD.</new> The WG will consider the effects (if any) of deploying the LSVR protocol while concurrently using the same transport session as other existing BGP address families. These considerations will be documented as part of the main protocol specification. A mechanism to be able to independently deploy LSVR from other address families may be defined (as needed). The LSVR protocol is intended as a self-standing routing protocol even if using existing BGP transport mechanisms and encodings, or if sharing the same transport session with other existing BGP address families. Similar as existing routing protocols, the LSVR protocol will not internally combine the route selection mechanisms or share routing information, except through common external interaction methods in the RIB. In order to achieve the noted objective, the working group will focus on standardization of protocol functionality, defining Link-State Vectors (LSVs) and defining standard path-vector route selection utilizing the Dijkstra SPF based algorithm, BGP-4 protocol mechanics and BGP-LS NRLI encoding. The working group will provide specifications to manage routing information from other unicast routing protocols or BGP address families to common prefixes. The LSVR WG is chartered to deliver the following documents: . Specification document describing LSV with standard Dijkstra SPF route/path selection (calculation) utilizing existing BGP protocol baseline functionality and BGP-LS packet encoding formats . Specification documenting protocol extensions required to efficiently reuse BGP to distribute LSVs within an IPv4/IPv6 DC with scope to include privacy and security considerations o The impact of these extensions to the security properties of BGP will be studied and documented o New attack vectors will be explored and documented o Mitigations to any new attack vectors identified will be discussed and documented <new> . Specification documenting L3DL protocol considering usage with BGP-SPF o A base protocol documenting Layer-3 Discovery and Liveness protocol o Protocol extensions documenting Layer-3 Discovery and Liveness Signing o Protocol extension to communicate the parameters needed to exchange inter-device Upper Layer Protocol Configuration for upper-layer protocols such as the BGP family L3DL Upper-Layer Protocol Configuration </new> . Applicability Statement for the use of LSVR in the Datacenter . YANG model specification for LSVR management . YANG model specification for L3DL management The WG will closely collaborate with the idr WG. Any modifications or extension to BGP that will not be specifically constrained to be used by LSVR must be carried out in the idr WG, but may be done in this WG after agreement with all the relevant chairs and the responsible Area Directors. (revision proposal) Milestones: . Mar 2024 Applicability statement for LSVR in DCs . Mar 2024 LSV distribution using BGP transport . Mar 2024 LSVR with standard Dijkstra path selection . Dec 2024 YANG specification for LSVR . <new>Jul 2024 Layer-3 Discovery and Liveness . Jul 2024 Layer-3 Discovery and Liveness Signing . Jul 2024 L3DL Upper-Layer Protocol Configuration . Dec 2024 YANG specification for L3DL</new> -----Original Message-----
- [Lsvr] Initiating LSVR re-chartering discussion -… Gunter van de Velde (Nokia)
- Re: [Lsvr] Initiating LSVR re-chartering discussi… Greg Mirsky
- Re: [Lsvr] Initiating LSVR re-chartering discussi… Gunter van de Velde (Nokia)
- Re: [Lsvr] Initiating LSVR re-chartering discussi… Paul Congdon
- Re: [Lsvr] Initiating LSVR re-chartering discussi… Bernier, Daniel
- Re: [Lsvr] Initiating LSVR re-chartering discussi… Gunter van de Velde (Nokia)
- Re: [Lsvr] Initiating LSVR re-chartering discussi… Randy Bush
- Re: [Lsvr] Initiating LSVR re-chartering discussi… Paul Congdon
- Re: [Lsvr] Initiating LSVR re-chartering discussi… Linda Dunbar
- Re: [Lsvr] Initiating LSVR re-chartering discussi… Gunter van de Velde (Nokia)
- Re: [Lsvr] Initiating LSVR re-chartering discussi… Shihang(Vincent)
- Re: [Lsvr] Initiating LSVR re-chartering discussi… Greg Mirsky
- Re: [Lsvr] Initiating LSVR re-chartering discussi… Linda Dunbar
- Re: [Lsvr] Initiating LSVR re-chartering discussi… Ketan Talaulikar
- Re: [Lsvr] Initiating LSVR re-chartering discussi… Randy Bush
- Re: [Lsvr] Initiating LSVR re-chartering discussi… Linda Dunbar
- Re: [Lsvr] Initiating LSVR re-chartering discussi… Greg Mirsky
- Re: [Lsvr] Initiating LSVR re-chartering discussi… Ketan Talaulikar