Re: [Isis-wg] Link-State Routing WG charter

Stewart Bryant <stewart.bryant@gmail.com> Wed, 24 January 2018 17:32 UTC

Return-Path: <stewart.bryant@gmail.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20CD51270AB; Wed, 24 Jan 2018 09:32:16 -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 7fDirerYNcuM; Wed, 24 Jan 2018 09:32:13 -0800 (PST)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (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 919521270A0; Wed, 24 Jan 2018 09:32:13 -0800 (PST)
Received: by mail-wm0-x229.google.com with SMTP id b21so10118199wme.4; Wed, 24 Jan 2018 09:32:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=GB+OrjtQGwS2wW7tX7OS/cp5BlNTzkV7Z7jrlGcnGaA=; b=ZHKG0ACgOf9J1/zQIVAfU939SGtcryYGzNDG8Omnt3SW40UW6QBr8gS8sbafaf7L0/ PKrhNEWAEN17iTzZafWRnpewT+XhiEY+nIwV4QuIYkIimySAfLqw7W5gdw/p+zH6kTbc LU6mX5XBKjC62zTqVpLz0KuuLRtuda3rnol4BwijR1QQwiKC18bH264JTAg9YNzYJOqa Y5/s9vvMHS0QpEq+3XqSxGmbcq1DvBcGVD+GggbWq5t/AmMR3bOsSKdypPkmKVPM5QXO MD+RFZ2UqjDxQ0FRCZv0issHpCFMgZ2iBsD8Wk9J3xNQIeDPF1IFRauyFZJe7XsUlI3P JVDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=GB+OrjtQGwS2wW7tX7OS/cp5BlNTzkV7Z7jrlGcnGaA=; b=TUujaZ7mJ2+MA4a5NeJYYjI74wq7iGqejLBc7Q1G7cAr21g0XCnMBp+p8du/Xze5G3 h04AOi7qmKsq15Hlw5QMox16ZwtStU+8abIZzL9BC4Or9wmTCX/0Ke43ovPZJazzYdjS F/e/71hXKKdqjCooXNmTlGAcFu2LK8+Uv1tPNYwwRkk0KtkY9oDszNuwvyyNp1TwTQf/ G20Hd0oWacVDdoVEHzytbLw1wyGLPLPzJ+UtFwKgnL2cncTkiaaO308tkIyWQsupetA+ 5ExO5NzSybWnA3bnkP0RtSfCmWCApH7dhEahiLcs6Klt+1MIYvey3qUklKN6C4b85MqC 8zew==
X-Gm-Message-State: AKwxytd/haTq+GqYkB+TOc5zM2m7j9JcSSBOBN6UQHw0eHKmRcIlg+K4 qP37zhJfG8Bo4kAXacDRD99Gn8S/
X-Google-Smtp-Source: AH8x225dTseMgzyE3c4gd3e6IRbxgHwfi8WQwTIgpIvB/d9FRtmkMZ4Erwo8SQYoduaT3E84ilQgXA==
X-Received: by 10.28.131.210 with SMTP id f201mr5714182wmd.117.1516815131765; Wed, 24 Jan 2018 09:32:11 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id r6sm2912002wrg.89.2018.01.24.09.32.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 Jan 2018 09:32:11 -0800 (PST)
To: Alia Atlas <akatlas@gmail.com>, isis-wg@ietf.org, OSPF List <ospf@ietf.org>
References: <CAG4d1rfR5Y85T_wNSVXB0WL4C8THyAkgevr6DyH1xcO=R+sOVQ@mail.gmail.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <0ae3753a-9037-9199-e61d-b4e15089be73@gmail.com>
Date: Wed, 24 Jan 2018 17:32:07 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <CAG4d1rfR5Y85T_wNSVXB0WL4C8THyAkgevr6DyH1xcO=R+sOVQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------22EE7C0E3DC55E23F55456A5"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/isis-wg/pRjtdCqLdRubCcDHHLryf10RGC0>
Subject: Re: [Isis-wg] Link-State Routing WG charter
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jan 2018 17:32:16 -0000

Alia,

I think that this merger is long overdue, and hopefully it will help new 
features to be written in an aligned way.

I think the remit to perform general maintenance should slightly 
clarified since the way the charter is written they look like they are 
at a lower priority than the enumerated list.

I would have thought that "LSR can coordinate with CCAMP and BIER on 
their extensions " should have been more directive.

- Stewart

On 24/01/2018 17:18, Alia Atlas wrote:
> Here is the proposed charter for the LSR working group
> that will be created from the SPF and ISIS working groups.
>
> This is scheduled for internal review for the IESG telechat on February 8.
>
> https://datatracker.ietf.org/doc/charter-ietf-lsr/
>
> The Link-State Routing (LSR) Working Group is chartered to document 
> current protocol implementation practices and improvements, protocol 
> usage scenarios, maintenance and extensions of link-state routing 
> interior gateway protocols (IGPs) with a focus on IS-IS, OSPFv2, and 
> OSPFv3.  The LSR Working Group is formed by merging the isis and ospf 
> WGs and will take on all their existing adopted work at the time of 
> chartering.
>
> IS-IS is an IGP specified and standardized by ISO through ISO 
> 10589:2002 and additional RFC standards with extensions to support IP 
> that has been deployed in the Internet for decades.  For the IS-IS 
> protocol, LSR’s work is focused on IP routing, currently based on the 
> agreement in RFC 3563 with ISO/JTC1/SC6. The LSR WG will interact with 
> other standards bodies that have responsible for standardizing IS-IS.
>
> OSPFv2 [RFC 2328 and extensions], is an IGP that has been deployed in 
> the Internet for decades. OSPFv3 [RFC5340 and extensions] provides 
> OSPF for IPv6 and IPv4 [RFC5838] which can be delivered over IPv6 or 
> IPv4 [RFC 7949].
>
> The LSR Working Group will generally manage its specific work items by 
> milestones agreed with the responsible Area Director.
>
> The following topics are expected to be an initial focus:
> 1) Improving OSPF support for IPv6 and extensions using OSPFv3 LSA 
> Extendibility.
> 2) Extensions needed for Segment Routing and associated architectural 
> changes
> 3) YANG models for IS-IS, OSPFv2, and OSPFv3 and extensions
> 4) Extensions for source-destination routing 
> [draft-ietf-rtgwg-dst-src-routing]
> 5) Potentially, extensions to better support specific network 
> topologies such as
> ones commonly used in data centers.
>
> The Link-State Routing (LSR) Working Group will coordinate with other 
> working groups, such as RTGWG, SPRING, MPLS, TEAS, V6OPS, and 6MAN, to 
> understand the need for extensions and to confirm that the planned 
> work meets the needs.  LSR can coordinate with CCAMP and BIER on their 
> extensions to the LSR IGPs as useful.  LSR may coordinate with other 
> WGs as needed.
>
> Regards,
> Alia
>
>
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www.ietf.org/mailman/listinfo/isis-wg