IETF Logo Mail Archive

Re: [Teep] TEEP breaking OTrP compatibility consensus

塚本明 <akira.tsukamoto@aist.go.jp> Mon, 05 August 2019 05:41 UTC

Return-Path: <akira.tsukamoto@aist.go.jp>
X-Original-To: teep@ietfa.amsl.com
Delivered-To: teep@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22B79120059 for <teep@ietfa.amsl.com>; Sun, 4 Aug 2019 22:41:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FROM_EXCESS_BASE64=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=aist.go.jp
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 0azfnZYemGMo for <teep@ietfa.amsl.com>; Sun, 4 Aug 2019 22:41:31 -0700 (PDT)
Received: from JPN01-TY1-obe.outbound.protection.outlook.com (mail-eopbgr1400057.outbound.protection.outlook.com [40.107.140.57]) (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 0F8CB120134 for <teep@ietf.org>; Sun, 4 Aug 2019 22:41:30 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ieM4BnaJJ+yIxVh0qJQXC5WWaVT8FwpJkHlQPOuQtFBhOUTdOBElnKBc992LSJx4AkK0c2b/GQ+IqK69S/KdunY+zVS2iEnDT30uKLRsY5LNNCDLpfkxTl08gTW46S85IngnawogQ/xN1k+cpUO2RPy8dM/EDASboLDtCrj1CNaF4SXDt7OlIyFimDdn71B6p2B3CGEzRxy6OJuDLb70QoUTEdrz15KgBoIeOFZn0nxxhKNJMUInWO7Tfojy0Ug8jIj4emlQqzfHPHRKGn2dx3gzMLX1894LIxQ6lhJ2Lkd0YTtkxJcq3XA7yU14JilUpVBrXBbhsPe4Ii4S8j5G8g==
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=7Aq0sxbURwt289zIMATGGdX3l8HPCkmg/vKxwpE8Rwc=; b=euRgTIV6t33QZElfGWAuBVGL5WdFK//tqpGyFKtbnI6hBtHTdQIuG4dkAK8TCxFxaifY8Yf6we1MNUt2BMH+h2DPbFhgxjskMxj7zMfn2+rz+Pr6/a/rCvgIZpSyGMaUUXw3QaqLDg9GWRL/t/zfjaysh6Jbw+N++m44Cv32TRLi+puh32TMwyLxvB6PSibaZeNnx7Dx9Q9Qe0WOABYh/RFdlOt0jkc6gVCe9uqWEWdkkfhJh5lxvpP26Rzh5vGAlaYH5lKrwYl5PFFu56tgoe1J/ZGu3D9uJ806BkNjxaBF86RsyVpk1GeS8NbGS/CwKtuylOG2DHwsbt7DSKb6jg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=aist.go.jp;dmarc=pass action=none header.from=aist.go.jp;dkim=pass header.d=aist.go.jp;arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aist.go.jp; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=7Aq0sxbURwt289zIMATGGdX3l8HPCkmg/vKxwpE8Rwc=; b=tcZIRLvUg0r5dukiqU+lrzGxalnCG2gbYqhzHkWZeXA0cWqVlnn7DWcy3r+x0T2fsc+B4mbTgDOBeVNNWmLjclHsDluzoN4US69BtD2ur8Lc0YJzjjYrlEBJ+yZ5mUjyWvcXfHive1LHXESzFwL18S5N2dOfQgRZ1ko2rBGXrPA=
Received: from TY1PR01MB1644.jpnprd01.prod.outlook.com (52.133.162.18) by TY1PR01MB1644.jpnprd01.prod.outlook.com (52.133.162.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2136.17; Mon, 5 Aug 2019 05:41:29 +0000
Received: from TY1PR01MB1644.jpnprd01.prod.outlook.com ([fe80::c48b:1157:7040:813a]) by TY1PR01MB1644.jpnprd01.prod.outlook.com ([fe80::c48b:1157:7040:813a%7]) with mapi id 15.20.2136.018; Mon, 5 Aug 2019 05:41:29 +0000
From: 塚本明 <akira.tsukamoto@aist.go.jp>
To: "Salz, Rich" <rsalz@akamai.com>, "teep@ietf.org" <teep@ietf.org>
CC: "ncamwing@cisco.com" <ncamwing@cisco.com>
Thread-Topic: [Teep] TEEP breaking OTrP compatibility consensus
Thread-Index: AQHVSl5I4dCtYdRaLESRpBJV5WLDRqbr170AgAAOYQCAACLSAIAAAYyA
Date: Mon, 05 Aug 2019 05:41:28 +0000
Message-ID: <TY1PR01MB16448117E86C51268BD589E4D8DA0@TY1PR01MB1644.jpnprd01.prod.outlook.com>
References: <5FDD8324-4F4E-4486-A086-C4E778B8AE39@cisco.com> <TY1PR01MB16448C27C596FC43027D5F12D8DA0@TY1PR01MB1644.jpnprd01.prod.outlook.com> <2A557EC8-4FD4-43B5-9DA1-2C854414B8E4@dell.com> <D3D5F7A7-EB18-4757-A013-5F71F78EFB18@akamai.com>
In-Reply-To: <D3D5F7A7-EB18-4757-A013-5F71F78EFB18@akamai.com>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=akira.tsukamoto@aist.go.jp;
x-originating-ip: [150.82.217.251]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d47e823f-7ead-4994-0fb9-08d719679074
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:TY1PR01MB1644;
x-ms-traffictypediagnostic: TY1PR01MB1644:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <TY1PR01MB1644873FC972505BFC0FEC7FD8DA0@TY1PR01MB1644.jpnprd01.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 01208B1E18
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(346002)(396003)(39860400002)(376002)(366004)(13464003)(189003)(199004)(8676002)(25786009)(76176011)(7696005)(81166006)(81156014)(8936002)(85182001)(68736007)(4326008)(86362001)(966005)(102836004)(6506007)(478600001)(53546011)(71190400001)(6116002)(71200400001)(256004)(2906002)(99286004)(14454004)(3846002)(2501003)(76116006)(476003)(6246003)(55016002)(229853002)(74316002)(446003)(486006)(66066001)(11346002)(53936002)(110136005)(7736002)(316002)(305945005)(33656002)(52536014)(66946007)(66476007)(5660300002)(66556008)(64756008)(66446008)(26005)(6436002)(6306002)(9686003)(186003); DIR:OUT; SFP:1101; SCL:1; SRVR:TY1PR01MB1644; H:TY1PR01MB1644.jpnprd01.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: aist.go.jp does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: p0rUFajm0mwaPgaWbX3uNjsdXjHhYl2XieRdbVSyCgmvQKjFvhrJoP6dXTWMfKYlZvENK+udR8op2AR/XHs7beCJ9ZohHEaU9K8MUizdp7qrWPzLGxc81MWOXR+BX2BtGm+wZUygg0zdZ0+ENkBKynzz8Qo1PdJaxctmuRXccPUq3l4TVrOrGg85nbKwHW/elGBM9ghGBi9Y4J+FSYfgI02iRXmI86j6D9DrHom8FUMoyeeL+kKX3gR0bZhALiJRTuSPum/bVsrA7BMH1yr/Z0sjzOt9wUxsLMPmlbqrKvYhY0P5cB5gTMxrWOxtWSuqi2e/V2S7jsbqluoTayTC1i1RciKnalS/POvs45yvb1tG1zLTqnJVZTUFKntYmIRQrb354BiGSrSq86d2kdOH++eX8/POUu1XUVnExTsS/6U=
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: aist.go.jp
X-MS-Exchange-CrossTenant-Network-Message-Id: d47e823f-7ead-4994-0fb9-08d719679074
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Aug 2019 05:41:29.0986 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 18a7fec8-652f-409b-8369-272d9ce80620
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: akira.tsukamoto@aist.go.jp
X-MS-Exchange-Transport-CrossTenantHeadersStamped: TY1PR01MB1644
Archived-At: <https://mailarchive.ietf.org/arch/msg/teep/a9sTh8OolskiECbdKXM3gcFWjuc>
Subject: Re: [Teep] TEEP breaking OTrP compatibility consensus
X-BeenThere: teep@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A Protocol for Dynamic Trusted Execution Environment Enablement <teep.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teep>, <mailto:teep-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teep/>
List-Post: <mailto:teep@ietf.org>
List-Help: <mailto:teep-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teep>, <mailto:teep-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2019 05:41:33 -0000

> >    I am also for breaking compatibility but I would prefer to change the name of the draft not just adding -v2 to the
> name.
> 
> Same here.

Initially I felt the same. Then I thought that I have not seen any implementation of full OTrP-v1 so
if the first implementation would be OTrPv2 then I felt it would not much matter in implementations
as far as the future variants would not have confusing name.

Akira

> -----Original Message-----
> From: TEEP <teep-bounces@ietf.org> On Behalf Of Salz, Rich
> Sent: Monday, August 5, 2019 2:30 PM
> To: teep@ietf.org
> Cc: ncamwing@cisco.com
> Subject: Re: [Teep] TEEP breaking OTrP compatibility consensus
> 
> >    I am also for breaking compatibility but I would prefer to change the name of the draft not just adding -v2 to the
> name.
> 
> Same here.
> 
> We saw similar confusion with the base ACME spec, which is used by LetsEncrypt, and the IETF version. QUIC also
> re-used the name, but the confusion there was much more tractable because the base implementation is pretty much
> controlled by one party, who has been very careful to label things as IETF QUIC and gQUIC, for example.
> 
> 
> _______________________________________________
> TEEP mailing list
> TEEP@ietf.org
> https://www.ietf.org/mailman/listinfo/teep

v2.23.0 | Report a Bug | By Email