IETF Logo Mail Archive

Re: Review of: Characterization of Proposed Standards

Dave Crocker <dhc@dcrocker.net> Sat, 02 November 2013 22:45 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8679E21E8118 for <ietf@ietfa.amsl.com>; Sat, 2 Nov 2013 15:45:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aBHhfT38YbEO for <ietf@ietfa.amsl.com>; Sat, 2 Nov 2013 15:45:21 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1E55221E8114 for <ietf@ietf.org>; Sat, 2 Nov 2013 15:45:17 -0700 (PDT)
Received: from [10.105.7.29] ([70.42.240.24]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id rA2MioEB032629 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 2 Nov 2013 15:45:07 -0700
Message-ID: <5275804D.9050200@dcrocker.net>
Date: Sat, 02 Nov 2013 15:44:29 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>, Dave Crocker <dcrocker@bbiw.net>
Subject: Re: Review of: Characterization of Proposed Standards
References: <5269209F.3060706@dcrocker.net> <B4B31C25-C472-41B3-AAF8-96670E0E243F@NLnetLabs.nl> <52729C1D.7010400@dcrocker.net> <CAC4RtVCewEKatJKJnBbCqgsuBjHCOHY49WoTx+y-K_zDt+Smxg@mail.gmail.com> <40AFC5D09A1926489ECFED9D7633D98A20045B@ESESSMB307.ericsson.se> <CALaySJJ_o=YTgmzsUmJRWfNwH1-5DnhyKF_xDXa8nKQ=5_-jRQ@mail.gmail.com> <CALaySJKC+hP5SRn5-Euh7ugjRB-iQU5Wd090PKh-W+F8Y7adxQ@mail.gmail.com> <CALaySJJkbjCd9M=b_gZEGk9Y3nA1KH3hFoi45Sr1Z5=UFg5HgA@mail.gmail.com> <52757BC3.9020100@dcrocker.net> <CALaySJKJUVJP3Z-TtS2Yc+9-14L1LX7c5=ZnP4wUf27fvhVnXw@mail.gmail.com>
In-Reply-To: <CALaySJKJUVJP3Z-TtS2Yc+9-14L1LX7c5=ZnP4wUf27fvhVnXw@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sat, 02 Nov 2013 15:45:09 -0700 (PDT)
Cc: "<draft-kolkman-proposed-standards-clarified.all@tools.ietf.org>" <draft-kolkman-proposed-standards-clarified.all@tools.ietf.org>, IETF Discussion <ietf@ietf.org>, Jari Arkko <jari.arkko@ericsson.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Nov 2013 22:45:26 -0000

On 11/2/2013 3:28 PM, Barry Leiba wrote:
>>> Oh, and, of course, if we use my suggestion below, this document will
>>> have to "update" 6410 as well as 2026.
>>
>> It will "obsolete" both 6410 and 2026.  It's replacing them.
>
> No, I don't think so.  It's replacing specific sections of them, but
> not the whole documents.  I think we'd have a very hard time getting
> consensus on a full replacement of 2026.


sorry,  I clearly misunderstood what was being proposed.I'd like to 
blame it on Amtrak's impressive jossling of me today, but I suspect the 
flaws is genetic.

As nearly as I can tell, now, what's meant is to replace 6410 with the 
new document.  Please, please, please don't tell me that /portions/ of 
6410 are being replaced.

In any event, I've missed the logic for "updating", "replacing" or 
whatever 6410, if all of this isn't just being merged into 2026bis.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email