aboutsummaryrefslogblamecommitdiffstats
path: root/lib/diameter/doc/src/diameter_soc.xml
blob: 28e01ff1befdba41becf2ea2be17fc483889be3f (plain) (tree)
1
2
3
4
5
6
7
8
9
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
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
                                       
                                        






                                                                                       


                                        
 
         



                 
                 



                                                  




                                                                
 




                                                                        















                                   





                                                                     
 
   




                                                                      
 
   

                                                               



                                                                              
                                                 
 































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































                                                                              



          






                                                                  
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE chapter SYSTEM "chapter.dtd" [
  <!ENTITY gen_sctp '<seealso marker="kernel:gen_sctp">gen_sctp(3)</seealso>'>
  <!ENTITY gen_tcp '<seealso marker="kernel:gen_tcp">gen_tcp(3)</seealso>'>
  <!ENTITY service '<seealso marker="diameter#start_service-2">service</seealso>'>
  <!ENTITY capabilities '<seealso marker="diameter#capability">capabilities</seealso>'>
  <!ENTITY events '<seealso marker="diameter#service_event">events</seealso>'>
  <!ENTITY NA '&#8212;'>
  <!ENTITY BR '<br/>&nbsp;<br/>'>
  <!ENTITY % also SYSTEM "seealso.ent" >
  %also;
]>

<chapter>

<header>
<copyright>
<year>2011</year>
<year>2017</year>
<holder>Ericsson AB. All Rights Reserved.</holder>
</copyright>

<legalnotice>
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
 
    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

</legalnotice>

<title>Standards Compliance</title>
<prepared></prepared>
<responsible></responsible>
<docno></docno>
<approved></approved>
<checked></checked>
<date></date>
<rev></rev>
<file>diameter_soc.xml</file>

</header>

<p>
The table below summarizes the diameter application's compliance with
&the_rfc;.
Since the diameter application isn't a Diameter node on its own,
compliance is strictly the responsibility of the user in many cases,
diameter providing the means for the user to be compliant
rather than being compliant on its own.</p>

<p>
The Compliance column notes <em>C</em> (Compliant) if the required
functionality is implemented, <em>PC</em> (Partially Compliant) if
there are limitations, <em>NC</em> (Not Compliant) if functionality is
not implemented, or a dash if text is informational or only places
requirements that must be met by the user's implementation.</p>

<p>
Capitalized <em>Diameter</em> refers to the protocol, lowercase
<em>diameter</em> to the Erlang application.</p>

<!-- ===================================================================== -->

<section>
<title>&the_rfc; - Diameter Base Protocol</title>

<table>
<row>
  <cell><em>Section</em></cell>
  <cell><em>Title</em></cell>
  <cell><em>Compliance</em></cell>
  <cell><em>Notes</em></cell>
</row>
<row>
  <cell>1</cell>
  <cell>Introduction</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>1.1</cell>
  <cell>Diameter Protocol</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>1.1.1</cell>
  <cell>Description of the Document Set</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>1.1.2</cell>
  <cell>Conventions Used in This Document</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>1.1.3</cell>
  <cell>Changes from RFC 3588</cell>
  <cell>&NA;</cell>
  <cell>It is possible to configure a 3588 dictionary in
  order to get 3588 semantics, where the differ from 6733.</cell>
</row>
<row>
  <cell>1.2</cell>
  <cell>Terminology</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>1.3</cell>
  <cell>Approach to Extensibility</cell>
  <cell>&NA;</cell>
  <cell>The dictionary interface documented in &man_dict; provides
  extensibility, allowing the user to defined new AVPs, commands, and
  applications.
  Ready dictionaries are provided for the &the_rfc; common message, base
  accounting, and relay applications, as well as for RFC 7683,
  Diameter Overload Indicator Conveyance.</cell>
</row>
<row>
  <cell>1.3.1</cell>
  <cell>Defining New AVP Values</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>1.3.2</cell>
  <cell>Creating New AVPs</cell>
  <cell>&NA;</cell>
  <cell>New AVPs can be defined using the dictionary interface.
  Both both RFC data formats and extensions are supported.</cell>
