Re: [OPSAWG] Red: RFC8907 (was: Re: Can we please adopt draft-tuexen-opsawg-pcapng?)
tom petch <ietfc@btconnect.com> Fri, 13 November 2020 12:52 UTC
Return-Path: <ietfc@btconnect.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 595A43A08E7 for <opsawg@ietfa.amsl.com>; Fri, 13 Nov 2020 04:52:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 6QYn7bpi027Y for <opsawg@ietfa.amsl.com>; Fri, 13 Nov 2020 04:52:24 -0800 (PST)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-eopbgr130121.outbound.protection.outlook.com [40.107.13.121]) (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 75F343A08EB for <opsawg@ietf.org>; Fri, 13 Nov 2020 04:52:22 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=oEzFtRr1tEUqLSBB8fD1FjXAv6l0+DD7kAWM0gO49V70UAVP1H9k7yX2fY/T+GOUATSa4axmTYmnVHTHFap/9oNKVsLHMdxBB0cmI7z0EnPpxKzGImGbFKAiKpWaFNYbqIOfWLq1xR9BkCY8kAk28duHPwJVdHO6I2SWTfIIB+n+BcrqphXWUuCR+47kA39E+69RRGmit8IW/g9jbhONIDAIR+VflIz4YBOhWuAr+gybwQ0IBjHzKMi3Usyp5NqREJMH5dXo/3sGbylMeLIktB6/p/rHsXIzianjUS4cU+Xp4akyXkuYAjmI5J+bUBcL0BwpHlvUa0vzIWI7DRNb/w==
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=JLjZX5HPW9qUoFsC2hf9xvSewsuJMTjmeb+IXkZtda0=; b=Mp3odGEGeImZuAtphCyN33kCFNgBm8+sJREPJWxJmGiuKZ6OJQGKO4BwukbJRt+RRxIhriJ1R1BLS4QDmoLp8v4D/4fzEXc87g9cV4LinY2fCePVDOKNROL3EzrXZhn0pAhimuRiojPLgpa/2Ur5Kd60DfylE5STG/kKC3TCWOF89wpBxh5QfuL2NGFQU8y5YzTX0LHPnoma5D7qHY233VEctZoax3lP8+wxfdoXpTMAy1HbbspADPqsxYWfdmKWW35X9xJn5srHUyyDZneHAIasHO5aQzLMYU0giIN3xbX64E440g1M+dYDgGHqdDb6fh0gk5Sb2Dt1IB+bVmeBQg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=JLjZX5HPW9qUoFsC2hf9xvSewsuJMTjmeb+IXkZtda0=; b=IyCbmjHDVxbLXfl3LBERx3vNMJgqiWGUhZd8ISF5aPaFcIy8aVnjMDBXhZp4vbGwsgTccuFNF6Hl/MdgABOQq0o4XNWtNamn2VWFPRgB6syqKNeo56cryPv3zswDc2MGdsoZTJ5HoPyJtSU7JIMfyefclMaiWHR47MIiFcs0HM4=
Received: from AM7PR07MB6248.eurprd07.prod.outlook.com (2603:10a6:20b:134::11) by AM5PR0701MB2530.eurprd07.prod.outlook.com (2603:10a6:203:f::7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3564.13; Fri, 13 Nov 2020 12:52:10 +0000
Received: from AM7PR07MB6248.eurprd07.prod.outlook.com ([fe80::ad44:1086:3767:a804]) by AM7PR07MB6248.eurprd07.prod.outlook.com ([fe80::ad44:1086:3767:a804%8]) with mapi id 15.20.3564.025; Fri, 13 Nov 2020 12:52:10 +0000
From: tom petch <ietfc@btconnect.com>
To: Carsten Bormann <cabo@tzi.org>, opsawg <opsawg@ietf.org>
Thread-Topic: [OPSAWG] Red: RFC8907 (was: Re: Can we please adopt draft-tuexen-opsawg-pcapng?)
Thread-Index: AQHWuT+vtTREFnM3s0O4S3lpgMZFH6nFEhwAgAAqlACAAFp2AIAACHaAgABkAU8=
Date: Fri, 13 Nov 2020 12:52:10 +0000
Message-ID: <AM7PR07MB624873D4A630074D3112D5D5A0E60@AM7PR07MB6248.eurprd07.prod.outlook.com>
References: <20201111080817.g4oc75o5ufwtxd5p@anna.jacobs.jacobs-university.de> <873CA76D-E744-45CA-A82C-1228798619CB@tzi.org> <20201111092125.GF39343@faui48f.informatik.uni-erlangen.de> <079EB1DE-694E-403B-A9C5-F4ECD28DBC59@cisco.com> <20201111150739.GG39343@faui48f.informatik.uni-erlangen.de> <e195e3de-5d4a-8416-7e36-c17cec32af03@gmail.com> <9215_1605164101_5FACDC45_9215_16_1_787AE7BB302AE849A7480A190F8B933031578800@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <758CFA2F-E353-409D-987C-000C23EA0EC3@tzi.org> <22094_1605167175_5FACE847_22094_64_1_787AE7BB302AE849A7480A190F8B933031578836@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <9C197251-812E-4687-A585-4EF8B702E466@cisco.com> <20201112220244.GD39343@faui48f.informatik.uni-erlangen.de> <EF3EB8B3-3ABF-4854-95DB-49BDB6C953BD@deployingradius.com> <3903.1605228892@localhost> <CE8A4154-80AE-45CB-96E4-D7864832705A@cisco.com>, <F2DB3602-F013-403E-B9BD-69FC3DFABE46@tzi.org>
In-Reply-To: <F2DB3602-F013-403E-B9BD-69FC3DFABE46@tzi.org>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: tzi.org; dkim=none (message not signed) header.d=none;tzi.org; dmarc=none action=none header.from=btconnect.com;
x-originating-ip: [86.146.121.140]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 1993413a-fee7-4a94-590e-08d887d2ef56
x-ms-traffictypediagnostic: AM5PR0701MB2530:
x-microsoft-antispam-prvs: <AM5PR0701MB25307E787ED2A5607EF6C31BA0E60@AM5PR0701MB2530.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 6bGdDzqu30IcUU5xmUhNMIzNDb8wWYHneuMWgPCPO0U9Fh7PzaD/R/5wkyf0trZGF7KWJqYtHAFWWPO08YRsDagXg0ceajwtbHDaADzrriqkfS+yGsOQF4YyNlEmhWb13XH6+yh4aF5QHuOZu9/VW9iU723KP3u+ZshfUzmd+7XXNKFFDtdfyADwIhpN8AZVxFRC074/9AgXYfsvNpsvOAfKQM4cgQmGlcWgfi3ZS9n2zMnq1LP7J5U3hDuYMeMADLXt0iQgfg7Xi0vb+wp8GEVXq/BFRbPPWSKw6owQ/8D3EgAQC9krY8wXE0mVk1Jrvk6XOeJVZEY6DfSq3111L349vOPrXeji4r9BvwyBlMiKaQH3vMXG2+wjNgQZIaWxJfhIjBs4Tncj5MLGkvXkqw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM7PR07MB6248.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(396003)(346002)(39860400002)(366004)(136003)(376002)(9686003)(64756008)(110136005)(66446008)(91956017)(76116006)(6506007)(71200400001)(966005)(186003)(52536014)(7696005)(8676002)(33656002)(5660300002)(2906002)(66476007)(53546011)(478600001)(55016002)(66556008)(66946007)(8936002)(316002)(4001150100001)(26005)(86362001); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: cHoMpZ8JK6YIRW5cRevWhp7UXQ9ajQ3chkeCy5CcEiaDWQx87xq6D9nzCdHVoCAtZ5TUKjBCdrKkqLA0Wwi4QydU/TcC2edQUtlc6fA0wFB2NNCvCP3qAEL6DKb7EOiXdux7+ZNSIrdZOcy9k9pniM0UGJV5SQ1HQVNxKdCrDtrCDaE60dpXq+tNNID6ikyo6me3WNEZULCigbYc1AclTviouqd5vK8BzaNhVG6Y/Au6niHSCY0jX8iUglzNpgxS8xpDpidRONdtKHEHgA0yugSqZy/fkEXytWCZqSG39dM0+GJoFSHZOS2zxqRoFLjOxltWaoNFZ6OLrcJWz8vQuV61MnsjZgkD7YIuTNoT2r1NZqcFJZl/mHO/FYqezZ4hdt690jVIi/lFB6I6xM2WWutYOqxGAQ+KB3zR0w+n0yWhFq6zWg10Ho766cG4yS1VxHg2SLLDkFJUJg7odz7XJVEzUsSuThqNLllaElrbivHhCbUY2m6eKvpnHOUiLqP9vl8OkS7CJ12O8qxxqVB2pgaoKXF1kikLRRGkZ3IOlguK9ql5fUOK+t9s5bc8g5zpanF6o6u5KjZEBEed7QxODybCp1jeQGLm1b02cU7tYTUsWrgdUZrBlWRAHS+U+B8KDHL1dy+HuiaKRqeCXqPtA9gW2sJVOPCRPgH3j7oPApMditel1bXLy4mIK+FC+iPVcAVv1bumMnNx9/2++NGB8GACxBSgDaK0l5W+18hZvzEnrLsTgXHju0ZAsifXW1EEv+PpnMY7wuP4uyACForlYOQkaKzjuRThN3VwONB9V6wKHOMtsVCjTtygAY7NlMQf3xeLSBAo6/J4kuxZxS+9S2DLAoQl6id+06OC83jHHnRxfyPHeFoRYQp3KZn9dGDln9iuPYYvCiFkWHWrrXi3yg==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AM7PR07MB6248.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 1993413a-fee7-4a94-590e-08d887d2ef56
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Nov 2020 12:52:10.0185 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: maAy1FsFQaNDPOkY0VURIinc/bq+gQ6v1R0+lHxnC1F6bxmgRhmMvVjnSUUjJionPj322c//SCZ9oSdgzbSitA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB2530
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/KjehLFMDbhm24Bzrng-Tort69-E>
Subject: Re: [OPSAWG] Red: RFC8907 (was: Re: Can we please adopt draft-tuexen-opsawg-pcapng?)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Nov 2020 12:52:26 -0000
From: OPSAWG <opsawg-bounces@ietf.org> on behalf of Carsten Bormann <cabo@tzi.org> Sent: 13 November 2020 06:48 On 2020-11-13, at 07:18, Eliot Lear <lear=40cisco.com@dmarc.ietf.org> wrote: > > bureaucratic process The discussion is really frustrating. Lots of people who can point to other specifications and how they were handled in a way that was appropriate to those specifications. Thank you all for pointing to those examples; we learned some interesting history. But pcapng simply is a different case. Before insisting that pcapng is exactly like your favorite specification and therefore MUST be handled exactly like that, please do listen to the people here explaining why that is not so. There is no *real* issue with picking up pcapng as a standards-track specification. We sure can invent some issues here, but the fact that unrelated specification X was handled in way Y successfully doing a different process is getting boring quickly; it’s simply not relevant. The fact that we would probably design this differently a decade later is interesting, but again no reason to not go ahead with a standards-track specification with a view to not breaking things. I’m not going to comment on Toerless’ tangent that picking up a specification that is already in real-world use might require tying up the IESG in a promise not to actually review the WG result properly. (Yes, I’m feeling with you about the ANIMA email address issue.) But no, tying up the IESG in a corner is not a requirement for working on pcapng, and that tangent is not a useful discussion either. <tp> I do wonder if anyone has read draft-tuexen. I have no problem with OPSAWG producing a standards track specification of pcap... just that this I-D is an abysmal starting point. As I said before, perhaps half of the text needs to be ditched IMHO, all the proprietary stuff, all the references to github. And plenty needs adding to bring it up to IETF 2020 standards. Give it to the ISE and even they might choke on it but any output from them can only be a better starting point for an IETF WG. Tom Petch Grüße, Carsten _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
- [OPSAWG] Can we please adopt draft-tuexen-opsawg-… Eliot Lear
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Joe Clarke (jclarke)
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Michael Tuexen
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Michael Richardson
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Toerless Eckert
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Carsten Bormann
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Toerless Eckert
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Juergen Schoenwaelder
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Toerless Eckert
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Carsten Bormann
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Toerless Eckert
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Eliot Lear
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Juergen Schoenwaelder
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Vladimir Vassilev
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Toerless Eckert
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Blumenthal, Uri - 0553 - MITLL
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Eliot Lear
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Toerless Eckert
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Warren Kumari
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Toerless Eckert
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Toerless Eckert
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Carsten Bormann
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Michael Richardson
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Toerless Eckert
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Toerless Eckert
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Carsten Bormann
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Brian E Carpenter
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Toerless Eckert
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Eliot Lear
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Michael Richardson
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Michael Richardson
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Toerless Eckert
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Toerless Eckert
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Michael Richardson
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Brian E Carpenter
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Toerless Eckert
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Toerless Eckert
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Joel M. Halpern
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Michael Richardson
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Michael Richardson
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Toerless Eckert
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Michael Richardson
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Carsten Bormann
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Carsten Bormann
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… mohamed.boucadair
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Carsten Bormann
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… mohamed.boucadair
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Eliot Lear
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… tom petch
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Henk Birkholz
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Carsten Bormann
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Brian E Carpenter
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Toerless Eckert
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… Joe Clarke (jclarke)
- [OPSAWG] Red: RFC8907 (was: Re: Can we please ado… Toerless Eckert
- Re: [OPSAWG] Red: RFC8907 (was: Re: Can we please… Alan DeKok
- Re: [OPSAWG] Can we please adopt draft-tuexen-ops… MORTON, ALFRED C (AL)
- Re: [OPSAWG] Red: RFC8907 (was: Re: Can we please… Michael Richardson
- Re: [OPSAWG] Red: RFC8907 (was: Re: Can we please… Eliot Lear
- Re: [OPSAWG] Red: RFC8907 (was: Re: Can we please… Juergen Schoenwaelder
- Re: [OPSAWG] Red: RFC8907 (was: Re: Can we please… Carsten Bormann
- Re: [OPSAWG] Red: RFC8907 (was: Re: Can we please… tom petch
- Re: [OPSAWG] Red: RFC8907 (was: Re: Can we please… Toerless Eckert
- Re: [OPSAWG] Red: RFC8907 (was: Re: Can we please… Joe Clarke (jclarke)
- Re: [OPSAWG] Red: RFC8907 (was: Re: Can we please… Blumenthal, Uri - 0553 - MITLL