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
|
###### Fractal Generator Protocol ######
## Contact Name:
Thomas Dreibholz
## Contact Email:
thomas.dreibholz@gmail.com
## What type of assignment/registration are you requesting?
SCTP Payload Protocol Identifier for the Fractal Generator Protocol (FGP)
## Which registry are you requesting this assignment/registration be made in?
SCTP Parameters -> SCTP Payload Protocol Identifiers
## If possible, please give a brief description of why you need this assignment/registration:
The Fractal Generator Protocol (FGP) is used by the Fractal Generator Service application of the Reliable Server Pooling (RSerPool) framework implementation RSPLIB. The purpose of the FGP is to demonstrate ASAP cookie based failover (RFC 5351/RFC 5352) and RSerPool workload distribution (draft-dreibholz-rserpool-applic-distcomp-08). Particularly, it is also intended to be used in RSerPool interop testing. Since FGP is multiplexed with the ASAP protocol over a single SCTP stream, different PPIDs are required to distinguish between FGP and ASAP messages.
The implementation of the FGP is available as Open Source under GPLv3 licence within the RSPLIB package at:
https://www.nntb.no/~dreibh/rserpool/ .
Some more documentation of the FGP application can be found here:
* Dreibholz, T.; Becke, M.: ``The RSPLIB Project – From Research to Application´´ (PDF, 2104 KiB), Demo Presentation at the IEEE Global Communications Conference (GLOBECOM), Miami, Florida/U.S.A., December 8, 2010.
http://www.tdr.wiwi.uni-due.de/fileadmin/fileupload/I-TDR/ReliableServer/Publications/Globecom2010-Demo.pdf
* Dreibholz, T.: ``Reliable Server Pooling – Evaluation, Optimization and Extension of a Novel IETF Architecture´´ (PDF, 9079 KiB), University of Duisburg-Essen, Faculty of Economics, Institute for Computer Science and Business Information Systems, March 2007
https://duepublico.uni-duisburg-essen.de/servlets/DerivateServlet/Derivate-16326/Dre2006_final.pdf
## Additional Information. Please include a reference to the specification or RFC (if available) that defines this number or name space:
Registry Name: SCTP Payload Protocol Identifiers
Reference: [RFC4960]
Registration Procedures: First Come First Served
###### Ping Pong Protocol ######
## Contact Name:
Thomas Dreibholz
## Contact Email:
thomas.dreibholz@gmail.com
## What type of assignment/registration are you requesting?
SCTP Payload Protocol Identifier for the Ping Pong Protocol (PPP)
## Which registry are you requesting this assignment/registration be made in?
SCTP Parameters -> SCTP Payload Protocol Identifiers
## If possible, please give a brief description of why you need this assignment/registration:
The Ping Pong Protocol (PPP) is used by the Ping Pong Service application of the Reliable Server Pooling (RSerPool) framework implementation RSPLIB. The purpose of the PPP is to test RSerPool failover behaviour (RFC 5351/RFC 5352). Particularly, it is also intended to be used in RSerPool interop testing. Since PPP is multiplexed with the ASAP protocol over a single SCTP stream, different PPIDs are required to distinguish between PPP and ASAP messages.
The implementation of the PPP is available as Open Source under GPLv3 licence within the RSPLIB package at:
https://www.nntb.no/~dreibh/rserpool/ .
Some more documentation on RSPLIB can be found here:
* Dreibholz, T.: ``Reliable Server Pooling – Evaluation, Optimization and Extension of a Novel IETF Architecture´´ (PDF, 9079 KiB), University of Duisburg-Essen, Faculty of Economics, Institute for Computer Science and Business Information Systems, March 2007
https://duepublico.uni-duisburg-essen.de/servlets/DerivateServlet/Derivate-16326/Dre2006_final.pdf
## Additional Information. Please include a reference to the specification or RFC (if available) that defines this number or name space:
Registry Name: SCTP Payload Protocol Identifiers
Reference: [RFC4960]
Registration Procedures: First Come First Served
###### CalcApp Protocol ######
## Contact Name:
Thomas Dreibholz
## Contact Email:
thomas.dreibholz@gmail.com
## What type of assignment/registration are you requesting?
SCTP Payload Protocol Identifier for the CalcApp Protocol (CALCAPP)
## Which registry are you requesting this assignment/registration be made in?
SCTP Parameters -> SCTP Payload Protocol Identifiers
## If possible, please give a brief description of why you need this assignment/registration:
The CalcApp Protocol (CALCAPP) is used by the CalcApp Service application of the Reliable Server Pooling (RSerPool) framework implementation RSPLIB. The purpose of CALCAPP is to measure failover (RFC 5351/RFC 5352) and pool member selection policy (RFC 5356; draft-dreibholz-rserpool-asap-hropt-08; draft-dreibholz-rserpool-delay-07) performance in distributed setups (draft-dreibholz-rserpool-applic-distcomp-08). Particularly, it is also intended to be used in RSerPool interop testing.
Its implementation is available as Open Source under GPLv3 licence. Since CALCAPP is multiplexed with the ASAP protocol over a single SCTP stream, different PPIDs are required to distinguish between CALCAPP and ASAP messages.
The implementation of the CALCAPP is available as Open Source under GPLv3 licence within the RSPLIB package at:
https://www.nntb.no/~dreibh/rserpool/ .
Some more documentation of the CALCAPP application can be found here:
* Dreibholz, T.: ``Reliable Server Pooling – Evaluation, Optimization and Extension of a Novel IETF Architecture´´ (PDF, 9079 KiB), University of Duisburg-Essen, Faculty of Economics, Institute for Computer Science and Business Information Systems, March 2007
https://duepublico.uni-duisburg-essen.de/servlets/DerivateServlet/Derivate-16326/Dre2006_final.pdf
* Dreibholz, T.; Zhou, X.; Becke, M.; Pulinthanath, J.; Rathgeb, E. P.; Du, W.: ``On the Security of Reliable Server Pooling Systems´´ (PDF, 539 KiB), in International Journal on Intelligent Information and Database Systems (IJIIDS), vol. 4, no. 6, pp. 552–578, ISSN 1751-5858, December 2010.
http://www.tdr.wiwi.uni-due.de/fileadmin/fileupload/I-TDR/ReliableServer/Publications/IJIIDS2010.pdf
* Dreibholz, T.; Rathgeb, E. P.: ``Overview and Evaluation of the Server Redundancy and Session Failover Mechanisms in the Reliable Server Pooling Framework´´ (PDF, 1156 KiB), in International Journal on Advances in Internet Technology (IJAIT), vol. 2, no. 1, pp. 1–14, ISSN 1942-2652, June 2009.
http://www.tdr.wiwi.uni-due.de/fileadmin/fileupload/I-TDR/ReliableServer/Publications/IJAIT2009.pdf
* Dreibholz, T.; Rathgeb, E. P.: ``On Improving the Performance of Reliable Server Pooling Systems for Distance-Sensitive Distributed Applications´´ (PDF, 392 KiB), in Proceedings of the 15. ITG/GI Fachtagung Kommunikation in Verteilten Systemen (KiVS), Informatik aktuell, pp. 39–50, Springer, ISBN 978-3-540-69962-0, Bern/Switzerland, February 2007.
http://www.tdr.wiwi.uni-due.de/fileadmin/fileupload/I-TDR/ReliableServer/Publications/KiVS2007.pdf
* Dreibholz, T.; Rathgeb, E. P.: ``On the Performance of Reliable Server Pooling Systems´´ (PDF, 672 KiB), in Proceedings of the IEEE Conference on Local Computer Networks (LCN) 30th Anniversary, pp. 200–208, ISBN 0-7695-2421-4, ISSN 0742-1303, Sydney/Australia, November 16, 2005.
http://www.tdr.wiwi.uni-due.de/fileadmin/fileupload/I-TDR/ReliableServer/Publications/LCN2005.pdf
## Additional Information. Please include a reference to the specification or RFC (if available) that defines this number or name space:
Registry Name: SCTP Payload Protocol Identifiers
Reference: [RFC4960]
Registration Procedures: First Come First Served
###### Scripting Service Protocol ######
## Contact Name:
Thomas Dreibholz
## Contact Email:
thomas.dreibholz@gmail.com
## What type of assignment/registration are you requesting?
SCTP Payload Protocol Identifier for the Scripting Service Protocol (SSP)
## Which registry are you requesting this assignment/registration be made in?
SCTP Parameters -> SCTP Payload Protocol Identifiers
## If possible, please give a brief description of why you need this assignment/registration:
The Scripting Service Protocol (SSP is used by the Scripting Service Service application of the Reliable Server Pooling (RSerPool) framework implementation RSPLIB. The purpose of SSP is to distribute workload in an RSerPool-based compute pool (draft-dreibholz-rserpool-applic-distcomp-08). For example, SSP is used by the Simulation Processing Tool-Chain "SimProcTC" to distribute simulation runs.
Its implementation is available as Open Source under GPLv3 licence. Since SSP is multiplexed with the ASAP protocol over a single SCTP stream, different PPIDs are required to distinguish between SSP and ASAP messages.
The implementation of the SSP is available as Open Source under GPLv3 licence within the RSPLIB package at:
https://www.nntb.no/~dreibh/rserpool/ .
Some more documentation of the SSP application can be found here:
* Dreibholz, T.; Zhou, X.; Rathgeb, E. P.: ``SimProcTC – The Design and Realization of a Powerful Tool-Chain for OMNeT++ Simulations´´ (PDF, 551 KiB), in Proceedings of the 2nd ACM/ICST International Workshop on OMNeT++, pp. 1–8, ISBN 978-963-9799-45-5, Rome/Italy, March 6, 2009.
http://www.tdr.wiwi.uni-due.de/fileadmin/fileupload/I-TDR/ReliableServer/Publications/OMNeT__Workshop2009.pdf
* Dreibholz, T.; Rathgeb, E. P.: ``A Powerful Tool-Chain for Setup, Distributed Processing, Analysis and Debugging of OMNeT++ Simulations´´ (PDF, 557 KiB), in Proceedings of the 1st ACM/ICST International Workshop on OMNeT++, ISBN 978-963-9799-20-2, Marseille/France, March 7, 2008.
http://www.tdr.wiwi.uni-due.de/fileadmin/fileupload/I-TDR/ReliableServer/Publications/OMNeTWorkshop2008.pdf
* SimProcTC Homepage: https://www.nntb.no/~dreibh/omnetpp/
## Additional Information. Please include a reference to the specification or RFC (if available) that defines this number or name space:
Registry Name: SCTP Payload Protocol Identifiers
Reference: [RFC4960]
Registration Procedures: First Come First Served
###### Test Protocols ######
## Contact Name:
Thomas Dreibholz
## Contact Email:
thomas.dreibholz@gmail.com
## What type of assignment/registration are you requesting?
SCTP Payload Protocol Identifier for RSerPool test protocols:
- Echo (ECHO)
- Discard (DISCARD)
- Daytime (DAYTIME)
- Character Generator (CHARGEN)
## Which registry are you requesting this assignment/registration be made in?
SCTP Parameters -> SCTP Payload Protocol Identifiers
## If possible, please give a brief description of why you need this assignment/registration:
The protocols ECHO, DISCARD, DAYTIME and CHARGEN are test applications of the Reliable Server Pooling (RSerPool) framework implementation RSPLIB. The purpose of these protocols is to test the correct behaviour of implementations (according to RFC 5351 to RFC 5354 and RFC 5356). In particular, these protocols are used for interop testing (draft-dreibholz-rserpool-score-08). Since the test protocols are multiplexed with the ASAP protocol over a single SCTP stream, different PPIDs are required to distinguish between test protocol and ASAP messages.
The implementation of the ECHO, DISCARD, DAYTIME and CHARGEN protocols is available as Open Source under GPLv3 licence within the RSPLIB package at:
https://www.nntb.no/~dreibh/rserpool/ .
Some more information on RSerPool interop testing can be found here:
* draft-dreibholz-rserpool-score-08
* Dreibholz, T.: ``Reliable Server Pooling – Evaluation, Optimization and Extension of a Novel IETF Architecture´´ (PDF, 9079 KiB), University of Duisburg-Essen, Faculty of Economics, Institute for Computer Science and Business Information Systems, March 2007
https://duepublico.uni-duisburg-essen.de/servlets/DerivateServlet/Derivate-16326/Dre2006_final.pdf
## Additional Information. Please include a reference to the specification or RFC (if available) that defines this number or name space:
Registry Name: SCTP Payload Protocol Identifiers
Reference: [RFC4960]
Registration Procedures: First Come First Served
|
