idnits 2.17.1 draft-op3ft-leaptofrogans-uri-scheme-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- -- The document has an IETF Trust Provisions (28 Dec 2009) Section 6.c(i) Publication Limitation clause. 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 (September 9, 2018) is 2049 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). 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: March 13, 2019 OP3FT 6 September 9, 2018 8 The 'leaptofrogans' URI Scheme 9 draft-op3ft-leaptofrogans-uri-scheme-02 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. This document may not be modified, 24 and derivative works of it may not be created, except to format it 25 for publication as an RFC or to translate it into languages other 26 than English. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on March 13, 2019. 40 Copyright Notice 42 Copyright (c) 2018 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Background Information . . . . . . . . . . . . . . . . . . . . 3 58 1.1. About Frogans . . . . . . . . . . . . . . . . . . . . . . . 3 59 1.2. About the OP3FT . . . . . . . . . . . . . . . . . . . . . . 4 60 2. The Need for a New URI Scheme and its Purpose . . . . . . . . . 4 61 3. The Choice of the Scheme Name . . . . . . . . . . . . . . . . . 4 62 4. Scheme Syntax . . . . . . . . . . . . . . . . . . . . . . . . . 5 63 4.1. URI Scheme . . . . . . . . . . . . . . . . . . . . . . . . 5 64 4.2. IRI Usage and Encoding . . . . . . . . . . . . . . . . . . 5 65 5. Rights to Use the Trademark . . . . . . . . . . . . . . . . . . 6 66 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 67 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 68 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 69 8.1. Normative References . . . . . . . . . . . . . . . . . . . 7 70 8.2. Informative References . . . . . . . . . . . . . . . . . . 8 71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 73 1. Background Information 75 1.1. About Frogans 77 Frogans is a medium for publishing content and services on the 78 Internet. From its inception in 1999, the medium was designed as a 79 generic software layer running on top of the original Internet 80 infrastructure, i.e. the TCP and IP protocols and the Domain Name 81 System (DNS), alongside other existing layers such as E-mail or the 82 World Wide Web. 84 As a medium, Frogans is not meant for publishing Web sites, but 85 Frogans sites, a kind of site founded upon a different format, 86 enabling a different kind of communication between end users and 87 publishers of content and services. 89 Frogans is intended to be complementary to the World Wide Web, and 90 not to replace it. This is just like instant messaging, which was 91 not intended to and did not replace E-mail. 93 Compared to the World Wide Web, Frogans suggests visual rather than 94 text-based communication, focused content rather than long pages, and 95 natural interaction rather than complex user interfaces (see [FSDL] 96 Section 1.4 "Frogans 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 Internet offer 132 mechanisms enabling end users to easily go from one layer to another, 133 in both directions. This is commonly achieved using URIs [RFC3986]. 135 As regards the Frogans layer, in the outgoing direction, FSDL enables 136 Frogans site publishers to include in their Frogans sites way-out 137 buttons enabling end users to launch their usual Web browser on a 138 given Web page, or to launch their usual E-mail client with a given 139 E-mail address. This is achieved by associating a URI with each of 140 those way-out buttons (the scheme of the URI can be either 'http', 141 'https', or 'mailto'). 143 Conversely, in the incoming direction, Web site publishers should 144 have a means to include in their Web pages links enabling end users 145 to launch Frogans Player on a given Frogans site. Likewise, people 146 writing E-mail messages should have a means to include in their 147 messages links enabling recipients to launch Frogans Player on a 148 given Frogans site. More generally, any end-user application should 149 be able to launch Frogans Player on a given Frogans site. 151 In order to achieve this, a new URI scheme, containing a Frogans 152 address, is needed. 154 Given that Frogans as a medium does not enable deep linking for 155 Frogans sites, there is no need for additional information in the new 156 URI scheme other than the Frogans address. 158 3. The Choice of the Scheme Name 160 [RFC Editor: Please delete this section before publication] 162 The name chosen for the new URI scheme is 'leaptofrogans'. 164 This scheme name was chosen in compliance with [RFC7595] Section 3.8 165 "Scheme Name Considerations". 167 As regards the length of the scheme name, shorter names were 168 discussed but were not chosen: 170 o 'ltf': this name, an acronym for "leap to Frogans", was considered 171 insufficiently descriptive, especially for typical end users who 172 have little technical knowledge. 174 o 'leapto': this name was considered overly general, and is not 175 specifically associated with Frogans. 177 o 'frogans': this name was rejected because it could create 178 confusion between URIs based on this scheme and those Frogans 179 addresses that start with "frogans". 181 4. Scheme Syntax 183 Frogans addresses [IFAP] are international identifiers made up of 184 Unicode characters, so the new scheme will be also useful as an IRI 185 [RFC3987]. As a result, in compliance with [RFC7595] Section 1.1. 186 "URIs and IRIs", the corresponding URI syntax is defined and the IRI 187 usage follows the rules and transformations defined in [RFC3987]. 189 4.1. URI Scheme 191 The syntax for the 'leaptofrogans' URI scheme is: 193 leaptofrogans-uri = "leaptofrogans:" mapped-frogans-address 195 where mapped-frogans-address is a Frogans address compliant with 196 [IFAP] and encoded in UTF-8 [UTF-8], which is mapped according to the 197 method specified in [RFC3987] Section 3.1. "Mapping of IRIs to 198 URIs". 200 4.2. IRI Usage and Encoding 202 The syntax for IRIs corresponding to the 'leaptofrogans' URI scheme 203 is: 205 leaptofrogans-iri = "leaptofrogans:" frogans-address 207 where frogans-address is a Frogans address compliant with [IFAP] and 208 encoded in UTF-8 [UTF-8]. 210 Given that Frogans addresses cannot contain U+0025 PERCENT SIGN 211 characters, the conversion specified in [RFC3987] of an original IRI 212 to a URI (Section 3.1. "Mapping of IRIs to URIs"), then back to an 213 IRI (Section 3.2. "Converting URIs to IRIs") will result exactly in 214 the original IRI. 216 End-user applications can use either a URI or an IRI based on the 217 'leaptofrogans' URI scheme when launching Frogans Player on a given 218 Frogans site. This is because Frogans Player interprets both URIs 219 and IRIs based on the 'leaptofrogans' URI scheme. If the U+0025 220 PERCENT SIGN character is found in the string, then the string is 221 interpreted as a URI, otherwise it is interpreted as an IRI. 223 5. Rights to Use the Trademark 225 In order to enable all users worldwide to use the Frogans technology 226 in a clearly defined, secure and perpetual environment, the OP3FT 227 Bylaws [BYLAWS] provide for the implementation of an intellectual 228 property policy. 230 In this context, the OP3FT is the holder of the "Frogans" trademark 231 which is registered in France, the United States, and other countries 232 around the world. 234 However, this does not cause any problems with rights to use the 235 scheme name in IETF specifications and Internet protocols because, in 236 compliance with [RFC5378] Section 3.4. "Rights to Use Trademarks", 237 the OP3FT hereby grants to the IETF Trust a perpetual license to use 238 the "Frogans" trademark as part of the scheme name. 240 6. IANA Considerations 242 [RFC Editor: Please replace 'xxxx' with assigned RFC number before 243 publication] 245 In accordance with the guidelines and registration procedures for new 246 URI schemes [RFC7595], this section provides the information needed 247 to register the 'leaptofrogans' URI scheme. 249 Scheme name: 'leaptofrogans' 251 Status: permanent 253 URI Scheme Syntax: See Section 4 of RFC xxxx. 255 URI Scheme semantics: See Section 2 of RFC xxxx. 257 Encoding Considerations: See Section 4 of RFC xxxx. 259 Applications/protocols that use this scheme name: Frogans Player as 260 well as any end-user application (such as a Web browser or an E-mail 261 client) wishing to launch Frogans Player on a given Frogans site. 263 Interoperability Considerations: There are no known interoperability 264 concerns related to use of the 'leaptofrogans' URI scheme. 266 Security Considerations: See Section 7 of RFC xxxx. 268 Contact: Alexis Tamas mailto:alexis.tamas@op3ft.org 270 Change controller: OP3FT mailto:contact-standards@op3ft.org 272 References: RFC xxxx. 274 7. Security Considerations 276 The author of a Web page can create a link where the true nature of 277 the URI is hidden in the link text which is visible to end users. 278 The same applies for an E-mail message as well as for other end-user 279 applications. 281 As concerns URIs based on the 'leaptofrogans' URI scheme, this risk 282 of confusion is mitigated because Frogans Player always displays the 283 real Frogans address contained in the URI, and requires confirmation 284 by the end user before opening the corresponding Frogans site. 286 Also, an end-user application may provide a URI containing a Frogans 287 address that is not valid. This does not represent a risk because, 288 before asking for confirmation by the end user, Frogans Player always 289 verifies that the Frogans address contained in the URI is compliant 290 with [IFAP], and raises an error if the Frogans address is not 291 compliant. 293 8. References 295 8.1. Normative References 297 [IFAP] OP3FT, "International Frogans Address Pattern", 298 Version 1.1, ISBN 978-2-37313-000-3, November 2014, 299 . 301 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 302 Resource Identifier (URI): Generic Syntax", STD 66, 303 RFC 3986, DOI 10.17487/RFC3986, January 2005, 304 . 306 [RFC3987] Duerst, M. and M. Suignard, "Internationalized Resource 307 Identifiers (IRIs)", RFC 3987, DOI 10.17487/RFC3987, 308 January 2005, . 310 [RFC5378] Bradner, S., Ed. and J. Contreras, Ed., "Rights 311 Contributors Provide to the IETF Trust", BCP 78, RFC 5378, 312 DOI 10.17487/RFC5378, November 2008, 313 . 315 [RFC7595] Thaler, D., Ed., Hansen, T., and T. Hardie, "Guidelines 316 and Registration Procedures for URI Schemes", BCP 35, 317 RFC 7595, DOI 10.17487/RFC7595, June 2015, 318 . 320 [UTF-8] Yergeau, F., "UTF-8, a transformation format of ISO 321 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, 322 November 2003, . 324 8.2. Informative References 326 [BYLAWS] OP3FT, "Bylaws of the French Fonds de Dotation OP3FT, 327 Organization for the Promotion, Protection and Progress of 328 Frogans Technology", March 2012, 329 . 331 [FSDL] OP3FT, "Frogans Slide Description Language - 3.0", 332 Preliminary Draft 7, September 2018, 333 . 335 [OP3FT] OP3FT, "Organization for the Promotion, Protection and 336 Progress of Frogans Technology", . 338 Authors' Addresses 340 Alexis Tamas 341 OP3FT 342 6, Square Mozart 343 75016 Paris, 344 France 346 Phone: +33 1 53 92 00 40 347 Email: alexis.tamas@op3ft.org 348 Benjamin Phister (editor) 349 OP3FT 350 6, Square Mozart 351 75016 Paris, 352 France 354 Phone: +33 1 53 92 00 40 355 Email: benjamin.phister@op3ft.org 357 Jean-Emmanuel Rodriguez 358 OP3FT 359 6, Square Mozart 360 75016 Paris, 361 France 363 Phone: +33 1 53 92 00 40 364 Email: jean-emmanuel.rodriguez@op3ft.org