Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ucbvax!SRI-NIC.ARPA!tcp-ip-RELAY From: tcp-ip-RELAY@SRI-NIC.ARPA.UUCP Newsgroups: comp.protocols.tcp-ip Subject: (none) Message-ID: <8711251056.AA13801@umix.cc.umich.edu> Date: Tue, 24-Nov-87 10:25:00 EST Article-I.D.: umix.8711251056.AA13801 Posted: Tue Nov 24 10:25:00 1987 Date-Received: Sun, 29-Nov-87 04:40:55 EST Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 21 , userID=DUM1%SFU.BITNET@umix.cc.umich.edu, My_Hangout%SFU.BITNET@umix.cc.umich.edu, Userid=Q73X%UBC.Mailnet@umix.c Date: Tue, 24 Nov 87 07:25:00 PST To: userID=DUM1@SFU.MAILNET, userID=DUM1%SFU.BITNET@UMIX.CC.UMICH.EDU, My_Hangout%SFU.BITNET@UMIX.CC.UMICH.EDU, Userid= CERF@A.ISI.EDU, oconnor@SCCGATE.SCC.COM, tcp-ip@SRI-NIC.ARPA Subject: Re: Idle chatter about reference models 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