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

Nick Hilliard <nick@foobar.org> Fri, 04 January 2019 15:17 UTC

Return-Path: <nick@foobar.org>
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 DBBA9130DC1 for <sidrops@ietfa.amsl.com>; Fri, 4 Jan 2019 07:17:02 -0800 (PST)
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 XewI2LDzo8UN for <sidrops@ietfa.amsl.com>; Fri, 4 Jan 2019 07:17:00 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15876130934 for <sidrops@ietf.org>; Fri, 4 Jan 2019 07:16:59 -0800 (PST)
X-Envelope-To: sidrops@ietf.org
Received: from [IPv6:2a02:8084:2861:d680:9858:87dc:9299:2d6d] ([IPv6:2a02:8084:2861:d680:9858:87dc:9299:2d6d]) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id x04FGoFj094286 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Jan 2019 15:16:57 GMT (envelope-from nick@foobar.org)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Nick Hilliard <nick@foobar.org>
X-Mailer: iPhone Mail (16C101)
In-Reply-To: <A2D26666-46CE-4272-8F9F-9DAB1359F9CF@nlnetlabs.nl>
Date: Fri, 4 Jan 2019 15:16:50 +0000
Cc: SIDR Operations WG <sidrops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3D9C4CAD-5D82-4E6C-A28F-C2444E6DCC7A@foobar.org>
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> <20181220160248.204fa146@glaurung.nlnetlabs.nl> <A2D26666-46CE-4272-8F9F-9DAB1359F9CF@nlnetlabs.nl>
To: Tim Bruijnzeels <tim@nlnetlabs.nl>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/OgMjJyQ_TBh2DLquU5_ewNH2w0s>
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: Fri, 04 Jan 2019 15:17:03 -0000

No objection.

Nick

Sent from my iWotsit.

> On 4 Jan 2019, at 15:08, Tim Bruijnzeels <tim@nlnetlabs.nl> wrote:
> 
> Hi all,
> 
> Any objections to me making the following changes?
> * remove the blank line after the comments
> * no longer allow data to be used when TLS verification fails (MUST NOT..)
> 
> I would really appreciate some voices pro / con, and then spin a hopefully final version asap that I can ask last call on, again.
> 
> Tim
> 
> 
>> On 20 Dec 2018, at 16:02, Martin Hoffmann <martin@opennetlabs.com> wrote:
>> 
>> 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
>> 
>> _______________________________________________
>> Sidrops mailing list
>> Sidrops@ietf.org
>> https://www.ietf.org/mailman/listinfo/sidrops
> 
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops
>