Local delivery decision for IP broadcasts
Kanaiya Vasani <vasani@anubis.network.com> Thu, 19 January 1995 23:54 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa12432; 19 Jan 95 18:54 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa12428; 19 Jan 95 18:54 EST
Received: from venera.isi.edu by CNRI.Reston.VA.US id aa18394; 19 Jan 95 18:54 EST
Received: from nsco.network.com by venera.isi.edu (5.65c/5.61+local-20) id <AA18010>; Thu, 19 Jan 1995 15:34:02 -0800
Received: from anubis.network.com by nsco.network.com (4.1/1.34) id AA16890; Thu, 19 Jan 95 17:49:29 CST
Received: from cheech.network.com by anubis.network.com (4.1/SMI-4.1) id AA27672; Thu, 19 Jan 95 17:33:31 CST
Date: Thu, 19 Jan 1995 17:33:31 -0600
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Kanaiya Vasani <vasani@anubis.network.com>
Message-Id: <9501192333.AA27672@anubis.network.com>
To: rreq@isi.edu
Subject: Local delivery decision for IP broadcasts
Folks, The draft for the Router Req document - Revision 2.02 dated 1/3/95 states the following: The packet is passed to the forwarder and delivered locally if: If the packet's destination address is an IP broadcast address (other than a limited broadcast address) that addresses at least one of the logical interfaces associated with the physical interface on which the packet arrived. What if I have a broadcast packet that addresses a logical interface associated with some other physical interface? Could someone explain the rationale behind restricting it the way it is? Thanks, -Kanaiya
- Local delivery decision for IP broadcasts Kanaiya Vasani