netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Haley <Brian.Haley@hp.com>
To: yoshfuji@linux-ipv6.org
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH, TAKE 2] [IPV6] XFRM: extract xfrm_lookup() from ip6_dst_lookup() (is Re: [PATCH][IPv6] separation xfrm_lookup from ip6_dst_lookup)
Date: Wed, 27 Oct 2004 11:21:29 -0400	[thread overview]
Message-ID: <417FBCF9.5070808@hp.com> (raw)
In-Reply-To: <20041027.091039.56337914.yoshfuji@linux-ipv6.org>


> Because we do not support RFC3542, extra 128bits is definitely correct.

2292 was deprecated by 3542 in May 2003, when do we plan on supporting it?  I am 
willing to do this update, just please tell me the way you want me to go about it.

Thanks,

-Brian

  reply	other threads:[~2004-10-27 15:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-30  8:12 [PATCH][IPv6] separation xfrm_lookup from ip6_dst_lookup Kazunori Miyazawa
2004-08-02  2:51 ` David S. Miller
2004-08-03  9:00   ` YOSHIFUJI Hideaki / 吉藤英明
2004-08-03  9:21     ` Kazunori Miyazawa
2004-08-09 23:35     ` David S. Miller
2004-08-10  1:38       ` YOSHIFUJI Hideaki / 吉藤英明
2004-08-27 16:49   ` [PATCH, TAKE 2] [IPV6] XFRM: extract xfrm_lookup() from ip6_dst_lookup() (is Re: [PATCH][IPv6] separation xfrm_lookup from ip6_dst_lookup) YOSHIFUJI Hideaki / 吉藤英明
2004-08-28  0:02     ` David S. Miller
2004-10-25 21:27     ` Brian Haley
2004-10-26  3:55       ` YOSHIFUJI Hideaki / 吉藤英明
2004-10-26 14:29         ` Brian Haley
2004-10-26 15:43           ` YOSHIFUJI Hideaki / 吉藤英明
2004-10-26 18:09             ` Brian Haley
2004-10-27  0:10               ` YOSHIFUJI Hideaki / 吉藤英明
2004-10-27 15:21                 ` Brian Haley [this message]
2004-08-02  7:41 ` [PATCH][IPv6] separation xfrm_lookup from ip6_dst_lookup Herbert Xu
2004-08-03  2:09   ` David S. Miller
2004-08-03  8:19     ` YOSHIFUJI Hideaki / 吉藤英明
2004-08-03 10:55     ` 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=417FBCF9.5070808@hp.com \
    --to=brian.haley@hp.com \
    --cc=netdev@oss.sgi.com \
    --cc=yoshfuji@linux-ipv6.org \
    /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).