Re: Question: Hop-by-Hop Header and Router Alert

"Christopher Morrow" <christopher.morrow@gmail.com> Tue, 27 May 2008 01:53 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 B24AA28C161; Mon, 26 May 2008 18:53:23 -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 D6BC43A6C15 for <ipv6@core3.amsl.com>; Mon, 26 May 2008 18:53:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 qsKidBRCk3ha for <ipv6@core3.amsl.com>; Mon, 26 May 2008 18:53:22 -0700 (PDT)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.250]) by core3.amsl.com (Postfix) with ESMTP id E497528C161 for <ipv6@ietf.org>; Mon, 26 May 2008 18:53:21 -0700 (PDT)
Received: by an-out-0708.google.com with SMTP id d18so687848and.122 for <ipv6@ietf.org>; Mon, 26 May 2008 18:53:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=BobaOs/pz1z8jvMTQXxUFQSVTkHoYiYu0rAngFhh4k0=; b=P7w6nqNLX4ETAVVuExrAkmF6P0lT8EZTpVT9/8MiJufZ7oaLqP49+Lx8Dx5+sr+Zn+tHL4R22mwf/IFFN33qdRU6/NnoITdWnChlSl6hB1rSXrJ9I8396ev1YSnIEdvs/hA99pthcEpq+AFob1k1AZ4Ytald3bO9kCeoqRXnZJA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=uClEp3u09MvvRWMSjh+Fpu5zgqU767YCH76AHKBFgFzzujWQRY5lcOfRGHd0rQwNYV6cnBMeTRVzti0qMZKY+9Toit42JynGfY6i3lwJziz6sCZxRqkoMnh5iFhJCYE42zRH0Mu5/i3nygPnxiRZkNnWAqc4ZM531yYXAxhf2FM=
Received: by 10.100.46.10 with SMTP id t10mr838580ant.22.1211853203672; Mon, 26 May 2008 18:53:23 -0700 (PDT)
Received: by 10.100.14.14 with HTTP; Mon, 26 May 2008 18:53:23 -0700 (PDT)
Message-ID: <75cb24520805261853yfe9e25cw1e943745a28bbd7f@mail.gmail.com>
Date: Mon, 26 May 2008 21:53:23 -0400
From: Christopher Morrow <christopher.morrow@gmail.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: Question: Hop-by-Hop Header and Router Alert
In-Reply-To: <483B4395.2050605@ericsson.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <20080526133239.311900@gmx.net> <483B27A1.7040705@ericsson.com> <75cb24520805261609i61b2165cuf9470b1602399751@mail.gmail.com> <483B4395.2050605@ericsson.com>
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, May 26, 2008 at 7:11 PM, Suresh Krishnan
<suresh.krishnan@ericsson.com> wrote:
> Christopher Morrow wrote:
>>
>> On Mon, May 26, 2008 at 5:12 PM, Suresh Krishnan
>> <suresh.krishnan@ericsson.com> wrote:
>>>
>>> Hi Bernd,
>>>
>>> SpawnRR@gmx.de wrote:
>>>>
>>>> Hi all,
>>>>
>>>> I'm contacting you as I've a question regarding the Hop-by-Hop header
>>>> option 'Router Alert' and its exact use. I hope I don't disturb you...
>>>
>>> I am generally against any new proposal that uses hop by hop options
>>> (including router alerts) since they could increase the processing loads
>>> on intermediate routers and could be used as a DoS vector,
>>>
>>
>> most larger ip backbones today don't pay attention (drop/ignore)
>> Router-Alert ip-options in ipv4, I don't expect that trend to change
>> in ipv6... If you are planning on using hop-by-hop or router-alert in
>> ipv6 you probably are planning on a failed solution.
>
> Amen to that. I think the IETF needs to advise people to not use these to
> design new protocols. I did volunteer to write up a document stating just
> that, but there was sufficient interest in keeping these options alive.

what's confusing to me is that these survive while RH0 was
deprecated... they pose essentially the same sets of problems.

-Chris
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------