TLS 1.3). The supported_versions extension is omitted from
ClientHello.extensions and reconstructed in the transcript as a
single-valued list with the specified value. The
supported_versions extension is omitted from
ClientHello.extensions and reconstructed in the transcript with
the specified
1002 |
+--+
A new version of I-D, draft-rashok-tls-ticket-request-msg-01.txt
has been successfully submitted by Raja Ashok and posted to the
IETF repository.
Name: draft-rashok-tls-ticket-request-msg
Revision: 01
Title: TLS Ticket Request Message
Document date: 20
Hi All,
https://tools.ietf.org/html/draft-rashok-tls-ticket-request-msg-00
I am keen on improving this specification, so requesting all to provide
feedback on this.
Thanks & Regards,
Raja Ashok
This seems to be solving a very similar problem to
> draft-ietf-tls-ticketrequests (which I
r my understanding RFC8446 says a TLSv1.3 server should send session
ticket immediately after handshake. Even if it can delay, it will be very
difficult to identify how long it should delay sending session ticket by
prioritizing application data.
Thanks & Regards,
Raja Ashok
___
Hi All,
Requesting to go through this draft and provide your views on it.
Thanks & Regards,
Raja Ashok
-- Forwarded message -
From:
Date: Fri 20 Dec, 2019, 7:03 AM
Subject: New Version Notification for
draft-rashok-tls-ticket-request-msg-00.txt
To: Raja Ashok
A new ver
[Company_logo]
Raja Ashok V K
Huawei Technologies
Bangalore, India
http://www.huawei.com
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
This e-mail and its attachments contain confidential
not feasible, as in future if new named curves are defined then updating legacy
server is not easy. And also constraint (D)TLS server generally doesn't support
all the curves.
Please provide your suggestion on this. If my understanding is wrong, please
correct me.
Regards,
Ashok
_
r comments on this suggestion.
Regards,
Ashok
________
[Company_logo]
Raja Ashok V K
Huawei Technologies
Bangalore, India
http://www.huawei.com
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
This e
Hi Victor & Alessandro,
I have gone through the draft and I am having a doubt.
> The extension only affects the Certificate message from the server.
> It does not change the format of the Certificate message sent by the
> client.
This draft provides a mechanism to compress only the server
the message is not received, then client has
to retransmit its previous flight (CKE, CCS and FM) otherwise server wont
retransmit its message.
Regards,
Ashok
[Company_logo]
Raja Ashok V K
Huawei Technologies
Bangalore, India
http://www.huawei.com
version of this document.
I am requesting other members of this group also to look into and provide
comments for further improvements.
Regards,
Raja Ashok V K
Huawei Technologies
Bangalore, India
http://www.huawei.com
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发
Hi David & Nikos,
3rd version of the draft-jay-tls-psk-identity-extension has been submitted.
Your valuable comments are also fixed.
Please go through once and provide me your suggestion.
@Andreas : Requesting you also to go through and provide your suggestion.
Raja Ashok V K
Hu
the current IoT world needs this kind of new extension. This is the time
to do.
Regards,
Ashok
Raja Ashok VK
华为技术有限公司 Huawei Technologies Co., Ltd.
[Company_logo]
Phone:
Fax:
Mobile:
Email:
地址：深圳市龙岗区坂田华为基地 邮编：518129
Huawei Technologies Co., Ltd.
Bantian
I feel we can go ahead with TLS 1.3.
Or else TLS 3.4, because anyway we send 0x0304 on wire for TLS 1.3.
I hope all other three options (TLS 2.0, TLS 2 and TLS 4) will make confusion
with SSL versions for end user.
Raja Ashok VK
华为技术有限公司 Huawei Technologies
Hi Andreas,
Last week received some comments from Ilari and David. We are working on the
next version of this draft. We will upload it soon.
Regards,
Ashok
Raja Ashok VK
华为技术有限公司 Huawei Technologies Co., Ltd.
[Company_logo]
Phone:
Fax:
Mobile:
Email:
Huawei
Hi David & Nikos,
My comments are inlined in below mail, please check it.
-Original Message-
From: David Woodhouse [mailto:dw...@infradead.org]
Sent: 19 September 2016 13:04
To: Nikos Mavrogiannopoulos; Raja ashok; jayaraghavendra...@huawei.com
Subject: Re: draft-jay-tls-psk-iden
l me why we decided only few values as GREASE
value {0x0A0A, 0x1A1A, ..}. Whether chrome browser has found a real buggy web
server which supports these values ?
Regards,
R Ashok
____
Raja Ashok VK
华为技术有限公司 Huawei Technologies Co., Ltd.
[Company_logo]
Phone:
Fax:
Mo
ng, please clarify
me.
Regards,
R Ashok
____
Raja Ashok VK
华为技术有限公司 Huawei Technologies Co., Ltd.
[Company_logo]
Phone:
Fax:
Mobile:
Email:
Huawei Technologies Co., Ltd.
Bangalore, India
http://www.huawei.com
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地
18 matches
Mail list logo
