Re: [Uta] Warren Kumari's Discuss on draft-ietf-uta-smtp-tlsrpt-18: (with DISCUSS)

Viktor Dukhovni <ietf-dane@dukhovni.org> Mon, 16 April 2018 18:09 UTC

Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: uta@ietfa.amsl.com
Delivered-To: uta@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31D4A12D878; Mon, 16 Apr 2018 11:09:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 ikawAag4HxE5; Mon, 16 Apr 2018 11:09:02 -0700 (PDT)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [108.5.242.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B785127909; Mon, 16 Apr 2018 11:09:02 -0700 (PDT)
Received: from [10.200.0.109] (unknown [8.2.105.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id 9E5087A3309; Mon, 16 Apr 2018 18:09:01 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <152390148995.19628.3324657199992839201.idtracker@ietfa.amsl.com>
Date: Mon, 16 Apr 2018 14:08:29 -0400
Cc: The IESG <iesg@ietf.org>, uta@ietf.org, uta-chairs@ietf.org, draft-ietf-uta-smtp-tlsrpt@ietf.org, valery@smyslov.net, Leif Johansson <leifj@sunet.se>
Content-Transfer-Encoding: quoted-printable
Message-Id: <68D7C0C4-7E57-4742-BCE6-671621DFCE2E@dukhovni.org>
References: <152390148995.19628.3324657199992839201.idtracker@ietfa.amsl.com>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/uta/StqGPat7OHoLCJQvccHDyayum1o>
Subject: Re: [Uta] Warren Kumari's Discuss on draft-ietf-uta-smtp-tlsrpt-18: (with DISCUSS)
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: UTA working group mailing list <uta.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uta>, <mailto:uta-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uta/>
List-Post: <mailto:uta@ietf.org>
List-Help: <mailto:uta-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uta>, <mailto:uta-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2018 18:09:06 -0000


> On Apr 16, 2018, at 1:58 PM, Warren Kumari <warren@kumari.net> wrote:
> 
> I throw away the one that contains 'bar', fair enough, got it. What I don't
> understand is what a record would look like which is a single record (#2), but
> that contains multiple strings (#3). Can you provide an example of a TXT record
> with multiple strings? I don't *think* that this is just me being dense, and so
> I think that the document needs to better explain this / include the example.

Strings in TXT records have a single-octet length field. When returning a longer
string, or when one wants to explicitly segment a TXT RDATA into multiple strings
one returns:

	txt.example. IN TXT "first string" "second string" ... "last string"

with the wire RDATA being:

	<len1>first string<len2>second string...<lenN>last string

-- 
	Viktor.