Re: [homegate] A new proposed charter (and name) for HOMEGATE

["Kirksey, Heather R (Heather)" <[e-mail]>]

Ray and Mark,

I like this updated charter and think it sounds like a good way forward.  I also think it's less likely to incur overlap with other groups, while focusing on some areas where IETF can provide good value to the community.  

My only feedback/concern is that it's a rather long list of items you have on there to address -- I think that the working group leadership would need to be very focused to ensure that the work doesn't drag on too long.  

Thanks,
Heather


-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On Behalf Of Ray Bellis
Sent: Tuesday, September 07, 2010 12:05 PM
To: [e-mail]
Subject: [homegate] A new proposed charter (and name) for HOMEGATE

Mark Townsley and I, with lots of help from Ole Troan and input from various ADs and from Jason, have authored a new potential charter for this group.

We've taken a bit of a different direction from the previously proposed charter, but we think it is one which is more within the scope of what we believe the IETF can deliver, and takes into account most of the comments and feedback to date.

To avoid conflicting with the Home Gateway Initiative, and to better reflect the proposed scope of the group, the new name is the Home Networking (HOMENET) Working Group.

We believe that if the group agrees to this charter in general, we can start the process for WG formation.  That means we at least need to tell the ADs that we are OK asking them to circulate the text among the IESG and IAB by this Thursday, Sept 9th.

So, please send comments ASAP - positive or negative - so we can get a feel for whether this is the right way to go.

We'd also like to thank Jason Livingood for getting us this far.

--8<--8<--
Home networks are used for communication among networked devices
deployed within a home, and for communication with the Internet at
large. The manner in which a home network is used is evolving rapidly,
at times resulting in interoperability and/or performance problems on
the home network. In some cases, those working to solve these problems
have suggested the need for clarification of existing protocol
functionality or definition of new protocol functionality.

A home network can include a variety of data-link technologies, be it
Ethernet, 802.11, 802.15.4 or power line communication. Connected
devices may be as diverse as personal computers, televisions, digital
video recorders, telephones, computing tablets, digital cameras,
IP-enabled light switches, gaming consoles, audio output speakers, smart
electricity meters, toys, printers, routers and more. The home network
provides important local connectivity, Internet connectivity through one
or more Internet Service Providers, and connectivity to closed networks,
such as corporate VPNs and walled garden services.

Home networks offer unique challenges not only because of the wide range
of devices, applications, and user types, but also in that they are
typically not actively managed.

The broad purpose of the home networking (HOMENET) working group is to
describe the home network IP architecture and to work on clarifications
and improvements to IETF protocols to allow the home network to better
meet present and anticipated future requirements. Under this scope, the
current work items of the working group are related to addressing the
following requirements:

- Support for IPv4 and IPv6 with zero configuration, for IP prefix
 assignments and other fundamental aspects that are critical for
 network operation.

- Simple naming for devices in the home network, so they can be accessed
 from within the home network as well as from elsewhere on the
 Internet.

- Support for connections to multiple Internet service providers or
 closed networks (VPNs, walled gardens) at the same time

- IP routing across subnets and network segments with different Layer 2
 media (e.g., between Ethernet and 802.15.4).

- Effective queuing and forwarding mechanisms to enable efficient
 communication between network segments of different speeds.

- Reasonable default network layer security in accordance with known
 and/or expected threats, while not hindering the deployment of new
 applications or transport layer protocols.

- Support for DNSSEC validation within the home network.

The working group will work together with other standards development
organizations that define requirements on home networking devices
(including groups such as the Home Gateway Initiative, Broadband Forum,
CableLabs, UPnP, DLNA, etc.).

The HOMENET working group focuses on recommendations related to the use
of IETF-specified technologies such as DNS, DNSSEC, NATs, or IPv6, and
will not overlap with specifications related to system-level or
link-layer technologies developed by other standards bodies.

Extensions to IETF technologies will typically occur in the relevant
working groups chartered to maintain those technologies, based on
requirements from the HOMENET working group.

--8<--8<--

Ray and Mark

_______________________________________________
homegate mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/homegate