[homegate] Proposed Charter Update - 2010/09/09
Ray Bellis <Ray.Bellis@nominet.org.uk> Thu, 09 September 2010 15:17 UTC
Return-Path: <Ray.Bellis@nominet.org.uk>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DE6223A6832 for <homegate@core3.amsl.com>; Thu, 9 Sep 2010 08:17:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.452
X-Spam-Level:
X-Spam-Status: No, score=-10.452 tagged_above=-999 required=5 tests=[AWL=0.147, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id On9PQSaEzcIf for <homegate@core3.amsl.com>; Thu, 9 Sep 2010 08:17:58 -0700 (PDT)
Received: from mx4.nominet.org.uk (mx4.nominet.org.uk [213.248.199.24]) by core3.amsl.com (Postfix) with ESMTP id 2FFB93A68F2 for <homegate@ietf.org>; Thu, 9 Sep 2010 08:17:57 -0700 (PDT)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns; h=X-IronPort-AV:Received:Received:From:To:Subject: Thread-Topic:Thread-Index:Date:Message-ID:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: Content-Type:Content-ID:Content-Transfer-Encoding: MIME-Version; b=VV2NSkHP8cObJKHBDyMjRxanyFyEeDbvA8y2HdcUkCG5R4jMiCsQzBiW G0BfxBdYxgvgmVHBRSo8sM6/GPCRYT18qgQCf9lXKsYIaNkYBZg+XhUba 1WXhIGRpJufKtp4;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1284045505; x=1315581505; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20Proposed=20Charter=20Update=20-=202010/09/09 |Date:=20Thu,=209=20Sep=202010=2015:18:22=20+0000 |Message-ID:=20<14B94CC6-EA1D-44BD-9E01-457EB89C5E4E@nomi net.org.uk>|To:=20"homegate@ietf.org"=20<homegate@ietf.or g>|MIME-Version:=201.0|Content-Transfer-Encoding:=20quote d-printable|Content-ID:=20<1ebd9998-a108-42b6-aeee-fe2396 5ec5ef>; bh=M+UfaUGsu0hsU9NflLYNyN4VU07pV8V4oQNc+UdTzYY=; b=ZoXfZODy4M0hpnpFO/Vh9HSpqHVwo5797tuT+eb1AuJbYhAmW4I4ldpY kFOh0MbV+FeD++LfknkjpVdZbfurykTojQmEQtTuOa+K5GUeqhjp2XYWk 8cTRg3zmX4VFlX7;
X-IronPort-AV: E=Sophos;i="4.56,339,1280703600"; d="scan'208";a="21330900"
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx4.nominet.org.uk with ESMTP; 09 Sep 2010 16:18:23 +0100
Received: from WDS-EXC1.okna.nominet.org.uk ([fe80::1593:1394:a91f:8f5f]) by wds-exc2.okna.nominet.org.uk ([fe80::7577:eaca:5241:25d4%19]) with mapi; Thu, 9 Sep 2010 16:18:23 +0100
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: "homegate@ietf.org" <homegate@ietf.org>
Thread-Topic: Proposed Charter Update - 2010/09/09
Thread-Index: AQHLUDI9lGP5uu/nZ0KwO9E3QEY4dA==
Date: Thu, 09 Sep 2010 15:18:22 +0000
Message-ID: <14B94CC6-EA1D-44BD-9E01-457EB89C5E4E@nominet.org.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1ebd9998-a108-42b6-aeee-fe23965ec5ef>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [homegate] Proposed Charter Update - 2010/09/09
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 15:18:00 -0000
Based on (long) discussions with ADs, and feedback from the IP Directorate and various people here, please find below our latest draft. Most of the changes relate to scope and work items - in particular the ADs wanted to see a concrete list of proposed goals and milestones. There's also some structural change - mostly moving the text that was below the bullet list higher up the document. Ray and Mark [with thanks also to Ole for his help with the editing] --8<--8<-- Home Networking (homenet) Current status: Proposed Working group Last Updated: 2010-09-09 Chairs: TBD1 TBD2 TBD Area Directors: TBD3 TBD4 Internet Area Advisor: TBD3 Mailing List: Address: homenet@ietf.org To subscribe: https://www.ietf.org/mailman/listinfo/homenet Archive: http://www.ietf.org/mail-archive/web/homenet Description of working group: ----------------------------- Home networks are used for communication among networked devices deployed within a home or home office, and for communication with the Internet at large. The manner in which a home network is used is evolving, at times resulting in interoperability and/or performance problems. A home network can include a variety of data-link technologies, such as 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, gaming consoles, audio output speakers, smart electricity meters, light switches, toys, printers, routers and more. The home network provides 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 because 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. The HOMENET working group will deliver recommendations related to the use of IETF-specified technologies such as TCP, IPv6, DNS, and IP routing protocols and will not overlap with specifications related to system-level or link-layer technologies developed by other standards bodies. The working group will work together with other standards development organizations that define requirements and specifications on home networking devices (including groups such as the Home Gateway Initiative, Broadband Forum, CableLabs, UPnP, DLNA, etc.). Extensions to IETF technologies will typically occur in the relevant working groups chartered to maintain those technologies, based on recommendations and requirements from the HOMENET working group. When appropriate, the HOMENET working group itself may advance protocol specifications with close review from any affected working groups in the IETF. The initial deliverable for the HOMENET working group is a Home Networking Architecture document. This document will define terminology, specific problem statements, and describe how various solution areas fit together. These areas include, but are not limited to: * Routed home - automatic prefix assignment and distribution of other configuration information in a network with multiple routers, subnets and data link types. * Simple naming for entities 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. * Effective queuing and forwarding mechanisms to enable efficient communication between network segments of different speeds, latencies and error rates. * 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. Goals and Milestones: --------------------- Nov 2010 - Initial revision of a Home Network Architecture document Mar 2011 - Adopt a Home Network Architecture document as a WG item Mar 2011 - Individual drafts as WG candidates for Routed home requirements Mar 2011 - Individual drafts as WG candidates for Simple naming requirements Mar 2011 - Individual drafts as WG candidates for Multi-homing requirements Mar 2011 - Individual drafts as WG candidates for QoS requirements Mar 2011 - Individual drafts as WG candidates for Security requirements Mar 2011 - Individual drafts as WG candidates for DNSSEC requirements Jul 2011 - Recharter the working group Dec 2011 - Submission of the Home Network Architecture document to the IESG
- [homegate] Proposed Charter Update - 2010/09/09 Ray Bellis
- Re: [homegate] Proposed Charter Update - 2010/09/… Paul Hoffman
- Re: [homegate] Proposed Charter Update - 2010/09/… David Harrington
- Re: [homegate] Proposed Charter Update - 2010/09/… David Harrington
- Re: [homegate] Proposed Charter Update - 2010/09/… Mark Townsley
- Re: [homegate] Proposed Charter Update - 2010/09/… Paul Hoffman
- Re: [homegate] Proposed Charter Update - 2010/09/… David Harrington
- Re: [homegate] Proposed Charter Update - 2010/09/… Jari Arkko
- Re: [homegate] Proposed Charter Update - 2010/09/… Mark Townsley
- Re: [homegate] Proposed Charter Update - 2010/09/… Andrew Sullivan
- Re: [homegate] Proposed Charter Update - 2010/09/… Paul Hoffman