>Number:         15895
>Category:       standards
>Synopsis:       gif(4) man page does not mention RFC 2003 compatibility
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    standards-manager
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Mar 13 07:44:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Alan Barrett
>Release:        NetBSD 1.5ZA
>Organization:
Not much
>Environment:
System: NetBSD 1.5ZA
Architecture: i386
Machine: i386
>Description:
It appears from code inspection that the gif interface, when used in
IPv4-over-IPv4 mode, is compatible with RFC 2003.  However, the gif(4)
man page does not mention this.
>How-To-Repeat:
>Fix:

Index: share/man/man4/gif.4
--- gif.4	2002/03/04 14:50:54	1.19
+++ gif.4	2002/03/13 15:36:08
@@ -133,6 +133,19 @@
 .Pp
 Note that the ECN friendly behavior violates RFC2893.
 This should be used in mutual agreement with the peer.
+.Ss Packet format
+Every inner packet is encapsulated in an outer packet.
+The inner packet may be IPv4, IPv6, or ISO CLNP.
+The outer packet may be IPv4 or IPv6, and has all the
+usual IP headers, including a protocol field that identifies the
+type of inner packet.
+.Pp
+When the inner packet is IPv4, the protocol field of the outer packet
+is 4 (IPPROTO_IPV4).
+When the inner packet is IPv6, the protocol field of the outer packet
+is 41 (IPPROTO_IPV6).
+When the inner packet is ISO CNLP, the protocol field of the outer packet
+is 80 (IPPROTO_EON).
 .Ss Security
 Malicious party may try to circumvent security filters by using
 tunnelled packets.
@@ -197,6 +210,13 @@
 .Xr inet6 4 ,
 .Xr ifconfig 8
 .Rs
+.%A	C. Perkins
+.%B	RFC2003
+.%T	IP Encapsulation within IP
+.%D	October 1996
+.%O	ftp://ftp.isi.edu/in-notes/rfc2003.txt
+.Re
+.Rs
 .%A	R. Gilligan
 .%A	E. Nordmark
 .%B	RFC2893
@@ -212,6 +232,10 @@
 .%D	December 1999
 .%O	draft-ietf-ipsec-ecn-02.txt
 .Re
+.\"
+.Sh STANDARDS
+IPv4 over IPv4 encapsulation is compatible with RFC2003.
+IPv6 over IPv4 encapsulation is compatible with RFC2893.
 .\"
 .Sh HISTORY
 The
>Release-Note:
>Audit-Trail:
>Unformatted: