RFC 3793 (rfc3793) - Page 3 of 6

Survey of IPv4 Addresses in Currently Deployed IETF Sub-IP Area Standards Track and Experimental Documents

RFC 3793         IPv4 Addresses in the IETF Sub-IP Area         May 2004


5.  Proposed Standards

   Proposed Standards are introductory level documents.  There are no
   requirements for even a single implementation.  In many cases
   Proposed are never implemented or advanced in the IETF standards
   process.  They therefore are often just proposed ideas that are
   presented to the Internet community.  Sometimes flaws are exposed or
   they are one of many competing solutions to problems.  In these later
   cases, no discussion is presented as it would not serve the purpose
   of this discussion.

   5.01.  RFC 3031 Multiprotocol Label Switching Architecture (MPLS)

      There are no IPv4 dependencies in this specification.

   5.02.  RFC 3032 MPLS Label Stack Encoding

      This specification is both IPv4 and IPv6 aware and needs no
      changes.

   5.03.  RFC 3034 Use of Label Switching on Frame Relay Networks
         Specification

      There are no IPv4 dependencies in this specification.

   5.04.  RFC 3035 MPLS using LDP and ATM VC Switching

      There are no IPv4 dependencies in this specification.

   5.05.  RFC 3036 LDP Specification

      This specification is both IPv4 and IPv6 aware and needs no
      changes.

   5.06.  RFC 3038 VCID Notification over ATM link for LDP

      There are no IPv4 dependencies in this specification.

6.  Experimental RFCs

   Experimental RFCs typically define protocols that do not have
   widescale implementation or usage on the Internet.  They are often
   propriety in nature or used in limited arenas.  They are documented
   to the Internet community in order to allow potential
   interoperability or some other potential useful scenario.  In a few
   cases they are presented as alternatives to the mainstream solution
   to an acknowledged problem.




Nesser II & Bergstrom        Informational