[OSPF] merging OSPF & ISIS WGs & mailing lists

Alia Atlas <akatlas@gmail.com> Wed, 19 July 2017 08:03 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F6AE13167A; Wed, 19 Jul 2017 01:03:33 -0700 (PDT)
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 p6rSP047geIo; Wed, 19 Jul 2017 01:03:32 -0700 (PDT)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (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 2E7C0131600; Wed, 19 Jul 2017 01:03:32 -0700 (PDT)
Received: by mail-wm0-x22f.google.com with SMTP id g127so7411194wmd.0; Wed, 19 Jul 2017 01:03:32 -0700 (PDT)
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=p7thIIcylY+sgHwst0sxuSiLpbmb6JTPQQrFSEPgs5I=; b=mIexGnjc/ZE22TXMrM/on+NCe1O8JzS6kYeGFUFKsFXafvw73LK1ega/PlSTsbel+6 48/XTy9xXs28PbX2ySSLT240UGlK/qpCSOtTohiiZkwgfCpDyGtYXrHihWy1yOm2wMZL smczXYG/3D5rU+JofscvA2OA4gLLWdyiQcNv7oi0Lyo8d0RYIdv0mrg4r8Ick5NQRadM Q7PGUrVWN3tOqXsu08FHhBCaC4zx3aU5JsJuYaY+By8GsiIJSXKzOeHhIUTcl5l6GX0a SRTjm0lpokNHRi/bgWwpbIdoyC5M9NCbPS3B9cen0bM2IUcpEcYHNenuSV0szxTeJUMu qeVw==
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=p7thIIcylY+sgHwst0sxuSiLpbmb6JTPQQrFSEPgs5I=; b=iaNcNrj6A2oxqgvWHEor2bnRfg2PMuAahJPNkc1OUTck+s9XmBkKzjUGHrXlaahp3t wq7jwzds0oBL0pAKoEL6iDOaQd83iG2j9ZRSMt8kHm0m6Pcc85pWVDtTmf0Pvf8odqcB m1h3sblrDNb1PO+bsGh+rApK7dd+1mc1FP5dygSwZdeu8J6e4/iMkCdxY4V9aHMEmJfL 2Q80iYiyigt2C0yFg9yIEE2wjnZ4gkADWAjldaVofepqVnxDu41JDwCNCwxFWf0wlDDn zUWBs3f12Nxd1CljGGaTRhIc/1ME1YIz/scHcjhIcLW5jLAbksFcVkYSQraCvcDa6fnr /uBw==
X-Gm-Message-State: AIVw111C+nVhVLbEzRh9IWhlGjp/MOWC9tCN/gIYRX9sOF94WUE92QTr oEOotO6h2e2pnck5yQYtGEffCdb/+bZG
X-Received: by 10.28.216.21 with SMTP id p21mr3956912wmg.24.1500451410511; Wed, 19 Jul 2017 01:03:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.183.1 with HTTP; Wed, 19 Jul 2017 01:03:30 -0700 (PDT)
From: Alia Atlas <akatlas@gmail.com>
Date: Wed, 19 Jul 2017 04:03:30 -0400
Message-ID: <CAG4d1re_sm56RpyYLE+vAF22zhhcSPtwqBPwNSLiW2YiSpQHqA@mail.gmail.com>
To: "isis-wg@ietf.org" <isis-wg@ietf.org>, OSPF List <ospf@ietf.org>
Content-Type: multipart/alternative; boundary="001a11469ecc538cf80554a7117e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/eCbGZRiTf3XVtoW-8LIhzHHe3_M>
Subject: [OSPF] merging OSPF & ISIS WGs & mailing lists
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 08:03:33 -0000

As discussed in the ISIS and OSPF, we are going to be experimenting for the
next 4 months (through the next IETF at least) with what it would feel like
to have a merged WG for OSPF and IS-IS.  This is driven by the goals of
having conversations in one place for the various extensions that are
happening in OSPFv3, IS-IS, and OSPF and by the goal of having a slightly
larger WG and encourage cross-protocol learning and discussion.

At IETF 100, OSPF and IS-IS will be having a truly joint meeting.  Between
now and then, we will be having the equivalent of a joint mailing list.
After discussion with the Secretariat, this is most easily done by:
   1) Storing the current subscription list for each of the OSPF WG and
ISIS WG.
   2) Subscribe all subscribers of each mailing list to the other and vice
versa.

I will ask the Secretariat to do this tomorrow  (Thursday) morning (Prague
time).

One outcome of this experiment is that the IS-IS and OSPF WGs will be
merged together afterwards.  If you have thoughts on key aspects for the
charter, please do share them.  Such a charter would be likely around
link-state IGPs - and will need a new name.  Please share your suggestions
for possible names privately.

Regards,
Alia