Re: [Idr] Draft IDR charter text

John Scudder <jgs@juniper.net> Fri, 26 July 2019 03:28 UTC

Return-Path: <jgs@juniper.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3DAD120283 for <idr@ietfa.amsl.com>; Thu, 25 Jul 2019 20:28:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 MsCXcuktFqAi for <idr@ietfa.amsl.com>; Thu, 25 Jul 2019 20:28:55 -0700 (PDT)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2583120281 for <idr@ietf.org>; Thu, 25 Jul 2019 20:28:55 -0700 (PDT)
Received: from pps.filterd (m0108156.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x6Q3StXh005597 for <idr@ietf.org>; Thu, 25 Jul 2019 20:28:55 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=PPS1017; bh=3DcdvgNeQkNouSxfHPAUmPILdNBKvLcqiFNevUoSE10=; b=uu7zum7rxWVn3rXeG6unm1qMWaPgnVSaTm11d113Q8hm575Ykw1qJ33IjzbgEf/K/P46 meW4zuUNXtZbaIcJHaGk1Vq3BaIoi2Q9bKRIG0mQ0eZpzlOJLAecmX5QRawcvFQVixzJ 0+eebNDmuH9n6z7H3A6nJnZ+GuQP2FReyTo9cmFjaGuuvvCy9jxYPpJ4pRgAn9x7R182 w+AfRjHOU0uumQ8d95t6LCUThWG2ebPsyWkAsHqvvCglQ7mJZciW7TSZxsKhCjbkpDs7 8USbbOKhDvf5cbfVMG2eL+tML13hel3F46LxY99FOOZS8/k33g9VXOiWtUdDyi16slAO WQ==
Received: from nam02-bl2-obe.outbound.protection.outlook.com (mail-bl2nam02lp2050.outbound.protection.outlook.com [104.47.38.50]) by mx0a-00273201.pphosted.com with ESMTP id 2tyqx404k0-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <idr@ietf.org>; Thu, 25 Jul 2019 20:28:55 -0700
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=QE5jgVibIZMGuj0LvIv8YEIYzynpuPpptafGwQMxNoqRCCVGqb/Qb28KeX8r47xNDfVf1kqIru8CLUYRPQ9h9wg/e0f37OCe34XsDlUmCHlwAtACDhH3paTAjGDIeVrI15zrkA4uvKma03frMlFGJlco3dP1O8QdVV+wO1RVBohs32+DX9DA/KRcQg5bUyBUQeO9DjJKJBWE7VKwj/oht/kmZnoggT9UUXDkh1MwMtrftT1hT+tI7HUz9D7KJ5PT3NsOeDsd9nm01pJgxWtdhEWbUyQ4gUTlczVdaR6RB6NIA+k9zJQV9NNVb6/5zA1hSCRBNyhdsmdo8R0V/6j34A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=3DcdvgNeQkNouSxfHPAUmPILdNBKvLcqiFNevUoSE10=; b=hqpezBJmXsqhN8aFMExSScJcR+cuPn0kmZkyqb6A2VpKw8rJfINxQkXisrkw07AOKMYbGxmzAAZnWkib2qhtZSMt2YYBWWROM5A59xdnFdhmhtM/ZM06P5yD8u3XJCKMLDsvdo8xv6VjJFKUyV/kAyfX1vHf6gkMCkaNCp4np+/Knmn33YD2qFvN0JatbBV8kfcfoCFlyRkmsqy5l7KFCVRG+RZqYMAevQKR3kJ0joGRS3yFpUPoOEM/lh9C6qRLyCdI/7oScQ5QVWXH0qPc8+EIcreddWcvy055wr5f2aFyNMWEah+7TIhw1d3sYVZcwHMhDpubRUYVeEmeOiAgwQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=juniper.net;dmarc=pass action=none header.from=juniper.net;dkim=pass header.d=juniper.net;arc=none
Received: from DM6PR05MB4714.namprd05.prod.outlook.com (20.176.110.82) by DM6PR05MB6668.namprd05.prod.outlook.com (20.178.227.222) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2115.13; Fri, 26 Jul 2019 03:28:53 +0000
Received: from DM6PR05MB4714.namprd05.prod.outlook.com ([fe80::64b6:144d:5560:9148]) by DM6PR05MB4714.namprd05.prod.outlook.com ([fe80::64b6:144d:5560:9148%5]) with mapi id 15.20.2115.005; Fri, 26 Jul 2019 03:28:53 +0000
From: John Scudder <jgs@juniper.net>
To: idr wg <idr@ietf.org>
Thread-Topic: [Idr] Draft IDR charter text
Thread-Index: AQHVQzp9hpilNdztS0KdZzWAUtoSi6bcPgkA
Date: Fri, 26 Jul 2019 03:28:53 +0000
Message-ID: <833860C2-22F9-4A40-93A4-2513950774D2@juniper.net>
References: <9CBFDB82-5965-4D76-A85F-3A8F5C89357F@juniper.net>
In-Reply-To: <9CBFDB82-5965-4D76-A85F-3A8F5C89357F@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [66.129.241.10]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ac88f644-0763-4b97-f689-08d71179623a
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:DM6PR05MB6668;
x-ms-traffictypediagnostic: DM6PR05MB6668:
x-microsoft-antispam-prvs: <DM6PR05MB66684A64B6EC7C333456C0CBAAC00@DM6PR05MB6668.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01106E96F6
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(376002)(346002)(39860400002)(396003)(136003)(366004)(53754006)(189003)(199004)(446003)(11346002)(2616005)(476003)(102836004)(66946007)(229853002)(6246003)(316002)(486006)(6916009)(53546011)(6506007)(33656002)(186003)(99286004)(76176011)(26005)(6512007)(66446008)(5660300002)(256004)(305945005)(25786009)(64756008)(66556008)(66476007)(6486002)(53936002)(76116006)(71200400001)(86362001)(71190400001)(14444005)(91956017)(478600001)(68736007)(3846002)(8936002)(6116002)(14454004)(8676002)(81166006)(81156014)(2906002)(6436002)(66066001)(7736002)(36756003); DIR:OUT; SFP:1102; SCL:1; SRVR:DM6PR05MB6668; H:DM6PR05MB4714.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: BV6YERouMcFV6O2C0ndrLE/kEi/RVC7F1Tpf/xrUxTgd4xjZlUaieLod91F8lCpToD4GkViyB685Ndrs3qyTIrtJ7Ue5PWs5hO8PLbE6IBAdouw4YpNHJWElltX415SAF1RHVLh2h/FMnYXeCtr+gy0tuOBVCT1Q2IyTCm/2i4mrgO90jj4QRPtbh0SRtWeD/nccP0eLKXHuMaCUQifeGHVY4ANQKF+HeQffaNwZVsZZwsf5R6PUCgD5I2CDMq4COjbrwWxGdYOlrEJCFlwtYSu3Hl3F6BR1jpInqx4pP+zWM3o1tN7Izg58g/q6caHsSb4m51SF7Rm74wU1xlUdxQPFMfJFRIGrKxQcLN6pRtHTqfN9NA0PEnJXUv58pnitkv7M97sqw6RXlNKU8JzyOttjJonWXLMTTdRnbPngb0o=
Content-Type: text/plain; charset="utf-8"
Content-ID: <C8897B546F370542A1A2CF5CD3CD3599@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: ac88f644-0763-4b97-f689-08d71179623a
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Jul 2019 03:28:53.2021 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: jgs@juniper.net
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR05MB6668
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-07-26_02:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1907260045
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/aLN6DXWGiDFweOQ304Mdzi22rlI>
Subject: Re: [Idr] Draft IDR charter text
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jul 2019 03:28:58 -0000

I received a unicast suggestion to specifically cite YANG modules, as in:

OLD:
The main objective of the working group is to support the use of BGP-4 by IP version 4 and IP version 6 networks. The working group will continue to work on improving the robustness, scalability, deployability, manageability, and security of BGP.

NEW:
The main objective of the working group is to support the use of BGP-4 by IP version 4 and IP version 6 networks. The working group will continue to work on improving the robustness, scalability, deployability, manageability (including specification of YANG modules), and security of BGP.

Seems fine to me.

—John

> On Jul 25, 2019, at 6:44 PM, John Scudder <jgs=40juniper.net@dmarc.ietf.org> wrote:
> 
> Hi All,
> 
> Here’s a draft of new charter text we came up with after consulting with the Routing ADs [*]:
> 
> —
> The Inter-Domain Routing Working Group is chartered to standardize, develop, and support the Border Gateway Protocol Version 4 (BGP-4)  [RFC 4271] capable of supporting policy based routing for TCP/IP Internets.
> 
> The main objective of the working group is to support the use of BGP-4 by IP version 4 and IP version 6 networks. The working group will continue to work on improving the robustness, scalability, deployability, manageability, and security of BGP.
> 
> BGP is an enabling protocol or subject of interest for a number of other working groups, including BESS, LSVR, LSR, SIDROPS, and GROW. Those (and other) groups may develop standards that make use of BGP. IDR asks that when another working group proposes changes and additions to BGP, that IDR should be informed. In particular, if another working group requests allocation of a code point from a BGP protocol registry, IDR should be consulted as soon as possible. The Border Gateway Protocol (BGP) Parameters group is the most notable example of such registries. In general, protocol changes should be progressed through IDR, whereas uses of extensible mechanisms need only notification to IDR.
> 
> IDR desires to review extensions made to BGP in other working groups at least at WG document adoption and during working group last calls. The IDR working group will also provide advice and guidance on BGP to other working groups as requested.
> 
> IDR welcomes advice and requirements from other working groups, particularly from GROW which is chartered for this purpose. 
> —
> 
> The main changes vs. the prior text are,
> 
> 1. Talks in more detail about what we expect from our peer WGs and what they can expect from us.
> 2. Removes the “work items” section. This was largely redundant with the milestones and it just muddies the waters. 
> 
> Essentially the intent is to say “we do BGP” but a little more rigorously (or at least verbosely). :-)
> 
> If we adopt this charter, or one like it, the next step would be to do a pass of updating our milestones, fairly extensively. Many of the suggestions that have been made so far (thank you!) would fall into that discussion.
> 
> Regards,
> 
> —John
> 
> [*] Does not imply the Routing ADs have approved this text, they have not provided an opinion on it.