From 3d8f1b30675db567d3a2612379fd74fa879e4fb1 Mon Sep 17 00:00:00 2001
From: Miek Gieben <miek@miek.nl>
Date: Mon, 3 Sep 2018 07:27:10 +0100
Subject: [PATCH] Better references

Signed-off-by: Miek Gieben <miek@miek.nl>
---
 rfc/8341.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/rfc/8341.md b/rfc/8341.md
index a998847..ec13907 100644
--- a/rfc/8341.md
+++ b/rfc/8341.md
@@ -1646,7 +1646,7 @@ datastore.
 
 Note that the /nacm/groups data structure contains the administrative group names used by the
 server.  These group names may be configured locally and/or provided through an external protocol,
-such as RADIUS [@!RFC2865] [@!RFC5607].
+such as RADIUS [@RFC2865] [@RFC5607].
 
 An administrator needs to be aware of the security properties of any external protocol used by the
 transport layer to determine group names.  For example, if this protocol does not protect against
@@ -1749,7 +1749,9 @@ different access levels are needed, separate protocol operations should be defin
 <reference anchor='YANG-SEC' target='https://trac.ietf.org/trac/ops/wiki/yang-security-guidelines'>
 <front>
 <title>YANG Security Guidelines</title>
-<author/>
+<author>
+<organization>IETF</organization>
+</author>
 <date/>
 </front>
 <format type='HTML' target='https://trac.ietf.org/trac/ops/wiki/yang-security-guidelines'/>