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

Mahesh Jethanandani <mjethanandani@gmail.com> Tue, 23 January 2018 02:19 UTC

Return-Path: <mjethanandani@gmail.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 5391512D889 for <lsvr@ietfa.amsl.com>; Mon, 22 Jan 2018 18:19:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 jcH6qwrE3WOI for <lsvr@ietfa.amsl.com>; Mon, 22 Jan 2018 18:19:20 -0800 (PST)
Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFC5212D88B for <lsvr@ietf.org>; Mon, 22 Jan 2018 18:19:19 -0800 (PST)
Received: by mail-it0-x234.google.com with SMTP id 68so12043134ite.4 for <lsvr@ietf.org>; Mon, 22 Jan 2018 18:19:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=6QdwPMN2s/v4R/kP0GTsp4EKKokQ87KKJoztCmT4VpY=; b=o9CLf7smHLwCVYB7T+fZcY45ve/nuo8Q+09rWExvQfShtZK1dNZLGIfIsw4ML9ITPY pxm1PqrD1D/7bFcBHW+yUOTzXdfaRPEMijLsbGTpo0YB2duSbsB9VsmqCMz9g2xMWZA+ taWBds7sVAAd4S3gisItVGye5wJZRccDJgfoQXWzRX2QcU/rk8hHRQcXW/PlRl86qDlH wVWUSy1yC4X6KZfdF/+4uMq97+/zhly3VgXY/xlV5MJ8GwDslIrPG1eMXPryFFEApuoc cVBsShhBOVOeHUZ4ZcX+FaO7wWGZeNa3ur7eV36mnMG+2HM+a4PqRQEFtvyekSuc6UhM yWPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=6QdwPMN2s/v4R/kP0GTsp4EKKokQ87KKJoztCmT4VpY=; b=hXzIgc/uxZZ+WLI6G46ZpyupFvrdVkTF2Hd3mpNTSQswUJuOpQIRzQdg2uqkD66NYP 9G1MeEVweNYw/HRyjob1adOR4eylC2J7m10tcT+W78ap5O+w/xsb3K6J1wu6QdMKNxf6 ObUojhf9nbB5HKRv4eqsRi5Fs4owkLmwbdIOmd47IQzNljuayx2/CPurtNEIhot9WVDE hU52J9YitB+foBMqdJlAhjmYu7RxrJ1ozFKsWnSfTSHemEm3VOQGjGdak75stfOjiENZ 98AOMOjvbvpZIFrqvArhGCFYbKjOovD0XwdgvQ7xRE8Wwgba+RcCnwANqef4pAVl0nT2 N5tw==
X-Gm-Message-State: AKwxytdsybsxoQPZ1GqeUhsu74yeMK9CiRatv8gDYMwO/VulXxUBIykF 6OM0bsl1OOS4dm2xY2DXZX9xQ0s/
X-Google-Smtp-Source: AH8x224aJDkL+Tfr2RRSRF29hHzclrZzgzMHdS8Dxa+/4zzi4NYcZL7NnAyFbMjsm7K/eF2Wc856Sw==
X-Received: by 10.36.98.136 with SMTP id d130mr1563261itc.54.1516673958912; Mon, 22 Jan 2018 18:19:18 -0800 (PST)
Received: from mahesh-m-m8d1.attlocal.net ([2600:1700:edb0:8fd0:442:cec5:ad94:ce61]) by smtp.gmail.com with ESMTPSA id 137sm8871027ioo.22.2018.01.22.18.19.17 for <lsvr@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 22 Jan 2018 18:19:18 -0800 (PST)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Mon, 22 Jan 2018 18:19:16 -0800
References: <AM5PR0701MB2836FFBB9A9F6C3D7C3C7122E0110@AM5PR0701MB2836.eurprd07.prod.outlook.com> <f590456ccee0498eadbb5fa4e4e048cc@XCH-ALN-014.cisco.com>
To: "lsvr@ietf.org" <lsvr@ietf.org>
In-Reply-To: <f590456ccee0498eadbb5fa4e4e048cc@XCH-ALN-014.cisco.com>
Message-Id: <DB175B8E-8A90-48DA-A0A9-7459FFE2CF2C@gmail.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsvr/PTDVOcup7pR49ZSegbVliMEtpcg>
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: Tue, 23 Jan 2018 02:19:22 -0000

Charter looks good. Looking forward to discussion within the group.

> 
> -----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
> 
> _______________________________________________
> Lsvr mailing list
> Lsvr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsvr

Mahesh Jethanandani
mjethanandani@gmail.com