Debian Codegraph @

rfc8589.html

raw
1 <pre>Internet Engineering Task Force (IETF) A. Tamas
2 Request for Comments: 8589 B. Phister, Ed.
3 Category: Informational J-E. Rodriguez
4 ISSN: 2070-1721 OP3FT
5 May 2019
6
7
8 <span class="h1">The 'leaptofrogans' URI Scheme</span>
9
10 Abstract
11
12 This document describes the 'leaptofrogans' Uniform Resource
13 Identifier (URI) scheme, which enables applications to launch Frogans
14 Player on a given Frogans site. Frogans is a medium for publishing
15 content and services on the Internet, defined as a generic software
16 layer on the Internet. Frogans Player is software that enables end
17 users to browse Frogans sites.
18
19 Status of This Memo
20
21 This document is not an Internet Standards Track specification; it is
22 published for informational purposes.
23
24 This document is a product of the Internet Engineering Task Force
25 (IETF). It has been approved for publication by the Internet
26 Engineering Steering Group (IESG). Not all documents approved by the
27 IESG are candidates for any level of Internet Standard; see <a href="./rfc7841#section-2">Section&nbsp;2
28 of RFC 7841</a>.
29
30 Information about the current status of this document, any errata,
31 and how to provide feedback on it may be obtained at
32 <a href="https://www.rfc-editor.org/info/rfc8589">https://www.rfc-editor.org/info/rfc8589</a>.
33
34 Copyright Notice
35
36 Copyright (c) 2019 IETF Trust and the persons identified as the
37 document authors. All rights reserved.
38
39 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
40 Provisions Relating to IETF Documents
41 (<a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a>) in effect on the date of
42 publication of this document. Please review these documents
43 carefully, as they describe your rights and restrictions with respect
44 to this document. Code Components extracted from this document must
45 include Simplified BSD License text as described in Section 4.e of
46 the Trust Legal Provisions and are provided without warranty as
47 described in the Simplified BSD License.
48
49
50
51
52 <span class="grey">Tamas, et al. Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc8589">RFC 8589</a> leaptofrogans URI Scheme May 2019</span>
55
56
57 Table of Contents
58
59 <a href="#section-1">1</a>. Background Information . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
60 <a href="#section-1.1">1.1</a>. About Frogans . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
61 <a href="#section-1.2">1.2</a>. About the OP3FT . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
62 <a href="#section-2">2</a>. The Need for a New URI Scheme and Its Purpose . . . . . . . . <a href="#page-3">3</a>
63 <a href="#section-3">3</a>. Choice of the Scheme Name . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
64 <a href="#section-4">4</a>. Scheme Syntax . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
65 <a href="#section-4.1">4.1</a>. URI Scheme . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
66 <a href="#section-4.2">4.2</a>. IRI Usage and Encoding . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
67 <a href="#section-5">5</a>. Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
68 <a href="#section-6">6</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
69 <a href="#section-7">7</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
70 <a href="#section-8">8</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
71 <a href="#section-8.1">8.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
72 <a href="#section-8.2">8.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
73 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
74
75 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Background Information</span>
76
77 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. About Frogans</span>
78
79 Frogans is a medium for publishing content and services on the
80 Internet. From its inception in 1999, the medium was designed as a
81 generic software layer running on top of the original Internet
82 infrastructure (i.e., the TCP and IP protocols and the Domain Name
83 System (DNS)), alongside other existing layers such as E-mail or the
84 World Wide Web.
85
86 As a medium, Frogans is not meant for publishing Web sites, but
87 Frogans sites, a kind of site founded upon a different format,
88 enabling a different kind of communication between end users and
89 publishers of content and services.
90
91 Frogans is intended to be complementary to the World Wide Web; it is
92 not intended to be a replacement. This is analogous to instant
93 messaging, which was not intended to and did not replace E-mail.
94
95 Compared to the World Wide Web, Frogans suggests publishing content
96 and services that involve visual rather than text-based
97 communication, focused content rather than long pages, and natural
98 interaction rather than complex user interfaces. For further
99 information on the reasons for introducing Frogans on the Internet,
100 and for an in-depth discussion of the similarities and differences
101 between Frogans sites and Web sites, see [<a href="#ref-FSDL" title="&quot;Frogans Slide Description Language&quot;">FSDL</a>], Section 1.4
102 ("Frogans sites and Web sites").
103
104
105
106
107
108 <span class="grey">Tamas, et al. Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc8589">RFC 8589</a> leaptofrogans URI Scheme May 2019</span>
111
112
113 The technology making up the medium, i.e., the Frogans technology,
114 includes multiple components such as:
115
116 o An XML-based language, called Frogans Slide Description Language
117 [<a href="#ref-FSDL" title="&quot;Frogans Slide Description Language&quot;">FSDL</a>], used to develop Frogans sites.
118
119 o International identifiers, called Frogans addresses [<a href="#ref-IFAP" title="&quot;International Frogans Address Pattern&quot;">IFAP</a>], used
120 to access Frogans sites. Each Frogans site has its own Frogans
121 address.
122
123 o Browsing software, called Frogans Player, enabling end users to
124 browse Frogans sites. An end user opens a Frogans site by
125 entering its Frogans address in Frogans Player.
126
127 o A registry, called the Frogans Core Registry (FCR), that contains
128 all Frogans addresses registered by Frogans site publishers. The
129 registry operator, called the FCR Operator, ensures the resolution
130 of Frogans addresses when end users enter them in Frogans Player.
131
132 <span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. About the OP3FT</span>
133
134 Created in 2012, the Organization for the Promotion, Protection, and
135 Progress of Frogans Technology [<a href="#ref-OP3FT" title="&quot;Organization for the Promotion, Protection and Progress of Frogans Technology&quot;">OP3FT</a>] is a dedicated, non-profit
136 organization whose purpose is to hold, promote, protect, and ensure
137 the progress of the Frogans technology, in the form of an open
138 standard, available to all, free of charge.
139
140 As part of its mission, the OP3FT develops and releases technical
141 specifications, reference implementations (including Frogans Player),
142 and various policies, which define the rights and responsibilities of
143 all stakeholders involved in the technology worldwide.
144
145 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The Need for a New URI Scheme and Its Purpose</span>
146
147 Generic software layers running on top of the original Internet
148 infrastructure offer mechanisms that enable end users to easily go
149 from one layer to another, in both directions. For example, end
150 users can easily launch their usual Web browser on a given Web page
151 from a message in their usual E-mail client; in the other direction,
152 end users can easily launch their usual E-mail client with a given
153 E-mail address from a Web page in their usual Web browser. This is
154 commonly achieved using URIs [<a href="./rfc3986" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">RFC3986</a>].
155
156 As regards Frogans as a medium, in the outgoing direction, FSDL
157 enables Frogans site publishers to include way-out buttons in their
158 Frogans sites. These buttons enable end users to launch their usual
159 Web browser on a given Web page, or to launch their usual E-mail
160
161
162
163
164 <span class="grey">Tamas, et al. Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc8589">RFC 8589</a> leaptofrogans URI Scheme May 2019</span>
167
168
169 client with a given E-mail address. This is achieved by associating
170 a URI with each of those way-out buttons (the scheme of the URI can
171 be any of 'http', 'https', or 'mailto').
172
173 Conversely, in the incoming direction, Web-site publishers should
174 have a means to include in their Web pages links that enable end
175 users to launch Frogans Player on a given Frogans site. Likewise,
176 people writing E-mail messages should have a means to include in
177 their messages links that enable recipients to launch Frogans Player
178 on a given Frogans site. More generally, any end-user application
179 should be able to launch Frogans Player on a given Frogans site.
180
181 To achieve this, a new URI scheme, containing a Frogans address, is
182 needed.
183
184 Given that Frogans, as a medium, does not enable deep linking for
185 Frogans sites, there is no need for additional information in the new
186 URI scheme other than the Frogans address.
187
188 The use of a media type as a means to include on a Web page a link
189 that enables end users to launch Frogans Player on a given Frogans
190 site was tested in 2006 with the registration of the
191 'vnd.frogans.ltf' media type with IANA [<a href="#ref-LTF" title="&quot;Media Types&quot;">LTF</a>]. But use of a media
192 type was determined to be unsatisfactory for several reasons. First,
193 for any such link included on a Web page, the author of the Web page
194 had to create and host a .ltf file on the Web server hosting that Web
195 page, which was cumbersome. Furthermore, prior to creating such
196 links, the author had to ask the server administrator to associate
197 the .ltf files with the 'vnd.frogans.ltf' media type on the server.
198 Alternatively, the author could create a link via a redirection
199 service that would generate a .ltf file on the fly while associating
200 it with the 'vnd.frogans.ltf' media type. But that alternative
201 raised privacy concerns and potentially added latency for end users.
202 Finally, on the Web browser side, it appeared that using a media type
203 from a Web page to launch another application did not always work,
204 especially on mobile devices.
205
206 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Choice of the Scheme Name</span>
207
208 The name chosen for the new URI scheme is 'leaptofrogans'.
209
210 This scheme name was chosen in compliance with <a href="./rfc7595#section-3.8">[RFC7595], Section&nbsp;3.8</a>
211 ("Scheme Name Considerations").
212
213
214
215
216
217
218
219
220 <span class="grey">Tamas, et al. Informational [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc8589">RFC 8589</a> leaptofrogans URI Scheme May 2019</span>
223
224
225 The following shorter names were discussed, but they were not chosen:
226
227 o 'ltf': this name, an acronym for "leap to Frogans", was considered
228 insufficiently descriptive, especially for typical end users who
229 have little technical knowledge.
230
231 o 'leapto': this name was considered overly general, and it is not
232 specifically associated with Frogans.
233
234 o 'frogans': this name was rejected because it could create
235 confusion between URIs based on this scheme and those Frogans
236 addresses that start with "frogans".
237
238 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Scheme Syntax</span>
239
240 Frogans addresses [<a href="#ref-IFAP" title="&quot;International Frogans Address Pattern&quot;">IFAP</a>] are international identifiers made up of
241 Unicode characters. Thus, a method for encoding non-US-ASCII
242 characters is necessary when the new scheme is used as a URI. The
243 new scheme can also be useful as an IRI [<a href="./rfc3987" title="&quot;Internationalized Resource Identifiers (IRIs)&quot;">RFC3987</a>] in contexts where
244 IRIs are allowed.
245
246 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. URI Scheme</span>
247
248 The syntax for the 'leaptofrogans' URI scheme is:
249
250 leaptofrogans-uri = "leaptofrogans:" pct-encoded-frogans-address
251
252 where pct-encoded-frogans-address is a Frogans address compliant with
253 [<a href="#ref-IFAP" title="&quot;International Frogans Address Pattern&quot;">IFAP</a>] and whose Unicode characters are each encoded as follows:
254
255 o If the character is a US-ASCII character, do not replace it and
256 skip to the next character. Note that according to [<a href="#ref-IFAP" title="&quot;International Frogans Address Pattern&quot;">IFAP</a>], the
257 US-ASCII character cannot be the U+0025 PERCENT SIGN character.
258
259 o Otherwise, apply steps 1 through 3 below:
260
261 1. Convert the character to a sequence of one or more octets
262 using UTF-8 [<a href="#ref-UTF-8" title="&quot;UTF-8, a transformation format of ISO 10646&quot;">UTF-8</a>]
263
264 2. Convert each octet to %HH, where HH is the hexadecimal
265 notation of the octet value. Note that this is identical to
266 the percent-encoding mechanism in <a href="./rfc3986#section-2.1">Section&nbsp;2.1 of [RFC3986]</a>.
267
268 3. Replace the original character with the resulting character
269 sequence (i.e., a sequence of %HH triplets).
270
271
272
273
274
275
276 <span class="grey">Tamas, et al. Informational [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc8589">RFC 8589</a> leaptofrogans URI Scheme May 2019</span>
279
280
281 Examples of 'leaptofrogans' URIs:
282
283 - if the Frogans address is the string of US-ASCII characters
284 "Network-Name*Site-Name", the URI is as follows:
285
286 leaptofrogans:Network-Name*Site-Name
287
288 - if the Frogans address is the string of Unicode characters U+7F51,
289 U+7EDC, U+540D, U+002A, U+7AD9, U+540D (which is a Chinese
290 translation of the Frogans address in the previous example), the
291 URI is as follows:
292
293 leaptofrogans:%E7%BD%91%E7%BB%9C%E5%90%8D*%E7%AB%99%E5%90%8D
294
295 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. IRI Usage and Encoding</span>
296
297 The syntax for an IRI corresponding to the 'leaptofrogans' URI scheme
298 is:
299
300 leaptofrogans-iri = "leaptofrogans:" frogans-address
301
302 where frogans-address is a Frogans address compliant with [<a href="#ref-IFAP" title="&quot;International Frogans Address Pattern&quot;">IFAP</a>] and
303 encoded in UTF-8 [<a href="#ref-UTF-8" title="&quot;UTF-8, a transformation format of ISO 10646&quot;">UTF-8</a>].
304
305 In contexts where both URIs and IRIs are allowed, end-user
306 applications can use either a URI or an IRI based on the
307 'leaptofrogans' URI scheme when launching Frogans Player on a given
308 Frogans site. This is because Frogans Player must interpret both
309 URIs and IRIs based on the 'leaptofrogans' URI scheme. If the U+0025
310 PERCENT SIGN character is found in the string, then the string will
311 be interpreted by Frogans Player as a URI; otherwise, it will be
312 interpreted as an IRI.
313
314 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Trademarks</span>
315
316 In order to enable all users worldwide to use the Frogans technology
317 in a clearly defined, secure, and perpetual environment, the OP3FT
318 Bylaws [<a href="#ref-BYLAWS" title="&quot;Bylaws of the French Fonds de Dotation OP3FT, Organization for the Promotion, Protection and Progress of Frogans Technology&quot;">BYLAWS</a>] provide for the implementation of an intellectual
319 property policy.
320
321 In this context, the OP3FT is the holder of the "Frogans" trademark
322 that is registered in France, the United States, and other countries
323 around the world. The right to use the "Frogans" trademark in
324 references or as part of initiatives in connection with the Frogans
325 technology is granted in the OP3FT Trademark Usage Policy [<a href="#ref-OTUP" title="&quot;OP3FT Trademark Usage Policy&quot;">OTUP</a>].
326
327
328
329
330
331
332 <span class="grey">Tamas, et al. Informational [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc8589">RFC 8589</a> leaptofrogans URI Scheme May 2019</span>
335
336
337 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
338
339 In accordance with the guidelines and registration procedures for new
340 URI schemes [<a href="./rfc7595" title="&quot;Guidelines and Registration Procedures for URI Schemes&quot;">RFC7595</a>], IANA has registered 'leaptofrogans' URI scheme
341 as follows:
342
343 Scheme name: 'leaptofrogans'
344
345 Status: Permanent
346
347 Scheme syntax: See <a href="./rfc8589#section-4">Section&nbsp;4 of RFC 8589</a>.
348
349 Scheme semantics: See <a href="./rfc8589#section-2">Section&nbsp;2 of RFC 8589</a>.
350
351 Encoding considerations: See <a href="./rfc8589#section-4">Section&nbsp;4 of RFC 8589</a>.
352
353 Applications/protocols that use this scheme name: Frogans Player as
354 well as any end-user application (such as a Web browser or an
355 E-mail client) wishing to launch Frogans Player on a given Frogans
356 site.
357
358 Interoperability considerations: There are no known interoperability
359 concerns related to use of the 'leaptofrogans' URI scheme.
360
361 Security considerations: See <a href="./rfc8589#section-7">Section&nbsp;7 of RFC 8589</a>.
362
363 Contact: Alexis Tamas &lt;mailto:[email protected]&gt;
364
365 Change controller: OP3FT &lt;mailto:[email protected]&gt;
366
367 References: <a href="./rfc8589">RFC 8589</a>
368
369 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
370
371 The author of a Web page can create a link where the true nature of
372 the URI is hidden in the link text that is visible to end users. The
373 same applies for an E-mail message and other end-user applications.
374
375 For URIs based on the 'leaptofrogans' URI scheme, the risk of
376 confusion is mitigated because Frogans Player must always display the
377 real Frogans address contained in the URI, and it must always require
378 confirmation by the end user before opening the corresponding Frogans
379 site.
380
381 Also, an end-user application may provide a URI containing a Frogans
382 address that is not valid. This does not represent a risk because,
383 before asking for confirmation by the end user, Frogans Player must
384
385
386
387
388 <span class="grey">Tamas, et al. Informational [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc8589">RFC 8589</a> leaptofrogans URI Scheme May 2019</span>
391
392
393 always verify that the Frogans address contained in the URI is
394 compliant with [<a href="#ref-IFAP" title="&quot;International Frogans Address Pattern&quot;">IFAP</a>], and it must always raise an error if the
395 Frogans address is not compliant.
396
397 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
398
399 <span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
400
401 [<a id="ref-IFAP">IFAP</a>] OP3FT, "International Frogans Address Pattern",
402 Version 1.1, ISBN 978-2-37313-000-3, November 2014,
403 &lt;<a href="https://www.frogans.org/en/resources/ifap/access.html">https://www.frogans.org/en/resources/ifap/access.html</a>&gt;.
404
405 [<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
406 Resource Identifier (URI): Generic Syntax", STD 66,
407 <a href="./rfc3986">RFC 3986</a>, DOI 10.17487/RFC3986, January 2005,
408 &lt;<a href="https://www.rfc-editor.org/info/rfc3986">https://www.rfc-editor.org/info/rfc3986</a>&gt;.
409
410 [<a id="ref-RFC3987">RFC3987</a>] Duerst, M. and M. Suignard, "Internationalized Resource
411 Identifiers (IRIs)", <a href="./rfc3987">RFC 3987</a>, DOI 10.17487/RFC3987,
412 January 2005, &lt;<a href="https://www.rfc-editor.org/info/rfc3987">https://www.rfc-editor.org/info/rfc3987</a>&gt;.
413
414 [<a id="ref-RFC7595">RFC7595</a>] Thaler, D., Ed., Hansen, T., and T. Hardie, "Guidelines
415 and Registration Procedures for URI Schemes", <a href="https://www.rfc-editor.org/bcp/bcp35">BCP 35</a>,
416 <a href="./rfc7595">RFC 7595</a>, DOI 10.17487/RFC7595, June 2015,
417 &lt;<a href="https://www.rfc-editor.org/info/rfc7595">https://www.rfc-editor.org/info/rfc7595</a>&gt;.
418
419 [<a id="ref-UTF-8">UTF-8</a>] Yergeau, F., "UTF-8, a transformation format of ISO
420 10646", STD 63, <a href="./rfc3629">RFC 3629</a>, DOI 10.17487/RFC3629, November
421 2003, &lt;<a href="https://www.rfc-editor.org/info/rfc3629">https://www.rfc-editor.org/info/rfc3629</a>&gt;.
422
423 <span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
424
425 [<a id="ref-BYLAWS">BYLAWS</a>] OP3FT, "Bylaws of the French Fonds de Dotation OP3FT,
426 Organization for the Promotion, Protection and Progress of
427 Frogans Technology", July 2016,
428 &lt;<a href="https://www.op3ft.org/en/resources/bylaws/access.html">https://www.op3ft.org/en/resources/bylaws/access.html</a>&gt;.
429
430 [<a id="ref-FSDL">FSDL</a>] OP3FT, "Frogans Slide Description Language", Version 3.0,
431 Preliminary Draft 7, September 2018,
432 &lt;<a href="https://www.frogans.org/en/resources/fsdl/access.html">https://www.frogans.org/en/resources/fsdl/access.html</a>&gt;.
433
434 [<a id="ref-LTF">LTF</a>] IANA, "Media Types",
435 &lt;<a href="https://www.iana.org/assignments/media-types">https://www.iana.org/assignments/media-types</a>&gt;.
436
437 [<a id="ref-OP3FT">OP3FT</a>] OP3FT, "Organization for the Promotion, Protection and
438 Progress of Frogans Technology", &lt;<a href="https://www.op3ft.org/">https://www.op3ft.org/</a>&gt;.
439
440
441
442
443
444 <span class="grey">Tamas, et al. Informational [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc8589">RFC 8589</a> leaptofrogans URI Scheme May 2019</span>
447
448
449 [<a id="ref-OTUP">OTUP</a>] OP3FT, "OP3FT Trademark Usage Policy", March 2017,
450 &lt;<a href="https://www.frogans.org/en/resources/otup/access.html">https://www.frogans.org/en/resources/otup/access.html</a>&gt;.
451
452 Authors' Addresses
453
454 Alexis Tamas
455 OP3FT
456 6, Square Mozart
457 75016 Paris
458 France
459
460 Phone: +33 1 53 92 00 40
461 Email: [email protected]
462
463
464 Benjamin Phister (editor)
465 OP3FT
466 6, Square Mozart
467 75016 Paris
468 France
469
470 Phone: +33 1 53 92 00 40
471 Email: [email protected]
472
473
474 Jean-Emmanuel Rodriguez
475 OP3FT
476 6, Square Mozart
477 75016 Paris
478 France
479
480 Phone: +33 1 53 92 00 40
481 Email: [email protected]
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500 Tamas, et al. Informational [Page 9]
501 </pre>