Re: RIP-2 Addresses Links and MIB problems

Jeffrey C Honig <jch@nr-tech.cit.cornell.edu> Tue, 23 March 1993 14:55 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06518; 23 Mar 93 9:55 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa06514; 23 Mar 93 9:55 EST
Received: from atlas.xylogics.com by CNRI.Reston.VA.US id aa04440; 23 Mar 93 9:55 EST
Received: by atlas.xylogics.com id AA25325 (5.65c/UK-2.1-930202); Tue, 23 Mar 1993 09:58:29 -0500
Received: from MITCHELL.CIT.CORNELL.EDU by atlas.xylogics.com with SMTP id AA24799 (5.65c/UK-2.1-930202); Tue, 23 Mar 1993 09:57:49 -0500
Received: from MITCHELL.CIT.CORNELL.EDU by mitchell.cit.cornell.edu (4.1/1.34/Honig-1.3) id AA21379; Tue, 23 Mar 93 09:52:04 EST
Message-Id: <9303231452.AA21379@mitchell.cit.cornell.edu>
To: Fred Baker <fbaker@acc.com>
Cc: ietf-rip@xylogics.com
Subject: Re: RIP-2 Addresses Links and MIB problems
In-Reply-To: Message from fbaker@acc.com (Fred Baker) on Tue, 23 Mar 1993 05:58:33 -0800.<9303231358.AA19562@saffron.acc.com>
Organization: Information Technologies/Network Resources; Cornell University, Ithaca, NY
X-Mailier: MH-E [version 3.7+] MH [version 6.8]
Date: Tue, 23 Mar 1993 09:51:55 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Jeffrey C Honig <jch@nr-tech.cit.cornell.edu>

> The address of the routing neighbor is not sufficient to identify
> an unnumbered link, for two reasons. First, it is possible to have
> two links to the same neighbor; this would not distinbguish them.

How is this problem different than the one solved by OSPF fir the
ospfAddressLessIf variable indicating the interface index?  For
unnumbered links (in this case links where the local address is not
unique) you set this variable to the MIB Index of the interface.

> Second, it is possible to have an interface with no active neighbor
> at all. In that case, it is not possible to configure the interface.
> It is not possible to turn it on since, wityhout an active neighbor,
> it has no name.

Why not?  Just multicast or all-ones broadcast RIP packets to the
other side of the interface.  Maybe you can clarify, I am not dealing
with true unnumbered interfaces so I may not fully understand the
situation.

> For this reason, if unnumberedd interfaces are in view, I would suggest
> simply numbering them.

You mean assign IP addresses to them?  In my case they have IP
addresses, but they are not unique, they may be the same for multiple
P2P interfaces and up to one non-P2P (i.e. Ethernet) interfaces.
Internally I refer to them my their destination address, but those
destination addresses are not really my interface addresses so I
shouldn't report them in the MIB.  If I report the local addresses the
MIB falls apart.

Thanks.

Jeff