From flefauch@cisco.com Fri Jul 3 11:15:06 2009 Return-Path: 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 EC6CE28C323 for ; Fri, 3 Jul 2009 11:15:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.334 X-Spam-Level: X-Spam-Status: No, score=-10.334 tagged_above=-999 required=5 tests=[AWL=0.263, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=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 sVhdM9Rpi7xk for ; Fri, 3 Jul 2009 11:15:05 -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 B5CD528C316 for ; Fri, 3 Jul 2009 11:15:04 -0700 (PDT) X-Files: None : None X-IronPort-AV: E=Sophos;i="4.42,343,1243814400"; d="scan'208,217";a="44337614" Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 03 Jul 2009 18:15:27 +0000 Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n63IFRU0030311; Fri, 3 Jul 2009 20:15:27 +0200 Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n63IFR4E012156; Fri, 3 Jul 2009 18:15:27 GMT Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 3 Jul 2009 20:15:26 +0200 Received: from ams-flefauch-8712.cisco.com ([10.55.161.195]) by xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 3 Jul 2009 20:15:25 +0200 Message-Id: From: Francois Le Faucheur IMAP To: int-area@ietf.org Content-Type: multipart/alternative; boundary=Apple-Mail-46--97731741 Mime-Version: 1.0 (Apple Message framework v935.3) Date: Fri, 3 Jul 2009 20:15:24 +0200 References: <20090703171502.1ADE328C251@core3.amsl.com> X-Mailer: Apple Mail (2.935.3) X-OriginalArrivalTime: 03 Jul 2009 18:15:25.0931 (UTC) FILETIME=[3CF4ABB0:01C9FC0A] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=8536; t=1246644927; x=1247508927; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=flefauch@cisco.com; z=From:=20Francois=20Le=20Faucheur=20IMAP=20 |Subject:=20Call=20for=20comment=20on=20draft-rahman-rtg-ro uter-alert-considerations-02.txt=20 |Sender:=20; bh=8590fE2ozm/9AzMIB4lu5gIBhYxK1d7JhqEtkPJaCXc=; b=ozqb8jehlfGzR50i8j869QmN8FDdfRXkq9cHYApNJl5JobtDL1LfSnQSfM ocNeW6c6HeJ+EhvGem8w35ovAGEjMnuwspat7xevjVSGtCfG3bvwF0Bfg8CH RqrKuThsZW; Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; ); X-Mailman-Approved-At: Thu, 09 Jul 2009 00:17:34 -0700 Cc: Francois Le Faucheur IMAP , "Reshad \(rrahman\) Rahman" , Adrian Farrel , "Ashok Narayanan \(ashokn\)" , David Ward Subject: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jul 2009 18:15:07 -0000 --Apple-Mail-46--97731741 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit 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-considerations-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. > _______________________________________________ > 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 --Apple-Mail-46--97731741 Content-Type: multipart/mixed; boundary=Apple-Mail-47--97731741 --Apple-Mail-47--97731741 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable 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:

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 

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-rt= g-router-alert-considerations-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.
= --Apple-Mail-47--97731741 Content-Disposition: attachment; filename=mime-attachment Content-Type: message/external-body; x-unix-mode=0666; name="mime-attachment" Content-Transfer-Encoding: 7bit Content-Type: text/plain
Content-ID: <2009-07-03101229.I-D@ietf.org>

--Apple-Mail-47--97731741 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: 7bit
_______________________________________________
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

