IETF Logo Mail Archive

Re: [Suit] Wording for integrated payload size

Dave Thaler <dthaler@microsoft.com> Wed, 11 December 2019 18:51 UTC

Return-Path: <dthaler@microsoft.com>
X-Original-To: suit@ietfa.amsl.com
Delivered-To: suit@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62548120828 for <suit@ietfa.amsl.com>; Wed, 11 Dec 2019 10:51:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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_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=microsoft.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 8eDlB3yW-HTC for <suit@ietfa.amsl.com>; Wed, 11 Dec 2019 10:51:34 -0800 (PST)
Received: from NAM10-MW2-obe.outbound.protection.outlook.com (mail-mw2nam10on2129.outbound.protection.outlook.com [40.107.94.129]) (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 13B41120825 for <suit@ietf.org>; Wed, 11 Dec 2019 10:51:33 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=cfKeLfG4+FwYVlCJ/QzuhwfcGAZbJIKA9ELG2d/xupDs0CwFR45f+/kUcH9ip0jD99Cf26Lo9PenRUNZKHfUTo846uHs82QXxQutisWga3Pstb84muf1TaXRIu95vt+xui91kDtVlHNm5JRCF/78pwFkk42+yDCnouB+4r7P2IQdcAeAQWZdMdmpVFZetthi/7cHuPvcSi+swEWBMm4V2IynQeQvhwSvV762Zw/yUrB6nFTbrPfzCmceP31GfigvpqCBigBS8WgZk3wndcSJFfCUwgE08hRdF/t9EbIJL2cmNPBexnEYAXw1eqJxTx7Qc6O6mVtmH6OeKq0+719cpg==
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=j1zOcQdRwhGmzgZEQ8eb1/AaBXh1lOjG/bU+uVSN23Q=; b=kYS+MdMA49HZk+5NQ4xbkWIZg6eyXhkRQHOKwqTbcLYo2SESGO/m1HQee3MOv87/YKMry7idu5HQR+lar8HCsfhbaPXCXqWknSgFEaeI2NWPScqy+2C9IvAkT/E1vxi2HmiSy08DiE3v6jPmzr3g9t1udaqAT5gBOCthelAIQrLr3T8pmw90Ky2cMcMh3xMgnFDELxRjXalTeA9YY1/4stuUGX6Ze4l3daHAEAORCD7Ur2O2HTFQ76dWScKwjgfbam0S5sUFlqQLymQL1S02HJoPlPAMeRc0M/Lk8PDt7sihOEY9gBklXnUnl/uLZkeh1MZDp1WPhqZgGDo7iBtCcg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=j1zOcQdRwhGmzgZEQ8eb1/AaBXh1lOjG/bU+uVSN23Q=; b=C5SXcMtXuy326rwBusX9BAiLhmeHD45zia0uPDqo9H+2xKw2USZIw+8TBYPDrjji4CQeMTNnLxAjvsuQKl3R9yNz0lXYiMW2viM2hsUuw3IzZfVwEsOCv073Thc1tokCE5veyTn0TaQqVummvvYxCY3XLyxvSX72Bjuj2Y5B6ds=
Received: from MWHPR21MB0784.namprd21.prod.outlook.com (10.173.51.150) by MWHPR21MB0832.namprd21.prod.outlook.com (10.173.51.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2559.7; Wed, 11 Dec 2019 18:51:32 +0000
Received: from MWHPR21MB0784.namprd21.prod.outlook.com ([fe80::a116:227:f704:a027]) by MWHPR21MB0784.namprd21.prod.outlook.com ([fe80::a116:227:f704:a027%14]) with mapi id 15.20.2538.012; Wed, 11 Dec 2019 18:51:32 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: Brendan Moran <Brendan.Moran@arm.com>, suit <suit@ietf.org>
Thread-Topic: Wording for integrated payload size
Thread-Index: AQHVrEAJWYIMpqtbJEmLD8MchsbiNqe1T0sg
Date: Wed, 11 Dec 2019 18:51:32 +0000
Message-ID: <MWHPR21MB0784F574BE1FFD50743040FCA35A0@MWHPR21MB0784.namprd21.prod.outlook.com>
References: <734509A8-7562-4B47-AAE5-54F840C4A298@arm.com>
In-Reply-To: <734509A8-7562-4B47-AAE5-54F840C4A298@arm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Owner=dthaler@ntdev.microsoft.com; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2019-12-11T18:51:31.5170139Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Application=Microsoft Azure Information Protection; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=5c5ca03b-c877-4bc5-bc7b-d5605a462dd5; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Extended_MSFT_Method=Automatic
authentication-results: spf=none (sender IP is ) smtp.mailfrom=dthaler@microsoft.com;
x-originating-ip: [73.59.106.235]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: a1bc4923-1edc-4ed1-c827-08d77e6b23fd
x-ms-traffictypediagnostic: MWHPR21MB0832:
x-microsoft-antispam-prvs: <MWHPR21MB0832D073FEC7C797E31774D0A35A0@MWHPR21MB0832.namprd21.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 024847EE92
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(39860400002)(346002)(376002)(136003)(366004)(40434004)(189003)(199004)(13464003)(7696005)(5660300002)(66476007)(66556008)(64756008)(66446008)(76116006)(10290500003)(316002)(478600001)(966005)(186003)(110136005)(52536014)(6506007)(66946007)(26005)(53546011)(33656002)(8990500004)(2906002)(86362001)(55016002)(9686003)(8936002)(8676002)(81156014)(81166006)(71200400001); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR21MB0832; H:MWHPR21MB0784.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: tPAXGuoxdE654lWwW2sPu828RKjHv8Uc0Yo61VdAfXbLuh0DGJ/SOtAxybedBEkZpwb57n0vyb50TMtm3fzV5O5ya0z7EFflsDSTlUacwG4WKzk0xuYJ/ZB22EHIz08Uei0L9z56ahVbGLbfAAKZWJ0VNb9kqNmyep9bEK09TcGRMoUWCn9OGDIcExmf87eUkTVDlA88KHHUoa7MQvDPyF6m2RPSvT4ayBUgJxIJbx5NjQa4oq397d4r+4EUhbDktQvUh27cX341ScxqNMoodGMNQ6KCBTDkk+2Rr1ToTaHNvZb2VrJCQu89c+TCqmqCALEOisxKIe4oPr9yUJgh5D+eQCqs3s4ygK7o2PImfV0WZ/zwuXrU/YKtJZtTs1klUj8Gr01MwP2Avw3gmumzWYs2Sl3tXO613Ki3ni0EcyMRQSNCEHb2AQUggvSjBRFpTugUKG/BNyjoMOiqK13pzVZ7vFcEbg00YErIi28i28loKZ83L0BfveynYc55Q3IOVxGlJJtkwDo/0H9AX8gwVSSFLWcUbtZjaSyCirrx3RZcMNjky+tVHGkoNjC4fCp+
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: a1bc4923-1edc-4ed1-c827-08d77e6b23fd
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Dec 2019 18:51:32.6059 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 4BvT4ysCqfISHw3wIa1Unmo/jEnHZeexn+Oxn8/sXB5QyFXzsohDQg+uNNuFn8YBkl6zeuw9fxetDHfTCsNasWSCMdeVs6SXe9wLuzYtL4I=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR21MB0832
Archived-At: <https://mailarchive.ietf.org/arch/msg/suit/04SsWoErTwBkf8_P23uiXd-boZ8>
Subject: Re: [Suit] Wording for integrated payload size
X-BeenThere: suit@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Software Updates for Internet of Things <suit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/suit>, <mailto:suit-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/suit/>
List-Post: <mailto:suit@ietf.org>
List-Help: <mailto:suit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/suit>, <mailto:suit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Dec 2019 18:51:36 -0000

Grammatical comment:  "stored to" reads oddly to me.
I'd suggest replacing with either "stored in" or "saved to".

Dave

-----Original Message-----
From: Suit <suit-bounces@ietf.org> On Behalf Of Brendan Moran
Sent: Friday, December 6, 2019 6:19 AM
To: suit <suit@ietf.org>
Subject: [Suit] Wording for integrated payload size

To finalise the information model, we need to address the issue raised at ietf106: how big can an integrated payload be? The suggestion made at the meeting was that no specific requirement should be made, but that the information model needed some text to explain the tradeoffs in size of payload. Here is my proposal for that text.


Best Regards,
Brendan


When an integrated payload is provided, this increases the size of the manifest. Manifest size can cause several processing and storage concerns that require careful consideration. The payload can prevent the whole manifest from being contained in a single network packet, which can cause fragmentation and the loss of portions of the manifest in lossy networks. This causes the need for reassembly and retransmission logic. If the manifest is too large to fit in RAM, then it must be processed modularly; first evaluating delegation chains, then the security container, then processing the actual manifest, which includes verifying the integrated payload. While the manifest has been organised to enable this type of processing, it creates additional complexity in the parser. If the manifest is stored to nonvolatile storage prior to processing, the integrated payload may cause the manifest to exceed the available storage. Because the manifest is received prior to validation of applicability,  authority, or correctness, integrated payloads cause the recipient to expend network bandwidth and energy that may not be required if the manifest is discarded and these costs vary with the size of the integrated payload.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

_______________________________________________
Suit mailing list
Suit@ietf.org
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fsuit&amp;data=02%7C01%7Cdthaler%40microsoft.com%7C9d5dbf0c98c845d1453508d77a573609%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637112387316385698&amp;sdata=jvELlCP5PxSIqjoHOAG1NZkXyyn8oc2CPuOm6g5WaTs%3D&amp;reserved=0

v2.23.0 | Report a Bug | By Email