On publishing new revisions of drafts when transitioning to BESS
Martin Vigoureux <martin.vigoureux@alcatel-lucent.com> Fri, 24 October 2014 20:41 UTC
Return-Path: <martin.vigoureux@alcatel-lucent.com>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43F241A8F38; Fri, 24 Oct 2014 13:41:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7p-y288b_BRk; Fri, 24 Oct 2014 13:40:58 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A845C1A8BAF; Fri, 24 Oct 2014 13:40:58 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id 5C78E7646DCE7; Fri, 24 Oct 2014 20:40:53 +0000 (GMT)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s9OKeuTA023700 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 24 Oct 2014 22:40:56 +0200
Received: from [135.244.224.4] (135.239.27.40) by FR712WXCHHUB03.zeu.alcatel-lucent.com (135.239.2.74) with Microsoft SMTP Server (TLS) id 14.3.195.1; Fri, 24 Oct 2014 22:40:56 +0200
Message-ID: <544AB951.8090909@alcatel-lucent.com>
Date: Fri, 24 Oct 2014 22:40:49 +0200
From: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "bess@ietf.org" <bess@ietf.org>
Subject: On publishing new revisions of drafts when transitioning to BESS
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [135.239.27.40]
Archived-At: http://mailarchive.ietf.org/arch/msg/l3vpn/g5al4wo5cigDpNb1UVfl1YtsN-4
Cc: l2vpn@ietf.org, L3VPN <l3vpn@ietf.org>
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn/>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Oct 2014 20:41:00 -0000
Authors, we have received questions from some of you on how to handle the submission of new revisions of your drafts that fall in the scope of BESS. The procedure is quite simple: Please submit those as either draft-ietf-bess-foo-00 if your document is already a WG document, or as draft-<individual>-bess-foo-00 if it is not. In short, when transitioning to BESS, revision number has to be reset to 00. We will then request the secretariat to mark the old document as replaced by the new one in order to keep the history and maintain the link. For the specific case of documents being polled for adoption it shall be possible to directly move from draft-<individual>-<wgname>-foo-xx to draft-ietf-bess-foo-00 Thank you M&T
- On publishing new revisions of drafts when transi… Martin Vigoureux