IETF Logo Mail Archive

Re: [TLS] consensus call: draft-ietf-tls-ticketrequests

Sean Turner <sean@sn3rd.com> Wed, 04 March 2020 21:03 UTC

Return-Path: <sean@sn3rd.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EAA63A089C for <tls@ietfa.amsl.com>; Wed, 4 Mar 2020 13:03:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.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 Y4-JQKo6tAIs for <tls@ietfa.amsl.com>; Wed, 4 Mar 2020 13:03:36 -0800 (PST)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (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 6FEE93A0898 for <tls@ietf.org>; Wed, 4 Mar 2020 13:03:36 -0800 (PST)
Received: by mail-qt1-x82b.google.com with SMTP id l21so2506823qtr.8 for <tls@ietf.org>; Wed, 04 Mar 2020 13:03:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=9JB5kpT6NtEL6HDq37dgNUMf4Wq3aTKaNFQDRLnfuRE=; b=EUG9PIdrvCpfj1BG3zUNsZaYraRT0pj/rp8mcpD5hy/x19tR/OmaP+SaLhddPFXrKS 29+ha0d/iVjMGKdE3H7TAoefGatka8SurfO6b1v6oN1SktITwbfIcBVw6ifRHgnU830P Pa80uikOd+DM5WLymkMNik9dWc+Kkj1lIzzsc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=9JB5kpT6NtEL6HDq37dgNUMf4Wq3aTKaNFQDRLnfuRE=; b=hpvxIfxdW+hBWE4IseyFfroY8IMo97e3uN2DhN3usbPOOZmDQ80PEEn+9hQZAFD9ni ummNH8+3eXIeYNntD1LraXQ1lKZL0jM2vFcJq9MXdDfRsYtqpurx2GEYGLHxQiGCf9wt 4UumAAq09O8BOsIDTzUCCDvErREu035o2UclZzY5ke0kyGQOQ9ZVmQ8R8cHleDw3jxF8 XihJH0rDz2LOwCUyDE38Wo4d26MnoR0SVrYkAkJljnUtL2BwEM3jW7syUV2iN+LsoEEa TbX62pNlsrlkLZeCWndvZVFuLwGbfVDqkhND8DN8UdSD2MJ7NEbt6yQvj/ATChLiNcsr rICA==
X-Gm-Message-State: ANhLgQ3oB8MY/ccKjqlMc5DD5yyTZcZ8yg4EEvxd7u/1DdH8LJxosDfZ jFL/GJBvdLEoE8iMYAuVxeuroH+7DPs=
X-Google-Smtp-Source: ADFU+vsMrHjbJ8VSFtiFOmhGGt8z9VO04SeeNgiiywvLZvgiiJBAXmdIAqlRCAwIoODBconYVC0G5A==
X-Received: by 2002:ac8:47d9:: with SMTP id d25mr4245323qtr.134.1583355815368; Wed, 04 Mar 2020 13:03:35 -0800 (PST)
Received: from sn3rd.lan ([75.102.131.34]) by smtp.gmail.com with ESMTPSA id 11sm14179851qko.76.2020.03.04.13.03.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Mar 2020 13:03:34 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <20200304204334.GP18021@localhost>
Date: Wed, 04 Mar 2020 16:03:33 -0500
Cc: TLS List <tls@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <21913C56-AA8B-4C91-9071-E440059677D9@sn3rd.com>
References: <4E07012F-AB53-4727-A309-D8A15222A433@sn3rd.com> <0E7E2E43-CC46-488E-981E-BF8417821D85@sn3rd.com> <D661BFB4-6B07-4519-BEFD-754F9460768C@akamai.com> <20200304201520.GO18021@localhost> <E540459B-9287-41EB-8F23-2E9C3E6ECE71@sn3rd.com> <20200304204334.GP18021@localhost>
To: Nico Williams <nico@cryptonector.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/XUHywKwaNvQ6C-sKYyIAr7tFboo>
Subject: Re: [TLS] consensus call: draft-ietf-tls-ticketrequests
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2020 21:03:41 -0000


> On Mar 4, 2020, at 15:43, Nico Williams <nico@cryptonector.com> wrote:
> 
> On Wed, Mar 04, 2020 at 03:22:33PM -0500, Sean Turner wrote:
>>> On Mar 4, 2020, at 15:15, Nico Williams <nico@cryptonector.com> wrote:
>>> On Wed, Mar 04, 2020 at 05:09:35PM +0000, Salz, Rich wrote:
>>>>>   Must the ticket reuse use case be addresses
>>>>    in draft-ietf-tls-ticketrequests?
>>> 
>>> I'm missing this post in my inbox, so I shall reply to Rich Salz's
>>> reply.  Thanks for having this LC.
>> 
>> I forwarded it directly to you.
> 
> Ah, it had landed in my spam folder.  Thanks.
> 
>>> Can we also ask why or why not?  Of course, some of us have already
>>> explained our positions, but I am interested in the rationales for any
>>> new yes/no/don't-cares.
>> 
>> If people have something new reason to add sure, but I would rather
>> not rehash all the previous emails.
> 
> Certainly anyone voicing new opinions should provide a rationale.
> 
> That's part of how we find consensus.  We're not counting votes.
> 
> Nico
> -- 

Nico,

Luckily we’re not just counting votes.

People are free to add, as they way more often than not do, as much rationale as they would like. They can add their own personal rationale, refer to another already provided, or not.

spt

v2.23.0 | Report a Bug | By Email