In your previous mail you wrote:
There was a proposal way back to simply embed the (local) scope
identifier in the address, as an API mechanism, so applications
=> this was already proposed and rejected. Some of us still use
this internally in their kernel and should be able to explain
why this is not a so good idea...
would have one less thing to worry about. At the application level
that could have worked (before Paul's draft - now there are no bits
left in site locals to steak (borrow) for the purpose).
=> PS: I don't believe this is the Paul's idea which is more
a new version of Christian's one (i.e. a new attempt to make
site-local addresses live again, periodic discussion like the
ASCII/last-smart format of RFCs, with same conclusions (too difficult,
keep them where they are, and keep the ASCII format :-)).
Regards
[EMAIL PROTECTED]
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
