[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

IPv6 and Microsoft - An excerpt from an Independent study of mine on IPv6



------ =_NextPart_000_01BE133C.70D31600
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Ramesh,

Thanks for the update on Microsoft!

I' ve seen many emails around Microsoft IPv6 status and it would be just fair 
at this stage to ask directly Richard Draves, the man in charge at Microsoft, 
as we know that his team is actively testing its IPv6 implementation using one 
of our Telebit IPv6 routers connected to the 6Bone.

This might put this issue to bed!

VBR,
Latif
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Latif LADID
Chairman, Global-ISDN
-----------------------------
Vice President, Sales EMEA
Telebit Communications A/S
31, Domaine de Brameschhof
8290 KEHLEN - LUXEMBOURG
(:            + 352 - 30 71 35
Fax:            + 352 - 30 53 64					
*:            [email protected]	
Web Page:    http://www.tbit.dk	
The PAXNET Integrated Solution: IPv4 - IPv6 - ATM - ISDN - FR - X.25
@@@@@@@@ @@@@@@@@@@@@@@@@@@@@@@@

----------
From: 	Ramesh Shanmuganathan[SMTP:[email protected]]
Reply To: 	Ramesh Shanmuganathan
Sent: 	Wednesday, November 18, 1998 03:29
To: 	Spencer Giacalone; 6bone; Steve Hill
Subject: 	IPv6 and Microsoft - An excerpt from an Indepedndent study of mine on 
IPv6

 <<File: ATT00001.txt>>


------ =_NextPart_000_01BE133C.70D31600
Content-Type: text/plain; name="ATT00001.txt"
Content-Transfer-Encoding: quoted-printable

Hi!

I was doing an independent study on IPv6 at Rochester Institute of
Technology as part my master's program.I did happen to look at =
Microsoft's
current state of IPv6 research and development. This is what I found =
from
there web site. I hope it's useful.

Regards,
Ramesh


Microsoft's implementation is a work-in-progress and does not yet =
support
all of the features of the IPv6 protocol. The features that are =
currently
supported are:
=EF=80=AE Basic IPv6 header processing
=EF=80=AE Hop-By-Hop and Destination Options headers
=EF=80=AE Fragmentation header
=EF=80=AE Neighbor Discovery
=EF=80=AE Stateless address autoconfiguration
=EF=80=AE ICMPv6
=EF=80=AE Multicast Listener Discovery (a.k.a. IGMPv6)
=EF=80=AE Automatic and configured tunnels
=EF=80=AE IPv6 over IPv4 (Carpenter/Jung draft)
=EF=80=AE UDP and TCP over IPv6
=EF=80=AE Raw packet transmission

They do not (yet) support mobility, authentication, encryption, or =
routing
headers. Our next major release will have at least the minimum required
mobility support as well as partial authentication and security support.
They have done some interoperability testing at the UNH interoperability
Lab, and have a machine on the 6bone. They do especially encourage other
IPv6 implementers to download their code for testing.

The current release runs on NT 4 and NT 5 build 1773 (or later). Build =
1773
was distributed at WinHEC '98. (NT 5 Beta 2 will be supported when it is
available. NT 5 Beta 1 is not supported.) At this time, Microsoft =
Research
has no plans to support this experimental stack on Windows 95 or Windows =
98.
It is their choice to implement IPv6 in NT as a separate protocol stack =
from
the existing IPv4 stack. This allows for ease of experimentation with =
IPv6
without affecting existing IPv4 functionality.

They also have available applications and utilities such as ping6, =
tracert6,
ttcp6 (over both UDP and TCP), and ftp6/ftpd6. Those for which we can =
freely
distribute the source code are included in the release. For more info, =
visit
MS V6:http://research.microsoft.com/msripv6/


_________________________________________________________________

Ramesh Shanmuganathan
233D Perkins Green
Perkins Road
Rochester
NY 14623
Tel: 716-424-8384/8796
E-mail: [email protected]
Internet: http://www.rit.edu/~rxs6469



------ =_NextPart_000_01BE133C.70D31600--