Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!iuvax!cica!tut.cis.ohio-state.edu!ucbvax!VENERA.ISI.EDU!braden
From: braden@VENERA.ISI.EDU
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  Forwarding IP packets with source on net 0?
Message-ID: <8907142043.AA00510@braden.isi.edu>
Date: 14 Jul 89 20:43:59 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 21


Steve,

  The Host Requirements RFC draft (Internet Layer, Section 3.2.1.3)
  says a host MUST NOT send {0,*} except as a source address as part of
  a booting procedure (which is your case, I believe).  More importantly,
  a host receiving a datagram with such a source address MUST ignore the
  datagram.

 The discussion of filtering bogus addresses in RFC-1009 (Section 4.4
 and Appendix A.1) talks only about the destination address; it does
 outlaw forwarding to {0,*} as a destination.   We put no requirements
 on the source address in order to avoid excessive gateway overhead.

 I would certainly agree with you and Vint that architecturally, a
 gateway that forwards such a datagram is in bad odor, but for
 efficiency reasons you may want to enforce this at the end host, not
 the gateway.
 
 Bob Braden