[TLS] TLS Next Proto Negotiation

gswaru@rediffmail.com Mon, 05 September 2011 04:23 UTC

Return-Path: <gswaru@rediffmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 3CC4821F877B for <tls@ietfa.amsl.com>; Sun, 4 Sep 2011 21:23:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.385
X-Spam-Level: ****
X-Spam-Status: No, score=4.385 tagged_above=-999 required=5 tests=[AWL=-1.033, BAYES_80=2, HTML_IMAGE_ONLY_12=2.46, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MSGID_FROM_MTA_HEADER=0.803, SARE_SUB_ENC_UTF8=0.152, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Dl9Ynvz6yQCA for <tls@ietfa.amsl.com>; Sun, 4 Sep 2011 21:23:34 -0700 (PDT)
Received: from rediffmail.com (f4mail-235-128.rediffmail.com []) by ietfa.amsl.com (Postfix) with SMTP id D664021F8760 for <tls@ietf.org>; Sun, 4 Sep 2011 21:23:33 -0700 (PDT)
Received: (qmail 32581 invoked by uid 510); 5 Sep 2011 04:25:13 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=redf; d=rediffmail.com; b=UymliGClxpVAY0WmC28eoDeeqkdS5rbkgJnmAT25jH5BOZDuo0RRiqbpRL5qf0lFxgF10H5LooZhf8SmVKwgCpD031FhNMGaq2clPsK+w78RNij9Ee2eq/qT1+f2QN7NpUQBLe+CgVbOabAhL0kO5KihVYbY7Nmoj5GSdpzSKx0= ;
x-m-msg: asd54ad564ad7aa6sd5as6d5; a6da7d6asas6dasd77; 5dad65ad5sd;
X-CTCH-Spam: Unknown
X-CTCH-VOD: Unknown
X-CTCH-Flags: : 0
X-CTCH-RefID: str=0001.0A150204.4E644F2A.0037,ss=1,re=0.000,fgs=0
Date: 5 Sep 2011 04:25:13 -0000
Message-ID: <20110905042513.32561.qmail@f4mail-235-128.rediffmail.com>
MIME-Version: 1.0
To: "tls@ietf.org" <tls@ietf.org>, "Adam Langley " <agl@google.com>
Received: from unknown by rediffmail.com via HTTP; 05 Sep 2011 04:25:11 -0000
Sender: gswaru@rediffmail.com
From: gswaru@rediffmail.com
Content-Type: multipart/alternative; boundary="=_4c1c30d38231572bfa7fd0edd28a7344"
Subject: [TLS] =?utf-8?q?TLS_Next_Proto_Negotiation?=
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: gswaru@rediffmail.com
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: <http://www.ietf.org/mail-archive/web/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: Mon, 05 Sep 2011 04:23:35 -0000

Thanks Adam, for confirming that we need to use the Next Protocol handshake message in plain for FINISH computation. Now that this message is 32 byte padded, do we need to use the padbytes also for finish calcualtion or use only the message until padbytes only.
Thanks and Regards,