## 5 BSI Secure Networking Guide
### Content Completeness and Depth of the BSI Guide  
This section presents and evaluates the results of the assessment of the BSI guide for completeness and depth. The table follows the same scheme as in Section 4.1. The colums are: A = Count of covered RFCs, B = Count of relevant RFCs, C = Completeness, D = Weight (gray rows)/Importance Rating (white rows), E = Weighted Completeness (A*D), F = Depth. Category rows are shaded gray, with their subcategories below them (white rows). Values for subcategories are aggregated to the main categories. Totals are shown in the last line of the table (see Table 7). Overall:The BSI guide is not focused on details and also does not contain every aspect of IPv6. This can be seen when looking at the overall results. Only 66 out of the 213 relevant RFCs are covered in the guide, resulting in a completeness of 0.31 (31%). The weighted completeness increases this by 0.01 (1%) to 0.32 (32%). This means that the BSI guide, in general, takes the individual importance of the categories in consideration. Since the weights are quite evenly spread, their impact is only small. The depth is only 0.17. This is also due to the low coverage since missing RFCs receive a depth of 0 and thus have a huge negative impact on the overall depth. Nevertheless, this low value shows that the BSI guide does not explain all details of the included topics. \begin{table}
\begin{tabular}{l c c c c c c} \hline
**Category** & **A** & **B** & **C** & **D** & **E** & **F** \\ \hline Specification \& Address Format & 27 & 57 & 0.47 & 0.22 & 0.10 & 0.28 \\ \hline Specification & 3 & 4 & 0.75 & 6.17 & & 0.40 \\ Address Features & 14 & 19 & 0.74 & 6.69 & & 0.55 \\ Header & 7 & 13 & 0.54 & 6.05 & & 0.22 \\ Mobile IPv6 & 3 & 21 & 0.14 & 5.76 & & 0.06 \\ \hline IPsec \& ICMPv6 & 14 & 69 & 0.20 & 0.14 & 0.03 & 0.11 \\ \hline ICMPv6 Specification & 4 & 6 & 0.67 & 6.03 & & 0.40 \\ Neighbor Discovery & 5 & 11 & 0.45 & 6.59 & & 0.29 \\ Path MTU Discovery & 1 & 1 & 1.00 & 6.00 & & 0.40 \\ Multicast Listener Discovery & 2 & 5 & 0.40 & & 0.16 \\ IPsec & 2 & 13 & 0.15 & 6.93 & & 0.08 \\ IKEv2 & 0 & 13 & 0.00 & 5.66 & & 0.00 \\ Cryptographic Methods & 0 & 20 & 0.00 & 5.69 & & 0.00 \\ \hline DHCPv6 \& Autoconfiguration & 4 & 14 & 0.29 & 0.21 & 0.06 & 0.16 \\ \hline Stateless Autoconfiguration & 2 & 2 & 1.00 & 6.66 & & 0.60 \\ DHCPv6 & 2 & 12 & 0.17 & 6.28 & & 0.08 \\ \hline Routing \& DNS & 10 & 40 & 0.25 & 0.24 & 0.06 & 0.11 \\ \hline DNS Specification & 1 & 3 & 0.33 & 6.03 & & 0.27 \\ Security issues & 1 & 9 & 0.11 & 6.62 & & 0.04 \\ DNSSEC & 0 & 9 & 0.00 & 5.69 & & 0.00 \\ Multihoming & 1 & 7 & 0.14 & 5.00 & & 0.06 \\ Routing Protocols & 5 & 5 & 1.00 & 6.03 & & 0.40 \\ PIM & 2 & 7 & 0.29 & 4.62 & & 0.11 \\ \hline Transition Methods & 11 & 33 & 0.33 & 0.20 & 0.07 & 0.16 \\ \hline Dual Stack & 2 & 4 & 0.50 & 7.38 & & 0.25 \\ Tunneling & 6 & 16 & 0.38 & 6.38 & & 0.18 \\ Translation & 3 & 13 & 0.23 & 6.21 & & 0.11 \\ \hline Totals & **66** & **213** & **0.31** & & **0.32** & **0.17** \\ \hline \end{tabular}
\end{table} 
Table 7: BSI Content Completeness and Depth. Columns: A = Count of covered RFCs; B = Count of relevant RFCs; C = Completeness; D = Weight/Importance Rating; E = Weighted Completeness (A * D); F = Depth. Specification and Address format:Twenty-seven out of the 57 relevant RFCs are covered in the BSI guide which results in a completeness of 0.47 (47%) in this category. In particular, _Mobile IPv6_ is responsible for such a low value because only 3 of the possible 21 RFCs are at least mentioned. Without this subcategory, this result would be increased to 0.66. Also the other subcategories are missing some aspects, e.g., _Address Features_ and _Header_. Depth is at 0.28. This value also got negatively affected by _Mobile IPv6_ to a large extent. On the other hand, _Mobile IPv6_ is rated relatively low for importance in our survey and thus the low attention might be justifiable. The other subcategories are relatively well described concerning depth and respective importance, even though _Header_ should receive more coverage.