From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: ajtuomin@morphine.tml.hut.fi
Cc: takamiya@po.ntts.co.jp, davem@redhat.com, kuznet@ms2.inr.ac.ru,
netdev@oss.sgi.com, linux-kernel@vger.kernel.org,
pekkas@netcore.fi, torvalds@transmeta.com, jagana@us.ibm.com,
yoshfuji@linux-ipv6.org
Subject: Re: [PATCHSET] Mobile IPv6 for 2.5.43
Date: Fri, 01 Nov 2002 12:27:58 +0900 (JST) [thread overview]
Message-ID: <20021101.122758.809131116.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <20021031104146.GA18786@morphine.tml.hut.fi>
In article <20021031104146.GA18786@morphine.tml.hut.fi> (at Thu, 31 Oct 2002 12:41:46 +0200), Antti Tuominen <ajtuomin@morphine.tml.hut.fi> says:
> > (4) Processing Mobility Header
> > How about using ip6_txoptions and hdrproc_lst?
> > Because Mobility header is an extension header, we think it is
> > reasonable way to handle it in ipv6_parse_exthdrs().
>
> No. We did this back in Draft 15, when all the mobility stuff was
> destination options. Mobility Header is not an extension header, but
> rather a final protocol. Only Home Address Option is an extension
> header and is handled in ipv6/exthdrs.c. What is the problem with
> this?
This is not so strong request here at this moment.
--yoshfuji
next prev parent reply other threads:[~2002-11-01 3:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 16:26 Antti Tuominen
2002-10-17 17:18 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-17 17:56 ` Mitsuru KANDA
2002-10-18 11:16 ` Antti Tuominen
2002-10-17 23:52 ` Ville Nuorvala
2002-10-18 0:56 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-17 20:14 ` Pekka Savola
2002-10-18 7:39 ` Antti Tuominen
2002-10-17 22:51 ` Ville Nuorvala
2002-10-31 8:44 ` Noriaki Takamiya
2002-10-31 8:55 ` Pekka Savola
2002-10-31 9:08 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-31 10:41 ` Antti Tuominen
2002-11-01 3:27 ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
2002-10-31 10:44 ` Henrik Petander
2002-11-01 3:22 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-17 17:22 Krishna Kumar
2002-10-17 21:57 ` Ville Nuorvala
2002-10-17 17:46 Krishna Kumar
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=20021101.122758.809131116.yoshfuji@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=ajtuomin@morphine.tml.hut.fi \
--cc=davem@redhat.com \
--cc=jagana@us.ibm.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=pekkas@netcore.fi \
--cc=takamiya@po.ntts.co.jp \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®