Re: [Mathmesh] Using UDF for CDN content

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 15 November 2019 08:35 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: mathmesh@ietfa.amsl.com
Delivered-To: mathmesh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BFDC120119 for <mathmesh@ietfa.amsl.com>; Fri, 15 Nov 2019 00:35:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 VdIK5y9HdoJB for <mathmesh@ietfa.amsl.com>; Fri, 15 Nov 2019 00:35:45 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5629412008B for <mathmesh@ietf.org>; Fri, 15 Nov 2019 00:35:44 -0800 (PST)
Received: from [192.168.41.2] (unknown [49.77.183.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by tuna.sandelman.ca (Postfix) with ESMTPSA id 5868F3897C for <mathmesh@ietf.org>; Fri, 15 Nov 2019 03:32:33 -0500 (EST)
To: mathmesh@ietf.org
References: <2301212a-ebea-7c8d-f52a-83e2988df71e@sandelman.ca> <A545E94E-E05C-4DC2-8EEB-2682C8EA8936@tzi.org>
From: Michael Richardson <mcr+ietf@sandelman.ca>
Message-ID: <a88be414-104e-498d-2ad3-3ddd04f813d4@sandelman.ca>
Date: Fri, 15 Nov 2019 16:35:37 +0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <A545E94E-E05C-4DC2-8EEB-2682C8EA8936@tzi.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mathmesh/1HF-xaxPeXtQqyLUASvBX4NvRvQ>
Subject: Re: [Mathmesh] Using UDF for CDN content
X-BeenThere: mathmesh@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <mathmesh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mathmesh>, <mailto:mathmesh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mathmesh/>
List-Post: <mailto:mathmesh@ietf.org>
List-Help: <mailto:mathmesh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mathmesh>, <mailto:mathmesh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Nov 2019 08:35:47 -0000


On 2019-11-12 11:30 p.m., Carsten Bormann wrote:
> RFC 6920


  which is: Naming Things with Hashes

while it provides for retrieving things via a /.well-known interface,
and it provides for human readable (nih), it just feels too hard to use
in practice.  I think that I can build a udf:// server with any stock
static web server by just putting the things into a flat directory, with
the files named for the encrypted/hashed items.

ni:// supports fixing the content, but not encrypting it.

So I agree that there is significant overlap, and maybe we can make
udf:// an extension of ni://.  We should explore that.