IDPR as a Proposed Standard

yakov@watson.ibm.com Thu, 30 April 1992 20:09 UTC

Received: from nri.nri.reston.va.us by ietf.NRI.Reston.VA.US id aa03611; 30 Apr 92 16:09 EDT
Received: from nri.reston.va.us by NRI.Reston.VA.US id aa07593; 30 Apr 92 16:14 EDT
Received: from PARK-STREET.BBN.COM by NRI.Reston.VA.US id aa07581; 30 Apr 92 16:14 EDT
Received: from park-street by PARK-STREET.bbn.COM id aa02471; 30 Apr 92 15:46 EDT
Received: from BBN.COM by PARK-STREET.BBN.COM id aa02467; 30 Apr 92 15:44 EDT
Received: from watson.ibm.com by BBN.COM id aa26987; 30 Apr 92 15:43 EDT
Received: from yktvmz.watson.ibm.com by watson.ibm.com (IBM VM SMTP V2R2) with BSMTP id 1844; Thu, 30 Apr 92 15:43:40 EDT
Date: Thu, 30 Apr 92 15:41:11 EDT
From: yakov@watson.ibm.com
To: jnc@ginger.lcs.mit.edu
Cc: iab@isi.edu, iesg@isi.edu, idpr-wg@bbn.com, hinden@sun.com
Subject: IDPR as a Proposed Standard
Message-ID: <9204301614.aa07581@NRI.Reston.VA.US>

>	As to how long the various drafts have been around, I got the
>impression from your message that the Architecture document had only recently
>appeared. This confused me, since I thought I recalled seeing this some time
>ago. I found the following in my file system:
>
>  65 -rw-r-----  1 jnc         65965 Jul 25  1991 /u/jnc/docs/idpr_arch.id
>
>I don't know where I got it, but the .id ending seems to indicate it's an I-D.
>True, the *latest* version may have only gone up recently, but the basic
>document has been around for a while. I reviewed the table of contents of this
>and the latest version, and they appear very similar (although the latest
>version has more comparitive material with DV algorithms). (The new version
>is about 7K characters longer.)

Here is posting to the IETF mailing list that I hope would help to clarify
the confusion (as you see, it is dated April 16):

		---------------------------------------------------------------------------
    Received: from venera.isi.edu by watson.ibm.com (IBM VM SMTP V2R2) with TCP;
       Thu, 16 Apr 92 16:18:52 EDT
    Received: by venera.isi.edu (5.65c/5.65+local-4)
    	id <AA01450>; Thu, 16 Apr 1992 07:53:49 -0700
    Received: from NRI.RESTON.VA.US by venera.isi.edu (5.65c/5.65+local-4)
    	id <AA01443>; Thu, 16 Apr 1992 07:53:45 -0700
    Received: from NRI.NRI.Reston.Va.US by NRI.Reston.VA.US id aa06927;
              16 Apr 92 10:24 EDT
    To: IETF <ietf@ISI.EDU>
    From: Internet-Drafts@NRI.Reston.VA.US
    Reply-To: Internet-Drafts@NRI.Reston.VA.US
    Subject: ID ACTION:draft-ietf-idpr-architecture-04.txt, .ps
    Date: Thu, 16 Apr 92 10:24:48 -0400
    Sender: cclark@NRI.Reston.VA.US
    Message-Id:  <9204161024.aa06927@NRI.Reston.VA.US>


    A Revised Internet Draft is available from the on-line Internet-Drafts
    directories. This draft is a work item of the
    Inter-Domain Policy Routing Working Group of the IETF.

           Title     : An Architecture for Inter-Domain Policy Routing
           Author(s) : Marianne Lepp, Martha Steenstrup
           Filename  : draft-ietf-idpr-architecture-04.txt, .ps
           Pages     : 30
		---------------------------------------------------------------------------

As you correctly pointed out, the new version is different from
the previous one. I don't think that comparing the table of contents
is that indicative of the differences, but just the difference
sizes (as you pointed out 7 K characters)  should give you a hint
about the possible scope of differences.

>	I can't speak to the manner in which it was prepared, though, and
>would like to see a reply on this issue.

Here are the facts related to how it was prepared:

	1) It was posted as an Internet Draft WITHOUT any prior
		 review by the working group.
  2) Specifically, it WAS NOT posted to the WG mailing list prior
	   to its appearance as an Internet Draft.
  3) It appears as an Internet Draft with no advance notice to the WG.

>	I fail to see that the fact that several WG members do not agree with
>the actions taken means much. In every WG, there are one or more members who
>do not agree with actions taken by the WG. This does not invalidate the
>decisions of the WG. How is this case any different?  Do a majority of the WG
>members who were actually involved in the development of the protocol disagree
>with these actions? If we are to discard the results of any WG which has a few
>members who do not agree with those results, we might as well fold up shop and
>go home.
>

	The issue is much more deeper that just "several WG members do not agree".
	The issue is that there are several key design issues in IDPR,
	where choices were made quite a while ago, and the choices
	turned out to be ill-justified from a technical point of view.
	
	Thus, moving IDPR in its present form along the standards track
	is likely to lead towards deployment of an immature protocol.
	As was pointed out by Tony Li "This is a hinderance due to its
	opportunity cost for the entire community". In view of these
	factors several members of the working group suggested to submit it
	now as an informational document and have one more round
	of reevaluation of some early made design decisions before
	submitting it to the IESG as a Proposed Standard. These
	suggestions were made by Deborah Estrin and Tony Li, and
 I can certainly support their position.


 Yakov  Rekhter