Chris Rebert | 4 Apr 05:10 2016

Review request for gittorrent: URI scheme

Hello,

Per the advice of RFC 7595, I hereby present the following proposed
registration of the "gittorrent" provisional URI scheme for review.
Any feedback is greatly appreciated. Thanks.

Cheers,
Chris
****
http://chrisrebert.com
Browser 🐛 of the day: http://bugzil.la/1259972

********

Scheme name:  gittorrent

Status:  Provisional

Applications/protocols that use this scheme name:
  GitTorrent ("A decentralization of GitHub using BitTorrent and
  Bitcoin")

Contact:
  Scheme creator:
    Chris Ball <http://printf.net/>
  Registering party:
    Chris Rebert <iana.url.schemes.gittorrent <at> chrisrebert.com>

Change controller:
  Either the scheme creator or the registering party.
(Continue reading)

Erik Wilde | 22 Feb 10:20 2016
Picon

Request for provisional registration: itms-books/itms-ibookss (Apple iBooks Store)

hello.

http://www.iana.org/assignments/uri-schemes/prov/itms is how apple's 
iTunes music/media store has been registered as a provisional URI 
scheme. this is a registration request for the corresponding 
itms-books/itms-bookss schemes, which identify resources in apple's 
iBooks store. it seems that in practice, itms-books/itms-bookss URIs are 
increasingly replaced by HTTP(S) URIs with the prefix 
http(s)://itunes.apple.com/ (and variations of this prefix, including 
the domain ibooks.apple.com), but itms-ibooks continues to work and is 
still used for identifying apple iBooks store resources.

here is the registration template:

-----------------------------------------

Uniform Resource Identifier (URI) Scheme names: itms-books, itms-bookss
Status: provisional

Scheme syntax:
    itms-books:
    itms-bookss:

Scheme semantics:
    Used for connecting to the Apple iBooks Store

Encoding considerations:
    Unknown, use with care.

Applications/protocols that use this scheme name:
(Continue reading)

Erik Wilde | 22 Feb 10:17 2016
Picon

Request for provisional registration: itms-apps (Apple App Store)

hello.

http://www.iana.org/assignments/uri-schemes/prov/itms is how apple's 
iTunes music/media store has been registered as a provisional URI 
scheme. this is a registration request for the corresponding itms-apps 
scheme, which identifies resources in apple's app store. it seems that 
in practice, itms-apps URIs are increasingly replaced by HTTP(S) URIs 
with the prefix http(s)://itunes.apple.com/ (and variations of this 
prefix, including the domain appstore.apple.com), but itms-apps 
continues to work and is still used for identifying app store resources.

here is the registration template:

-----------------------------------------

Uniform Resource Identifier (URI) Scheme name: itms-apps
Status: provisional

Scheme syntax:
    itms-apps:

Scheme semantics:
    Used for connecting to the Apple App Store

Encoding considerations:
    Unknown, use with care.

Applications/protocols that use this scheme name:

Interoperability considerations:
(Continue reading)

Marco Pontello | 10 Jan 15:16 2016
Picon
Gravatar

URI scheme registration request: blockchain

Hello!

This is a request for a new URI scheme.
Thanks for the attention.


Resource Identifier (RI) Scheme name: blockchain 
Status: provisional

