Re: SDRP working group

Noel Chiappa <> Tue, 17 November 1992 22:07 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa03114; 17 Nov 92 17:07 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa03110; 17 Nov 92 17:07 EST
Received: from PIZZA.BBN.COM by CNRI.Reston.VA.US id aa15621; 17 Nov 92 17:06 EST
Received: from pizza by PIZZA.BBN.COM id aa18570; 17 Nov 92 16:54 EST
Received: from BBN.COM by PIZZA.BBN.COM id aa18566; 17 Nov 92 16:52 EST
Received: from GINGER.LCS.MIT.EDU by BBN.COM id aa05521; 17 Nov 92 16:51 EST
Received: by id AA07839; Tue, 17 Nov 92 16:51:29 -0500
Date: Tue, 17 Nov 92 16:51:29 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Noel Chiappa <>
Message-Id: <>
Subject: Re: SDRP working group

    If SDRP is going to be developed as a source routing protocol as
    charter (and you also) suggests, does that mean IDPR is 

Huh? What on earth lead you to this conclusion? IDPR is a very diferent beast
(for one thing, it's a real routing protocol) using a different model of how
to do the source routing (with flow setup), and the prime contractor (BBN) is
not working on Unified (i.e. SDRP) at all. IDPR work is going forward; my
understanding is they are getting ready to do a signficant field trial using
the completed implementastions of the IDPR Routing Protocol.