In the context of the HOMENET working group, one imagines that restoring
general end-to-end reachability is arguably a worthy goal.
+1
+1
Sander
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
google.com' might cause some problems... With DNSSEC in place it can still
cause a denial of service when unsigned or invalidly signed data is returned.
Met vriendelijke groet,
Sander Steffann
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org
No more than a DHCPv6 server saying please use this DNS server for
everything. Right?
Right.
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
HI,
So let's just say that giving a single /64 to the home is incompatible with
homenet architecture, and we need more addresses. I'm fine with that.
Yes please. I think some ISPs *need* to get a signal like this.
Sander
___
homenet mailing list
Op 15 feb. 2014, om 11:35 heeft Lorenzo Colitti lore...@google.com het
volgende geschreven:
Which ones are those, though? I mean - we can certainly write this up as is,
but if it doesn't work on Windows, Mac OS, or iOS, then... how much use will
it be in the real world? Given that homenet
Hi,
Op 1 jun. 2014, om 12:50 heeft Gert Doering g...@space.net het volgende
geschreven:
On Sun, Jun 01, 2014 at 10:47:03AM +0200, Pierre Pfister wrote:
So even if most will agree that supporting multiple routing protocol is a
madness in the general case.
It?s not that hard to ?support it?
Hi Tim,
Just as a reminder, here is what we converged on at IETF89 for text in the
homenet arch. The “zero or one” protocol message was clear. I don’t recall a
clear answer on whether to pass config info via the routing protocol or a
separate protocol, but as HNCP shapes up as a proposal I
My opinion is that homenet shouldn't require new functionality in the host
stack for it to work, but if we can present suggestions for enhancements in
the host stack that makes things work better, and also enhance homenet to
take advantage of enhancements in host stacks to make things work
I haven't even mentioned source address selection, as that doesn't come
into play for a singlehomed homenet - but as soon as the homenet gets
multihomed, applications would benefit a LOT from doing intelligent
source address selection. Like in presenting users a selection menu
use ISP? -
Hi,
Op 14 okt. 2014, om 18:27 heeft Ted Lemon mel...@fugue.com het volgende
geschreven:
On Oct 14, 2014, at 11:22 AM, Sander Steffann san...@steffann.nl wrote:
One thing that does worry me is every application developer having to
re-invent the code for all of this (find labels, actually
Hi James,
Consider a hypothetical router that has the regular automatic default
behavior of commissioning a new standalone network while discovering any
existing networks that it already possesses the credentials to join. Now
consider what happens when devices of this category are
Hi Ted,
My point was that homenets should have ULAs, and should not use GUAs for
local communication, because GUAs can be flash renumbered, and the use of
them on the local wire has the potential to cause disruptions on the local
wire that could be prevented by using ULAs. And that there
Hi,
Op 16 okt. 2014, om 15:22 heeft Lorenzo Colitti lore...@google.com het
volgende geschreven:
Per the table in http://tools.ietf.org/html/rfc6724#section-2.1 it will pick
the GUA as a destination address, and per Rule 6, it will choose the GUA to
connect to it.
Do you know if
Hi Barbara,
OTT video does not use multicast. IPTV deployments do use multicast. Those
that I'm aware of require use of the provider-supplied CE router, which has
an IGMP proxy (and MLD proxy if IPv6 multicast is supported) for LAN-to-WAN
multicast management. Where Wi-Fi distribution of
Hi,
All these discussions about the routing protocol are making me despair... What
the *** is wrong here in the IETF? What happened to producing working solutions
and specs? All this discussion about which routing protocol is capable of doing
what, my protocol is as good as yours, bashing each
Hi,
Op 10 aug. 2015, om 10:20 heeft Lorenzo Colitti lore...@google.com het
volgende geschreven:
Personally I doubt that in the market segment we're talking about (which
includes many vendors that just take open source implementations, integrate
them, and ship them) vendors will
Hi Brian,
If that makes sense (for any value of IsBabeliS) I don't think we have a
problem.
I would suggesting adding text near the beginning stating that HNCP is
agnostic
about the routing protocol, but that a single routing protocol must be used.
And that single routing protocol is ...
Hi Barbara,
> Should we really only suggest that the router dynamically probe the quality
> of wireless links? Or would it make sense to suggest dynamic probing of all
> links, because assuming the entire path between 2 routers uses a single
> physical layer technology may not be a good
> Op 18 jun. 2019, om 17:03 heeft Ted Lemon het volgende
> geschreven:
>
> On Jun 18, 2019, at 10:56 AM, Daniel Migault
> wrote:
>> I am also questioning on whether we should provide some sort of
>> recommendations for the UI. While we are not UI designers, I believe some
>> properties
19 matches
Mail list logo
