[homenet] Fwd: I-D Action: draft-ietf-homenet-front-end-naming-delegation-01.txt
Daniel Migault <mglt.ietf@gmail.com> Tue, 17 February 2015 21:13 UTC
Return-Path: <mglt.ietf@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5065A1A876C for <homenet@ietfa.amsl.com>; Tue, 17 Feb 2015 13:13:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YyTUbUxa3K-n for <homenet@ietfa.amsl.com>; Tue, 17 Feb 2015 13:13:30 -0800 (PST)
Received: from mail-wg0-x235.google.com (mail-wg0-x235.google.com [IPv6:2a00:1450:400c:c00::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09B0A1A1EF8 for <homenet@ietf.org>; Tue, 17 Feb 2015 13:13:30 -0800 (PST)
Received: by mail-wg0-f53.google.com with SMTP id a1so21938607wgh.12 for <homenet@ietf.org>; Tue, 17 Feb 2015 13:13:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HInmnbG+B3Q1VbQCnCj336b8SVF5MIa5X0+C/9tGaR8=; b=v+Z/QKbJ9O9DxXnFdISNlaggTPElUAH256eyJisSS2awX7+LrNZgM5kBFzjvx3Dd1q yrWrZiwViztIzD+SZnpJNBGuEklmYn0IvVqByoNWPanJe6pwLf03pnG+YS1uK+SvuimV 50IQqxUiHAfSeUvTCcYM8vsv5cGhnO1JPJuhz43h1sJ828Khi0+0LMPgXOVxB8UPajbT gZjmG7+CveoOHdgR0H8YfmYcNTXaO5VA9oGeYupWrTIdied6VfB494BnqHaefhwabxCu eHBkDTfOSvNiaMx/zIKTooxlPVrN7Ec+KbI29F8gXkSpbk+YZEJQboQLDHigWUaTyjeY hFdA==
MIME-Version: 1.0
X-Received: by 10.194.192.167 with SMTP id hh7mr2128053wjc.151.1424207608787; Tue, 17 Feb 2015 13:13:28 -0800 (PST)
Received: by 10.194.68.39 with HTTP; Tue, 17 Feb 2015 13:13:28 -0800 (PST)
In-Reply-To: <20150217193623.25643.39237.idtracker@ietfa.amsl.com>
References: <20150217193623.25643.39237.idtracker@ietfa.amsl.com>
Date: Tue, 17 Feb 2015 22:13:28 +0100
Message-ID: <CADZyTknzSqZwkBBqyabNkXoLpaawRv+=_4FFq77unvRYc6JKoA@mail.gmail.com>
From: Daniel Migault <mglt.ietf@gmail.com>
To: "homenet@ietf.org" <homenet@ietf.org>
Content-Type: multipart/alternative; boundary="047d7b8743f89bb704050f4f2c4a"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/j-uffyfyoK1AxL2kLbfFFJbSPPI>
Cc: Ralf Weber <Ralf.Weber@nominum.com>, Wouter Cloetens <wouter.cloetens@softathome.com>, Chris Griffiths <cgriffiths@dyn.com>
Subject: [homenet] Fwd: I-D Action: draft-ietf-homenet-front-end-naming-delegation-01.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Feb 2015 21:13:33 -0000
Hi, Please find the new version of the Outsourcing Home Network Authoritative Naming Service <http://tools.ietf.org/html/draft-ietf-homenet-front-end-naming-delegation-01>. We believed we addressed all comments we received through the list and off list. By the way thanks to all those that provided feedbacks, and feel free to provide more feed backs. Here are the main modifications: - 1) We clarify how the CPE is involved in the DNS resolution and how the home network requirements are met -- more specifically how naming resolution inside the home network is provided even though IP connectivity is down. Regarding this issues, we were in line with the received comments, so the new version is mostly clarifying this aspect. - 2) A number of issues were related to names that are not expected to be publish on the public Internet, and remain published only within the home network. This includes link-local, site-local and NAT IP addresses as well as Private domain names. As these requirements results in two different views, a "private" and a "public" view we describe the problem and provide guidance on how to deal with each of these cases in section 7 "handling on different views". I believe all raised issues so far have been considered as discussed on the mailing list. - 3) A privacy section has been added. It exposes the privacy concerns of outsourcing the DNS service. - 4) Text has been added on how reverse zone may be handled as an alternative to the generation of an explicit reverse zone. - 5) We clarify the pro/con about outsourcing the zone signature operation. The recommended way is clearly not to outsource it. This is the recommendation running for a while now, so we hope the text is clear by now. If not let us know. - 6) We clarify when needed when col-localization of the functions is needed. More specifically, when two functions needs to run on the same hardware. Such considerations only happened outside the master/slave architecture. - 7) RFC2308 has been added for the SOA BR, Daniel ---------- Forwarded message ---------- From: <internet-drafts@ietf.org> Date: Tue, Feb 17, 2015 at 8:36 PM Subject: [homenet] I-D Action: draft-ietf-homenet-front-end-naming-delegation-01.txt To: i-d-announce@ietf.org Cc: homenet@ietf.org A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Home Networking Working Group of the IETF. Title : Outsourcing Home Network Authoritative Naming Service Authors : Daniel Migault Wouter Cloetens Chris Griffiths Ralf Weber Filename : draft-ietf-homenet-front-end-naming-delegation-01.txt Pages : 25 Date : 2015-02-16 Abstract: CPEs are designed to provide IP connectivity to home networks. Most CPEs assign IP addresses to the nodes of the home network which makes it a good candidate for hosting the naming service. With IPv6, the naming service makes nodes reachable from the home network as well as from the Internet. However, CPEs have not been designed to host such a naming service exposed on the Internet. This may expose the CPEs to resource exhaustion which would make the home network unreachable, and most probably would also affect the home network inner communications. In addition, DNSSEC management and configuration may not be well understood or mastered by regular end users. Misconfiguration may also results in naming service disruption, thus these end users may prefer to rely on third party naming providers. This document describes a homenet naming architecture where the CPEs manage the DNS zone associates to its home network, and outsources the naming service and eventually the DNSSEC management on the Internet to a third party designated as the Public Authoritative Servers. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-homenet-front-end-naming-delegation/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-homenet-front-end-naming-delegation-01 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-homenet-front-end-naming-delegation-01 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet -- Daniel Migault Ericsson
- [homenet] I-D Action: draft-ietf-homenet-front-en… internet-drafts
- [homenet] Fwd: I-D Action: draft-ietf-homenet-fro… Daniel Migault
- Re: [homenet] Fwd: I-D Action: draft-ietf-homenet… Juliusz Chroboczek