Re: [Rats] Next steps on draft-ietf-rats-architecture IPR discussion

Roman Danyliw <rdd@cert.org> Tue, 25 January 2022 23:14 UTC

Return-Path: <rdd@cert.org>
X-Original-To: rats@ietfa.amsl.com
Delivered-To: rats@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 763AC3A1531 for <rats@ietfa.amsl.com>; Tue, 25 Jan 2022 15:14:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_BLOCKED=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=seicmu.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 F4WRiy0OXF4g for <rats@ietfa.amsl.com>; Tue, 25 Jan 2022 15:14:05 -0800 (PST)
Received: from USG02-CY1-obe.outbound.protection.office365.us (mail-cy1usg02on0094.outbound.protection.office365.us [23.103.209.94]) (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 5046B3A1530 for <rats@ietf.org>; Tue, 25 Jan 2022 15:14:05 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector5401; d=microsoft.com; cv=none; b=hzesvStncgMYWsikV+sx0Yup56QLjqMdQL91MYEu4lEFqg71PJH/eoluaSc2OJ66Arg+CJwm82jVjapK+eO7FWAyiEl2YJ7fuCXI9xlE5I77+bhRX/niMKRsAbrPOjwH2f6P3EcaFbqzMRdnJKcY4Dqgm+2NTm0GN+EMU3dUWxSNSftqfiANl3ESTK7tPOPuby9eKGg4EPsFoLlWWH15oKluNrULna1sEsgfS+hGWiR1vK9G6CfaetxL7UxDZChx3rWWJpdHrwqp0PiWiSTBCuKXx9yUyMQhCFppxqcfoFAYPTDS5Qu5EMrWTmh0EPia2OR7axFOU7ZNWl3jSy0rvA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector5401; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=0GChSs/syqrGuqNVx4p/J9hWfCRxyV354mRUUzNrE1g=; b=uLgkuLB8c0ptEKgV28jnSMj0eq4NxtqyfgMnMTZKg2ig3DRQTCw6kQiOLIUGyyI8NBxKRMDEcWUt/rp129Ht7BbnShvYaKcj+I831HOmosLpOl6SGo/pEbnOFz1JFfQ4K7w8Kz4eYhCdAuJzBtPxfwFujFzNiLyyQfizYbqshgpTGY/JamnDJTs00R1Njelm5oA3JW1AEbvSNwxbloDBERc5/630TTm9tjgFgQ/xZTS/znEbLVu+A64undNTgD0oIDJB0EOdnTAqE7dOpXgeHULvNLSs86q/sPlTVI6p2uC/R0+x94mCuT7kXVRW2xK1//vystgNYyKCc/EyyEYmxw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cert.org; dmarc=pass action=none header.from=cert.org; dkim=pass header.d=cert.org; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=seicmu.onmicrosoft.com; s=selector1-seicmu-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=0GChSs/syqrGuqNVx4p/J9hWfCRxyV354mRUUzNrE1g=; b=RbPlIo/CLsz4UPjTurIBDm+Ndgk+ep8yIR4hHo2A/3BvBbTkRTJkmD+2sAHtBz/0FqWM/L3OfHxvnDrVJzEwzAMql9zTkSpfmNk0aV291YBKuGi7l/j+e4A4FWBtf0IGaCZABuv35UqynIVSrleoQadbbyuwqSf4iQ2PTEEI0sw=
Received: from PH1P110MB1116.NAMP110.PROD.OUTLOOK.COM (2001:489a:200:174::12) by PH1P110MB1727.NAMP110.PROD.OUTLOOK.COM (2001:489a:200:177::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4909.7; Tue, 25 Jan 2022 23:14:02 +0000
Received: from PH1P110MB1116.NAMP110.PROD.OUTLOOK.COM ([fe80::485d:9334:e952:9019]) by PH1P110MB1116.NAMP110.PROD.OUTLOOK.COM ([fe80::485d:9334:e952:9019%3]) with mapi id 15.20.4909.017; Tue, 25 Jan 2022 23:14:02 +0000
From: Roman Danyliw <rdd@cert.org>
To: "rats@ietf.org" <rats@ietf.org>
Thread-Topic: Next steps on draft-ietf-rats-architecture IPR discussion
Thread-Index: AdfsWLAQYv0uGBNjSV2Essksc2V3Bgl5jAgQ
Date: Tue, 25 Jan 2022 23:14:02 +0000
Message-ID: <PH1P110MB1116EFDDC33A9E3D77E86261DC5F9@PH1P110MB1116.NAMP110.PROD.OUTLOOK.COM>
References: <BN1P110MB09398BE35EAC3406BDCFDBF1DC6F9@BN1P110MB0939.NAMP110.PROD.OUTLOOK.COM>
In-Reply-To: <BN1P110MB09398BE35EAC3406BDCFDBF1DC6F9@BN1P110MB0939.NAMP110.PROD.OUTLOOK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=cert.org;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 46a3cb54-44b3-4821-64cc-08d9e058601d
x-ms-traffictypediagnostic: PH1P110MB1727:EE_
x-microsoft-antispam-prvs: <PH1P110MB1727EE34930D707943292866DC5F9@PH1P110MB1727.NAMP110.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: T527Xb569mAgMZ5IReGRAfh5vIG6PsAwQmZrgBJGHpbvh9uvYdXZ2K+gdw8F6yD2tQEDJiXCPHlpss1P8Q0qmwgJ3RzoCk2VOWWlMSlm99hx9WWElltxMyp4x9ykWzPnsWILrqOxFsmR9DCHiXCGFX0QY7pQkJigMbRzLSK6hzuEEyygfBpEeBUv0amjinljKGd4s4E3bppjnUsumjlR0+xxu8JFIv1ZSG+N9oEIK/+TfXKdO/efa6bqimifrAWuDo5H13U6nmiuAkeGUYEddgKDS/qXY2e1O9m/nC67C46wjkZnKjrbcQDlqbEqGlUhWi5XYf2lcERbxS+5F8URX0tuLBRZEsTJpOEe6dngyavwHW8ib061/ZU3EGq/X4BU5xFcKhsQNPeOyNIq3miKaZE1wDaCV8ldXgLXUJOI1xKKDedYzgQwOg60YYCKOaufTkDnY+BIjnPQsldSGZwCD7h3yK8NnMdnn338MAX+YnovLsOob35UkK1hr6EaDnwmAmqn9e1po8Mxf/ZzS8FEnswyr+MIjfNF+iWOjI0BCmtkVgnnl8WsnWq5g8nFMPuBvKcj94QOqlhQbjRO/jJxjv6yvw/4JYxpqPP6Z3u2P4m1m6oiTRTa19395ISdaTAe6k1XTLH/E2L74Q2LWSjAIj2cXyPltxhVws0Miz/BzFug342DFPR223uDM0pWosV9bGfKEKuRGqdGbcOmsA0nZg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:PH1P110MB1116.NAMP110.PROD.OUTLOOK.COM; PTR:; CAT:NONE; SFS:(366004)(5660300002)(82960400001)(66556008)(66446008)(55016003)(64756008)(71200400001)(38070700005)(86362001)(8936002)(83380400001)(52536014)(33656002)(76116006)(498600001)(122000001)(66476007)(66946007)(38100700002)(2906002)(6506007)(8676002)(6916009)(9686003)(7696005)(53546011)(186003)(966005)(26005); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: ZRhrxyf3IGeX+sPD0pl7CAI3N1OOqAqNQAgXXvpPLd5t9cyyJNT3TWoOji499IqAFD2dGgYCTVvh/hFPuI9wIwAfA9VIRlc2yXopNLm6kquWn6xohffIQpopTmsuAtRl5BY+DkuHby5zXYwKChNMhg==
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: cert.org
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: PH1P110MB1116.NAMP110.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 46a3cb54-44b3-4821-64cc-08d9e058601d
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Jan 2022 23:14:02.3449 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 95a9dce2-04f2-4043-995d-1ec3861911c6
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PH1P110MB1727
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/3nCTOkNYW8ydEo0zHZlQoY8F92A>
Subject: Re: [Rats] Next steps on draft-ietf-rats-architecture IPR discussion
X-BeenThere: rats@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Remote ATtestation procedureS <rats.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rats>, <mailto:rats-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rats/>
List-Post: <mailto:rats@ietf.org>
List-Help: <mailto:rats-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rats>, <mailto:rats-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jan 2022 23:14:08 -0000

Hi!

Thanks for everyone's patience as we determined how to handle this document.  In both the call on next steps by the chairs [7] and this thread, I was looking for objections, alternative approaches [1] and positive confirmations to proceed [2][3][4][5][6].  Thanks for all of the feedback from the document authors as well.  In response to [8] that requested more time to review the claims, I didn't close the review period in December and kept the call open until now (one month later).  

Upon review of this WG feedback, it appears that the rough consensus is to move forward with publishing this document.

Doc Shepherd (Kathleen): can you please revise the shepherd write-up to capture this discussion.

WG chairs: when you assess that all WGLC feedback has been adjudicated, please advance the document to me with a "publication request"

Regards,
Roman

[1] https://mailarchive.ietf.org/arch/msg/rats/KQhxVPCN3xDgEo5jFhB9on-ayVM/
[2] https://mailarchive.ietf.org/arch/msg/rats/xihv0yHc9hyc7-32sP4J-NJs_HY/
[3] https://mailarchive.ietf.org/arch/msg/rats/uyRm8z6Rzy0YHz8lLNtTbdtBOoI/
[4] https://mailarchive.ietf.org/arch/msg/rats/37EFdkip0px3tG5OasYRpQvZaUU/
[5] https://mailarchive.ietf.org/arch/msg/rats/37EFdkip0px3tG5OasYRpQvZaUU/
[6] https://mailarchive.ietf.org/arch/msg/rats/JrHQgIlSQR7ihMup3K6BiTYXgIU/
[7] https://mailarchive.ietf.org/arch/msg/rats/6FKaaDLry7_PexyhI5jySAOZ3cE/
[8] https://mailarchive.ietf.org/arch/msg/rats/lMudsv_xOzBWP_AXvT47P7bz-Dw/


> -----Original Message-----
> From: RATS <rats-bounces@ietf.org> On Behalf Of Roman Danyliw
> Sent: Wednesday, December 8, 2021 12:36 PM
> To: rats@ietf.org
> Subject: [Rats] Next steps on draft-ietf-rats-architecture IPR discussion
> 
> Hi!
> 
> The cognizant co-chairs and I have been coordinating on how to handle draft-
> ieft-rats-architecture [1].
> 
> This document [1] is through WG Last Call but emerging IPR claims [6] [7]
> necessitated a WG discussion on how to proceed.  When such claims emerge, it
> is common practice to explicitly consult the WG on next steps with the
> document (but not evaluating the merits of the IPR). This consultation was
> explained during IETF 112 and ran in November [2].  Unfortunately, the results
> were inconclusive due to almost no feedback being provided.
> 
> Specifically, only three parties responded on next steps [3] [4] [5] and among
> the respondents was a document author [3].  [4] suggested the WG wait for the
> full patent details (which are not public) in the case of one IPR claim.  [5]
> indicated support for proceeding with publication as planned.  To repeat, this
> level of feedback is insufficient consensus on any direct.
> 
> If we are to reach resolution on this issue, WG feedback is needed.  As such,
> WG consultation on the IPR is being re-opened till December 20, 2021.  Please
> respond to the thread [2].  Consider the existing IPR feedback discussion to
> date - are you comfortable proceeding to publication with the IPR information
> that exists? do you need to wait for full details on the IPR claims? are you
> outright uncomfortable with publication given the IPR information that is
> published? any other position?
> 
> To make best use of the time while we continue to discuss the issue:
> 
> ** The WG can resolve the early AD review comments [8] shared on November
> 12.  The next step in the document review process is an AD review where these
> would be a subset of blocking feedback before IETF LC.
> 
> ** In response to a request by the document authors, early review by the
> SECDIR and IOTDIR will also be requested by the chairs.  The WG should keep in
> mind that this is an "early review".  As is standard practice, another re-
> review(s) will be triggered in advance of IETF LC and IESG telechat.
> 
> Regards,
> Roman, Nancy and Kathleen
> 
> [1] https://datatracker.ietf.org/doc/draft-ietf-rats-architecture/
> [2] https://mailarchive.ietf.org/arch/msg/rats/6FKaaDLry7_PexyhI5jySAOZ3cE/
> [3]
> https://mailarchive.ietf.org/arch/msg/rats/GrDPAPgYWMgmUJUJu3_GBzC2FSQ
> /
> [4] https://mailarchive.ietf.org/arch/msg/rats/lMudsv_xOzBWP_AXvT47P7bz-
> Dw/
> 
> _______________________________________________
> RATS mailing list
> RATS@ietf.org
> https://www.ietf.org/mailman/listinfo/rats