Re: minutes of RIPv2 meeting in Amsterdam

Gerry Meyer <gerry@spider.co.uk> Tue, 20 July 1993 14:39 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04584; 20 Jul 93 10:39 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa04580; 20 Jul 93 10:39 EDT
Received: from atlas.xylogics.com by CNRI.Reston.VA.US id aa08720; 20 Jul 93 10:39 EDT
Received: by atlas.xylogics.com id AA26233 (5.65c/UK-2.1-930202); Tue, 20 Jul 1993 10:37:10 -0400
Received: from ben.uknet.ac.uk by atlas.xylogics.com with SMTP id AA13237 (5.65c/UK-2.1-930202); Tue, 20 Jul 1993 10:36:57 -0400
Received: from castle.ed.ac.uk by ben.uknet.ac.uk via JANET with NIFTP (PP) id <sg.12666-0@ben.uknet.ac.uk>; Tue, 20 Jul 1993 15:34:31 +0100
Received: from spider.co.uk by castle.ed.ac.uk id aa11789; 20 Jul 93 15:34 WET DST
Received: by widow.spider.co.uk; Tue, 20 Jul 93 15:41:21 +0100
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Gerry Meyer <gerry@spider.co.uk>
Date: Tue, 20 Jul 93 15:30:24 +0100
Message-Id: <9142.9307201430@orbweb.spider.co.uk>
Received: by orbweb.spider.co.uk; Tue, 20 Jul 93 15:30:24 +0100
To: ariel@process.com, ietf-rip@xylogics.com
Subject: Re: minutes of RIPv2 meeting in Amsterdam
Cc: gerry@spider.co.uk

>Gerry Meyer's Demand Routing proposal was discussed at length.  It was
>agreed that it performed a useful function.  However, Robert Ullman
>pointed out that it simulated many of the functions of TCP and that RAP
>used TCP.  Robert and Gerry will continue the discussion after Gerry
>has had an opportunity to read the RAP RFC.  The slides from Gerry's
>presentation are included in these Proceedings.

Like all other current routing protocols, RAP (experimental RFC 1476)
currently does not address the problem of running a routing protocol on
a switched network.  It is also IP-specific in its current form.
I feel RAP is a red-herring in this discussion.

The real issue is what is the most appropriate method to operate on demand
circuits with RIP protocol variants (IP, Novell, Apple etc):

(a) an appropriate unreliable service (UDP-IP, IPX etc) which is what we
    currently use and is proposed in the Internet Draft.

(b) over a single reliable transport (TCP, encapsulating Novell RIP etc),

(c) the 'appropriate' reliable transport (TCP for IP, NCP or SPX for Novell
    etc).

I think the 'best' method depends on where you are coming from.  I rule
out (c) immediately as requiring transports not otherwise required in a
multi-protocol router.

How I intend to proceed is to sketch through case (b) for myself to see
what functionality it can provide.   I will then mail a list of pros and
cons for the two methods for a discussion on the mailing list.

    Gerry