--Apple-Mail-47--97731741-- --Apple-Mail-46--97731741-- From remi.despres@free.fr Mon Jul 13 09:53:34 2009 Return-Path: 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 AEFDA28C4EC for ; Mon, 13 Jul 2009 09:53:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.78 X-Spam-Level: X-Spam-Status: No, score=-1.78 tagged_above=-999 required=5 tests=[AWL=0.169, BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3] 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 LOfl+znla-Yd for ; Mon, 13 Jul 2009 09:53:34 -0700 (PDT) Received: from smtp19.orange.fr (smtp19.orange.fr [80.12.242.18]) by core3.amsl.com (Postfix) with ESMTP id 53CA628C4EE for ; Mon, 13 Jul 2009 09:53:22 -0700 (PDT) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf1922.orange.fr (SMTP Server) with ESMTP id 43AC420000B8; Mon, 13 Jul 2009 18:53:34 +0200 (CEST) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf1922.orange.fr (SMTP Server) with ESMTP id 2E22C20000BE; Mon, 13 Jul 2009 18:53:34 +0200 (CEST) Received: from [193.248.104.44] (Mix-Lille-207-14-44.w193-248.abo.wanadoo.fr [193.248.104.44]) by mwinf1922.orange.fr (SMTP Server) with ESMTP id 9477020000B8; Mon, 13 Jul 2009 18:53:32 +0200 (CEST) X-ME-UUID: 20090713165332608.9477020000B8@mwinf1922.orange.fr In-Reply-To: <4A5B58D5.9030603@gmail.com> References: <4A5B58D5.9030603@gmail.com> Mime-Version: 1.0 (Apple Message framework v753.1) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <70E49167-5455-4A41-981E-0DC49F67816A@free.fr> Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= Date: Mon, 13 Jul 2009 18:53:26 +0200 To: Brian E Carpenter X-Mailer: Apple Mail (2.753.1) Cc: "Templin, Fred L" , Internet Area Subject: Re: [Int-area] Ramblings about RANGER and SAM X-BeenThere: int-area@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Internet Area Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jul 2009 16:53:34 -0000 Le 13 juil. 09 =E0 17:55, Brian E Carpenter a =E9crit : > Fred and R=E9mi, > > This may be a bit of a stretch, but I have the impression that > RANGER and SAM cannot both flourish, and that they would be > much stronger as a combined approach, with compromise on both > sides no doubt. There are clearly common points in RANGER and SAM. Whether they can been combined is still unclear to me, but discussing =20= it with Fred Templin in Stockholm should be interesting. > > In fact I think they both (like LISP) may not be quite radical > enough. > When I look at the issues of scope that are tackled in > draft-carpenter-behave-referral-object, I get a bit pessimistic. > However, I think we have to consider that trying to force all > address/scope semantics into the very conservative design of an > IPv6 address is probably hopeless. We took that conservative > design in 1994 because we were relying on a relatively rapid > dual-stack driven deployment; NATs and firewalls were largely > unknown. Not seeing so far what is missing with a SAM like approach, I am less =20= pessimistic. > I think it may be time to be more radical (as some people indeed > said in 1994). Which means a variable length self-describing > address format (as Louis Pouzin said in 1974). Variable length hierarchical addresses, with careful route selection =20 depending on used source addresses, seem to me sufficient do the job. > But the first > step towards that is a general framework for multiple addressing > domains, which I think both SAM and RANGER are trying to do. > > Unfortunately I will not be in Stockholm, but I'd appreciate > your reactions to these ramblings. Too bad you cannot be there. Regards, RD From touch@ISI.EDU Mon Jul 13 16:29:15 2009 Return-Path: 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 9EAB828C0FE for ; Mon, 13 Jul 2009 16:29:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.5 X-Spam-Level: X-Spam-Status: No, score=-2.5 tagged_above=-999 required=5 tests=[AWL=0.099, 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 r3CPE0MxDtDY for ; Mon, 13 Jul 2009 16:29:14 -0700 (PDT) Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 988B03A6E6B for ; Mon, 13 Jul 2009 16:28:57 -0700 (PDT) Received: from [75.217.188.140] (140.sub-75-217-188.myvzw.com [75.217.188.140]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id n6DNT2hu006063; Mon, 13 Jul 2009 16:29:04 -0700 (PDT) Message-ID: <4A5BC33E.1040301@isi.edu> Date: Mon, 13 Jul 2009 16:29:02 -0700 From: Joe Touch User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: "'Internet Area'" X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: touch@isi.edu Subject: [Int-area] new version (02) of draft-touch-intarea-ipv4-unique-id X-BeenThere: int-area@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Internet Area Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jul 2009 23:29:15 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, all, A new version of this doc has been posted. It has been substantially rewritten to be much simpler, with fewer MUST/MAY/SHOULD statements, and more explanation. Joe -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpbwz4ACgkQE5f5cImnZrt4YQCfaFXcB+aWp/Y8ZLMQie5e1eHi 4i0An2S12RZKraxI8KbV4uKYBudSwBky =kB5S -----END PGP SIGNATURE----- From Fred.L.Templin@boeing.com Tue Jul 14 18:43:37 2009 Return-Path: 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 5282A3A67D3 for ; Tue, 14 Jul 2009 18:43:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.115 X-Spam-Level: X-Spam-Status: No, score=-6.115 tagged_above=-999 required=5 tests=[AWL=0.484, BAYES_00=-2.599, 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 OoMD7Sv98PKx for ; Tue, 14 Jul 2009 18:43:36 -0700 (PDT) Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id 89C9C3A67A5 for ; Tue, 14 Jul 2009 18:43:36 -0700 (PDT) Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n6F1g6EM008570 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 14 Jul 2009 20:42:06 -0500 (CDT) Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n6F1g61q012996 for ; Tue, 14 Jul 2009 20:42:06 -0500 (CDT) Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n6F1g626012992 for ; Tue, 14 Jul 2009 20:42:06 -0500 (CDT) Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 14 Jul 2009 18:42:05 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Tue, 14 Jul 2009 18:42:04 -0700 Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A10629F375@XCH-NW-7V2.nw.nos.boeing.com> In-Reply-To: <4A5BC33E.1040301@isi.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: New version of SEAL (draft-templin-intarea-seal) Thread-Index: AcoEEdnk7cnXZjAARFSp+x8r/cTk+AA2pjbw References: <4A5BC33E.1040301@isi.edu> From: "Templin, Fred L" To: "Internet Area" X-OriginalArrivalTime: 15 Jul 2009 01:42:06.0224 (UTC) FILETIME=[75B81900:01CA04ED] Subject: [Int-area] New version of SEAL (draft-templin-intarea-seal) X-BeenThere: int-area@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Internet Area Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jul 2009 01:43:37 -0000 Hello, A new version of the SEAL document is available. This version is essentially a (bis) of the version in the RFC editor queue and makes a number of important improvements. In particular, there are now two "modes" of operation - a lightweight mode for performance critical routers connected to robust links and a fully functioned mode that supports larger packet sizes even up to IPv6 jumbogram size. There are a number of other features that bring substantial improvements. Please have a look at the new document version: http://tools.ietf.org/html/draft-templin-intarea-seal Fred fred.l.templin@boeing.com From remi.despres@free.fr Thu Jul 16 00:26:01 2009 Return-Path: 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 3942C3A6882 for ; Thu, 16 Jul 2009 00:26:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.607 X-Spam-Level: X-Spam-Status: No, score=-1.607 tagged_above=-999 required=5 tests=[AWL=0.342, BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3] 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 gSftEclbJG1h for ; Thu, 16 Jul 2009 00:25:59 -0700 (PDT) Received: from smtpfb2-g21.free.fr (smtpfb2-g21.free.fr [212.27.42.10]) by core3.amsl.com (Postfix) with ESMTP id 1F2193A6811 for ; Thu, 16 Jul 2009 00:25:57 -0700 (PDT) Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by smtpfb2-g21.free.fr (Postfix) with ESMTP id A1AE9CA9274 for ; Thu, 16 Jul 2009 09:23:48 +0200 (CEST) Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id CC4DAE080C7 for ; Thu, 16 Jul 2009 09:23:16 +0200 (CEST) Received: from [192.168.0.15] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by smtp6-g21.free.fr (Postfix) with ESMTP id DFAC8E080F3 for ; Thu, 16 Jul 2009 09:23:13 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v753.1) Content-Transfer-Encoding: 7bit Message-Id: <2023EE47-AAB1-4099-9FBF-1796835ABC84@free.fr> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: Internet Area From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= Date: Thu, 16 Jul 2009 09:23:06 +0200 X-Mailer: Apple Mail (2.753.1) Subject: [Int-area] SAM draft 03 available X-BeenThere: int-area@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Internet Area Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jul 2009 07:26:01 -0000 Hello all, A largely revised version of the draft on SAM is now available at http://www.ietf.org/internet-drafts/draft-despres-sam-03.txt TITLE: Scalable Multihoming across IPv6 Local-Address Routing Zones Global-Prefix/Local-Address Stateless Address Mapping (SAM) I will present it at the Intarea session on Wednesday July 29. SAM is a simple tool for hosts in multihomed sites to automatically send their e2e packets via the right ISP gateways. As such, it is complementary of Shim6 and SCTP in hosts that have multiple global addresses. It also has provision to extend autoconfiguration to delegated global prefixes, and supports a flexible hierarchy of local-addressing zones. Regards, RD PS: Apologies for having sent to the Intarea list comments about this draft before the document itself was announced. From karagian@cs.utwente.nl Fri Jul 17 05:07:32 2009 Return-Path: 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 8029F28C2CE for ; Fri, 17 Jul 2009 05:07:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.603 X-Spam-Level: * X-Spam-Status: No, score=1.603 tagged_above=-999 required=5 tests=[AWL=-0.307, BAYES_40=-0.185, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545] 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 LhXvF71M0CTd for ; Fri, 17 Jul 2009 05:07:31 -0700 (PDT) Received: from denhaag.ewi.utwente.nl (denhaag.ewi.utwente.nl [130.89.10.11]) by core3.amsl.com (Postfix) with ESMTP id 894A028C2C5 for ; Fri, 17 Jul 2009 05:07:31 -0700 (PDT) Received: from ewi977 (ewi977.ewi.utwente.nl [130.89.12.129]) by denhaag.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id n6HC7evf024845 for ; Fri, 17 Jul 2009 14:07:46 +0200 (MEST) From: "Georgios Karagiannis" To: Date: Fri, 17 Jul 2009 14:07:51 +0200 Message-ID: <001d01ca06d7$3a008b90$810c5982@dynamic.ewi.utwente.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 Thread-Index: AcoG1zVwqAk9EIWTQdSpVBUBfsG+hw== X-Scanned-By: MIMEDefang 2.52 on 130.89.10.11 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3 (denhaag.ewi.utwente.nl [130.89.10.11]); Fri, 17 Jul 2009 14:07:47 +0200 (MEST) Subject: [Int-area] draft on requirements imposed by traffic safety applications on network/transport layers X-BeenThere: int-area@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Internet Area Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jul 2009 12:07:32 -0000 Hi all A new Internet draft has been submitted to the IETF that describes a number of communication performance requirements that are imposed by traffic safety applications on a network layer, see: http://www.ietf.org/internet-drafts/draft-karagiannis-traffic-safety-require ments-00.txt These traffic safety applications and requirements have been derived during the VSC (Vehicular Safety Communications) and VSC-A (VSC-Applications) projects. Currently, the standardization activities within the IEEE 1609 and ISO TC 204 are considering that traffic safety applications can only be supported by non-IP based netwok and transport solutions. The goal of this document is to stimulate the discussion on judging whether these performance requirements could or could not be supported (currently and in the future) by IP based network and transport solutions. We are wondering whether this draft could be discussed in the Intarea session (July 29) or within another meeting during the 75th IETF in Stockholm, Sweden. Best regards, Georgios From christian.vogt@ericsson.com Mon Jul 20 14:22:37 2009 Return-Path: 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 1E72A3A6A20 for ; Mon, 20 Jul 2009 14:22:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.746 X-Spam-Level: X-Spam-Status: No, score=-5.746 tagged_above=-999 required=5 tests=[AWL=-0.277, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, 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 zEfEsZwEOU3S for ; Mon, 20 Jul 2009 14:22:36 -0700 (PDT) Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) by core3.amsl.com (Postfix) with ESMTP id 6E77B3A67D7 for ; Mon, 20 Jul 2009 14:22:36 -0700 (PDT) Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id n6KLKp8k015358 for ; Mon, 20 Jul 2009 16:20:52 -0500 Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.56]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Mon, 20 Jul 2009 16:20:32 -0500 Received: from [155.53.229.41] ([155.53.229.41]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Mon, 20 Jul 2009 16:20:32 -0500 Message-Id: <8AF7F472-82F5-4A04-8673-9AC8DE0ACE92@ericsson.com> From: Christian Vogt To: Internet Area Mailing List Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Mon, 20 Jul 2009 14:20:33 -0700 X-Mailer: Apple Mail (2.935.3) X-OriginalArrivalTime: 20 Jul 2009 21:20:32.0735 (UTC) FILETIME=[EA2636F0:01CA097F] Subject: [Int-area] Revision: Harmfulness Analysis of Address Translator Designs X-BeenThere: int-area@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Internet Area Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2009 21:22:37 -0000 Dear all - I would like to notify you about a revision of the NAT design analysis that I had written as input to the discussion around NAT for IPv6. The revision addresses the feedback I had received, and adds the missing references to the document. http://tools.ietf.org/html/draft-vogt-address-translation-harmfulness Further comments are welcome. - Christian From flefauch@cisco.com Thu Jul 23 02:11:04 2009 Return-Path: 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 006743A6B0A for ; Thu, 23 Jul 2009 02:11:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.598 X-Spam-Level: X-Spam-Status: No, score=-8.598 tagged_above=-999 required=5 tests=[AWL=2.000, 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 MIHn6ntEu0Nk for ; Thu, 23 Jul 2009 02:11:02 -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 C8C5B3A6AAF for ; Thu, 23 Jul 2009 02:11:01 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: An8AAMbFZ0qQ/uCKe2dsb2JhbACCJhUYlx4BARYkBp0jiCWQdwWEDQ X-IronPort-AV: E=Sophos;i="4.43,253,1246838400"; d="scan'208,217";a="45658028" Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 23 Jul 2009 09:10:51 +0000 Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n6N9Apin004949 for ; Thu, 23 Jul 2009 11:10:51 +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 n6N9ApUX016523 for ; Thu, 23 Jul 2009 09:10:51 GMT Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by xbh-ams-102.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 23 Jul 2009 11:10:51 +0200 Received: from ams-flefauch-8716.cisco.com ([10.55.161.199]) by xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Jul 2009 11:10:50 +0200 Message-Id: <75DB09D8-DD8C-4874-99CB-423FB85B7FD0@cisco.com> From: Francois Le Faucheur IMAP To: int-area@ietf.org Content-Type: multipart/alternative; boundary=Apple-Mail-3--549890250 Mime-Version: 1.0 (Apple Message framework v935.3) Date: Thu, 23 Jul 2009 11:10:49 +0200 X-Mailer: Apple Mail (2.935.3) X-OriginalArrivalTime: 23 Jul 2009 09:10:51.0146 (UTC) FILETIME=[798726A0:01CA0B75] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=8862; t=1248340251; x=1249204251; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=flefauch@cisco.com; z=From:=20Francois=20Le=20Faucheur=20IMAP=20 |Subject:=20Call=20for=20comment=20on=20draft-rahman-rtg-ro uter-alert-considerations-02.txt |Sender:=20; bh=s/3WFGO2qnwLoIv1iHyqUuVg3wlLi0il+DusUO3VayU=; b=hBu5h1hZgwmAKdZRlo+Znf1FY0Q0Q4y0kqYXENYGs7SaPfCBQlldoD0zDQ IhC86T/Gwu1yiaSbtcj7e90cxISs2FI0bOtcnwZuQ/lzwHZMi0luFaoKL1ts sbd+FsqAwe; Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; ); Subject: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2009 09:11:04 -0000 --Apple-Mail-3--549890250 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit 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-considerations-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
Content-ID: <2009-07-03101229.I-D@ietf.org >

