The scope value is [0..F], but 0 and F are marked as "reserved".
Usually "reserved" values in protocols can be handled by "ignore on receive, zero on send". However, with scope and scoped addressing, I just can't ignore it on receive. What should I do with addresses starting with FF00::/16 FF0F::/16 a) when receiving a packet using those as destination. My first assumption: Drop it b) when application requests sending a packet to such address? My first assumption: reject with error Above logic will be hardcoded in all stacks, so anyone thinking later of redefining the meanings is severly limited. Just wanting to verify that I can do it in above way. Actually, only the value 0 is the problematic one (for 'F' I can just pretend that it is just another level above global, like universal :-). -------------------------------------------------------------------- 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] --------------------------------------------------------------------
