A new Request for Comments is now available in online RFC libraries.


        RFC 2004:

        Title:      Minimal Encapsulation within IP
        Author:     C. Perkins
        Date:       October 1996
        Mailbox:    perk@watson.ibm.com
        Pages:      6
        Characters: 12,202
        Updates/Obsoletes:  None

        URL:        ftp://ds.internic.net/rfc/rfc2004.txt


This document specifies a method by which an IP datagram may be
encapsulated (carried as payload) within an IP datagram, with less
overhead than "conventional" IP encapsulation that adds a second IP
header to each encapsulated datagram.  Encapsulation is suggested as a
means to alter the normal IP routing for datagrams, by delivering them
to an intermediate destination that would otherwise not be selected by
the (network part of the) IP Destination Address field in the original
IP header.  Encapsulation may be serve a variety of purposes, such as
delivery of a datagram to a mobile node using Mobile IP. This RFC is a
product of the IP Routing for Wireless/Mobile Hosts Working Group of
the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Mary Kennedy
USC/Information Sciences Institute