Re: [homenet] [Int-area] Evaluate impact of MAC address randomization to IP applications

2020-09-22 Thread David R. Oran
On 22 Sep 2020, at 17:18, Stephen Farrell wrote: Hiya, On 22/09/2020 22:08, Lee, Yiu wrote: Hi Stephen, Thanks for the notes. Actually, we believe that there are good privacy reasons to randomize mac-address. This BoF isn't trying to "fix" randomized mac-address. On the contrary, we want the

[homenet] -CoDel

2019-03-15 Thread David R. Oran
On 15 Mar 2019, at 8:34, Toke Høiland-Jørgensen wrote: Juliusz Chroboczek writes: PIE [...] lends itself better for implementation in existing hardware, or hardware with small modification. Could one of you please explain why? With the caveat that I have never worked with any of this har

Re: [homenet] Introduction to draft-ietf-homenet-simple-naming

2018-05-31 Thread David R. Oran
On 30 May 2018, at 19:39, Brian E Carpenter wrote: On 31/05/2018 08:53, Juliusz Chroboczek wrote: Well, let me invent something. I throw together my network and it names the printers as printer1 and printer2. Being a stickler, I decide to rename them as Printer 1 and Printer 2. I m

Re: [homenet] Comments requested for draft CER-ID

2014-10-27 Thread David R Oran
Silly question: Isn’t the border defined by a link and not a router? What if you have uplinks to two different ISPs on the same router? This seems to assume there’s only one border link on a router, and that router connects to only one external entity. On Oct 27, 2014, at 8:59 AM, Michael Klobe

Re: [homenet] HNCP security?

2014-09-18 Thread David R Oran
On Sep 18, 2014, at 11:46 AM, Rene Struik wrote: > It seems that the cryptographic literature needs to be rewritten now ... > > == > Anything you can do with a cert, you can do with raw public keys, and you > don't need CA's. See RFC4871 for an example. I would have thought it was the opposite

Re: [homenet] Unicast DNS within the Homenet?

2012-09-13 Thread David R Oran
On Sep 13, 2012, at 1:12 PM, Michael Thomas wrote: > On 09/12/2012 06:57 PM, Ted Lemon wrote: >> On Sep 12, 2012, at 9:02 PM, Mark Andrews wrote: >>> My machines have names. Those names don't change as I move around >>> the world. Random DHCP servers at coffee shops DO NOT have the >>> abilit

Re: [homenet] naming, what's the problem?

2012-08-08 Thread David R Oran
On Aug 6, 2012, at 2:30 PM, Michael Thomas wrote: > I've been rereading the charter and the -arch document and they both > seem to make a presumption that we actually know what the problems > are in a homenet. At the very least, I'm not convinced that we've captured > what those problems are. Th

Re: [homenet] home networking of a different kind

2012-03-29 Thread David R Oran
On Mar 27, 2012, at 11:13 PM, Jari Arkko wrote: > Not sure if this is on or off-topic for this working group but here's a > recent extension to my home network setup: > > http://thingsonip.blogspot.fr/2012/03/smart-igloos.html > I assume you need special protocols to get through - does that me

Re: [homenet] Name resolution in the homenet architecture document

2012-03-13 Thread David R Oran
On Mar 13, 2012, at 12:23 PM, Ralph Droms wrote: > > On Mar 13, 2012, at 12:16 PM 3/13/12, Ray Bellis wrote: > >> >> On 11 Mar 2012, at 15:22, Fred Baker wrote: >> >>> ICANN is now selling "dotless" names. A name without dots has a defined >>> behavior in most DNS resolvers; they find a way

Re: [homenet] Fwd: I-D Action: draft-haddad-homenet-gateway-visibility-00.txt

2011-10-26 Thread David R Oran
On Oct 26, 2011, at 12:25 PM, Wassim Haddad wrote: > Dear all, > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > Title: Ensuring Home Network Visibility to Home Gateway > > This memo describes a mechanism designed to increase the home gateway > visibil

Re: [homenet] [homegate] HOMENET working group proposal

2011-08-07 Thread David R Oran
On Aug 7, 2011, at 9:16 AM, Pascal Thubert (pthubert) wrote: > Looks obvious, but is it? > Yes. > In one hand, we want the capability to reach anywhere we're allowed to from > home. OTOH, if anything in my home is reachable from anywhere, we are back to > the firewall paradigm. > Why? You a