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
|
<pre>Internet Engineering Task Force (IETF) A. Morton
Request for Comments: 6038 L. Ciavattone
Updates: <a href="./rfc5357">5357</a> AT&T Labs
Category: Standards Track October 2010
ISSN: 2070-1721
<span class="h1">Two-Way Active Measurement Protocol (TWAMP) Reflect Octets and</span>
<span class="h1">Symmetrical Size Features</span>
Abstract
This memo describes two closely related features for the core
specification of the Two-Way Active Measurement Protocol (TWAMP): an
optional capability where the responding host returns some of the
command octets or padding octets to the sender, and an optional
sender packet format that ensures equal test packet sizes are used in
both directions.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc6038">http://www.rfc-editor.org/info/rfc6038</a>.
Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Morton & Ciavattone Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6038">RFC 6038</a> Reflect Octets & Symmetric Size October 2010</span>
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a>
<a href="#section-2">2</a>. Requirements Language ...........................................<a href="#page-3">3</a>
<a href="#section-3">3</a>. Purpose and Scope ...............................................<a href="#page-4">4</a>
<a href="#section-4">4</a>. TWAMP Control Extensions ........................................<a href="#page-4">4</a>
<a href="#section-4.1">4.1</a>. Connection Setup with New Features .........................<a href="#page-5">5</a>
<a href="#section-4.2">4.2</a>. Reflect Octets: Request-TW-Session Packet Format ...........<a href="#page-6">6</a>
<a href="#section-4.3">4.3</a>. Reflect Octets: Accept Session Packet Format ...............<a href="#page-7">7</a>
<a href="#section-4.4">4.4</a>. Additional Considerations ..................................<a href="#page-9">9</a>
<a href="#section-5">5</a>. Extended TWAMP Test .............................................<a href="#page-9">9</a>
<a href="#section-5.1">5.1</a>. Sender Behavior ............................................<a href="#page-9">9</a>
<a href="#section-5.1.1">5.1.1</a>. Packet Timings ......................................<a href="#page-9">9</a>
<a href="#section-5.1.2">5.1.2</a>. Reflect Octets: Packet Formats and Contents .........<a href="#page-9">9</a>
5.1.3. Reflect Octets: Interaction with Padding
Truncation .........................................<a href="#page-11">11</a>
<a href="#section-5.1.4">5.1.4</a>. Symmetrical Size: Session-Sender Packet Format .....<a href="#page-13">13</a>
5.1.5. Symmetrical Size AND Reflect Octets:
Session-Sender Packet ..............................<a href="#page-14">14</a>
<a href="#section-5.2">5.2</a>. Reflector Behavior ........................................<a href="#page-14">14</a>
5.2.1. Reflect Octets: Session-Reflector Packet
Format and Contents ................................<a href="#page-15">15</a>
<a href="#section-5.2.2">5.2.2</a>. Symmetrical Size: Session-Reflector Packet Format ..16
5.2.3. Symmetrical Size AND Reflect Octets:
Session-Sender Packet Format .......................<a href="#page-16">16</a>
<a href="#section-6">6</a>. Security Considerations ........................................<a href="#page-17">17</a>
<a href="#section-7">7</a>. IANA Considerations ............................................<a href="#page-17">17</a>
<a href="#section-7.1">7.1</a>. Registry Specification ....................................<a href="#page-17">17</a>
<a href="#section-7.2">7.2</a>. Registry Contents .........................................<a href="#page-17">17</a>
<a href="#section-8">8</a>. Acknowledgements ...............................................<a href="#page-17">17</a>
<a href="#section-9">9</a>. Normative References ...........................................<a href="#page-18">18</a>
<span class="grey">Morton & Ciavattone Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6038">RFC 6038</a> Reflect Octets & Symmetric Size October 2010</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The Two-Way Active Measurement Protocol (TWAMP) [<a href="./rfc5357" title=""A Two-Way Active Measurement Protocol (TWAMP)"">RFC5357</a>] is an
extension of the One-way Active Measurement Protocol (OWAMP)
[<a href="./rfc4656" title=""A One-way Active Measurement Protocol (OWAMP)"">RFC4656</a>]. The TWAMP specification gathered wide review as it
approached completion, and the by-products were several
recommendations for new features in TWAMP.
This memo describes two closely related features for TWAMP.
One is the OPTIONAL capability for the responder host to return a
limited number of unassigned (padding) octets to the Control-Client
or Session-Sender entities in both the TWAMP-Control and TWAMP-Test
protocols. With this capability, the Control-Client or Session-
Sender can embed octets of information it deems useful and have the
assurance that the corresponding reply/test packet will contain that
information when it is reflected and returned (by the Server or
Session-Reflector).
The memo also adds an OPTIONAL capability to ensure that reflected
test packets are the same size in both directions of transmission.
This is accomplished by specifying a new TWAMP-Test Session-Sender
packet format. Although TWAMP [<a href="./rfc5357" title=""A Two-Way Active Measurement Protocol (TWAMP)"">RFC5357</a>] recommends padding
truncation to achieve symmetrical sizes (to compensate for the
Session-Reflector's larger test packet header), it's not guaranteed
that the Session-Reflector will truncate the padding, and it's not
possible if there's insufficient padding.
This memo is an update to the TWAMP core protocol specified in
[<a href="./rfc5357" title=""A Two-Way Active Measurement Protocol (TWAMP)"">RFC5357</a>]. Measurement systems are not required to implement the
features described in this memo to claim compliance with [<a href="./rfc5357" title=""A Two-Way Active Measurement Protocol (TWAMP)"">RFC5357</a>].
Throughout this memo, the bits marked MBZ (Must Be Zero) MUST be set
to zero by senders and MUST be ignored by receivers. Also, the HMAC
(Hashed Message Authentication Code) MUST be calculated as defined in
<a href="./rfc4656#section-3.2">Section 3.2 of [RFC4656]</a>.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Requirements Language</span>
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="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="grey">Morton & Ciavattone Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6038">RFC 6038</a> Reflect Octets & Symmetric Size October 2010</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Purpose and Scope</span>
The purpose of this memo is to define two OPTIONAL closely related
features for TWAMP [<a href="./rfc5357" title=""A Two-Way Active Measurement Protocol (TWAMP)"">RFC5357</a>]. The features enhance the TWAMP host's
capabilities to perform a simple operation on control and test
packets: the reflection of octets or padding, and the capability to
ensure symmetrical size TWAMP-Test packets. Motivations include
permitting the controller host to tag packets with an index for
simplified identification, and/or assert that the same size test
packets will be used in each direction.
The scope of the memo is limited to specifications of the following
features:
o Reflect Octets: the capability of the Server/Session-Reflector to
reflect specific octets back to the Client/Session-Sender, and a
similar service provided by the Client and Session-Sender.
o Symmetrical Size: the capability to ensure that TWAMP-Test
protocol uses the same packet size in both directions through
support of a new TWAMP-Test Session-Sender test packet format in
both the Session-Sender and the Session-Reflector. Only the
Session-Sender test packet format is new.
This memo extends the modes of operation through assignment of two
new values in the Modes field (see <a href="./rfc4656#section-3.1">Section 3.1 of [RFC4656]</a> for the
format of the Server Greeting message), while retaining backward
compatibility with the core TWAMP [<a href="./rfc5357" title=""A Two-Way Active Measurement Protocol (TWAMP)"">RFC5357</a>] implementations. The two
new values correspond to the two features defined in this memo.
When the Server and Control-Client have agreed to use the Reflect
Octets mode during control connection setup, then the Control-Client,
the Server, the Session-Sender, and the Session-Reflector MUST all
conform to the requirements of that mode, as identified below.
When the Server and Control-Client have agreed to use the Symmetrical
Size mode during control connection setup, then the Control-Client,
the Server, the Session-Sender, and the Session-Reflector MUST all
conform to the requirements of that mode, as identified below.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. TWAMP Control Extensions</span>
TWAMP-Control protocol [<a href="./rfc5357" title=""A Two-Way Active Measurement Protocol (TWAMP)"">RFC5357</a>] uses the Modes field to identify and
select specific communication capabilities, and this field is a
recognized extension mechanism. The following sections describe two
such extensions.
<span class="grey">Morton & Ciavattone Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6038">RFC 6038</a> Reflect Octets & Symmetric Size October 2010</span>
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Connection Setup with New Features</span>
TWAMP connection establishment follows the procedure defined in
<a href="./rfc4656#section-3.1">Section 3.1 of [RFC4656]</a> and <a href="./rfc5357#section-3.1">Section 3.1 of [RFC5357]</a>. The new
features require two new bit positions (and values) to identify the
ability of the Server/Session-Reflector to reflect specific octets
back to the Control-Client/Session-Sender, and to support the new
Session-Sender packet format in the TWAMP-Test protocol. See the
IANA section for details on the assigned values and bit positions.
The Server sets one or both of the new bit positions in the Modes
field of the Server Greeting message to indicate its capabilities and
willingness to operate in either of these modes (or both) if desired.
If the Control-Client intends to operate all test sessions invoked
with this control connection using one or both of the new modes, it
MUST set the Mode field bit corresponding to each function in the
Setup Response message. With this and other extensions, the Control-
Client MAY set multiple Mode field bits in the Setup Response
message.
<span class="grey">Morton & Ciavattone Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6038">RFC 6038</a> Reflect Octets & Symmetric Size October 2010</span>
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Reflect Octets: Request-TW-Session Packet Format</span>
The bits designated for the Reflect Octets feature in the Request-TW-
Session command are as shown in the packet format below.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 5 | MBZ | IPVN | Conf-Sender | Conf-Receiver |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of Schedule Slots |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. ... Many fields (66 octets) not shown ... .
. .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Padding Length (4 octets) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Start Time (8 octets) |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timeout (8 octets) |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type-P Descriptor |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Octets to be reflected | Length of padding to reflect |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MBZ (4 octets) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| HMAC (16 octets) |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
It is important to note that the Padding Length field continues to
specify the number of padding octets that the Session-Sender will
append to ALL TWAMP-Test packets associated with this test session.
See below for considerations on the minimum length of the padding
octets following the definitions of the two new fields that follow
the Type-P Descriptor.
Note that the number of padding octets appended to the Session-
Reflector's test packet depends on support for the truncation process
that TWAMP recommends, see <a href="./rfc5357#section-4.2.1">Section 4.2.1 of [RFC5357]</a>.
<span class="grey">Morton & Ciavattone Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6038">RFC 6038</a> Reflect Octets & Symmetric Size October 2010</span>
The Octets to be reflected field SHALL be 2 octets long, as shown,
and contain the octets that the Server MUST reflect in the Accept
Session message as specified below.
The Length of padding to reflect field SHALL be 2 octets long and
contain an unsigned binary value in units of octets. This field
communicates the length of the padding in the TWAMP-Test Packet that
the Session-Sender expects to be reflected and the length of octets
that the Session-Reflector SHALL return in its TWAMP-Test packet
format (see <a href="#section-5.2">Section 5.2</a>). By including this length field in the
Request-TW-Session message, a Server is able to determine if it can
comply with a specific request to reflect padding in the TWAMP-Test
packets and to arrange for the Session-Reflector processing in
advance.
The Padding Length SHOULD be >= 27 octets when specifying a test
session using the Unauthenticated TWAMP-Test mode to allow for the
truncation process that TWAMP recommends, see <a href="./rfc5357#section-4.2.1">Section 4.2.1 of
[RFC5357]</a>.
The Padding Length SHOULD be >= 56 octets when specifying a test
session using the Authenticated or Encrypted TWAMP-Test modes to
allow for the truncation process that TWAMP recommends, see <a href="./rfc5357#section-4.2.1">Section</a>
<a href="./rfc5357#section-4.2.1">4.2.1 of [RFC5357]</a>.
The Padding Length SHALL be > the Length of padding to reflect when
specifying a test session using the OPTIONAL Reflect Octets mode.
In Unauthenticated TWAMP-Test mode, the Padding Length SHALL be >= 27
+ Length of padding to reflect octets when specifying a test session
using both the OPTIONAL Reflect Octets mode and the truncation
process that TWAMP recommends, see <a href="./rfc5357#section-4.2.1">Section 4.2.1 of [RFC5357]</a>.
In Authenticated or Encrypted TWAMP-Test modes, the Padding Length
SHALL be >= 56 + Length of padding to reflect octets when specifying
a test session using both the OPTIONAL Reflect Octets mode and the
truncation process that TWAMP recommends, see <a href="./rfc5357#section-4.2.1">Section 4.2.1 of
[RFC5357]</a>.
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Reflect Octets: Accept Session Packet Format</span>
The bits designated for the Reflect Padding feature in the Accept
Session command are as shown in the packet format below.
<span class="grey">Morton & Ciavattone Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc6038">RFC 6038</a> Reflect Octets & Symmetric Size October 2010</span>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Accept | MBZ | Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
| |
| SID (16 octets) |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reflected octets | Server octets |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MBZ (8 octets) |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| HMAC (16 octets) |
| |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Reflected octets field SHALL contain the octets from the Request-
TW-Session Octets to be reflected field and be 2 octets long, as
shown.
The Server octets field SHALL contain information that the Server
intends to be returned in the TWAMP-Test Packet Padding (to be
reflected) field, OR SHALL be zero, and be 2 octets long, as shown.
Although the Server determines the SID, this field is very long (16
octets) and does not normally appear in TWAMP-Test packets. The
following items MUST be part of compliant implementations using the
Reflect Octets feature:
o When a Server does not require octets to be returned in TWAMP-Test
packets, it MUST send all zeros in the Server octets field.
o When a Server intends octets to be returned in TWAMP-Test packets,
it MUST send a non-zero value in the Server octets field, and the
TWAMP-Test Sender MUST include those octets at the beginning of
the Packet Padding (to be reflected) field.
o <a href="#section-4.1.2">Section 4.1.2</a> defines how Server octets MUST be included in the
TWAMP-Test packet padding when this service is desired by the
Server (indicated in the second of two figures in this section).
<span class="grey">Morton & Ciavattone Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc6038">RFC 6038</a> Reflect Octets & Symmetric Size October 2010</span>
When performing the truncation process that TWAMP recommends, see
<a href="./rfc5357#section-4.2.1">Section 4.2.1 of [RFC5357]</a>, if calculations on the Padding lengths
reveal that there are insufficient octets supplied to produce equal-
length Session-Sender and Session-Reflector test packets, then the
Accept field MUST be set to 3 to indicate that some aspect of the
request is not supported.
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. Additional Considerations</span>
The value of the Modes field sent by the Server in the Server
Greeting message is the bit-wise OR of the mode values that it is
willing to support during this session.
With the publication of this memo as an RFC, the last 7 bit positions
of the Modes 32-bit field are used. A Control-Client conforming to
this extension of [<a href="./rfc5357" title=""A Two-Way Active Measurement Protocol (TWAMP)"">RFC5357</a>] MAY ignore the values in the higher bits
of the Modes field, or it MAY support other features that are
communicated in those bit positions. The other bits are available
for future protocol extensions.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Extended TWAMP Test</span>
The TWAMP-Test protocol is similar to the OWAMP [<a href="./rfc4656" title=""A One-way Active Measurement Protocol (OWAMP)"">RFC4656</a>] test
protocol with the exception that the Session-Reflector transmits test
packets to the Session-Sender in response to each test packet it
receives. TWAMP, see <a href="./rfc5357#section-4">Section 4 of [RFC5357]</a>, defines two additional
test packet formats for packets transmitted by the Session-Reflector.
The appropriate format depends on the security mode chosen. The new
modes specified here utilize some of the padding octets within each
test packet format or require truncation of those octets depending on
the security mode in use.
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Sender Behavior</span>
This section describes extensions to the behavior of the TWAMP
Session-Sender.
<span class="h4"><a class="selflink" id="section-5.1.1" href="#section-5.1.1">5.1.1</a>. Packet Timings</span>
The Send Schedule is not utilized in TWAMP, and this is unchanged in
this memo.
<span class="h4"><a class="selflink" id="section-5.1.2" href="#section-5.1.2">5.1.2</a>. Reflect Octets: Packet Formats and Contents</span>
The Session-Sender packet format and content follow the same
procedure and guidelines as defined in <a href="./rfc4656#section-4.1.2">Section 4.1.2 of [RFC4656]</a> (as
indicated in <a href="./rfc5357#section-4.1.2">Section 4.1.2 of [RFC5357]</a>).
<span class="grey">Morton & Ciavattone Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc6038">RFC 6038</a> Reflect Octets & Symmetric Size October 2010</span>
The Reflect Octets mode re-designates the original TWAMP-Test Packet
Padding field (see <a href="./rfc4656#section-4.1.2">Section 4.1.2 of [RFC4656]</a>), as shown below for
Unauthenticated mode:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Estimate | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
| Packet Padding (to be reflected) |
. (length in octets specified in command) .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. Additional Packet Padding .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Packet Padding (to be reflected) field SHALL correspond to the
length of octets specified in the Request-TW-Session Length of
padding to reflect field to this test session. These are the octets
that the Session-Sender expects will be returned by the Session-
Reflector.
The length of the Additional Packet Padding field is the difference
between two fields in the Request-TW-Session command, as follows:
Additional Packet Padding, in octets =
Padding Length - Length of padding to reflect
When a Server intends octets to be returned in TWAMP-Test packets, it
MUST send a non-zero value in the Server octets field, and the TWAMP-
Test Session-Sender MUST include those octets in the first 2 octets
of the Packet Padding (to be reflected) field as shown below:
<span class="grey">Morton & Ciavattone Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc6038">RFC 6038</a> Reflect Octets & Symmetric Size October 2010</span>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Server octets |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
| Remaining Packet Padding (to be reflected) |
. (total length in octets specified in command) .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Server octets field contains the same information that the Server
returned to the Control-Client in the Accept-Session message
corresponding to this specific test session (see <a href="#section-4.3">Section 4.3</a>). At
the Session-Reflector, these octets MUST be reflected the same as the
rest of the Packet Padding (to be reflected) field.
Note that it is permissible for the Session-Sender to insert the same
octets used in the Octets to be reflected field of the Request-TW-
Session command elsewhere in the Packet Padding (to be reflected)
field.
<span class="h4"><a class="selflink" id="section-5.1.3" href="#section-5.1.3">5.1.3</a>. Reflect Octets: Interaction with Padding Truncation</span>
When the Reflect Octets mode is selected, and performing the
truncation process that TWAMP recommends, see <a href="./rfc5357#section-4.2.1">Section 4.2.1 of
[RFC5357]</a>, the Session-Sender MUST anticipate a minimum padding
required to achieve equal-size test packets in both directions. The
amount of padding needed to achieve symmetrical packet size depends
on both the security mode (Unauthenticated/Authenticated/Encrypted)
and whether the Reflect Octets mode is selected simultaneously.
When using the truncation process in TWAMP alone, see <a href="./rfc5357#section-4.2.1">Section 4.2.1
of [RFC5357]</a>, the Session-Sender MUST append sufficient Packet
Padding octets to allow the same IP packet payload lengths to be used
in each direction of transmission (this is usually desirable). To
compensate for the Session-Reflector's larger test packet format, the
Session-Sender MUST append at least 27 octets of padding in
Unauthenticated mode, and at least 56 octets in Authenticated and
Encrypted modes. The sizes of TWAMP-Test protocol packets and the
resulting truncated padding to achieve equal packet sizes in both
directions are shown in the table below:
<span class="grey">Morton & Ciavattone Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc6038">RFC 6038</a> Reflect Octets & Symmetric Size October 2010</span>
+-------------------+----------------------+---------------------+
| Octets in: | Unauthenticated Mode | Auth/Encrypted Mode |
+-------------------+----------------------+---------------------+
| Reflector Header | 41 | 104 |
| Sender Header | 14 | 48 |
| Truncated Padding | 27 | 56 |
+-------------------+----------------------+---------------------+
TWAMP-Test Padding Truncation
When using the Reflect Octets mode simultaneously with the truncation
process that TWAMP recommends in <a href="./rfc5357#section-4.2.1">Section 4.2.1 of [RFC5357]</a>, the
Session-Sender MUST append at least 27 octets of padding plus the
Length of the padding to reflect octets when operating in
Unauthenticated mode. The Session-Sender MUST append at least 56
octets of padding plus the Length of the padding to reflect octets
when operating in Authenticated and Encrypted modes.
<span class="grey">Morton & Ciavattone Standards Track [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc6038">RFC 6038</a> Reflect Octets & Symmetric Size October 2010</span>
<span class="h4"><a class="selflink" id="section-5.1.4" href="#section-5.1.4">5.1.4</a>. Symmetrical Size: Session-Sender Packet Format</span>
When the Symmetrical Size mode is selected, the Session-Sender SHALL
use the following TWAMP-Test Packet Format in Unauthenticated mode:
Unauthenticated Mode
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Estimate | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
| |
| MBZ (27 octets) |
| |
| |
| |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+ +
. .
. Packet Padding .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This feature REQUIRES only a new Session-Sender test packet format,
the Session-Reflector test packet format is unchanged.
<span class="grey">Morton & Ciavattone Standards Track [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc6038">RFC 6038</a> Reflect Octets & Symmetric Size October 2010</span>
<span class="h4"><a class="selflink" id="section-5.1.5" href="#section-5.1.5">5.1.5</a>. Symmetrical Size AND Reflect Octets: Session-Sender Packet</span>
<span class="h4"> Format</span>
When both the Symmetrical Size mode and the Reflect Octets mode are
selected, the Session-Sender SHALL use the following TWAMP-Test
Packet Format in Unauthenticated mode:
Unauthenticated Mode
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Estimate | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
| |
| MBZ (27 octets) |
| |
| |
| |
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | |
+-+-+-+-+-+-+-+-+ +
| Packet Padding (to be reflected) |
. (length in octets specified in command) .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. Additional Packet Padding .
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
In this combined mode, the Packet Padding to be reflected follows the
27 MBZ octets. In Authenticated or Encrypted modes, the Packet
Padding to be reflected follows the 56 MBZ octets.
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Reflector Behavior</span>
The TWAMP Reflector follows the procedures and guidelines in <a href="./rfc5357#section-4.2">Section</a>
<a href="./rfc5357#section-4.2">4.2 of [RFC5357]</a>, with the following additional functions:
o Reflect Octets mode: Designated octets in the Packet Padding (to
be reflected) field of the Session-Sender's test packet MUST be
included in the Session-Reflector's test packet.
<span class="grey">Morton & Ciavattone Standards Track [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc6038">RFC 6038</a> Reflect Octets & Symmetric Size October 2010</span>
o Symmetrical Size mode: The Session-Reflector MUST operate using
the Session_Reflector Packet Format defined in <a href="#section-5.1.4">Section 5.1.4</a>,
where the Padding Octets are separated from the information
fields.
<span class="h4"><a class="selflink" id="section-5.2.1" href="#section-5.2.1">5.2.1</a>. Reflect Octets: Session-Reflector Packet Format and Contents</span>
The Reflect Padding feature re-designates the Packet Padding field,
as shown below. When the Reflect Octets mode is selected, the
Session-Sender SHALL use the following TWAMP-Test Packet Format in
Unauthenticated mode:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Error Estimate | MBZ |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Receive Timestamp |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender Timestamp |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender Error Estimate | MBZ |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sender TTL | Packet Padding (from Session-Sender) |
+-+-+-+-+-+-+-+-+ +
. .
+ +-+-+-+-+-+-+-+-+
| Packet Padding (from Session-Sender) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| |
| |
. Additional Packet Padding .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Packet Padding (from Session-Sender) field MUST be the same
octets as the Packet Padding (to be reflected) field in the Session-
Sender's test packet, and therefore MUST conform to the length
specified in the Request-TW-Session message.
<span class="grey">Morton & Ciavattone Standards Track [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc6038">RFC 6038</a> Reflect Octets & Symmetric Size October 2010</span>
When the Server has returned a non-zero value in the Server octets
field of the Accept Session message (as described in <a href="#section-4.3">Section 4.3</a>),
then the Session-Reflector SHALL reflect these octets the same as the
rest of the Packet Padding (to be reflected) field.
<a href="./rfc5357#section-4.2.1">Section 4.2.1 of [RFC5357]</a> recommends a padding truncation process
for use in TWAMP. When using that process in conjunction with the
Reflect Octets mode, the Session-Reflector MUST reflect the
designated octets from the Session-Sender's test packet in the Packet
Padding (from Session-Sender) field, and MAY re-use additional Packet
Padding from the Session-Sender. The Session-Reflector MUST truncate
the padding such that the highest number octets are discarded, and
the test packet length equals the Session-Sender's packet length.
When using the recommended truncation process, the Session-Reflector
MUST truncate exactly 27 octets of padding in Unauthenticated mode,
and exactly 56 octets in Authenticated and Encrypted modes.
In any case, the Session-Reflector MAY re-use the Sender's Packet
Padding (since the requirements for padding generation are the same
for each).
<span class="h4"><a class="selflink" id="section-5.2.2" href="#section-5.2.2">5.2.2</a>. Symmetrical Size: Session-Reflector Packet Format</span>
When Symmetrical Size mode is selected, the Session-Reflector packet
formats for Unauthenticated and Authenticated/Encrypted modes are
identical to the core TWAMP specification, see <a href="./rfc5357#section-4.2.1">Section 4.2.1 of
[RFC5357]</a>. Thus, the Session-Reflector test packet format is
unchanged.
The Session-Reflector MUST construct its test packet using the
information in the Session-Sender's test packet. The length of the
Session-Reflector's test packet SHALL equal the length of the
Session-Sender's test packet.
<span class="h4"><a class="selflink" id="section-5.2.3" href="#section-5.2.3">5.2.3</a>. Symmetrical Size AND Reflect Octets: Session-Sender Packet</span>
<span class="h4"> Format</span>
When both the Symmetrical Size mode and the Reflect Octets mode are
selected, the Session-Reflector MUST operate using the Session-Sender
Packet Format defined in <a href="#section-5.1.5">Section 5.1.5</a>, where the Padding Octets are
separated from the information fields, and the Packet Padding (to be
reflected) field precedes the Additional Padding.
The Session-Reflector SHALL use the same TWAMP-Test Packet Format as
specified in <a href="#section-5.2.1">Section 5.2.1</a>, above.
<span class="grey">Morton & Ciavattone Standards Track [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc6038">RFC 6038</a> Reflect Octets & Symmetric Size October 2010</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
These extended modes of operation do not appear to permit any new
attacks on hosts communicating with core TWAMP [<a href="./rfc5357" title=""A Two-Way Active Measurement Protocol (TWAMP)"">RFC5357</a>].
The security considerations that apply to any active measurement of
live networks are relevant here as well. See [<a href="./rfc4656" title=""A One-way Active Measurement Protocol (OWAMP)"">RFC4656</a>] and
[<a href="./rfc5357" title=""A Two-Way Active Measurement Protocol (TWAMP)"">RFC5357</a>].
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span>
This memo adds two modes to the IANA registry for the TWAMP Modes
field, and describes behavior when the new modes are used. This
field is a recognized extension mechanism for TWAMP.
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Registry Specification</span>
IANA has created a TWAMP-Modes registry (as requested in [<a href="./rfc5618" title=""Mixed Security Mode for the Two-Way Active Measurement Protocol (TWAMP)"">RFC5618</a>]).
TWAMP-Modes are specified in TWAMP Server Greeting messages and Setup
Response messages, as described in <a href="./rfc5357#section-3.1">Section 3.1 of [RFC5357]</a>,
consistent with <a href="./rfc4656#section-3.1">Section 3.1 of [RFC4656]</a>, and extended by this memo.
Modes are indicated by setting bits in the 32-bit Modes field that
correspond to values in the Modes registry. For the TWAMP-Modes
registry, we expect that new features will be assigned increasing
registry values that correspond to single bit positions, unless there
is a good reason to do otherwise (more complex encoding than single-
bit positions may be used in the future to access the 2^32 value
space).
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Registry Contents</span>
The TWAMP-Modes registry has been augmented as follows:
Value Description Semantics Definition
--------------------------------------------------------
32 Reflect Octets this memo, <a href="#section-3.1">Section 3.1</a>
Capability new bit position (5)
64 Symmetrical Size this memo, <a href="#section-3.1">Section 3.1</a>
Sender Test Packet Format new bit position (6)
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgements</span>
The authors thank Steve Baillargeon, Walt Steverson, and Stina Ross
for helpful review and comments.
<span class="grey">Morton & Ciavattone Standards Track [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc6038">RFC 6038</a> Reflect Octets & Symmetric Size October 2010</span>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</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-RFC4656">RFC4656</a>] Shalunov, S., Teitelbaum, B., Karp, A., Boote, J., and M.
Zekauskas, "A One-way Active Measurement Protocol
(OWAMP)", <a href="./rfc4656">RFC 4656</a>, September 2006.
[<a id="ref-RFC5357">RFC5357</a>] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J.
Babiarz, "A Two-Way Active Measurement Protocol (TWAMP)",
<a href="./rfc5357">RFC 5357</a>, October 2008.
[<a id="ref-RFC5618">RFC5618</a>] Morton, A. and K. Hedayat, "Mixed Security Mode for the
Two-Way Active Measurement Protocol (TWAMP)", <a href="./rfc5618">RFC 5618</a>,
August 2009.
Authors' Addresses
Al Morton
AT&T Labs
200 Laurel Avenue South
Middletown, NJ 07748
USA
Phone: +1 732 420 1571
Fax: +1 732 368 1192
EMail: acmorton@att.com
URI: <a href="http://home.comcast.net/~acmacm/">http://home.comcast.net/~acmacm/</a>
Len Ciavattone
AT&T Labs
200 Laurel Avenue South
Middletown, NJ 07748
USA
Phone: +1 732 420 1239
EMail: lencia@att.com
Morton & Ciavattone Standards Track [Page 18]
</pre>
|
