You're probably right.
On the other hand, as per Ole Troan's earlier email (which I agree
with), I don't think all router implementations should be required to
support multi-sites.
I think Ole's comments apply to specialized routers. If you are
marketing a general purpose router, you almost have to put in
support since you don't know how or where they will be deployed.
Not necessarily. Even if we go to the trouble of fully defining
how site-local address will work, it is still possible that the
market will decide not to support them. If no one builds SBRs,
no one will have effective site borders.
Are there any commercial routers today that include SBR support?
Who has an implementation of an SBR that includes routing protocols?
Brian, I know you wrote one with RIPng. Are there others? I'd
be very interested in hearing about implementation experiences.
Does anyone have a SIP or SCTP implementation that will work in a
multi-sited environment? Or other complex applications that pass
addressing information? What were your experiences?
Does anyone have an operational network that uses site-local
addresses to provide private addressing within a globally connected
network? Why did you choose to do this? What were your experiences?
Please note that I am interested in deployed, operational networks,
not theoretical deployments.
Have any network administrators installed a two-faced DNS that
returns IPv6 site-local addresses within the site, but not externally?
How did that work out?
What doesn't really exist is the filtering of prefixes being put
into route exchange messages based on an arbitrary index (zone
id).
The other big issue is how the routing table(s) are built and
managed. That can be a big hit on memory/storage space.
Brian, could you elaborate on these things?
Thanks,
Margaret
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
