Re: IPv6 updates & related RA-Guard document
Mohacsi Janos <mohacsi@niif.hu> Wed, 26 September 2012 07:41 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 09B3B21F87E3 for <ipv6@ietfa.amsl.com>; Wed, 26 Sep 2012 00:41:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.296
X-Spam-Level:
X-Spam-Status: No, score=0.296 tagged_above=-999 required=5 tests=[AWL=-0.300, 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 JWxJYXBUAEMG for <ipv6@ietfa.amsl.com>; Wed, 26 Sep 2012 00:41:26 -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 2D8AF21F867C for <ipv6@ietf.org>; Wed, 26 Sep 2012 00:41:25 -0700 (PDT)
Received: from bolha.lvs.iif.hu (bolha.lvs.iif.hu [193.225.14.181]) by strudel.ki.iif.hu (Postfix) with ESMTP id 6F6AD389; Wed, 26 Sep 2012 09:41:24 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at bolha.lvs.iif.hu
Received: from strudel.ki.iif.hu ([IPv6:::ffff:193.6.222.244]) by bolha.lvs.iif.hu (bolha.lvs.iif.hu [::ffff:193.225.14.72]) (amavisd-new, port 10024) with ESMTP id mzxqPon2kjrP; Wed, 26 Sep 2012 09:41:21 +0200 (CEST)
Received: by strudel.ki.iif.hu (Postfix, from userid 9002) id 08A663A3; Wed, 26 Sep 2012 09:41:21 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by strudel.ki.iif.hu (Postfix) with ESMTP id 014F4389; Wed, 26 Sep 2012 09:41:20 +0200 (CEST)
Date: Wed, 26 Sep 2012 09:41:20 +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: <09ABA7A7-8FDE-43AA-B2E6-C4C501995C53@gmail.com>
Message-ID: <alpine.DEB.2.00.1209260938010.22890@strudel.ki.iif.hu>
References: <09ABA7A7-8FDE-43AA-B2E6-C4C501995C53@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 07:41:27 -0000
On Tue, 25 Sep 2012, RJ Atkinson wrote: > Hi, > > Work on the RA-Guard specification in another IETF WG > drove the creation of two I-Ds currently in this WG: > - draft-ietf-6man-nd-extension-headers > - draft-ietf-6man-oversized-header-chain > > The RA Guard work in the other IETF WG is currently > *blocked* pending the 6MAN WG approving the 2 I-Ds above. > > In turn, the RA Guard work is a high priority for all kinds > of network operators (i.e. not just ISPs), because it provides > practical risk reduction and risk mitigation for a real-world > operational security issue. > > RA Guard implementers can't really move forward until the > RA Guard I-D is approved by the other WG -- which I believe > is at present blocked on the 2 I-Ds at top being approved > by the 6MAN WG. > > My understanding is that the technical content in these > 2 IPv6 Spec update I-Ds has been presented more than once. > > Further, the drafts have been around long enough that active > 6MAN WG participants already should have read them. > > I am a bit confused about where we stand with these today, > so I have two questions: > > - Where does the 6MAN WG stand with these two drafts ? > > - How can we move them forward (soon -- i.e. BEFORE the > next IETF in-person meeting), so that the other active > IETF work (i.e. RA-Guard) can be unblocked ? 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. > > - Can these go into WG Last Call now ? > > Thanks, > > Ran > > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- >
- IPv6 updates & related RA-Guard document RJ Atkinson
- Re: IPv6 updates & related RA-Guard document Mohacsi Janos
- Re: IPv6 updates & related RA-Guard document Fernando Gont
- Re: IPv6 updates & related RA-Guard document RJ Atkinson
- Re: IPv6 updates & related RA-Guard document Mohacsi Janos