From: Andras Kis-Szabo <kisza@securityaudit.hu>
To: Netdev <netdev@oss.sgi.com>
Subject: IPv6 RFC2292, 1883 and 2460 (was: RFC2292(bis))
Date: 20 May 2002 11:55:27 +0200 [thread overview]
Message-ID: <1021888528.8107.25.camel@hoi> (raw)
Hi,
The RFC2292 based on the RFC1883 (and the Linux network (api/libc level)
implementation, too).
The RFC1883 obsolated by the RFC2460.
The Type0 routing header has changed between the two version: the S/L
bits were removed from it. (Changes 01.3) (And the address limit was
deleted, too)
Do the other implementations support the S/L bits?
(The current Netfilter implementation based on the RFC2460.)
regards
kisza
--
Andras Kis-Szabo Security Development, Design and Audit
-------------------------/ Zorp, NetFilter and IPv6
kisza@SecurityAudit.hu /-----Member of the BUTE-MIS-SEARCHlab------>
reply other threads:[~2002-05-20 9:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1021888528.8107.25.camel@hoi \
--to=kisza@securityaudit.hu \
--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).