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

Christopher Morrow <christopher.morrow@gmail.com> Tue, 26 February 2019 06:26 UTC

Return-Path: <christopher.morrow@gmail.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 E9FBD130E77 for <sidrops@ietfa.amsl.com>; Mon, 25 Feb 2019 22:26:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 dJp6WSl_rG8n for <sidrops@ietfa.amsl.com>; Mon, 25 Feb 2019 22:26:44 -0800 (PST)
Received: from mail-it1-x132.google.com (mail-it1-x132.google.com [IPv6:2607:f8b0:4864:20::132]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13A751295EC for <sidrops@ietf.org>; Mon, 25 Feb 2019 22:26:44 -0800 (PST)
Received: by mail-it1-x132.google.com with SMTP id v83so2477086itf.1 for <sidrops@ietf.org>; Mon, 25 Feb 2019 22:26:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=IplKy9AEj6sHkLYtfKdPshESTYUJPWVDLo3od+fZl6k=; b=fRwoKPmgElx7vcN8CXCYiSzvMSdppEOM0u7U/M6lp77oOC8LdnMwobLn9RJPvo6aA6 0Rt8lFDdU/TCxyWhqHezjC9s40slgpr6Qoiq0v9owjzzXLYRGeHLRfDB8DSkGs0GkBmX qJHpe8oHA/CTGHlx3WOlsXn7ynOBp8bPpoGYrPP1649Hnh9D2I8nykv3nP2YpDeLt0BV HFx1YMbOlE9I4JyNidOoiCaD+TYz6fF2+SKp+yit9jfCJL6vAzg8PsKvEg545Klf2kYQ X4lfELC5LNHyTTHklc0xy+RL4r+DSaHwWh9nxY22NhEN8SJUfHCZP7yytiMx6A2sBfBv HVkg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IplKy9AEj6sHkLYtfKdPshESTYUJPWVDLo3od+fZl6k=; b=ZtLfyQoLt/N5pv25FpkSEVnNaT8DC/diJfV5ktiwMtYyoH8Gf6K8YB1DeOffShF0bh qz+TNFrVQqz5XazYKLG/guFL/EqiYqpCJNLN2I6y9rk8GSL2vo19cxdp0uARWRKZ+vpG eYJuc/SONegwFN+NbxUs2lruiePs8fARqmVB/06iyijsgwyjHDesW4RYtmnpwmOgD2/u xIX6++plEqQeSWh2t7gram7XgCdZkUd5Iue80dX3e5d0hP91Sib6USE1hzX1F0INgimx +2EgZLvjOmor+fhHkCYM6vgRWCa+JmGQCYqu4MdzURNHpGNDC/LqVeQQytsmmueKvS7E WTXw==
X-Gm-Message-State: AHQUAuYaiKP86Uqni10hA+iauMXUiHyIJlgT+IQ7LLa31m0P4xo/5fOx olvSR/porNvmDePYWEscUaQozcl9RdRdh3XjMOle/g==
X-Google-Smtp-Source: AHgI3IbGHdi06jVCrwrqDVjJ3ryO5ailFXLnCfcimyNUYWUG3OpUogUe7Ts+xgN5II9jE4DaTMKL0Z37eQDF5BJk+/U=
X-Received: by 2002:a02:745:: with SMTP id f66mr12426999jaf.137.1551162402990; Mon, 25 Feb 2019 22:26:42 -0800 (PST)
MIME-Version: 1.0
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> <3D9C4CAD-5D82-4E6C-A28F-C2444E6DCC7A@foobar.org>
In-Reply-To: <3D9C4CAD-5D82-4E6C-A28F-C2444E6DCC7A@foobar.org>
From: Christopher Morrow <christopher.morrow@gmail.com>
Date: Tue, 26 Feb 2019 01:26:31 -0500
Message-ID: <CAL9jLabyVEK-_C+3qYPZAc2UdxtX_Hr=gVnE67MEK4HOotNKeQ@mail.gmail.com>
To: Nick Hilliard <nick@foobar.org>
Cc: Tim Bruijnzeels <tim@nlnetlabs.nl>, SIDR Operations WG <sidrops@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000004f4320582c62413"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/XaRJVW54PtqQWxutaLnNT25A8_c>
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: Tue, 26 Feb 2019 06:26:47 -0000

Howdy! Time went by, it's not november but it seems like people support and
don't not-support this.
I've questions for the authors and then we can push this up the hill to the
IESG folks.

thanks!
-chris

On Fri, Jan 4, 2019 at 10:17 AM Nick Hilliard <nick@foobar.org>; wrote:

> 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
> >
>
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops
>