From: RongQing Li <roy.qing.li@gmail.com>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC PATCH] xfrm: avoid to send/receive the exceeding hard lifetime data
Date: Sat, 15 Dec 2012 09:36:27 +0800 [thread overview]
Message-ID: <CAJFZqHyRTW5eShGzLVzkHTDAeopwC5L6wS=Cfh_DTa82DE2s1g@mail.gmail.com> (raw)
In-Reply-To: <20121214113945.GH18940@secunet.com>
2012/12/14 Steffen Klassert <steffen.klassert@secunet.com>:
> On Fri, Dec 14, 2012 at 02:58:03PM +0800, RongQing Li wrote:
>>
>> Yes, RFC does not say how to handle this packet.
>>
>> But when I do a IPsec compliance test with IxANVL, the test case 5.3/5.11,
>> which reports a error because it expects this packet should be dropped, but not.
>>
>>
>> I do not know if it is bug, or if it is valuable to fix it?
>>
>
> As long as the RFC does not state anything else, we ar ok in the
> synchronous code path. But we need a fix for the asynchronous
> code path.
>
Thanks.
-Roy
prev parent reply other threads:[~2012-12-15 1:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 8:25 [RFC PATCH] xfrm: avoid to send/receive the exceeding hard lifetime data roy.qing.li
2012-12-13 10:14 ` Steffen Klassert
2012-12-14 6:58 ` RongQing Li
2012-12-14 11:39 ` Steffen Klassert
2012-12-15 1:36 ` RongQing Li [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJFZqHyRTW5eShGzLVzkHTDAeopwC5L6wS=Cfh_DTa82DE2s1g@mail.gmail.com' \
--to=roy.qing.li@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).