Re: IPv6 updates & related RA-Guard document

Mohacsi Janos <mohacsi@niif.hu> Wed, 26 September 2012 14:43 UTC

Return-Path: <mohacsi@niif.hu>
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 8C5F821F86EC for <ipv6@ietfa.amsl.com>; Wed, 26 Sep 2012 07:43:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.446
X-Spam-Level:
X-Spam-Status: No, score=0.446 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HELO_EQ_HU=1.35, HOST_EQ_HU=1.245, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UvfBBSdUbEfJ for <ipv6@ietfa.amsl.com>; Wed, 26 Sep 2012 07:43:31 -0700 (PDT)
Received: from strudel.ki.iif.hu (strudel.ki.iif.hu [IPv6:2001:738:0:411:20f:1fff:fe6e:ec1e]) by ietfa.amsl.com (Postfix) with ESMTP id F35BB21F86E5 for <ipv6@ietf.org>; Wed, 26 Sep 2012 07:43:30 -0700 (PDT)
Received: from cirkusz.lvs.iif.hu (cirkusz.lvs.iif.hu [193.225.14.182]) by strudel.ki.iif.hu (Postfix) with ESMTP id 97240D0; Wed, 26 Sep 2012 16:43:29 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at cirkusz.lvs.iif.hu
Received: from strudel.ki.iif.hu ([IPv6:::ffff:193.6.222.244]) by cirkusz.lvs.iif.hu (cirkusz.lvs.iif.hu [::ffff:193.225.14.72]) (amavisd-new, port 10024) with ESMTP id JAQi688fwPeI; Wed, 26 Sep 2012 16:43:23 +0200 (CEST)
Received: by strudel.ki.iif.hu (Postfix, from userid 9002) id 129193BC; Wed, 26 Sep 2012 16:43:23 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by strudel.ki.iif.hu (Postfix) with ESMTP id 0993BD0; Wed, 26 Sep 2012 16:43:23 +0200 (CEST)
Date: Wed, 26 Sep 2012 16:43:23 +0200
From: Mohacsi Janos <mohacsi@niif.hu>
X-X-Sender: mohacsi@strudel.ki.iif.hu
To: RJ Atkinson <rja.lists@gmail.com>
Subject: Re: IPv6 updates & related RA-Guard document
In-Reply-To: <3AD20224-EBC3-463C-9433-4015BBC67EF9@gmail.com>
Message-ID: <alpine.DEB.2.00.1209261639420.22890@strudel.ki.iif.hu>
References: <09ABA7A7-8FDE-43AA-B2E6-C4C501995C53@gmail.com> <alpine.DEB.2.00.1209260938010.22890@strudel.ki.iif.hu> <3AD20224-EBC3-463C-9433-4015BBC67EF9@gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 26 Sep 2012 14:43:31 -0000

On Wed, 26 Sep 2012, RJ Atkinson wrote:

>
> On 26  Sep 2012, at 03:41 , Mohacsi Janos wrote:
>> RA-guard work mostly done at v6ops.
>> http://tools.ietf.org/html/draft-ietf-v6ops-ra-guard-08
>> http://tools.ietf.org/html/draft-ietf-v6ops-ra-guard-implementation-04
>>
>> Probably drafts should be circulated on v6ops mailing list
>> and have support from there.
>
> IETF v6ops WG Charter does not include updates to the
> IPv6 specifications.  Quoting from this WG Charter:
> 	"Specifying any protocols or transition
> 	mechanisms is out of scope of the WG."
>
> IETF 6MAN WG Charter DOES include updates to the
> IPv6 specifications, again quoting from this WG Charter:
> 	"The working group will address protocol limitations/issues
> 	discovered during deployment and operation."
>
> This is why the draft-*-ra-guard-* documents (quoted above)
> belong in the IETF v6ops WG, while the 2 different I-Ds
> that I mentioned belong here in the IETF 6MAN WG.
>
> Now, in practice, the 2 draft-ietf-6man-* I-Ds that I mentioned
> before already have been reviewed by many folks in v6ops,
> as part of examining the RA Guard documents, and I believe
> there is broad support for these updates within v6ops.
> However, these 2 protocol specification updates are required
> to be handled by the IETF 6MAN WG, simply as a matter
> of the applicable IETF WG charters and usual IETF processes.

The situation must be clear for everybody now. I fully support WGLC for 2 
draft-ietf-6man-* I-Ds to move forward.

Best Regards,
 	Janos Mohacsi