RE: [rip] Specific request processing

gmalkin@toplayer.com Thu, 18 March 2004 17:33 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26459 for <rip-archive@ietf.org>; Thu, 18 Mar 2004 12:33:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B41Oc-0005v1-00 for rip-archive@ietf.org; Thu, 18 Mar 2004 12:33:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B41Nm-0005tS-00 for rip-archive@ietf.org; Thu, 18 Mar 2004 12:32:39 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B41N9-0005rC-00; Thu, 18 Mar 2004 12:31:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B41NA-00084t-Tt; Thu, 18 Mar 2004 12:32:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B41Mj-00082t-Kn for rip@optimus.ietf.org; Thu, 18 Mar 2004 12:31:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26414 for <rip@ietf.org>; Thu, 18 Mar 2004 12:31:29 -0500 (EST)
From: gmalkin@toplayer.com
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B41Mi-0005ph-00 for rip@ietf.org; Thu, 18 Mar 2004 12:31:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B41Lv-0005mz-00 for rip@ietf.org; Thu, 18 Mar 2004 12:30:44 -0500
Received: from mail.toplayer.com ([66.100.252.67] helo=tlnmail1.toplayer.com) by ietf-mx with esmtp (Exim 4.12) id 1B41LF-0005gZ-00 for rip@ietf.org; Thu, 18 Mar 2004 12:30:01 -0500
Received: by tlnmail1.toplayer.com with Internet Mail Service (5.5.2657.72) id <G5XTTRPN>; Thu, 18 Mar 2004 12:29:26 -0500
Message-ID: <F6242D340921D5118D1E00508BB9837A04BBB6BA@tlnmail1.toplayer.com>
To: kishoren@huawei.com, gmalkin@toplayer.com, rip@ietf.org
Subject: RE: [rip] Specific request processing
Date: Thu, 18 Mar 2004 12:29:22 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C40D0E.8D6E0F00"
Sender: rip-admin@ietf.org
Errors-To: rip-admin@ietf.org
X-BeenThere: rip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rip>, <mailto:rip-request@ietf.org?subject=unsubscribe>
List-Id: Routing Information Protocol Working Group <rip.ietf.org>
List-Post: <mailto:rip@ietf.org>
List-Help: <mailto:rip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rip>, <mailto:rip-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.8 required=5.0 tests=AWL,HTML_40_50, HTML_FONTCOLOR_BLUE,HTML_MESSAGE,NO_REAL_NAME autolearn=no version=2.60

That is true, but there isn't anything that can be done about it.
Unfortunately,
OSPF allows larger metrics than RIP and there we're stuck with it. In a case
like that, the only thing you can do is respond with "no such route." Any
other
response would be open to too much interpretation.
 
Gary
 
-----Original Message-----
From: Nanda kishore [mailto:kishoren@huawei.com]
Sent: Thursday, March 18, 2004 11:04 AM
To: gmalkin@toplayer.com; rip@ietf.org
Subject: Re: [rip] Specific request processing


But the metric will be inconsistent.
For ospf / BGP metric may be more than 16 
How to respond send the metric in BGP say 123456
Wont' it be invalid in a rip response. ?.
 
Nanda kishore
-----------------------
Senior Software Engineer
Huawei Technology India Pvt. Ltd.
Leela Galleria, 
Bangalore, India.
Ph. 25265596 (R)
      25217152 Ext 662 (O)
 
 

----- Original Message ----- 
From: gmalkin@toplayer.com <mailto:gmalkin@toplayer.com>  
To: kishoren@huawei.com <mailto:kishoren@huawei.com>  ; rip@ietf.org
<mailto:rip@ietf.org>  ; ripng@ietf.org <mailto:ripng@ietf.org>  
Sent: Thursday, March 18, 2004 8:58 PM
Subject: RE: [rip] Specific request processing

You should respond with whichever route the router will use for that
destination,
whether or not it is a RIP route. This is true for all queries.
Gary Malkin             Cheap, fast, good... 
508-870-1300 x254                Pick two! 

-----Original Message-----
From: Nanda kishore [mailto:kishoren@huawei.com]
Sent: Thursday, March 18, 2004 5:06 AM
To: rip@ietf.org <mailto:rip@ietf.org> ; ripng@ietf.org
<mailto:ripng@ietf.org> 
Subject: [rip] Specific request processing


Hi,
 
    In RIP, RIPng If we get a specific request for a particualr desination,
RFC's say
that we should respond without doing split-horizon processing. Does that
mean that
we should respond with only RIP route. 
 
Say there is a BGP/OSPF route for desination 210.1.1.0/24 and we got a
specific request
for that destination
 
    Case 1: There is a RIP route with cost 4 which is inactive
(Administrative distance)
    Case 2: There is no RIP route to the destination (BGP/OSPF's route is
there with cost XYZ)
 
Which metric should we respond with. 
 
Regards
Nanda kishore
-----------------------
Senior Software Engineer
Huawei Technology India Pvt. Ltd.
Leela Galleria, 
Bangalore, India.
Ph. 25265596 (R)
      25217152 Ext 662 (O)