Re: Revision of RFC 7302

Ted Hardie <ted.ietf@gmail.com> Mon, 02 May 2016 18:02 UTC

Return-Path: <ted.ietf@gmail.com>
X-Original-To: urn-nid@ietfa.amsl.com
Delivered-To: urn-nid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7D2812D5D5 for <urn-nid@ietfa.amsl.com>; Mon, 2 May 2016 11:02:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, 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=gmail.com
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 g7y1GtGlfPDT for <urn-nid@ietfa.amsl.com>; Mon, 2 May 2016 11:02:39 -0700 (PDT)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (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 70BD412D135 for <urn-nid@ietf.org>; Mon, 2 May 2016 11:02:39 -0700 (PDT)
Received: by mail-oi0-x232.google.com with SMTP id x19so200042804oix.2 for <urn-nid@ietf.org>; Mon, 02 May 2016 11:02:39 -0700 (PDT)
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; bh=sVcDyr7R8f5zn9Nslz/Af/+zAiCRq54TCC3LUJBg26s=; b=Ogb3v4zfodlKT7t74Aboh/SkFnkJ5OdeHvxVkIL3pk+UA5HLwt7pnS0/1IWPirJOC3 qZvQJ3ip5w2xu5cPjbImUmUgCxS2Y8V2qKbvM9kcEYvtp3D33+L4oLLCC4IoAUzEcth5 uocZEqVYW8AYkZ90N0ICgyDtq8iQyEkBVjM4BZdnSijGLEZhXBFj39c1lQzoR63FWYsX NfAiRrB2bj/LVmJBHWP755CSlQ9PMm0SkyFBaHtUNC/Svi+C8if34yUKqDR2Uqy3PiFe 4KrZGnbAjSOQQZXyY1pFWzf7KzYFU8hl8mIjHQPBmTyIKiQJb9Ybv9pur+mXqG/o+l9J VynA==
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; bh=sVcDyr7R8f5zn9Nslz/Af/+zAiCRq54TCC3LUJBg26s=; b=iaQJv+tQ97UoAf5WT7yHyEZuZwK3e5inK3aXLOKU0LqT4PbJA9MByThfjHMGIbzOjq lf8eLDpfqC6dhBBJ6QWd241lT/uQcnUW2I6FJ6uvoRfszua0hP6X/P1dQsL2UhjDwPJ/ //3Ea/XkZw9S0Y4firVjCuTSaj0rAzHKreQKU0MUT51HF8b4eIbFvV7cXLjuZlT6IqHQ C/+ZGxz1GDPBDB+Inqj9Mec1auLXpkK3mGFI5SahBreoOpwwMptUiWna2kAV+f5mTq5e NIq5PEnpTBr7HbOOCehLfcpNKDQY1sIKAyAJvmzIjtagvMcX6O77EWWLCoSVZvw6dAzH tIag==
X-Gm-Message-State: AOPr4FV7x1TGYeooAc9iD2ntOkgOFAKW+NIpb6Xh28TYxHMPuca78GJMv39hlaQ/893igb1yD5AeB6txNuSNxA==
X-Received: by 10.157.15.155 with SMTP id d27mr16101682otd.87.1462212158729; Mon, 02 May 2016 11:02:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.22.186 with HTTP; Mon, 2 May 2016 11:02:19 -0700 (PDT)
In-Reply-To: <CAF_7JxBSXo-EjC3-11Yop5W_Sgo4mWoPvb7SGxH90V9QVHPbUw@mail.gmail.com>
References: <CAF_7JxBSXo-EjC3-11Yop5W_Sgo4mWoPvb7SGxH90V9QVHPbUw@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Mon, 2 May 2016 11:02:19 -0700
Message-ID: <CA+9kkMD=ArH=Y+WxQ-SJ0m3Y3Ka-4pZQhtvifx5H9aAZUqv9XA@mail.gmail.com>
Subject: Re: Revision of RFC 7302
To: Pierre-Anthony Lemieux <pal@sandflow.com>
Content-Type: multipart/alternative; boundary=001a113db0cc4eb29e0531dfcc6f
Archived-At: <http://mailarchive.ietf.org/arch/msg/urn-nid/h0DSR8aWaDNvxR9mFqhoJgGcru4>
Cc: "urn-nid@ietf.org" <urn-nid@ietf.org>
X-BeenThere: urn-nid@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <urn-nid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn-nid/>
List-Post: <mailto:urn-nid@ietf.org>
List-Help: <mailto:urn-nid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 May 2016 18:02:41 -0000

Thanks for the pointer.  The RFC series allows a document to update a
previous document, as well as along one to obsolete a previous document.
Looking through this, it appears that only the process for identifier
resolution has changed.  Given that, a much shorter document updating RFC
7302 noting the change might be simpler.

Generally speaking this is a stylistic choice, and there is certainly no
requirement to take that path.  But given the general stability
requirements for URNs, highlighting that the only changes are to resolution
might be useful.

regards,

Ted Hardie

On Sat, Apr 30, 2016 at 2:23 PM, Pierre-Anthony Lemieux <pal@sandflow.com>;
wrote:

> Good morning/evening,
>
> Please find at the link below a proposed revision of RFC 7302. This
> revision adds support for confidential resolution of EIDR Identifiers
> using HTTP over TLS -- addressing a known limitation of RFC 7302.
>
> https://www.ietf.org/id/draft-pal-eidr-urn-2016-00.txt
>
> Very much looking forward to your comments and feedback. Let me know
> if you need additional information.
>
> Best,
>
> -- Pierre [on behalf of MovieLabs (http://movielabs.com)]
>
>