</row>
<row>
  <cell>1.3.3</cell>
  <cell>Creating New Commands</cell>
  <cell>&NA;</cell>
  <cell>New commands can be defined using the dictionary interface.</cell>
</row>
<row>
  <cell>1.3.4</cell>
  <cell>Creating New Diameter Applications</cell>
  <cell>&NA;</cell>
  <cell>New applications can be defined using the dictionary interface.</cell>
</row>
<row>
  <cell>2</cell>
  <cell>Protocol Overview</cell>
  <cell>&NA;</cell>
  <cell>Session state is the responsibility of the user.&BR;
  The role of a Diameter node is determined by the user's
  implementation.</cell>
</row>
<row>
  <cell>2.1</cell>
  <cell>Transport</cell>
  <cell>PC</cell>
  <cell>Ports are configured by the user: diameter places no
  restrictions.&BR;
  The transport interface documented in &man_transport;
  allows the user to implement their own methods.
  Ready support is provided for TCP, TCP/TLS, and SCTP, but not
  DTLS/SCTP.&BR;
  Multiple connections to the same peer is possible.
  ICMP messages are not interpreted.</cell>
</row>
<row>
  <cell>2.1.1</cell>
  <cell>SCTP Guidelines</cell>
  <cell>C</cell>
  <cell>Unordered sending is configurable in &man_sctp;.
  There is no special handling of DPR/DPA: since a user that cares
  about pending answers should wait for them before initiating
  DPR.&BR;
  A PPID can be configured with a a gen_sctp sctp_default_send_param
  option.</cell>
</row>
<row>
  <cell>2.2</cell>
  <cell>Securing Diameter Messages</cell>
  <cell>PC</cell>
  <cell>DTLS is not supported by &man_sctp;. See also
  2.1.</cell>
</row>
<row>
  <cell>2.3</cell>
  <cell>Diameter Application Compliance</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>2.4</cell>
  <cell>Application Identifiers</cell>
  <cell>C</cell>
  <cell>The user configures diameter with the identifiers to send at
  capabilities exchange, along with corresponding dictionaries
  defining the messages of the applications.</cell>
</row>
<row>
  <cell>2.5</cell>
  <cell>Connections vs. Sessions</cell>
  <cell>C</cell>
  <cell>Connections are realized by configuring transport. Sessions
  are the responsibility of the user.</cell>
</row>
<row>
  <cell>2.6</cell>
  <cell>Peer Table</cell>
  <cell>PC</cell>
  <cell>Routing is implemented by the user in callbacks documented in
  &man_app;.
  A peer table of the documented form is not exposed to the user.</cell>
</row>
<row>
  <cell>2.7</cell>
  <cell>Routing Table</cell>
  <cell>PC</cell>
  <cell>See 2.6.
  A routing table of the documented form is not exposed to
  the user.</cell>
</row>
<row>
  <cell>2.8</cell>
  <cell>Role of Diameter Agents</cell>
  <cell>C</cell>
  <cell>Most role-specific behaviour is implemented by the user.
  How a node advertises itself at capabilities exchange is determined
  by user configuration.</cell>
</row>
<row>
  <cell>2.8.1</cell>
  <cell>Relay Agents</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>2.8.2</cell>
  <cell>Proxy Agents</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>2.8.3</cell>
  <cell>Redirect Agents</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>2.8.4</cell>
  <cell>Translation Agents</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>2.9</cell>
  <cell>Diameter Path Authorization</cell>
  <cell>&NA;</cell>
  <cell>Authorization is the responsibility of the user.</cell>
</row>
<row>
  <cell>3</cell>
  <cell>Diameter Header</cell>
  <cell>C</cell>
  <cell>Hop-by-Hop and End-to-End Identifiers are set by diameter when
  sending outgoing requests.</cell>
</row>
<row>
  <cell>3.1</cell>
  <cell>Command Codes</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>3.2</cell>
  <cell>Command Code Format Specification</cell>
  <cell>C</cell>
  <cell>Commands are defined as CCF specifications in dictionary
  files.</cell>
</row>
<row>
  <cell>3.3</cell>
  <cell>Diameter Command Naming Conventions</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>4</cell>
  <cell>Diameter AVPs</cell>
  <cell>C</cell>
  <cell>Any required padding is added by diameter when encoding
  outgoing messages.</cell>
</row>
<row>
  <cell>4.1</cell>
  <cell>AVP Header</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>4.1.1</cell>
  <cell>Optional Header Elements</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>4.2</cell>
  <cell>Basic AVP Data Formats</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>4.3</cell>
  <cell>Derived AVP Data Formats</cell>
  <cell>C</cell>
  <cell>Arbitrary derived data formats are supported by the dictionary
  interface.</cell>
</row>
<row>
  <cell>4.3.1</cell>
  <cell>Common Derived AVP Data Formats</cell>
  <cell>C</cell>
  <cell>Beware that RFC 6733 changed the DiameterURI transport/port
  defaults specified in RFC3588.
  Relying on the defaults can result in interoperability
  problems.</cell>
</row>
<row>
  <cell>4.4</cell>
  <cell>Grouped AVP Values</cell>
  <cell>C</cell>
  <cell>The M-bit on a component AVP of a Grouped AVP that does not
  set M is ignored: such AVPs are not regarded as erroneous at
  decode.&BR;
  Grouped AVPs are defined as CCF specifications in dictionary
  files.</cell>
</row>
<row>
  <cell>4.4.1</cell>
  <cell>Example AVP with a Grouped Data Type</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>4.5</cell>
  <cell>Diameter Base Protocol AVPs</cell>
  <cell>C</cell>
  <cell>The base AVPs are defined in the common dictionary provided by
  diameter.
  There are common dictionaries for both RFC 3588 and RFC 6733 since
  the latter made changes to both syntax and semantics.</cell>
</row>
<row>
  <cell>5</cell>
  <cell>Diameter Peers</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>5.1</cell>
  <cell>Peer Connections</cell>
  <cell>PC</cell>
  <cell>A peer's DiameterIdentity is not required when initiating a
  connection: the identify is received at capabilities exchange, at
  which time the connection can be rejected if the identity is
  objectionable.&BR;
  The number of connections established depends on the user's
  configuration. Multiple connections per peer is possible.</cell>
</row>
<row>
  <cell>5.2</cell>
  <cell>Diameter Peer Discovery</cell>
  <cell>NC</cell>
  <cell>No form of peer discovery is implemented.
  The user can implement this independently of diameter if
  required.</cell>
</row>
<row>
  <cell>5.3</cell>
  <cell>Capabilities Exchange</cell>
  <cell>C</cell>
  <cell>All supported applications are sent in CEA.
  The user can reject an incoming CER or CEA in a configured
  callback.&BR;
  Both transport security at connection establishment and
  negotiated via an Inband-Security AVP are supported.</cell>
</row>
<row>
  <cell>5.3.1</cell>
  <cell>Capabilities-Exchange-Request</cell>
  <cell>C</cell>
  <cell>CER is sent and received by diameter.</cell>
</row>
<row>
  <cell>5.3.2</cell>
  <cell>Capabilities-Exchange-Answer</cell>
  <cell>C</cell>
  <cell>CEA is sent and received by diameter.</cell>
</row>
<row>
  <cell>5.3.3</cell>
  <cell>Vendor-Id AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>5.3.4</cell>
  <cell>Firmware-Revision AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>5.3.5</cell>
  <cell>Host-IP-Address AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>5.3.6</cell>
  <cell>Supported-Vendor-Id AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>5.3.7</cell>
  <cell>Product-Name AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>5.4</cell>
  <cell>Disconnecting Peer Connections</cell>
  <cell>C</cell>
  <cell>DPA will not be answered with error: a peer that wants to a
  avoid a race can wait for pending answers before sending
  DPR.</cell>
</row>
<row>
  <cell>5.4.1</cell>
  <cell>Disconnect-Peer-Request</cell>
  <cell>C</cell>
  <cell>DPR is sent by diameter in response to configuration
  changes requiring a connection to be broken.
  The user can also send DPR.</cell>
