early proposed charter for the Link-State Routing WG

Alia Atlas <akatlas@gmail.com> Tue, 23 January 2018 17:22 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DECD9127137; Tue, 23 Jan 2018 09:22:10 -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 GtgUOt5b2zRa; Tue, 23 Jan 2018 09:22:09 -0800 (PST)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::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 26C96127275; Tue, 23 Jan 2018 09:22:09 -0800 (PST)
Received: by mail-oi0-x22d.google.com with SMTP id w135so876958oie.3; Tue, 23 Jan 2018 09:22:09 -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:cc; bh=KTmmgmxKcIyvFT3NBbAkMPSJJDVfESm7IYtUbcoCWdw=; b=ApqI2naGyYPBTgAtsn+OyUVZ3hkIiu+AQ+6PHT63ulC0JAmTNThqfE2GegvtupVZKN ETS5g5HnwcIazuKlCGX5ff7fzUNkopGkjkpY2iZRjDXII+6f8FDjKrMHZMSDdLecNgVb FsUtOniIR+I/MwxUdTQ55DZeooUT1qfW8naLPjsghlvqPGQAX124nVbsDaTln4MWC6Te 8mS7XrOemNnzIDZcrVaS/dyyHk/NvdB2EAIjQ6J3YmxqFTWMyUFZtdZdeKCRkFUR6ifC l8ygQcf/JGEfLM3zlugwaI/uRKTKkL8O+3ktSKfSXO4xUkx77xMslsatZfnbzS0pMsHu SHSA==
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:cc; bh=KTmmgmxKcIyvFT3NBbAkMPSJJDVfESm7IYtUbcoCWdw=; b=AH7k98Tnu+/hBMhFHerrnsVAvHC/dP7iizXPbW97zLJGxnZ6GdQ+1v5vsztVLGWQq/ xPEjBCAkOKUcCqrtVv/H65vF1npTvVgYxaqAr3zboPZUMxqJE8ZxbyHss064pLNqK77x 27cKTigI5hyYDW4dYt2g/u6uVJJcm0MPNKFGE1SzNO4MKJEEEwzvzUmbICyYU1xAk+/B JZ9AHbeTrHzov64xfpVGuL7BObzJczGGObNehwApAzaloZ1wDZuK3MIDSTGTD2WlfMnU /Sgk639sHbqgWtnFn6ohlHOlu3m5P6OOB0Vw3wZtMN+CF+v8XqeTGoMfA3qzffk2W2ya mX9w==
X-Gm-Message-State: AKwxytcN30Shwkmc1lLvkNMpQzGb9JAx7DU15m8/Y+zeOGprBdB6MkAX JN9h61brPEzmveEb6mkWC3w5PPt5bv5y1SmmICfwYw==
X-Google-Smtp-Source: AH8x2276/w30RkrEP8K0zQ4iPaSK9GuOV0ILlsHjivxX3cfxoQb11TsoHZpfPizNWtuDvOdCQI9kCTjmQNndk9Jn8Zc=
X-Received: by 10.202.75.15 with SMTP id y15mr6274259oia.5.1516728127845; Tue, 23 Jan 2018 09:22:07 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.21.103 with HTTP; Tue, 23 Jan 2018 09:22:05 -0800 (PST)
From: Alia Atlas <akatlas@gmail.com>
Date: Tue, 23 Jan 2018 12:22:05 -0500
Message-ID: <CAG4d1rf1njJF0vpt8tQ3vQUTBC4T+_ZJw=2DGHViSqW6pfvMjg@mail.gmail.com>
Subject: early proposed charter for the Link-State Routing WG
To: isis-wg@ietf.org, OSPF List <ospf@ietf.org>
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c17f5447fb1e056374c963"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/nr2ekF6ok8fodrfDOAyv48yZi74>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jan 2018 17:22:11 -0000

I am working on the initial charter for the LSR WG, which will combine the
OSPF and ISIS WGs.  At this time, I do not see moving the fast-reroute work
from RTGWG, but I am willing to hear opinions.

In general, feedback on what areas should be the initial focus or specific
concerns on scoping would be useful.  My basic plan is for a broad charter
focused
on maintenance, usage scenarios, and extensions - much as OSPF and ISIS are
chartered today.

I would like to have this on the February 8 IESG telechat, so rapid
feedback and reviews
of the proposed charter when it is sent out would be appreciated.

Thanks,
Alia