Re: [v6ops] Fwd: [Lsvr] New Non-WG Mailing List: LSVR- Link State Vector Routing

"Van De Velde, Gunter (Nokia - BE/Antwerp)" <> Fri, 12 January 2018 15:04 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7CDF8127275 for <>; Fri, 12 Jan 2018 07:04:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.92
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 7Fkl-1ER4H2W for <>; Fri, 12 Jan 2018 07:04:32 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9D0AC1270A3 for <>; Fri, 12 Jan 2018 07:04:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1-nokia-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=lEpRLpdoRbKMYIAsKngt/rPdl8KxwnXHcSdMwAJVfow=; b=E1Y9Z69LRSu5q97MFnMDYGOUQIeO44FxPmxepBAiTcQuABgJdmOEcwNwUUQ9dDOVCF37C6lzX2ynkYQhDUpPh49FBpwdvs4HbztMGH56A9GYWG+6rQYwFDUA7IKoAJTrNgtblcQKTtWk72kMaxgIgxAHtjvZighVHJm1IYyxQbg=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.407.1; Fri, 12 Jan 2018 15:04:28 +0000
Received: from ([fe80::645d:a0f3:c36b:9aa3]) by ([fe80::645d:a0f3:c36b:9aa3%14]) with mapi id 15.20.0407.009; Fri, 12 Jan 2018 15:04:28 +0000
From: "Van De Velde, Gunter (Nokia - BE/Antwerp)" <>
To: Fred Baker <>, " WG" <>
Thread-Topic: [v6ops] Fwd: [Lsvr] New Non-WG Mailing List: LSVR- Link State Vector Routing
Thread-Index: AQHTi7XkbZDeCOpi+EinFsc485SpjKNwVW7g
Date: Fri, 12 Jan 2018 15:04:28 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
authentication-results: spf=none (sender IP is );
x-originating-ip: [2a02:1810:4d67:a00:7c0a:3264:9d6d:66ee]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM5PR0701MB1746; 7:RKfRXas0ll7NFPePl7BZegfevQqbVZUGHjLIVki5St/NN09ZY7t4BUkEFs1gBnQ/BupXeV43CsW2WJoykhYC/2x7yDIBr+v5E8oeYHMJb1N9kHuWKMbcRM1L4+P25blvDV+fukaVdJjrJb7UNcw1wbUK4uvemaH0LxRSwuR5mAyZuAMXh7lZ53JJP7JruKJ7u9SNjdyGt464H4lsUUMivL8/F7dMbDWePbkvCcr7r2M5azN5EdxMiQ4IrRvY/2+8
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: f0466ab1-104a-473e-17df-08d559cdc72f
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(48565401081)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7193020); SRVR:AM5PR0701MB1746;
x-ms-traffictypediagnostic: AM5PR0701MB1746:
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:(28532068793085)(192374486261705)(85827821059158)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040470)(2401047)(8121501046)(5005006)(10201501046)(93006095)(93001095)(3231023)(11241501184)(806099)(944501075)(3002001)(6055026)(6041268)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123558120)(20161123562045)(6072148)(201708071742011); SRVR:AM5PR0701MB1746; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:AM5PR0701MB1746;
x-forefront-prvs: 0550778858
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(346002)(366004)(39860400002)(39380400002)(396003)(189003)(199004)(33656002)(2900100001)(606006)(105586002)(106356001)(81156014)(25786009)(110136005)(2950100002)(2906002)(790700001)(6116002)(53936002)(5250100002)(81166006)(14454004)(8676002)(53546011)(6506007)(68736007)(316002)(8936002)(3660700001)(966005)(478600001)(3280700002)(97736004)(39060400002)(236005)(9686003)(102836004)(54896002)(6306002)(55016002)(86362001)(5660300001)(74316002)(7736002)(6436002)(99286004)(19609705001)(59450400001)(6246003)(76176011)(7696005)(229853002)(437434002)(223123001); DIR:OUT; SFP:1102; SCL:1; SRVR:AM5PR0701MB1746;; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None ( does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 3pLMc+oTSvhbwQIHi6LHSevqEXAHztCC3ljbpw+PG+huHFisCqH1gmUowGo/tlk0dZ4QmKxTRnfZKkdURglPQ92itMhsTuNCOmW8TdK9yb08NM+6D5j+0yYcMnbdw2Qz
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM5PR0701MB28366002452B3336E90911B5E0170AM5PR0701MB2836_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: f0466ab1-104a-473e-17df-08d559cdc72f
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jan 2018 15:04:28.6775 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB1746
Archived-At: <>
Subject: Re: [v6ops] Fwd: [Lsvr] New Non-WG Mailing List: LSVR- Link State Vector Routing
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 12 Jan 2018 15:04:35 -0000

Thanks Fred.

Currently the charter is under discussion on LSVR email list. The proposed draft charter:

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

><>, 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:



> 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

From: v6ops [] On Behalf Of Fred Baker
Sent: Friday, January 12, 2018 15:59
To: WG <>
Subject: [v6ops] Fwd: [Lsvr] New Non-WG Mailing List: LSVR- Link State Vector Routing

A few weeks ago, I mentioned the chartering of the rift working group on this list. A parallel group has started the chartering exercise, working n BGP SPF. You may be interested to join it.

Begin forwarded message:

From: IETF Secretariat <<>>
Subject: [Lsvr] New Non-WG Mailing List: LSVR- Link State Vector Routing
Date: December 13, 2017 at 1:30:55 PM PST
To: "IETF Announcement List" <<>>

A new IETF non-working group email list has been created.

List address:<>
To subscribe:

This list is for discussion related to architectural, standardization and manageability aspects for Link State Vector Routing.

For additional information, please contact the list administrators.

Lsvr mailing list<>