Re: [Lsvr] Kicking off the LSVR (Link State Vector Routing) charter discussion

Derek Yeung <derek@arrcus.com> Mon, 22 January 2018 23:42 UTC

Return-Path: <derek@arrcus.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 1BDB612D855 for <lsvr@ietfa.amsl.com>; Mon, 22 Jan 2018 15:42:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netorgft1331857.onmicrosoft.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 qiXHGFMshtby for <lsvr@ietfa.amsl.com>; Mon, 22 Jan 2018 15:42:00 -0800 (PST)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0074.outbound.protection.outlook.com [104.47.33.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E9B012D850 for <Lsvr@ietf.org>; Mon, 22 Jan 2018 15:41:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=NETORGFT1331857.onmicrosoft.com; s=selector1-arrcus-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=AX8qrf6uCHFdlHiQEojp+HWLH5ehW8zOoGnumCetJ+s=; b=G8W8bE2A5fih2W57h+KFqbVKI0cPwcKZZKaI8CPvoZmkcAEeX/G+1Uj2IBE/n9uA4vYQ7DgdVyD8kL5FWVjCNRxRVHd1/67jZXpAYRUm7/MB0yhn9bWMW2eWpChlJKTeM/lyjVGrrdYG7E7pVJNLsLrtd3pMm82D81KgjOZzaq8=
Received: from CO2PR18MB0025.namprd18.prod.outlook.com (10.161.83.14) by CO2PR18MB0025.namprd18.prod.outlook.com (10.161.83.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.428.17; Mon, 22 Jan 2018 23:41:56 +0000
Received: from CO2PR18MB0025.namprd18.prod.outlook.com ([10.161.83.14]) by CO2PR18MB0025.namprd18.prod.outlook.com ([10.161.83.14]) with mapi id 15.20.0428.019; Mon, 22 Jan 2018 23:41:56 +0000
From: Derek Yeung <derek@arrcus.com>
To: "Lsvr@ietf.org" <Lsvr@ietf.org>
Thread-Topic: [Lsvr] Kicking off the LSVR (Link State Vector Routing) charter discussion
Thread-Index: AQHTk7Ph+7mNXfhTnE2i389mqeAKi6OAZHaA//+jMYA=
Date: Mon, 22 Jan 2018 23:41:56 +0000
Message-ID: <6BA96756-14E1-4BA0-A5F0-06362DA61F39@arrcus.com>
References: <CAOBQASkA3UZktiwPpFnWXbAgWHxVkbcgZSfcU6KYu06rS-oREA@mail.gmail.com> <FAA6C970-6F09-4901-8721-B3FB465FA874@cisco.com>
In-Reply-To: <FAA6C970-6F09-4901-8721-B3FB465FA874@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=derek@arrcus.com;
x-originating-ip: [75.8.210.205]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CO2PR18MB0025; 7:rfvkNX8XfdRW+zkx6XnrgaEwanBuDmLYaYMY3zpgvr0KR5UTENocYKAEjZAl/byWSNaRdrmf7uE7HZ+tyBuqK5Yhs7SwlXL/OYA5isLEZuTDbnifuhq3n0iC1H+FOPC1eIJQD14VkzSvMujZjFcoGGB6JyNUIah6L43dePW74xPQXYmPvxAzQ1DfUmJjW/SeoJioSirVp5q0ub7BtUGm97LBRyE95U6vUTPKaq2oufk0cMuczIkPUNqOQAhPGS+G
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 663e4577-2d0d-42dd-ea32-08d561f1b943
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:CO2PR18MB0025;
x-ms-traffictypediagnostic: CO2PR18MB0025:
x-microsoft-antispam-prvs: <CO2PR18MB0025E927B34346A77BF8A111CCEC0@CO2PR18MB0025.namprd18.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(192374486261705)(85827821059158)(95692535739014)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(5005006)(8121501046)(3231023)(2400081)(944501161)(93006095)(93001095)(10201501046)(3002001)(6041288)(20161123562045)(2016111802025)(20161123558120)(20161123564045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6043046)(6072148)(201708071742011); SRVR:CO2PR18MB0025; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:CO2PR18MB0025;
x-forefront-prvs: 0560A2214D
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39830400003)(396003)(346002)(39380400002)(376002)(366004)(189003)(199004)(26005)(6436002)(478600001)(53546011)(3660700001)(3280700002)(5640700003)(97736004)(6506007)(6306002)(54896002)(99286004)(6512007)(53936002)(77096007)(236005)(14454004)(229853002)(2950100002)(2351001)(7736002)(76176011)(83716003)(6486002)(3846002)(66066001)(6916009)(6116002)(102836004)(8676002)(2906002)(606006)(81166006)(81156014)(5660300001)(316002)(82746002)(105586002)(2900100001)(106356001)(966005)(68736007)(25786009)(33656002)(6246003)(36756003)(8936002)(59450400001)(86362001)(2501003)(437434002); DIR:OUT; SFP:1101; SCL:1; SRVR:CO2PR18MB0025; H:CO2PR18MB0025.namprd18.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: arrcus.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: Isz/KL+ZzgYRFlMmrBzVTz+DpBsm/eJNTZaavKEFH6Gjk3paQ33SrOcTfPx9BitkqZ8JRbDz3vhe1dP65MeINA==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_6BA9675614E14BA0A5F006362DA61F39arrcuscom_"
MIME-Version: 1.0
X-OriginatorOrg: arrcus.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 663e4577-2d0d-42dd-ea32-08d561f1b943
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jan 2018 23:41:56.4479 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 697b3529-5c2b-40cf-a019-193eb78f6820
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO2PR18MB0025
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsvr/17fX73Z7hX6y4yQI5K23p6MqsWw>
Subject: Re: [Lsvr] Kicking off the LSVR (Link State Vector Routing) charter discussion
X-BeenThere: lsvr@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 22 Jan 2018 23:42:04 -0000

I support this charter.
Looking forwards to contribute.

Thanks,
Derek

From: Lsvr <lsvr-bounces@ietf.org> on behalf of "Satya Mohanty (satyamoh)" <satyamoh@cisco.com>
Date: Monday, January 22, 2018 at 1:14 PM
To: Neeraj Malhotra <eneerajm@gmail.com>, "Lsvr@ietf.org" <Lsvr@ietf.org>
Subject: Re: [Lsvr] Kicking off the LSVR (Link State Vector Routing) charter discussion

I support this initiative.
It should be useful for dc-routing.

Thanks,
—Satya

From: Lsvr <lsvr-bounces@ietf.org<mailto:lsvr-bounces@ietf.org>> on behalf of Neeraj Malhotra <eneerajm@gmail.com<mailto:eneerajm@gmail.com>>
Date: Monday, January 22, 2018 at 10:50 AM
To: "Lsvr@ietf.org<mailto:Lsvr@ietf.org>" <Lsvr@ietf.org<mailto:Lsvr@ietf.org>>
Subject: [Lsvr] Kicking off the LSVR (Link State Vector Routing) charter discussion




Hi,



excellent start. fully support the effort and looking forward to contributing.



Thanks,

Neeraj



> On 1/10/18 5:50 AM, Van De Velde, Gunter (Nokia - BE/Antwerp) wrote:

>

> [Note: Target audience, and discussions should happen on

> lsvr@ietf.org<mailto:lsvr@ietf.org>, however "rtgwg", "idr" and "dcrouting" email lists have

> been added as the concepts originated in those working groups]

>

> Since dcrouting@ietf100, a few people have been discussing a possible WG

> charter for LSVR (Link State Vector Routing).

> Here is what we have so far.  Comments and improvements would be most

> welcome.

>

> WG page is to be setup soon.

> Subscription to LSVR mailing list:

> https://www.ietf.org/mailman/listinfo/lsvr

>

> Feedback (comments, edits, corrections, etc)  on the draft LSVR

> charter is appreciated

>

>

> ***** DRAFT CHARTER UPDATE - JAN 10 2018 *****

>   Charter: LSVR - Link State Vector Routing

>   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.  The LSVR WG will utilize

> existing the IPv4/IPv6 transport, packet formats, and error handling from

> BGP-4 (RFC4271). Additionally, the BGP-LS NLRI encoding mechanisms defined

> in RFC7752 are utilized to facilitate Link-State Vector (LSV) routing

> information distribution. An LSV is intended to be specified as a data

> structure comprised of a link identification, link attributes, neighbor

> information, cost toward neighbors, and other attributes that are defined

> for control plane function and policy-based routing decisions.

>   The LSVR specification is initially focused on operation within a

> single datacenter (DC) with preliminary focus on specifying functionality

> within a single distribution domain.  Routing protocol functionality defined

> by LSVR would be typically routing within a datacenter's underlay routing

> plane.

>   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 existing

> Dijkstra SPF based algorithm, BGP-4 protocol mechanics, and BGP-LS NRLI

> encoding.

>   For the purposes of the initial work within the LSVR WG, and until

> further specified by the WG, the following definitions apply to this

> charter.

>   - Link-State Vector - An LSV is intended to represent a data structure

> (data set) comprised of link identification, link attributes, neighbor

> information, cost towards neighbors, and other potential attributes that can

> be utilized to make routing decisions.

> - LSVR Distribution Domain - Initially scoped as a set of participating

> LSVR nodes in a single administrative domain.

>      The LSVR WG is chartered to deliver the following documents:

>   - Publish Applicability Statement for the use of LSVR in the

> Datacenter - Target Status: Informational

> - Publish specification document describing LSV with standard Dijkstra

> SPF route/path selection (calculation) utilizing existing BGP protocol

> baseline functionality and BGP-LS packet encoding formats - Target:

> Standards Track (Based on draft draft-keyupate-idr-bgp-spf)

> - Publish 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 - - Target:

> Standards Track

> - Publish YANG model specification for LSVR - - Target: Standards

> Track

>   LSVR Milestones:

>   - Applicability statement for LSVR in DCs: March 2019

> - LSVR with standard Dijkstra path selection: March 2019

> - LSV distribution using BGP transport: March 2019

> - YANG specification for LSRV: July 2019

>

> _______________________________________________

> rtgwg mailing list

> rtgwg@ietf.org<mailto:rtgwg@ietf.org>

> https://www.ietf.org/mailman/listinfo/rtgwg

>



_______________________________________________

Lsvr



References:



   - Re: [Lsvr] Kicking off the LSVR (Link State Vector Routing) charter

   discussion

   <https://mailarchive.ietf.org/arch/msg/lsvr/ejhm_8H4TD94810i-_QC6yI1bxM><https://mailarchive.ietf.org/arch/msg/lsvr/ejhm_8H4TD94810i-_QC6yI1bxM%3E>

   Victor Kuarsingh <victor@jvknet.com><mailto:victor@jvknet.com&gt>; <victor@jvknet.com&gt><mailto:victor@jvknet.com&amp;gt&gt>;;