Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!ukma!nrl-cmf!ames!ucbcad!ucbvax!SRI-NIC.ARPA!tcp-ip-RELAY
From: tcp-ip-RELAY@SRI-NIC.ARPA ("tcp-ip-RELAY%SRI-NIC.ARPA")
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Idle chatter about reference models
Message-ID: <8711250610.AA15736@ucbvax.Berkeley.EDU>
Date: Tue, 24-Nov-87 10:25:00 EST
Article-I.D.: ucbvax.8711250610.AA15736
Posted: Tue Nov 24 10:25:00 1987
Date-Received: Sat, 28-Nov-87 10:58:32 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 14

Vint,

Couldn't GGP and EGP be viewed as application (or management or
somesuch) protocols that just happen to have transport functionality
built into them?  Using  such a view in Mike's diagram,
GGP/EGP might be vertical rectangles that spanned several of the
corresponding layers in the ISO model.

My own favorite is to view them as management protocols
of the IP layer (that happen to provide their own transport).
After all, their purpose is to update an IP MIB (that's ISOese
for routing table).

Phill