Re: [TLS] Expanding the alert space

Nikos Mavrogiannopoulos <nmav@gnutls.org> Thu, 06 July 2006 13:20 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FyTml-00068R-AX; Thu, 06 Jul 2006 09:20:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FyTmj-00068K-Nu for tls@lists.ietf.org; Thu, 06 Jul 2006 09:20:49 -0400
Received: from ug-out-1314.google.com ([66.249.92.171]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyTmi-0004N6-F0 for tls@lists.ietf.org; Thu, 06 Jul 2006 09:20:49 -0400
Received: by ug-out-1314.google.com with SMTP id m3so288864uge for <tls@lists.ietf.org>; Thu, 06 Jul 2006 06:20:47 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:user-agent:references:in-reply-to:mime-version:content-disposition:date:content-type:content-transfer-encoding:message-id:sender; b=R8xKIQozUqQzbH8ghhgzIF4ujJTd+7hCBKKTG2khVonhed89iDTWk5u4DHw7UvCipxQ2FGo6xQlWSRE5tFL/HTI0rGHgCYfaQuiM53mESP0wMxczswGLsiwgyftgRuSIjSoAwLRMz/tpSu+fAd7KaTFUVJGnxGg2jBypnzgsY5c=
Received: by 10.67.89.5 with SMTP id r5mr702709ugl; Thu, 06 Jul 2006 06:20:47 -0700 (PDT)
Received: from ?172.16.1.196? ( [81.175.93.238]) by mx.gmail.com with ESMTP id y1sm729841uge.2006.07.06.06.20.46; Thu, 06 Jul 2006 06:20:47 -0700 (PDT)
From: Nikos Mavrogiannopoulos <nmav@gnutls.org>
To: tls@lists.ietf.org
Subject: Re: [TLS] Expanding the alert space
User-Agent: KMail/1.9.1
References: <20060705140425.B4687222425@laser.networkresonance.com>
In-Reply-To: <20060705140425.B4687222425@laser.networkresonance.com>
MIME-Version: 1.0
Content-Disposition: inline
Date: Thu, 6 Jul 2006 15:20:45 +0200
Content-Type: text/plain; charset="iso-8859-7"
Content-Transfer-Encoding: 7bit
Message-Id: <200607061520.45640.nmav@gnutls.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
X-BeenThere: tls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/tls>
List-Post: <mailto:tls@lists.ietf.org>
List-Help: <mailto:tls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=subscribe>
Errors-To: tls-bounces@lists.ietf.org

On Wed 05 Jul 2006 15:56, Eric Rescorla wrote:
> I've noticed lately that people seem to want to define a lot of new
> TLS alerts. What would people think about expanding the alert space
> in 1.2? 16 bits enough? I've considered a few times having a freeform
> string field as well that could be used to report errors in detail
> for debugging, but maybe that's too clever.

I am scared of a freeform string, because in the end it would
need to handle internationalization (because somebody will think it's 
usefull information to print to the user) etc etc... thus we might
later need a TLS extension to specify the language, encodings and so on.
It might be too much for such a protocol!

About the extension to 16bit... I'm not totally against, but unless TLS 
1.2 is significantly different[0] than 1.1, I wouldn't go for it.


[0]. In the sense that if there too many incompatible changes, one more 
doesn't harm :)

regards,
Nikos


_______________________________________________
TLS mailing list
TLS@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls