> | - Or assume that the host distributes different flows > to different default > | routers. How will you guarantee that the routers will > not pick the same flow > | label values (which would be a problem if the flows go > to the same > | destination)? > | > | - Or what if the host is "dumb" only with some flows, > but will assign flow > | label values for some other flows. How will you > synchronize the flow label > | setup in the host and the router? > > Any of these can be handled by administrative control if > necessary (the > first few bits in the flow label identify the source - 0 -> > original host, > 1, 2, .. N identify a router). > > Smart routers are possible, not necessarily smart though. >
=> Sorry but this is very unrealistic. Setting the flow label at the default router, pretty much rules out the multiple default router case for a realistic scenario. I don't think that should be allowed. The node initiating the connection is the node with most information about it's flow and it should be the one setting it. Let's not try to buit any more dependencies on the default routers. Hesham -------------------------------------------------------------------- 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] --------------------------------------------------------------------
