Re: [Int-area] Call for comment on draft-rahman-rtg-router-alert-considerations-02.txt

Francois Le Faucheur IMAP <flefauch@cisco.com> Wed, 29 July 2009 15:45 UTC

Return-Path: <flefauch@cisco.com>
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 094B93A6B93 for <int-area@core3.amsl.com>; Wed, 29 Jul 2009 08:45:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.207
X-Spam-Level:
X-Spam-Status: No, score=-10.207 tagged_above=-999 required=5 tests=[AWL=0.391, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 p-B7l+nLrx73 for <int-area@core3.amsl.com>; Wed, 29 Jul 2009 08:45:44 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id B72F33A6903 for <int-area@ietf.org>; Wed, 29 Jul 2009 08:45:43 -0700 (PDT)
X-IronPort-AV: E=Sophos; i="4.43,289,1246838400"; d="scan'208,217"; a="46082745"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 29 Jul 2009 15:45:44 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n6TFjiaS026155; Wed, 29 Jul 2009 17:45:44 +0200
Received: from xbh-ams-102.cisco.com (xbh-ams-102.cisco.com [144.254.73.132]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6TFjiRM009832; Wed, 29 Jul 2009 15:45:44 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by xbh-ams-102.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 29 Jul 2009 17:45:44 +0200
Received: from hakhan-unix.cisco.com ([10.61.103.203]) by xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 29 Jul 2009 17:45:43 +0200
Message-Id: <1A2ECBC5-6471-4085-9FFB-92CFBDED2C51@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
To: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
In-Reply-To: <alpine.DEB.2.00.0907291733060.684@melkinpaasi.cs.helsinki.fi>
Content-Type: multipart/alternative; boundary="Apple-Mail-3--7797619"
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 29 Jul 2009 17:45:41 +0200
References: <75DB09D8-DD8C-4874-99CB-423FB85B7FD0@cisco.com> <alpine.DEB.2.00.0907291733060.684@melkinpaasi.cs.helsinki.fi>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 29 Jul 2009 15:45:43.0500 (UTC) FILETIME=[A1BFF8C0:01CA1063]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=12852; t=1248882344; x=1249746344; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=flefauch@cisco.com; z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco. com> |Subject:=20Re=3A=20[Int-area]=20Call=20for=20comment=20on= 20draft-rahman-rtg-router-alert-considerations-02.txt |Sender:=20; bh=V02mAiRRZ0q52k/Vj4/JpaxqS1sMzwY+w+T1+lQFXSU=; b=u4pu9O9iZylyYAoQhb4hBUfWCokKNf4YFYTE7Sr0BakVRQdRAP4toBjOZS fMlLJeKf+fvKkOsg4b5zBynzcVNWPszTIPBmW4Jb3+yYGObEQ+UFEOHLBPpp 46BHL5/8uc;
Authentication-Results: ams-dkim-2; header.From=flefauch@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; );
Cc: int-area@ietf.org, "Reshad Rahman (rrahman)" <rrahman@cisco.com>, David Ward <dward@cisco.com>, Ashok Narayanan <ashokn@cisco.com>, Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: [Int-area] Call for comment on draft-rahman-rtg-router-alert-considerations-02.txt
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, 29 Jul 2009 15:45:46 -0000

Hello Jukka,

On 29 Jul 2009, at 16:37, Jukka MJ Manner wrote:

>
> Hi,
>
> I'll repeat here my comment that I gave on the mic.
>
> 1. I believe the point of the draft is to say that you should not  
> use RAO end-to-end across the Internet.

yes, that is one of the points the draft is trying to make.
 From our conversation, I believe your specific suggestion would be  
that section 3.1 is generalized to say e2e RAO is problematic, whether  
for new e2e application/protocol or for existing application/protocol  
(while it currently only explicitly mentions this for new application/ 
protocol). Right?

> If you have a closely controlled environment, RAO is okey, provided  
> that you know what you are doing

Again, from conversation, you'd like section 2 to make that point  
irrespective of whether we're talking about existing or (potentially  
new) protocol/application. Right?

> (and this part is what the document is trying to tell, describe the  
> more or less well-knwon problems with RAO). Yet, to me the message  
> is a bit fuzzy and unclear.

I think addressing the previous points would probably make things  
clearer. Feel free to propose additional specific suggestions.

>
> 2. IPv6 hop-by-hop options have the same problems, I guess.
>

Agreed. Suresh's draft http://tools.ietf.org/html/draft-krishnan-ipv6-hopbyhop-03 
  was also brought to our attention. I believe it argues that exact  
point.

For the sake of closing the RAO issue asap, I liked the idea of just  
focusing on RAO, but if the WG wants to kill the "hop-by-hop option"  
bird at the same time, I suppose we could. Opinions?

Thanks

Francois



>
> Cheers,
> Jukka
>
> On Thu, 23 Jul 2009, Francois Le Faucheur IMAP wrote:
>
>> Hello,
>> The Routing, Transport and Internet area directors have agreed to  
>> move the
>> work on Router Alert option (that started in Routing Area) into the  
>> Internet
>> Area.
>> Therefore, we would appreciate feedback from this list on the new  
>> version
>> of draft-rahman-rtg-router-alert-considerations.
>> Thank you
>> Francois
>> Begin forwarded message:
>>
>>      From: Internet-Drafts@ietf.org
>> Date: 3 July 2009 19:15:02 CEDT
>> To: i-d-announce@ietf.org
>> Subject: I-D
>> Action:draft-rahman-rtg-router-alert-considerations-02.txt
>> Reply-To: internet-drafts@ietf.org
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> Title           : IP Router Alert Considerations and Usage
>> Author(s)       : F. Le Faucheur
>> Filename        : draft-rahman-rtg-router-alert-considerations-02.txt
>> Pages           : 18
>> Date            : 2009-07-03
>> The IP Router Alert Option is an IP option that alerts transit
>> routers to more closely examine the contents of an IP packet.  RSVP,
>> PGM, IGMP/MLD and MRD are some of the protocols which make use of the
>> IP Router Alert option.  This document discusses security aspects,
>> common practices and usage guidelines around the use of the current
>> IP Router Alert option.  Specifically, it provides recommendations on
>> the use of Router Alert by new protocols, discusses controlled
>> environments where existing protocols depending on Router Alert can
>> be used effectively and discusses protection approaches for Service
>> Providers.  Finally it provides brief guidelines for Router Alert
>> implementation on routers.
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-rahman-rtg-router-alert-considera
>> tions-02.txt
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>> Below is the data which will enable a MIME compliant mail reader
>> implementation to automatically retrieve the ASCII version of the
>> Internet-Draft.
>> Content-Type: text/plain<BR>Content-ID:
>> &lt;2009-07-03101229.I-D@ietf.org&gt;<BR><BR>
>>      _______________________________________________
>>      I-D-Announce mailing list
>>      I-D-Announce@ietf.org
>>      https://www.ietf.org/mailman/listinfo/i-d-announce
>>      Internet-Draft directories: http://www.ietf.org/shadow.html
>>      or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>