Vista Beta 1 and Longhorn Server Beta 1 include a new implementation of the TCP/IP protocol suite known as the Next Generation TCP/IP stack. The Next Generation TCP/IP stack in Windows Vista and Windows Server Longhorn is a complete redesign of TCP/IP functionality for both IPv4 and IPv6 that meets the connectivity and performance needs of today’s varied networking environments and technologies. Elsewhere, will Office 12 be named… Office Mondo?
Mondo? …. Vista ? …. What are they thinking with these names?
Well, it seems Microsoft likes Italian words!
Mondo= World
Vista= Sight
> Well, it seems Microsoft likes Italian words!
> Mondo= World
> Vista= Sight
Well, Vista exists in other languages, including English.
Mondo (world) is incorrect. It should be Mondo minus Massachusetts. 🙂 It’s almost Mondo but not quite.
Maybe it’s better Quasimondo.
dô-ôb
Was XPerience that much better??
Any bets TCP/IP-NG will be slightly incompatible with the standard, or have some patented extra bits somewhere?
– Peder
Maybe they were hitting the peace pipe with the Ubuntu guys?
The new tcp/ip stack doesn’t sound particularly groundbreaking, they haven’t moved it out of the kernel or anything interesting, it’s just “new,” hardly newsworthy.
How is it “hardly newsworthy?” The biggest and most pervasive commercial software company on the planet has swapped out their notorious BSD-based TCP/IP implementation in favor of a newer one that offers Windows users a much better experience, like the ability ot change protocol settings without a reboot. That seems like pretty big news to me.
While it doesn’t implement new features, it’s seemingly a huge plus for Windows users.
How is it “hardly newsworthy?” The biggest and most pervasive commercial software company on the planet has swapped out their notorious BSD-based TCP/IP implementation in favor of a newer one that offers Windows users a much better experience, like the ability ot change protocol settings without a reboot. That seems like pretty big news to me.
So BSD code demands reboot. You risk getting chewed and spitted out by BSD users
swapped out their notorious BSD-based TCP/IP implementation
Windows TCP/IP hasn’t been BSD-based for years. In fact, it was only at the beginning, for a very short time.
>The biggest and most pervasive commercial software company
>on the planet has swapped out their notorious BSD-based
>TCP/IP implementation
Windows NT, 200*, XP don’t use BSD stack! It was in windows 9x !
“Windows NT, 200*, XP don’t use BSD stack! It was in windows 9x !”
You might like to read this article ( http://www.kuro5hin.org/?op=displaystory;sid=2001/6/19/05641/7357 ) its written by one of the original programmers on the Windows NT project.
Some of use appreciate this kind of news. I’m very interested in OSS, and I use Linux / GNU / Mozilla a lot and promote it everywhere, but I don’t like the narrow-minded behaviour os some people who think that OSS defines the borders of the world. Windows is an important OS, no matter how much you like it.
This new TCP/IP stack shows some interesting features – multiprocessor, multiuser (each user it’s own routing container), very good support for IP6 – it’s going to make things better.
Unbelievable how some people wonder if the new TCP/IP stack will communicate with OSS TCP/IP. Totally unrealistic. Image the news papers: Windows Vista not able to browse 95% of the WWW. Because if MS would do that, IE would not communicatie with Apache WWW servers AND not with current Windows servers who still use the older TCP/IP. You have to be a fool to suggest something like this, I’m sorry to say. MS cares about backward compatability, and I’m sure this new stack will play nice with other stacks.
The impact on IP6 will be huge. IP6 enabled by default, that means the mainstream OS vendor will force IP6 upon the market – which is a good think, the world needs IP6.
For what it’s worth something NEW in such a core thing as TCP/IP stack will probably mean untested software full of as-of-yet undiscovered holes. That always happens when something’s redesigned. Unless it WAS redesigned in the first place and it’s not just PR hype.
a CVS export of the latest BSD TCP/IP Stack tree, which they will be implementing shortly.
http://www.answers.com/mondo&r=67
Any support for interoperability? Might be a good thing in a communications layer – no?
NFS?
SMB connectivity with Samba servers or clients?
Is Windows IPV6 compatible with Linux IPV6?
SSH? SFTP? SCP? Lisa? Zeroconf?
Can Windows use a CUPS printer yet?
window has been able to use CUPS printers since win98.
Window services for unix provides NFS support.
And when 2003 R2 comes out, it has support for NFS, among many other things.
>>window has been able to use CUPS printers since win98.<<
Can it? Great!
How do I get it to?
Also, how do I install & set up Windows SFU, or would I be better off with Cygwin?
http://www.microsoft.com/windowsserversystem/sfu/default.mspx
Pretty straight forwadr.
Sorry Microsoft, this word is patented by the italian language. You have to pay a royalty fee to use it.
Mondo smash StarOffice
*LOL*
Let’s see if that happens…
Maybe Microsoft wan’ts to get rid of open-source netstack which is part of the “viral software”. Also they have now tool to make life of non-Microsoft systems difficult in Microsoft-only LANs that may require the next generation net stack for increased security etc. Probably Microsoft even dream of Windows-only Internet in distant future.
Actually the BSD netscack isn’t “viral software”, since the BSD-license isn’t a “viral” license.
It’s either marketing hype or a de-commoditized protocol created in an attempt to create a vendor lock-in on the internet.
You should take a look at: http://channel9.msdn.com/ShowPost.aspx?PostID=116554
it implements CTCP (Compound TCP) algorithm which has performance improvements that are greater than FAST at (http://netlab.caltech.edu/). So it should mean much faster downloads even on a DSL line.
More information on the CTCP can be found at: http://research.microsoft.com/research/pubs/view.aspx?type=Technica…
This improvement will be available in Beta2 and NOT beta1
Great info. Unfortunately, I don’t have time to read the papers you have linked…
I have a question, though: does that would need specific support from both parties? I mean, if you are a subscriber and want to reap the benefits from CTCP, would the host (say, a web server) needs to use CTCP too? What about the ATMs, gateways and firewalls routing your traffic? If that is the case, then I don’t see any improvement for a while. Unless the implementation is open, that’s it.
Steve: Well, Bill….what are we going to do. We have already told people that every new feature that we promised that was going to be in this OS we can’t deliver on. This OS is starting to look like the Windows ME of the NT-line. I am worried, any ideas?
Bill: *lightbulb* It’s new and improved! Now with “TcpIP-NG!”! Put a big yellow sticker on the box, people will eat it up. And just in case we can put some of those little toys in the box like you get with cracker jacks, like say a little BB-puzzle with your big bald head…that will be worth the $200 to most people.
Man it’s 1999(ME) all over again. Poor monkeysoft.
Hey screwy naming worked for them right??
As far as their NextGen TCP/IP implementation doesn’t break RFCs, I welcome new stack. Current TCP/IP is working well, but it’s apparently a mess inside.
Well, look at next sentences in pointed article (my italic):
“WFP is more secure, integrated in the stack, and much easier for independent software vendors (ISVs) to build drivers, services, and applications that must filter, analyze, or modify TCP/IP traffic.”
“The Next-Generation TCP/IP stack has an infrastructure to enable more modular components that can be dynamically inserted and removed.”
What we get finally:
[NextGen TCP/IP stack should be] more secure, [but it’s] much easier for [anybody to] modify TCP/IP traffic [and/or] insert more [unwanted] components dynamically.
🙂
>”WFP is more secure, integrated in the stack, and much easier for independent software vendors (ISVs) to build drivers, services, and applications that must filter, analyze, or modify TCP/IP traffic.”
“The Next-Generation TCP/IP stack has an infrastructure to enable more modular components that can be dynamically inserted and removed.” <
That’s funny i remember an earlier article saying how MSFT was going to remove direct TCP/IP access from end users and software.
they rewrite there TCP/ip stack, which in the old days they took form BSD. then they evolve it to what we have today which is a mess, so they do a rewrite to clean it up and make sure IPv6 is fully supported and stuff .
so they call this next gen TCP/IP?
-Nex6
It’s a myth that MS took their TCP/IP stack from BSD, they only took some userland tools such as ftp and telnet from BSD. BTW, IPv6 has been supported by *BSD TCP/IP stacks for a long time… possibly it was the first to implement ipv6.
This is nothing but typical Microsoft hype like about anything else surrounding Vista. I am tired of essentially reading Microsoft advertising everywhere. If they would have focused on development instead of creating hype and FUD, it would have been more beneficial for everyone and Vista would have had a chance.
Yeah, because they don’t have a marketing department that’s seperate from the developers. Yep, all the developers are the ones donig the talking and not actually developing.
This may not be news to some of you (I don’t see how, it fits the exact definition of news), but it’s a good thing no matter how you look at it.
The interfaces in the current TCP/IP stack for TCP/IP security (filtering for local host traffic), the firewall hook, the filter hook, and the storage of packet filter information has been replaced with a new framework known as the Windows Filtering Platform (WFP).
Translation : will break every network related third party software out there.
What’s up with swapping out critical OS components in the beta stage of product that will suposedly ship real soon now anyway ?
Who says they are just swapping it out now?!
These are the things they have been working no since the reset, but they simply wouldn’t announce it until they were far enough along that they were pretty sure these components would not be dropped.
IF they are changing the way that drivers are written, I wonder what effect this will have on the NDIS API. If there are significant API changes as part of this, this means that old drivers might not work on Vista. It may also be an attempt to break the ndis technology in FreeBSD and other systems which is used today for, eg, wireless cards that have no native driver.
Oh pulease, Microsoft couldn’t give two hoots what is happening in the FreeBSD world, let alone the Linux world – they’ve already got enough on their plate with Vista – trying to convince their existing customers of Windows 9x/2000/XP that Vista is the future – whilst at the same time, trying to persuade them to upgrade to Windows XP 18 months before the release of Windows Vista.
From what it sounds like, the NDIS 5.1 will be simply a matter of changing a few things; the API is documented, it would be simply a matter of the Project Evil programmers to read up on the API changes/additions and add those changes when and where necessary.
Mondo.. World.
Office World. Megalomania rulez.
W l’Italia anyways
>Unbelievable how some people wonder if the new TCP/IP
>stack will communicate with OSS TCP/IP. Totally
>unrealistic. Image the news papers: Windows Vista not
>able to browse 95% of the WWW.
You under-estimate the depth of Microsoft’s monoculture. They’d be well capable of this if their customers wouldn’t scream until hoarse.
Office Mongo seems more like it.
I suspect HeathCliff came to mind?
It’s very funny. I think you don’t know anything about networking in Vista and in general. But i understand you: it’s easy to be a sarcastic and incompetent somebody.
The Routing compartments thing looks cool. I’m not sure exactly how many people would benefit from it, since I’d imagine most rdesktop users tend not to use VPN’s…
That said, it looks like one of those technologies that once it’s in there, people will start building nifty stuff around it.
Now – how long to implement this under Linux.
See, that’s the big thing. A lot of the things going into Vista aren’t that amazing by themselves. But they provide the technologies for developers to make some pretty frickin’ sweet stuff.
Microsoft doesn’t make the really cool stuff, they provide the platforms and technologies for other people to.
Ehmm in EAST-Germany an popular Condom Mark was called Mondo 🙂
Why is it that when Microsoft improves their software and makes things better for everyone that tons of people act like jerks and jacka$$es?
I am not saying that everything that is made by Microsoft is so golden, but damn can’t we just enjoy some news about something without morons posting crap.
is that Mondo is a SKU name that the Office team uses internally. You’ve heard of Office Pro? Office Standard? Office Small Business Edition? Mondo is the SKU that includes every piece of code that is a part of any ‘Office’ product. It is an internal only SKU used for testing by members of the Office team. Mondo has been around for a long time. I’d say it is very unlikely that this will become the product name.
http://windows.czweb.org/show_article.php?id_article=99“>Windows