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

Pushpasis Sarkar <pushpasis.ietf@gmail.com> Thu, 18 January 2018 17:22 UTC

Return-Path: <pushpasis.ietf@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 826B4129516 for <lsvr@ietfa.amsl.com>; Thu, 18 Jan 2018 09:22:12 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 6eOSZzXWfg8Y for <lsvr@ietfa.amsl.com>; Thu, 18 Jan 2018 09:22:10 -0800 (PST)
Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (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 AAB2812711D for <lsvr@ietf.org>; Thu, 18 Jan 2018 09:21:56 -0800 (PST)
Received: by mail-it0-x230.google.com with SMTP id w14so13783280itc.3 for <lsvr@ietf.org>; Thu, 18 Jan 2018 09:21:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=sS6MsAwUnQKfgq7cW9gBfxLkjyUnnZrXxR8VoQWC80I=; b=EJc8eO7c1AS/hp3+O9zxyjtE0tkhS2on61j9IG3nhNh8LHiraUEUzI6KQoarU6Coap RNlbqBcOphsaQ4vQkaFUQaFgmi8ANlUiRk9byh774Oh7ag8j2qr2EKWiaeDcv/N1Jy6z xQWscMxPTjMntWCp+fHk54W0EzyJss5ER2gltmkRuzlF29XNwrGYAHWAF/y4r4EmUdxi HbQdkgza83/BA4bTNaO++8kaICL5WFLpN+3QmXOmpeTZ4D19NOMAN4C4ql+GZ+nDl0Ek 38pkYb/M6uh98hF5wAKtAZhxnxEbvG2YLFOgu0byf9IAfpUvMYTX1x9jZQLL9c8MvsJL isbg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=sS6MsAwUnQKfgq7cW9gBfxLkjyUnnZrXxR8VoQWC80I=; b=CsPy2aI6B/JpN2XUWcp5wZnhyQPu6CxHZ3xw6+dVHDTRcTX12mOtSlDI22kjHQK9vJ hKOEC/omgxNobI8qbwvvSAgXcrotJjRQip2nDkPVliESxkudw3TKsRJZxmdsXeXET+3q 4qLs1p3azVRm78DaXONGmQIyeEEpAQwVNWAmDPekuPPm9RDn7DN/2eT0/wOWcjYiYtWQ 7xNDsqIYO0xyW0gbiOw+SP2OCWCI+H4L7JgZqY6P2N0VFyFKXrRbwuqjwMJWExvfCcHd b8sZZY8mZ5AAjj9MJ5Mx87vb1i/WMzqaxpDyhfPyw90+J29vAJP/8fVABVWkAbMEuBce zlaQ==
X-Gm-Message-State: AKwxytelEna6Sn8yDnRH01UhAVwR02IJgXJE31zKwJSH0471bzoHRzci /knCQaSRxkrnhMHkCmK4ei3EIeloxqtvNqAIhot9nw==
X-Google-Smtp-Source: ACJfBot8fFsdYagUY0xEbKdLawztWlPgxUdAq13lhlPTAqW4WFZe1aZsWKqPTOYNQ1kDoWn8ThVyrNN3FoVjMeUlenc=
X-Received: by 10.36.52.8 with SMTP id z8mr19155753itz.130.1516296115497; Thu, 18 Jan 2018 09:21:55 -0800 (PST)
MIME-Version: 1.0
Received: by 10.2.159.26 with HTTP; Thu, 18 Jan 2018 09:21:55 -0800 (PST)
From: Pushpasis Sarkar <pushpasis.ietf@gmail.com>
Date: Thu, 18 Jan 2018 22:51:55 +0530
Message-ID: <CAEFuwkhz0ze84wmSD82hWNogJA8rxVgV7NLedqeP2gDa1Gi0Pw@mail.gmail.com>
To: lsvr@ietf.org
Content-Type: multipart/alternative; boundary="001a114752ce56cf8b0563103310"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsvr/3_AXicjtLLSH-u9V_LVwWSar9a8>
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: Thu, 18 Jan 2018 17:22:16 -0000

Hi All,

I went through the charter details, and it seems to be in a quite good
state to get things started. Hoping we can accommodate some changes
here and there (if at all needed).

Looking forward to contributing more on this soon.

Thanks and regards,

-Pushpasis


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

References:

   - Re: [Lsvr] Kicking off the LSVR (Link State Vector Routing) charter
   discussion
   <https://mailarchive.ietf.org/arch/msg/lsvr/ejhm_8H4TD94810i-_QC6yI1bxM>
   Victor Kuarsingh <victor@jvknet.com>