Re: [homenet] Status of draft-tldm-simple-homenet-naming CFA

Toke Høiland-Jørgensen <toke@toke.dk> Wed, 16 August 2017 15:24 UTC

Return-Path: <toke@toke.dk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F260D132498 for <homenet@ietfa.amsl.com>; Wed, 16 Aug 2017 08:24:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=toke.dk
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 6rK842wYSFrI for <homenet@ietfa.amsl.com>; Wed, 16 Aug 2017 08:24:07 -0700 (PDT)
Received: from mail.toke.dk (mail.toke.dk [52.28.52.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66F9B13249F for <homenet@ietf.org>; Wed, 16 Aug 2017 08:24:07 -0700 (PDT)
From: Toke Høiland-Jørgensen <toke@toke.dk>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1502897045; bh=v/njsPFQmR19FoTTfq+soPT22/yHBmxZQ89yv6WcWQc=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=MCHquCOsA66bT5evvRv4ziDdwuOsN/OfhhTsDf/6MCP2xIAVniQ7uT9x39qvBiR0Z Wc4HBwj4uIHo39kwGkDFEYoy4kjZizsKVzuBG7WjAmYLZPLzbRE6xXC+n8NBtT3OOm 9ZgSGoiTQuJZEuSg0zIqDdSI7JOrcnxRncqvl0zOFa5Te9UV1fF2/lkMDEZVs+V9Ic qMSzY6UCXr69ONRL8/nHf2Vi7bzgn1yIBG+X11Tdptyea0KZeYAqSTdeYHWAGB2UYW V4omlIEIXBAb3DRcVwI6MxmBC/21eP6XsPolaHpZYC0NaVq1f5/OXv/rgk34dWXmyM c2fUEogbaUe1A==
To: Ted Lemon <mellon@fugue.com>
Cc: Ralf Weber <dns@fl1ger.de>, HOMENET <homenet@ietf.org>, Juliusz Chroboczek <jch@irif.fr>
In-Reply-To: <16EE0CA3-4618-416C-91E1-F56FD7D8BB27@fugue.com>
References: <2D09D61DDFA73D4C884805CC7865E6114DBF5904@GAALPA1MSGUSRBF.ITServices.sbc.com> <CAPt1N1m5nVGD-y2VrbkoTEPTs4qF98oRxGuvd-Has1yzuS0fmg@mail.gmail.com> <874ltez1wg.fsf@toke.dk> <7E8390B5-9048-4783-B17F-6C9EA5610887@fugue.com> <7ivalujdfu.wl-jch@irif.fr> <15F1CE39-82EE-4B0D-A31B-2C1805991541@fugue.com> <871sofzqma.fsf@toke.dk> <CAPt1N1=oiU+DbjD6izOBNJOnC25d=-S3ARqFxydRfWLEet5mEQ@mail.gmail.com> <87valry4o7.fsf@toke.dk> <FCAD81FA-BBA0-45B0-8F1F-D1D5FD010484@fugue.com> <87shgvxybl.fsf@toke.dk> <4AF8CF8A-F781-449F-9C53-A9603889746E@fugue.com> <87lgmnxr3u.fsf@toke.dk> <E3E75086-BF36-4F59-86BD-7FFDAFE772AB@fugue.com> <87fuctxdrc.fsf@toke.dk> <FB44A942-9DE3-4CE6-88C5-402B20756462@fugue.com> <877ey4y62g.fsf@toke.dk> <D70AED02-5EE5-45B8-8BAC-C38C8C38E8EB@fl1ger.de> <87y3qjwsak.fsf@toke.dk> <8EA5872B-24B3-42DF-9A07-81FB6DC7118D@fugue.com> <16EE0CA3-4618-416C-91E1-F56FD7D8BB27@fugue.com>
Date: Wed, 16 Aug 2017 17:24:08 +0200
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <87mv6zwn6v.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/kLNf2QJGWdmlFSKZoubUmyqXcGg>
Subject: Re: [homenet] Status of draft-tldm-simple-homenet-naming CFA
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 16 Aug 2017 15:24:09 -0000

Ted Lemon <mellon@fugue.com> writes:

> El 16 ag 2017, a les 9:40, Ted Lemon <mellon@fugue.com> va escriure:
>> Ah, if this is your concern, I think that's answered by the whitelisting stuff I was talking about earlier.   But in this case you really do need to have separate caches per PvD, and the MPvD-aware clients on the net need to be able to use them.   We could say that this is optional to support, though, and so if you want to pay for one router with this feature, that router's resolver can be advertised in the PvD-aware path.
>
> BTW, I think we have probably carried this discussion as far as is
> useful until a new rev of the draft is done. Daniel is working on a
> new draft, he said, and when he's done his bit I'll do a pass as well
> and try to capture the changes we've discussed here, and then we can
> iterate again. :)

Yup, fine with me :)

-Toke