</row>
<row>
  <cell>5.4.2</cell>
  <cell>Disconnect-Peer-Answer</cell>
  <cell>C</cell>
  <cell>DPR is answered by diameter.</cell>
</row>
<row>
  <cell>5.4.3</cell>
  <cell>Disconnect-Cause AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>5.5</cell>
  <cell>Transport Failure Detection</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>5.5.1</cell>
  <cell>Device-Watchdog-Request</cell>
  <cell>C</cell>
  <cell>DWR is sent and received by diameter.
  Callbacks notify the user of transitions into and out of the OKAY
  state.</cell>
</row>
<row>
  <cell>5.5.2</cell>
  <cell>Device-Watchdog-Answer</cell>
  <cell>C</cell>
  <cell>DWA is sent and received by diameter.</cell>
</row>
<row>
  <cell>5.5.3</cell>
  <cell>Transport Failure Algorithm</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>5.5.4</cell>
  <cell>Failover and Failback Procedures</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>5.6</cell>
  <cell>Peer State Machine</cell>
  <cell>PC</cell>
  <cell>The election process is modified as described in 5.6.4.</cell>
</row>
<row>
  <cell>5.6.1</cell>
  <cell>Incoming Connections</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>5.6.2</cell>
  <cell>Events</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>5.6.3</cell>
  <cell>Actions</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>5.6.4</cell>
  <cell>The Election Process</cell>
  <cell>PC</cell>
  <cell>As documented, the election assumes knowledge of a peer's
  DiameterIdentity when initiating a connection, which diameter
  doesn't require. Connections will be accepted if configuration
  allows multiple connections per peer to be established or there is
  no existing connection. Note that the election process is only
  applicable when multiple connections per peer is
  disallowed.</cell>
</row>
<row>
  <cell>6</cell>
  <cell>Diameter Message Processing</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>6.1</cell>
  <cell>Diameter Request Routing Overview</cell>
  <cell>&NA;</cell>
  <cell>Routing is performed by the user.
  A callback from diameter provides a list of available suitable peer
  connections.</cell>
</row>
<row>
  <cell>6.1.1</cell>
  <cell>Originating a Request</cell>
  <cell>C</cell>
  <cell>Requests are constructed by the user; diameter sets header
  fields as defined in the relevant dictionary.</cell>
</row>
<row>
  <cell>6.1.2</cell>
  <cell>Sending a Request</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>6.1.3</cell>
  <cell>Receiving Requests</cell>
  <cell>C</cell>
  <cell>Loops are detected by diameter when the return value of a
  request callback asks that a request be forwarded.
  Loop detection in other cases is the responsibility of the
  user.</cell>
</row>
<row>
  <cell>6.1.4</cell>
  <cell>Processing Local Requests</cell>
  <cell>C</cell>
  <cell>The user decides whether or not to process a request locally
  in the request callback from diameter.</cell>
</row>
<row>
  <cell>6.1.5</cell>
  <cell>Request Forwarding</cell>
  <cell>PC</cell>
  <cell>See 2.6.</cell>
</row>
<row>
  <cell>6.1.6</cell>
  <cell>Request Routing</cell>
  <cell>PC</cell>
  <cell>See 2.7.</cell>
</row>
<row>
  <cell>6.1.7</cell>
  <cell>Predictive Loop Avoidance</cell>
  <cell>C</cell>
  <cell>See 6.1.3.</cell>
</row>
<row>
  <cell>6.1.8</cell>
  <cell>Redirecting Requests</cell>
  <cell>PC</cell>
  <cell>See 2.6.</cell>
</row>
<row>
  <cell>6.1.9</cell>
  <cell>Relaying and Proxying Requests</cell>
  <cell>C</cell>
  <cell>A Route-Record AVP is appended by diameter when the return
  value of a request callback asks that a request be forwarded.
  Appending the AVP in other cases is the responsibility of the
  user.</cell>
