IETF Logo Mail Archive

Re: [core] Is this a typo in -08

Brian Raymor <Brian.Raymor@microsoft.com> Wed, 26 April 2017 20:41 UTC

Return-Path: <Brian.Raymor@microsoft.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2762127342; Wed, 26 Apr 2017 13:41:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.022
X-Spam-Level:
X-Spam-Status: No, score=-2.022 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-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 ugdmQL8N_CtH; Wed, 26 Apr 2017 13:40:58 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02on0119.outbound.protection.outlook.com [104.47.37.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 470B51294AB; Wed, 26 Apr 2017 13:40:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=9Ptx+E0wD+L9YgNzm1wTcXzqcziuDkqg6YEGGA2F1JQ=; b=eDMYULUEMBh1Rx4yJaro2mNmxpRs1Bx0b032nXmJoWtOuXXsCM3J99/003Xy5IIxdjzEyyyVAqB7MIR9/FIAvoSqk3mQ/TJW6LNnla/sbv5PUpZa0z+SdKbvPFnL+oePmWsulcnRdOGY/yXaTqpgdPt4QGpU1tn3EBkCmcOziB4=
Received: from CY1PR21MB0087.namprd21.prod.outlook.com (10.161.169.140) by CY1PR21MB0088.namprd21.prod.outlook.com (10.161.169.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1075.0; Wed, 26 Apr 2017 20:40:55 +0000
Received: from CY1PR21MB0087.namprd21.prod.outlook.com ([10.161.169.140]) by CY1PR21MB0087.namprd21.prod.outlook.com ([10.161.169.140]) with mapi id 15.01.1075.000; Wed, 26 Apr 2017 20:40:55 +0000
From: Brian Raymor <Brian.Raymor@microsoft.com>
To: Jim Schaad <ietf@augustcellars.com>, 'Carsten Bormann' <cabo@tzi.org>, 'Christian Amsüss' <c.amsuess@energyharvesting.at>
CC: "draft-ietf-core-coap-tcp-tls@ietf.org" <draft-ietf-core-coap-tcp-tls@ietf.org>, 'core' <core@ietf.org>
Thread-Topic: [core] Is this a typo in -08
Thread-Index: AdK+aQzsAiYCPhiESlGRpkR4uC1l0QAA3+SAAAAc6YAABT5yAAASzE/g
Date: Wed, 26 Apr 2017 20:40:55 +0000
Message-ID: <CY1PR21MB0087829ECB9C38B41CE48DAE83110@CY1PR21MB0087.namprd21.prod.outlook.com>
References: <013c01d2be69$26723c70$7356b550$@augustcellars.com> <20170426090737.joqmfg5alcpi546i@hephaistos.amsuess.com> <068A4DFE-6169-46A0-BBDD-C7583E3C724F@tzi.org> <015d01d2be81$fc3b77a0$f4b266e0$@augustcellars.com>
In-Reply-To: <015d01d2be81$fc3b77a0$f4b266e0$@augustcellars.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: augustcellars.com; dkim=none (message not signed) header.d=none;augustcellars.com; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [174.61.159.182]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY1PR21MB0088; 7:Ym+IddU+u5U1mbHi434UpeijZ+uNYYZ2wM7gFVmu1UOorbPa8IvTZkcG/9bTgw3IIZW0/jAS8WnVw0ip9KuqlGbNIea1uYRcPQzwxhbRlkicAxrNCKiDUpcjacHIiQ27bvKTAuYJ0ys/26PsQmX5ysG0JuW9vlApdzp0f6gEb+YIQQzczDY2I7Xhp2nPrRetH+4/XSgpf6UE7HtzPBbfcjLFhe9Uoa7eSWCHPoc7FhyAYlizIkvkKnrSEpK4cDFD4KTcpyB05d/A7s5nS3yiq+mU3H6+9RxlJQRonsKWVVDWn+ajY1W6Shr50TqLA/KewQ85HktrFkNuymO9NCs2LkLaGK04T2ksazMt22T3Zn0=
x-ms-office365-filtering-correlation-id: 2099bb6a-76ec-47fe-738e-08d48ce489ac
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081); SRVR:CY1PR21MB0088;
x-microsoft-antispam-prvs: <CY1PR21MB00885CD2F000640D415092EC83110@CY1PR21MB0088.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(166708455590820);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040450)(601004)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(6055026)(61426038)(61427038)(6041248)(20161123560025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(20161123562025)(20161123555025)(20161123564025)(6072148); SRVR:CY1PR21MB0088; BCL:0; PCL:0; RULEID:; SRVR:CY1PR21MB0088;
x-forefront-prvs: 0289B6431E
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39840400002)(39450400003)(39400400002)(39410400002)(39860400002)(39850400002)(51444003)(13464003)(24454002)(377454003)(7696004)(99286003)(66066001)(8936002)(189998001)(54906002)(5660300001)(4326008)(55016002)(2950100002)(8990500004)(10290500003)(6116002)(3660700001)(102836003)(122556002)(3846002)(81166006)(3280700002)(86362001)(2906002)(86612001)(5005710100001)(38730400002)(93886004)(6436002)(6506006)(50986999)(54356999)(76176999)(2900100001)(77096006)(229853002)(305945005)(25786009)(53546009)(6246003)(7736002)(53936002)(74316002)(9686003)(33656002)(6306002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR21MB0088; H:CY1PR21MB0087.namprd21.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Apr 2017 20:40:55.4893 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR21MB0088
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/FDqDPrzi_GoB0TQ4PlMSbBUG2tQ>
Subject: Re: [core] Is this a typo in -08
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 20:41:00 -0000

Tracking in https://github.com/core-wg/coap-tcp-tls/issues/143 for coap-tcp-tls-09.

-----Original Message-----
From: Jim Schaad [mailto:ietf@augustcellars.com] 
Sent: Wednesday, April 26, 2017 4:41 AM
To: 'Carsten Bormann' <cabo@tzi.org>; 'Christian Amsüss' <c.amsuess@energyharvesting.at>
Cc: draft-ietf-core-coap-tcp-tls@ietf.org; 'core' <core@ietf.org>
Subject: RE: [core] Is this a typo in -08



-----Original Message-----
From: Carsten Bormann [mailto:cabo@tzi.org] 
Sent: Wednesday, April 26, 2017 2:11 AM
To: Christian Amsüss <c.amsuess@energyharvesting.at>
Cc: Jim Schaad <ietf@augustcellars.com>; draft-ietf-core-coap-tcp-tls@ietf.org; core <core@ietf.org>
Subject: Re: [core] Is this a typo in -08


> On Apr 26, 2017, at 11:07, Christian Amsüss <c.amsuess@energyharvesting.at> wrote:
> 
> On Wed, Apr 26, 2017 at 01:43:14AM -0700, Jim Schaad wrote:
>> In descriptive usage, a BERT Option is interpreted in the same way as
>>   the equivalent Option with SZX == 6, except that the payload is also
>>   allowed to contain a multiple of 1024 bytes (non-final BERT block) or
>>   more than 1024 bytes (final BERT block).
>> 
>> However I think that the last sentence should read "less than 1024 bytes".
> 
> Sounds right to me: It extends what is already permitted for SZX=6, 
> and
> <=1024 is already allowed for final SZX=6 blocks. (In effect, the last 
> BERT block can have any length, only limited by Max-Message-Size).

Yes.

This seems to be the second time that someone stumbles about that wording; maybe we can find a better way to say this.

[JLS] I think I now understand what this text is supposed to be saying.

"except that the payload is also allowed to contain multiple blocks.  For non-final BERT blocks, the payload is always a multiple of 1024 bytes. 
For final BERT blocks, the payload is a multiple (possibly 0) of 1024 bytes plus a  partial block of less than 1024 bytes."

Jim


Grüße, Carsten

v2.29.0 | Report a Bug | By Email | System Status