IETF Logo Mail Archive

Re: [Teep] TEEP breaking OTrP compatibility consensus

<Faibish.Sorin@dell.com> Mon, 05 August 2019 03:25 UTC

Return-Path: <Faibish.Sorin@dell.com>
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 1D3AB120146 for <teep@ietfa.amsl.com>; Sun, 4 Aug 2019 20:25:36 -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=dell.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 F8P9YJ1dzbVO for <teep@ietfa.amsl.com>; Sun, 4 Aug 2019 20:25:34 -0700 (PDT)
Received: from mx0b-00154904.pphosted.com (mx0b-00154904.pphosted.com [148.163.137.20]) (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 63B30120140 for <teep@ietf.org>; Sun, 4 Aug 2019 20:25:34 -0700 (PDT)
Received: from pps.filterd (m0170395.ppops.net [127.0.0.1]) by mx0b-00154904.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x753OMkK023502 for <teep@ietf.org>; Sun, 4 Aug 2019 23:25:32 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dell.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=smtpout1; bh=7S48Y3LlFcsQEWpogK+HZXzl2fGM3GjX+U1QVp7C9bc=; b=ChS8X6yF9rj+Bwq9/5trqAdiSELfr6/GaQ7Z1nYERp6YLCgxO/95dUg97Yh813w3feWi DIE64vZbDAeVPKor7zeiRY2UbiC4jkWW7Xca9OiMlum++mCNH1ByW1KJHEGkGKRbq2cs 8sGTOgJ1STOT2oW9L5wUpsK518Jj8DYl2rZRZKyWYjEK+aDvXuOJrDH6HBp+CDStsD6m /BM8ciyMuLdcLpeZw2Tw2jpbi/qoY+yIKac4U57cgEyemtGVyLUu+SLd7cil4ApSMLjS 9umwYDywQcBZR0UhdeqkKbWftSPfjPDmNJbxF+XeN96xu5Ov9grkf1Thqci12WnIo0nq 8w==
Received: from mx0a-00154901.pphosted.com (mx0a-00154901.pphosted.com [67.231.149.39]) by mx0b-00154904.pphosted.com with ESMTP id 2u56xq4sb3-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <teep@ietf.org>; Sun, 04 Aug 2019 23:25:32 -0400
Received: from pps.filterd (m0133268.ppops.net [127.0.0.1]) by mx0a-00154901.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x753NHNE141006 for <teep@ietf.org>; Sun, 4 Aug 2019 23:25:31 -0400
Received: from ausxipps310.us.dell.com (AUSXIPPS310.us.dell.com [143.166.148.211]) by mx0a-00154901.pphosted.com with ESMTP id 2u5qpsatmr-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <teep@ietf.org>; Sun, 04 Aug 2019 23:25:31 -0400
X-LoopCount0: from 10.166.132.71
X-PREM-Routing: D-Outbound
X-IronPort-AV: E=Sophos;i="5.60,349,1549951200"; d="scan'208";a="404457335"
From: Faibish.Sorin@dell.com
To: akira.tsukamoto@aist.go.jp
CC: ncamwing@cisco.com, teep@ietf.org
Thread-Topic: [Teep] TEEP breaking OTrP compatibility consensus
Thread-Index: AQHVSz1tjWaoUjZWTUKSBcTEZHLHVA==
Date: Mon, 05 Aug 2019 03:25:28 +0000
Message-ID: <2A557EC8-4FD4-43B5-9DA1-2C854414B8E4@dell.com>
References: <5FDD8324-4F4E-4486-A086-C4E778B8AE39@cisco.com>, <TY1PR01MB16448C27C596FC43027D5F12D8DA0@TY1PR01MB1644.jpnprd01.prod.outlook.com>
In-Reply-To: <TY1PR01MB16448C27C596FC43027D5F12D8DA0@TY1PR01MB1644.jpnprd01.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-08-05_01:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound 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-1908050035
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 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-1908050035
Archived-At: <https://mailarchive.ietf.org/arch/msg/teep/j5ha57qDgVaknVzgVQq5L-75vLk>
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 03:25:36 -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. Thank you

./Sorin

Sent from my iPad

> On Aug 4, 2019, at 10:40 PM, 塚本明 <akira.tsukamoto@aist.go.jp> wrote:
> 
> 
> [EXTERNAL EMAIL] 
> 
> Hi,
> 
> I am fine with OTrPv2 breaking backwards compatibility against the first OTrP draft.
> 
> Akira
> 
>> -----Original Message-----
>> From: TEEP <teep-bounces@ietf.org> On Behalf Of Nancy Cam-Winget (ncamwing)
>> Sent: Sunday, August 4, 2019 9:48 AM
>> To: teep@ietf.org
>> Subject: [Teep] TEEP breaking OTrP compatibility consensus
>> 
>> All,
>> 
>> 
>> 
>> At IETF 105, there was consensus to the question: Is the (TEEP working) group willing to break backwards compatibility
>> with OTrP 1.0?
>> 
>> 
>> 
>> If there are objections to this decision, please respond by Aug 16th to this email with the rationale for why TEEP should
>> continue OTrP compatibility.
>> 
>> 
>> 
>> Thanks,
>> 
>>                Nancy
>> 
>> 
> 
> _______________________________________________
> TEEP mailing list
> TEEP@ietf.org
> https://www.ietf.org/mailman/listinfo/teep

v2.23.0 | Report a Bug | By Email