Re: [addr-select-dt] Proposed default policy table

[Aleksi Suhonen <[e-mail]>]

Hi,

Tony wrote:
> I suggest leaving 10, 40,&  80 in the precedence so people can move IPv4 or
> ULA around without feeling the need to rewrite the other labels (they don't
> have to, but an obvious hole to park it in reduces confusion).

The number of bits in the precedence value has not been defined, but I 
understand that most implementations use at least 32 bits anyway. I 
would like to see the default precedence values multiplied by 100 to 
leave more room for algorithmically generated entries and manual tinkering.

There are only 4 values available between fc00::/8 and fd00::/8 for 
example. Those could be easily consumed after a couple of corporate fusions.

I guess the idea has been that local administration can override all 
values to their liking. However, my understanding of the best practises 
for system and network administration is that the defaults are changed 
as little as possible. And the defaults should preferably "shine 
through" from under local modifications. This means that when the 
defaults are changed due to some software update, they might adversely 
interfere with the local changes.

I don't mind it if the default precedences are multiplied by even more 
than a hundred, I just feel it is important that there should be more 
space between the default values.

Tony Hain also wrote:
 > Precedence  Label  Prefix
 > ----------  -----  --------------------------------
  ...
 >          1      6  fec0::/16

Aren't we removing site local completely while we're at it? Or if it 
should be kept around, then why not add 3ffe::/16 too for the same reason?

-- 
	Aleksi Suhonen
	Department of Communications Engineering
	Tampere University of Technology