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

I'll participate.

Some considerations:
Should  LSVR introduce a grouping in the way that OSPF has areas and ISIS has levels?
If so, should the LSVR area border router terminate links from multiple areas (the IGP way) or use a special link to connect to adjoining areas (like an ASBR in BGP)?

Should LSVR routes be downloaded into RIB separately from traditional BGP routes?
If so, then they will compete for best path on an equal footing with other protocols when being redistributed into traditional BGP.
If not, then traditional BGP can import an LSVR path and an IGP path for the same prefix.

The sequence number TLV seems overly complex to me. I can appreciate that a speaker can receive multiple copies of a single link state from multiple neighbors. If they are different, then it must be a transient condition. In steady state, all copies should be identical, in contrast to traditional BGP routes. During the transient, what's wrong with choosing the most recently received copy?

As already mentioned, BGP-LS could run over a different session than traditional BGP. This would prevent bulk data in one session from delaying data in the other session. Also, it would allow one session to be reset without resetting the other one. Session resets occur at certain configuration changes (e.g. enabling the address family) and to recover from certain errors.

Thanks,
Jakob

-----Original Message-----
From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Van De Velde, Gunter (Nokia - BE/Antwerp)
Sent: Wednesday, January 10, 2018 2:51 AM
To: Lsvr@ietf.org
Cc: idr@ietf.org; dcrouting@ietf.org; Victor Kuarsingh <victor.kuarsingh@oracle.com>; Keyur Patel <keyur@arrcus.com>; Van De Velde, Gunter (Nokia - BE/Antwerp) <gunter.van_de_velde@nokia.com>; Shawn Zandi <szandi@linkedin.com>; rtgwg@ietf.org
Subject: Kicking off the LSVR (Link State Vector Routing) charter discussion

[Note: Target audience, and discussions should happen on 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
https://www.ietf.org/mailman/listinfo/rtgwg