> > Some apps care about having consistent view of addressing across all > > locations in the network. > > The trouble is that while filters exist this will NEVER be true, in the > general case.
filters don't mess up addressing. ambiguous addresses do. > In closing, three guidelines / work items: > > * Applications should not assume that all addresses are equal. applications should not have to know which addresses are more equal than others. or to state this better, it's fine if apps simply avoid passing some kinds of addresses around as long as they can easily tell which ones to pass around and which ones to not pass around. it's not fine if there's not an easily-identifiable, portable address available for every host that is expected to work with an app. > * Applications should not assume that addresses can be forwarded at-will, > unless provided with additional (configured?) information that would support > this assumption. applications should be able to forward addresses to other hosts; this is an essential capability. that doesn't mean that they can expect those addresses to be usable from remote locations. but if they're not usable, the reason should be either network failure or administrative prohibition - in other words, something that the app should not be expected to work around. > * Applications that do not care to do their own address management need a > higher level abstraction to the current sockets and getaddrinfo APIs. not sure what you mean by this. Keith -------------------------------------------------------------------- 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] --------------------------------------------------------------------
