RFC 3794 (rfc3794) - Page 2 of 31
Survey of IPv4 Addresses in Currently Deployed IETF Transport Area Standards Track and Experimental Documents
Alternative Format: Original Text Document
RFC 3794 IPv4 Addresses in the IETF Transport Area June 2004
10.0. Normative Reference. . . . . . . . . . . . . . . . . . . . . 30
11.0. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 30
12.0. Full Copyright Statement . . . . . . . . . . . . . . . . . . 31
1.0. Introduction
This document is part of a document set aiming to document all usage
of IPv4 addresses in IETF standards. In an effort to have the
information in a manageable form, it has been broken into 7 documents
conforming to the current IETF areas (Application, Internet,
Operations & Management, Routing, Security, Sub-IP and Transport).
For a full introduction, please see the introduction [1].
2.0. Document Organization
The rest of the document sections are described below.
Sections 3, 4, 5, and 6 each describe the raw analysis of Full,
Draft, and Proposed Standards, and Experimental RFCs. Each RFC is
discussed in its turn starting with RFC 1 and ending with (around)
RFC 3100. The comments for each RFC are "raw" in nature. That is,
each RFC is discussed in a vacuum and problems or issues discussed do
not "look ahead" to see if the problems have already been fixed.
Section 7 is an analysis of the data presented in Sections 3, 4, 5,
and 6. It is here that all of the results are considered as a whole
and the problems that have been resolved in later RFCs are
correlated.
3.0. Full Standards
Full Internet Standards (most commonly simply referred to as
"Standards") are fully mature protocol specification that are widely
implemented and used throughout the Internet.
3.1. RFC 768 User Datagram Protocol
Although UDP is a transport protocol there is one reference to the
UDP/IP interface that states; "The UDP module must be able to
determine the source and destination internet addresses and the
protocol field from the internet header." This does not force a
rewrite of the protocol but will clearly cause changes in
implementations.
Nesser II & Bergstrom Informational