Encapsulation protocol

Garrett.Wollman@uvm.edu Sun, 13 June 1993 00:52 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04406; 12 Jun 93 20:52 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa04402; 12 Jun 93 20:52 EDT
Received: from thumper.bellcore.com by CNRI.Reston.VA.US id aa22555; 12 Jun 93 20:52 EDT
Received: by thumper.bellcore.com (4.1/4.7) id <AA05009> for ietf-archive@nri.reston.va.us; Sat, 12 Jun 93 20:52:36 EDT
Received: from sadye.emba.uvm.edu by thumper.bellcore.com (4.1/4.7) id <AA05005> for /usr/lib/sendmail -oi -fowner-pip X-pip; Sat, 12 Jun 93 20:52:34 EDT
Received: by sadye.emba.uvm.edu id AA06366 (5.65/6.02); Sat, 12 Jun 93 20:52:32 -0400
Date: Sat, 12 Jun 1993 20:52:32 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Garrett.Wollman@uvm.edu
Message-Id: <9306130052.AA06366@sadye.emba.uvm.edu>
To: PIP mailing list <pip@thumper.bellcore.com>
Subject: Encapsulation protocol

What protocol is being used to encapsulate PIP over IPv4?  If no
protocol has been chosen yet, I would strongly suggest use of protocol
4, which is just a direct encapsulation of the entire IPgram inside IP
itself.  The reason is that this is already being used to encapsulate
IP multigrams inside unicast IP; this makes it possible to leverage
existing code.  (Also, I've written a network interface driver which
implements this protocol, for use by both multicast and unicast values
of IP.)

-GAWollman

--
Garrett A. Wollman   | Shashish is simple, it's discreet, it's brief. ... 
wollman@emba.uvm.edu | Shashish is the bonding of hearts in spite of distance.
uvm-gen!wollman      | It is a bond more powerful than absence.  We like people
UVM disagrees.       | who like Shashish.  - Claude McKenzie + Florent Vollant