Keith; At 09:27 PM 11/12/02 -0500, Keith Moore wrote:
You keep saying that some apps will fail with scoped addresses. My poor brain can't grasp why this is so. Can you give me a detailed example of how an app will fail if it has multiple scoped addresses to choice from? I don't mean that it may be hard to for the app to decide which address to use. Yes that's a hard problem, and we don't have a solution to it yet, but that doesn't seem a good enough reason to kill site locals to me. I also don't mean that an app can get confused and it will fail to connect to the correct proper destination if it uses a scoped address at the wrong time. Yes this can happen, but it's still part of the address selection problem, not a basic problem with an app.[snip snip snip] No. Scopes reduce the ablity of the network to support apps. They make it harder to produce an app that works independently of network location, and they don't add a single extra capability that wasn't present already.
I'm looking for something like FTP and NAT. FTP exchanges IP addresses in data messages which fail when NATs cause these addresses to change. There are all kinds of kludges that try to work around this problem, but the basic issue is that the E2E property of IP was lost and the apps suffer for this change.
I don't see the same thing happening with site-local's, everyone agrees that they aren't a v6 NAT replacement so apps are not allowed to propagate site locals outside of the site boundary. Yes, hosts need to be aware of the site boundary, but that is still an address selection problem not a problem with the app itself. Site-locals are unique within the site boundaries and look just like a global IPv6 address, so what is a specific example where an app will be broken by using a site-local address?
Rich
Why in the world you should be trying to promote dysfunction in the network is beyond me.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] --------------------------------------------------------------------
------------------------------------ Richard A. Carlson e-mail: [EMAIL PROTECTED] Network Research Section phone: (630) 252-7289 Argonne National Laboratory fax: (630) 252-4021 9700 Cass Ave. S. Argonne, IL 60439 -------------------------------------------------------------------- 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] --------------------------------------------------------------------