</row>
<row>
  <cell>6.2</cell>
  <cell>Diameter Answer Processing</cell>
  <cell>C</cell>
  <cell>Answer message are constructed by the user, except in the case
  of some protocol errors, in which case the procedures are
  followed.</cell>
</row>
<row>
  <cell>6.2.1</cell>
  <cell>Processing Received Answers</cell>
  <cell>C</cell>
  <cell>Answers with an unknown Hop-by-Hop Identifier are
  discarded.</cell>
</row>
<row>
  <cell>6.2.2</cell>
  <cell>Relaying and Proxying Answers</cell>
  <cell>&NA;</cell>
  <cell>Modifying answers is the responsibility of the user in
  callbacks from diameter.</cell>
</row>
<row>
  <cell>6.3</cell>
  <cell>Origin-Host AVP</cell>
  <cell>C</cell>
  <cell>The order of AVPs in an encoded message is determined by
  the CCF of the message in question.&BR;
  AVPs defined in the RFC are defined in dictionaries provided by
  diameter.
  Their proper use in application messages is the responsibility of
  the user.</cell>
</row>
<row>
  <cell>6.4</cell>
  <cell>Origin-Realm AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>6.5</cell>
  <cell>Destination-Host AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>6.6</cell>
  <cell>Destination-Realm AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>6.7</cell>
  <cell>Routing AVPs</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>6.7.1</cell>
  <cell>Route-Record AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>6.7.2</cell>
  <cell>Proxy-Info AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>6.7.3</cell>
  <cell>Proxy-Host AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>6.7.4</cell>
  <cell>Proxy-State AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>6.8</cell>
  <cell>Auth-Application-Id AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>6.9</cell>
  <cell>Acct-Application-Id AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>6.10</cell>
  <cell>Inband-Security-Id AVP</cell>
  <cell>C</cell>
  <cell>See 2.1.</cell>
</row>
<row>
  <cell>6.11</cell>
  <cell>Vendor-Specific-Application-Id AVP</cell>
  <cell>C</cell>
  <cell>Note that the CCF of this AVP is not the same as in RFC
  3588.</cell>
</row>
<row>
  <cell>6.12</cell>
  <cell>Redirect-Host AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>6.13</cell>
  <cell>Redirect-Host-Usage AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>6.14</cell>
  <cell>Redirect-Max-Cache-Time AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>7</cell>
  <cell>Error Handling</cell>
  <cell>C</cell>
  <cell>Answers are formulated by the user in most cases.
  Answers setting the E-bit can be sent by diameter itself in response
  to a request that cannot be handled by the user.</cell>
</row>
<row>
  <cell>7.1</cell>
  <cell>Result-Code AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>7.1.1</cell>
  <cell>Informational</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>7.1.2</cell>
  <cell>Success</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>7.1.3</cell>
  <cell>Protocol Errors</cell>
  <cell>C</cell>
  <cell>Result codes 3001, 3002, 3005, and 3007 can be sent in answers
  formulated by diameter, if configured to do so.</cell>
</row>
<row>
  <cell>7.1.4</cell>
  <cell>Transient Failures</cell>
  <cell>C</cell>
  <cell>Result code 4003 is sent in CEA if there is an existing
  connection to the peer in question and configuration does not allow
  more than one.</cell>
</row>
<row>
  <cell>7.1.5</cell>
  <cell>Permanent Failures</cell>
  <cell>C</cell>
  <cell>Message reception detects 5001, 5004,
  5005, 5008, 5009, 5010, 5011, 5014, 5015, and 5017 errors.
  It ignores 5013 errors at the admonition of sections 3 and 4.1.&BR;
  Note that RFC 3588 did not allow 5xxx result codes in
  answers setting the E-bit, while RFC 6733 does.
  This is a potential interoperability problem since the Diameter
  protocol version has not changed.</cell>
</row>
<row>
  <cell>7.2</cell>
  <cell>Error Bit</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>7.3</cell>
  <cell>Error-Message AVP</cell>
  <cell>C</cell>
  <cell>The user can include this AVP as required.</cell>
</row>
<row>
  <cell>7.4</cell>
  <cell>Error-Reporting-Host AVP</cell>
  <cell>C</cell>
  <cell>The user can include this AVP as required.</cell>
