IETF Logo Mail Archive

Re: [Arcing] A bit more on the problem statement

Ted Hardie <ted.ietf@gmail.com> Thu, 04 February 2016 23:12 UTC

Return-Path: <ted.ietf@gmail.com>
X-Original-To: arcing@ietfa.amsl.com
Delivered-To: arcing@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4FEF1B339A for <arcing@ietfa.amsl.com>; Thu, 4 Feb 2016 15:12:53 -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 uYjK0l53tYwm for <arcing@ietfa.amsl.com>; Thu, 4 Feb 2016 15:12:51 -0800 (PST)
Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::236]) (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 9EAA81B3385 for <arcing@ietf.org>; Thu, 4 Feb 2016 15:12:51 -0800 (PST)
Received: by mail-qk0-x236.google.com with SMTP id o6so27874916qkc.2 for <arcing@ietf.org>; Thu, 04 Feb 2016 15:12:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=03shqFAtWuM0rdcuQr5G/XgtJsPnTM9tB0JNiN3DtZU=; b=YtJXD3PH0X0qQuZE5RLrWr1GdRMT0w/sThnrj+ioErQ98LLhcB3jT1gdCyh08ZjWPY 8KE/iWrpWmXC6rPRa1JEcPCP0TB+8LHFJncLWZqGKLym6stH62XfHMJnFIwuPGsyQ3GX 4Z/DBolchssjTTZCSwf0YOBkfDyqbvjXoTqhJx6b3jqenZZAe8wfyf0oVHW243cYUQpG Phc01NbeeHff1Pl4spY121QaA6pZIwE+BW6tvE1msqBh5wZkrlZ9y5nk11HRMsTjVv4j qOIvJlP26afKUeyQxrqv7H6LTzKxvCvmImWDUl8vy4djRypHz8JJ/g4ylz1mvXRzfA+z cYaA==
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:cc:content-type; bh=03shqFAtWuM0rdcuQr5G/XgtJsPnTM9tB0JNiN3DtZU=; b=cqAqFskMUywzoSVRx/0H71bmG8S9tpqcv+2sApU6HmGxYAclEPUvcWkRGPcQ631g6L BYCWzscNJS5wF/iyYyYkTu6onZvp49GyhmLwo0YmYy+w65PaDzY4MNbuUeTXPX7ARn5Z DX8HiZoU6d0Yg+X2dPFp7La8MZFRR3nTRct5h82oyQtGuudjgJvj6hC7RjCAg2AkB/09 KOmR7KZrP6mkXqmX/NUhMIKwFtICkilsBWFmHmuTGWcDzeMUueNfc9ASY7M7avwOc57s cOJTOVRv3YK4cTV7ajqiByKbhAbqLMIRPUdc0Fj8uoZnSFHkTEHNJx6L+tbDp2Yo3Kz0 dXpA==
X-Gm-Message-State: AG10YOR2sVR2kStwLYUq7pJkM92n4t+AMm1YUDlyYLJnvi5MgmuJo9Wck87UEWZ1+IwkJSDfpl8WiYSbf0/0Yg==
X-Received: by 10.55.71.66 with SMTP id u63mr12428293qka.67.1454627570837; Thu, 04 Feb 2016 15:12:50 -0800 (PST)
MIME-Version: 1.0
Received: by 10.55.14.211 with HTTP; Thu, 4 Feb 2016 15:12:31 -0800 (PST)
In-Reply-To: <56B3D81C.9050609@gmail.com>
References: <CA+9kkMDBPHYg3ENofdZ2jQxh=Wjv3KZXK+gw=5nYT0B=VL87Qg@mail.gmail.com> <524E4EBB-DB02-4091-9F5D-14F103A81178@mnot.net> <CA+9kkMBP1EBe7Bc0nh-DJoJaFNzSofPyuO2NOR+BDjJtFt_WZA@mail.gmail.com> <56B3D81C.9050609@gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Thu, 04 Feb 2016 15:12:31 -0800
Message-ID: <CA+9kkMBspy_mKummQDvBcaSC3PXX4-cLde=Qpfi9y8Ey31_BdQ@mail.gmail.com>
To: Douglas Otis <doug.mtview@gmail.com>
Content-Type: multipart/alternative; boundary="001a114a7974a3f066052af9dfa8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/arcing/KK9rLcJVWwqawKDnSPLBDuYVvns>
Cc: arcing@ietf.org
Subject: Re: [Arcing] A bit more on the problem statement
X-BeenThere: arcing@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: This list will discuss different architectural approaches to signalling alternative resolution contexts for Internet names <arcing.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/arcing>, <mailto:arcing-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/arcing/>
List-Post: <mailto:arcing@ietf.org>
List-Help: <mailto:arcing-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/arcing>, <mailto:arcing-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 23:12:54 -0000

On Thu, Feb 4, 2016 at 3:00 PM, Douglas Otis <doug.mtview@gmail.com> wrote:

>
> On 2/4/16 11:44 AM, Ted Hardie wrote:
> > If we get broad agreement to use a particular signal,
> > like .alt, then folks minting new namespaces in .alt can
> > avoid collision with a simple FCFS registry.  If everyone
> > plays nice, there is no collision and you have no big
> > issues.  But we have no way of making that so, and we
> > have seen in the pseudo-TLD case that people mint these,
> > use them, and then require updates of others to deal with
> > the collisions.  Depending on the usage of .alt or a
> > similar signal, that could remain a concern (at least
> > version of the proposal had no registry at all, just the
> > reserved top label).
>
> Dear Ted,
>
> Why assume .home should be converted to .home.alt? Is this
> to ensure .alt gains inertia with its namespace containing
> definitions similar to those found with
> https://tools.ietf.org/html/draft-cheshire-homenet-dot-home-02?
>
>
​For what it is worth, I think you missed the fact I was citing
someone else's work, not advocating .alt myself.  That said,
I believe the draft you cite has a method that covers this:
​




> Open-ended FCFS registration will encourage an explosion of
> variant namespaces having any number of resolution methods
> and context. It seems safer to keep .home as defined by
> draft-cheshire-homenet-dot-home-02, and let .alt develop
> independently. In the goodness of time resource assessments
> and related risks assessments can then be made.
>
> Small home CPE devices offer limited storage and need
> simplistic access methods to limit vulnerabilities and
> coding complexity. As such, offering a highly extensible
> resolution structure as a first step seems ill considered.
> Otherwise, assessing security risks will provide resulting
> extensibility APIs likely to make Java and Flash defense
> seem trivial in comparison and will do nothing to limit the
> leakage of .home.
>
> Regards,
> Douglas Otis
>
>
>
> _______________________________________________
> Arcing mailing list
> Arcing@ietf.org
> https://www.ietf.org/mailman/listinfo/arcing
>

v2.23.0 | Report a Bug | By Email