idnits 2.17.1 draft-op3ft-leaptofrogans-uri-scheme-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 7, 2019) is 1898 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force A. Tamas 3 Internet-Draft B. Phister, Ed. 4 Intended status: Informational J-E. Rodriguez 5 Expires: August 11, 2019 OP3FT 6 February 7, 2019 8 The 'leaptofrogans' URI Scheme 9 draft-op3ft-leaptofrogans-uri-scheme-07 11 Abstract 13 This document describes the 'leaptofrogans' Uniform Resource 14 Identifier (URI) scheme, which enables applications to launch Frogans 15 Player on a given Frogans site. Frogans is a medium for publishing 16 content and services on the Internet, defined as a generic software 17 layer on the Internet. Frogans Player is software enabling end users 18 to browse Frogans sites. 20 Status of this Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on August 11, 2019. 37 Copyright Notice 39 Copyright (c) 2019 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Background Information . . . . . . . . . . . . . . . . . . . . 3 55 1.1. About Frogans . . . . . . . . . . . . . . . . . . . . . . . 3 56 1.2. About the OP3FT . . . . . . . . . . . . . . . . . . . . . . 4 57 2. The Need for a New URI Scheme and its Purpose . . . . . . . . . 4 58 3. The Choice of the Scheme Name . . . . . . . . . . . . . . . . . 5 59 4. Scheme Syntax . . . . . . . . . . . . . . . . . . . . . . . . . 5 60 4.1. URI Scheme . . . . . . . . . . . . . . . . . . . . . . . . 6 61 4.2. IRI Usage and Encoding . . . . . . . . . . . . . . . . . . 6 62 5. Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . 7 63 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 64 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 8 65 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 66 8.1. Normative References . . . . . . . . . . . . . . . . . . . 8 67 8.2. Informative References . . . . . . . . . . . . . . . . . . 9 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 70 1. Background Information 72 1.1. About Frogans 74 Frogans is a medium for publishing content and services on the 75 Internet. From its inception in 1999, the medium was designed as a 76 generic software layer running on top of the original Internet 77 infrastructure, i.e. the TCP and IP protocols and the Domain Name 78 System (DNS), alongside other existing layers such as E-mail or the 79 World Wide Web. 81 As a medium, Frogans is not meant for publishing Web sites, but 82 Frogans sites, a kind of site founded upon a different format, 83 enabling a different kind of communication between end users and 84 publishers of content and services. 86 Frogans is intended to be complementary to the World Wide Web, and 87 not to replace it. This is analogous to instant messaging, which was 88 not intended to and did not replace E-mail. 90 Compared to the World Wide Web, Frogans suggests visual rather than 91 text-based communication, focused content rather than long pages, and 92 natural interaction rather than complex user interfaces. For further 93 information on the reasons for introducing Frogans on the Internet, 94 and for an in-depth discussion of the similarities and differences 95 between Frogans sites and Web sites, see [FSDL] Section 1.4 "Frogans 96 sites and Web sites". 98 The technology making up the medium, i.e. the Frogans technology, 99 includes multiple components such as: 101 o An XML-based language, called Frogans Slide Description Language 102 [FSDL], used to develop Frogans sites. 104 o International identifiers, called Frogans addresses [IFAP], used 105 to access Frogans sites. Each Frogans site has its own Frogans 106 address. 108 o Browsing software, called Frogans Player, enabling end users to 109 browse Frogans sites. An end user opens a Frogans site by 110 entering its Frogans address in Frogans Player. 112 o A registry, called the Frogans Core Registry (FCR), that contains 113 all Frogans addresses registered by Frogans site publishers. The 114 registry operator, called the FCR Operator, ensures the resolution 115 of Frogans addresses when end users enter them in Frogans Player. 117 1.2. About the OP3FT 119 Created in 2012, the OP3FT [OP3FT] is a dedicated, non-profit 120 organization whose purpose is to hold, promote, protect and ensure 121 the progress of the Frogans technology, in the form of an open 122 standard, available to all, free of charge. 124 As part of its mission, the OP3FT develops and releases technical 125 specifications, reference implementations (including Frogans Player), 126 and various policies, which define the rights and responsibilities of 127 all stakeholders involved in the technology worldwide. 129 2. The Need for a New URI Scheme and its Purpose 131 Generic software layers running on top of the original Internet 132 infrastructure offer mechanisms enabling end users to easily go from 133 one layer to another, in both directions. For example, end users can 134 easily launch their usual Web browser on a given Web page from a 135 message in their usual E-mail client; and in the other direction, end 136 users can easily launch their usual E-mail client with a given E-mail 137 address from a Web page in their usual Web browser. This is commonly 138 achieved using URIs [RFC3986]. 140 As regards Frogans as a medium, in the outgoing direction, FSDL 141 enables Frogans site publishers to include in their Frogans sites 142 way-out buttons. These buttons enable end users to launch their 143 usual Web browser on a given Web page, or to launch their usual 144 E-mail client with a given E-mail address. This is achieved by 145 associating a URI with each of those way-out buttons (the scheme of 146 the URI can be any of 'http', 'https', or 'mailto'). 148 Conversely, in the incoming direction, Web site publishers should 149 have a means to include in their Web pages links enabling end users 150 to launch Frogans Player on a given Frogans site. Likewise, people 151 writing E-mail messages should have a means to include in their 152 messages links enabling recipients to launch Frogans Player on a 153 given Frogans site. More generally, any end-user application should 154 be able to launch Frogans Player on a given Frogans site. 156 In order to achieve this, a new URI scheme, containing a Frogans 157 address, is needed. 159 Given that Frogans as a medium does not enable deep linking for 160 Frogans sites, there is no need for additional information in the new 161 URI scheme other than the Frogans address. 163 The use of a MIME type as a means to include on a Web page a link 164 enabling end users to launch Frogans Player on a given Frogans site 165 was tested in 2006 with the registration of the 'vnd.frogans.ltf' 166 media type with IANA [LTF]. But that use of a media type was 167 revealed to be unsatisfactory for several reasons. First, for any 168 such link included on a Web page, the author of the Web page had to 169 create and host a .ltf file on the Web server hosting that Web page, 170 which was cumbersome. Furthermore, prior to creating such links, the 171 author had to ask the server administrator to associate the .ltf 172 files with the 'vnd.frogans.ltf' media type on the server. 173 Alternatively, the author could create a link via a redirection 174 service which would generate a .ltf file on the fly while associating 175 it with the 'vnd.frogans.ltf' media type. But that alternative 176 raised privacy concerns, and potentially added latency for end users. 177 Finally, on the Web browser side, it appeared that using a media type 178 from a Web page to launch another application did not always work, 179 especially on mobile devices. 181 3. The Choice of the Scheme Name 183 The name chosen for the new URI scheme is 'leaptofrogans'. 185 This scheme name was chosen in compliance with [RFC7595] Section 3.8 186 "Scheme Name Considerations". 188 As regards the length of the scheme name, shorter names were 189 discussed but were not chosen: 191 o 'ltf': this name, an acronym for "leap to Frogans", was considered 192 insufficiently descriptive, especially for typical end users who 193 have little technical knowledge. 195 o 'leapto': this name was considered overly general, and is not 196 specifically associated with Frogans. 198 o 'frogans': this name was rejected because it could create 199 confusion between URIs based on this scheme and those Frogans 200 addresses that start with "frogans". 202 4. Scheme Syntax 204 Frogans addresses [IFAP] are international identifiers made up of 205 Unicode characters. Thus a method for encoding non US-ASCII 206 characters is necessary when the new scheme is used as a URI. The 207 new scheme can also be useful as an IRI [RFC3987] in contexts where 208 IRIs are allowed. 210 4.1. URI Scheme 212 The syntax for the 'leaptofrogans' URI scheme is: 214 leaptofrogans-uri = "leaptofrogans:" pct-encoded-frogans-address 216 where pct-encoded-frogans-address is a Frogans address compliant with 217 [IFAP] whose Unicode characters are each encoded as follows: 219 o If the character is a US-ASCII character, do not replace it and 220 skip to the next character. Note that according to [IFAP], this 221 character cannot be the U+0025 PERCENT SIGN character. 223 o Otherwise, apply steps 1 through 3 below: 225 1. Convert the character to a sequence of one or more octets 226 using UTF-8 [UTF-8] 228 2. Convert each octet to %HH, where HH is the hexadecimal 229 notation of the octet value. Note that this is identical to 230 the percent-encoding mechanism in section 2.1 of [RFC3986]. 232 3. Replace the original character with the resulting character 233 sequence (i.e., a sequence of %HH triplets). 235 Examples of 'leaptofrogans' URIs: 237 - if the Frogans address is the string of US-ASCII characters 238 "Network-Name*Site-Name": 240 leaptofrogans:Network-Name*Site-Name 242 - if the Frogans address is the string of Unicode characters U+7F51, 243 U+7EDC, U+540D, U+002A, U+7AD9, U+540D (which is a Chinese 244 translation of the Frogans address in the previous example): 246 leaptofrogans:%E7%BD%91%E7%BB%9C%E5%90%8D*%E7%AB%99%E5%90%8D 248 4.2. IRI Usage and Encoding 250 The syntax for IRIs corresponding to the 'leaptofrogans' URI scheme 251 is: 253 leaptofrogans-iri = "leaptofrogans:" frogans-address 255 where frogans-address is a Frogans address compliant with [IFAP] and 256 encoded in UTF-8 [UTF-8]. 258 In contexts where both URIs and IRIs are allowed, end-user 259 applications can use either a URI or an IRI based on the 260 'leaptofrogans' URI scheme when launching Frogans Player on a given 261 Frogans site. This is because Frogans Player must interpret both 262 URIs and IRIs based on the 'leaptofrogans' URI scheme. If the U+0025 263 PERCENT SIGN character is found in the string, then the string will 264 be interpreted by Frogans Player as a URI, otherwise it will be 265 interpreted as an IRI. 267 5. Trademarks 269 In order to enable all users worldwide to use the Frogans technology 270 in a clearly defined, secure and perpetual environment, the OP3FT 271 Bylaws [BYLAWS] provide for the implementation of an intellectual 272 property policy. 274 In this context, the OP3FT is the holder of the "Frogans" trademark 275 which is registered in France, the United States, and other countries 276 around the world. The right to use the "Frogans" trademark in 277 references or as part of initiatives in connection with the Frogans 278 technology is granted in the OP3FT Trademark Usage Policy [OTUP]. 280 6. IANA Considerations 282 [RFC Editor: Please replace 'xxxx' with assigned RFC number before 283 publication] 285 In accordance with the guidelines and registration procedures for new 286 URI schemes [RFC7595], this section provides the information needed 287 to register the 'leaptofrogans' URI scheme. 289 Scheme name: 'leaptofrogans' 291 Status: Permanent 293 Scheme syntax: See Section 4 of RFC xxxx. 295 Scheme semantics: See Section 2 of RFC xxxx. 297 Encoding considerations: See Section 4 of RFC xxxx. 299 Applications/protocols that use this scheme name: Frogans Player as 300 well as any end-user application (such as a Web browser or an E-mail 301 client) wishing to launch Frogans Player on a given Frogans site. 303 Interoperability considerations: There are no known interoperability 304 concerns related to use of the 'leaptofrogans' URI scheme. 306 Security considerations: See Section 7 of RFC xxxx. 308 Contact: Alexis Tamas mailto:alexis.tamas@op3ft.org 310 Change controller: OP3FT mailto:contact-standards@op3ft.org 312 References: RFC xxxx. 314 7. Security Considerations 316 The author of a Web page can create a link where the true nature of 317 the URI is hidden in the link text which is visible to end users. 318 The same applies for an E-mail message as well as for other end-user 319 applications. 321 As concerns URIs based on the 'leaptofrogans' URI scheme, this risk 322 of confusion is mitigated because Frogans Player must always display 323 the real Frogans address contained in the URI, and require 324 confirmation by the end user before opening the corresponding Frogans 325 site. 327 Also, an end-user application may provide a URI containing a Frogans 328 address that is not valid. This does not represent a risk because, 329 before asking for confirmation by the end user, Frogans Player must 330 always verify that the Frogans address contained in the URI is 331 compliant with [IFAP], and raise an error if the Frogans address is 332 not compliant. 334 8. References 336 8.1. Normative References 338 [IFAP] OP3FT, "International Frogans Address Pattern", 339 Version 1.1, ISBN 978-2-37313-000-3, November 2014, 340 . 342 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 343 Resource Identifier (URI): Generic Syntax", STD 66, 344 RFC 3986, DOI 10.17487/RFC3986, January 2005, 345 . 347 [RFC3987] Duerst, M. and M. Suignard, "Internationalized Resource 348 Identifiers (IRIs)", RFC 3987, DOI 10.17487/RFC3987, 349 January 2005, . 351 [RFC7595] Thaler, D., Ed., Hansen, T., and T. Hardie, "Guidelines 352 and Registration Procedures for URI Schemes", BCP 35, 353 RFC 7595, DOI 10.17487/RFC7595, June 2015, 354 . 356 [UTF-8] Yergeau, F., "UTF-8, a transformation format of ISO 357 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, 358 November 2003, . 360 8.2. Informative References 362 [BYLAWS] OP3FT, "Bylaws of the French Fonds de Dotation OP3FT, 363 Organization for the Promotion, Protection and Progress of 364 Frogans Technology", March 2012, 365 . 367 [FSDL] OP3FT, "Frogans Slide Description Language - 3.0", 368 Preliminary Draft 7, September 2018, 369 . 371 [LTF] Tamas, A., "Media Type 'vnd.frogans.ltf'", March 2006, . 375 [OP3FT] OP3FT, "Organization for the Promotion, Protection and 376 Progress of Frogans Technology", 2012, 377 . 379 [OTUP] OP3FT, "OP3FT Trademark Usage Policy", March 2017, 380 . 382 Authors' Addresses 384 Alexis Tamas 385 OP3FT 386 6, Square Mozart 387 75016 Paris, 388 France 390 Phone: +33 1 53 92 00 40 391 Email: alexis.tamas@op3ft.org 392 Benjamin Phister (editor) 393 OP3FT 394 6, Square Mozart 395 75016 Paris, 396 France 398 Phone: +33 1 53 92 00 40 399 Email: benjamin.phister@op3ft.org 401 Jean-Emmanuel Rodriguez 402 OP3FT 403 6, Square Mozart 404 75016 Paris, 405 France 407 Phone: +33 1 53 92 00 40 408 Email: jean-emmanuel.rodriguez@contrib.op3ft.org