Hello,

A few quick comments on the draft.  Sorry for lack of content.

Substantial:

   This document proposes an approach to allocating IPv6 Site-Local
   address so they are globally unique and routable only inside of a
   site.

==> it would be good to go a bit more in depth to how this is actually a 
problem.  For some it surely isn't; if they don't need to prepare for 
site-mergers, for example.

5.0 Disadvantages

      - No default aggregation of site-local prefixes inside of the
        site.
      - If areas are used and the site is merged with another site, the
        areas that are duplicated will have to be advertised as /64
        prefixes (with the loss of aggregation) and later renumbered.

==> 48-2 bits seems a bit unreadable, that is: if you see an EUI48 
address, it probably isn't apparent that it corresponds to the 46 bit site 
identifier.  So, it would probably make sense to have them be the same.

==> another disadvantage is that the sites should really be /48's to make 
mergers with Internet global prefixes & addressing easier.

Editorial:

2.0 Acknowledgments

==> s/dg/dge/
==> this section should be around security considerations section, below

   aggregation).  Each /64 prefix in the area would occupy an entry in a
   routers forwarding table.

==> s/router/router'/

   Site boarder routers MUST NOT forward any packets with site-local
   source or destination addresses outside of the site.

==> s/boarder/border/

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

--------------------------------------------------------------------
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]
--------------------------------------------------------------------

Reply via email to