message to 'down' intf

Benny Rodrig <> Mon, 27 March 1995 14:04 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa02245; 27 Mar 95 9:04 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa02241; 27 Mar 95 9:04 EST
Received: from by CNRI.Reston.VA.US id aa05132; 27 Mar 95 9:04 EST
Received: from by (5.65c/5.61+local-21) id <AA04869>; Mon, 27 Mar 1995 05:36:55 -0800
Received: from ([]) by (4.1/SMI-4.1) id AA16756; Mon, 27 Mar 95 15:35:34 IST
Received: by with Microsoft Mail id <>; Mon, 27 Mar 95 15:36:26 PST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Benny Rodrig <>
To: 'Fred Baker' <>
Cc: 'rreq' <>
Subject: message to 'down' intf
Date: Mon, 27 Mar 95 15:36:00 PST
Message-Id: <>
Encoding: 23 TEXT
X-Mailer: Microsoft Mail V3.0

In draft-ietf-rreq-cidr-02.txt, Revision 2.05 from 3/17/95
Section 5.2.3, Local Delivery Decision, reads:
              + The packet is delivered locally and not considered for
                 forwarding in the following cases:
                  - The packet's destination address exactly matches
                    one of the router's IP addresses,

Shouldn't this be unless the interface corresponding to this IP address
is 'down'?
If the router is configured with an IP address of net X, but is currently
disconnected from network X, should it identify and deliver locally
(e.g. answer ping) messages destined to that IP address?

I also have an editorial comment:
Section mentions two types of broadcast that are indistinguishable
under CIDR. This section is unclear, as the names of these two types
were both changed to network-prefix-directed-broadcasts, making them
truly indistinguishable...

Benny Rodrig