Re: [Mops] Barry Leiba's Block on charter-ietf-mops-00-00: (with BLOCK and COMMENT)
"Eric Vyncke (evyncke)" <evyncke@cisco.com> Fri, 04 October 2019 12:33 UTC
Return-Path: <evyncke@cisco.com>
X-Original-To: mops@ietfa.amsl.com
Delivered-To: mops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5464312082B; Fri, 4 Oct 2019 05:33:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=Y1rwRETB; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=eu3nkTZv
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 TQN-99CNx3qK; Fri, 4 Oct 2019 05:33:38 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2651F120805; Fri, 4 Oct 2019 05:33:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7940; q=dns/txt; s=iport; t=1570192418; x=1571402018; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=j2oFriUTi2Lzk1ijuckVzxiOgdjgbM7gVPrkXQLCiq4=; b=Y1rwRETBgDlH1yinHIpHUsN7yPU83B6p/nsYaYaVp6kXkER+yX6I0LJ0 iH/BuDEC3gh89pFt3YM53uXDqOFAqYMUVwhPq52c0Og3uqupAStwqMVLd oA8DC74pytFFlMGWn5MBfLC7jWH6OP4W/uGwYucHdROp5woZOB5cf4tK3 c=;
IronPort-PHdr: 9a23:QVfnZhI7fvLllFPlltmcpTVXNCE6p7X5OBIU4ZM7irVIN76u5InmIFeBvad2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUgMdz8AfngguGsmAXEDlPfjhbCESF8VZX1gj9Ha+YgBY
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CfBQARO5dd/40NJK1cChwBAQEEAQEMBAEBgWeBSyQsA21WIAQLKoNiQINHA4pIgjeYHoFCgRADVAkBAQEMAQEjCgIBAYRAAheCMCM4EwIDCQEBBAEBAQIBBQRthS0MhUwCAQMMBhERDAEBNwEPAgEGAhoCJgICAjAVEAIEAQ0FFA6DAAGBagMdAQIMkmCQYQKBOIhhdYEygn0BAQWBSEFAgkMYghcDBoEMKIwOGIFAP4ERJwwTgkw+gmECAwGBKgEHCwEfF4J2MoImjQWCZpxpaAqCI4cIhRiEdYQDG4I6h06POI4rgT6GYpERAgQCBAUCDgEBBYFpImdxcBU7KgGCQVAQFIFPg3OFFIU/dIEpjgCCRQEB
X-IronPort-AV: E=Sophos;i="5.67,256,1566864000"; d="scan'208";a="638470234"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 04 Oct 2019 12:33:36 +0000
Received: from XCH-ALN-016.cisco.com (xch-aln-016.cisco.com [173.36.7.26]) by alln-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id x94CXaC1029370 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 4 Oct 2019 12:33:37 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-ALN-016.cisco.com (173.36.7.26) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 4 Oct 2019 07:33:36 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 4 Oct 2019 07:33:36 -0500
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 4 Oct 2019 07:33:35 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=WRDJsDqJSccPci/CQGaXQuuv6J2+bLjUL/fwxYBSi0n46Aq5YRBm63kHma9ht70g/TtoEcwu7xN8Rr3hOBk85+zRnxy9OgK+u3xEuJGE8IynX4U+bF1Cu/m7qUR82Lz6jF6U8bYZB5bcvb9n4ulqVsqj/p8Ye1A2LAEVxkbMekKZiSMQumS42xEeDBt+vifHwcMOfnIlloX24FBpMqZiUDmsaILtJubkTW4uQxn5wIqs/5RBymcDsHO326bOhtOFOnm7FNbL+S3EDT28PnQNyrf2sEuAbbktEgaNdq3QYIH+cDqEukHKrERg/huBjnNpbNRkuNREc4lOacwbUKU2kg==
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=j2oFriUTi2Lzk1ijuckVzxiOgdjgbM7gVPrkXQLCiq4=; b=OD6hOkLVL/waKS++JRADz/UFucnzkw+Vlsmam3jYv4xquRpvk91y0/UY1xI2jYtthlPSmc9Dqvs9Kd1vw0g6SbUtO37I/dtAQsYkirTzM0oinDg8Lq4/VTL4PUJu2cqwF+7S1LDT++GXMwVk+IYCUNPmlb+qyZZl8uLtW8EzqcDAGLtA1/1k1fdyzSkNQbkrJvAXPWjWYWk/VSOk8KJBn3xFk+XWhqHh61ZtWSPUu1H5B6/4/CTigNlTfRyI1wrix83UN6EjJ+Cghd56J46RJaM+YeLUTKgwna2EFxuaotk/hIDhCGsIQpVFxaFv8fBRZ++rkxZUoQD/I4gLMG2gsQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=j2oFriUTi2Lzk1ijuckVzxiOgdjgbM7gVPrkXQLCiq4=; b=eu3nkTZvZd0oxulEQjvB1C+VD9hPcBh4qmUtIuyC2IfwCAIm78ARa3JyR9vfiDpXpIl9Hk4++6AFLqKbligKfGS2gngiqbnhY7uyB0YHZjTWMH0ytI4YTvMKNFOqHEmQvx3gPQ5r9BHXAyoNF9d0NfK5CCNwCl2WovSPoQV0bQ0=
Received: from MN2PR11MB4144.namprd11.prod.outlook.com (20.179.150.210) by MN2PR11MB3888.namprd11.prod.outlook.com (10.255.181.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2305.15; Fri, 4 Oct 2019 12:33:35 +0000
Received: from MN2PR11MB4144.namprd11.prod.outlook.com ([fe80::e4f8:d335:c018:c62a]) by MN2PR11MB4144.namprd11.prod.outlook.com ([fe80::e4f8:d335:c018:c62a%7]) with mapi id 15.20.2305.023; Fri, 4 Oct 2019 12:33:35 +0000
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: Barry Leiba <barryleiba@computer.org>, The IESG <iesg@ietf.org>
CC: "mops-chairs@ietf.org" <mops-chairs@ietf.org>, "mops@ietf.org" <mops@ietf.org>
Thread-Topic: Barry Leiba's Block on charter-ietf-mops-00-00: (with BLOCK and COMMENT)
Thread-Index: AQHVeifP7SDyLE331kSg+ub/Jlajf6dKjRcA
Date: Fri, 04 Oct 2019 12:33:35 +0000
Message-ID: <9FD42763-117F-4955-A83E-0AB370283680@cisco.com>
References: <157013392463.16231.13761068623463791174.idtracker@ietfa.amsl.com>
In-Reply-To: <157013392463.16231.13761068623463791174.idtracker@ietfa.amsl.com>
Accept-Language: fr-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1d.0.190908
authentication-results: spf=none (sender IP is ) smtp.mailfrom=evyncke@cisco.com;
x-originating-ip: [2001:420:c0c1:36:b8af:cfb:7d52:4da8]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 9a61d6cc-e02e-4885-1151-08d748c71314
x-ms-traffictypediagnostic: MN2PR11MB3888:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <MN2PR11MB3888CDD1A6A296F0B625B2C4A99E0@MN2PR11MB3888.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 018093A9B5
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(376002)(39860400002)(366004)(136003)(396003)(199004)(189003)(76116006)(86362001)(25786009)(54906003)(6486002)(33656002)(486006)(76176011)(316002)(66574012)(58126008)(110136005)(71200400001)(7736002)(305945005)(5660300002)(476003)(11346002)(256004)(81166006)(46003)(66946007)(81156014)(186003)(66476007)(446003)(8936002)(2906002)(4326008)(966005)(6246003)(6506007)(2616005)(229853002)(91956017)(99286004)(102836004)(64756008)(6436002)(66446008)(6116002)(6512007)(66556008)(36756003)(478600001)(6306002)(71190400001)(8676002)(14444005)(14454004); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3888; H:MN2PR11MB4144.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: kFN3/r7xNh86r3B+N0lpw7/BIpLRrHi92n2py9eOQJbbwltCweEDcq5QmCowpQgnhMTZIx/ZaamfLX2XWhVXo/GETOWNqtwT00TNJVAk4pGGHpvNDztZVEEUQfpdE4BBPpv2dlyeRObJ0DSmGTbxS4mCXzWwWxawaP9xYhRhORfWA9V0bXXugDpllIP7fxwfgavv+GA7y9+4WE5mMDca2ddF2x9u8BTfkqyM2SvtEN/c6SvfOVxqXeaBJPCrNlB0HDxOsTKvVA5y22IKgwWY3Qvy8YtDlzZfVFxw8PUOavsK2dlEnjwokXclN23eI+LrwT4rLNWAoFhqNPuyiFVyeUcrTKQRLxs4tto/sPVefMIlj6vdu3pMKJlbSORgNyUk/+JSpx/WOQndQ5m7P4fZaeXhe8VOAkTV4kl6WgrZCwa+QIm9cwRmymAbUaN3oDFea92Midnq0uIz1aLq31+0yg==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <03AEAFB0562CD84BA23AF2C47606FE85@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 9a61d6cc-e02e-4885-1151-08d748c71314
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Oct 2019 12:33:35.0399 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: p6h4xKL3ycwVETF1jOvR9r9NVbHWYdUNWLoD7RmW0fjRTb0mREtY4uJUJvM5cnM5uIAUrVbw8pnJ7IV0Y4IM4A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3888
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.26, xch-aln-016.cisco.com
X-Outbound-Node: alln-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/5K-UUbPTD1cL4u86HT76HrjR3BY>
Subject: Re: [Mops] Barry Leiba's Block on charter-ietf-mops-00-00: (with BLOCK and COMMENT)
X-BeenThere: mops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Media OPerationS <mops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mops>, <mailto:mops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mops/>
List-Post: <mailto:mops@ietf.org>
List-Help: <mailto:mops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mops>, <mailto:mops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Oct 2019 12:33:40 -0000
Barry Thank for your review and your valuable comments as always. You are right that it is not so easy to have a charter for a "standing working group" which is the first (?) attempt by the IETF community to have something resembling to a "special interest group". On your two specific BLOCKs, I will let the current chairs to rewrite your first concern and indeed adding new work items will require a re-charter in the current state of the IETF. So, let's be clear on it for now (and initiate some works on "special interest groups") Thank you also for your comments/nits: they will improve the text. Leslie and Glen, may I suggest to update accordingly the draft charter ? And if the MOPS list agrees with it, then upload it ? (if you do not have the permission, then simply send it to me) Regards, -éric On 03/10/2019, 22:19, "iesg on behalf of Barry Leiba via Datatracker" <iesg-bounces@ietf.org on behalf of noreply@ietf.org> wrote: Barry Leiba has entered the following ballot position for charter-ietf-mops-00-00: Block When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-mops/ ---------------------------------------------------------------------- BLOCK: ---------------------------------------------------------------------- In general, I'm not terribly happy with how this charter lays out specific work items (or doesn't). It's very vague, and then when I look to the milestones I get more of an understanding. On the one hand, this is OK, because we want this to be flexible, as a standing working group. On the other hand, I would feel better with being somewhat more specific. And I realize that this isn't terribly actionable, so I'm asking that we think about this, and I won't hold this "block" beyond our doing some reasonable consideration. I do have two specific blocking comments, both of which should be easy to sort out: The premise of MOPS is that continued development of Internet-using technologies should be properly coordinated in order to ensure that the existing technologies are well-utilized, and new ones are developed in sympathy with the Internet’s core protocols and design. This sounds like a lot of fuzz without real substance. Let’s try to tease out what its really saying and word it more accessibly. At some level this seems to be saying that the premise of MOPS is that what the IETF does is good. I’m sure there’s more meant here than that, but I don’t understand what. Future work items within this scope will be adopted by the Working Group only if there is a substantial expression of interest from the community and if the work clearly does not fit elsewhere in the IETF. And only with a re-chartering, yes? I don’t think we want the working group to be able to pick up *any* related work it chooses, just because it doesn’t fit elsewhere, right? ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- And then there are a number of editorial things: MOPS’ focus is on identifying areas where existing protocols and/or networks are challenged I suggest avoiding the issue of how to make a possessive of “MOPS” (I would use “MOPS’s”) by saying “The focus of MOPS is….” MOPS will solicit input on operational issues and practices, existing and proposed technologies related to the deployment, engineering, and operation of media streaming and manipulation protocols and procedures in the global Internet, inter-domain and single domain networking. Because the second list item has commas in it, you need the main list to use semicolons. Otherwise it’s impossible to be sure one has parsed it accurately. NEW MOPS will solicit input on operational issues and practices; existing and proposed technologies related to the deployment, engineering, and operation of media streaming and manipulation protocols and procedures in the global Internet; and inter-domain and single-domain networking. END In this case, media is considered to include “In this case” seems odd here. I think you mean, “In the context of this charter,” or something like that. MOPS acts as a clearinghouse to identify appropriate venues for further protocol development, where necessary. I’d rather be more direct in how this is worded (adjust as needed): NEW Where new protocols are needed, MOPS will identify appropriate venues for their development. END Bullet 3 needs a period at the end. And what “resulting innovations” are we talking about here? It sounds like more fuzz, so can we be more specific? including global Internet, inter-domain and within-domain operations. Earlier, you used “single-domain”, and here you use “within-domain”; please be consistent. There must be a continuous expression of interest for the Working Group to work on a particular work item. I think you mean “continuing”.
- [Mops] Barry Leiba's Block on charter-ietf-mops-0… Barry Leiba via Datatracker
- Re: [Mops] Barry Leiba's Block on charter-ietf-mo… Eric Vyncke (evyncke)
- Re: [Mops] [EXTERNAL] Re: Barry Leiba's Block on … Deen, Glenn (NBCUniversal)
- Re: [Mops] Barry Leiba's Block on charter-ietf-mo… Leslie Daigle