netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: nicolas.dichtel@dev.6wind.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH RFC] xfrm6: handling fragment
Date: Sat, 01 Nov 2008 21:12:21 -0700 (PDT)	[thread overview]
Message-ID: <20081101.211221.67297722.davem@davemloft.net> (raw)
In-Reply-To: <490B3DC9.906@dev.6wind.com>

From: Nicolas Dichtel <nicolas.dichtel@dev.6wind.com>
Date: Fri, 31 Oct 2008 18:18:01 +0100

> RFC4301 Section 7.1 says:
> 
> "7.1.  Tunnel Mode SAs that Carry Initial and Non-Initial Fragments
> 
>      All implementations MUST support tunnel mode SAs that are configured
>      to pass traffic without regard to port field (or ICMP type/code or
>      Mobility Header type) values.  If the SA will carry traffic for
>      specified protocols, the selector set for the SA MUST specify the
>      port fields (or ICMP type/code or Mobility Header type) as ANY.  An
>      SA defined in this fashion will carry all traffic including initial
>      and non-initial fragments for the indicated Local/Remote addresses
>      and specified Next Layer protocol(s)."
> 
> But for IPv6, fragment is treated as a protocol. Would the following patch be acceptable to catch protocol transported in fragmented packet?
> In IPv4, there is no problem.
> 
> Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>

This seems good, I've applied this to net-next-2.6

Thanks.

      reply	other threads:[~2008-11-02  4:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31 17:18 [PATCH RFC] xfrm6: handling fragment Nicolas Dichtel
2008-11-02  4:12 ` David Miller [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=20081101.211221.67297722.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@dev.6wind.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).