lkml.org 
[lkml]   [2003]   [Jan]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: (usagi-core 11007) [PATCH] IPsec Configuration Extension for IPv6
From
   From: Kazunori Miyazawa <Kazunori.Miyazawa@jp.yokogawa.com>
Date: Tue, 7 Jan 2003 13:00:50 +0900

This patch is simple extension of PF_KEY to support IPv6;
to accept IPv6 IPsec configurations.

Ok. Your patch looks OK and probably I will integrate it to my
tree tomorrow.

However this patch does not contain any codes to process the packets
in IPv6 stack because we wonder how we should implement it:

1. The building packet codes of datagram (ip_append_data()) is
very different from ip6_build_xmit(). And I guess you will
change ip6_build_xmit() to ip6_append_data().

2. How should we implement to process destination option header
which is inside of AH and/or ESP? There seems two options.
One is to process IPsec on parsing extension headers.
The other is to process IPsec as upper layer protocol and
we always check the destination option header when we finish
to process AH or ESP.

We will be glad to hear your preferences, plans or a better way
to implementation.

To be honest no concrete plans exist. Alexey is currently
offline and I expected to bring him into an ipv6 ipsec discussion
as soon as he reappears. I do not know when he will return, however.

Because of this, I would suggest to just keep working in area of
AH/ESP ipv6-specific packet creation and parsing. Stay clear of
routing/dst/input/output interface issues. If you finish the packet
handling/building work and Alexey does not return, we can work on
design without him.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:32    [W:0.048 / U:7.204 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site