mischief/openbsd-src
1
0
Fork 0
mirror of https://github.com/openbsd/src.git synced 2024-12-22 16:42:56 -08:00
Code

refer to RFCs consistently (RFC XXXX);

Browse Source
This commit is contained in:
jmc 2003-08-08 10:13:33 +00:00
parent 51d125d743
commit 89f4369686
10 changed files with 37 additions and 37 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
usr.bin/nc/nc.1
View File

@ -1,4 +1,4 @@
.\" $OpenBSD: nc.1,v 1.24 2003/01/05 09:39:39 pvalchev Exp $
.\" $OpenBSD: nc.1,v 1.25 2003/08/08 10:13:33 jmc Exp $
.\"
.\" Copyright (c) 1996 David Sacerdote
.\" All rights reserved.
@ -119,7 +119,7 @@ Specifies the IP of the interface which is used to send the packets.
.It Fl t
Causes
.Nm
to send RFC854 DON'T and WON'T responses to RFC854 DO and WILL requests.
to send RFC 854 DON'T and WON'T responses to RFC 854 DO and WILL requests.
This makes it possible to use
.Nm
to script telnet sessions.

4
usr.bin/skey/skey.1
View File

@ -1,4 +1,4 @@
.\" $OpenBSD: skey.1,v 1.22 2001/06/20 17:12:29 millert Exp $
.\" $OpenBSD: skey.1,v 1.23 2003/08/08 10:13:33 jmc Exp $
.\" @(#)skey.1 1.1 10/28/93
.\"
.Dd October 28, 1993
@ -88,7 +88,7 @@ Selects RMD-160 (160 bit Ripe Message Digest) as the hash algorithm.
.Xr skeyinfo 1 ,
.Xr skeyinit 1
.Pp
.Em RFC2289
.Em RFC 2289
.Sh TRADEMARKS AND PATENTS
S/Key is a Trademark of Bellcore.
.Sh AUTHORS

6
usr.sbin/arp/arp.4
View File

@ -1,4 +1,4 @@
.\" $OpenBSD: arp.4,v 1.16 2003/06/12 12:59:49 jmc Exp $
.\" $OpenBSD: arp.4,v 1.17 2003/08/08 10:13:33 jmc Exp $
.\" $NetBSD: arp.4,v 1.2 1995/03/01 11:50:56 chopps Exp $
.\"
.\" Copyright (c) 1985, 1986, 1988, 1994
@ -132,11 +132,11 @@ The routing information is not modified.
.Rs
.%A Plummer, D.
.%B "An Ethernet Address Resolution Protocol"
.%T RFC826
.%T RFC 826
.Re
.Rs
.%A Karels, M.J.
.%A Leffler, S.J.
.%B Trailer Encapsulations
.%T RFC893
.%T RFC 893
.Re

4
usr.sbin/faithd/faithd.8
View File

@ -1,4 +1,4 @@
.\" $OpenBSD: faithd.8,v 1.26 2003/07/02 09:14:30 jmc Exp $
.\" $OpenBSD: faithd.8,v 1.27 2003/08/08 10:13:33 jmc Exp $
.\" $KAME: faithd.8,v 1.36 2002/05/09 13:59:16 itojun Exp $
.\"
.\" Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project.
@ -315,7 +315,7 @@ setting.
.%A Jun-ichiro itojun Hagino
.%A Kazu Yamamoto
.%T "An IPv6-to-IPv4 transport relay translator"
.%B RFC3142
.%B RFC 3142
.%O ftp://ftp.isi.edu/in-notes/rfc3142.txt
.%D June 2001
.Re

6
usr.sbin/mrouted/mrouted.8
View File

@ -1,4 +1,4 @@
.\" $OpenBSD: mrouted.8,v 1.13 2003/06/12 12:59:51 jmc Exp $
.\" $OpenBSD: mrouted.8,v 1.14 2003/08/08 10:13:33 jmc Exp $
.\" The mrouted program is covered by the license in the accompanying file
.\" named "LICENSE". Use of the mrouted program represents acceptance of
.\" the terms and conditions listed in that file.
@ -19,9 +19,9 @@
.Sh DESCRIPTION
.Nm
is an implementation of the Distance-Vector Multicast Routing
Protocol (DVMRP), an earlier version of which is specified in RFC-1075.
Protocol (DVMRP), an earlier version of which is specified in RFC 1075.
It maintains topological knowledge via a distance-vector routing protocol
(like RIP, described in RFC-1058), upon which it implements a multicast
(like RIP, described in RFC 1058), upon which it implements a multicast
datagram forwarding algorithm called Reverse Path Multicasting.
.Pp
.Nm

