Re: [76attendees] Rogue IPv6 RA

Arifumi Matsumoto <> Mon, 09 November 2009 14:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7A5963A693F; Mon, 9 Nov 2009 06:31:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.557
X-Spam-Status: No, score=-2.557 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id UWJyCY5pceBq; Mon, 9 Nov 2009 06:31:02 -0800 (PST)
Received: from ( [IPv6:2001:fa8::25]) by (Postfix) with ESMTP id 2A61728C133; Mon, 9 Nov 2009 06:31:01 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by (8.14.3/8.14.3) with ESMTP id nA9EVQrV018433; Mon, 9 Nov 2009 23:31:27 +0900 (JST) (envelope-from
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset="us-ascii"; format="flowed"; delsp="yes"
From: Arifumi Matsumoto <>
In-Reply-To: <>
Date: Mon, 09 Nov 2009 23:33:16 +0900
Content-Transfer-Encoding: 7bit
Message-Id: <>
References: <> <> <>
To: Yuji Sekiya <>
X-Mailer: Apple Mail (2.1076)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 ( [IPv6:::1]); Mon, 09 Nov 2009 23:31:27 +0900 (JST)
Subject: Re: [76attendees] Rogue IPv6 RA
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 09 Nov 2009 14:31:03 -0000

let me CC to 6man ML,

Per RFC4861,

6.3.4.  Processing Received Router Advertisements
       - If the address is already present in the host's Default Router
         List and the received Router Lifetime value is zero,  
         time-out the entry as specified in Section 6.3.5.
6.3.5.  Timing out Prefixes and Default Routers

    Whenever the invalidation timer expires for a Prefix List entry,  
    entry is discarded.  No existing Destination Cache entries need be
    updated, however.  Should a reachability problem arise with an
    existing Neighbor Cache entry, Neighbor Unreachability Detection  
    perform any needed recovery.

    Whenever the Lifetime of an entry in the Default Router List  
    that entry is discarded.  When removing a router from the Default
    Router list, the node MUST update the Destination Cache in such a  
    that all entries using the router perform next-hop determination
    again rather than continue sending traffic to the (deleted) router.

I'm not sure what does "immediately time-out the entry as specified
in Section 6.3.5." mean.
Does it mean both paragraphs in 6.3.5. or just the latter paragraph ?

If the latter paragraph only should be executed, the address given
by rogue RA remains, right ?

On 2009/11/09, at 19:55, Yuji Sekiya wrote:

> At Mon, 9 Nov 2009 19:52:48 +0900,
> Arifumi Matsumoto wrote:
>> IIRC, routerlifetime and address lifetime is not correlated.
>> So, that address can be used for the source address for
>> outgoing sessions, right ?
> I think some of implementation bind prefix and its default
> router, so default router is expired, the prefix is not
> selected as source address.
> -- Yuji Sekiya