Re: [TLS] Proposed text for removing renegotiation

Martin Thomson <> Wed, 28 May 2014 22:45 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 2973B1A0721 for <>; Wed, 28 May 2014 15:45:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id n-pXZFu5Vkjo for <>; Wed, 28 May 2014 15:45:24 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:400c:c00::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C16D71A071D for <>; Wed, 28 May 2014 15:45:23 -0700 (PDT)
Received: by with SMTP id x12so11821652wgg.33 for <>; Wed, 28 May 2014 15:45:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YUOZQL9eCnvA/Py01+UgEL/O1Np7kh3KogpMXvAe0lM=; b=HfrH8Qz30QjDkN1TFgrrEXUyF7DjNl0Azq1nKTDeOxiYDq+LE9YJxQSsc9nBaTyFSw qSAAViveEzzqLQJJMRSk32jNyAF71rdccNPxdj2Bl7mPfE+FzFl6PzrFfIALpFurTxZ+ Cwzho022Gnc3qXj5/tLIioOP/cF/0zS3ADkJubjP8cQ67tveHkpoulk3IzFbgoBPJKLH y/Kv0YDUR+iBR/6T2D/gLXn0NEWmjPR09Qc1jOo44tciR2UPRpIJRohthSvXC9ZZH9d8 6Qlelumwy83+yR5Ct589h8Fz8L6OItEpZem2kQQdCyR58zp/pyfnPJoPYx6kqwh62/6x nw4A==
MIME-Version: 1.0
X-Received: by with SMTP id oy1mr3787071wjb.87.1401317119018; Wed, 28 May 2014 15:45:19 -0700 (PDT)
Received: by with HTTP; Wed, 28 May 2014 15:45:18 -0700 (PDT)
In-Reply-To: <m2vbspv8w1.fsf@localhost.localdomain>
References: <> <> <> <m2vbspv8w1.fsf@localhost.localdomain>
Date: Wed, 28 May 2014 15:45:18 -0700
Message-ID: <>
From: Martin Thomson <>
To: Geoffrey Keating <>
Content-Type: text/plain; charset="UTF-8"
Cc: "" <>
Subject: Re: [TLS] Proposed text for removing renegotiation
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 28 May 2014 22:45:25 -0000

On 28 May 2014 15:25, Geoffrey Keating <> wrote:
> I think this should be handled by TLS, not by having the application
> request rekeying or renegotiation.  If TLS handles it, I don't see why
> there's a need for a special 'renegotiate' or 'change key' message; it
> can quietly change the key when the appropriate limit is hit.

I wasn't proposing that the application be in control of when rekeying
occurs.  (Yes, if an app needs an explicit break in continuity, then
opening a new connection is a perfectly reasonable way to achieve that

Yes, you could just roll on through, identify a point where rekeying
is necessary and automatically do it.  That's even more aggressively
spartan than what I've proposed.

A message enables more than just necessary rekeying.  It also allows
for read and write states to be kept in sync.

It also means that you don't have to go to great lengths to contrive a
rekeying scenario in your testing.  I certainly don't want rekeying to
be rare enough that it breaks the first time that it ever actually
happens.  That's a surefire plan for backup generator syndrome.