refer to RFCs consistently (RFC XXXX);

7 files changed, 37 insertions, 37 deletions

diff --git a/src/lib/libc/net/getaddrinfo.3 b/src/lib/libc/net/getaddrinfo.3
index f91681dbcd..a9004e3207 100644
--- a/src/lib/libc/net/getaddrinfo.3
+++ b/src/lib/libc/net/getaddrinfo.3
@@ -1,4 +1,4 @@
-.\"     $OpenBSD: getaddrinfo.3,v 1.24 2003/07/27 15:34:03 jmc Exp $
+.\"     $OpenBSD: getaddrinfo.3,v 1.25 2003/08/08 09:26:02 jmc Exp $
 .\"     $KAME: getaddrinfo.3,v 1.29 2001/02/12 09:24:45 itojun Exp $
 .\"
 .\" Copyright (c) 1983, 1987, 1991, 1993
@@ -542,7 +542,7 @@ indicate an unknown error.
 .%A J. Bound
 .%A W. Stevens
 .%T Basic Socket Interface Extensions for IPv6
-.%R RFC2553
+.%R RFC 2553
 .%D March 1999
 .Re
 .Rs
@@ -566,7 +566,7 @@ The
 function is defined in IEEE POSIX 1003.1g draft specification,
 and documented in
 .Dq Basic Socket Interface Extensions for IPv6
-.Pq RFC2553 .
+.Pq RFC 2553 .
 .\"
 .Sh HISTORY
 The implementation first appeared in WIDE Hydrangea IPv6 protocol stack kit.
@@ -574,4 +574,4 @@ The implementation first appeared in WIDE Hydrangea IPv6 protocol stack kit.
 .Sh BUGS
 The current implementation is not thread-safe.
 .Pp
-The text was shamelessly copied from RFC2553.
+The text was shamelessly copied from RFC 2553.
diff --git a/src/lib/libc/net/getnameinfo.3 b/src/lib/libc/net/getnameinfo.3
index 606a95572c..03b6149e01 100644
--- a/src/lib/libc/net/getnameinfo.3
+++ b/src/lib/libc/net/getnameinfo.3
@@ -1,4 +1,4 @@
-.\"     $OpenBSD: getnameinfo.3,v 1.21 2003/06/02 20:18:35 millert Exp $
+.\"     $OpenBSD: getnameinfo.3,v 1.22 2003/08/08 09:26:02 jmc Exp $
 .\"     $KAME: getnameinfo.3,v 1.20 2001/01/05 13:37:37 itojun Exp $
 .\"
 .\" Copyright (c) 1983, 1987, 1991, 1993
@@ -253,7 +253,7 @@ The error code can be found in errno.
 .%A J. Bound
 .%A W. Stevens
 .%T Basic Socket Interface Extensions for IPv6
-.%R RFC2553
+.%R RFC 2553
 .%D March 1999
 .Re
 .Rs
@@ -277,7 +277,7 @@ The
 function is defined in IEEE POSIX 1003.1g draft specification,
 and documented in
 .Dq Basic Socket Interface Extensions for IPv6
-.Pq RFC2553 .
+.Pq RFC 2553 .
 .\"
 .Sh HISTORY
 The implementation first appeared in WIDE Hydrangea IPv6 protocol stack kit.
@@ -285,9 +285,9 @@ The implementation first appeared in WIDE Hydrangea IPv6 protocol stack kit.
 .Sh BUGS
 The current implementation is not thread-safe.
 .Pp
-The text was shamelessly copied from RFC2553.
+The text was shamelessly copied from RFC 2553.
 .Pp
 .Ox
 intentionally uses a different
 .Dv NI_MAXHOST
-value from what RFC2553 suggests, to avoid buffer length handling mistakes.
+value from what RFC 2553 suggests, to avoid buffer length handling mistakes.
diff --git a/src/lib/libc/net/if_indextoname.3 b/src/lib/libc/net/if_indextoname.3
index 2b7073328f..30293dcdf2 100644
--- a/src/lib/libc/net/if_indextoname.3
+++ b/src/lib/libc/net/if_indextoname.3
@@ -1,4 +1,4 @@
-.\"     $OpenBSD: if_indextoname.3,v 1.6 2003/06/02 20:18:35 millert Exp $
+.\"     $OpenBSD: if_indextoname.3,v 1.7 2003/08/08 09:26:02 jmc Exp $
 .\" Copyright (c) 1983, 1991, 1993
 .\"     The Regents of the University of California.  All rights reserved.
 .\"
@@ -130,7 +130,7 @@ on errors.
 .Xr networking 4
 .Pp
 R. Gilligan, S.  Thomson, J. Bound, and W. Stevens,
-``Basic Socket Interface Extensions for IPv6,'' RFC2553, March 1999.
+``Basic Socket Interface Extensions for IPv6,'' RFC 2553, March 1999.
 .Sh STANDARDS
 These functions are defined in ``Basic Socket Interface Extensions for IPv6''
-.Pq RFC2533 .
+.Pq RFC 2533 .
diff --git a/src/lib/libc/net/inet.3 b/src/lib/libc/net/inet.3
index 73beb8d7a4..cb974c9e85 100644
--- a/src/lib/libc/net/inet.3
+++ b/src/lib/libc/net/inet.3
@@ -1,4 +1,4 @@
-.\"     $OpenBSD: inet.3,v 1.16 2003/06/02 20:18:35 millert Exp $
+.\"     $OpenBSD: inet.3,v 1.17 2003/08/08 09:26:02 jmc Exp $
 .\"     $NetBSD: inet.3,v 1.7 1997/06/18 02:25:24 lukem Exp $
 .\"
 .\" Copyright (c) 1983, 1990, 1991, 1993
@@ -201,7 +201,7 @@ and
 .Xr getnameinfo 3
 are recommended rather than the functions presented here.
 .Pp
-The presentation format of an IPv6 address is given in [RFC1884 2.2]:
+The presentation format of an IPv6 address is given in [RFC 1884 2.2]:
 .Pp
 There are three conventional forms for representing IPv6 addresses as
 text strings:
diff --git a/src/lib/libc/net/inet6_option_space.3 b/src/lib/libc/net/inet6_option_space.3
index 8757641eac..4e5dc22711 100644
--- a/src/lib/libc/net/inet6_option_space.3
+++ b/src/lib/libc/net/inet6_option_space.3
@@ -1,4 +1,4 @@
-.\"     $OpenBSD: inet6_option_space.3,v 1.12 2003/06/02 20:18:35 millert Exp $
+.\"     $OpenBSD: inet6_option_space.3,v 1.13 2003/08/08 09:26:02 jmc Exp $
 .\"     $KAME: inet6_option_space.3,v 1.7 2000/05/17 14:32:13 itojun Exp $
 .\"
 .\" Copyright (c) 1983, 1987, 1991, 1993
@@ -61,7 +61,7 @@
 Building and parsing the Hop-by-Hop and Destination options is
 complicated due to alignment constraints, padding and
 ancillary data manipulation.
-RFC2292 defines a set of functions to help the application.
+RFC 2292 defines a set of functions to help the application.
 The function prototypes for
 these functions are all in the
 .Aq Pa netinet/in.h
@@ -99,7 +99,7 @@ is the number of options to be stored in the object.
 This is of little consequence, since it is assumed that most
 Hop-by-Hop option headers and Destination option headers carry only
 one option
-.Pq appendix B of [RFC-2460] .
+.Pq appendix B of [RFC 2460] .
 .\"
 .Ss inet6_option_init
 .Fn inet6_option_init
@@ -386,7 +386,7 @@ is not
 .Dv NULL .
 .\"
 .Sh EXAMPLES
-RFC2292 gives comprehensive examples in chapter 6.
+RFC 2292 gives comprehensive examples in chapter 6.
 .\"
 .Sh DIAGNOSTICS
 .Fn inet6_option_init
@@ -420,14 +420,14 @@ value.
 .%A W. Stevens
 .%A M. Thomas
 .%T "Advanced Sockets API for IPv6"
-.%N RFC2292
+.%N RFC 2292
 .%D February 1998
 .Re
 .Rs
 .%A S. Deering
 .%A R. Hinden
 .%T "Internet Protocol, Version 6 (IPv6) Specification"
-.%N RFC2460
+.%N RFC 2460
 .%D December 1998
 .Re
 .\"
@@ -435,10 +435,10 @@ value.
 The functions
 are documented in
 .Dq Advanced Sockets API for IPv6