</row>
<row>
  <cell>7.5</cell>
  <cell>Failed-AVP AVP</cell>
  <cell>C</cell>
  <cell>The user constructs application-specific messages, but
  diameter provides failed AVPs in message callbacks. Failed component AVPs
  are grouped within the relevant Grouped AVPs.</cell>
</row>
<row>
  <cell>7.6</cell>
  <cell>Experimental-Result AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>7.7</cell>
  <cell>Experimental-Result-Code AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>8</cell>
  <cell>Diameter User Sessions</cell>
  <cell>&NA;</cell>
  <cell>Authorization and accounting AVPs are defined in provided
  dictionaries. Their proper use is the responsibility of the
  user.</cell>
</row>
<row>
  <cell>8.1</cell>
  <cell>Authorization Session State Machine</cell>
  <cell>&NA;</cell>
  <cell>Authorization is the responsibility of the user: diameter does
  not implement this state machine.</cell>
</row>
<row>
  <cell>8.2</cell>
  <cell>Accounting Session State Machine</cell>
  <cell>&NA;</cell>
  <cell>Accounting is the responsibility of the user: diameter does
  not implement this state machine.</cell>
</row>
<row>
  <cell>8.3</cell>
  <cell>Server-Initiated Re-Auth</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>8.3.1</cell>
  <cell>Re-Auth-Request</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>8.3.2</cell>
  <cell>Re-Auth-Answer</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>8.4</cell>
  <cell>Session Termination</cell>
  <cell>&NA;</cell>
  <cell>Session-related messages and AVPs are defined in provided
  dictionaries. Their proper use is the user's responsibility.</cell>
</row>
<row>
  <cell>8.4.1</cell>
  <cell>Session-Termination-Request</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>8.4.2</cell>
  <cell>Session-Termination-Answer</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>8.5</cell>
  <cell>Aborting a Session</cell>
  <cell>&NA;</cell>
  <cell>Session-related messages and AVPs are defined in provided
  dictionaries. Their proper use is the user's responsibility.</cell>
</row>
<row>
  <cell>8.5.1</cell>
  <cell>Abort-Session-Request</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>8.5.2</cell>
  <cell>Abort-Session-Answer</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>8.6</cell>
  <cell>Inferring Session Termination from Origin-State-Id</cell>
  <cell>&NA;</cell>
  <cell>Session-related messages and AVPs are defined in provided
  dictionaries. Their proper use is the user's responsibility.</cell>
</row>
<row>
  <cell>8.7</cell>
  <cell>Auth-Request-Type AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>8.8</cell>
  <cell>Session-Id AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>8.9</cell>
  <cell>Authorization-Lifetime AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>8.10</cell>
  <cell>Auth-Grace-Period AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>8.11</cell>
  <cell>Auth-Session-State AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>8.12</cell>
  <cell>Re-Auth-Request-Type AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>8.13</cell>
  <cell>Session-Timeout AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>8.14</cell>
  <cell>User-Name AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>8.15</cell>
  <cell>Termination-Cause AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>8.16</cell>
  <cell>Origin-State-Id AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>8.17</cell>
  <cell>Session-Binding AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>8.18</cell>
  <cell>Session-Server-Failover AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>8.19</cell>
  <cell>Multi-Round-Time-Out AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>8.20</cell>
  <cell>Class AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>8.21</cell>
  <cell>Event-Timestamp AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>9</cell>
  <cell>Accounting</cell>
  <cell>&NA;</cell>
  <cell>Accounting-related messages and AVPs are defined in provided
  dictionaries. Their proper use is the user's responsibility.</cell>
