Re: [homenet] draft-mglt-homenet-front-end-naming-delegation-01

["Griffiths, Chris" <[e-mail]>]

On Nov 7, 2012, at 11:31 AM, Andrew Sullivan <[e-mail]> wrote:

> While I was delighted to notice that
> draft-mglt-homenet-front-end-naming-delegation-01 had been modified in
> response to previous suggestions, such that it removed some of the
> more controversial parts of its predecessor, the core remark I made
> about the -00 is still true: I think it is way, way too complicated.
> I also think it's a nearly solved problem in shipping product to-day.

Andrew,

As one of the newer co-authors on this draft, I am happy to see that the changes we made to the draft have resolved some of the more contentious issues previously brought up.  I would like to understand further if you or other folks in the WG have any suggestions on how we could make this less complex and address naming both in and out of the home.  As an operator who is deploying home network platforms to millions of customers today, I politely disagree that this problem is nearly solved today in shipping products, but could be solved with existing platforms and protocols which desperately needs documentation..  Given the proposed architecture for Homenet, and the ability to have multiple layers of networks, there is going to be a need for a scaled approach to deal with internal and external naming which will need to include service discovery and publishing naming to outside the home.

Thanks

Chris