Re: [homenet] HNCP, RA and DHCPv4

2015-07-31 Thread Tim Chown
Hi, On 27 Jul 2015, at 14:58, Juliusz Chroboczek j...@pps.univ-paris-diderot.fr wrote: snip Renumbering is not as smooth -- it appears to be impossible to remove a set of addresses wholesale, retracting a set of PIOs merely causes the old addresses to become deprecated. Since after a

Re: [homenet] some IS-IS questions

2015-07-31 Thread Tim Chown
On 28 Jul 2015, at 21:21, Gert Doering g...@space.net wrote: Hi, On Tue, Jul 28, 2015 at 11:55:16AM -0400, Ted Lemon wrote: This means that the end user can be assumed to plug home routers together in arbitrary topologies, [..] Our goal is for this to work in a multihomed IPv6

Re: [homenet] HNCP, RA and DHCPv4

2015-07-31 Thread Juliusz Chroboczek
Much will depend if the ISP is offering their customer a ‘graceful’ renumbering event. If they do, then the principle applied in RFC4192 could be applied, and you will have a period where both prefixes (old and new) co-exist, before the old prefix is removed. In that case, the older

Re: [homenet] HNCP, RA and DHCPv4

2015-07-31 Thread STARK, BARBARA H
Much will depend if the ISP is offering their customer a ‘graceful’ renumbering event. If they do, then the principle applied in RFC4192 could be applied, and you will have a period where both prefixes (old and new) co- exist, before the old prefix is removed. In that case, the older

Re: [homenet] HNCP, RA and DHCPv4

2015-07-31 Thread STARK, BARBARA H
Actually RFC 6204 (and its successor 7084) have a requirement that enforces keeping it in the RA for at least 2h. HNCP makes following 7084 mandatory atm. If you're referring to RFC 7084's: L-13: If the delegated prefix changes, i.e., the current prefix is replaced with a new

Re: [homenet] HNCP, RA and DHCPv4

2015-07-31 Thread Steven Barth
If you're referring to RFC 7084's: L-13: If the delegated prefix changes, i.e., the current prefix is replaced with a new prefix without any overlapping time period, then the IPv6 CE router MUST immediately advertise the old prefix with a Preferred Lifetime

Re: [homenet] HNCP, RA and DHCPv4

2015-07-31 Thread STARK, BARBARA H
Why don't you set the valid lifetime to 0 as well? If a new host is connecting to the network while you're advertising the max(old valid lft, 2h) valid lifetime, it will actually auto-configure itself with an address from the withdrawn prefix. If you set valid lifetime to 0, it won't.

Re: [homenet] HNCP, RA and DHCPv4

2015-07-31 Thread Tore Anderson
* Steven Barth If a new host is connecting to the network while you're advertising the max(old valid lft, 2h) valid lifetime, it will actually auto-configure itself with an address from the withdrawn prefix. If you set valid lifetime to 0, it won't. Sounds good, i don't mind. Just have to

Re: [homenet] HNCP, RA and DHCPv4

2015-07-31 Thread Tore Anderson
* Steven Barth In an ungraceful case (flash renumbering) we stop announcing the prefix in HNCP and the individual routers who have assigned it, MUST deprecate it according to RFC 7084 (not just stop announcing it in RAs). This deprecation sets preferred lifetime to 0 and valid lifetime to max