On Thu, Oct 2, 2014 at 6:50 AM, Leddy, John
<[email protected]> wrote:
> My worry on this topic is that we are referring to ³the Home² and ³the
> Enterprise².

I have always approached homenet as a place to get standards that also work for
small business. Small business is the place (IMHO) where much of an
ipv6 revolution
could start to happen.

> It isn¹t that clear of a distinction.  This isn¹t just a simple L2 flat
> home vs. a Fortune 1000 enterprise.

+1

> The home is getting more complex and includes work from home; IOT, home
> security, hot spots, cloud services, policies, discovery etc.
> Large numbers of SMB¹s look like more high end residential than they do
> large enterprises.

+1

>
> It would be ideal to have a solution that spans the range of size and
> complexity for both residential and enterprise.
> Perhaps enabling features/capabilities where required.
>
> Also, as far as IPV6 connectivity residential is probably ahead of
> enterprises in adopting V6 centric architectures and services.
> Residential doesn¹t have much of a choice, it just happens.

Comcast's rollout has been quite impressive. Gfiber's also.
Others, not so much.

>
> 2cents, John
>
> On 10/2/14, 9:15 AM, "Stephen Farrell" <[email protected]> wrote:
>
>>
>>
>>On 02/10/14 13:49, Michael Behringer (mbehring) wrote:
>>> My personal goal is that what we do in ANIMA is fully compatible with
>>> and ideally used in homenet. It would feel wrong to me to have an
>>> infrastructure that doesn't work in a homenet.
>>>
>>> The security bootstrap is a good example of what we can achieve, with
>>> reasonable effort.
>>
>>FWIW, it is not clear to me that the reasonable requirements
>>for provisioning device security information (or bootstrapping
>>if we wanted to call it that) are the same.
>>
>>In enterprise environments we see fewer larger vendors of devices.
>>In the home where we additionally have a large range of vendors
>>many of whom are tiny and leverage a lot of OSS and who could
>>perhaps not take part in the kind of provisioning infrastructure
>>that is quite reasonable for enterprises and their vendors.
>>
>>I do think both want to end up in the same state, where devices
>>are authorised for connection to the network and where there is
>>some keying material usable for security, but I'd be surprised
>>if one approach to getting there worked the same way for both
>>homes and enterprises.
>>
>>S.
>>
>>_______________________________________________
>>homenet mailing list
>>[email protected]
>>https://www.ietf.org/mailman/listinfo/homenet
>>
>
> _______________________________________________
> homenet mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/homenet



-- 
Dave Täht

https://www.bufferbloat.net/projects/make-wifi-fast

_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet

Reply via email to