Re: New I-D Submitted (Re: Newbie Question about addressing impacts)
Iljitsch van Beijnum <[email protected]> Fri, 22 Oct 2004 14:41:53 +0200
| Newsgroups | gmane.ietf.multi6 |
|---|---|
| Message-ID | <[email protected]> |
On 15-okt-04, at 11:01, Arifumi Matsumoto wrote: > In short, in our model, ISPs provide Source Address Selection > Policies as well as Prefix Delegation Info by DHCP. > The consumer edge router receives those policies (from > multiple ISPs) and re-distribute them to end nodes. > End nodes put them into policy table, which leads to > appropriate source address selection. > http://www.nttv6.net/~arifumi/draft-arifumi-multi6-sas-policy-dist > -00.txt Hm, I'm worried about the policy information becoming too extensive to fit comfortably in DHCP or RA packets. I guess it would be possible to broadcast basic policy information this way and then create a cache of more specific information on-demand, e.g. when ICMP messages come in. (The advantage of using RA here is that when connectivity changes, a lot of hosts can be informed quickly about a new policy.) > http://www.nttv6.net/~arifumi/draft-arifumi-ipv6-nd-source-address- > selection-opt-00.txt > http://www.nttv6.net/~arifumi/draft-hirotaka-dhc-source-address- > selection-opt-00.txt Why must the padding be ones? On many systems, newly allocated memory is filled with zeros, so this would be easier. And then there's tradition. :-)