Re: [Uri-review] URI Scheme "ves:"

Thanks for the comments -

On 12/18/2021 1:15 PM, Tim Bray wrote:
> - Should you also register content-types for these things?

If fact there's already one registered - application/vnd.ves.encrypted

This is not a type VES URI is pointing to, but rather encrypted content 
stored by external means, the item encryption key for this content is 
identified by a VaultItem VES URI. There are no specific content types 
for objects identified by VES URIs, because those are handled by libVES 
or an equivalent tool, and are communicated in an e2ee form with the low 
level VES REST API as JSON objects.

> - Assuming you do, one wonders why you couldn't use regular old https 
> URLs, if these things are located on a DNS-addressable server.
>
The API server is DNS addressable, it's api.ves.host, however I see a 
few reasons to not use http uri -

- There are forms of VES URI that use an implicit app domain, which 
comes from the current context of libVES, or other VES API tool. An http 
uri wouldn't have the means to use the current context;

- I purposely specified some permitted violations of URI syntax that VES 
URI should tolerate, because it simplifies interactions between the 
client software and libVES, without causing any ambiguity;

- The ability to decrypt the object identified by VES URI, and even the 
ability to access the encrypted content and metadata, depends on the 
current context of libVES. Again, a stateless http uri wouldn't be good 
for it.

> On Fri, Dec 17, 2021 at 11:06 PM Jim Zubov <jz@vesvault.com> wrote:
>
>     Please consider the following provisional URI scheme for registration,
>     any comments are welcome:
>
>         Scheme name:
>           ves
>
>         Status:
>           Provisional
>
>         Applications/protocols that use this scheme name:
>           A unique identifier of an end-to-end encrypted object stored
>           in VES Repository (https://ves.host/docs/repo).
>           The passphrases that unlock the VES keychains are managed
>           locally on the user devices by VESvault (https://vesvault.com),
>           applications can use open source libVES or an equivalent tool
>           to access VES Repository.
>
>         Contact:
>           Jim Zubov<jz@vesvault.com>  <mailto:jz@vesvault.com>  VESvault Corp
>
>         Change controller:
>           Jim Zubov<jz@vesvault.com>  <mailto:jz@vesvault.com>  VESvault Corp
>
>         References:
>           https://ves.host/assets/download/VES%20URI%20Scheme.pdf
>           https://ves.host/docs/repo
>           https://vesvault.com
>
>
>
>
>     _______________________________________________
>     Uri-review mailing list
>     Uri-review@ietf.org
>     https://www.ietf.org/mailman/listinfo/uri-review
>