IETF Logo Mail Archive

Re: [COSE] Comments on draft-ietf-cose-rfc8152bis-struct-07 and draft-ietf-cose-rfc8152bis-algs-06

Carsten Bormann <cabo@tzi.org> Tue, 03 December 2019 08:30 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: cose@ietfa.amsl.com
Delivered-To: cose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AF02120180 for <cose@ietfa.amsl.com>; Tue, 3 Dec 2019 00:30:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 mLn-ITzGJ6b2 for <cose@ietfa.amsl.com>; Tue, 3 Dec 2019 00:30:36 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8D1A120131 for <cose@ietf.org>; Tue, 3 Dec 2019 00:30:35 -0800 (PST)
Received: from [192.168.217.116] (p548DC893.dip0.t-ipconnect.de [84.141.200.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 47RwCs6gVzz160x; Tue, 3 Dec 2019 09:30:33 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <01bd01d5a9a1$e6481490$b2d83db0$@augustcellars.com>
Date: Tue, 03 Dec 2019 09:30:37 +0100
Cc: John Mattsson <john.mattsson=40ericsson.com@dmarc.ietf.org>, cose@ietf.org
X-Mao-Original-Outgoing-Id: 597054634.572926-428fe4bf86b86b2fc4d92726ebe5757e
Content-Transfer-Encoding: quoted-printable
Message-Id: <BBE6DEF9-3FC0-4DF9-B37E-8EF69BBAB108@tzi.org>
References: <E1082983-0F56-47BA-A548-7920F8AEDD95@ericsson.com> <01bd01d5a9a1$e6481490$b2d83db0$@augustcellars.com>
To: Jim Schaad <ietf@augustcellars.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/h7DbaRL0PSH48UfBlJ62NzDuH9U>
Subject: Re: [COSE] Comments on draft-ietf-cose-rfc8152bis-struct-07 and draft-ietf-cose-rfc8152bis-algs-06
X-BeenThere: cose@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CBOR Object Signing and Encryption <cose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cose>, <mailto:cose-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cose/>
List-Post: <mailto:cose@ietf.org>
List-Help: <mailto:cose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cose>, <mailto:cose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Dec 2019 08:30:38 -0000

On Dec 3, 2019, at 07:21, Jim Schaad <ietf@augustcellars.com> wrote:
> 
> [JLS] I just went through the document again and made sure that I was consistent.  I am always using either "byte string" or "string".  The latter is used for text strings.  I am not sure that 

(I’m not sure what you wanted to say what you aren’t sure of…
The sentence didn’t finish.)

I’m also in favor of being specific and saying “byte string” or “text string”.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email