-.Pq RFC2292 .
+.Pq RFC 2292 .
 .\"
 .Sh HISTORY
 The implementation first appeared in KAME advanced networking kit.
 .\"
 .Sh BUGS
-The text was shamelessly copied from RFC2292.
+The text was shamelessly copied from RFC 2292.
diff --git a/src/lib/libc/net/inet6_rthdr_space.3 b/src/lib/libc/net/inet6_rthdr_space.3
index 4db0fdd5e0..33b209af4f 100644
--- a/src/lib/libc/net/inet6_rthdr_space.3
+++ b/src/lib/libc/net/inet6_rthdr_space.3
@@ -1,4 +1,4 @@
-.\"     $OpenBSD: inet6_rthdr_space.3,v 1.12 2003/06/02 20:18:35 millert Exp $
+.\"     $OpenBSD: inet6_rthdr_space.3,v 1.13 2003/08/08 09:26:02 jmc Exp $
 .\"     $KAME: inet6_rthdr_space.3,v 1.8 2000/05/17 14:30:15 itojun Exp $
 .\"
 .\" Copyright (c) 1983, 1987, 1991, 1993
@@ -63,7 +63,7 @@
 .Fn inet6_rthdr_getflags "const struct cmsghdr *cmsg" "int index"
 .\"
 .Sh DESCRIPTION
-RFC2292 IPv6 advanced API defines eight
+RFC 2292 IPv6 advanced API defines eight
 functions that the application calls to build and examine a Routing
 header.
 Four functions build a Routing header:
@@ -258,10 +258,10 @@ or
 Upon an error the return value of the function is -1.
 .Pp
 Note: Addresses are indexed starting at 1, and flags starting at 0,
-to maintain consistency with the terminology and figures in RFC2460.
+to maintain consistency with the terminology and figures in RFC 2460.
 .\"
 .Sh EXAMPLES
-RFC2292 gives comprehensive examples in chapter 8.
+RFC 2292 gives comprehensive examples in chapter 8.
 .\"
 .Sh DIAGNOSTICS
 .Fn inet6_rthdr_space
@@ -290,14 +290,14 @@ return -1 on error.
 .%A W. Stevens
 .%A M. Thomas
 .%T "Advanced Sockets API for IPv6"
-.%N RFC2292
+.%N RFC 2292
 .%D February 1998
 .Re
 .Rs
 .%A S. Deering
 .%A R. Hinden
 .%T "Internet Protocol, Version 6 (IPv6) Specification"
-.%N RFC2460
+.%N RFC 2460
 .%D December 1998
 .Re
 .\"
@@ -305,13 +305,13 @@ return -1 on error.
 The functions
 are documented in
 .Dq Advanced Sockets API for IPv6
-.Pq RFC2292 .
+.Pq RFC 2292 .
 .\"
 .Sh HISTORY
 The implementation first appeared in KAME advanced networking kit.
 .\"
 .Sh BUGS
-The text was shamelessly copied from RFC2292.
+The text was shamelessly copied from RFC 2292.
 .Pp
 .Fn inet6_rthdr_reverse
 is not implemented yet.
diff --git a/src/lib/libc/net/resolver.3 b/src/lib/libc/net/resolver.3
index bb0ac86009..577420e9f1 100644
--- a/src/lib/libc/net/resolver.3
+++ b/src/lib/libc/net/resolver.3
@@ -1,4 +1,4 @@
-.\"     $OpenBSD: resolver.3,v 1.16 2003/06/02 20:18:36 millert Exp $
+.\"     $OpenBSD: resolver.3,v 1.17 2003/08/08 09:26:02 jmc Exp $
 .\"
 .\" Copyright (c) 1985, 1991, 1993
 .\"     The Regents of the University of California.  All rights reserved.
@@ -325,12 +325,12 @@ see
 .Xr hostname 7 ,
 .Xr named 8
 .Pp
-.%T RFC1032 ,
-.%T RFC1033 ,
-.%T RFC1034 ,
-.%T RFC1035 ,
-.%T RFC1535 ,
-.%T RFC974
+.%T RFC 1032 ,
+.%T RFC 1033 ,
+.%T RFC 1034 ,
+.%T RFC 1035 ,
+.%T RFC 1535 ,
+.%T RFC 974
 .Rs
 .%T "Name Server Operations Guide for BIND"
 .Re