Simple. To make it easy to set up a network. For amateurs who just want to
plug a couple of PC's together in their home or office. Microsoft, for all
the bad rap they take, have throughout their tenure made great effort to
make things easier for people to do things.
Whether they succeeded or not can be argued. But the history, going back to
Windows for Workgroups, has been to try to make it relatively easy for non
technical people to set up simple networks for file and print sharing.
What with NetBEUI losing in the market place, and the pre-eminence of IP
due to the internet ) why not attempt another form of easy networking using
something like this?
Question: how long before we start hearing people say things like "why
should I pay a professional to come in and set up my network when I can just
buy a couple of computers, a hub, and some wire at CompUSA and do it all
myself?"
Chuck
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
Craig Columbus
Sent: Saturday, January 06, 2001 7:49 AM
To: [EMAIL PROTECTED]
Subject: RE: A question regarding private addressing
OK. I can accept that Microsoft (or Apple for that matter) would do
something like this and then expect the world to revolve around
them. However, I'm confused as to the benefit. Why would anyone want a
non-assigned default IP address to appear on their network? Do they really
think that people will implement a non-RFC1918 compliant address space just
to save configuration time? (Actually, I can think of several cases where
people might just go for this.)
How do Internet backbone routers (BGP ASs) deal with this traffic?
Let's say that I want to take the easy way out and I connect a small
network to the Internet via an ISP. I'm not running NAT, but I'm running
the 169.254 addresses inside my network. If I've got a static route to an
ISP public address, and we're not exchanging routing information, I can't
see how this traffic would ever get back to my network. If I'm exchanging
routes with an ISP (via BGP or some other interior protocol), where and how
do the 169.254 routes get filtered? There has to be some mechanism, or
there would be thousands of summary routes back to 169.254 showing up on
the Internet table.
Any help in understanding this is appreciated.
Thanks,
Craig
At 03:27 AM 1/6/2001 -0800, you wrote:
>On May 28, 10:03am, Priscilla Oppenheimer wrote:
>}
>} Microsoft stole this from AppleTalk. Ironically, Apple doesn't care and
in
>
> MS made a draft RFC about it, which has expired, and there is a
>new draft by Apple (see my previous note).
>
>} fact has been using the Automatic Private IP Addressing scheme for a few
>} years. I think Microsoft themselves only started using it pretty
recently.
>} (Windows 2000, you say?)
>
> No, Windows 98 does it as well (not sure about Windows 95, but it
>would be a good bet).
>
>}-- End of excerpt from Priscilla Oppenheimer
>
>_________________________________
>FAQ, list archives, and subscription info:
>http://www.groupstudy.com/list/cisco.html
>Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
_________________________________
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
