[TLS] 答复: Minutes for TLS IETF 102 uploaded

2018-08-09 Thread yinxinxing
+1. I am also confused by the *. I open the link via web. Yin Xinxing -邮件原件- 发件人: TLS [mailto:tls-boun...@ietf.org] 代表 Russ Housley 发送时间: 2018年8月10日 6:08 收件人: Christopher Wood 抄送: IETF TLS 主题: Re: [TLS] Minutes for TLS IETF 102 uploaded I do not understand the formatting. Are the '*'

Re: [TLS] WG call for adoption of draft-rescorla-tls-dtls-connection-id

2017-12-12 Thread yinxinxing
I also agree adopting this WG draft. This feature will help a lot to solve the NAT rebinding problems in IOT fields. Happy to see that there was a strong WG consensus on adopting the draft in Singapore. Yin Xinxing 发件人: TLS [mailto:tls-boun...@ietf.org] 代表 Tobias Gondrom 发送时间: 2017年12月13日 11:06

Re: [TLS] Connection ID Draft

2017-11-02 Thread yinxinxing
I agree with Matt. The port/IP could be reallocated to the peer that sends packets with connection ID. Yin Xinxing -邮件原件- 发件人: TLS [mailto:tls-boun...@ietf.org] 代表 Matt Caswell 发送时间: 2017年11月3日 0:32 收件人: tls@ietf.org 主题: Re: [TLS] Connection ID Draft On 17/10/17 22:35, Martin Thomson

Re: [TLS] Connection ID Draft

2017-10-26 Thread yinxinxing
hold. 发件人: Eric Rescorla [mailto:e...@rtfm.com] 发送时间: 2017年10月26日 12:05 收件人: yinxinxing 抄送: tls@ietf.org 主题: Re: [TLS] Connection ID Draft On Wed, Oct 25, 2017 at 8:02 PM, yinxinxing mailto:yinxinx...@huawei.com>> wrote: Hi Ekr, Sorry for the delay. I don’t quite understand “The wa

Re: [TLS] Connection ID Draft

2017-10-25 Thread yinxinxing
matched in the receiver's 5-tuple table. For the above choices, what do you think? Or do you have any other good solution to be updated in the draft? Regards, Yin Xinxing 发件人: Eric Rescorla [mailto:e...@rtfm.com] 发送时间: 2017年10月23日 20:13 收件人: yinxinxing 抄送: tls@ietf.org 主题: Re: [TLS] Connecti

Re: [TLS] Connection ID Draft

2017-10-23 Thread yinxinxing
include C-CID), and client will use S-CID in its application message. Will the draft cover this scenario? Yin Xinxing 发件人: Eric Rescorla [mailto:e...@rtfm.com] 发送时间: 2017年10月13日 21:00 收件人: yinxinxing 抄送: tls@ietf.org 主题: Re: [TLS] Connection ID Draft On Fri, Oct 13, 2017 at 1:11 AM, yinxinxing

Re: [TLS] Connection ID Draft

2017-10-20 Thread yinxinxing
Hi Martin, According to the code you described in previous email, ISTM your idea of parsing the standard packet and CID packet is using the 5-tuple. The benefit is that no new contenttype or version is needed. But the precondition for well working is that the 5-tuple of the CID packet will not

[TLS] 答复: 答复: Connection ID Draft

2017-10-13 Thread yinxinxing
:47 收件人: yinxinxing 抄送: tls@ietf.org 主题: Re: 答复: [TLS] Connection ID Draft On Fri, Oct 13, 2017 at 7:41 PM, yinxinxing mailto:yinxinx...@huawei.com>> wrote: Thanks Ekr. For “I explicitly did not want to do that, because there are a lot of valid ways to generate CID. This is also what we

[TLS] 答复: Connection ID Draft

2017-10-13 Thread yinxinxing
. Regards, Yin Xinxing 发件人: Eric Rescorla [mailto:e...@rtfm.com] 发送时间: 2017年10月13日 21:00 收件人: yinxinxing 抄送: tls@ietf.org 主题: Re: [TLS] Connection ID Draft On Fri, Oct 13, 2017 at 1:11 AM, yinxinxing mailto:yinxinx...@huawei.com>> wrote: Hi Ekr, Thanks for your effort. The draft looks good.

[TLS] 答复: Connection ID Draft

2017-10-13 Thread yinxinxing
is is what I mean "worse". Regards, Yin Xinxing -邮件原件- 发件人: Hannes Tschofenig [mailto:hannes.tschofe...@gmx.net] 发送时间: 2017年10月13日 23:41 收件人: yinxinxing; Eric Rescorla; tls@ietf.org 主题: Re: [TLS] Connection ID Draft I would like to focus on one of the points raised below:

[TLS] 答复: Connection ID Draft

2017-10-13 Thread yinxinxing
I agree with Stephen. It is essential to ensure the new connection ID couldn't be linked to the old one to avoid tracking risk. However, it is some sort of implementation issues, and there are more ways to do that(not only hash method). Maybe we can at least give suggestions or warning in the d

Re: [TLS] Connection ID Draft

