Re: [homenet] In-network connectivity and HNCP: IPv6 ULA

2018-07-19 Thread Juliusz Chroboczek
> I think the local ULA should be used for all intra-ULA connections. We had a > debate about this about four years ago, and apparently the text in the HNCP > spec reflects the outcome of that discussion, but I think we understand the > problem better now and we should fix this. Agreed.

Re: [homenet] In-network connectivity and HNCP: IPv6 ULA

2018-07-19 Thread Juliusz Chroboczek
I've re-read Section 6.5 of 7788, and it looks like I was wrong. Sorry, I should not be writing technical mails in the middle of the night. As far as I can tell from the wording of 6.5: - creating ULA is SHOULD if there's no global IPv6, MUST NOT otherwise; - creating private IPv4 is MAY if

Re: [homenet] In-network connectivity and HNCP: IPv6 ULA

2018-07-18 Thread Ted Lemon
Juliusz, with all due respect, if you have a connection over IPv4 and suddenly your IPv4 network is deconfigured, your connection will hang. I know this because that's what happened. This is not good behavior, and should not be the default behavior of homenets. On Wed, Jul 18, 2018 at 10:29

Re: [homenet] In-network connectivity and HNCP: IPv6 ULA

2018-07-18 Thread Juliusz Chroboczek
>> But if we want homenet to be widely adopted, I do not think this is the >> correct default behavior: it violates the principle of least surprise. > There's no surprise, it just works. RFC 6724, Section 6, Rule 8. Er, no. ULAs have global scope. My bad. -- Juliusz

Re: [homenet] In-network connectivity and HNCP: IPv6 ULA

2018-07-18 Thread Juliusz Chroboczek
> In order for IPv6 to be useful, you need naming to work. No argument here. > But if we want homenet to be widely adopted, I do not think this is the > correct default behavior: it violates the principle of least surprise. There's no surprise, it just works. RFC 6724, Section 6, Rule 8. --

Re: [homenet] In-network connectivity and HNCP: IPv6 ULA

2018-07-18 Thread Ted Lemon
Sure. If no services are advertised over IPv4, then we needn't offer IPv4 on the network at all. But if we do offer IPv4 on the network, it should be stable, and not vanish at the whim of the ISP. On Wed, Jul 18, 2018 at 9:52 PM, Brian E Carpenter < brian.e.carpen...@gmail.com> wrote: > Ted,

Re: [homenet] In-network connectivity and HNCP: IPv6 ULA

2018-07-18 Thread Brian E Carpenter
Ted, On 19/07/2018 13:36, Ted Lemon wrote: > In order for IPv6 to be useful, you need naming to work. We had this > discussion when I brought this up last year. It should be possible for an > IPv6-only homenet to work. But if we want homenet to be widely adopted, I > do not think this is the

Re: [homenet] In-network connectivity and HNCP: IPv6 ULA

2018-07-18 Thread Ted Lemon
In order for IPv6 to be useful, you need naming to work. We had this discussion when I brought this up last year. It should be possible for an IPv6-only homenet to work. But if we want homenet to be widely adopted, I do not think this is the correct default behavior: it violates the principle of

[homenet] In-network connectivity and HNCP: IPv6 ULA

2018-07-18 Thread Juliusz Chroboczek
During his talk, Ted claimed that he lost all connectivity when his uplink went down. This should not happen -- HNCP normally maintains an IPv6 ULA that remains stable no matter what happens to DHCPv6 prefix delegations or DHCPv4 leases. This is described in Section 6.5 of RFC 7788, and it is