Re: Comments on draft-carpenter-newtrk-questions-00.txt

Douglas Otis <dotis@mail-abuse.org> Thu, 13 July 2006 22:06 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G19KG-0004P7-Sp; Thu, 13 Jul 2006 18:06:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G19KF-0004P1-3z for ietf@ietf.org; Thu, 13 Jul 2006 18:06:27 -0400
Received: from b.mail.sonic.net ([64.142.19.5]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G19KD-0006XK-Mx for ietf@ietf.org; Thu, 13 Jul 2006 18:06:27 -0400
Received: from [132.219.21.213] (h15d5-net84db.lab.risq.net [132.219.21.213] (may be forged)) (authenticated bits=0) by b.mail.sonic.net (8.13.8.Beta0/8.13.7) with ESMTP id k6DM6D4K030933 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Thu, 13 Jul 2006 15:06:20 -0700
In-Reply-To: <44B69E1B.5050309@cisco.com>
References: <p06300025c0db326985f9@[142.131.134.210]> <2278C088-133C-4353-9CF1-AC47899ED409@cisco.com> <44B5EC23.6090303@cisco.com> <44B69AFF.3020504@att.com> <44B69E1B.5050309@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <D2EE5E18-60AA-4612-8FA5-E9E202353D3A@mail-abuse.org>
Content-Transfer-Encoding: 7bit
From: Douglas Otis <dotis@mail-abuse.org>
Date: Thu, 13 Jul 2006 18:06:04 -0400
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: Tony Hansen <tony@att.com>, ietf@ietf.org
Subject: Re: Comments on draft-carpenter-newtrk-questions-00.txt
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

On Jul 13, 2006, at 3:25 PM, Eliot Lear wrote:

> We are in this position because we are not today documenting  
> existing practice, having not properly understood the lack of  
> desire to do what you class as "minor amount of work".

The SRD approach generates Name.Serial references to sets of  
documents after expending a "minor amount of work."  This minor  
effort reduces other efforts expected of the RFC editor, IESG, IETF  
WGs, and of those attempting to compile useful references.  When  
other standard bodies want to coordinate IETF changing references,  
Name.Serial makes predicting future references simple.  These stable  
and recognizable references should assist someone wanting to specify  
a level of compliance by picking the Serial number.  These references  
will likely be viewed as either Current or Stable by the community,  
rather than less meaningful Draft-Standard, Proposed-Standard, etc.   
When joined together in sets, the status of individual RFCs become  
far less relevant.  Once Serial.Name is instantiated, outmoded  
unsupported designators could be themselves made historic. : )

> If the work truly is minor, then again I have no problem with this  
> approach, as it's actually a two step approach that hides behind  
> the word Historic.  But let us not get ourselves into a position  
> where we're marking widely used specs Historic left and right  
> simply because we couldn't get someone to jump through hoops.
>
> And I think we're at the point where I'm violating my own rule.   
> There is no concrete proposal here that I can argue in favor of or  
> oppose, so I think I'd better shut up and wait for one.

I think there was general consensus for going forward with the SRD  
draft in Paris.  It is hard to understand who's oxen was being gored,  
and why the newtrk group failed to move forward, but the view that  
this represents additional effort is greatly mistaken.  When seen in  
the larger picture, this approach represents a significant reduction  
in efforts expended by all involved.

-Doug


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf