Re: [Tools-discuss] On the "replaced by / replaces" status of drafts ...

Martin Vigoureux <martin.vigoureux@alcatel-lucent.com> Fri, 03 August 2012 00:25 UTC

Return-Path: <martin.vigoureux@alcatel-lucent.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3A1C11E8087 for <tools-discuss@ietfa.amsl.com>; Thu, 2 Aug 2012 17:25:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.543
X-Spam-Level:
X-Spam-Status: No, score=-109.543 tagged_above=-999 required=5 tests=[AWL=-0.586, BAYES_00=-2.599, HELO_EQ_FR=0.35, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 s+H+fhE-3L1I for <tools-discuss@ietfa.amsl.com>; Thu, 2 Aug 2012 17:25:40 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by ietfa.amsl.com (Postfix) with ESMTP id B3E9321E8037 for <tools-discuss@ietf.org>; Thu, 2 Aug 2012 17:25:39 -0700 (PDT)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q730PbsO021151 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <tools-discuss@ietf.org>; Fri, 3 Aug 2012 02:25:37 +0200
Received: from US70TWXCHHUB04.zam.alcatel-lucent.com (135.5.2.36) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (135.120.45.64) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 3 Aug 2012 02:25:36 +0200
Received: from [135.244.36.21] (135.5.27.11) by US70TWXCHHUB04.zam.alcatel-lucent.com (135.5.2.36) with Microsoft SMTP Server (TLS) id 14.2.247.3; Thu, 2 Aug 2012 20:25:32 -0400
Message-ID: <501B1A79.2010803@alcatel-lucent.com>
Date: Fri, 03 Aug 2012 02:25:29 +0200
From: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
CC: "tools-discuss@ietf.org" <tools-discuss@ietf.org>
References: <501AC332.90604@alcatel-lucent.com>
In-Reply-To: <501AC332.90604@alcatel-lucent.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [135.5.27.11]
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.84
Subject: Re: [Tools-discuss] On the "replaced by / replaces" status of drafts ...
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tools-discuss>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Aug 2012 00:25:40 -0000

sorry, I got mixed up on two draft names

> In relation to the replacement topic, yet not directly linked:
> http://tools.ietf.org/wg/mpls shows a long list of documents (Related
> Active Documents) but a good proportion of them have in fact expired a
> (very) long time ago.
> I noticed that all of the expired documents in that list are documents
> which carry the same name than a working group document (except for the
> prefix draft-ietf/draft-myname). This seems to be the reason for them
> appearing in that list, regardless of any replacement status.
> The glitch that leads me to that conclusion is the presence of
> draft-liu-mpls-tp-ring-protection in the list.
> This document has expired and is not replaced by any WG document.
> It is draft-weingarten-mpls-tp-linear-protection which is replaced by
> draft-ietf-mpls-tp-linear-protection, and this is correctly shown.

please read draft-weingarten-mpls-tp-ring-protection and 
draft-ietf-mpls-tp-ring-protection instead.