IETF Logo Mail Archive

Re: Next steps: IPv6 core specifications to Internet Standard.

Fernando Gont <fgont@si6networks.com> Mon, 23 May 2016 15:54 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0094112D128 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:54:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 9u-IZzJACIb2 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:54:10 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC52512D0AA for <ipv6@ietf.org>; Mon, 23 May 2016 08:54:09 -0700 (PDT)
Received: from [192.168.3.104] (192-174-17-190.fibertel.com.ar [190.17.174.192]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id BF2FD80616; Mon, 23 May 2016 17:54:03 +0200 (CEST)
Subject: Re: Next steps: IPv6 core specifications to Internet Standard.
To: otroan@employees.org, 6man WG <ipv6@ietf.org>
References: <025B4B8D-E3B0-450D-9519-6D5D14B8ABC1@employees.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <57432795.4070602@si6networks.com>
Date: Mon, 23 May 2016 11:53:57 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <025B4B8D-E3B0-450D-9519-6D5D14B8ABC1@employees.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/cxm-gDQ5NqNRQOSxjBzpNN-ZCf4>
Cc: 6man-chairs@tools.ietf.org, int-ads@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 May 2016 15:54:11 -0000

Ole,

On 05/23/2016 07:17 AM, otroan@employees.org wrote:
>
> As we’re finishing the edits on the RFC2460bis, RFC1981bis and
> RFC4291bis, we will initiate working group last calls with the
> intended status of Internet Standard. We will do a single last call
> for the updated documents (RFC2460, RFC4291, RFC1981) and a separate
> working group last call for the unchanged documents (RFC3596,
> RFC4443, RFC4941).

After reading RFC4941, it looks like it really needs to be updated, and
also that if one were to publish RFC4941 in 2016, a fair share of text
would be edited.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

v2.23.0 | Report a Bug | By Email