Re: [Sidrops] WGLC: draft-ietf-sidrops-https-tal - ENDS Nov 26 2018 (11/26/2018)

Martin Hoffmann <martin@opennetlabs.com> Thu, 20 December 2018 15:02 UTC

Return-Path: <martin@opennetlabs.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0621B130E11 for <sidrops@ietfa.amsl.com>; Thu, 20 Dec 2018 07:02:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.878
X-Spam-Level:
X-Spam-Status: No, score=-5.878 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_HI=-5, URIBL_BLOCKED=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 2va3qfhK-EGX for <sidrops@ietfa.amsl.com>; Thu, 20 Dec 2018 07:02:52 -0800 (PST)
Received: from dicht.nlnetlabs.nl (dicht.nlnetlabs.nl [185.49.140.10]) (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 6778D1271FF for <sidrops@ietf.org>; Thu, 20 Dec 2018 07:02:51 -0800 (PST)
Received: from glaurung.nlnetlabs.nl (unknown [IPv6:2a04:b900:0:1:a2c5:89ff:feb5:e311]) by dicht.nlnetlabs.nl (Postfix) with ESMTPSA id ADF4E25885 for <sidrops@ietf.org>; Thu, 20 Dec 2018 16:02:48 +0100 (CET)
Authentication-Results: dicht.nlnetlabs.nl; dmarc=none (p=none dis=none) header.from=opennetlabs.com
Date: Thu, 20 Dec 2018 16:02:48 +0100
From: Martin Hoffmann <martin@opennetlabs.com>
Cc: SIDR Operations WG <sidrops@ietf.org>
Message-ID: <20181220160248.204fa146@glaurung.nlnetlabs.nl>
In-Reply-To: <0FD77962-7633-4B34-BBFE-42A668498E2B@nlnetlabs.nl>
References: <CAL9jLaZCqPnL_-gf3KV4fxWCa7hZuBkhyZDOkAqa=_s1sj7Mzg@mail.gmail.com> <0403D83D-7886-4E49-873A-78181A8BCFA4@nlnetlabs.nl> <CACWOCC8veqMgKjgaFp6Fg_q0E4Qo=jj-aWTnfu2AkeXDjK6FSw@mail.gmail.com> <0FD77962-7633-4B34-BBFE-42A668498E2B@nlnetlabs.nl>
Organization: Open Netlabs
X-Mailer: Claws Mail 3.17.1 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/-SxcLew_MwRGOviHklJBOfh2aBI>
Subject: Re: [Sidrops] WGLC: draft-ietf-sidrops-https-tal - ENDS Nov 26 2018 (11/26/2018)
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Dec 2018 15:02:55 -0000

Tim Bruijnzeels wrote:
> On 17 Dec 2018, at 17:14, Job Snijders <job@ntt.net> wrote:
> > 
> > Section 2.1 "ASCII" should probably be UTF-8, this is 2018 and we
> > are the IETF  
> 
> So, the machines will most likely ignore this anyway. I guess that
> UTF-8 should be okay, provided we restrict the allowed line breaks to
> <CRLF> or <LF> for these lines as well. So maybe rephrase:
> 
> Current:
> 
>    1.  an optional comment section consisting of one or more lines
>        starting with the '#' character, containing human readable
>        informational ASCII text, followed by an empty line using a
>        "<CRLF>" or "<LF>" line break only.
> 
> New:
> 
>    1.  an optional comment section consisting of one or more lines
>        starting with the '#' character, containing human readable
>        informational UTF-8 text, and ending with a "<CRLF>" or 
>        "<LF>" line break. Followed by an empty line using a
>        "<CRLF>" or "<LF>" line break only.

I don’t quite see why the empty line after the comment is necessary at
all. Since all the comment lines start with a hash, the end of the
comment section can be identified by the first line not starting with a
hash.

Kind regards,
Martin