Re: Question: Hop-by-Hop Header and Router Alert
Pekka Savola <pekkas@netcore.fi> Tue, 27 May 2008 04:55 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 A5C813A6B40; Mon, 26 May 2008 21:55:24 -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 478F43A6AEC for <ipv6@core3.amsl.com>; Mon, 26 May 2008 21:55:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_51=0.6]
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 NPdTDwCDP-Qf for <ipv6@core3.amsl.com>; Mon, 26 May 2008 21:55:22 -0700 (PDT)
Received: from netcore.fi (eunet-gw.ipv6.netcore.fi [IPv6:2001:670:86:3001::1]) by core3.amsl.com (Postfix) with ESMTP id 0ABAF3A68D1 for <ipv6@ietf.org>; Mon, 26 May 2008 21:55:21 -0700 (PDT)
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.13.8/8.13.8) with ESMTP id m4R4tGei029476; Tue, 27 May 2008 07:55:16 +0300
Received: from localhost (pekkas@localhost) by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id m4R4tGSL029472; Tue, 27 May 2008 07:55:16 +0300
Date: Tue, 27 May 2008 07:55:16 +0300
From: Pekka Savola <pekkas@netcore.fi>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: Question: Hop-by-Hop Header and Router Alert
In-Reply-To: <483B27A1.7040705@ericsson.com>
Message-ID: <alpine.LRH.1.10.0805270750580.29077@netcore.fi>
References: <20080526133239.311900@gmx.net> <483B27A1.7040705@ericsson.com>
User-Agent: Alpine 1.10 (LRH 962 2008-03-14)
MIME-Version: 1.0
X-Virus-Scanned: ClamAV 0.93/6816/Fri Apr 18 03:41:09 2008 on otso.netcore.fi
X-Virus-Status: Clean
Cc: SpawnRR@gmx.de, ipv6@ietf.org
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org
On Mon, 26 May 2008, Suresh Krishnan wrote: >> Second question: >> >> What will happen if a router doesn?t recognize the value in the >> router alert?s value field? Will it continue parsing the datagram >> and then forward the packet to the next hop (two MSB in the >> Hop-by-Hop option type field set to ?00?), or will it immediately >> stop parsing and forward the received IPv6 packet to the next >> hop (two MSB in the Hop-by-Hop option type field set to ?00?)? > > The router code will not see this as an error. It will forward the > packet through as if nothing happened. This is required for incremental > deployment(e.g. non RSVP routers among RSVP routers) FWIW, I share Suresh's sentiments about Hop-by-Hop and Router Alert options :-) FYI, here is discussion on what Linux does (which is a bit different given that there is no strict fast/slow path separation). An application running on the router needs to set IPV6_ROUTER_ALERT sockopt with value of the desired RA option it wants to see. Other messages are not delivered to the application and are forwarded as normal. If some application gets the packet, it is responsible for re-injecting a new packet: http://www.mail-archive.com/netdev@vger.kernel.org/msg50634.html -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
- Question: Hop-by-Hop Header and Router Alert SpawnRR
- Re: Question: Hop-by-Hop Header and Router Alert Suresh Krishnan
- Re: Question: Hop-by-Hop Header and Router Alert Christopher Morrow
- Re: Question: Hop-by-Hop Header and Router Alert Suresh Krishnan
- Re: Question: Hop-by-Hop Header and Router Alert Christopher Morrow
- Re: Question: Hop-by-Hop Header and Router Alert Pekka Savola
- Re: Question: Hop-by-Hop Header and Router Alert SpawnRR