|
9 | 9 | <meta content=" |
10 | 10 | Blocking clients by IP address creates not only local availability problems for clients, but also can foster conditions that lead to systemic issues, such as centralization of Internet protocols. This document makes recommendations to mitigate these effects. |
11 | 11 | " name="description"> |
12 | | -<meta content="xml2rfc 3.30.0" name="generator"> |
| 12 | +<meta content="xml2rfc 3.31.0" name="generator"> |
13 | 13 | <meta content="Internet-Draft" name="keyword"> |
14 | 14 | <meta content="draft-nottingham-blocking-best-practices-latest" name="ietf.draft"> |
15 | 15 | <!-- Generator version information: |
16 | | - xml2rfc 3.30.0 |
17 | | - Python 3.12.11 |
| 16 | + xml2rfc 3.31.0 |
| 17 | + Python 3.12.12 |
18 | 18 | ConfigArgParse 1.7 |
19 | 19 | google-i18n-address 3.1.1 |
20 | 20 | intervaltree 3.1.0 |
21 | 21 | Jinja2 3.1.6 |
22 | 22 | lxml 5.3.1 |
23 | | - platformdirs 4.3.8 |
| 23 | + platformdirs 4.5.0 |
24 | 24 | pycountry 24.6.1 |
25 | 25 | PyYAML 6.0.2 |
26 | | - requests 2.32.4 |
27 | | - setuptools 80.9.0 |
28 | | - wcwidth 0.2.13 |
| 26 | + requests 2.32.5 |
| 27 | + wcwidth 0.2.14 |
29 | 28 | --> |
30 | 29 | <link href="draft-nottingham-blocking-best-practices.xml" rel="alternate" type="application/rfc+xml"> |
31 | 30 | <link href="#copyright" rel="license"> |
|
1044 | 1043 | <thead><tr> |
1045 | 1044 | <td class="left">Internet-Draft</td> |
1046 | 1045 | <td class="center">Blocking by IP Address</td> |
1047 | | -<td class="right">August 2025</td> |
| 1046 | +<td class="right">October 2025</td> |
1048 | 1047 | </tr></thead> |
1049 | 1048 | <tfoot><tr> |
1050 | 1049 | <td class="left">Nottingham</td> |
1051 | | -<td class="center">Expires 6 February 2026</td> |
| 1050 | +<td class="center">Expires 29 April 2026</td> |
1052 | 1051 | <td class="right">[Page]</td> |
1053 | 1052 | </tr></tfoot> |
1054 | 1053 | </table> |
|
1061 | 1060 | <dd class="internet-draft">draft-nottingham-blocking-best-practices-latest</dd> |
1062 | 1061 | <dt class="label-published">Published:</dt> |
1063 | 1062 | <dd class="published"> |
1064 | | -<time datetime="2025-08-05" class="published">5 August 2025</time> |
| 1063 | +<time datetime="2025-10-26" class="published">26 October 2025</time> |
1065 | 1064 | </dd> |
1066 | 1065 | <dt class="label-intended-status">Intended Status:</dt> |
1067 | 1066 | <dd class="intended-status">Best Current Practice</dd> |
1068 | 1067 | <dt class="label-expires">Expires:</dt> |
1069 | | -<dd class="expires"><time datetime="2026-02-06">6 February 2026</time></dd> |
| 1068 | +<dd class="expires"><time datetime="2026-04-29">29 April 2026</time></dd> |
1070 | 1069 | <dt class="label-authors">Author:</dt> |
1071 | 1070 | <dd class="authors"> |
1072 | 1071 | <div class="author"> |
@@ -1111,7 +1110,7 @@ <h2 id="name-status-of-this-memo"> |
1111 | 1110 | time. It is inappropriate to use Internet-Drafts as reference |
1112 | 1111 | material or to cite them other than as "work in progress."<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p> |
1113 | 1112 | <p id="section-boilerplate.1-4"> |
1114 | | - This Internet-Draft will expire on 6 February 2026.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p> |
| 1113 | + This Internet-Draft will expire on 29 April 2026.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p> |
1115 | 1114 | </section> |
1116 | 1115 | </div> |
1117 | 1116 | <div id="copyright"> |
|
0 commit comments