IDPR as a Proposed Standard

yakov@watson.ibm.com Thu, 16 April 1992 18:52 UTC

Received: from nri.nri.reston.va.us by ietf.NRI.Reston.VA.US id aa03343; 16 Apr 92 14:52 EDT
Received: from nri.reston.va.us by NRI.Reston.VA.US id aa21286; 16 Apr 92 14:56 EDT
Received: from PARK-STREET.BBN.COM by NRI.Reston.VA.US id aa21279; 16 Apr 92 14:56 EDT
Received: from park-street by PARK-STREET.bbn.COM id aa14206; 16 Apr 92 14:24 EDT
Received: from BBN.COM by PARK-STREET.BBN.COM id aa14202; 16 Apr 92 14:22 EDT
Received: from watson.ibm.com by BBN.COM id aa18528; 16 Apr 92 14:26 EDT
Received: from YKTVMV by watson.ibm.com (IBM VM SMTP V2R2) with BSMTP id 0599; Thu, 16 Apr 92 14:26:01 EDT
Date: Thu, 16 Apr 92 14:23:17 EDT
From: yakov@watson.ibm.com
To: iab@isi.edu, iesg@nri.reston.va.us
Cc: idpr-wg@bbn.com, jnc@ginger.lcs.mit.edu
Subject: IDPR as a Proposed Standard
Message-ID: <9204161456.aa21279@NRI.Reston.VA.US>

  Dear IAB and IESG members,

  I sincerely regret that Noel's message  brought you into the
  discussion about moving IDPR towards a Proposed Standard
  without proper briefing and enough background.

  However, given this, I feel obliged to point you to the following:

  1) Just because some of the design decisions "were made years ago"
     can not be used as a justification for saying that "it's too late
     to bring some of these up." This is especially true, if the
     design decision "were made without as much data as would have been
     desirable" as was asserted by Noel.

  2) Would IAB/IESG consider inability to obtain further funding,
     or any other funding related problems as a justification for moving
     a protocol towards a standardization ?

  3) It is certainly not correct that IDPR "was done in an open".
     IDPR design was originally done by the ORWG group that was
     CLOSED. At the time the group became open, all of the design
     decisions were already made. Several of you can certainly
     attest to this.

  Yakov Rekhter