Re: Revised 6MAN Charter

Tim Chown <tjc@ecs.soton.ac.uk> Mon, 20 August 2007 13:08 UTC

Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IN6zI-0002wp-FM; Mon, 20 Aug 2007 09:08:08 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IN6zG-0002vA-St for ipv6@ietf.org; Mon, 20 Aug 2007 09:08:06 -0400
Received: from owl.ecs.soton.ac.uk ([152.78.68.129]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IN6zG-00072d-C7 for ipv6@ietf.org; Mon, 20 Aug 2007 09:08:06 -0400
X-ECS-MailScanner-Watermark: 1188220081.20108@CkEgZf7aJR73qoFeCw7bvg
Received: from goose.ecs.soton.ac.uk (goose.ecs.soton.ac.uk [152.78.68.131]) by owl.ecs.soton.ac.uk (8.13.1/8.13.1) with ESMTP id l7KD7xEd017436 for <ipv6@ietf.org>; Mon, 20 Aug 2007 14:08:00 +0100
X-ECS-MailScanner-Watermark: 1188220057.24107@lFqOcFdz+UlmLNES6ajILw
Received: from login.ecs.soton.ac.uk (login.ecs.soton.ac.uk [152.78.68.189]) by goose.ecs.soton.ac.uk (8.13.1/8.13.1) with ESMTP id l7KD7YGA017249 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ipv6@ietf.org>; Mon, 20 Aug 2007 14:07:36 +0100
Received: from login.ecs.soton.ac.uk (localhost.localdomain [127.0.0.1]) by login.ecs.soton.ac.uk (8.13.8/8.11.6) with ESMTP id l7KD7oXj012982 for <ipv6@ietf.org>; Mon, 20 Aug 2007 14:07:50 +0100
Received: (from tjc@localhost) by login.ecs.soton.ac.uk (8.13.8/8.13.8/Submit) id l7KD7mEm012981 for ipv6@ietf.org; Mon, 20 Aug 2007 14:07:48 +0100
Date: Mon, 20 Aug 2007 14:07:48 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: IPv6 WG <ipv6@ietf.org>
Message-ID: <20070820130748.GH9879@login.ecs.soton.ac.uk>
Mail-Followup-To: IPv6 WG <ipv6@ietf.org>
References: <46C4288A.1060408@innovationslab.net> <20070820105429.GB9879@login.ecs.soton.ac.uk> <46C9888E.5050705@piuha.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <46C9888E.5050705@piuha.net>
User-Agent: Mutt/1.4.2.2i
X-ECS-MailScanner: Found to be clean, Found to be clean
X-Spam-Status: No
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Subject: Re: Revised 6MAN Charter
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Mon, Aug 20, 2007 at 03:26:54PM +0300, Jari Arkko wrote:
> 
> > Also, could the cahirs confirm the final status of the existing eight WG
> > drafts as listed at:
> > http://www.ietf.org/html.charters/ipv6-charter.html
> >
> > Four of these aren't mentioned in the revised charter; are they
> > expected to complete before 6MAN forms?
> >   
> 
> http://tools.ietf.org/wg/ipv6/ gives the status of the various items.
> Basically, anything that is RFC Editor's queue need not be
> listed any more. Some rechartering efforts have ignored
> documents in IESG Processing stage too, because it can be
> assumed that the documents get approved before the charter.

Thanks Jari, in which case all looks well... the RFC Editor Queue drafts
were not mentioned, but as you say these should be approved before 6MAN
becomes active.

RFC-Editor's Queue:
draft-ietf-ipv6-2461bis-11
draft-ietf-ipv6-over-ppp-v2-03
draft-ietf-ipv6-privacy-addrs-v2-05
draft-ietf-ipv6-rfc2462bis-08

-- 
Tim

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------