Debian Codegraph @

rfc8688.html

raw
1 <!DOCTYPE html>
2 <html lang="en" class="RFC">
3 <head>
4 <meta charset="utf-8">
5 <meta content="Common,Latin" name="scripts">
6 <meta content="initial-scale=1.0" name="viewport">
7 <title>RFC 8688: A Session Initiation Protocol (SIP) Response Code for Rejected Calls</title>
8 <meta content="Eric W. Burger" name="author">
9 <meta content="Bhavik Nagda" name="author">
10 <meta content="
11 This document defines the 608 (Rejected) Session Initiation Protocol
12 (SIP) response code. This response code enables calling parties to learn
13 that an intermediary rejected their call attempt. No one will deliver,
14 and thus answer, the call. As a 6xx code, the caller will be aware that
15 future attempts to contact the same User Agent Server will likely fail.
16 The initial use case driving the need for the 608 response code is when
17 the intermediary is an analytics engine. In this case, the rejection is
18 by a machine or other process. This contrasts with the 607 (Unwanted)
19 SIP response code in which a human at the target User Agent Server
20 indicates the user did not want the call. In some jurisdictions, this
21 distinction is important. This document also defines the use of the
22 Call-Info header field in 608 responses to enable rejected callers to
23 contact entities that blocked their calls in error. This provides a
24 remediation mechanism for legal callers that find their calls
25 blocked.
26 " name="description">
27 <meta content="xml2rfc 2.35.0" name="generator">
28 <meta content="STIR" name="keyword">
29 <meta content="SIPCORE" name="keyword">
30 <meta content="IANA" name="keyword">
31 <meta content="8688" name="rfc.number">
32 <link href="rfc8688.xml" type="application/rfc+xml" rel="alternate">
33 <link href="#copyright" rel="license">
34 <style type="text/css">/*
35
36 NOTE: Changes at the bottom of this file overrides some earlier settings.
37
38 Once the style has stabilized and has been adopted as an official RFC style,
39 this can be consolidated so that style settings occur only in one place, but
40 for now the contents of this file consists first of the initial CSS work as
41 provided to the RFC Formatter (xml2rfc) work, followed by itemized and
42 commented changes found necssary during the development of the v3
43 formatters.
44
45 */
46
47 /* fonts */
48 @import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
49 @import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
50 @import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */
51
52 @viewport {
53 zoom: 1.0;
54 width: extend-to-zoom;
55 }
56 @-ms-viewport {
57 width: extend-to-zoom;
58 zoom: 1.0;
59 }
60 /* general and mobile first */
61 html {
62 }
63 body {
64 max-width: 90%;
65 margin: 1.5em auto;
66 color: #222;
67 background-color: #fff;
68 font-size: 14px;
69 font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
70 line-height: 1.6;
71 scroll-behavior: smooth;
72 }
73 .ears {
74 display: none;
75 }
76
77 /* headings */
78 #title, h1, h2, h3, h4, h5, h6 {
79 margin: 1em 0 0.5em;
80 font-weight: bold;
81 line-height: 1.3;
82 }
83 #title {
84 clear: both;
85 border-bottom: 1px solid #ddd;
86 margin: 0 0 0.5em 0;
87 padding: 1em 0 0.5em;
88 }
89 .author {
90 padding-bottom: 4px;
91 }
92 h1 {
93 font-size: 26px;
94 margin: 1em 0;
95 }
96 h2 {
97 font-size: 22px;
98 margin-top: -20px; /* provide offset for in-page anchors */
99 padding-top: 33px;
100 }
101 h3 {
102 font-size: 18px;
103 margin-top: -36px; /* provide offset for in-page anchors */
104 padding-top: 42px;
105 }
106 h4 {
107 font-size: 16px;
108 margin-top: -36px; /* provide offset for in-page anchors */
109 padding-top: 42px;
110 }
111 h5, h6 {
112 font-size: 14px;
113 }
114 #n-copyright-notice {
115 border-bottom: 1px solid #ddd;
116 padding-bottom: 1em;
117 margin-bottom: 1em;
118 }
119 /* general structure */
120 p {
121 padding: 0;
122 margin: 0 0 1em 0;
123 text-align: left;
124 }
125 div, span {
126 position: relative;
127 }
128 div {
129 margin: 0;
130 }
131 .alignRight.art-text {
132 background-color: #f9f9f9;
133 border: 1px solid #eee;
134 border-radius: 3px;
135 padding: 1em 1em 0;
136 margin-bottom: 1.5em;
137 }
138 .alignRight.art-text pre {
139 padding: 0;
140 }
141 .alignRight {
142 margin: 1em 0;
143 }
144 .alignRight > *:first-child {
145 border: none;
146 margin: 0;
147 float: right;
148 clear: both;
149 }
150 .alignRight > *:nth-child(2) {
151 clear: both;
152 display: block;
153 border: none;
154 }
155 svg {
156 display: block;
157 }
158 .alignCenter.art-text {
159 background-color: #f9f9f9;
160 border: 1px solid #eee;
161 border-radius: 3px;
162 padding: 1em 1em 0;
163 margin-bottom: 1.5em;
164 }
165 .alignCenter.art-text pre {
166 padding: 0;
167 }
168 .alignCenter {
169 margin: 1em 0;
170 }
171 .alignCenter > *:first-child {
172 border: none;
173 /* this isn't optimal, but it's an existence proof. PrinceXML doesn't
174 support flexbox yet.
175 */
176 display: table;
177 margin: 0 auto;
178 }
179
180 /* lists */
181 ol, ul {
182 padding: 0;
183 margin: 0 0 1em 2em;
184 }
185 ol ol, ul ul, ol ul, ul ol {
186 margin-left: 1em;
187 }
188 li {
189 margin: 0 0 0.25em 0;
190 }
191 .ulCompact li {
192 margin: 0;
193 }
194 ul.empty, .ulEmpty {
195 list-style-type: none;
196 }
197 ul.empty li, .ulEmpty li {
198 margin-top: 0.5em;
199 }
200 ul.compact, .ulCompact,
201 ol.compact, .olCompact {
202 line-height: 100%;
203 margin: 0 0 0 2em;
204 }
205
206 /* definition lists */
207 dl {
208 }
209 dl > dt {
210 float: left;
211 margin-right: 1em;
212 }
213 /*
214 dl.nohang > dt {
215 float: none;
216 }
217 */
218 dl > dd {
219 margin-bottom: .8em;
220 min-height: 1.3em;
221 }
222 dl.compact > dd, .dlCompact > dd {
223 margin-bottom: 0em;
224 }
225 dl > dd > dl {
226 margin-top: 0.5em;
227 margin-bottom: 0em;
228 }
229
230 /* links */
231 a {
232 text-decoration: none;
233 }
234 a[href] {
235 color: #22e; /* Arlen: WCAG 2019 */
236 }
237 a[href]:hover {
238 background-color: #f2f2f2;
239 }
240 figcaption a[href],
241 a[href].selfRef {
242 color: #222;
243 }
244 /* XXX probably not this:
245 a.selfRef:hover {
246 background-color: transparent;
247 cursor: default;
248 } */
249
250 /* Figures */
251 tt, code, pre, code {
252 background-color: #f9f9f9;
253 font-family: 'Roboto Mono', monospace;
254 }
255 pre {
256 border: 1px solid #eee;
257 margin: 0;
258 padding: 1em;
259 }
260 img {
261 max-width: 100%;
262 }
263 figure {
264 margin: 0;
265 }
266 figure blockquote {
267 margin: 0.8em 0.4em 0.4em;
268 }
269 figcaption {
270 font-style: italic;
271 margin: 0 0 1em 0;
272 }
273 @media screen {
274 pre {
275 overflow-x: auto;
276 max-width: 100%;
277 max-width: calc(100% - 22px);
278 }
279 }
280
281 /* aside, blockquote */
282 aside, blockquote {
283 margin-left: 0;
284 padding: 1.2em 2em;
285 }
286 blockquote {
287 background-color: #f9f9f9;
288 color: #111; /* Arlen: WCAG 2019 */
289 border: 1px solid #ddd;
290 border-radius: 3px;
291 margin: 1em 0;
292 }
293 cite {
294 display: block;
295 text-align: right;
296 font-style: italic;
297 }
298
299 /* tables */
300 table {
301 width: 100%;
302 margin: 0 0 1em;
303 border-collapse: collapse;
304 border: 1px solid #eee;
305 }
306 th, td {
307 text-align: left;
308 vertical-align: top;
309 padding: 0.5em 0.75em;
310 }
311 th {
312 text-align: left;
313 background-color: #e9e9e9;
314 }
315 tr:nth-child(2n+1) > td {
316 background-color: #f5f5f5;
317 }
318 table caption {
319 font-style: italic;
320 margin: 0;
321 padding: 0;
322 text-align: left;
323 }
324 table p {
325 /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
326 be allowed within tables more generally, it would be far better to select on a class. */
327 margin: 0;
328 }
329
330 /* pilcrow */
331 a.pilcrow {
332 color: #666; /* Arlen: AHDJ 2019 */
333 text-decoration: none;
334 visibility: hidden;
335 user-select: none;
336 -ms-user-select: none;
337 -o-user-select:none;
338 -moz-user-select: none;
339 -khtml-user-select: none;
340 -webkit-user-select: none;
341 -webkit-touch-callout: none;
342 }
343 @media screen {
344 aside:hover > a.pilcrow,
345 p:hover > a.pilcrow,
346 blockquote:hover > a.pilcrow,
347 div:hover > a.pilcrow,
348 li:hover > a.pilcrow,
349 pre:hover > a.pilcrow {
350 visibility: visible;
351 }
352 a.pilcrow:hover {
353 background-color: transparent;
354 }
355 }
356
357 /* misc */
358 hr {
359 border: 0;
360 border-top: 1px solid #eee;
361 }
362 .bcp14 {
363 font-variant: small-caps;
364 }
365
366 .role {
367 font-variant: all-small-caps;
368 }
369
370 /* info block */
371 #identifiers {
372 margin: 0;
373 font-size: 0.9em;
374 }
375 #identifiers dt {
376 width: 3em;
377 clear: left;
378 }
379 #identifiers dd {
380 float: left;
381 margin-bottom: 0;
382 }
383 #identifiers .authors .author {
384 display: inline-block;
385 margin-right: 1.5em;
386 }
387 #identifiers .authors .org {
388 font-style: italic;
389 }
390
391 /* The prepared/rendered info at the very bottom of the page */
392 .docInfo {
393 color: #666; /* Arlen: WCAG 2019 */
394 font-size: 0.9em;
395 font-style: italic;
396 margin-top: 2em;
397 }
398 .docInfo .prepared {
399 float: left;
400 }
401 .docInfo .prepared {
402 float: right;
403 }
404
405 /* table of contents */
406 #toc {
407 padding: 0.75em 0 2em 0;
408 margin-bottom: 1em;
409 }
410 nav.toc ul {
411 margin: 0 0.5em 0 0;
412 padding: 0;
413 list-style: none;
414 }
415 nav.toc li {
416 line-height: 1.3em;
417 margin: 0.75em 0;
418 padding-left: 1.2em;
419 text-indent: -1.2em;
420 }
421 /* references */
422 .references dt {
423 text-align: right;
424 font-weight: bold;
425 min-width: 7em;
426 }
427 .references dd {
428 margin-left: 8em;
429 overflow: auto;
430 }
431
432 .refInstance {
433 margin-bottom: 1.25em;
434 }
435
436 .references .ascii {
437 margin-bottom: 0.25em;
438 }
439
440 /* index */
441 .index ul {
442 margin: 0 0 0 1em;
443 padding: 0;
444 list-style: none;
445 }
446 .index ul ul {
447 margin: 0;
448 }
449 .index li {
450 margin: 0;
451 text-indent: -2em;
452 padding-left: 2em;
453 padding-bottom: 5px;
454 }
455 .indexIndex {
456 margin: 0.5em 0 1em;
457 }
458 .index a {
459 font-weight: 700;
460 }
461 /* make the index two-column on all but the smallest screens */
462 @media (min-width: 600px) {
463 .index ul {
464 -moz-column-count: 2;
465 -moz-column-gap: 20px;
466 }
467 .index ul ul {
468 -moz-column-count: 1;
469 -moz-column-gap: 0;
470 }
471 }
472
473 /* authors */
474 address.vcard {
475 font-style: normal;
476 margin: 1em 0;
477 }
478
479 address.vcard .nameRole {
480 font-weight: 700;
481 margin-left: 0;
482 }
483 address.vcard .label {
484 font-family: "Noto Sans",Arial,Helvetica,sans-serif;
485 margin: 0.5em 0;
486 }
487 address.vcard .type {
488 display: none;
489 }
490 .alternative-contact {
491 margin: 1.5em 0 1em;
492 }
493 hr.addr {
494 border-top: 1px dashed;
495 margin: 0;
496 color: #ddd;
497 max-width: calc(100% - 16px);
498 }
499
500 /* temporary notes */
501 .rfcEditorRemove::before {
502 position: absolute;
503 top: 0.2em;
504 right: 0.2em;
505 padding: 0.2em;
506 content: "The RFC Editor will remove this note";
507 color: #9e2a00; /* Arlen: WCAG 2019 */
508 background-color: #ffd; /* Arlen: WCAG 2019 */
509 }
510 .rfcEditorRemove {
511 position: relative;
512 padding-top: 1.8em;
513 background-color: #ffd; /* Arlen: WCAG 2019 */
514 border-radius: 3px;
515 }
516 .cref {
517 background-color: #ffd; /* Arlen: WCAG 2019 */
518 padding: 2px 4px;
519 }
520 .crefSource {
521 font-style: italic;
522 }
523 /* alternative layout for smaller screens */
524 @media screen and (max-width: 1023px) {
525 body {
526 padding-top: 2em;
527 }
528 #title {
529 padding: 1em 0;
530 }
531 h1 {
532 font-size: 24px;
533 }
534 h2 {
535 font-size: 20px;
536 margin-top: -18px; /* provide offset for in-page anchors */
537 padding-top: 38px;
538 }
539 #identifiers dd {
540 max-width: 60%;
541 }
542 #toc {
543 position: fixed;
544 z-index: 2;
545 top: 0;
546 right: 0;
547 padding: 0;
548 margin: 0;
549 background-color: inherit;
550 border-bottom: 1px solid #ccc;
551 }
552 #toc h2 {
553 margin: -1px 0 0 0;
554 padding: 4px 0 4px 6px;
555 padding-right: 1em;
556 min-width: 190px;
557 font-size: 1.1em;
558 text-align: right;
559 background-color: #444;
560 color: white;
561 cursor: pointer;
562 }
563 #toc h2::before { /* css hamburger */
564 float: right;
565 position: relative;
566 width: 1em;
567 height: 1px;
568 left: -164px;
569 margin: 6px 0 0 0;
570 background: white none repeat scroll 0 0;
571 box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
572 content: "";
573 }
574 #toc nav {
575 display: none;
576 padding: 0.5em 1em 1em;
577 overflow: auto;
578 height: calc(100vh - 48px);
579 border-left: 1px solid #ddd;
580 }
581 }
582
583 /* alternative layout for wide screens */
584 @media screen and (min-width: 1024px) {
585 body {
586 max-width: 724px;
587 margin: 42px auto;
588 padding-left: 1.5em;
589 padding-right: 29em;
590 }
591 #toc {
592 position: fixed;
593 top: 42px;
594 right: 42px;
595 width: 25%;
596 margin: 0;
597 padding: 0 1em;
598 z-index: 1;
599 }
600 #toc h2 {
601 border-top: none;
602 border-bottom: 1px solid #ddd;
603 font-size: 1em;
604 font-weight: normal;
605 margin: 0;
606 padding: 0.25em 1em 1em 0;
607 }
608 #toc nav {
609 display: block;
610 height: calc(90vh - 84px);
611 bottom: 0;
612 padding: 0.5em 0 0;
613 overflow: auto;
614 }
615 img { /* future proofing */
616 max-width: 100%;
617 height: auto;
618 }
619 }
620
621 /* pagination */
622 @media print {
623 body {
624
625 width: 100%;
626 }
627 p {
628 orphans: 3;
629 widows: 3;
630 }
631 #n-copyright-notice {
632 border-bottom: none;
633 }
634 #toc, #n-introduction {
635 page-break-before: always;
636 }
637 #toc {
638 border-top: none;
639 padding-top: 0;
640 }
641 figure, pre {
642 page-break-inside: avoid;
643 }
644 figure {
645 overflow: scroll;
646 }
647 h1, h2, h3, h4, h5, h6 {
648 page-break-after: avoid;
649 }
650 h2+*, h3+*, h4+*, h5+*, h6+* {
651 page-break-before: avoid;
652 }
653 pre {
654 white-space: pre-wrap;
655 word-wrap: break-word;
656 font-size: 10pt;
657 }
658 table {
659 border: 1px solid #ddd;
660 }
661 td {
662 border-top: 1px solid #ddd;
663 }
664 }
665
666 /* This is commented out here, as the string-set: doesn't
667 pass W3C validation currently */
668 /*
669 .ears thead .left {
670 string-set: ears-top-left content();
671 }
672
673 .ears thead .center {
674 string-set: ears-top-center content();
675 }
676
677 .ears thead .right {
678 string-set: ears-top-right content();
679 }
680
681 .ears tfoot .left {
682 string-set: ears-bottom-left content();
683 }
684
685 .ears tfoot .center {
686 string-set: ears-bottom-center content();
687 }
688
689 .ears tfoot .right {
690 string-set: ears-bottom-right content();
691 }
692 */
693
694 @page :first {
695 padding-top: 0;
696 @top-left {
697 content: normal;
698 border: none;
699 }
700 @top-center {
701 content: normal;
702 border: none;
703 }
704 @top-right {
705 content: normal;
706 border: none;
707 }
708 }
709
710 @page {
711 size: A4;
712 margin-bottom: 45mm;
713 padding-top: 20px;
714 /* The follwing is commented out here, but set appropriately by in code, as
715 the content depends on the document */
716 /*
717 @top-left {
718 content: 'Internet-Draft';
719 vertical-align: bottom;
720 border-bottom: solid 1px #ccc;
721 }
722 @top-left {
723 content: string(ears-top-left);
724 vertical-align: bottom;
725 border-bottom: solid 1px #ccc;
726 }
727 @top-center {
728 content: string(ears-top-center);
729 vertical-align: bottom;
730 border-bottom: solid 1px #ccc;
731 }
732 @top-right {
733 content: string(ears-top-right);
734 vertical-align: bottom;
735 border-bottom: solid 1px #ccc;
736 }
737 @bottom-left {
738 content: string(ears-bottom-left);
739 vertical-align: top;
740 border-top: solid 1px #ccc;
741 }
742 @bottom-center {
743 content: string(ears-bottom-center);
744 vertical-align: top;
745 border-top: solid 1px #ccc;
746 }
747 @bottom-right {
748 content: '[Page ' counter(page) ']';
749 vertical-align: top;
750 border-top: solid 1px #ccc;
751 }
752 */
753
754 }
755
756 /* Changes introduced to fix issues found during implementation */
757 /* Make sure links are clickable even if overlapped by following H* */
758 a {
759 z-index: 2;
760 }
761 /* Separate body from document info even without intervening H1 */
762 section {
763 clear: both;
764 }
765
766
767 /* Top align author divs, to avoid names without organization dropping level with org names */
768 .author {
769 vertical-align: top;
770 }
771
772 /* Leave room in document info to show Internet-Draft on one line */
773 #identifiers dt {
774 width: 8em;
775 }
776
777 /* Don't waste quite as much whitespace between label and value in doc info */
778 #identifiers dd {
779 margin-left: 1em;
780 }
781
782 /* Give floating toc a background color (needed when it's a div inside section */
783 #toc {
784 background-color: white;
785 }
786
787 /* Make the collapsed ToC header render white on gray also when it's a link */
788 @media screen and (max-width: 1023px) {
789 #toc h2 a,
790 #toc h2 a:link,
791 #toc h2 a:focus,
792 #toc h2 a:hover,
793 #toc a.toplink,
794 #toc a.toplink:hover {
795 color: white;
796 background-color: #444;
797 text-decoration: none;
798 }
799 }
800
801 /* Give the bottom of the ToC some whitespace */
802 @media screen and (min-width: 1024px) {
803 #toc {
804 padding: 0 0 1em 1em;
805 }
806 }
807
808 /* Style section numbers with more space between number and title */
809 .section-number {
810 padding-right: 0.5em;
811 }
812
813 /* prevent monospace from becoming overly large */
814 tt, code, pre, code {
815 font-size: 95%;
816 }
817
818 /* Fix the height/width aspect for ascii art*/
819 pre.sourcecode,
820 .art-text pre {
821 line-height: 1.12;
822 }
823
824
825 /* Add styling for a link in the ToC that points to the top of the document */
826 a.toplink {
827 float: right;
828 margin-right: 0.5em;
829 }
830
831 /* Fix the dl styling to match the RFC 7992 attributes */
832 dl > dt,
833 dl.dlParallel > dt {
834 float: left;
835 margin-right: 1em;
836 }
837 dl.dlNewline > dt {
838 float: none;
839 }
840
841 /* Provide styling for table cell text alignment */
842 table td.text-left,
843 table th.text-left {
844 text-align: left;
845 }
846 table td.text-center,
847 table th.text-center {
848 text-align: center;
849 }
850 table td.text-right,
851 table th.text-right {
852 text-align: right;
853 }
854
855 /* Make the alternative author contact informatio look less like just another
856 author, and group it closer with the primary author contact information */
857 .alternative-contact {
858 margin: 0.5em 0 0.25em 0;
859 }
860 address .non-ascii {
861 margin: 0 0 0 2em;
862 }
863
864 /* With it being possible to set tables with alignment
865 left, center, and right, { width: 100%; } does not make sense */
866 table {
867 width: auto;
868 }
869
870 /* Avoid reference text that sits in a block with very wide left margin,
871 because of a long floating dt label.*/
872 .references dd {
873 overflow: visible;
874 }
875
876 /* Control caption placement */
877 caption {
878 caption-side: bottom;
879 }
880
881 /* Limit the width of the author address vcard, so names in right-to-left
882 script don't end up on the other side of the page. */
883
884 address.vcard {
885 max-width: 30em;
886 margin-right: auto;
887 }
888
889 /* For address alignment dependent on LTR or RTL scripts */
890 address div.left {
891 text-align: left;
892 }
893 address div.right {
894 text-align: right;
895 }
896
897 /* Provide table alignment support. We can't use the alignX classes above
898 since they do unwanted things with caption and other styling. */
899 table.right {
900 margin-left: auto;
901 margin-right: 0;
902 }
903 table.center {
904 margin-left: auto;
905 margin-right: auto;
906 }
907 table.left {
908 margin-left: 0;
909 margin-right: auto;
910 }
911
912 /* Give the table caption label the same styling as the figcaption */
913 caption a[href] {
914 color: #222;
915 }
916
917 @media print {
918 .toplink {
919 display: none;
920 }
921
922 /* avoid overwriting the top border line with the ToC header */
923 #toc {
924 padding-top: 1px;
925 }
926
927 /* Avoid page breaks inside dl and author address entries */
928 .vcard {
929 page-break-inside: avoid;
930 }
931
932 }
933 /* Avoid wrapping of URLs in references */
934 @media screen {
935 .references a {
936 white-space: nowrap;
937 }
938 }
939 /* Tweak the bcp14 keyword presentation */
940 .bcp14 {
941 font-variant: small-caps;
942 font-weight: bold;
943 font-size: 0.9em;
944 }
945 /* Tweak the invisible space above H* in order not to overlay links in text above */
946 h2 {
947 margin-top: -18px; /* provide offset for in-page anchors */
948 padding-top: 31px;
949 }
950 h3 {
951 margin-top: -18px; /* provide offset for in-page anchors */
952 padding-top: 24px;
953 }
954 h4 {
955 margin-top: -18px; /* provide offset for in-page anchors */
956 padding-top: 24px;
957 }
958 /* Float artwork pilcrow to the right */
959 @media screen {
960 .artwork a.pilcrow {
961 display: block;
962 line-height: 0.7;
963 margin-top: 0.15em;
964 }
965 }
966 /* Make pilcrows on dd visible */
967 @media screen {
968 dd:hover > a.pilcrow {
969 visibility: visible;
970 }
971 }
972 /* Make the placement of figcaption match that of a table's caption
973 by removing the figure's added bottom margin */
974 .alignLeft.art-text,
975 .alignCenter.art-text,
976 .alignRight.art-text {
977 margin-bottom: 0;
978 }
979 .alignLeft,
980 .alignCenter,
981 .alignRight {
982 margin: 1em 0 0 0;
983 }
984 /* In print, the pilcrow won't show on hover, so prevent it from taking up space,
985 possibly even requiring a new line */
986 @media print {
987 a.pilcrow {
988 display: none;
989 }
990 }
991 /* Styling for the external metadata */
992 div#external-metadata {
993 background-color: #eee;
994 padding: 0.5em;
995 margin-bottom: 0.5em;
996 display: none;
997 }
998 div#internal-metadata {
999 padding: 0.5em; /* to match the external-metadata padding */
1000 }
1001 /* Styling for title RFC Number */
1002 h1#rfcnum {
1003 clear: both;
1004 margin: 0 0 -1em;
1005 padding: 1em 0 0 0;
1006 }
1007 /* Make .olPercent look the same as <ol><li> */
1008 dl.olPercent > dd {
1009 margin: 0 0 0.25em 0;
1010 min-height: initial;
1011 }
1012 /* Give aside some styling to set it apart */
1013 aside {
1014 border-left: 1px solid #ddd;
1015 margin: 1em 0 1em 2em;
1016 padding: 0.2em 2em;
1017 }
1018 aside > dl,
1019 aside > ol,
1020 aside > ul,
1021 aside > table,
1022 aside > p {
1023 margin-bottom: 0;
1024 }
1025 /* Additional page break settings */
1026 @media print {
1027 figcaption, table caption {
1028 page-break-before: avoid;
1029 }
1030 }
1031 /* Font size adjustments for print */
1032 @media print {
1033 body { font-size: 10pt; line-height: normal; max-width: 96%; }
1034 h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
1035 h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */
1036 h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */
1037 h4 { font-size: 1em; padding-top: 1.5em; }
1038 h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; }
1039 }
1040 /* Sourcecode margin in print, when there's no pilcrow */
1041 @media print {
1042 .sourcecode {
1043 margin-bottom: 1em;
1044 }
1045 }</style>
1046 <link href="rfc-local.css" type="text/css" rel="stylesheet">
1047 <link href="https://dx.doi.org/10.17487/rfc8688" rel="alternate">
1048 <link href="urn:issn:2070-1721" rel="alternate">
1049 <link href="https://datatracker.ietf.org/doc/draft-ietf-sipcore-rejected-09" rel="prev">
1050 </head>
1051 <body>
1052 <script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
1053 <table class="ears">
1054 <thead><tr>
1055 <td class="left">RFC 8688</td>
1056 <td class="center">SIP Response Code for Rejected Calls</td>
1057 <td class="right">December 2019</td>
1058 </tr></thead>
1059 <tfoot><tr>
1060 <td class="left">Burger &amp; Nagda</td>
1061 <td class="center">Standards Track</td>
1062 <td class="right">[Page]</td>
1063 </tr></tfoot>
1064 </table>
1065 <div id="external-metadata" class="document-information"></div>
1066 <div id="internal-metadata" class="document-information">
1067 <dl id="identifiers">
1068 <dt class="label-stream">Stream:</dt>
1069 <dd class="stream">Internet Engineering Task Force (IETF)</dd>
1070 <dt class="label-rfc">RFC:</dt>
1071 <dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc8688" class="eref">8688</a></dd>
1072 <dt class="label-category">Category:</dt>
1073 <dd class="category">Standards Track</dd>
1074 <dt class="label-published">Published:</dt>
1075 <dd class="published">
1076 <time datetime="2019-12" class="published">December 2019</time>
1077 </dd>
1078 <dt class="label-issn">ISSN:</dt>
1079 <dd class="issn">2070-1721</dd>
1080 <dt class="label-authors">Authors:</dt>
1081 <dd class="authors">
1082 <div class="author">
1083 <div class="author-name">E.W. Burger</div>
1084 <div class="org">Georgetown University</div>
1085 </div>
1086 <div class="author">
1087 <div class="author-name">B. Nagda</div>
1088 <div class="org">Massachusetts Institute of Technology</div>
1089 </div>
1090 </dd>
1091 </dl>
1092 </div>
1093 <h1 id="rfcnum">RFC 8688</h1>
1094 <h1 id="title">A Session Initiation Protocol (SIP) Response Code for Rejected Calls</h1>
1095 <section id="section-abstract">
1096 <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
1097 <p id="section-abstract-1">This document defines the 608 (Rejected) Session Initiation Protocol
1098 (SIP) response code. This response code enables calling parties to learn
1099 that an intermediary rejected their call attempt. No one will deliver,
1100 and thus answer, the call. As a 6xx code, the caller will be aware that
1101 future attempts to contact the same User Agent Server will likely fail.
1102 The initial use case driving the need for the 608 response code is when
1103 the intermediary is an analytics engine. In this case, the rejection is
1104 by a machine or other process. This contrasts with the 607 (Unwanted)
1105 SIP response code in which a human at the target User Agent Server
1106 indicates the user did not want the call. In some jurisdictions, this
1107 distinction is important. This document also defines the use of the
1108 Call-Info header field in 608 responses to enable rejected callers to
1109 contact entities that blocked their calls in error. This provides a
1110 remediation mechanism for legal callers that find their calls
1111 blocked.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
1112 </section>
1113 <div id="status-of-memo">
1114 <section id="section-boilerplate.1">
1115 <h2 id="name-status-of-this-memo">
1116 <a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
1117 </h2>
1118 <p id="section-boilerplate.1-1">
1119 This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
1120 <p id="section-boilerplate.1-2">
1121 This document is a product of the Internet Engineering Task Force
1122 (IETF). It represents the consensus of the IETF community. It has
1123 received public review and has been approved for publication by
1124 the Internet Engineering Steering Group (IESG). Further
1125 information on Internet Standards is available in Section 2 of
1126 RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
1127 <p id="section-boilerplate.1-3">
1128 Information about the current status of this document, any
1129 errata, and how to provide feedback on it may be obtained at
1130 <span><a href="https://www.rfc-editor.org/info/rfc8688">https://www.rfc-editor.org/info/rfc8688</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
1131 </section>
1132 </div>
1133 <div id="copyright">
1134 <section id="section-boilerplate.2">
1135 <h2 id="name-copyright-notice">
1136 <a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
1137 </h2>
1138 <p id="section-boilerplate.2-1">
1139 Copyright (c) 2019 IETF Trust and the persons identified as the
1140 document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
1141 <p id="section-boilerplate.2-2">
1142 This document is subject to BCP 78 and the IETF Trust's Legal
1143 Provisions Relating to IETF Documents
1144 (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
1145 publication of this document. Please review these documents
1146 carefully, as they describe your rights and restrictions with
1147 respect to this document. Code Components extracted from this
1148 document must include Simplified BSD License text as described in
1149 Section 4.e of the Trust Legal Provisions and are provided without
1150 warranty as described in the Simplified BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
1151 </section>
1152 </div>
1153 <div id="toc">
1154 <section id="section-toc.1">
1155 <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
1156 <a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
1157 </h2>
1158 <nav class="toc"><ul class="toc ulEmpty">
1159 <li class="toc ulEmpty" id="section-toc.1-1.1">
1160 <p id="section-toc.1-1.1.1"><a href="#section-1" class="xref">1</a>.  <a href="#name-introduction" class="xref">Introduction</a><a href="#section-toc.1-1.1.1" class="pilcrow">¶</a></p>
1161 </li>
1162 <li class="toc ulEmpty" id="section-toc.1-1.2">
1163 <p id="section-toc.1-1.2.1"><a href="#section-2" class="xref">2</a>.  <a href="#name-terminology" class="xref">Terminology</a><a href="#section-toc.1-1.2.1" class="pilcrow">¶</a></p>
1164 </li>
1165 <li class="toc ulEmpty" id="section-toc.1-1.3">
1166 <p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-protocol-operation" class="xref">Protocol Operation</a><a href="#section-toc.1-1.3.1" class="pilcrow">¶</a></p>
1167 <ul class="toc ulEmpty">
1168 <li class="toc ulEmpty" id="section-toc.1-1.3.2.1">
1169 <p id="section-toc.1-1.3.2.1.1"><a href="#section-3.1" class="xref">3.1</a>.  <a href="#name-intermediary-operation" class="xref">Intermediary Operation</a><a href="#section-toc.1-1.3.2.1.1" class="pilcrow">¶</a></p>
1170 </li>
1171 <li class="toc ulEmpty" id="section-toc.1-1.3.2.2">
1172 <p id="section-toc.1-1.3.2.2.1"><a href="#section-3.2" class="xref">3.2</a>.  <a href="#name-jws-construction" class="xref">JWS Construction</a><a href="#section-toc.1-1.3.2.2.1" class="pilcrow">¶</a></p>
1173 <ul class="toc ulEmpty">
1174 <li class="toc ulEmpty" id="section-toc.1-1.3.2.2.2.1">
1175 <p id="section-toc.1-1.3.2.2.2.1.1"><a href="#section-3.2.1" class="xref">3.2.1</a>.  <a href="#name-jose-header" class="xref">JOSE Header</a><a href="#section-toc.1-1.3.2.2.2.1.1" class="pilcrow">¶</a></p>
1176 </li>
1177 <li class="toc ulEmpty" id="section-toc.1-1.3.2.2.2.2">
1178 <p id="section-toc.1-1.3.2.2.2.2.1"><a href="#section-3.2.2" class="xref">3.2.2</a>.  <a href="#name-jwt-payload" class="xref">JWT Payload</a><a href="#section-toc.1-1.3.2.2.2.2.1" class="pilcrow">¶</a></p>
1179 </li>
1180 <li class="toc ulEmpty" id="section-toc.1-1.3.2.2.2.3">
1181 <p id="section-toc.1-1.3.2.2.2.3.1"><a href="#section-3.2.3" class="xref">3.2.3</a>.  <a href="#name-jws-signature" class="xref">JWS Signature</a><a href="#section-toc.1-1.3.2.2.2.3.1" class="pilcrow">¶</a></p>
1182 </li>
1183 </ul>
1184 </li>
1185 <li class="toc ulEmpty" id="section-toc.1-1.3.2.3">
1186 <p id="section-toc.1-1.3.2.3.1"><a href="#section-3.3" class="xref">3.3</a>.  <a href="#name-uac-operation" class="xref">UAC Operation</a><a href="#section-toc.1-1.3.2.3.1" class="pilcrow">¶</a></p>
1187 </li>
1188 <li class="toc ulEmpty" id="section-toc.1-1.3.2.4">
1189 <p id="section-toc.1-1.3.2.4.1"><a href="#section-3.4" class="xref">3.4</a>.  <a href="#name-legacy-interoperation" class="xref">Legacy Interoperation</a><a href="#section-toc.1-1.3.2.4.1" class="pilcrow">¶</a></p>
1190 </li>
1191 <li class="toc ulEmpty" id="section-toc.1-1.3.2.5">
1192 <p id="section-toc.1-1.3.2.5.1"><a href="#section-3.5" class="xref">3.5</a>.  <a href="#name-announcement-requirements" class="xref">Announcement Requirements</a><a href="#section-toc.1-1.3.2.5.1" class="pilcrow">¶</a></p>
1193 </li>
1194 </ul>
1195 </li>
1196 <li class="toc ulEmpty" id="section-toc.1-1.4">
1197 <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-examples" class="xref">Examples</a><a href="#section-toc.1-1.4.1" class="pilcrow">¶</a></p>
1198 <ul class="toc ulEmpty">
1199 <li class="toc ulEmpty" id="section-toc.1-1.4.2.1">
1200 <p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>.  <a href="#name-full-exchange" class="xref">Full Exchange</a><a href="#section-toc.1-1.4.2.1.1" class="pilcrow">¶</a></p>
1201 </li>
1202 <li class="toc ulEmpty" id="section-toc.1-1.4.2.2">
1203 <p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>.  <a href="#name-web-site-jcard" class="xref">Web Site jCard</a><a href="#section-toc.1-1.4.2.2.1" class="pilcrow">¶</a></p>
1204 </li>
1205 <li class="toc ulEmpty" id="section-toc.1-1.4.2.3">
1206 <p id="section-toc.1-1.4.2.3.1"><a href="#section-4.3" class="xref">4.3</a>.  <a href="#name-multi-modal-jcard" class="xref">Multi-modal jCard</a><a href="#section-toc.1-1.4.2.3.1" class="pilcrow">¶</a></p>
1207 </li>
1208 <li class="toc ulEmpty" id="section-toc.1-1.4.2.4">
1209 <p id="section-toc.1-1.4.2.4.1"><a href="#section-4.4" class="xref">4.4</a>.  <a href="#name-legacy-interoperability" class="xref">Legacy Interoperability</a><a href="#section-toc.1-1.4.2.4.1" class="pilcrow">¶</a></p>
1210 </li>
1211 </ul>
1212 </li>
1213 <li class="toc ulEmpty" id="section-toc.1-1.5">
1214 <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-iana-considerations" class="xref">IANA Considerations</a><a href="#section-toc.1-1.5.1" class="pilcrow">¶</a></p>
1215 <ul class="toc ulEmpty">
1216 <li class="toc ulEmpty" id="section-toc.1-1.5.2.1">
1217 <p id="section-toc.1-1.5.2.1.1"><a href="#section-5.1" class="xref">5.1</a>.  <a href="#name-sip-response-code" class="xref">SIP Response Code</a><a href="#section-toc.1-1.5.2.1.1" class="pilcrow">¶</a></p>
1218 </li>
1219 <li class="toc ulEmpty" id="section-toc.1-1.5.2.2">
1220 <p id="section-toc.1-1.5.2.2.1"><a href="#section-5.2" class="xref">5.2</a>.  <a href="#name-sip-feature-capability-indi" class="xref">SIP Feature-Capability Indicator</a><a href="#section-toc.1-1.5.2.2.1" class="pilcrow">¶</a></p>
1221 </li>
1222 <li class="toc ulEmpty" id="section-toc.1-1.5.2.3">
1223 <p id="section-toc.1-1.5.2.3.1"><a href="#section-5.3" class="xref">5.3</a>.  <a href="#name-json-web-token-claim" class="xref">JSON Web Token Claim</a><a href="#section-toc.1-1.5.2.3.1" class="pilcrow">¶</a></p>
1224 </li>
1225 <li class="toc ulEmpty" id="section-toc.1-1.5.2.4">
1226 <p id="section-toc.1-1.5.2.4.1"><a href="#section-5.4" class="xref">5.4</a>.  <a href="#name-call-info-purpose" class="xref">Call-Info Purpose</a><a href="#section-toc.1-1.5.2.4.1" class="pilcrow">¶</a></p>
1227 </li>
1228 </ul>
1229 </li>
1230 <li class="toc ulEmpty" id="section-toc.1-1.6">
1231 <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-security-considerations" class="xref">Security Considerations</a><a href="#section-toc.1-1.6.1" class="pilcrow">¶</a></p>
1232 </li>
1233 <li class="toc ulEmpty" id="section-toc.1-1.7">
1234 <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-references" class="xref">References</a><a href="#section-toc.1-1.7.1" class="pilcrow">¶</a></p>
1235 <ul class="toc ulEmpty">
1236 <li class="toc ulEmpty" id="section-toc.1-1.7.2.1">
1237 <p id="section-toc.1-1.7.2.1.1"><a href="#section-7.1" class="xref">7.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a><a href="#section-toc.1-1.7.2.1.1" class="pilcrow">¶</a></p>
1238 </li>
1239 <li class="toc ulEmpty" id="section-toc.1-1.7.2.2">
1240 <p id="section-toc.1-1.7.2.2.1"><a href="#section-7.2" class="xref">7.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a><a href="#section-toc.1-1.7.2.2.1" class="pilcrow">¶</a></p>
1241 </li>
1242 </ul>
1243 </li>
1244 <li class="toc ulEmpty" id="section-toc.1-1.8">
1245 <p id="section-toc.1-1.8.1"><a href="#section-appendix.a" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a><a href="#section-toc.1-1.8.1" class="pilcrow">¶</a></p>
1246 </li>
1247 <li class="toc ulEmpty" id="section-toc.1-1.9">
1248 <p id="section-toc.1-1.9.1"><a href="#section-appendix.b" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a><a href="#section-toc.1-1.9.1" class="pilcrow">¶</a></p>
1249 </li>
1250 </ul>
1251 </nav>
1252 </section>
1253 </div>
1254 <section id="section-1">
1255 <h2 id="name-introduction">
1256 <a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
1257 </h2>
1258 <p id="section-1-1">The IETF has been addressing numerous issues surrounding how to
1259 handle unwanted and, depending on the jurisdiction, illegal calls <span>[<a href="#RFC5039" class="xref">RFC5039</a>]</span>. Secure Telephone Identity Revisited
1260 (STIR) <span>[<a href="#RFC7340" class="xref">RFC7340</a>]</span> and Signature-based
1261 Handling of Asserted information using toKENs (SHAKEN) <span>[<a href="#SHAKEN" class="xref">SHAKEN</a>]</span> address the cryptographic signing and
1262 attestation, respectively, of signaling to ensure the integrity and
1263 authenticity of the asserted caller identity.<a href="#section-1-1" class="pilcrow">¶</a></p>
1264 <p id="section-1-2">This document describes a new <span><a href="#RFC3261" class="xref">Session Initiation Protocol (SIP)</a> [<a href="#RFC3261" class="xref">RFC3261</a>]</span> response code,
1265 608, which allows calling parties to learn that an intermediary rejected
1266 their call. As described below, we need a distinct indicator to
1267 differentiate between a user rejection and an intermediary's rejection
1268 of a call. In some jurisdictions, service providers may not be permitted
1269 to block calls, even if unwanted by the user, unless there is an
1270 explicit user request. Moreover, users may misidentify the nature of a
1271 caller.<a href="#section-1-2" class="pilcrow">¶</a></p>
1272 <p id="section-1-3">For example, a legitimate caller may call a user who finds the call
1273 to be unwanted. However, instead of marking the call as unwanted, the
1274 user may mark the call as illegal. With that information, an analytics
1275 engine may determine to block all calls from that source. However, in
1276 some jurisdictions, blocking calls from that source for other users may
1277 not be legal. Likewise, one can envision jurisdictions that allow an
1278 operator to block such calls, but only if there is a remediation
1279 mechanism in place to address false positives.<a href="#section-1-3" class="pilcrow">¶</a></p>
1280 <p id="section-1-4">Some call-blocking services may return responses such as 604 (Does
1281 Not Exist Anywhere). This might be a strategy to try to get a
1282 destination's address removed from a calling database. However, other
1283 network elements might also interpret this to mean the user truly does
1284 not exist, which might result in the user not being able to receive
1285 calls from anyone, even if they wanted to receive the calls. In many
1286 jurisdictions, providing such false signaling is also illegal.<a href="#section-1-4" class="pilcrow">¶</a></p>
1287 <p id="section-1-5">The 608 response code addresses this need of remediating falsely
1288 blocked calls. Specifically, this code informs the SIP User Agent Client
1289 (UAC) that an intermediary blocked the call and provides a redress
1290 mechanism that allows callers to contact the operator of the
1291 intermediary.<a href="#section-1-5" class="pilcrow">¶</a></p>
1292 <p id="section-1-6">In the current call handling ecosystem, users can explicitly reject a
1293 call or later mark a call as being unwanted by issuing a <span><a href="#RFC8197" class="xref">607 SIP response code
1294 (Unwanted)</a> [<a href="#RFC8197" class="xref">RFC8197</a>]</span>. Figures <a href="#uas_reject" class="xref">1</a>
1295 and <a href="#reject_ladder" class="xref">2</a> show the operation
1296 of the 607 SIP response code. The User Agent Server (UAS) indicates the
1297 call was unwanted. As <span>[<a href="#RFC8197" class="xref">RFC8197</a>]</span>
1298 explains, not only does the called party desire to reject that call,
1299 they can let their proxy know that they consider future calls from that
1300 source unwanted. Upon receipt of the 607 response from the UAS, the
1301 proxy may send unwanted call indicators, such as the value of the From
1302 header field and other information elements, to a call analytics engine.
1303 For various reasons described in <span>[<a href="#RFC8197" class="xref">RFC8197</a>]</span>, if a network operator receives multiple reports of
1304 unwanted calls, that may indicate that the entity placing the calls is
1305 likely to be a source of unwanted calls for many people. As such, other
1306 customers of the service provider may want the service provider to
1307 automatically reject calls on their behalf.<a href="#section-1-6" class="pilcrow">¶</a></p>
1308 <p id="section-1-7">There is another value of the 607 rejection code. Presuming the proxy
1309 forwards the response code to the UAC, the calling UAC or intervening
1310 proxies will also learn the user is not interested in receiving calls
1311 from that sender.<a href="#section-1-7" class="pilcrow">¶</a></p>
1312 <span id="name-unwanted-607-call-flow"></span><div id="uas_reject">
1313 <figure id="figure-1">
1314 <div class="artwork art-text alignCenter art-ascii-art" id="section-1-8.1">
1315 <pre>
1316 +-----------+
1317 | Call |
1318 | Analytics |
1319 | Engine |
1320 +-----------+
1321 ^ | (likely not SIP)
1322 | v
1323 +-----------+
1324 +-----+ 607 | Called | 607 +-----+
1325 | UAC | &lt;--------- | Party | &lt;-------- | UAS |
1326 +-----+ | Proxy | +-----+
1327 +-----------+
1328 </pre>
1329 </div>
1330 <figcaption><a href="#figure-1" class="selfRef">Figure 1</a>:
1331 <a href="#name-unwanted-607-call-flow" class="selfRef">Unwanted (607) Call Flow</a>
1332 </figcaption></figure>
1333 </div>
1334 <p id="section-1-9">For calls rejected with a 607 from a legitimate caller, receiving a
1335 607 response code can inform the caller to stop attempting to call the
1336 user. Moreover, if a legitimate caller believes the user is rejecting
1337 their calls in error, they can use other channels to contact the user.
1338 For example, if a pharmacy calls a user to let them know their
1339 prescription is available for pickup and the user mistakenly thinks the
1340 call is unwanted and issues a 607 response code, the pharmacy, having an
1341 existing relationship with the customer, can send the user an email or
1342 push a note to the pharmacist to ask the customer to consider not
1343 rejecting their calls in the future.<a href="#section-1-9" class="pilcrow">¶</a></p>
1344 <p id="section-1-10">Many systems that allow the user to mark the call unwanted (e.g.,
1345 with the 607 response code) also allow the user to change their mind and
1346 unmark such calls. This mechanism is relatively easy to implement as the
1347 user usually has a direct relationship with the service provider that is
1348 blocking calls.<a href="#section-1-10" class="pilcrow">¶</a></p>
1349 <p id="section-1-11">However, things become more complicated if an intermediary, such as a
1350 third-party provider of call management services that classifies calls
1351 based on the relative likelihood that the call is unwanted,
1352 misidentifies the call as unwanted. <a href="#cae_reject" class="xref">Figure 3</a> shows this case. Note that the UAS typically does
1353 not receive an INVITE since the called party proxy rejects the call on
1354 behalf of the user. In this situation, it would be beneficial for the
1355 caller to learn who rejected the call so they can correct the
1356 misidentification.<a href="#section-1-11" class="pilcrow">¶</a></p>
1357 <span id="name-unwanted-607-ladder-diagram"></span><div id="reject_ladder">
1358 <figure id="figure-2">
1359 <div class="artwork art-text alignCenter art-call-flow" id="section-1-12.1">
1360 <pre>
1361 +--------+ +-----------+
1362 | Called | | Call |
1363 +-----+ | Party | | Analytics | +-----+
1364 | UAC | | Proxy | | Engine | | UAS |
1365 +-----+ +--------+ +-----------+ +-----+
1366 | INVITE | | |
1367 | --------------&gt; | Is call OK? | |
1368 | |-------------------&gt;| |
1369 | | | |
1370 | | Yes | |
1371 | |&lt;-------------------| |
1372 | | | |
1373 | | INVITE | |
1374 | | ------------------------------&gt; |
1375 | | | |
1376 | | | 607 |
1377 | | &lt;------------------------------ |
1378 | | | |
1379 | | Unwanted call | |
1380 | 607 | -----------------&gt; | |
1381 | &lt;-------------- | indicators | |
1382 | | | |
1383 </pre>
1384 </div>
1385 <figcaption><a href="#figure-2" class="selfRef">Figure 2</a>:
1386 <a href="#name-unwanted-607-ladder-diagram" class="selfRef">Unwanted (607) Ladder Diagram</a>
1387 </figcaption></figure>
1388 </div>
1389 <span id="name-rejected-608-call-flow"></span><div id="cae_reject">
1390 <figure id="figure-3">
1391 <div class="artwork art-text alignCenter art-ascii-art" id="section-1-13.1">
1392 <pre>
1393 +-----------+
1394 | Call |
1395 | Analytics |
1396 | Engine |
1397 +-----------+
1398 ^ | (likely not SIP)
1399 | v
1400 +-----------+
1401 +-----+ 608 | Called | +-----+
1402 | UAC | &lt;--------- | Party | | UAS |
1403 +-----+ | Proxy | +-----+
1404 +-----------+
1405 </pre>
1406 </div>
1407 <figcaption><a href="#figure-3" class="selfRef">Figure 3</a>:
1408 <a href="#name-rejected-608-call-flow" class="selfRef">Rejected (608) Call Flow</a>
1409 </figcaption></figure>
1410 </div>
1411 <p id="section-1-14">In this situation, one might consider having the intermediary use the
1412 607 response code. 607 indicates to the caller that the subscriber does
1413 not want the call. However, <span>[<a href="#RFC8197" class="xref">RFC8197</a>]</span>
1414 specifies that one of the uses of 607 is to inform analytics engines
1415 that a user (human) has rejected a call. The problem here is that
1416 network elements downstream from the intermediary might interpret the
1417 607 as coming from a user (human) who has marked the call as unwanted,
1418 as opposed to coming from an algorithm using statistics or machine
1419 learning to reject the call. An algorithm can be vulnerable to the
1420 base-rate fallacy <span>[<a href="#BaseRate" class="xref">BaseRate</a>]</span> rejecting
1421 the call. In other words, those downstream entities should not rely on
1422 another entity "deciding" the call is unwanted. By distinguishing
1423 between a (human) user rejection and an intermediary engine's
1424 statistical rejection, a downstream network element that sees a 607
1425 response code can weigh it as a human rejection in its call analytics,
1426 versus deciding whether to consider a 608 at all, and if so, weighing it
1427 appropriately.<a href="#section-1-14" class="pilcrow">¶</a></p>
1428 <p id="section-1-15">It is useful for blocked callers to have a redress mechanism. One can
1429 imagine that some jurisdictions will require it. However, we must be
1430 mindful that most of the calls that intermediaries block will, in fact,
1431 be illegal and eligible for blocking. Thus, providing alternate contact
1432 information for a user would be counterproductive to protecting that
1433 user from illegal communications. This is another reason we do not
1434 propose to simply allow alternate contact information in a 607 response
1435 message.<a href="#section-1-15" class="pilcrow">¶</a></p>
1436 <p id="section-1-16">Why do we not use the same mechanism an analytics service provider
1437 offers their customers? Specifically, why not have the analytics service
1438 provider allow the called party to correct a call blocked in error? The
1439 reason is that while there is an existing relationship between the
1440 customer (called party) and the analytics service provider, it is
1441 unlikely there is a relationship between the caller and the analytics
1442 service provider. Moreover, there are numerous call blocking providers
1443 in the ecosystem. Therefore, we need a mechanism for indicating an
1444 intermediary rejected a call that also provides contact information for
1445 the operator of that intermediary without exposing the target user's
1446 contact information.<a href="#section-1-16" class="pilcrow">¶</a></p>
1447 <p id="section-1-17">The protocol described in this document uses existing SIP protocol
1448 mechanisms for specifying the redress mechanism. In the Call-Info header
1449 field passed back to the UAC, we send additional information specifying
1450 a redress address. We choose to encode the redress address using <span><a href="#RFC7095" class="xref">jCard</a> [<a href="#RFC7095" class="xref">RFC7095</a>]</span>. As we will see later in
1451 this document, this information needs to have its own application-layer
1452 integrity protection. Thus, we use jCard rather than <span><a href="#RFC6350" class="xref">vCard</a> [<a href="#RFC6350" class="xref">RFC6350</a>]</span>, as we have a marshaling
1453 mechanism for creating a JavaScript Object Notation <span><a href="#RFC8259" class="xref">(JSON)</a> [<a href="#RFC8259" class="xref">RFC8259</a>]</span> object, such as a jCard,
1454 and a standard integrity format for such an object, namely, JSON Web
1455 Signature <span><a href="#RFC7515" class="xref">(JWS)</a> [<a href="#RFC7515" class="xref">RFC7515</a>]</span>. The SIP
1456 community is familiar with this concept as it is the mechanism used by
1457 <span><a href="#RFC8224" class="xref">STIR</a> [<a href="#RFC8224" class="xref">RFC8224</a>]</span>.<a href="#section-1-17" class="pilcrow">¶</a></p>
1458 <p id="section-1-18">Integrity protecting the jCard with a cryptographic signature might
1459 seem unnecessary at first, but it is essential to preventing potential
1460 network attacks. <a href="#Security" class="xref">Section 6</a> describes
1461 the attack and why we sign the jCard in more detail.<a href="#section-1-18" class="pilcrow">¶</a></p>
1462 </section>
1463 <section id="section-2">
1464 <h2 id="name-terminology">
1465 <a href="#section-2" class="section-number selfRef">2. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a>
1466 </h2>
1467 <p id="section-2-1"> The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>",
1468 "<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", "<span class="bcp14">SHALL NOT</span>", "<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>",
1469 "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>",
1470 "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are
1471 to be interpreted as described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span>
1472 <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> when, and only when, they appear in all
1473 capitals, as shown here.<a href="#section-2-1" class="pilcrow">¶</a></p>
1474 </section>
1475 <section id="section-3">
1476 <h2 id="name-protocol-operation">
1477 <a href="#section-3" class="section-number selfRef">3. </a><a href="#name-protocol-operation" class="section-name selfRef">Protocol Operation</a>
1478 </h2>
1479 <p id="section-3-1">This section uses the term "intermediary" to mean the entity that
1480 acts as a SIP UAS on behalf of the user in the network as opposed to the
1481 user's UAS (usually, but not necessarily, their phone). The intermediary
1482 could be a back-to-back user agent (B2BUA) or a SIP Proxy.<a href="#section-3-1" class="pilcrow">¶</a></p>
1483 <p id="section-3-2"><a href="#cae_ladder" class="xref">Figure 4</a> shows an overview of the
1484 call flow for a rejected call.<a href="#section-3-2" class="pilcrow">¶</a></p>
1485 <span id="name-rejected-608-ladder-diagram"></span><div id="cae_ladder">
1486 <figure id="figure-4">
1487 <div class="artwork art-text alignCenter art-call-flow" id="section-3-3.1">
1488 <pre>
1489 +--------+ +-----------+
1490 | Called | | Call |
1491 +-----+ | Party | | Analytics | +-----+
1492 | UAC | | Proxy | | Engine | | UAS |
1493 +-----+ +--------+ +-----------+ +-----+
1494 | INVITE | | |
1495 | --------------&gt; | Is call OK? | |
1496 | |-------------------&gt;| |
1497 | | | |
1498 | | Yes | |
1499 | |&lt;-------------------| |
1500 | | | |
1501 | | INVITE | |
1502 | | ------------------------------&gt; |
1503 | | | |
1504 | | | 607 |
1505 | | &lt;------------------------------ |
1506 | | | |
1507 | | Unwanted call | |
1508 | 607 | -----------------&gt; | |
1509 | &lt;-------------- | indicators | |
1510 | | | |
1511 </pre>
1512 </div>
1513 <figcaption><a href="#figure-4" class="selfRef">Figure 4</a>:
1514 <a href="#name-rejected-608-ladder-diagram" class="selfRef">Rejected (608) Ladder Diagram</a>
1515 </figcaption></figure>
1516 </div>
1517 <section id="section-3.1">
1518 <h3 id="name-intermediary-operation">
1519 <a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-intermediary-operation" class="section-name selfRef">Intermediary Operation</a>
1520 </h3>
1521 <p id="section-3.1-1">An intermediary <span class="bcp14">MAY</span> issue the 608 response code in a
1522 failure response for an INVITE, MESSAGE, SUBSCRIBE, or other
1523 out-of-dialog <span><a href="#RFC3261" class="xref">SIP</a> [<a href="#RFC3261" class="xref">RFC3261</a>]</span>
1524 request to indicate that an intermediary rejected the offered
1525 communication as unwanted by the user. An intermediary
1526 <span class="bcp14">MAY</span> issue the 608 as the value of the "cause" parameter
1527 of a SIP reason-value in a Reason header field <span>[<a href="#RFC3326" class="xref">RFC3326</a>]</span>.<a href="#section-3.1-1" class="pilcrow">¶</a></p>
1528 <p id="section-3.1-2">If an intermediary issues a 608 code and there are no indicators
1529 the calling party will use the contents of the Call-Info header field
1530 for malicious purposes (see <a href="#Security" class="xref">Section 6</a>), the intermediary <span class="bcp14">MUST</span> include a
1531 Call-Info header field in the response.<a href="#section-3.1-2" class="pilcrow">¶</a></p>
1532 <p id="section-3.1-3">If there is a Call-Info header field, it <span class="bcp14">MUST</span> have
1533 the "purpose" parameter of "jwscard". The value of the Call-Info
1534 header field <span class="bcp14">MUST</span> refer to a valid JSON Web Signature
1535 (JWS) <span>[<a href="#RFC7515" class="xref">RFC7515</a>]</span> encoding of a <span><a href="#RFC7095" class="xref">jCard</a> [<a href="#RFC7095" class="xref">RFC7095</a>]</span> object. The following
1536 section describes the construction of the JWS.<a href="#section-3.1-3" class="pilcrow">¶</a></p>
1537 <p id="section-3.1-4">Proxies need to be mindful that a downstream intermediary may
1538 reject the attempt with a 608 while other paths may still be in
1539 progress. In this situation, the requirements stated in <span><a href="https://www.rfc-editor.org/rfc/rfc3261#section-16.7" class="relref">Section 16.7</a> of [<a href="#RFC3261" class="xref">RFC3261</a>]</span> apply.
1540 Specifically, the proxy should cancel pending transactions and must
1541 not create any new branches. Note this is not a new requirement but
1542 simply pointing out the existing 6xx protocol mechanism in SIP.<a href="#section-3.1-4" class="pilcrow">¶</a></p>
1543 </section>
1544 <section id="section-3.2">
1545 <h3 id="name-jws-construction">
1546 <a href="#section-3.2" class="section-number selfRef">3.2. </a><a href="#name-jws-construction" class="section-name selfRef">JWS Construction</a>
1547 </h3>
1548 <p id="section-3.2-1">The intermediary constructs the JWS of the jCard as follows.<a href="#section-3.2-1" class="pilcrow">¶</a></p>
1549 <section id="section-3.2.1">
1550 <h4 id="name-jose-header">
1551 <a href="#section-3.2.1" class="section-number selfRef">3.2.1. </a><a href="#name-jose-header" class="section-name selfRef">JOSE Header</a>
1552 </h4>
1553 <p id="section-3.2.1-1">The Javascript Object Signing and Encryption (JOSE) header
1554 <span class="bcp14">MUST</span> include the typ, alg, and x5u parameters from
1555 <span><a href="#RFC7515" class="xref">JWS</a> [<a href="#RFC7515" class="xref">RFC7515</a>]</span>. The typ
1556 parameter <span class="bcp14">MUST</span> have the value "vcard+json".
1557 Implementations <span class="bcp14">MUST</span> support ES256 as JSON Web
1558 Algorithms (JWA) <span>[<a href="#RFC7518" class="xref">RFC7518</a>]</span> defines
1559 it and <span class="bcp14">MAY</span> support other registered signature
1560 algorithms. Finally, the x5u parameter <span class="bcp14">MUST</span> be a URI
1561 that resolves to the public key certificate corresponding to the key
1562 used to digitally sign the JWS.<a href="#section-3.2.1-1" class="pilcrow">¶</a></p>
1563 </section>
1564 <div id="JWT">
1565 <section id="section-3.2.2">
1566 <h4 id="name-jwt-payload">
1567 <a href="#section-3.2.2" class="section-number selfRef">3.2.2. </a><a href="#name-jwt-payload" class="section-name selfRef">JWT Payload</a>
1568 </h4>
1569 <p id="section-3.2.2-1">The payload contains two JSON values. The first JSON Web Token
1570 (JWT) claim that <span class="bcp14">MUST</span> be present is the <span><a href="#RFC7519" class="xref">"iat" (issued at) claim</a> [<a href="#RFC7519" class="xref">RFC7519</a>]</span>.
1571 The "iat" <span class="bcp14">MUST</span> be set to the date and time of the
1572 issuance of the 608 response. This mandatory component protects the
1573 response from replay attacks.<a href="#section-3.2.2-1" class="pilcrow">¶</a></p>
1574 <p id="section-3.2.2-2">The second JWT claim that <span class="bcp14">MUST</span> be present is the
1575 "jcard" claim. The value of the <span><a href="#RFC7095" class="xref">jcard</a> [<a href="#RFC7095" class="xref">RFC7095</a>]</span> claim is a JSON array conforming to
1576 the JSON jCard data format defined in <span>[<a href="#RFC7095" class="xref">RFC7095</a>]</span>. <a href="#JWT-IANA" class="xref">Section 5.3</a> describes the registration. In
1577 the construction of the jcard claim, the "jcard" <span class="bcp14">MUST</span>
1578 include at least one of the URL, EMAIL, TEL, or ADR properties. UACs
1579 supporting this specification <span class="bcp14">MUST</span> be prepared to
1580 receive a full jCard. Call originators (at the UAC) can use the
1581 information returned by the jCard to contact the intermediary that
1582 rejected the call to appeal the intermediary's blocking of the call
1583 attempt. What the intermediary does if the blocked caller contacts
1584 the intermediary is outside the scope of this document.<a href="#section-3.2.2-2" class="pilcrow">¶</a></p>
1585 </section>
1586 </div>
1587 <div id="s.JWS">
1588 <section id="section-3.2.3">
1589 <h4 id="name-jws-signature">
1590 <a href="#section-3.2.3" class="section-number selfRef">3.2.3. </a><a href="#name-jws-signature" class="section-name selfRef">JWS Signature</a>
1591 </h4>
1592 <p id="section-3.2.3-1"><span><a href="#RFC7515" class="xref">JWS</a> [<a href="#RFC7515" class="xref">RFC7515</a>]</span> specifies the
1593 procedure for calculating the signature over the jCard JWT. <a href="#EXAMPLES" class="xref">Section 4</a> of this document has a detailed
1594 example on constructing the JWS, including the signature.<a href="#section-3.2.3-1" class="pilcrow">¶</a></p>
1595 </section>
1596 </div>
1597 </section>
1598 <section id="section-3.3">
1599 <h3 id="name-uac-operation">
1600 <a href="#section-3.3" class="section-number selfRef">3.3. </a><a href="#name-uac-operation" class="section-name selfRef">UAC Operation</a>
1601 </h3>
1602 <p id="section-3.3-1">A UAC conforming to this specification <span class="bcp14">MUST</span> include
1603 the sip.608 feature-capability indicator in the Feature-Caps header
1604 field of the INVITE request.<a href="#section-3.3-1" class="pilcrow">¶</a></p>
1605 <p id="section-3.3-2">Upon receiving a 608 response, UACs perform normal SIP processing
1606 for 6xx responses.<a href="#section-3.3-2" class="pilcrow">¶</a></p>
1607 <p id="section-3.3-3">As for the disposition of the jCard itself, the UAC
1608 <span class="bcp14">MUST</span> check the "iat" claim in the JWT. As noted in
1609 <a href="#JWT" class="xref">Section 3.2.2</a>, we are concerned about replay
1610 attacks. Therefore, the UAC <span class="bcp14">MUST</span> reject jCards that
1611 come with an expired "iat". The definition of "expired" is a matter of
1612 local policy. A reasonable value would be on the order of a minute due
1613 to clock drift and the possibility of the playing of an audio
1614 announcement before the delivery of the 608 response.<a href="#section-3.3-3" class="pilcrow">¶</a></p>
1615 </section>
1616 <section id="section-3.4">
1617 <h3 id="name-legacy-interoperation">
1618 <a href="#section-3.4" class="section-number selfRef">3.4. </a><a href="#name-legacy-interoperation" class="section-name selfRef">Legacy Interoperation</a>
1619 </h3>
1620 <p id="section-3.4-1">If the UAC indicates support for 608 and the intermediary issues a
1621 608, life is good, as the UAC will receive all the information it
1622 needs to remediate an erroneous block by an intermediary. However,
1623 what if the UAC does not understand 608? For example, how can we
1624 support callers from a legacy, non-SIP, public-switched network
1625 connecting to the SIP network via a media gateway?<a href="#section-3.4-1" class="pilcrow">¶</a></p>
1626 <p id="section-3.4-2">We address this situation by having the first network element that
1627 conforms with this specification play an announcement. See <a href="#announcement" class="xref">Section 3.5</a> for requirements on the
1628 announcement. The simple rule is a network element that inserts the
1629 sip.608 feature capability <span class="bcp14">MUST</span> be able to convey at a
1630 minimum how to contact the operator of the intermediary that rejected
1631 the call attempt.<a href="#section-3.4-2" class="pilcrow">¶</a></p>
1632 <p id="section-3.4-3">The degenerate case is the intermediary is the only element that
1633 understands the semantics of the 608 response code. Obviously, any SIP
1634 device will understand that a 608 response code is a 6xx error.
1635 However, there are no other elements in the call path that understand
1636 the meaning of the value of the Call-Info header field. The
1637 intermediary knows this is the case as the INVITE request will not
1638 have the sip.608 feature capability. In this case, one can consider
1639 the intermediary to be the element "inserting" a virtual sip.608
1640 feature capability. If the caveats described in Sections <a href="#announcement" class="xref">3.5</a> and <a href="#Security" class="xref">6</a> do not hold, the intermediary <span class="bcp14">MUST</span>
1641 play the announcement.<a href="#section-3.4-3" class="pilcrow">¶</a></p>
1642 <p id="section-3.4-4">Now we take the case where a network element that understands the
1643 608 response code receives an INVITE for further processing. A network
1644 element conforming with this specification <span class="bcp14">MUST</span> insert
1645 the sip.608 feature capability per the behaviors described in <span><a href="https://www.rfc-editor.org/rfc/rfc6809#section-4.2" class="relref">Section 4.2</a> of [<a href="#RFC6809" class="xref">RFC6809</a>]</span>.<a href="#section-3.4-4" class="pilcrow">¶</a></p>
1646 <p id="section-3.4-5">Do note that even if a network element plays an announcement
1647 describing the contents of the 608 response message, the network
1648 element <span class="bcp14">MUST</span> forward the 608 response code message as
1649 the final response to the INVITE.<a href="#section-3.4-5" class="pilcrow">¶</a></p>
1650 <p id="section-3.4-6">One aspect of using a feature capability is that only the network
1651 elements that will either consume (UAC) or play an announcement (media
1652 gateway, session border controller (SBC) <span>[<a href="#RFC7092" class="xref">RFC7092</a>]</span>, or proxy) need to understand the sip.608 feature
1653 capability. If the other network elements conform to <span><a href="https://www.rfc-editor.org/rfc/rfc3261#section-16.6" class="relref">Section 16.6</a> of [<a href="#RFC3261" class="xref">RFC3261</a>]</span>, they will pass
1654 header fields such as "Feature-Caps: *;+sip.608" unmodified and
1655 without need for upgrade.<a href="#section-3.4-6" class="pilcrow">¶</a></p>
1656 <p id="section-3.4-7">Because the ultimate disposition of the call attempt will be a
1657 600-class response, the network element conveying the announcement in
1658 the legacy direction <span class="bcp14">MUST</span> use the 183 Session Progress
1659 response to establish the media session. Because of the small chance
1660 the UAC is an extremely old legacy device and is using UDP, the UAC
1661 <span class="bcp14">MUST</span> include support for <span><a href="#RFC3262" class="xref">100rel</a> [<a href="#RFC3262" class="xref">RFC3262</a>]</span> in its INVITE, the network element
1662 conveying the announcement <span class="bcp14">MUST</span> Require 100rel in the
1663 183, and the UAC <span class="bcp14">MUST</span> issue a Provisional Response
1664 ACKnowledgement (PRACK) to which the network element
1665 <span class="bcp14">MUST</span> respond 200 OK PRACK.<a href="#section-3.4-7" class="pilcrow">¶</a></p>
1666 </section>
1667 <div id="announcement">
1668 <section id="section-3.5">
1669 <h3 id="name-announcement-requirements">
1670 <a href="#section-3.5" class="section-number selfRef">3.5. </a><a href="#name-announcement-requirements" class="section-name selfRef">Announcement Requirements</a>
1671 </h3>
1672 <p id="section-3.5-1">There are a few requirements on the element that handles the
1673 announcement for legacy interoperation.<a href="#section-3.5-1" class="pilcrow">¶</a></p>
1674 <p id="section-3.5-2">As noted above, the element that inserts the sip.608 feature
1675 capability is responsible for conveying the information referenced by
1676 the Call-Info header field in the 608 response message. However, this
1677 specification does not mandate how to convey that information.<a href="#section-3.5-2" class="pilcrow">¶</a></p>
1678 <p id="section-3.5-3">Let us take the case where a telecommunications service provider
1679 controls the element inserting the sip.608 feature capability. It
1680 would be reasonable to expect the service provider would play an
1681 announcement in the media path towards the UAC (caller). It is
1682 important to note the network element should be mindful of the media
1683 type requested by the UAC as it formulates the announcement. For
1684 example, it would make sense for an INVITE that only indicated audio
1685 codecs in the <span><a href="#RFC4566" class="xref">Session
1686 Description Protocol (SDP)</a> [<a href="#RFC4566" class="xref">RFC4566</a>]</span> to result in an audio announcement.
1687 Likewise, if the INVITE only indicated <span><a href="#RFC4103" class="xref">real-time text</a> [<a href="#RFC4103" class="xref">RFC4103</a>]</span> and the network element can
1688 render the information in the requested media format, the network
1689 element should send the information in a text format.<a href="#section-3.5-3" class="pilcrow">¶</a></p>
1690 <p id="section-3.5-4">It is also possible for the network element inserting the sip.608
1691 feature capability to be under the control of the same entity that
1692 controls the UAC. For example, a large call center might have legacy
1693 UACs, but have a modern outbound calling proxy that understands the
1694 full semantics of the 608 response code. In this case, it is enough
1695 for the outbound calling proxy to digest the Call-Info information and
1696 handle the information digitally rather than "transcoding" the
1697 Call-Info information for presentation to the caller.<a href="#section-3.5-4" class="pilcrow">¶</a></p>
1698 </section>
1699 </div>
1700 </section>
1701 <div id="EXAMPLES">
1702 <section id="section-4">
1703 <h2 id="name-examples">
1704 <a href="#section-4" class="section-number selfRef">4. </a><a href="#name-examples" class="section-name selfRef">Examples</a>
1705 </h2>
1706 <p id="section-4-1">These examples are not normative, do not include all protocol
1707 elements, and may have errors. Review the protocol documents for actual
1708 syntax and semantics of the protocol elements.<a href="#section-4-1" class="pilcrow">¶</a></p>
1709 <section id="section-4.1">
1710 <h3 id="name-full-exchange">
1711 <a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-full-exchange" class="section-name selfRef">Full Exchange</a>
1712 </h3>
1713 <p id="section-4.1-1">Given an INVITE, shamelessly taken from <span>[<a href="#SHAKEN" class="xref">SHAKEN</a>]</span>, with the line breaks in the Identity header field
1714 for display purposes only:<a href="#section-4.1-1" class="pilcrow">¶</a></p>
1715 <div id="section-4.1-2">
1716 <pre class="sourcecode">
1717 INVITE sip:[email protected] SIP/2.0
1718 Max-Forwards: 69
1719 Contact: &lt;sip:+12155550112@[2001:db8::12]:50207;rinstance=9da3088f3&gt;
1720 To: &lt;sip:[email protected]&gt;
1721 From: "Alice" &lt;sip:[email protected]&gt;;tag=614bdb40
1722 Call-ID: 79048YzkxNDA5NTI1MzA0OWFjOTFkMmFlODhiNTI2OWQ1ZTI
1723 P-Asserted-Identity: "Alice"&lt;sip:[email protected]&gt;,
1724 &lt;tel:+12155550112&gt;
1725 CSeq: 2 INVITE
1726 Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO,
1727 MESSAGE, OPTIONS
1728 Content-Type: application/sdp
1729 Date: Tue, 16 Aug 2016 19:23:38 GMT
1730 Feature-Caps: *;+sip.608
1731 Identity: eyJhbGciOiJFUzI1NiIsInR5cCI6InBhc3Nwb3J0IiwicHB0Ijoic2hha2V
1732 uIiwieDV1IjoiaHR0cDovL2NlcnQuZXhhbXBsZTIubmV0L2V4YW1wbGUuY2VydCJ9.eyJ
1733 hdHRlc3QiOiJBIiwiZGVzdCI6eyJ0biI6IisxMjE1NTU1MDExMyJ9LCJpYXQiOiIxNDcx
1734 Mzc1NDE4Iiwib3JpZyI6eyJ0biI6IisxMjE1NTU1MDExMiJ9LCJvcmlnaWQiOiIxMjNlN
1735 DU2Ny1lODliLTEyZDMtYTQ1Ni00MjY2NTU0NDAwMCJ9.QAht_eFqQlaoVrnEV56Qly-OU
1736 tsDGifyCcpYjWcaR661Cz1hutFH2BzIlDswTahO7ujjqsWjeoOb4h97whTQJg;info=
1737 &lt;http://cert.example2.net/example.cert&gt;;alg=ES256
1738 Content-Length: 153
1739
1740 v=0
1741 o=- 13103070023943130 1 IN IP6 2001:db8::177
1742 c=IN IP6 2001:db8::177
1743 t=0 0
1744 m=audio 54242 RTP/AVP 0
1745 a=sendrecv
1746 </pre><a href="#section-4.1-2" class="pilcrow">¶</a>
1747 </div>
1748 <p id="section-4.1-3">An intermediary could reply:<a href="#section-4.1-3" class="pilcrow">¶</a></p>
1749 <div id="section-4.1-4">
1750 <pre class="sourcecode">
1751 SIP/2.0 608 Rejected
1752 Via: SIP/2.0/UDP [2001:db8::177]:60012;branch=z9hG4bK-524287-1
1753 From: "Alice" &lt;sip:[email protected]&gt;;tag=614bdb40
1754 To: &lt;sip:[email protected]&gt;
1755 Call-ID: 79048YzkxNDA5NTI1MzA0OWFjOTFkMmFlODhiNTI2OWQ1ZTI
1756 CSeq: 2 INVITE
1757 Call-Info: &lt;https://block.example.net/complaint-jws&gt;;purpose=jwscard
1758 </pre><a href="#section-4.1-4" class="pilcrow">¶</a>
1759 </div>
1760 <p id="section-4.1-5">The location https://block.example.net/complaint-jws resolves to a
1761 JWS. One would construct the JWS as follows.<a href="#section-4.1-5" class="pilcrow">¶</a></p>
1762 <p id="section-4.1-6">The JWS header of this example jCard could be:<a href="#section-4.1-6" class="pilcrow">¶</a></p>
1763 <div id="section-4.1-7">
1764 <pre class="sourcecode lang-json">
1765 { "alg":"ES256",
1766 "typ":"vcard+json",
1767 "x5u":"https://certs.example.net/reject_key.cer"
1768 }
1769 </pre><a href="#section-4.1-7" class="pilcrow">¶</a>
1770 </div>
1771 <p id="section-4.1-8">Now, let us construct a minimal jCard. For this example, the jCard
1772 refers the caller to an email address,
1773 [email protected]:<a href="#section-4.1-8" class="pilcrow">¶</a></p>
1774 <div id="section-4.1-9">
1775 <pre class="sourcecode lang-json">
1776 ["vcard",
1777 [
1778 ["version", {}, "text", "4.0"],
1779 ["fn", {}, "text", "Robocall Adjudication"],
1780 ["email", {"type":"work"}, "text",
1781 "[email protected]"]
1782 ]
1783 ]
1784 </pre><a href="#section-4.1-9" class="pilcrow">¶</a>
1785 </div>
1786 <p id="section-4.1-10">With this jCard, we can now construct the JWT:<a href="#section-4.1-10" class="pilcrow">¶</a></p>
1787 <div id="section-4.1-11">
1788 <pre class="sourcecode lang-json">{
1789 "iat":1546008698,
1790 "jcard":["vcard",
1791 [
1792 ["version", {}, "text", "4.0"],
1793 ["fn", {}, "text", "Robocall Adjudication"],
1794 ["email", {"type":"work"},
1795 "text", "[email protected]"]
1796 ]
1797 ]
1798 } </pre><a href="#section-4.1-11" class="pilcrow">¶</a>
1799 </div>
1800 <p id="section-4.1-12">To calculate the signature, we need to encode the JSON Object
1801 Signing and Encryption (JOSE) header and JWT into base64url. As an
1802 implementation note, one can trim whitespace in the JSON objects to
1803 save a few bytes. UACs <span class="bcp14">MUST</span> be prepared to receive
1804 pretty-printed, compact, or bizarrely formatted JSON. For the purposes
1805 of this example, we leave the objects with pretty whitespace. Speaking
1806 of pretty vs. machine formatting, these examples have line breaks in
1807 the base64url encodings for ease of publication in the RFC format. The
1808 specification of base64url allows for these line breaks, and the
1809 decoded text works just fine. However, those extra line-break octets
1810 would affect the calculation of the signature. Implementations
1811 <span class="bcp14">MUST NOT</span> insert line breaks into the base64url
1812 encodings of the JOSE header or JWT. This also means UACs
1813 <span class="bcp14">MUST</span> be prepared to receive arbitrarily long octet
1814 streams from the URI referenced by the Call-Info header field.<a href="#section-4.1-12" class="pilcrow">¶</a></p>
1815 <p id="section-4.1-13">base64url of JOSE header:<a href="#section-4.1-13" class="pilcrow">¶</a></p>
1816 <div class="artwork art-text alignLeft art-hex-dump" id="section-4.1-14">
1817 <pre>
1818 eyJhbGciOiJFUzI1NiIsInR5cCI6InZjYXJkK2pzb24iLCJ4NXUiOiJodHRwczov
1819 L2NlcnRzLmV4YW1wbGUubmV0L3JlamVjdF9rZXkuY2VyIn0=
1820 </pre><a href="#section-4.1-14" class="pilcrow">¶</a>
1821 </div>
1822 <p id="section-4.1-15">base64url of JWT:<a href="#section-4.1-15" class="pilcrow">¶</a></p>
1823 <div class="artwork art-text alignLeft art-hex-dump" id="section-4.1-16">
1824 <pre>
1825 eyJpYXQiOjE1NDYwMDg2OTgsImpjYXJkIjpbInZjYXJkIixbWyJ2ZXJzaW9uIix7
1826 fSwidGV4dCIsIjQuMCJdLFsiZm4iLHt9LCJ0ZXh0IiwiUm9ib2NhbGwgQWRqdWRp
1827 Y2F0aW9uIl0sWyJlbWFpbCIseyJ0eXBlIjoid29yayJ9LCJ0ZXh0IiwicmVtZWRp
1828 YXRpb25AYmxvY2tlci5leGFtcGxlLm5ldCJdXV19
1829 </pre><a href="#section-4.1-16" class="pilcrow">¶</a>
1830 </div>
1831 <p id="section-4.1-17">In this case, the object to sign (remembering this is just a single
1832 long line; the line breaks are for ease of review but do not appear in
1833 the actual object) is as follows:<a href="#section-4.1-17" class="pilcrow">¶</a></p>
1834 <div class="artwork art-text alignLeft art-hex-dump" id="section-4.1-18">
1835 <pre>
1836 eyJhbGciOiJFUzI1NiIsInR5cCI6InZjYXJk
1837 K2pzb24iLCJ4NXUiOiJodHRwczovL2NlcnRzLmV4YW1wbGUubmV0L3JlamVjdF9r
1838 ZXkuY2VyIn0.eyJpYXQiOjE1NDYwMDg2OTgsImpjYXJkIjpbInZjYXJkIixbWyJ2
1839 ZXJzaW9uIix7fSwidGV4dCIsIjQuMCJdLFsiZm4iLHt9LCJ0ZXh0IiwiUm9ib2Nh
1840 bGwgQWRqdWRpY2F0aW9uIl0sWyJlbWFpbCIseyJ0eXBlIjoid29yayJ9LCJ0ZXh0
1841 IiwicmVtZWRpYXRpb25AYmxvY2tlci5leGFtcGxlLm5ldCJdXV19
1842 </pre><a href="#section-4.1-18" class="pilcrow">¶</a>
1843 </div>
1844 <p id="section-4.1-19">We use the following X.509 PKCS #8-encoded Elliptic Curve Digital
1845 Signature Algorithm (ECDSA) key, also shamelessly taken from <span>[<a href="#SHAKEN" class="xref">SHAKEN</a>]</span>, as an example key for signing the
1846 hash of the above text. Do NOT use this key in real life! It is for
1847 example purposes only. At the very least, we would strongly recommend
1848 encrypting the key at rest.<a href="#section-4.1-19" class="pilcrow">¶</a></p>
1849 <div class="artwork art-text alignLeft" id="section-4.1-20">
1850 <pre>
1851 -----BEGIN PRIVATE KEY-----
1852 MIGHAgEAMBMGByqGSM49AgEGCCqGSM49AwEHBG0wawIBAQQgi7q2TZvN9VDFg8Vy
1853 qCP06bETrR2v8MRvr89rn4i+UAahRANCAAQWfaj1HUETpoNCrOtp9KA8o0V79IuW
1854 ARKt9C1cFPkyd3FBP4SeiNZxQhDrD0tdBHls3/wFe8++K2FrPyQF9vuh
1855 -----END PRIVATE KEY-----
1856
1857 -----BEGIN PUBLIC KEY-----
1858 MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE8HNbQd/TmvCKwPKHkMF9fScavGeH
1859 78YTU8qLS8I5HLHSSmlATLcslQMhNC/OhlWBYC626nIlo7XeebYS7Sb37g==
1860 -----END PUBLIC KEY-----
1861 </pre><a href="#section-4.1-20" class="pilcrow">¶</a>
1862 </div>
1863 <p id="section-4.1-21">The resulting JWS, using the above key on the above object, renders
1864 the following ECDSA P-256 SHA-256 digital signature.<a href="#section-4.1-21" class="pilcrow">¶</a></p>
1865 <div class="artwork art-text alignLeft" id="section-4.1-22">
1866 <pre>
1867 7uz2SADRvPFOQOO_UgF2ZTUjPlDTegtPrYB04UHBMwBD6g9AmL
1868 5harLJdTKDSTtH-LOV1jwJaGRUOUJiwP27ag
1869 </pre><a href="#section-4.1-22" class="pilcrow">¶</a>
1870 </div>
1871 <p id="section-4.1-23">Thus, the JWS stored at https://blocker.example.net/complaints-jws
1872 would contain:<a href="#section-4.1-23" class="pilcrow">¶</a></p>
1873 <div class="artwork art-text alignLeft" id="section-4.1-24">
1874 <pre>
1875 eyJhbGciOiJFUzI1NiIsInR5cCI6InZjYXJkK2pzb24iLCJ4NXUiOiJodHRwczovL
1876 2NlcnRzLmV4YW1wbGUubmV0L3JlamVjdF9rZXkuY2VyIn0.eyJpYXQiOjE1NDYwMD
1877 g2OTgsImpjYXJkIjpbInZjYXJkIixbWyJ2ZXJzaW9uIix7fSwidGV4dCIsIjQuMCJ
1878 dLFsiZm4iLHt9LCJ0ZXh0IiwiUm9ib2NhbGwgQWRqdWRpY2F0aW9uIl0sWyJlbWFp
1879 bCIseyJ0eXBlIjoid29yayJ9LCJ0ZXh0IiwicmVtZWRpYXRpb25AYmxvY2tlci5le
1880 GFtcGxlLm5ldCJdXV19.7uz2SADRvPFOQOO_UgF2ZTUjPlDTegtPrYB04UHBMwBD6
1881 g9AmL5harLJdTKDSTtH-LOV1jwJaGRUOUJiwP27ag
1882 </pre><a href="#section-4.1-24" class="pilcrow">¶</a>
1883 </div>
1884 </section>
1885 <section id="section-4.2">
1886 <h3 id="name-web-site-jcard">
1887 <a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-web-site-jcard" class="section-name selfRef">Web Site jCard</a>
1888 </h3>
1889 <p id="section-4.2-1">For an intermediary that provides a Web site for adjudication, the
1890 jCard could contain the following. Note that we do not show the
1891 calculation of the JWS; the URI reference in the Call-Info header
1892 field would be to the JWS of the signed jCard.<a href="#section-4.2-1" class="pilcrow">¶</a></p>
1893 <div id="section-4.2-2">
1894 <pre class="sourcecode lang-json">
1895 ["vcard",
1896 [
1897 ["version", {}, "text", "4.0"],
1898 ["fn", {}, "text", "Robocall Adjudication"],
1899 ["url", {"type":"work"},
1900 "text", "https://blocker.example.net/adjudication-form"]
1901 ]
1902 ] </pre><a href="#section-4.2-2" class="pilcrow">¶</a>
1903 </div>
1904 </section>
1905 <section id="section-4.3">
1906 <h3 id="name-multi-modal-jcard">
1907 <a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-multi-modal-jcard" class="section-name selfRef">Multi-modal jCard</a>
1908 </h3>
1909 <p id="section-4.3-1">For an intermediary that provides a telephone number and a postal
1910 address, the jCard could contain the following. Note that we do not
1911 show the calculation of the JWS; the URI reference in the Call-Info
1912 header field would be to the JWS of the signed jCard.<a href="#section-4.3-1" class="pilcrow">¶</a></p>
1913 <div id="section-4.3-2">
1914 <pre class="sourcecode lang-json">["vcard",
1915 [
1916 ["version", {}, "text", "4.0"],
1917 ["fn", {}, "text", "Robocall Adjudication"],
1918 ["adr", {"type":"work"}, "text",
1919 ["Argument Clinic",
1920 "12 Main St","Anytown","AP","000000","Somecountry"]
1921 ]
1922 ["tel", {"type":"work"}, "uri", "tel:+1-555-555-0112"]
1923 ]
1924 ]</pre><a href="#section-4.3-2" class="pilcrow">¶</a>
1925 </div>
1926 <p id="section-4.3-3">Note that it is up to the UAC to decide which jCard contact
1927 modality, if any, it will use.<a href="#section-4.3-3" class="pilcrow">¶</a></p>
1928 </section>
1929 <section id="section-4.4">
1930 <h3 id="name-legacy-interoperability">
1931 <a href="#section-4.4" class="section-number selfRef">4.4. </a><a href="#name-legacy-interoperability" class="section-name selfRef">Legacy Interoperability</a>
1932 </h3>
1933 <p id="section-4.4-1"><a href="#legacy_ladder" class="xref">Figure 5</a> depicts a call flow
1934 illustrating legacy interoperability. In this non-normative example,
1935 we see a UAC that does not support the full semantics for 608.
1936 However, there is an SBC that does support 608. Per <span>[<a href="#RFC6809" class="xref">RFC6809</a>]</span>, the SBC can insert "*;+sip.608"
1937 into the Feature-Caps header field for the INVITE. When the
1938 intermediary, labeled "Called Party Proxy" in the figure, rejects the
1939 call, it knows it can simply perform the processing described in this
1940 document. Since the intermediary saw the sip.608 feature capability,
1941 it knows it does not need to send any media describing whom to contact
1942 in the event of an erroneous rejection. For illustrative purposes, the
1943 figure shows generic SIP Proxies in the flow. Their presence or
1944 absence or the number of proxies is not relevant to the operation of
1945 the protocol. They are in the figure to show that proxies that do not
1946 understand the sip.608 feature capability can still participate in a
1947 network offering 608 services.<a href="#section-4.4-1" class="pilcrow">¶</a></p>
1948 <span id="name-legacy-operation"></span><div id="legacy_ladder">
1949 <figure id="figure-5">
1950 <div class="artwork art-text alignCenter art-ascii-art" id="section-4.4-2.1">
1951 <pre>
1952 +---------+
1953 | Call |
1954 |Analytics|
1955 | Engine |
1956 +--+--+---+
1957 ^ |
1958 | |
1959 | v
1960 +-+--+-+
1961 +---+ +-----+ +---+ +-----+ +-----+ |Called|
1962 |UAC+----+Proxy+----+SBC+----+Proxy+----+Proxy+----+Party |
1963 +---+ +-----+ +---+ +-----+ +-----+ |Proxy |
1964 | | +------+
1965 | INVITE | |
1966 |------------------&gt;| |
1967 | | INVITE |
1968 | |------------------------------&gt;|
1969 | | Feature-Caps: *;+sip.608 |
1970 | | |
1971 | | 608 Rejected |
1972 | |&lt;------------------------------|
1973 | 183 | Call-Info: &lt;...&gt; |
1974 |&lt;------------------| [path for Call-Info elided |
1975 | SDP for media | for illustration purposes]|
1976 | | |
1977 | PRACK | |
1978 |------------------&gt;| |
1979 | | |
1980 | 200 OK PRACK | |
1981 |&lt;------------------| |
1982 | | |
1983 |&lt;== Announcement ==| |
1984 | | |
1985 | 608 Rejected | |
1986 |&lt;------------------| |
1987 | Call-Info: &lt;...&gt; | |
1988 | | |
1989 </pre>
1990 </div>
1991 <figcaption><a href="#figure-5" class="selfRef">Figure 5</a>:
1992 <a href="#name-legacy-operation" class="selfRef">Legacy Operation</a>
1993 </figcaption></figure>
1994 </div>
1995 <p id="section-4.4-3">When the SBC receives the 608 response code, it correlates that
1996 with the original INVITE from the UAC. The SBC remembers that it
1997 inserted the sip.608 feature capability, which means it is responsible
1998 for somehow alerting the UAC the call failed and disclosing whom to
1999 contact. At this point, the SBC can play a prompt, either natively or
2000 through a mechanism such as <span><a href="#RFC4240" class="xref">NETANN</a> [<a href="#RFC4240" class="xref">RFC4240</a>]</span>, that sends the relevant information in
2001 the appropriate media to the UAC. Since this is a potentially long
2002 transaction and there is a chance the UAC is using an unreliable
2003 transport protocol, the UAC will have indicated support for
2004 provisional responses, the SBC will indicate it requires a PRACK from
2005 the UAC in the 183 response, the UAC will provide the PRACK, and the
2006 SBC will acknowledge receipt of the PRACK before playing the
2007 announcement.<a href="#section-4.4-3" class="pilcrow">¶</a></p>
2008 <p id="section-4.4-4">As an example, the SBC could extract the FN and TEL jCard fields
2009 and play something like a special information tone (see Section
2010 6.21.2.1 of Telcordia <span>[<a href="#SR-2275" class="xref">SR-2275</a>]</span> or Section 7 of <span><a href="#ITU.E.180.1998" class="xref">ITU-T E.180</a> [<a href="#ITU.E.180.1998" class="xref">ITU.E.180.1998</a>]</span>), followed by "Your call
2011 has been rejected by...", followed by a text-to-speech translation of
2012 the FN text, followed by "You can reach them on...", followed by a
2013 text-to-speech translation of the telephone number in the TEL
2014 field.<a href="#section-4.4-4" class="pilcrow">¶</a></p>
2015 <p id="section-4.4-5">Note that the SBC also still sends the full 608 response code,
2016 including the Call-Info header field, towards the UAC.<a href="#section-4.4-5" class="pilcrow">¶</a></p>
2017 </section>
2018 </section>
2019 </div>
2020 <section id="section-5">
2021 <h2 id="name-iana-considerations">
2022 <a href="#section-5" class="section-number selfRef">5. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
2023 </h2>
2024 <section id="section-5.1">
2025 <h3 id="name-sip-response-code">
2026 <a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-sip-response-code" class="section-name selfRef">SIP Response Code</a>
2027 </h3>
2028 <p id="section-5.1-1">This document defines a new SIP response code, 608, in the
2029 "Response Codes" subregistry of the "Session Initiation Protocol (SIP)
2030 Parameters" registry defined in <span>[<a href="#RFC3261" class="xref">RFC3261</a>]</span>.<a href="#section-5.1-1" class="pilcrow">¶</a></p>
2031 <dl class="dlParallel dlCompact" id="section-5.1-2">
2032 <dt id="section-5.1-2.1">Response code:</dt>
2033 <dd style="margin-left: 9.0em" id="section-5.1-2.2">608<a href="#section-5.1-2.2" class="pilcrow">¶</a>
2034 </dd>
2035 <dt id="section-5.1-2.3">Description:</dt>
2036 <dd style="margin-left: 9.0em" id="section-5.1-2.4">Rejected<a href="#section-5.1-2.4" class="pilcrow">¶</a>
2037 </dd>
2038 <dt id="section-5.1-2.5">Reference:</dt>
2039 <dd style="margin-left: 9.0em" id="section-5.1-2.6">RFC 8688<a href="#section-5.1-2.6" class="pilcrow">¶</a>
2040 </dd>
2041 </dl>
2042 </section>
2043 <section id="section-5.2">
2044 <h3 id="name-sip-feature-capability-indi">
2045 <a href="#section-5.2" class="section-number selfRef">5.2. </a><a href="#name-sip-feature-capability-indi" class="section-name selfRef">SIP Feature-Capability Indicator</a>
2046 </h3>
2047 <p id="section-5.2-1">This document defines the feature capability, sip.608, in the "SIP
2048 Feature-Capability Indicator Registration Tree" registry defined in
2049 <span>[<a href="#RFC6809" class="xref">RFC6809</a>]</span>.<a href="#section-5.2-1" class="pilcrow">¶</a></p>
2050 <dl class="dlParallel dlCompact" id="section-5.2-2">
2051 <dt id="section-5.2-2.1">Name:</dt>
2052 <dd style="margin-left: 7.0em" id="section-5.2-2.2">sip.608<a href="#section-5.2-2.2" class="pilcrow">¶</a>
2053 </dd>
2054 <dt id="section-5.2-2.3">Description:</dt>
2055 <dd style="margin-left: 7.0em" id="section-5.2-2.4">This feature-capability indicator, when included in a
2056 Feature-Caps header field of an INVITE request, indicates that the
2057 entity associated with the indicator will be responsible for
2058 indicating to the caller any information contained in the 608 SIP
2059 response code, specifically, the value referenced by the Call-Info
2060 header field.<a href="#section-5.2-2.4" class="pilcrow">¶</a>
2061 </dd>
2062 <dt id="section-5.2-2.5">Reference:</dt>
2063 <dd style="margin-left: 7.0em" id="section-5.2-2.6">RFC 8688<a href="#section-5.2-2.6" class="pilcrow">¶</a>
2064 </dd>
2065 </dl>
2066 </section>
2067 <div id="JWT-IANA">
2068 <section id="section-5.3">
2069 <h3 id="name-json-web-token-claim">
2070 <a href="#section-5.3" class="section-number selfRef">5.3. </a><a href="#name-json-web-token-claim" class="section-name selfRef">JSON Web Token Claim</a>
2071 </h3>
2072 <p id="section-5.3-1">This document defines the new JSON Web Token claim in the "JSON Web
2073 Token Claims" subregistry created by <span>[<a href="#RFC7519" class="xref">RFC7519</a>]</span>. <a href="#JWT" class="xref">Section 3.2.2</a> defines the
2074 syntax. The required information is:<a href="#section-5.3-1" class="pilcrow">¶</a></p>
2075 <dl class="dlParallel dlCompact" id="section-5.3-2">
2076 <dt id="section-5.3-2.1">Claim Name:</dt>
2077 <dd style="margin-left: 10.0em" id="section-5.3-2.2">jcard<a href="#section-5.3-2.2" class="pilcrow">¶</a>
2078 </dd>
2079 <dt id="section-5.3-2.3">Claim Description:</dt>
2080 <dd style="margin-left: 10.0em" id="section-5.3-2.4">jCard data<a href="#section-5.3-2.4" class="pilcrow">¶</a>
2081 </dd>
2082 <dt id="section-5.3-2.5">Change Controller:</dt>
2083 <dd style="margin-left: 10.0em" id="section-5.3-2.6">IESG<a href="#section-5.3-2.6" class="pilcrow">¶</a>
2084 </dd>
2085 <dt id="section-5.3-2.7">Reference:</dt>
2086 <dd style="margin-left: 10.0em" id="section-5.3-2.8">RFC 8688, <span>[<a href="#RFC7095" class="xref">RFC7095</a>]</span><a href="#section-5.3-2.8" class="pilcrow">¶</a>
2087 </dd>
2088 </dl>
2089 </section>
2090 </div>
2091 <section id="section-5.4">
2092 <h3 id="name-call-info-purpose">
2093 <a href="#section-5.4" class="section-number selfRef">5.4. </a><a href="#name-call-info-purpose" class="section-name selfRef">Call-Info Purpose</a>
2094 </h3>
2095 <p id="section-5.4-1">This document defines the new predefined value "jwscard" for the
2096 "purpose" header field parameter of the Call-Info header field. This
2097 modifies the "Header Field Parameters and Parameter Values"
2098 subregistry of the "Session Initiation Protocol (SIP) Parameters"
2099 registry by adding this RFC as a reference to the line for the header
2100 field "Call-Info" and parameter name "purpose":<a href="#section-5.4-1" class="pilcrow">¶</a></p>
2101 <dl class="dlParallel dlCompact" id="section-5.4-2">
2102 <dt id="section-5.4-2.1">Header Field:</dt>
2103 <dd style="margin-left: 10.0em" id="section-5.4-2.2">Call-Info<a href="#section-5.4-2.2" class="pilcrow">¶</a>
2104 </dd>
2105 <dt id="section-5.4-2.3">Parameter Name:</dt>
2106 <dd style="margin-left: 10.0em" id="section-5.4-2.4">purpose<a href="#section-5.4-2.4" class="pilcrow">¶</a>
2107 </dd>
2108 <dt id="section-5.4-2.5">Predefined Values:</dt>
2109 <dd style="margin-left: 10.0em" id="section-5.4-2.6">Yes<a href="#section-5.4-2.6" class="pilcrow">¶</a>
2110 </dd>
2111 <dt id="section-5.4-2.7">Reference:</dt>
2112 <dd style="margin-left: 10.0em" id="section-5.4-2.8">RFC 8688<a href="#section-5.4-2.8" class="pilcrow">¶</a>
2113 </dd>
2114 </dl>
2115 </section>
2116 </section>
2117 <div id="Security">
2118 <section id="section-6">
2119 <h2 id="name-security-considerations">
2120 <a href="#section-6" class="section-number selfRef">6. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
2121 </h2>
2122 <p id="section-6-1">Intermediary operators need to be mindful to whom they are sending
2123 the 608 response. The intermediary could be rejecting a truly malicious
2124 caller. This raises two issues. The first is the caller, now alerted
2125 that an intermediary is automatically rejecting their call attempts, may
2126 change their call behavior to defeat call-blocking systems. The second,
2127 and more significant risk, is that by providing a contact in the
2128 Call-Info header field, the intermediary may be giving the malicious
2129 caller a vector for attack. In other words, the intermediary will be
2130 publishing an address that a malicious actor may use to launch an attack
2131 on the intermediary. Because of this, intermediary operators may wish to
2132 configure their response to only include a Call-Info header field for
2133 INVITE, or other signed initiating methods, that pass validation by
2134 <span><a href="#RFC8224" class="xref">STIR</a> [<a href="#RFC8224" class="xref">RFC8224</a>]</span>.<a href="#section-6-1" class="pilcrow">¶</a></p>
2135 <p id="section-6-2">Another risk is as follows. Consider an attacker that floods a proxy
2136 that supports the sip.608 feature. However, the SDP in the INVITE
2137 request refers to a victim device. Moreover, the attacker somehow knows
2138 there is a 608-aware gateway connecting to the victim who is on a
2139 segment that lacks the sip.608 feature capability. Because the mechanism
2140 described here can result in sending an audio file to the target of the
2141 SDP, an attacker could use the mechanism described by this document as
2142 an amplification attack, given a SIP INVITE can be under 1 kilobyte and
2143 an audio file can be hundreds of kilobytes. One remediation for this is
2144 for devices that insert a sip.608 feature capability to only transmit
2145 media to what is highly likely to be the actual source of the call
2146 attempt. A method for this is to only play media in response to a
2147 STIR-signed INVITE that passes validation. Beyond requiring a valid STIR
2148 signature on the INVITE, the intermediary can also use remediation
2149 procedures such as doing the connectivity checks specified by <span><a href="#RFC8445" class="xref">Interactive Connectivity
2150 Establishment</a> [<a href="#RFC8445" class="xref">RFC8445</a>]</span>. If the target did not request the media, the check
2151 will fail.<a href="#section-6-2" class="pilcrow">¶</a></p>
2152 <p id="section-6-3">Yet another risk is a malicious intermediary that generates a
2153 malicious 608 response with a jCard referring to a malicious agent. For
2154 example, the recipient of a 608 may receive a TEL URI in the vCard. When
2155 the recipient calls that address, the malicious agent could ask for
2156 personally identifying information. However, instead of using that
2157 information to verify the recipient's identity, they are phishing the
2158 information for nefarious ends. A similar scenario can unfold if the
2159 malicious agent inserts a URI that points to a phishing or other site.
2160 As such, we strongly recommend the recipient validates to whom they are
2161 communicating with if asking to adjudicate an erroneously rejected call
2162 attempt. Since we may also be concerned about intermediate nodes
2163 modifying contact information, we can address both issues with a single
2164 solution. The remediation is to require the intermediary to sign the
2165 jCard. Signing the jCard provides integrity protection. In addition, one
2166 can imagine mechanisms such as used by <span>[<a href="#SHAKEN" class="xref">SHAKEN</a>]</span>.<a href="#section-6-3" class="pilcrow">¶</a></p>
2167 <p id="section-6-4">Similarly, one can imagine an adverse agent that maliciously spoofs a
2168 608 response with a victim's contact address to many active callers who
2169 may then all send redress requests to the specified address (the basis
2170 for a denial-of-service attack). The process would occur as follows: (1)
2171 a malicious agent senses INVITE requests from a variety of UACs and (2)
2172 spoofs 608 responses with an unsigned redress address before the
2173 intended receivers can respond, causing (3) the UACs to all contact the
2174 redress address at once. The jCard encoding allows the UAC to verify the
2175 blocking intermediary's identity before contacting the redress address.
2176 Specifically, because the sender signs the jCard, we can
2177 cryptographically trace the sender of the jCard. Given the protocol
2178 machinery of having a signature, one can apply local policy to decide
2179 whether to believe that the sender of the jCard represents the owner of
2180 the contact information found in the jCard. This guards against a
2181 malicious agent spoofing 608 responses.<a href="#section-6-4" class="pilcrow">¶</a></p>
2182 <p id="section-6-5">Specifically, one could use policies around signing certificate
2183 issuance as a mechanism for traceback to the entity issuing the jCard.
2184 One check could be verifying that the identity of the subject of the
2185 certificate relates to the To header field of the initial SIP request,
2186 similar to validating that the intermediary was vouching for the From
2187 header field of a SIP request with that identity. Note that we are only
2188 protecting against a malicious intermediary and not a hidden
2189 intermediary attack (formerly known as a "man-in-the-middle attack").
2190 Thus, we only need to ensure the signature is fresh, which is why we
2191 include "iat". For most implementations, we assume that the intermediary
2192 has a single set of contact points and will generate the jCard on
2193 demand. As such, there is no need to directly correlate HTTPS fetches to
2194 specific calls. However, since the intermediary is in control of the
2195 jCard and Call-Info response, an intermediary may choose to encode
2196 per-call information in the URI returned in a given 608 response.
2197 However, if the intermediary does go that route, the intermediary
2198 <span class="bcp14">MUST</span> use a non-deterministic URI reference mechanism and
2199 be prepared to return dummy responses to URI requests referencing calls
2200 that do not exist so that attackers attempting to glean call metadata by
2201 guessing URIs (and thus calls) will not get any actionable information
2202 from the HTTPS GET.<a href="#section-6-5" class="pilcrow">¶</a></p>
2203 <p id="section-6-6">Since the decision of whether to include Call-Info in the 608
2204 response is a matter of policy, one thing to consider is whether a
2205 legitimate caller can ascertain whom to contact without including such
2206 information in the 608. For example, in some jurisdictions, if only the
2207 terminating service provider can be the intermediary, the caller can
2208 look up who the terminating service provider is based on the routing
2209 information for the dialed number. Thus, the Call-Info jCard could be
2210 redundant information. However, the factors going into a particular
2211 service provider's or jurisdiction's choice of whether to include
2212 Call-Info is outside the scope of this document.<a href="#section-6-6" class="pilcrow">¶</a></p>
2213 </section>
2214 </div>
2215 <section id="section-7">
2216 <h2 id="name-references">
2217 <a href="#section-7" class="section-number selfRef">7. </a><a href="#name-references" class="section-name selfRef">References</a>
2218 </h2>
2219 <section id="section-7.1">
2220 <h3 id="name-normative-references">
2221 <a href="#section-7.1" class="section-number selfRef">7.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
2222 </h3>
2223 <dl class="references">
2224 <dt id="RFC2119">[RFC2119]</dt>
2225 <dd>
2226 <span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"Key words for use in RFCs to Indicate Requirement Levels"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 2119</span>, <span class="seriesInfo">DOI 10.17487/RFC2119</span>, <time datetime="1997-03">March 1997</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>&gt;</span>. </dd>
2227 <dt id="RFC3261">[RFC3261]</dt>
2228 <dd>
2229 <span class="refAuthor">Rosenberg, J.</span><span class="refAuthor">, Schulzrinne, H.</span><span class="refAuthor">, Camarillo, G.</span><span class="refAuthor">, Johnston, A.</span><span class="refAuthor">, Peterson, J.</span><span class="refAuthor">, Sparks, R.</span><span class="refAuthor">, Handley, M.</span><span class="refAuthor">, and E. Schooler</span>, <span class="refTitle">"SIP: Session Initiation Protocol"</span>, <span class="seriesInfo">RFC 3261</span>, <span class="seriesInfo">DOI 10.17487/RFC3261</span>, <time datetime="2002-06">June 2002</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3261">https://www.rfc-editor.org/info/rfc3261</a>&gt;</span>. </dd>
2230 <dt id="RFC3262">[RFC3262]</dt>
2231 <dd>
2232 <span class="refAuthor">Rosenberg, J.</span><span class="refAuthor"> and H. Schulzrinne</span>, <span class="refTitle">"Reliability of Provisional Responses in Session Initiation Protocol (SIP)"</span>, <span class="seriesInfo">RFC 3262</span>, <span class="seriesInfo">DOI 10.17487/RFC3262</span>, <time datetime="2002-06">June 2002</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3262">https://www.rfc-editor.org/info/rfc3262</a>&gt;</span>. </dd>
2233 <dt id="RFC3326">[RFC3326]</dt>
2234 <dd>
2235 <span class="refAuthor">Schulzrinne, H.</span><span class="refAuthor">, Oran, D.</span><span class="refAuthor">, and G. Camarillo</span>, <span class="refTitle">"The Reason Header Field for the Session Initiation Protocol (SIP)"</span>, <span class="seriesInfo">RFC 3326</span>, <span class="seriesInfo">DOI 10.17487/RFC3326</span>, <time datetime="2002-12">December 2002</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3326">https://www.rfc-editor.org/info/rfc3326</a>&gt;</span>. </dd>
2236 <dt id="RFC6809">[RFC6809]</dt>
2237 <dd>
2238 <span class="refAuthor">Holmberg, C.</span><span class="refAuthor">, Sedlacek, I.</span><span class="refAuthor">, and H. Kaplan</span>, <span class="refTitle">"Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP)"</span>, <span class="seriesInfo">RFC 6809</span>, <span class="seriesInfo">DOI 10.17487/RFC6809</span>, <time datetime="2012-11">November 2012</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6809">https://www.rfc-editor.org/info/rfc6809</a>&gt;</span>. </dd>
2239 <dt id="RFC7095">[RFC7095]</dt>
2240 <dd>
2241 <span class="refAuthor">Kewisch, P.</span>, <span class="refTitle">"jCard: The JSON Format for vCard"</span>, <span class="seriesInfo">RFC 7095</span>, <span class="seriesInfo">DOI 10.17487/RFC7095</span>, <time datetime="2014-01">January 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7095">https://www.rfc-editor.org/info/rfc7095</a>&gt;</span>. </dd>
2242 <dt id="RFC7515">[RFC7515]</dt>
2243 <dd>
2244 <span class="refAuthor">Jones, M.</span><span class="refAuthor">, Bradley, J.</span><span class="refAuthor">, and N. Sakimura</span>, <span class="refTitle">"JSON Web Signature (JWS)"</span>, <span class="seriesInfo">RFC 7515</span>, <span class="seriesInfo">DOI 10.17487/RFC7515</span>, <time datetime="2015-05">May 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7515">https://www.rfc-editor.org/info/rfc7515</a>&gt;</span>. </dd>
2245 <dt id="RFC7518">[RFC7518]</dt>
2246 <dd>
2247 <span class="refAuthor">Jones, M.</span>, <span class="refTitle">"JSON Web Algorithms (JWA)"</span>, <span class="seriesInfo">RFC 7518</span>, <span class="seriesInfo">DOI 10.17487/RFC7518</span>, <time datetime="2015-05">May 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7518">https://www.rfc-editor.org/info/rfc7518</a>&gt;</span>. </dd>
2248 <dt id="RFC7519">[RFC7519]</dt>
2249 <dd>
2250 <span class="refAuthor">Jones, M.</span><span class="refAuthor">, Bradley, J.</span><span class="refAuthor">, and N. Sakimura</span>, <span class="refTitle">"JSON Web Token (JWT)"</span>, <span class="seriesInfo">RFC 7519</span>, <span class="seriesInfo">DOI 10.17487/RFC7519</span>, <time datetime="2015-05">May 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7519">https://www.rfc-editor.org/info/rfc7519</a>&gt;</span>. </dd>
2251 <dt id="RFC8174">[RFC8174]</dt>
2252 <dd>
2253 <span class="refAuthor">Leiba, B.</span>, <span class="refTitle">"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 8174</span>, <span class="seriesInfo">DOI 10.17487/RFC8174</span>, <time datetime="2017-05">May 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>&gt;</span>. </dd>
2254 </dl>
2255 </section>
2256 <section id="section-7.2">
2257 <h3 id="name-informative-references">
2258 <a href="#section-7.2" class="section-number selfRef">7.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
2259 </h3>
2260 <dl class="references">
2261 <dt id="BaseRate">[BaseRate]</dt>
2262 <dd>
2263 <span class="refAuthor">Bar-Hillel, M.</span>, <span class="refTitle">"The Base-Rate Fallacy in Probability Judgements"</span>, <time datetime="1977-04">April 1977</time>, <span>&lt;<a href="https://apps.dtic.mil/docs/citations/ADA045772">https://apps.dtic.mil/docs/citations/ADA045772</a>&gt;</span>. </dd>
2264 <dt id="ITU.E.180.1998">[ITU.E.180.1998]</dt>
2265 <dd>
2266 <span class="refAuthor">ITU-T</span>, <span class="refTitle">"Technical characteristics of tones for the telephone service"</span>, <span class="seriesInfo">ITU-T Recommendation E.180/Q.35</span>, <time datetime="1998-03">March 1998</time>. </dd>
2267 <dt id="RFC4103">[RFC4103]</dt>
2268 <dd>
2269 <span class="refAuthor">Hellstrom, G.</span><span class="refAuthor"> and P. Jones</span>, <span class="refTitle">"RTP Payload for Text Conversation"</span>, <span class="seriesInfo">RFC 4103</span>, <span class="seriesInfo">DOI 10.17487/RFC4103</span>, <time datetime="2005-06">June 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4103">https://www.rfc-editor.org/info/rfc4103</a>&gt;</span>. </dd>
2270 <dt id="RFC4240">[RFC4240]</dt>
2271 <dd>
2272 <span class="refAuthor">Burger, E., Ed.</span><span class="refAuthor">, Van Dyke, J.</span><span class="refAuthor">, and A. Spitzer</span>, <span class="refTitle">"Basic Network Media Services with SIP"</span>, <span class="seriesInfo">RFC 4240</span>, <span class="seriesInfo">DOI 10.17487/RFC4240</span>, <time datetime="2005-12">December 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4240">https://www.rfc-editor.org/info/rfc4240</a>&gt;</span>. </dd>
2273 <dt id="RFC4566">[RFC4566]</dt>
2274 <dd>
2275 <span class="refAuthor">Handley, M.</span><span class="refAuthor">, Jacobson, V.</span><span class="refAuthor">, and C. Perkins</span>, <span class="refTitle">"SDP: Session Description Protocol"</span>, <span class="seriesInfo">RFC 4566</span>, <span class="seriesInfo">DOI 10.17487/RFC4566</span>, <time datetime="2006-07">July 2006</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4566">https://www.rfc-editor.org/info/rfc4566</a>&gt;</span>. </dd>
2276 <dt id="RFC5039">[RFC5039]</dt>
2277 <dd>
2278 <span class="refAuthor">Rosenberg, J.</span><span class="refAuthor"> and C. Jennings</span>, <span class="refTitle">"The Session Initiation Protocol (SIP) and Spam"</span>, <span class="seriesInfo">RFC 5039</span>, <span class="seriesInfo">DOI 10.17487/RFC5039</span>, <time datetime="2008-01">January 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5039">https://www.rfc-editor.org/info/rfc5039</a>&gt;</span>. </dd>
2279 <dt id="RFC6350">[RFC6350]</dt>
2280 <dd>
2281 <span class="refAuthor">Perreault, S.</span>, <span class="refTitle">"vCard Format Specification"</span>, <span class="seriesInfo">RFC 6350</span>, <span class="seriesInfo">DOI 10.17487/RFC6350</span>, <time datetime="2011-08">August 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6350">https://www.rfc-editor.org/info/rfc6350</a>&gt;</span>. </dd>
2282 <dt id="RFC7092">[RFC7092]</dt>
2283 <dd>
2284 <span class="refAuthor">Kaplan, H.</span><span class="refAuthor"> and V. Pascual</span>, <span class="refTitle">"A Taxonomy of Session Initiation Protocol (SIP) Back-to-Back User Agents"</span>, <span class="seriesInfo">RFC 7092</span>, <span class="seriesInfo">DOI 10.17487/RFC7092</span>, <time datetime="2013-12">December 2013</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7092">https://www.rfc-editor.org/info/rfc7092</a>&gt;</span>. </dd>
2285 <dt id="RFC7340">[RFC7340]</dt>
2286 <dd>
2287 <span class="refAuthor">Peterson, J.</span><span class="refAuthor">, Schulzrinne, H.</span><span class="refAuthor">, and H. Tschofenig</span>, <span class="refTitle">"Secure Telephone Identity Problem Statement and Requirements"</span>, <span class="seriesInfo">RFC 7340</span>, <span class="seriesInfo">DOI 10.17487/RFC7340</span>, <time datetime="2014-09">September 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7340">https://www.rfc-editor.org/info/rfc7340</a>&gt;</span>. </dd>
2288 <dt id="RFC8197">[RFC8197]</dt>
2289 <dd>
2290 <span class="refAuthor">Schulzrinne, H.</span>, <span class="refTitle">"A SIP Response Code for Unwanted Calls"</span>, <span class="seriesInfo">RFC 8197</span>, <span class="seriesInfo">DOI 10.17487/RFC8197</span>, <time datetime="2017-07">July 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8197">https://www.rfc-editor.org/info/rfc8197</a>&gt;</span>. </dd>
2291 <dt id="RFC8224">[RFC8224]</dt>
2292 <dd>
2293 <span class="refAuthor">Peterson, J.</span><span class="refAuthor">, Jennings, C.</span><span class="refAuthor">, Rescorla, E.</span><span class="refAuthor">, and C. Wendt</span>, <span class="refTitle">"Authenticated Identity Management in the Session Initiation Protocol (SIP)"</span>, <span class="seriesInfo">RFC 8224</span>, <span class="seriesInfo">DOI 10.17487/RFC8224</span>, <time datetime="2018-02">February 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8224">https://www.rfc-editor.org/info/rfc8224</a>&gt;</span>. </dd>
2294 <dt id="RFC8259">[RFC8259]</dt>
2295 <dd>
2296 <span class="refAuthor">Bray, T., Ed.</span>, <span class="refTitle">"The JavaScript Object Notation (JSON) Data Interchange Format"</span>, <span class="seriesInfo">STD 90</span>, <span class="seriesInfo">RFC 8259</span>, <span class="seriesInfo">DOI 10.17487/RFC8259</span>, <time datetime="2017-12">December 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8259">https://www.rfc-editor.org/info/rfc8259</a>&gt;</span>. </dd>
2297 <dt id="RFC8445">[RFC8445]</dt>
2298 <dd>
2299 <span class="refAuthor">Keranen, A.</span><span class="refAuthor">, Holmberg, C.</span><span class="refAuthor">, and J. Rosenberg</span>, <span class="refTitle">"Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal"</span>, <span class="seriesInfo">RFC 8445</span>, <span class="seriesInfo">DOI 10.17487/RFC8445</span>, <time datetime="2018-07">July 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8445">https://www.rfc-editor.org/info/rfc8445</a>&gt;</span>. </dd>
2300 <dt id="SHAKEN">[SHAKEN]</dt>
2301 <dd>
2302 <span class="refAuthor">ATIS/SIP Forum IP-INNI Task Group</span>, <span class="refTitle">"Signature-based Handling of Asserted information using toKENs (SHAKEN)"</span>, <span class="seriesInfo">ATIS 1000074</span>, <time datetime="2017-01">January 2017</time>, <span>&lt;<a href="https://www.sipforum.org/download/sip-forum-twg-10-signature-based-handling-of-asserted-information-using-tokens-shaken-pdf/?wpdmdl=2813">https://www.sipforum.org/download/sip-forum-twg-10-signature-based-handling-of-asserted-information-using-tokens-shaken-pdf/?wpdmdl=2813</a>&gt;</span>. </dd>
2303 <dt id="SR-2275">[SR-2275]</dt>
2304 <dd>
2305 <span class="refAuthor">Telcordia</span>, <span class="refTitle">"Telcordia Notes on the Networks"</span>, <span class="seriesInfo">Telcordia SR-2275</span>, <time datetime="2000-10">October 2000</time>. </dd>
2306 </dl>
2307 </section>
2308 </section>
2309 <div id="Acknowledgements">
2310 <section id="section-appendix.a">
2311 <h2 id="name-acknowledgements">
2312 <a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a>
2313 </h2>
2314 <p id="section-appendix.a-1">This document liberally lifts from <span>[<a href="#RFC8197" class="xref">RFC8197</a>]</span> in its text and structure. However, the mechanism and
2315 purpose of 608 is quite different than 607. Any errors are the current
2316 editor's and not the editor of RFC 8197. Thanks also go to Ken Carlberg
2317 of the FCC, Russ Housley, Paul Kyzivat, and Tolga Asveren for their
2318 suggestions on improving the document. Tolga's suggestion to provide a
2319 mechanism for legacy interoperability served to expand the document by
2320 50%. In addition, Tolga came up with the jCard attack. Finally, Christer
2321 Holmberg, as always, provided a close reading and fixed a SIP
2322 feature-capability bug found by Yehoshua Gev.<a href="#section-appendix.a-1" class="pilcrow">¶</a></p>
2323 <p id="section-appendix.a-2">Of course, we appreciated the close read and five pages of comments
2324 from our estimable Area Director, Adam Roach. In addition, we received
2325 valuable comments during IETF Last Call and JWT review from Ines Robles,
2326 Mike Jones, and Brian Campbell, and IESG review from Alissa Cooper, Eric
2327 Vyncke, Alexey Melnikov, Benjamin Kaduk, Barry Leiba, and with most
2328 glee, Warren Kumari.<a href="#section-appendix.a-2" class="pilcrow">¶</a></p>
2329 <p id="section-appendix.a-3">Finally, Bhavik Nagda provided clarifying edits as well and, more
2330 especially, wrote and tested an implementation of the 608 response code
2331 in Kamailio. Code is available at <span><a href="https://github.com/nagdab/608_Implementation">https://github.com/nagdab/608_Implementation</a></span>. Grace Chuan
2332 from MIT regenerated and verified the JWT while working at the FCC.<a href="#section-appendix.a-3" class="pilcrow">¶</a></p>
2333 </section>
2334 </div>
2335 <div id="authors-addresses">
2336 <section id="section-appendix.b">
2337 <h2 id="name-authors-addresses">
2338 <a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
2339 </h2>
2340 <address class="vcard">
2341 <div dir="auto" class="left"><span class="fn nameRole">Eric W. Burger</span></div>
2342 <div dir="auto" class="left"><span class="org">Georgetown University</span></div>
2343 <div dir="auto" class="left"><span class="street-address">37th &amp; O St, NW</span></div>
2344 <div dir="auto" class="left">
2345 <span class="locality">Washington</span>, <span class="region">DC</span> <span class="postal-code">20057</span>
2346 </div>
2347 <div dir="auto" class="left"><span class="country-name">United States of America</span></div>
2348 <div class="email">
2349 <span>Email:</span>
2350 <a href="mailto:[email protected]" class="email">[email protected]</a>
2351 </div>
2352 </address>
2353 <address class="vcard">
2354 <div dir="auto" class="left"><span class="fn nameRole">Bhavik Nagda</span></div>
2355 <div dir="auto" class="left"><span class="org">Massachusetts Institute of Technology</span></div>
2356 <div dir="auto" class="left"><span class="street-address">77 Massachusetts Avenue</span></div>
2357 <div dir="auto" class="left">
2358 <span class="locality">Cambridge</span>, <span class="region">MA</span> <span class="postal-code">02139</span>
2359 </div>
2360 <div dir="auto" class="left"><span class="country-name">United States of America</span></div>
2361 <div class="email">
2362 <span>Email:</span>
2363 <a href="mailto:[email protected]" class="email">[email protected]</a>
2364 </div>
2365 </address>
2366 </section>
2367 </div>
2368 <script>var toc = document.getElementById("toc");
2369 var tocToggle = toc.querySelector("h2");
2370 var tocNav = toc.querySelector("nav");
2371
2372 // mobile menu toggle
2373 tocToggle.onclick = function(event) {
2374 if (window.innerWidth < 1024) {
2375 var tocNavDisplay = tocNav.currentStyle ? tocNav.currentStyle.display : getComputedStyle(tocNav, null).display;
2376 if (tocNavDisplay == "none") {
2377 tocNav.style.display = "block";
2378 } else {
2379 tocNav.style.display = "none";
2380 }
2381 }
2382 }
2383
2384 // toc anchor scroll to anchor
2385 tocNav.addEventListener("click", function (event) {
2386 event.preventDefault();
2387 if (event.target.nodeName == 'A') {
2388 if (window.innerWidth < 1024) {
2389 tocNav.style.display = "none";
2390 }
2391 var href = event.target.getAttribute("href");
2392 var anchorId = href.substr(1);
2393 var anchor = document.getElementById(anchorId);
2394 anchor.scrollIntoView(true);
2395 window.history.pushState("","",href);
2396 }
2397 });
2398
2399 // switch toc mode when window resized
2400 window.onresize = function () {
2401 if (window.innerWidth < 1024) {
2402 tocNav.style.display = "none";
2403 } else {
2404 tocNav.style.display = "block";
2405 }
2406 }
2407 </script>
2408 </body>
2409 </html>