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

Jacob Uecker <juecker.ietf@gmail.com> Wed, 24 January 2018 17:01 UTC

Return-Path: <juecker.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 AFFB812708C for <lsvr@ietfa.amsl.com>; Wed, 24 Jan 2018 09:01:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, 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 xvsKU7-Tkqzg for <lsvr@ietfa.amsl.com>; Wed, 24 Jan 2018 09:01:46 -0800 (PST)
Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::22d]) (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 7F95112DA68 for <lsvr@ietf.org>; Wed, 24 Jan 2018 09:01:46 -0800 (PST)
Received: by mail-qt0-x22d.google.com with SMTP id d54so12088127qtd.4 for <lsvr@ietf.org>; Wed, 24 Jan 2018 09:01:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=xLpAvhk24rCLUetVMj1jjdCgGYwum8hsLSMVbx5JIzg=; b=TXsgK/uhFZulZKa8HtxFrXFjTsBjUqkKLfMnSCy55wIRRRvewkCe8tHA+S5V84In9p v8p+zpJTty9+zZplTJ5ACv7bXJtkqbx+8gUas4GXqagl8gqMZRhjJ7RNP0E7ss7O5Ob/ lgiU+9QLcYZAzCbJ/2XJyc42Ap7LWTTONTVhtAfRNqOuC2uc9CSTB18rFTbBkRgI7IW0 /JOYDj0GoLhkkJOJSQMIgr6ubC8JUZ63uvtpzUJ2JzOtkcAtQSCqbzs6aNlds4N5Cp0z Si8s89bEnsjiG9bcMkuKObXt0y0hP+FsFleYVgLdddHPhl6nWCU4NX4LlK6hE5OZgP2W sEQQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=xLpAvhk24rCLUetVMj1jjdCgGYwum8hsLSMVbx5JIzg=; b=WN8yUiQaUNZdXdnPdYU1hbwQjOw4gryGck+mCHwc6vxwiX6NFviEcqYsmN+om/rZT3 Bxw3JRT7/ZpR9wYA8546X/+IyUinlwn6Ccqf9GMt92K2C1k5HcBvBye4XV77bqT3wS9h /MJDEQak6t1hd+fqFF9K2lXUbfTCiKJt0EuWEW1iEvwTb5di5/WGxvoi5edIprP/3EEK R8bjGHsb8zhYhrwdzJfdxq8Z0f9DJBp3OHah4dKKbSBBmVBNxAP75r6P4rNzTURsf34r gURV3Jx5CIBKkRCmk7Slw90sXHmSzWWissPUoH78fx0jIm/Psyj4QONC4J17Mi30qyAq JKVA==
X-Gm-Message-State: AKwxytdPvyj90XwHSRfn2gFu9WRLiuwM5HbEKEgsPb8T4EujG7WibXHh LPthnnsr0oL9UjnfMWkcc3hvVEWg
X-Google-Smtp-Source: AH8x227qOyVR7RJBJS6b3WEogLL2labSYO6RI14qFpbngiOfkX9zVScq8KyfuSuqlxAxdU8uCg4ldQ==
X-Received: by 10.55.169.140 with SMTP id s134mr10660022qke.39.1516813305323; Wed, 24 Jan 2018 09:01:45 -0800 (PST)
Received: from ?IPv6:2600:8801:880:d03:a1f7:f4e4:d797:2ccb? ([2600:8801:880:d03:a1f7:f4e4:d797:2ccb]) by smtp.gmail.com with ESMTPSA id u9sm2473645qtj.80.2018.01.24.09.01.44 for <lsvr@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 Jan 2018 09:01:44 -0800 (PST)
From: Jacob Uecker <juecker.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_EF638900-1E85-4818-BAE3-25B2E5D0F95D"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 24 Jan 2018 09:01:42 -0800
References: <CAEFuwkhz0ze84wmSD82hWNogJA8rxVgV7NLedqeP2gDa1Gi0Pw@mail.gmail.com>
To: lsvr@ietf.org
In-Reply-To: <CAEFuwkhz0ze84wmSD82hWNogJA8rxVgV7NLedqeP2gDa1Gi0Pw@mail.gmail.com>
Message-Id: <5A61AA43-8C1F-48AB-A984-817FBE1A0419@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsvr/ERPWaz9eGxmP9xN_LFe6dJWFYA0>
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: Wed, 24 Jan 2018 17:01:50 -0000

I’m looking forwarding to participating - particularly from the operations perspective. 

The charter looks good.

-Jacob


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