[TLS] Expanding the alert space

Eric Rescorla <ekr@networkresonance.com> Wed, 05 July 2006 13:56 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fy7rc-0004Z3-BS; Wed, 05 Jul 2006 09:56:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fy7rb-0004Yy-Ga for tls@ietf.org; Wed, 05 Jul 2006 09:56:23 -0400
Received: from laser.networkresonance.com ([198.144.196.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fy7ra-00040H-7e for tls@ietf.org; Wed, 05 Jul 2006 09:56:23 -0400
Received: from networkresonance.com (raman.networkresonance.com [198.144.196.3]) by laser.networkresonance.com (Postfix) with ESMTP id B4687222425 for <tls@ietf.org>; Wed, 5 Jul 2006 07:04:25 -0700 (PDT)
To: tls@ietf.org
X-Mailer: MH-E 7.4.3; nmh 1.0.4; XEmacs 21.4 (patch 19)
Date: Wed, 05 Jul 2006 06:56:16 -0700
From: Eric Rescorla <ekr@networkresonance.com>
Message-Id: <20060705140425.B4687222425@laser.networkresonance.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Cc:
Subject: [TLS] Expanding the alert space
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

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.

Thoughts?
-Ekr

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