Re: Rogue Route Advertisement issues
Fred Baker <fred@cisco.com> Tue, 05 August 2008 18:44 UTC
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C70B03A69C4; Tue, 5 Aug 2008 11:44:19 -0700 (PDT)
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8AEA828C31E for <ipv6@core3.amsl.com>; Tue, 5 Aug 2008 11:44:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.569
X-Spam-Level:
X-Spam-Status: No, score=-104.569 tagged_above=-999 required=5 tests=[AWL=2.030, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OIRJIf+-yRX8 for <ipv6@core3.amsl.com>; Tue, 5 Aug 2008 11:44:17 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id ABA2628C324 for <ipv6@ietf.org>; Tue, 5 Aug 2008 11:44:17 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,311,1215388800"; d="scan'208";a="136100563"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-6.cisco.com with ESMTP; 05 Aug 2008 18:44:48 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id m75IimLV023309; Tue, 5 Aug 2008 11:44:48 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m75IimP1020346; Tue, 5 Aug 2008 18:44:48 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 5 Aug 2008 11:44:47 -0700
Received: from [10.242.24.125] ([10.21.90.40]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 5 Aug 2008 11:44:44 -0700
Message-Id: <CD0D1EF6-3078-4136-8D12-9186DB99AAF3@cisco.com>
From: Fred Baker <fred@cisco.com>
To: ipv6@ietf.org
In-Reply-To: <F8FE1754-14F9-4323-8CFA-4DCD0786EF87@cisco.com>
Mime-Version: 1.0 (Apple Message framework v926)
Subject: Re: Rogue Route Advertisement issues
Date: Tue, 05 Aug 2008 11:44:41 -0700
References: <F8FE1754-14F9-4323-8CFA-4DCD0786EF87@cisco.com>
X-Mailer: Apple Mail (2.926)
X-OriginalArrivalTime: 05 Aug 2008 18:44:44.0390 (UTC) FILETIME=[53EF3860:01C8F72B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=646; t=1217961888; x=1218825888; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:=20Fred=20Baker=20<fred@cisco.com> |Subject:=20Re=3A=20Rogue=20Route=20Advertisement=20issues |Sender:=20; bh=tHLWdSHUDEsfcVbdvwkgCE1fbimgnm9KEF6jpdat8BU=; b=DnlIYZM5PHWhsn9jp+la0rV12+eHd+NCjEc62UFvGs+1RGFiFsSnXIRanE 7jTPjY47cB1VOX1iQWpsgL5IkWjiBYPk18sXhTGQYOZjrtpDmPkGN1hhVr5e C93tpLSrZ4;
Authentication-Results: sj-dkim-4; header.From=fred@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
Cc: Ron Bonica <rbonica@juniper.net>, Sam Hartman <hartmans-ietf@mit.edu>, Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org
In two weeks, I plan to open a two week WGLC on two documents that address an issue in IPv6 Neighbor Discovery. They are: http://tools.ietf.org/html/draft-chown-v6ops-rogue-ra "Rogue IPv6 Router Advertisement Problem Statement", Tim Chown, Stig Venaas, 14-Jul-08, <draft-chown-v6ops-rogue-ra-01.txt> http://tools.ietf.org/html/draft-ietf-v6ops-ra-guard "IPv6 RA-Guard", Gunter Van de Velde, Eric Levy-Abegnoli, Chip Popoviciu, Janos Mohacsi, 30-Jun-08, <draft-ietf-v6ops-ra-guard-00.txt> Since this comments on 6man protocol usage, it seems appropriate to get 6man comments. Please comment to v6ops@ops.ietf.org -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
- Re: Rogue Route Advertisement issues Fred Baker