Subject: Re: [homegate] First Pass of Notes Attached

From: David R Oran <[email-masked]>
Date: Wed, 14 Jul 2010 08:04:39 -0400

Here's some more material for the marked section: "Dave Oran felt there is an interesting place for the IETF to play [WOULD LIKE MORE FROM DAVE ON THIS]. One question he had was what the presenters felt there were any gaps in their existing work."

Dave Oran feels that there are a few areas that are directly in the IETF's scope of interest and competence that are not adequately addressed by the other SDOs represented. In general, the principles for what to tackle were very well captured by JFM's slide (get the exact words from his slide) - the essence being that homegate can and should tackle the specification of what home gateways need to do and not do to provide access from the home network to critical Internet infrastructure services (e.g. DNS) and to the broadest possible range of internet applications.

In addition to fleshing out the work on IPv6 CPE that is ongoing, Dave feels that homegate ought to tackle routing and other IPv6 services (e.g. address delegation, multiple subnets, multihoming) on home networks that affect the ability to access and use resources not just in the home but on the internet as a whole.

While a number of the other SDOs do stuff in the QoS domain (especially HGI, DLNA, and IEEE) I got the nagging sense that none of these really capture the essence of the QoS architecture that the IETF has designed over many years (hence my questions to the HGI folks about users not being able to control traffic classification, and my questions about what these latency bounds IEEE AVB provides really mean). It seems to me that there is an opportunity for homegate to tackle this "inside/outside" disconnect in the QoS approaches specified by the other SDOs.

Also, during a sidebar IM conversation with Ralph Droms the issue came up of how to do a better job of naming - right now the only options for naming resources on a home network are either entirely local (e.g. UPnP or mDNS with .local) or require the user to register a domain in the DNS (either directly or through a service like dyndns) and use wide-area Bonjour, which challenges even the most astute technically to configure correctly. We really ought to have a way to name resources on home networks such that they can be globally referenced through the dns. This was of less importance in the IPv4 environment because (a)user could at some inconvenience actually type and understand IPv4 addresses, and (b) IPv4 NAT renders the ability to globally reference the resources moot.

DaveO.

On Jul 13, 2010, at 1:20 PM, Jason Livingood wrote:

> Feel free to mark up.  Thank you all for participating!
> 
> 
> Regards,
> Jason
>  
> Jason Livingood
> Executive Director
> Internet Systems Engineering
> National Engineering & Technical Operations
> Comcast Cable Communications
> 215-286-7813
> [email-masked] 
> <Homegate Workshop Notes - 20100713 - v1.docx>