Scheme syntax:
   blockchain:[//chain]</type/hash>

Scheme semantics:
   Referencing objects on a specific blockchain.

Encoding considerations:
   7-bit ASCII is sufficient.

Applications/protocols that use this scheme name:
   Crypto wallets, block explorers, etc.

Interoperability considerations:
   None.

Security considerations:
   None known or expected.

Contact:
   Registering party: Marco Pontello <marcopon <at> gmail.com>
   Scheme creator: Marco Pontello <marcopon <at> gmail.com>

Author/Change controller:
   See previous answer.

References:
   BIP 122 (Bitcoin Improvement Proposal) provide rationale & info:

   Simple test handler / demo (sort of a blockchain explorer proxy):
_______________________________________________
Uri-review mailing list
Uri-review <at> ietf.org
https://www.ietf.org/mailman/listinfo/uri-review
John Wason | 13 Nov 01:42 2015

URI scheme registration request

Scheme Name:

The requested scheme improvement is for use with Robot Raconteur, a communication framework for robotics and automation. It will have the basic form "rr://" for unsecured transport and "rrs://" for transports secured using StartTLS channel upgrade.  Because Robot Raconteur is capable of running over multiple transports, the scheme will also need to specify which transport to use.  This will be accomplished using the "rr" "plus" transport type.  Currently in use transport schemes are:

rr://foo - Cloud Transport (always secure)
rr+cloud://foo - Cloud Transport (always secure)
rr+tcp://foo - TCP Transport
rrs+tcp://foo - TCP secure transport
rr+usb://localhost - USB transport
rr+pci://localhost - PCI/PCIe transport

Possible schemes for future use with websockets (currently not used)
rr+ws://foo
rrs+ws://foo
rr+wss://foo
rrs+wss://foo

Status:
Provisional

Application/protocols that use this scheme name:
None

Contact:
John Wason
Wason Technology, LLC
PO Box 669
Tuxedo, NY 10987
+1-518-279-6234
wason <at> wasontech.com

Change controller:
John Wason
Wason Technology, LLC
PO Box 669
Tuxedo, NY 10987
+1-518-279-6234
wason <at> wasontech.com

Reference:
Robot Raconteur is currently a proprietary software project.  All documentation can be found at http://robotraconteur.com/documentation .  It currently has port 48653 officially registered for TCP and UDP use along with the host names "robotraconteur" and "rr-discovery".  Standardization is of interest however the exact method and commercial implications are still being investigated.

Scheme Syntax:
See "Scheme Name"

Scheme semantics:
Each scheme will point to a host (and possibly port).  The host will be "localhost" for the hardware based protocols.

Definition of Operations:
Asynchronous message stream using binary protocol.

Context of Use:
Robot Raconteur communication protocol over port 48653 (where applicable).

Internationalization and Character Encoding:
All strings in the message stream are encoded as UTF-8 and do not have any security implications.  The only part of the URI expecting to contain international characters are hostnames registered through DNS.

Security considerations:
Robot Raconteur is mainly used for communication over the local network except for the cloud transport.  All transports over the internet use TLS or DTLS security using certificates matched to each node through a UUID unless the user specifically uses unsecured TCP.  Nodes can be secured using password and certificate based authentication. The transport itself is immune to parsing attacks as it uses length prefixes for all data fields.

-- John Wason, Ph.D. Wason Technology, LLC PO Box 669 Tuxedo, NY 10987 (518) 279-6234 wason <at> wasontech.com
_______________________________________________
Uri-review mailing list
Uri-review <at> ietf.org
https://www.ietf.org/mailman/listinfo/uri-review
uri-review@ditp.org | 21 Oct 11:56 2015

Review request for scheme DIS

Hello,

This a review request for a provisional registration of the URI scheme 
name DIS. You will find the draft registration form below.

DIS is the acronym of Distributed Information System. This system is in 
design process and only partially implemented. It will use the protocol 
DITP (Distributed Information Transfer Protocol). As recommended I 
should use dis as scheme name instead of the protocol name ditp. Is that 
right ?

I don't find the "Security consideration" very informative. What is it 
suppose to apply to ? The URI interpretation, the protocol, ...?

-------------------------

Scheme name: dis

Status: Provisional

Scheme syntax: dis:<path>
     A DIS URI has no authority, query or fragment part.
     The path segments uses exclusively the characters
     '-', '_', '~, '.', '0' to '9', 'A' to 'Z' and 'a' to 'z'.
     The path may be absolute or root less.
     The total length of a dis URI, including the scheme
     name, is limited to 66 characters.
     URI examples: "dis:", "dis:/", "dis:~", "dis:/-OvsR8/345"

Encoding considerations:
     Not all combinations of the valid chars form a valid
     URI.

Applications/protocols that use this scheme name:
    The URI is a reference to an information stored in the
    Distributed Information System (DIS). The URI is
    intended to be used with Web applications.

Security consideration:
    Unknown, use with care.

Contact: Christophe Meessen <uri-review [at] ditp.org>

Change controller: same as contact

References: http://www.ditp.org

--

-- 
Ch.Meessen
David_Warden | 28 Sep 02:30 2015
Picon

Updated VNC Scheme draft available

Hi all,

An updated version of the proposed VNC URI scheme is now available:
http://www.ietf.org/id/draft-warden-appsawg-vnc-scheme-05.txt

This draft clarifies in Section 3.2 that applications detecting security sensitive parameters in the URI
should not persist that data unless it is encrypted. Users should avoid including sensitive parameters
in environments where they may be accessed and stored by generic URI-handling applications.

The table of contents section titles have also been updated to reflect previous changes. 

David Warden
Software Development Principal Engineer
Dell | Enterprise Solutions Group 
Sean Leonard | 26 Sep 00:58 2015

Request -02 review of SHA URIs

Hello URI Reviewers:

I request review of the SHA URIs in this draft-02, per RFC 7595. The URI schemes are "sha1", "sha256",
"sha1msg", and "sha256msg", respectively.

Most feedback was incorporated, or at least considered, in this document. If folks feel that their
feedback is not reflected please contact me and I will look into it further.

Thank you,

Sean

Begin forwarded message:

> From: internet-drafts <at> ietf.org
> Subject: New Version Notification for draft-seantek-sha-uris-02.txt
> Date: September 25, 2015 at 3:51:02 PM PDT
> 

A new version of I-D, draft-seantek-sha-uris-02.txt
has been successfully submitted by Sean Leonard and posted to the
IETF repository.

Name:		draft-seantek-sha-uris
Revision:	02
Title:		URI Schemes for SHA-1 and SHA-256
Document date:	2015-09-25
Group:		Individual Submission
Pages:		13
URL:            https://www.ietf.org/internet-drafts/draft-seantek-sha-uris-02.txt
Status:         https://datatracker.ietf.org/doc/draft-seantek-sha-uris/
Htmlized:       https://tools.ietf.org/html/draft-seantek-sha-uris-02
Diff:           https://www.ietf.org/rfcdiff?url2=draft-seantek-sha-uris-02

Abstract:
  This document registers Uniform Resource Identifier schemes for use
  with certain Secure Hash Algorithm (SHA) functions, namely SHA-1 and
  SHA-256. The purpose is to identify data streams and content in a
  simple, "drop-in" way within the URI infrastructure.

Attachment (smime.p7s): application/pkcs7-signature, 4831 bytes
_______________________________________________
Uri-review mailing list
Uri-review <at> ietf.org
https://www.ietf.org/mailman/listinfo/uri-review
David_Warden | 22 Sep 19:28 2015
Picon

URI Review of VNC Scheme

Hi everyone,

I've submitted a VNC scheme document:
http://www.ietf.org/id/draft-warden-appsawg-vnc-scheme-04.txt 

Hopefully this will allow VNC clients to be launched from other applications while avoiding conflicts
among competing schemes. 

Review and comments from members of this list are welcome. 

This document has been reviewed to some extent in the applications area working group (apps-discuss) and
by publishers of VNC clients. Upon advice of the area director, we plan to publish this as an independent
submission. As part of this process, I have been advised to request additional review on this list. 

Thanks,

David Warden
Software Development Principal Engineer
Dell | Enterprise Solutions Group 
Adrian Hope-Bailie | 17 Sep 10:14 2015

Scheme with both hierarchical and non-hierarchical elements

Hi list,

My company is in the process of designing a URI scheme to address resources that are part of a complex distributed system.

Some of the resources make sense to be addressed via a hierarchical syntax as they have sub-resources and related resources which could be addressed relative to the parent.

eg: scheme://root-resource/sub-resource/other-relative-resource

However, there are other resources which do not fit this pattern. They stand alone and I am considering using a different syntax for these.

eg: scheme:namespace:resource-identifier

Is it considered bad practice to have a URI scheme that mixes these two forms?

Thanks for the help,
Adrian
_______________________________________________
Uri-review mailing list
Uri-review <at> ietf.org
https://www.ietf.org/mailman/listinfo/uri-review
Jennifer Clark | 16 Sep 15:21 2015

IANA Customer Feedback

Dear IANA Customer,

ICANN strives to continuously improve its delivery of the IANA functions. Please take just 5 minutes to participate in the 2015 IANA Customer Survey. Your feedback is essential to help us improve our service to you.

This short survey is being managed by Ebiquity, an independent research firm. Ebiquity is committed to protecting the confidentiality of all respondents, in line with the Code of Conduct of ESOMAR and CASRO. This means data is reported to ICANN in aggregate, so that all opinions are confidential and not attributed to any specific individual.

Please complete the survey hosted at https://www.ebiquityinsights.com/E0181/index.pl?surveynumber=71823 which will remain open until October 13, 2015. ICANN will summarize the results and publish the summary in December 2015.

We appreciate your time and helping us improve the delivery of the IANA functions.

If you have any questions, please contact me at jennifer.clark <at> ebiquityinsights.com or Marilia Hirano at marilia.hirano <at> icann.org.

Yours sincerely,

Jennifer Clark
Account Director, Ebiquity

If you would not like to receive further emails about this research project please reply to this message and type REMOVE in the subject line.

_______________________________________________
Uri-review mailing list
Uri-review <at> ietf.org
https://www.ietf.org/mailman/listinfo/uri-review

Gmane