fixed a reference

lamps-wg · Nov 2, 2024 · bde46b1 · bde46b1
1 parent 95e052c
commit bde46b1
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 5 deletions.
diff --git a/draft-ietf-lamps-rfc4210bis.md b/draft-ietf-lamps-rfc4210bis.md
@@ -75,16 +75,16 @@ informative:
   RFC2585:
   RFC4210:
   RFC4212:
-  RFC4301:
   RFC4511:
   RFC5912:
   RFC6268:
   RFC6712:
+  RFC7296:
   RFC7299:
+  RFC8446:
   RFC8572:
   RFC8649:
   RFC8995:
-  RFC9110:
   RFC9147:
   RFC9162:
   I-D.ietf-anima-brski-ae:
@@ -791,7 +791,7 @@ information endangering the security of the PKI when intercepted. However,
 it might be possible for an eavesdropper to utilize the available information to
 gather confidential technical or business critical information. Therefore, users
 should consider protection of confidentiality on lower levels of the protocol
-stack, e.g., by using TLS {{RFC9110}}, DTLS {{RFC9147}}, or IPSEC {{RFC4301}}.
+stack, e.g., by using TLS {{RFC8446}}, DTLS {{RFC9147}}, or IPSEC {{RFC7296}}.
 
 
 

diff --git a/draft-ietf-lamps-rfc6712bis.md b/draft-ietf-lamps-rfc6712bis.md
@@ -70,9 +70,9 @@ informative:
   RFC9483:
   RFC2510:
   RFC4210:
-  RFC4301:
   RFC5246:
   RFC6712:
+  RFC7296:
   RFC8446:
   RFC9530:
   RFC9205:
@@ -444,7 +444,7 @@ users:
   certificates. Therefore, users of the HTTP transfer for CMP messages
   should consider using HTTP over TLS according to {{RFC9110}} and {{RFC9110}} or using virtual
   private networks created, for example, by utilizing Internet
-  Protocol Security according to {{RFC4301}}.
+  Protocol Security according to {{RFC7296}}.
 
 
 # IANA Considerations {#sect-6}