All of lore.kernel.org
 help / color / mirror / Atom feed
From: Diego Beltrami <diego.beltrami@HIIT.FI>
To: netdev@oss.sgi.com
Subject: Re: [Hipsec] [PATCH 2.6.12.2] XFRM: BEET IPsec mode for Linux
Date: Mon, 25 Jul 2005 16:28:55 +0300	[thread overview]
Message-ID: <1122298135.14873.70.camel@odysse> (raw)
In-Reply-To: <1122295307.14873.37.camel@odysse>

Folks,
I'm sorry but the sent patch included in the email seems to be broken.
Please, use the URL 
http://hipl.hiit.fi/beet/beet-patch-v1.0-2.6.12.2

Sincerely


> Hi folks,
> 
> we have been working for three months to implement a new IPsec mode,
> the "BEET" mode, for Linux. Below is a link to the BEET specification
> and
> the abstract:
> 
> http://www.ietf.org/internet-drafts/draft-nikander-esp-beet-mode-03.txt
> 
> Abstract
> 
>    This document specifies a new mode, called Bound End-to-End Tunnel
>    (BEET) mode, for IPsec ESP.  The new mode augments the existing ESP
>    tunnel and transport modes.  For end-to-end tunnels, the new mode
>    provides limited tunnel mode semantics without the regular tunnel
>    mode overhead.  The mode is intended to support new uses of ESP,
>    including mobility and multi-address multi-homing.
> 
> The BEET mode is required by the Host Identity Protocol (HIP), which
> provides authenticated Diffie-Hellman for end-hosts, as well as
> mobility and multihoming support. The BEET mode is also useful for
> other similar protocols being developed at the IETF.
> 
> Ericsson has already developed a BEET patch for *BSD. Our patch
> provides the similar functionality, but using the XFRM architecture.
> The patch is included at the end of this email and also at the following
> URL:
> http://hipl.hiit.fi/beet/beet-patch-v1.0-2.6.12.2
> 
> We have made some testing in order to assure the quality of the
> patch. All the tests passed, and below is a list of them:
> 
> * Does not break transport and tunnel mode (with CONFIG_XFRM_BEET
> on/off)
> * All inner-outer combinations with varying test applications:
>   ICMP, ICMPv6, FTP, SSH, nc, nc6
> * Works with fragmented packets
> * Interoperability with HIPL
> * Real machines, virtual machines (vmware)
> * Tested with long data streams
> 
> The BEET development team:
> 
> * Abhinav Pathak <abpathak@iitk.ac.in> (InfraHIP/HIIT)
> * Diego Beltrami <diego.beltrami@hiit.fi> (InfraHIP/HIIT)
> * Kristian Slavov <kristian.slavov@nomadiclab.com> (Ericsson)
> * Miika Komu <miika@iki.fi> (InfraHIP/HIIT)
> * Jeff Ahrenholz <jeffrey.m.ahrenholz@boeing.com> (Boeing)
> 
> On the behalf of the BEET development team,
> 
> Signed-off-by: Diego Beltrami <diego.beltrami@hiit.fi>
> 
> 
> 

       reply	other threads:[~2005-07-25 13:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1122295307.14873.37.camel@odysse>
2005-07-25 13:28 ` Diego Beltrami [this message]
2005-07-26 13:02 ` [PATCH 2.6.12.2] XFRM: BEET IPsec mode for Linux Miika Komu
2005-07-28 11:36 ` Herbert Xu
2005-07-29 15:33   ` [hipl-users] " Diego Beltrami
2005-07-29 15:45     ` [Infrahip] " Pekka Nikander
2005-07-29 23:48       ` Herbert Xu
2005-07-30 11:01         ` Diego Beltrami
2005-07-30 11:15     ` [hipl-users] " Herbert Xu

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=1122298135.14873.70.camel@odysse \
    --to=diego.beltrami@hiit.fi \
    --cc=netdev@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.