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
|
<pre>Network Working Group W. Harold
Request for Comments: 3529 IBM
Category: Experimental April 2003
<span class="h1">Using Extensible Markup Language-Remote Procedure Calling</span>
<span class="h1">(XML-RPC) in Blocks Extensible Exchange Protocol (BEEP)</span>
Status of this Memo
This memo defines an Experimental Protocol for the Internet
community. It does not specify an Internet standard of any kind.
Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract
XML-RPC is an Extensible Markup Language-Remote Procedure Calling
protocol that works over the Internet. It defines an XML format for
messages that are transfered between clients and servers using HTTP.
An XML-RPC message encodes either a procedure to be invoked by the
server, along with the parameters to use in the invocation, or the
result of an invocation. Procedure parameters and results can be
scalars, numbers, strings, dates, etc.; they can also be complex
record and list structures.
This document specifies a how to use the Blocks Extensible Exchange
Protocol (BEEP) to transfer messages encoded in the XML-RPC format
between clients and servers.
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. BEEP Profile Identification . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2.1">2.1</a> Profile Initialization . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3">3</a>. XML-RPC Message Packages . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-4">4</a>. XML-RPC Message Exchange . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-5">5</a>. URL Schemes . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-5.1">5.1</a> The xmlrpc.beep URL Scheme. . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-5.1.1">5.1.1</a> Resolving IP/TCP Address Information . . . . . . <a href="#page-6">6</a>
<a href="#section-5.2">5.2</a> The xmlrpc.beeps URL Scheme . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-6">6</a>. Initial Registrations . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-6.1">6.1</a> Registration: The XML-RPC Profile . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-6.2">6.2</a> Registration: The xmlrpc.beep URL Scheme. . . . . . . . <a href="#page-9">9</a>
<span class="grey">Harold Experimental [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc3529">RFC 3529</a> Using XML-RPC in BEEP April 2003</span>
<a href="#section-6.3">6.3</a> Registration: The xmlrpc.beeps URL Scheme . . . . . . . <a href="#page-10">10</a>
6.4 Registration: The System (Well-Known) TCP port number
for XML-RPC over BEEP . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-7">7</a>. Security Considerations . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#section-8">8</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
Appendix
<a href="#appendix-A">A</a>. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
<a href="#appendix-B">B</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
Full Copyright Statement . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This memo specifies how messages encoded in the XML-RPC [<a href="#ref-1" title=""XML-RPC Specification"">1</a>] format
are transmitted using a BEEP profile [<a href="#ref-2" title=""The Blocks Extensible Exchange Protocol Core"">2</a>].
Throughout this memo, the terms "request" and "response" refer to the
"methodCall" and "methodResponse" elements defined by the XML-RPC
specification [<a href="#ref-1" title=""XML-RPC Specification"">1</a>]. Further the terms "peer", "client", "server", and
"one-to-one" are used in the context of BEEP. In particular,
Sections <a href="#section-2.1">2.1</a> and <a href="#section-2.1.1">2.1.1</a> of [<a href="#ref-2" title=""The Blocks Extensible Exchange Protocol Core"">2</a>] discuss BEEP roles and exchange styles.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. BEEP Profile Identification</span>
The BEEP profile for XML-RPC is identified as
<a href="http://iana.org/beep/transient/xmlrpc">http://iana.org/beep/transient/xmlrpc</a>
in the BEEP "profile" element during channel creation.
In BEEP, when the first channel is successfully created, the
"serverName" attribute in the "start" element identifies the "virtual
host" associated with the peer acting in the server role, e.g.,
<start number='1' serverName='stateserver.example.com'>
<profile uri='http://iana.org/beep/transient/xmlrpc' />
</start>
The "serverName" attribute is analogous to HTTP's "Host" request-
header field (c.f., Section 14.23 of [<a href="#ref-3" title=""Hypertext Transfer Protocol -- HTTP/1.1"">3</a>]).
<span class="grey">Harold Experimental [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc3529">RFC 3529</a> Using XML-RPC in BEEP April 2003</span>
There are two states in the BEEP profile for XML-RPC, "boot", the
profile's initial state, and "ready":
o In the "boot" state, the peer requesting the creation of the
channel sends a "bootmsg" (either during channel initialization or
in a "MSG" message).
* If the other peer sends a "bootrpy" (either during channel
initialization or in a "RPY" message), then the "ready" state
is entered
* Otherwise, the other peer sends an "error" (either during
channel initialization or in a "ERR" message), and no state
change occurs.
o In the "ready" state, the initiating peer begins an XML-RPC
message pattern by sending a "MSG" message containing a request.
The other peer completes the message pattern by sending back a
"RPY" message containing a response.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a> Profile Initialization</span>
The boot message is used to identify the resource accessed by the
channel bound to the BEEP profile for XML-RPC.
The DTD syntax for the boot message and its response are:
<!ELEMENT bootmsg EMPTY>
<!ATTLIST bootmsg
resource CDATA #REQUIRED>
<!ELEMENT bootrpy EMPTY>
The boot message contains a single mandatory attribute: "resource",
which is analagous to HTTP's "abs_path" Request-URI parameter (c.f.,
Section 5.1.2 of [<a href="#ref-3" title=""Hypertext Transfer Protocol -- HTTP/1.1"">3</a>])
If the peer acting in the server role recognizes the requested
resource, it replies with a boot response. Otherwise, if the boot
message is improperly formed, or if the requested resource isn't
recognized, the peer acting in the server role replies with an error
message (c.f., Section 7.1 of [<a href="#ref-2" title=""The Blocks Extensible Exchange Protocol Core"">2</a>]).
Typically, the boot message and its response are exchanged during
channel initialization (c.f., Section 2.3.1.2 of [<a href="#ref-2" title=""The Blocks Extensible Exchange Protocol Core"">2</a>]).
<span class="grey">Harold Experimental [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc3529">RFC 3529</a> Using XML-RPC in BEEP April 2003</span>
For example, here the boot message and its response are exchanged
during channel initialization:
C: <start number='1' serverName='stateserver.example.com'>
C: <profile uri='http://iana.org/beep/transient/xmlrpc'>
C: <![CDATA[<bootmsg resource='/NumberToName' />]]>
C: </profile>
C: </start>
S: <profile uri='http://iana.org/beep/transient/xmlrpc'>
S: <![CDATA[<bootrpy />]]>
S: </profile>
The channel bound to the BEEP profile for XML-RPC is now in the
"ready" state.
Alternatively, here is an example in which the boot exchange is
unsuccessful:
C: <start number='1' serverName='stateserver.example.com'>
C: <profile uri='http://iana.org/beep/transient/xmlrpc'>
C: <![CDATA[<bootmsg resource='/NameToCapital' />]]>
C: </profile>
C: </start>
S: <profile uri='http://iana.org/beep/transient/xmlrpc'>
S: <![CDATA[<error code='550'>resource not
S: supported</error>]]>
S: </profile>
Although the channel was created successfully, it remains in the
"boot" state.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. XML-RPC Message Packages</span>
The BEEP profile for XML-RPC transmits requests and responses encoded
as UTF-8 using the media type "application/xml" [<a href="#ref-4" title=""XML Media Types"">4</a>], e.g.,
I: MSG 1 1 . 0 364
I: Content-Type: application/xml
I:
I: <?xml version="1.0"?>
I: <methodCall>
I: <methodName>examples.getStateName</methodName>
I: <params>
I: <param>
I: <value><i4>41</i4></value>
I: </param>
<span class="grey">Harold Experimental [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc3529">RFC 3529</a> Using XML-RPC in BEEP April 2003</span>
I: </params>
I: </methodCall>
I: END
and its associated response
L: RPY 1 1 . 201 100
L: Content-Type: application/xml
L:
L: <?xml version="1.0"?>
L: <methodResponse>
L: <params>
L: <param>
L: <value><string>South Dakota</string></value>
L: </param>
L: </params>
L: </methodRespose>
L: END
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. XML-RPC Message Exchange</span>
A request/response exchange involves sending a request, which results
in a response being returned.
The BEEP profile for XML-RPC achieves this using a one-to-one
exchange, in which the client sends a "MSG" message containing an
request, and the server sends back a "RPY" message containing an
response.
The BEEP profile for XML-RPC does not use the "ERR" message for XML-
RPC faults when performing one-to-one exchanges. Whatever response
is generated by the server is always returned in the "RPY" message.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. URL Schemes</span>
This memo defines two URL schemes, "xmlrpc.beep" and "xmlrpc.beeps",
which identify the use of XML-RPC over BEEP over TCP. Note that, at
present, a "generic" URL scheme for XML-RPC is not defined.
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a> The xmlrpc.beep URL Scheme</span>
The "xmlrpc.beep" URL scheme uses the "generic URI" syntax defined in
Section 3 of [<a href="#ref-5" title=""Uniform Resource Identifiers (URI): Generic Syntax"">5</a>], specifically:
o the value "xmlrpc.beep" is used for the scheme component; and,
o the server-based naming authority defined in Section 3.2.2 of [<a href="#ref-5" title=""Uniform Resource Identifiers (URI): Generic Syntax"">5</a>]
is used for the authority component.
<span class="grey">Harold Experimental [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc3529">RFC 3529</a> Using XML-RPC in BEEP April 2003</span>
o the path component maps to the "resource" component of the boot
message sent during profile initialization (if absent, it defaults
to "/").
The values of both the scheme and authority components are case-
insensitive.
For example, the URL
xmlrpc.beep://stateserver.example.com/NumberToName
might result in the example shown in <a href="#section-2.1">Section 2.1</a>.
<span class="h4"><a class="selflink" id="section-5.1.1" href="#section-5.1.1">5.1.1</a> Resolving IP/TCP Address Information</span>
The "xmlrpc.beep" URL scheme indicates the use of the BEEP profile
for XML-RPC running over TCP/IP.
If the authority component contains a domain name and a port number,
e.g.,
xmlrpc.beep://stateserver.example.com:1026
then the DNS is queried for the A RRs corresponding to the domain
name, and the port number is used directly.
If the authority component contains a domain name and no port number,
e.g.,
xmlrpc.beep://stateserver.example.com
the SRV algorithm [<a href="#ref-6" title=""A DNS RR for specifying the location of services (DNS SRV)"">6</a>] is used with a service parameter of "xmlrpc-
beep" and a protocol parameter of "tcp" to determine the IP/TCP
addressing information. If no appropriate SRV RRs are found (e.g.,
for "_xmlrpc-beep._tcp.stateserver.example.com"), then the DNS is
queried for the A RRs corresponding to the domain name and the port
number used is assigned by the IANA for the registration in <a href="#section-6.4">Section</a>
<a href="#section-6.4">6.4</a>.
If the authority component contains an IP address, e.g.,
xmlrpc.beep://10.0.0.2:1026
then the DNS is not queried, and the IP address is used directly. If
a port number is present, it is used directly; otherwise, the port
number used is assigned by the IANA for the registration in <a href="#section-6.4">Section</a>
<a href="#section-6.4">6.4</a>.
<span class="grey">Harold Experimental [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc3529">RFC 3529</a> Using XML-RPC in BEEP April 2003</span>
While the use of literal IPv6 addresses in URLs is discouraged, if a
literal IPv6 address is used in a "xmlrpc.beep" URL, it must conform
to the syntax specified in [<a href="#ref-7" title=""Format for Literal IPv6 Addresses in URL's"">7</a>].
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a> The xmlrpc.beeps URL Scheme</span>
The "xmlrpc.beeps" URL scheme is identical, in all ways, to the
"xmlrpc.beep" URL scheme specified in <a href="#section-5.1">Section 5.1</a>, with the exception
that prior to starting the BEEP profile for XML-RPC, the BEEP session
must be tuned for privacy. In particular, note that both URL schemes
use the identical algorithms and parameters for address resolution as
specified in <a href="#section-5.1.1">Section 5.1.1</a> (e.g., the same service name for SRV
lookups, the same port number for TCP, and so on).
There are two ways to perform privacy tuning on a BEEP session,
either:
o a transport security profile may be successfully started; or,
o a user authentication profile that supports transport security may
be successfully started.
In either case the client must present the authority component of the
URL in the "serverName" attribute of the "start" element it uses to
tune the session for privacy.
When TLS is used for privacy the client must verify that the
authority component of the URL matches the server's identity as
presented in the server's certificate. Section 2.4 of [<a href="#ref-9" title=""Using TLS with IMAP, POP3 and ACAP"">9</a>] describes
the matching process.
For the URL:
xmlrpc.beeps://stateserver.example.com/NumberToName
the whole process might look like:
S: <wait for incoming connection @ stateserver.example.com>
C: <open connection to stateserver.example.com>
C: RPY 0 0 . 0 52
C: Content-Type: application/xml
C:
C: <greeting />
C: END
S: RPY 0 0 . 0 110
S: Content-Type: application/xml
S:
S: <greeting>
<span class="grey">Harold Experimental [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc3529">RFC 3529</a> Using XML-RPC in BEEP April 2003</span>
S: <profile uri='http://iana.org/beep/TLS' />
S: <profile uri='http://iana.org/beep/SASL/DIGEST-MD5' />
S: </greeting>
S: END
C: MSG 0 1 . 52 158
C: Content-Type: application/xml
C:
C: <start number='1' serverName='stateserver.example.com'>
C: <profile uri='http://iana.org/beep/TLS'>
C: <![CDATA[<ready />]]>
C: </profile>
C: </start>
C: END
S: RPY 0 1 . 110 121
S: Content-Type: application/xml
S:
S: <profile uri='http://iana.org/beep/TLS'>
S: <![CDATA[<proceed />]]>
S: </profile>
S: END
... TLS negotiations ...
S: RPY 0 0 . 0 88
S: Content-Type: application/xml
S:
S: <greeting>
S: <profile uri='http://iana.org/beep/transient/xmlrpc'>
S: </greeting>
S: END
C: RPY 0 0 . 0 52
C: Content-Type: application/xml
C:
C: <greeting />
C: END
... use the server's certificate to verify that it is
in fact stateserver.example.com ...
C: MSG 0 1 . 112 211
C: Content-Type: application/xml
C:
C: <start number='3' serverName='stateserver.example.com'>
C: <profile uri='http://iana.org/beep/transient/xmlrpc'>
C: <![CDATA[<bootmsg resource='/NumberToName' />]]>
C: </profile>
C: </start>
C: END
<span class="grey">Harold Experimental [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc3529">RFC 3529</a> Using XML-RPC in BEEP April 2003</span>
S: RPY 0 2 . 341 402
S: Content-Type: application/xml
S:
S: <profile uri='http://iana.org/beep/transient/xmlrpc'>
S: <![CDATA[<bootrpy />]]>
S: </profile>
S: END
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Initial Registrations</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a> Registration: The XML-RPC Profile</span>
Profile Identification: <a href="http://iana.org/beep/transient/xmlrpc">http://iana.org/beep/transient/xmlrpc</a>
Messages exchanged during Channel Creation: bootmsg, bootrpy
Messages starting one-to-one exchanges: bootmsg, methodCall
Messages in positive replies: bootrpy, methodResponse
Messages in negative replies: error
Messages in one-to-many exchanges: none
Message Syntax: methodCall, methodResponse as defined in [<a href="#ref-1" title=""XML-RPC Specification"">1</a>]
Message Semantics: c.f., [<a href="#ref-1" title=""XML-RPC Specification"">1</a>]
Contact Information: Ward Harold <wharold@us.ibm.com>
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a> Registration: The xmlrpc.beep URL Scheme</span>
URL scheme name: xmlrpc.beep
URL scheme syntax: c.f., <a href="#section-5.1">Section 5.1</a>
Character encoding considerations: c.f., the "generic URI" syntax
defined in Section 3 of [<a href="#ref-5" title=""Uniform Resource Identifiers (URI): Generic Syntax"">5</a>]
Intended usage: identifies a XML-RPC resource made available using
the BEEP profile for XML-RPC
Applications using this scheme: c.f., "Intended usage", above
Interoperability considerations: n/a
Security Considerations: c.f., <a href="#section-7">Section 7</a>
<span class="grey">Harold Experimental [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc3529">RFC 3529</a> Using XML-RPC in BEEP April 2003</span>
Relevant Publications: c.f., [<a href="#ref-1" title=""XML-RPC Specification"">1</a>], and [<a href="#ref-2" title=""The Blocks Extensible Exchange Protocol Core"">2</a>]
Contact Information: Ward Harold <wharold@us.ibm.com>
Author/Change controller: the IESG
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a> Registration: The xmlrpc.beeps URL Scheme</span>
URL scheme name: xmlrpc.beeps
URL scheme syntax: c.f., <a href="#section-5.2">Section 5.2</a>
Character encoding considerations: c.f., the "generic URI" syntax
defined in Section 3 of [<a href="#ref-5" title=""Uniform Resource Identifiers (URI): Generic Syntax"">5</a>]
Intended usage: identifies a XML-RPC resource made available using
the BEEP profile for XML-RPC after the BEEP session has been tuned
for privacy
Applications using this scheme: c.f., "Intended usage", above
Interoperability considerations: n/a
Security Considerations: c.f., <a href="#section-7">Section 7</a>
Relevant Publications: c.f., [<a href="#ref-1" title=""XML-RPC Specification"">1</a>], and [<a href="#ref-2" title=""The Blocks Extensible Exchange Protocol Core"">2</a>]
Contact Information: Ward Harold <wharold@us.ibm.com>
Author/Change controller: the IESG
<span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a> Registration: The System (Well-Known) TCP port number for XML-RPC</span>
<span class="h3"> over BEEP</span>
Protocol Number: TCP
Message Formats, Types, Opcodes, and Sequences: c.f., <a href="#section-2.1">Section 2.1</a>
Functions: c.f., [<a href="#ref-1" title=""XML-RPC Specification"">1</a>]
Use of Broadcast/Multicast: none
Proposed Name: XML-RPC over BEEP
Short name: xmlrpc-beep
Contact Information: Ward Harold <wharold@us.ibm.com>
<span class="grey">Harold Experimental [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc3529">RFC 3529</a> Using XML-RPC in BEEP April 2003</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
Although service provisioning is a policy matter, at a minimum, all
implementations must provide the following tuning profiles:
for authentication: <a href="http://iana.org/beep/SASL/DIGEST-MD5">http://iana.org/beep/SASL/DIGEST-MD5</a>
for confidentiality: <a href="http://iana.org/beep/TLS">http://iana.org/beep/TLS</a> (using the
TLS_RSA_WITH_3DES_EDE_CBC_SHA cipher)
for both: <a href="http://iana.org/beep/TLS">http://iana.org/beep/TLS</a> (using the
TLS_RSA_WITH_3DES_EDE_CBC_SHA cipher supporting client-side
certificates)
Further, implementations may choose to offer MIME-based security
services providing message integrity and confidentiality, such as
OpenPGP [<a href="#ref-8" title=""MIME Security with OpenPGP"">8</a>] or S/MIME [<a href="#ref-10" title=""S/MIME Version 3 Message Specification"">10</a>].
Regardless, consult [<a href="#ref-2" title=""The Blocks Extensible Exchange Protocol Core"">2</a>]'s <a href="#section-9">Section 9</a> for a discussion of BEEP-specific
security issues.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
[<a id="ref-1">1</a>] Winer, D., "XML-RPC Specification", January 1999,
<a href="http://www.xmlrpc.com/spec">http://www.xmlrpc.com/spec</a>
[<a id="ref-2">2</a>] Rose, M., "The Blocks Extensible Exchange Protocol Core", <a href="./rfc3080">RFC</a>
<a href="./rfc3080">3080</a>, March 2001.
[<a id="ref-3">3</a>] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L.,
Leach, P. and T. Berners-Lee, "Hypertext Transfer Protocol --
HTTP/1.1", <a href="./rfc2616">RFC 2616</a>, June 1999.
[<a id="ref-4">4</a>] Murata, M., St. Laurent, S. and D. Kohn, "XML Media Types", <a href="./rfc3023">RFC</a>
<a href="./rfc3023">3023</a>, January 2001.
[<a id="ref-5">5</a>] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource
Identifiers (URI): Generic Syntax", <a href="./rfc2396">RFC 2396</a>, August 1998.
[<a id="ref-6">6</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-7">7</a>] Hinden, R., Carpenter, B. and L. Masinter, "Format for Literal
IPv6 Addresses in URL's", <a href="./rfc2732">RFC 2732</a>, December 1999.
[<a id="ref-8">8</a>] Elkins, M., Del Torto, D., Levien, R. and T. Roessler, "MIME
Security with OpenPGP", <a href="./rfc3156">RFC 3156</a>, August 2001.
<span class="grey">Harold Experimental [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc3529">RFC 3529</a> Using XML-RPC in BEEP April 2003</span>
[<a id="ref-9">9</a>] Newman, C., "Using TLS with IMAP, POP3 and ACAP", <a href="./rfc2595">RFC 2595</a>, June
1999.
[<a id="ref-10">10</a>] Ramsdell, B., "S/MIME Version 3 Message Specification", <a href="./rfc2633">RFC</a>
<a href="./rfc2633">2633</a>, June 1999.
[<a id="ref-11">11</a>] O'Tuathail, E. and M. Rose, "Using the Simple Object Access
Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)",
<a href="./rfc3288">RFC 3288</a>, June 2002.
<span class="grey">Harold Experimental [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc3529">RFC 3529</a> Using XML-RPC in BEEP April 2003</span>
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Acknowledgements</span>
This document is based, in part, on Using SOAP in BEEP [<a href="#ref-11" title=""Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)"">11</a>] and the
author gratefully acknowledges the contributions of Marshall Rose
<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. IANA Considerations</span>
The IANA has registered the profile specified in <a href="#section-6.1">Section 6.1</a>, and has
selected an IANA-specific URI, e.g.,
<a href="http://iana.org/beep/xmlrpc">http://iana.org/beep/xmlrpc</a>
The IANA has registered "xmlrpc.beep" and "xmlrpc.beeps" as URL
schemes, as specified in <a href="#section-6.2">Section 6.2</a> and <a href="#section-6.3">Section 6.3</a>, respectively.
(See: <a href="http://www.iana.org/assignments/uri-schemes">http://www.iana.org/assignments/uri-schemes</a>)
The IANA has registered "XML-RPC over BEEP" as a TCP port number
(602), as specified in <a href="#section-6.4">Section 6.4</a>. (See:
<a href="http://www.iana.org/assignments/port-numbers">http://www.iana.org/assignments/port-numbers</a>)
<span class="grey">Harold Experimental [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc3529">RFC 3529</a> Using XML-RPC in BEEP April 2003</span>
Author's Address
Ward K Harold
IBM
11400 Burnet Road
Austin, Texas 78759
US
Phone: +1 512 838 3622
EMail: wharold@us.ibm.com
<span class="grey">Harold Experimental [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc3529">RFC 3529</a> Using XML-RPC in BEEP April 2003</span>
Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS 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.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Harold Experimental [Page 15]
</pre>
|
