adding NAT, encaps, etc. to RREQ
Craig Partridge <craig@bbn.com> Thu, 17 March 1994 18:58 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08648; 17 Mar 94 13:58 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa08644; 17 Mar 94 13:58 EST
Received: from moe.rice.edu by CNRI.Reston.VA.US id aa18044; 17 Mar 94 13:58 EST
Received: from FRED.BBN.COM by moe.rice.edu (AA25526); Thu, 17 Mar 94 12:19:54 CST
Message-Id: <9403171819.AA25526@moe.rice.edu>
To: rreq@rice.edu
Subject: adding NAT, encaps, etc. to RREQ
Date: Thu, 17 Mar 1994 13:12:32 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Craig Partridge <craig@bbn.com>
Hi folks:
Just an idea from Host Requirements experience. In several cases, we
concluded that some topic needed attention, and a group of people would go
off to write an RFC on that topic. One could then (if appropriate) mention
that RFC in the requirements RFC. It would seem that NAT and encaps would
benefit from their own RFCs.
Craig
- adding NAT, encaps, etc. to RREQ Craig Partridge