Site-local are simply comparable with the private IP-addresses of IPv4
(10.x.x.x,...), where the Network Administrator bans all internal transports
from going out. Only here the config is implemented into the router...
There are no big changes that impact higher-level software (e.g.
authentication servers), so selection of these servers can be done using
IPv6, but still we need something else (e.g. DNS as MS-Win2k-Domain
uses)....
It simply has nothing to do with this and won't interfere with it in any
way...
- Joris
>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]On Behalf Of Tony Hain
>Sent: Wednesday, 04 April 2001 0:30
>To: Margaret Wasserman; Tomohide Nagashima
>Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
>[EMAIL PROTECTED]; [EMAIL PROTECTED];
>[EMAIL PROTECTED]
>Subject: RE: what is a site?
>
>
>I would normally let this go, but there has been enough
>confusion on this
>subject that it needs to be very clear. Both Margaret and KRE
>are correct, a
>site is defined by the boundary of a contiguous routing domain
>configured by
>the network administrator (I assume the ISP in Margaret's definition is
>providing a managed private network or just defensively
>filtering non-global
>addresses). It is nothing more, and has no other constraints.
>
>If someone were creating documentation and wanted to show a 'typical
>example' of a site, using a building or campus would be a
>reasonable way to
>describe the concept. But there should not be any language in
>the standards
>restricting it more than Margaret has here.
>
>Tony
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
