From owner-ietf-rip@BayNetworks.COM Wed Oct 29 11:35:28 1997 Delivery-Date: Wed, 29 Oct 1997 11:35:28 -0500 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from ns.cnri.reston.va.us (cnri [132.151.1.1]) by ietf.org (8.8.7/8.8.7a) with ESMTP id LAA19777 for ; Wed, 29 Oct 1997 11:35:27 -0500 (EST) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by ns.cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id LAA10026 for ; Wed, 29 Oct 1997 11:38:30 -0500 (EST) Received: from mailhost.BayNetworks.COM ([134.177.1.107] (may be forged)) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id IAA06513; Wed, 29 Oct 1997 08:21:32 -0800 (PST) Received: from majordomo.BayNetworks.COM (majordomo.BayNetworks.COM [192.32.253.10]) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id IAA21262; Wed, 29 Oct 1997 08:33:58 -0800 (PST) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id LAA14341; Wed, 29 Oct 1997 11:30:43 -0500 (EST) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([132.245.135.115] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id LAA14337; Wed, 29 Oct 1997 11:30:38 -0500 (EST) for Received: from lobster1.corpeast.Baynetworks.com (ns2.corpeast.baynetworks.com [192.32.72.17]) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with SMTP id LAA01309 for ; Wed, 29 Oct 1997 11:28:15 -0500 (EST) Received: from bl-mail1.corpeast.BayNetworks.com (bl-mail1-nf0) by lobster1.corpeast.Baynetworks.com (4.1/BNET-97/04/29-S) id AA29146; Wed, 29 Oct 97 11:28:13 EST for ietf-rip@majordomo.BayNetworks.COM Received: from atlas.xylogics.com ([132.245.33.7]) by bl-mail1.corpeast.BayNetworks.com (post.office MTA v2.0 0529 ID# 0-13458) with ESMTP id AAA8087 for ; Wed, 29 Oct 1997 11:28:06 -0500 Received: from bighorn.xylogics.com (bighorn.xylogics.com [132.245.32.188]) by atlas.xylogics.com (8.7.3/8.7.3) with SMTP id LAA02094 for ; Wed, 29 Oct 1997 11:25:54 -0500 (EST) Received: by bighorn.xylogics.com id AA02872 (5.x/UK-doug-sol2-951219); Wed, 29 Oct 1997 11:25:52 -0500 From: Gary Scott Malkin Date: Wed, 29 Oct 1997 11:25:52 -0500 Message-Id: <2872.9710291625@bighorn.xylogics.com> To: ietf-rip@xylogics.com Subject: re-homed list Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk Sorry for the test, but the list has just been re-homed. The majordomo server is now working. You can leave the list by sending email to: majordomo@baynetworks.com -or- ietf-rip-request@baynetworks.com In the body of the message (the subject is ignored): unsubscribe ietf-rip -- Gary Malkin Cheap, Fast, Good (978) 916-4237 Pick two! From owner-ietf-rip@BayNetworks.COM Mon Nov 3 13:29:33 1997 Delivery-Date: Mon, 03 Nov 1997 13:29:33 -0500 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from ns.cnri.reston.va.us (cnri [132.151.1.1]) by ietf.org (8.8.7/8.8.7a) with ESMTP id NAA18120 for ; Mon, 3 Nov 1997 13:29:32 -0500 (EST) Received: from smtp-gw.BayNetworks.COM (ns5.baynetworks.com [194.133.90.101]) by ns.cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id NAA03746 for ; Mon, 3 Nov 1997 13:32:15 -0500 (EST) Received: from mailhost.BayNetworks.COM ([132.245.135.84] (may be forged)) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id TAA19272; Mon, 3 Nov 1997 19:18:50 +0100 (MET) Received: from majordomo.BayNetworks.COM ([192.32.253.10] (may be forged)) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id NAA16239; Mon, 3 Nov 1997 13:22:20 -0500 (EST) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id NAA23043; Mon, 3 Nov 1997 13:20:37 -0500 (EST) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([132.245.135.84] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id NAA23039; Mon, 3 Nov 1997 13:20:32 -0500 (EST) for Received: from majordomo.BayNetworks.COM ([192.32.253.10] (may be forged)) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id NAA16135 for ; Mon, 3 Nov 1997 13:17:58 -0500 (EST) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id NAA23035; Mon, 3 Nov 1997 13:19:59 -0500 (EST) for Received: from europa.csg-server (europa.compunnel.com [206.20.61.1]) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id KAA25578 for ; Mon, 3 Nov 1997 10:04:21 -0800 (PST) Received: from Nairobi ([208.204.137.66]) by europa.csg-server (post.office MTA v2.0 0813 ID# 0-17912) with SMTP id AAA441; Mon, 3 Nov 1997 13:21:18 -0500 Message-ID: <345E14A3.10CD@ficon-tech.com> Date: Mon, 03 Nov 1997 13:14:59 -0500 From: "Pratap Reddy P." Organization: Ficon Technology X-Mailer: Mozilla 3.0 (X11; I; SunOS 5.5 i86pc) MIME-Version: 1.0 To: ietf-rip@BayNetworks.COM CC: gmalkin@xylogics.com Subject: nexthop Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk Hi, According to rfc (1723), nexthop should be on the same logical subnet on which packet came. If somebody sends a route with with nexthop which is not *directly reachable*, can we drop that route?? rfc also says treat that nexthop as 0.0.0.0, but doesn't it look reasonable to invalidate that route?? If nexthop is not on the same logical subnet, but it's directly reachable to me, should I accept that route or not?? (I don't know whether this is directly reachable for the sender also or not. I assume it is for him too). If I accept this, should I take nexthop as 0.0.0.0 (same as sender)?? Thanks in advance, regards Pratap -- Pratap Reddy P. Phone: (732) 283-2770 Ext. 324 Ficon Technology Fax: (732) 283-2848 1000 Route 9 North mailto:preddy@ficon-tech.com Woodbridge, NJ 07095 http://www.ficon-tech.com From owner-ietf-rip@BayNetworks.COM Thu Nov 6 18:01:08 1997 Delivery-Date: Thu, 06 Nov 1997 18:01:08 -0500 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from ns.cnri.reston.va.us (cnri [132.151.1.1]) by ietf.org (8.8.7/8.8.7a) with ESMTP id SAA23327 for ; Thu, 6 Nov 1997 18:01:07 -0500 (EST) Received: from smtp-gw.BayNetworks.COM (ns4.BayNetworks.COM [192.32.253.7]) by ns.cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id SAA17182 for ; Thu, 6 Nov 1997 18:04:08 -0500 (EST) Received: from mailhost.BayNetworks.COM ([132.245.135.84] (may be forged)) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id SAA16160; Thu, 6 Nov 1997 18:09:33 -0500 (EST) Received: from majordomo.BayNetworks.COM ([192.32.253.10] (may be forged)) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id RAA27698; Thu, 6 Nov 1997 17:59:08 -0500 (EST) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id RAA28720; Thu, 6 Nov 1997 17:56:55 -0500 (EST) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([132.245.135.84] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id RAA28716; Thu, 6 Nov 1997 17:56:48 -0500 (EST) for Received: from lobster1.corpeast.Baynetworks.com (ns2.corpeast.baynetworks.com [192.32.72.17]) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with SMTP id RAA27547 for ; Thu, 6 Nov 1997 17:54:12 -0500 (EST) Received: from bl-mail1.corpeast.BayNetworks.com (bl-mail1-nf0) by lobster1.corpeast.Baynetworks.com (4.1/BNET-97/04/29-S) id AA12285; Thu, 6 Nov 97 17:54:12 EST for ietf-rip@majordomo.BayNetworks.COM Received: from atlas.xylogics.com ([132.245.33.7]) by bl-mail1.corpeast.BayNetworks.com (post.office MTA v2.0 0529 ID# 0-13458) with ESMTP id AAA2064 for ; Thu, 6 Nov 1997 17:54:06 -0500 Received: from bighorn.xylogics.com (bighorn.xylogics.com [132.245.32.188]) by atlas.xylogics.com (8.7.3/8.7.3) with SMTP id RAA20557; Thu, 6 Nov 1997 17:51:42 -0500 (EST) Received: by bighorn.xylogics.com id AA08941 (5.x/UK-doug-sol2-951219); Thu, 6 Nov 1997 17:51:39 -0500 From: Gary Scott Malkin Date: Thu, 6 Nov 1997 17:51:39 -0500 Message-Id: <8941.9711062251@bighorn.xylogics.com> To: preddy@ficon-tech.com Cc: ietf-rip@BayNetworks.COM In-Reply-To: <345E14A3.10CD@ficon-tech.com> (preddy@ficon-tech.com) Subject: Re: nexthop Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk > If somebody sends a route with with nexthop which is not *directly > reachable*, can we drop that route?? > rfc also says treat that nexthop as 0.0.0.0, but doesn't it look > reasonable to invalidate that route?? You should not drop the route. You should enter it into your table as though the nexthop were left unspecified; that is, use the originator of the route as the next hop (standard RIP). > If nexthop is not on the same logical subnet, but it's directly > reachable to me, should I accept that route or not?? (I don't know > whether this is directly reachable for the sender also or not. I assume > it is for him too). > If I accept this, should I take nexthop as 0.0.0.0 (same as sender)?? The applicability document mentions an additional use for the nexthop field. If the next hop is for another interface, you could chose to use it. This ability should be controled by a configuration option. -- Gary Malkin Cheap, Fast, Good (978) 916-4237 Pick two! From owner-ietf-rip@BayNetworks.COM Wed Nov 26 18:35:09 1997 Delivery-Date: Wed, 26 Nov 1997 18:35:09 -0500 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from ns.cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id SAA24465 for ; Wed, 26 Nov 1997 18:35:08 -0500 (EST) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by ns.cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id SAA13024 for ; Wed, 26 Nov 1997 18:38:05 -0500 (EST) Received: from mailhost.BayNetworks.COM ([134.177.1.107] (may be forged)) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id PAA25918; Wed, 26 Nov 1997 15:34:22 -0800 (PST) Received: from majordomo.BayNetworks.COM (majordomo.BayNetworks.COM [192.32.253.10]) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id PAA18117; Wed, 26 Nov 1997 15:34:01 -0800 (PST) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id SAA03013; Wed, 26 Nov 1997 18:34:17 -0500 (EST) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([132.245.135.115] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id SAA03009; Wed, 26 Nov 1997 18:34:12 -0500 (EST) for Received: from lobster1.corpeast.Baynetworks.com (ns2.corpeast.baynetworks.com [192.32.72.17]) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with SMTP id SAA24034 for ; Wed, 26 Nov 1997 18:31:00 -0500 (EST) Received: from bl-mail1.corpeast.BayNetworks.com (bl-mail1-nf0) by lobster1.corpeast.Baynetworks.com (4.1/BNET-97/04/29-S) id AA22253; Wed, 26 Nov 97 18:31:07 EST for ietf-rip@majordomo.BayNetworks.COM Received: from atlas.xylogics.com ([132.245.33.7]) by bl-mail1.corpeast.BayNetworks.com (post.office MTA v2.0 0529 ID# 0-13458) with ESMTP id AAA1400 for ; Wed, 26 Nov 1997 18:30:56 -0500 Received: from bighorn.xylogics.com (bighorn.xylogics.com [132.245.32.188]) by atlas.xylogics.com (8.7.3/8.7.3) with SMTP id SAA29497 for ; Wed, 26 Nov 1997 18:28:22 -0500 (EST) Received: by bighorn.xylogics.com id AA06722 (5.x/UK-doug-sol2-951219); Wed, 26 Nov 1997 18:28:21 -0500 From: Gary Scott Malkin Date: Wed, 26 Nov 1997 18:28:21 -0500 Message-Id: <6722.9711262328@bighorn.xylogics.com> To: ietf-rip@xylogics.com Subject: Agenda requests Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk Are there any requests for time on the RIP WG agenda for D.C.? Some of the RFCs are up for advancement and there's some new stuff out there. -- Gary Malkin Cheap, Fast, Good (978) 916-4237 Pick two! From owner-ietf-rip@BayNetworks.COM Fri Dec 5 05:56:52 1997 Delivery-Date: Fri, 05 Dec 1997 05:56:53 -0500 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from ns.cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id FAA10871 for ; Fri, 5 Dec 1997 05:56:52 -0500 (EST) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by ns.cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id FAA20971 for ; Fri, 5 Dec 1997 05:59:46 -0500 (EST) Received: from mailhost.BayNetworks.COM (screen2r.BayNetworks.COM [134.177.3.1]) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id CAA21873; Fri, 5 Dec 1997 02:56:06 -0800 (PST) Received: from majordomo.BayNetworks.COM ([192.32.253.10] (may be forged)) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id FAA16305; Fri, 5 Dec 1997 05:55:33 -0500 (EST) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id FAA16880; Fri, 5 Dec 1997 05:56:34 -0500 (EST) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([134.177.1.109] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id FAA16876; Fri, 5 Dec 1997 05:56:28 -0500 (EST) for Received: from majordomo.BayNetworks.COM ([192.32.253.10] (may be forged)) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id CAA06087 for ; Fri, 5 Dec 1997 02:53:04 -0800 (PST) Received: from smtp-gw.BayNetworks.COM (ns3.BayNetworks.COM [192.32.253.3]) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id FAA16872; Fri, 5 Dec 1997 05:55:55 -0500 (EST) for Received: from lynx.europe.shiva.com (lynx.europe.shiva.com [134.191.64.5]) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id FAA05580 for ; Fri, 5 Dec 1997 05:52:36 -0500 (EST) Received: from edhub.europe.shiva.com (edhub.europe.shiva.com [134.191.64.228]) by lynx.europe.shiva.com (8.8.8/8.8.5) with SMTP id KAA16336 for ; Fri, 5 Dec 1997 10:52:02 GMT Received: by edhub.europe.shiva.com(Lotus SMTP MTA v1.1 (385.6 5-6-1997)) id 80256564.003B7752 ; Fri, 5 Dec 1997 10:49:31 +0000 X-Lotus-FromDomain: Shiva@SHIVA From: "Edhub" To: Ietf-Rip@BayNetworks.COM Message-ID: <80256563.0072F273.00@edhub.europe.shiva.com> Date: Thu, 4 Dec 1997 20:55:12 +0000 Subject: Agenda for IETF Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk Hi Don't see an agenda on the IETF web site - does this mean there isn't one? :-) Cheers Neil From owner-ietf-rip@BayNetworks.COM Mon Dec 8 17:02:52 1997 Delivery-Date: Mon, 08 Dec 1997 17:02:53 -0500 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from ns.cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id RAA16235 for ; Mon, 8 Dec 1997 17:02:52 -0500 (EST) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by ns.cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id RAA04858 for ; Mon, 8 Dec 1997 17:05:46 -0500 (EST) Received: from mailhost.BayNetworks.COM ([134.177.1.107] (may be forged)) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id OAA00260; Mon, 8 Dec 1997 14:01:48 -0800 (PST) Received: from majordomo.BayNetworks.COM (majordomo.BayNetworks.COM [192.32.253.10]) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id OAA05759; Mon, 8 Dec 1997 14:01:07 -0800 (PST) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id RAA22854; Mon, 8 Dec 1997 17:01:46 -0500 (EST) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([141.251.211.49] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id RAA22850; Mon, 8 Dec 1997 17:01:39 -0500 (EST) for Received: from lobster1.corpeast.Baynetworks.com (lobster1.corpeast.baynetworks.com [192.32.72.17]) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with SMTP id WAA13912 for ; Mon, 8 Dec 1997 22:58:16 +0100 (MET) Received: from bl-mail1.corpeast.BayNetworks.com (bl-mail1-nf0) by lobster1.corpeast.Baynetworks.com (4.1/BNET-97/04/29-S) id AA15618; Mon, 8 Dec 97 16:58:08 EST for ietf-rip@majordomo.BayNetworks.COM Received: from atlas.xylogics.com ([132.245.33.7]) by bl-mail1.corpeast.BayNetworks.com (post.office MTA v2.0 0529 ID# 0-13458) with ESMTP id AAA7799 for ; Mon, 8 Dec 1997 16:57:49 -0500 Received: from bighorn.xylogics.com (bighorn.xylogics.com [132.245.32.188]) by atlas.xylogics.com (8.7.3/8.7.3) with SMTP id QAA03678; Mon, 8 Dec 1997 16:54:54 -0500 (EST) Received: by bighorn.xylogics.com id AA09803 (5.x/UK-doug-sol2-951219); Mon, 8 Dec 1997 16:54:52 -0500 From: Gary Scott Malkin Date: Mon, 8 Dec 1997 16:54:52 -0500 Message-Id: <9803.9712082154@bighorn.xylogics.com> To: ietf-rip@xylogics.com Cc: agenda@ns.ietf.org, jhalpern@newbridge.com Subject: Session Canceled Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk Something which should have happened didn't and people who should be here aren't, so I'm canceling the RIP session in D.C. Stay tuned for more news soon! -- Gary Malkin Cheap, Fast, Good (978) 916-4237 Pick two! From owner-ietf-rip@BayNetworks.COM Sun Dec 21 02:40:01 1997 Delivery-Date: Sun, 21 Dec 1997 02:40:01 -0500 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from ns.cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id CAA23607 for ; Sun, 21 Dec 1997 02:40:00 -0500 (EST) Received: from smtp-gw.BayNetworks.COM (ns4.BayNetworks.COM [192.32.253.7]) by ns.cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id CAA22416 for ; Sun, 21 Dec 1997 02:42:51 -0500 (EST) Received: from mailhost.BayNetworks.COM ([132.245.135.115] (may be forged)) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id CAA17141; Sun, 21 Dec 1997 02:29:22 -0500 (EST) Received: from majordomo.BayNetworks.COM ([192.32.253.10] (may be forged)) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id CAA09037; Sun, 21 Dec 1997 02:28:16 -0500 (EST) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id CAA15461; Sun, 21 Dec 1997 02:27:49 -0500 (EST) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([132.245.135.84] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id CAA15457; Sun, 21 Dec 1997 02:27:43 -0500 (EST) for Received: from majordomo.BayNetworks.COM ([192.32.253.10] (may be forged)) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id CAA22679 for ; Sun, 21 Dec 1997 02:24:00 -0500 (EST) Received: from smtp-gw.BayNetworks.COM (ns3.BayNetworks.COM [192.32.253.3]) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id CAA15453; Sun, 21 Dec 1997 02:27:10 -0500 (EST) for Received: from messenger.rnd.co.il ([207.232.32.59] (may be forged)) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id CAA01841 for ; Sun, 21 Dec 1997 02:23:55 -0500 (EST) Received: by MESSENGER with Internet Mail Service (5.0.1458.49) id ; Sun, 21 Dec 1997 09:25:17 +0200 Message-ID: <0124851EDBF3D011AAA300008370C8670EBA30@MESSENGER> From: Hamutal Schur-Galinka To: "'ietf-rip@baynetworks.com'" Subject: rip tables in unnumbered ip interfaces Date: Sun, 21 Dec 1997 09:25:14 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: multipart/alternative; boundary="---- =_NextPart_001_01BD0DF2.59D59C20" Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------ =_NextPart_001_01BD0DF2.59D59C20 Content-Type: text/plain Hello, According to RFC 1812, when using unnumbered IP interface in routers (on point-to-point interfaces), the IP address that such an interface gets is one of the IP addresses of one of the Ethernet interfaces of that router. What should be done with MIB tables that have the IP address as a key, such as: rip2IfConfTable, rip2IfStatTable ? Thank you, Hamutal Schur. Hamutals@rnd.co.il ------ =_NextPart_001_01BD0DF2.59D59C20 Content-Type: text/html

Hello,

According to RFC 1812, when using unnumbered IP interface in routers (on
point-to-point interfaces), the IP address that such an interface gets
is one of the IP addresses of one of the Ethernet interfaces of that
router.
What should be done with MIB tables that have the IP address as a key,
such as: rip2IfConfTable, rip2IfStatTable ?

Thank you,
Hamutal Schur.
Hamutals@rnd.co.il

------ =_NextPart_001_01BD0DF2.59D59C20-- From owner-ietf-rip@BayNetworks.COM Sun Dec 21 19:25:49 1997 Delivery-Date: Sun, 21 Dec 1997 19:25:50 -0500 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from ns.cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id TAA04882 for ; Sun, 21 Dec 1997 19:25:49 -0500 (EST) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by ns.cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id TAA00977 for ; Sun, 21 Dec 1997 19:28:39 -0500 (EST) Received: from mailhost.BayNetworks.COM (screen2r.BayNetworks.COM [134.177.3.1]) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id QAA23207; Sun, 21 Dec 1997 16:15:27 -0800 (PST) Received: from majordomo.BayNetworks.COM ([192.32.253.10] (may be forged)) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id QAA04777; Sun, 21 Dec 1997 16:15:21 -0800 (PST) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id TAA16627; Sun, 21 Dec 1997 19:14:55 -0500 (EST) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([134.177.1.107] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id TAA16623; Sun, 21 Dec 1997 19:14:49 -0500 (EST) for Received: from majordomo.BayNetworks.COM (majordomo.BayNetworks.COM [192.32.253.10]) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id QAA17222 for ; Sun, 21 Dec 1997 16:11:03 -0800 (PST) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id TAA16619; Sun, 21 Dec 1997 19:14:16 -0500 (EST) for Received: from messenger.rnd.co.il ([207.232.32.59] (may be forged)) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id QAA23118 for ; Sun, 21 Dec 1997 16:10:31 -0800 (PST) Received: by MESSENGER with Internet Mail Service (5.0.1458.49) id ; Sun, 21 Dec 1997 16:24:54 +0200 Message-ID: <0124851EDBF3D011AAA300008370C8670AAA99@MESSENGER> From: Ohad Dekel To: "'ietf-rip@baynetworks.com'" Subject: rip tables with unnumbered ip interfaces Date: Sun, 21 Dec 1997 16:24:52 +0200 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: multipart/alternative; boundary="---- =_NextPart_001_01BD0E2C.F8BAE630" Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------ =_NextPart_001_01BD0E2C.F8BAE630 Content-Type: text/plain Hello, According to RFC 1812, when using unnumbered IP interface in routers (on point-to-point interfaces), the IP address that such an interface gets is one of the IP addresses of one of the Ethernet interfaces of that router. What should be done with MIB tables that have the IP address as a key, such as: rip2IfConfTable, rip2IfStatTable, ipAddrTable ? Thank you, Hamutal Schur. please send the answer to: Hamutals@rnd.co.il ------ =_NextPart_001_01BD0E2C.F8BAE630 Content-Type: text/html

Hello,

According to RFC 1812, when using unnumbered IP interface in routers (on
point-to-point interfaces), the IP address that such an interface gets
is one of the IP addresses of one of the Ethernet interfaces of that
router.
What should be done with MIB tables that have the IP address as a key,
such as: rip2IfConfTable, rip2IfStatTable, ipAddrTable ?

Thank you,
Hamutal Schur.
please send the answer to: Hamutals@rnd.co.il

------ =_NextPart_001_01BD0E2C.F8BAE630-- From owner-ietf-rip@BayNetworks.COM Fri Jan 30 13:38:22 1998 Delivery-Date: Fri, 30 Jan 1998 13:38:22 -0500 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from ns.cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id NAA17635 for ; Fri, 30 Jan 1998 13:38:21 -0500 (EST) Received: from smtp-gw.BayNetworks.COM (ext-ns1.baynetworks.com [134.177.3.20]) by ns.cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id NAA19468 for ; Fri, 30 Jan 1998 13:41:03 -0500 (EST) Received: from mailhost.BayNetworks.COM (screen2r.BayNetworks.COM [134.177.3.1]) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id KAA12188; Fri, 30 Jan 1998 10:27:05 -0800 (PST) Received: from majordomo.BayNetworks.COM ([192.32.253.10] (may be forged)) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id KAA17829; Fri, 30 Jan 1998 10:27:03 -0800 (PST) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id NAA27929; Fri, 30 Jan 1998 13:28:03 -0500 (EST) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([132.245.135.115] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id NAA27925; Fri, 30 Jan 1998 13:27:58 -0500 (EST) for Received: from majordomo.BayNetworks.COM ([192.32.253.10] (may be forged)) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id NAA04149 for ; Fri, 30 Jan 1998 13:22:19 -0500 (EST) Received: from smtp-gw.BayNetworks.COM (ext-ns3.baynetworks.com [192.32.253.3] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id NAA27921; Fri, 30 Jan 1998 13:27:25 -0500 (EST) for Received: from ns.owlseye.com (owl@ns.owlseye.com [199.173.193.212]) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id NAA07617 for ; Fri, 30 Jan 1998 13:23:22 -0500 (EST) Received: (from owl@localhost) by ns.owlseye.com (8.8.8/8.7.3) id NAA06402; Fri, 30 Jan 1998 13:05:27 -0500 (EST) Date: Fri, 30 Jan 1998 13:05:27 -0500 (EST) Message-Id: <199801301805.NAA06402@ns.owlseye.com> From: owl@owlseye.com To: ietf-rip@BayNetworks.COM Reply-To: owl@owlseye.com Subject: OK to send e-mail? Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk OK to send an e-mail to ietf-rip@baynetworks.com? From owner-ietf-rip@BayNetworks.COM Mon Feb 2 09:58:40 1998 Delivery-Date: Mon, 02 Feb 1998 09:58:45 -0500 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from ns.cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id JAA25519 for ; Mon, 2 Feb 1998 09:58:37 -0500 (EST) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by ns.cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id KAA02283 for ; Mon, 2 Feb 1998 10:01:18 -0500 (EST) Received: from mailhost.BayNetworks.COM ([134.177.1.107] (may be forged)) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id GAA08945; Mon, 2 Feb 1998 06:40:43 -0800 (PST) Received: from majordomo.BayNetworks.COM ([192.32.253.10] (may be forged)) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id GAA25226; Mon, 2 Feb 1998 06:40:31 -0800 (PST) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id JAA02886; Mon, 2 Feb 1998 09:41:33 -0500 (EST) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([134.177.1.107] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id JAA02882; Mon, 2 Feb 1998 09:41:27 -0500 (EST) for Received: from majordomo.BayNetworks.COM ([192.32.253.10] (may be forged)) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id GAA24491 for ; Mon, 2 Feb 1998 06:36:03 -0800 (PST) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id JAA02874; Mon, 2 Feb 1998 09:40:49 -0500 (EST) for Received: from hclhprnd.hclt.com (hclhprnd.hclt.com [204.160.251.1]) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id GAA08335 for ; Mon, 2 Feb 1998 06:35:20 -0800 (PST) Received: from utopia.hclt.com (utopia.hclt.com [204.160.251.53]) by hclhprnd.hclt.com (8.8.5/SCO5) with SMTP id OAA19385 for ; Mon, 2 Feb 1998 14:40:27 GMT Received: by utopia.hclt.com id AA03413 (5.67c/IDA-1.5 for ietf-rip@baynetworks.com); Mon, 2 Feb 1998 19:55:34 GMT Message-Id: <199802021955.AA03413@utopia.hclt.com> Subject: ok To: ietf-rip@BayNetworks.COM Date: Mon, 2 Feb 1998 19:55:34 +0000 (GMT) From: "Thangaraj M" X-Mailer: ELM [version 2.4 PL25] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk ok From owner-ietf-rip@BayNetworks.COM Sun Feb 15 02:00:58 1998 Delivery-Date: Sun, 15 Feb 1998 02:00:59 -0500 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id CAA03207 for ; Sun, 15 Feb 1998 02:00:58 -0500 (EST) Received: from smtp-gw.BayNetworks.COM (ns2.BayNetworks.COM [134.177.3.16]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id CAA14872 for ; Sun, 15 Feb 1998 02:03:38 -0500 (EST) Received: from mailhost.BayNetworks.COM (screen2r.BayNetworks.COM [134.177.3.1]) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id WAA17755; Sat, 14 Feb 1998 22:37:13 -0800 (PST) Received: from majordomo.BayNetworks.COM ([192.32.253.10] (may be forged)) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id WAA02006; Sat, 14 Feb 1998 22:36:46 -0800 (PST) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id BAA06530; Sun, 15 Feb 1998 01:38:38 -0500 (EST) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([134.177.1.107] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id BAA06526; Sun, 15 Feb 1998 01:38:32 -0500 (EST) for Received: from majordomo.BayNetworks.COM ([192.32.253.10] (may be forged)) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id WAA10881 for ; Sat, 14 Feb 1998 22:31:49 -0800 (PST) Received: from smtp-gw.BayNetworks.COM (ext-ns3.baynetworks.com [192.32.253.3] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id BAA06522; Sun, 15 Feb 1998 01:37:17 -0500 (EST) for Received: from netcom13.netcom.com (andrade@netcom13.netcom.com [192.100.81.125]) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id BAA25537 for ; Sun, 15 Feb 1998 01:33:03 -0500 (EST) Received: (from andrade@localhost) by netcom13.netcom.com (8.8.5-r-beta/8.8.5/(NETCOM v1.02)) id WAA03381; Sat, 14 Feb 1998 22:32:34 -0800 (PST) From: Andrade Software Andrade Networking Message-Id: <199802150632.WAA03381@netcom13.netcom.com> Subject: Routing questions about IPv4 header To: nimrod-wg@bbn.com, idr@merit.edu, isis@merit.edu, ietf-rip@BayNetworks.COM Date: Sat, 14 Feb 1998 22:32:33 -0800 (PST) Cc: andrade@netcom13.netcom.com (Alex Alten) Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk Andrade Software & Networking Andrad@Netcom.Com X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2111 Pardon me if I've reached the wrong discussion groups. These seemed to be the best ones for answering my questions. My questions are about the behavior of routers as IPv4 datagrams flow through them. These are based on my understanding of RFC 791. I need to understand some subtle issues with the handling of the IPv4 header. In particular I want to know if any of the following will break the proper routing behavior or cause IPv4 packets to be discarded with typical routers now deployed on the Internet. Q1: In byte #7 there are three bits reserved. The highest bit is always set to 0. Can it be set to 1? Q2: Again in byte #7, if the DF bit is 1 is the MF bit ignored? Can it be set to 1? Q3: If the DF bit is 1 are the Offset (13 bits in bytes #7 & #8) and the Identification (16 bits in bytes #5 & #6) fields ignored? Can they be set to any value? Q4: In byte #2 is the Type of Service Field ever used? Can any pattern be set here? Q5: Options can follow byte #20. An option has a two byte header, the 2nd byte is the length in bytes. This means that the data can be up to 254 bytes in length. However the IHL has a maximum value of 15 (= 60 bytes). Does this mean that the option data only has a real maximum of 38 bytes (40 minus the 2 option header bytes)? Q6: Will routers honor datagrams that include an option field that carry routing or neighbor greeting information? For example, if the payload a RIP, LSP or IS-IS data? Or it is an ICMP message? Q7: As a follow on to Q6. Can the option be an option which has not yet been defined in an RFC? E.g. an experimental or unregistered option number? Will a router honor it? Will it allow RIP, LSP, IS-IS, ICMP, etc. to piggyback on it? I appreciate any answers you may have. Please ensure that your response includes my email address (Andrade@Netcom.Com) since I am not a subscriber to your discussion group. Thank you, - Alex Alten -- Alex Alten P.O. Box 11406 Pleasanton, CA 94588 USA Andrade@Netcom.Com (510) 417-0159 Fax/Voice From owner-idr@merit.edu Sun Feb 15 02:32:28 1998 Delivery-Date: Sun, 15 Feb 1998 02:32:28 -0500 Return-Path: owner-idr@merit.edu Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id CAA03293 for ; Sun, 15 Feb 1998 02:32:27 -0500 (EST) Received: from merit.edu (merit.edu [198.108.1.42]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id CAA14898 for ; Sun, 15 Feb 1998 02:35:08 -0500 (EST) Received: (from majordom@localhost) by merit.edu (8.8.7/8.8.5) id CAA14289 for idr-outgoing; Sun, 15 Feb 1998 02:09:14 -0500 (EST) Received: from netcom13.netcom.com (andrade@netcom13.netcom.com [192.100.81.125]) by merit.edu (8.8.7/8.8.5) with ESMTP id BAA14039; Sun, 15 Feb 1998 01:32:39 -0500 (EST) Received: (from andrade@localhost) by netcom13.netcom.com (8.8.5-r-beta/8.8.5/(NETCOM v1.02)) id WAA03381; Sat, 14 Feb 1998 22:32:34 -0800 (PST) From: Andrade Software Andrade Networking Message-Id: <199802150632.WAA03381@netcom13.netcom.com> Subject: Routing questions about IPv4 header To: nimrod-wg@bbn.com, idr@merit.edu, isis@merit.edu, ietf-rip@baynetworks.com Date: Sat, 14 Feb 1998 22:32:33 -0800 (PST) Cc: andrade@netcom13.netcom.com (Alex Alten) Sender: owner-idr@merit.edu Precedence: bulk Andrade Software & Networking Andrad@Netcom.Com X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2111 Pardon me if I've reached the wrong discussion groups. These seemed to be the best ones for answering my questions. My questions are about the behavior of routers as IPv4 datagrams flow through them. These are based on my understanding of RFC 791. I need to understand some subtle issues with the handling of the IPv4 header. In particular I want to know if any of the following will break the proper routing behavior or cause IPv4 packets to be discarded with typical routers now deployed on the Internet. Q1: In byte #7 there are three bits reserved. The highest bit is always set to 0. Can it be set to 1? Q2: Again in byte #7, if the DF bit is 1 is the MF bit ignored? Can it be set to 1? Q3: If the DF bit is 1 are the Offset (13 bits in bytes #7 & #8) and the Identification (16 bits in bytes #5 & #6) fields ignored? Can they be set to any value? Q4: In byte #2 is the Type of Service Field ever used? Can any pattern be set here? Q5: Options can follow byte #20. An option has a two byte header, the 2nd byte is the length in bytes. This means that the data can be up to 254 bytes in length. However the IHL has a maximum value of 15 (= 60 bytes). Does this mean that the option data only has a real maximum of 38 bytes (40 minus the 2 option header bytes)? Q6: Will routers honor datagrams that include an option field that carry routing or neighbor greeting information? For example, if the payload a RIP, LSP or IS-IS data? Or it is an ICMP message? Q7: As a follow on to Q6. Can the option be an option which has not yet been defined in an RFC? E.g. an experimental or unregistered option number? Will a router honor it? Will it allow RIP, LSP, IS-IS, ICMP, etc. to piggyback on it? I appreciate any answers you may have. Please ensure that your response includes my email address (Andrade@Netcom.Com) since I am not a subscriber to your discussion group. Thank you, - Alex Alten -- Alex Alten P.O. Box 11406 Pleasanton, CA 94588 USA Andrade@Netcom.Com (510) 417-0159 Fax/Voice From owner-ietf-rip@BayNetworks.COM Mon Feb 16 09:31:24 1998 Delivery-Date: Mon, 16 Feb 1998 09:31:24 -0500 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id JAA23016 for ; Mon, 16 Feb 1998 09:31:23 -0500 (EST) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id JAA01971 for ; Mon, 16 Feb 1998 09:33:58 -0500 (EST) Received: from mailhost.BayNetworks.COM (screen2r.BayNetworks.COM [134.177.3.1]) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id GAA09199; Mon, 16 Feb 1998 06:00:31 -0800 (PST) Received: from majordomo.BayNetworks.COM ([192.32.253.10] (may be forged)) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id JAA02727; Mon, 16 Feb 1998 09:01:44 -0500 (EST) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id JAA09436; Mon, 16 Feb 1998 09:03:10 -0500 (EST) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([134.177.1.109] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id JAA09432; Mon, 16 Feb 1998 09:03:04 -0500 (EST) for Received: from majordomo.BayNetworks.COM ([192.32.253.10] (may be forged)) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id FAA20128 for ; Mon, 16 Feb 1998 05:57:26 -0800 (PST) Received: from smtp-gw.BayNetworks.COM (ext-ns3.baynetworks.com [192.32.253.3] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id JAA09422; Mon, 16 Feb 1998 09:02:30 -0500 (EST) for Received: from p-voyageur.issy.cnet.fr (p-voyageur.issy.cnet.fr [139.100.0.39]) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id IAA20174 for ; Mon, 16 Feb 1998 08:58:14 -0500 (EST) Received: by p-voyageur.issy.cnet.fr with Internet Mail Service (5.0.1458.49) id <12ZCNMXM>; Mon, 16 Feb 1998 14:42:55 +0100 Message-ID: <33C73673A9D6D0119A8800805FBE0C1C091799@p-colombin.issy.cnet.fr> From: ALGLAVE Dominique CNET/DTL/ISS To: "'ietf-rip@BayNetworks.COM'" Subject: UNSUBSCRIBE Date: Mon, 16 Feb 1998 14:42:51 +0100 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk From owner-ietf-rip@BayNetworks.COM Mon Feb 16 09:32:00 1998 Delivery-Date: Mon, 16 Feb 1998 09:32:01 -0500 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id JAA23035 for ; Mon, 16 Feb 1998 09:32:00 -0500 (EST) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id JAA01977 for ; Mon, 16 Feb 1998 09:34:39 -0500 (EST) Received: from mailhost.BayNetworks.COM ([134.177.1.107] (may be forged)) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id GAA09210; Mon, 16 Feb 1998 06:00:52 -0800 (PST) Received: from majordomo.BayNetworks.COM ([192.32.253.10] (may be forged)) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id GAA16094; Mon, 16 Feb 1998 06:00:24 -0800 (PST) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id JAA09441; Mon, 16 Feb 1998 09:03:34 -0500 (EST) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([134.177.1.107] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id JAA09437; Mon, 16 Feb 1998 09:03:28 -0500 (EST) for Received: from majordomo.BayNetworks.COM ([192.32.253.10] (may be forged)) by mailhost.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id FAA03433 for ; Mon, 16 Feb 1998 05:57:23 -0800 (PST) Received: from smtp-gw.BayNetworks.COM (ext-ns3.baynetworks.com [192.32.253.3] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id JAA09427; Mon, 16 Feb 1998 09:02:55 -0500 (EST) for Received: from p-voyageur.issy.cnet.fr (p-voyageur.issy.cnet.fr [139.100.0.39]) by smtp-gw.BayNetworks.COM (8.8.6/8.8.6) with ESMTP id IAA20210 for ; Mon, 16 Feb 1998 08:58:36 -0500 (EST) Received: by p-voyageur.issy.cnet.fr with Internet Mail Service (5.0.1458.49) id <12ZCNMX3>; Mon, 16 Feb 1998 14:43:02 +0100 Message-ID: <33C73673A9D6D0119A8800805FBE0C1C09179A@p-colombin.issy.cnet.fr> From: ALGLAVE Dominique CNET/DTL/ISS To: "'ietf-rip@BayNetworks.COM'" Date: Mon, 16 Feb 1998 14:43:02 +0100 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk UNSUBSCRIBE From owner-ietf-rip@BayNetworks.COM Wed Apr 15 11:01:04 1998 Delivery-Date: Wed, 15 Apr 1998 11:01:05 -0400 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id LAA01267 for ; Wed, 15 Apr 1998 11:01:01 -0400 (EDT) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id LAA11941 for ; Wed, 15 Apr 1998 11:03:29 -0400 (EDT) Received: from mailhost.BayNetworks.COM ([134.177.1.107]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id HAA29050; Wed, 15 Apr 1998 07:41:08 -0700 (PDT) Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id HAA26576; Wed, 15 Apr 1998 07:39:13 -0700 (PDT) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id KAA08674; Wed, 15 Apr 1998 10:41:39 -0400 (EDT) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([132.245.135.84] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id KAA08666; Wed, 15 Apr 1998 10:40:58 -0400 (EDT) for Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id KAA05433 for ; Wed, 15 Apr 1998 10:35:25 -0400 (EDT) Received: from smtp-gw.BayNetworks.COM (ext-ns3.baynetworks.com [192.32.253.3] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id KAA08662; Wed, 15 Apr 1998 10:40:25 -0400 (EDT) for Received: from atlas.xylogics.com ([192.32.253.1]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id KAA21310 for ; Wed, 15 Apr 1998 10:35:33 -0400 (EDT) Received: from ns.ietf.org (ietf.org [132.151.1.19]) by atlas.xylogics.com (8.7.3/8.7.3) with ESMTP id KAA22886 for ; Wed, 15 Apr 1998 10:32:19 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id KAA00408; Wed, 15 Apr 1998 10:33:34 -0400 (EDT) Message-Id: <199804151433.KAA00408@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ietf-rip@xylogics.com From: Internet-Drafts@ns.ietf.org Reply-to: Internet-Drafts@ns.ietf.org Subject: I-D ACTION:draft-ietf-ripv2-protocol-v2-03.txt Date: Wed, 15 Apr 1998 10:33:33 -0400 Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the RIP Version II Working Group of the IETF. Title : RIP Version 2 Carrying Additional Information Author(s) : G. Malkin Filename : draft-ietf-ripv2-protocol-v2-03.txt Pages : 36 Date : 14-Apr-98 This document specifies an extension of the Routing Information Protocol (RIP), as defined in [1], to expand the amount of useful information carried in RIP messages and to add a measure of security. A companion document will define the SNMP MIB objects for RIP-2 [2]. An additional document will define cryptographic security improvements for RIP-2 [3]. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ripv2-protocol-v2-03.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ripv2-protocol-v2-03.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ripv2-protocol-v2-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980414151549.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ripv2-protocol-v2-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ripv2-protocol-v2-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980414151549.I-D@ietf.org> --OtherAccess-- --NextPart-- From adm Wed Apr 15 11:26:32 1998 Delivery-Date: Wed, 15 Apr 1998 11:36:59 -0400 Return-Path: adm Received: (from adm@localhost) by ns.ietf.org (8.8.5/8.8.7a) id LAA02238 for ietf-123-outbound.10@ietf.org; Wed, 15 Apr 1998 11:25:02 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id KAA00408; Wed, 15 Apr 1998 10:33:34 -0400 (EDT) Message-Id: <199804151433.KAA00408@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ietf-rip@xylogics.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-ripv2-protocol-v2-03.txt Date: Wed, 15 Apr 1998 10:33:33 -0400 Sender: cclark@cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the RIP Version II Working Group of the IETF. Title : RIP Version 2 Carrying Additional Information Author(s) : G. Malkin Filename : draft-ietf-ripv2-protocol-v2-03.txt Pages : 36 Date : 14-Apr-98 This document specifies an extension of the Routing Information Protocol (RIP), as defined in [1], to expand the amount of useful information carried in RIP messages and to add a measure of security. A companion document will define the SNMP MIB objects for RIP-2 [2]. An additional document will define cryptographic security improvements for RIP-2 [3]. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ripv2-protocol-v2-03.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ripv2-protocol-v2-03.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ripv2-protocol-v2-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980414151549.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ripv2-protocol-v2-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ripv2-protocol-v2-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980414151549.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-ietf-rip@BayNetworks.COM Fri May 22 08:52:46 1998 Delivery-Date: Fri, 22 May 1998 08:52:46 -0400 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from cnri.reston.va.us (ns.cnri.reston.va.us [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id IAA02769 for ; Fri, 22 May 1998 08:52:45 -0400 (EDT) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id IAA20186 for ; Fri, 22 May 1998 08:55:08 -0400 (EDT) Received: from mailhost.BayNetworks.COM ([134.177.1.107]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id FAA08878; Fri, 22 May 1998 05:34:42 -0700 (PDT) Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id FAA28123; Fri, 22 May 1998 05:34:33 -0700 (PDT) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id IAA02497; Fri, 22 May 1998 08:39:36 -0400 (EDT) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([132.245.135.115] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id IAA02493; Fri, 22 May 1998 08:39:30 -0400 (EDT) for Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id IAA16922 for ; Fri, 22 May 1998 08:29:35 -0400 (EDT) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id IAA02489; Fri, 22 May 1998 08:38:57 -0400 (EDT) for Received: from teil.soft.net (teil.soft.net [164.164.10.2]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with SMTP id FAA08462 for ; Fri, 22 May 1998 05:28:29 -0700 (PDT) Received: by teil.soft.net (940816.SGI.8.6.9/940406.SGI) for ietf-rip@baynetworks.com id SAA13276; Fri, 22 May 1998 18:01:21 -0530 From: gsudar@teil.soft.net (G. Sudarshan) Message-Id: <199805222331.SAA13276@teil.soft.net> Subject: Route set with REJECT flag in the IP route table - regd To: ietf-rip@BayNetworks.COM Date: Fri, 22 May 1998 18:01:21 -0530 (IST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk Hello ! The following has details of a RIP implementation. I need clarification for the problem mentioned. Thanks in advance. have a nice day, sudarshan Salient features of RIP daemon implemented : ---------------- I have a RIP daemon which sends and receives RIPv1 packets. It also receives RIPv2 packet and uses only the subnet mask of the route entries. All other RIPv2 spcific information are ignored. The daemon does not send RIPv2 packets. The RIPv2 routes are installed in IP route table with the subnet mask received as part of the RIP packet. The host routes are not installed in IP route table but interface network information is installed in IP route table. Problem : ------- Assume a router has 2 interfaces configured with 164.164.10.100, 164.164.20.100 with all netmask being 255.255.255.0. Assume that the same router has another interface with IP address 165.165.10.100 and netmask 255.255.0.0 configured to reach router R. RIP daemon should not advertise 164.164.10.0 and 164.164.20.0 to router R (as per RIPv1 RFC). But it will advertise route information for 164.164.10.0 to the interface with IP address 164.164.20.100 and vice-versa. The router has a default route to router R. This default route is selected if no other route is available. Doubts : 1. What route information is advertised to router R ? 2. If e.g. 164.164.0.0 is advertised then how my router (with RIP daemon running is the only routing protocol running) will ensure that a packet to 164.164.30.100 cannot be forwarded ? From owner-ietf-rip@BayNetworks.COM Fri May 22 10:47:50 1998 Delivery-Date: Fri, 22 May 1998 10:47:50 -0400 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from cnri.reston.va.us (ns.cnri.reston.va.us [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id KAA04354 for ; Fri, 22 May 1998 10:47:50 -0400 (EDT) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id KAA20629 for ; Fri, 22 May 1998 10:50:14 -0400 (EDT) Received: from mailhost.BayNetworks.COM (screen2r.BayNetworks.COM [134.177.3.1]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id HAA20435; Fri, 22 May 1998 07:31:35 -0700 (PDT) Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id HAA29657; Fri, 22 May 1998 07:32:09 -0700 (PDT) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id KAA02869; Fri, 22 May 1998 10:37:49 -0400 (EDT) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([132.245.135.84] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id KAA02865; Fri, 22 May 1998 10:37:43 -0400 (EDT) for Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id KAA05237 for ; Fri, 22 May 1998 10:31:40 -0400 (EDT) Received: from smtp-gw.BayNetworks.COM (ext-ns4.baynetworks.com [192.32.253.7]) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id KAA02861; Fri, 22 May 1998 10:37:11 -0400 (EDT) for Received: from fwns2.raleigh.ibm.com (fwns2d.raleigh.ibm.com [204.146.167.236]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id KAA23663 for ; Fri, 22 May 1998 10:31:37 -0400 (EDT) Received: from rtpmail01.raleigh.ibm.com (rtpmail01.raleigh.ibm.com [9.37.172.24]) by fwns2.raleigh.ibm.com (AIX4.2/UCB 8.7/8.7RTP-FW1.1) with ESMTP id KAA67180; Fri, 22 May 1998 10:29:20 -0400 (EDT) Received: from aceman.raleigh.ibm.com (aceman.raleigh.ibm.com [9.37.177.119]) by rtpmail01.raleigh.ibm.com (8.8.5/8.8.5/RTP-ral-1.1) with SMTP id KAA58574; Fri, 22 May 1998 10:29:23 -0400 Received: from loopback by aceman.raleigh.ibm.com (AIX 4.1/UCB 5.64/4.03-RAL) id AA27022; Fri, 22 May 1998 10:29:21 -0400 Message-Id: <35658BC1.C1A45BA2@raleigh.ibm.com> Date: Fri, 22 May 1998 10:29:21 -0400 From: Acee Lindem Organization: IBM Networking Divison X-Mailer: Mozilla 4.04 [en] (X11; I; AIX 4.1) Mime-Version: 1.0 To: "G. Sudarshan" Cc: ietf-rip@BayNetworks.COM Subject: Re: Route set with REJECT flag in the IP route table - regd References: <199805222331.SAA13276@teil.soft.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk G. Sudarshan wrote: > > Hello ! > > The following has details of a RIP implementation. I need clarification > for the problem mentioned. Thanks in advance. > > have a nice day, > sudarshan > > Salient features of RIP daemon implemented : > ---------------- > I have a RIP daemon which sends and receives RIPv1 packets. It also receives > RIPv2 packet and uses only the subnet mask of the route entries. All other > RIPv2 spcific information are ignored. The daemon does not send RIPv2 packets. > > The RIPv2 routes are installed in IP route table with the subnet mask > received as part of the RIP packet. The host routes are not installed in > IP route table but interface network information is installed in IP route > table. This doesn't sound too useful. Are you aware of Veron Schryver's routed implementation including RIPv2 and IRDP? I have a copy but can't seem to find the ftp achive site right now. > > Problem : > ------- > Assume a router has 2 interfaces configured with 164.164.10.100, > 164.164.20.100 with all netmask being 255.255.255.0. > Assume that the same router has another interface with IP address > 165.165.10.100 and netmask 255.255.0.0 configured to reach router R. > RIP daemon should not advertise 164.164.10.0 and 164.164.20.0 to > router R (as per RIPv1 RFC). But it will advertise route information > for 164.164.10.0 to the interface with IP address 164.164.20.100 and vice-versa. > The router has a default route to router R. This default route is selected if > no other route is available. > Doubts : > 1. What route information is advertised to router R ? You can either advertise nothing or 164.164/16. > 2. If e.g. 164.164.0.0 is advertised then how my > router (with RIP daemon running is the only routing protocol running) > will ensure that a packet to 164.164.30.100 cannot be forwarded ? You should add a reject route to 164.164/16. -- Acee From owner-ietf-rip@BayNetworks.COM Fri May 22 11:45:53 1998 Delivery-Date: Fri, 22 May 1998 11:45:53 -0400 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from cnri.reston.va.us (ns.cnri.reston.va.us [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id LAA05528 for ; Fri, 22 May 1998 11:45:52 -0400 (EDT) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id LAA21056 for ; Fri, 22 May 1998 11:48:17 -0400 (EDT) Received: from mailhost.BayNetworks.COM (screen2r.BayNetworks.COM [134.177.3.1]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id IAA27071; Fri, 22 May 1998 08:32:02 -0700 (PDT) Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id IAA05694; Fri, 22 May 1998 08:32:46 -0700 (PDT) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id LAA03060; Fri, 22 May 1998 11:38:32 -0400 (EDT) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([134.177.1.107] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id LAA03056; Fri, 22 May 1998 11:38:26 -0400 (EDT) for Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id IAA09721 for ; Fri, 22 May 1998 08:27:59 -0700 (PDT) Received: from smtp-gw.BayNetworks.COM (ext-ns4.baynetworks.com [192.32.253.7]) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id LAA03052; Fri, 22 May 1998 11:37:53 -0400 (EDT) for Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id LAA28682 for ; Fri, 22 May 1998 11:32:19 -0400 (EDT) Received: (from vjs@localhost) by calcite.rhyolite.com (8.8.5/calcite) id JAA25985 mail_from ; Fri, 22 May 1998 09:30:11 -0600 (MDT) Date: Fri, 22 May 1998 09:30:11 -0600 (MDT) From: Vernon Schryver Message-Id: <199805221530.JAA25985@calcite.rhyolite.com> To: acee@raleigh.ibm.com, gsudar@teil.soft.net Subject: Re: Route set with REJECT flag in the IP route table - regd Cc: ietf-rip@BayNetworks.COM Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk > From: Acee Lindem > To: "G. Sudarshan" > Cc: ietf-rip@BayNetworks.COM > ... > .... Are you aware of Veron Schryver's routed > implementation including RIPv2 and IRDP? I have a copy but can't seem to > find the ftp achive site right now. > ... Look in ftp.rhyolite.com:src/routed.tar.Z or in ftp.sgi.com:sgi/src/routed.tar.Z I've recently fixed some obscure problems related to RIPv1, variable length subnet masks, and media such as ATM and HIPPI that support neither multicast nor broadcast. Slightly older (and in one case modified in ways I strongly disagree with) versions of the code can be found in current distributions of NetBSD, FreeBSD, and OpenBSD. Vernon Schryver vjs@rhyolite.com From owner-ietf-rip@BayNetworks.COM Tue Jun 2 21:43:31 1998 Delivery-Date: Tue, 02 Jun 1998 21:43:32 -0400 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from cnri.reston.va.us (ns.cnri.reston.va.us [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id VAA01867 for ; Tue, 2 Jun 1998 21:43:31 -0400 (EDT) Received: from smtp-gw.BayNetworks.COM (ext-ns4.baynetworks.com [192.32.253.7]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id VAA11377 for ; Tue, 2 Jun 1998 21:45:52 -0400 (EDT) Received: from mailhost.BayNetworks.COM ([132.245.135.115]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id VAA27315; Tue, 2 Jun 1998 21:23:15 -0400 (EDT) Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id VAA06240; Tue, 2 Jun 1998 21:25:41 -0400 (EDT) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id VAA05005; Tue, 2 Jun 1998 21:31:21 -0400 (EDT) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([132.245.135.84] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id VAA05001; Tue, 2 Jun 1998 21:31:15 -0400 (EDT) for Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id VAA11332 for ; Tue, 2 Jun 1998 21:17:14 -0400 (EDT) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id VAA04996; Tue, 2 Jun 1998 21:30:42 -0400 (EDT) for Received: from loop.com.tw (loop.com.tw [168.95.223.19]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id SAA04505 for ; Tue, 2 Jun 1998 18:19:42 -0700 (PDT) Received: from loop.com.tw (james [140.132.1.55]) by loop.com.tw (8.7.1/8.7.1) with ESMTP id JAA14544 for ; Wed, 3 Jun 1998 09:20:51 +0800 (CST) Message-ID: <35757925.1525522D@loop.com.tw> Date: Wed, 03 Jun 1998 09:26:13 -0700 From: james Organization: loop X-Mailer: Mozilla 4.03 [en] (Win16; I) MIME-Version: 1.0 To: ietf-rip@BayNetworks.COM Subject: Route set with REJECT flag in the IP route table - regd Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk Hello ! The following has details of a RIP implementation. I need clarification for the problem mentioned. Thanks in advance. have a nice day, sudarshan Salient features of RIP daemon implemented : ---------------- I have a RIP daemon which sends and receives RIPv1 packets. It also receives RIPv2 packet and uses only the subnet mask of the route entries. All other RIPv2 spcific information are ignored. The daemon does not send RIPv2 packets. The RIPv2 routes are installed in IP route table with the subnet mask received as part of the RIP packet. The host routes are not installed in IP route table but interface network information is installed in IP route table. Problem : ------- Assume a router has 2 interfaces configured with 164.164.10.100, 164.164.20.100 with all netmask being 255.255.255.0. Assume that the same router has another interface with IP address 165.165.10.100 and netmask 255.255.0.0 configured to reach router R. RIP daemon should not advertise 164.164.10.0 and 164.164.20.0 to router R (as per RIPv1 RFC). But it will advertise route information for 164.164.10.0 to the interface with IP address 164.164.20.100 and vice-versa. The router has a default route to router R. This default route is selected if no other route is available. Doubts : 1. What route information is advertised to router R ? 2. If e.g. 164.164.0.0 is advertised then how my router (with RIP daemon running is the only routing protocol running) will ensure that a packet to 164.164.30.100 cannot be forwarded ? From owner-ietf-rip@BayNetworks.COM Wed Jun 3 10:34:47 1998 Delivery-Date: Wed, 03 Jun 1998 10:34:47 -0400 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from cnri.reston.va.us (ns.cnri.reston.va.us [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id KAA17659 for ; Wed, 3 Jun 1998 10:34:47 -0400 (EDT) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id KAA13332 for ; Wed, 3 Jun 1998 10:37:09 -0400 (EDT) Received: from mailhost.BayNetworks.COM (screen2r.BayNetworks.COM [134.177.3.1]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id HAA01242; Wed, 3 Jun 1998 07:20:21 -0700 (PDT) Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id HAA13743; Wed, 3 Jun 1998 07:21:02 -0700 (PDT) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id KAA07629; Wed, 3 Jun 1998 10:27:02 -0400 (EDT) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([132.245.135.115] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id KAA07625; Wed, 3 Jun 1998 10:26:57 -0400 (EDT) for Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id KAA11290 for ; Wed, 3 Jun 1998 10:16:30 -0400 (EDT) Received: from smtp-gw.BayNetworks.COM (ext-ns3.baynetworks.com [192.32.253.3]) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id KAA07621; Wed, 3 Jun 1998 10:26:21 -0400 (EDT) for Received: from fwns2.raleigh.ibm.com (fwns2d.raleigh.ibm.com [204.146.167.236]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id KAA12290 for ; Wed, 3 Jun 1998 10:20:57 -0400 (EDT) Received: from rtpmail03.raleigh.ibm.com (rtpmail03.raleigh.ibm.com [9.37.172.47]) by fwns2.raleigh.ibm.com (AIX4.2/UCB 8.7/8.7RTP-FW1.1) with ESMTP id KAA62330; Wed, 3 Jun 1998 10:18:49 -0400 (EDT) Received: from aceman.raleigh.ibm.com (aceman.raleigh.ibm.com [9.37.177.119]) by rtpmail03.raleigh.ibm.com (8.8.5/8.8.5/RTP-ral-1.1) with SMTP id KAA25562; Wed, 3 Jun 1998 10:18:52 -0400 Received: from loopback by aceman.raleigh.ibm.com (AIX 4.1/UCB 5.64/4.03-RAL) id AA13134; Wed, 3 Jun 1998 10:18:50 -0400 Message-Id: <35755B4A.83026CB9@raleigh.ibm.com> Date: Wed, 03 Jun 1998 10:18:50 -0400 From: Acee Lindem Organization: IBM Networking Divison X-Mailer: Mozilla 4.04 [en] (X11; I; AIX 4.1) Mime-Version: 1.0 To: james Cc: ietf-rip@BayNetworks.COM Subject: Re: Route set with REJECT flag in the IP route table - regd References: <35757925.1525522D@loop.com.tw> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk james wrote: > > Hello ! > > The following has details of a RIP implementation. I need clarification > for the problem mentioned. Thanks in advance. > > have a nice day, > sudarshan > > Salient features of RIP daemon implemented : > ---------------- > I have a RIP daemon which sends and receives RIPv1 packets. It also > receives > RIPv2 packet and uses only the subnet mask of the route entries. All > other > RIPv2 spcific information are ignored. The daemon does not send RIPv2 > packets. > > The RIPv2 routes are installed in IP route table with the subnet mask > received as part of the RIP packet. The host routes are not installed in > IP route table but interface network information is installed in IP > route > table. > > Problem : > ------- > Assume a router has 2 interfaces configured with 164.164.10.100, > 164.164.20.100 with all netmask being 255.255.255.0. > Assume that the same router has another interface with IP address > 165.165.10.100 and netmask 255.255.0.0 configured to reach router R. > RIP daemon should not advertise 164.164.10.0 and 164.164.20.0 to > router R (as per RIPv1 RFC). But it will advertise route information > for 164.164.10.0 to the interface with IP address 164.164.20.100 and > vice-versa. > The router has a default route to router R. This default route is > selected if > no other route is available. > Doubts : > 1. What route information is advertised to router R ? Since router R is using RIPv1 you can advertise the class B (164.164/16) or no route at all. > 2. If e.g. 164.164.0.0 is advertised then how my > router (with RIP daemon running is the only routing protocol running) > will ensure that a packet to 164.164.30.100 cannot be forwarded ? You could install 164.164/16 as a reject route (i.e., a route which causes packets to be dropped and ICMP host unreachables to be sent). -- Acee From owner-ietf-rip@BayNetworks.COM Mon Jun 8 10:26:01 1998 Delivery-Date: Mon, 08 Jun 1998 10:26:01 -0400 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from cnri.reston.va.us (ns.cnri.reston.va.us [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id KAA25269 for ; Mon, 8 Jun 1998 10:26:00 -0400 (EDT) Received: from smtp-gw.BayNetworks.COM (ext-ns3.baynetworks.com [192.32.253.3]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id KAA02722 for ; Mon, 8 Jun 1998 10:28:23 -0400 (EDT) Received: from mailhost.BayNetworks.COM ([132.245.135.84]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id KAA09056; Mon, 8 Jun 1998 10:13:34 -0400 (EDT) Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id KAA06066; Mon, 8 Jun 1998 10:04:46 -0400 (EDT) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id KAA03223; Mon, 8 Jun 1998 10:13:55 -0400 (EDT) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([134.177.1.107] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id KAA03219; Mon, 8 Jun 1998 10:13:48 -0400 (EDT) for Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id HAA01561 for ; Mon, 8 Jun 1998 07:02:37 -0700 (PDT) Received: from smtp-gw.BayNetworks.COM (ext-ns3.baynetworks.com [192.32.253.3]) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id KAA03215; Mon, 8 Jun 1998 10:13:15 -0400 (EDT) for Received: from atlas.xylogics.com ([132.245.139.1]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id KAA08470 for ; Mon, 8 Jun 1998 10:07:47 -0400 (EDT) Received: from ietf.org (ietf.org [132.151.1.19]) by atlas.xylogics.com (8.7.3/8.7.3) with ESMTP id KAA26572 for ; Mon, 8 Jun 1998 10:04:26 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id KAA24550; Mon, 8 Jun 1998 10:05:14 -0400 (EDT) Message-Id: <199806081405.KAA24550@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ietf-rip@xylogics.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-ripv2-protocol-v2-04.txt Date: Mon, 08 Jun 1998 10:05:13 -0400 Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the RIP Version II Working Group of the IETF. Title : RIP Version 2 Carrying Additional Information Author(s) : G. Malkin Filename : draft-ietf-ripv2-protocol-v2-04.txt Pages : 37 Date : 05-Jun-98 This document specifies an extension of the Routing Information Protocol (RIP), as defined in [1], to expand the amount of useful information carried in RIP messages and to add a measure of security. A companion document will define the SNMP MIB objects for RIP-2 [2]. An additional document will define cryptographic security improvements for RIP-2 [3]. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ripv2-protocol-v2-04.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ripv2-protocol-v2-04.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ripv2-protocol-v2-04.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980605163702.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ripv2-protocol-v2-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ripv2-protocol-v2-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980605163702.I-D@ietf.org> --OtherAccess-- --NextPart-- From adm Mon Jun 8 10:36:28 1998 Delivery-Date: Mon, 08 Jun 1998 10:45:38 -0400 Return-Path: adm Received: (from adm@localhost) by ietf.org (8.8.5/8.8.7a) id KAA25579 for ietf-123-outbound.10@ietf.org; Mon, 8 Jun 1998 10:35:03 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id KAA24550; Mon, 8 Jun 1998 10:05:14 -0400 (EDT) Message-Id: <199806081405.KAA24550@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ietf-rip@xylogics.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-ripv2-protocol-v2-04.txt Date: Mon, 08 Jun 1998 10:05:13 -0400 Sender: cclark@CNRI.RESTON.VA.US --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the RIP Version II Working Group of the IETF. Title : RIP Version 2 Carrying Additional Information Author(s) : G. Malkin Filename : draft-ietf-ripv2-protocol-v2-04.txt Pages : 37 Date : 05-Jun-98 This document specifies an extension of the Routing Information Protocol (RIP), as defined in [1], to expand the amount of useful information carried in RIP messages and to add a measure of security. A companion document will define the SNMP MIB objects for RIP-2 [2]. An additional document will define cryptographic security improvements for RIP-2 [3]. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ripv2-protocol-v2-04.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ripv2-protocol-v2-04.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ripv2-protocol-v2-04.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980605163702.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ripv2-protocol-v2-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ripv2-protocol-v2-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980605163702.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-ietf-rip@BayNetworks.COM Tue Jun 9 06:02:58 1998 Delivery-Date: Tue, 09 Jun 1998 06:03:03 -0400 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from cnri.reston.va.us (ns.cnri.reston.va.us [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id GAA18598 for ; Tue, 9 Jun 1998 06:02:58 -0400 (EDT) Received: from smtp-gw.BayNetworks.COM (ns5.baynetworks.com [194.133.90.101]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id GAA07415 for ; Tue, 9 Jun 1998 06:05:10 -0400 (EDT) Received: from mailhost.BayNetworks.COM ([132.245.135.84]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id LAA22069; Tue, 9 Jun 1998 11:29:23 +0200 (MET DST) Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id FAA29895; Tue, 9 Jun 1998 05:23:55 -0400 (EDT) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id FAA08117; Tue, 9 Jun 1998 05:32:16 -0400 (EDT) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([132.245.135.115] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id FAA08113; Tue, 9 Jun 1998 05:32:11 -0400 (EDT) for Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id FAA10388 for ; Tue, 9 Jun 1998 05:21:20 -0400 (EDT) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id FAA08109; Tue, 9 Jun 1998 05:31:26 -0400 (EDT) for Received: from hitiij.hitachi.co.jp (root@hitiij.hitachi.co.jp [133.145.224.3]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id CAA07583 for ; Tue, 9 Jun 1998 02:20:09 -0700 (PDT) Received: from naganuki.in.hitachi-it.co.jp by hitiij.hitachi.co.jp (8.8.8+2.7Wbeta7/3.6W-hitiij) id SAA22739; Tue, 9 Jun 1998 18:20:20 +0900 (JST) Received: from in.hitachi-it.co.jp ([202.16.25.82]) by naganuki.in.hitachi-it.co.jp (8.8.8/3.6W-naganuki) with ESMTP id SAA28584; Tue, 9 Jun 1998 18:23:19 +0900 (JST) Message-ID: <357CFEB2.77BFACF2@in.hitachi-it.co.jp> Date: Tue, 09 Jun 1998 18:21:54 +0900 From: Nariyasu Hirata X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: ietf-rip@BayNetworks.COM Subject: Auth Data Length Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk Hi. I need a clarification about the Auth Data Length octet for the MD5 authentication. Methinks RFC 2082 says this octet is the value 16, but I found that some major router uses the value 16 instead. Is this value count the Address Family and Authentication Type fields along with the Authentication Data trailer? Thanks. - Hirata From owner-ietf-rip@BayNetworks.COM Tue Jun 9 09:57:56 1998 Delivery-Date: Tue, 09 Jun 1998 09:57:56 -0400 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from cnri.reston.va.us (ns.cnri.reston.va.us [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id JAA22047 for ; Tue, 9 Jun 1998 09:57:55 -0400 (EDT) Received: from smtp-gw.BayNetworks.COM (ext-ns4.baynetworks.com [192.32.253.7]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id KAA08135 for ; Tue, 9 Jun 1998 10:00:17 -0400 (EDT) Received: from mailhost.BayNetworks.COM ([132.245.135.84]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id JAA25224; Tue, 9 Jun 1998 09:39:58 -0400 (EDT) Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id JAA16642; Tue, 9 Jun 1998 09:39:21 -0400 (EDT) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id JAA08820; Tue, 9 Jun 1998 09:49:30 -0400 (EDT) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([132.245.135.84] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id JAA08816; Tue, 9 Jun 1998 09:49:24 -0400 (EDT) for Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id JAA16327 for ; Tue, 9 Jun 1998 09:35:13 -0400 (EDT) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id JAA08812; Tue, 9 Jun 1998 09:48:48 -0400 (EDT) for Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id GAA17281 for ; Tue, 9 Jun 1998 06:36:23 -0700 (PDT) Received: (from vjs@localhost) by calcite.rhyolite.com (8.8.5/calcite) id HAA17178 mail_from ; Tue, 9 Jun 1998 07:39:28 -0600 (MDT) Date: Tue, 9 Jun 1998 07:39:28 -0600 (MDT) From: Vernon Schryver Message-Id: <199806091339.HAA17178@calcite.rhyolite.com> To: hirata@in.hitachi-it.co.jp, ietf-rip@BayNetworks.COM Subject: Re: Auth Data Length Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk > From: Nariyasu Hirata > To: ietf-rip@BayNetworks.COM > I need a clarification about the Auth Data Length octet for the MD5 > authentication. Methinks RFC 2082 says this octet is the value 16, but I > found that some major router uses the value 16 instead. > Is this value count the Address Family and Authentication Type fields > along with the Authentication Data trailer? I do not understand. Should one of the values "16" in that message be something else? My code (in FreeBSD, NetBSD, OpenBSD, and IRIX) puts 16 or the length of the MD5 hash into the twelth byte. I paragraph "(4)" of section 3.1 of RFC 2082 as saying the value should be 16. What other implementations (major or otherwise) of RIPv2 MD5 authentiation have you found to test with, particularly that use something other than 16? Years ago I gave up nagging people inside a very major router vendor to arrange private interoperation test of their new code to look for exactly this kind of issue. I've always been worried that my personal reading of the MD5 RIPv2 draft might have been wrong. Vernon Schryver vjs@rhyolite.com From owner-ietf-rip@BayNetworks.COM Tue Jun 9 21:12:30 1998 Delivery-Date: Tue, 09 Jun 1998 21:12:31 -0400 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from cnri.reston.va.us (ns.cnri.reston.va.us [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id VAA02627 for ; Tue, 9 Jun 1998 21:12:30 -0400 (EDT) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id VAA11673 for ; Tue, 9 Jun 1998 21:14:53 -0400 (EDT) Received: from mailhost.BayNetworks.COM ([132.245.135.115]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id SAA22220; Tue, 9 Jun 1998 18:00:47 -0700 (PDT) Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id VAA15130; Tue, 9 Jun 1998 21:01:12 -0400 (EDT) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id VAA11704; Tue, 9 Jun 1998 21:07:46 -0400 (EDT) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([134.177.1.107] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id VAA11700; Tue, 9 Jun 1998 21:07:40 -0400 (EDT) for Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id RAA26817 for ; Tue, 9 Jun 1998 17:56:24 -0700 (PDT) Received: from smtp-gw.BayNetworks.COM (ns2.BayNetworks.COM [134.177.3.16]) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id VAA11696; Tue, 9 Jun 1998 21:07:06 -0400 (EDT) for Received: from hitiij.hitachi.co.jp (root@hitiij.hitachi.co.jp [133.145.224.3]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id RAA04355 for ; Tue, 9 Jun 1998 17:56:49 -0700 (PDT) Received: from naganuki.in.hitachi-it.co.jp by hitiij.hitachi.co.jp (8.8.8+2.7Wbeta7/3.6W-hitiij) id JAA07662; Wed, 10 Jun 1998 09:56:00 +0900 (JST) Received: from in.hitachi-it.co.jp ([202.16.25.82]) by naganuki.in.hitachi-it.co.jp (8.8.8/3.6W-naganuki) with ESMTP id JAA07030; Wed, 10 Jun 1998 09:59:02 +0900 (JST) Message-ID: <357DDA09.37C76A20@in.hitachi-it.co.jp> Date: Wed, 10 Jun 1998 09:57:45 +0900 From: Nariyasu Hirata X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: Vernon Schryver CC: ietf-rip@BayNetworks.COM Subject: Re: Auth Data Length References: <199806091339.HAA17178@calcite.rhyolite.com> Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk Vernon Schryver wrote: > > > From: Nariyasu Hirata > > To: ietf-rip@BayNetworks.COM > > > I need a clarification about the Auth Data Length octet for the MD5 > > authentication. Methinks RFC 2082 says this octet is the value 16, but I > > found that some major router uses the value 16 instead. Alas, I had to say that one uses the value 20 instead. > > Is this value count the Address Family and Authentication Type fields > > along with the Authentication Data trailer? > > I do not understand. Should one of the values "16" in that message > be something else? > > My code (in FreeBSD, NetBSD, OpenBSD, and IRIX) puts 16 or the length of > the MD5 hash into the twelth byte. I paragraph "(4)" of section 3.1 of > RFC 2082 as saying the value should be 16. > > What other implementations (major or otherwise) of RIPv2 MD5 authentiation > have you found to test with, particularly that use something other than > 16? Years ago I gave up nagging people inside a very major router vendor > to arrange private interoperation test of their new code to look for > exactly this kind of issue. I've always been worried that my personal > reading of the MD5 RIPv2 draft might have been wrong. My reading is the same as you, but at least one major vender uses a different value. You will find the name of the vender at the Authors' section of RFC 2082. - Hirata From owner-ietf-rip@BayNetworks.COM Tue Jun 9 21:40:32 1998 Delivery-Date: Tue, 09 Jun 1998 21:40:33 -0400 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from cnri.reston.va.us (ns.cnri.reston.va.us [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id VAA02752 for ; Tue, 9 Jun 1998 21:40:32 -0400 (EDT) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id VAA11735 for ; Tue, 9 Jun 1998 21:42:55 -0400 (EDT) Received: from mailhost.BayNetworks.COM ([134.177.1.107]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id SAA24386; Tue, 9 Jun 1998 18:25:33 -0700 (PDT) Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id SAA08354; Tue, 9 Jun 1998 18:25:30 -0700 (PDT) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id VAA11750; Tue, 9 Jun 1998 21:34:40 -0400 (EDT) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([132.245.135.84] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id VAA11746; Tue, 9 Jun 1998 21:34:34 -0400 (EDT) for Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id VAA12165 for ; Tue, 9 Jun 1998 21:20:27 -0400 (EDT) Received: from smtp-gw.BayNetworks.COM (ext-ns4.baynetworks.com [192.32.253.7]) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id VAA11742; Tue, 9 Jun 1998 21:34:02 -0400 (EDT) for Received: from tor.securecomputing.com (tor.securecomputing.com [199.71.190.98]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id VAA19011 for ; Tue, 9 Jun 1998 21:20:24 -0400 (EDT) Received: by janus.tor.securecomputing.com id <11651>; Tue, 9 Jun 1998 21:25:47 -0400 Message-Id: <98Jun9.212547edt.11651@janus.tor.securecomputing.com> To: Nariyasu Hirata cc: Vernon Schryver , ietf-rip@BayNetworks.COM Subject: Re: Auth Data Length References: <199806091339.HAA17178@calcite.rhyolite.com> <357DDA09.37C76A20@in.hitachi-it.co.jp> In-reply-to: hirata's message of "Tue, 09 Jun 1998 20:57:45 -0400". <357DDA09.37C76A20@in.hitachi-it.co.jp> From: "C. Harald Koch" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <17687.897441899.1@gamera.tornd.securecomputing.com> Date: Tue, 9 Jun 1998 21:24:59 -0400 Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk In message <357DDA09.37C76A20@in.hitachi-it.co.jp>, Nariyasu Hirata writes: > Alas, I had to say that one uses the value 20 instead. Sounds like SHA/SHA1; the digest output for that algorithm is 20 bytes instead of 16. Or it could be a bug. :-) -- Harald Koch "Madness takes its toll. Please have exact change." -Karen Murphy From owner-ietf-rip@BayNetworks.COM Tue Jun 9 21:52:27 1998 Delivery-Date: Tue, 09 Jun 1998 21:52:27 -0400 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from cnri.reston.va.us (ns.cnri.reston.va.us [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id VAA02803 for ; Tue, 9 Jun 1998 21:52:27 -0400 (EDT) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id VAA11753 for ; Tue, 9 Jun 1998 21:54:50 -0400 (EDT) Received: from mailhost.BayNetworks.COM (screen2r.BayNetworks.COM [134.177.3.1]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id SAA25841; Tue, 9 Jun 1998 18:41:51 -0700 (PDT) Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id SAA24021; Tue, 9 Jun 1998 18:42:44 -0700 (PDT) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id VAA11773; Tue, 9 Jun 1998 21:50:01 -0400 (EDT) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM ([134.177.1.109] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id VAA11769; Tue, 9 Jun 1998 21:49:55 -0400 (EDT) for Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id SAA23766 for ; Tue, 9 Jun 1998 18:39:33 -0700 (PDT) Received: from smtp-gw.BayNetworks.COM (ext-ns3.baynetworks.com [192.32.253.3]) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id VAA11763; Tue, 9 Jun 1998 21:49:18 -0400 (EDT) for Received: from hitiij.hitachi.co.jp (root@hitiij.hitachi.co.jp [133.145.224.3]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id VAA00174 for ; Tue, 9 Jun 1998 21:43:48 -0400 (EDT) Received: from naganuki.in.hitachi-it.co.jp by hitiij.hitachi.co.jp (8.8.8+2.7Wbeta7/3.6W-hitiij) id KAA17217; Wed, 10 Jun 1998 10:38:31 +0900 (JST) Received: from in.hitachi-it.co.jp ([202.16.25.82]) by naganuki.in.hitachi-it.co.jp (8.8.8/3.6W-naganuki) with ESMTP id KAA08458; Wed, 10 Jun 1998 10:41:33 +0900 (JST) Message-ID: <357DE400.F1AC9490@in.hitachi-it.co.jp> Date: Wed, 10 Jun 1998 10:40:16 +0900 From: Nariyasu Hirata X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: "C. Harald Koch" CC: Vernon Schryver , ietf-rip@BayNetworks.COM Subject: Re: Auth Data Length References: <199806091339.HAA17178@calcite.rhyolite.com> <357DDA09.37C76A20@in.hitachi-it.co.jp> <98Jun9.212547edt.11651@janus.tor.securecomputing.com> Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk C. Harald Koch wrote: > > In message <357DDA09.37C76A20@in.hitachi-it.co.jp>, Nariyasu Hirata writes: > > Alas, I had to say that one uses the value 20 instead. > > Sounds like SHA/SHA1; the digest output for that algorithm is 20 bytes instead > of 16. > > Or it could be a bug. :-) > Ignoring the authentication data length, they passed MD5 authentication. I do not think there happens accidental collisions of MD5 and SHA checksums. :-) - Hirata From owner-ietf-rip@BayNetworks.COM Tue Jun 30 09:51:55 1998 Delivery-Date: Tue, 30 Jun 1998 09:51:56 -0400 Return-Path: owner-ietf-rip@BayNetworks.COM Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id JAA14523 for ; Tue, 30 Jun 1998 09:51:55 -0400 (EDT) Received: from smtp-gw.BayNetworks.COM (ns2.BayNetworks.COM [134.177.3.16]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id JAA09533 for ; Tue, 30 Jun 1998 09:54:16 -0400 (EDT) Received: from mailhost.BayNetworks.COM ([132.245.135.115]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id GAA01660; Tue, 30 Jun 1998 06:39:49 -0700 (PDT) Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id JAA01015; Tue, 30 Jun 1998 09:39:40 -0400 (EDT) Received: (from major@localhost) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) id JAA01961; Tue, 30 Jun 1998 09:46:49 -0400 (EDT) for ietf-rip-outgoing X-Authentication-Warning: majordomo.BayNetworks.COM: major set sender to owner-ietf-rip@majordomo using -f Received: from mailhost.BayNetworks.COM (h016d.s86b1.BayNetworks.COM [134.177.1.109] (may be forged)) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id JAA01957; Tue, 30 Jun 1998 09:46:42 -0400 (EDT) for Received: from majordomo.BayNetworks.COM ([192.32.253.10]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id GAA28487 for ; Tue, 30 Jun 1998 06:38:09 -0700 (PDT) Received: from smtp-gw.BayNetworks.COM (ns4.BayNetworks.COM [192.32.253.7]) by majordomo.BayNetworks.COM (8.8.6/BNET-SVR4) with ESMTP id JAA01953; Tue, 30 Jun 1998 09:46:09 -0400 (EDT) for Received: from atlas.xylogics.com (fw1-int.corpeast.baynetworks.com [132.245.139.1]) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id JAA21712 for ; Tue, 30 Jun 1998 09:38:09 -0400 (EDT) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by atlas.xylogics.com (8.7.3/8.7.3) with ESMTP id JAA10006 for ; Tue, 30 Jun 1998 09:36:28 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id JAA14204; Tue, 30 Jun 1998 09:37:35 -0400 (EDT) Message-Id: <199806301337.JAA14204@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ietf-rip@xylogics.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-ripv2-protocol-v2-05.txt Date: Tue, 30 Jun 1998 09:37:29 -0400 Sender: owner-ietf-rip@BayNetworks.COM Precedence: bulk --NextPart Note: This revision reflects comments received during the last call period. A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the RIP Version II Working Group of the IETF. Title : RIP Version 2 Carrying Additional Information Author(s) : G. Malkin Filename : draft-ietf-ripv2-protocol-v2-05.txt Pages : 37 Date : 29-Jun-98 This document specifies an extension of the Routing Information Protocol (RIP), as defined in [1], to expand the amount of useful information carried in RIP messages and to add a measure of security. A companion document will define the SNMP MIB objects for RIP-2 [2]. An additional document will define cryptographic security improvements for RIP-2 [3]. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ripv2-protocol-v2-05.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ripv2-protocol-v2-05.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ripv2-protocol-v2-05.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980629172900.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ripv2-protocol-v2-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ripv2-protocol-v2-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980629172900.I-D@ietf.org> --OtherAccess-- --NextPart-- From adm Tue Jun 30 10:46:50 1998 Delivery-Date: Tue, 30 Jun 1998 11:04:22 -0400 Return-Path: adm Received: (from adm@localhost) by ietf.org (8.8.5/8.8.7a) id KAA15842 for ietf-123-outbound.10@ietf.org; Tue, 30 Jun 1998 10:45:03 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id JAA14204; Tue, 30 Jun 1998 09:37:35 -0400 (EDT) Message-Id: <199806301337.JAA14204@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ietf-rip@xylogics.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-ripv2-protocol-v2-05.txt Date: Tue, 30 Jun 1998 09:37:29 -0400 Sender: cclark@ns.cnri.reston.va.us --NextPart Note: This revision reflects comments received during the last call period. A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the RIP Version II Working Group of the IETF. Title : RIP Version 2 Carrying Additional Information Author(s) : G. Malkin Filename : draft-ietf-ripv2-protocol-v2-05.txt Pages : 37 Date : 29-Jun-98 This document specifies an extension of the Routing Information Protocol (RIP), as defined in [1], to expand the amount of useful information carried in RIP messages and to add a measure of security. A companion document will define the SNMP MIB objects for RIP-2 [2]. An additional document will define cryptographic security improvements for RIP-2 [3]. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ripv2-protocol-v2-05.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-ripv2-protocol-v2-05.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ripv2-protocol-v2-05.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980629172900.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ripv2-protocol-v2-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ripv2-protocol-v2-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980629172900.I-D@ietf.org> --OtherAccess-- --NextPart--