</row>
<row>
  <cell>9.1</cell>
  <cell>Server Directed Model</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>9.2</cell>
  <cell>Protocol Messages</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>9.3</cell>
  <cell>Accounting Application Extension and Requirements</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>9.4</cell>
  <cell>Fault Resilience</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>9.5</cell>
  <cell>Accounting Records</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>9.6</cell>
  <cell>Correlation of Accounting Records</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>9.7</cell>
  <cell>Accounting Command Codes</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>9.7.1</cell>
  <cell>Accounting-Request</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>9.7.2</cell>
  <cell>Accounting-Answer</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>9.8</cell>
  <cell>Accounting AVPs</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>9.8.1</cell>
  <cell>Accounting-Record-Type AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>9.8.2</cell>
  <cell>Acct-Interim-Interval AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>9.8.3</cell>
  <cell>Accounting-Record-Number AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>9.8.4</cell>
  <cell>Acct-Session-Id AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>9.8.5</cell>
  <cell>Acct-Multi-Session-Id AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>9.8.6</cell>
  <cell>Accounting-Sub-Session-Id AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>9.8.7</cell>
  <cell>Accounting-Realtime-Required AVP</cell>
  <cell>C</cell>
  <cell></cell>
</row>
<row>
  <cell>10</cell>
  <cell>AVP Occurrence Tables</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>10.1</cell>
  <cell>Base Protocol Command AVP Table</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>10.2</cell>
  <cell>Accounting AVP Table</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11</cell>
  <cell>IANA Considerations</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11.1</cell>
  <cell>AVP Header</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11.1.1</cell>
  <cell>AVP Codes</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11.1.2</cell>
  <cell>AVP Flags</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11.2</cell>
  <cell>Diameter Header</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11.2.1</cell>
  <cell>Command Codes</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11.2.2</cell>
  <cell>Command Flags</cell>
  <cell></cell>
  <cell></cell>
</row>
<row>
  <cell>11.3</cell>
  <cell>AVP Values</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11.3.1</cell>
  <cell>Experimental-Result-Code AVP</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11.3.2</cell>
  <cell>Result-Code AVP Values</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11.3.3</cell>
  <cell>Accounting-Record-Type AVP Values</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11.3.4</cell>
  <cell>Termination-Cause AVP Values</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11.3.5</cell>
  <cell>Redirect-Host-Usage AVP Values</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11.3.6</cell>
  <cell>Session-Server-Failover AVP Values</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11.3.7</cell>
  <cell>Session-Binding AVP Values</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11.3.8</cell>
  <cell>Disconnect-Cause AVP Values</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11.3.9</cell>
  <cell>Auth-Request-Type AVP Values</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11.3.10</cell>
  <cell>Auth-Session-State AVP Values</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11.3.11</cell>
  <cell>Re-Auth-Request-Type AVP Values</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11.3.12</cell>
  <cell>Accounting-Realtime-Required AVP Values</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11.3.13</cell>
  <cell>Inband-Security-Id AVP (code 299)</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11.4</cell>
  <cell>_diameters Service Name and Port Number Registration</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11.5</cell>
  <cell>SCTP Payload Protocol Identifiers</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>11.6</cell>
  <cell>S-NAPTR Parameters</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>12</cell>
  <cell>Diameter Protocol-Related Configurable Parameters</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>13</cell>
  <cell>Security Considerations</cell>
  <cell>PC</cell>
  <cell>See 2.1.&BR;
  IPsec is transparent to diameter.</cell>
</row>
<row>
  <cell>13.1</cell>
  <cell>TLS/TCP and DTLS/SCTP Usage</cell>
  <cell>PC</cell>
  <cell>See 2.1.</cell>
</row>
<row>
  <cell>13.2</cell>
  <cell>Peer-to-Peer Considerations</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>13.3</cell>
  <cell>AVP Considerations</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>14</cell>
  <cell>References</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>14.1</cell>
  <cell>Normative References</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>
<row>
  <cell>14.2</cell>
  <cell>Informative References</cell>
  <cell>&NA;</cell>
  <cell></cell>
</row>

<tcaption>RFC 6733 Compliance</tcaption>
</table>

</section>

</chapter>

<!--  LocalWords:  AVP AVPs CCF DiameterIdentity CEA CER Inband IP
-->
<!--  LocalWords:  DPA DPR DWR DWA Failover Failback Proxying Auth
-->
<!--  LocalWords:  interoperability Multi Timestamp Realtime
-->