Re: [Int-area] Reviews of "IP Router Alert Considerations" document

Roland Bless <roland.bless@kit.edu> Wed, 03 November 2010 16:58 UTC

Return-Path: <roland.bless@kit.edu>
X-Original-To: int-area@core3.amsl.com
Delivered-To: int-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 379703A69E7 for <int-area@core3.amsl.com>; Wed, 3 Nov 2010 09:58:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
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 SYb5y0EGXBNS for <int-area@core3.amsl.com>; Wed, 3 Nov 2010 09:58:42 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by core3.amsl.com (Postfix) with ESMTP id 01A1F28C0FA for <int-area@ietf.org>; Wed, 3 Nov 2010 09:58:42 -0700 (PDT)
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5]) by iramx2.ira.uni-karlsruhe.de with esmtps port 25 id 1PDgfY-0004QY-Eg; Wed, 03 Nov 2010 17:58:46 +0100
Received: from i72ms.tm.uni-karlsruhe.de ([141.3.70.5] helo=smtp.ipv6.tm.uni-karlsruhe.de) by irams1.ira.uni-karlsruhe.de with esmtps port 25 id 1PDgfY-0003fG-AN; Wed, 03 Nov 2010 17:58:40 +0100
Received: from vorta.tm.uka.de (i72vorta.tm.uni-karlsruhe.de [IPv6:2001:638:204:6:21b:fcff:fe96:fe02]) by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id 4012E2FC00A; Wed, 3 Nov 2010 17:58:40 +0100 (CET)
Received: from [IPv6:::1] (ip6-localhost [IPv6:::1]) by vorta.tm.uka.de (Postfix) with ESMTPS id E37111B9E; Wed, 3 Nov 2010 17:58:39 +0100 (CET)
Message-ID: <4CD194BF.5030909@kit.edu>
Date: Wed, 03 Nov 2010 17:58:39 +0100
From: Roland Bless <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.15) Gecko/20101027 Thunderbird/3.0.10
MIME-Version: 1.0
To: Francois Le Faucheur <flefauch@cisco.com>
References: <5CAADD76-8815-4681-B945-DD12C747B907@ericsson.com> <738EF258-9E5F-4867-AAAD-4E0D8A2D5224@cisco.com> <82CFD851-4918-4A8E-A76A-BE53F1B36EC4@ericsson.com>
In-Reply-To: <82CFD851-4918-4A8E-A76A-BE53F1B36EC4@ericsson.com>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (irams1.ira.uni-karlsruhe.de)
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-AV: Kaspersky (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1288803526.942091000
Cc: Area Mailing List <int-area@ietf.org>
Subject: Re: [Int-area] Reviews of "IP Router Alert Considerations" document
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Nov 2010 16:58:43 -0000

Hi,

I've got some more comments on
draft-ietf-intarea-router-alert-considerations-02.txt before WGLC:
Section 3:
>  Secondly, some protocols requiring punting may be
>    carried over a transport protocol (e.g., TCP or UDP) possibly because
>    they require the services of that transport protocol or perhaps
>    because the protocol does not justify allocation of a scarce next
>    level protocol value. 

You may add that one also gets discouraged using other protocols by
anticipated deployment problems due to firewalls and NATs filtering
"unknown" protocols.

> Therefore,
>    it is generally not possible to ensure that only the IP Router Alert
>    packets of interest are punted to the slow path while other IP Router
>    Alert packets are efficiently forwarded (i.e., in fast path).

This statement is IMHO misleading, because the following paragraph
actually points out that considering the value field is such a possibility.

> However, only one
>    value (zero) was defined in [RFC2113] and no IANA registry for IPv4
>    Router Alert values was available until recently. 

You may add a reference to [RFC5350] here:
was available until recently [RFC5350].

Regards,
 Roland