Hi!

> bin ich da mal wieder nicht auf der Hoehe der Zeit?
[...]
> > > But for my understanding what is wrong/missing with site-local
> > > addresses definitions in RFC 2373 IPv6 Addressing Architecture:

> > There is nothing wrong/bad, but IETF soon as possible will deprecate the
> > Site-Local address space.
> 
> Stimmt das? Wenn ja, wieso?

In Wien gab es zum Adressenthema vom IAB ein open architecture meeting,
bei dem wohl dieser Schluss gezogen wurde.

Aus meinen Notizen:

- Issues:
  o multihoming
  o assembling a local network without necessarily
    having to contact an ISP to obtain address space
    (e.g., home net)
  o renumbering local networks without significant pain
    Some proposed solutions are challenged in terms of:
    * providing referential integrity - how is referential       
      integrity maintained when identifiers are not globally
      unique or are overloaded?
    * choosing between different identifiers for an object which       
      has different "reachability" and the reachability is context-dependent
    * security/transiting trust in layered address resolution - 
      how do we secure dynamic update of the "reverse path" if the
      trust relationship between a DHCP server and a DHCP client is
      very weak? A: wavesec.org ?
    * providing solutions that work across all layers of the stack and
      all areas - how do we find a solution that is great for
      routing but also great for security?

Dort wurden auch site-local Adressen diskutiert:

- ipv6
  o unique global addresses
  o site-local
  o link-local
  one can call it address realm membership
  OK, but what does this really solve/help ? And how they are being used ?
- what is site-local, what is a site ?
  o wireless multihoming becoming commonplace (wifi, bluetooth, umts etc)
  o add hoc role
  o role based access control
  o context is all

- scoping is a filtering function and will exist no matter
  what prefix is used
- filter boundaries are an operational decision and not
  appropriate for rigid definition
- local scope:
  o no registration required
  o stable addresses, local app persistence across connectivity events
  o private: well known filters possible

Irgendwie (und da kann ich die Diskussion nachvollziehen) ist unklar,
was site-local bringt und wie's verwaltet wird und ob da nicht durch
die Hintertuer rfc1918 wieder kommt.

Andererseits gibt es Nutzerkreise, von denen folgende Anekdote
berichtet wurde:

Some bank said: we not use v6 if we do not have assured local
adress space that will never be routed.

-- 
MfG/Best regards, Kurt Jaeger                                  17 years to go !
LF.net GmbH        fon +49 711 90074-23  [EMAIL PROTECTED]  
Ruppmannstr. 27    fax +49 711 90074-33
D-70565 Stuttgart  mob +49 171 3101372
_______________________________________________
ipv6 mailing list
[EMAIL PROTECTED]
http://listserv.uni-muenster.de/mailman/listinfo/ipv6

Antwort per Email an