On Wed, Aug 06, 2003 at 11:25:56AM -0700, Christian Huitema wrote: > > Let's be clear. Our group (Windows Networking) has received a lot of feedback from > developers of applications on the Windows platform. The negative developers' > feedback was mostly centered on the difficulty of identifying the scope of an > address, specially when a node is connected to several sites (e.g. home network and > VPN to the corporate network), or when a node moves from site to site. Since the > scope is not indicated in the address itself, applications have to keep track of a > "site identifier" of some kind. The bottom line is that ambiguity hurts. The local > scope nature also hurts, but not quite as much; it is another case of limited > connectivity, which is a common "feature" in many networks.
Change the flow label to scope label, and get those bits in use ;-) Tim -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
