1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
|
<pre>Network Working Group P. Saint-Andre
Request for Comments: 4622 JSF
Category: Standards Track July 2006
<span class="h1">Internationalized Resource Identifiers (IRIs)</span>
<span class="h1">and Uniform Resource Identifiers (URIs) for</span>
<span class="h1">the Extensible Messaging and Presence Protocol (XMPP)</span>
Status of This Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
This document defines the use of Internationalized Resource
Identifiers (IRIs) and Uniform Resource Identifiers (URIs) in
identifying or interacting with entities that can communicate via the
Extensible Messaging and Presence Protocol (XMPP).
<span class="grey">Saint-Andre Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc4622">RFC 4622</a> XMPP IRIs/URIs July 2006</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a>
<a href="#section-1.1">1.1</a>. Terminology ................................................<a href="#page-3">3</a>
<a href="#section-2">2</a>. Use of XMPP IRIs and URIs .......................................<a href="#page-4">4</a>
<a href="#section-2.1">2.1</a>. Rationale ..................................................<a href="#page-4">4</a>
<a href="#section-2.2">2.2</a>. Form .......................................................<a href="#page-4">4</a>
<a href="#section-2.3">2.3</a>. Authority Component ........................................<a href="#page-6">6</a>
<a href="#section-2.4">2.4</a>. Path Component .............................................<a href="#page-7">7</a>
<a href="#section-2.5">2.5</a>. Query Component ............................................<a href="#page-7">7</a>
<a href="#section-2.6">2.6</a>. Fragment Identifier Component ..............................<a href="#page-9">9</a>
<a href="#section-2.7">2.7</a>. Generation of XMPP IRIs/URIs ...............................<a href="#page-9">9</a>
<a href="#section-2.7.1">2.7.1</a>. Generation Method ...................................<a href="#page-9">9</a>
<a href="#section-2.7.2">2.7.2</a>. Generation Notes ...................................<a href="#page-10">10</a>
<a href="#section-2.7.3">2.7.3</a>. Generation Example .................................<a href="#page-11">11</a>
<a href="#section-2.8">2.8</a>. Processing of XMPP IRIs/URIs ..............................<a href="#page-12">12</a>
<a href="#section-2.8.1">2.8.1</a>. Processing Method ..................................<a href="#page-12">12</a>
<a href="#section-2.8.2">2.8.2</a>. Processing Notes ...................................<a href="#page-13">13</a>
<a href="#section-2.8.3">2.8.3</a>. Processing Example .................................<a href="#page-14">14</a>
<a href="#section-2.9">2.9</a>. Internationalization ......................................<a href="#page-14">14</a>
<a href="#section-3">3</a>. IANA Registration of xmpp URI Scheme ...........................<a href="#page-15">15</a>
<a href="#section-3.1">3.1</a>. URI Scheme Name ...........................................<a href="#page-15">15</a>
<a href="#section-3.2">3.2</a>. Status ....................................................<a href="#page-15">15</a>
<a href="#section-3.3">3.3</a>. URI Scheme Syntax .........................................<a href="#page-15">15</a>
<a href="#section-3.4">3.4</a>. URI Scheme Semantics ......................................<a href="#page-16">16</a>
<a href="#section-3.5">3.5</a>. Encoding Considerations ...................................<a href="#page-16">16</a>
<a href="#section-3.6">3.6</a>. Applications/protocols That Use This URI Scheme Name ......<a href="#page-16">16</a>
<a href="#section-3.7">3.7</a>. Interoperability Considerations ...........................<a href="#page-16">16</a>
<a href="#section-3.8">3.8</a>. Security Considerations ...................................<a href="#page-16">16</a>
<a href="#section-3.9">3.9</a>. Contact ...................................................<a href="#page-17">17</a>
<a href="#section-3.10">3.10</a>. Author/Change Controller .................................<a href="#page-17">17</a>
<a href="#section-3.11">3.11</a>. References ...............................................<a href="#page-17">17</a>
<a href="#section-4">4</a>. IANA Considerations ............................................<a href="#page-17">17</a>
<a href="#section-5">5</a>. Security Considerations ........................................<a href="#page-17">17</a>
<a href="#section-5.1">5.1</a>. Reliability and Consistency ...............................<a href="#page-17">17</a>
<a href="#section-5.2">5.2</a>. Malicious Construction ....................................<a href="#page-18">18</a>
<a href="#section-5.3">5.3</a>. Back-End Transcoding ......................................<a href="#page-18">18</a>
<a href="#section-5.4">5.4</a>. Sensitive Information .....................................<a href="#page-18">18</a>
<a href="#section-5.5">5.5</a>. Semantic Attacks ..........................................<a href="#page-19">19</a>
<a href="#section-5.6">5.6</a>. Spoofing ..................................................<a href="#page-19">19</a>
<a href="#section-6">6</a>. References .....................................................<a href="#page-20">20</a>
<a href="#section-6.1">6.1</a>. Normative References ......................................<a href="#page-20">20</a>
<a href="#section-6.2">6.2</a>. Informative References ....................................<a href="#page-20">20</a>
<span class="grey">Saint-Andre Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc4622">RFC 4622</a> XMPP IRIs/URIs July 2006</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The Extensible Messaging and Presence Protocol (XMPP) is a streaming
XML technology that enables any two entities on a network to exchange
well-defined but extensible XML elements (called "XML stanzas") at a
rate close to real time.
As specified in [<a href="#ref-XMPP-CORE" title=""Extensible Messaging and Presence Protocol (XMPP): Core"">XMPP-CORE</a>], entity addresses as used in
communications over an XMPP network must not be prepended with a
Uniform Resource Identifier (URI) scheme (as specified in [<a href="#ref-URI" title=""Uniform Resource Identifier (URI): Generic Syntax"">URI</a>]).
However, applications external to an XMPP network may need to
identify XMPP entities either as URIs or, in a more modern fashion,
as Internationalized Resource Identifiers (IRIs; see [<a href="#ref-IRI" title=""Internationalized Resource Identifiers (IRIs)"">IRI</a>]).
Examples of such external applications include databases that need to
store XMPP addresses and non-native user agents such as web browsers
and calendaring applications that provide interfaces to XMPP
services.
The format for an XMPP address is defined in [<a href="#ref-XMPP-CORE" title=""Extensible Messaging and Presence Protocol (XMPP): Core"">XMPP-CORE</a>]. Such an
address may contain nearly any [<a href="#ref-UNICODE" title=""The Unicode Standard, Version 3.2.0"">UNICODE</a>] character and must adhere to
various profiles of [<a href="#ref-STRINGPREP" title=""Preparation of Internationalized Strings ("">STRINGPREP</a>]. The result is that an XMPP address
is fully internationalizable and is very close to being an IRI
without a scheme. However, given that there is no freestanding
registry of IRI schemes, it is necessary to define XMPP identifiers
primarily as URIs rather than as IRIs, and to register an XMPP URI
scheme instead of an IRI scheme. Therefore, this document does the
following:
o Specifies how to identify XMPP entities as IRIs or URIs.
o Specifies how to interact with XMPP entities as IRIs or URIs.
o Formally defines the syntax for XMPP IRIs and URIs.
o Specifies how to transform XMPP IRIs into URIs and vice-versa.
o Registers the xmpp URI scheme.
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Terminology</span>
This document inherits terminology from [<a href="#ref-IRI" title=""Internationalized Resource Identifiers (IRIs)"">IRI</a>], [<a href="#ref-URI" title=""Uniform Resource Identifier (URI): Generic Syntax"">URI</a>], and
[<a href="#ref-XMPP-CORE" title=""Extensible Messaging and Presence Protocol (XMPP): Core"">XMPP-CORE</a>].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="#ref-TERMS" title=""Key words for use in RFCs to Indicate Requirement Levels"">TERMS</a>].
<span class="grey">Saint-Andre Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc4622">RFC 4622</a> XMPP IRIs/URIs July 2006</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Use of XMPP IRIs and URIs</span>
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Rationale</span>
As described in [<a href="#ref-XMPP-IM" title=""Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence"">XMPP-IM</a>], instant messaging and presence
applications of XMPP must handle im: and pres: URIs (as specified by
[<a href="#ref-CPIM" title=""Common Profile for Instant Messaging (CPIM)"">CPIM</a>] and [<a href="#ref-CPP" title=""Common Profile for Presence (CPP)"">CPP</a>]). However, there are many other applications of
XMPP (including network management, workflow systems, generic
publish-subscribe, remote procedure calls, content syndication,
gaming, and middleware), and these applications do not implement
instant messaging and presence semantics. Neither does a generic
XMPP entity implement the semantics of any existing URI scheme, such
as the http:, ftp:, or mailto: scheme. Therefore, it is appropriate
to define a new URI scheme that makes it possible to identify or
interact with any XMPP entity (not just instant messaging and
presence entities) as an IRI or URI.
XMPP IRIs and URIs are defined for use by non-native interfaces and
applications, and primarily for the purpose of identification rather
than of interaction (on the latter distinction, see Section 1.2.2 of
[<a href="#ref-URI" title=""Uniform Resource Identifier (URI): Generic Syntax"">URI</a>]). In order to ensure interoperability on XMPP networks, when
data is routed to an XMPP entity (e.g., when an XMPP address is
contained in the 'to' or 'from' attribute of an XML stanza) or an
XMPP entity is otherwise identified in standard XMPP protocol
elements, the entity MUST be addressed as <[node@]domain[/resource]>
(i.e., without a prepended scheme), where the "node identifier",
"domain identifier", and "resource identifier" portions of an XMPP
address conform to the definitions provided in Section 3 of
[<a href="#ref-XMPP-CORE" title=""Extensible Messaging and Presence Protocol (XMPP): Core"">XMPP-CORE</a>].
(Note: For historical reasons, the term "resource identifier" is used
in XMPP to refer to the optional portion of an XMPP address that
follows the domain identifier and the "/" separator character (for
details, refer to Section 3.4 of [<a href="#ref-XMPP-CORE" title=""Extensible Messaging and Presence Protocol (XMPP): Core"">XMPP-CORE</a>]; this use of the term
"resource identifier" is not to be confused with the meanings of
"resource" and "identifier" provided in Section 1.1 of [<a href="#ref-URI" title=""Uniform Resource Identifier (URI): Generic Syntax"">URI</a>]).
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Form</span>
As described in [<a href="#ref-XMPP-CORE" title=""Extensible Messaging and Presence Protocol (XMPP): Core"">XMPP-CORE</a>], an XMPP address used natively on an XMPP
network is a string of Unicode characters that (1) conforms to a
certain set of [<a href="#ref-STRINGPREP" title=""Preparation of Internationalized Strings ("">STRINGPREP</a>] profiles and [<a href="#ref-IDNA" title=""Internationalizing Domain Names in Applications (IDNA)"">IDNA</a>] restrictions, (2)
follows a certain set of syntax rules, and (3) is encoded as [<a href="#ref-UTF-8" title=""UTF-8, a transformation format of ISO 10646"">UTF-8</a>].
The form of such an address can be represented using Augmented
Backus-Naur Form ([<a href="#ref-ABNF" title=""Augmented BNF for Syntax Specifications: ABNF"">ABNF</a>]) as:
[ node "@" ] domain [ "/" resource ]
<span class="grey">Saint-Andre Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc4622">RFC 4622</a> XMPP IRIs/URIs July 2006</span>
In this context, the "node" and "resource" rules rely on distinct
profiles of [<a href="#ref-STRINGPREP" title=""Preparation of Internationalized Strings ("">STRINGPREP</a>], and the "domain" rule relies on the concept
of an internationalized domain name as described in [<a href="#ref-IDNA" title=""Internationalizing Domain Names in Applications (IDNA)"">IDNA</a>]. (Note:
There is no need to refer to punycode in the IRI syntax itself, since
any punycode representation would occur only inside an XMPP
application in order to represent internationalized domain names.
However, it is the responsibility of the processing application to
convert [<a href="#ref-IRI" title=""Internationalized Resource Identifiers (IRIs)"">IRI</a>] syntax into [<a href="#ref-IDNA" title=""Internationalizing Domain Names in Applications (IDNA)"">IDNA</a>] syntax before addressing XML stanzas
to the specified entity on an XMPP network.)
Naturally, in order to be converted into an IRI or URI, an XMPP
address must be prepended with a scheme (specifically, the xmpp
scheme) and may also need to undergo transformations that adhere to
the rules defined in [<a href="#ref-IRI" title=""Internationalized Resource Identifiers (IRIs)"">IRI</a>] and [<a href="#ref-URI" title=""Uniform Resource Identifier (URI): Generic Syntax"">URI</a>]. Furthermore, in order to
enable more advanced interaction with an XMPP entity rather than
simple identification, it is desirable to take advantage of
additional aspects of URI syntax and semantics, such as authority
components, query components, and fragment identifier components.
Therefore, the ABNF syntax for an XMPP IRI is defined as shown below
using Augmented Backus-Naur Form specified by [<a href="#ref-ABNF" title=""Augmented BNF for Syntax Specifications: ABNF"">ABNF</a>], where the
"ifragment", "ihost", and "iunreserved" rules are defined in [<a href="#ref-IRI" title=""Internationalized Resource Identifiers (IRIs)"">IRI</a>],
the "pct-encoded" rule is defined in [<a href="#ref-URI" title=""Uniform Resource Identifier (URI): Generic Syntax"">URI</a>], and DQUOTE is defined in
[<a href="#ref-ABNF" title=""Augmented BNF for Syntax Specifications: ABNF"">ABNF</a>]:
xmppiri = "xmpp" ":" ihierxmpp
[ "?" iquerycomp ]
[ "#" ifragment ]
ihierxmpp = iauthpath / ipathxmpp
iauthpath = "//" iauthxmpp [ "/" ipathxmpp ]
iauthxmpp = inodeid "@" ihost
ipathxmpp = [ inodeid "@" ] ihost [ "/" iresid ]
inodeid = *( iunreserved / pct-encoded / nodeallow )
nodeallow = "!" / "$" / "(" / ")" / "*" / "+" / "," / ";" /
"=" / "[" / "\" / "]" / "^" / "`" / "{" / "|" /
"}"
iresid = *( iunreserved / pct-encoded / resallow )
resallow = "!" / DQUOTE / "$" / "&" / "'" / "(" / ")" /
"*" / "+" / "," / ":" / ";" / "<" / "=" / ">" /
"[" / "\" / "]" / "^" / "`" / "{" / "|" / "}"
iquerycomp = iquerytype [ *ipair ]
iquerytype = *iunreserved
ipair = ";" ikey "=" ivalue
ikey = *iunreserved
ivalue = *( iunreserved / pct-encoded )
<span class="grey">Saint-Andre Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc4622">RFC 4622</a> XMPP IRIs/URIs July 2006</span>
However, the foregoing syntax is not appropriate for inclusion in the
registration of the xmpp URI scheme, since the IANA recognizes only
URI schemes and not IRI schemes. Therefore, the ABNF syntax for an
XMPP URI rather than for IRI is defined as shown in <a href="#section-3.3">Section 3.3</a> of
this document (see below under "IANA Registration"). If it is
necessary to convert the IRI syntax into URI syntax, an application
MUST adhere to the mapping procedure specified in Section 3.1 of
[<a href="#ref-IRI" title=""Internationalized Resource Identifiers (IRIs)"">IRI</a>].
The following is an example of a basic XMPP IRI/URI used for purposes
of identifying a node associated with an XMPP server:
xmpp:node@example.com
Descriptions of the various components of an XMPP IRI/URI are
provided in the following sections.
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Authority Component</span>
As explained in <a href="#section-2.8">Section 2.8</a> of this document, in the absence of an
authority component, the processing application would authenticate as
a configured user at a configured XMPP server. That is, the
authority component section is unnecessary and should be ignored if
the processing application has been configured with a set of default
credentials.
In accordance with <a href="./rfc3986#section-3.2">Section 3.2 of RFC 3986</a>, the authority component
is preceded by a double slash ("//") and is terminated by the next
slash ("/"), question mark ("?"), or number sign ("#") character, or
by the end of the IRI/URI. As explained more fully in <a href="#section-2.8.1">Section 2.8.1</a>
of this document, the presence of an authority component signals the
processing application to authenticate as the node@domain specified
in the authority component rather than as a configured node@domain
(see the Security Considerations section of this document regarding
authentication). (While it is unlikely that the authority component
will be included in most XMPP IRIs or URIs, the scheme allows for its
inclusion, if appropriate.) Thus, the following XMPP IRI/URI
indicates to authenticate as "guest@example.com":
xmpp://guest@example.com
Note well that this is quite different from the following XMPP
IRI/URI, which identifies a node "guest@example.com" but does not
signal the processing application to authenticate as that node:
xmpp:guest@example.com
<span class="grey">Saint-Andre Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc4622">RFC 4622</a> XMPP IRIs/URIs July 2006</span>
Similarly, using a possible query component of "?message" to trigger
an interface for sending a message, the following XMPP IRI/URI
signals the processing application to authenticate as
"guest@example.com" and to send a message to "support@example.com":
xmpp://guest@example.com/support@example.com?message
By contrast, the following XMPP IRI/URI signals the processing
application to authenticate as its configured default account and to
send a message to "support@example.com":
xmpp:support@example.com?message
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Path Component</span>
The path component of an XMPP IRI/URI identifies an XMPP address or
specifies the XMPP address to which an XML stanza shall be directed
at the end of IRI/URI processing.
For example, the following XMPP IRI/URI identifies a node associated
with an XMPP server:
xmpp:example-node@example.com
The following XMPP IRI/URI identifies a node associated with an XMPP
server along with a particular XMPP resource identifier associated
with that node:
xmpp:example-node@example.com/some-resource
Inclusion of a node is optional in XMPP addresses, so the following
XMPP IRI/URI simply identifies an XMPP server:
xmpp:example.com
<span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Query Component</span>
There are many potential use cases for encapsulating information in
the query component of an XMPP IRI/URI; examples include but are not
limited to:
o sending an XMPP message stanza (see [<a href="#ref-XMPP-IM" title=""Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence"">XMPP-IM</a>]),
o adding a roster item (see [<a href="#ref-XMPP-IM" title=""Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence"">XMPP-IM</a>]),
o sending a presence subscription (see [<a href="#ref-XMPP-IM" title=""Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence"">XMPP-IM</a>]),
o probing for current presence information (see [<a href="#ref-XMPP-IM" title=""Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence"">XMPP-IM</a>]),
<span class="grey">Saint-Andre Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc4622">RFC 4622</a> XMPP IRIs/URIs July 2006</span>
o triggering a remote procedure call (see [<a href="#ref-JEP-0009" title=""Jabber-RPC"">JEP-0009</a>]),
o discovering the identity or capabilities of another entity (see
[<a href="#ref-JEP-0030" title=""Service Discovery"">JEP-0030</a>]),
o joining an XMPP-based text chat room (see [<a href="#ref-JEP-0045" title=""Multi-User Chat"">JEP-0045</a>]),
o interacting with publish-subscribe channels (see [<a href="#ref-JEP-0060" title=""Publish-Subscribe"">JEP-0060</a>]),
o providing a SOAP interface (see [<a href="#ref-JEP-0072" title=""SOAP Over XMPP"">JEP-0072</a>]), and
o registering with another entity (see [<a href="#ref-JEP-0077" title=""In-Band Registration"">JEP-0077</a>]).
Many of these potential use cases are application specific, and the
full range of such applications cannot be foreseen in advance given
the continued expansion in XMPP development; however, there is
agreement within the Jabber/XMPP developer community that all the
uses envisioned to date can be encapsulated via a "query type",
optionally supplemented by one or more "key-value" pairs (this is
similar to the "application/x-www-form-urlencoded" MIME type
described in [<a href="#ref-HTML" title=""HTML 4.0 Specification"">HTML</a>]).
As an example, an XMPP IRI/URI intended to launch an interface for
sending a message to the XMPP entity "example-node@example.com" might
be represented as follows:
xmpp:example-node@example.com?message
Similarly, an XMPP IRI/URI intended to launch an interface for
sending a message to the XMPP entity "example-node@example.com" with
a particular subject might be represented as follows:
xmpp:example-node@example.com?message;subject=Hello%20World
If the processing application does not understand query components or
the specified query type, it MUST ignore the query component and
treat the IRI/URI as consisting of, for example,
<xmpp:example-node@example.com> rather than
<xmpp:example-node@example.com?query>. If the processing application
does not understand a particular key within the query component, it
MUST ignore that key and its associated value.
As noted, there exist many kinds of XMPP applications (both actual
and potential), and such applications may define query types and keys
for use in the query component portion of XMPP URIs. The Jabber
Registrar function (see [<a href="#ref-JEP-0053" title=""Jabber Registrar"">JEP-0053</a>]) of the Jabber Software Foundation
maintains a registry of such query types and keys at
<<a href="http://www.jabber.org/registrar/querytypes.html">http://www.jabber.org/registrar/querytypes.html</a>>. To help ensure
<span class="grey">Saint-Andre Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc4622">RFC 4622</a> XMPP IRIs/URIs July 2006</span>
interoperability, any application using the formats defined in this
document SHOULD submit any associated query types and keys to that
registry in accordance with the procedures specified in [<a href="#ref-JEP-0147" title=""XMPP IRI/URI Query Components"">JEP-0147</a>].
<span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a>. Fragment Identifier Component</span>
As stated in Section 3.5 of [<a href="#ref-URI" title=""Uniform Resource Identifier (URI): Generic Syntax"">URI</a>], "The fragment identifier component
of a URI allows indirect identification of a secondary resource by
reference to a primary resource and additional identifying
information." Because the resource identified by an XMPP IRI/URI
does not make available any media type (see [<a href="#ref-MIME" title=""Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types"">MIME</a>]) and therefore (in
the terminology of [<a href="#ref-URI" title=""Uniform Resource Identifier (URI): Generic Syntax"">URI</a>]) no representation exists at an XMPP
resource, the semantics of the fragment identifier component in XMPP
IRIs/URIs are to be "considered unknown and, effectively,
unconstrained" (ibid.). Particular XMPP applications MAY make use of
the fragment identifier component for their own purposes. However,
if a processing application does not understand fragment identifier
components or the syntax of a particular fragment identifier
component included in an XMPP IRI/URI, it MUST ignore the fragment
identifier component.
<span class="h3"><a class="selflink" id="section-2.7" href="#section-2.7">2.7</a>. Generation of XMPP IRIs/URIs</span>
<span class="h4"><a class="selflink" id="section-2.7.1" href="#section-2.7.1">2.7.1</a>. Generation Method</span>
In order to form an XMPP IRI from an XMPP node identifier, domain
identifier, and resource identifier, the generating application MUST
first ensure that the XMPP address conforms to the rules specified in
[<a href="#ref-XMPP-CORE" title=""Extensible Messaging and Presence Protocol (XMPP): Core"">XMPP-CORE</a>], including application of the relevant [<a href="#ref-STRINGPREP" title=""Preparation of Internationalized Strings ("">STRINGPREP</a>]; it
MUST then concatenate the following:
1. The "xmpp" scheme and the ":" character
2. Optionally (if an authority component is to be included before
the node identifier), the characters "//", an authority component
of the form node@domain, and the character "/".
3. Optionally (if the XMPP address contained an XMPP "node
identifier"), a string of Unicode characters that conforms to the
"inodeid" rule, followed by the "@" character.
4. A string of Unicode characters that conforms to the "ihost" rule.
5. Optionally (if the XMPP address contained an XMPP "resource
identifier"), the character "/" and a string of Unicode
characters that conforms to the "iresid" rule.
<span class="grey">Saint-Andre Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc4622">RFC 4622</a> XMPP IRIs/URIs July 2006</span>
6. Optionally (if a query component is to be included), the "?"
character and query component.
7. Optionally (if a fragment identifier component is to be
included), the "#" character and fragment identifier component.
In order to form an XMPP URI from the resulting IRI, an application
MUST adhere to the mapping procedure specified in Section 3.1 of
[<a href="#ref-IRI" title=""Internationalized Resource Identifiers (IRIs)"">IRI</a>].
<span class="h4"><a class="selflink" id="section-2.7.2" href="#section-2.7.2">2.7.2</a>. Generation Notes</span>
Certain characters are allowed in the node identifier, domain
identifier, and resource identifier portions of a native XMPP address
but prohibited by the "inodeid", "ihost", and "iresid" rules of an
XMPP IRI. Specifically, the "#" and "?" characters are allowed in
node identifiers, and the "/", "?", "#", and "@" characters are
allowed in resource identifiers, but these characters are used as
delimiters in XMPP IRIs. In addition, the " " ([<a href="#ref-US-ASCII" title=""Coded Character Set - 7-bit American Standard Code for Information Interchange"">US-ASCII</a>] space)
character is allowed in resource identifiers but prohibited in IRIs.
Therefore, all the foregoing characters MUST be percent-encoded when
transforming an XMPP address into an XMPP IRI.
Consider the following nasty node in an XMPP address:
nasty!#$%()*+,-.;=?[\]^_`{|}~node@example.com
That address would be transformed into the following XMPP IRI:
xmpp:nasty!%23$%25()*+,-.;=%3F[\]^_`{|}~node@example.com
Consider the following repulsive resource in an XMPP address (split
into two lines for layout purposes):
node@example.com
/repulsive !#"$%&'()*+,-./:;<=>?@[\]^_`{|}~resource
That address would be transformed into the following XMPP IRI (split
into two lines for layout purposes):
xmpp:node@example.com
/repulsive%20!%23"$%25&'()*+,-.%2F:;<=>%3F%40[\]^_`{|}~resource
Furthermore, virtually any character outside the [<a href="#ref-US-ASCII" title=""Coded Character Set - 7-bit American Standard Code for Information Interchange"">US-ASCII</a>] range is
allowed in an XMPP address and therefore also in an XMPP IRI, but URI
syntax forbids such characters directly and specifies that such
characters MUST be percent-encoded. In order to determine the URI
associated
<span class="grey">Saint-Andre Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc4622">RFC 4622</a> XMPP IRIs/URIs July 2006</span>
with an XMPP IRI, an application MUST adhere to the mapping procedure
specified in Section 3.1 of [<a href="#ref-IRI" title=""Internationalized Resource Identifiers (IRIs)"">IRI</a>].
<span class="h4"><a class="selflink" id="section-2.7.3" href="#section-2.7.3">2.7.3</a>. Generation Example</span>
Consider the following XMPP address:
<ji&#x159;i@&#x10D;echy.example/v Praze>
Note: The string "&#x159;" stands for the Unicode character LATIN
SMALL LETTER R WITH CARON, and the string "&#x10D;" stands for the
Unicode character LATIN SMALL LETTER C WITH CARON, following the "XML
Notation" used in [<a href="#ref-IRI" title=""Internationalized Resource Identifiers (IRIs)"">IRI</a>] to represent characters that cannot be
rendered in ASCII-only documents (note also that these characters are
represented in their stringprep canonical form). The '<' and '>'
characters are not part of the address itself but are provided to set
off the address for legibility. For those who do not read Czech,
this example could be Anglicized as "george@czech-lands.example/In
Prague".
In accordance with the process specified above, the generating
application would do the following to generate a valid XMPP IRI from
this address:
1. Ensure that the XMPP address conforms to the rules specified in
[<a href="#ref-XMPP-CORE" title=""Extensible Messaging and Presence Protocol (XMPP): Core"">XMPP-CORE</a>], including application of the relevant [<a href="#ref-STRINGPREP" title=""Preparation of Internationalized Strings ("">STRINGPREP</a>]
profiles and encoding as a [<a href="#ref-UTF-8" title=""UTF-8, a transformation format of ISO 10646"">UTF-8</a>] string.
2. Concatenate the following:
1. The "xmpp" scheme and the ":" character.
2. An "authority component" if included (not shown in this
example).
3. A string of Unicode characters that represents the XMPP
address, transformed in accordance with the "inodeid",
"ihost", and "iresid" rules.
4. The "?" character followed by a "query component", if
appropriate to the application (not shown in this example).
5. The "#" character followed by a "fragment identifier
component", if appropriate to the application (not shown in
this example).
<span class="grey">Saint-Andre Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc4622">RFC 4622</a> XMPP IRIs/URIs July 2006</span>
The result is this XMPP IRI:
<xmpp:ji&#x159;i@&#x10D;echy.example/v%20Praze>
In order to generate a valid XMPP URI from the foregoing IRI, the
application MUST adhere to the procedure specified in Section 3.1 of
[<a href="#ref-IRI" title=""Internationalized Resource Identifiers (IRIs)"">IRI</a>], resulting in the following URI:
<xmpp:ji%C5%99i@%C4%8Dechy.example/v%20Praze>
<span class="h3"><a class="selflink" id="section-2.8" href="#section-2.8">2.8</a>. Processing of XMPP IRIs/URIs</span>
<span class="h4"><a class="selflink" id="section-2.8.1" href="#section-2.8.1">2.8.1</a>. Processing Method</span>
If a processing application is presented with an XMPP URI and not
with an XMPP IRI, it MUST first convert the URI into an IRI by
following the procedure specified in Section 3.2 of [<a href="#ref-IRI" title=""Internationalized Resource Identifiers (IRIs)"">IRI</a>].
In order to decompose an XMPP IRI for interaction with the entity it
identifies, a processing application MUST separate:
1. The "xmpp" scheme and the ":" character.
2. The authority component, if included (the string of Unicode
characters between the "//" characters and the next "/"
character, the "?" character, the "#" character, or the end of
the IRI).
3. A string of Unicode characters that represents an XMPP address as
transformed in accordance with the "inodeid", "ihost", and
"iresid" rules.
4. Optionally the query component, if included, using the "?"
character as a separator.
5. Optionally the fragment identifier component, if included, using
the "#" character as a separator.
At this point, the processing application MUST ensure that the
resulting XMPP address conforms to the rules specified in
[<a href="#ref-XMPP-CORE" title=""Extensible Messaging and Presence Protocol (XMPP): Core"">XMPP-CORE</a>], including application of the relevant [<a href="#ref-STRINGPREP" title=""Preparation of Internationalized Strings ("">STRINGPREP</a>]. The
processing application then would either (1) complete further XMPP
handling itself or (2) invoke a helper application to complete XMPP
handling; such XMPP handling would most likely consist of the
following steps:
<span class="grey">Saint-Andre Standards Track [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc4622">RFC 4622</a> XMPP IRIs/URIs July 2006</span>
1. If not already connected to an XMPP server, connect either as the
user specified in the authority component or as the configured
user at the configured XMPP server, normally by adhering to the
XMPP connection procedures defined in [<a href="#ref-XMPP-CORE" title=""Extensible Messaging and Presence Protocol (XMPP): Core"">XMPP-CORE</a>]. (Note: The
processing application SHOULD ignore the authority component if
it has been configured with a set of default credentials.)
2. Optionally, determine the nature of the intended recipient (e.g.,
via [<a href="#ref-JEP-0030" title=""Service Discovery"">JEP-0030</a>]).
3. Optionally, present an appropriate interface to a user based on
the nature of the intended recipient and/or the contents of the
query component.
4. Generate an XMPP stanza that translates any user or application
inputs into their corresponding XMPP equivalents.
5. Send the XMPP stanza via the authenticated server connection for
delivery to the intended recipient.
<span class="h4"><a class="selflink" id="section-2.8.2" href="#section-2.8.2">2.8.2</a>. Processing Notes</span>
It may help implementors to note that the first two steps of "further
XMPP handling", as described at the end of <a href="#section-2.8.1">Section 2.8.1</a>, are similar
to HTTP authentication ([<a href="#ref-HTTP-AUTH" title=""HTTP Authentication: Basic and Digest Access Authentication"">HTTP-AUTH</a>]), while the next three steps are
similar to the handling of mailto: URIs ([<a href="#ref-MAILTO" title=""The mailto URL scheme"">MAILTO</a>]).
As noted in <a href="#section-2.7.2">Section 2.7.2</a> of this document, certain characters are
allowed in the node identifier, domain identifier, and resource
identifier portions of a native XMPP address but prohibited by the
"inodeid", "ihost", and "iresid" rules of an XMPP IRI. The
percent-encoded octets corresponding to these characters in XMPP IRIs
MUST be transformed into the characters allowed in XMPP addresses
when processing an XMPP IRI for interaction with the represented XMPP
entity.
Consider the following nasty node in an XMPP IRI:
xmpp:nasty!%23$%()*+,-.;=%3F[\]^_`{|}~node@example.com
That IRI would be transformed into the following XMPP address:
nasty!#$%()*+,-.;=?[\]^_`{|}~node@example.com
<span class="grey">Saint-Andre Standards Track [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc4622">RFC 4622</a> XMPP IRIs/URIs July 2006</span>
Consider the following repulsive resource in an XMPP IRI (split into
two lines for layout purposes):
xmpp:node@example.com
/repulsive%20!%23"$%25&'()*+,-.%2F:;<=>%3F%40[\]^_`{|}~resource
That IRI would be transformed into the following XMPP address (split
into two lines for layout purposes):
node@example.com
/repulsive !#"$%&'()*+,-./:;<=>?@[\]^_`{|}~resource
<span class="h4"><a class="selflink" id="section-2.8.3" href="#section-2.8.3">2.8.3</a>. Processing Example</span>
Consider the XMPP URI that resulted from the previous example:
<xmpp:ji%C5%99i@%C4%8Dechy.example/v%20Praze>
In order to generate a valid XMPP IRI from that URI, the application
MUST adhere to the procedure specified in Section 3.2 of [<a href="#ref-IRI" title=""Internationalized Resource Identifiers (IRIs)"">IRI</a>],
resulting in the following IRI:
<xmpp:ji&#x159;i@&#x10D;echy.example/v%20Praze>
In accordance with the process specified above, the processing
application would remove the "xmpp" scheme and ":" character to
extract the XMPP address from this XMPP IRI, converting any
percent-encoded octets from the "inodeid", "ihost", and "iresid"
rules into their character equivalents (e.g., "%20" into the space
character).
The result is this XMPP address:
<ji&#x159;i@&#x10D;echy.example/v Praze>
<span class="h3"><a class="selflink" id="section-2.9" href="#section-2.9">2.9</a>. Internationalization</span>
Because XMPP addresses are [<a href="#ref-UTF-8" title=""UTF-8, a transformation format of ISO 10646"">UTF-8</a>] strings and because octets outside
the [<a href="#ref-US-ASCII" title=""Coded Character Set - 7-bit American Standard Code for Information Interchange"">US-ASCII</a>] range within XMPP addresses can be easily converted to
percent-encoded octets, XMPP addresses are designed to work well with
Internationalized Resource Identifiers ([<a href="#ref-IRI" title=""Internationalized Resource Identifiers (IRIs)"">IRI</a>]). In particular, with
the exceptions of stringprep verification, the conversion of
syntax-relevant [<a href="#ref-US-ASCII" title=""Coded Character Set - 7-bit American Standard Code for Information Interchange"">US-ASCII</a>] characters (e.g., "?"), and the conversion
of percent-encoded octets from the "inodeid", "ihost", and "iresid"
rules into their character equivalents (e.g., "%20" into the
[<a href="#ref-US-ASCII" title=""Coded Character Set - 7-bit American Standard Code for Information Interchange"">US-ASCII</a>] space character), an XMPP IRI can be constructed directly
by prepending the "xmpp" scheme and ":" character to an XMPP address.
Furthermore, an XMPP IRI can be converted into URI syntax by adhering
<span class="grey">Saint-Andre Standards Track [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc4622">RFC 4622</a> XMPP IRIs/URIs July 2006</span>
to the procedure specified in Section 3.1 of [<a href="#ref-IRI" title=""Internationalized Resource Identifiers (IRIs)"">IRI</a>], and an XMPP URI
can be converted into IRI syntax by adhering to the procedure
specified in Section 3.2 of [<a href="#ref-IRI" title=""Internationalized Resource Identifiers (IRIs)"">IRI</a>], thus ensuring interoperability
with applications that are able to process URIs but unable to process
IRIs.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IANA Registration of xmpp URI Scheme</span>
In accordance with [<a href="#ref-URI-SCHEMES" title=""Guidelines and Registration Procedures for New URI Schemes"">URI-SCHEMES</a>], this section provides the
information required to register the xmpp URI scheme.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. URI Scheme Name</span>
xmpp
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Status</span>
permanent
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. URI Scheme Syntax</span>
The syntax for an xmpp URI is defined below using Augmented
Backus-Naur Form as specified by [<a href="#ref-ABNF" title=""Augmented BNF for Syntax Specifications: ABNF"">ABNF</a>], where the "fragment",
"host", "pct-encoded", and "unreserved" rules are defined in [<a href="#ref-URI" title=""Uniform Resource Identifier (URI): Generic Syntax"">URI</a>]
and DQUOTE is defined in [<a href="#ref-ABNF" title=""Augmented BNF for Syntax Specifications: ABNF"">ABNF</a>]:
xmppuri = "xmpp" ":" hierxmpp [ "?" querycomp ] [ "#" fragment ]
hierxmpp = authpath / pathxmpp
authpath = "//" authxmpp [ "/" pathxmpp ]
authxmpp = nodeid "@" host
pathxmpp = [ nodeid "@" ] host [ "/" resid ]
nodeid = *( unreserved / pct-encoded / nodeallow )
nodeallow = "!" / "$" / "(" / ")" / "*" / "+" / "," / ";" /
"=" / "[" / "\" / "]" / "^" / "`" / "{" / "|" /
"}"
resid = *( unreserved / pct-encoded / resallow )
resallow = "!" / DQUOTE / "$" / "&" / "'" / "(" / ")" /
"*" / "+" / "," / ":" / ";" / "<" / "=" / ">" /
"[" / "\" / "]" / "^" / "`" / "{" / "|" / "}"
querycomp = querytype [ *pair ]
querytype = *( unreserved / pct-encoded )
pair = ";" key "=" value
key = *( unreserved / pct-encoded )
value = *( unreserved / pct-encoded )
<span class="grey">Saint-Andre Standards Track [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc4622">RFC 4622</a> XMPP IRIs/URIs July 2006</span>
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. URI Scheme Semantics</span>
The xmpp URI scheme identifies entities that natively communicate
using the Extensible Messaging and Presence Protocol (XMPP), and is
mainly used for identification rather than for resource location.
However, if an application that processes an xmpp URI enables
interaction with the XMPP address identified by the URI, it MUST
follow the methodology defined in <a href="./rfc4622#section-2">Section 2 of RFC 4622</a>, Use of XMPP
IRIs and URIs, to reconstruct the encapsulated XMPP address, connect
to an appropriate XMPP server, and send an appropriate XMPP "stanza"
(XML fragment) to the XMPP address. (Note: There is no MIME type
associated with the xmpp URI scheme.)
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. Encoding Considerations</span>
In addition to XMPP URIs, there will also be XMPP Internationalized
Resource Identifiers (IRIs). Prior to converting an Extensible
Messaging and Presence Protocol (XMPP) address into an IRI (and in
accordance with [<a href="#ref-XMPP-CORE" title=""Extensible Messaging and Presence Protocol (XMPP): Core"">XMPP-CORE</a>]), the XMPP address must be represented as
[<a href="#ref-UTF-8" title=""UTF-8, a transformation format of ISO 10646"">UTF-8</a>] by the generating application (e.g., by transforming an
application's internal representation of the address as a UTF-16
string into a UTF-8 string), and the UTF-8 string must then be
prepended with the "xmpp" scheme and ":" character. However, because
an XMPP URI must contain only [<a href="#ref-US-ASCII" title=""Coded Character Set - 7-bit American Standard Code for Information Interchange"">US-ASCII</a>] characters, the UTF-8 string
of an XMPP IRI must be transformed into URI syntax by adhering to the
procedure specified in <a href="./rfc3987">RFC 3987</a>.
<span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>. Applications/protocols That Use This URI Scheme Name</span>
The xmpp URI scheme is intended to be used by interfaces to an XMPP
network from non-native user agents, such as web browsers, as well as
by non-native applications that need to identify XMPP entities as
full URIs or IRIs.
<span class="h3"><a class="selflink" id="section-3.7" href="#section-3.7">3.7</a>. Interoperability Considerations</span>
There are no known interoperability concerns related to use of the
xmpp URI scheme. In order to help ensure interoperability, the
Jabber Registrar function of the Jabber Software Foundation maintains
a registry of query types and keys that can be used in the query
components of XMPP URIs and IRIs, located at
<<a href="http://www.jabber.org/registrar/querytypes.html">http://www.jabber.org/registrar/querytypes.html</a>>.
<span class="h3"><a class="selflink" id="section-3.8" href="#section-3.8">3.8</a>. Security Considerations</span>
See <a href="./rfc4622#section-5">Section 5 of RFC 4622</a>, Security Considerations.
<span class="grey">Saint-Andre Standards Track [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc4622">RFC 4622</a> XMPP IRIs/URIs July 2006</span>
<span class="h3"><a class="selflink" id="section-3.9" href="#section-3.9">3.9</a>. Contact</span>
Peter Saint-Andre [mailto:stpeter@jabber.org,
xmpp:stpeter@jabber.org]
<span class="h3"><a class="selflink" id="section-3.10" href="#section-3.10">3.10</a>. Author/Change Controller</span>
This scheme is registered under the IETF tree. As such, the IETF
maintains change control.
<span class="h3"><a class="selflink" id="section-3.11" href="#section-3.11">3.11</a>. References</span>
[<a id="ref-XMPP-CORE">XMPP-CORE</a>]
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Considerations</span>
This document registers a URI scheme. The registration template can
be found in <a href="#section-3">Section 3</a> of this document. In order to help ensure
interoperability, the Jabber Registrar function of the Jabber
Software Foundation maintains a registry of query types and keys that
can be used in the query components of XMPP URIs and IRIs, located at
<<a href="http://www.jabber.org/registrar/querytypes.html">http://www.jabber.org/registrar/querytypes.html</a>>.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
Providing an interface to XMPP services from non-native applications
introduces new security concerns. The security considerations
discussed in [<a href="#ref-IRI" title=""Internationalized Resource Identifiers (IRIs)"">IRI</a>], [<a href="#ref-URI" title=""Uniform Resource Identifier (URI): Generic Syntax"">URI</a>], and [<a href="#ref-XMPP-CORE" title=""Extensible Messaging and Presence Protocol (XMPP): Core"">XMPP-CORE</a>] apply to XMPP IRIs, and
the security considerations discussed in [<a href="#ref-URI" title=""Uniform Resource Identifier (URI): Generic Syntax"">URI</a>] and [<a href="#ref-XMPP-CORE" title=""Extensible Messaging and Presence Protocol (XMPP): Core"">XMPP-CORE</a>] apply
to XMPP URIs. In accordance with Section 2.7 of [<a href="#ref-URI-SCHEMES" title=""Guidelines and Registration Procedures for New URI Schemes"">URI-SCHEMES</a>] and
Section 7 of [<a href="#ref-URI" title=""Uniform Resource Identifier (URI): Generic Syntax"">URI</a>], particular security considerations are specified
in the following sections.
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Reliability and Consistency</span>
Given that XMPP addresses of the form node@domain.tld are typically
created via registration at an XMPP server or provisioned by an
administrator of such a server, it is possible that such addresses
may also be unregistered or deprovisioned. Therefore, the XMPP
IRI/URI that identifies such an XMPP address may not be reliably and
consistently associated with the same principal, account owner,
application, or device.
XMPP addresses of the form node@domain.tld/resource are typically
even more ephemeral (since a given XMPP resource identifier is
typically associated with a particular, temporary session of an XMPP
client at an XMPP server); therefore the XMPP IRI/URI that identifies
such an XMPP address probably will not reliably and consistently be
<span class="grey">Saint-Andre Standards Track [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc4622">RFC 4622</a> XMPP IRIs/URIs July 2006</span>
associated with the same session. However, the procedures specified
in Section 10 of [<a href="#ref-XMPP-CORE" title=""Extensible Messaging and Presence Protocol (XMPP): Core"">XMPP-CORE</a>] effectively eliminate any potential
confusion that might be introduced by the lack of reliability and
consistency for the XMPP IRI/URI that identifies such an XMPP
address.
XMPP addresses of the form domain.tld are typically long-lived XMPP
servers or associated services; although naturally it is possible for
server or service administrators to de-commission the server or
service at any time, typically the IRIs/URIs that identify such
servers or services are the most reliable and consistent of XMPP
IRIs/URIs.
XMPP addresses of the form domain.tld/resource are not yet common on
XMPP networks; however, the reliability and consistency of XMPP
IRIs/URIs that identify such XMPP addresses would likely fall
somewhere between those that identify XMPP addresses of the form
domain.tld and those that identify XMPP addresses of the form
node@domain.tld.
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Malicious Construction</span>
Malicious construction of XMPP IRIs/URIs is made less likely by the
prohibition on port numbers in XMPP IRIs/URIs (since port numbers are
to be discovered using [<a href="#ref-DNS-SRV" title=""A DNS RR for specifying the location of services (DNS SRV)"">DNS-SRV</a>] records, as specified in
[<a href="#ref-XMPP-CORE" title=""Extensible Messaging and Presence Protocol (XMPP): Core"">XMPP-CORE</a>]).
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Back-End Transcoding</span>
Because the base XMPP protocol is designed to implement the exchange
of messages and presence information and not the retrieval of files
or invocation of similar system functions, it is deemed unlikely that
the use of XMPP IRIs/URIs would result in harmful dereferencing.
However, if an XMPP protocol extension defines methods for
information retrieval, it MUST define appropriate controls over
access to that information. In addition, XMPP servers SHOULD NOT
natively parse XMPP IRIs/URIs but instead SHOULD accept only the XML
wire protocol specified in [<a href="#ref-XMPP-CORE" title=""Extensible Messaging and Presence Protocol (XMPP): Core"">XMPP-CORE</a>] and any desired extensions
thereto.
<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. Sensitive Information</span>
The ability to interact with XMPP entities via a web browser or other
non-native application may expose sensitive information (such as
support for particular XMPP application protocol extensions) and
thereby make it possible to launch attacks that are not possible or
that are unlikely on a native XMPP network. Due care must be taken
<span class="grey">Saint-Andre Standards Track [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc4622">RFC 4622</a> XMPP IRIs/URIs July 2006</span>
in deciding what information is appropriate for representation in
XMPP IRIs or URIs.
In particular, advertising XMPP IRIs/URIs in publicly accessible
locations (e.g., on websites) may make it easier for malicious users
to harvest XMPP addresses from the authority and path components of
XMPP IRIs/URIs and therefore to send unsolicited bulk communications
to the users or applications represented by those addresses. Due
care should be taken in balancing the benefits of open information
exchange against the potential costs of unwanted communications.
To help prevent leaking of sensitive information, passwords and other
user credentials are forbidden in the authority component of XMPP
IRIs/URIs; in fact they are not needed, since the fact that
authentication in XMPP occurs via [<a href="#ref-SASL" title=""Simple Authentication and Security Layer (SASL)"">SASL</a>] makes it possible to use the
SASL ANONYMOUS mechanism, if desired.
<span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. Semantic Attacks</span>
Despite the existence of non-hierarchical URI schemes such as
[<a href="#ref-MAILTO" title=""The mailto URL scheme"">MAILTO</a>], by association human users may expect all URIs to include
the "//" characters after the scheme name and ":" character.
However, in XMPP IRIs/URIs, the "//" characters precede the authority
component rather than the path component. Thus,
xmpp://guest@example.com indicates to authenticate as
"guest@example.com", whereas xmpp:guest@example.com identifies the
node "guest@example.com". Processing applications MUST clearly
differentiate between these forms, and user agents SHOULD discourage
human users from including the "//" characters in XMPP IRIs/URIs
since use of the authority component is envisioned to be helpful only
in specialized scenarios, not more generally.
<span class="h3"><a class="selflink" id="section-5.6" href="#section-5.6">5.6</a>. Spoofing</span>
The ability to include effectively the full range of Unicode
characters in an XMPP IRI may make it easier to execute certain forms
of address mimicking (also called "spoofing"). However, XMPP IRIs
are no different from other IRIs in this regard, and applications
that will present XMPP IRIs to human users must adhere to best
practices regarding address mimicking in order to help prevent
attacks that result from spoofed addresses (e.g., the phenomenon
known as "phishing"). For details, refer to the Security
Considerations of [<a href="#ref-IRI" title=""Internationalized Resource Identifiers (IRIs)"">IRI</a>].
<span class="grey">Saint-Andre Standards Track [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc4622">RFC 4622</a> XMPP IRIs/URIs July 2006</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
[<a id="ref-ABNF">ABNF</a>] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", <a href="./rfc4234">RFC 4234</a>, October 2005.
[<a id="ref-IRI">IRI</a>] Duerst, M. and M. Suignard, "Internationalized
Resource Identifiers (IRIs)", <a href="./rfc3987">RFC 3987</a>, January 2005.
[<a id="ref-TERMS">TERMS</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-URI">URI</a>] Berners-Lee, T., Fielding, R., and L. Masinter,
"Uniform Resource Identifier (URI): Generic Syntax",
STD 66, <a href="./rfc3986">RFC 3986</a>, January 2005.
[<a id="ref-XMPP-CORE">XMPP-CORE</a>] Saint-Andre, P., "Extensible Messaging and Presence
Protocol (XMPP): Core", <a href="./rfc3920">RFC 3920</a>, October 2004.
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
[<a id="ref-CPIM">CPIM</a>] Peterson, J., "Common Profile for Instant Messaging
(CPIM)", <a href="./rfc3860">RFC 3860</a>, August 2004.
[<a id="ref-CPP">CPP</a>] Peterson, J., "Common Profile for Presence (CPP)",
<a href="./rfc3859">RFC 3859</a>, August 2004.
[<a id="ref-DNS-SRV">DNS-SRV</a>] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR
for specifying the location of services (DNS SRV)",
<a href="./rfc2782">RFC 2782</a>, February 2000.
[<a id="ref-HTML">HTML</a>] Raggett, D., "HTML 4.0 Specification", W3C
REC REC-html40-19980424, April 1998.
[<a id="ref-HTTP-AUTH">HTTP-AUTH</a>] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence,
S., Leach, P., Luotonen, A., and L. Stewart, "HTTP
Authentication: Basic and Digest Access
Authentication", <a href="./rfc2617">RFC 2617</a>, June 1999.
[<a id="ref-IDNA">IDNA</a>] Faltstrom, P., Hoffman, P., and A. Costello,
"Internationalizing Domain Names in Applications
(IDNA)", <a href="./rfc3490">RFC 3490</a>, March 2003.
[<a id="ref-JEP-0009">JEP-0009</a>] Adams, D., "Jabber-RPC", JSF JEP 0009, February 2006.
<span class="grey">Saint-Andre Standards Track [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc4622">RFC 4622</a> XMPP IRIs/URIs July 2006</span>
[<a id="ref-JEP-0030">JEP-0030</a>] Hildebrand, J., Millard, P., Eatmon, R., and P.
Saint-Andre, "Service Discovery", JSF JEP 0030,
January 2006.
[<a id="ref-JEP-0045">JEP-0045</a>] Saint-Andre, P., "Multi-User Chat", JSF JEP 0045,
September 2005.
[<a id="ref-JEP-0053">JEP-0053</a>] Saint-Andre, P., "Jabber Registrar", JSF JEP 0053,
May 2004.
[<a id="ref-JEP-0060">JEP-0060</a>] Millard, P., Saint-Andre, P., and R. Meijer,
"Publish-Subscribe", JSF JEP 0060, June 2005.
[<a id="ref-JEP-0072">JEP-0072</a>] Forno, F. and P. Saint-Andre, "SOAP Over XMPP", JSF
JEP 0072, December 2005.
[<a id="ref-JEP-0077">JEP-0077</a>] Saint-Andre, P., "In-Band Registration", JSF JEP 0077,
January 2006.
[<a id="ref-JEP-0147">JEP-0147</a>] Saint-Andre, P., "XMPP IRI/URI Query Components", JSF
JEP 0147, March 2006.
[<a id="ref-MAILTO">MAILTO</a>] Hoffman, P., Masinter, L., and J. Zawinski, "The
mailto URL scheme", <a href="./rfc2368">RFC 2368</a>, July 1998.
[<a id="ref-MIME">MIME</a>] Freed, N. and N. Borenstein, "Multipurpose Internet
Mail Extensions (MIME) Part Two: Media Types",
<a href="./rfc2046">RFC 2046</a>, November 1996.
[<a id="ref-SASL">SASL</a>] Melnikov, A. and K. Zeilenga, "Simple Authentication
and Security Layer (SASL)", <a href="./rfc4422">RFC 4422</a>, June 2006.
[<a id="ref-STRINGPREP">STRINGPREP</a>] Hoffman, P. and M. Blanchet, "Preparation of
Internationalized Strings ("STRINGPREP")", <a href="./rfc3454">RFC 3454</a>,
December 2002.
[<a id="ref-UNICODE">UNICODE</a>] The Unicode Consortium, "The Unicode Standard, Version
3.2.0", 2000.
The Unicode Standard, Version 3.2.0 is defined by The
Unicode Standard, Version 3.0 (Reading, MA, Addison-
Wesley, 2000. ISBN 0-201-61633-5), as amended by the
Unicode Standard Annex #27: Unicode 3.1
(<a href="http://www.unicode.org/reports/tr27/">http://www.unicode.org/reports/tr27/</a>) and by the
Unicode Standard Annex #28: Unicode 3.2
(<a href="http://www.unicode.org/reports/tr28/">http://www.unicode.org/reports/tr28/</a>).
<span class="grey">Saint-Andre Standards Track [Page 21]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
<span class="grey"><a href="./rfc4622">RFC 4622</a> XMPP IRIs/URIs July 2006</span>
[<a id="ref-URI-SCHEMES">URI-SCHEMES</a>] Hansen, T., Hardie, T., and L. Masinter, "Guidelines
and Registration Procedures for New URI Schemes",
<a href="./rfc4395">RFC 4395</a>, February 2006.
[<a id="ref-US-ASCII">US-ASCII</a>] American National Standards Institute, "Coded
Character Set - 7-bit American Standard Code for
Information Interchange", ANSI X3.4, 1986.
[<a id="ref-UTF-8">UTF-8</a>] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, <a href="./rfc3629">RFC 3629</a>, November 2003.
[<a id="ref-XMPP-IM">XMPP-IM</a>] Saint-Andre, P., "Extensible Messaging and Presence
Protocol (XMPP): Instant Messaging and Presence",
<a href="./rfc3921">RFC 3921</a>, October 2004.
Author's Address
Peter Saint-Andre
Jabber Software Foundation
EMail: stpeter@jabber.org
URI: xmpp:stpeter@jabber.org
<span class="grey">Saint-Andre Standards Track [Page 22]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
<span class="grey"><a href="./rfc4622">RFC 4622</a> XMPP IRIs/URIs July 2006</span>
Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Saint-Andre Standards Track [Page 23]
</pre>
|
