netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: netdev@oss.sgi.com
Subject: Re: IPv6 auth header length calculation patch
Date: Sun, 05 Jan 2003 02:05:45 +0900 (JST)	[thread overview]
Message-ID: <20030105.020545.34113263.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <873co8dhr2.wl@ipinfusion.com>

In article <873co8dhr2.wl@ipinfusion.com> (at Sat, 04 Jan 2003 08:03:45 -0800), Kunihiro Ishiguro <kunihiro@ipinfusion.com> says:

> This is a USAGI patch to fix IPv6 auth header length calculation.
> (I'm not USAGI member.  I'm working on IPv6 IPsec based on 2.5 code
> base).
:
> Would you mind to apply this to avoid wrong header length calculation?

Just a moment please.  
We'll make a patch for this by ourselves.

-- 
Hideaki YOSHIFUJI @ USAGI Project <yoshfuji@linux-ipv6.org>
GPG FP: 9022 65EB 1ECF 3AD1 0BDF  80D8 4807 F894 E062 0EEA

      reply	other threads:[~2003-01-04 17:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-04 16:03 IPv6 auth header length calculation patch Kunihiro Ishiguro
2003-01-04 17:05 ` YOSHIFUJI Hideaki / 吉藤英明 [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=20030105.020545.34113263.yoshfuji@linux-ipv6.org \
    --to=yoshfuji@linux-ipv6.org \
    --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 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).