I think it's great the folks are starting to consider the difficult problems
associated with site-local addresses in particular and scoped addresses in
general. In the past these have been glossed over with hand-waving arguments
that scopes would ``just work'' with minimal application involvement and a
little DNS magic.
Before you try to solve the problems by effectively reducing scopes to a
degenerate case of one and restricting site-local addresses to sites with
no global addresses (or even with no external connectivity), please keep in
mind that site-local addresses have been offered up as the solution to a
number of other problems which themselves were difficult to hand-wave away.
For example, the ability to have long-term tcp connections within a site in
the face of global address renumbering has--given the lack of any protocol
or application support for that renumbering--been pushed onto site-local
addressing. (The problem is hardly confined to tcp, but that's the usual
example cited.)
Any language that reduces site-local addresses to second-class citizens (or,
worse, implies that they should not be used concurrent with global addresses)
will give stack and application vendors an excuse to fail to support such
configurations. I don't think you want to open such a huge can of worms as
it will entail revisiting every problem that has been ``resolved'' with an
admonition to simply use site-local addresses.
Dan Lanciani
ddl@danlan.*com
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
