[homenet] New version draft-mglt-homenet-naming-architecture-dhc-options-02.txt

Daniel Migault <mglt.ietf@gmail.com> Wed, 02 July 2014 14:39 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 EE2E91A0240 for <homenet@ietfa.amsl.com>; Wed, 2 Jul 2014 07:39:40 -0700 (PDT)
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 wTE7ezbUzRYu for <homenet@ietfa.amsl.com>; Wed, 2 Jul 2014 07:39:39 -0700 (PDT)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B988E1A0242 for <homenet@ietf.org>; Wed, 2 Jul 2014 07:39:38 -0700 (PDT)
Received: by mail-wg0-f43.google.com with SMTP id b13so858125wgh.26 for <homenet@ietf.org>; Wed, 02 Jul 2014 07:39:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=zmbjB0ndP0OApHLAHLrhOzNYKdP6y2N6UxkyDchLk2U=; b=0o+xEL+bJHVNM0m6yoZo/vhzQ7dNerB8ARL2XY+kJhPDIs4KeK4PR3AhlqJ0K11T4u pgyvr6zJCCqvnFSJYtZLMy4T4+vsb6dmQPqdmga79+Kxw+zcEVCEhXxUjvnCDnWHG58A U4ekKzeeQbUEjfx8KsJ5YEUWsr8RxrCOHUbnL0Dkznf+GyIuQTaOpQy0Cqj0YlNdfgcR 3LVnBOoiDfJdDHmXHamXwHQrwYxD50AP+VlB4VhigfwRX9vdSF9/yUb2OhGhdRFfqtYu x66S21N49Nvy8dr2bnmm0MWK1M5Ut4pDXjvWvkdkBrWm0ztJGba933jNAbf8rjRxhuVf 7QOA==
MIME-Version: 1.0
X-Received: by 10.194.63.77 with SMTP id e13mr4138833wjs.104.1404311975353; Wed, 02 Jul 2014 07:39:35 -0700 (PDT)
Received: by 10.194.51.131 with HTTP; Wed, 2 Jul 2014 07:39:35 -0700 (PDT)
Date: Wed, 02 Jul 2014 16:39:35 +0200
Message-ID: <CADZyTkk6rUuFJ5Wds2hioBBQa9-kXDJxyg_gBGQ1R6u5CHF2Ww@mail.gmail.com>
From: Daniel Migault <mglt.ietf@gmail.com>
To: "homenet@ietf.org" <homenet@ietf.org>
Content-Type: multipart/alternative; boundary="047d7b86d96271e55404fd36dce6"
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/l9nTfCsxv5IP7M9NBSHj42Taj10
Subject: [homenet] New version draft-mglt-homenet-naming-architecture-dhc-options-02.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: Wed, 02 Jul 2014 14:39:41 -0000

Hi,

Here is a new version of the DHCP Options for Homenet Naming Architecture
<http://datatracker.ietf.org/doc/draft-mglt-homenet-naming-architecture-dhc-options/>.
DHCP Options are designed so the CPE can automatically outsource its
Authoritative DNS Service. [1]

We carefully considered the remarks of the DHCP WG in London for the design
of the options. We also considered the remarks we received in the Homenet
WG more especially:
    - We removed TSIG for securing transaction between the CPE and the DNS
servers. Intead we used SIG(0)
    -  We considered AXFR and Master/Slave mechanisms to outsource the Zone
from the CPE to the DNS Server.
    - We documented how outsourcing can be done on DNS owned/managed by the
ISP and by third party DNS providers.

The scope of the draft is designing DHCP Option to outsource a Zone from
the CPE to the some other DNS. As such we did not discussed:
    - whether the zone shoudl be signed or not.
    - how the DS record should be updated. This should be performed by the
DNS server hosting the zone, not (necessarily) the CPE.
    - the cases of internal / external zones

This points have not been omitted and will be discussed in
draft-mglt-homenet-front-end-naming-delegation.

Feel free to make comments!

Daniel

[1]
http://datatracker.ietf.org/doc/draft-mglt-homenet-naming-architecture-dhc-options/




-- 
Daniel Migault
Orange Labs -- Security
+33 6 70 72 69 58