Re: [urn] Request for a Namespace Registration for Unique (Vaccination) Certificate Identifier
Peter Saint-Andre <stpeter@mozilla.com> Wed, 11 August 2021 17:41 UTC
Return-Path: <stpeter@mozilla.com>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AB8C3A1E34 for <urn@ietfa.amsl.com>; Wed, 11 Aug 2021 10:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mozilla.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 7MP3gY049RSY for <urn@ietfa.amsl.com>; Wed, 11 Aug 2021 10:41:25 -0700 (PDT)
Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (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 0E8333A1E32 for <urn@ietf.org>; Wed, 11 Aug 2021 10:41:25 -0700 (PDT)
Received: by mail-io1-xd29.google.com with SMTP id 188so4676842ioa.8 for <urn@ietf.org>; Wed, 11 Aug 2021 10:41:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=J9aeSIHsYRh+0Z1H+3RaAUY/a12ABfVj8X9t8eKslXY=; b=G8DXI0gemVy9kvj0OtmwxFnSt+97IQb9rZPT60O7g8ruLSdoIRhMIBRqCKLC5/Qg8a 6rJIaolZ477TWv7n4L1XXAwJDcyBbaBwIqpPEIumaTlvTa9eVujBJxl9CpWdsToShzkw EC0qx/HVLTAETZStWAn83JxqXtOY51u5e6IWI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=J9aeSIHsYRh+0Z1H+3RaAUY/a12ABfVj8X9t8eKslXY=; b=OwvKYSdtNkONHfme39WFq83Hq55BfQp0MmlK1079iwmKp/kx5yxEhDP39WTExFMAri P7eInvITCB7qgtgkuO97jH25VsWlKnviIiQne/dc7xV2IQRRgmTs2KJFPcp7/UnH4Qif 3do0Hh+Ujtmu3yPYvS8POC2tstZkUckOIFaNpOSpeVqss1/Wg36rFGiDfHbqNHd4SsFb KgsSIVtsLqb22dDf4IVvxECDYShWUYLBU+ELiCc6mGHOvXCQd3hN5yypKkzX4CX9Ui1e vnSb/wjmXuyFhA+tLGqmgfrwykHKBFlY+Vrrt3DuslEq2v0Hlm8VizcHQGdAMvQVrHko GfLQ==
X-Gm-Message-State: AOAM530RvHX2AjjuSgj2F8/OubWTCm9vVHkF06WysbmUDmWi+uyf6Wtq chst02op2KiuhB2+gYLh1UCXP2Q0E/BZIA==
X-Google-Smtp-Source: ABdhPJxDovmJ/Ab3YqfHjiWTOKOaOe/czUBAYenJGdHJe0lMroxaHXVOw7sgk8UtsmyMLUDSKjmDog==
X-Received: by 2002:a5e:8f07:: with SMTP id c7mr245744iok.32.1628703683036; Wed, 11 Aug 2021 10:41:23 -0700 (PDT)
Received: from dragon.local (c-73-78-113-156.hsd1.co.comcast.net. [73.78.113.156]) by smtp.gmail.com with ESMTPSA id p12sm7657305ilp.87.2021.08.11.10.41.22 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 11 Aug 2021 10:41:22 -0700 (PDT)
To: Dirk-Willem van Gulik <dirkx@webweaving.org>
Cc: urn@ietf.org, the eHEALTH-NETWORK Secretariat <eHEALTH-NETWORK@ec.europa.eu>
References: <3053F7E9-7C6A-4AAB-AC87-63DC1D6A58D7@webweaving.org> <b74e2e97-3fd3-d24a-3844-4b6ffef821d1@mozilla.com> <36DA5C85-D4D9-4257-9050-304E0BB2C714@webweaving.org>
From: Peter Saint-Andre <stpeter@mozilla.com>
Message-ID: <7cd1750c-0c5f-42b8-6608-9287d594079f@mozilla.com>
Date: Wed, 11 Aug 2021 11:41:21 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <36DA5C85-D4D9-4257-9050-304E0BB2C714@webweaving.org>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/JEGZvrZ0MOHlycDpegNx0f_qexU>
Subject: Re: [urn] Request for a Namespace Registration for Unique (Vaccination) Certificate Identifier
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn/>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Aug 2021 17:41:30 -0000
On 8/11/21 5:25 AM, Dirk-Willem van Gulik wrote: > On 11 Aug 2021, at 01:07, Peter Saint-Andre <stpeter@mozilla.com> wrote: >> On 8/1/21 7:37 AM, Dirk-Willem van Gulik wrote: > >>> For this reason the design[2] calls for a Unique (Vaccination) >>> Certificate Identifier (UVCI) that uniquely identifies a specific test, >>> vaccination or recovery certificate. > ... >> However, the foregoing paragraph seems to indicate that a URN would >> identify a test, vaccination, or recovery certificate. That could be > .... >> administered, etc.) - that is, not one URN per person encapsulating >> numerous events in an array or what have you. That also doesn't seem >> quite consistent with this later paragraph: >> >>> The UVCI pertains to a specific (medical) record about a specific >>> person’s vaccination, test or recovery at event level [1,2]. This >>> record is subject to national legislation and regulation. >> >> Could you clarify this aspect? > > You are correct - this is wrong and badly written. > > It is an identifier for a specific assertion (e.g. this person was > vaccinated; this person was tested) rather than something tied to > the person; it is inside the elements of arrays of such assertions > about 'a' vaccination, test or recovery statement*. > > We've tried to clarify this in the next version of the draft. Thanks for the clarifications. As I understand it, the URN identifies a vaccination event, a test event, or a recovery event. The URN itself does not associate the assertion with a particular person (there is no "person" construct built into the URN). For instance, if I get a test, that test is assigned a URN. If I receive documentation (physical or digital) of the URN that's been assigned and I present such documentation, the assocation comes from the fact that I'm the one presenting the documentation. Some other system (say, a medical records system) could formally associate that URN with some other identifier for me as a person within a given nation or region, but that kind of association is out of scope for the URN definition. If this is correct, I think we could slightly adjust the wording to make it fully clear. Peter
- [urn] Request for a Namespace Registration for Un… Dirk-Willem van Gulik
- Re: [urn] Request for a Namespace Registration fo… Hakala, Juha E
- Re: [urn] Request for a Namespace Registration fo… Dirk-Willem van Gulik
- Re: [urn] Request for a Namespace Registration fo… Peter Saint-Andre
- Re: [urn] Request for a Namespace Registration fo… Dirk-Willem van Gulik
- Re: [urn] Request for a Namespace Registration fo… Dirk-Willem van Gulik
- Re: [urn] Request for a Namespace Registration fo… Peter Saint-Andre
- Re: [urn] Request for a Namespace Registration fo… Ed Guy
- Re: [urn] Request for a Namespace Registration fo… Dirk-Willem van Gulik
- Re: [urn] Request for a Namespace Registration fo… Dirk-Willem van Gulik
- Re: [urn] Request for a Namespace Registration fo… Dirk-Willem van Gulik
- Re: [urn] Request for a Namespace Registration fo… Ted Hardie
- Re: [urn] Request for a Namespace Registration fo… Dale R. Worley
- Re: [urn] Request for a Namespace Registration fo… Dirk-Willem van Gulik