Re: [TLS] kicking off charter revision discussion

Nico Williams <nico@cryptonector.com> Wed, 31 October 2018 04:12 UTC

Return-Path: <nico@cryptonector.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 521CB1252B7 for <tls@ietfa.amsl.com>; Tue, 30 Oct 2018 21:12:00 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 cDwYUk6-fnIK for <tls@ietfa.amsl.com>; Tue, 30 Oct 2018 21:11:58 -0700 (PDT)
Received: from cichlid.maple.relay.mailchannels.net (cichlid.maple.relay.mailchannels.net [23.83.214.36]) (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 801CA123FFD for <tls@ietf.org>; Tue, 30 Oct 2018 21:11:58 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 72BEF42E36; Wed, 31 Oct 2018 04:11:57 +0000 (UTC)
Received: from pdx1-sub0-mail-a65.g.dreamhost.com (unknown [100.96.20.98]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 3DB7C42E09; Wed, 31 Oct 2018 04:11:57 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a65.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.16.2); Wed, 31 Oct 2018 04:11:57 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Company-Imminent: 3a304db1597140c7_1540959117346_62176054
X-MC-Loop-Signature: 1540959117346:1998110149
X-MC-Ingress-Time: 1540959117346
Received: from pdx1-sub0-mail-a65.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a65.g.dreamhost.com (Postfix) with ESMTP id F3B50805BC; Tue, 30 Oct 2018 21:11:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=FP44+98iCW6VOQ ge/YGVKi+LCjY=; b=YBr7efTk3s2DI4gh7KUmIJB28cP4ri1K0V96XM9oV9trhW lXB7flXH0cNL4od338WHDuRjJ7PhDSa6gEDY0eX/SmR0jcU1teMHS0iHNAxIj+cG RAEzg+4L3J8hM8kLc9H1Gp7tquDSdVTJGA/YwmIxGv1Y3AHS39WWhU1ApEWIU=
Received: from localhost (unknown [24.28.108.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a65.g.dreamhost.com (Postfix) with ESMTPSA id EC398805BD; Tue, 30 Oct 2018 21:11:55 -0700 (PDT)
Date: Tue, 30 Oct 2018 23:11:53 -0500
X-DH-BACKEND: pdx1-sub0-mail-a65
From: Nico Williams <nico@cryptonector.com>
To: Sean Turner <sean@sn3rd.com>
Cc: tls@ietf.org
Message-ID: <20181031041152.GJ2486@localhost>
References: <E94102EF-0F2E-44B1-9B61-94E4702F9FE1@sn3rd.com> <20181030214147.GH2486@localhost> <57A19984-01DC-4620-A931-693647DE9235@sn3rd.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <57A19984-01DC-4620-A931-693647DE9235@sn3rd.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: -100
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedtkedriedugdeilecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucggtfgfnhhsuhgsshgtrhhisggvpdfftffgtefojffquffvnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpeffhffvuffkfhggtggujggfsehttdertddtredvnecuhfhrohhmpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqnecukfhppedvgedrvdekrddutdekrddukeefnecurfgrrhgrmhepmhhouggvpehsmhhtphdphhgvlhhopehlohgtrghlhhhoshhtpdhinhgvthepvdegrddvkedruddtkedrudekfedprhgvthhurhhnqdhprghthheppfhitghoucghihhllhhirghmshcuoehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmqedpmhgrihhlfhhrohhmpehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmpdhnrhgtphhtthhopehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/6UT0ZryPCkBpiSTyHwIYSCWUxbs>
Subject: Re: [TLS] kicking off charter revision discussion
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, 31 Oct 2018 04:12:00 -0000

On Tue, Oct 30, 2018 at 09:53:47PM -0400, Sean Turner wrote:
> > On Oct 30, 2018, at 17:41, Nico Williams <nico@cryptonector.com> wrote:
> > On Wed, Oct 24, 2018 at 08:19:33PM -0400, Sean Turner wrote:
> >> Proposed Charter Text
> > 
> > +1, but see comments below.
> > 
> > First off, suppose we wanted to write a successor to RFC2712 for TLS
> > 1.3, should we pursue that in the TLS WG, or KITTEN WG?  I'm amenable to
> > either, and even both.
> 
> I think both would be bad, but whether it goes in one or the other
> would come down to whether there are enough people interested in doing
> the work.

OK.  I suspect we can get it done in KITTEN WG, where we have the
Kerberos expertise, as it's really just a use of PSK in TLS, so we'd not
need to extend TLS in any way.  I think most here would agree.

> > Should the DANE DNSSEC chain extension be on the charter?  We do need to
> > finish it.
> 
> In the current charter, we already have generic text about extensions
> and no specific text about the DANE DNSSEC draft though we adopted the
> draft and there is a milestone for it.  I prefer not to list every
> draft we are working on in the charter specifically because then we
> have to change the darn charter every time we want to adopt a draft.

Just making sure!

> We are going to spend a lot of time discussing the DANE DNSSEC draft.
> When it gets done and what is in it is certainly up for discussion.

Indeed.

Thanks,

Nico
--