2017-10-13 Thread yinxinxing
Hi Ekr, Thanks for your effort. The draft looks good. A few comments are listed below. 1. Based on the draft, for either DTLS1.2 or 1.3, server can’t differentiate whether the packet from client is a “connection ID” packet or a standard DTLS 1.2/1.3 packet. (I saw Thomas Fossati and Niko

[TLS] 答复: Solving the NAT expiring problem causing DTLS renegotiation with high power consumption in DTLS1.2

2017-07-18 Thread yinxinxing
Thanks Wing. I am glad to discuss the technical details of CID draft with Hannes, Thomas and Nikos. Regards, Yin Xinxing -邮件原件- 发件人: Dan Wing [mailto:danw...@gmail.com] 发送时间: 2017年7月19日 0:34 收件人: yinxinxing 抄送: tls@ietf.org; Sean Turner 主题: Re: [TLS] Solving the NAT expiring problem

[TLS] 答复: Solving the NAT expiring problem causing DTLS renegotiation with high power consumption in DTLS1.2

2017-07-16 Thread yinxinxing
don't need to bother the server(customer) to deploy anti-DOS devices, why not have a try? Regards, Yin Xinxing -邮件原件- 发件人: yinxinxing 发送时间: 2017年7月13日 16:56 收件人: 'Dan Wing' 抄送: tls@ietf.org; Sean Turner 主题: 答复: [TLS] Solving the NAT expiring problem causing DTLS renegotia

[TLS] 答复: Solving the NAT expiring problem causing DTLS renegotiation with high power consumption in DTLS1.2

2017-07-13 Thread yinxinxing
Hi Wing, Please see the comments inline Regards, Yin Xinxing -邮件原件- 发件人: Dan Wing [mailto:danw...@gmail.com] 发送时间: 2017年7月13日 12:35 收件人: yinxinxing 抄送: tls@ietf.org; Sean Turner 主题: Re: [TLS] Solving the NAT expiring problem causing DTLS renegotiation with high power consumption in

[TLS] 答复: Solving the NAT expiring problem causing DTLS renegotiation with high power consumption in DTLS1.2

2017-07-12 Thread yinxinxing
Thanks Wing, Please see my comments inline. Regards, Yin Xinxing -邮件原件- 发件人: Dan Wing [mailto:danw...@gmail.com] 发送时间: 2017年7月13日 8:52 收件人: yinxinxing 抄送: tls@ietf.org; Sean Turner 主题: Re: [TLS] Solving the NAT expiring problem causing DTLS renegotiation with high power consumption in

[TLS] 答复: Solving the NAT expiring problem causing DTLS renegotiation with high power consumption in DTLS1.2

2017-07-12 Thread yinxinxing
Thanks Sean! Your question and comments are valuable. Please check my comments inline. Regards, Yin Xinxing -邮件原件- 发件人: Sean Turner [mailto:s...@sn3rd.com] 发送时间: 2017年7月12日 22:57 收件人: yinxinxing 抄送: tls@ietf.org 主题: Re: [TLS] Solving the NAT expiring problem causing DTLS

[TLS] 答复: Solving the NAT expiring problem causing DTLS renegotiation with high power consumption in DTLS1.2

2017-07-12 Thread yinxinxing
Hi Dan Wing, Thanks for your comments. Please see my comments inline. Regards, Yin Xinxing -邮件原件- 发件人: Dan Wing [mailto:danw...@gmail.com] 发送时间: 2017年7月13日 1:09 收件人: yinxinxing 抄送: tls@ietf.org; Sean Turner 主题: Re: [TLS] Solving the NAT expiring problem causing DTLS renegotiation with

[TLS] Solving the NAT expiring problem causing DTLS renegotiation with high power consumption in DTLS1.2

2017-07-06 Thread yinxinxing
solved in DTLS 1.2 as soon as possible. Any comment is appreciated. Regards, Yin Xinxing 发件人: yinxinxing 发送时间: 2017年6月27日 16:28 收件人: 'Eric Rescorla' 抄送: tls@ietf.org; Tobias Gondrom 主题: Re: [TLS] Yin Xinxing joins the TLS WG Thanks Eric, I have seen the CID scheme, and talked with

Re: [TLS] Yin Xinxing joins the TLS WG

2017-06-27 Thread yinxinxing
, 1 million connection is nothing. Regards, Yin Xinxing 发件人: Eric Rescorla [mailto:e...@rtfm.com] 发送时间: 2017年6月25日 21:33 收件人: yinxinxing 抄送: tls@ietf.org; Xiongxiaochun 主题: Re: [TLS] Yin Xinxing joins the TLS WG Hi Yin, The usual solution to this is to add a connection id. Please see: https

[TLS] Yin Xinxing joins the TLS WG

2017-06-25 Thread yinxinxing
Hello everyone, I am Yin Xinxing from Huawei company. I am glad to join the TLS WG. For the DLTS 1.3 draft, I am interested and have some ideas to talk with you. DTLS has a lot of application scenarios in IOT fields, but currently, there is some difficulty when DTLS 1.2 is applied to IOT device