[homenet] Fwd: I-D ACTION:draft-lemon-homenet-naming-architecture-00.txt

Ted Lemon <mellon@fugue.com> Thu, 24 March 2016 12:03 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 0082112DADB for <homenet@ietfa.amsl.com>; Thu, 24 Mar 2016 05:03:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id V3A5BhX4PwYm for <homenet@ietfa.amsl.com>; Thu, 24 Mar 2016 05:03:38 -0700 (PDT)
Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (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 6876E12DAC8 for <homenet@ietf.org>; Thu, 24 Mar 2016 05:03:19 -0700 (PDT)
Received: by mail-lf0-x22c.google.com with SMTP id d82so32485394lfe.3 for <homenet@ietf.org>; Thu, 24 Mar 2016 05:03:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=6X8DNykzM+9jLBIXiT9niz0GvyndGTNFakT0U203TIk=; b=sxSTfarVdKABTiZawOC/ok2/28NAcNgbeThhSnXbvB+20o4uQkIDOrugDMrWTIH4EE aFAO53YyoK3cL7EvJHHxrGnQpIrjLwjv6iBrLdxufT3ExSESdMM+fgOw4a+rhBiD1cdM /pb0SUVbIXtO9mxw/9vA8jLWPUEIuVBDzr7a/az6wvhLziUAMPruSTPpSXbllNFLJ10R D8fZ30JZqlELBMm3KzN4GDAnHBrJ9u7KyfSZAcksbWPbOcqY6bFIHYl094OYhI8GeQsN WBV6q/qXz2GxmzFQYKhM8loXwdilPf+FsGn80+lvJZ7hYenu3fCi9Jy13nPFzwFJcJFA 2CCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=6X8DNykzM+9jLBIXiT9niz0GvyndGTNFakT0U203TIk=; b=Bd3WP9L6MRMRJrZbET1c6ecQz9zltf0k7v1ZRgLmVSGc5y9QS7kVBd++W+lQjhgwzB mEjbiI9ZtCIPXdebSOxBt8gHHrDknBsXceQm7gSABHGOmy5g9Spnaz2wAQB6SdlTfbvX IhqLVZanUuYU7ktrifwNxwI7vIbidZ+Eypu3UMAc2N89cpSvwullgDV1rFUtJyh+QAc/ Vln7iNeRKuFXiu4DvYBexfy9NNmWl5VdAWerD6fglhwgcX8baBDbbYlGzsUgrGXQ4s/W pO1ChAgcxwOZ7G+Nh97MJlTSzxY8wS/wA9Imn+eEhcdA/giLK0YIq3dPflKeetJxjSob AhAQ==
X-Gm-Message-State: AD7BkJJyl06zqpg4cJ+D2m2vucpcsQt8q5tXGWLl4Dt4mTi5iC6U11BPkpFJXOg3/y8Qx+Kj9KzSWZVflzZ9Zg==
X-Received: by with SMTP id m7mr3415085lfd.109.1458820997642; Thu, 24 Mar 2016 05:03:17 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Thu, 24 Mar 2016 05:02:38 -0700 (PDT)
X-Originating-IP: []
In-Reply-To: <20160323164509.2510.24152.idtracker@ietfa.amsl.com>
References: <20160323164509.2510.24152.idtracker@ietfa.amsl.com>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 24 Mar 2016 08:02:38 -0400
Message-ID: <CAPt1N1ni-01feyMSaa0-7GhFCXPSS0gPSL8fAzVnhWehih2Pug@mail.gmail.com>
To: homenet@ietf.org
Content-Type: multipart/alternative; boundary=001a113fb5405b104c052eca3b54
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/tNm0d0pJ8HuWqY8n4VLaUMK3pNA>
Subject: [homenet] Fwd: I-D ACTION:draft-lemon-homenet-naming-architecture-00.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Thu, 24 Mar 2016 12:03:41 -0000

I've published a straw-man homenet naming architecture document for
discussion at IETF in Buenos Aires.   This document is a first attempt, and
represents just my thoughts, not the thoughts of the architecture team as a
whole, because I didn't get it out in time for us to discuss it--that's why
I published it just in my name.

It's a 20-page document, but should be a fairly painless read.   There's
some extra detail in it that doesn't belong in the final document because I
wanted to include some ideas that need to be fleshed out in other drafts,
which don't yet exist.

One big issue that DNSSD folks will recognize is that this draft does not
adopt mdns hybrid as a solution.   This is something I'd particularly like
to discuss--when I reread the MDNS hybrid draft in the process of working
on this document, I wasn't happy with the direction it had gone--it didn't
look like it would really be consistent with the goals of the homenet
project.   But I may have misunderstood the intention of the draft, and I
it may also be that the Homenet working group would prefer to settle for
something that basically works rather than pushing to reinvent the wheel.

Anyway, please don't take this document as an assertion that this is
definitely what the homenet naming architecture should look like.   Your
reactions to what's written in the document - agreement, disagreement, why
is this missing, why is this here, will help to move the discussion forward
and get us to something that the working group can have consensus on.


---------- Forwarded message ----------
From: <Internet-Drafts@ietf.org>
Date: Wed, Mar 23, 2016 at 12:45 PM
Subject: I-D ACTION:draft-lemon-homenet-naming-architecture-00.txt
To: i-d-announce@ietf.org

A new Internet-Draft is available from the on-line Internet-Drafts

    Title         : Homenet Naming and Service Discovery Architecture
    Author(s)     : T. Lemon
    Filename      : draft-lemon-homenet-naming-architecture
    Pages         : 20
    Date          : 2016-03-23

   This document recommends a naming and service discovery resolution
   architecture for homenets.  This architecture covers the publication
   and resolution of names of hosts on the homenet both within the
   homenet and on the public internet, and the use of such names for
   offering and discovering services that exist on the homenet both
   within the homenet and on the public internet.  Security and privacy
   implications and techniques for automatically and administratively
   setting security and privacy policies for such names are also

A URL for this Internet-Draft is:

Internet-Drafts are also available by anonymous FTP at:

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the

I-D-Announce mailing list
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt