From b5ad7dbf4968ab8fa92af67cdbd58a30f89ad3c7 Mon Sep 17 00:00:00 2001 From: Henrik Levkowetz Date: Fri, 7 Jun 2019 12:30:21 +0000 Subject: [PATCH] Updated references of RFC 5226 to RFC 8126, which obsoletes it. Fixes issue #2726. - Legacy-Id: 16235 --- ietf/templates/doc/shepherd_writeup.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ietf/templates/doc/shepherd_writeup.txt b/ietf/templates/doc/shepherd_writeup.txt index bf4e68b91..17ea610cb 100644 --- a/ietf/templates/doc/shepherd_writeup.txt +++ b/ietf/templates/doc/shepherd_writeup.txt @@ -118,7 +118,7 @@ Confirm that any referenced IANA registries have been clearly identified. Confirm that newly created IANA registries include a detailed specification of the initial contents for the registry, that allocations procedures for future registrations are defined, and a -reasonable name for the new registry has been suggested (see RFC 5226). +reasonable name for the new registry has been suggested (see RFC 8126). (18) List any new IANA registries that require Expert Review for future allocations. Provide any public guidance that the IESG would find @@ -249,7 +249,7 @@ Confirm that any referenced IANA registries have been clearly identified. Confirm that newly created IANA registries include a detailed specification of the initial contents for the registry, that allocations procedures for future registrations are defined, and a -reasonable name for the new registry has been suggested (see RFC 5226). +reasonable name for the new registry has been suggested (see RFC 8126). (18) List any new IANA registries that require Expert Review for future allocations. Provide any public guidance that the IESG would find