Re: SDRP working group

Deborah Estrin <> Wed, 18 November 1992 05:25 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa04858; 18 Nov 92 0:25 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa04854; 18 Nov 92 0:25 EST
Received: from PIZZA.BBN.COM by CNRI.Reston.VA.US id aa22861; 18 Nov 92 0:25 EST
Received: from pizza by PIZZA.BBN.COM id aa21837; 18 Nov 92 0:20 EST
Received: from BBN.COM by PIZZA.BBN.COM id aa21831; 18 Nov 92 0:18 EST
Received: from by BBN.COM id aa10339; 18 Nov 92 0:17 EST
Received: from by (5.64+/SMI-3.0DEV3-USC+2.3) id AA16342; Tue, 17 Nov 92 21:16:53 PST
Received: by (4.1/SMI-3.0DEV3-ucs+1.1) id AA26569; Tue, 17 Nov 92 21:16:49 PST
Date: Tue, 17 Nov 92 21:16:49 PST
Message-Id: <>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Deborah Estrin <>
In-Reply-To: Noel Chiappa's message of Tue, 17 Nov 92 16:45:30 -0500 <>
Subject: Re: SDRP working group

SDRP is a complete routing architecutre (well a piece of one). So far
we have only specified in detail one version of one part of that
architecture. We have ideas and sketches on the other parts but I dont
think any of us have said that we have all parts fully specified.

We do have some concrete suggestions for ways to begin on the other
parts of the routing protocol. These would be "version 1" of the other
parts of routing. Just like what we have now is version 1 of the
packet forwarding.

Noel, I did NOT say that the overal protocol should be called SDFP. I
said that the spec that we put out should be called the Packet
Forwarding and Control Message Specification.... Minor details...but
who can pronounce SDFP anyway...:}