From: Bernd Petrovitsch <bernd@gams.at>
To: "Mike A. Harris" <mharris@opensourceadvocate.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: About IP address
Date: Tue, 28 Nov 2000 10:46:20 +0100 [thread overview]
Message-ID: <200011280946.KAA25036@frodo.gams.co.at> (raw)
In-Reply-To: Your message of "Mon, 27 Nov 2000 16:32:17 EST." <20001127163217.B20394@alcove.wittsend.com>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
To throw additional information (or confusion or simply wrong stuff?) in :
In message <20001127163217.B20394@alcove.wittsend.com>, "Michael H. Warfield" w
rote:
> I have been unable to find any documentation in the RFCs
>which lay claim to restricting 128.0.*.* or 191.255.*.*. The fact
RFC1940, though it's "only" informational, bottom of page 7 :
--- snip ---
Source Route (variable)
The components of the source route are syntactically IP
addresses.
An IP address from network 128.0.0.0 is used to encode a next
hop that is a domain. The least significant two octets contain
the DI, which is an Internet Autonomous System number.
--- snip ---
Bernd
--
Bernd Petrovitsch Email : bernd@gams.at
G.A.M.S GmbH Fax : +43 1 8958499-60
Stiegerg. 15-17/8 A-1150 Vienna/Austria/Europe
LUGA : http://www.luga.at
[-- Attachment #2: Type: application/pgp-signature, Size: 1195 bytes --]
prev parent reply other threads:[~2000-11-28 10:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-24 13:36 Su Hwan Hwang
2000-11-24 14:22 ` John Crowhurst
2000-11-24 22:15 ` J. Dow
2000-11-24 22:30 ` Mike A. Harris
2000-11-27 21:32 ` Michael H. Warfield
2000-11-27 20:55 ` H. Peter Anvin
2000-11-28 9:46 ` Bernd Petrovitsch [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=200011280946.KAA25036@frodo.gams.co.at \
--to=bernd@gams.at \
--cc=linux-kernel@vger.kernel.org \
--cc=mharris@opensourceadvocate.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
all inboxes | Powered by JetHome®