Re: IDPR as a Proposed Standard

Deborah Estrin <estrin@usc.edu> Mon, 13 April 1992 18:42 UTC

Received: from nri.nri.reston.va.us by ietf.NRI.Reston.VA.US id aa03875; 13 Apr 92 14:42 EDT
Received: from nri.reston.va.us by NRI.Reston.VA.US id aa13241; 13 Apr 92 14:45 EDT
Received: from PARK-STREET.BBN.COM by NRI.Reston.VA.US id aa13235; 13 Apr 92 14:45 EDT
Received: from park-street by PARK-STREET.bbn.COM id aa00126; 13 Apr 92 14:18 EDT
Received: from BBN.COM by PARK-STREET.BBN.COM id aa00120; 13 Apr 92 14:16 EDT
Received: from usc.edu by BBN.COM id aa26220; 13 Apr 92 14:20 EDT
Received: from excalibur.usc.edu by usc.edu (5.64+/SMI-3.0DEV3) id AA01036; Mon, 13 Apr 92 11:20:11 PDT
Received: by excalibur.usc.edu (4.1/SMI-3.0DEV3) id AA28997; Mon, 13 Apr 92 11:24:03 PDT
Date: Mon, 13 Apr 92 11:24:03 PDT
Message-Id: <9204131824.AA28997@excalibur.usc.edu>
From: Deborah Estrin <estrin@usc.edu>
Sender: estrin@jerico.usc.edu
To: yakov@watson.ibm.com
Cc: idpr-wg@bbn.com
In-Reply-To: yakov@watson.ibm.com's message of Mon, 13 Apr 92 07:53:48 EDT <9204131155.AA16019@usc.edu>
Subject: Re: IDPR as a Proposed Standard
Reply-To: estrin@usc.edu

OK. I think this is largely a communication problem. I interpreted
your remarks in terms of source-demand routing in general, not IDPR in
particular. It sounded to me as if you were arguing that working on a
source-specific routing mechanism was not justified, whereas I thought
we had justified that in several documents. (And maybe I was not the
only one who misinterpreted your comments this way ?)

Now I see (Think) that you are saying you do see the need for this but
have questions about IDPR as an instatiation of it.

If that is the case, and if you are calling for  careful round of
analyzing a design for "version 2 IDPR" or whatever we want to call
it, then I think I agree with you. 

Sorry if I flamed unnecessarily....I thought I was jsut being
"defensive" but now you tell me that there was no "offense" intended :}