> Yes, this can be an issue, but it's not really a serious problem. forcing apps to deal with scopes at all is a serious problem. being able to compare scopes from different addresses only addresses one small aspect of that problem.
though making an app 'protocol independent' is one example of having apps deal with scopes since presumably the app may have to deal with a mixture of v4 and v6 addresses, a mixture of v4-only and v6-only and dual-stack hosts, and various kinds of connectivity (no v4, local v4, global v4) X (no v6, local v6 only, global v6) it should not be assumed that it's appropriate to expect every app to be protocol independent. there will be v4-only apps. there will be v6-only apps. there will be apps that can run one or the other but not both. this is a natural consequence of v6 deployment scenarios. app vendors shouldn't expect that limiting themselves to scoped addresses provides anything in the way of security other than delusion. it's not appropriate for the vendor to assume that the site or local environment is secure. bottom line: there is insufficient justification for expecting apps to deal with scoped addresses. 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] --------------------------------------------------------------------