22
usr.sbin/openssl/openssl.1
View File

@ -1,4 +1,4 @@
.\" $OpenBSD: openssl.1,v 1.10 2003/07/16 09:05:58 jmc Exp $
.\" $OpenBSD: openssl.1,v 1.11 2003/08/08 10:13:33 jmc Exp $
.\" ====================================================================
.\" Copyright (c) 1998-2002 The OpenSSL Project. All rights reserved.
.\"
@ -2204,7 +2204,7 @@ The options are as follows:
This specifies the input format.
The
.Ar DER
argument uses an ASN1 DER encoded form compatible with RFC2459 (PKIX)
argument uses an ASN1 DER encoded form compatible with RFC 2459 (PKIX)
DSS-Parms that is a SEQUENCE consisting of p, q and g, respectively.
The
.Ar PEM
@ -3164,7 +3164,7 @@ If neither option is present then the
field is omitted meaning fresh revocation information is immediately available.
.El
.Sh OCSP RESPONSE VERIFICATION
OCSP Response follows the rules specified in RFC2560.
OCSP Response follows the rules specified in RFC 2560.
.Pp
Initially the OCSP responder certificate is located and the signature on
the OCSP request checked using the responder certificate's public key.
@ -3460,8 +3460,8 @@ For compatibility with some CAs it will also accept:
.Sh PKCS7 RESTRICTIONS
There is no option to print out all the fields of a PKCS#7 file.
.Pp
The PKCS#7 routines only understand PKCS#7 v 1.5 as specified in RFC2315.
They cannot currently parse, for example, the new CMS as described in RFC2630.
The PKCS#7 routines only understand PKCS#7 v 1.5 as specified in RFC 2315.
They cannot currently parse, for example, the new CMS as described in RFC 2630.
.\"
.\" PKCS8
.\"
@ -4460,12 +4460,12 @@ value is used then only
and
.Em BMPStrings
will be used.
This follows the PKIX recommendation in RFC2459.
This follows the PKIX recommendation in RFC 2459.
If the
.Fl utf8only
option is used then only
.Em UTF8Strings
will be used: this is the PKIX recommendation in RFC2459 after 2003.
will be used: this is the PKIX recommendation in RFC 2459 after 2003.
Finally, the
.Ar nombstr
option just uses
@ -7237,7 +7237,7 @@ Only the first four will normally be used.
Use the old format.
This is equivalent to specifying no name options at all.
.It Ar RFC2253
Displays names compatible with RFC2253; equivalent to
Displays names compatible with RFC 2253; equivalent to
.Ar esc_2253 , esc_ctrl ,
.Ar esc_msb , utf8 , dump_nostr , dump_unknown ,
.Ar dump_der , sep_comma_plus , dn_rev and sname .
@ -7258,7 +7258,7 @@ It is equivalent to
and
.Ar align .
.It Ar esc_2253
Escape the "special" characters required by RFC2253 in a field that is
Escape the "special" characters required by RFC 2253 in a field that is
.Cm \& ,+"<>; .
Additionally,
.Cm \&#
@ -7282,7 +7282,7 @@ Without the option, all escaping is done with the
character.
.It Ar utf8
Convert all strings to UTF8 format first.
This is required by RFC2253.
This is required by RFC 2253.
If you are lucky enough to have a UTF8 compatible terminal then the use
of this option (and
.Em not
@ -7336,7 +7336,7 @@ for the AVA separator.
It also indents the fields by four characters.
.It Ar dn_rev
Reverse the fields of the DN.
This is required by RFC2253.
This is required by RFC 2253.
As a side effect, this also reverses the order of multiple AVAs but this is
permissible.
.It Ar nofname , sname , lname , oid

6
usr.sbin/pppoe/pppoe.8
View File

@ -1,4 +1,4 @@
.\" $OpenBSD: pppoe.8,v 1.14 2003/06/04 04:32:55 jason Exp $
.\" $OpenBSD: pppoe.8,v 1.15 2003/08/08 10:13:33 jmc Exp $
.\"
.\" Copyright (c) 2000 Network Security Technologies, Inc.
.\" (http://www.netsec.net)
@ -122,7 +122,7 @@ line tells
.Nm ppp
to use synchronous encoding for the packets sent between it and
.Nm pppoe .
According to RFC2516, protocol compression,
According to RFC 2516, protocol compression,
.Em protocomp ,
is not recommended, so
it is disabled, but not denied.
@ -216,7 +216,7 @@ to adjust the maximum segment size on outgoing SYN packets.
.Xr hostname.if 5 ,
.Xr ppp 8
.Rs
.%T RFC2516 A Method for Transmitting PPP Over Ethernet (PPPoE)
.%T RFC 2516 A Method for Transmitting PPP Over Ethernet (PPPoE)
.%A L. Mamakos, et al.
.Re
.Sh HISTORY

12
usr.sbin/rdate/rdate.8
View File

@ -1,4 +1,4 @@
.\" $OpenBSD: rdate.8,v 1.23 2003/06/12 12:59:52 jmc Exp $
.\" $OpenBSD: rdate.8,v 1.24 2003/08/08 10:13:33 jmc Exp $
.\" $NetBSD: rdate.8,v 1.4 1996/04/08 20:55:17 jtc Exp $
.\"
.\" Copyright (c) 1994 Christos Zoulas
@ -43,22 +43,22 @@
.Nm
displays and sets the local date and time from the
host name or address given as the argument.
The time source may be an RFC868 TCP protocol server,
The time source may be an RFC 868 TCP protocol server,
which is usually implemented as a built-in service of
.Xr inetd 8 ,
or an RFC1361 protocol SNTP/NTP server.
or an RFC 1361 protocol SNTP/NTP server.
By default,
.Nm
uses the RFC868 TCP protocol.
uses the RFC 868 TCP protocol.
.Pp
The options are as follows:
.Bl -tag -width Ds
.It Fl n
Use SNTP (RFC1361) instead of the RFC868 time protocol.
Use SNTP (RFC 1361) instead of the RFC 868 time protocol.
.It Fl c
Correct leap seconds.
Sometimes required when synchronizing to an NTP server.
When synchronizing using the RFC868 protocol, use this option only if the
When synchronizing using the RFC 868 protocol, use this option only if the
server does not correctly account for leap seconds.
You can determine if you need this parameter if you sync against an NTP
server (with this parameter) or (recommended) check with a local radio

6
usr.sbin/route6d/route6d.8
View File

@ -1,4 +1,4 @@
.\" $OpenBSD: route6d.8,v 1.14 2003/02/11 07:26:20 jmc Exp $
.\" $OpenBSD: route6d.8,v 1.15 2003/08/08 10:13:33 jmc Exp $
.\" $KAME: route6d.8,v 1.11 2002/06/02 15:00:30 itojun Exp $
.\"
.\" Copyright (c) 1996 WIDE Project. All rights reserved.
@ -222,14 +222,14 @@ signal
.%A G. Malkin
.%A R. Minnear
.%T RIPng for IPv6
.%R RFC2080
.%R RFC 2080
.%D January 1997
.Re
.\"
.Sh NOTES
.Nm
uses the advanced IPv6 API,
defined in RFC2292,
defined in RFC 2292,
for communicating with peers using link-local addresses.
.Pp
Internally

4
usr.sbin/rtadvd/rtadvd.8
View File

@ -1,4 +1,4 @@
.\" $OpenBSD: rtadvd.8,v 1.19 2003/03/18 11:18:55 jmc Exp $
.\" $OpenBSD: rtadvd.8,v 1.20 2003/08/08 10:13:33 jmc Exp $
.\" $KAME: rtadvd.8,v 1.18 2002/04/28 10:43:02 jinmei Exp $
.\"
.\" Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project.
@ -145,7 +145,7 @@ In this case,
.Nm
will transmit router advertisement with router lifetime 0
to all the interfaces
.Pq in accordance with RFC2461 6.2.5 .
.Pq in accordance with RFC 2461 6.2.5 .
.Sh RETURN VALUES
The
.Nm