Re: [homenet] HNCP: avoiding renumbering

2015-08-17 Thread Gert Doering
Hi, On Sun, Aug 16, 2015 at 11:57:07PM -0700, Toerless Eckert wrote: I don't know why Juliusz called stable storage bad. I'd assume it has to do with flash write cycles on $30 routers... Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG

Re: [homenet] HNCP: avoiding renumbering

2015-08-17 Thread Juliusz Chroboczek
I don't know why Juliusz called stable storage bad. Ideology. Soft state good, hard state bad. A network protocol should be able to recover all the data it needs just by consulting its neighbours. If it needs stable storage to function, then it's a failed design. Yeah, I know, I'm a fanatic.

Re: [homenet] HNCP: avoiding renumbering

2015-08-17 Thread Markus Stenberg
On 17.8.2015, at 9.57, Toerless Eckert eck...@cisco.com wrote: On Mon, Aug 17, 2015 at 09:41:24AM +0300, Markus Stenberg wrote: Just like in some other old workplace, cough, ???if it does not work without IPsec, do not expect it to work with it???. Should i even try to understand that

Re: [homenet] HNCP: avoiding renumbering

2015-08-17 Thread normen.kowalewski
authors. BR, Normen -Ursprüngliche Nachricht- Von: Markus Stenberg [mailto:markus.stenb...@iki.fi] Gesendet: Montag, 17. August 2015 10:11 An: Toerless Eckert Cc: homenet@ietf.org; Juliusz Chroboczek Betreff: Re: [homenet] HNCP: avoiding renumbering On 17.8.2015, at 9.57, Toerless Eckert

Re: [homenet] HNCP: avoiding renumbering

2015-08-17 Thread Markus Stenberg
On 17.8.2015, at 14.19, normen.kowalew...@telekom.de wrote: Hi, +1. a) Any idea how often this data changes and really needs a re-write in “a typical home ;-) ? Not very often, at least if you don’t bother to prune ‘old’ stuff much (it depends a bit, but most conservative setup would

Re: [homenet] HNCP: avoiding renumbering

2015-08-17 Thread Toerless Eckert
On Mon, Aug 17, 2015 at 01:01:04PM +1200, Brian E Carpenter wrote: That may be desirable to limit churn, but must not be depended on. The architecture is explicit on pp 25-26 that renumbering is an expected event: https://tools.ietf.org/html/rfc7368#page-25 The addressing, routing and naming

Re: [homenet] HNCP: avoiding renumbering

2015-08-17 Thread Toerless Eckert
On Mon, Aug 17, 2015 at 09:41:24AM +0300, Markus Stenberg wrote: Just like in some other old workplace, cough, ???if it does not work without IPsec, do not expect it to work with it???. Should i even try to understand that reference ? ;-) I do not expect homenet stuff to do much better

Re: [homenet] HNCP: avoiding renumbering

2015-08-17 Thread Markus Stenberg
On 17.8.2015, at 9.22, Toerless Eckert eck...@cisco.com wrote: On Mon, Aug 17, 2015 at 01:01:04PM +1200, Brian E Carpenter wrote: That may be desirable to limit churn, but must not be depended on. The architecture is explicit on pp 25-26 that renumbering is an expected event:

Re: [homenet] HNCP: avoiding renumbering

2015-08-17 Thread Eric Vyncke (evyncke)
I think that Brian has summarized this renumbering avoidance as desirable but nothing to be depended on -éric On 17/08/15 08:57, homenet on behalf of Toerless Eckert (eckert) homenet-boun...@ietf.org on behalf of eck...@cisco.com wrote: On Mon, Aug 17, 2015 at 09:41:24AM +0300, Markus Stenberg

[homenet] HNCP: avoiding renumbering

2015-08-16 Thread Juliusz Chroboczek
When an HNCP router is restarted, the prefixes it allocated to a link are adopted by neighbouring routers; if the router then restarts, it will agree to the prefixes advertised by its neighbours, which avoids renumbering. Unfortunately, this only applies to link with multiple HNCP routers: on a

Re: [homenet] HNCP: avoiding renumbering

2015-08-16 Thread Markus Stenberg
On 16.8.2015, at 14.40, Juliusz Chroboczek j...@pps.univ-paris-diderot.fr wrote: When an HNCP router is restarted, the prefixes it allocated to a link are adopted by neighbouring routers; if the router then restarts, it will agree to the prefixes advertised by its neighbours, which avoids

Re: [homenet] HNCP: avoiding renumbering

2015-08-16 Thread Juliusz Chroboczek
which avoids renumbering. Why do we care? Homenets need to be renumbering-proof anyway, because the ISP might change the prefix anytime. You're right, that deserves clarifying. We're trying really hard to make sure that in no circumstances is running a Homenet router worse than running an

Re: [homenet] HNCP: avoiding renumbering

2015-08-16 Thread Brian E Carpenter
On 17/08/2015 11:01, Juliusz Chroboczek wrote: which avoids renumbering. Why do we care? Homenets need to be renumbering-proof anyway, because the ISP might change the prefix anytime. You're right, that deserves clarifying. We're trying really hard to make sure that in no circumstances

Re: [homenet] HNCP: avoiding renumbering

2015-08-16 Thread Brian E Carpenter
On 17/08/2015 11:01, Juliusz Chroboczek wrote: which avoids renumbering. Why do we care? Homenets need to be renumbering-proof anyway, because the ISP might change the prefix anytime. You're right, that deserves clarifying. We're trying really hard to make sure that in no circumstances

Re: [homenet] HNCP: avoiding renumbering

2015-08-16 Thread Brian E Carpenter
n 17/08/2015 01:01, Markus Stenberg wrote: On 16.8.2015, at 14.40, Juliusz Chroboczek j...@pps.univ-paris-diderot.fr wrote: When an HNCP router is restarted, the prefixes it allocated to a link are adopted by neighbouring routers; if the router then restarts, it will agree to the prefixes