Re: [Lsvr] Kicking off the LSVR (Link State Vector Routing) charter discussion
Jeff Tantsura <jefftant.ietf@gmail.com> Mon, 22 January 2018 23:51 UTC
Return-Path: <jefftant.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 54C2F12D7F3 for <lsvr@ietfa.amsl.com>; Mon, 22 Jan 2018 15:51:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, MIME_QP_LONG_LINE=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 rzkEBu9UYRgJ for <lsvr@ietfa.amsl.com>; Mon, 22 Jan 2018 15:51:57 -0800 (PST)
Received: from mail-yb0-x230.google.com (mail-yb0-x230.google.com [IPv6:2607:f8b0:4002:c09::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 1101812D82D for <Lsvr@ietf.org>; Mon, 22 Jan 2018 15:51:57 -0800 (PST)
Received: by mail-yb0-x230.google.com with SMTP id h9so4015842ybg.10 for <Lsvr@ietf.org>; Mon, 22 Jan 2018 15:51:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=user-agent:date:subject:from:to:message-id:thread-topic:references :in-reply-to:mime-version; bh=4k5eB07s40jPh5ZeSJmM8aNlsnSc4pm/aKsvR5V3J0Y=; b=qUnULfoD7FWzhyRkqBKeZ5TCsb8wV8SE/eqXP32CnSEaaSBLMsHzOzpXvzW4wZwN1L VFrqOlZr2PJiTXtG4/ZxTc0qtfdh7qLLbku+e6RRQqji2JAOb+xtdv473kHX4npMnnIj WdNVt8+zhodZM4Tj78zKmhydVrOycaeO6tZJ7OAYarWR3+u7DmLCRrXWSWX2KBVGV2c8 D244M+5BbaHB+PNlOZJeXaIHpTPaEULrSqYSLO06/uDJ5Jjk91q1gTJzfkcSOFgjwJbY 6g6BLonVOFSGwm6wUAISdIbzxZ0iI7E/SOjLGVzk545GRB1T+rPz0ltycI19Nidmtk/0 7vPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:message-id :thread-topic:references:in-reply-to:mime-version; bh=4k5eB07s40jPh5ZeSJmM8aNlsnSc4pm/aKsvR5V3J0Y=; b=fo3GVSoKfnzytpjsZfxZJx1PM68JTF1jgf82Ab51nCbQDxaJA9mu6TJBA0KOyoG+Vb AISqjgE/SMgMtIOJy3Hn/ZtjPj2L0+xt8td+ptwUBJtMwfGhm5PWhA1+pq1wLnkPf2pY O8BCKhThJQylyPhdwajqeMg6v5k2gmhWUyY/4ehzYCmOeMAGd5NftHNgfSOQXAV284Gv PWawiI7yNOxNZbTWl1ZsKjY/O3sSdbCLKslRi6O4jFS+MtG7h3sGfvuQl+3VqLatALYn rA9fJ6dyIhOisNMbu4ib6ZzVyiB+nVbdcYvhKnF2DNpa6mTA8QEids4SmO3L1c+e1m0M 1JhQ==
X-Gm-Message-State: AKwxytfkJqRAvFTMUM6dRDsDLAk5J84lzH8j1X9A0h/BDul4XeGoEKfe Qz7aSh/B0nC0iwA8K7SyL6QcpA==
X-Google-Smtp-Source: AH8x2246MYqJn2jByqesSeYhXT4rgmRQF20gjrKyAhcJR9TcCV+8USI0bU7Oi0ajCjV6ew7vAGnemA==
X-Received: by 10.129.122.73 with SMTP id v70mr564056ywc.156.1516665115933; Mon, 22 Jan 2018 15:51:55 -0800 (PST)
Received: from [135.227.239.108] ([66.201.62.254]) by smtp.gmail.com with ESMTPSA id o77sm6773358ywd.97.2018.01.22.15.51.51 for <Lsvr@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 22 Jan 2018 15:51:55 -0800 (PST)
User-Agent: Microsoft-MacOutlook/f.27.0.171010
Date: Mon, 22 Jan 2018 15:51:49 -0800
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: "Lsvr@ietf.org" <Lsvr@ietf.org>
Message-ID: <DE4958EF-CDAF-4274-BEE0-01135FE7833A@gmail.com>
Thread-Topic: [Lsvr] Kicking off the LSVR (Link State Vector Routing) charter discussion
References: <CAOBQASkA3UZktiwPpFnWXbAgWHxVkbcgZSfcU6KYu06rS-oREA@mail.gmail.com> <FAA6C970-6F09-4901-8721-B3FB465FA874@cisco.com> <6BA96756-14E1-4BA0-A5F0-06362DA61F39@arrcus.com>
In-Reply-To: <6BA96756-14E1-4BA0-A5F0-06362DA61F39@arrcus.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3599481112_1307639284"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsvr/XiYVZa6ZcT81fkK9olVd6dN8g8Q>
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: Mon, 22 Jan 2018 23:51:59 -0000
Charter looks good to begin with. Cheers, Jeff > 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>; <victor@jvknet.com>>;; _______________________________________________ Lsvr mailing list Lsvr@ietf.org https://www.ietf.org/mailman/listinfo/lsvr
- [Lsvr] Kicking off the LSVR (Link State Vector Ro… Neeraj Malhotra
- Re: [Lsvr] Kicking off the LSVR (Link State Vecto… Satya Mohanty (satyamoh)
- Re: [Lsvr] Kicking off the LSVR (Link State Vecto… Derek Yeung
- Re: [Lsvr] Kicking off the LSVR (Link State Vecto… Jeff Tantsura
- Re: [Lsvr] Kicking off the LSVR (Link State Vecto… Bocci, Matthew (Nokia - GB)
- Re: [Lsvr] Kicking off the LSVR (Link State Vecto… Rabadan, Jorge (Nokia - US/Mountain View)
- Re: [Lsvr] [Idr] Kicking off the LSVR (Link State… Serpil Bayraktar (serpil)
- Re: [Lsvr] [Idr] Kicking off the LSVR (Link State… Padma Pillay-Esnault
- Re: [Lsvr] [Idr] 回复: Kicking off the LSVR (Link S… Keyur Patel