> _______________________________________________ > 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 --Apple-Mail-3--549890250 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable
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 

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-rt= g-router-alert-considerations-02.txt

Internet-Drafts are also = available by anonymous FTP at:
ftp://ftp.ietf.org/internet-d= rafts/

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.or= g&gt;<BR><BR>
_______________________________________________
I-D-= Announce mailing list
I-D-Announce@ietf.org
https://www.ie= tf.org/mailman/listinfo/i-d-announce
Internet-Draft = directories: http://www.ietf.org/shadow.html
or 
ftp://ftp.ietf.org/ietf= /1shadow-sites.txt

= --Apple-Mail-3--549890250-- From rdroms@cisco.com Sun Jul 26 02:23:29 2009 Return-Path: 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 6940D3A68D5 for ; Sun, 26 Jul 2009 02:23:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 RpU-0wZZktnL for ; Sun, 26 Jul 2009 02:23:28 -0700 (PDT) Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id A39FF3A689E for ; Sun, 26 Jul 2009 02:23:28 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAAa+a0qrR7PD/2dsb2JhbAC3IYgojhYFhA0 X-IronPort-AV: E=Sophos;i="4.43,271,1246838400"; d="scan'208";a="189711511" Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-2.cisco.com with ESMTP; 26 Jul 2009 09:23:29 +0000 Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n6Q9NTJO018615 for ; Sun, 26 Jul 2009 02:23:29 -0700 Received: from sjc-vpnasa-493.cisco.com (sjc-vpnasa-493.cisco.com [10.21.105.239]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n6Q9NSCY001075 for ; Sun, 26 Jul 2009 09:23:29 GMT Message-Id: From: Ralph Droms To: int-area@ietf.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Sun, 26 Jul 2009 11:23:28 +0200 X-Mailer: Apple Mail (2.935.3) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=111; t=1248600209; x=1249464209; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rdroms@cisco.com; z=From:=20Ralph=20Droms=20 |Subject:=20meeting=20and=20jabber=20scribes=20for=20intare a=20meeting |Sender:=20; bh=2uWm9+BpuQKktE8u9sLWwKjrqhKQAaM9ODzyaFUvNAU=; b=EDmQeq2O4JKjZobD/T11/Mb9jYwZDPD4luuJjMV/VrlBLzucArD4R8j8uK ng3G9KRSclIpynOYrtkrF8wUeFfDE7Alk7vlerJ//U+hWTD4V8SNGQQBeJfq cio0HsVMfd; Authentication-Results: sj-dkim-3; header.From=rdroms@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); Subject: [Int-area] meeting and jabber scribes for intarea meeting X-BeenThere: int-area@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Internet Area Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jul 2009 09:23:29 -0000 Please let me know if you're willing to act as a scribe for the intarea meeting, Wed 1510-1610. - Ralph From rdroms@cisco.com Wed Jul 29 01:34:25 2009 Return-Path: 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 6D8FB3A6BC8 for ; Wed, 29 Jul 2009 01:34:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.201 X-Spam-Level: X-Spam-Status: No, score=-6.201 tagged_above=-999 required=5 tests=[AWL=0.398, BAYES_00=-2.599, 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 NWlPnijZdEG5 for ; Wed, 29 Jul 2009 01:34:24 -0700 (PDT) Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 9A9363A69C1 for ; Wed, 29 Jul 2009 01:34:24 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAN+lb0qrR7PE/2dsb2JhbAC7VognkCMFhBA X-IronPort-AV: E=Sophos;i="4.43,288,1246838400"; d="scan'208";a="356124005" Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-6.cisco.com with ESMTP; 29 Jul 2009 08:34:26 +0000 Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n6T8YQpl011497 for ; Wed, 29 Jul 2009 01:34:26 -0700 Received: from sjc-vpnasa-649.cisco.com (sjc-vpnasa-649.cisco.com [10.21.106.140]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id n6T8YPsd014254 for ; Wed, 29 Jul 2009 08:34:26 GMT Message-Id: From: Ralph Droms To: int-area@ietf.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Wed, 29 Jul 2009 10:34:24 +0200 X-Mailer: Apple Mail (2.935.3) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=348; t=1248856466; x=1249720466; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rdroms@cisco.com; z=From:=20Ralph=20Droms=20 |Subject:=20(SECOND=20TRY)=20meeting=20and=20jabber=20scrib es=20for=20intarea=20meeting |Sender:=20; bh=PsniKjj1lmuTK7b3JdQIr/zO/HdfipzEntbyoQpSUOU=; b=UWZQcWqEF9TkiZyQH+sothb6iwSRmOozEpjjkTdDmftOfKC+xeCjF8z+Tn IJ5ryJOn9OjW98IvjffGcNEWnvI93w4aAcNNMnuVt5PzD+8G483U4G/tbUkE qCzrBteKf3; Authentication-Results: sj-dkim-4; header.From=rdroms@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); Subject: [Int-area] (SECOND TRY) meeting and jabber scribes for intarea meeting X-BeenThere: int-area@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Internet Area Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jul 2009 08:34:25 -0000 Our agenda will be very tight at the intarea meeting. We can save time by identifying volunteer scribes before the meeting. Please let me know if you're willing to act as a scribe for the intarea meeting, Wed 1510-1610. Also, I could use a volunteer to drive presentations and handle other logistics during the meeting. - Ralph From jmanner@cs.Helsinki.FI Wed Jul 29 07:37:10 2009 Return-Path: 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 7438D3A6BD8 for ; Wed, 29 Jul 2009 07:37:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 LI6XTkj1Nngv for ; Wed, 29 Jul 2009 07:37:09 -0700 (PDT) Received: from mail.cs.helsinki.fi (courier.cs.helsinki.fi [128.214.9.1]) by core3.amsl.com (Postfix) with ESMTP id 6FC423A6E47 for ; Wed, 29 Jul 2009 07:37:09 -0700 (PDT) Received: from melkinpaasi.cs.helsinki.fi (melkinpaasi.cs.helsinki.fi [128.214.11.93]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by mail.cs.helsinki.fi with esmtp; Wed, 29 Jul 2009 17:37:09 +0300 id 00063E0A.4A705E95.000074FC Date: Wed, 29 Jul 2009 17:37:09 +0300 (EEST) From: Jukka MJ Manner To: Francois Le Faucheur IMAP In-Reply-To: <75DB09D8-DD8C-4874-99CB-423FB85B7FD0@cisco.com> Message-ID: References: <75DB09D8-DD8C-4874-99CB-423FB85B7FD0@cisco.com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-696230645-2037729606-1248878229=:684" Cc: int-area@ietf.org 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jul 2009 14:37:10 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---696230645-2037729606-1248878229=:684 Content-Type: TEXT/PLAIN; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8BIT 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. If you have a closely controlled environment, RAO is okey, provided that you know what you are doing (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. 2. IPv6 hop-by-hop options have the same problems, I guess. 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
Content-ID: > <2009-07-03101229.I-D@ietf.org>

> _______________________________________________ > 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 > > > > ---696230645-2037729606-1248878229=:684-- From flefauch@cisco.com Wed Jul 29 08:45:46 2009 Return-Path: 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 ; 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 ; 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 ; 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 To: Jukka MJ Manner In-Reply-To: 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> 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 |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\)" , David Ward , Ashok Narayanan , Adrian Farrel 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jul 2009 15:45:46 -0000 --Apple-Mail-3--7797619 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit 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
Content-ID: >> <2009-07-03101229.I-D@ietf.org>

>> _______________________________________________ >> 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 >> --Apple-Mail-3--7797619 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable 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.
=46rom 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

Francoi= s




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
<= /blockquote>
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&n= bsp;
Reply-To: internet-drafts@ietf.org
<= /blockquote>
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-ale= rt-considera
tions-02.txt
Internet-Drafts are also available by anonymous FTP = at:
ftp://ftp.ietf.org/internet-d= rafts/
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.or= g&gt;<BR><BR>
=      ____________________________________________= ___
=      I-D-Announce mailing = list
=      I-D-Announce@ietf.org
     https://www.ie= tf.org/mailman/listinfo/i-d-announce
     Internet-Draft = directories: http://www.ietf.org/shadow.html
=      or ftp://ftp.ietf.org/ietf= /1shadow-sites.txt

= --Apple-Mail-3--7797619--