I think the draft is a bit optimistic with respect to its claim of satisfying
homenet requirements. For example, there is a very limited set of multi-homing
topologies where the internal routers don't find themselves asking, "Which way
is up?". Additionally, without source routing, I don't see h
In message <11573.1363356...@sandelman.ca>, Michael Richardson writes:
> Mark the other part is the update-reverse-zone-by-TCP DNS update,
> authorized by TCP. You've talked about this. Do you think we need a
> dnsext action to permit this, or any kind of document outside of
> homenet?
Given th
On 03/15/2013 07:10 AM, Michael Richardson wrote:
Okay, so there would be standards work to do multi-master.
I thought so, but I wasn't clear.
Are there any multi-master implementations using proprietary protocols?
I think that multi-master isn't that important for homenet.
I think that having a
On 03/15/2013 04:04 AM, Robert Cragie wrote:
On 14/03/2013 9:42 PM, Michael Thomas wrote:
On 03/14/2013 10:03 AM, Michael Behringer (mbehring) wrote:
From: Michael Thomas [mailto:m...@mtcc.com]
[...]
In today's world access control is gated at L2 via wpa or similar. Are you
suggesting that w
On 03/15/2013 07:23 AM, Michael Richardson wrote:
Michael> Mark, I am still confused as to whether there is anything
Michael> new/unimplemented here too. If my CER, say, is the master,
probably not, but not every piece of code out there supports the
particular characteristic. I've se
On 3/15/13 10:48 AM, "Livingood, Jason" wrote:
>With the new gTLDs this is certainly a concern. Definitely don't use .home
>since there are many applicants. However, .local is reserved by ICANN so
>it cannot in my understanding become a new gTLD per the gTLD guidebook,
>section 2.2.1.2.1 "Reserved
On 3/14/13 9:50 AM, "Simon Kelley" wrote:
>Lots of homenet-type
>installations will have it set to ".lan" or something similar. Some will
>set it to ".local" only to discover that the .local TLD has been
>usurped.
With the new gTLDs this is certainly a concern. Definitely don't use .home
since
> "Michael" == Michael Thomas writes:
Michael> Mark, I am still confused as to whether there is anything
Michael> new/unimplemented here too. If my CER, say, is the master,
probably not, but not every piece of code out there supports the
particular characteristic. I've seen lots of
> "Mark" == Mark Andrews writes:
Mark> It is quite common for the stealth masters to exist (not
Mark> listed in the NS RRset). It is also quite common for
Mark> recursive servers to have local copies of zones that are in
Mark> use locally but not be listed in the NS RRset. T
> -Original Message-
> From: homenet-boun...@ietf.org [mailto:homenet-boun...@ietf.org] On
> Behalf Of Brian E Carpenter
[]
> > Before we dive into the solution space, Brian, do you agree that the
> framework draft should include this requirement?
>
> Yes, but I think that simplicity o
On 15/03/2013 11:12, Michael Behringer (mbehring) wrote:
>> -Original Message-
>> From: Brian E Carpenter [mailto:brian.e.carpen...@gmail.com]
> [...]
>>> But I think the need goes beyond wireless. If I have visitors, I may not
>>> like
>> it if they plug in a device into the Ethernet sock
> -Original Message-
> From: Brian E Carpenter [mailto:brian.e.carpen...@gmail.com]
[...]
> > But I think the need goes beyond wireless. If I have visitors, I may not
> > like
> it if they plug in a device into the Ethernet socket in the guest room, and
> the
> device has full access to e
On 14/03/2013 9:42 PM, Michael Thomas wrote:
On 03/14/2013 10:03 AM, Michael Behringer (mbehring) wrote:
From: Michael Thomas [mailto:m...@mtcc.com]
[...]
In today's world access control is gated at L2 via wpa or similar.
Are you
suggesting that we have a L3 equivalent? In addition? In repla
On 15/03/2013 00:16, Michael Behringer (mbehring) wrote:
>> -Original Message-
>> From: Michael Thomas [mailto:m...@mtcc.com]
>> Sent: 14 March 2013 17:43
>> To: Michael Behringer (mbehring)
>> Cc: Tim Chown; homenet@ietf.org Group
>> Subject: Re: [homenet] Next steps for draft-behringer-ho
14 matches
Mail list logo
