[TLS] TLS Next Proto negotiation

gswaru@rediffmail.com Mon, 18 July 2011 12: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 3F33021F8BA1 for <tls@ietfa.amsl.com>; Mon, 18 Jul 2011 05:23:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.263
X-Spam-Level: ***
X-Spam-Status: No, score=3.263 tagged_above=-999 required=5 tests=[AWL=0.178, BAYES_50=0.001, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_2=0.001, J_CHICKENPOX_65=0.6, 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 H-fRuKe+8mih for <tls@ietfa.amsl.com>; Mon, 18 Jul 2011 05:23:04 -0700 (PDT)
Received: from rediffmail.com (f4mail-235-121.rediffmail.com []) by ietfa.amsl.com (Postfix) with SMTP id F1F9C21F8686 for <tls@ietf.org>; Mon, 18 Jul 2011 05:23:03 -0700 (PDT)
Received: (qmail 9005 invoked by uid 510); 18 Jul 2011 12:22:59 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=redf; d=rediffmail.com; b=M01PS7uAz27toRU4A+Ay/f5CpDYGBA7f7lt6wow/xaPzO4LtNgZxbnD30qZQTW4GCy1vp1OJafDgr/kPIvGvqODj8DhaC8TW0bzBnEmBnfblyoG71sRE7HY6UI9QMdKT0tLsdu5v11LZRcS6RFjJXpYEw6WGSlFuplxF1SmY/Tg= ;
x-m-msg: asd54ad564ad7aa6sd5as6d5; a6da7d6asas6dasd77; 5dad65ad5sd;
Date: 18 Jul 2011 12:22:59 -0000
Message-ID: <20110718122259.8995.qmail@f4mail-235-121.rediffmail.com>
MIME-Version: 1.0
To: "tls " <tls@ietf.org>
Received: from unknown by rediffmail.com via HTTP; 18 Jul 2011 12:22:59 -0000
Sender: gswaru@rediffmail.com
From: gswaru@rediffmail.com
Content-Type: multipart/alternative; boundary="=_2f247820b0f58a8402c34f75cb15e683"
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, 18 Jul 2011 12:23:09 -0000

I have gone the TLS NPN draft, it talks about the new handshake message Next Protocol handshake message which is sent from Client to server after Change cipher spec and before Finish. But when I capture the packet with NPN enable(using google chrome to browse google web services), I find NULL NPN extnesion is sent from client to server and server is responding back with NPN extension with the protocol. But there is no next protocol handshake message sent by client after change cipher spec, instead I see a strange encrypted packet from Server side even before server is sending change cipher spec, this is on new session.
Can some one help me on understanding the next protocol handshake message, the format and other details, of whether it is encrypted/decrypted. or provide me a packet cpature with has these details.
Thanks and Regards,