1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
|
<pre>Internet Engineering Task Force (IETF) L. Zheng
Request for Comments: 7063 Huawei Technologies
Category: Informational Z. Zhang
ISSN: 2070-1721 Juniper Networks
R. Parekh
Cisco Systems
December 2013
<span class="h1">Survey Report on Protocol Independent Multicast - Sparse Mode (PIM-SM)</span>
<span class="h1">Implementations and Deployments</span>
Abstract
This document provides supporting documentation to advance the IETF
stream's Protocol Independent Multicast - Sparse Mode (PIM-SM)
protocol from Proposed Standard to Internet Standard.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc7063">http://www.rfc-editor.org/info/rfc7063</a>.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Zheng, et al. Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7063">RFC 7063</a> Survey Report on PIM-SM December 2013</span>
Table of Contents
<a href="#section-1">1</a>. Motivation ......................................................<a href="#page-3">3</a>
<a href="#section-1.1">1.1</a>. Overview of PIM-SM .........................................<a href="#page-3">3</a>
<a href="#section-1.2">1.2</a>. Requirements of RFCs 2026 and 6410 .........................<a href="#page-3">3</a>
<a href="#section-2">2</a>. Survey on Implementations and Deployments .......................<a href="#page-4">4</a>
<a href="#section-2.1">2.1</a>. Methodology ................................................<a href="#page-4">4</a>
<a href="#section-2.2">2.2</a>. Operator Responses .........................................<a href="#page-4">4</a>
<a href="#section-2.2.1">2.2.1</a>. Description of PIM-SM Deployments ...................<a href="#page-4">4</a>
2.2.2. PIM-SM Deployment with Other Multicast
Technologies ........................................<a href="#page-4">4</a>
2.2.3. PIM-SM Rendezvous Points (RPs) and RP
Discovery Mechanisms ................................<a href="#page-4">4</a>
<a href="#section-2.3">2.3</a>. Vendor Responses ...........................................<a href="#page-5">5</a>
<a href="#section-2.3.1">2.3.1</a>. Implementations Based on RFCs 4601 and 2362 .........<a href="#page-5">5</a>
<a href="#section-2.3.2">2.3.2</a>. Lack of (*,*,RP) and PMBR Implementations ...........<a href="#page-5">5</a>
<a href="#section-2.3.3">2.3.3</a>. Implementations of Other Features of <a href="./rfc4601">RFC 4601</a> .......<a href="#page-5">5</a>
<a href="#section-2.4">2.4</a>. Key Findings ...............................................<a href="#page-6">6</a>
<a href="#section-3">3</a>. Security Considerations .........................................<a href="#page-6">6</a>
<a href="#section-4">4</a>. Acknowledgements ................................................<a href="#page-6">6</a>
<a href="#section-5">5</a>. References ......................................................<a href="#page-6">6</a>
<a href="#section-5.1">5.1</a>. Normative References .......................................<a href="#page-6">6</a>
<a href="#section-5.2">5.2</a>. Informative References .....................................<a href="#page-7">7</a>
<a href="#appendix-A">Appendix A</a>. Questionnaire ..........................................<a href="#page-8">8</a>
<a href="#appendix-A.1">A.1</a>. PIM Survey for Operators ....................................<a href="#page-8">8</a>
<a href="#appendix-A.2">A.2</a>. PIM Survey for Implementors ................................<a href="#page-10">10</a>
<span class="grey">Zheng, et al. Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7063">RFC 7063</a> Survey Report on PIM-SM December 2013</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Motivation</span>
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Overview of PIM-SM</span>
Protocol Independent Multicast - Sparse Mode (PIM-SM) was first
published as [<a href="./rfc2117" title=""Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification"">RFC2117</a>] in 1997. This version was then obsoleted by
[<a href="./rfc2362" title=""Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification"">RFC2362</a>] in 1998. The protocol was classified as Experimental in
both documents. The protocol specification was then rewritten in
whole and advanced to Proposed Standard as [<a href="./rfc4601" title=""Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)"">RFC4601</a>] in 2006.
Considering its multiple independent implementations developed and
sufficient successful operational experience gained, the PIM WG
decided to advance the PIM-SM protocol to Internet Standard. The
conducted survey and this document are part of the work.
<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Requirements of RFCs 2026 and 6410</span>
[<a id="ref-RFC2026">RFC2026</a>] defines the stages in the standardization process, the
requirements for moving a document between stages, and the types of
documents used during this process. <a href="./rfc2026#section-4.1.2">Section 4.1.2 of [RFC2026]</a>
states that:
The requirement for at least two independent and interoperable
implementations applies to all of the options and features of the
specification. In cases in which one or more options or features
have not been demonstrated in at least two interoperable
implementations, the specification may advance to the Draft
Standard level only if those options or features are removed.
[<a id="ref-RFC6410">RFC6410</a>] updates the IETF Standards Process defined in [<a href="./rfc2026" title=""The Internet Standards Process -- Revision 3"">RFC2026</a>].
Primarily, it reduces the Standards Process from three Standards
Track maturity levels to two. The second maturity level is a
combination of Draft Standard and Standard as specified in [<a href="./rfc2026" title=""The Internet Standards Process -- Revision 3"">RFC2026</a>].
<a href="./rfc6410#section-2.2">Section 2.2 of [RFC6410]</a> states that:
(1) There are at least two independent interoperating
implementations with widespread deployment and successful
operational experience.
(2)...
(3) There are no unused features in the specification that greatly
increase implementation complexity.
Optional features that do not meet the aforesaid criteria have been
identified by the PIM Working Group and will be removed. This
document provides supporting documentation to advance the IETF
stream's Protocol Independent Multicast - Sparse Mode (PIM-SM)
protocol from Proposed Standard to Internet Standard.
<span class="grey">Zheng, et al. Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7063">RFC 7063</a> Survey Report on PIM-SM December 2013</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Survey on Implementations and Deployments</span>
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Methodology</span>
A questionnaire was issued by the PIM WG co-chairs and announced
widely to the vendors and operational community to obtain information
on PIM-SM implementations and deployments. The survey concluded on
22 Oct 2012. The responses remain confidential and only combined
results are published here, while responders chose whether to keep
their affiliations confidential. The raw questionnaire is shown in
<a href="#appendix-A">Appendix A</a>, and a compilation of the responses is included in the
following section.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Operator Responses</span>
Nine operators responded to the survey. They are SWITCH, National
Research Council Canada, South Dakota School of Mines and Technology,
Motorola Solutions, and five anonymous operators.
<span class="h4"><a class="selflink" id="section-2.2.1" href="#section-2.2.1">2.2.1</a>. Description of PIM-SM Deployments</span>
Since 1998, PIM-SM has been deployed for a wide variety of
applications: Campus, Enterprise, Research and WAN networks,
Broadband ISP, and Digital TV. There are five deployments based on
[<a href="./rfc4601" title=""Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)"">RFC4601</a>] implementations and two on [<a href="./rfc2362" title=""Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification"">RFC2362</a>] implementations. PIM-
SM for IPv6 has been deployed by three operators. Out of the nine
operators, six have deployed PIM-SM implementations from multiple
vendors.
Operators reported minor interoperability issues and these were
addressed by the vendors. There was no major interoperability
concern reported by the operators.
<span class="h4"><a class="selflink" id="section-2.2.2" href="#section-2.2.2">2.2.2</a>. PIM-SM Deployment with Other Multicast Technologies</span>
Except for one deployment of PIM-SM with Multicast Extensions to OSPF
(MOSPF), all other operators have deployed PIM-SM exclusively. No
operators acknowledged deployments of either (*,*,RP) or PIM
Multicast Border Route (PMBR) for interconnection between PIM-SM and
other multicast domains.
<span class="h4"><a class="selflink" id="section-2.2.3" href="#section-2.2.3">2.2.3</a>. PIM-SM Rendezvous Points (RPs) and RP Discovery Mechanisms</span>
The number of PIM-SM RPs deployed by operators ranges from a few
(e.g., sixteen) to a massively scaled number (four hundred). Both
static configuration and Bootstrap Router (BSR) have been deployed as
RP discovery mechanisms.
<span class="grey">Zheng, et al. Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7063">RFC 7063</a> Survey Report on PIM-SM December 2013</span>
Anycast-RP has been deployed for RP redundancy. Two operators have
deployed Anycast-RP using the Multicast Source Discovery Protocol
(MSDP) [<a href="./rfc3446" title=""Anycast Rendevous Point (RP) mechanism using Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP)"">RFC3446</a>]. Three operators have deployed Anycast-RP using
both MSDP [<a href="./rfc3446" title=""Anycast Rendevous Point (RP) mechanism using Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP)"">RFC3446</a>] and PIM [<a href="./rfc4610" title=""Anycast-RP Using Protocol Independent Multicast (PIM)"">RFC4610</a>] for different scenarios. The
best common practice seems to be to use static-RP configuration with
Anycast-RP for redundancy.
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Vendor Responses</span>
Eight vendors reported PIM-SM implementations. They are XORP, Huawei
Technologies, Cisco Systems, Motorola Solutions, Juniper Networks,
and three other anonymous vendors.
<span class="h4"><a class="selflink" id="section-2.3.1" href="#section-2.3.1">2.3.1</a>. Implementations Based on RFCs 4601 and 2362</span>
Four vendors reported PIM-SM implementations based on [<a href="./rfc4601" title=""Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)"">RFC4601</a>] and
two reported PIM-SM implementations based on [<a href="./rfc2362" title=""Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification"">RFC2362</a>]. Two other
reported implementations are hybrids.
Minor interoperability issues have been addressed by the vendors over
the years and no concerns were reported by any vendor.
<span class="h4"><a class="selflink" id="section-2.3.2" href="#section-2.3.2">2.3.2</a>. Lack of (*,*,RP) and PMBR Implementations</span>
Most vendors have not implemented (*,*,RP) state as specified in
[<a href="./rfc4601" title=""Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)"">RFC4601</a>] either due to lack of deployment requirements or due to
security concerns. Similarly, most vendors have also not implemented
PMBR due to lack of deployment requirements or because it was
considered too complex and non-scalable.
Only one vendor, XORP, reported (*,*,RP) and PMBR implementation and
they were implemented just because these were part of the [<a href="./rfc4601" title=""Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)"">RFC4601</a>]
specification.
<span class="h4"><a class="selflink" id="section-2.3.3" href="#section-2.3.3">2.3.3</a>. Implementations of Other Features of <a href="./rfc4601">RFC 4601</a></span>
Most vendors have implemented all of the following from the [<a href="./rfc4601" title=""Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)"">RFC4601</a>]
specification:
o Source-Specific Multicast (SSM)
o Join suppression
o Explicit tracking
o Register mechanism
o Shortest Path Tree (SPT) switchover at last-hop router
<span class="grey">Zheng, et al. Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7063">RFC 7063</a> Survey Report on PIM-SM December 2013</span>
o Assert mechanism
o Hashing of group to RP mappings
Some vendors do not implement explicit tracking and SSM.
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Key Findings</span>
PIM-SM has been widely implemented and deployed for different
applications. The protocol is sufficiently well specified in
[<a href="./rfc4601" title=""Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)"">RFC4601</a>] resulting in interoperable implementation deployed by
operators.
There are no deployments and only one known implementation of
(*,*,RP) and PMBR as specified in [<a href="./rfc4601" title=""Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)"">RFC4601</a>]. Hence, it is necessary
to remove these features from the specification as required by
[<a href="./rfc2026" title=""The Internet Standards Process -- Revision 3"">RFC2026</a>] and [<a href="./rfc6410" title=""Reducing the Standards Track to Two Maturity Levels"">RFC6410</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security Considerations</span>
The PIM WG is aware of at least three (and believes there are more)
PIM-SM implementations that support the use of IPsec to protect PIM
messages. For at least one of them, IPsec is not part of the PIM
implementation itself -- one just configures IPsec with Security
Policy Databases (SPDs) where interface, the ALL_PIM_ROUTERS
multicast address, etc., can be used as selectors, according to
[<a href="./rfc5796" title=""Authentication and Confidentiality in Protocol Independent Multicast Sparse Mode (PIM-SM) Link-Local Messages"">RFC5796</a>].
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Acknowledgements</span>
The authors would like to thank Tim Chown and Bill Atwood, who helped
to collect and anonymize the responses as the neutral third party.
Special thanks are also given to Alexander Gall, William F. Maton
Sotomayor, Steve Bauer, Sonum Mathur, Pavlin Radoslavov, Shuxue Fan,
Sameer Gulrajani, and to the anonymous responders.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. References</span>
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Normative References</span>
[<a id="ref-RFC2026">RFC2026</a>] Bradner, S., "The Internet Standards Process -- Revision
3", <a href="https://www.rfc-editor.org/bcp/bcp9">BCP 9</a>, <a href="./rfc2026">RFC 2026</a>, October 1996.
[<a id="ref-RFC6410">RFC6410</a>] Housley, R., Crocker, D., and E. Burger, "Reducing the
Standards Track to Two Maturity Levels", <a href="https://www.rfc-editor.org/bcp/bcp9">BCP 9</a>, <a href="./rfc6410">RFC 6410</a>,
October 2011.
<span class="grey">Zheng, et al. Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7063">RFC 7063</a> Survey Report on PIM-SM December 2013</span>
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Informative References</span>
[<a id="ref-RFC2117">RFC2117</a>] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering,
S., Handley, M., Jacobson, V., Liu, C., Sharma, P., and L.
Wei, "Protocol Independent Multicast-Sparse Mode (PIM-SM):
Protocol Specification", <a href="./rfc2117">RFC 2117</a>, June 1997.
[<a id="ref-RFC2362">RFC2362</a>] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering,
S., Handley, M., and V. Jacobson, "Protocol Independent
Multicast-Sparse Mode (PIM-SM): Protocol Specification",
<a href="./rfc2362">RFC 2362</a>, June 1998.
[<a id="ref-RFC3446">RFC3446</a>] Kim, D., Meyer, D., Kilmer, H., and D. Farinacci, "Anycast
Rendevous Point (RP) mechanism using Protocol Independent
Multicast (PIM) and Multicast Source Discovery Protocol
(MSDP)", <a href="./rfc3446">RFC 3446</a>, January 2003.
[<a id="ref-RFC4601">RFC4601</a>] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
"Protocol Independent Multicast - Sparse Mode (PIM-SM):
Protocol Specification (Revised)", <a href="./rfc4601">RFC 4601</a>, August 2006.
[<a id="ref-RFC4610">RFC4610</a>] Farinacci, D. and Y. Cai, "Anycast-RP Using Protocol
Independent Multicast (PIM)", <a href="./rfc4610">RFC 4610</a>, August 2006.
[<a id="ref-RFC5796">RFC5796</a>] Atwood, W., Islam, S., and M. Siami, "Authentication and
Confidentiality in Protocol Independent Multicast Sparse
Mode (PIM-SM) Link-Local Messages", <a href="./rfc5796">RFC 5796</a>, March 2010.
<span class="grey">Zheng, et al. Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc7063">RFC 7063</a> Survey Report on PIM-SM December 2013</span>
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Questionnaire</span>
This section provides copies of the questionnaires exactly as
distributed to operators and implementors.
<span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a>. PIM Survey for Operators</span>
Introduction:
PIM-SM was first published as <a href="./rfc2117">RFC2117</a> in 1997 and then again as
<a href="./rfc2362">RFC2362</a> in 1998. The protocol was classified as Experimental in
both of these documents. The PIM-SM protocol specification was then
rewritten in whole and advanced to Proposed Standard as <a href="./rfc4601">RFC4601</a> in
2006. Considering the multiple independent implementations developed
and the successful operational experience gained, the IETF has
decided to advance the PIM-SM routing protocol to Draft Standard.
This survey intends to provide supporting documentation to advance
the Protocol Independent Multicast - Sparse Mode (PIM-SM) routing
protocol from IETF Proposed Standard to Draft Standard. (Due to
<a href="./rfc6410">RFC6410</a>, now the intention is to progress it to Internet Standard.
Draft Standard is no longer used.)
This survey is issued on behalf of the IETF PIM Working Group.
The responses will be collected by a neutral third-party and kept
strictly confidential if requested in the response; only the final
combined results will be published. Tim Chown and Bill Atwood have
agreed to anonymize the response to this Questionnaire. They have a
long experience with multicast but have no direct financial interest
in this matter, nor ties to any of the vendors involved. Tim is
working at University of Southampton, UK, and he has been active in
the IETF for many years, including the mboned working group, and he
is a co-chair of the 6renum working group. Bill is at Concordia
University, Montreal, Canada, and he has been an active participant
in the IETF pim working group for over ten years, especially in the
area of security.
Please send questionnaire responses addressed to them both. The
addresses are tjc@ecs.soton.ac.uk and william.atwood@concordia.ca.
Please include the string "<a href="./rfc4601">RFC4601</a> bis Questionnaire" in the subject
field.
<span class="grey">Zheng, et al. Informational [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc7063">RFC 7063</a> Survey Report on PIM-SM December 2013</span>
Before answering the questions, please complete the following
background information.
Name of the Respondent:
Affiliation/Organization:
Contact Email:
Provide description of PIM deployment:
Do you wish to keep the information provided confidential:
Questions:
1 Have you deployed PIM-SM in your network?
2 How long have you had PIM-SM deployed in your network? Do you know
if your deployment is based on the most recent <a href="./rfc4601">RFC4601</a>?
3 Have you deployed PIM-SM for IPv6 in your network?
4 Are you using equipment with different (multi-vendor) PIM-SM
implementations for your deployment?
5 Have you encountered any inter-operability or backward-
compatibility issues amongst differing implementations? If yes,
what are your concerns about these issues?
6 Have you deployed both dense mode and sparse mode in your network?
If yes, do you route between these modes using features such as
*,*,RP or PMBR?
7 To what extent have you deployed PIM functionality, like BSR, SSM,
and Explicit Tracking?
8 Which RP mapping mechanism do you use: Static, AutoRP, or BSR?
9 How many RPs have you deployed in your network?
10 If you use Anycast-RP, is it Anycast-RP using MSDP (<a href="./rfc3446">RFC 3446</a>) or
Anycast-RP using PIM (<a href="./rfc4610">RFC4610</a>)?
11 Do you have any other comments on PIM-SM deployment in your
network?
<span class="grey">Zheng, et al. Informational [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc7063">RFC 7063</a> Survey Report on PIM-SM December 2013</span>
<span class="h3"><a class="selflink" id="appendix-A.2" href="#appendix-A.2">A.2</a>. PIM Survey for Implementors</span>
Introduction:
PIM-SM was first published as <a href="./rfc2117">RFC2117</a> in 1997 and then again as
<a href="./rfc2362">RFC2362</a> in 1998. The protocol was classified as Experimental in both
of these documents. The PIM-SM protocol specification was then
rewritten in whole and advanced to Proposed Standard as <a href="./rfc4601">RFC4601</a> in
2006. Considering the multiple independent implementations developed
and the successful operational experience gained, the IETF has
decided to advance the PIM-SM routing protocol to Draft Standard.
This survey intends to provide supporting documentation to advance
the Protocol Independent Multicast - Sparse Mode (PIM-SM) routing
protocol from IETF Proposed Standard to Draft Standard. (Due to
<a href="./rfc6410">RFC6410</a>, now the intention is to progress it to Internet Standard.
Draft Standard is no longer used.)
This survey is issued on behalf of the IETF PIM Working Group.
The responses will be collected by a neutral third-party and kept
strictly confidential if requested in the response; only the final
combined results will be published. Tim Chown and Bill Atwood have
agreed to anonymize the response to this Questionnaire. They have a
long experience with multicast but have no direct financial interest
in this matter, nor ties to any of the vendors involved. Tim is
working at University of Southampton, UK, and he has been active in
the IETF for many years, including the mboned working group, and he
is a co-chair of the 6renum working group. Bill is at Concordia
University, Montreal, Canada, and he has been an active participant
in the IETF pim working group for over ten years, especially in the
area of security.
Please send questionnaire responses addressed to them both. The
addresses are tjc@ecs.soton.ac.uk and william.atwood@concordia.ca.
Please include the string "<a href="./rfc4601">RFC 4601</a> bis Questionnaire" in the subject
field.
<span class="grey">Zheng, et al. Informational [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc7063">RFC 7063</a> Survey Report on PIM-SM December 2013</span>
Before answering the questions, please complete the following
background information.
Name of the Respondent:
Affiliation/Organization:
Contact Email:
Provide description of PIM implementation:
Do you wish to keep the information provided confidential:
Questions:
1 Have you implemented PIM-SM?
2 Is the PIM-SM implementation based on <a href="./rfc2362">RFC2362</a> or <a href="./rfc4601">RFC4601</a>?
3 Have you implemented (*,*, RP) state of <a href="./rfc4601">RFC4601</a>? What is the
rationale behind implementing or omitting (*,*,RP)?
4 Have you implemented the PMBR as specified in <a href="./rfc4601">RFC4601</a> and <a href="./rfc2715">RFC2715</a>?
What is the rationale behind implementing or omitting PMBR?
5 Have you implemented other features and functions of <a href="./rfc4601">RFC4601</a>:
- SSM
- Join Suppression
- Explicit tracking
- Register mechanism
- SPT switchover at last-hop router
- Assert mechanism
- Hashing of group to RP mappings
6 Does your PIM-SM implementation support IPv6?
7 Have you encountered any inter-operability issues with other PIM
implementations in trials or in the field?
8 Do you have any other comments or concerns about PIM-SM as
specified in <a href="./rfc4601">RFC4601</a>?
<span class="grey">Zheng, et al. Informational [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc7063">RFC 7063</a> Survey Report on PIM-SM December 2013</span>
Authors' Addresses
Lianshu Zheng
Huawei Technologies
China
EMail: vero.zheng@huawei.com
Zhaohui Zhang
Juniper Networks
USA
EMail: zzhang@juniper.net
Rishabh Parekh
Cisco Systems
USA
EMail: riparekh@cisco.com
Zheng, et al. Informational [Page 12]
</pre>
|
